Loading...
Loading...
BVI Interface protocol went UP/DOWN (show ip int brief) even when there is a interface associated to the BVI, however the BVI status is UP/UP (show int BVI xx)
LAB recreation between ASR9010 and ASR 9006 did nto reproduce the problem, however any attempt between two ASR9001 always triggered the problem Two ASR9001 running IOS XR 5.3.3 connected to two ASR9000V Satellite in a dual home scenario, so each ASR9001 is connected to both ASR9000V. Besides that both ASR9001 is connected to each other running ICCP configuration between them. Each ASR9001 interface connected to ASR9000V as well as the connection between ASR9001 have the respective interfaces associated to BVI The scenario contains the following: - HSRP between these ASR9001 and they are based on BVI and the BVI is using VRF configuration - BRIDGE DOMAIN where the connection between the ASR9000, the connection to the Satellites and the routed BVI are configured The HSRP status initially was normal ACTIVE/STANDBY between two ASR9001 and we have 6 interfaces associated to BVI, I mean one for each ASR9000V (total of 2) two for each ASR9000V (total of 4) Simulating the failure: - Turning off the one of the ASR9001 the HSRP status transitioned correctly to ACTIVE in the other ASR9001 was in STANBY before. At this point the topology remained with one ASR9001 and two ASR9000V, so we have just one interface of each ASR9000V associated to BVI (total of 2) - Turning off the ASR9000V the topology remained with one ASR9001 and one ASR9000V, however the HSRP that is based on BVI has transitioning to INIT After all, BVI became UP/DOWN from show ip int brief point of view indicating that there was no interface associated to BVI which was not true since the remained ASR9000V was connected using the remained interface associated to BVI, however from the show int bvi command the BVI was UP/UP
Remove L2VPN configuration and applied the same L2VPN configuration again made the BVI interface protocol UP ! RP/0/RSP0/CPU0:ASR9K_1#conf t Fri Sep 16 12:45:47.900 UTC RP/0/RSP0/CPU0:ASR9K_1(config)#no l2vpn <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< removed l2vpn RP/0/RSP0/CPU0:ASR9K_1(config)#commit Fri Sep 16 12:45:55.642 UTC RP/0/RSP0/CPU0:ASR9K_1(config)#! <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< added the same l2vpn configuration RP/0/RSP0/CPU0:ASR9K_1(config)#l2vpn RP/0/RSP0/CPU0:ASR9K_1(config-l2vpn)# bridge group pruebas RP/0/RSP0/CPU0:ASR9K_1(config-l2vpn-bg)# bridge-domain pruebas RP/0/RSP0/CPU0:ASR9K_1(config-l2vpn-bg-bd)# interface TenGigE0/0/2/3.50 RP/0/RSP0/CPU0:ASR9K_1(config-l2vpn-bg-bd-ac)# ! RP/0/RSP0/CPU0:ASR9K_1(config-l2vpn-bg-bd-ac)# interface GigabitEthernet100/$ RP/0/RSP0/CPU0:ASR9K_1(config-l2vpn-bg-bd-ac)# ! RP/0/RSP0/CPU0:ASR9K_1(config-l2vpn-bg-bd-ac)# interface GigabitEthernet101/$ RP/0/RSP0/CPU0:ASR9K_1(config-l2vpn-bg-bd-ac)# ! RP/0/RSP0/CPU0:ASR9K_1(config-l2vpn-bg-bd-ac)# routed interface BVI50 RP/0/RSP0/CPU0:ASR9K_1(config-l2vpn-bg-bd)# ! RP/0/RSP0/CPU0:ASR9K_1(config-l2vpn-bg-bd)# ! RP/0/RSP0/CPU0:ASR9K_1(config-l2vpn-bg-bd)#! RP/0/RSP0/CPU0:ASR9K_1(config-l2vpn-bg-bd)#commit Fri Sep 16 12:46:24.967 UTC RP/0/RSP0/CPU0:ASR9K_1(config-l2vpn-bg-bd)# RP/0/RSP0/CPU0:ASR9K_1# RP/0/RSP0/CPU0:ASR9K_1#sh int bvi50 Fri Sep 16 12:46:41.081 UTC BVI50 is up, line protocol is up <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< UP Interface state transitions: 3 Hardware is Bridge-Group Virtual Interface, address is 5087.8957.124d Internet address is 10.10.10.105/27 MTU 1514 bytes, BW 10000000 Kbit (Max: 10000000 Kbit) reliability 255/255, txload 0/255, rxload 0/255 Encapsulation ARPA, loopback not set, Last link flapped 00:00:16 ARP type ARPA, ARP timeout 04:00:00 Last input 00:05:19, output 00:00:00 Last clearing of "show interface" counters never 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 82 packets input, 5002 bytes, 0 total input drops 0 drops for unrecognized upper-level protocol Received 13 broadcast packets, 66 multicast packets 20908 packets output, 1276044 bytes, 0 total output drops Output 1000 broadcast packets, 19903 multicast packets RP/0/RSP0/CPU0:ASR9K_1#sh ip int brie | i Up Fri Sep 16 12:46:48.328 UTC BVI50 10.10.10.105 Up Up TEST <<<<<<<<<<<<<<<<<<<<<<<<< UP Loopback0 201.168.5.1 Up Up default Loopback100 10.168.100.1 Up Up satelitemgmt Loopback101 10.168.101.1 Up Up satelitemgmt MgmtEth0/RSP0/CPU0/0 172.16.156.67 Up Up default GigabitEthernet101/0/0/42 unassigned Up Up default GigabitEthernet101/0/0/42.50 unassigned Up Up default TenGigE0/0/2/1 10.168.101.1 Up Up satelitemgmt RP/0/RSP0/CPU0:ASR9K_1#sh l2vpn bridge-domain bd-name pruebas Fri Sep 16 12:46:59.708 UTC Legend: pp = Partially Programmed. Bridge group: pruebas, bridge-domain: pruebas, id: 0, state: up, ShgId: 0, MSTi: 0 Aging: 300 s, MAC limit: 4000, Action: none, Notification: syslog Filter MAC addresses: 0 ACs: 4 (2 up), VFIs: 0, PWs: 0 (0 up), PBBs: 0 (0 up) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< UP / 2 ACs List of ACs: BV50, state: up, BVI MAC addresses: 2 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< UP BVI50 Gi100/0/0/42.50, state: down, Static MAC addresses: 0 Gi101/0/0/42.50, state: up, Static MAC addresses: 0 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< UP BVI50 Te0/0/2/3.50, state: down, Static MAC addresses: 0 List of Access PWs: List of VFIs: RP/0/RSP0/CPU0:ASR9K_1#ping vrf TEST 10.10.10.105 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< BVI50 become reachable from own router Fri Sep 16 12:47:10.344 UTC Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.10.10.105, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/8/35 ms RP/0/RSP0/CPU0:ASR9K_1#sh hsrp Fri Sep 16 13:00:57.280 UTC IPv4 Groups: P indicates configured to preempt. | Interface Grp Pri P State Active addr Standby addr Group addr BV50 1 100 P Active local unknown 10.10.10.97 <<<<<<<<<<<<<<<<<<<<<<<<<< become ACTIVE IPv6 Groups: P indicates configured to preempt. | Interface Grp Pri P State Active addr Standby addr Group addr RP/0/RSP0/CPU0:ASR9K_1#sh nv satellite status Fri Sep 16 13:02:56.055 UTC Satellite 100 ------------- Status: Discovery Stalled; Conflict: interface is down Type: asr9000v IPv4 address: 10.168.100.100 (VRF: satelitemgmt) Serial Number: CAT1838U33A Configured satellite fabric links: TenGigE0/0/2/0 -------------- Status: Discovery Stalled; Conflict: interface is down Remote ports: GigabitEthernet0/0/0-43 Satellite 101 ------------- Status: Connected (Stable) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Redundancy: Active (Group: 100) Type: asr9000v MAC address: 78ba.f9e8.1948 IPv4 address: 10.168.100.101 (VRF: satelitemgmt) Serial Number: CAT1918U1TA Remote version: Compatible (not latest version) ROMMON: 127.0 (Latest) FPGA: 1.13 (Latest) IOS: 378.0 (Available: 533.100) Configured satellite fabric links: TenGigE0/0/2/1 -------------- Status: Satellite Ready Remote ports: GigabitEthernet0/0/0-43
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.