NMS5-UX/NMS5-LX

HARDWARE PLATFORM AND

COMMUNICATION NETWORK DIMENSIONING

Issue: Ed.22

Date: 24-11-2015

Ed.22 24/11/2015
1
 SUMMARY

1. FOREWORD ...............................................................................................4

2. INTRODUCTION .........................................................................................4

3. NMS5UX-B SYSTEM CONFIGURATION ....................................................5

3.1 Basic Hardware and Software ..............................................................5

3.2 Hardware Platform Dimensioning .........................................................6

4. NMS5-LX SYSTEM CONFIGURATION .......................................................7

4.1 Basic Hardware and Software ..............................................................7

4.2 Hardware Platform Dimensioning .........................................................8

5. INSTALLATIONS ON VIRTUAL SERVER .................................................11

6. PC BASED GRAPHICAL ACCESS ...........................................................12

6.1.1 Hardware requirements ...............................................................12

6.1.2 Software requirements ................................................................12

6.2 System “archive (file)” dimensioning ...................................................13

Alarm history log ......................................................................13

Performance Monitor log ..........................................................13

Transaction Log .......................................................................13

7. COMMUNICATION NETWORK ................................................................14

7.1 Network for Equipment Connection ....................................................14

Configuration messages ..........................................................14

Alarm and status messages .....................................................14

Alarms and Status ..................................................................................15

Performance Monitoring Messages .........................................15

7.2 Network for Remote Connection .........................................................26

7.3 NETWORK for GEOGRAPHYCAL redundancy ................................27

7.4 NETWORK for North Bound interface (NBI) ......................................27

Ed.22 24/11/2015
2
 7.5 TCP/UDP PORT NUMBER.................................................................28

Protocols ................................................................................................28

TCP/UDP Ports ......................................................................................28

Protocols ................................................................................................29

TCP/UDP Ports ......................................................................................29

7.6 OSI network design constraint ............................................................30

Design constraints ..................................................................................30

Supported value .....................................................................................30

8. NMS5-UX - SYSTEM REDUNDANCY .......................................................31

9. NMS5-LX - SYSTEM REDUNDANCY .......................................................31

Ed.22 24/11/2015
3
1. FOREWORD
Siae Microelettronica has been successfully implementing management
systems since many years. Throughout this period data have been gathered
from real-time traffic bearing systems and collated against theoretical
calculations developed by engineers from the SIAE R&D laboratories in Milan,
Italy. The results of these studies have allowed SIAE to publish the following
guidelines for "Dimensioning" equipment used for the management of
telecommunications networks.

2. INTRODUCTION
The objective of this document is to provide information on system and
communication network dimensioning thus enabling:

 Appropriate control of the Network Element

 Acceptable response times to the operator commands.

 Availability of information concerning the implementation of system

redundancy.

Ed.22 24/11/2015
4
3. NMS5UX-B SYSTEM CONFIGURATION

3.1 BASIC HARDWARE AND SOFTWARE

The NMS5UX-B has been validated on the following hw platform:

 HP Servers with Itanium CPU

NMS5UX-B software runs on the following Sw platform:

 HP-UX Rel. 11i V3

 Data Base ORACLE 10.g

Ed.22 24/11/2015
5
 3.2 HARDWARE PLATFORM DIMENSIONING

The hardware dimensioning is achieved in consideration of the following

parameters:

 Number and types of managed Network Elements

 Number of Network operators who can access the system

simultaneously.

As a reference, the following table shows some hardware configurations versus

network load.

Reference HW: HP Integrity rx2800 i4 Server with Intel Itanium processor

9300 series

Server type and configuration Max. NE Max.

Load Operators
HP rx2800 i4, 1 x Processor Itanium 9520 4 Core, 4000 10
1.73GHz, 20MB Cache
Memory: 8 GB RAM, 4x140GByte Hard disks
HP rx2800 i4, 1 x Processor Itanium 9540 8 Core, 8000 16
2.13GHz, 24MB Cache
Memory: 16 GB RAM, 6x140GByte Hard disks
HP rx2800 i4, 1 x Processor Itanium 9560 8 Core, 12000 25
2.53GHz, 32MB Cache
Memory: 64 GB RAM, 8x140GByte Hard disks
DUAL Servers HW requirements: 20.000 50

MAIN SERVER
HP rx2800 i4, 1 x Processor Itanium 9560 8 Core,
2.53GHz, 32MB Cache
Memory: 64 GB RAM, 8x140GByte Hard disks
P.M. SERVER
HP rx2800 i4, 1 x Processor Itanium 9520 4 Core,
1.73GHz, 20MB Cache
Memory: 8 GB RAM, 4x140GByte Hard disks

NOTE:

Ed.22 24/11/2015
6
To improve the system performances it is better to have four mirrored hard
disks.

The number of disks improves the system performances and availability not
only the storage capacity.

If number of NEs greater than 12.000 (large network with 7000-9000 links) or
number of concurrent operators greater than 25, the solution is DUAL SERVER
architecture, to provide load balancing architecture.

Two servers are needed to split load between main and PM server, adding a
new server dedicated to Performance Monitoring (TDM and Ethernet counters):
 Reading from NE
 Storing in NMS5UX database
 Export to file

The server is required if the Performance Monitoring counters collection must

be enabled on all NE of the managed network.

4. NMS5-LX SYSTEM CONFIGURATION

4.1 BASIC HARDWARE AND SOFTWARE

The NMS5-LX has been validated on the following hw platform:

 PC Pentium D & Pentium 4 (Desktop PC)

 IBM x336 Servers with XEON CPU

 Hp Proliant Servers with XEON CPU (DL380G8)

NMS5-LX software runs on the following SW platform:

 SUSE Linux Enterprise Server 11 SP3

 Database ORACLE 10.g for NMS 6.x

 Database Oracle 12 from NMS 7.0.0

Ed.22 24/11/2015
7
4.2 HARDWARE PLATFORM DIMENSIONING

The hardware dimensioning is achieved in consideration of the following

parameters:

 Number and types of managed Network Elements

 Number of Network operators who can access the system

simultaneously.

 Number of operators connected by PC running X-Terminal emulator

(X.11 protocol) or GoGlobal

The following table (The same of NMS5-UX) shows how the above parameters
affect system load; the load of PDH point to point radio equipment is placed as
a reference equal to one.

Parameter NE Load
"EL" PDH Radio 1
"AL" & "ALC" PDH Radio 1
"AL+" & "ALC+" terminal PDH Radio 1
"AL+" nodal per each configured IDU+ 1
"ALPlus2" 1
"ALCPlus2" 1
"ALCPlus2e" 1
“AGS10” 1
“ALFOplus80HD” 1
“AGS20” 1
“ALFOPlus2” 1
SDH Radio - STM-1 Interface (US and ALS)
SDH Radio – 63x2 Mbit/s Interface (US) 1
SDH Radio – n+1 STM-1 Interface (TL) 1
SDH Add-Drop Mux ADM-C and ADM1 1
FAM, C-FAM, FAMxC 2
Point to Multipoint (PMP) 5

Proxy Agent SNMP 300

Note 1: "Proxy Agent SNMP" is the optional module to forward alarm

notifications to upper management system

Ed.22 24/11/2015
8
 Using the above parameters it is possible to calculate the overall network load
in order to select the most cost-effective HW platform.

As a reference, the following table shows some hardware configurations versus

network load.

Server type and configuration Max. NE Max.

Operators
PC Intel Core i5-650 3,20GHz 4MbL3 2.000 5
Memory: 6 GBytes, SATA Hard disk: 500 GBytes
Server HW requirements: 5.000 10
1 x Processor 8 Core Intel® Xeon® E5-2650
(2GHz) or higher, 6GB RAM, 20MB Cache,
Disks: 6 x 140GBytes SAS
Server HW requirements: 10.000 20
2 x Processors 8 Core Intel® Xeon® E5-2650
(2GHz) ) or higher, 32GB RAM, 20MB Cache,
Disks: 8 x 140GBytes SAS
Server HW requirements: 12.000 25
2 x Processors 8 Core Intel® Xeon® E5-2650
(2GHz) or higher, 64GB RAM, 20MB Cache
Disks: 8 x 140GBytes SAS
DUAL Servers HW requirements: 20.000 50

