Installation & Configuration Guide Service Delivery Engine (SDE

)
Release 5.60 For Fairshare Part Number: 05-00095 Rev. C04 July 8, 2010

Installation & Configuration Guide: Service Delivery Engine Release 5.60 Rev. C04 For Fairshare Part Number: 05-00095-C04 Last modified: July 8, 2010 The most current version of this document is available on Sandvine’s support web site at https://support.sandvine.com/ This document and the product described within are copyrighted. Under copyright laws, neither this document nor the product may be reproduced, translated or reduced to any electronic medium or machine readable or other form without prior written authorization from Sandvine Incorporated. Copyright 2007 - 2010, Sandvine Incorporated. All rights reserved. Sandvine Incorporated™ and Sandvine Leaf design are trademarks of Sandvine. All other product names mentioned herein are trademarks of their respective owners. The following are trademarks of Sandvine: Sandvine Incorporated™ Powering IP Services™ Sandvine Virtual Switch Cluster™ Intelligent Broadband Networks™ Sandvine Incorporated shall not be liable for technical or editorial errors or omissions contained herein; nor for incidental or consequential damages resulting from the furnishing, performance or use of this material. Information in this document is subject to change without notice. Sandvine is committed to ensuring the accuracy of our documentation and to continuous improvement. If you encounter errors or omissions in this user guide, or have comments, questions or ideas, we welcome your feedback. Please send your comments to Sandvine via e-mail at support@sandvine.com.

Contents
List of figures...................................................................7 List of tables....................................................................9 Chapter
1

Deployment overview...................................................... 11
Installation guide overview...................................................... 13 Hardware requirements.......................................................... 14
Minimum server requirements.................................................. 14 Hardware verification............................................................ 14 Operating system................................................................. 15

Network requirements for SDE installation................................... 16
Dummy VIPs........................................................................ 16 Virtual IPs for SDE services...................................................... 17

Deployment architecture........................................................ 18
Data collection.................................................................... Fairshare enforcement........................................................... Sample deployment configurations............................................ SDE clusters........................................................................ 18 18 19 21

Installation prerequisites........................................................ 24
Pre-installation requirements................................................... 24 VIP requirements.................................................................. 26 RHEL 5.4 installation packages................................................. 26

Requesting a support account.................................................. 28

Chapter

2

Installing the management cluster...................................... 29
Pre-installation check list....................................................... 31 Management cluster overview.................................................. 32 Creating RHEL accessibility to yum............................................ 33 Local yum installation............................................................ 35 Configuring yum to install the SDE from an FTP site or HTTP server..... 37 Installing the SDE software from the yum repository....................... 39 Installation verifications......................................................... 41 Installation troubleshooting..................................................... 44
Missing dependencies............................................................. 44 yum troubleshooting.............................................................. 44 SDE machine hostname.......................................................... 45

Logging into the EMS............................................................. 46
EMS access options................................................................ 46
Fairshare Installation & Configuration Guide: Release 5.60 Rev. C04
05-00095-C04 July 8, 2010 1

............ 70 71 71 71 71 72 Installation checks and troubleshooting........................................ 58 Second SDE machine............ 77 Configuring SDE parameters.............................................................................................................. Configuring the outbound IPDR relay........... 60 Adding SDE nodes....................................... 50 Configuring the services........ 2010 05-00095-C04 .................. 80 Log parameters... 84 Fairshare parameters...................... 73 Cluster installation complete..................................... 73 Chapter 4 Global SDE parameters................................................................................................................................................. 53 Attaching new services to the SDE node..................................................................properties file............................................... Configuring the edge VIP(s).............................................................. Attaching the services................... Changing the border VIP in the fsam_conf.......................................... 63 SDE system view........................... 83 WSAM parameters............ Changing the border VIP in the fsam_conf.... 68 Installing the SDE software....................................................................................................................................................... Configuring a second edge VIP............................................................ 70 Adding SDE nodes...........................properties file...................................... 57 Configuring the outbound IPDR relay............ 75 Overview of SDE parameters...... 78 Garbage gates............................. Adding an edge service................................................................................................. Attaching services to the new node........................................................ C04 July 8.............. 47 Configuring the management machine...................................................................................................................Windows EMS installation...............................................60 Rev.......................................................................properties file......................................................................... 46 Installing the X Window System package group............................................................. 60 61 61 61 62 62 Installation checks and troubleshooting............................................... 50 Configuring the WSAM service.............. 81 COPS parameters.................................. 69 Configuring the nodes....... 55 Changing the border VIP in the fsam_conf............................ Configuring the outbound relay.............. 67 Cluster overview..................................... 65 Chapter 3 Adding additional clusters................................................................. 47 EMS login sequence...... 63 Cluster installation complete......................................... 77 General parameters......................................................... 85 2 Fairshare Installation & Configuration Guide: Release 5.............................................................................. SDE node parameters...............................................

................................... 109 Map import process... 107 Viewing CMTSs in the EMS following import............ 95 Import CMTSs/CMTS maps overview.............................. 119 Configuring the SPB to the SDE.. 117 Excluding subnets...................................................................................................................... 96 Import CMTSs........................... 2010 3 ....................... 131 SNMP agent..................................................... IPDR collection parameters................. 97 CSV data file....60 Rev......................................... 126 Application server parameters.............................................................................. 108 Import CMTS maps............................................................................................................................................................................ 127 RKS parameters............................................................................................................ 133 SNMP parameters......................................................................................................................................... 92 Chapter 5 Import CMTSs...... SPB collection parameters...................................................................................... 86 General data collection parameters........................................................................................................................................... 132 Configuring trap receivers.. 123 Application managers................. 118 SPB configuration process.......................... 120 Chapter 7 Configuring additional network elements to the system..................................................... 125 Application servers............................ 86 89 89 90 Subscriber mapping parameters........................... 105 Importing CMTS lists...................... 133 Fairshare Installation & Configuration Guide: Release 5................................................. 124 Application manager parameters................ 119 Mapping edge services to SPBs.... 126 Record Keeping Servers (RKSs)........................................... 117 Excluding individual IPs....................................... 101 Importing CMTSs when using inbound IPDR relay............................................. 110 Chapter 6 Configuring SPB connections.................................Data collection parameters........... 109 CMTS maps XML description file..................................................................... 128 Chapter 8 SNMP............................................................................................................................................................................................................................................ 97 CMTS XML description file...................................................................................... 113 SPB configuration overview...... C04 05-00095-C04 July 8..................................................... SNMP collection parameters.............. 100 CMTS and IPDR session attributes............ 107 Import errors............................................................. 114 IP exclusions.......

.......................... 144 Post-upgrade procedures................................. 143 Upgrade process...... 152 Appendix B External configuration procedures.............................. 137 Chapter 10 NetPortal........................... 152 SCP program........................................................................................................................... 166 CMTS.................................. 164 Configuring CMTS maps........ 155 Configuring CMTSs through the EMS....................................................................................................................................... 149 Configuring SSL between EMS and SDE.... 162 Manually configuring CMTS interfaces and maps.. 2010 05-00095-C04 ....................................... 136 Configuring SDE nodes for reports..................................................... 171 4 Fairshare Installation & Configuration Guide: Release 5......................................................................................................................................................... 164 Configuring CMTSs through the CLI.................................................................................... 153 Application Servers........................... 140 NetPortal installation.............................................................. 152 SFTP program.... 150 Changing the location of the log files................................................................................Chapter 9 Reports....................................60 Rev.................... C04 July 8............... 147 Appendix A Additional install procedures.............................................................. 156 CMTS parameters.............................................................................. 151 Transferring files to the SDE machine.................................................. 158 Configuring IPDR sessions..................................................... 135 Reports overview........................... 167 Appendix D Example XML description files for CMTS import.................................................................................................................................................... 166 Using the CLI......................... 154 Appendix C Manually configuring CMTSs............................. 139 NetPortal overview. 142 Edge service.......................... 142 Chapter 11 SDE upgrade........... 166 Accessing the CLI................................................................................. 141 Configuring the NetPortal services......................................... 142 Management service....... 164 Manually configuring CMTS interfaces and maps................................. 145 APPENDICES..............................................................................................................

.......................................................60 Rev............................. 180 Index........................................................ 179 Ports used for SDE communications............................................... 2010 5 ................. C04 05-00095-C04 July 8.................................................................................... 177 SDE uninstall procedure....Example XML description file for IPDR collection and PCMM enforcement.............................. 178 Appendix F SDE ports....................................... 185 Fairshare Installation & Configuration Guide: Release 5........................................................ 172 Example XML description file for SPB data collection and PCMM-PTS enforcement.................. 174 Appendix E Uninstalling the SDE...

6 Fairshare Installation & Configuration Guide: Release 5. 2010 05-00095-C04 .60 Rev. C04 July 8.

.......................................................118 New SPB dialog box................. C04 05-00095-C04 July 8...................................................................................................................................................................................................................55 Attached SDE services.....................................................60 New SDE Node dialog box....156 New IPDR Session dialog box.........128 New Trap Receiver dialog box......................................164 Fairshare Installation & Configuration Guide: Release 5......20 External IPDR data collection and PCMM enforcement.................................................................................124 New AS dialog box............................................................133 Add SDE Report View dialog box.....................53 New Service dialog box.................................................................................107 Import CMTS Maps dialog box...................................................................................111 New IP dialog box...............................................................................................127 New Primary RKS dialog box...................117 New Subnet dialog box..............................................................................................................................19 Internal IPDR collection and PCMM enforcement ......................................................................21 Support registration dialog box.......54 Expanded SDE node list...............126 New RKS dialog box..................60 Rev..................50 New Service dialog box....................................48 Virtual IP dialog box...........137 New CMTS dialog box......119 New AM dialog box...............28 EMS login dialog box.............................................................................162 New Subnet dialog box.........................................................................................List of figures SPB collection and PTS enforcement via the SPB...................... 2010 7 ................56 New SDE Node dialog box...............................................70 Import CMTS List dialog box.........................................................................

C04 July 8.60 Rev.8 Fairshare Installation & Configuration Guide: Release 5. 2010 05-00095-C04 .

.................................................81 Table 10: COPS parameters.................................................................................129 Table 24: SNMP parameters................120 Table 20: AM attributes......................................................83 Table 11: WSAM parameters................................................................................................165 Table 28: Communications ports..........................................................................162 Table 27: CMTS interfaces and maps ..............................................................................................133 Table 25: CMTS EMS parameters......................................................... C04 05-00095-C04 July 8.............................16 Table 4: Pre-installation check list.............................................................................158 Table 26: IPDR session parameters....................................................List of tables Table 1: Hardware requirements.......................61 Table 8: General parameters...180 Fairshare Installation & Configuration Guide: Release 5.....................126 Table 22: RKS values...................................86 Table 14: SNMP collection parameters.. 2010 9 ...............60 Rev.....................................78 Table 9: Log parameters.............51 Table 6: Services parameters/nodes...............85 Table 13: General data collection parameters...................................84 Table 12: Fairshare parameters................................................................................90 Table 16: SPB collection parameters....................................................................................91 Table 17: Subscriber mapping and P2SPB parameters...............................................15 Table 3: SDE cluster IP requirements for multiple subnets...............................................31 Table 5: VIP parameters.........128 Table 23: RKS primary/secondary parameters................................................................................92 Table 18: Attributes for CMTS import...............................................................101 Table 19: SPB parameters...............89 Table 15: IPDR collection parameters.......14 Table 2: Partitions..........................54 Table 7: SDE node parameters..................................125 Table 21: Application server attributes.

10 Fairshare Installation & Configuration Guide: Release 5. C04 July 8. 2010 05-00095-C04 .60 Rev.

The following topics are included in this chapter: • • “Installation guide overview” on page 13 — explains the purpose of this guide “Hardware requirements” on page 14 — presents the hardware and operating system requirements prior to SDE software installation “Network requirements for SDE installation” on page 16 — explains the different types of IP addresses required for the SDE machine and software “Deployment architecture” on page 18 — describes the deployment architecture in a multi-cluster environment “Installation prerequisites” on page 24 — explains the necessary preparations on the SDE machine prior to SDE software installation 1 • • • .Deployment overview This chapter provides an overview of the necessary concepts and procedures required for installing and configuring the SDE for Fairshare Traffic Management. It also lists the installation prerequisites for each SDE machine and cluster.

2010 05-00095-C04 .60 Rev.Chapter 1: Deployment overview • “Requesting a support account” on page 28 — explains how to open a Sandvine customer support account 12 Fairshare Installation & Configuration Guide: Release 5. C04 July 8.

regarding hardware requirements. Following completion of all steps in this guide. to the system. installation prerequisites. It also provides explanatory information. Fairshare Installation & Configuration Guide: Release 5. and the services and virtual IP addresses used by the SDE.60 Rev. this guide explains how to configure all external network elements. C04 05-00095-C04 July 8. included in this chapter. They navigate the operator through the steps for installing and configuring an SDE cluster that contains all the management functionality. 2010 13 . the SDE system can be configured for Fairshare. such as CMTSs. depending on your system’s architecture. They also explain how to install and configure additional SDE clusters to achieve scalability within a multi-cluster site. Finally. see the Fairshare Solution Guide.Installation guide overview Installation guide overview This guide provides detailed instructions for installing the SDE (Service Delivery Engine) in the service provider’s network and performing initial system configuration. It is highly recommended that you familiarize yourself with the information in this chapter prior to commencing installation in order to facilitate your ability to perform the necessary procedures. Note: Details of the installation process may vary somewhat according to your system’s specific architecture. For instructions. The instructions in this guide are presented in the exact order in which they should be performed.

keyboard. verify that the actual hardware included in the SDE server meets or exceeds the minimum server requirements listed above. equipped with RS232 cable and USB ports Quantity 1 per SDE node 1 Minimum server requirements The SDE can be run on industry-standard servers meeting the following requirements: • • • • • • • • Intel Xeon® 2.4GHz (EM64T) Quad Core 64-bit processor 16GB RAM Minimum 500GB HDD available capacity with a minimum supported 10K rpm HD SAS Raid 5 minimum 2 (minimum) 1GB Ethernet network ports (4 recommended) CD ROM drive Red Hat Enterprise Linux 5.Chapter 1: Deployment overview Hardware requirements Table 1: Hardware requirements displays the hardware requirements for installing the SDE software. 2010 05-00095-C04 . and mouse).4. rather than relying solely on the vendor's server type part numbers.com/list. you should verify that the hardware you are using is 100-percent compatible with Red Hat Enterprise Linux 5. Therefore.4supported hardware can be found at: https://hardware.4 64-bit implementation compatibility Hardware verification The hardware used in systems is known to change frequently. Table 1: Hardware requirements Item Industry-standard server meeting the requirements explained in the section “Minimum server requirements” on page 14 Console (including monitor.60 Rev.cgi? version=5&cf_internal_whiteboard=Server&cf_internal_whiteboard=Desktop/ Workstation&cf_internal_whiteboard=Laptop 14 Fairshare Installation & Configuration Guide: Release 5. In addition. C04 July 8. prior to commencing the installation using third-party hardware. The most recent list of RHEL 5.redhat.

For instructions. C04 05-00095-C04 July 8.60 Rev. see “Changing the location of the log files” on page 151. but the SDE can be configured upon installation so that the logs are written to a different partition. configuration and database backups Recommended Size 10 GB 480 GB 10 GB SDE logs are stored by default in /opt. Fairshare Installation & Configuration Guide: Release 5.RAID 5 Installation • • No Swap 3 partitions (see following table) Partitions Partition / /opt /var Table 2: Contents OS (RHEL 5.4) SDE and MySQL database System logs.Hardware requirements Operating system • Red Hat Enterprise Linux 5. with 64-bit implementation Recommended partitioning model The following partitioning model is recommended: RAID • • Recommended . 2010 15 .4.RAID 10 Minimum .

Chapter 1: Deployment overview Network requirements for SDE installation Prior to installing RHEL on the servers.60 Rev.” The SDE commonly is deployed in clusters of two SDE nodes to provide for failover.g. When the SDE is deployed in a multi-cluster configuration—e. C04 July 8. dummy VIPs aren’t required. each SDE machine must be assigned a primary. have a place to “land. 2010 05-00095-C04 . check that the following network requirements are available and at hand for each SDE machine: • • • • • 1 physical IP address Subnet mask Default gateway 1 primary name server IP If the physical IPs and virtual IPs used for each SDE cluster are not all in the same subnet. These dummy VIPs ensure that the service VIPs. or “dummy” VIP. of SDE machines 2 (1 cluster) 4 (2 clusters) No. Table 3: SDE cluster IP requirements for multiple subnets No. the system comprises two or more clusters—dummy VIPs are required only to address the use of different subnets within a cluster. When subnets differ from cluster to cluster (each cluster uses physical IPs and service VIPs within the same subnet). of physical IPs 2 4 2 4 No.. The following table displays physical IP and dummy VIP requirements on the SDE machine for the following deployment examples when a cluster’s physical IPs and service VIPs are in different subnets. which “float” between servers to address load and provide failover. each SDE machine also requires a “dummy” VIP. of dummy VIPs 16 Fairshare Installation & Configuration Guide: Release 5. Dummy VIPs When the physical IPs used by the SDE machines and the service VIPs used by the SDE system are not all in the same subnet.

Each service is assigned at least one VIP. Fairshare Installation & Configuration Guide: Release 5. VIPs are dynamic IP addresses assigned to services. The SDE communicates with the outer world (e. CMTSs.. 2010 17 .60 Rev.Network requirements for SDE installation Virtual IPs for SDE services In addition to the physical IP. and possibly the dummy VIP. the SDE system requires virtual IPs (VIPs) to configure the system following installation of the SDE software. required for each SDE machine.g. C04 05-00095-C04 July 8. its virtual IPs fail over to the second SDE machine. but is linked to at least one service and. Services are high-availability network connections delivered by a group of SDE nodes to other network elements. by association. If an SDE host fails. Each SDE node is assigned a physical IP address. external IPDR collectors) using these VIP addresses. along with the services—and their corresponding network elements— attached to the VIPs. to its VIP(s).

as well as the additional number of SDE clusters required for scaling to support the total number of CMTSs provisioned within the site. the policy server forwards the gates directly to the relevant CMTS. The SDE allows a number of deployment solutions. In the first type. the SDE nodes also connect directly to the CMTSs provisioned to the network to receive interface information via SNMP. The nodes also connect directly to the CMTSs provisioned to the network to receive QAM interface information via SNMP. bandwidth is calculated using data received from the IPDR records or traffic statistics stored in the SPB. Depending on the type of data collection. C04 July 8. SNMP collection also can be disabled. the SDE sends PCMM gates to the policy server based on Fairshare decisions. but not both. 18 Fairshare Installation & Configuration Guide: Release 5. or using PacketCable™ Multimedia (PCMM). the SDE’s internal IPDRC (IPDR collector) can receive IPDR and SNMP data directly from the CMTSs or from a third-party IPDR collector can using the SDE’s inbound IPDR relay function. depending on the service provider’s requirements. When Fairshare is enforced by setting an attribute in the PTS. When data collection is via the SPB. In this case. For PCMM enforcement.Chapter 1: Deployment overview Deployment architecture Each SDE deployment consists of an SDE management cluster. Fairshare enforcement Fairshare enforcement can be implemented by setting a subscriber attribute in the Sandvine Policy Traffic Switch (PTS). Data collection Data collection can be either via the Sandvine SPB (Subscriber Policy Broker) or using an IPDR collector. When SNMP is disabled. When the SDE’s internal policy server is used. 2010 05-00095-C04 .60 Rev. The SDE also allows a hybrid enforcement solution in which both PTS and PCMM enforcement are used. In the second type. depending on the Fairshare rule’s action. the nodes in each cluster receive subscriber data directly from the SPB. The SDE supports two types of IPDR data collection. the CMTS interfaces are configured manually in the system. A third-party policy server also can be used for PCMM enforcement. the management cluster (first cluster configured to the system) sends gates for Fairshare actions to the external policy server. which then forwards them to the designated CMTSs. each SDE is associated with one or more SPBs and the SDE sets a subscriber attribute in the PTS through all SPBs associated with that SDE.

A third diagram shows IPDR data collection and PCMM enforcement using third-party network elements. all of them configured for active-standby mode. while the second shows IPDR collection and PCMM enforcement using the SDE’s internal IPDR collector and policy server. The services shown in the diagrams are explained in the SDE cluster information that follows. 2010 19 . C04 05-00095-C04 July 8.60 Rev.Deployment architecture Sample deployment configurations The following diagrams of the SDE within the service provider’s network portray different types of data collection and enforcement. 1 2 · Management Service · Edge Service SNMP Enf orc em ent Collection CMTSs Management Cluster 1 3 4 Cluster 2 · Edge Service nt me rce nfo E n tio llec Co SNMP CMTSs MP SN CMTSs 5 6 Cluster 3 · Edge Service Enforce ment Collection 2 SPB collection and PTS enforcement via the SPB Fairshare Installation & Configuration Guide: Release 5. The first diagram illustrates SPB collection and PTS enforcement via the SPB.

60 Rev. C04 July 8.Chapter 1: Deployment overview 1 2 Management Cluster · · · · Management Service Border Service WSAM Service Edge Service IP DR SN M P PCMM CMTSs 3 4 Cluster 2 · Edge Service IPDR SNMP PCMM CMTSs 5 6 Cluster 3 · Edge Service IPDR SNMP PCMM CMTSs Internal IPDR collection and PCMM enforcement 20 Fairshare Installation & Configuration Guide: Release 5. 2010 05-00095-C04 .

