Case Study Page 1 of 13 Case Title： Network Management System (NMS) for RTN600 Equipment Kwan Chan Yip (K00714421) Optical Network Product Department Abstract ： Network Management system (NMS) is a system comprising software, firmware, and hardware used to manage a large and complex network. An NMS may receive alarms and alerts from multiple element management systems (EMSs), each of which manages one or more specific intelligent network elements (NEs). This study describe about transmission of the NM Information and the guide to connect NMS on OptiX RTN600 equipment. Keywords：Microwave, NMS, Ethernet, WebLCT. Case Text: Situation One NMS trial had been done. This trial had involved 11 links. This case study is to provide the guide on how to configure and connect NMS. Description of problems or challenges OptiX RTN 600 equipment can connect the network with third-party microwave equipment, either comprised between the OptiX RTN 600 equipment only or from different manufacturers. The OptiX RTN 600 provides two auto-sensing 10M/100M Ethernet NM ports, which was connected through the internal HUB. For the connection between the equipment from different manufacturers, the NM information needs to be transparently transmitted among them to ensure the centralized management of all the microwave equipment on the network. In this case, a flexible access solution to the NM system can be used and help to improve the competitive capacity of the OptiX RTN 600 equipment. [1] When the network is comprised between the OptiX RTN 600 equipment only, the HW ECC protocol data is transmitted through the uniform DCC channel among the NEs. As we know, DCC cannot be transmitted when no microwave link or optical port
Transcript
Case Study
Page 1 of 13
Case Title： Network Management System (NMS) for RTN600 Equipment
Kwan Chan Yip (K00714421)
Optical Network Product Department
Abstract：Network Management system (NMS) is a system comprising software,
firmware, and hardware used to manage a large and complex network. An NMS may
receive alarms and alerts from multiple element management systems (EMSs), each of
which manages one or more specific intelligent network elements (NEs). This study
describe about transmission of the NM Information and the guide to connect NMS on
OptiX RTN600 equipment.
Keywords：Microwave, NMS, Ethernet, WebLCT.
Case Text:
Situation One NMS trial had been done. This trial had involved 11 links. This case study is
to provide the guide on how to configure and connect NMS.
Description of problems or challenges
OptiX RTN 600 equipment can connect the network with third-party microwave
equipment, either comprised between the OptiX RTN 600 equipment only or from
different manufacturers. The OptiX RTN 600 provides two auto-sensing 10M/100M
Ethernet NM ports, which was connected through the internal HUB.
For the connection between the equipment from different manufacturers, the NM
information needs to be transparently transmitted among them to ensure the centralized
management of all the microwave equipment on the network. In this case, a flexible
access solution to the NM system can be used and help to improve the competitive
capacity of the OptiX RTN 600 equipment. [1]
When the network is comprised between the OptiX RTN 600 equipment only, the
HW ECC protocol data is transmitted through the uniform DCC channel among the NEs.
As we know, DCC cannot be transmitted when no microwave link or optical port
Case Study
Page 2 of 13
connection exists between two sets of OptiX RTN 600 equipment. Therefore, the network
cables is using to connect the NE cascading ports between two sets of OptiX RTN 600 to
implement the ECC communication and transmit the NM information. [1]
This case study was concentrated on comprised between the OptiX RTN 600
equipment and describe about transmission of the NM Information and the guide to
connect NMS on OptiX RTN600 equipment.
This NMS trial was done:
1. To configure IP address at Huawei GNE radio link.
2. To test connectivity from NOC to NE through Kuantan GNE (Test visiblility router
from Kuala Lumpur up to Kuantan, and NE at GNE site up to last mile).
3. To initial / discover NE up to last mile.
4. To test NE NMS function.
Analysis, Strategies and Actions
We connect the internal HUB Ethernet for site A to site L via NM ports.
A B D C
H G F E
I J K L
Figure 1 NMS Lan cable connection
Case Study
Page 3 of 13
A BF CE
G
D
IH J K L
Figure 2 Visio NMS Connection
1. Connection between OptiX RTN and router.
We need to connect the NM port in site A, which was between OptiX RTN
620 and customer’s router which will connect to HQ Kuala Lumpur.
Figure 3 OptiX RTN 620
Figure 4 Router
Case Study
Page 4 of 13
Figure 5 Connection from OptiX RTN 600 to router via Lan cable
2. Connection between OptiX RTN and OptiX RTN.
We need to connect the NM port for other OptiX RTN equipment to
access the NMS. We connect Eth Hub to Eth to extend the Nm signal, where we
connect ETH HUB for upper equipment and connect to HUB for lower equipment.
Figure 6 SCC front panel
Case Study
Page 5 of 13
F
ETH HUB
ETH
igure 7 SCC front panel
There are two extension modes for the extended ECC which we can configure via
WebLCT:
1. Automatic mode
On an Ethernet, the NE with the largest IP address is automatically
considered as server and other NEs are automatically clients. The NEs
automatically establish TCP connections between the server and clients
and also establish corresponding MAC connections according to the TCP
connections. In the automatic mode, the server and clients need not be
manually specified.
2. Manual mode
In the manual mode, NEs establish TCP connections between the server
and clients according to the server, clients, IDs of connecting ports, which
are set manually and other information that is entered manually. They then
establish corresponding MAC connections according to the TCP
connections.
1. Select the NE from the Object Tree in the NE Explorer. Choose
Communication > ECC Management from the Function Tree.
Case Study
Page 6 of 13
F
2. Set the ECC extended mode. If ECC Extended Mode is set to
Auto mode, other parameters are invalid.
3. Set other parameters when the ECC extended mode is set to the
manual mode.
For the equipment which connects to router, we need set to Specified Mode. We will enter the parameters manually, while the other equipments from other sites in this
NMS connection were set to Auto Mode, where the largest IP address will be considered
as server.
igure 8 ECC Management
Case Study
Page 7 of 13
Next, we need to enter the IP address, subnet mask and gateway into the IDU that
we set to Specified Mode, which was connecting directly to router. In this case, the IDU
is in Wisma Celcom. An Internet Protocol (IP) address is a unique number that can
identify each host on a network. Gateway IP refers to a device on a network which sends
local network traffic to other networks, and subnet mask number helps to define the
relationship between the host and the rest of the network. In this case, the IP address,
subnet mask and gateway were given by the customer, which was record in their
database. Therefore, we just need to key in the related information and parameter into
the communication parameter setting.
HQ
Region office
igure 9 IP information & Parameter F
Case Study
Page 8 of 13
igure 10 NE Communication Parameter Setting F
Result
Now, we can connect the entire network via NMS. We now can access and login
from any of these site which was connect to NMS (Site A – Site L) and remote all others
site via remote and manage all site’s information.
F igure 11 NE Search list (Before Logged In)
Case Study
Page 9 of 13
Site Name
F igure 12 NE Search list (After Logged In)
F igure 13 NE ECC Link Management List
Case Study
Page 10 of 13
Suggestion or Review
For information, there was NO service will affected when we connect to NMS and
configure the IP address for router according to nature of work.
Besides, the NE cascading ports cannot be connected as a ring due to network
broadcast storm may occur, which will causes repeated reset of the SCC board [1]. As
both the Ethernet NM ports and the NE cascading ports on the SCC board of the OptiX
RTN 600 support the MDI and MDI-X auto-sensing function the network cable used for
the extended ECC can be the straight-through cable or the crossover cable. (The cable
type’s information will be provided below).
We also need to plan the IDs of NEs for all IDU in NMS. We need to follow few principles
when planning NE IDs [2]:
• The IDs of the NEs in a DCN should not be repeated.
• When the number of existing NEs does not exceed the range represented by the
basic ID, do not use the extended ID if possible.
Case Study
Page 11 of 13
Reference
[1] Song Xiaobin (2005), NM System Access Solutions for the OptiX RTN 600. Huawei Technologies Co., Ltd.
[2] Kwan Chan Yip (2008). Modified the NE ID on WebLCT. Huawei Technologies Co.,Ltd. [3] http://www.ertyu.org/steven_nikkel/ethernetcables.html
Date accessed: 20.10.2008 [4] http://en.wikipedia.org/wiki/Ethernet_crossover_cable Date accessed: 20.10.2008 [5] http://www.yourdictionary.com/nms Date accessed: 20.10.2008 [6] http://www.more.net/technical/netserv/tcpip/viewip.html
Source: NM System Access Solutions for the OptiX RTN 600
Figure 15 Modular plug pin positioning
igure 16 ETH/ETH-HUB interface pin assignment F
Case Study
Page 13 of 13
Table 1 ETH/ETH-HUB interface pin assignment
Interface Pin Signal
1 Transmitting data (+)
2 Transmitting data (-)
3 Receiving data (+)
6 Receiving data (-)
ETH/ETH-HUB
4, 5, 7, 8 Reserved The ETH/ETH-HUB interface supports MDI/MDI-X auto-sensing, which means it can also transmit data through pins 3 and 6, and receive data through pins 1 and 3.
Table 2 Straight-Through Wiring (both ends are the same)
RJ45 Pin # Wire Color (T568B)
Wire Diagram(T568B)
10Base-T Signal 100Base-TX Signal 1000Base-T Signal
