Junos OS

 View Only
last person joined: 18 hours ago 

Ask questions and share experiences about Junos OS.
  • 1.  Problem to use labels of other routing-instance in VPLS connection

    Posted 09-28-2022 12:12
    Hello friends,

    I have a scenario with a VPLS where I would need to use the labels and ips from another table (not the master) and I'm having difficulty.

    Follow my current configuration

    set interfaces ge-0/0/0 flexible-vlan-tagging
    set interfaces ge-0/0/0 encapsulation flexible-ethernet-services
    set interfaces ge-0/0/0 unit 3904 encapsulation vlan-vpls
    set interfaces ge-0/0/0 unit 3904 vlan-id 100
    set interfaces ge-0/0/0 unit 4050 vlan-id 4050
    set interfaces ge-0/0/0 unit 4050 family inet address 172.17.1.106/24
    set interfaces ge-0/0/0 unit 4050 family mpls mtu 1450
    set interfaces irb unit 100 family inet address 192.168.1.1/24
    set interfaces lo0 unit 0 family inet address 1.1.1.1/32
    set routing-instances VS-IDC protocols ospf area 0.0.0.1 interface ge-0/0/0.4050 interface-type p2p
    set routing-instances VS-IDC protocols ospf area 0.0.0.1 interface lo0.0 passive
    set routing-instances VS-IDC protocols ldp interface ge-0/0/0.4050
    set routing-instances VS-IDC protocols ldp interface lo0.0
    set routing-instances VS-IDC protocols mpls interface ge-0/0/0.4050
    set routing-instances VS-IDC protocols mpls interface lo0.0
    set routing-instances VS-IDC instance-type virtual-router
    set routing-instances VS-IDC interface ge-0/0/0.4050
    set routing-instances VS-IDC interface lo0.0
    set routing-instances vpls protocols vpls encapsulation-type ethernet
    set routing-instances vpls protocols vpls no-tunnel-services
    set routing-instances vpls protocols vpls vpls-id 3904
    set routing-instances vpls protocols vpls mtu 1508
    set routing-instances vpls protocols vpls neighbor 2.2.2.2
    set routing-instances vpls instance-type vpls
    set routing-instances vpls vlan-id 100
    set routing-instances vpls routing-interface irb.100
    set routing-instances vpls interface ge-0/0/0.3904
    set routing-options router-id 1.1.1.1

    the show vpls connections command returns the VPLS error as being OL (no outgoing label)

    Would there be any way to use the labels generated in the routing-instance VS-IDC in the VPLS?

    ------------------------------
    Guilherme Noll
    ------------------------------


  • 2.  RE: Problem to use labels of other routing-instance in VPLS connection

    Posted 09-28-2022 19:07
    Where is the vpls neighbor on the network?
    The configuration above would only work with two directly connected devices if there is anything between the two vpls neighbors you will also need to configure an LSP and expand to targeted LDP signaling.

    ------------------------------
    Steve Puluka BSEET - Juniper Ambassador
    IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP - Retired)
    http://puluka.com/home
    ------------------------------



  • 3.  RE: Problem to use labels of other routing-instance in VPLS connection

    Posted 09-29-2022 11:48

    Sorry, I forgot this detail.

    Here is my routing table. I get the neighbor by OSPF

    show route

    inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    186.237.112.16/28 *[Direct/0] 15:08:37
    > via irb.100
    186.237.112.30/32 *[Local/0] 15:08:37
    Local via irb.100

    VS-IDC.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    1.1.1.1/32 *[Direct/0] 15:10:28
    > via lo0.0
    172.17.1.0/24 *[Direct/0] 15:08:37
    > via ge-0/0/0.4050
    172.17.1.106/32 *[Local/0] 15:08:37
    Local via ge-0/0/0.4050
    224.0.0.2/32 *[LDP/9] 15:10:28, metric 1
    MultiRecv
    224.0.0.5/32 *[OSPF/10] 15:10:36, metric 1
    MultiRecv

    VS-IDC.mpls.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    0 *[MPLS/0] 15:10:36, metric 1
    to table VS-IDC.inet.0
    0(S=0) *[MPLS/0] 15:10:36, metric 1
    to table VS-IDC.mpls.0
    1 *[MPLS/0] 15:10:36, metric 1
    Receive
    2 *[MPLS/0] 15:10:36, metric 1
    to table VS-IDC.inet6.0
    2(S=0) *[MPLS/0] 15:10:36, metric 1
    to table VS-IDC.mpls.0
    13 *[MPLS/0] 15:10:36, metric 1
    Receive

    inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    ff02::2/128 *[INET6/0] 15:10:36
    MultiRecv

    VS-IDC.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    ff02::2/128 *[INET6/0] 15:10:36
    MultiRecv

    l2circuit.0: 1 destinations, 1 routes (0 active, 0 holddown, 1 hidden)



    ------------------------------
    Guilherme Noll
    ------------------------------