MAIN SERVER
2 x Processors 8 Core Intel® Xeon® E5-2650
(2GHz) or higher, 64GB RAM, 20MB Cache
Disks: 8 x 140GBytes SAS
P.M. SERVER
2 x Processors 8 Core Intel® Xeon® E5-2650
(2GHz) ) or higher, 16GB RAM, 20MB Cache,
Disks: 8 x 140GBytes SAS
Note: Server is required for redundant PSU (Power Supply Unit)

Other hardware requirements for the main server or PC are the following ones:

 DVD Read/Write

It is recommended to have four mirrored hard disks, in order to improve the

system performances.

Ed.22 24/11/2015
9
If number of NEs greater than 12.000 (large network with 7000-9000 links) or
number of concurrent operators greater than 25, the solution is DUAL SERVER
architecture, to provide load balancing architecture.

Two servers are needed to split load between main and PM server, adding a
new server dedicated to Performance Monitoring (TDM and Ethernet counters):
 Reading from NE
 Storing in NMS5UX database
 Export to file

The server is required if the Performance Monitoring counters collection must

be enabled on all NE of the managed network.

Ed.22 24/11/2015
10
 5. INSTALLATIONS ON VIRTUAL SERVER
NMS5-LX can be installed on virtual server based on VMware Vsphere.

The characteristics of the physical servers described in previous section can be

translated into following specification in case of virtualization.

Virtual server requirements Max. NE Max.

Load Operators
CPU count: 1
Memory: 8 GBytes 2.000 5
Virtual disk: 100 GB
CPU count: 2
Memory: 16 GBytes 5.000 10
Virtual disk: 200 GB
CPU count: 4
Memory: 32 GBytes
Virtual disk: 500 GB performed for OLTP DB (Note 1) 10.000 20
(Note 2)
CPU count: 4
Memory: 32 GBytes
Virtual disk: 500 GB performed for OLTP DB (Note 1) 12.000 25
(Note 2)
DUAL Virtual Servers Configuration:
Main Server
CPU count: 8
Memory: 64 GBytes
Virtual disk: 500 GB
20.000 50
Secondary Server
CPU count: 8
Memory: 16 GBytes
Virtual disk: 500 GB performed for OLTP DB (Note 1)
(Note 2)

Note 1: Paravirtual SCSI controller is required for disk dedicated to store Oracle
Data.

Note 2: Optimal Physical Hardware: equal or greater than Xeon bi-processor

E5-2680 and optimal Memory Type DDR-1600

Ed.22 24/11/2015
11
6. PC BASED GRAPHICAL ACCESS

6.1.1 Hardware requirements

In order to achieve reasonable response time, we suggest the following

hardware characteristics:

CPU: Pentium II class

System RAM: 2 GBytes

Video RAM 512 Mbytes

Monitor resolution 1280x1024 (19” suggested)

6.1.2 Software requirements

The following X-Terminal emulators have been validated:

 Exceed
 Reflection-X
 XMing

Instead of X-Terminal emulator, it is recommended to use GO-Global that is a

server-based ultrathin-client solution. GO-Global provide a fast access to
NMS5UX/LX graphical applications using low speed link.
GoGlobal supported version are 2.0, 2.1 and 2.2

Ed.22 24/11/2015
12
6.2 SYSTEM “ARCHIVE (FILE)” DIMENSIONING

The following paragraph describes the byte record dimensioning of the system
archives; since the result of this calculation has a low impact on the total mass-
memory devices dimensions, this paragraph is for information only.

Alarm history log

The maximum number of records is configurable during the system start-up

(Default: 50000 records).
For big network (Number of NE greater then 4000) the suggested value is
1.000.000

Performance Monitor log

Six (configurable) Oracle tables form the archive, each one containing the
performance records accumulated in a month. There are no limits on the
maximum number of records stored in a table.

Transaction Log

The maximum number of records is configurable during the system start-up

(Default: 50000 records).

The following table shows the number of bytes that are relevant to the above-
mentioned archives.

Archive Byte per Record

Alarm History 426

Performance Monitor 64
Transaction Log 217

Ed.22 24/11/2015
13
7. COMMUNICATION NETWORK

The following paragraph describes the data needed for dimensioning the
communication network that is required for the management system to connect
the managed equipment directly or via remote operators.

