Changing the Logical Loopback Interface for Provisioning
The loopback interface supports many different network and operational functions and is an always-up interface. This means that the loopback interface ensures that the device is reachable, even if some of the physical interfaces are down or removed, or an IP address has changed. In most cases, you always define a loopback interface.
Junos OS follows the IP convention of identifying the loopback interface as lo0.
Junos OS requires that the loopback interface always be configured with a /32 network mask, thus avoiding any unnecessary allocation of address space.
Typically, the VRF or virtual-router routing instance IP address is drawn from among the IP addresses associated with interfaces configured for that routing instance. If none of the interfaces associated with a VRF or virtual-router routing instance is configured with an IP address, you need to explicitly configure a logical loopback interface with an IP address. This interface must then be associated with the routing instance.
You change the logical unit of the loopback interface to be a logical unit other than unit 0 to be used as the default loopback logical interface for all provisioning tasks that are initiated from Connectivity Services Director
Although Junos OS allows you to assign multiple loopback addresses to the same loopback unit, the Junos Space software recognizes only the first address assigned to the loopback unit. Therefore, when you change the loopback address of an N-PE device, it must be to that of a different loopback unit.
To change the logical unit of the loopback interface: