The sub-interface IP is reset after the IPRAN device restarts

Not involved

After the customer's RA5100 device is powered off and restarted, the interface IP configuration will be reset. The fault phenomenon is as follows:

The process of device A self-communication is as follows:

1. After device A is powered on, it automatically creates a network management self-communication loopback port (loopback 1023/4095 for our company), generates a 32-bit management address (129.X.X.X for our company) according to the default rules, automatically creates an OSPF process, and automatically creates a network management VPN instance

2. Create a 4094 sub-interface, bind the network management VPN instance, and borrow the IP address of the network management self-communication loopback interface

3. The 4094 sub-interface enables the OSPF protocol by default, uses the OSPF standard process for negotiation and route calculation, and uses a specific type 10 LSA to flood related network element information, including: manufacturer identification, device model, device MAC, NEID, NEIP V4, NEIP V6, etc.

4. After receiving the type 10 LSA from device A, device B reports a trap to the network management platform to inform that a new device A has been found.

5. After receiving the trap from device B, the network management platform learns the NEIP of device A. After determining that it is a new device, it automatically selects a management IP as the NEIP of device A according to the IP resource planning of BB, and sends the configuration (via device B, telnet to device A).

6. After the NE IP of device A is modified, the OSPF 65535 process is renegotiated, device B reports a trap again, and the network management platform automatically generates a basic configuration template and sends it to device A (telnet directly to device A through the new NEIP).

7. After the basic configuration is sent, the network management platform can directly manage device A through SNMP. After the network management personnel add the corresponding network element information (such as installation location, etc.), the A device is finally online.

Device power-on → NEID/NEIP → LLDP intercommunication → OSPF intercommunication → NMS discovery

Based on the phenomenon, it is suspected that the network management did not send neip, resulting in all sub-interfaces 4094 borrowing the 129-segment address generated by the loopback interface according to the rules.

After the customer uses ne-ip to specify the NE IP address, the IP address will not be reset.

ne-ip

Use ne-ip to configure the NE IP for an NE.

Use undo ne-ip to restore the default.

Syntax

ne-ip ip-address { mask-length | mask }

undo ne-ip

Default

The NE IP is automatically generated according to the NE ID and changes with the NE ID. The IP address takes 129 as the eight high-order bits and the NE ID as the remaining 24 bits. The mask length is 32.

Views

DCN view

Predefined user roles

network-admin

Parameters

ip-address: Specifies an IPv4 address.

mask-length: Specifies the mask length in the range of 1 to 32.

mask: Specifies the mask length in dotted decimal format.

Usage guidelines

After DCN is enabled, the system assigns an NE IP to the loopback interface with the largest interface number, and specifies the NE IP as the LLDP management address.

A manually configured NE IP overwrites the default NE IP and breaks the mapping with the NE ID.