Page 1 Title page Alcatel-Lucent 5620 SERVICE AWARE MANAGER | 13.0 R7 PLANNING GUIDE 3HE-09809-AAAG-TQZZA Issue 1 | December 2015...
Page 2 Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications.
Page 3: Table Of Contents
Redundancy deployment considerations for 5620 SAM 1-15 1-15 ..................Operating systems specifications Overview ...................................... Operating systems specifications ............................5620 SAM Client or Client Delegate software requirements ................... Platform requirements Overview ...................................... Hardware platform requirements overview ........................Hardware platform and resource requirements using Virtualization ..............
Page 4 Bandwidth requirements for collocated 5620 SAM installations ................Bandwidth requirements for distributed 5620 SAM installations ................Bandwidth requirements for 5620 SAM GUI Clients ....................Bandwidth requirements for displaying 5620 SAM GUI Clients on X displays ..........Bandwidth requirements for 5620 SAM-O OSS Clients 5-10 5-10 ..................
Page 5 ............................5620 SAM network element communication ......................... 5620 SAM and firewalls ................................ Port Information ..................................FTP between the 5620 SAM Server and 5620 SAM Auxiliary Statistics Collector and the managed network 7-15 7-15 ............................................................................... 5620 SAM 3HE-09809-AAAG-TQZZA 13.0 R7...
Page 6 5620 SAM Server multiple IP addresses deployment scenarios ................5620 SAM Auxiliary Statistics Collector multiple IP addresses deployment scenarios ......... 5620 SAM Auxiliary Call Trace Collector multiple IP addresses deployment scenarios ......5620 SAM Auxiliary Cflowd Collector multiple IP addresses deployment scenarios ........
Page 7: About This Document
5620 SAM Release 13.0 but instead presents the reader with pre-installation information required to plan a successful deployment. The 5620 SAM Planning Guide is not a comprehensive list of technologies supported or not supported by 5620 SAM or the platforms hosting it. The Alcatel-Lucent NSM Product Group should be consulted for clarification when uncertainty exists.
Page 8: Document Support
• Added firewall port 13528 for 1830 OCS management • Added 5620 SAM Cflowd Auxiliary requirements • Updated port 9010 requirements • Addition of the 5620 SAM Analytics Server Document support Customer documentation and product support URLs: Customer documentation welcome page •...
Page 9: Product Deployment Overview
• 5620 SAM Auxiliary (Statistics Collector, Call Trace Collector, Cflowd Collector) • 5620 SAM Auxiliary Database • 5620 SAM Database • 5620 SAM Analytics Server 5620 SAM supports co-location of the 5620 SAM Server and 5620 SAM Database software on a single workstation..............................................5620 SAM 3HE-09809-AAAG-TQZZA 13.0 R7...
Page 10 SAM Database or the 5620 SAM Auxiliary Database for statistics record storage. The 5620 SAM Auxiliary Database is deployed in a cluster of three servers and when used with the 5620 SAM Auxiliary Statistics Collector, can be used to collect higher rates of accounting, performance, and application assurance accounting statistics and to increase retention of accounting, and performance statistics.
Page 11 Connectivity between 5620 SAM components supports IPv6 with certain restrictions where the following is not supported: • 5620 SAM deployments that include the management of 1830 PSS / OCS, 9500 MPR, 9471 WMM, 5780 DSC, eNodeBs, Small Cell Access Points / Gateways •...
Page 12 The following illustrates a typical deployment of 5620 SAM in standalone mode when the 5620 SAM Server and 5620 SAM Database functions are collocated and a 5620 SAM Auxiliary Call Trace Collector is used. The 5620 SAM Auxiliary Statistics Collector is not supported in this configuration.
Page 13 Auxiliary Statistics Collectors or it could be configured redundant as n+1. There can be one or two 5620 SAM Auxiliary Call Trace Collectors collecting call trace data from the network with redundancy of the 5620 SAM Call Trace Collector supported. The 5620 SAM Auxiliary Database must always be installed in a cluster of three instances.
Page 14 5620 SAM Auxiliary Database, 5620 SAM Auxiliary Database, 5620 SAM Analytics Server, and 5620 SAM Database. The 5620 SAM Client can be installed on RHEL Server x86-64, RHEL Server x86, or Windows where the 5620 SAM Client Delegate can be installed on RHEL Server x86-64, or Windows Server 2008R2 and Server 2012.
Page 15 Each 5620 SAM Auxiliary Call Trace Collector is configured as a preferred for the 5620 SAM Active Server and as a reserved for the 5620 SAM Standby Server. This allows for a redundant 5620 SAM Auxiliary Call Trace Collector configuration.
Page 16: 5620 Sam Key Technologies
The Client Delegate platform provides an option to consolidate multiple installations of the 5620 SAM GUI Client on a single workstation. Individual 5620 SAM Clients can be installed on the Client Delegate. The 5620 SAM Client also supports the ability for multiple users to share a single installation;...
Page 17 The 5620 SAM Database embeds an installation of Oracle 12c Release 1 Enterprise Edition, which is installed with the 5620 SAM Database. This database is used to store information about the managed network. The installation of Oracle is customized for use with the 5620 SAM application and must be dedicated to 5620 SAM.
Page 18: Redundancy Architecture
• Loss of physical network connectivity between 5620 SAM Server and/or 5620 SAM Database and the managed network • Hardware failure on workstation hosting the 5620 SAM Server and/or 5620 SAM...
Page 19 5620 SAM Auxiliary Call Trace Collector must be used. The 5620 SAM Auxiliary Call Trace Collector can be installed in a redundant pair. Up to two 5620 SAM Auxiliary Call Trace Collector redundant pairs can be installed.
Page 20 5620 SAM Auxiliary Collectors configured. In the example where redundancy is geographic, there can be up to four 5620 SAM Auxiliary Statistics Collectors and up to two 5620 SAM Auxiliary Call Trace Collector workstations configured in each geographic location. The Preferred/Reserved role of the 5620 SAM Auxiliary Collector is dependent and configured on the 5620 SAM Server that is active.
Page 21 Product deployment overview Redundancy architecture ..............................................Figure 1-8 5620 SAM distributed Server/Database redundant deployment with redundant 5620 SAM Auxiliaries that crosses geographic boundaries 5620 SAM Clients Geographic Location A Geographic Location B Oracle DataGuard 5620 SAM Database 5620 SAM Database...
Page 22 Preferred for the Standby Server Managed Reserved for the Standby Server Reserved for the Active Server Network 24405 Further information about 5620 SAM redundancy can be found in the 5620 SAM User Guide ..............................................1-14 5620 SAM 3HE-09809-AAAG-TQZZA 13.0 R7...
Page 23: Redundancy Deployment Considerations For 5620 Sam
When deploying 5620 SAM in a redundant configuration, the following items should be considered. It is a best practice to keep the 5620 SAM Server, 5620 SAM Database, and 5620 SAM Auxiliary Collectors in the same geographic site to avoid the impact of network latency.
Page 24 Redundancy deployment considerations for 5620 SAM ..............................................• The machines which are intended to be used as primary 5620 SAM Server and 5620 SAM Database should be installed on the same LAN as one another with high quality network connectivity.
Page 25: Operating Systems Specifications
Operating systems specifications Red Hat Enterprise Linux (RHEL) 5620 SAM is supported on Red Hat Enterprise Linux 6, Server Edition x86-64 for the 5620 SAM Server, 5620 SAM Auxiliary Collector, 5620 SAM Auxiliary Database, 5620 SAM Analytics Server, 5620 SAM Database, 5620 SAM Client Delegate, and 5620 SAM Client.
Page 26 5620 SAM supports the use of the RHEL Logical Volume Manager (LVM) on all server types except for the 5620 SAM Auxiliary Database. The support of LVM is limited to the resizing of logical volumes only. To ensure that disk throughput and latency of the resized volume remains consistent, the procedure Adding LVM disk space, in the System Administrator Guide, needs to be followed.
Page 27: 5620 Sam Client Or Client Delegate Software Requirements
5620 SAM Client or Client Delegate software requirements 5620 SAM Client or Client Delegate software requirements 5620 SAM clients can be launched, installed and uninstalled through a web browser (Web Launch, Install and Uninstall). To use this functionality, each client platform must have a system JRE (Java Runtime Environment) installed.
Page 28 The NEtO element manager that is cross launched from the 5620 SAM Client UI requires binding to a specific system port on a 5620 SAM Client and therefore a Client Delegate can only support a single NEtO instance running amongst all clients connected to a Client Delegate at any time.
Page 29: Platform Requirements
P latform requirements Overview Purpose This section defines the platform requirements for successfully running the 5620 SAM application. Following these platform guidelines is necessary to ensure the 5620 SAM application performs adequately. Contents Hardware platform requirements overview Hardware platform and resource requirements using Virtualization...
Page 30: Hardware Platform Requirements Overview
In exceptional circumstances, a single 5620 SAM GUI Client can be temporarily run from a 5620 SAM Server, provided that a minimum of 16 GB RAM is installed on the 5620 SAM Server in a distributed configuration, and 24 GB RAM is installed on the 5620 SAM Server/Database in a collocated configuration.
Page 31: Hardware Platform And Resource Requirements Using Virtualization
Virtualization is supported using both VMware vSphere ESXi and RHEL KVM. All other forms of virtualization or virtualization products are not supported. For installations of the 5620 SAM Server, 5620 SAM Database, and 5620 SAM Auxiliary Collector on a Guest Operating System of a virtualized installation, the Guest Operating System must be a 5620 SAM supported version of RHEL 6 Server x86-64.
Page 32 5620 SAM. VMware Virtualization 5620 SAM supports using VMware vSphere ESXi 5.0, 5.1, 5.5, and 6.0 only, on x86 based servers natively supported by ESXi. VMware’s Hardware Compatibility List (HCL) should be consulted to determine specific hardware support. Not all features offered by ESXi are supported when using 5620 SAM.
Page 33 • Do not include memory snapshots • Always reboot all 5620 SAM Virtual Machines after reverting to snapshots • 5620 SAM performance can be degraded by as much as 30% when a snapshot exists and therefore 5620 SAM performance and stability is not guaranteed •...
Page 34: Minimum Hardware Platform Requirements
In that case, the distributed minimum platform is recommended. Red Hat support must be purchased for all platforms running RHEL Server with 5620 SAM. It is strongly recommended to purchase a support package from Red Hat that provides 24x7 support.
Page 35 Platform requirements Minimum hardware platform requirements ..............................................HP x86 hardware configuration with RHEL Server x86-64 Table 3-2 5620 SAM RHEL Server x86-64 minimum collocated platforms For networks not exceeding: • 675 MDAs • 1000 GNEs • 5 simultaneous 5620 SAM Clients (GUI or OSS) •...
Page 36 Platform requirements Minimum hardware platform requirements ..............................................Table 3-3 5620 SAM RHEL Server x86-64 minimum distributed platforms (continued) For networks not exceeding: • 1875 MDAs • Maximum of 5,000 GNEs • 5 simultaneous 5620 SAM Clients (GUI or OSS) •...
Page 37 • 2 Call Trace Sessions (if using a 5620 SAM Auxiliary Call Trace Collector) • 10,000 Cflowd flows and 1M unique records in memory (if using a 5620 SAM Auxiliary Cflowd Collector) 5620 SAM application VM Guest H/W Resource Requirements 5620 SAM Server 3 * x86 CPU Cores, minimum 2.4GHz...
Page 38 Higher numbers may be achievable, but Alcatel-Lucent will only support the stated maximums. In the event that higher number of simultaneous 5620 SAM Clients is desired, the number of equivalent MDAs can be reduced. Note that all stated maximums may not be achievable simultaneously.
Page 39 300GB disk space I/O throughput and latency as provided in 5620 SAM Sizing response When a 5620 SAM Statistics Auxiliary is installed, the 5620 SAM Database is required to have a minimum 16 GB RAM to accommodate the additional Oracle database sessions.
Page 40 The Client Delegate platform provides an option to consolidate multiple installations of the 5620 SAM GUI Client on a single workstation or the option of installing one instance of the 5620 SAM GUI client run by many users (with unique Operating System accounts).
Page 41 Platform requirements Minimum hardware platform requirements ..............................................Additional memory for each 5620 SAM Client will be required for management of the network elements described in “GNE, Alcatel-Lucent OmniSwitch, 9471 WMM, eNodeB, and 5780 DSC considerations” (p. 5-20) or for a Web Browser if SAM Supervisor is to be used.
Page 42: 5620 Sam-O 3Gpp Interface
5620 SAM-O 3GPP Interface requires a separate JVM to be installed on the 5620 SAM Server, and is only supported on 5620 SAM Servers with a minimum 24GB RAM in a distributed configuration or 5620 SAM Server/Databases with a minimum 32GB RAM in a collocated configuration.
Page 43: 5620 Sam Gui Client Platform Requirements
In cases where other applications are running on the same platform as the 5620 SAM Client, it is important to ensure 1 GB RAM is available to the 5620 SAM Client. Additional memory for each 5620 SAM Client will be required for management of the network elements described in “GNE, Alcatel-Lucent OmniSwitch, 9471 WMM,...
Page 44 5620 SAM GUI Client platform requirements ..............................................A 5620 SAM GUI client installation is supported on a Guest Operating System of a VMware vSphere ESXi or RHEL KVM installation. The Guest OS must be one of those supported for GUI Clients found in “Operating systems specifications”...
Page 45 MDAs deployed in the network using the help button on the 5620 SAM GUI. It is also possible to determine the number of statistics being handled by the system by looking at the 5620 SAM GUI’s “Statistics Collection” information window.
Page 46 5620 SAM | 5650 CPAM Installation and Upgrade Guide. The increased disk I/O performance offered by RAID 0 is required for all 5620 SAM deployments. The 5620 SAM | 5650 CPAM Installation and Upgrade Guide provides details of these configurations.
Page 47 See the following table for required mount points and performance targets when using 5620 SAM with a SAN. Note that certain mount points may not be required due to deployment options. Refer to the 5620 SAM | 5650 CPAM Installation and Upgrade Guide for required mount points based upon the type of 5620 SAM workstations deployed.
Page 48 5620 SAM includes a benchmarking utility to be used for determining the throughput and latency of the storage device to be used with the virtual server hosting 5620 SAM. The utility is installed with a 5620 SAM Server in the /opt/5620sam/server/nms/bin/unsupported/5620_SAM_IOTest directory and is called 5620_SAM_IOTest.pl.
Page 49 /opt/5620sam/samdb/tablespace < 1.0 /opt/5620sam/server/nms/log < 1.0 /opt/5620sam/samdb/archivelog < 1.0 /opt/5620sam/nebackup < 1.0 The 5620 SAM | 5650 CPAM Installation and Upgrade Guide should be consulted for recommended partition sizes..............................................5620 SAM 3-21 3HE-09809-AAAG-TQZZA 13.0 R7 Issue 1 December 2015...
Page 50 Platform requirements Storage considerations ............................................................................................3-22 5620 SAM 3HE-09809-AAAG-TQZZA 13.0 R7 Issue 1 December 2015...
Page 51 Mechanism to maintain current state of network elements Mechanism to maintain current state of network elements 5620 SAM uses several mechanisms to maintain and display the current state of the network elements it manages. These mechanisms can include: • IP connectivity (ping) verification •...
Page 52 IP connectivity (ping) verification IP connectivity (ping) verification 5620 SAM can be configured to ping all network elements at a configurable interval to monitor IP connectivity. If the network element is unreachable, an alarm will be raised against the network element. Details of the alarm are the following: •...
Page 53 If they do not match, 5620 SAM will request only the missing traps from the network element. If at any point 5620 SAM realizes that it is missing more than 200 traps from a network element, or if the network element no longer has the missed trap, SAM will request a full resynchronization on that network element rather than just request the missing traps.
Page 54 “SNMP trap sequence verification” (p. 4-3) describes 5620 SAM behavior with regards to trap handling. When a network outage occurs, the network element configuration in 5620 SAM will be made consistent with the network element, but any event notifications, such as SNMP traps, that occurred during the network outage will not have been processed.
Page 55 N etwork requirements Overview Purpose This chapter defines the network requirements for the 5620 SAM systems, network elements, and OSS systems. Contents Network requirements Connectivity to the network elements Bandwidth requirements for collocated 5620 SAM installations Bandwidth requirements for distributed 5620 SAM installations...
Page 56 Be sure to include the tables with the bandwidth required for statistics collection in the total bandwidth required between the 5620 SAM workstations, as they are in separate tables. The tables do not specify the underlying infrastructure required to support these bandwidth requirements.
Page 57 Bandwidth requirements for collocated 5620 SAM installations The following table lists the bandwidth requirements for the connections between the components of a 5620 SAM Collocated installation. It is a good practice to measure the bandwidth utilization between the various components to determine a suitable bandwidth.
Page 58 5620 SAM Server to a 5620 SAM Client 1 Mbps 5620 SAM Server to a 5620 SAM-O Client (The bandwidth will 1 Mbps depend on the OSS application) Between a primary and a standby 5620 SAM Server...
Page 59 The registerLogToFile method of retrieving statistics can be compressed or uncompressed. Using the compressed option will require additional CPU requirements on the workstation that is collecting the statistics (either 5620 SAM Server or 5620 SAM Auxiliary Statistics Collector). In this case, the bandwidth required will be reduced.
Page 60 4.6 Mbps Collector is NOT installed). 5620 SAM Auxiliary Statistics Collector to 5670 RAM 5620 SAM Server to 5620 SAM Database workstation if the 5620 3.1 Mbps SAM Server is collecting the statistics 5620 SAM Auxiliary Statistics Collector to 5620 SAM Database...
Page 61 5620 SAM Auxiliary Statistics Collector to 5620 SAM Server and 5620 SAM Server to 5620 SAM Database. It is also a best practice to ensure that the 5620 SAM Auxiliary Statistics Collector, 5620 SAM Server, and 5620 SAM Database are all collocated in the same geographic site.
Page 62 NOTE: a higher bandwidth may be desirable 5620 SAM Auxiliary Database Cluster When a 5620 SAM Auxiliary Database Cluster is part of a 5620 SAM deployment, there are a number of bandwidth requirements listed below. Any bandwidths not listed are not impacted significantly by the use of the 5620 SAM Auxiliary Database for statistics collection.
Page 63 In situations where the frequency of changes sent to the 5620 SAM GUI is significant and exceeds the bandwidth specification, the performance of the 5620 SAM Client will degrade, and there is a possibility that the connection to the server will be dropped.
Page 64 5620 SAM-O when the bandwidth between the machine hosting this application and the 5620 SAM Server is less than the quantity specified in the tables above, possibly as little as 128 kbps. However, in situations where the frequency of network changes increases, the performance or responsiveness of the application will degrade.
Page 65 Disable messages are sent to the 5620 SAM Auxiliary Call Trace Collector from the 5620 SAM Server. 5620 SAM OSS Clients can ask the 5620 SAM Server for the list of 5620 SAM Call Trace Collector workstations, and ftp connect directly to the 5620 SAM Auxiliary Call Trace Collector to retrieve the call trace log files.
Page 66 5620 SAM Server(s), 5620 SAM Auxiliary(s) and the network elements. This bandwidth will be used to carry the management traffic between 5620 SAM and the network element. The following table describes the bandwidth requirements for a particular network element.
Page 67: 5620 Sam
Details on the bandwidth requirements The recommended bandwidth described above is a conservative figure that is meant to ensure that the performance of 5620 SAM and its ability to manage successfully each network element will not be affected by unusual network conditions.
Page 68 In the worst case however, this bandwidth utilization will be less than that utilized during a network element discovery. • SNMP polling: It is possible to configure 5620 SAM to poll the SNMP MIBs on the network elements at various intervals. By default, 5620 SAM will perform a complete poll of the SNMP MIBs every 24 hours on non-SR–OS based network elements.
Page 69 SAM can communicate with a minimum of 20-30 NEs simultaneously – this can increase to 60-70 NEs on a 16 CPU core 5620 SAM Server workstation. For Networks of over 1,000 NEs or where a SAM Auxiliary Statistics ..............................................
Page 70 5 ms. For example, is a specific operation required 5620 SAM to send 1,000 SNMP gets to a single Network Element, 5620 SAM will spend a total of 5 seconds sending and receiving packets when the round trip latency to the network element if 5 ms. The time that 5620 SAM spends sending and receiving the same packets would increase to 50 seconds if the round trip latency were increased to 50 ms.
Page 71 • 7710 SPR Common geographical location of 5620 SAM workstations It is ideal to ensure that all 5620 SAM workstations and the 5620 SAM OSS clients are collocated within a geographical site on a high availability network to avoid the impact of network latency.
Page 72 • 5620 SAM GUI Clients and 5620 SAM Client Delegate Server • 5620 SAM OSS Clients The performance and operation of 5620 SAM can be significantly impacted if there is any measurable packet loss between the 5620 SAM workstations. Significant packet loss can cause 5620 SAM reliability issues.
Page 73 25 seconds sending and receiving 1000 packets (500 SNMP gets and 500 SNMP responses). With a 0.1% packet loss (1 packet out of the 1,000) the 5620 SAM Server will wait for the retry time-out (10 seconds) to expire before retransmitting. This will cause the time to complete the 500 SNMP gets to increase by 10 seconds –...
Page 74: Gne, Alcatel-Lucent Omniswitch, 9471 Wmm, Enodeb, And 5780 Dsc Considerations
5620 SAM Client workstation or 5620 SAM Delegate workstation. It requires a direct connection from the 5620 SAM Client to the 5780 DSC. As such, unique firewall rules are required. There are also increased memory requirements on the 5620 SAM Client and/or 5620 SAM Delegate workstations for the Web Browser.
Page 75: Scaling
S caling Overview Purpose This chapter provides general information about platform scalability for the 5620 SAM. Contents Scaling guidelines Scalability limits 5620 SAM Performance Targets Scaling guidelines for 5620 SAM OSS Clients OSS client limits 5620 SAM OSS Clients using JMS...
Page 76 To achieve these scale limits, a distributed 5620 SAM configuration is required, and may also require a 5620 SAM Auxiliary Statistics Collector and a storage array for the 5620 SAM database workstation.
Page 77 10 interfaces of interest on each device (10 x 18,000 = 180,000 interfaces). Processing of traps from interface types that are not of interest can be turned off in 5620 SAM. Under high trap load, 5620 SAM may drop traps 5620 SAM uses the number of MDAs as the fundamental unit of network dimensioning.
Page 78: Scaling Guidelines
5620 SAM Performance Targets Table 6-3, “5620 SAM Release 13.0 Performance Targets” (p. 6-4) represents the performance targets 5620 SAM. Factors that may result in fluctuations of these targets include: • 5620 SAM Server and 5620 SAM Database system resources •...
Page 79 <15 minutes redundant system Notes: The target includes the installation of the software on the existing servers and 5620 SAM database conversion. Operating System installation/upgrades, patching, pre/post-upgrade testing and file transfers are excluded from the target. Provided proper planning and parallel execution procedures were followed.
Page 80: Scaling Guidelines For 5620 Sam Oss Clients
OSS client limits OSS client limits There can be a maximum of 20 5620 SAM OSS-JMS Clients. Greater than 10 5620 SAM OSS-JMS Clients requires a SAM Server with a minimum of 16 CPU Cores. The number of 5620 SAM OSS-HTTP Clients supported by a 5620 SAM Server workstation is 2 times the number of CPU cores with at least 10 and at most 30 clients supported.
Page 81: 5620 Sam 3Gpp Oss Client
5620 SAM 3GPP OSS Client 5620 SAM 3GPP OSS Client 5620 SAM 3GPP OSS Clients connect to the 3GPP CORBA interface provided on the 5620 SAM Server. Network latency between the 5620 SAM Server and a 5620 SAM 3GPP OSS Client will reduce the message rate.
Page 82: Scaling Guidelines For Statistics Collection
Subscribers, SAPs, and spoke SDP bindings and contain data related to traffic flows that can be used for QoS and traffic management, and application aware reporting. These statistics are collected on the 7x50 ISA cards and retrieved by 5620 SAM via a file that is transferred via ftp/sftp.
Page 83 ..............................................Performance statistics Refer to the 5620 SAM Statistics Management Guide to find the steps required to configure 5620 SAM to retrieve and process performance statistics. Note that two steps are required to enable the collection of performance statistics from the network. First, a policy is defined which specifies a set of polling periods for various MIBs.
Page 84 5620 SAM Server or Auxiliary Statistics collector are set at the installation time and depend on the number of CPU Core available to the 5620 SAM Server or Auxiliary Statistics collector software. The number of CPU Cores...
Page 85 ..............................................The following tables provide the maximum number of accounting statistics records that can be retrieved and processed by the 5620 SAM Server or 5620 SAM Auxiliary Statistics Collector in various situations. To reach the peak accounting statistics collection from the 5620 SAM Auxiliary Statistics Collector workstation, the 5620 SAM Database workstation requires a customized configuration that can be obtained from Alcatel-Lucent personnel.
Page 86 5620 SAM Server are set at the installation time and depend on the number of CPUs available to the 5620 SAM Server software. The number of CPUs available to the 5620 SAM Server depends on the number of CPUs on the workstation and whether the 5620 SAM Database software is collocated with the 5620 SAM Server software on the same workstation.
Page 87 # dmidecode | grep "Core Count" | /usr/bin/awk '{SUM += $3} END {print SUM}' In situations where 5620 SAM is asked to collect more application assurance accounting records than it can process in the specified retrieval period, the extra statistics will not be retrieved from the network.
Page 88 However, it is important to consider that enabling the collection of one type of statistics will reduce the capability of 5620 SAM to collect and process the other type of statistics. It is therefore not possible to achieve the maximum stated limits for performance, application assurance, and accounting statistics records simultaneously, in certain configurations.
Page 89 Using SAM Server Performance Statistics, 5620 SAM can assist in determining how many polled and accounting statistics are being collected. 5620 SAM performance can be adversely affected by increasing the number of historical statistics entries recorded by the 5620 SAM. 5620 SAM system impacts include increased time listing log records from the GUI and OSS clients, increased Oracle tablespaces, and increased database backups times.
Page 90: Scaling Guidelines For Scheduled Tests (Stm)
There are a number of factors which will influence 5620 SAM’s ability to concurrently manage and schedule a large number of tests. 5620 SAM keeps track of how many tests are running concurrently. This is to limit the initiation of the tests, and the processing of the results without interfering with the system’s other functions.
Page 91 Guidelines for maximizing STM test execution: By default, 5620 SAM will only allow test suites with a combined weight of 80,000 to execute concurrently. The test suite weights are identified in the 5620 SAM GUI’s Test Suites List window.
Page 92 This will allow the test suite results to be received from the network element and processed by 5620 SAM more quickly freeing up available system weight more quickly.
Page 93 NE schedulable with “Accounting file” selected. This will produce STM tests that will be executed on the network element, while the test results will be returned to 5620 SAM by way of an accounting file in a similar way to accounting Statistics.
Page 94 • The amount of data that is generated/updated by the test within the network elements. 5620 SAM will have to obtain this information and store it in the 5620 SAM database. The quantity of data depends on the type of tests being performed and the configuration of the objects on which the tests are performed.
Page 95 24 hours. At the maximum collection rate of 500,000 test results per 10 minutes, the storage requirements on the 5620 SAM Server in the xml_output directory is 300GB per JMS client. The storage requirements are doubled if using the maximum number of JMS clients for file accounting STM results.
Page 96: Scaling Guidelines For Cflowd Statistics Collection
Number of aggregated output requests that are sent to the server every 60 minutes. Assumes transfer has sufficient bandwidth to complete in a timely manner. Packet loss may increase if communication between the 5620 SAM Cflowd Aux and target file server is interrupted.
Page 97 Auxiliary is the memory used by the number of unique objects/records (or unique routes, i.e. the # of output records the 5620 SAM Cflowd Auxiliary produces in the IPDR files) in 5620 SAM Cflowd Auxiliary memory at any one time. And finally the interval size –...
Page 98 Number of aggregated output requisitions that are sent to the server every 60 seconds. Assumes transfer has sufficient bandwidth to complete in a timely manner. Packet loss may increase if communication between the 5620 SAM Cflowd Aux and target file server is interrupted ..............................................
Page 99: Security
S ecurity Overview Purpose This chapter provides general information about platform security for the 5620 SAM Contents Securing 5620 SAM Operating system installation for 5620 SAM workstations 5620 SAM software installation 5620 SAM network element communication 5620 SAM and firewalls...
Page 100 (p. 7-3) • Network Element connection configuration as described in “5620 SAM network element communication” (p. 7-4) • If installing RHEL, configure 5620 SAM to run at runlevel 3 as opposed to the default runlevel 5 ..............................................5620 SAM 3HE-09809-AAAG-TQZZA 13.0 R7...
Page 101 Hat, or Microsoft which will include security fixes as well as functional fixes. If a patch is found to be incompatible with 5620 SAM, the patch may need to be removed until a solution to the incompatibility is provided by Red Hat, Microsoft, or Alcatel-Lucent.
Page 102 5620 SAM and firewalls 5620 SAM and firewalls A firewall can be deployed to protect the 5620 SAM server from the managed network and to protect the server from the network hosting the 5620 SAM clients. The diagrams below illustrate this and show the communications services that are required through the firewalls.
Page 103 Security 5620 SAM and firewalls ..............................................Figure 7-1 Firewalls and 5620 SAM standalone deployments SNMP traps 5620 SAM Server Managed EJB/HTTP Network SNMP/SSH/ 5620 SAM Clients Telnet 5620 SAM Database 22668 Figure 7-2 Firewalls and 5620 SAM redundant deployments ftp/tftp...
Page 104 Security Port Information ..............................................Port Information Port Information The following table describes the listening ports on the various 5620 SAM Applications. Table 7-1 5620 SAM firewall requirements Default port Type Encryption Description 5620 SAM Server and 5620 SAM Auxiliary (Statistics and Call Trace)
Page 105 None. Internal system communications protocol (JBoss Naming Service -JNDI) This port is required to ensure the 5620 SAM GUI and OSS clients properly initialize with the 5620 SAM Server. When initially logging into the 5620 SAM Server, 5620 SAM GUI and OSS clients use this port to find the various services that are available.
Page 106 None. HTTP See port 8444 for secure This port provides an HTTP interface for 5620 SAM client. The communications. 5620 SAM Client uses this port to verify the existence of the server. 8086 None. HTTP See port 8445 for secure This port provides an HTTP interface to the WebDav Server for communications.
Page 107 SSL/TLS. Strong ciphers are clients to the WDSL 3GPP WebServices Integration Reference supported. Selection of CBC Points. This is a secure version of port 8980. Used only if 5620 and AES ciphers provided by SAM-O Clients are connecting via SSL.
Page 108 11800 Static Encryption Internal system communications protocol (JBoss Clustering) Ports from 32768 - Encryption provided by AES This port is required to ensure that redundant 5620 SAM Servers 65536 Cipher Algorithm with 128 can monitor each other. bit Cipher Strength.
Page 109 Cipher Strength. The number of required ports depends on the number of 5620 SAM Auxiliary workstations that are installed. Note that 5620 SAM can be configured to use a different port for this purpose. The procedure is available from Alcatel-Lucent Personnel.
Page 110 SSL/TLS. Strong ciphers are Auxiliary Server management interface. This is a secure version of supported. Selection of CBC port 9990. Used only if the 5620 SAM Cflowd Auxiliary Server is and AES ciphers provided by SSL secured. TLS are supported.
Page 111 Dynamic Encryption HTTPS Encryption provided by This port is required for the 5620 SAM Client to be able to SSL/TLS. Strong ciphers are communicate with the 5780 DSC. supported. Selection of CBC and AES ciphers provided by TLS are supported.
Page 112 None. 5620 SAM Database Proxy This port is used by the 5620 SAM Server to monitor disk usage on a remote 5620 SAM Database. When there are redundant databases, it is also allows the 5620 SAM Server to initiate database switchovers and failovers.
Page 113 FTP between the 5620 SAM Server and 5620 SAM Auxiliary Statistics Collector and the managed network FTP between the 5620 SAM Server and 5620 SAM Auxiliary Statistics Collector and the managed network 5620 SAM Server and 5620 SAM Auxiliary Statistics Collector will use FTP for several purposes.
Page 114 1024-65536. This data will be sent to the 5620 SAM Server on a port in the range of 1024-65536. Support for EPSV/EPRT ftp commands (commands that can replace PASV/PORT commands) must be enabled for connections to the 7x50 family of routers.
Page 115 IPv6 <base client install dir>/nms/sample/firewall/ip6tables_DelegateServer It is imperative that all rules are considered completely for the 5620 SAM systems to inter-operate correctly. The following tables will define the rules to be applied to each 5620 SAM workstation. Within the section there will be a number of conditions that indicate whether or not that particular table needs to be applied.
Page 116 > 1023 Managed Network > 1023 Server(s) Passive FTP ports for data transfer Table 7-5 SSH / SFTP / SCP Firewall rules for traffic between the 5620 SAM Server(s) and the managed network Protocol From port To port Notes Server(s)
Page 117 RADIUS Server For RADIUS authentication When there is a firewall at the interface that reaches the 5620 SAM Client(s) (NIC 3 on Figure 8-2, “Distributed 5620 SAM Server/Database deployment with multiple network interfaces” (p. 8-4) ) the following rules need to be applied.
Page 118 Corba 3GPP-compliant Client When there is a firewall configured, and there are redundant 5620 SAM Auxiliary workstation(s), the following rules need to be applied to the appropriate interface. If multiple interfaces are used for communication to the clients (GUI and OSS) and...
Page 119 Security Firewall and NAT rules ..............................................When a firewall and NAT are configured to the 5620 SAM Server at the SAM client interface (NIC 3 on Figure 8-2, “Distributed 5620 SAM Server/Database deployment with multiple network interfaces” (p. 8-4) ) the following rules need to be applied to allow the OSS clients to retrieve the logToFile accounting statistics information.
Page 120 Figure 8-2, “Distributed 5620 SAM Server/Database deployment with multiple network interfaces” (p. 8-4) ) and 5620 SAM Auxiliary Statistics / Call Trace Servers are configured, then the following rules need to be applied: Table 7-15 Firewall rules for traffic coming into the 5620 SAM Server(s) from the 5620 SAM Auxiliary Statistics / Call Trace Server(s).
Page 121 Figure 8-2, “Distributed 5620 SAM Server/Database deployment with multiple network interfaces” (p. 8-4) ), the following rules apply. Table 7-18 SNMP Firewall rules for traffic coming into the 5620 SAM Auxiliary Statistics Collector Server(s) from the Managed Network Protocol From port...
Page 122 Collector and the managed network” (p. 7-15) Note: FTP access is only required for the 5620 SAM Auxiliary Statistics Collector. Table 7-21 SNMP Firewall rules for traffic coming into the 5620 SAM Auxiliary Call Trace Server(s) from the Managed Network...
Page 123 7750 routers to 5620 SAM Cflowd Auxiliary Server. When there is a firewall at the interface that reaches the 5620 SAM Client(s) (NIC 3 on Figure 8-2, “Distributed 5620 SAM Server/Database deployment with multiple network interfaces” (p. 8-4) ), the following rules apply for FTP access to the 5620 SAM Auxiliary by the OSS Client.
Page 124 (p. 7-15) When there is a firewall at the interface that communicates with the 5620 SAM Servers, the following rules apply for inter process communication. If multiple interfaces are used for 5620 SAM Server communication to the clients (GUI and OSS) and auxiliary servers,...
Page 125 Server(s) > 32768 Auxiliary Server(s) When there is a firewall at the interface that reaches the 5620 SAM Client(s) (NIC 3 on Figure 8-2, “Distributed 5620 SAM Server/Database deployment with multiple network interfaces” (p. 8-4) ) and NAT is used on the 5620 SAM Auxiliary Server(s), the following rules apply to allow the OSS clients to collect the logToFile accounting statistics files.
Page 126 Security Firewall and NAT rules ..............................................Table 7-28 Additional Firewall rules required to allow services on the 5620 SAM client(s) to communicate with the 5620 SAM Auxiliary(s) if NAT is used on the Auxiliary Server(s). (continued) Protocol From port To port...
Page 127 Ensure that ICMP protocol traffic from the 5620 SAM Server workstation(s) can reach the 5620 SAM delegate workstation. 5620 SAM Client to managed network communications Apply the following changes to the connection between the 5620 SAM Client and the managed network. Note that all connections are bi-directional. Table 7-33...
Page 128 Security Firewall and NAT rules ..............................................Table 7-35 Firewall rules for traffic between the 5620 SAM Client and the eNodeB NEM (continued) Protocol From port To port Notes 5620 SAM Client(s) Managed Network NetConf over SSH Table 7-36 Firewall rules for traffic between the 5620 SAM Client and GNEs...
Page 129 Security Firewall and NAT rules ..............................................Table 7-38 Firewall rules for traffic between the 5620 SAM Client (NEtO) and 9500MPR (MSS-1C / MPR-e) (continued) Protocol From port To port Notes 5620 SAM Client 11500 Managed Network Equipment View (GUI) Table 7-39...
Page 130 Security Firewall and NAT rules ............................................................................................7-32 5620 SAM 3HE-09809-AAAG-TQZZA 13.0 R7 Issue 1 December 2015...
Page 131: Deploying The 5620 Sam With Multiple Network Interfaces/Ip Addresses
Overview Purpose This chapter provides general information about 5620 SAM deployments with multiple network interfaces and IP addresses. Contents Deploying the 5620 SAM with multiple network interfaces/IP addresses 5620 SAM Server multiple IP addresses deployment scenarios...
Page 132 It is a security requirement that all IP communications from a 5620 SAM Auxiliary Collector to the 5620 SAM Main server use only one IP address. This IP Address must be the same IP address as the Auxiliary Collector IP address configured when installing the Main Server.
Page 133 Deploying the 5620 SAM with multiple network Deploying the 5620 SAM with multiple network interfaces/IP addresses interfaces/IP addresses ..............................................Figure 8-1 Collocated 5620 SAM Server/Database deployment with multiple network interfaces bge0 5620 SAM Server/ 5620 SAM Clients Database bge1 Managed...
Page 134 Figure 8-2, “Distributed 5620 SAM Server/Database deployment with multiple network interfaces” (p. 8-4) illustrates a distributed, redundant 5620 SAM deployment where the 5620 SAM components are configured to actively use more than one network interface..............................................5620 SAM 3HE-09809-AAAG-TQZZA 13.0 R7...
Page 135: 5620 Sam Server Multiple Ip Addresses Deployment Scenarios
5620 SAM Server must be used for both communication types. • One network interface can be used to service the requirements of the 5620 SAM clients (GUIs and OSS) (NIC 3 on Figure 8-2, “Distributed 5620 SAM Server/Database deployment with multiple network interfaces”...
Page 136: 5620 Sam Auxiliary Statistics Collector Multiple Ip Addresses Deployment Scenarios
Collector. OSS Clients will use this IP address to retrieve the logToFile statistics collection data from the 5620 SAM Auxiliary Statistics Collector. • One network interface can be used to communicate with the 5620 SAM Server, 5620 SAM Database, 5620 SAM Auxiliary Database cluster as well as any redundant 5620 SAM components should they be present (NIC 1 on Figure 8-2, “Distributed 5620...
Page 137: 5620 Sam Auxiliary Call Trace Collector Multiple Ip Addresses Deployment Scenarios
IP connectivity to the 5620 SAM Server peer. If different interfaces are used for communication to the clients and/or auxiliary servers, the IP connectivity required to the 5620 SAM Server peer could be through the client interface (NIC 3 on Figure 8-2, “Distributed 5620 SAM Server/Database deployment with multiple network interfaces”...
Page 138: 5620 Sam Auxiliary Cflowd Collector Multiple Ip Addresses Deployment Scenarios
IP connectivity to the 5620 SAM Server peer. If different interfaces are used for communication to the clients and/or auxiliary servers, the IP connectivity required to the 5620 SAM Server peer could be through the client interface (NIC 3 on Figure 8-2, “Distributed 5620 SAM Server/Database deployment with multiple network interfaces”...
Page 139: Using Network Address Translation
IP connectivity to the 5620 SAM Server peer. If different interfaces are used for communication to the clients and/or auxiliary servers, the IP connectivity required to the 5620 SAM Server peer could be through the client interface (NIC 3 on Figure 8-2, “Distributed 5620 SAM Server/Database deployment with multiple network interfaces”...
Page 140 SAM Clients must communicate to the SAM Server through the SAM Server public IP address. The 5620 SAM Auxiliary will need to be able to connect to the public IP address of the 5620 SAM server.
Page 141 Deploying the 5620 SAM with multiple network Using Network Address Translation interfaces/IP addresses ..............................................Figure 8-4 5620 SAM Server deployment using NAT with IP Address communication Routing loopback required for SAM Server Private Public Network Network 5620 SAM Server 5620 SAM Client...
Page 142 Using Network Address Translation interfaces/IP addresses ..............................................The figure below illustrates a deployment of 5620 SAM where NAT is used between the 5620 SAM complex, 5620 SAM clients, and the managed network. Figure 8-6 5620 SAM deployment with NAT 5620 SAM Client...
Page 143: Configuring 5620 Sam Server To Utilize Multiple Network Interfaces
Use of hostnames for the 5620 SAM Client There are a number of situations where it is necessary for the 5620 SAM Client to be configured to use a hostname rather than a fixed IP address to reach the 5620 SAM Server.
Page 144 Deploying the 5620 SAM with multiple network Use of hostnames for the 5620 SAM Client interfaces/IP addresses ............................................................................................8-14 5620 SAM 3HE-09809-AAAG-TQZZA 13.0 R7 Issue 1 December 2015...

Alcatel-Lucent 5620 Planning Manual

Quick Links

Related Manuals for Alcatel-Lucent 5620

Summary of Contents for Alcatel-Lucent 5620

Table of Contents