7.1 NETWORK FOR EQUIPMENT CONNECTION

The messages exchanged between the network management system and the
network elements can be summarised as follows:

Configuration messages

These messages have short duration and seldom occur; therefore they do not
impact upon system dimensioning.

Alarm and status messages

Spontaneous alarm reporting and status messages arriving at the management

system from the network elements utilises “TRAP” SNMP.

An alarm message is between 150 and 200 bytes long.

The system interrogates each network element periodically in order to verify the
status.

The interval of the checking period is configured at the system start-up. The
periodical inquiry uses a “GET” SNMP message; the size of GET-Request
message (from NMS5-UX) is 100 bytes and the size of the GET-Response
message (from equipment) is 115 bytes.

The peak alarm rate managed by NMS5-UX/LX is 50 traps per second

The average alarm rate managed by NMS5-UX/LX is 25 traps per second

Ed.22 24/11/2015
14
The table here below shows the above-mentioned characteristics:

Alarms and Status

Messages N. of bytes

Alarms (Trap SNMP) 150-200

Polling check for NE:

GET-Request 100

GET-Response 115

Performance Monitoring Messages

The following points summarise how Performance Monitoring is managed by

NMS5-UX.

The NMS5-UX automatically and periodically checks the Performance

Monitoring counters; the period is configurable during the system start-up (2
hours default).

For any point of measure and for any counter typology, the following counter
sets are provided:

 Daily counters relevant to the previous day

 Daily counters relevant to the current day

 15 minutes counters relevant to the current 15 minutes

 16 counter set of 15 minutes in order to cover 4 hours

Ed.22 24/11/2015
15
The tables here below show data relevant to the Performance Monitoring
counters for each type of equipment.

"EL" Radio (PDH)

Messages dimension
Type Counter Measuring points
(bytes)
total 2:
GET-Request: 260
G.826 BBE, ES, SES, UAS Radio 1
GET-Response: 270
Radio 2
Total 2:
Rlts1, Rlts2, Rlts3, GET-Request: 300
Rx Power Level Radio 1
Rlts4, RxMax, RxMin. GET-Response: 320
Radio 2

"AL" Radio (PDH)

Messages dimension
Type Counter Measuring points
(bytes)
total 5:
Radio 1
BBE, ES, SES, Radio 2 GET-Request: 270
G.828
SEP, UAS Radio After Switch GET-Response: 280
1xE1 Radio side
1xE1 Line side
Total 2:
Rlts1, Rlts2, Rlts3, GET-Request: 300
Rx Power Level Radio 1
Rlts4, RxMax, RxMin. GET-Response: 320
Radio 2
total 2:
Tlts1, Tlts2, Tlts3, GET-Request: 300
Tx Power Level Radio 1
Tlts4, TxMax, TxMin GET-Response: 320
Radio 2

Ed.22 24/11/2015
16
 US Radio (SDH)
STM1 Tributary

Messages dimension
Type Counter Measuring points
(bytes)
total 3:
STM1 Line GET-Request: 260
G.826 (B1) BBE, ES, SES, UAS
STM1 Radio 1 GET-Response: 270
STM1 Radio 2
total 3:
BBE, ES, SES, UAS,
BBEFE, ESFE, STM1 Line GET-Request: 360
G.826 (B2 & M1)
SESFE, UASFE, STM1 Radio 1 GET-Response: 390
UASBIDI
STM1 Radio 2
Total 2:
Rlts1, Rlts2, Rlts3, GET-Request: 300
Rx Power Level Radio 1
Rlts4, RxMax, RxMin. GET-Response: 320
Radio 2
total 2:
Tlts1, Tlts2, Tlts3, GET-Request: 300
Tx Power Level Radio 1
Tlts4, TxMax, TxMin GET-Response: 320
Radio 2

US Radio (SDH)
63xE1 Tributary

Messages dimension
Type Counter Measuring points
(bytes)
total 3:
GET-Request: 260
G.826 (B1) BBE, ES, SES, UAS STM1 Radio 1
GET-Response: 270
STM1 Radio 2
BBE, ES, SES, UAS, total 3:
BBEFE, ESFE, GET-Request: 360
G.826 (B2 & M1) STM1 Radio 1
SESFE, UASFE, GET-Response: 390
UASBIDI STM1 Radio 2
BBE, ES, SES, UAS,
BBEFE, ESFE, total 63: GET-Request: 360
G.826 (VC12)
SESFE, UASFE, 63xVC12 GET-Response: 390
UASBIDI
Total 2:
Rlts1, Rlts2, Rlts3, GET-Request: 300
Rx Power Level Radio 1
Rlts4, RxMax, RxMin. GET-Response: 320
Radio 2
total 2:
Tlts1, Tlts2, Tlts3, GET-Request: 300
Tx Power Level Radio 1
Tlts4, TxMax, TxMin GET-Response: 320
Radio 2

Ed.22 24/11/2015
17
 Als Radio (SDH) and TL
STM1 Tributary

Messages dimension
Type Counter Measuring points
(bytes)
total 6:
BBE, ES, SES, 4xSTM1 Line GET-Request: 270
G.828 (B1)
SEP,UAS STM1 Radio 1 GET-Response: 280
STM1 Radio 2
total 6:
BBE, ES, SES,
SEP, UAS, BBEFE, 4xSTM1 Line GET-Request: 390
G.828 (B2 & M1)
ESFE, SESFE, STM1 Radio 1 GET-Response: 410
UASFE, UASBIDI
STM1 Radio 2
Total 2:
Rlts1, Rlts2, Rlts3, GET-Request: 300
Rx Power Level Radio 1
Rlts4, RxMax, RxMin. GET-Response: 320
Radio 2
total 2:
Tlts1, Tlts2, Tlts3, GET-Request: 300
Tx Power Level Radio 1
Tlts4, TxMax, TxMin GET-Response: 320
Radio 2

ADM –EXP63
63xE1 Tributary

Messages dimension
Type Counter Measuring points
(bytes)
total 2:
GET-Request: 270
G.828 (B1) BBE, ES, SES, UAS STM1 East
GET-Response: 280
STM1 West
BBE, ES, SES, UAS,
BBEFE, ESFE, total 2:
GET-Request: 390
G.828 (B2 & M1) SESFE, STM1 Radio 1
SEPFE, UASFE, GET-Response: 410
STM1 Radio 2
UASBIDI
BBE, ES, SES, UAS,
BBEFE, ESFE, total 63: GET-Request: 390
G.828 (VC12) SESFE,
SEPFE, UASFE, 63xVC12 GET-Response: 410
UASBIDI

Ed.22 24/11/2015
18
 "AL+" Radio (PDH)
Messages dimension
Type Counter Measuring points
(bytes)
total 5:
Radio 1
BBE, ES, SES, Radio 2 GET-Request: 270
G.828
SEP, UAS Radio After Switch GET-Response: 280
1xE1 Radio side
1xE1 Line side
Total 2:
Rlts1, Rlts2, Rlts3, GET-Request: 300
Rx Power Level Radio 1
Rlts4, RxMax, RxMin. GET-Response: 320
Radio 2
total 2:
Tlts1, Tlts2, Tlts3, GET-Request: 300
Tx Power Level Radio 1
Tlts4, TxMax, TxMin GET-Response: 320
Radio 2
total 2:
BBE, ES, SES, GET-Request: 270
G.828 (B1) 2xSTM1 Line
SEP,UAS GET-Response: 280

BBE, ES, SES, total 2:

SEP, UAS, BBEFE, GET-Request: 390
G.828 (B2 & M1) 2xSTM1 Line
ESFE, SESFE, GET-Response: 410
UASFE, UASBIDI
BBE, ES, SES, UAS,
BBEFE, ESFE, total 128: GET-Request: 390
G.828 (VC12) SESFE,
SEPFE, UASFE, 2x63 VC12 GET-Response: 410
UASBIDI

Ed.22 24/11/2015
19
 "ALPlus2" "ALCPlus2 & ALCPlus2e" Radio
