[Question} - How to add multiple loopback IP in one logical router

kronicklezkronicklez Member Posts: 40 ■■□□□□□□□□
in Juniper
Hi all,



Can someone guide me how to add multiple loopback IP in one logical router in Olive. FYI i already try but failed. Refering to this URL Bring MPLS Network at Your Home Lab :: Juniper ...this person can add multiple loopback IP in one logical router. I'm use OLIVE - QEMU 10R. Thanks..
· Share on FacebookShare on Twitter

Comments

  • ccie15672ccie15672 Member Posts: 92 ■■■□□□□□□□
    You can apply as many IPs as you want to the same logical loopback interface..
    Derick Winkworth
    CCIE #15672 (R&S, SP), JNCIE-M #721
    Chasing: CCIE Sec, CCSA (Checkpoint)
    · Share on FacebookShare on Twitter
  • AldurAldur Member Posts: 1,460
    There's a few rules you'll want to keep in mind here. First, as previously noted, you can add as many IP addresses to the loopback interface as you want but only if this is under the same logical unit. Second you can only have 1 logical unit per loopback interface per routing instance. The later is what you saw in the link that you provided.

    Below is a section of the config from the link that was provided. Notice that there are 2 unit's defined under the loopback interface and that unit 16 is placed inside the vpn1 routing instance. This leaves only unit 25 under the main routing instance inside the logical router.
                lo0 {
                unit 16 {
                    family inet {
                        address 192.168.1.100/32;
                    }
                }
                unit 25 {
                    family inet {
                        address 202.162.208.1/32;
                    }
                }
            }
        }
.....
        routing-instances {
            vpn1 {
                instance-type vrf;
                interface fxp0.10;
                interface lo0.16;  <-----------------------------
                route-distinguisher 2500:100;
                vrf-import vpn1-import;
                vrf-export vpn1-export;
                vrf-target target:2500:100;
                vrf-table-label;
                protocols {
                    bgp {
                        group to_ce3 {
                            type external;
                            peer-as 65000;
                            as-override;
                            neighbor 192.168.1.1;
                        }
                    }
                }
            }
        }
    HTH
    "Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."

    -Bender
    · Share on FacebookShare on Twitter
  • kronicklezkronicklez Member Posts: 40 ■■□□□□□□□□
    Aldur wrote: »
    There's a few rules you'll want to keep in mind here. First, as previously noted, you can add as many IP addresses to the loopback interface as you want but only if this is under the same logical unit. Second you can only have 1 logical unit per loopback interface per routing instance. The later is what you saw in the link that you provided.

    Below is a section of the config from the link that was provided. Notice that there are 2 unit's defined under the loopback interface and that unit 16 is placed inside the vpn1 routing instance. This leaves only unit 25 under the main routing instance inside the logical router.
                lo0 {
                unit 16 {
                    family inet {
                        address 192.168.1.100/32;
                    }
                }
                unit 25 {
                    family inet {
                        address 202.162.208.1/32;
                    }
                }
            }
        }
