Alcatel-Lucent 5620 Planning Manual Download Page 120

Page: 120 / 144

Table 7-14

Firewall rules for setups with redundant 5620 SAM Servers.
(continued)

Protocol

From port

To port

TCP

Any

Servers

9010

Servers

TCP

Any

Servers

11800

Servers

TCP

11800

Servers

Any

Servers

TCP

Any

Servers

12010

Servers

TCP

12010

Servers

Any

Servers

TCP

Any

Servers

12300-12307

Servers

TCP

12300-12307

Servers

Any

Servers

TCP

> 32768

Servers

> 32768

Servers

When there is a firewall at the SAM management interface (NIC 1 on

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).

Protocol

From port

To port

TCP

Any

Auxiliary Server(s)

12300-12307

Server(s)

TCP

12300-12307

Auxiliary Server(s)

Any

Server(s)

TCP

Any

Auxiliary Server(s)

12800

Server(s)

TCP

12800

Auxiliary Server(s)

Any

Server(s)

When there is a firewall at the SAM management interface (NIC 1 on

Figure 8-2,

“Distributed 5620 SAM Server/Database deployment with multiple network interfaces”
(p. 8-4)

) and NAT is configured, then the following rules need to be applied. Services

require the use of public addresses.

5620 SAM Database firewall and NAT rules

When there is a firewall at the interface that reaches the SAM management network (NIC
1 on

Figure 8-2, “Distributed 5620 SAM Server/Database deployment with multiple

network interfaces” (p. 8-4)

), the following rules apply.

Security

Firewall and NAT rules

....................................................................................................................................................................................................................................

7-22

5620 SAM

3HE-09809-AAAG-TQZZA 13.0 R7

Issue 1

December 2015

Summary of Contents for 5620

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: ...lcatel 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 This document may contain information regarding the use and installation of non Alcatel Lucent pr...

Page 3: ...620 SAM 1 15 1 15 2 Operating systems specifications Overview 2 1 2 1 Operating systems specifications 2 1 2 1 5620 SAM Client or Client Delegate software requirements 2 3 2 3 3 Platform requirements Overview 3 1 3 1 Hardware platform requirements overview 3 2 3 2 Hardware platform and resource requirements using Virtualization 3 3 3 3 Minimum hardware platform requirements 3 6 3 6 5620 SAM O 3GPP...

Page 4: ...5 3 Bandwidth requirements for distributed 5620 SAM installations 5 3 5 3 Bandwidth requirements for 5620 SAM GUI Clients 5 9 5 9 Bandwidth requirements for displaying 5620 SAM GUI Clients on X displays 5 9 5 9 Bandwidth requirements for 5620 SAM O OSS Clients 5 10 5 10 Bandwidth requirements for the 5620 SAM Auxiliary Statistics Collector workstation 5 10 5 10 Bandwidth requirements for the 5620 ...

Page 5: ...for scheduled tests STM Scaling guidelines for scheduled tests STM 6 16 6 16 Scaling guidelines for Cflowd statistics collection Scaling guidelines for Cflowd statistics collection 6 22 6 22 7 Security Overview 7 1 7 1 Securing 5620 SAM 7 2 7 2 Operating system installation for 5620 SAM workstations 7 3 7 3 5620 SAM software installation 7 3 7 3 5620 SAM network element communication 7 4 7 4 5620 ...

Page 6: ...tistics Collector multiple IP addresses deployment scenarios 8 6 8 6 5620 SAM Auxiliary Call Trace Collector multiple IP addresses deployment scenarios 8 7 8 7 5620 SAM Auxiliary Cflowd Collector multiple IP addresses deployment scenarios 8 8 8 8 Using Network Address Translation 8 9 8 9 Configuring 5620 SAM Server to utilize multiple network interfaces 8 13 8 13 Use of hostnames for the 5620 SAM ...

Page 7: ...ould be consulted for clarification when uncertainty exists The 5620 SAM Planning Guide details the following aspects of the Alcatel Lucent 5620 SAM product Product deployment overview Supported operating systems specifications Hardware platform requirements Network requirements Scaling guidelines Workstation configuration Firewall information Intended audience This document is intended for networ...

Page 8: ...rmation 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 https infoproducts alcatel lucent com cgi bin doc_welc pl Technical support http support alcatel lucent com How to comment ...

Page 9: ...re 5620 SAM architecture Seven types of platforms can be present in a 5620 SAM deployment 5620 SAM GUI Client workstation s 5620 SAM GUI Client Delegate workstation s 5620 SAM Server 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 D...

Page 10: ...ter of three separate instances and can tolerate a single server failure with no data loss A 5620 SAM Auxiliary Statistics Collector must be installed on an independent workstation and can only be configured in a 5620 SAM distributed deployment A 5620 SAM Auxiliary Call Trace Collector must be installed on an independent workstation to collect the call trace information from WMM vMM network elemen...

Page 11: ...yments with the 3GPP OSS interface EMS integration with 5620 SAM 5620 SAM deployments using SAML SSO Dual Stack between SAM components including clients A network element can only be managed by one 5620 SAM standalone or redundant deployment Having multiple 5620 SAM deployments managing the same network element is not supported and will cause unexpected behavior The following illustrates a typical...

Page 12: ...e active 5620 SAM Auxiliary Statistics Collectors or it could be configured redundant and there can be one or two 5620 SAM Auxiliary Call Trace Collectors collecting call trace data from the network Figure 1 2 5620 SAM standalone deployment distributed 5620 SAM Server and 5620 SAM Database configuration 22674 5620 SAM Clients Managed Network 5620 SAM Server 5620 SAM Database Figure 1 3 5620 SAM st...

Page 13: ...ed in a cluster of three instances Figure 1 4 5620 SAM standalone deployment distributed 5620 SAM Server and 5620 SAM Database configuration and 5620 SAM Auxiliary Collectors 22672 5620 SAM Clients Managed Network 5620 SAM Database 5620 SAM Server 5620 SAM Auxiliary Statistics Collector 5620 SAM Auxiliary Call Trace Collector s Figure 1 5 5620 SAM standalone deployment distributed 5620 SAM Server ...

Page 14: ...620 SAM Auxiliary Statistics Collector workstation should be used when statistics collection is expected to exceed the capacity of the 5620 SAM Server Refer to Chapter 3 Platform requirements for scalability details of the 5620 SAM Server and dimensioning of the 5620 SAM Auxiliary Statistics Collector workstation The 5620 SAM Auxiliary Statistics Collector can be configured as preferred or reserve...

Page 15: ...ations in the 5620 SAM Auxiliary Call Trace Collector redundant pair will collect the call trace information from the network elements at any given time and the call trace information is synchronized between the Preferred and Reserved pair of workstations Information on the redundancy model of the 5620 SAM Auxiliary Call Trace Collector can be found in Redundancy architecture p 1 10 The 5620 SAM A...

Page 16: ... 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 however each user must run the client with a unique UNIX id Information on dimensioning the 5620 SAM Client Delegate platform is given in Minimum har...

Page 17: ...iguration Oracle s official support position for running Oracle Database 12c embedded within 5620 SAM on VMware hosted virtual environments is described in Oracle Support Note 249212 1 Oracle will only provide support for issues that either are known to occur on the native Operating System or can be demonstrated not to be as a result of running on VMware In addition VMware has a public statement c...

Page 18: ... SAM Server and 5620 SAM Database collocated configuration 5620 SAM Server and 5620 SAM Database distributed configuration The following illustrates a 5620 SAM redundant installation when the 5620 SAM Server and 5620 SAM Database components are installed in a collocated configuration The following illustrates a 5620 SAM redundant installation when the 5620 SAM Server and 5620 SAM Database componen...

Page 19: ...hen collecting statistics using the 5620 SAM Auxiliary Database latency between all 5620 SAM workstations including redundant servers except for Clients and Client Delegates must be less than one millisecond When Call Trace information is being collected from WMM network elements in customer networks a 5620 SAM Auxiliary Call Trace Collector must be used The 5620 SAM Auxiliary Call Trace Collector...

Page 20: ...or is dependent and configured on the 5620 SAM Server that is active In both geographic locations the 5620 SAM Server is configured such that the 5620 SAM Auxiliary Statistics Collectors in its geographic location is preferred The 5620 SAM Auxiliary Collector in the opposite geographic location is configured to be reserved In this scenario if the 5620 SAM Auxiliary Collector for the active 5620 SA...

Page 21: ... the Active Server Reserved for the Standby Server 5620 SAM Auxiliary Call Trace Collector s Preferred for the Standby Server Reserved for the Active Server 5620 SAM Server Standby 5620 SAM Auxiliary Preferred for the Standby Server Reserved for the Active Server 5620 SAM Server Active 5620 SAM Auxiliary Statistics Collector Preferred for the Active Server Reserved for the Standby Server Rsync of ...

Page 22: ...all Trace Collector s Preferred for the Active Server Reserved for the Standby Server 5620 SAM Auxiliary Call Trace Collector s Preferred for the Standby Server Reserved for the Active Server 5620 SAM Server Standby 5620 SAM Auxiliary Statistics Collector Reserved 5620 SAM Server Active 5620 SAM Auxiliary Statistics Collector Preferred for the Active Server Reserved for the Standby Server Rsync of...

Page 23: ...the active 5620 SAM Server Database must be installed or upgraded before the machine that will initially be used as the standby The workstations hosting the 5620 SAM software should be connected in a way to prevent a single physical failure from isolating the two workstations from each other Workstations running the 5620 SAM Server Database software must be configured to perform name service datab...

Page 24: ...e same versions and patch levels as the 5620 SAM Server and 5620 SAM Database workstations If collecting statistics using the 5620 SAM Auxiliary Database the operating systems installed on the 5620 SAM Auxiliary Database workstations must be of the same versions and patch levels as the 5620 SAM Server and 5620 SAM Database workstations 5620 SAM Auxiliary Collectors are intended to be on the same h...

Page 25: ...atabase 5620 SAM Analytics Server 5620 SAM Database 5620 SAM Client Delegate and 5620 SAM Client The 5620 SAM Client is also supported on Red Hat Enterprise Linux 6 Server Edition x86 Previous releases or other variants of Red Hat and other Linux variants are not supported 5620 SAM Release 13 0 R7 supports the following base RHEL versions RHEL Server 6 x86 64 x86 Update 2 6 2 RHEL Server 6 x86 64 ...

Page 26: ...M Client Delegate and 5620 SAM Database workstation RHEL operating system must be installed in English 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 Alcatel Lucent recommends the installation of any OS driver or firmware updates that the hardware vendor advises f...

Page 27: ...tware 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 The 5620 SAM web browser installer launcher requires Oracle Java version 7 0 or greater for the system JRE on all platforms The system JRE needs to be already ins...

Page 28: ... running amongst all clients connected to a Client Delegate at any time To consolidate 5620 SAM Client UIs to a single server when using the NEtO element manager a virtualized solution should be used instead with each 5620 SAM Client residing in a separate VM Operating systems specifications 5620 SAM Client or Client Delegate software requirements 2 4 5620 SAM 3HE 09809 AAAG TQZZA 13 0 R7 Issue 1 ...

Page 29: ...ation performs adequately Contents Hardware platform requirements overview 3 2 Hardware platform and resource requirements using Virtualization 3 3 Minimum hardware platform requirements 3 6 5620 SAM O 3GPP Interface 3 14 5620 SAM GUI Client platform requirements 3 15 Determining platform requirements for larger networks 3 16 Storage considerations 3 17 5620 SAM 3HE 09809 AAAG TQZZA 13 0 R7 Issue ...

Page 30: ...tions Alcatel Lucent reserves the right to remove any application from workstations running 5620 SAM components that are suspected of causing issues The hardware platforms do not support running applications that are not specifically identified for that platform For instance a 5620 SAM client is not supported on the hardware platform for a distributed or collocated 5620 SAM Server as there is a si...

Page 31: ...opriately to ensure that other Guest OSs on the same physical server do not negatively impact the operation of 5620 SAM Virtualized installations of 5620 SAM are server vendor agnostic but must meet specific hardware criteria and performance targets to be used with 5620 SAM Server class hardware must be used not desktops Processor support is limited to Intel and AMD based x86 CPUs with a minimum C...

Page 32: ...pon CPU cores and not threads If threaded CPUs are used the number of vCPUs required should be multiplied by the number of threads per physical CPU core and assigned to the Virtual Machine Virtual Machine Version 8 9 or 10 must be used The disk must be Thick Provisioned with Eager Zero set The SCSI controller must be set to VMware Paravirtual and the Disk Provisioning must be Thick Provision Eager...

Page 33: ... 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 Snapshots should be kept for the least amount of time possible Snapshot deletion can take many hours and will pause the VM several times SAM Database failover will occur when VMs are reverted to snapshots requiring a re instantiation of the Stan...

Page 34: ...ur tables list the minimum hardware platform requirements for deployments of 5620 SAM Release 13 0 product on the RHEL x86 64 operating systems Table 3 4 5620 SAM Virtual Machine minimum configuration p 3 8 and Table 3 5 5620 SAM Virtual Machine minimum configuration with auxiliary p 3 9 list the minimum hardware requirements for deployments of 5620 SAM using VMware vSphere ESXi or RHEL KVM in lab...

