This section describes the roadmap for configuring the DCN function that enables the U2000 to load and manage NEs.
On a PTN network, the OptiX PTN 7900-24 NEs and core nodes connected to an external DCN network act as gateway NEs (GNEs). GNEs connect to the external DCN network through management interfaces, and the entire PTN network is managed using the management-plane DCN solution. The management-plane DCN solution requires U2000 routes to be imported to the management-plane dynamic routes of PTN NEs, a U2000-destined route to be generated in the DCN OSPF domain for DCN packet forwarding, and OptiX PTN 7900-24-destined static routes to be configured.
The process of DCN solution configuration is as follows:
- Search and create the active and standby GNEs in the U2000 LCT.
- Configure the FTP service for the GNEs.
Configure GNEs to interwork with the U2000.
When the DCN solution traverses a Layer 3 network:- Configure the IP addresses of the interface connecting the Layer 3 network to the U2000, the interfaces connecting the Layer 3 network to the active and standby GNEs, and the interfaces connecting the switches on the Layer 3 network to be on different network segments.
- On the Layer 3 switches connected to the active and standby GNEs, configure static routes destined for the management IP addresses of the GNEs, with the IP addresses of the GNEs' interfaces connected to the Layer 3 network as the next hops. In addition, advertise the static routes. On the Layer 3 switch connected to the U2000, advertise the direct route.
- On the U2000 server, configure aggregated static routes destined for the IP addresses of all the PTN NEs, with the IP address of the interface connecting the Layer 3 switch to the U2000 as the next hop.
- Configure BFD on the interfaces connecting the active and standby GNEs to Layer 3 switches.
- On each pair of PTN GNEs, configure static routes destined for the U2000, with the IP addresses of the GNEs' interfaces connected to the Layer 3 switches as the next hops. In addition, associate BFD between Layer 3 switches. For the active and standby GNEs, import the static routes destined for the U2000 to the OSPF DCN process and advertise the routes to other indirectly connected GNEs.
When the DCN solution traverses a Layer 2 network:- Configure VRRP protection for the active and standby GNEs, with the virtual IP address of the VRRP protection group as the next hop of the routes from the U2000 to the GNEs.
- Configure static routes between the U2000 and the active and standby GNEs to prevent a protection failure. The failure may be resulted from the matching of a direct route when the U2000 accesses the active or standby GNE whose IP address is on the same network segment as the NE IP address. In addition, ensure that the mask of a static route is longer than that of a direct route.
- On the active and standby GNEs, configure static routes destined for the U2000, with the administrative interfaces of the GNEs as outbound interfaces. Then, import the routes to the OSPF process.
- Configure the Layer 2 network to bear VRRP between the active and standby GNEs. Alternatively, configure a VRRP heartbeat link between A and B and configure VRRP to track administrative interface status.
- Set IP addresses for the GNEs.
- Configure the indirectly connected GNEs and get them online.
- Set the NE name and ID of each indirectly connected GNE.
- Configure the global SNMP parameters.
- Configure NE communication parameters.
- In the U2000 main topology, create NEs by means of search.
NOTE:If NEs go online using the default SNMP and remote login parameters, modify the parameters according to security requirements.