.....
        routing-instances {
            vpn1 {
                instance-type vrf;
                interface fxp0.10;
                interface lo0.16;  <-----------------------------
                route-distinguisher 2500:100;
                vrf-import vpn1-import;
                vrf-export vpn1-export;
                vrf-target target:2500:100;
                vrf-table-label;
                protocols {
                    bgp {
                        group to_ce3 {
                            type external;
                            peer-as 65000;
                            as-override;
                            neighbor 192.168.1.1;
                        }
                    }
                }
            }
        }
    HTH


    Hi Aldur,


    Thanks for give a feedback. At last have someone give some feedback and explanation to me. Just one question Aldur. Do you test that config in olive or real equipment? Thanks again. Below is the error that i get after i commit.

    [edit logical-systems London-PE]
    root@Main-Router# commit
    [edit logical-systems London-PE interfaces lo0]
    'unit 400'
    if_instance: Multiple loopback interfaces not permitted in master routing instance
    error: configuration check-out failed

    [edit logical-systems London-PE]
    root@Main-Router#
    · Share on FacebookShare on Twitter
  • kronicklezkronicklez Member Posts: 40 ■■□□□□□□□□
    Hi all,



    Just to inform that my problem solved. Thanks for response.
    · Share on FacebookShare on Twitter
  • kronicklezkronicklez Member Posts: 40 ■■□□□□□□□□
    Hi Aldur,



    Need your expertise reagrding my config below. I cant ping between CE1 to CE2 even my config same with the URL that i mention before. Thanks.



    root@Main-Router# run show route logical-system PE1

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

    10.1.1.0/30 *[Direct/0] 03:30:26
    > via fxp1.10
    10.1.1.1/32 *[Local/0] 03:30:26
    Local via fxp1.10
    10.1.2.0/30 *[OSPF/10] 03:05:21, metric 2
    > to 10.1.1.2 via fxp1.10
    10.1.3.0/30 *[OSPF/10] 03:01:27, metric 3
    > to 10.1.1.2 via fxp1.10
    202.162.208.1/32 *[Direct/0] 03:09:19
    > via lo0.15
    202.162.208.7/32 *[OSPF/10] 02:17:25, metric 3
    > to 10.1.1.2 via fxp1.10
    202.162.208.252/32 *[OSPF/10] 03:01:27, metric 2
    > to 10.1.1.2 via fxp1.10
    202.162.208.254/32 *[OSPF/10] 03:05:21, metric 1
    > to 10.1.1.2 via fxp1.10
    224.0.0.5/32 *[OSPF/10] 03:09:19, metric 1
    MultiRecv
    ---(more)---


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

    202.162.208.7/32 *[RSVP/7/1] 02:17:12, metric 3
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2

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

    172.17.63.1/32 *[BGP/170] 02:10:04, localpref 100
    AS path: 777 I
    > to 192.168.1.2 via fxp1.100
    172.17.68.1/32 *[BGP/170] 02:04:21, localpref 100, from 202.162.208.7
    AS path: 911 I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2
    192.168.1.0/30 *[Direct/0] 03:09:19
    > via fxp1.100
    [BGP/170] 02:10:04, localpref 100
    AS path: 777 I
    > to 192.168.1.2 via fxp1.100
    192.168.1.1/32 *[Local/0] 03:09:19
    Local via fxp1.100
    ---(more 26%)---

    192.168.1.100/32 *[Direct/0] 03:09:19
    > via lo0.105
    192.168.2.0/30 *[BGP/170] 02:17:01, localpref 100, from 202.162.208.7
    AS path: I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2
    192.168.2.100/32 *[BGP/170] 02:17:01, localpref 100, from 202.162.208.7
    AS path: I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2

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

    172.17.63.0/24 *[Static/5] 00:32:35
    > to 192.168.1.2 via fxp1.110
    172.17.68.77/32 *[BGP/170] 01:03:09, localpref 100, from 202.162.208.7
    AS path: 1500 I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2
    192.168.1.0/30 *[Direct/0] 01:02:00
    > via fxp1.110
    192.168.1.1/32 *[Local/0] 01:02:00
    Local via fxp1.110
    192.168.1.77/32 *[Direct/0] 01:03:09
    > via lo0.115
    ---(more 40%)---

    192.168.2.0/30 *[BGP/170] 01:03:09, localpref 100, from 202.162.208.7
    AS path: I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2
    192.168.2.77/32 *[BGP/170] 01:03:09, localpref 100, from 202.162.208.7
    AS path: I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2

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

    0 *[MPLS/0] 03:09:19, metric 1
    Receive
    1 *[MPLS/0] 03:09:19, metric 1
    Receive
    2 *[MPLS/0] 03:09:19, metric 1
    Receive
    16 *[VPN/0] 03:09:19
    to table vpn.inet.0, Pop
    18 *[VPN/0] 01:03:09
    to table vpnv6.inet.0, Pop

    bgp.l3vpn.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both
    ---(more 53%)---


    2500:100:172.17.68.1/32
    *[BGP/170] 02:04:21, localpref 100, from 202.162.208.7
    AS path: 911 I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2
    2500:100:192.168.2.0/30
    *[BGP/170] 02:17:01, localpref 100, from 202.162.208.7
    AS path: I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2
    2500:100:192.168.2.100/32
    *[BGP/170] 02:17:01, localpref 100, from 202.162.208.7
    AS path: I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2
    2500:666:172.17.68.77/32
    *[BGP/170] 01:16:06, localpref 100, from 202.162.208.7
    AS path: 1500 I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2
    2500:666:192.168.2.0/30
    *[BGP/170] 01:16:06, localpref 100, from 202.162.208.7
    AS path: I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2
    2500:666:192.168.2.77/32
    *[BGP/170] 01:16:06, localpref 100, from 202.162.208.7
    ---(more 68%)---

    AS path: I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2

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

    ::ffff:202.162.208.7/128
    *[RSVP/7/1] 02:17:12, metric 3
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2

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

    2001:5c0:1::/126 *[Static/5] 03:09:19
    > to 2001:d30:1::3 via fxp1.100
    2001:5c0:7::/126 *[BGP/170] 02:17:01, localpref 100, from 202.162.208.7
    AS path: I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2
    2001:d30:1::/126 *[Direct/0] 03:09:19
    > via fxp1.100
    2001:d30:1::1/128 *[Local/0] 03:09:19
    Local via fxp1.100
    2001:d30:1::100/128*[Direct/0] 03:09:19
    ---(more 81%)---

    > via lo0.105
    2001:d30:7::/126 *[BGP/170] 02:17:01, localpref 100, from 202.162.208.7
    AS path: I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2
    2001:d30:7::700/128*[BGP/170] 02:17:01, localpref 100, from 202.162.208.7
    AS path: I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2
    fe80::/64 *[Direct/0] 03:09:19
    > via fxp1.100
    fe80::5254:0:6412:3457/128
    *[Local/0] 03:09:19
    Local via fxp1.100
    fe80::5254:ff:fe12:3456/128
    *[Direct/0] 03:09:19
    > via lo0.105

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

    2500:100:2001:5c0:7::/126
    *[BGP/170] 02:17:01, localpref 100, from 202.162.208.7
    AS path: I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2
    ---(more 95%)---

    2500:100:2001:d30:7::/126
    *[BGP/170] 02:17:01, localpref 100, from 202.162.208.7
    AS path: I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2
    2500:100:2001:d30:7::700/128
    *[BGP/170] 02:17:01, localpref 100, from 202.162.208.7
    AS path: I
    > to 10.1.1.2 via fxp1.10, label-switched-path toPE2

    [edit]
    root@Main-Router# exit
    · Share on FacebookShare on Twitter
Sign In or Register to comment.