Project

General

Profile

Actions

Bug #2708

closed

CARP status missing the word "Backup"

Added by ahshang ang about 12 years ago. Updated about 12 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
12/02/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0.1
Affected Architecture:

Description

Version: 2.0.1-RELEASE (amd64)

Bug trigger condition:
1)Assign IP 192.168.105.1 to OPT2 interface in master pfsense box and assign IP 192.168.105.2 to OPT2 interface in backup pfsense box.
2)Create a CARP VIP 192.168.105.3 for OPT2 interface.
3)Create an IP alias 192.168.115.1 for OPT2 interface in master pfsense box and create an IP alias 192.168.115.2 for OPT2 interface in backup pfsense box.
4)Create a CARP VIP 192.168.115.3 for OPT2 interface.

Problem: If you check the CARP status in backup pfsense box, the word "Backup" will be missing for CARP VIP interface 192.168.105.3 on CARP status page. Screenshot attached.


Files

carp-missing-backup-word.JPG (24.5 KB) carp-missing-backup-word.JPG ahshang ang, 12/02/2012 08:39 PM
Actions #1

Updated by ahshang ang about 12 years ago

The IP addresses mentioned is just an example thus it is different than the IP addresses in attached screenshot.

Actions #2

Updated by Jim Pingle about 12 years ago

  • Status changed from New to Feedback

Please also provide the output of "ifconfig -a" off both hosts.

Actions #3

Updated by ahshang ang about 12 years ago

master pfsense:

em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 150 0
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:ac:b5:b8
inet6 fe80::20c:29ff:feac:b5b8%em0 prefixlen 64 scopeid 0x1
inet 60.54.136.62 netmask 0xfffffffc broadcast 60.54.136.63
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 150 0
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:ac:b5:c2
inet6 fe80::20c:29ff:feac:b5c2%em1 prefixlen 64 scopeid 0x2
inet 192.168.105.13 netmask 0xffffff00 broadcast 192.168.105.255
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em2: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 150 0
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:ac:b5:cc
inet6 fe80::20c:29ff:feac:b5cc%em2 prefixlen 64 scopeid 0x3
inet 192.168.215.4 netmask 0xffffff00 broadcast 192.168.215.255
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em3: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 150 0
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:ac:b5:d6
inet6 fe80::20c:29ff:feac:b5d6%em3 prefixlen 64 scopeid 0x4
inet 58.26.115.4 netmask 0xffffff00 broadcast 58.26.115.255
inet 192.168.155.4 netmask 0xffffff00 broadcast 192.168.155.255
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em4: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:ac:b5:e0
inet 192.168.254.1 netmask 0xffffff00 broadcast 192.168.254.255
inet6 fe80::20c:29ff:feac:b5e0%em4 prefixlen 64 scopeid 0x5
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> metric 0 mtu 1500
pflog0: flags=100<PROMISC> metric 0 mtu 33664
pfsync0: flags=41<UP,RUNNING> metric 0 mtu 1460
pfsync: syncdev: em4 syncpeer: 192.168.254.2 maxupd: 128 syncok: 1
enc0: flags=0<> metric 0 mtu 1536
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0xa
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
ovpnc2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1500
options=80000<LINKSTATE>
inet6 fe80::20c:29ff:feac:b5b8%ovpnc2 prefixlen 64 scopeid 0xe
inet 192.168.88.51 --> 192.168.88.52 netmask 0xffffffff
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
Opened by PID 40636
vip3: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 192.168.105.3 netmask 0xffffff00
carp: MASTER vhid 3 advbase 1 advskew 0
vip2: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 192.168.215.3 netmask 0xffffff00
carp: MASTER vhid 2 advbase 1 advskew 0
vip5: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 192.168.155.3 netmask 0xffffff00
carp: MASTER vhid 5 advbase 1 advskew 0
vip4: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 58.26.115.3 netmask 0xffffff00
carp: MASTER vhid 4 advbase 1 advskew 0

backup pfsense:

em0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:95:19:e3
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 150 0
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:95:19:ed
inet 192.168.105.14 netmask 0xffffff00 broadcast 192.168.105.255
inet6 fe80::20c:29ff:fe95:19ed%em1 prefixlen 64 scopeid 0x2
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em2: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 150 0
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:95:19:f7
inet 192.168.215.5 netmask 0xffffff00 broadcast 192.168.215.255
inet6 fe80::20c:29ff:fe95:19f7%em2 prefixlen 64 scopeid 0x3
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em3: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 150 0
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:95:19:01
inet 192.168.155.9 netmask 0xffffff00 broadcast 192.168.155.255
inet6 fe80::20c:29ff:fe95:1901%em3 prefixlen 64 scopeid 0x4
inet 192.168.155.5 netmask 0xffffff00 broadcast 192.168.155.255
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em4: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:95:19:0b
inet 192.168.254.2 netmask 0xffffff00 broadcast 192.168.254.255
inet6 fe80::20c:29ff:fe95:190b%em4 prefixlen 64 scopeid 0x5
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> metric 0 mtu 1500
pflog0: flags=100<PROMISC> metric 0 mtu 33664
pfsync0: flags=41<UP,RUNNING> metric 0 mtu 1460
pfsync: syncdev: em4 syncpeer: 224.0.0.240 maxupd: 128 syncok: 1
enc0: flags=0<> metric 0 mtu 1536
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0xa
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
vip2: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 192.168.215.3 netmask 0xffffff00
carp: BACKUP vhid 2 advbase 1 advskew 100
vip3: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 192.168.105.3 netmask 0xffffff00
carp: BACKUP vhid 3 advbase 1 advskew 100
vip5: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 192.168.155.3 netmask 0xffffff00
carp: BACKUP vhid 5 advbase 1 advskew 100
ovpnc2: flags=8010<POINTOPOINT,MULTICAST> metric 0 mtu 1500
options=80000<LINKSTATE>

Actions #4

Updated by Jim Pingle about 12 years ago

  • Status changed from Feedback to Rejected

You have a configuration error. There is no 58.26.115.x IP on the backup unit, so it can't add a CARP VIP for that subnet. Because vip4 is present in the config but not in ifconfig, the status is blank.

While that could be more informative in the GUI, it's not a bug, it's the result of a configuration error.

Actions #5

Updated by ahshang ang about 12 years ago

Jim, thanks for pointing out the misconfiguration. I agree that GUI should be more informative on the misconfiguration.

Actions

Also available in: Atom PDF