[c-nsp] Incompatibility for send-label between Cisco andJuniper?
Jason Koh
kohtohshyr at pacific.net.sg
Wed Sep 27 04:40:31 EDT 2006
Hi Alex
Thanks, it works. The reason I couldn't get it to work in the first place
was because I tried to commit before putting rib inet.3 into the config
first.
----- Original Message -----
From: "Alex" <ecralar at hotmail.com>
To: "Jason Koh" <kohtohshyr at pacific.net.sg>; <cisco-nsp at puck.nether.net>
Sent: Monday, September 25, 2006 8:05 PM
Subject: Re: [c-nsp] Incompatibility for send-label between Cisco
andJuniper?
> Jason,
>
> I've got it working in the lab (long email):
> Diagram:
> AS 2,T320-ge-7/0/2(10.16.0.1/24)<---->(10.16.0.2/24)Cisco 7301-gi0/2, AS1.
>
> Juniper relevant config and printouts:
>
> [edit protocols bgp]
> user at as2# show
> group test {
> type external;
> family inet {
> unicast; <==========apparently, these 2 can
> labeled-unicast { <====be configured together
> rib {
> inet.3;
> }
> }
> }
> export test;
> peer-as 1;
> neighbor 10.16.0.2;
>
> [edit routing-options]
> user at as2# show
> rib inet.3 {
> static {
> route 10.177.177.0/24 discard;
> route 10.176.176.0/24 reject;
> }
> }
> static {
> route 2.2.2.0/26 discard;
> route 10.1.0.0/16 next-hop 10.0.2.2;
> route 10.100.0.0/16 next-hop 10.0.1.2;
> route 10.178.178.0/24 discard;
> }
> autonomous-system 2;
>
> [edit policy-options policy-statement test]
> user at as2# show
> term 1 {
> from protocol static;
> then accept;
> }
> user at as2> show bgp summary
> Groups: 1 Peers: 1 Down peers: 0
> Table Tot Paths Act Paths Suppressed History Damp State
> Pending
> inet.0 1 1 0 0 0 0
> inet.3 1 1 0 0 0 0
> Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn
> State|#Active/Received/Damped...
> 10.16.0.2 1 31 32 0 0 13:50
> Establ
> inet.0: 1/1/0
> inet.3: 1/1/0
>
> user at as2> show route table inet.3
>
> inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 10.176.176.0/24 *[Static/5] 00:42:33
> Reject
> 10.177.177.0/24 *[Static/5] 00:46:39
> Discard
> 10.186.186.0/24 *[BGP/170] 00:25:41, MED 0, localpref 100
> AS path: 1 I
> > to 10.16.0.2 via ge-7/0/2.0, Push 0
>
> user at as2> show route receive-protocol bgp 10.16.0.2 extensive
>
> inet.0: 15 destinations, 15 routes (14 active, 0 holddown, 1 hidden)
> * 10.187.187.0/24 (1 entry, 1 announced)
> Nexthop: 10.16.0.2
> MED: 0
> AS path: 1 I
>
> inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
>
> * 10.186.186.0/24 (1 entry, 1 announced)
> Route Label: 0
> Nexthop: 10.16.0.2
> MED: 0
> AS path: 1 I
>
> user at as2> show route advertising-protocol bgp 10.16.0.2
>
> inet.0: 15 destinations, 15 routes (14 active, 0 holddown, 1 hidden)
> Prefix Nexthop MED Lclpref AS path
> * 2.2.2.0/26 Self I
> * 10.178.178.0/24 Self I
>
> inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
> Prefix Nexthop MED Lclpref AS path
> * 10.176.176.0/24 Self I
> * 10.177.177.0/24 Self I
>
> Cisco config and relevant printouts:
>
> interface Loopback186
> ip address 10.186.186.1 255.255.255.0
> !
> interface Loopback187
> ip address 10.187.187.1 255.255.255.0
> !
> router bgp 1
> bgp log-neighbor-changes
> neighbor 10.16.0.1 remote-as 2
> neighbor 10.16.0.1 update-source GigabitEthernet0/2
> !
> address-family ipv4
> neighbor 10.16.0.1 activate
> neighbor 10.16.0.1 soft-reconfiguration inbound
> neighbor 10.16.0.1 route-map lb out
> neighbor 10.16.0.1 send-label
> no auto-summary
> no synchronization
> network 10.186.186.0 mask 255.255.255.0
> network 10.187.187.0 mask 255.255.255.0
> exit-address-family
> !
> ip prefix-list 186 seq 10 permit 10.186.186.0/24
> !
> route-map lb permit 10
> match ip address prefix-list 186
> set mpls-label
> !
> route-map lb permit 20
>
> internet#sh ip bgp neighbors 10.16.0.1 advertised-routes
> BGP table version is 21, local router ID is 1.1.1.1
> Status codes: s suppressed, d damped, h history, * valid, > best, i -
> internal,
> r RIB-failure, S Stale
> Origin codes: i - IGP, e - EGP, ? - incomplete
>
> Network Next Hop Metric LocPrf Weight Path
> *> 10.186.186.0/24 0.0.0.0 0 32768 i
> *> 10.187.187.0/24 0.0.0.0 0 32768 i
>
> Total number of prefixes 2
>
> internet#sh ip bgp neighbors 10.16.0.1 received-routes
> BGP table version is 21, local router ID is 1.1.1.1
> Status codes: s suppressed, d damped, h history, * valid, > best, i -
> internal,
> r RIB-failure, S Stale
> Origin codes: i - IGP, e - EGP, ? - incomplete
>
> Network Next Hop Metric LocPrf Weight Path
> *> 2.2.2.0/26 10.16.0.1 0 2 i
> *> 10.176.176.0/24 10.16.0.1 0 2 i
> *> 10.177.177.0/24 10.16.0.1 0 2 i
> *> 10.178.178.0/24 10.16.0.1 0 2 i
>
> internet#sh ip bgp 10.176.176.0
> BGP routing table entry for 10.176.176.0/24, version 19
> Paths: (1 available, best #1, table Default-IP-Routing-Table)
> Not advertised to any peer
> 2, (received & used)
> 10.16.0.1 from 10.16.0.1 (10.19.14.1)
> Origin IGP, localpref 100, valid, external, best,
> mpls labels in/out nolabel/100064
> internet#sh ip bgp 10.186.186.0
> BGP routing table entry for 10.186.186.0/24, version 20
> Paths: (1 available, best #1, table Default-IP-Routing-Table)
> Advertised to update-groups:
> 2
> Local
> 0.0.0.0 from 0.0.0.0 (1.1.1.1)
> Origin IGP, metric 0, localpref 100, weight 32768, valid, sourced,
> local, best,
> mpls labels in/out unasgnd(from LDP)/nolabel
>
> So "unicast" and "labeled-unicast" are not mutually exclusive, as the doc
> suggests (at least in JUNOS 7.4R2.6).
> Of course, if You don't want all inet.3 to be advertised then You can
> filter out unwanted prefixes outbound from Juniper by applying export
> policy.
>
> Regards
> Alex
>
>
>
More information about the cisco-nsp
mailing list