Messages dimension
Type Counter Measuring points
(bytes)
total 4:
Radio 1
BBE, ES, SES, GET-Request: 270
G.828 Radio 2
SEP, UAS GET-Response: 280
1xE1 Radio side
1xE1 Line side
Total 2:
Rlts1, Rlts2, Rlts3, GET-Request: 300
Rx Power Level Radio 1
Rlts4, RxMax, RxMin. GET-Response: 320
Radio 2
total 2:
Tlts1, Tlts2, Tlts3, GET-Request: 300
Tx Power Level Radio 1
Tlts4, TxMax, TxMin GET-Response: 320
Radio 2
total 2:
BBE, ES, SES, GET-Request: 270
G.828 (B1) 2xSTM1 Line
SEP,UAS GET-Response: 280

BBE, ES, SES, total 2:

SEP, UAS, BBEFE, GET-Request: 390
G.828 (B2 & M1) 2xSTM1 Line
ESFE, SESFE, GET-Response: 410
UASFE, UASBIDI
BBE, ES, SES, UAS,
BBEFE, ESFE, total 63: GET-Request: 390
G.828 (VC12) SESFE,
SEPFE, UASFE, 63 VC12 GET-Response: 410
UASBIDI
4QAMStrong, 4QAM
8PSK,16QAM,32QAM total 2:
GET-Request: 370
ACM 64QAM,128QAM, Radio 1
256QAM, GET-Response: 390
Radio 2
DownShift,UpShift

Ed.22 24/11/2015
20
 AGS10 (ML PPP)
Messages dimension
Type Counter Measuring points
(bytes)
total 1:
BBE, ES, SES, GET-Request: 270
G.828 1xE1 Internal side
SEP, UAS GET-Response: 280
1xE1 Line side
total 2:
BBE, ES, SES, GET-Request: 270
G.828 (B1) 2xSTM1 Line
SEP,UAS GET-Response: 280

BBE, ES, SES, total 2:

SEP, UAS, BBEFE, GET-Request: 390
G.828 (B2 & M1) 2xSTM1 Line
ESFE, SESFE, GET-Response: 410
UASFE, UASBIDI
BBE, ES, SES, UAS,
BBEFE, ESFE, total 63: GET-Request: 390
G.828 (VC12) SESFE,
SEPFE, UASFE, 63 VC12 GET-Response: 410
UASBIDI

"ALFOplus" Radio
Messages dimension
Type Counter Measuring points
(bytes)
BBE, ES, SES, total 1: GET-Request: 270
G.828
SEP, UAS Radio 1 GET-Response: 280
Rlts1, Rlts2, Rlts3, Total 1: GET-Request: 300
Rx Power Level
Rlts4, RxMax, RxMin. Radio 1 GET-Response: 320
Tlts1, Tlts2, Tlts3, total 1: GET-Request: 300
Tx Power Level
Tlts4, TxMax, TxMin Radio 1 GET-Response: 320
4QAMStrong, 4QAM
16QAMStrong,
16QAM,32QAM total 1: GET-Request: 480
ACM 64QAM,128QAM,
256QAM,512QAM,102 Radio 1 GET-Response: 500
4QAM
DownShift,UpShift

Ed.22 24/11/2015
21
 "ALFOplus80" Radio
Messages dimension
Type Counter Measuring points
(bytes)
BBE, ES, SES, total 1: GET-Request: 270
G.828
SEP, UAS Radio 1 GET-Response: 280
Rlts1, Rlts2, Rlts3, Total 1: GET-Request: 300
Rx Power Level
Rlts4, RxMax, RxMin. Radio 1 GET-Response: 320
Tlts1, Tlts2, Tlts3, total 1: GET-Request: 300
Tx Power Level
Tlts4, TxMax, TxMin Radio 1 GET-Response: 320
4QAM, 16QAM, total 1: GET-Request: 270
ACM 64QAM,
DownShift,UpShift Radio 1 GET-Response: 280

"ALFOplus80HD" Radio
Messages dimension
Type Counter Measuring points
(bytes)
BBE, ES, SES, total 1: GET-Request: 270
G.828
SEP, UAS Radio 1 GET-Response: 280
Rlts1, Rlts2, Rlts3, Total 1: GET-Request: 300
Rx Power Level
Rlts4, RxMax, RxMin. Radio 1 GET-Response: 320
Tlts1, Tlts2, Tlts3, total 1: GET-Request: 300
Tx Power Level
Tlts4, TxMax, TxMin Radio 1 GET-Response: 320
BPSK, 4QAMStrong,
ACM 4QAM, 16QAM, total 1: GET-Request: 330
64QAM, Radio 1 GET-Response: 350
DownShift,UpShift

