BGP Vpnv4 rechability issue when MPLS command is deleted from interface
Hi Team,
i am facing an issue with bgp vpnv4 redundancy. i have connectivity as below. R5 is advertising vpnv4 prefix 55.55.55.55/32 throught bgp to R6 and R3. R6 and R3 advertising the same prefix to R1 without changing the nexhop. R6 and R3 advertising bgp lable to R1 for R5 loopback address (5.5.5.5) to establish the end-to-end bgp lsp. MPLS LDP is running on all the interfaces along with isis.
Routing is as below :-
<R1>dis ip routing-table vpn-instance a 55.55.55.55 verbose
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Table : a
Summary Count : 1
Destination: 55.55.55.55/32
Protocol: IBGP Process ID: 0
Preference: 255 Cost: 0
NextHop: 5.5.5.5 Neighbour: 3.3.3.3
State: Active Adv Relied Age: 00h36m44s
Tag: 0 Priority: low
Label: 1032 QoSInfo: 0x0
IndirectID: 0x9
RelayNextHop: 6.6.6.6 Interface: GigabitEthernet0/0/1
TunnelID: 0x28 Flags: RD
<R1>
R1>dis ip routing-table 5.5.5.5 verbose
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Table : Public
Summary Count : 1
Destination: 5.5.5.5/32
Protocol: IBGP Process ID: 0
Preference: 255 Cost: 0
NextHop: 6.6.6.6 Neighbour: 6.6.6.6
State: Active Adv Relied Age: 00h37m29s
Tag: 0 Priority: low
Label: 1038 QoSInfo: 0x0
IndirectID: 0x7
RelayNextHop: 16.0.0.6 Interface: GigabitEthernet0/0/1
TunnelID: 0x26 Flags: RD
<R1>
<R1>dis ip routing-table 6.6.6.6 verbose
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Table : Public
Summary Count : 1
Destination: 6.6.6.6/32
Protocol: ISIS-L2 Process ID: 1
Preference: 15 Cost: 1000
NextHop: 16.0.0.6 Neighbour: 0.0.0.0
State: Active Adv Age: 00h37m57s
Tag: 0 Priority: medium
Label: NULL QoSInfo: 0x0
IndirectID: 0x0
RelayNextHop: 0.0.0.0 Interface: GigabitEthernet0/0/1
TunnelID: 0x26 Flags: D
<R1>
<R1>dis bgp vpnv4 vpn-instance a routing-table
BGP Local router ID is 12.0.0.1
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
VPN-Instance a, Router ID 12.0.0.1:
Total Number of Routes: 3
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 11.11.11.11/32 0.0.0.0 0 0 ?
*>i 55.55.55.55/32 5.5.5.5 0 100 0 i
* i 5.5.5.5 0 100 0 i
<R1>
<R1>dis bgp routing-table
BGP Local router ID is 12.0.0.1
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 3
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 1.1.1.1/32 0.0.0.0 0 0 i
*>i 5.5.5.5/32 6.6.6.6 0 100 0 i
* i 3.3.3.3 0 100 0 i
<R1>
When i am removing the "MPLS" command from Gigabit0/0/1 interface on R1 routers , redundancy is not working.
service should shift to redundant path through gi0/0/0. but it is not working.
Please find the below logs after removing the "mpls" command on gi0/0/1 interface .
[R1]dis bgp vpnv4 all routing-table
BGP Local router ID is 12.0.0.1
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total number of routes from all PE: 3
Route Distinguisher: 100:1
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 11.11.11.11/32 0.0.0.0 0 0 ?
*>i 55.55.55.55/32 5.5.5.5 0 100 0 i
* i 5.5.5.5 0 100 0 i
VPN-Instance a, Router ID 12.0.0.1:
Total Number of Routes: 3
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 11.11.11.11/32 0.0.0.0 0 0 ?
i 55.55.55.55/32 5.5.5.5 0 100 0 i
i 5.5.5.5 0 100 0 i
[R1]
[R1]dis bgp vpnv4 all routing-table
BGP Local router ID is 12.0.0.1
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total number of routes from all PE: 3
Route Distinguisher: 100:1
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 11.11.11.11/32 0.0.0.0 0 0 ?
*>i 55.55.55.55/32 5.5.5.5 0 100 0 i
* i 5.5.5.5 0 100 0 i
VPN-Instance a, Router ID 12.0.0.1:
Total Number of Routes: 3
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 11.11.11.11/32 0.0.0.0 0 0 ?
i 55.55.55.55/32 5.5.5.5 0 100 0 i
i 5.5.5.5 0 100 0 i
[R1]
[R1]
[R1]
[R1]dis ip rou
[R1]dis ip routing-table 6.6.6.6 ver
[R1]dis ip routing-table 6.6.6.6 verbose
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Table : Public
Summary Count : 1
Destination: 6.6.6.6/32
Protocol: ISIS-L2 Process ID: 1
Preference: 15 Cost: 1000
NextHop: 16.0.0.6 Neighbour: 0.0.0.0
State: Active Adv Age: 00h00m48s
Tag: 0 Priority: medium
Label: NULL QoSInfo: 0x0
IndirectID: 0x0
RelayNextHop: 0.0.0.0 Interface: GigabitEthernet0/0/1
TunnelID: 0x0 Flags: D
[R1]dis ip rou
[R1]dis ip routing-table vpn
[R1]dis ip routing-table vpn-instance a
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Tables: a
Destinations : 1 Routes : 1
Destination/Mask Proto Pre Cost Flags NextHop Interface
11.11.11.11/32 Direct 0 0 D 127.0.0.1 LoopBack100
[R1]
[R1]
[R1]dis bgp rou
[R1]dis bgp routing-table
BGP Local router ID is 12.0.0.1
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 3
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 1.1.1.1/32 0.0.0.0 0 0 i
*>i 5.5.5.5/32 6.6.6.6 0 100 0 i
* i 3.3.3.3 0 100 0 i
[R1]
can anyone please help how can i archive the redundancy in this scenarion ?
bgp 12
peer 3.3.3.3 as-number 12
peer 3.3.3.3 connect-interface LoopBack0
peer 6.6.6.6 as-number 12
peer 6.6.6.6 connect-interface LoopBack0
#
ipv4-family unicast
undo synchronization
network 1.1.1.1 255.255.255.255
peer 3.3.3.3 enable
peer 3.3.3.3 route-policy label export
peer 3.3.3.3 label-route-capability
peer 6.6.6.6 enable
peer 6.6.6.6 route-policy label export
peer 6.6.6.6 label-route-capability check-tunnel-reachable
#
ipv4-family vpnv4
policy vpn-target
peer 3.3.3.3 enable
peer 6.6.6.6 enable
#
ipv4-family vpn-instance a
import-route direct
#
return
[R1]
bgp 12
peer 1.1.1.1 as-number 12
peer 1.1.1.1 connect-interface LoopBack0
peer 5.5.5.5 as-number 12
peer 5.5.5.5 connect-interface LoopBack0
#
ipv4-family unicast
undo synchronization
peer 1.1.1.1 enable
peer 1.1.1.1 route-policy mpls export
peer 1.1.1.1 reflect-client
peer 1.1.1.1 next-hop-local
peer 1.1.1.1 label-route-capability check-tunnel-reachable
peer 5.5.5.5 enable
peer 5.5.5.5 route-policy mpls export
peer 5.5.5.5 reflect-client
peer 5.5.5.5 next-hop-local
peer 5.5.5.5 label-route-capability check-tunnel-reachable
#
ipv4-family vpnv4
undo policy vpn-target
peer 1.1.1.1 enable
peer 1.1.1.1 reflect-client
peer 5.5.5.5 enable
peer 5.5.5.5 reflect-client
#
return
<R6>
- x
- convention：
- Emotion(0)
SK47
Created May 29, 2020 07:48:59
(0)
(0)
Thanks for replay wang is there any way through which i can archive the redundancy , for example if i remove the mpls command from gi0/0/1, bgp route for 5.5.5.5 changes from 6.6.6.6 to 3.3.3.3 ? however redundancy is working fine after shutting the interface gi0/0/1.
|
SK47
Created May 29, 2020 07:48:59
(0)
(0)
Thanks for replay wang is there any way through which i can archive the redundancy , for example if i remove the mpls command from gi0/0/1, bgp route for 5.5.5.5 changes from 6.6.6.6 to 3.3.3.3 ? however redundancy is working fine after shutting the interface gi0/0/1.
|
Comment
- Politically sensitive content
- Content concerning pornography, gambling, and drug abuse
- Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
