Feature Requirements |
Series |
Models |
|---|---|---|
1. Telecom DCN cannot be enabled using the LLDP association mode on the AP. (1) If a device has been configured as an AP, telecom DCN cannot be enabled using the LLDP association mode. (2) After a device on which telecom DCN has been enabled using the LLDP association mode goes online as an AP, the telecom DCN configuration is automatically deleted. 2. You can enable telecom DCN using a PAF or License file. However, this mode is not recommended because it has the following restrictions: An interface enabled with telecom DCN generates a VLAN 4094 sub-interface. If the telecom DCN configurations on the AP and master are different, the following restrictions apply: (1) When the AP's internal communication interface is the default telecom DCN interface and the telecom DCN function is not enabled on the master's internal communication interface, if the configuration delivered on the master's internal communication interface conflicts with the VLAN 4094 sub-interface, the actual configuration on the AP's internal communication interface does not take effect. For example, the internal communication interface of the master is added to a trunk interface. (2) When the AP's external communication interface is the default telecom DCN interface but the master's extended interface does not support telecom DCN, if the configuration delivered to the master's extended interface conflicts with the VLAN 4094 sub-interface, the actual configuration does not take effect on the AP's external communication interface. For example, the VLAN 4094 sub-interface is configured on the master's extended interface. If telecom DCN is enabled on an AP, internal communication and external communication interfaces on the AP may fail to be added to a trunk interface, or the 4094 VLAN or 4094 sub-interface configuration cannot be used on the external communication interface. As a result, service forwarding is affected. Don't use the device that enables the telecom DCN as the AP. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Destination ports (listening) TCP ports 5432 and 1400, UDP ports 1400 and 1500, and source ports UDP ports 1405, 1400, 1401, and 1402 are well-known ports for the DCN feature and cannot be occupied by users. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The GNE and NE security encryption functions are as follows: 1. Disable channel encryption from the NE first and then from the GNE. Otherwise, the NE cannot process the packets sent by the GNE. 2. If PTN devices and routers in transport mode are not configured in sequence, NEs cannot process packets from the NMS. 3. After channel encryption is disabled from the NE, the NE cannot parse the encrypted packets sent from the GNE and discards the packets until channel encryption is disabled on the GNE. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In transport mode, physical interfaces' DCN VLANs and service VLANs are exclusive, and physical interfaces' DCN VLANs cannot be configured on sub-interfaces. Commands related to service VLANs that are exclusive with DCN VLANs: Commands on main interfaces: port default vlan port trunk allow-pass vlan Command on sub-interfaces: vlan-type dot1q Service VLANs cannot be configured after a DCN VLAN is configured.Plan VLANs properly. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
China Telecom DCN does not support automatic ISSU enabling. After a device is upgraded from a version that does not support Telecom DCN or an earlier version that does not support Telecom DCN to a version that supports Telecom DCN using ISSU, Telecom DCN cannot be automatically enabled. Method 1: Restart the device after the ISSU upgrade is complete. Method 2: If the telecom DCN has been enabled on other adjacent devices, the local device can automatically enable the telecom DCN through LLDP association. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A GNE can be managed by a maximum of 17 NMSs.The device fails to be maNoneged through QX if there are more than 17 NMSs. Wait for the expiry of invalid TCP connections. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |