Professional Documents
Culture Documents
RTSO/MTS (http://10.7.44.64/)
Good to know
GNE: A GNE is connected to the NMS through a local area network (LAN) or wide area
network (WAN). Its application layer can directly communicate with the NMS
application layer.
Non-GNE: A non-GNE communicates with the GNE through the DCN channels between
NEs. It is recommended that fewer than 50 non-GNEs are affiliated to a GNE.
Access Control: The access control function is used so that the NE can be connected to
the NMS through an Ethernet service port. The PSN transmits DCN packets between the
NMS and the GNE when transmitting Ethernet services. In this case, the Ethernet service
port on the GNE should be enabled with the access control function.
N.B. From next page, consider the steps only. For value setting , follow the EMS plan
provided by TP.
Step-1(Check Plan)
10.216.4.69
GNE
Non-GNE
Non-GNE
Step-3(Add VLAN)
DHDMRK
Step-1
Step-5
301
Step-6
Step-2
Step-3
Step-4
Step-7
Step-4(Access Control)
Select the port which is passing Eth traffic
Access control IP
and Subnet Mask
10.216.7.2
10.216.4.69
115
2
3
0.0.0.0
0.0.0.0
10.216.4.69
Step-9(Reachability Test-Optional)
Step-1(Add VLAN)
4
5
301
6
2
Step-2(Port Settings-FE/GE)
Step-3(Port Settings-IF)
Step-5(Reachability Test-Optional)
NOTES
No access control setting is required for Non-GNE.
Better to start from opposite end.
Updating NE IP will disconnect NE from WebLct. To reconnect use IP auto-discovery or
use any free IP of allocated IP block.
As Non-GNE cant be checked remotely, confirm integration locally using NE search.
Must Remove all old EMS cables from NMS/COM ports. Otherwise it may create
Ethernet loop.
Ensure each IF/Modem port naming, each used FE/Ethernet port naming during
working with Each NE.
For any query or observation, send e-mail to mts@grameenphone.com.
Thank you