This section describes the networking capability of a DCN subnet.
A GNE connects to the NMS using the TCP/IP protocol. In general, the NE that connects to the NMS through a LAN or WAN is a GNE. The NMS application layer can directly communicate with the application layer of the GNE. The NMS can connect to one or more GNEs. A GNE and the non-GNEs connected to it comprise a management domain. The NMS accesses a non-GNE in the management domain through the GNE.
GNEs communicate with non-GNEs through the DCN channels between them. Non-GNEs can communicate with an NMS only through a GNE.
Due to the inherent limitations of the DCC protocol, there is a limit on the number of NEs (physical NEs with unique IDs) in a network even though there are sufficient GNEs. If the number of NEs in a network exceeds the limit, the network must be divided into multiple DCN subnets.
The DCN subnet scale varies depending on the communication protocol used by the DCN subnet. The details are as follows:
When the HWECC protocol is used, the upper limit on physical NEs on a DCN subnet is 200 (100 or less is recommended).
When the IP over DCC protocol is used, the upper limit on physical NEs on a DCN subnet is 64.
When the OSI over DCC protocol is used, the upper limit on physical NEs on a DCN subnet is 100.
Multiple GNEs can be configured for a DCN. GNEs bridge the DCN communication between an NMS and the non-GNEs that are connected to the GNEs. The GNEs forward communication traffic between the NMS and non-GNEs. Users must manually specify a GNE for non-GNEs.
Each GNE can connect to a maximum of 50 non-GNEs, regardless of the protocol. If there are more than 50 non-NEs for one GNE, another GNE must be added.