BGP Configuration lost after NetScaler HA failover

book

Article ID: CTX217704

calendar_today

Updated On:

Description

The below Tabular column details about the Configuration difference Before and After the Failover event.

Normal Configuration.After failover configuration.
KKA-HZS-L1#show run
!
log syslog
log record-priority
!
ns route-install propagate
!
ns route-install default
!
ns route-install bgp
!
interface lo0
ip address 127.0.0.1/8
ipv6 address fe80::1/64
ipv6 address ::1/128
!
interface vlan0
ipv6 address fe80::ec4:7aff:fe44:5f9/64
!
interface vlan141
ip address 10.x.96.29/29
!
interface vlan162
ip address 10.x.192.137/25
!
router bgp 65468
bgp log-neighbor-changes
redistribute kernel
redistribute ospf
redistribute isis
redistribute trill
neighbor NIS_D peer-group
neighbor NIS_D remote-as 65468
neighbor NIS_D soft-reconfiguration inbound
neighbor 10.x.96.25 peer-group NIS_D
neighbor 10.x.96.26 peer-group NIS_D
!
end		KKA-HZS-L1#show running-config 
!
log syslog
log record-priority
!
ns route-install propagate
!
ns route-install default
!
ns route-install bgp
!
interface lo0
ip address 127.0.0.1/8
ipv6 address fe80::1/64
ipv6 address ::1/128
!
interface vlan0
ipv6 address fe80::ec4:7aff:fe44:5f9/64
!
interface vlan141
ip address 10.x.96.29/29
!
interface vlan162
ip address 10.x.192.137/25
!
router bgp 65468
bgp log-neighbor-changes
redistribute kernel
redistribute ospf
redistribute isis
!
end


 

Resolution

Since we support the “trill” protocol can we request the customer to delete the “redistribute trill” entry in the ZebOS.conf file and then disable and enable the BGP routing feature.
> disable ns feature bgprouting
>Done
> enable ns feature bgprouting
>Done

Problem Cause

This issue is happening when the “Zebos.conf” file has the “redistribute trill” entry. We miss all the bgp entries followed by “redistribute trill” entry.
 

Additional Information

Test Case Summary:
Case 1:
When the Zebos.conf has the trill protocol entry|
root@ns# vi ZebOS.conf
!
log syslog
log record-priority
!
interface lo0
ip address 127.0.0.1/8
ipv6 address fe80::1/64
ipv6 address ::1/128
!
interface vlan0
ip address 10.x.40.43/24
ipv6 address fe80::78bd:73ff:fe63:3f91/64
!
interface vlan20
ip address 10.x.96.29/29
!
router bgp 65468
bgp log-neighbor-changes
redistribute kernel
redistribute ospf
redistribute isis
redistribute trill >>>  config  has the trill protocol
neighbor NIS_D peer-group
neighbor NIS_D remote-as 65468
neighbor NIS_D soft-reconfiguration inbound
neighbor 10.x.96.25 peer-group NIS_D
neighbor 10.x.96.26 peer-group NIS_D
!
end

Before restarting the bgprouting feature we don’t have any bgp routing entry
> vtysh
ns#show running-config
!
log syslog
log record-priority
!
interface lo0
ip address 127.0.0.1/8
ipv6 address fe80::1/64
ipv6 address ::1/128
!
interface vlan0
ip address 10.x.40.48/24
ipv6 address fe80::e0ef:cfff:fee1:f365/64
!
interface vlan20
ip address 10.x.96.29/29
!
end

Re-enabling the bgprouting feature which triggers the bgpd process to read the entry from the “Zebos.conf” file.
 > disable ns feature bgpRouting
Done
> 
> enable ns feature bgpRouting
Done
> 
Soon after re-enabling the bgp feature which reads the config from the Zebos.conf , since we don’t support trill protocol we can see whatever config existed after the “redistribute trill” is missing.
> vtysh
ns#show running-config
!
log syslog
log record-priority
!
interface lo0
ip address 127.0.0.1/8
ipv6 address fe80::1/64
ipv6 address ::1/128
!
interface vlan0
ip address 10.x.40.48/24
ipv6 address fe80::e0ef:cfff:fee1:f365/64
!
interface vlan20
ip address 10.x.96.29/29
!
router bgp 65468
bgp log-neighbor-changes
redistribute kernel
redistribute ospf
redistribute isis
!end
 
------Case 2----------
When the Zebos.conf doesn’t have the trill protocol entry|
root@ns# vi ZebOS.conf
!
log syslog
log record-priority
!
interface lo0
ip address 127.0.0.1/8
ipv6 address fe80::1/64
ipv6 address ::1/128
!
interface vlan0
ip address 10.x.40.43/24
ipv6 address fe80::78bd:73ff:fe63:3f91/64
!
interface vlan20
ip address 10.x.96.29/29
!
router bgp 65468
bgp log-neighbor-changes
redistribute kernel
redistribute ospf
redistribute isis
neighbor NIS_D peer-group
neighbor NIS_D remote-as 65468
neighbor NIS_D soft-reconfiguration inbound
neighbor 10.x.96.25 peer-group NIS_D
neighbor 10.x.96.26 peer-group NIS_D
!
End
 
> disable ns feature bgprouting
Done
> 
> enable ns feature bgprouting
Done
> 
 
We are now able to see the all the entries|
> vtysh
ns#
ns#show running-config
!
log syslog
log record-priority
!
interface lo0
ip address 127.0.0.1/8
ipv6 address fe80::1/64
ipv6 address ::1/128
!
interface vlan0
ip address 10.x.40.48/24
ipv6 address fe80::e0ef:cfff:fee1:f365/64
!
interface vlan20
ip address 10.x.96.29/29
!
router bgp 65468
bgp log-neighbor-changes
redistribute kernel
redistribute ospf
redistribute isis
neighbor NIS_D peer-group
neighbor NIS_D remote-as 65468
neighbor NIS_D soft-reconfiguration inbound
neighbor 10.x.96.25 peer-group NIS_D
neighbor 10.x.96.26 peer-group NIS_D
!
end
ns#
 
Powered by Wolken Software