Bug #15428
closed
UI appears to put incorrect CARP parameters into the low level NIC configurations
0%
Description
it appears that there is a bug with the UI and supporting code, for v2.7.2-RELEASE, in regard to the way that the UI sets up the low level CARP parameters on the NICS.
In my system, both the primary and secondary NICs are set up by the UI with advskew = 254 at the ifconfig level, regardless of what is specified via the UI
Taking my LAN setups as an example, I use the following CARP parameters on the UI:
primary: advbase=1, advskew=0, base IP=10.0.0.1/16
secondary: advbase=1, advskew=100, base IP =10.0.0.2/16
However, when I look at the NICs via ifconfig, I see that advbase is set to 254. The same happens with my WAN NICs. Here is the output of ifconfig for each of the LAN NICs:
Primary:
em1: flags=1008943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
description: LAN
options=48120b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,HWSTATS,MEXTPG>
ether 00:0b:ab:86:50:fa
inet 10.0.0.1 netmask 0xffff0000 broadcast 10.0.255.255
inet 10.0.0.3 netmask 0xffff0000 broadcast 10.0.255.255 vhid 2
inet6 fe80::20b:abff:fe86:50fa%em1 prefixlen 64 scopeid 0x2
carp: MASTER vhid 2 advbase 1 advskew 254
peer 224.0.0.18 peer6 ff02::12
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
Secondary:
em1: flags=1008943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
description: LAN
options=48120b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,HWSTATS,MEXTPG>
ether 00:0b:ab:86:52:12
inet 10.0.0.2 netmask 0xffff0000 broadcast 10.0.255.255
inet 10.0.0.3 netmask 0xffff0000 broadcast 10.0.255.255 vhid 2
inet6 fe80::20b:abff:fe86:5212%em1 prefixlen 64 scopeid 0x2
carp: BACKUP vhid 2 advbase 1 advskew 254
peer 224.0.0.18 peer6 ff02::12
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
The result is that the primary does not automatically resume master once it comes up. A manual reboot of the secondary is necessary to put the firewalls in their normal HA state. HA is therefore not working as intended.
Updated by Chris Linstruth 10 days ago
First check to see if you have you have both nodes in CARP maintenance mode. If so, take them out of that mode and check again.
Updated by Jim Pingle 10 days ago
- Status changed from New to Not a Bug
- Priority changed from Urgent to Normal
A skew of 254 indicates a problem in your setup not a problem with how the settings were applied. Either they are in maintenance mode or you have something that has triggered a demotion (e.g. VIPs on a NIC which is unplugged/no link).
This site is not for discussion and diagnosis, post on the forum for assistance.