cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
445
Views
0
Helpful
1
Replies

router isis border node with lan automation - fabric in a box

p11l
Level 1
Level 1

Hi community,

Picture from our setup is attached to this post.

I've tested our setup in case of a failure. Put port-chan 7 to Router-2 in offline mode.
I encounter that routing goes through port-Ch1 between BN-1 and BN-2.

Now my problem i've that isis does something I dont understand.

BN-1 and BN-2 are manualy configured and have this isis config:
router isis
net 49.0000.xxxx.xxxx.xxxx.00 -->xxx are different on every system
metric-style wide

redistribute connected

 

Failure case workes fine.

Now I does LAN automation - worked well.
I tested again failure case.
Now the routing does'nt go from BN-2 to BN1 over port-ch 1 else from BN-2 to LAN automated device.
isis neighbors shows "down" state over port-ch 1

 

 

 

 

Output From BN-1:
System Id       Type Interface     IP Address      State Holdtime Circuit Id
Router-2	    L1   Vl70        172.16.130.252  	UP    24       Router-1.02
Router-2	    L2   Vl70        172.16.130.252  	UP    24       Router-1.02
BN-2		    L1   Po1         172.16.131.5       DOWN  29       BN-2.01
BN-2		    L2   Po1         172.16.131.5    	DOWN  26       BN-2.01
BN-2		    L1   Vl70        172.16.130.2    	DOWN  25       BN-2.02
BN-2		    L2   Vl70        172.16.130.2    	DOWN  21       BN-2.02
LAN-Autom.Dev-1 L2   Te1/1/3     172.16.133.1       UP    25       47
Router-1	    L1   Vl70        172.16.130.253     UP    9        Router-1.02
Router-1 	    L2   Vl70        172.16.130.253     UP    7        Router-1.02
Output From BN-2:
System Id       Type Interface     IP Address      State Holdtime Circuit Id
Router-2 		L1   Vl70        172.16.130.252  UP    26       Router-1.02
Router-2 		L2   Vl70        172.16.130.252  UP    26       Router-1.02
BN-1 			L1 	 Po1         172.16.131.4    DOWN  26       BN-1.01
BN-1 			L2 	 Po1         172.16.131.4    DOWN  24       BN-2.01
BN-1 			L1   Vl70        172.16.130.1    DOWN  26       Router-1.02
BN-1 			L2   Vl70        172.16.130.1    DOWN  22       Router-1.02
LAN-Autom.Dev-1 L2   Te1/1/3     172.16.133.4    UP    23       48
Router-1   		L1   Vl70        172.16.130.253  UP    8        Router-1.02
Router-1   		L2   Vl70        172.16.130.253  UP    8        Router-1.02

 

 

 

 

 


I've checked both BN configurations and see that router isis config have more lines after LAN Automation Workflow.
+ log-adjacency-changes
+ nsf ietf
+ bfd all-interfaces

I tryed a litte bit and remove the line "bfd all-interfaces" from ech BN and now my isis between BN-1 and BN-2 worked again.

 

 

 

 

Output from BN-1
System Id       Type Interface     IP Address      State Holdtime Circuit Id
Router-2	    L1   Vl70        172.16.130.252  	UP    23       Router-1.02
Router-2	    L2   Vl70        172.16.130.252  	UP    23       Router-1.02
BN-2		    L1   Po1         172.16.131.5       UP    8        BN-2.01
BN-2		    L2   Po1         172.16.131.5    	UP    8        BN-2.01
BN-2		    L1   Vl70        172.16.130.2    	UP    25       Router-1.02
BN-2		    L2   Vl70        172.16.130.2    	UP    21       Router-1.02
LAN-Autom.Dev-1 L2   Te1/1/3     172.16.133.1       UP    26       47
Router-1	    L1   Vl70        172.16.130.253     UP    9        Router-1.02
Router-1 	    L2   Vl70        172.16.130.253     UP    9        Router-1.02

 

 

 

 

So now my questions:
What does "bfd all-interfaces" and is there any need to leave it in the system wide configuration?
bfd = bidirectional forwarding detection
I saw in a document that i can disable bfd in interface configuration and leave it system wide for lan automated devices so it may be worked on port-ch 1 on BN-1 and BN-2.

Thanks a lot for your answers and i hope my problem is clear to understand.

 

Edit

I did a "debug isis bfd port-channel 1" on every BN.

Maybe this will help to find the error?

