Pre-staging rules are predefined. These rules contain criteria for classifying the MPLS role of each device, in addition to recommending which physical interfaces should be UNI interfaces. For each recommended UNI interface, the system recommends its primary loopback address and its VLAN pool profile.

Correctly assigning MPLS roles to devices is critical for provisioning the correct MPLS behavior. Each MPLS role has a different behavior. For example, N-PE is the only role allowed to terminate MPLS sessions..

N-PE Device Classification Rules

The system recommends the N-PE role for devices that satisfy the following criteria:

• The comment field in the device configuration identifies the device as an N-PE device.
• The device role is set to N-PE unless EBGP is enabled for the device. Specifically, the device role is set to N-PE unless the device configuration has configuration/protocols/bgp/group/type set to external. IF EBGP is enabled, the device role is set to P.
• The device is assigned a loopback address. A device that has no loopback address cannot function as an N-PE device.
• LDP is enabled on the loopback interface for the device. LDP must be enabled on the loopback interface if the device is to be a assigned the PE MPLS role. (Required point-to-point Ethernet services.)
• L2 VPN signaling for BGP is enabled. Specifically, the rule checks whether the device configuration has configuration/protocols/bgp/family/l2vpn/signaling or configuration/protocols/bgp/group/l2vpn/signaling set. (Required for Layer 2 Ethernet services.)
• inet-vpn unicast for BGP is enabled. Specifically, the rule checks whether the device configuration has configuration/protocols/bgp/family/inet-vpn/unicast set. (Required for Layer 3 VPN services.)

UNI Classification Rules

Before an interface on an N-PE device can be provisioned as a UNI, it must satisfy the following criteria:

• The interface must be Gigabit Ethernet (ge), 10-Gigabit Ethernet (xe), Aggregated Ethernet (ae), or Fast Ethernet (fe) type.

  Fast Ethernet (fe) interfaces are supported for the Ethernet service configurations (on M Series devices with Junos OS Release 10.2R1.6).

• Checks for Gigabit Ethernet (ge) interfaces within an Aggregated Ethernet (ae) interface. Excludes Gigabit Ethernet interfaces that are configured within an Aggregated Ethernet interface from UNI assignment.
• Checks for bridge family on logical interfaces. Excludes interfaces from UNI assignment if interface configuration on the device has /interface/unit/family/bridge set.
• Checks for the following configurations on a device interface. An interface is excluded from UNI assignment when all of the following configurations are present and the logical interface is Unit 0:
  • An IP address is defined on the physical interface. The interface configuration on the device has interface/unit/name/../family/inet/address/name set. For example:

    interfaces {				
    	ge-0/1/0 {
      		unit 0 {
    			family inet {
    				address 10.10.30.52;
    			} 
     		}
    	}
    }
    

  • MPLS is enabled on the physical port. The interface configuration on the device has interface/unit/name/../family/mpls set. For example:

    interfaces {				
    	ge-0/1/0 {
    		unit 0 {
    			family mpls;
     		}
    	}
    }
    

  • OSPF is running on the logical interface. The interface configuration on the device has configuration/protocols/ospf/area/interface set. For example:

    interfaces {				
    	ge-5/0/0 {
       	unit 0 {
    			family inet {
    				address 10.10.34/30;
    					} 
     			family mpls;
    					}
    			}
    	}
    protocols {
    	ospf {
    		traffic-engineering;
    			area 0.0.0.0. {
    				interface ge-5/0/0.0;
    			}
    		}
    	}
    

  • MPLS is running on the physical interface. The interface configuration on the device has configuration/protocols/mpls/interface set. For example:

    interfaces {				
    	ge-5/0/0 {
      		unit 0 {
    			family inet {
    				address 10.10.34/30;
    			} 
    			family mpls;
    			}
    		}
    	}
    protocols {
    	mpls {
    		interface ge-5/0/0.0;
    		}
    	}
    	

VLAN Pool Profile Classification Rules

The Junos Space software assigns VLAN pool ranges to the UNIs, depending on the configured encapsulation.

Auto Discovery Only

The Junos Space software enables the router to process only the autodiscovery network layer reachability information (NLRI) update messages for LDP-based VPLS update messages.

AS Number Check

The Junos Space software checks for the Autonomous System (AS) number of a device. If the AS number is not configured for a device, the Service Capability is assigned as Layer 2.