Page 35: ...5620 SAM RHEL Server x86 64 minimum distributed platforms For networks not exceeding 1875 MDAs Maximum of 5 000 GNEs 5 simultaneous 5620 SAM Clients GUI or OSS 2000 elemental STM tests every 10 minutes 150 000 performance or 200 000 accounting statistics records every 15 minutes 150 000 TCAs OR 1275 MDAs Maximum of 5 000 GNEs 25 simultaneous 5620 SAM Clients GUI or OSS 2000 elemental STM tests eve...

Page 36: ...t least 146 GB in size is required for performance and storage capacity Example platform HP Proliant DL380p Gen8 Server or HP DL380 G7 Server Virtual Machine hardware configurations for Labs Table 3 4 5620 SAM Virtual Machine minimum configuration For networks not exceeding 675 MDAs 1000 GNEs 5 simultaneous 5620 SAM Clients GUI or OSS 1000 elemental STM tests every 10 minutes 50 000 performance or...

Page 37: ...RAM minimum 1 SAS 10K RPM disk drive of at least 146 GB each in size 5620 SAM Database 3 x86 CPU Cores minimum 2 4GHz 16 GB RAM minimum 2 SAS 10K RPM disk drives of at least 146 GB in size is required 5620 SAM Auxiliary Statistics and or Call Trace 3 x86 CPU Cores minimum 2 4GHz 8 GB RAM minimum 1 SAS 10K RPM disk drive of at least 146 GB in size is required 5620 SAM Auxiliary Cflowd 4 x86 CPU Cor...

Page 38: ...ation Scaling limits for collocated configurations Collocated configurations have been capped at the maximums described in the following table 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 achie...

Page 39: ...DL380p Gen8 Proliant DL380 G7 Table 3 9 5620 SAM Auxiliary platforms VM Architecture Supported 5620 SAM Auxiliary type Configuration VMware KVM Statistics Collector 4 x86 CPU Cores minimum 2 4GHz 8 GB RAM minimum 16GB RAM is recommended 500GB disk space I O throughput and latency as provided in 5620 SAM Sizing response VMware KVM Call Trace Collector 4 x86 CPU Cores minimum 2 4GHz 16 GB RAM minimu...

Page 40: ...Gen9 VMware KVM 4 x86 CPU Cores minimum 2 4GHz 24 GB RAM minimum 200GB disk space I O throughput and latency as provided in the 5620 SAM Sizing response Platform requirements for 5620 SAM Client Delegate workstations 5620 SAM allows multiple GUI clients to be installed on a single HP x86 workstation running RHEL 6 Server x86 64 or specific versions of Windows This option enables customers to launc...

Page 41: ...20 SAM Client Delegate resource requirements p 3 13 describes resource requirements for this type of workstation Table 3 12 Minimum 5620 SAM Client Delegate resource requirements Architecture Configuration HP x86 4 x86 CPU Cores minimum 2 0GHz 16 GB RAM minimum 24 GB for networks with greater than 15K NEs 1 SAS 10K RPM disk drives 146GB in size Example platform Proliant DL380p Gen8 VMware KVM 4 x8...

Page 42: ... Citrix Server XenApp Version 6 5 Windows 2012R2 Citrix Server XenApp Version 7 6 Windows 7 Citrix Client Receiver Version 3 4 0 29577 The following Citrix software has been tested with the RHEL Client Delegate Citrix Server XenApp Presentation Server 4 0 with Feature Pack 1 and Patch PSE400SOLX066 for Solaris x86 Citrix Client Version 8 50 117422 for Solaris x86 Citrix Client Receiver Version 3 4...

Page 43: ... Support Microsoft Windows Support NEM eNodeB Supported Supported NEtO 9500 MPR Not supported Supported MI 9471 WMM Not supported Supported PSS WebUI 1830 PSS Supported Supported The following table provides the minimum requirement for the hardware that will host 5620 SAM GUI client software Additional memory and disk resources will be required by the Operating System Table 3 15 5620 SAM GUI hardw...

Page 44: ...y resolution for java GUI 1280 720 72ppi Display resolution for Web Apps minimum 1920 1080 72ppi Display resolution for Web Apps recommended 1 CPU Core 2 GHz or higher 1 GB dedicated RAM 1 5 GB for networks with greater than 15K NEs 1 GB available disk space 1280 1024 Display resolution for java GUI 1280 720 72ppi Display resolution for Web Apps minimum 1920 1080 72ppi Display resolution for Web A...

Page 45: ...eck the Scheduled Polling Stats Processed Periodic and the Accounting Stats Processed Periodic columns for the performance and accounting stats that your system is currently processing within the time interval defined by the collection policy 15 minutes by default Storage considerations Storage considerations This section provides information on configuring workstations that will host 5620 SAM sof...

Page 46: ...orted Alcatel Lucent will provide disk layout and configuration details for customers requiring a Storage Array or layouts not specified in the 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 A RAID 0 stripe s...

Page 47: ...quirements Table 3 17 SAN Mount Points and performance requirements Mount Point Read MB s Write MB s opt 5620sam SAM Server 9 32 opt 5620sam SAM Database 3 4 opt 5620sam Statistics Auxiliary 24 150 opt 5620sam Cflowd Auxiliary 4 6 opt 5620sam server xml_output 32 32 opt 5620sam auxserver xml_output 113 113 opt 5620sam dbbackup 69 112 opt 5620sam samdb tablespace 300 88 opt 5620sam samdb redolog 58...

Page 48: ...20 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 If 5620 SAM has not yet been installed the utility can be obtained from Alcatel Lucent or from the 5620 SAM software package Executing the utility with the h flag will present the user with a help menu explaining different options and prese...

Page 49: ...pace 158 8 1 0 opt 5620sam server nms log 1 1 1 0 opt 5620sam samdb archivelog 14 38 1 0 opt 5620sam nebackup 6 6 1 0 The 5620 SAM 5650 CPAM Installation and Upgrade Guide should be consulted for recommended partition sizes Platform requirements Storage considerations 5620 SAM 3HE 09809 AAAG TQZZA 13 0 R7 Issue 1 December 2015 3 21 ...

Page 50: ...Platform requirements Storage considerations 3 22 5620 SAM 3HE 09809 AAAG TQZZA 13 0 R7 Issue 1 December 2015 ...

Page 51: ...quence verification 4 3 Scheduled SNMP MIB polling 4 3 Network outages 4 4 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 SNMP connectivity verification SNMP trap...

Page 52: ...ity checks using ping must be scheduled through the default policy SNMP connectivity verification SNMP connectivity verification 5620 SAM performs an SNMP communication check every 4 minutes If 5620 SAM can not communicate via SNMP with a network element 5620 SAM will raise a communications alarm against that network element 5620 SAM will also color the network element red on the map to indicate t...

Page 53: ...l network elements and verifies the trap sequence number every 4 minutes 5620 SAM compares that sequence number with the sequence number of the last trap it received from that network element 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 ele...

