Even though a configured VPLS site-identifier parameter is greater than site-range, the configuration appears to be committed successfully; no any error messages are logged or displayed. However, the VPLS connection is out of range and goes down. This article describes the cause of this behavior and explains that it is expected.

When a VPLS is configured with the site-identifier parameter greater than the site-range, the VPLS connection will be out of range and will go down. However, the configuration is accepted without any error message being logged or displayed. Customers receive no warning or error message displayed during the commit operation.

Normal behavior: In the following example, the site-range is 20 and site-identifier is in range.

TEST2 {
    instance-type vpls;
    interface ge-0/1/8.0;
    route-distinguisher 6.6.6.6:1;
    vrf-target target:10:60;
    protocols {
        vpls {
            site-range 20; 
            interface ge-0/1/8.0 {
                 encapsulation-type ethernet;
            }
            no-tunnel-services;
            site test {
                site-identifier 19; 
            }
        }
    }
}

The VPLS session is up without any problem. To verify this, run the command show vpls connections.

[edit routing-instances]
root@mx480xxx# run show vpls connections
Layer-2 VPN connections:

Legend for connection status (St)
EI -- encapsulation invalid NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down NP -- interface hardware not present
CM -- control-word mismatch -> -- only outbound connection is up
CN -- circuit not provisioned <- -- only inbound connection is up
OR -- out of range Up -- operational
OL -- no outgoing label Dn -- down
LD -- local site signaled down CF -- call admission control failure
RD -- remote site signaled down SC -- local and remote site ID collision
LN -- local site not designated LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status IL -- no incoming label
MM -- MTU mismatch MI -- Mesh-Group ID not available
BK -- Backup connection ST -- Standby connection
PF -- Profile parse failure PB -- Profile busy
RS -- remote site standby SN -- Static Neighbor
LB -- Local site not best-site RB -- Remote site not best-site
VM -- VLAN ID mismatch

Legend for interface status
Up -- operational
Dn -- down

Instance: TEST2
Edge protection: Not-Primary
Local site: test (19)
connection-site Type St Time last up # Up trans
10 rmt Up Mar 15 15:48:54 2016 1
Remote PE: 2.2.2.2, Negotiated control-word: No
Incoming label: 262194, Outgoing label: 262179
Local interface: lsi.84934656, Status: Up, Encapsulation: VPLS
Description: Intf - vpls TEST2 local site 19 remote site 10

Out-of-range behavior: The following example shows what happens to the VPLS session when the site-identifier is configured out of range.

lab@mx480xxx# set protocols vpls site test site-identifier 21 

[edit routing-instances TEST2]
lab@mx480xxx# commit 
commit complete

[edit routing-instances]

lab@mx480xxx# show 
TEST2 {
    instance-type vpls;
    interface ge-0/1/8.0;
    route-distinguisher 6.6.6.6:1;
    vrf-target target:10:60;
    protocols {
        vpls {
            site-range 20;
            interface ge-0/1/8.0 {
                encapsulation-type ethernet;
            }
            no-tunnel-services;
            site test {
                site-identifier 21;
            }
        }
    }


lab@mx480xxx# run show vpls connections 
Layer-2 VPN connections:

Legend for connection status (St)   
EI -- encapsulation invalid      NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch     WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down    NP -- interface hardware not present 
CM -- control-word mismatch      -> -- only outbound connection is up
CN -- circuit not provisioned    <- -- only inbound connection is up
OR -- out of range               Up -- operational
OL -- no outgoing label          Dn -- down                      
LD -- local site signaled down   CF -- call admission control failure      
RD -- remote site signaled down  SC -- local and remote site ID collision
LN -- local site not designated  LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status  IL -- no incoming label
MM -- MTU mismatch               MI -- Mesh-Group ID not available
BK -- Backup connection          ST -- Standby connection
PF -- Profile parse failure      PB -- Profile busy
RS -- remote site standby        SN -- Static Neighbor
LB -- Local site not best-site   RB -- Remote site not best-site
VM -- VLAN ID mismatch

Legend for interface status 
Up -- operational           
Dn -- down

Instance: TEST2
Edge protection: Not-Primary
  Local site: test (21)
    connection-site           Type  St     Time last up          # Up trans
    10                        rmt   OR   

The Junos OS system does not check the VPLS site-range parameter during the commit check.

This is expected behavior. Please check the VPLS site-identifier parameter before committing the configuration.