Routing

Expand all | Collapse all

VPLS config

Jump to Best Answer
  • 1.  VPLS config

    Posted 05-31-2017 13:53

    Hello Community.

     

    I hope you are all fine today. 

     

    I am trying to set in my lab a VPLS conection between 2 SRXs. I know that this is not the SRX threat but I thought the issue fits better here. 

     

     

    I am trying to set a VPLS between 2 SRX. I've managed to do it. however I dont see to be able to ping across my 2 servers. 

     

    This is the config performed on the SRX210

     

    ge-0/0/0 {

        description TO_SRX_220;

        unit 0 {

            family inet {

                address 10.0.248.166/22;

            }

            family mpls;

        }

    }

    fe-0/0/2 {

        description TO_WINDOWS_SERVER

        vlan-tagging;

        encapsulation vlan-vpls;

        unit 660 {

            encapsulation vlan-vpls;

            vlan-id 660;

            family vpls;

        }

    }

    lo0 {

        unit 0 {

            family inet {

                address 1.1.1.1/32;

     }

     

    I am running OSPF between the SRXs as IGP and MPLS and LDP on all interfaces

     

    show protocols

    mpls {

        interface all;

    }

    ospf {

        area 0.0.0.0 {

            interface ge-0/0/0.0;

            interface lo0.0 {

                passive;

            }

        }

    }

    ldp {

        interface all;

     

     

    the VPLS instance has been set as well

     

    jchaves@SRX210HE# show routing-instances

    VPLS {

        instance-type vpls;

        interface fe-0/0/2.660;

        protocols {

            vpls {

                no-tunnel-services;

                vpls-id 660;

                neighbor 2.2.2.2;

     

    *************Config on second SRX220*************

     

     

    jchaves# show interfaces              

    ge-0/0/0 {

        description TO_SRX_210;

        unit 0 {

            family inet {

                address 10.0.248.188/22;

            }

            family mpls;

        }

    }

    ge-0/0/1 {

        description TO_MAC_OS;

        vlan-tagging;

        encapsulation vlan-vpls;

        unit 660 {

            encapsulation vlan-vpls;

            vlan-id 660;

            family vpls;

        }

    }

    lo0 {

        unit 0 {

            family inet {

                address 2.2.2.2/32;

    }

     

     

    Protocols config

     

    jchaves# show protocols

    mpls {

        interface all;

    }

    ospf {

        area 0.0.0.0 {

            interface ge-0/0/0.0;

            interface lo0.0 {

                passive;

            }

        }

    }

    ldp {

        interface all;

    }

     

    the VPLS instance

     

    jchaves# show routing-instances                  

    VPLS {

        instance-type vpls;

        interface ge-0/0/1.660;

        protocols {

            vpls {

                no-tunnel-services;

                vpls-id 660;

                neighbor 1.1.1.1;

     

     

     

     

    OK. So the conig has been listed. I know that something is missing as I am unable to ping my windows server from my MAC and vicebersa. 

     

     

    This is the MPLS, LDP and VPLS status.

     

     

    jchaves@SRX210HE# run show mpls interface

    Interface        State       Administrative groups (x: extended)

    ge-0/0/0.0       Up         <none>

     

     

    jchaves@SRX210HE# run show ldp interface

    Interface            Label space ID        Nbr count   Next hello

    lo0.0                1.1.1.1:0                2           0

    ge-0/0/0.0           1.1.1.1:0                1           2

     

    jchaves@SRX210HE# run show ldp statistics    

    Message type               Total                     Last 5 seconds

                           Sent      Received          Sent      Received

    Hello                  3907          3408             2             1

    Initialization            2             2             0             0

    Keepalive              1118          1116             1             1

    Notification              1             0             0             0

    Address                   2             2             0             0

    Address withdraw          0             0             0             0

    Label mapping             7            11             0             0

    Label request             0             0             0             0

    Label withdraw            2             7             0             0

    Label release             7             2             0             0

    Label abort               0             0             0             0

    All UDP                3907          3408             2             1

    All TCP                1138          1140             1             1

     

     

    Event type                             Total        Last 5 seconds

     

    Sessions opened                            2                  0

    Sessions closed                            1                  0

    Topology changes                           6                  0

    No router id                               0                  0

    No address                                 0                  0

    No interface                               0                  0

    No session                                 0                  0

    No adjacency                               0                  0

    Unknown version                            0                  0

    Malformed PDU                              0                  0

    Malformed message                          0                  0

    Unknown message type                       0                  0

    Inappropriate message                      0                  0

    Malformed TLV                              0                  0

    Bad TLV value                              0                  0

    Missing TLV                                0                  0

    PDU too large                              0                  0

    PDU too small                              0                  0

     

     

     

    Instance: VPLS

      VPLS-id: 660

        Neighbor                  Type  St     Time last up          # Up trans

        192.168.1.200(vpls-id 660) rmt  OL   <<<<<<<<<<<<<<<<<<<<<<<<<<<Coudl this be the problem?

        2.2.2.2(vpls-id 660)      rmt   Up     May 31 20:32:57 2017           1

          Remote PE: 2.2.2.2, Negotiated control-word: No

          Incoming label: 262145, Outgoing label: 262145

          Negotiated PW status TLV: No

          Local interface: lsi.1049344, Status: Up, Encapsulation: ETHERNET

            Description: Intf - vpls VPLS neighbor 2.2.2.2 vpls-id 660

     

     

     

    Let me know if more info is needed. 

     

     

    Thanks in advanced. 

     

     

     



  • 2.  RE: VPLS config

     
    Posted 05-31-2017 15:28

    Are your computers plugged directly into the port ge-0/0/2?

     

    I notice these ports are setup with vlan tagging enabled and a vlan id set.  Comuters are generally looking for and generating untagged frames.  So these should be setup as access mode.



  • 3.  RE: VPLS config

    Posted 05-31-2017 15:39

     

    yes. They are directly connected to those ports. 

     

    Should I remove the current config as set them as Access ports under vlan 660 with no VPLS encapsulation or any other confi than standard Ethernet Access ports?

     

     

     



  • 4.  RE: VPLS config
    Best Answer

     
    Posted 05-31-2017 16:01

    I believe the correct encapsulation then is ethernet-vpls instead of vlan-vpls and this generally requires the use of unit 0.

     

    Make the matching interface.unit change in the vpls routing instance as well.

     

    fe-0/0/2 {
        encapsulation ethernet-vpls;
        unit 0 {
            family vpls;
        }
    }
    

     



  • 5.  RE: VPLS config

    Posted 06-01-2017 08:19

     

    Thanks you. This was the missing part. after doing this on both LAN facing interfaces. the traffic worked. 

     

     



  • 6.  RE: VPLS config

    Posted 05-31-2017 23:37

    Hello,

    First things first - VPLS on SRX requires packet-mode

     

     

    https://kb.juniper.net/InfoCenter/index?page=content&id=KB30461

     

    Secondly, "OL" code usually indicated there is no transport label available for remote neighbor.

    Please post "show route table inet.3 protocol ldp" printout.

    HTH

    Thx

    Alex



  • 7.  RE: VPLS config

    Posted 06-01-2017 08:20

    Hi, 

     

    Yeah. This was another headache that I went through after noticing that not even the LDP session was being established. 

     

     

    Thanks