Page 54: ...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 This will cause intermediate state change alarms to not be reflected in 5620 SAM during the network outage NE mainten...

Page 55: ...g 5620 SAM GUI Clients on X displays 5 9 Bandwidth requirements for 5620 SAM O OSS Clients 5 10 Bandwidth requirements for the 5620 SAM Auxiliary Statistics Collector workstation 5 10 Bandwidth requirements for the 5620 SAM Call Trace Collector workstation 5 11 Bandwidth requirements for the 5620 SAM Auxiliary Cflowd Collector workstation 5 11 5620 SAM bandwidth requirements for communicating with...

Page 56: ...e 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 See Chapter 8 Deploying the 5620 SAM with multiple network interfaces IP addresses for information on configuring t...

Page 57: ...g statistics bandwidth requirements 5620 SAM Client GUI 1 Mbps 5620 SAM O Client The bandwidth will depend on the OSS application 1 Mbps Between primary and standby 5620 SAM Server Database workstation NOTE When network element database backup synchronization is enabled the bandwidth requirement between the 5620 SAM Servers will vary significantly depending on the size of the network element backu...

Page 58: ... is enabled 6 Mbps sustained 15 25 Mbps during re instantiation or database backup synchronization 3 Mbps minimum Table 5 3 Additional bandwidth requirements for file accounting STM results collection Bandwidth requirements for installations collecting file accounting STM results using the logToFile method only Increased Bandwidth per 50 000 file accounting STM records 5620 SAM Server to a 5620 SA...

Page 59: ...s collection Bandwidth requirements for installations collecting accounting statistics Additional bandwidth per 200 000 accounting statistics records 5620 SAM Server to a 5620 SAM O O Client if using findToFile OR 5620 SAM Server to 5620 SAM O Client if using an uncompressed registerLogToFile 5620 SAM Auxiliary Statistics Collector is NOT installed OR 5620 SAM Auxiliary Statistics Collector to 562...

Page 60: ...agement statistics collection Bandwidth requirements for installations collecting performance and optical performance management statistics Increased Bandwidth per 200 000 performance and optical performance management statistics records 5620 SAM Server to a 5620 SAM O Client if using findToFile OR 5620 SAM Server to 5620 SAM O Client if using an uncompressed registerLogToFile 5620 SAM Auxiliary S...

Page 61: ...SAM Auxiliary Statistics Collector is installed to collect statistics using the 5620 SAM Database the bandwidth requirements between two geographic locations will need to reflect the state where a 5620 SAM Auxiliary Statistics Collector in geographic location A may send information to the active 5620 SAM Server in geographic location B which will in turn send information back to the 5620 SAM Datab...

Page 62: ...significantly by the use of the 5620 SAM Auxiliary Database for statistics collection The 5620 SAM Auxiliary Database Server requires a minimum of two network interfaces one for communication to the 5620 SAM management complex and one for internal data communication between each of the 5620 SAM Auxiliary Database servers in the cluster The interface for internal data communication needs to be dedi...

Page 63: ... GUI Clients on X displays Bandwidth requirements for displaying 5620 SAM GUI Clients on X displays 5620 SAM GUI Clients can be displayed remotely on terminals using the X11 protocol for graphical displays In these cases it is important to ensure the bandwidth availability between the workstation running the 5620 SAM Client and the host displaying the 5620 SAM Client be at least 1024 Kbps Also it ...

Page 64: ...er to reduce bandwidth requirements and the possible effects of network latency In an environment where network changes are infrequent it is possible to successfully operate an application using the 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 situ...

Page 65: ...SS 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 Bandwidth requirements for the 5620 SAM Auxiliary Cflowd Collector workstation Bandwidth requirements for the 5620 SAM Auxiliary Cflowd Collector workstation The main factors impacting communic...

Page 66: ...iles are being transferred Use the information on the left to calculate the amount of data generated for the expected Statistics Use this to calculate the time to transfer at a given bandwidth The total time must be less than 50 of collection interval For example if 1GB of IPDR files are expected per interval and the collection interval is 5min a 45 Mbps connection will take 3min 2sec to transfer ...

Page 67: ...s that 5620 SAM can fully discover or resynchronize all of the objects contained in the network element within a reasonable amount of time usually no more than a few minutes for a densely populated network element The following are the main operations that result in significant amounts of information being exchanged between 5620 SAM and the network elements These factors are therefore the principa...

Page 68: ...ween 5620 SAM and the network element is less than half of the amount of data transferred during the network element discovery Provisioning of services and deployment of configuration changes When network elements are configured or when services are provisioned via the 5620 SAM GUI or via application using the 5620 SAM O interface a small quantity of network bandwidth is utilized The amount of dat...

Page 69: ... on the topology of the infrastructure that is used to carry the management traffic From 5620 SAM s perspective there must be sufficient bandwidth as per Table 5 12 5620 SAM Server to network bandwidth requirements p 5 12 between itself and each of the network elements that is under management In cases where the management traffic is carried over physical point to point links between the 5620 SAM ...

Page 70: ...abase Auxiliary must be no longer than 1 ms otherwise overall 5620 SAM performance will be significantly impacted Since SNMP communication to a single Network Element is synchronous the impact of latency is directly related to the number of SNMP gets and responses Operations to a Network Element with a round trip latency of 50 ms will have the network transmission time increase by ten times compar...

Page 71: ...bling the DB Alignment feature within 5620 SAM Optimizing throughput between 5620 SAM workstations In high speed high latency networks the TCP socket buffer size controls the maximum network throughput that can be achieved If the TCP socket buffer is too small it will limit the network throughput despite the fact that the available bandwidth might support much higher transfer rates Adjusting the T...

Page 72: ... considerations This section describes network reliability considerations Reliability between 5620 SAM components The 5620 SAM requires reliable network communications between all the SAM Components 5620 SAM Servers 5620 SAM Databases 5620 SAM Auxiliaries 5620 SAM Auxiliary Databases 5620 SAM Analytics Server 5620 SAM GUI Clients and 5620 SAM Client Delegate Server 5620 SAM OSS Clients The perform...

Page 73: ... retrieval possibly to the point where statistics collection will be incomplete CLI session operation NE backup retrieval and software download performance The following example highlights the significant impact of lost packets It only considers the SNMP communication times with one network element With the default mediation policy configured with an SNMP retry time out of 10 seconds and an averag...

Page 74: ...ment tools to be configured the MME MI tool and the Client Their management includes communication directly from the 5620 SAM Client to the 9471 WMM platforms The eNodeB NEM is installed along with the 5620 SAM Client and communicates with the eNodeB elements in the network through a UDP proxy configured on the 5620 SAM Server eliminating the need for direct communication between the network eleme...

Page 75: ...ents 6 6 OSS client limits 6 6 5620 SAM OSS Clients using JMS 6 6 5620 SAM 3GPP OSS Client 6 7 Scaling guidelines for statistics collection 6 8 Statistics collection 6 8 Scaling guidelines for scheduled tests STM 6 16 Scaling guidelines for scheduled tests STM 6 16 Scaling guidelines for Cflowd statistics collection 6 22 Scaling guidelines for Cflowd statistics collection 6 22 5620 SAM 3HE 09809 A...

Page 76: ... Alcatel Lucent personnel to ensure you have the correct platform and configuration for your network size Table 6 1 5620 SAM Release 13 0 R7 scalability limits Attribute of managed network Scaling Limit Maximum number of managed MDAs 60 000 Maximum number of Network Elements 50 000 Maximum number of GNEs1 50 000 Maximum number of managed services 4 000 000 Maximum number of optical transport servi...

Page 77: ... size of a network the number of deployed or expected MDAs as opposed to the capacity of each router must be calculated Table 6 2 Network element maximums and equivalency Network element Type Maximum number of network elements supported MDA equivalency 7750 7450 7710 50 000 1 MDA 1 MDA1 2 7705 50 000 50 000 7210 50 000 50 000 OMNISwitch 6250 6400 6450 6850 6855 each shelf in the stackable chassis ...

Page 78: ... 5620 SAM Performance Targets 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 network activity user OSS activity database activity network size latency Table 6 3 5620 SAM Release 13 0 Performance T...

Page 79: ...eate 1 VPLS service 6 sites 1 SAP site 30 circuits fully meshed 10 seconds Average time to configure 100 VPLS services on 3 sites using one SAP 16 minutes Average time to add 1 IES interface to an existing service 1 5 seconds Average time to create 1 static route on a 7750 SR 0 6 seconds Average time to create 1 MAC ACL filter 0 8 seconds Average time to create 1 GRE SDP 0 75 seconds Average time ...

Page 80: ...imum message rate comparable to non durable clients Network latency between the 5620 SAM Server and a 5620 SAM OSS Client will reduce the JMS message rate For durable JMS clients the Duplicate OK method will allow for a higher message rate than the Auto Acknowledge method Refer to the 5620 SAM O OSS Interface Developer Guide for more information 5620 SAM is also able to deliver hundreds of message...

Page 81: ...AM Server and a 5620 SAM 3GPP OSS Client will reduce the message rate Table 6 5 3GPP OSS JMS messaging rates CORBA messaging Roundtrip latency from the OSS Client to the 5620 SAM Server 0ms 20ms 40ms 3GPP OSS connection messages s 74 68 53 Scaling Scaling guidelines for 5620 SAM OSS Clients 5620 SAM 3GPP OSS Client 5620 SAM 3HE 09809 AAAG TQZZA 13 0 R7 Issue 1 December 2015 6 7 ...

Page 82: ... 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 Statistics Item An individual statistics counter such as RxOctets or TxFrames Statistics Record A collection of statistics items which is retrieved from the router and stored in the 5620 SAM database as an atomic ...

Page 83: ...nificantly on the number of CPU Cores available to the 5620 SAM Server or Auxiliary Statistics collector software The tables below show the maximum number of performance statistics that can be retrieved and processed by the 5620 SAM server and the 5620 SAM Auxiliary Statistics Collector every 15 minutes Table 6 6 Maximum number of performance statistics records processed by a 5620 SAM Server Numbe...

Page 84: ...cts the maximum number of performance statistics records that can be collected from one network element in a 15 minute interval would be 6000 records 66 of 900 seconds divided by 100 ms latency Accounting statistics Refer to the 5620 SAM Statistics Management Guide to find the steps required to configure 5620 SAM to retrieve and process accounting statistics The quantity of resources which are all...

Page 85: ...tatistics records processed by a 5620 SAM Statistics Auxiliary Number of Active Auxiliary Statistics Collectors Maximum number of accounting statistics records per 15 minute interval Statistics collection with SAM Database Statistics collection with Auxiliary Database logToFile only 8 CPU Cores 16GB RAM 12 CPU Cores 24GB RAM 12 CPU Cores 32GB RAM 12 CPU Cores 24GB RAM 1 10 000 000 10 000 000 20 00...

Page 86: ...ver 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 Scaling of Application Assurance collection is related to the number of objects configured for collection as opposed to the number of records collected per interval The following tables provide the maximum number of application assu...

Page 87: ...ng records than it can process in the specified retrieval period the extra statistics will not be retrieved from the network Exporting performance and accounting statistics records There are two methods to export accounting and performance statistics from 5620 SAM registerLogToFile and findToFile The registerLogToFile method is the preferred method and is required for situations where more than 40...

Page 88: ...M can collect performance application assurance and accounting statistics records simultaneously 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 st...

Page 89: ...low shows the different retention rates that are achievable depending upon the collection rate and statistic type Table 6 13 Maximum statistics interval retention SAM Database Statistics Type Total Number of statistics records to be stored in the Database Maximum number of retention intervals Performance 40M 672 40M 96 Accounting 40M 672 40M 16 Table 6 14 Maximum statistics interval retention Auxi...

Page 90: ... used by test suites Test Suite A collection of elemental tests that can be assigned to a specific schedule There are three defined sections in which tests can be placed within a test suite First run Generated and Last run The tests are executed in order by these sections It is possible to configure the execution order of tests within the First Run and Last Run sections to be parallel or sequentia...

Page 91: ...eriod with results stored in the SAM Database or SAM Database and using logToFile Maximum accounting file STM elemental test results in a 10 minute period using logToFile only Distributed 5620 SAM Configuration with minimum 8 CPU Core 5620 SAM Server 6 000 500 0001 500 0001 Distributed 5620 SAM Configuration NOTE It may be possible to achieve higher numbers depending on the 5620 SAM Server activit...

Page 92: ... quickly Rather than scheduling a test suite to run sequentially consider duplicating the test suite and running the test suites on alternating schedules This allows each test suite time to complete or time out before the same test suite is executed again Remember that this may cause double the system weight to be consumed until the alternate test suite has completed Create test suites that contai...

Page 93: ...hat the objective is to perform LSP pings on each LSP as frequently as possible The following steps are to be followed 1 Create 4 test suites each containing 100 elemental LSP ping tests 2 One at a time execute each test suite and record the time each one took to complete Assume that the longest time for executing one of the test suites is 5 minutes 3 Create a schedule that is ongoing and has a fr...

Page 94: ...umber of test suites scheduled at or around the same time The number of tests in a test suite The number of routers over which the tests are being executed Generally a large number of tests on a single router can be expected to take longer than the same number of tests distributed over many routers A 5620 SAM Database backup may temporarily reduce the system s ability to write test results into th...

Page 95: ...by up to 80GB A larger tablespace partition should be considered The maximum number of test results stored in the database reflects the sum of the aggregate results test results and probe results Running 10 tests with 1 probe each versus 1 test with 10 probes consumes the same amount of disk space When using logToFile for accounting file STM test results the maximum time to live on the disk is 24 ...

Page 96: ...a Mobile deployment Volume statistics require an aggregation interval of 60 minutes As an alternative Volume Special Study statistics on specific subscribers can be used The only key factor of difference is whether or not additional counters are enabled for Comprehensive statistics Table 6 17 cflowd statistics scaling limits for residential and mobile deployments 5620 SAM Cflowd Auxiliary processi...

Page 97: ...s Comprehensive statistics types are fixed at 60 minute intervals A unique object route for TCP Volume records in the business context is SAP App AppGroup Interval ID Src Group ID Source Interface ID Dest Group ID Dest Interface ID A Volume record will also have a direction field Volume records coming from the router to the 5620 SAM Cflowd Auxiliary will result in two output records in the IPDR fi...

Page 98: ...me Unknown 5M TCP All Cnt 0 5 RTP All Cnt 1 Notes 1 Comprehensive Volume Unknown Volume SS All Counters RTP TCP TCP S S Counter Selection Default Counters Leaving default enabled counters on All Counters Enabling all available counters for given stat type There are 40 60 total counters available for TCP and RTP types 2 Number of aggregated output requisitions that are sent to the server every 60 s...

Page 99: ...nstallation for 5620 SAM workstations 7 3 5620 SAM software installation 7 3 5620 SAM network element communication 7 4 5620 SAM and firewalls 7 4 Port Information 7 6 FTP between the 5620 SAM Server and 5620 SAM Auxiliary Statistics Collector and the managed network 7 15 Firewall and NAT rules 7 16 5620 SAM 3HE 09809 AAAG TQZZA 13 0 R7 Issue 1 December 2015 7 1 ...

Page 100: ... CPAM Installation and Upgrade Guide Install the latest Recommended Patch Cluster from Red Hat available at www redhat com If installing RHEL disable the mDNS Service Implement firewall rules for 5620 SAM to control access to ports on 5620 SAM platforms as described in 5620 SAM and firewalls p 7 4 If installing RHEL enable the RHEL firewall filter rules lists See Firewall and NAT rules p 7 16 for ...

Page 101: ...e additional platform hardening does not impact 5620 SAM s operation The 5620 SAM Product Group makes no commitment to make 5620 SAM compatible with a customer s hardening requirements 5620 SAM software installation 5620 SAM software installation Alcatel Lucent recommends the following steps when installing the 5620 SAM components Configure the 5620 SAM Server IP validation during the 5620 SAM Dat...

Page 102: ...of the built in firewall using iptables Standalone Firewall products must not be collocated on servers hosting 5620 SAM components Only the built in RHEL firewall used to enable filter rules lists can be collocated with 5620 SAM components See Firewall and NAT rules p 7 16 for more details Some 5620 SAM operations require idle TCP ports to remain open for longer periods of time Therefore customer ...

Page 103: ...nd 5620 SAM redundant deployments 22667 5620 SAM Server 5620 SAM Database 5620 SAM Auxiliary 5620 SAM Clients TCP Oracle ftp tftp ftp tftp SNMP SNMP SSH Telnet SNMP traps JMS JMS EJB HTTP JMS TCP Oracle Managed Network Active 5620 SAM Server 5620 SAM Database 5620 SAM Auxiliary TCP Oracle JMS Standby Security 5620 SAM and firewalls 5620 SAM 3HE 09809 AAAG TQZZA 13 0 R7 Issue 1 December 2015 7 5 ...

Page 104: ...0 SAM OSS clients 69 UDP None TFTP This port is used to do ftp when managing 1830 PSS equipment If there are none of these NEs in the network this port is not required 80 TCP None See port 443 for secure communications HTTP This port provides an HTTP interface for the User Documentation Server InfoCenter and Web Applications Also provides a WebDav Server for snapshots and workorders 162 UDP Static...

Page 105: ...0 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 This port is also used by the 5620 SAM GUI and OSS clients to register with the 5620 SAM Server to receive notification of network changes 1998 TCP None RMI Port for CNBI This is a local port to the host 1999 TCP None JNDI Port for CNBI This is a l...

Page 106: ... server 8086 TCP None See port 8445 for secure communications HTTP This port provides an HTTP interface to the WebDav Server for WTA This port is only required on the CallTrace Auxiliary 8087 TCP Dynamic Encryption Encryption provided by SSL TLS Strong ciphers are supported Selection of CBC and AES ciphers provided by TLS are supported HTTP HTTPS if SSL is configured Servlet connector used for com...

Page 107: ...d on the CallTrace Auxiliary 8483 TCP None JBoss RMI port for WebServices This is a local port to the host 8889 TCP None Notification port used by TAO CORBA Notification This is a local port to the host 8980 TCP None See port 9443 for secure communications HTTP This port provides an HTTP interface for 5620 SAM O Clients to the WDSL 3GPP WebServices Integration Reference Points 9010 TCP None This p...

Page 108: ...cess the JMX console for the JMS server process 10190 TCP Dynamic Encryption Encryption provided by SSL TLS Strong ciphers are supported Selection of CBC and AES ciphers provided by TLS are supported JBoss Management Console Used to access the JBoss management console for the auxiliary server process 10199 TCP Dynamic Encryption Encryption provided by SSL TLS Strong ciphers are supported Selection...

Page 109: ...AM DCP Server and the 5620 SAM Server or dedicated ftp server for retrieving IPDR files 22 TCP Dynamic Encryption Cipher Suite and strength as per RFC 4253 SSH SCP SFTP This port is used to enable SSH SFTP SCP communication between the 5620 SAM DCP Server and the 5620 SAM Server or dedicated ftp server for retrieving IPDR files 1090 TCP None JBoss RMI JRMP socket for connecting to the JMX MBeanSer...

Page 110: ...d by TLS are supported HTTPS This port provides an HTTPS secure HTTP 5620 SAM Cflowd Auxiliary Server management interface This is a secure version of port 9990 Used only if the 5620 SAM Cflowd Auxiliary Server is SSL secured 9990 TCP None See port 9443 for secure communications HTTP This port provides an HTTP 5620 SAM Cflowd Auxiliary Server management interface 9999 TCP Dynamic Encryption Encryp...

Page 111: ...ong ciphers are supported Selection of CBC and AES ciphers provided by TLS are supported HTTPS This port is required for the 5620 SAM Client to be able to communicate with the 5780 DSC 830 TCP Dynamic Encryption Cipher Suite and strength as per RFC 4253 SSH for eNodeB SSHv2 for MME This port is used by the eNodeB and MME network elements for NetConf management 1099 TCP None RMI This port is requir...

