Junos OS

Hi Experts

I have One MX480 and Two MX240 routers connected with each others. Running VPLS and L3 services b/w them.
In MX480 2 (1Gbps) port connect with server machine configure as vpls access port.
In Mx240 1 (1Gbps) port connect with Cisco switch configure as vpls Trunk port.

The issue is i m not able to ping from server to vlan on cisco switch,but
when i change MX240 port as access port same as cisco switch it can accessible.
What i observe problem is in trunk port may be.

- vpls nodes show UP.
- Mac address of clients show in vpls mac-table.

My configs.

MX480:-

 ge-1/1/3 {
        encapsulation ethernet-vpls;
        unit 0 {
            family vpls;
        }
    }


Local site: AccessZTE1 (1)
    connection-site           Type  St     Time last up          # Up trans
    3                         rmt   Up     Mar  4 04:45:39 2010           1
      Remote PE: 192.168.3.3, Negotiated control-word: No
      Incoming label: 262163, Outgoing label: 262201
      Local interface: lsi.1050624, Status: Up, Encapsulation: VPLS
        Description: Intf - vpls VPLS local site 1 remote site 3


MAC flags (S -static MAC, D -dynamic MAC,
           SE -Statistics enabled, NM -Non configured MAC)
Routing instance : VPLS
 Bridging domain : __VPLS__, VLAN : NA
   MAC                 MAC      Logical
   address             flags    interface
   00:19:c6:1c:9f:00   D        ge-1/1/5.0          
   00:1f:16:2c:de:4f   D        ge-1/1/3.0          
   00:d0:d0:a1:2e:92   D        ge-1/1/2.0          
   00:d0:d0:a1:71:b0   D        ge-1/1/4.0          
   64:16:8d:f6:f9:15   D        lsi.1050624     



MX240:-   

    ge-1/1/0 {
        vlan-tagging;
        encapsulation flexible-ethernet-services;
        unit 1 {
            encapsulation vlan-vpls;
            vlan-id 1;
            input-vlan-map pop;
            output-vlan-map push;
            family vpls;
        }
        unit 2 {
            encapsulation vlan-vpls;
            vlan-id 2;
            input-vlan-map pop;
            output-vlan-map push;
            family vpls;
        }
    }


Instance: VPLS
  Local site: AccessZTE1 (3)
    connection-site           Type  St     Time last up          # Up trans
    1                         rmt   Up     Mar  4 04:44:34 2010           1
      Remote PE: 192.168.1.1, Negotiated control-word: No
      Incoming label: 262201, Outgoing label: 262163
      Local interface: lsi.1051136, Status: Up, Encapsulation: VPLS
        Description: Intf - vpls VPLS local site 3 remote site 1


MAC flags (S -static MAC, D -dynamic MAC,
           SE -Statistics enabled, NM -Non configured MAC)
Routing instance : VPLS
 Bridging domain : __VPLS__, VLAN : NA
   MAC                 MAC      Logical
   address             flags    interface
   00:1f:16:2c:de:4f   D        lsi.1051136         
   00:d0:d0:a1:2e:92   D        lsi.1051136         
   00:d0:d0:a1:71:b0   D        lsi.1051136         
   64:16:8d:f6:f9:15   D        ge-1/1/0.2          


 

Thanks in advance

 FAS

Hello there,

I noticed You are using vlan-ids 1 and 2 on trunk port connected to Cisco switch.

AFAIK, some Cisco switches do not accept tagged frames with 802.1Q VLAN id == 1 by default. 

Try to use different VLAN id, not 1.

Rgds

Alex

Hi Alex

Thanks for the reply.

Yah I  tried with VLANID 2 and 3 with out ID 1. but the problem is still there.

l will check one more time. Alex any other advise ?

Rgds

FAS

Hi Alex

 I success to ping Valn 2 IP and there Client IP from sever connect to MX480. same scenario with other MX240 with Vlan ID 3.

but some strange behavior i found when i connected both Sites with MX240-2 and MX240-3 at a moment ping response will be drop. Like VLAN 3 IP = 192.254.0.204

                                VLAN 2 IP = 192.253.0.202 From server connect to MX480. I add 2 server connect with 2different  ports of MX480 with different subnet but output has same.

Regards

FAS

Hi.

Can you post the interface and routing-instance config on all three of your MX`s ?

Hi

MX480

    VPLS {
        instance-type vpls;
        interface ge-1/1/0.0;
        interface ge-1/1/2.0;
        interface ge-1/1/3.0;
        interface ge-1/1/4.0;
        interface ge-1/1/5.0;
        interface ge-1/1/6.0;
        interface ge-1/1/7.0;
        route-distinguisher 6555:1;
        vrf-target target:6555:420;
        protocols {
            vpls {
                site-range 20;
                no-tunnel-services;
                site AccessZTE1 {
                    site-identifier 1;
                    interface ge-1/1/3.0;
                    interface ge-1/1/2.0;
                }
            }
        }

 ge-1/1/3 {
        encapsulation ethernet-vpls;
        unit 0 {
            family vpls;
        }

MX240-3

   VPLS {
        instance-type vpls;
        interface ge-1/1/1.2;
        route-distinguisher 6555:3;
        vrf-target target:6555:420;
        protocols {
            vpls {
                site-range 20;
                no-tunnel-services;
                site AccessZTE1 {
                    site-identifier 3;
                    interface ge-1/1/1.2;
                }
            }

    ge-1/1/1 {
        vlan-tagging;
        encapsulation flexible-ethernet-services;
        unit 2 {
            encapsulation vlan-vpls;
            vlan-id 2;
            input-vlan-map pop;
            output-vlan-map push;
            family vpls;
        }

MX240-2

 VPLS {
        instance-type vpls;
        interface ge-1/1/0.3;
        route-distinguisher 6555:2;
        vrf-target target:6555:420;
        protocols {
            vpls {
                site-range 20;
                no-tunnel-services;
                site AccessZTE1 {
                    site-identifier 2;
                    interface ge-1/1/0.3;
                }
            }

  ge-1/1/0 {
        vlan-tagging;
        encapsulation flexible-ethernet-services;
        unit 3 {
            encapsulation vlan-vpls;
            vlan-id 3;
            input-vlan-map pop;
            output-vlan-map push;
            family vpls;
        }

Thanks

FAS

Hi.

I was just wondering about the GE interfaces on the MX240 routers.

With vlan-tagging and input/ouput-vlan-map rewrite rules, how does the VPLS instance treat these interfaces ? Vlan id 2 and 3 are removed on incoming frames, what vlan are they put in(if any?) then ? Default vlan ? (and in this something that is possible on the MX ?)

I am doing work now which consist of some of the same config as you are working on.On "access" ports, i also use rewrite rules, but there push the proper vlan on ingress packets and pop on egress.And the VPLS routing-instance is defined with the specific vlan aswell(no range on my setup)

Hi Stianm

The point U r mention is absolutely right. Now i created VPLS routing-instance with the specific vlan.

Appreciated

FAS

So its working now ? 🙂

i've only done VPLS with a J-Series or SRX in router mode, so forgive me if this is a dumb observation for the MX --

I don't think you need the input/output vlan-maps on the MX240 sub interfaces for this VPLS implementation.

I want to say the input/output-vlan-maps are used for some Q-in-Q type stuff (I think)

good luck,

will