Ed.22 24/11/2015
22
 "AGS20”
Messages dimension
Type Counter Measuring points
(bytes)
BBE, ES, SES, total 2: GET-Request: 270
G.828
SEP, UAS Radio 2 GET-Response: 280
Rlts1, Rlts2, Rlts3, Total 2: GET-Request: 300
Rx Power Level
Rlts4, RxMax, RxMin. Radio 2 GET-Response: 320
Tlts1, Tlts2, Tlts3, total 2: GET-Request: 300
Tx Power Level
Tlts4, TxMax, TxMin Radio 2 GET-Response: 320
4QAMStrong, 4QAM
16QAMStrong,
ACM 16QAM,32QAM total 2: GET-Request: 330
64QAM,128QAM,
256QAM,512QAM,102 Radio 2 GET-Response: 350
4QAM
DownShift,UpShift

Ed.22 24/11/2015
23
The following table contains the minimum transmission rate(Kbit/s) required to
manage a NE according to the Equipment type.

EQUIPMENT TYPE Bit Rate

"EL" PDH Radio 2,4Kb/s
"AL" PDH Radio 2,4Kb/s
"AL+" PDH Radio (terminal) 2,4Kb/s
"AL+" PDH Radio - TDM Matrix - STM1 MST 63xVC12 9,6Kb/s
"ALPlus2" "ALCPlus2" & “ALCPLUS2e” Terminal 2,4Kb/s
"ALPlus2","ALCPlus2"& “ALCPLUS2e” TDM Matrix - STM1 MST 4,8Kb/s
126xVC12
"US" SDH Radio - STM1 Tributary 4,8Kb/s
"US" SDH Radio - 63xE1 Tributary 9,6Kb/s
"Als" SDH Radio - STM1 Tributary 4,8Kb/s
"TL" SDH Radio - STM1 Tributary 4,8Kb/s
ADM-C, ADM1, EXP63 & FAMxC 9,6Kb/s
PMP - Point to Multipoint 4,8Kb/s
AGS10 4,8Kbs
ALFOPlus, ALFOplus80, ALFOplus80HD 2,4Kb/s
AGS20 Terminal 2,4Kb/s
AGS20 TDM Matrix 4,8Kbs
CommServer 9,6Kb/s

Ed.22 24/11/2015
24
The following table contains the bit rate of the Embedded Operating Channel
(EOC) , the EOC is the communication channel used for the management of
the remote equipments.

EQUIPMENT TYPE EOC

Bit Rate
"EL" 4xE1 PDH - Radio EOC 32 Kb/s
"EL" 16xE1 PDH - Radio EOC 64 Kb/s
"AL" PDH - Radio EOC 64 Kb/s
"AL+" PDH - Radio EOC 64 Kb/s
"ALPlus2" , "ALCPlus2" "& “ALCPLUS2e” Radio EOC 128Kb/s
"US" SDH Radio - D1...D3 STM1 192Kb/s
"ALs" SDH Radio - D1...D3 STM1 192Kb/s
"TL" SDH Radio - D1...D3 STM1 192Kb/s
ADM-C, ADM1 & EXP63 - D1...D3 STM1 192Kb/s
ADM-C, ADM1 & EXP63 - D4...D12 STM1 576Kb/s

Using the above two tables is possible to evaluate the maximum number of
equipment connected to a GNE (Gateway Network Element)

Ed.22 24/11/2015
25
7.2 NETWORK FOR REMOTE CONNECTION

Connection to the NMS5-UX/NMS5-LX server from a remote terminal is

possible by two methods:

 X-Terminal

The connecting network should be capable of carrying X.11 protocol (protocol

for transferring graphical features)

It is advisable to provide 256 Kbit/s links in order to guarantee suitable

response time

 GO-Global

The protocol used by GO-Global guarantees suitable response time with

128 Kbit/s links. The response time is acceptable also using 64Kbit/s link

The following table summarises the above-mentioned data.

Remote Connection Required Bit Rate

X-Terminal (X.11 protocol) 256 Kbit/s sec
GO-Global 128 Kbit/sec