Page 112: ...he 9471 WMM Provisioning GUI NOTE Only required when using 9471 MME 4 0 or older 11500 TCP None Equipment View Used while managing 9500 MPR MSS 1C MPR e NEs using the Equipment View function as part of NetO N A ICMP N A ICMP Only used if the Ping Policy is enabled as part of network element mediation 5620 SAM Database 22 TCP Dynamic Encryption Cipher Suite and strength as per RFC 4253 SSH This por...

Page 113: ...20 SAM Clients running the NetO manager 5010 UDP None Trap Trap port used by 9500 MPR devices to send traps to 5620 SAM Clients running the NetO manager 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 Statisti...

Page 114: ...he filter rules lists provided with each 5620 SAM component All others should disable the RHEL firewall The installation of each 5620 SAM component will include the filter rules lists to be applied for successful communication between different 5620 SAM components OSS Clients and Network Elements The table below defines the location Table 7 2 Sample iptables filter rules lists file locations SAM C...

Page 115: ... 8 4 the following firewall rules need to be applied Table 7 3 SNMP Firewall rules for traffic between the 5620 SAM Server s and the managed network Protocol From port On To port On Notes UDP Any Managed Network 162 Server s SNMP trap initiated from the NE UDP 32768 Server s 161 Managed Network SNMP request UDP Any Server s 8001 Managed Network SNMP for 9471 WMM UDP 161 Managed Network 32768 Serve...

Page 116: ... Server s SAM SSH response TCP Any Managed Network 22 Server s eNodeB and 1830 PSS SFTP request TCP 22 Server s Any Managed Network eNodeB and 1830 PSS SFTP response TCP 32768 Server s 830 Managed Network SSH request for eNodeB TCP 830 Managed Network 32768 Server s SSH response for eNodeB TCP 32768 Server s 830 Managed Network SSHv2 request for MME TCP 830 Managed Network 32768 Server s SSHv2 res...

Page 117: ...ith multiple network interfaces p 8 4 the following rules need to be applied Table 7 9 Firewall rules for traffic coming into the 5620 SAM Server s from the 5620 SAM Client s GUI OSS Protocol From port On To port On Notes TCP Any SAM O Client 21 Server s If FTP is required TCP Any SAM O Client 22 Server s If SFTP SCP is required TCP 1023 SAM O Client 1023 Server s If FTP is required TCP Any SAM O ...

Page 118: ...ient interface NIC 3 on Figure 8 2 Distributed 5620 SAM Server Database deployment with multiple network interfaces p 8 4 or the SAM network interface NIC 1 on Figure 8 2 Distributed 5620 SAM Server Database deployment with multiple network interfaces p 8 4 on the 5620 SAM Server Table 7 10 Firewall rules for traffic coming into the 5620 SAM Server s from the 5620 SAM Auxiliary Statistics Call Tra...

Page 119: ... On To port On TCP 1523 Database Server s Any Server s TCP 9002 Database Server s Any Server s When there is a firewall at the SAM management interface NIC 1 on Figure 8 2 Distributed 5620 SAM Server Database deployment with multiple network interfaces p 8 4 and 5620 SAM Server redundancy is configured then the following rules need to be applied Configuration needs to be in both directions to hand...

Page 120: ...erver s from the 5620 SAM Auxiliary Statistics Call Trace Server s Protocol From port On To port On TCP Any Auxiliary Server s 12300 12307 Server s TCP 12300 12307 Auxiliary Server s Any Server s TCP Any Auxiliary Server s 12800 Server s TCP 12800 Auxiliary Server s Any Server s When there is a firewall at the SAM management interface NIC 1 on Figure 8 2 Distributed 5620 SAM Server Database deploy...

Page 121: ...dant only Protocol From port On To port On TCP Any Database Servers 22 Database Servers TCP 22 Database Servers Any Database Servers TCP Any Database Servers 1523 Database Servers TCP 1523 Database Servers 9000 Database Servers TCP 9002 Database Servers 9002 Database Servers TCP 9003 Database Servers 9003 Database Servers 5620 SAM Auxiliary Server firewall and NAT rules When there is a firewall at...

Page 122: ...mple STM Accounting statistics NE backups TCP 21 Managed Network Any Auxiliary Server s FTP responses TCP 1023 Managed Network 1023 Auxiliary Server s Passive FTP ports for data transfer See FTP between the 5620 SAM Server and 5620 SAM Auxiliary Statistics 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 Firew...

Page 123: ...rmation TCP 21 22 SAM O Client Any Auxiliary Server s S FTP responses TCP 1023 SAM O Client Any Auxiliary Server s Passive S FTP ports for data transfer See FTP between the 5620 SAM Server and 5620 SAM Auxiliary Statistics Collector and the managed network p 7 15 Only for 5620 SAM Auxiliary Call Trace Collectors TCP Any SAM O Client 8086 Auxiliary Server s HTTP interface for WebDAV for WTA TCP Any...

Page 124: ...loyment with multiple network interfaces p 8 4 of the 5620 SAM Auxiliary Table 7 25 Firewall rules for inter process communication on the 5620 SAM Auxiliary Statistics Call Trace Server s Protocol From port On To port On TCP Any Auxiliary Server s 1095 Auxiliary Server s TCP Any Auxiliary Server s 12300 12307 Auxiliary Server s TCP 12300 12307 Auxiliary Server s Any Auxiliary Server s TCP Any Auxi...

Page 125: ...ork interfaces p 8 4 of the 5620 SAM Auxiliary Table 7 27 Firewall rules for traffic coming into the 5620 SAM Auxiliary Statistics Call Trace Server s from the 5620 SAM Server s Protocol From port On To port On TCP 1097 Server s Any Auxiliary Server s TCP 1099 Server s Any Auxiliary Server s TCP 4447 Server s Any Auxiliary Server s TCP 32768 Server s 32768 Auxiliary Server s When there is a firewa...

Page 126: ...y Server s TCP 9002 Database Server s Any Auxiliary Server s When there is a firewall at the interface that reaches the SAM management network NIC 1 on Figure 8 2 Distributed 5620 SAM Server Database deployment with multiple network interfaces p 8 4 the following rules apply Table 7 30 Firewall rules for traffic coming into the 5620 SAM Auxiliary Server s from the 5620 SAM Server s Protocol From p...

Page 127: ...tween the 5620 SAM Client and the 5780 DSC Protocol From port On To port On Notes TCP Any 5620 SAM Client s 443 Managed Network HTTPS Table 7 34 Firewall rules for traffic between the 5620 SAM Client and the 9471 WMM Protocol From port On To port On Notes TCP Any 5620 SAM Client s 1099 Managed Network RMI TCP Any 5620 SAM Client s 1234 Managed Network Search agent TCP Any 5620 SAM Client s 1235 Ma...