Output debug BN-1:
Oct 15 13:19:01.117: ISIS-BFD: RCV ADJ deleted notification.
Oct 15 13:19:01.117: ISIS-BFD: Delete all associated BFD sessions.
Oct 15 13:19:01.117: ISIS-BFD: free bfd session
Oct 15 13:19:01.117: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  handle:2 neigh proc:ISIS, idb:Port-channel1 handle:2 active
Oct 15 13:19:01.117: ISIS-BFD: global bfd session deleted
Oct 15 13:19:01.117: ISIS-BFD: BFD session{Port-channel1, 172.16.131.5} deleted due to Adjacency delete
Oct 15 13:19:02.113: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to down
Oct 15 13:19:03.107: %LINK-5-CHANGED: Interface TenGigabitEthernet1/1/1, changed state to administratively down
Oct 15 13:19:03.112: %LINK-5-CHANGED: Interface TenGigabitEthernet1/1/2, changed state to administratively down
Oct 15 13:19:03.112: %LINK-5-CHANGED: Interface Port-channel1, changed state to administratively down
Oct 15 13:19:04.108: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/1/1, changed state to down
Oct 15 13:19:04.112: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/1/2, changed state to down
Oct 15 13:19:07.132: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up
Oct 15 13:19:07.133: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/1/1, changed state to up
Oct 15 13:19:07.134: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/1/2, changed state to up
Oct 15 13:19:08.132: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to up
Oct 15 13:19:08.133: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/1/1, changed state to up
Oct 15 13:19:08.234: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/1/2, changed state to up
Oct 15 13:19:10.122: ISIS-BFD: Failed to get AF ipv4 address from adjacency.
Oct 15 13:19:10.122: ISIS-BFD: Create BFD session(Port-channel1, 172.16.131.5), adj intf Port-channel1
Oct 15 13:19:10.122: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 172.16.131.5 proc:ISIS, idb:Port-channel1 handle:2 act
Oct 15 13:19:10.122: ISIS-BFD: BFD session{Port-channel1, 172.16.131.5} successfully added
Oct 15 13:19:10.122: ISIS-BFD: Neighbor bfd IP Enabled
Oct 15 13:19:10.122: ISIS-BFD: RCV NBR ADJ BFD change: afi:ipv4 nbr_bfd_enabled:1
Oct 15 13:19:10.122: ISIS-BFD: isis bfd tlv changed, levelindex 0
Oct 15 13:19:10.122: ISIS-BFD: isis proc bfd change, level 1, intf Po1
Oct 15 13:19:10.122: ISIS-BFD: mtid 0 topo usable 0, level 1
Oct 15 13:19:10.122: ISIS-BFD: HDL BFD CHG: nbr_usable_changed:1, event:1,old_adj_state:INIT, new_adj_state:DOWN
Oct 15 13:19:10.128: ISIS-BFD: isis bfd tlv changed, levelindex 1
Oct 15 13:19:10.128: ISIS-BFD: isis proc bfd change, level 2, intf Po1
Oct 15 13:19:10.128: ISIS-BFD: mtid 0 topo usable 0, level 2
Oct 15 13:19:10.128: ISIS-BFD: HDL BFD CHG: nbr_usable_changed:1, event:1,old_adj_state:DOWN, new_adj_state:DOWN
Output debug BN-2:
Oct 15 13:19:03.148: ISIS-BFD: RCV ADJ deleted notification.
Oct 15 13:19:03.148: ISIS-BFD: Delete all associated BFD sessions.
Oct 15 13:19:03.148: ISIS-BFD: free bfd session
Oct 15 13:19:03.148: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  handle:2 neigh proc:ISIS, idb:Port-channel1 handle:2 active
Oct 15 13:19:03.148: ISIS-BFD: global bfd session deleted
Oct 15 13:19:03.148: ISIS-BFD: BFD session{Port-channel1, 172.16.131.4} deleted due to Adjacency delete
Oct 15 13:19:03.148: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/1/2, changed state to down
Oct 15 13:19:07.277: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/1/1, changed state to up
Oct 15 13:19:07.284: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/1/2, changed state to up
Oct 15 13:19:08.276: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/1/1, changed state to up
Oct 15 13:19:08.284: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/1/2, changed state to up
Oct 15 13:19:09.120: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up
Oct 15 13:19:10.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to up
Oct 15 13:19:10.126: ISIS-BFD: Failed to get AF ipv4 address from adjacency.
Oct 15 13:19:10.126: ISIS-BFD: Create BFD session(Port-channel1, 172.16.131.4), adj intf Port-channel1
Oct 15 13:19:10.126: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 172.16.131.4 proc:ISIS, idb:Port-channel1 handle:2 act
Oct 15 13:19:10.126: ISIS-BFD: BFD session{Port-channel1, 172.16.131.4} successfully added
Oct 15 13:19:10.126: ISIS-BFD: Neighbor bfd IP Enabled
Oct 15 13:19:10.126: ISIS-BFD: RCV NBR ADJ BFD change: afi:ipv4 nbr_bfd_enabled:1
Oct 15 13:19:10.126: ISIS-BFD: isis bfd tlv changed, levelindex 0
Oct 15 13:19:10.126: ISIS-BFD: isis proc bfd change, level 1, intf Po1
Oct 15 13:19:10.126: ISIS-BFD: mtid 0 topo usable 0, level 1
Oct 15 13:19:10.126: ISIS-BFD: HDL BFD CHG: nbr_usable_changed:1, event:1,old_adj_state:INIT, new_adj_state:DOWN
Oct 15 13:19:10.128: ISIS-BFD: isis bfd tlv changed, levelindex 1
Oct 15 13:19:10.128: ISIS-BFD: isis proc bfd change, level 2, intf Po1
Oct 15 13:19:10.128: ISIS-BFD: mtid 0 topo usable 0, level 2
Oct 15 13:19:10.128: ISIS-BFD: HDL BFD CHG: nbr_usable_changed:1, event:1,old_adj_state:DOWN, new_adj_state:DOWN
1 Reply 1

p11l
Level 1
Level 1

Hello Together,

I've solved the problem.

Because lan automation wirte command "bfd all-interfaces" to router isis configuration I need to write timer interval like seen on lan automated interfaces to my port- channel.

Command are: bfd interval 250 min_rx 250 multiplier 3