Alcatel-Lucent - Proprietary See notice on first page.
Issue 1.0, October 2012 2 - 7
...
System interfaces
Figure
Figure 2 shows the different NTM interfaces.
Figure 2 NTM Interfaces
Network elements
NTM supports various switches in the network that are equipped with the generics shown in Table 1.
Reference: Chapter 10, “Time Synchronization” in the System Administration Guide Table 1 NTM supported switch GENERIC
Switch Type
1A ESS 1ae8, 1ae9, 1ae10 1ae11, 1ae12, 1ae13_0
4ESS 4e12, 4e13 4e14, 4e15, 4e16, 4e17, 4e18, 4e19, 4e20, 4e21, 4e22, 4e23, 4e27, 4e28 5ESS 5e4, 5e5, 5e6 5e7, 5e8, 5e9, 5e9_2, 5e10, 5e11,
5e12, 5e13, 5e14, 5e15, 5e16, 5e16_1, 5e16_1h, 5e16_2 DMS 100/200 dms24, dms25,
dms26, dms27, dms28
na007, na009, na010, na012, na013, na014, na016, na017, sn05_100
DMS 250 ucs07, ucs08, ucs09, ucs12, ucs13, ucs14, ucs16, sn04tdm, sn05_250 DMS 500 ncs06, ncs07, ncs10, ncs12, ncs13,
ncs14, ncs16, ncs17, sn05_500
EWSD ewsd10, ewsd11, ewsd12, ewsd13,
ewsd13a, ewsd16
sn02, sn03, sn04, sn05, sn06, sn07, sn08
GTD-5 gtd1641, gtd1711, gtd1721,
gtd1722, gtd1732, gtd4003
Sonus GSX gsx5_1, gsx5_2
Sonus PSX psx5_1, psx5_2
DCC fepr1, tdms1, tdms2, tdms3, npm6.0
NMS
...
Alcatel-Lucent - Proprietary See notice on first page.
Issue 1.0, October 2012 2 - 9
Managing the network element interface
The data collector manages the interface to the network entity in NTM. The 5-minute data provides you with time for analysis after seeing the data. The act (activate) and deact
(deactivate) commands allow you, on a per-entity basis, to activate or deactivate the collection of 5-minute data from a network entity. You may or may not want to see the data for all network entities. If, for example, there is a network entity that is overloaded, you might not want to continue collecting data from that entity until the network is back to normal.
Important! The linkstat (link status) command determines the per-entity data collection status for all office and data types at any time.
Reference: See the “act” (p. 4), “deact” (p. 11), and “linkstat” (p. 9) commands in the Input Commands Guide.
Data collection concentrators
DCC (Data Collection Concentrator) is the generic term for a network element that collects and concentrates data from multiple network elements. This information is then passed on to NTM. DCC systems include EADAS (Engineering and Administrative Data Acquisition System), FEP (Front-End Processor), NPM and TDMS (Traffic Data
Management System). With this interface, the switch polling order and the data volume for each switch is detected automatically, and the user does not have to determine any switch-to-DCC mapping. Also, the switch status can be displayed with the linkstat
command.
Important! NTM also supports DCOS (Data Collection Operations System) as an EADAS.
EADAS interface
NTM no longer provides an EADAS interface via Datakit; customers must update from DCOS to a Telecordia NPM (Network Performance Monitor), which utilizes TCP/IP to implement the EADAS interface.
Data collection for 1A ESS, 5ESS, DMS, EWSD, and LSSGR switches is accomplished via an EADAS interface, which is used as a data concentrator for these switches. Many switch types can also be connected directly to NTM via TCP/IP.
Front-end processor (FEP)
The FEP (Front-End Processor) is one type of data collection concentrator that collects and concentrates data from the 5ESS, DMS, and GTD-5 switch types. This information is then passed on to NTM. This data can be collected via Ethernet. If support for GTD-5 switches is needed, then the FEP is the data concentrator.
Traffic data management system
The TDMS system is a type of data collection-concentrator that collects and concentrates data from the 1A ESS, 5ESS, and DMS 250 switches types. NTM supports two types (classes) of TDMS generics:
• TDMS1 is treated as an EADAS
• TDMS2 is treated as a FEP
Data collection operations system
The DCOS system is a type of data collection-concentrator. It is treated by NTM as a 1BED6 EADAS.
Office connectivity
The preferred method of connectivity between network elements and the NTM host is through TCP/IP direct connections. Some switches may not have the capability to connect through TCP/IP and may still be mediated through various types of DCC’s or FTP links.
DCC’s are connected to the NTM host through a TCP/IP connection.
Purchasable features may need to be installed before TCP/IP direct connectivity is available.
Reference: “List of purchasable features” (p. 2)
Connecting Network elements to the NTM host via TCP/IP has many benefits including:
• Improved switch to NTM host communications.
The use of TCP/IP over an Ethernet network will significantly speed up the transfer of data, control, and audit messages between an office and the NTM host.
TCP provides reliable, error free data exchange.
• Increased effectiveness of the NTM Feature Set Data Collection.
Increasing the speed and throughput of the data collection network may result in fewer switches reporting late data.
• Increased Reliability of the NTM Feature Set Data Collection.
Providing a reliable data network may result in fewer errors in the data reported.
• Reduce maintenance cost by eliminating network DCC’s.
Reference: For a description of the NTM protocol stack for 4ESS switches, see Chapter 10, “Time Synchronization” in the System Administration Guide
...
Alcatel-Lucent - Proprietary See notice on first page.
Issue 1.0, October 2012 2 - 1 1
TCP/IP ports used by NTM
Table 2 shows the ports reserved by NTM and official ports used by NTM. These are defined in the “/etc/services” file. As a general rule, check with your system administrator to confirm ports before proceeding with any configuration changes. Table 3 shows other ports that may be required by NTM.
Network
Element Type DCC Connection TCP/IP Connection
DCC Mediated Offices
4ESS Prior to NTM Release 13, 4ESS offices were connect through BX.25 links. Beginning with Release 13 there is either a Datatek DT-4180 interface device or AISwitch interface between the 4ESS office and the NTM host.
Not Applicable
1A ESS 1ae11 and later Not Applicable
EWSD ewsd10 and later Not Applicable
LSSGR lssgr87 Not Applicable
DCC Mediated or TCP/IP Connected Offices
5ESS 5e4 to 5e15 5e15+
NTM does not support Phase 1 DMS switches. See special considerations for dealing with these switches in Chapter 2, “Commands for Auditing Network Elements” in the Input Commands Guide.
DMS 100/200 dms24+, na007 to na013 na013+, sn05_100+
DMS 250 ucs07 to ucs13 ucs13+, sn04tdm+, sn05_250+
DMS 500 ncs06 to ncs13 ncs13+, sn05_500+
GTD-5 gtd1641+ (Data collect via a FEP) gtd4003+
TCP/IP Only Connected Offices SCSNSN
(Succession)
Not Applicable sn02+
sn06+ uses FTP links
Sonus GSX Not Applicable gsx5_1+
Sonus PSX Not Applicable psx5_1+
DCC fepr1+, tdms1+, npm6_0+
NMS
Important! Ports that may be used by HP-UX are not listed in this document Table 2 Ports reserved by NTM and official ports used by NTM
Official Service Name
Port/
Protocol Description
http 80/tcp HTTP server
https 443/tcp Secure http server
ldap 389/tcp LDAP server
ldaps 636/tcp Secure LDAP server
dcolnms 50022/tcp NTM BDR DCOLNMS
nmsrcv 50023/tcp NTM BDR NMSRCV
auappletserv 8085/tcp NTM GUI Auto Update Server
ssh
40000-46143
Local SSH ports for Succession secure interface
ErrorLogServer 4400/tcp NTM GUI Error Log Server 3800/tcp NTM Network overview server 18085/tcp NTM Historical clock server 10724/tcp GTD-5
9553/tcp SCSN SDN 9554/tcp SCSN SDN 9555/tcp SCSN SDN Table 3 Other Ports that may be required by NTM
Official Service
Name Port/Protocol Description
exec 512/tcp Remote execution, password
required
login 513/tcp Remote login
shell 514/tcp Remote command
ntp 123/udp Network Time protocol
syslog 514/udp Remote system logging
printer 515/tcp Remote print spooling
ftp 20/tcp File Transfer Protocol (Data)
...
Alcatel-Lucent - Proprietary See notice on first page.
Issue 1.0, October 2012 2 - 1 3
Important! NTM uses port numbers that are already registered in /etc/services for other applications (e.g. port 4400). NTM is using alias functionality.
Graphic workstations and PCs
Graphic workstations or PCs are used with NTM to show network view displays. They provide a high-level view of the network, intended to alert network managers to potential problems. The server workstation is connected to the client workstations or PCs, through TCP/IP over an Ethernet network in a server/client configuration. The server and client workstations or PCs are connected to the host computer through the Ethernet network.
These can be optionally configured to project the displays onto a wallboard.
User terminals
User terminals for NTM are connected to the host computer through the Ethernet network.
NTM also supports terminals that implement the X-windows standard and interface over the Ethernet.
System printers
The system printer is under the control of the print spooler; it is available for any user to print files. The HPJet printer or an equivalent model is recommended. Use of multiple printers is possible.
ftp 21/tcp File Transfer Protocol (Control)
ftp >1024/tcp Succession offices File Transfer Protocol - passive mode (Data) ssh 22/tcp Secure logins, file transfers (scp,
sftp) and port forwarding
telnet 23/tcp Virtual Terminal Protocol
smtp 25/tcp Simple Mail Transfer Protocol
Table 3 Other Ports that may be required by NTM
...