[j-nsp] Site Range (out of range) for L2VPNs - Juniper MX

Serge Vautour sergevautour at yahoo.ca
Tue Aug 13 13:51:53 EDT 2013


Try site ID 2 for site LAB-C. -Serge




________________________________
 From: Austin Leyland <austin.leyland at gmail.com>
To: juniper-nsp at puck.nether.net 
Sent: Tuesday, August 13, 2013 2:07:50 PM
Subject: [j-nsp] Site Range (out of range) for L2VPNs - Juniper MX
 

Hi,

I have three MX80s in a learning lab, in is-is and ibgp full mesh.  I am
trying to configure two L2VPN circuits as follows

LAB-A port 1/1/2 vlan 510 to LAB-B port 1/1/2 vlan 510
LAB-A port 1/1/2 vlan 512 to LAB-C port 1/1/2 vlan 512

When i try to bring the circuits up, I get an 'out of range' error, even
though I have not varied the site-range from the default which I understand
to be 65535.

Instance: TEST205-2006
  Local site: LAB-C (3)
    connection-site           Type  St     Time last up          # Up trans
    1                         rmt   OR

The config I am using is :


LAB-A (loopback ip 192.168.11.10):

interfaces {
    ge-1/1/2 {
        description TEST;
        vlan-tagging;
        encapsulation flexible-ethernet-services;
        unit 510 {
            description "service 1";
            encapsulation vlan-ccc;
            vlan-id 510;
        }
        unit 512 {
            description "service 2";
            encapsulation vlan-ccc;
            vlan-id 512;
        }
}

routing-instances {
    TEST205-2005 {
        instance-type l2vpn;
        interface ge-1/1/2.510;
        route-distinguisher 192.168.11.10:510;
        vrf-target target:12345:510;
        protocols {
            l2vpn {
                encapsulation-type ethernet-vlan;
                interface ge-1/1/2.510;
                site LAB-A {
                    site-identifier 1;
                    interface ge-1/1/2.510;
                }
            }
        }
    }
    TEST205-2006 {
        instance-type l2vpn;
        interface ge-1/1/2.512;
        route-distinguisher 192.168.11.10:512;
        vrf-target target:12345:512;
        protocols {
            l2vpn {
                encapsulation-type ethernet-vlan;
                interface ge-1/1/2.512;
                site LAB-A {
                    site-identifier 1;
                    interface ge-1/1/2.512;
                }
            }
        }
    }
}


LAB-C (loopback IP 192.168.11.12):

interfaces {
    ge-1/1/2 {
        apply-groups INTERFACE-PARAMETERS-EDGE;
        description SERVICE2;
        vlan-tagging;
        encapsulation flexible-ethernet-services;
        unit 512 {
            encapsulation vlan-ccc;
            vlan-id 512;
        }
    }
}

routing-instances {
    TEST205-2006 {
        instance-type l2vpn;
        interface ge-1/1/2.512;
        route-distinguisher 192.168.11.12:512;
        vrf-target target:12345:512;
        protocols {
            l2vpn {
                encapsulation-type ethernet-vlan;
                interface ge-1/1/2.512;
                site LAB-C {
                    site-identifier 3;
                    interface ge-1/1/2.512;
                }
            }
        }
    }
}

Any idea why this is occurring?

AL
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


More information about the juniper-nsp mailing list