Page 128: ...Any Managed Network FTP TCP 22 5620 SAM Client Any Managed Network sFTP TCP Any 5620 SAM Client 22 Managed Network sFTP TCP Any 5620 SAM Client s 23 Managed Network Telnet TCP Any 5620 SAM Client s 80 Managed Network HTTP UDP Any 5620 SAM Client s 161 Managed Network SNMP TCP 1023 5620 SAM Client s 1023 Managed Network Passive FTP UDP 5010 5620 SAM Client s 5010 Managed Network SNMP Table 7 38 Fir...

Page 129: ...ny Managed Network FTP TCP Any 5620 SAM Client s 23 Managed Network Telnet TCP Any 5620 SAM Client s 80 Managed Network HTTP UDP Any 5620 SAM Client s 161 Managed Network SNMP TCP 1023 5620 SAM Client s 1023 Managed Network Passive FTP UDP 5010 5620 SAM Client Any Managed Network SNMP Table 7 40 Firewall rules for traffic between the 5620 SAM Client and Omni Switches Protocol From port On To port ...

Page 130: ...Security Firewall and NAT rules 7 32 5620 SAM 3HE 09809 AAAG TQZZA 13 0 R7 Issue 1 December 2015 ...

Page 131: ...e IP addresses deployment scenarios 8 5 5620 SAM Auxiliary Statistics Collector multiple IP addresses deployment scenarios 8 6 5620 SAM Auxiliary Call Trace Collector multiple IP addresses deployment scenarios 8 7 5620 SAM Auxiliary Cflowd Collector multiple IP addresses deployment scenarios 8 8 Using Network Address Translation 8 9 Configuring 5620 SAM Server to utilize multiple network interface...

Page 132: ...tion must be paid to the firewall rules on the network interfaces on the 5620 SAM Server and 5620 SAM Auxiliary Collector NICs 1 and NICs 3 on Figure 8 2 Distributed 5620 SAM Server Database deployment with multiple network interfaces p 8 4 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...

Page 133: ...terfaces 22666 5620 SAM Server Database bge0 bge1 Managed network 5620 SAM Clients Deploying the 5620 SAM with multiple network interfaces IP addresses Deploying the 5620 SAM with multiple network interfaces IP addresses 5620 SAM 3HE 09809 AAAG TQZZA 13 0 R7 Issue 1 December 2015 8 3 ...

Page 134: ...liary Optional 5620 SAM Server Standby 5620 SAM Database Standby NIC 4 5620 SAM Auxiliary Optional NIC 1 NIC 1 NIC 1 NIC 1 NIC 1 NIC 1 NIC 2 NIC 3 Switch Router Switch Router NIC 4 NIC 2 IPv4 Managed Network NIC 3 Switch Router Switch Router NIC 3 Switch Router Switch Router IPv6 Managed Network NIC 4 NIC 4 NIC 2 NIC 4 NIC 3 NIC 2 5620 SAM Clients NIC 1 5620 SAM Auxiliary Database Cluster optional...

Page 135: ...s and OSS must be configured to use the same IP address to communicate to the 5620 SAM Server This IP address can be different from the one used by the managed devices to communicate with the 5620 SAM Server One network interface can be used to communicate with the 5620 SAM Database 5620 SAM Auxiliary Database and 5620 SAM Auxiliary Collectors as well as any redundant 5620 SAM components should th...

Page 136: ...ces will use to retrieve the accounting statistics files and performance statistics from the network elements One network interface can be used to service the requirements of the OSS clients NIC 3 on Figure 8 2 Distributed 5620 SAM Server Database deployment with multiple network interfaces p 8 4 This network interface contains the IP address that all OSS clients will use to communicate with the 5...

Page 137: ...5620 SAM Auxiliary Call Trace Collector supports the configuration of different IP addresses for the following purposes One network interface can be used to retrieve information from the managed network NIC 2 on Figure 8 2 Distributed 5620 SAM Server Database deployment with multiple network interfaces p 8 4 This network interface contains the IP address that the managed devices will use to send t...

Page 138: ...mer s discretion to perform maintenance operations such as workstation backups IPv4 and IPv6 network elements can be managed from the same interface or from separate interfaces NIC3 and or NIC4 on Figure 8 2 Distributed 5620 SAM Server Database deployment with multiple network interfaces p 8 4 5620 SAM Auxiliary Cflowd Collector multiple IP addresses deployment scenarios 5620 SAM Auxiliary Cflowd ...

Page 139: ...Figure 8 2 Distributed 5620 SAM Server Database deployment with multiple network interfaces p 8 4 Therefore routing must also exist between the client interfaces NIC 3 on Figure 8 2 Distributed 5620 SAM Server Database deployment with multiple network interfaces p 8 4 on both SAM Servers and the Auxiliary Collectors Additional network interfaces may be configured on the 5620 SAM Auxiliary Cflowd C...

Page 140: ... routing loopback from the SAM Server private IP address to the SAM Server public IP address must be configured in this scenario as all 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 Figure 8 3 5620 SAM Server deployments with NAT between the Server and th...

Page 141: ...ll Figure 8 4 5620 SAM Server deployment using NAT with IP Address communication 5620 SAM Server NAT Enabled Firewall 5620 SAM Client Client must connect to SAM Server Public IP Address 5620 SAM Client Client must connect to SAM Server Public IP Address 22663 Private Network Public Network Routing loopback required for SAM Server Figure 8 5 5620 SAM Server deployment using NAT with Name Resolution...

Page 142: ...tion is not supported between the 5620 SAM Auxiliary Call Trace Collector and the Managed Network Figure 8 6 5620 SAM deployment with NAT Managed Network 5620 SAM Server 5620 SAM Auxiliary 5620 SAM Database 5620 SAM Server 5620 SAM Auxiliary 5620 SAM Database Private Network NAT Enabled Firewall NAT Enabled Firewall 5620 SAM Client Active Standby 22661 Deploying the 5620 SAM with multiple network ...

Page 143: ...er s public address is exposed to multiple networks with different IP addresses a hostname can be used instead of a fixed IP address This is most useful when NAT is used between 5620 SAM clients and the 5620 SAM Server that can be accessed via multiple networks For situations where the 5620 SAM Client and the 5620 SAM Auxiliary are using different network interfaces to the 5620 SAM Server the 5620...

Page 144: ...Deploying the 5620 SAM with multiple network interfaces IP addresses Use of hostnames for the 5620 SAM Client 8 14 5620 SAM 3HE 09809 AAAG TQZZA 13 0 R7 Issue 1 December 2015 ...

Search results

Summary of Contents for 5620

Reviews:

Related manuals for 5620

Brands by name

Popular brands

Alcatel-Lucent 5620, Planning Manual

Search results

Summary of Contents for 5620

Reviews:

Related manuals for 5620

Brands by name

Popular brands