the CMTSs provisioned to the failed machine—and their subscribers—are transferred automatically to the functioning machine.60 Rev. This cluster is in charge of the following: • The system’s management functionality. in the case of a two-node deployment. There is only one management service and only one Fairshare Installation & Configuration Guide: Release 5. deployed in active-standby or active-active mode. Alternatively. When the SDE is deployed in active-standby mode. which is used to configure and monitor the SDE. or nodes. In both scenarios. you can configure the CMTS load to be balanced evenly between the two SDE machines (active-active mode). C04 05-00095-C04 July 8. The management service. A Fairshare engine and MySQL database sit on each node. connects to the management service using a virtual IP.Deployment architecture IPDR Collector 1 2 · · · · IPDR records IPD R SNMP CMTSs Management Cluster Management Service Border Service WSAM Service Edge Service ord er s erv er) Policy Server PC M PC MM (v ia b M IPDR Collector 3 IPDR records IPD R SNMP CMTSs 4 Cluster 2 · Edge Service PCMM (via IPDR Collector Policy Server 5 IPDR records IPD R SNMP CMTSs 6 Cluster 3 · Edge Service b or d er ser ver) Policy Server External IPDR data collection and PCMM enforcement SDE clusters An SDE cluster consists of two SDE machines. The Element Management System (EMS). is configured to the first SDE node in the system. a highavailability service that provides connections to SDE’s management system. in the event of failover. the only cluster in the site. 2010 PC M PC MM (via M PC M border server) M 21 . and the management service spreads changes to all SDE nodes. the CMTSs are all connected to the first SDE machine. Management cluster The management cluster is the first cluster configured to the site or.

All clusters Edge services support connections to CMTSs. respectively) to the 22 Fairshare Installation & Configuration Guide: Release 5. No VIP is configured for the WSAM service. The second border service connects to the external policy server using the policy server’s IP address. one edge service and a minimum of two VIPs are configured for each cluster. The border service is configured to the first SDE node. is created for the cluster. as well as any SPBs defined in the system. one edge service and one VIP is configured for each cluster. When the SDE uses an external policy server. The first border service’s VIP supports the internal connections to and from the WSAM. 2010 05-00095-C04 . the SPB—attached to the VIP. no border service is required. Although each SDE node is assigned a physical IP address. logically through one or more edge VIPs. two border services are configured to the system. One border service is configured to the system. The data collector relays bandwidth usage information (subscriber statistics or IPDR data. both nodes are linked to the cluster’s edge service and.the service is attached to both nodes. no WSAM service is required. If Fairshare will be applied by setting subscriber attributes in the PTS. The WSAM receives service requests through the first VIP and sends the gates to the external policy server through the second VIP. also are linked to the edge VIP. • The connections to the WSAM (Web Services Application Manager) and the policy server when Fairshare is applied using PCMM. by association. along with the CMTSs—and. • The connection between the WSAM and the Fairshare engine when Fairshare is applied using PCMM. If Fairshare will be applied by setting subscriber attributes in the PTS. as well as to the SPB or an external IPDR collector. but for failover purposes is attached to both nodes in the cluster. but the management service may be attached to a few or all nodes in the site. The SDE node that “owns” the VIP communicates with the CMTSs attached to this VIP address. If the active SDE node fails. All SDE nodes in the site connect to the WSAM using the VIP assigned to the border service.Chapter 1: Deployment overview management VIP per site. Each CMTS. a high-availability service that provides the connection between the Fairshare engine on each node and the WSAM. the edge service and edge VIP are transferred to the other node in the cluster. to one of its VIPs. For failover purposes. C04 July 8.60 Rev. if relevant. The SDE uses edge services to provide for failover and high availability within every SDE cluster: • • When the SDE is deployed in active-standby mode. Database relay and replication A MySQL database sits on each node in the cluster. One WSAM service. When each cluster is configured for active-active mode. This border service is a high-availability service that supports the internal connections to and from the WSAM.

When an edge service is attached to both nodes in the cluster.60 Rev. The Fairshare engine on each SDE node polls the database. 2010 23 . The SDE stores the information in the MySQL database on the node. in order to make Fairshare decisions. C04 05-00095-C04 July 8. also using the edge VIP.Deployment architecture SDE nodes according to the node to which each SPB or CMTS is attached according to the edge VIP configured to the node. the databases on the two nodes are configured automatically as master-slave/slave-master for full replication in the event of failover. Fairshare Installation & Configuration Guide: Release 5.

below.Chapter 1: Deployment overview Installation prerequisites The procedures described in this guide assume that Red Hat Enterprise Linux 5. each SDE machine has been assigned a primary.60 Rev. you must verify that the following installation prerequisites have been met: • • • Each SDE machine has been assigned a physical IP address on the eth0 interface. or use commands or tools provided by Red Hat Enterprise Linux. The hostname has been configured properly in the following locations: • • • • hostname /etc/hosts /etc/sysconfig/network If a cluster’s IPs and VIPs are not all in the same subnet. The machine’s primary. 2010 05-00095-C04 . Perform the recommended pre-installation checks. virtual IP ensures that the VIPs assigned to services have a place to “land.4 has been installed as the operating system on each machine. Recommended pre-installation checks It is highly recommended that the following checks be performed on every server prior to SDE software installation: 24 Fairshare Installation & Configuration Guide: Release 5. as necessary. The /etc/issue folder contains Red Hat Enterprise Linux Server release 5. Each SDE node's time is synchronized with the NTP server and is modified to the correct time and time zone. virtual IP address. The time and time zone on all SDE machines must be coordinated for the SDE to work properly. • • • • Warning: Failure to comply with the above pre-installation requirements may result in system failure.localdomain. Do NOT use the default hostname. Each SDE machine has been assigned a hostname.4. Pre-installation requirements Prior to SDE software installation.” Each SDE has access to a DNS server. to perform the above steps. The time and time zone of all SPBs and PTSs deployed in the Fairshare system is synchronized with the NTP server and coordinated with the time and time zone of all SDEs. according to any special instructions regarding packages provided to the operator. C04 July 8. localhost.

run the domainname command. 5.Installation prerequisites 1. see “Installation verifications” on page 41. If the command returns (none). The output will be similar to the following: Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: d Wake-on: d Current message level: 0x00000007 (7) Link detected: yes If a response similar to the following appears.1 localhost. enable portmap.0.. C04 05-00095-C04 July 8.localdomain localhost ::1 localhost6.localdomain6 localhost6 <SDE-IP> <SDE-hostname(as it appear in the 'hostname' command output)> 3. Check that /etc/sysconfig/network contains information similar to the following: NETWORKING=yes NETWORKING_IPV6=no HOSTNAME=<SDE-hostname> Where <SDE-hostname> is as it appears in the hostname command output 4. If portmap isn’t running. 2010 25 . If the hostname doesn’t contain a domain name. you should reconfigure the interface as default: Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Fairshare Installation & Configuration Guide: Release 5. 2. do not add a domain name to the hostname.60 Rev. Verify in the /sbin/ethtool output for eth0 (/sbin/ethtool eth0) that the eth0 interface was configured properly..0. Check that service portmap is running by using the following command: service portmap status The following response (with the appropriate PID) should appear: portmap (pid xxxx) is running. Check that /etc/hosts contains information similar to the following: 127.

Check the RPC connectivity using the following command: rpcinfo -p A response similar to the following should appear: program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 791 status 100024 1 tcp 794 status VIP requirements As explained in the previous section. the VIP is available. including management and the connection between each SDE machine and its assigned CMTSs. The following is a list by section of the packages that should be selected for the RHEL 5. Check the RHEL is not set to secure mode by running the following command: cat /etc/selinux/config The following line should appear: SELINUX=disabled If the response shows that secure mode is enabled.60 Rev. 1 edge VIP is required for each cluster configured for active-standby mode. Note: It is recommended that. If the ping receives no response. 7. the SDE uses VIPs to provide high availability connections to the various system functions. C04 July 8. Therefore.4 64-bit operating system should be installed as server mode on the SDE server. 2010 05-00095-C04 .Chapter 1: Deployment overview Cannot get message level: No such device Cannot get link status: No such device No data available 6.4 installation: 26 Fairshare Installation & Configuration Guide: Release 5. 2 edge VIPs are required for each cluster: one for each node.4 installation packages The Red Hat Linux 5. change the line to ‘SELINUX=disabled’ and then reboot the machine. you should have the following VIPs at hand: • • • 1 VIP for the SDE management service 1 VIP for the border service that connects to the WSAM (PCMM only) 1 or more VIPs for each edge service. Prior to SDE installation and configuration. RHEL 5. If the clusters are configured instead for active-active mode. you ping the assigned VIPs to verify that they are not already in use. Each cluster is assigned 1 edge service. prior to beginning the installation process.

Applications: Only editors should be installed if vi is not sufficient. 2010 27 .) Development: no packages Servers: no packages Base System: • • • Administration Tools: default sub-options Base: default sub-options Optional: X Window System (if EMS Linux will be used) • Languages: Install languages depending on the customer’s location and preferences.Installation prerequisites • • • • • Desktop Environments: No packages should be installed.60 Rev. Fairshare Installation & Configuration Guide: Release 5. C04 05-00095-C04 July 8. (Editors will automatically install Vim and Emacs.

Chapter 1: Deployment overview Requesting a support account In order to download SDE software and updates. When your request has been processed. C04 July 8. Click Submit. Navigate to https://support. you will be emailed a confirmation indicating that your support account is active. 2. To request an account: 1. 2010 05-00095-C04 .sandvine. Support registration dialog box 3. 4. Click Register for Support Account. you need to create a Sandvine customer support account. 28 Fairshare Installation & Configuration Guide: Release 5.60 Rev. A registration dialog box appears.com/. Fill in all mandatory fields.

The following topics are included in this chapter: • “Pre-installation check list” on page 31 — provides a mandatory checklist of requirements that must be met before you can begin the installation process “Management cluster overview” on page 32 — lists the step-by-step procedures for installing and configuring the management cluster “Creating RHEL accessibility to yum” on page 33 — explains how to create accessibility to the RHEL installation folder 2 • • . or the only cluster in a deployment with two SDE machines.Installing the management cluster This chapter provides detailed instructions for installing and configuring the network architecture of both SDE machines in the management cluster. This is the first cluster installed in the site.

Chapter 2: Installing the management cluster • • “Local yum installation” on page 35 — explains how to install the SDE using a local yum installation “Configuring yum to install the SDE from an FTP site or HTTP server” on page 37 — explains how to configure yum on the SDE machine so that the SDE software can be installed from an FTP site or HTTP server “Installing the SDE software from the yum repository” on page 39 — gives instructions for installing the SDE software on the SDE machine from the SDE yum repository “Installation verifications” on page 41 — lists the procedures for verifying the SDE installation “Installation troubleshooting” on page 44 — provides procedures for troubleshooting the SDE installation “Logging into the EMS” on page 46 — explains how to log into the EMS Web interface in order to configure the SDE system “Configuring the management machine” on page 50 — explains how to configure the network architecture on the management SDE machine “Changing the border VIP in the fsam_conf.properties file” on page 57 — gives instructions for an additional configuration of the border VIP when Fairshare is implemented using PCMM “Configuring the outbound IPDR relay” on page 58 — gives instructions for configuring the SDE to relay IPDR data to an external data collector “Second SDE machine” on page 60 — provides instructions for installing the SDE software on the second machine “Installation checks and troubleshooting” on page 63 — provides a list of verification procedures that should be performed after the SDE is installed and configured on both machines • • • • • • • • • 30 Fairshare Installation & Configuration Guide: Release 5.60 Rev. 2010 05-00095-C04 . C04 July 8.

60 Rev.Pre-installation check list Pre-installation check list Before reading this chapter and starting to install the SDE software. The time and time zone of all SPBs and PTSs deployed in the Fairshare system are synchronized with the NTP server and coordinated with the time and time zone of all SDEs. Mark if ‘yes’ 1 2 3 5 6 7 Fairshare Installation & Configuration Guide: Release 5. Every SDE machine's time and time zone are synchronized with the NTP server and are modified to the correct time and time zone. virtual IP address. Each SDE machine has been assigned a hostname (do NOT use the default) that is configured properly in: • hostname • /etc/hosts • /etc/sysconfig/network 4 Each SDE machine has been assigned a second IP address that will be used as a primary.x 64-bit implementation is installed on every SDE machine Each SDE machine has been assigned an IP address on the eth0 interface. C04 05-00095-C04 July 8. Table 4: Pre-installation check list Prerequisite Red Hat Enterprise Linux Server release 5. Note: This is required ONLY if the IPs assigned to the two SDE servers in the cluster and the virtual IPs that will be assigned through the SDE EMS later in the SDE configuration processs are not all in the same subnet. please use the following checklist to make sure that your network and the target SDE machines are ready to begin the process. 2010 31 . Each SDE has access to a DNS server that is configured properly.

see “Configuring yum to install the SDE from an FTP site or HTTP server” on page 37. the WSAM and border services are configured to the management cluster. To create access to the Red Hat Enterprise Linux 5. The management service is configured to this cluster. To perform a local yum install. Step 2: Once you have created access to the RHEL 5. 32 Fairshare Installation & Configuration Guide: Release 5. see “Local yum installation” on page 35. C04 July 8. you must create access on the Linux machine to the official Red Hat Enterprise Linux 5. An edge service also is configured to this cluster. For sites containing only two SDE servers. enabling the SDE to spread configuration changes to all SDE nodes in the site.60 Rev. 2010 05-00095-C04 .Chapter 2: Installing the management cluster Management cluster overview The management cluster is the first cluster installed in the site. Step 1: The first step in installing and configuring the management cluster is to install the SDE software on both Linux machines designated as SDE servers. As an installation prerequisite. This access is required for first-time SDE installation.x installation folder. To install the SDE software from an HTTP or FTP repository. If the SDE will implement Fairshare using PCMM. Or. as well as SDE upgrades.x installation folder. You can copy the SDE install folders to your server and install the SDE software locally. it is the only cluster. you can install the SDE software from an HTTP or FTP yum repository.x installation folder. the SDE uses the yum installer to install the SDE software on the machine. see “Creating RHEL accessibility to yum” on page 33.

repos. For a local copy of the RHEL official installation: [rhel_x64] name= RHEL RPM Cache baseurl=file:///opt/rhel5. Installation folder on an FTP site 3.x/. If you are creating local access to the RHEL installation folder. 2.{x}/Server enabled=1 protect=0 gpgcheck=0 where {x} is the exact version of RHEL 5. make an integral copy of the /Server directory from the RHEL 5. To ensure proper SDE functionality. Three types of access are possible: 1. 2010 33 . Do not upgrade to a new version of the operating system until Sandvine has qualified the release and sent notification to the field.x installation DVD (using rsync r or cp -r) and store it on the SDE machine at /opt/RHEL5. C04 05-00095-C04 July 8. you need to create this accessibility. create a /etc/yum. You also must update accessibility to the correct RHEL installation folder each time you update the RHEL operating system.repo file that contains the yum repository definition for the Red Hat Enterprise Linux Server official installation RPMs.60 Rev. keep in mind the server address (for installations using FTP and HTTP ) and full path to the server folder of the RHEL installation. you must create accessibility to a qualified release only. the file will contain the following content: Note: For all installations. Prior to installing the SDE for the first time. Installation folder on an HTTP server To create the accessibility: 1. Warning: Sandvine qualifies each SDE release against specific versions of Red Hat Enterprise Linux.Creating RHEL accessibility to yum Creating RHEL accessibility to yum All SDE installations and upgrades must be able to access a RHEL 5.d/rhel. For all access types. Local copy of the official RHEL installation folder 2. Depending on the way you want to access the RHEL official installation.x installation folder containing the Red Hat installation RPMs.x For the RHEL installation stored on an FTP site: [rhel_x64] name= RHEL RPM Cache Fairshare Installation & Configuration Guide: Release 5. The folder needs to be accessible.

34 Fairshare Installation & Configuration Guide: Release 5. proceed to “Local yum installation” on page 35 to install the software locally or “Configuring yum to install the SDE from an FTP site or HTTP server” on page 37 to install the SDE software from an HTTP or FTP site.x installation folder. C04 July 8.60 Rev.Chapter 2: Installing the management cluster baseurl=ftp://{FTP site IP address}/${full path rhel installation disc}/Server enabled=1 protect=0 gpgcheck=0 For the RHEL installation stored on an HTTP server: [rhel_x64] name= RHEL RPM Cache baseurl=http://{MY http SERVER Ip address}/${full path rhel installation disc}/Server enabled=1 protect=0 gpgcheck=0 Next step: Now that you have created accessibility to the RHEL 5. 2010 05-00095-C04 .

x86_64 package. Confirm that your system is running with RHEL-64 bit by entering the following command: uname -p The following should appear: x86_64 6.60 A response similar to the following. should appear: baseurl=file:///opt/install/sde-5. refer to “Creating RHEL accessibility to yum” on page 33.60 Rev.Sandvine baseurl=file://<install path> enabled=1 protect=0 gpgcheck=0 3. similar to the following example: Available Packages redhat-release. 2010 35 . Run the following command to cleanup the yum cache: yum clean all 7. Check that you have accessibility to the Red Hat installation respository.3 rhel_x64 If the package is not displayed.x86_64 Fairshare Installation & Configuration Guide: Release 5. 2. enter the following command: export sde_dont_install_firewall_table=yes 5. Copy the following folder from the Sandvine FTP site to: /opt/install/: • SDE-5. On the SDE machine. To install the SDE software locally using yum: 1.4.repo under /etc/yum.60 4. enter the following command: yum list --showduplicates redhat-release |grep -vi installed The output should show the available redhat-release.Sandvine SDE for \$releasever . For example: /opt/install/sde-5. with the appropriate file path.60 [sde] name= SDE . If you want to preserve your current firewall settings following the install. Create a file called svsde.repo.d/ Where <install path> is the full path of the SDE RPM directory. C04 05-00095-C04 July 8.Local yum installation Local yum installation The following instructions enable operators to install the SDE software locally.x86_64 5Server-5. Enter the following installation command: yum install sde-with_fs_edge.0.

60 Rev.Chapter 2: Installing the management cluster After initial installation of packages. a script appears that includes the following notification. 2010 05-00095-C04 . Type ‘y’ to continue the SDE software installation. When the installation process is complete. signifying that the installation is complete: Complete! 36 Fairshare Installation & Configuration Guide: Release 5. a response similar to the following should appear: Transaction Summary =============================================== Install 40 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 254 M Is this ok [y/N]: 8. C04 July 8.

similar to the following example: Available Packages redhat-release. Check that you have accessibility to the Red Hat installation respository. 2010 37 .com/ SDE/SDE-5. The yum installer must be included in the Red Hat Enterprise Linux installation. At the password prompt.xxx.xxx> where <xxx. enter ‘yes’. b. 3.xxx. C04 05-00095-C04 July 8.repos.0. 4. refer to “Creating RHEL accessibility to yum” on page 33.60 enabled=1 protect=0 gpgcheck=0 where <user_name> is the customer support user name and <password> is the customer support password. proceed directly to “Installing the SDE software from the yum repository” on page 39.60/sde-5. Note: This procedure is for first-time SDE installation only.3 rhel-disc If the package is not displayed.d/ called svsde. a. At the prompt. On the SDE machine.xxx> is the IP address of the SDE machine. Create a file in /etc/yum. You will be asked whether you want to continue connecting to the machine. Connect to the SDE machine using SSH: ssh root@<xxx. If you are installing the SDE software from an HTTP or FTP site.4.x86_64 package. enter the password you assigned during RHEL installation. If you have already performed it.repo with the following contents: [sde] name= Sandvine Service Delivery Engine baseurl=ftp://<user_name>:<password>:ftp.x86_64 5Server-5. Run the following command: Fairshare Installation & Configuration Guide: Release 5.Configuring yum to install the SDE from an FTP site or HTTP server Configuring yum to install the SDE from an FTP site or HTTP server The SDE uses the yum installer to automatically install or update the SDE software from the Sandvine FTP site or the service provider’s HTTP site. the first time you install the software on the machine you need to point the installer to the correct yum repository.sandvine.60 Rev.xxx. 2. To point the installer to the yum repository: 1. enter the following command: yum list --showduplicates redhat-release |grep -vi installed The output should show the available redhat-release.xxx.support.

Chapter 2: Installing the management cluster yum clean all Next step: You are now ready to install the SDE software. 2010 05-00095-C04 . See “Installing the SDE software from the yum repository” on page 39. 38 Fairshare Installation & Configuration Guide: Release 5.60 Rev. C04 July 8.

At the prompt. 4. Type ‘y’ to continue. To proceed with the install. b. a response similar to the following should appear: Transaction Summary =============================================== Install 40 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 254 M Is this ok [y/N]: 5. signifying that the installation is complete: End Post-Install script Fairshare Installation & Configuration Guide: Release 5. You will be asked whether you want to continue connecting to the machine.xxx. a script appears that includes the following notification.xxx. enter the password you assigned during RHEL installation. 2010 39 . execute the following lines: yum install sde-with_fs_edge.60 Rev.xxx. To install the SDE software on the machine: 1. Do not proceed with the installation until the system is running with RHEL-64bits. a.xxx. connect to the SDE machine using SSH: ssh root@<xxx.xxx> where <xxx. Confirm that your system is running with RHEL-64 bit by entering the following command: uname -p The following should appear: x86_64 Warning: If the output is ‘i686’ or ‘i386’. At the password prompt. your system is running with RHEL-32bits and does not meet system specifications. If you want to preserve your current firewall settings following the install.xxx> is the IP address of the SDE machine. If you are not already connected. C04 05-00095-C04 July 8.x86_64 After initial installation of packages. enter ‘yes’. enter the following command: export sde_dont_install_firewall_table=yes 3.Installing the SDE software from the yum repository Installing the SDE software from the yum repository Caution: Make sure that the RHEL version installed on the machine is supportd by the SDE software you want to install. When the installation process is complete. 2.

Chapter 2: Installing the management cluster Next step: Following software installation. 2010 05-00095-C04 . 40 Fairshare Installation & Configuration Guide: Release 5. See “Installation verifications”.60 Rev. verify that the software has been installed correctly. C04 July 8.

xxxx 3dm-5..Installation verifications Installation verifications Following installation. with the appropriate version numbers: SDE with Fairshare Edge .60-xxxx FSAS-5.. wsam_wdog (pid xxxxx) is running.60-xxxx IPDRC-5. 2010 41 .60-xxxx svIp2Qam-5.. Fairshare Installation & Configuration Guide: Release 5.60-xxxx jdk_config-5. fs_am_wdog (pid xxxxx) is running. At root..60-xxxx svDBMaintenance-5.60-xxxx IPDR_DB-5...60-xxxx PS-5. enter the following to verify that the proper system modules were installed: sde_info The following response should appear. C04 05-00095-C04 July 8....60-xxxx EMS-Linux-5.60. svPolicyServer (pid xxxxx) is running.40-xxxx sde_ems-5..60-xxxx SDE_Upgrade-5. verify that the SDE is running successfully by checking the status of the SDE and spread services with the following command: service sde status The following response (with the appropriate PID) should appear: ps_watchdog (pid xxxxx) is running. perform the following steps to verify that the SDE installation was successful: 1.. ps_agent_wdog (pid xxxxx) is running.60-xxxx svupdate-1-17 WSAM-5. svAgent (pid xxxxx) is running..Version: 5. Reload the shell variable environment by running the following command: source ~/.40-xxxx SDE_CONF-5.60-xxxx NetReport-5.60-xxxx SDE_CMD-5..60 Rev.60-xxxx 3.60-xxxx SDE_MIBS-5.60-xxxx SDE_Agent-5.60-xxxx SDE_Monitoring-5.60-xxxx sde_common_libs-5.60-xxxx sde-with_fs_edge-5..bashrc 2. svWsam (pid xxxxx) is running. At root.60-xxxx sde_config-5.

4... 2010 05-00095-C04 .sh (pid xxxxx) is running. manually create it now: mkdir /opt/tmp chmod 777 /opt/tmp d.. wdogReplication.. dbm_wdog (pid xxxxx) is running.Chapter 2: Installing the management cluster svFSAS (pid xxxxx) is running...60 Rev... Note: In the event that the above response shows that the SDE Agent is stopped (svAgent stopped. If the appropriate response does not appear: a. Verify that portmap is running: service portmap status 6.. C04 July 8... db_wdog (pid xxxxx) is running. Verify that portmap is running: service portmap status The following response (with the appropriate PID) should appear: portmap (pid xxxx) is running. svIp2Qam (pid xxxxx) is running.. Verify that the /opt/tmp directory was created during the installation: ll /opt/tmp c. Start portmap: service portmap start d... ip2qam_wdog (pid xxxxx) is running. Check that MySQL is located in /opt/mysql: ll /opt/mysql b. If the /opt/tmp directory was not created. svIPDRCollector (pid xxxxx) is running.. see “Installation checks and troubleshooting” on page 63.. by executing the following: mysql SDE_DC_DB 42 Fairshare Installation & Configuration Guide: Release 5. ipdr_wdog (pid xxxxx) is running. Verify that the rules are enabled: chkconfig --list | grep portmap portmap 0:off 1:off 2:off 3:on 4:off 5:on 6:off c.. 5... Run MySQL.. enable portmap's levels: chkconfig --levels 35 portmap on b. Verify that the spread watchdogs are running by entering the following: service spread status The following response (with the appropriate PID) should appear: spread_wdog (pid xxxx) is running. svDBMaintenance (pid xxxxx) is running.)...... Check that MySQL was correctly installed: a.

Installation verifications MySQL should start with the correct my. 2010 43 . C04 05-00095-C04 July 8. e. Fairshare Installation & Configuration Guide: Release 5.cnf loaded. enter the following commands: rm -rf /var/lib/mysql/ib* rm -rf /var/lib/mysql/SDE_DC_DB service mysql restart g.60 Rev. halt installation and contact Sandvine customer support. If my.cnf was not loaded correctly into the database. enter the following commands: cd /var/lib mv mysql /opt cd /var/lib ln -s /opt/mysql f.sql Caution: If any of the above steps failed. Load the database schema using the following command: mysql -u root SDE_DC_DB < /opt/SDE/IPDRC_DB/SDE_DC_DB. If the /opt/mysql/ was not created upon SDE installation.

3.2-7. In this case.2-7.2-7.2. To clean the yum cache: • Enter the following command: yum clean all 44 Fairshare Installation & Configuration Guide: Release 5. as described in “Configuring yum to install the SDE from an FTP site or HTTP server” on page 37.3.3.el5 is needed by package 1:net-snmp-perl-5.noarch. 2010 05-00095-C04 .noarch. as explained in “Creating RHEL accessibility to yum” on page 33.el5.x86_64 from sde-retail has depsolving problems --> Missing Dependency: net-snmp = 1:5.2-7.noarch: failure: SDE_CONF-5.2-7.5.2. 2.40-0020.60 Rev. a message similar to the following appears: 1:net-snmp-perl-5.x86_64 (sde-retail) To solve the problem: 1. Verify that you have access to the RHEL installation folder.40-0021.el5.rpm from sde-udpate: [Errno 256] No more mirrors to try.3.5.2.rpm from sde: [Errno 256] No more mirrors to try. then reconfigure the yum installer. See “Installing the SDE software from the yum repository” on page 39.Chapter 2: Installing the management cluster Installation troubleshooting Missing dependencies If net-snmp RPMs are missing during yum installation. C04 July 8.40-0021.el5 is needed by package 1:net-snmp-perl-5.el5.noarch: failure: SDE_Monitoring-5.x86_64 (sde-retail) Error: Missing Dependency: net-snmp = 1:5.2. you should clean the yum cache. SDE_CONF .40-0020. Rerun the SDE install command.2. yum troubleshooting If the yum installer was not configured correctly.3. error message 256 appears when you start the yum installation: Error Downloading Packages: SDE_Monitoring .

Wait 5 seconds and then start Spread: service spread start d. Fairshare Installation & Configuration Guide: Release 5. so that you can configure the services that run on the machine. Wait 5 seconds and then restart the SDE: service sde start Next step: You are now ready to log into the EMS.0. and spread doesn’t work properly.localdomain6 localhost6 127.0.xxx. ::1 localhost6. Run hostname and add the hostname to the machine (example new name is shown in bold).xxx is the IP address of the SDE node. C04 05-00095-C04 July 8. 3. Stop the SDE processes: service sde stop b.xxx <sde hostname> Where xxx. Stop Spread: service spread stop c.localdomain localhost xxx. To change the host name: 1.localdomain) prior to SDE software installation. then save the file: hostname <sde hostname> 2.xxx. change the hostname on the machine. To resolve the problem. as explained in “Logging into the EMS” on page 46.Installation troubleshooting SDE machine hostname If the SDE machine’s hostname is not changed from the default (localhost.xxx. Restart the SDE and services: a. Edit and save the /etc/hosts file for the new hostname (changes shown in bold): /etc/hosts Do not remove the following line. the SDE agent fails to mount.1 localhost.60 Rev.xxx. Edit and save the /etc/sysconfig/network file for the new hostname (changes shown in bold): /etc/sysconfig/network NETWORKING=yes NETWORKING_IPV6=yes HOSTNAME=<sde hostname> 4. or various programs that require network functionality will fail. 2010 45 .

2. Note: Every installation of the Windows EMS comes with JRE 1.Chapter 2: Installing the management cluster Logging into the EMS Following installation of the SDE software on both machines. EMS access options The SDE includes three EMS graphic interfaces: • • The Web EMS interface enables users to access the EMS from any Windows machine using a Web browser. select the latest version of EMS. It enables you to configure the SDE system. • The SDE also includes an EMS command line interface (CLI) that enables operators to configure network elements and view the status of different system elements in an SDE node from the command line on the local SDE machine. 2010 05-00095-C04 . Log into the Sandvine Customer Support Site located at https:// support.60 Rev. C04 July 8.com with your user name and password. In the Software tab. 46 Fairshare Installation & Configuration Guide: Release 5. or from a Linux host machine using a full Linux graphic interface (e. To install the EMS on a Windows machine: 1. Windows EMS installation The Windows EMS install file can be accessed through the Sandvine Customer Support Web site. The Windows EMS can be installed and run on any Windows machine. then select the correct stream and software release.. KDE or GNOME) through an SSH connection to the SDE machine.g. select SDE > EMS from the Family of Products. The Linux EMS can be run from the SDE machine. The EMS is the graphical user interface for configuring. This JRE is used only when the EMS is running.sandvine. EMS software file path 3. managing and troubleshooting the SDE system. If you are working with the latest SDE release. The Linux EMS also can be run from a Windows machine via an X Windows interface. connect to the first machine in the cluster using the SDE EMS (Element Management System).6. Click the SDE EMS version that you want to download to your machine.

0.xx. a Linux distribution with graphic support.16. Click Launch SDE EMS. Double-click the downloaded SDE-EMS-x. In the dialog box that appears.Logging into the EMS 4. C04 05-00095-C04 July 8.xxxx. Fairshare Installation & Configuration Guide: Release 5. For example. Installing the X Window System package group For systems with access to a RHEL 5. click OK or Run to run the EMS installer.i386 EMS login sequence Note: The following information assumes the EMS is already installed on a Windows machine and/or that the X Window System package group for Red Hat Enterprise Linux has been installed on the SDE machine. to install the X Window System package group: 1. To run the Linux EMS from a Windows machine. make sure that an X Windows interface is installed. 2010 47 .16. 2.i386 libXtst. Open your Web browser and go the following URL: http://<SDE_MACHINE>:<port>/sde_ems where <SDE_MACHINE> is the IP or FQDN of the SDE machine and <port> is the port specified during Tomcat installation. To run the EMS using the Web interface from any machine: 1. The EMS Web portal appears.bit distribution yum repository. Log into the SDE machine. the URL might be: http://172. 5. On a Linux machine. At the security warning.104:8085/sde_ems/. must be installed on the machine. Click Run. 3. When running the SDE from a remote Linux machine. and a security warning appears. the port is usually 8085.104.exe file icon. 6.0.60 Rev. Run the following commands: yum groupinstall "X Window System" yum install gtk2.x 64. click Save. for an SDE machine with IP address 172. such as KDE or GNOME. The SDE EMS login dialog box appears. 2. Java Web is activated.

from the Start > All Programs menu select Sandvine > SDE EMS 5. Note: The SDE machine’s IP address or FQDN is used for first-time EMS login only. the Red Hat Enterprise Linux X Window System package group must be installed already on the machine. The EMS Manager appears.xx > SDE EMS The EMS login dialog box appears. Execute the following lines: cd /opt/SDE/SDE_EMS/ ./ems_start From a Windows machine: 1. 2. • • 48 Fairshare Installation & Configuration Guide: Release 5. In the SDE Server field. Note: To run the EMS from an SDE machine. Or. Connect to the SDE machine using an X Windows interface. Once the system’s management VIP is configured. type the IP address or FQDN of the machine on which the SDE is installed. log into the EMS using the management VIP. execute the following lines: cd /opt/SDE/SDE_EMS/ . execute the following lines: ssh -X <IP address of SDE machine> cd /opt/SDE/SDE_EMS/ . C04 July 8. 2. Click OK. 2010 05-00095-C04 ./ems_start The EMS login dialog box appears.Chapter 2: Installing the management cluster EMS login dialog box To run the Windows EMS: • On the Windows machine. To run the Linux EMS on the SDE machine or from a remote machine (Linux or Windows): • On the SDE machine. 3. To log in: 1.60 Rev./ems_start On a remote Linux machine. double-click the EMS icon on the desktop. Type sv_admin as the user name and sv_admin as the password.

“Configuring the management machine” on page 50. 2010 49 .Logging into the EMS SDE EMS manager Next step: You are now ready to proceed to the next step. C04 05-00095-C04 July 8.60 Rev. Fairshare Installation & Configuration Guide: Release 5.

To assign the management service a VIP: 1. C04 July 8. Follow the order described in the instructions for these configurations. The EMS connects to the management service using this VIP. The Virtual IP dialog box appears. Type the VIP in the Virtual IP field.60 Rev. If the SDE will implement Fairshare actions using PCMM. border. 2010 05-00095-C04 . and edge—and one predefined SDE node (the machine whose IP you just used to log into the EMS). Virtual IP dialog box 2. Configuring the services The SDE comes with three predefined services—one each for management. open Services List > Management Service. In the Configurations tree. 50 Fairshare Installation & Configuration Guide: Release 5. also configure a border service VIP and a WSAM service. Rightclick Virtual IPs. then select Add Virtual IP. Configure the VIP for the management and edge services.Chapter 2: Installing the management cluster Configuring the management machine The management machine is the first SDE server in the cluster. The management service MUST be assigned a VIP in order to enable operators to add more than one node to the SDE for high availability. Assigning the management VIP The management VIP is the first VIP assigned to the system. The different VIP parameters are explained in “VIP parameters” on page 51. and the management service spreads changes to all SDE nodes. Configure the management machine’s network architecture before adding the second machine to the system through the EMS.

4.Configuring the management machine 3. This is the pre-defined SDE node that assumes “ownership” of the VIP. The SDE communicates with other network elements (CMTSs. 2010 51 . IP of the node on the computer network that serves as an access point to another network IP of the predefined SDE node that assumes “ownership” of the VIP Parameter Virtual IP Default Value -- Netmask 255. Use the management VIP instead of the SDE machine’s physical IP address when logging into the SDE EMS from any location. the VIPs move from the failed node to an active node. subnet mask.255 Default Gateway -- Primary SDE Node -- Configuring the edge VIP To configure the edge VIP: 1. In the event of failover. C04 05-00095-C04 July 8. 2. and default gateway. An alert appears that the EMS will automatically reconnect to the SDE using the management VIP. Netmask assigned to the VIP.255. The Virtual IP dialog box appears. The system automatically assigns the first SDE node as the primary SDE node. 5. Click OK to continue. Assign at least one per service. including a Web browser. You will be unable to add any additional nodes to the SDE without the management VIP. The VIP appears under the management service in the Configurations tree. VIP parameters Table 5: VIP parameters Definition Dynamic IP address assigned to a service. then select Add Virtual IP. Click OK. AMs. ASs) using these IP addresses. 3. It remains with the VIP if it moves from node to node. Click OK. Select the correct netmask and default gateway from the drop-down lists. The SDE automatically designates the first SDE node as the VIP’s primary SDE node. This is the SDE machine that assumes ownership of the VIP. Fairshare Installation & Configuration Guide: Release 5. Caution: The management service must be assigned a VIP for the SDE to work properly. Specify the virtual IP.255.60 Rev. in the future. Right-click Virtual IPs. SPBs. open Services List > Edge Service. In the Configurations tree.

assign the border service a VIP. In the Configurations tree. you are now ready to configure the database decimation. you are required to configure an additional border service. Specify the virtual IP. you should configure the border service VIP at this point. If the SDE will implement Fairshare using PCMM. Otherwise. and default gateway. 2. The Virtual IP dialog box appears. Configuring the border VIP If the SDE will implement Fairshare actions using PCMM. To assign the border VIP: 1. C04 July 8. as explained in Configuring database decimation. subnet mask. then select Add Service. Configuring the external PS connection When the SDE will connect to third-party policy servers for PCMM Fairshare implementation. 52 Fairshare Installation & Configuration Guide: Release 5. In the Configurations tree. 2010 05-00095-C04 . This is the SDE machine that assumes ownership of the VIP. open Services List > Border Service. Right-click Virtual IPs.Chapter 2: Installing the management cluster Next step: If the SDE will apply Fairshare actions by setting attributes in the PTS. To configure the border VIP for the external policy server: 1. which connects to the external policy server using the policy server’s physical IP. right-click Services List.60 Rev. 3. If the SDE will apply Fairshare actions using an external policy server. The New Service dialog box appears. then select Add Virtual IP. Click OK. The system automatically assigns the first SDE node as the primary SDE node. you are now ready to configure a WSAM service. configure the external PS connection at this point.

g. 7. The IP appears under the border service in the Configurations tree. 3.Configuring the management machine New Service dialog box 2. then select Add external PS IP. then select Add Service.. Fairshare Installation & Configuration Guide: Release 5. 4. You are now ready to configure a WSAM service. Change the Use for external PS attribute to ‘Yes’. ‘External PS’). ‘Border_2’). open the node for the border service you just created. 5. C04 05-00095-C04 July 8. Right-click External PS IPs. External PS IP dialog box 8. Configuring the WSAM service To configure the WSAM service: 1. Assign the service a name (e. and then click OK. Right-click Services List. The External PS IP dialog box appears. Optionally type a description of the service (e.60 Rev.g. 2010 53 . Type the IP of the policy server. The service appears in the Services list. Click OK. In the Configurations tree. 6. The New Service dialog box appears..

The service appears in the Services list. The PS Entry Point is the VIP of the border service. Defines the WSAM (Web Services Application Manager) Parameter Type Border Default Value N/A Border Edge Edge Management Management WSAM WSAM 54 Fairshare Installation & Configuration Guide: Release 5. Service parameters Table 6: Services parameters/nodes Definition Defines the type of service being added Supports connections from the Fairshare Engine to the WSAM and/or from the WSAM to the policy server to achieve high availability Supports connections to CMTSs and SPBs to achieve high availability Provides connections to management systems. Click the Type field and select WSAM from the list. The WSAM uses this VIP to receive Fairshare rule actions from the different SDE nodes and to communicate with the policy server. 3. see “Service parameters” on page 54. C04 July 8..60 Rev. ‘WSAM Service’).Chapter 2: Installing the management cluster New Service dialog box 2. Optionally type a description of the service.g. Specify the PS Entry Point and the AM ID. For a complete list of WSAM service parameters. Assign the service a name (e. 4. Click OK. 2010 05-00095-C04 . 6. 5. Define only one management service per system.

60 Rev. Select the check box for the WSAM service. C04 05-00095-C04 July 8. expand the SDE node and select Attached Services. you need to attach this service to the SDE node: To attach a new service: 1.Configuring the management machine Parameter Name Description OSS (edge service only) PS Entry Point (WSAM service only) AM ID (WSAM service only) Definition Name of service as it appears in the EMS Optional description of the service OSS to which the edge service connects VIP of the border service used to communicate with the policy server Operator-assigned ID of this AM. 2010 55 . In the SDE Node List. Expanded SDE node list 2. All services should be marked as attached in the EMS right pane. Used by the policy server to send gates HTTP port on which the WSAM receives requests for service from the application server and sends responses in turn. Default Value ServiceType_X -none -- -- Port (WSAM service only) 8080 Attaching new services to the SDE node If you created a WSAM service so that the SDE can implement Fairshare actions using PCMM. A list of services appears in the EMS right pane. Fairshare Installation & Configuration Guide: Release 5.

Chapter 2: Installing the management cluster

Attached SDE services

Next step: For all deployments that will implement Fairshare using PCMM, continue on to “Changing the border VIP in the fsam_conf.properties file” on page 57. For deployments that apply Fairshare solely through the PTS, proceed to the installation and configuration of the second machine in the cluster, as described in “Second SDE machine” on page 60. If the SDE will relay the DOCSIS 2.0 IPDR data to an external data collector, configure the outbound relay after changing the border VIP or before installing the second machine, as explained in “Configuring the outbound IPDR relay” on page 58.

56

Fairshare Installation & Configuration Guide: Release 5.60 Rev. C04
July 8, 2010 05-00095-C04

Changing the border VIP in the fsam_conf.properties file

Changing the border VIP in the fsam_conf.properties file
For all deployments that will implement Fairshare using PCMM, edit the fsam_conf.properties file in order to define the border VIP that the Fairshare engine will use to send Fairshare requests to the WSAM. To define the border VIP: 1. Stop the SDE service if you haven’t already done so: service sde stop 2. Open the fsam_conf.properties file for editing: vi /opt/SDE/FSAS/config/fsam_conf.properties 3. The file currently is configured to send Fairshare requests to the WSAM on the local machine. In the WSAM Parameters section, change the parameter com.cmx.odsp.fsam.wsam_url=localhost:8080 to com.cmx.odsp.fsam.wsam_url=<border_VIP>:8080 where border_VIP is the VIP defined for the border service and the PS entry point of the WSAM. If the WSAM sends the gates for the Fairshare actions to an external policy server, border_VIP is the second VIP of the border service configured to the system. 4. Save the file. 5. Restart the SDE service: service sde start Next step: If the SDE will relay the DOCSIS 2.0 IPDR data to an external data collector, configure the outbound relay after changing the border VIP or before installing the second machine, as explained in “Configuring the outbound IPDR relay” on page 58. Otherwise, proceed to the installation and configuration of the second machine in the cluster, as described in “Second SDE machine” on page 60.

Fairshare Installation & Configuration Guide: Release 5.60 Rev. C04
05-00095-C04 July 8, 2010

57

Chapter 2: Installing the management cluster

Configuring the outbound IPDR relay
If the SDE will also relay IPDR data to an external data collector, configure the outbound IPDR relay at this point. The SDE relays the IPDR data from all CMTS vendor types in streaming mode. To configure the outbound relay: 1. On the SDE machine, open the /etc/sysconfig/sde file for editing: vi /etc/sysconfig/sde 2. At the end of the file, add the following line: RUN_IPDR_REDIRECT=yes The file should appear as follows: RUN_WIMAX=noRUN_IPDR=yes RUN_FSAM=yes RUN_SPBC=yes RUN_MYSQL=yes RUN_WEBEMS=yes RUN_MYSQL=yes RUN_MYSQL_CLUSTER=yes RUN_IPDR_REDIRECT=yes 3. Save the file. 4. Execute the following commands: service sde init service sde restart 5. Check the status of the IPDR redirect process: service sde status The response should include the following, with the appropriate PID, indicating that svIPDR redirect is running: svIPDRRedirect (pid 1234) is running... 6. In the SDE EMS, in the SDE Parameters > IPDR Collection node: a. Set Enable File Logging to ‘Yes’. b. Configure the IP address of the external collector in the Relay Collector IP field. c. Configure the port of the external collector in the Relay Collector Port field. The relay collector port is usually 6210. Note: Make sure you also set Enable File Logging to ‘Yes’ on every CMTS configured to the SDE. For instructions, see “Import CMTSs/CMTS maps overview” on page 96 or “Configuring CMTSs through the EMS” on page 156.

58

Fairshare Installation & Configuration Guide: Release 5.60 Rev. C04
July 8, 2010 05-00095-C04

as described in “Second SDE machine” on page 60.Configuring the outbound IPDR relay Next step: Proceed to the installation and configuration of the second machine in the cluster. Fairshare Installation & Configuration Guide: Release 5. C04 05-00095-C04 July 8. 2010 59 .60 Rev.

In the event the second SDE node fails. Note: Upon recovery of a failed SDE node. 60 Fairshare Installation & Configuration Guide: Release 5. and the failover node hands off the border and edge VIPs to their original owner. however. along with all the CMTSs attached to the first node’s edge VIP. For load balancing purposes. Type the SDE’s physical IP address or FQDN. C04 July 8. the edge VIP designated for the node fails over to the first SDE node.60 Rev. configure the cluster’s high availability by configuring the second node to the system and attaching all services to the second node. 2010 05-00095-C04 . In the Configurations tree. its VIPS—and services—are transferred to the second SDE node. Adding SDE nodes To add an SDE node to the system: 1. This enables you to configure half the CMTSs in the cluster to the first SDE node and half to the second SDE node. the node tries to resume its original configuration.Chapter 2: Installing the management cluster Second SDE machine Following configuration of the first SDE node. remains on the failover machine. you can assign a second VIP to the edge service and designate the second SDE machine as the VIP’s primary SDE node. right-click SDE Node List and select Add SDE Node. The management service. and the net mask assigned to the machine upon OS installation. New SDE Node dialog box 2. The New SDE Node dialog box appears. In the event that the first node fails.

The name enables you to differentiate the different types of nodes in the EMS GUI.255. 2010 61 . 2. see “SDE node parameters” on page 61. etc. Fairshare Installation & Configuration Guide: Release 5. the node appears in the SDE Node List.60 Rev. Select the check box for every service shown in the Attributes pane. half the CMTSs connect to the SDE using the first VIP and half the CMTSs connect to the second VIP. This configures the cluster for activeactive mode. Select Attached Services. In the SDE Node List.0 Description -- Attaching services to the new node To attach the services to the second SDE node: 1. The Progress Information bar appears to inform you of the configuration's progress. Click OK. Configuring a second edge VIP Depending on your system’s configuration. 4. When this configuration is used. 3. SDE node parameters Table 7: SDE node parameters Description Defines the name of the SDE node as it appears in the SDE Node List Physical IP address or FQDN of the machine The mask assigned to the machine upon installation Optional description of the machine (types of services it hosts. For a description of the different node parameters. The configuration may take up to 2 minutes. A list of services appears in the EMS right pane. expand the second SDE node.Second SDE machine 3.) Parameter Label Default Value SDE_1 IP or FQDN Mask -255.255. you can optionally configure a second edge VIP to the system for CMTS load balancing purposes and designate the second SDE machine as the VIP’s primary SDE node. C04 05-00095-C04 July 8. Optionally give the node a name and description. When the configuration is complete.

C04 July 8. Click OK. on the SDE machine edit the com.properties file For all deployments that will implement Fairshare using PCMM. 3. 2. then click OK. Specify the virtual IP. and default gateway. as described in “Configuring the outbound IPDR relay” on page 58. 2010 05-00095-C04 .properties file to define the border VIP that the Fairshare engine will use to send Fairshare requests to the WSAM. open Services List > Edge Service. In the Configurations tree. see “Changing the border VIP in the fsam_conf. To change the primary node: a. Right-click Virtual IPs. Click Change. then select Add Virtual IP. 4.60 Rev.properties file” on page 57. Changing the border VIP in the fsam_conf. b. or else first configure the outbound IPDR relay. Next step: Proceed to “Installation checks and troubleshooting” on page 63.cmx.fsam.Chapter 2: Installing the management cluster Adding an edge VIP To add an edge VIP: 1. Change the primary SDE node so that the new SDE node assumes ownership of the VIP. subnet mask. Next step: Proceed to “Installation checks and troubleshooting” on page 63.odsp. In the Primary SDE Node dialog box. For instructions. configure the outbound IPDR relay at this point. select the second node from the list.wsam_url=<border_VIP>:8080 parameter in the fsam_conf. 62 Fairshare Installation & Configuration Guide: Release 5. The system automatically assigns the first SDE node configured to the system as the primary SDE node. Configuring the outbound relay If the SDE will relay IPDR data to an external data collector. The Virtual IP dialog box appears.

Note: SDE System also displays simulators.Installation checks and troubleshooting Installation checks and troubleshooting Following configuration of the second SDE node. or disabled. When both nodes are active. 2010 63 . Fairshare Installation & Configuration Guide: Release 5. perform the following steps to verify that the SDE is properly configured: 1. both should be green. Log into the SDE machine and verify that the VIPs are listed using the following command: ifconfig If any of the above checks failed.60 Rev. It contains the following levels: • • • SDE nodes WSAMs and VIPs configured to the node Devices (CMTSs. In the EMS SDE Nodes List > Logs node. 3. verify that all logs are free of errors. halt installation and contact Sandvine. In the EMS Status > SDE system node. verify that the SDE machines are green and that all required VIPs are attached to them. see below. For an explanation of the status view for the different SDE configurations. AMs) that communicate with the node on a given VIP The statuses of elements are displayed as follows: • • • • • Green — element connected Yellow — element is operational but no services are linked to it Red — element is disconnected Gray — element is disabled Blue — neutral element. disconnected. C04 05-00095-C04 July 8. such as a VIP When a cluster is configured in active-standby mode. the active SDE node should appear as green and the standby node should be yellow. SDE system view The Status > SDE System node displays a hierarchical diagram of the SDE system and indicates whether the different elements are connected. 2.

Chapter 2: Installing the management cluster SDE System: cluster in active-standby mode SDE System: active-active mode 64 Fairshare Installation & Configuration Guide: Release 5.60 Rev. 2010 05-00095-C04 . C04 July 8.

continue with Chapter 4: “Global SDE parameters” on page 75. For a single-cluster deployment (2 machines). Fairshare Installation & Configuration Guide: Release 5. 2010 65 . C04 05-00095-C04 July 8.Installation checks and troubleshooting SDE System: failover from active-active mode Cluster installation complete Next step: If the deployment includes more than one SDE cluster.60 Rev. continue on to Chapter 3: “Adding additional clusters” on page 67.

2010 05-00095-C04 .Chapter 2: Installing the management cluster 66 Fairshare Installation & Configuration Guide: Release 5. C04 July 8.60 Rev.

distributed architecture “Installation checks and troubleshooting” on page 73 — provides a list of verification procedures that should be performed after the SDE is installed and configured on both machines 3 • • • . The following topics are included in this chapter: • “Cluster overview” on page 68 — describes the new SDE cluster and the required configurations “Installing the SDE software” on page 69 — gives instructions for installing the SDE software on the SDE machines “Configuring the nodes” on page 70 — provides instructions for configuring the cluster’s high availability.Adding additional clusters This chapter provides detailed instructions for installing and configuring additional clusters to the site.

depending on whether it will run in active-standby mode (1 VIP) or activeactive mode (2 VIPs).60 Rev. 2010 05-00095-C04 .Chapter 3: Adding additional clusters Cluster overview Every additional cluster in the regional data center contains two SDE nodes. The number of clusters you configure will depending on the scaling requirements for the deployment. One or two VIPs are assigned to the edge service. C04 July 8. 68 Fairshare Installation & Configuration Guide: Release 5. Configure each additional cluster in the system in the exact order that the information is provided in this chapter. One edge service is configured to the cluster.

60 Rev. For instructions see “Local yum installation” on page 35. Following installation of the software. • Configure the SDE machine’s yum installer to point to the correct repository (first-time installation only when the yum repository is used) and install the software from the yum repository. For information. or. 2010 69 . verify that the installation is correct by using the procedures in “Installation verifications” on page 41. see “Configuring yum to install the SDE from an FTP site or HTTP server” on page 37 and “Installing the SDE software from the yum repository” on page 39.Installing the SDE software Installing the SDE software Install the SDE software on both machines in the cluster prior to configuring the VIPs. On each machine you need to: • Install the SDE software from the local yum repository. Fairshare Installation & Configuration Guide: Release 5. C04 05-00095-C04 July 8.

and the net mask assigned to the machine upon OS installation. assign the edge service one VIP (activestandby cluster) or two VIPs (active-active cluster). see “SDE node parameters” on page 61. Type the SDE’s physical IP address or FQDN. After the services are attached to the nodes. In the Configurations tree. For a description of the different node parameters. New SDE Node dialog box 2. C04 July 8. 3. Adding SDE nodes To add an SDE node to the system: 1.60 Rev. the node appears in the SDE Node List. 70 Fairshare Installation & Configuration Guide: Release 5. When the configuration is complete. The New SDE Node dialog box appears. The Progress Information bar appears to inform you of the configuration's progress. The configuration may take up to 2 minutes. Click OK. Designate the VIP(s) primary SDE node. Depending on the specific configuration of your system.Chapter 3: Adding additional clusters Configuring the nodes After installing the SDE software on the machines. right-click SDE Node List and select Add SDE Node. you also can attach the management service to the nodes at this point. 2010 05-00095-C04 . create a new edge service and attach it to both nodes. 4. add both nodes to the SDE system. The name enables you to differentiate the different types of nodes in the EMS GUI. Optionally give the node a name and description. Next.

Select Attached Services. then select Add Service. 2010 71 . Click Change.wsam_url=<border_VIP>:8080 parameter in the Fairshare Installation & Configuration Guide: Release 5. To change the primary node: a. 4.60 Rev. A list of services appears in the EMS right pane. The system automatically assigns the first SDE node configured to the system as the primary SDE node. Select the check box for the edge service. then click OK.fsam.odsp. on each SDE machine edit the com. Optionally type a description of the service.cmx. 3. Change the primary SDE node so that one of the nodes in the new cluster assumes ownership of the VIP. Attaching the services To attach the services to the nodes: 1. select Edge as the type of service and give the service a name. In the SDE Node List. In the New Service dialog box. Right-click Virtual IPs. 3. 4. 2. 2. Repeat the above steps for the second node in the cluster. do so at this time. Right-click Services List. C04 05-00095-C04 July 8. In the Primary SDE Node dialog box. Click OK. subnet mask. expand the first node in the cluster. 3. In the Configurations tree. select the second node from the list. and default gateway.properties file If the deployment will implement Fairshare using PCMM.Configuring the nodes Adding an edge service To create an edge service: 1. then select Add Virtual IP. b. Click OK. Specify the virtual IP. open Services List > Edge Service. The service appears in the Services list. The Virtual IP dialog box appears. Configuring the edge VIP(s) To configure the VIP(s) for the edge service: 1. 2. The New Service dialog box appears. Changing the border VIP in the fsam_conf. 4. Note: If your system’s configuration calls for attaching the management service to all SDE nodes.

as explained in “Configuring the outbound IPDR relay” on page 58. 2010 05-00095-C04 .Chapter 3: Adding additional clusters fsam_conf. or else first configure the outbound IPDR relay. Next step: Proceed to “Installation checks and troubleshooting” on page 63 to verify that the SDE is properly installed and configured. on each SDE machine configure the outbound IPDR relay.properties file” on page 57. Next step: Proceed to “Installation checks and troubleshooting” on page 63. C04 July 8. Configuring the outbound IPDR relay If the SDE will relay IPDR data to an external data collector. see “Changing the border VIP in the fsam_conf.60 Rev. For instructions.properties file to define the border VIP that the Fairshare engine will use to send Fairshare requests to the WSAM. 72 Fairshare Installation & Configuration Guide: Release 5.

C04 05-00095-C04 July 8. 3. see below. perform the following steps to verify that the SDE is properly configured: 1. For an explanation of the status view for the different SDE configurations.Installation checks and troubleshooting Installation checks and troubleshooting Following configuration of the second SDE node. If you have finished installing additional clusters. Fairshare Installation & Configuration Guide: Release 5. Log into the SDE machine and verify that the VIPs are listed using the following command: ifconfig If any of the above checks failed. halt installation and contact Sandvine.60 Rev. 2010 73 . 2. repeat the steps in this chapter for each cluster in the site. keep the EMS open and proceed to Chapter 4: “Global SDE parameters” on page 75. In the EMS SDE Nodes List > Logs node. verify that the SDE machines are green and that all required VIPs are attached to them. Cluster installation complete Next step: If the deployment includes more than two SDE clusters. In the EMS Status > SDE system node. verify that all logs are free of errors.

2010 05-00095-C04 .Chapter 3: Adding additional clusters 74 Fairshare Installation & Configuration Guide: Release 5. C04 July 8.60 Rev.

These parameters define the SDE’s behavior. as well as parameters that define system behavior when the SDE policy server is deployed “Log parameters” on page 81 — define the behavior of the different SDE logs “COPS parameters” on page 83 — protocol parameters for the COPS connection between the SDE and each AM or CMTS that connects to it when the SDE policy server is deployed “WSAM parameters” on page 84 — define the WSAM configuration parameters 4 • • • • . The following topics are included in this chapter: • “Overview of SDE parameters” on page 77 — contains information on configuring SDE parameters “General parameters” on page 78 — miscellaneous parameters common to the SDE.Global SDE parameters This chapter provides instructions for defining the global SDE parameters as part of the SDE configuration process.

60 Rev. C04 July 8. which collects subscriber usage and network topology information “Subscriber mapping parameters” on page 92 — explains how to configure the SDE for subscriber topology mapping • 76 Fairshare Installation & Configuration Guide: Release 5.Chapter 4: Global SDE parameters • • “Fairshare parameters” on page 85 — define the attributes of the different Fairshare elements “Data collection parameters” on page 86 — used to configure the SDE’s data collector module. 2010 05-00095-C04 .

define the parameters as necessary. 3. Unless otherwise indicated. Fairshare Installation & Configuration Guide: Release 5. 2. 2010 77 . log into the Web EMS. The SDE applies them to every cluster and node in the system.60 Rev. In the attributes pane. In the Configurations tree. Define the global parameters only once. open the SDE Parameters node. C04 05-00095-C04 July 8.Overview of SDE parameters Overview of SDE parameters The SDE contains a number of global parameters that define the behavior of different system elements. use the default values. Configuring SDE parameters To configure SDE parameters: 1. according to the values in the parameter tables. If necessary. then select the type of parameters you want to configure.

For use with the SDE policy server only Maximum amount of time a gate can exist before it is labeled a suspect garbage gate. For use with PCMM I02 when the SDE policy server is used Time interval between Gate-Infos during the gate synchronization process following a CMTS reconnection. For use with the SDE policy server only Maximum number of gates the edge service keeps in stateful storage. Range = 0 250. Element ID * 1 Stateful Limit 100000 Stateful Sync Yes Sync Time Between GateInfo (ms) 500 Storage Gate Timeout (sec) 180 (3 min) Garbage Gates Maximum Time (hour) 0 78 Fairshare Installation & Configuration Guide: Release 5. Parameter FEID Default Value Sandvine Inc. Table 8: General parameters Description Financial Entity ID. If you are using Fairshare with a third-party policy server or the SPB for data collection.Chapter 4: Global SDE parameters General parameters General parameters are miscellaneous parameters that are common to the SDE system. C04 July 8. Note: Parameters marked with an ‘*’ require configuration when the SDE policy server is used.60 Rev. For use with the SDE policy server only Network-wide unique identifier in the range of 0-99.000. If the number of gates in the system exceeds the stateful limit. For use with the SDE policy server only Time interval before the SDE erases a gate from the gate store if the CMTS doesn’t respond to the gate. Identifies the paying entity. Defined by the MSO according to PCMM specifications. 2010 05-00095-C04 . For use with the SDE policy server only SDE verifies a gate’s existence after CMTS reconnection by sending a Gate-Info. no new gates are processed by the SDE for forwarding to the CMTS. define only the RO Community and RW Community parameters. All other general parameters are for use when the SDE policy server is used.000.

all gates may be suspect T3=0 .General parameters Parameter Description When the time is set to ‘0’ the feature is disabled. below.only those gates without an idle time out can be suspect Cleans the IPsec configuration if the COPS connection is closed because the number of reconnect tries exceeds 10. For use with the SDE policy server only If CMTS buffering is used. Default Value Garbage Gates Start Time Determines the starting time for calculating the maximum amount of time in the above parameter: Creation . For use with the SDE policy server only If a CMTS temporarily disconnects from the SDE.60 Rev.calculation of maximum amount of time from the last time the gate was modified For use with the SDE policy server only.’ the system enables high availability for the gate store within each service. the SDE buffers the gates while waiting for the CMTS to reconnect. For use with the SDE policy server only. 2010 79 . the maximum time the gate waits in the queue before the SDE returns the gate with an error. “See Garbage gates”.maximum amount of time is calculated from when the gate was created Modification . See “Garbage gates”. C04 05-00095-C04 July 8. For use with the SDE policy server only All gates Enable Security No Failover on Startup Time (sec) 30 PSID 3333333333 Remote Stateful Update Yes Enable CMTS buffering Yes Maximum wait time in CMTS buffer (sec) 10 Fairshare Installation & Configuration Guide: Release 5. For use with the SDE policy server only If ‘yes. below. Creation Accounted Gates Determines which gates may be suspected as garbage gates: all gates . For use with the SDE policy server only SDE node’s ID number (I03 only). For use with the SDE policy server only Amount of time that elapses after system restart before the lead SDE node checks that all the nodes in his group are running.

2010 05-00095-C04 .60 Rev. 80 Fairshare Installation & Configuration Guide: Release 5.Chapter 4: Global SDE parameters Parameter RO Community Description The read only community for the SDE SNMP agent The read-write community for the SDE SNMP agent The cycle between DNS resolutions when a connection fails Default Value svPublic RW Community svPrivate 60 DNS resolution retry period (sec) Garbage gates The garbage gates feature (for use with the SDE policy server only) enables the SDE to tag gates as “suspect garbage gates” if they remain in the system unused for long periods of time. Use the Gates status list to view or delete suspect garbage gates. These may be gates that remain in the system after they are no longer needed. C04 July 8. or the CMTS may have deleted them though they are still recognized by the SDE.

which displays all activity on the SDE.60 Rev. Alert. Info. Warning. that a log can reach before the SDE renames it and starts a new one. the SDE generates an activity log for each CMTS (and—when the SDE policy server is used—for each RKS and AM) defined in the system. when it is enabled. Notice. warnings. debug and other information. 2010 81 . Critical. Default values may be used. which records system errors. the IP of the Syslog server and its threshold. Main Activity Log enabled: All activity logs activated Defines the debug level of the different processes: None. Table 9: Log parameters Description No Activity: No log activity on any system interface Main Activity Log disabled: Log activated only for the SDE node. Debug Internal debug flag. Maximum size = 10MB Defines the debug level: None. with the exception of the IP address for the Syslog server. in bytes. N/A Parameters Activity Log Level Default Value Main Activity Log Disabled Debug Level Info Max Error Log Size (Bytes) 512000 Max COPS Log Size (Bytes) (Internal PS only) 0 COPS Debug Level (Internal PS only) Info Debug Mutex (Internal PS only) No Fairshare Installation & Configuration Guide: Release 5. Debug The maximum size. Info. In addition. and the error log.) appears in the SDE node log. etc. C04 05-00095-C04 July 8. The SDE contains two central logs: the activity log. Configure the log parameters according to the values in the following table. Use the log parameters to define whether the Syslog is enabled or disabled and. Network element activity (CMTS. Warning. in bytes. Error.Log parameters Log parameters Log parameters define the behavior of the SDE system logs. Error. of the COPS library log before the SDE stores it and starts a new one. The log parameters also allow operators to configure the SDE so that each node sends messages to an external Syslog server. but not in the log specific to the network element. Maximum size = 10MB The maximum size.

Debug Info Enable Syslog Syslog Server Syslog Threshold No -Info 82 Fairshare Installation & Configuration Guide: Release 5. N/A No Internal debug flag. N/A No Internal debug flag. Info. N/A No Internal debug flag.60 Rev. Warning. N/A No Internal debug flag. Warning. 2010 05-00095-C04 . Debug Enables SDE to write to the Syslog IP address of the Syslog Server Defines the Syslog level: Error. C04 July 8. N/A No Internal debug flag. N/A No Defines the debug level of the log for the SDE agent: Error. Info. N/A Default Value No Internal debug flag. N/A No Internal debug flag.Chapter 4: Global SDE parameters Parameters Debug Thread (For use with SDE PS) Debug Socket (For use with SDE PS) Debug COPS (For use with SDE PS) Debug FSM (For use with SDE PS) Debug Gate (For use with SDE PS) Debug PS (For use with SDE PS) Debug Sharing (For use with SDE PS) Debug Dump (For use with SDE PS) Management Log Threshold Description Internal debug flag.

C04 05-00095-C04 July 8.COPS parameters COPS parameters COPS parameters define the protocol parameters for the COPS connections between the WSAM and the policy server when the SDE’s policy server is used. Timeout in ms when resending OPN Parameter PCMM Client Type Default Value 32778 Listening Port PEP ID COPS OPN Timeout (ms) 3918 SV-SDE_tm 60000 KA Timeout (sec) 30 COPS OPN Resend Timeout (ms) Reconnect Timeout (ms) Compatible PCMM Version 2000 Time in ms before reconnecting to the CMTS The most recent PCMM version with which the SDE is compatible. The SDE will also be compatible with all previous versions. 2010 83 . This value can be changed for each CMTS through the CMTS attributes. Ethernet card on which the SDE runs 10000 PKT-SP-MM-I03 Interface name eth0 Fairshare Installation & Configuration Guide: Release 5. All default parameters may be used.60 Rev. Table 10: COPS parameters Description Defines the COPS client type according to the PCMM protocol Port on which the AM connects to the SDE String that identifies the SDE The amount of time in milliseconds that the SDE waits between opening a COPS connection and waiting for the CAT message Keep Alive Timeout in seconds for the CMTS.

2010 05-00095-C04 .Chapter 4: Global SDE parameters WSAM parameters WSAM parameters define the configuration of the WSAM in the SDE. Note: If you change this value to ‘Yes’ you MUST restart the SDE. ‘Yes’ for this configuration. it also must be activated in the AS. Use the default value. If HTTP is used. Use all default parameters. Table 11: WSAM parameters Description Determines whether HTTPS is used to secure the connection between the AS and WSAM or Fairshare Engine and WSAM. The attribute must be set to this mode for Fairshare to work.60 Rev. Parameter Use HTTPS Default Value No Time between retries (sec) Retries number 60 30 Ignore AS Username Yes Session Store Capacity 100000 Enable WSAM Session Sharing Yes Caution: The Ignore AS Username attribute must be set to ‘yes’ for Fairshare to work. These parameters are used when the SDE applies Fairshare actions using PCMM. Note: If you change this value to ‘No’ you must restart the SDE. 84 Fairshare Installation & Configuration Guide: Release 5. rather than HTTP (the default). No: Accepts service requests that arrive without a user name in the header or from an unknown application server. The SDE assigns a default user name in this case. The maximum number of sessions that the WSAM can hold in its session store Determines whether the WSAM nodes will share service requests among themselves. Retry interval for the persistency function The number of times the persistency function tries to recreate a WSAM session Yes: WSAM only authorizes service requests from application servers with known user names (configured in SDE). C04 July 8.

EXACTLY as defined in the SPB. Use all default parameters. 2010 85 . the Enable File Logging parameter MUST be set to ‘yes’. the parameters should be set to ‘6’. Default number of periods for which the Fairshare policy is applied (1 period = 15 minutes). This parameter is required only when Fairshare uses data from the SPB. The number of connections the SDE supports between the Fairshare Engine on each node and the WSAM. C04 05-00095-C04 July 8. The total number of connections in a regional data center cannot exceed 40. in a 6-node. data center. and the parameter should be defined accordingly.Fairshare parameters Fairshare parameters Fairshare parameters define the parameters for the different Fairshare elements. This parameter is used only for applying Fairshare actions using PCMM. Table 12: Fairshare parameters Description Realm name of the service provider. Note: To enable IPDR logging to sFlow files.) Parameter Realm Name Default Value DEFAULT Default Duration 1 Connections per Node 20 Fairshare Installation & Configuration Guide: Release 5. or 3 cluster.60 Rev. (For example.

They also contain parameters that enable the NetPortal to access the subscriber usage and topology information from a central location.Chapter 4: Global SDE parameters Data collection parameters Data collection parameters define the method the SDE uses to collect subscriber and network topology data. Subscriber usage data can be collected using IPDR or from the SPB. or interfaces can be configured manually and bandwidth can be calculated using IPDR data. The SDE can use SNMP to discover CMTS interfaces and retrieve bandwidth usage information. 86 Fairshare Installation & Configuration Guide: Release 5. The data collection node contains four sets of parameters: • General parameters: define the source of subscriber usage data and the method of configuring interfaces and calculating bandwidth. C04 July 8.60 Rev. Table 13: General data collection parameters Description Defines the source of subscriber usage data: IPDR: receives IPDR data from CMTSs or an external data collector SPB: collects subscriber statistics from the SPB None: The SDE doesn’t collect subscriber data. The source of the information for CMTS interface properties: Parameter Data Collection Default Value IPDR Interface Definitions Source SNMP SNMP: SDE receives interface properties through SNMP. SNMP collection: enable the operator to define the interval for polling CMTSs using SNMP IPDR collection: enable the SDE to collect subscriber data using IPDR SPB collection: enable the SDE to collect subscriber statistics from the SPB • • • General data collection parameters General data collection parameters define the source of subscriber usage data and the method of configuring interfaces and calculating bandwidth. 2010 05-00095-C04 . They also contain parameters that enable the NetPortal to access the subscriber usage and topology information from a central location.

60 Rev. this Yes Use SCN Enable Central Database Logging Primary Central Database -- Secondary Central Database -- Fairshare Installation & Configuration Guide: Release 5. 2010 87 .) Determines whether the contents of each cluster’s database is copied to the central database for use by the NetPortal: Yes: Each cluster’s database is logged to the central database. this parameter is set to ‘No’ . On the NetPortal cluster. When the NetPortal is used. Interface properties are configured manually through the EMS Default Value Interface Bandwidth Source The source of interface congestion information: SNMP SNMP: SDE receives the congestion information through SNMP IPDR: Interface congestion information is obtained from the IPDR record Subscriber Tier Source The source of the SCN for determining the subscriber’s tier. IP address of the secondary NetPortal node. IP address of the primary NetPortal node. Use XML: Retrieves the SDE subscriber list (cmxSubscribers. Use this setting in a test environment.Data collection parameters Parameter Description By Configuration: SNMP is disabled in the SDE.xml). C04 05-00095-C04 July 8. Use SCN: Retrieves the tier information from the CMTS. No: The SDE cluster doesn’t log to the central database. (See “Data tier injection” on page 88 for an explanation of this feature. all SDE clusters except the NetPortal are set to ‘Yes’. Use this setting in a real network environment. Use External Source: Retrieves the tier information from an external source via a CSV file. On the NetPortal cluster. the Primary Central Database parameter for all SDE clusters except the NetPortal should be set to the edge VIP of the NetPortal cluster. When the NetPortal is used. this parameter should be left empty. When the NetPortal is used.

2010 05-00095-C04 . In the SCN Source field. Default Value Collecting CMTS interface information The SDE provides different options for collecting CMTS interface information and calculating bandwidth usage: • SNMP is used to discover CMTS interfaces. Data tier injection In order to apply Fairshare policies by tier. It may retrieve bandwidth using SNMP or IPDR (for deployments collecting data using IPDR). it is possible to import subscriber tier attributes directly into the SDE from a third-party source. select SDE Parameters > Data Collection > General. In order to enable importing of tier attributes. For this option. see Configuring CMTS interfaces. you may want to specify a different Upstream ifSpeed default and Downstream ifSpeed default for each CMTS. C04 July 8. select Use External Source. in the EMS. The Interface Bandwidth Source parameter can be set to ‘SNMP’ or ‘IPDR’ depending on the type of deployment and the service provider’s needs. If the deployment uses IPDR data collection. the Interface Definitions Source parameter is set to ‘SNMP’. This option can be used only if the system is configured for IPDR data collection. To import subscriber tier attributes from a third party: 1. • To configure CMTS interfaces manually when the ‘By Configuration’ value is used for the parameter.60 Rev.Chapter 4: Global SDE parameters Parameter Description parameter should be left empty on the NetPortal cluster. interfaces are configured manually for the CMTS through the EMS and bandwidth is calculated using data received from the IPDR records. see “CMTS and IPDR session attributes” on page 101. 88 Fairshare Installation & Configuration Guide: Release 5. 2. SNMP is not used. the IPDR collector does not overwrite the field in the Fairshare database. The Interface Definitions Source is set to ‘By Configuration’ and the Interface Bandwidth Source is set to ‘IPDR’. For information. the SDE uses the interface properties acquired from the IPDR data and the Upstream/ Downstream ifSpeed default parameters defined for the CMTS in the SDE. If the interfaces are not configured in the EMS . If this option is enabled. Instead.

that contains the data to be imported. Fairshare Installation & Configuration Guide: Release 5.<Tier>.Data collection parameters EMS showing Subscriber Tier Source drop-down menu 3. Table 14: SNMP collection parameters Description Polling interval when SNMP is used to fetch CMTS interface information Parameter SNMP Polling Time (ms) Default Value 900000 IPDR collection parameters IPDR collection parameters define how the SDE collects subscriber data using IPDR. Place the file in the /opt/SDE/data_injection directory.172. 2010 89 . The file should include three columns in the following exact order: <Subscriber CM MAC address >.60 Rev. named <csv_file_name>.<CMTS IP>.3.gold 4. The CSV file entries should appear in the same format as the following example: 020300083100. The SDE imports the subscriber tiers from the third-party source.152.16. SNMP collection parameters SNMP collection parameters define the interval for polling CMTSs using SNMP. Create a CSV file. C04 05-00095-C04 July 8.

90 Fairshare Installation & Configuration Guide: Release 5. -- Relay Collector Port -- IPDR File Listening Port 6210 IPDR SP Listening Port 4737 Logging inbound IPDR files to the SDE You can optionally configure the SDE so that inbound IPDR files are written both to the Fairshare database and directly to the SDE machine. When this parameter is set to ‘Yes’. set Enable File Logging to ‘Yes’. C04 July 8. Yes: writes to file No: doesn’t write to file Parameter TFTP Directory Default Value /opt/tftpboot/ Enable File Logging No Relay Collector IP The IP to which the IPDR data will be sent when the SDE relays data to an the external IPDR collector. This value is used for IPDR data collection.Chapter 4: Global SDE parameters Table 15: IPDR collection parameters Description Home directory of the TFTP server. Used only when the SDE relays data to a third-party collector The port that must be opened on the external IPDR collector when it receives data from the SDE. Enables the IPDR collector to write all IPDR records to file. Used only when the SDE relays data to a third-party collector When IPDR Stream is used. Enable File Logging also has to be enabled for each CMTS. 2010 05-00095-C04 . Note: Make sure that Enable File Logging is also set to ‘Yes’ for each CMTS. The SDE port used when the CMTS sends data over SP. To configure the SDE to log the inbound IPDR files to the SDE: • In the Data Collection > IPDR Collection parameters. SPB collection parameters SPB collection parameters define how the SDE collects subscriber data from the SPB. the port on which the IPDR collector listens for incoming connections (NA for the inbound IPDR relay).60 Rev.

C04 05-00095-C04 July 8.60 Rev. However. The amount of time the SDE waits after a request to the SPB before timing out and starting a new polling request The maximum number of SPB collection sessions that are allowed to run simultaneously Parameter Check for new data every (min) Default Value 3 PTS Reporting Period (min) 15 SPB Request Timeout (sec) 60 Number of SPB Connections 1 Fairshare Installation & Configuration Guide: Release 5. the minimum value is 15 minutes. 2010 91 .Data collection parameters Table 16: SPB collection parameters Description How often the SDE requests information from the SPB. The value should be equal to or lower than that configured for the PTS to report to the SPB. How often the PTS reports to the SPB. This value must match the interval configured on the PTS and SPB for PTS reporting.

C04 July 8.g. Yes: Performs a ‘push all’ whenever the SDE detects that an SPB was reactivated. interface or tier between IPDR reporting periods. It writes the subscriber topology information to the Fairshare database to provide full subscriber mapping. SCN and tier information in a non-SDE reporting environment (e. This operation is required when there are long intervals between Push to SPB activity or if the SPB was disconnected. Table 17: Subscriber mapping and P2SPB parameters Description Enables the SDE to dynamically discover subscriber IPs and topology information. Changing this parameter from to ‘No’ to ‘Yes’ activates an immediate push all. all P2SPB parameters must be configured. this feature can be used optionally to enable the SDE to detect changes to a subscriber’s CMTS. 2010 05-00095-C04 . as it enables the SPB to provide reports containing subscriber QAM.. Subscriber to QAM mapping dynamically discovers subscriber IP addresses and QAM mapping based on DHCP packets teed by the PTS.60 Rev. No: The SDE doesn’t perform any push all. Required when SPB data collection is used Enables operators to map subscriber topology information from the Fairshare database to the SPB Pushes all subscriber topology data to the SPB.Chapter 4: Global SDE parameters Subscriber mapping parameters The subscriber mapping parameters enable operators to provide full subscriber mapping for the different types of data collection. Subscriber to QAM mapping is required when SPB data collection is used. CMTS. It detects changes in subscriber mapping and associates the subscriber’s cable modem with its upstream/ downstream channels. including the number of subscribers whose topology No Parameter Enable Subscriber To QAM Mapping Enable Push to SPB Default Value Yes Push all subscribers to SPB on start-up No 92 Fairshare Installation & Configuration Guide: Release 5. The results of the push all action. When P2SPB is enabled. The P2SPB (Push to SPB) feature enables operators to map subscriber topology information from the Fairshare database to the SPB. bonded group. the NDS). When IPDR data collection is used and the PTS is deployed in the system. This feature can be used with either SPB or IPDR data collection.

tier SCN attribute name scn_attr Next step: After configuring the global SDE parameters.Subscriber mapping parameters Parameter Description information was pushed to the SPB. Default Value Tier attribute name The attribute name of the tier as it appears on the SPB. continue on to the next step. It enables the SDE to push tier information to the correct attribute. The attribute name of the SCN as it appears on the SPB. See Chapter 5: “Import CMTSs” on page 95. 2010 93 . C04 05-00095-C04 July 8. configuring CMTSs to the system.60 Rev. It enables the SDE to push SCN information to the correct attribute. are displayed in the SDE node’s Push To SPB activity log. Fairshare Installation & Configuration Guide: Release 5.

Chapter 4: Global SDE parameters 94 Fairshare Installation & Configuration Guide: Release 5. C04 July 8.60 Rev. 2010 05-00095-C04 .

The following topics are included in this chapter: • “Import CMTSs/CMTS maps overview” on page 96 — explains the Import CMTS option and outlines the different steps in the procedure “Import CMTSs” on page 97 — explains how to set up a CSV data file and CMTS XML description file and import CMTS lists “Importing CMTS lists” on page 107 “Import CMTS maps” on page 109 — explains how to import CMTS map lists from a CSV file. including how to set a CMTS XML description file to accompany the CSV file. This step is required only if the SDE policy server will be used to apply Fairshare actions 5 • • • .Import CMTSs This chapter provides instructions for configuring large numbers of CMTSs and their related maps to the system in a single action using the Import/Export CMTSs and CMTS Maps feature.

For instructions regarding how to manually configure individual CMTSs to the system. Note: The Import CMTS Maps option is required only when the SDE policy server will be used to apply Fairshare actions. 96 Fairshare Installation & Configuration Guide: Release 5. C04 July 8. 2010 05-00095-C04 . This feature facilitates the configuration process by eliminating the need to manually configure every CMTS using the EMS or the EMS command line interface. see Appendix C: “Manually configuring CMTSs” on page 155.Chapter 5: Import CMTSs Import CMTSs/CMTS maps overview The Import CMTS and Import CMTS Maps options allow operators to configure large numbers of CMTSs and their related maps to the system in a single action by importing them from CSV files containing the attributes for each CMTS being imported. The files necessary for the import can be prepared in advance. However. the actual import should be performed after configuring the SDE clusters for services.60 Rev.

Save the CSV and XML files to the folder. 5. as defined in the XML description file you create for the process. or one for each edge service or CMTS. It is recommended that you create the XML file first to define the specific attributes (and their corresponding column).60 Rev. Create one or more CSV data files for the CMTSs provisioned to the site. The steps for performing the Import CMTS or Import CMTS Maps process are as follows: 1. • At a minimum. The DOCSIS type also is required for non- Fairshare Installation & Configuration Guide: Release 5. Make sure that each column matches the appropriate Index ID in the XML file. Save both files in the directory of your choice on the machine from which you are running or connecting to the Web EMS. They also contain the required values for each CMTS’s IPDR sessions. see “CMTS XML description file” on page 97. along with the attributes you want to configure for these CMTSs. They all MUST follow the same template. C04 05-00095-C04 July 8.Import CMTSs Import CMTSs In order to import a list of CMTSs or CMTS maps from a CSV data file. see “CSV data file” on page 100. Create one or more CSV files containing the attributes for each CMTS being imported. Create a dedicated folder on the SDE machine from which you are running the EMS (the machine on which you are using the Web browser). and then build the CSV files according to the XML file. 2010 97 . You can create a single CSV data file for the site. see “Importing CMTS lists” on page 107. Create an XML description file that explains each of the attributes in each CMTS that will be imported. including the metadata and parameters for the CMTSs’ IPDR sessions. The corresponding XML file provides metadata about each column in the CSV files. For information. Import the CSV and XML files using the Import CMTS List feature. For instructions. you need to create an XML file that provides metadata about each column in the CSV files that you also will create. 3. For instructions. 2. only the IP (Ip attribute) and vendor ( attribute) of each CMTS is required in the XML and CSV files. 4. CMTS XML description file The CSV files contain a list of all the CMTSs you are importing.

This unique ID is used to identify the CMTS when importing ranges or subnets. see Appendix D: “Example XML description files for CMTS import” on page 171. If the system contains more than 1 edge service or more than 1 VIP for the edge service. or the DOCSIS 3. you also must define the edge service and VIP for each CMTS. the DocsisVersion parameter must be defined for DOCSIS 2. If DOCSIS 2.0 CMTSs will send SAMIS IPDR data to the SDE (as opposed to SAMIS-TYPE-1). C04 July 8. Depending on the specific Fairshare configuration. • • • • The only other requirement is that the index IDs must match the columns in the CSV file. Otherwise. • If you also will be importing CMTS maps. separated by the IPDRSessions tag. SnmpCollection and IpdrCollection attributes. 2010 05-00095-C04 .0 CMTSs. the XML and CSV files also must define the value for the CollectOnly.0" encoding="UTF-8"?> <CmtsView> <Index id="0">IsEnabled</Index> <Index id="1">CmtsLabel</Index> <Index id="2">Id</Index> <Index id="3">Ip</Index> <Index id="4">IpdrIP</Index> <Index id="5">SnmpIP</Index> <Index id="6">IpdrRecordIP</Index> <Index id="7">Port</Index> <Index id="8">CmtsVendor</Index> <Index id="9">CmtsKATimeout</Index> <Index id="10">RksId</Index> <Index id="11">Service</Index> <Index id="12">VipId</Index> <Index id="13">CmtsJitter</Index> 98 Fairshare Installation & Configuration Guide: Release 5. Available CMTS attributes The XML file below displays all available CMTS attribute fields that can be included in the XML file and corresponding CSV file.60 Rev.0 CMTSs are used. Note: To see sample XML description files for different Fairshare deployment types. When these attributes are defined. For an explanation of each of the attributes and possible values. For deployments using IPDR collection.Chapter 5: Import CMTSs DOCSIS 3. each CMTS will default to the first edge service and edge VIP defined in the system. All other values will fall back to the defaults defined in the system. it is recommended that you assign each CMTS a unique ID (Id attribute).0 (‘20’). depending on your system’s configuration. the IPDR session parameters are defined after all CMTS parameters. <?xml version="1. see “CMTS and IPDR session attributes” on page 101. the Service attribute must appear before the VipId attribute.

indicating that 2 IPDR sessions are defined for the CMTS. The following XML file displays a sample XML file with the minimum CMTS parameters and one IPDR session. 2010 99 . The values for each session are listed one after another. <?xml version="1. separated by a comma. the import won’t work. C04 05-00095-C04 July 8. the IPDRSessions attribute might be assigned a value of 2.Import CMTSs <Index id="14">CmtsUPDelay</Index> <Index id="15">CmtsDownDelay</Index> <Index id="16">RCGap</Index> <Index id="17">CollectOnly</Index> <Index id="18">community</Index> <Index id="19">AllSubnets</Index> <Index id="20">SnmpCollection</Index> <Index id="21">IpdrCollection</Index> <Index id="22">CmtsUpstreamCongestion</Index> <Index id="23">CmtsdDownstreamCongestion</Index> <Index id="26">DocsisVersion</Index> <Index id="27">EnableFile</Index> </CmtsView> Caution: If the Service attribute is not listed before the VipID.60 Rev. IPDR session definitions IPDR sessions are configured in the CMTS XML and CSV files and are imported with the CMTSs in a single action. using the IPDRSessions tag to separate them from the CMTS fields. Define the IPDR attribute fields at the end of the XML file. This tag also indicates the number of IPDR sessions added to the current CMTS. Fairshare Installation & Configuration Guide: Release 5.0" encoding="UTF-8"?> <CmtsView> <Index id="0"> CmtsLabel </Index> <Index id="1"> Ip </Index> <Index id="2"> IPDRSessions </Index> <IPDRSessionParams> <Index id=“3">SessionName</Index> <Index id=“4">DocsisType</Index> <Index id=“5">SessionId</Index> <Index id=“6">ConnectionMode</Index> <Index id=“7">SessionType</Index> <Index id=“8">Port</Index> </IPDRSessionParams> </CmtsView> In the CSV file.

Chapter 5: Import CMTSs

For example, for two IPDR sessions, the values might be defined in the CSV file as: session_1,CPE-TYPE,24,CMTS,Event,1432,session_2,SAMIS-TYPE-1,22,CMTS,Event, 1432 For an explanation of each of the IPDR session attributes and their possible values, see “CMTS and IPDR session attributes” on page 101.

CSV data file
Each row in the CSV file defines the attributes for a specific CMTS. Each column in the CSV file corresponds to a specific index ID (CMTS attribute) defined in the XML description file. The CSV file columns are listed in the same order as the XML description file index IDs so that each consecutive CSV column maps to the next index ID in the XML description file. For example: • • • CSV column A = <Index id="0"> CSV column B = <Index id="1"> CSV column C = <Index id="2">

The following figure displays the attributes contained in a sample CSV file for five CMTSs, while the accompanying sample XML file illustrates how these columns correspond to CMTS attributes.

<?xml version="1.0" encoding="UTF-8" ?> <CmtsView> <Index id ="0">IsEnabled</Index> <Index id ="1">CmtsLabel</Index> <Index id ="2">Id</Index> <Index id ="3">Ip</Index> </CmtsView> In the above example, the Index ID explains which column of the CSV file is mapped to each CMTS attribute: • • • • Index id = 0, IsEnabled is mapped to column A. Index id = 1, CmtsLabel is mapped to column B (and used to identify the CMTS when importing CMTS map ranges or subnets). Index id = 2, Id is mapped to column C. Index id = 3, Ip is mapped to column D.

100

Fairshare Installation & Configuration Guide: Release 5.60 Rev. C04
July 8, 2010 05-00095-C04

Import CMTSs

CMTS and IPDR session attributes
The following table describes the CMTS and IPDR session attributes that may be included in the CSV file. Table 18: Attributes for CMTS import Description
Determines whether the CMTS is enabled. CMTS name, as it appears in the EMS Unique ID of the CMTS Physical IP address or FQDN of the CMTS. If the SDE connects to the SPB for data collections and/ or Fairshare enforcement, the format must match the format (IP or FQDN) used to define CMTSs in the SPB. When the SDE initiates the IPDR/ SP connection, the IP address the SDE uses to connect to the CMTS to receive IPDR data, if different than the CMTS IP. If the CMTS or external relay initiates the connection, this is the IP value contained in initiatorId field of the CONNECT message. If the IPDR IP is empty, the value of the CMTS IP is used. The IP address the SDE uses to connect to the CMTS to receive SNMP data, if different from the IP address defined above for the CMTS. Used for all deployment types The IP address sent by the CMTS in the IPDR record’s CMTSipAddress field, if different from the IP address defined above for the CMTS. Use this IP when the CMTS or external relay

Attribute
IsEnabled / IsDisabled CmtsLabel

Value to Define
Disabled/ Enabled

Default Value
Enabled

<alphanumeric>

CMTS_<X>

Id Ip

numeric <000.000.000.000 > or alphanumeric

---

IpdrIP

<000.000.000.000 >

--

SnmpIP

<000.000.000.000 >

--

IpdrRecordIP

<000.000.000.000 >

--

Fairshare Installation & Configuration Guide: Release 5.60 Rev. C04
05-00095-C04 July 8, 2010

101

Chapter 5: Import CMTSs

Attribute

Description
sends IPDR data to the SDE using file mode. If the IPDR Record IP is not configured, the SDE by default uses the IPDR IP. If no IPDR IP is configured, either, the SDE uses the CMTS IP for the IPDR data.

Value to Define

Default Value

Port

CMTS COPS port number . Used only with the SDE policy server CMTS vendor: Cisco, BigBand, Motorola, Arris, Relay (used for third-party IPDR collectors) Keep Alive Timeout in sec. between the CMTS and PS. Optimize the value (30s) according to the CMTS’s status. Used only with the SDE policy server The RKS linked to this CMTS. Optional parameter used only with the SDE policy server Name of the edge service connected to the CMTS, as defined in the cmxServices.xml file Edge VIP that the selected service uses to connect to the CMTS Minimum jitter guarantee capacity. Used only with the SDE policy server Minimum delay on the cable modem. Used only with the SDE policy server Minimum delay on the CMTS. Used only with the SDE policy server Time interval in ms that the SDE waits before forwarding the next

usually ‘3918’ (the standard) <Vendor name>

3918

CmtsVendor

--

CmtsKATimeout

0 = no time 1 - 4294967295

--

RksId

--

None

Service

<alphanumeric>

Edge Service

VipId

<000.000.000.000 >

--

CmtsJitter

0 - 4294967296

200

CmtsUPDelay

0 - 4294967296

30

CmtsDownDelay

0 - 4294967296

200

RCGap

0 = disables the rate limit feature,

0

102

Fairshare Installation & Configuration Guide: Release 5.60 Rev. C04
July 8, 2010 05-00095-C04

Optional parameter used only with the SDE policy server Default AllSubnets No SnmpCollection Determines whether the SDE collects SNMP data from the CMTS. No: SDE doesn't collect SNMP data. No: The SDE collects both IPDR and/or SNMP data from and sends policies to the CMTS using the SDE policy server Yes: The SDE only collects IPDR and/ or SNMP data from the CMTS.Import CMTSs Attribute Description gate command. Min delay range = 20 ms to 2^31-1. Default Value CollectOnly Determines whether the SDE connects to the CMTS as a policy server. 2010 103 . Use this setting for deployments using an external policy server or only the PTS to apply Fairshare actions. No community The SNMP community used for CMTS Discovery on this CMTS Determines whether the discovery process discovers all CMTSs subnets. Accuracy is ± 5 ms. Yes Fairshare Installation & Configuration Guide: Release 5.60 Rev. (Use this setting when setting up the relay from third-party IPDR collectors. This parameter is used only when the SDE is set to SNMP collection (the default) in the L2 Topology parameters. ‘Default’ or <alphanumeric> Yes: Discovers all subnets No: Discovers only those subnets belonging to a DOCSIS MAC layer Yes: SDE collects SNMP data from the CMTS.) Yes: SDE collects IPDR data from the CMTS or SPB statistics. C04 05-00095-C04 July 8. Used only with the SDE policy server Value to Define no delay. Yes IpdrCollection Determines whether the SDE collects IPDR or SPB data.

or DOCSIS 1.100 80 IfSpeedUpstreamDef ault All positive values are accepted. 2010 05-00095-C04 . DOCSIS version supported by the CMTS: DOCSIS 3. Default ifSpeed assigned to any unrecognized CMTS downstream interface an the IPDR record.0 30 EnableFile Yes = writes to file No = doesn’t write to file No IPDRSessions SessionName <numeric> <alphanumeric> (maximum length of 50) SAMIS-TYPE-1 CPE-TYPE SAMIS 1 IPDR Session_1 -- DocsisType 104 Fairshare Installation & Configuration Guide: Release 5. This parameter is used for IPDR data collection. C04 July 8.60 Rev. When using the outbound IPDR relay function. even if the CMTS is DOCSIS 3. 42884296 11 = 1.100 80 CmtsDownstreamCongestion 1 . If the CMTS will send SAMIS data to the SDE.1 20 = 2. SAMIS. select ‘DOCSIS 2’. or CPE-TYPE 1 .Chapter 5: Import CMTSs Attribute Description Value to Define No: The CMTS only sends COPS messages and SNMP data Default Value CmtsUpstreamConge stion Percentage of the upstream bandwidth above which an interface on a CMTS is considered congested Percentage of the downstream bandwidth above which an interface on a CMTS is considered congested Default ifSpeed assigned to any unrecognized CMTS upstream interface in an IPDR record. DOCSIS 2. this parameter must be set to ‘Yes’.0 30 = 3. Enables the IPDR collector to write the CMTS’s IPDR records to file. Indicates the number of IPDR sessions added to the CMTS Optional name assigned to the IPDR session type for identification purposes Defines the type of data sent to the SDE: SAMIS-TYPE-1. 10240000 IfSpeedDownstream Default DocsisVersion All positive values are accepted.0.

65535 SDE SessionType Determines the type of IPDR flow.60 Rev. and the SDE treats the IPDR data in the same manner as if it were received directly from the CMTS. the collector initiates an IPDR connection to the SDE. according to the CMTS’s configuration: Value to Define 0 .255 1 Default Value ConnectionMode CMTS: the IPDR waits for the CMTS to initiate sessions. Event: An event serves as the trigger for the CMTS to send the data. Fairshare Installation & Configuration Guide: Release 5. SDE: the SDE initiates the connection. 2010 105 . C04 05-00095-C04 July 8. The XML and CSV files for the CMTS import must contain the following attributes specific to this deployment type: Note: No other configurations are required on the SDE for the inbound IPDR relay. according to the CMTS’s configuration: Time Interval Port The SDE port used when the CMTS sends data over SP (Client connection mode only) 4737 Importing CMTSs when using inbound IPDR relay When the SDE receives IPDR data from an external IPDR collector rather than directly from the CMTSs. 1025 . Ad Hoc: The IPDR closes the session between the intervals at which the CMTS sends the data (Server connection mode only). Time Interval: The CMTS sends IPDR data at intervals.Import CMTSs Attribute SessionId Description Unique ID that must match the IPDR Session ID configured on the CMTS Defines whether the SDE or CMTS initiates the IPDR sessions.

2010 05-00095-C04 . include the IpdrIP field. The parameter should match the CMTSipAddress field that the relay fills for the particular CMTS. • • • • • • • • 106 Fairshare Installation & Configuration Guide: Release 5. C04 July 8. Use the SnmpCollection attribute and set the value of the attribute to ‘Yes’.60 Rev. Use the attribute and set its value to ’Yes’. include the IpdrRecordIP parameter. Include the ConnectionMode tag and set the value to ‘CMTS’. If the relay will send the IPDR data using file mode. Include the IPDRSessions tag and define the IPDR sessions: The SessionName attribute is option. The relay uses the IpdrIp value to fill the initiatorId field of the CONNECT message instead of the CMTS’s IP address. SAMIS.Chapter 5: Import CMTSs • If the relay will send the IPDR data using an IPDR/SP connection. or CPE-TYPE). Include the DOCSISType attribute and define the type of data sent for each CMTS (SAMIS-TYPE-1. Include the SessionId and SessionType attributes and define their values according to the configurations on the relay.

Click Import.Importing CMTS lists Importing CMTS lists Note: Prior to importing a CMTS list. Validated fields are: • • • • • • IsEnabled ServiceID VipId CollectOnly community IpdrRecordIP 107 Fairshare Installation & Configuration Guide: Release 5. Repeat the procedure for each CSV file you need to import. The CMTSs appear in the CMTS List > CMTS tree in the Configurations tree. 2010 . This message refers you to the EMS log for a list of CMTSs that were not imported successfully. In the Configurations tree of the SDE EMS. The Import CMTS List dialog box appears. 3. right-click CMTS List and select Import CMTSs from CSV file. Import CMTS List dialog box 2. an error message appears on the EMS. 4. C04 05-00095-C04 July 8. To import a CMTS list: 1. verify that a CMTS XML description file has been created that provides metadata about the CSV data file. Errors are reported only for fields that are validated during the import process. Import errors If an error occurs during the CMTS import procedure.60 Rev. Set the path for the CSV and corresponding XML file to be imported.

resize the EMS window using the mouse.g. the EMS displays only the first 99 CMTSs in the CMTS list > CMTS Tree. the correct number of CMTSs is displayed. and then maximize it. Note: When viewing the SDE system through the EMS using Status > SDE System.g. 108 Fairshare Installation & Configuration Guide: Release 5. even though the correct number of CMTSs is displayed in the status bar at the bottom of the screen.Chapter 5: Import CMTSs • • • SnmpIp SnmpCollection IpdrCollection The EMS log is created on the machine from which you are running the EMS at the following location: • • • Mozilla Firefox: Firefox installation folder (e. C04 July 8. To display all CMTSs in the CMTS tree..60 Rev. C:\Program Files\Mozilla Firefox) Windows EMS: Windows EMS installation folder (e. 2010 05-00095-C04 ..C:\Program Files\EMS \SDE_EMS Linux EMS: /opt/SDE/SDE_EMS/ Viewing CMTSs in the EMS following import When 100 or more CMTSs are configured to the system in a single import.

Import CMTS maps

Import CMTS maps
The Import CMTS Maps feature enables you to import subscriber maps for the CMTSs you import using the Import CMTS feature. When this feature is used, you do not need to manually define the maps for a long list of imported CMTSs when the SDE enforces Fairshare using its internal policy server. The Import CMTS Maps feature supports both subnets and ranges. It is enough to define either the CMTS’s range or the subnet, but you can define multiple ranges and subnets for the same CMTS depending on your system’s requirements as long as they don’t conflict with each other. Prior to importing CMTS maps, you must create a CMTS map XML description file that provides metadata about the CSV data file. Separate XML and CSV files must be created for importing ranges or subnets. Create one XML file for ranges and one XML file for subnets, but as many CSV files as required to import the different ranges and/or subnets for each CMTS. Caution: You can import CMTS maps only after importing their related CMTSs. When the SDE collects subscriber data from the SPB, you must configure the IP exclusions for MTA and CPE IP addresses prior to importing subnets or ranges for a CMTS. For information regarding IP exclusions, see “IP exclusions” on page 117.

CMTS maps XML description file
The EMS supports two CSV files for CMTS maps: a range file and a subnet file. In order to import the CMTS maps from either of these files, you first must create a CMTS map XML description file that provides metadata about the CSV data file. This file resides on the EMS machine in the directory of your choice.

Sample subnet file
The following is a sample XML file for map subnets. The MapID attribute in column 0 is mapped to the MapID for the corresponding CMTS. <?xml version="1.0" encoding="UTF-8" ?> <MapDescription> <General> <Type>Subnet</Type> <Index id="0">Id</Index> </General> <Subnet> <Index id="1">Net</Index> <Index id="2">Mask</Index> </Subnet> </MapDescription> Where Id (Index ID 0) is the unique ID of the CMTS as specified in the CMTS CSV file.

Fairshare Installation & Configuration Guide: Release 5.60 Rev. C04
05-00095-C04 July 8, 2010

109

Chapter 5: Import CMTSs

The following sample CSV file contains a single subnet for the CMTS corresponding to MapID 1 and three subnets corresponding to MapID 2 (shown in column 0).

Sample CMTS map subnet CSV file

Sample range file
The CSV file for map ranges closely resembles the file for map subnets. However, the XML file contains different fields, as shown in the sample map range XML file, below. <?xml version="1.0" encoding="UTF-8" ?> <MapDescription> <General> <Type>Range</Type> <Index id="0">Id</Index> </General> <Range> <Index id="1">FirstIP</Index> <Index id="2">LastIP</Index> </Range> </MapDescription> Where Id (Index ID 0) is the unique ID of the CMTS as specified in the CMTS CSV file.

Map import process
To import CMTS maps: 1. In the Configurations tree, select CMTS List, then click the arrow next to Import/Export on the toolbar and select Import CMTS Maps from CSV file. Or, in the Configurations tree, right-click CMTS List and select Import CMTS Maps from CSV file. The Import CMTS Maps dialog box appears.

110

Fairshare Installation & Configuration Guide: Release 5.60 Rev. C04
July 8, 2010 05-00095-C04

Import CMTS maps

Import CMTS Maps dialog box

2. Set the path for the CSV and XML files. 3. Click Import. The CMTS maps appear under the corresponding CMTS in the CMTS list. Next step: If your Fairshare system includes SPB data collection or PTS enforcement, see Chapter 6: “Configuring SPB connections” on page 113 Otherwise see Chapter 7: “Configuring additional network elements to the system” on page 123 for instructions on configuring third-party network elements to the system for use with non-Fairshare PCMM or Chapter 8: “SNMP” on page 131 for instructions on configuring the connection to the SNMP trap receiver.

Fairshare Installation & Configuration Guide: Release 5.60 Rev. C04
05-00095-C04 July 8, 2010

111

C04 July 8. 2010 05-00095-C04 .60 Rev.Chapter 5: Import CMTSs 112 Fairshare Installation & Configuration Guide: Release 5.

The following topics are included in this chapter: • “SPB configuration overview” on page 114 — explains the SPB and how it is used in the Fairshare system “IP exclusions” on page 117 — explains how to exclude MTA and CPE IPs relayed by SPBs during data collection from the Fairshare database “SPB configuration process” on page 119 — provides instructions for configuring the Sandvine SPB to the SDE 6 • • .Configuring SPB connections This chapter provides detailed instructions for configuring SPBs to the system. Instructions are provided for both configuring the SPB for subscriber data collection and for applying Fairshare actions by setting PTS attributes.

When data collection is through IPDR and Fairshare actions are applied through the PTS. After the SPBs are configured to the system. Each cluster connects to the SPB using the VIP configured for the edge service. two SPBs are configured to the system. but can be configured to many SPBs for Fairshare enforcement. and each cluster connects to only one SPB. However. • Two mappings are created. each SDE cluster’s edge service is mapped to an SPB for data collection and/or Fairshare enforcement. one for data collection (Collector Edge Services List) and one for Fairshare enforcement (Enforcement Edge Services List). The type of SDE deployment determines the manner in which edge services are mapped to the SPB to apply Fairshare actions using the PTS: • When data collection is through the SPB and Fairshare actions are applied through the PTS. C04 July 8. The SDE also uses a cluster’s edge VIP to connect to the SPB for PTS Fairshare enforcement. each cluster’s edge service is configured to one SPB for collection.Chapter 6: Configuring SPB connections SPB configuration overview The SDE can connect to the Subscriber Policy Broker (SPB) both to collect subscriber traffic data in order to make Fairshare decisions and to apply Fairshare actions by setting subscriber attributes in the PTS. 114 Fairshare Installation & Configuration Guide: Release 5. The attribute used to apply a Fairshare action is set only on the SPB containing the subscriber’s data. Each SPB collects data for two SDE clusters. Again. The following diagrams depict the different ways the SPB is connected for the two different uses. many edge services—and their clusters—can be mapped to the same SPB. In the first diagram. and each cluster sets PTS attributes through the same SPB. For subscriber data collection. 2010 05-00095-C04 . each edge service is mapped to only one SPB.60 Rev. Many edge services can be mapped to the same SPB. and only one SPB is configured to each service. many edge services can be mapped to the same SPB for data collection. each edge service is configured to the same SPB for both collection and enforcement.

2010 115 . Two SPBs are configured to the system. C04 05-00095-C04 July 8. but only the SPB containing the subscriber’s data acts on it. Fairshare Installation & Configuration Guide: Release 5.60 Rev. Request to set an attribute are sent to both SPBs. both are connected to all SDE clusters.SPB configuration overview 1 2 Cluster 1 Edg eS erv ice 1 3 4 Cluster 2 e Servic Edge 2 1 5 6 Cluster 3 E dge Serv ic e3 2 Edg eS er 4 v ic e 7 8 Cluster 4 SDE configured for SPB data collection with PTS enforcement The second diagram is for deployments that collect data using IPDR and apply Fairshare through the PTS.

2010 05-00095-C04 .60 Rev. C04 July 8.Chapter 6: Configuring SPB connections 1 2 Cluster 1 Ed ge Se r vi ce 1 3 4 Cluster 2 e2 Edge Servic ge Ed er S 3 ice erv 1 ce vi 1 Ed ge 6 Cluster 3 Edge Ser vice 3 Ed ge S er v 5 ic e eS Se Edg rv i ce 2 4 2 7 8 Cluster 4 e4 e rvic eS Edg SDE configured for SPBs used for PTS Fairshare enforcement only (IPDR collection) 116 Fairshare Installation & Configuration Guide: Release 5.

However. only the CM IP address is required because the Fairshare Engine applies Fairshare actions on this IP. The New IP dialog box appears. you must configure the IP exclusions in the SDE. This usually is when the SPB is first configured to the system or new ranges of MTA or CPE IP addresses are added to the subscriber network. Excluding individual IPs To exclude individual IPs from the active users: 1.60 Rev. The PTS collects subscriber data for each MAC address. Fairshare Installation & Configuration Guide: Release 5. CPE. and cable modem (CM) IP addresses. 2. This enables you to exclude MTA and CPE IP addresses—as well as any other IP addresses that should be excluded (for example. Each MAC address can contain multiple IPs: MTA. Right-click IP List and select Add New IP. Exclude IPs ranges and IPs through the IP Settings > IP Exclusions node of the EMS. 2010 117 . In the Configurations tree. New IP dialog box 3. transponder IPs)—from the subscriber data collected from the SPB and entered in the Fairshare database Active_Users table. MTA and CPE IPs addresses must be excluded before the SDE begins to collect data from the SPB for any IP range or MAC address. All non-MTA and non-CPE IPs that should be excluded from the Active_Users table also need to be excluded at this phase. C04 05-00095-C04 July 8.IP exclusions IP exclusions Before configuring SPBs to the system. open IP Settings > IP Exclusions. which the SPB sends to the SDE when Fairshare is configured for SPB data collection. Type in the IP address of the IP address you want to exclude.

Excluding subnets To exclude a subnet from the active users: 1. 5.60 Rev. 5. C04 July 8. 2010 05-00095-C04 . open IP Settings > IP Exclusions. Repeat steps 2-4 for each IP address you want to add to the list. Define the IP address and mask of the subnet you want to exclude. The New Subnet dialog box appears. In the Configurations tree. Click OK. New Subnet dialog box 3. 2. Repeat steps 2-4 for each subnet you want to add to the list. 4.Chapter 6: Configuring SPB connections 4. Click OK. Right-click Subnet List and select Add New Subnet. 118 Fairshare Installation & Configuration Guide: Release 5.

C04 05-00095-C04 July 8. type the IP address of the SPB being configured to the SDE. • Configuring the SPB to the SDE To configure the SPB: 1. The default database is ‘sv_stat’. New SPB dialog box 2. type the password used to log into the SPB database and Web service. Click OK. SPB user name and SPB Port. The SPB appears in the SPB list. 6. Fairshare actions. In the IP field. In the SPB Password field. 4.60 Rev. This is the name of the database in the SPB. the configuration process is as follows: • • Configure the SPB to the system. The mapping defines whether the SPBs will be used for data collection. See “Configuring the SPB to the SDE” on page 119. See SPB policies. 2010 119 . Define the database for storing the SBP data. For each SPB that will collect subscriber data. or both. In the Configurations tree. right-click SPB List and select Add SPB. 3. See “Mapping edge services to SPBs” on page 120. create SPB policies in order to define the active users in the Fairshare database. 5.The New SPB dialog box appears.SPB configuration process SPB configuration process For each SPB that will be used in the deployment. Type in the name of the SPB. Map the edge service configured for each SDE cluster to SPBs to define the SPB’s Fairshare roles. The defaults may be used for Database user name. 7. Fairshare Installation & Configuration Guide: Release 5.

C04 July 8.Chapter 6: Configuring SPB connections SPB parameters Table 19: SPB parameters Description Name of the SPB configured to the system IP address of the SPB User name for accessing the database through the Web service Password used to connect to the SPB database and Web service Port the SDE uses to communicate with the SPB Time zone in which the SPB is located GMT Attribute Name IP SPB user name Default Value SPB_1 -spbadmin SPB Password sandvine SPB Port SPB Time Zone 8081 Mapping edge services to SPBs To define how each SPB is used in the system. 120 Fairshare Installation & Configuration Guide: Release 5. designate the purpose of each edge service that will be used to communicate with the SPB by mapping it to the Collector Edge Services List and/or Enforcement Edge Services List located under each SPB node in the EMS. 2010 05-00095-C04 . This maps each SDE cluster to many SPBs for setting PTS attributes.60 Rev. you can map each edge service to only one SPB’s Collector Edge Services List. For enforcement purposes. you can map each edge service to as many SPBs as are configured in the system. SPB edge services lists While each list can contain many edge services. This is the edge service that the SDE cluster uses to collect data from the SPB.

From the drop-down list. To map more than one edge service to the SPB’s Enforcement Edge Services List. Next step: Proceed to Chapter 7: “Configuring additional network elements to the system” on page 123 for instructions on configuring third-party network elements for use with non-Fairshare PCMM or Chapter 8: “SNMP” on page 131 for instructions on configuring the connection to the SNMP trap receiver. 4. 2010 121 . To map edge services to the SPB for enforcement purposes. right click Enforcement Edge Services List.SPB configuration process To map edge services to SPBs: 1. To map an edge service to the SPB for collection purposes right click Collector Edge Services List. In the EMS Configurations tree > SPB List. The New Edge Service dialog box appears. New Edge Service dialog box 3. select the edge service you want to map to the SPB. C04 05-00095-C04 July 8. open the SPB to which you want to map the edge service.60 Rev. repeat steps 2-3. Next. 2. select Add Edge Service from the menu. Fairshare Installation & Configuration Guide: Release 5.

C04 July 8.Chapter 6: Configuring SPB connections 122 Fairshare Installation & Configuration Guide: Release 5.60 Rev. 2010 05-00095-C04 .

Configuring additional network elements to the system
This chapter provides detailed instructions for configuring the additional third-party network elements that can optionally connect to the SDE system when the SDE policy server is used. The following topics are included in this chapter: • “Application managers” on page 124 — provides step-by-step instructions for configuring external application managers to the SDE “Application servers” on page 126 — provides step-by-step instructions for configuring application servers to the SDE “Record Keeping Servers (RKSs)” on page 127 — provides step-by-step instructions for optionally configuring RKSs to the SDE

7

Chapter 7: Configuring additional network elements to the system

Application managers
Note: For use when the SDE policy server is deployed for end-to-end QoS. Application managers are devices that interface to PCMM policy servers using PCMM COPS to request QoS-based service for applications on behalf of an end user or network management system. These include PCMM-compliant session border controllers and softswitches. The SDE accepts gates only from third-party AMs configured to the system. This provides an added level of security. Each AM is linked to a border service and assigned a VIP during configuration. The border service supports the COPS connection from the AM, and the SDE listens to the AM using the specified VIP. To configure an application manager: 1. In the Configurations tree, right-click AM List; then select Add Application Manager. The New AM dialog box appears.

New AM dialog box

2. Define the AM’s ID, as defined by PCMM. 3. Define the AM’s IP address or FQDN. 4. Define the service to which it is connected and the listening VIP. All other attributes are optional. The operator may optionally disable or re-enable the AM. When an AM is disabled, it is as if it is not defined in the system. The SDE does not accept any gate commands from the AM; nor will it send any alarms on the component.

124

Fairshare Installation & Configuration Guide: Release 5.60 Rev. C04
July 8, 2010 05-00095-C04

Application managers

5. The Label value defines the name of the AM as it appears in the AM List. 6. Click OK. The AM appears in the AM List.

Application manager parameters
Table 20: AM attributes Description
Determines whether the AM is enabled. When an AM is disabled, it is as if it is not defined in the system. The SDE does not accept any gate commands from the AM, nor will it send any alarms on the component. Identity of the AM as defined by PCMM (included in all COPS messages) AM label IP address or FQDN of the AM The specific service to which the AMs connects The VIP the selected service uses to listen to the AM AM Vendor

Attribute
Enabled/Disabled

Default Value
Enabled

AMID*

--

Label IP or FQDN* Service* Listening VIP*

AM_1 localhost Border Service --

Vendor

none

Fairshare Installation & Configuration Guide: Release 5.60 Rev. C04
05-00095-C04 July 8, 2010

125

If AS doesn’t send contect ID. then select Add Application Server. In the Configurations tree. as defined in system AS: AS generates its own ID (used for stateless application server) WSAM: WSAM generates the context ID Both: WSAM searches for context ID. 3. but context ID not found. The New AS dialog box appears. WSAM creates new session with new ID Attributes AS Username Default Value AS_1 Generate ContextId Both 126 Fairshare Installation & Configuration Guide: Release 5. If AS sends context ID.Chapter 7: Configuring additional network elements to the system Application servers Note: For use when the SDE policy server is deployed for end-to-end QoS. WSAM creates a new session with given ID. right-click Application Servers. Define the application server’s user name. Click OK. The AS appears in the Application Servers list. 2010 05-00095-C04 .60 Rev. To configure an application server: 1. New AS dialog box 2. C04 July 8. Application server parameters Table 21: Application server attributes Description Application server’s user name.

60 Rev. Optionally redefine the RKS’s attributes according to the RKS Values table. The RKS appears in the RKS Servers list. Click OK. 2010 127 . 4. right-click RKS Servers and select Add RKS. Fairshare Installation & Configuration Guide: Release 5. Right-click the RKS. but the same RKS also may be used for many CMTSs.Record Keeping Servers (RKSs) Record Keeping Servers (RKSs) Note: For use when the SDE policy server is deployed for end-to-end QoS. New RKS dialog box 2. then select Add Primary/Secondary RKS. C04 05-00095-C04 July 8. 3. The New RKS dialog box appears. The New Primary/ Secondary RKS dialog box appears. In the Configurations tree. You can define up to two RKSs (primary and secondary) for each CMTS. To configure an RKS: 1. Use of the RKS is optional. The Record Keeping Server (RKS) stores event messages generated by the CMTS and SDE regarding volume-based and time-based usage information.

To create a secondary RKS. No: non-default CMTS Yes: default CMTS. 2010 05-00095-C04 . Number of times the PS retries to send an Event Message to the RKS in case of an error. Define the RKS’s IP or FQDN.60 Rev. Waiting time in ms between retries when sending an Event Message. repeat steps 4-6 above. The Port parameter is optional. continue on to Chapter 8: “SNMP” on page 131 to optionally configure the SNMP trap. 6. Next step: After configuring the RKSs to the system. 7. C04 July 8.Chapter 7: Configuring additional network elements to the system New Primary RKS dialog box 5. RKS parameters Table 22: RKS values Desciption RKS label Vendor of the RKS RKS to which event messages are routed if the CMTS isn’t linked to an RKS. Click OK. Attributes Label Vendor Default Default RKS_1 none No Retry Number 3 Retry Time Interval (ms) 500 128 Fairshare Installation & Configuration Guide: Release 5. It is recommended that you also define the Shared Secret.

Record Keeping Servers (RKSs) Table 23: RKS primary/secondary parameters Description IP address or FQDN of the RKS RADIUS accounting port RADIUS authentication secret (recommended) Attribute IP or FQDN* Port Shared Secret Default Value localhost 1813 0000000000000000 (0 x 16) Note: Parameters in the above table marked with with an ‘*’ require configuration.60 Rev. C04 05-00095-C04 July 8. Fairshare Installation & Configuration Guide: Release 5. 2010 129 .

Chapter 7: Configuring additional network elements to the system 130 Fairshare Installation & Configuration Guide: Release 5.60 Rev. 2010 05-00095-C04 . C04 July 8.

The following topics are included in this chapter: • • .SNMP 8 “SNMP agent” on page 132 — explains the SDE SNMP agent and how to change its community “Configuring trap receivers” on page 133 — explains how to configure the SDE to send alarm notifications to an external trap receiver This chapter explains the SNMP agent and how to optionally configure the trap receivers so that external NOCs can receive SDE alarms.

You can change the SDE’s RO and RW communities through the SDE general parameters in the EMS. using the SDE SNMP agent. the SDE SNMP agent forwards alarm information to external NOCs using different interfaces.Chapter 8: SNMP SNMP agent The SDE system provides SDE-specific fault notifications via SNMP. The structure and parameters in each message depend on the type of notification message sent.s 132 Fairshare Installation & Configuration Guide: Release 5. C04 July 8. The read-write community is ‘svPrivate’. When trap receivers are configured to the system. 2010 05-00095-C04 . such as notification that a network element is disconnected. The SNMP community for retrieving information is ‘svPublic’. The SDE supports SNMP v2c.60 Rev.

open SNMP.Configuring trap receivers Configuring trap receivers The SNMP alarm notification system can send alarms to external trap receivers. In the Configurations tree. SNMP parameters Table 24: SNMP parameters Description Identifying name of the trap receiver IP of the machine receiving the traps generated by the SDE SNMP community Version of SNMP being used Attribute Label IP Default Value TrapReceiver1 -- Community SNMP Version public 2c Fairshare Installation & Configuration Guide: Release 5. 2010 133 . Click OK. 2. The New Trap Receiver dialog box appears.60 Rev. 4. Define the values for the trap receiver. The trap receiver appears in the Trap Receivers list. For a trap receiver to receive these alarm notifications. Right-click Trap Receivers. then select Add Trap Receiver. you must configure it in the SDE. To configure the trap receiver: 1. New Trap Receiver dialog box 3. C04 05-00095-C04 July 8.

C04 July 8. 2010 05-00095-C04 . 134 Fairshare Installation & Configuration Guide: Release 5.60 Rev.Chapter 8: SNMP Next step: After configuring trap receivers. continue on to Chapter 9: “Reports” on page 135 to configure the system for stability monitoring reports.

which enables operators to monitor the performance of each SDE machine. The following topics are included in this chapter: • • .Reports 9 “Reports overview” on page 136 — describes the types and frequency of reports the SDE generates “Configuring SDE nodes for reports” on page 137 — explains how to configure the nodes to create reports This chapter explains the SDE stability monitoring function.

136 Fairshare Installation & Configuration Guide: Release 5. 2010 05-00095-C04 . C04 July 8.Chapter 9: Reports Reports overview The Reports option enables operators to view each SDE node's stability. CPU and hard drive usage. broken out by data type. The SDE creates two types of reports: • • Report log Graphs in JPEG format. and creates daily. that enhance the operator's understanding of the system's behavior: • • • • • Gate and session traffic for each system node PS process CPU and memory activity (internal PS only) PS gate and memory consumption in KB (internal PS only) WSAM CPU and memory activity WSAM session and memory consumption in KB System reports are generated each day at exactly 23:50.60 Rev. The SDE stability monitoring function collects data on system memory. and monthly status reports in the form of logs and graphs. weekly. and availability in real time through the EMS when Fairshare is applied using PCMM. as well as on gate and session traffic on the SDE node. The monthly reports are generated at 23:50 on the last day of each month and are a summary of system performance for the month. Weekly reports are generated each Saturday night at 23:50 and are a summary of system performance for the week. reliability.

Click OK. you may need to perform additional configurations on the network elements connected to the system. right-click Reports and select Add SDE Report View. To configure a node for reports: 1. C04 05-00095-C04 July 8. For information on configuring the Fairshare application within the SDE.Configuring SDE nodes for reports Configuring SDE nodes for reports Prior to viewing reports in the EMS. However. see Appendix B: “External configuration procedures” on page 153. Select the node you want to monitor. The Add SDE Report View dialog box appears. Add SDE Report View dialog box 2. you must configure each SDE node in the system for reports. Mission accomplished: The SDE system is now fully installed and configured. For instructions regarding how to configure these external elements for the SDE. In the Configurations tree. 2010 137 . see the SDE Fairshare Solution Guide. Fairshare Installation & Configuration Guide: Release 5. 3.60 Rev.

Chapter 9: Reports 138 Fairshare Installation & Configuration Guide: Release 5. 2010 05-00095-C04 . C04 July 8.60 Rev.

which enables operators to view NetReports from all sites in a multi-site deployment from one central location.NetPortal 10 “NetPortal overview” on page 140 — describes the NetPortal “NetPortal installation” on page 141 — explains how to install and configure the SDE software on the NetPortal machines “Configuring the NetPortal services” on page 142 — gives instructions for configuring the NetPortal’s management and edge services This chapter provides detailed instructions for installing the NetPortal. The following topics are included in this chapter: • • • .

configured in active-standby mode to allow for failover. The NetPortal connects to the CMTSs or clusters within a site using the cluster’s edge VIP in order to access NetReports. for a specific CMTS or for a specific MAC address. C04 July 8.60 Rev. It consists of two SDE machines located in a national data center (NDC). You can view NetReports by cluster within a specific site. 2010 05-00095-C04 . Support Site Rsync/ FTP Internet National Data Center (NDC) Centralized package update server SDE NetPortal HTTP HTTP HTTP HTTP HTTP HTTP Site Site SDE Fairshare Cluster#3 SDE Fairshare Cluster#1 SDE Fairshare Cluster#2 CMTS CMTS CMTS CMTS CMTS CMTS CMTS CMTS CMTS CMTS CMTS CMTS NetPortal architecture 140 Fairshare Installation & Configuration Guide: Release 5.Chapter 10: NetPortal NetPortal overview The NetPortal provides a central location for accessing NetReports from all sites in a deployment. The reports are exactly the same as those accessed using the NetReport application within the data center.

C04 05-00095-C04 July 8.sh /opt/TOMCAT/bin/startup. Set the portal property to ‘true’: central. To install the SDE software on each NetPortal machine: 1. The SDE Fairshare software is installed on each NetPortal machine. “Installation troubleshooting” on page 44. 2010 141 .properties file for editing: vi /opt/TOMCAT/webapps/NetReport/WEB-INF/classes/ conf. The edge VIP is used to communicate with the SDE sites and for replication within the NetPortal cluster to ensure high availability. beginning with Chapter 2: “Installing the management cluster” on page 29.60 Rev. including all installation verifications and concluding with the troubleshooting steps.NetPortal installation NetPortal installation The NetPortal installation process closely resembles the installation process for installing SDE clusters within a site. Configure both SDE machines in the NetPortal cluster to run as a NetPortal: a. 3. Stop and start the Tomcat server: /opt/TOMCAT/bin/shutdown.properties b. open the /opt/TOMCAT/webapps/NetReport/WEBINF/classes/conf. but the machine is set for NetPortal use. 2. Follow the instructions for installing the SDE software on a machine. On the SDE machines.db=false portal=true c. Both a management and edge VIP are configured for the NetPortal cluster.db=false local. Save the file.sh Fairshare Installation & Configuration Guide: Release 5.

60 Rev. connect to the SDE EMS and configure the management and edge services. See “Assigning the management VIP” on page 50. C04 July 8. Attach the edge VIP to both nodes for high availability. the NetPortal will use this VIP to communicate with the SDE sites and to replicate the MySQL database between the two nodes. Edge service To configure the edge service: 1.Chapter 10: NetPortal Configuring the NetPortal services To configure the NetPortal services. Assign the management service a VIP. See “Attaching services to the new node” on page 61. 2. 142 Fairshare Installation & Configuration Guide: Release 5. Management service To configure the management service: 1. Assign the edge service a VIP. Attach the management VIP to both nodes for high availability. See “Configuring the edge VIP” on page 51. In addition to edge functionality. 2010 05-00095-C04 . See “Attaching services to the new node” on page 61. 2.

SDE upgrade This chapter provides instructions for upgrading the SDE to the current SDE release. The following topics are included in this chapter: • “Upgrade process” on page 144 — explains the SDE upgrade process 11 .

The following result should appear: Do you want to preserve your current iptables settings [yes/ no] If you want to save the current iptables settings (firewall rules). To upgrade the SDE: 1. 2010 05-00095-C04 .Chapter 11: SDE upgrade Upgrade process SDE upgrade enables services providers to upgrade the SDE software from a central location. RHN support will be disabled. The upgrade process also updates the database and system configurations to the new version. If you are using the yum repository.d) enter [yes] else if you want to use a local directory enter [no] 3. The following should appear: iptables 0:off 1:off 2:on 3:on 4:on 6:off Flushing firewall rules: [ OK ] Setting chains to policy ACCEPT: nat mangle filter [ OK ] Unloading iptables modules: [ OK ] Applying iptables firewall rules: [ OK ] Loading additional iptables modules: ip_conntrack_netbios_n[ OK ] This system is not registered with RHN. then type Enter.60 Rev. if you want to use the default yum repository (/etc/yum.noarch where <INSTALL_PATH> is the path for the yum repository 2. enter ‘yes’. C04 July 8. The following result should appear: Enter the path of the local repository Enter the path of the Yum local repository. 4. enter ‘yes’. 5:on ************************************************************* **** Check if this node is the management node *** ************************************************************* ************************************************************* 144 Fairshare Installation & Configuration Guide: Release 5. Run the upgrade script by running the following command: sde_upgrade The following result should appear: To update the components.repo –y upgrade SDE_Upgrade. enter ‘no’.repos. run the following command: yum -c <INSTALL_PATH>/sv. If you are not using the yum repository. On the SDE management machine.

Fairshare Installation & Configuration Guide: Release 5. A detailed upgrade log is located at: /opt/install/svUpgrade_mm_dd_yyyy_hh_mm.sh fs_admin 3. 6. install the most recent release of the SDE EMS on the remote machine. If you are not using the administrative group ‘sv_admin’ to receive EMS administrator access.sh <GROUP_NAME> Where <GROUP_NAME> is the group name of the administrator.log. repeat steps 1-4 above on all other SDE machines while the management machine is running the upgrade.log. it is recommended that you also perform the following upgrade verifications: 1. When the upgrade is finished on every machine. if you are using the Windows EMS to manage and monitor to the system. See “Windows EMS installation” on page 46. If you are upgrading from a previous SDE stream (e.Upgrade process **** You are in the Management Master node . On every SDE node. the following notification appears on the management machine when the upgrade is complete: ************************************************************* **** Finish to Upgrade all the System *** ************************************************************* You can verify on each machine that the upgrade was performed properly. C04 05-00095-C04 July 8. perform the installation verification procedures described in “Installation verifications” on page 41. if the system is being upgraded to a new SDE stream the following notification appears on all non-management machines: ************************************************************* **** This is not the Master management node then exit *** ************************************************************* For all upgrade types. Post-upgrade procedures Following completion of the upgrade process. run the following command on every SDE node: /opt/SDE/cmd/setSDEGroupAdmin. After performing the installation verifications. 2010 145 . starting Upgrade *** ************************************************************* 5. For example: /opt/SDE/cmd/setSDEGroupAdmin. A log of the database upgrade is located at: /opt/SDE/logs/svUpgrade_db. check the firewall rules: service iptables status 2.60 Rev.40 to SDE 5.60). A log of the upgrade is located at: /opt/install/sde_install_mm_dd_yyyy_hh_min..g. After the upgrade process is complete. SDE 5.log.

2010 05-00095-C04 . C04 July 8.Chapter 11: SDE upgrade If you are using the Web EMS.60 Rev. 146 Fairshare Installation & Configuration Guide: Release 5. clean the cache of the Internet browser prior to connecting to the SDE.

and for version checks Appendix B: “External configuration procedures” on page 153 — explains the external configuration procedures required on the thirdparty network elements to set up the end-to-end system Appendix C: “Manually configuring CMTSs” on page 155 — provides instructions for configuring CMTSs to the system using the EMS GUI or command line interface Appendix D: “Example XML description files for CMTS import” on page 171 — provides examples of XML description files for importing CMTSs • • • .Appendices This section contains the following appendices: • Appendix A: “Additional install procedures” on page 149 — provides instructions for configuring SSL between the EMS and SDE.

60 Rev.Section 1: Appendices • • Appendix E: “Uninstalling the SDE” on page 177 — provides the procedure for uninstalling the SDE software and packages Appendix F: “SDE ports” on page 179 — provides a table of ports used for communications between the SDE and the different system elements 148 Fairshare Installation & Configuration Guide: Release 5. C04 July 8. 2010 05-00095-C04 .

Additional install procedures This appendix describes additional installation procedures that may be required. The following topics are included in this appendix: • “Configuring SSL between EMS and SDE” on page 150 — provides instructions for configuring SSL between the EMS and SDE “Changing the location of the log files” on page 151 — explains how to move the SDE logs to a different partition on the machine “Transferring files to the SDE machine” on page 152 — explains how to transfer files from the client to the SDE machine using secure FTP or SCP A • • .

agent.properties Change the following line: com.cmx.cmx.Appendix A: Additional install procedures Configuring SSL between EMS and SDE The default protocol used for configuration between the EMS and the SDE system is RMI. This can be changed to RMI over SSL (with encryption) by editing the following file in the SDE: /opt/SDE/SDE_Agent/config/agent_conf.agent.security.60 Rev.use_ssl=false to: com.use_ssl=true 150 Fairshare Installation & Configuration Guide: Release 5. C04 July 8.security.odsp. 2010 05-00095-C04 .odsp.

60 Rev. However. 2010 151 . C04 05-00095-C04 July 8. you can optionally move logs to any other location on the machine. To change the location of the log files: 1. run the following command: service sde stop 2. Create a symlink from /opt/SDE/logs to /var/log/SDE/ by entering the following: ln -s /var/log/SDE logs /opt/SDE/logs 4. The following instructions use the example of changing the log location to /var/log/ SDE. Start the SDE: service sde start Fairshare Installation & Configuration Guide: Release 5.Changing the location of the log files Changing the location of the log files The SDE logs are located by default at /opt/SDE/logs. Move the /opt/SDE/logs folder to /var/log/SDE by entering the following: mv /opt/SDE/logs /var/log/SDE 3. On the SDE machine.

Synopsis: scp [-aAqQprvBCL] [-S path-to-ssh] [-o ssh-options] [-P port] [-c cipher] [-i identity][[user@]host1:]filename1.Appendix A: Additional install procedures Transferring files to the SDE machine Files may be transferred from the client to the SDE machine using secure FTP (FTP over SSH) or the SCP program. Copies between two remote hosts are permitted. Synopsis: sftp [-vC1] [-b batchfile] [-o ssh_option] [-s subsystem | sftp_server] [-B buffer_size] [-F ssh_config] [-P sftp_server path] [-R num_requests] [-S program] host sftp [[user@]host[:file [file]]] sftp [[user@]host[:dir[/]]] Example: sftp user@example. SFTP program SFTP (secure file transfer program) is an interactive file transfer program..com SCP program Any file name may contain a host and user specification to indicate that the file is to be copied to/from that host. C04 July 8. [[user@]host2:]filename2 Example: scp SourceFile user@host:directory/TargetFile scp user@host:folder/SourceFile TargetFile 152 Fairshare Installation & Configuration Guide: Release 5. similar to FTP.60 Rev. It connects and logs into the specified host and then enters an interactive command mode. 2010 05-00095-C04 . that performs all operations over an encrypted SSH transport. SFTP may use many features of SSH.. This section contains an example use of each of the two tools. such as public key authentication and compression.

External configuration procedures This appendix describes the configuration procedures required on external network devices so that they can work in conjunction with the SDE. For detailed instructions. refer to the specific device’s product documentation. The following topics are included in this appendix: • “Application Servers” on page 154 — gives instructions for configuring application servers to connect to the SDE B . refer to the specific device’s product documentation. For detailed instructions.

C04 July 8. 2010 05-00095-C04 . configure the virtual IP of the designated SDE border service in the AS.60 Rev. 154 Fairshare Installation & Configuration Guide: Release 5. configure application servers to send requests to the WSAM. To do so. Note: The application servers must also be configured in the SDE in order for the WSAM to communicate with them.Appendix B: External configuration procedures Application Servers Following installation and configuration of the SDE.

The SDE allows you to configure a CMTS to the system through the EMS GUI or using the EMS command line interface (EMS CLI). The following topics are included in this appendix: • “Configuring CMTSs through the EMS” on page 156 — provides step-by-step instructions for configuring CMTSs to the SDE “Manually configuring CMTS interfaces and maps” on page 164 — explains how to manually configure CMTS interfaces and maps to the system “Configuring CMTSs through the CLI” on page 166 — explains how to configure CMTSs through the CLI C • • .Manually configuring CMTSs This appendix describes the different methods of manually configuring individual CMTSs to the system.

3. The SDE does not try to connect to the CMTS. specify the IPDR Record IP if the IP address sent by the CMTS in the IPDR record’s CMTSipAddress field differs from the CMTS IP. 2010 05-00095-C04 . Define the CMTS’s IP address or FQDN. in the SNMP IP field configure the SNMP IP to which the SDE connects to collect the data. and the connecting VIP. If the CMTS uses IPDR/SP to send IPDR data to the SDE. 8. then select Add CMTS. When a CMTS is disabled. 7. 4.60 Rev. If a different IP address is configured on the CMTS for the SNMP relay. right-click CMTS List. 6. New CMTS dialog box 2. it is as if it is not defined in the system. Optionally define the CMTS vendor in the Vendor field. In the Configurations tree. Define the edge service to which the CMTS is connected (Service field). The New CMTS dialog box appears. In the Enabled/Disabled field. nor will it send any alarms on the component. The vendor can be used for CMTS identification purposes when using the EMS CLI.Appendix C: Manually configuring CMTSs Configuring CMTSs through the EMS To configure a CMTS to the system through the EMS: 1. Define the CMTS’s label. C04 July 8. If the SDE connects to the SPB for data collections and/or Fairshare enforcement. you can optionally disable the CMTS. the address format must match the format (IP or FQDN) used to define CMTSs in the SPB. If the CMTS sends IPDR data using using file mode. The Label value defines the name of the CMTS as it appears in the CMTS List. configure the IPDR IP if the IP address the SDE uses for IPDR/SP communications differs from the CMTS IP. 5. 156 Fairshare Installation & Configuration Guide: Release 5.

13. Otherwise. If the wrong community is defined for this CMTS. If the CMTS’s SNMP community differs from that defined for the system in the SDE general parameters.60 Rev. If the CMTS uses a different DOCSIS version. The SNMP Collection and Data Collection fields enable you to determine the type of information received from a CMTS. configure the DOCSIS version as 2.0. Caution: When the SDE uses a third-party policy server or only uses the PTS to apply Fairshare actions. C04 05-00095-C04 July 8. you Must specify the correct version in the DOCSIS Version field. If you want the IPDR collector to write all records from this CMTS to file on the SDE. By default. If Fairshare actions will be applied using the SDE policy server. if the SDE only collects IPDR and/or SNMP data from the CMTS (the SDE applies Fairshare actions through an external PS or the PTS) . respectively. above which an interface on the CMTS is considered to be congested. define the SNMP community for this CMTS in the SNMP Community field. Other fields are not applicable when the policy server is disabled (the Disable COPS field is set to ‘Yes’). 14. The Upstream ifSpeed default and Downstream ifSpeed default fields define values used for the interface ifSpeed in cases where the IPDR collector receives a record for a flow on an interface that has not been configured in the EMS or has not yet been received using SNMP. If the policy server is used. even if the CMTS supports DOCSIS 3. 2010 157 . select ‘Yes’. 10. It overrides the global threshold values defined in the Fairshare parameters. 12. the SDE receives both IPDR and SNMP data from a CMTS.0. or Data Collection parameter to ‘No’ to disable IPDR collection so that no data of that type is received from the CMTS. optionally configure all other attributes. The Cmts Upstream Congestion and CMTS Downstream Congestion fields define the precentage of upstream and downstream bandwidth. 11. Note: To enable IPDR logging on the CMTS. set this value to ‘No’. This percentage can be used to define conditions for triggering Fairshare actions on users on the specific CMTS. If the CMTS will send SAMIS IPDR data (as opposed to SAMIS-TYPE-1) . If SNMP is disabled in the Data Collection > General parameters (Interface Definitions Source and Interface Bandwidth Source). the Enable File Logging parameter also must be set to ‘yes’ in the Data Collection > IPDR Collection parameters. Defaults may be use Fairshare Installation & Configuration Guide: Release 5. In the Disable COPS field. set the Enable File Logging parameter to ‘yes’. 17.Configuring CMTSs through the EMS 9. 16.0. the CMTS will be displayed as being disconnected in the Status > CMTS node. 15. The default DOCSIS version of the CMTS is 3. you also need to set the SNMP Collection value to ‘No’. The AllSubnets value determines whether the discovery process discovers all CMTS subnets. the Disable COPS field MUST be set to ‘Yes’. its data collection won’t work. Set the SNMP Collection parameter to ‘No’ to disable SNMP data collection.

Appendix C: Manually configuring CMTSs 18. The CMTS appears in the CMTS Tree in the EMS right pane. If the SDE connects to the SPB for data collections and/ or Fairshare enforcement. or if SNMP is disabled (the IPDR Collector Interface Definitions Source parameter is configured to ‘By Configuration’). Caution: If the SNMP community defined in the SDE differs from the community defined in the CMTS. CMTS parameters The following table explains all possible parameters used in the New CMTS dialog box for manually configuring CMTSs to the system through the EMS. Click OK. If the IPDR IP is empty. if different than the CMTS IP. It also doesn’t receive any IPDR data. When a CMTS is disabled. this is the IP value contained in initiatorId field of the CONNECT message. see “Configuring IPDR sessions” on page 162.60 Rev. the value of the CMTS IP is used. Configure the IPDR sessions for the CMTS. the IP address the SDE uses to connect to the CMTS to receive IPDR data. If the CMTS or external relay initiates the connection. Define the CMTS interfaces and subscriber maps: Right-click the CMTS and select Map Discovery. 20. 2010 05-00095-C04 . The interface and map information are imported from the CMTS. the format must match the format (IP or FQDN) used to define CMTSs in the SPB. C04 July 8. Note: You can optionally disable or re-enable the CMTS. The SDE does not try to connect to the CMTS or send any alarms on the component. Attribute Enabled/Disabled Default Value Enabled Label IP or FQDN* CMTS_1 -- IPDR IP -- 158 Fairshare Installation & Configuration Guide: Release 5. it is as if it is not defined in the system. Map Discovery won’t work. Table 25: CMTS EMS parameters Description Determines whether the CMTS is enabled CMTS name Physical IP address or FQDN of the CMTS. When the SDE initiates the IPDR/ SP connection. 19. This determines the flow of the IPDR data. For instructions.

as defined in the EMS Edge VIP that the selected service uses to connect to the CMTS Minimum delay on the cable modem. Used only with the SDE policy server CMTS vendor: Cisco. BigBand. if different from the IP address defined for the CMTS. Relay (used for third-party IPDR collectors) Keep Alive Timeout in ms between the CMTS and PS. CMTS COPS port number. either. 2010 159 . Optional parameter used only with the SDE policy server Name of the edge service connected to the CMTS. Used only with the SDE policy server -- Default Value IPDR Record IP -- Port 3918 Vendor -- KA Timeout (sec) -- RKS none Service * Edge Service Connecting VIP * -- Upstream Delay (ms) 30 Fairshare Installation & Configuration Guide: Release 5. Motorola. Arris. if different from the IP address defined above for the CMTS. Use this IP when the CMTS or external relay sends IPDR data to the SDE using file mode. If no IPDR IP is configured. Used for all deployment types The IP address sent by the CMTS in the IPDR record’s CMTSipAddress field. C04 05-00095-C04 July 8.60 Rev.Configuring CMTSs through the EMS Attribute SNMP IP Description The IP address the SDE uses to connect to the CMTS to receive SNMP data. the SDE uses the CMTS IP for the IPDR data. the SDE by default uses the IPDR IP. Used only with the SDE policy server The RKS linked to this CMTS. If the IPDR Record IP is not configured. Optimize the value (30s) according to the CMTS’s status.

Appendix C: Manually configuring CMTSs Attribute Downstream Delay (ms) Description Minimum delay on the CMTS downstream. Yes: The SDE only collects IPDR and/or SNMP data from the CMTS. The SNMP community used for CMTS Discovery on this CMTS Determines whether the discovery process discovers all CMTSs subnets. no delay. 2010 05-00095-C04 . Yes: SDE collects SNMP data from the CMTS. Accuracy is ± 5 ms. No: The SDE collects IPDR and/or SNMP data from the CMTS and sends policies to the CMTS.60 Rev. C04 July 8. Used only with the SDE policy server Determines whether the SDE connects to the CMTS as a policy server. Optional parameter used only with the SDE policy server No: Discovers only those subnets belonging to a DOCSIS MAC layer Yes: Discovers all subnets Determines whether the SDE collects SNMP data from the specific CMTS. This parameter is used only when the SDE is set to SNMP collection (the default) in the L2 Topology parameters. Min delay range = 20 ms to 2^31-1. 200 Default Value Min Delay Between Gate Commands (ms) 0 Disable COPS No SNMP Community* Default AllSubnets No SNMP Collection* Yes 160 Fairshare Installation & Configuration Guide: Release 5. Used only with the SDE policy server Time interval in ms that the SDE waits before forwarding the next gate command: 0 = disables the rate limit feature. Change to ‘Yes’ for deployments using an external policy server or only the PTS to apply Fairshare actions.

DOCSIS 2.1.60 Rev. Yes: SDE collects IPDR data from the CMTS or SPB statistics. No: The CMTS only sends COPS messages and SNMP data Percentage of the upstream bandwidth above which an interface on a CMTS is considered congested. The default may be used. When using the outbound IPDR relay function.) Default Value Data collection* Determines whether the SDE collects IPDR or SPB data. This parameter is used for IPDR data collection. The default may be used. 2010 161 . If the CMTS will send SAMIS data to the SDE.Configuring CMTSs through the EMS Attribute Description No: SDE doesn't collect SNMP data. Yes = writes to file No = doesn’t write to file Yes Cmts Upstream Congestion (percentage) 80 Cmts Downstream Congestion (percentage) 80 Upstream ifSpeed default 10240000 Downstream ifSpeed default 42884296 Docsis Version* DOCSIS 3 Enable File Logging No Fairshare Installation & Configuration Guide: Release 5. even if the CMTS is DOCSIS 3. Enables the IPDR collector to write the CMTS’s IPDR records to file.0. this parameter must be set to ‘Yes’. C04 05-00095-C04 July 8. or DOCSIS 1. (Use this setting when setting up the relay from thirdparty IPDR collectors. select ‘DOCSIS 2’. Default ifSpeed assigned to any unrecognized CMTS upstream interface in an IPDR record Default ifSpeed assigned to any unrecognized CMTS downstream interface an the IPDR record DOCSIS version supported by the CMTS: DOCSIS 3. Percentage of the downstream bandwidth above which an interface on a CMTS is considered congested.

When the CMTS supports SAMIS-TYPE-1. The session appears in the IPDR Sessions list. C04 July 8. To configure the CMTS’s IPDR sessions: 1.Appendix C: Manually configuring CMTSs Note: Parameters in the above table marked with an ‘*’ require configuration.60 Rev. Configure the session ID. SAMIS. The New IPDR Session dialog box appears. IPDR session parameters Table 26: IPDR session parameters Description Optional name assigned to the IPDR session type for identification purposes Parameter IPDR Session Name Default Value IPDR_Session_1 162 Fairshare Installation & Configuration Guide: Release 5. When SAMIS is used. 3. Define the session type (SAMIS-TYPE-1. and then right-click IPDR Sessions and select Add IPDR Session. 5. 4. only the SAMIS IPDR session is configured. Open the CMTS to which you are adding the session. or CPE-TYPE). Click OK. Configuring IPDR sessions IPDR sessions enable service providers to configure the SDE to support the SAMIS and flow type of the IPDR data according to the CMTS’s configurations. you canconfigure two IPDR sessions: one for SAMIS-TYPE-1 and one for CPE-TYPE. 2010 05-00095-C04 . Optionally assign the session a name for identification purposes. connection initiator and session type according to the configurations on the CMTS. New IPDR Session dialog box 2.

If the CMTS is the initiator.Configuring CMTSs through the EMS Parameter IPDR Docsis Type Description Defines the type of data sent to the SDE: SAMIS-TYPE-1. 2010 163 . Time Interval Port 4737 Fairshare Installation & Configuration Guide: Release 5. it connects to this port on the CMTS. according to the CMTS’s configuration: CMTS: the IPDR waits for the CMTS to initiate sessions. Event: An event serves as the trigger for the CMTS to send the data. If the SDE is the initiator. Ad Hoc: The SDE closes the IPDR/SP connection when it is finished receiving data. SAMIS. C04 05-00095-C04 July 8. the SDE listens to this port.60 Rev. Default Value -- IPDR Session Id 1 Connection Initiator SDE IPDR Session Type Determines the type of IPDR flow. or CPE-TYPE Unique ID that must match the IPDR Session ID configured on the CMTS Defines whether the SDE or CMTS initiates the IPDR sessions. (Used when the SDE initiates the connection) Number of the port to which the IPDR/SP connection initiator should connect. according to the CMTS’s configuration: Time Interval: The CMTS sends IPDR data at intervals. SDE: the SDE initiates the connection.

Repeat for each range or subnet on the CMTS. 3. instead of importing them from directly from the CMTS using SNMP. Define the range for the CMTS. New Subnet dialog box 2. or define the net and mask. Manually configuring CMTS interfaces and maps The SDE allows you to manually configure CMTS interfaces and maps. right-click Maps. 2010 05-00095-C04 . In the Configurations tree. The New Subnet/Range dialog box appears. you must configure the IP exclusions for MTA and CPE IP addresses prior to adding new subnets or ranges for a CMTS. Click OK. To manually configure the maps: 1. instead of importing them from directly from the CMTS using SNMP.Appendix C: Manually configuring CMTSs Manually configuring CMTS interfaces and maps The SDE allows you to manually configure CMTS interfaces and maps. Configuring CMTS maps Caution: When the SDE collects subscriber data from the SPB. 164 Fairshare Installation & Configuration Guide: Release 5. C04 July 8.60 Rev. Select the interface. open the node for the CMTS you are configuring. and select Add Range or Add Subnet. For information regarding IP exclusions. 4. see “IP exclusions” on page 117.

Manually configuring CMTS interfaces and maps CMTS interface and map parameters Table 27: CMTS interfaces and maps Description Adds Interface Name of the interface.0 Add Subnet Net Mask -0.1 0. as defined in the CMTS. as defined in the CMTS Interface’s CM capacity. C04 05-00095-C04 July 8.60 Rev.0.255.0 255.0. Adds map to the CMTS Adds map range to CMTS First IP address in CMTS map range Last IP address in CMTS map range (must be larger than first IP) Adds subnet to the CMTS map Subnet net Subnet mask Node/Attribute Interfaces Name Default Value -If_1 CM Capacity (bits/sec) -- Maps Add Range First IP Last IP --0.0 Fairshare Installation & Configuration Guide: Release 5.0.255.0.0. 2010 165 .0.

C04 July 8. 2./ems_cli <command type> <parameter(s)> For example: 166 Fairshare Installation & Configuration Guide: Release 5./ems_cli editconfig command. Accessing the CLI 1./ems_cli addconfig command. At the command line. To configure CMTSs using the CLI. enter the following: cd /opt/SDE/SDE_EMS . you first must add the CMTS to the system using the . 2010 05-00095-C04 . Command syntax CLI commands use the following syntax: . It is for use on the SDE machine that owns the management service VIP./ems_cli ? CLI conventions Commands and command descriptions use the following conventions: Convention Courier New font <parameter> [parameter] [1st choice|2nd choice|3rd choice] Commands Parameters for which you supply values are in angle brackets A single parameter in square brackets is optional A ‘|’ between text indicates a choice of options Definition Using the CLI The command line interface requires use of specific syntax and user input for viewing and modifying elements.60 Rev. edit its attributes using the .Appendix C: Manually configuring CMTSs Configuring CMTSs through the CLI The EMS CLI enables you to configure individual CMTSs to the SDE directly from the command line. Establish an SSH connection to the SDE management machine or log onto the management machine locally. After adding the CMTS.

/ems_cli editconfig cmts <CMTS label> IsEnabled [Disabled| Enabled] To determine whether the discovery process discovers all CMTS subnets: . C04 05-00095-C04 July 8./ems_cli addconfig maps <CMTS_label> Subnet <mask> <interface> To add a range to the specified CMTS: ./ems_cli addconfig interfaces <CMTS_label> interface <interface name> Edit CMTS ./ems_cli addconfig maps <CMTS_label> Range <last IP> <interface> <subnet IP> • • <first IP> • To add an interface to the specified CMTS: ./ems_cli addconfig cmts <CMTS_label> <CMTS IP> [<service name> <connecting VIP>] To add a subnet to the specified CMTS: ./ems_cli editconfig cmts <CMTS label> AllSubnets Yes Edits the CMTS’s parameters so that the discovery process discovers all CMTS subnets CMTS Add CMTS • To add a new CMTS: ./ems_cli editconfig cmts <CMTS label> ip <new IP address or FQDN> 167 • • • • Fairshare Installation & Configuration Guide: Release 5.60 Rev./ems_cli editconfig cmts <CMTS label> Changes a parameter on the specified CMTS • To disable/enable the CMTS: . 2010 ./ems_cli editconfig cmts <CMTS label> CollectOnly [Yes|No] To change the CMTS's name: ./ems_cli editconfig cmts <CMTS label> CmtsLabel <new CMTS name> To change the CMTS's IP address or FQDN: .Configuring CMTSs through the CLI ./ems_cli editconfig cmts <CMTS label> AllSubnets [Yes|No] To determine whether the SDE only collects data from the CMTS: ./ems_cli addconfig cmts <CMTS_label> <CMTS IP> [<service name> <connecting VIP>] Configures a CMTS to the SDE .

C04 July 8./ems_cli editconfig cmts <CMTS label> CmtsKATimeout <new value> To change the CMTS's RKS: ./ems_cli editconfig cmts <CMTS label> service <new service> To change the VIP used to connect to the CMTS: ./ems_cli editconfig cmts <CMTS label> Community <new value> To configure the IP address the SDE uses to connect to the CMTS to receive SNMP data. if different from the IP address defined for the CMTS: Fairshare Installation & Configuration Guide: Release 5./ems_cli editconfig cmts <CMTS label> vipid <new IP> To change the CMTS's minimum delay between gate commands (ms): ./ems_cli editconfig cmts <CMTS label> SnmpIP <value> To configure the IP address sent by the CMTS in the IPDR record’s CMTSipAddress field. if different from the IP address defined for the CMTS: .Appendix C: Manually configuring CMTSs • • To change the CMTS's COPS port number: ./ems_cli editconfig cmts <CMTS label> port <new port value> To change the CMTS's vendor: . 2010 05-00095-C04 • • • • • • • • • • • • • 168 ./ems_cli editconfig cmts <CMTS label> RCGap <new value> To change the CMTS's jitter: .60 Rev./ems_cli editconfig cmts <CMTS label> MaxGrantSize <new value> To change the CMTS's Max Grants Per Interval parameter: ./ems_cli editconfig cmts <CMTS label> CmtsUPDelay <new value> To change the CMTS's downstream delay: ./ems_cli editconfig cmts <CMTS label> CmtsDownDelay <new value> To change the CMTS's Max Grant Size parameter: ./ems_cli editconfig cmts <CMTS label> CmtsJitter <new value> To change the CMTS's upstream delay: ./ems_cli editconfig cmts <CMTS label> rksid <new ID> To change the service to which the CMTS is connected: ./ems_cli editconfig cmts <CMTS label> CmtsVendor <vendor name> To change the CMTS's KA timeout (ms): ./ems_cli editconfig cmts <CMTS label> MaxGrantPerInterval <new value> To change the CMTS's SNMP community: .

/ems_cli editconfig cmts <CMTS label> CmtsUpstreamCongestion <value> To change the percentage of the downstream bandwidth above which an interface on a CMTS is considered congested: ./ems_cli editconfig cmts <CMTS label> IpdrRecordIP <value> • To change the percentage of the upstream bandwidth above which an interface on a CMTS is considered congested: ./ems_cli editconfig cmts <CMTS label> ifSpeedUpstreamDefault <value> To change the default ifSpeed assigned to any unrecognized CMTS downstream interface in an IPDR record ./ems_cli editconfig cmts <CMTS label> interfaces <interface name> interfacename <new interface name> To change the upstream bandwidth of the specified interface (bits/sec): .60 Rev. C04 05-00095-C04 July 8./ems_cli editconfig cmts <CMTS label> IPDRSession <interface name> MinInterfaceBW <value> • • • • • • • • • • Fairshare Installation & Configuration Guide: Release 5./ems_cli editconfig cmts <CMTS label> interfaces <interface name> UpstreamBW <value> To change the downstream bandwidth of the specified interface (bits/sec): ./ems_cli editconfig cmts <CMTS label> discovery <new source> To display parameters for changing a CMTS's interface: ./ems_cli editconfig cmts <CMTS label> ifSpeedDownstreamDefault <value> . 2010 169 ./ems_cli editconfig cmts <CMTS label> interfaces <interface name> MinInterfaceBW <value> To change the interface's CM capacity: ./ems_cli editconfig cmts <CMTS label> Enable file <value> • To change the CMTS's map auto discover source: ./ems_cli editconfig cmts <CMTS label> interfaces <interface name> ? To change the name of the specified interface: .Configuring CMTSs through the CLI ./ems_cli editconfig cmts <CMTS label> CmtsDownstreamCongestion <value> To change the default ifSpeed assigned to any unrecognized CMTS upstream interface in an IPDR record ./ems_cli editconfig cmts <CMTS label> interfaces <interface name> DownstreamBW <value> To change the interface's CM capacity: .

Appendix C: Manually configuring CMTSs 170 Fairshare Installation & Configuration Guide: Release 5. 2010 05-00095-C04 . C04 July 8.60 Rev.

Example XML description files for CMTS import This appendix provides example XML description files for configuring large numbers of CMTSs to the system. The following topics are included in this appendix: • “Example XML description file for IPDR collection and PCMM enforcement” on page 172 — provides an example XML description file for IPDR collection and Fairshare application using PCMM “Example XML description file for SPB data collection and PCMM-PTS enforcement” on page 174 — provides an example XML description file for SPB data collection and PCMM and PTS Fairshare application D • .

For information about importing CMTS maps. <?xml version="1.Appendix D: Example XML description files for CMTS import Example XML description file for IPDR collection and PCMM enforcement The example XML file below displays the maximum number of CMTS and IPDR session attribute fields that need to be defined for Fairshare when the SDE collects subscriber data using IPDR and applies Fairshare policies either through its policy server using PCMM. If the CMTS will not collect SNMP information. CMTS maps are required to apply Fairshare actions using the SDE policy server. 2010 05-00095-C04 • 172 . the SnmpCollection value must be set to ‘no’.60 Rev. see “Import CMTS maps” on page 109.0" encoding="UTF-8"?> <CmtsView> <Index id="0">IsEnabled</Index> <Index id="1">CmtsLabel</Index> <Index id="2">Id</Index> <Index id="3">Ip</Index> <Index id="4">IpdrIP</Index> <Index id="5">SnmpIP</Index> <Index id="6">IpdrRecordIP</Index> <Index id="7">Port</Index> <Index id="8">CmtsVendor</Index> <Index id="9">CmtsKATimeout</Index> <Index id="10">Service</Index> <Index id="11">VipId</Index> <Index id="12">community</Index> <Index id="13">AllSubnets</Index> <Index id="14">SnmpCollection</Index> <Index id="15">CmtsUpstreamCongestion</Index> <Index id="16">CmtsdDownstreamCongestion</Index> <Index id="19">DocsisVersion</Index> <Index id="20"> IPDRSessions </Index> <IPDRSessionParams> <Index id=“21">SessionName</Index> <Index id=“22">DocsisType</Index> <Index id=“23">SessionId</Index> <Index id=“24">ConnectionMode</Index> <Index id=“25">SessionType</Index> <Index id=“26">Port</Index> </IPDRSessionParams> </CmtsView> • The Id parameter is optional and is recommended when CMTS maps also will be imported. Fairshare Installation & Configuration Guide: Release 5. or by using PCMM to apply Fairshare on the upstream and the PTS to apply Fairshare on the downstream. C04 July 8.

60 Rev. If the CMTS COPS port number differs from the default. The AllSubnets parameter can be used to configure the SDE to display CMTS interfaces and subnets. Fairshare Installation & Configuration Guide: Release 5. 2010 173 .200 CmtsUPDelay .0 • • • • • Defaults may be used for the CmtsUpstreamCongestion and CmtsDownstreamCongestion attribute values. The RksId attribute is defined only if the system will also connect to a record keeping server. The CmtsKATimout parameter sets the Keep Alive Timeout between the CMTS and policy server. you MUST include the DocsisVersion field and define the correct DOCSIS version in the CSV file. If they are not defined in the XML and CSV files. define the Port attribute in the file.0 ms MaxGrantSize . the default values will be used: • • • • • • CmtsJitter . All other PCMM-related attributes are optional.30 ms CmtsDownDelay .0 MaxGrantPerInterval . If the CMTS’s DOCSIS version differs from the default (DOCSIS 3). Table 19: Attributes for CMTS import on page 101 explains the CMTS attributes defined by the above Index IDs.Example XML description file for IPDR collection and PCMM enforcement • • • The SnmpIP and IpdrRecordIP fields are defined only if they are different from the IP address defined for the CMTS. C04 05-00095-C04 July 8.200 ms RCGap .

For information about importing CMTS maps. the value for the CollectOnly. • • • • 174 Fairshare Installation & Configuration Guide: Release 5. The XML description file appears as follows: <?xml version="1.60 Rev. attribute should be set to ‘no’ to allow the SDE to send policies to the policy server. The Id parameter is optional and is recommended when CMTS maps also will be imported. CMTS maps are required to apply Fairshare actions using the SDE policy server. the Port field also should be added. C04 July 8. you MUST include the DocsisVersion field and define the correct DOCSIS version in the CSV file. 2010 05-00095-C04 . If the CMTS COPS port number differs from the default (3918). see “Import CMTS maps” on page 109. The SnmpIP field is defined only if it is different from the IP address defined for the CMTS.0" encoding="UTF-8"?> <CmtsView> <Index id="0">IsEnabled</Index> <Index id="1">CmtsLabel</Index> <Index id="2">Id</Index> <Index id="3">Ip</Index> <Index id="4">Port</Index> <Index id="5">CmtsVendor</Index> <Index id="6">CmtsKATimeout</Index> <Index id="7">Service</Index> <Index id="8">VipId</Index> <Index id="9">CollectOnly</Index> <Index id="10">community</Index> <Index id="11">AllSubnets</Index> <Index id="12">SnmpCollection</Index> <Index id="13">IpdrCollection</Index> <Index id="14">CmtsUpstreamCongestion</Index> <Index id="15">CmtsdDownstreamCongestion</Index> <Index id="22">DocsisVersion</Index> • In the CSV file.Appendix D: Example XML description files for CMTS import Example XML description file for SPB data collection and PCMM-PTS enforcement The following example XML file displays the maximum number of CMTS attribute fields that need to be defined for Fairshare when the SDE collects subscriber data from the SPB and applies Fairshare policies using PCMM on the upstream and the PTS on the downstream. If the CMTS’s DOCSIS version differs from the default (DOCSIS 3). The value for SnmpCollection should be set to ‘yes’ to allow the SDE to collect SNMP data from the CMTS.

200 ms RCGap . C04 05-00095-C04 July 8. Fairshare Installation & Configuration Guide: Release 5.30 ms CmtsDownDelay . Table 19: Attributes for CMTS import on page 101 explains the CMTS attributes defined by the above Index IDs.60 Rev. the default values will be used: • • • • • • CmtsJitter . 2010 175 .0 • Defaults may be used for the CmtsUpstreamCongestion and CmtsDownstreamCongestion attribute values.Example XML description file for SPB data collection and PCMM-PTS enforcement • • • • The CmtsKATimout parameter sets the Keep Alive Timeout between the CMTS and policy server. If they are not defined in the XML and CSV files.0 MaxGrantPerInterval . All other PCMM-related attributes are optional.200 CmtsUPDelay . The RksId attribute is defined only if the system will also connect to a record keeping server.0 ms MaxGrantSize . The AllSubnets parameter also may be used to configure the SDE to display CMTS interfaces and subnets.

2010 05-00095-C04 .Appendix D: Example XML description files for CMTS import 176 Fairshare Installation & Configuration Guide: Release 5. C04 July 8.60 Rev.

Uninstalling the SDE This appendix explains the procedure for uninstalling the SDE software The following topics are included in this appendix: • “SDE uninstall procedure” on page 178 — explains how to uninstall the SDE software from the server E .

Enforce removing the SDE packages if they still exist by entering the following command exactly as is: rpm -qa --qf '[%{SUMMARY} :%{NAME}-%{VERSION}-%{RELEASE}\n]' | grep SDE | cut -f2. On the SDE machine.60 Rev. To delete the SDE software: 1.-d: 4. Verify that no SDE package is still installed by entering the following command exactly as is: rpm -qa --qf '[%{SUMMARY} :%{NAME}-%{VERSION}-%{RELEASE}\n]' | grep SDE | cut -f2. Verify that the SDE is not running any more: service sde status 178 Fairshare Installation & Configuration Guide: Release 5. C04 July 8. 2010 05-00095-C04 . The uninstall procedure removes all /opt/SDE files. It also gives you the option of deleting the database.Appendix E: Uninstalling the SDE SDE uninstall procedure The following procedure should be used In cases where the SDE software must be deleted from the server before new software can be installed. Warning: The following procedures remove the SDE software from the server.-d: | xargs rpm -e Note: To delete a specific SDE package you can use the following command: rpm -e <package name> 3. run the SDE uninstall script: /opt/install/uninstall4sde 2.

SDE ports This appendix contains a table of ports the SDE uses to communicate with the EMS. The following topics are included in this appendix: • “Ports used for SDE communications” on page 180 — describes the ports used between the SDE and the different network resources F . NetPortal and external system elements through the firewall.

WSAM SOAP (TCP) ----------From border VIP: port 8888 WSEventing (From Fairshare Engine to WSAM) From physical IP to CMTS IP: 161 (UDP) ----------From edge VIP to CMTS IP: 4737 ----------From edge VIP to CMTS IP: 3918 (COPS) From physical IP to 3rd party PS IP: 3918 From edge VIP to 3rd party IPDR relay IP: 4737 From edge VIP to SPB IP: 8081 From physical IP: 3306 to NetPortal IP (For access to the MySQL database on the NetPortal machine) SDE port 111 RPC (UDP) 180 Fairshare Installation & Configuration Guide: Release 5.Appendix F: SDE ports Ports used for SDE communications The following table describes the ports used between the SDE and the different network resources: Table 28: Communications ports SDE CMTS 3rdparty PS 3rdparty IPDR relay SPB NetPortal (From) Accessing Element (To) Accessed Resource SDE From physical IP: ports 4803. 2010 05-00095-C04 . C04 July 8.4804 spread (UDP) port 1138 WSAM Session Sharing (TCP) port 1140 PS Session Sharing (TCP) ----------From mgmt VIP: port 22 (SSH) ----------To border VIP: port 8080 .60 Rev.

60 Rev. 2010 181 .XDR relay (TCP) SDE border VIP: port 3918 SDE border VIP: port 8080 To management VIP: port X X X X X 3rd-Party PS X X X X X 3rd-party IPDR relay X X X X X Applicaton Manager Application Server Operator Management System X X X X X X X X X X X X X X Fairshare Installation & Configuration Guide: Release 5.Ports used for SDE communications (From) Accessing Element (To) Accessed Resource SDE CMTS 3rdparty PS 3rdparty IPDR relay SPB NetPortal port 3306 MySQL database (TCP) ----------From physical IP: ports 7000-7015 EMS (TCP/ UDP) CMTS From edge VIP: port 6210 (TCP) From physical IP: port 3918 (UDP) From edge VIP: port 6210 IPDR file streaming (TCP) ----------From edge VIP: port 4737 . C04 05-00095-C04 July 8.

as DB/ NetReports are located on the cluster) Management Service To management VIP: port 22 (SSH) ----------Physical IP: port 7000-7015 EMS (TCP/ UDP) From management VIP: 8085 (to NetPortal communicati ng with the NetReports X X XX X NetPortal X X X X From edge VIP to NetPortal IP: port 3306 (MySQL replication) Note: When no edge VIP used. SNMP) port 1099 (EMS) ----------From edge VIP: port 8085 (NetReports connecting to the edge VIP.60 Rev. communications are through the 182 Fairshare Installation & Configuration Guide: Release 5.Appendix F: SDE ports (From) Accessing Element (To) Accessed Resource SDE CMTS 3rdparty PS 3rdparty IPDR relay SPB NetPortal 161/162 (UDP. C04 July 8. 2010 05-00095-C04 .

Ports used for SDE communications (From) Accessing Element (To) Accessed Resource SDE CMTS 3rdparty PS 3rdparty IPDR relay SPB NetPortal on the SDE clusters) Accessing element (outbound) will use any local port to connect to the accessed resource (inbound) when specific ports should be allowed.60 Rev. managemen t VIP Fairshare Installation & Configuration Guide: Release 5.g.. Systems belonging to the same cluster are allowed to connect to each other with no limitations—e. C04 05-00095-C04 July 8. 2010 183 . SDE-FS-1 can communicate with SDE-FS-2 through any port.

C04 July 8.60 Rev.Appendix F: SDE ports 184 Fairshare Installation & Configuration Guide: Release 5. 2010 05-00095-C04 .

Index /etc/hosts 25 /etc/stscibfug/network 25 A active-active mode. C04 05-00095-C04 July 8. 2010 . configuring 61 activity log 81 application manager configuring 124 parameters 125 application server configuring 126 external configuration 154 parameters 126 attaching services 55.60 Rev. CMTS 100 D data collection parameters 86 data tier injection 88 database excluding IPs from 117 for Fairshare 22 dependencies. missing 44 dummy VIPs 16 C CLI accessing 166 command syntax 166 conventions 166 cluster 21. 71 B border service border service 52 external PS connection 52 border VIP changing in properties file 57 configuring 52 procedure 107 XML description file 97 CMTS interfaces configuration parameters 165 manually configuring 88 CMTS maps configuration parameters 165 configuring 164 import process 110 importing 109 sample import range file 110 sample import subnet file 109 XML description file 109 CMTS XML description file hybrid Fairshare application 174 IPDR and PCMM 172 CMTSs IPDR sessions 162 command line interface. see CLI 46 COPS parameters values 83 CSV data file. 68 CMTS CLI add command 167 CLI edit command 167 configuring through CLI 166 configuring through EMS 156 default ifSpeed 157 disabling 156 importing 97 interfaces and maps 164 parameters 158 CMTS import attributes for CSV file 101 available attributes 98 CSV data file 100 errors 107 IPDR sessions 99 E edge service adding 71 purpose of 22 edge VIP adding 62 configuring 51. 71 EMS accessing 46 Linux GUI 47 loging in 47 usage 46 Windows installation 46 error log 81 eth0 25 185 Fairshare Installation & Configuration Guide: Release 5.

enable 161 file transfer 152 fsam_conf. 60 management log 81 management VIP assigning 50 purpose of 21 map range.properties file 57 FTP 152 collection parameters 89 IPDR file logging 157 IPDR relay inbound 105 outbound 58 IPDR session parameters 162 IPDR sessions configuring through EMS 162 importing 99 IPs. 2010 05-00095-C04 . C04 July 8. CMTS 107 importing CMTS maps 109 CMTSs 97 installation additional clusters 69 local yum 35 of NetPortal 141 prerequisites 24 troubleshooting 44 verifications 41 verifications on second machine 63.event messages 127 external policy server 52 F Fairshare enforcement 18 Fairshare parameters values 85 file logging 58. 32 node 50 service 21. sample XML import file 110 I ifSpeed 88 import errors. 90 file logging.60 Rev. excluding from database 117 L log parameters values 81 logs activity 81 changing location of 151 error 81 management 81 G garbage gates 80 gate store 79 general parameters values 78 global parameter settings 75 H hardware minimum server requirements 14 Recommended partitioning 15 requirements per node 14 verification 14 high availability 70 M machine hostname troubleshooting 45 management cluster 21. 73 verifications prior to 24 VIP requirements 26 yum 39 interface congestion 88 IPDR N net-snmp 44 NetPortal edge service 142 installing 141 management service 142 overview of 140 Network requirements 16 O operating system 15 186 Fairshare Installation & Configuration Guide: Release 5.

see VIP 17 Fairshare Installation & Configuration Guide: Release 5. 2010 187 . C04 05-00095-C04 July 8. configuring 150 stateful limit 78 subnets excluding from database 118 sample XML import file 109 support account 28 Syslog server 81 system monitoring SDE system view 63 S SCN source 87 SCP program 152 SDE cluster 21 SDE architecture 18 SDE deployment types 19 SDE node adding 60. see data tier injection 88 trap receiver configuring 133 parameters 133 troubleshooting machine hostname 45 yum install 44 U uninstall procedure 178 upgrade management machine 144 verification procedures 145 usage information 127 V VIP parameters 51 VIPs border 52 edge 51 management 50 purpose of 17 required 26 Virtual IP. 70 SDE node parameters 61 SDE parameters configuring 77 COPS 83 Fairshare 85 garbage gates 80 general 78 log 81 WSAM 84 SDE system view 63 SDE uninstall 178 second edge VIP 61 second SDE machine 60 service parameters 54 services attaching to nodes 55 predefined 50 session border controller 124 SFTP program 152 SNMP T tier injection.P portmap 25 ports table 180 pre-installation checklist of requirements 31 recommended checks 24 requirements 24 primary SDE node 51 R recovery 60 reports configuring 137 RHEL accessibility 33 RKS configuring 127 parameters 128 RPC connectivity 26 agent 132 collection parameters 89 trap receiver parameters 133 trap receivers 133 softswitch 124 SPB collection parameters 90 configuring to SDE 119 excluding individual IPs 117 mapping edge services 120 parameters 120 used with SDE 114 SSL.60 Rev.

installing 47 Y yum configuring as client 37 installation from repository 39 local installation 35 troubleshooting 44 X XML description file.W WSAM parameters values 84 WSAM service configuring 53 purpose of 22 XWindow. 2010 05-00095-C04 . CMTS 98 188 Fairshare Installation & Configuration Guide: Release 5.60 Rev. C04 July 8.

.

sandvine Sandvine Incorporated 408 Albert Street Waterloo.880. Ontario.com ® .884.9892 Web Site: www. Canada N2L 3V3 Phone: (+1) 519.sandvine.2600 Fax: (+1) 519.