Ed.22 24/11/2015
26
7.3 NETWORK FOR GEOGRAPHYCAL REDUNDANCY

The connecting network provides the connection between the main and the
stand-by server .
The connection is used to maintain the two data base aligned.

The connection band is required to reduce the execution time of data base
realignment at start-up time or during a main server restore.
The required band is according to the number of managed Network Element
and is reported by the following table.

Number of NEs Required Bit Rate

Up to 500 128 Kbit/s sec
Up to 1500 256 Kbit/sec
Up to 3000 512 Kbit/sec
Over 3000 1000Kbit/s

A128Kbit/s connection is enough to support the traffic needed to maintain the

main and stand-by data base aligned

7.4 NETWORK FOR NORTH BOUND INTERFACE (NBI)

The connecting network provides the connection between the server running
NMS5UX/LX and un upper level management system.

The connection is mainly used to carry GET/SET SNMP operations, SNMP

alarm notifications and to support a file transfer.

A128Kbit/s connection is enough to support the traffic needed to support the

above described operations

Ed.22 24/11/2015
27
7.5 TCP/UDP PORT NUMBER

The following table lists the protocols and the tcp/udp ports used to exchange
data between NMS5-UX/NMS5-LX application and SIAE Network Element.

Protocols TCP/UDP Ports

SNMP (Note 3) 161 (GET & SET)
162 (Trap)
Telnet (Note 2) 23
FTP (Note 1) 21

Note 1) The FTP server is always NMS, the NE acts as a client and the
connection is always established in passive mode.
The FTP operation done by the NE are:
 File GET (Sw download)
 File PUT (NE Error and Command log transfer)
Ftp uses standard TCP ports (greater then 1024)
ALCPlus, ALPlus, ALCPlus2 and ALPLUS2 use TCP ports 4600-
4650

Note 2)
The telnet port is used only for maintenance purpose and it is
opened only for the communication from OSS to NE

Note 3)
SNMP SET/GET UDP packets sent by OSS (HP-UX operating
system) use as source port a number greater tha 49152, the ports
have to be opened in order to allow the response from the NE.

Ed.22 24/11/2015
28
The following table lists the protocols and the tcp/udp ports can be used to
access NMS5UX /NMS5-LX server by an operator station or by a presentation
server (NMS5-UX only).

Protocols TCP/UDP Ports

SSH 22
Telnet 23
FTP 21
SQL*NET 1521 (TCP)
(Oracle)
X11 Not predefined
X Window
GoGlobal 491 (Default)
NFS
Network File System 2049 (Default)

Ed.22 24/11/2015
29
7.6 OSI NETWORK DESIGN CONSTRAINT

The SIAE equipment support the first three levels of the OSI stack and in
particular the IS-IS routing protocol.

The IS-IS protocol provides a hierarchical mechanism to split the routing

domain into areas, two router types (both supported by SIAE equipment) are
foreseen:

o L1 router
It supports intra area routing

o L2 router
It supports inter area routing

The following table summarizes the constraints to be considered in an OSI

network design.

Design constraints Supported value

Max NE per area 150NE
Max number of area The following formula provides the max number of
(L2 router) supported area (N2):
N2 < (150 - N1)/4
N1 = number of NE within the area

It is possible to install the OSI stack on the HP-UX server not on NMS5-LX with
LINUX

Ed.22 24/11/2015
30
8. NMS5-UX - SYSTEM REDUNDANCY

The use of NMS5UX in conjunction with HP-UX provides the following system
redundancy options:

 System with two or more CPUs

 Hard Disk Mirroring

Redundancy is also obtainable by means of a stand-by system that is remotely

located (geographical redundancy) with respect to the main system using an
automatic Data Base alignment between main and stand-by system.

In the event that the main system fails the stand-by system has to be
reactivated manually.

9. NMS5-LX - SYSTEM REDUNDANCY

The use of NMS5-LX on XEON Server provide the following system

redundancy options:

 System with two or more CPUs

 Hard Disk Mirroring

Redundancy is also obtainable by means of a stand-by system that is remotely

located (geographical redundancy) with respect to the main system using an
automatic Data Base alignment between main and stand-by system.

In the event that the main system fails the stand-by system has to be
reactivated manually.

Ed.22 24/11/2015
31