# 2
Running ifconfig -a on both services
balrog#ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
lo0:1: flags=1008849<UP,LOOPBACK,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 8232 index 1inet 172.16.193.1 netmask ffffffff
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 147.132.179.30 netmask ffffff80 broadcast 147.132.179.127
ether 0:3:ba:c1:d:d9
bge0:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 147.132.179.27 netmask ffffff80 broadcast 147.132.179.127
bge1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 147.132.114.150 netmask ffffff80 broadcast 147.132.114.255
ether 0:3:ba:c1:d:d9
bge1:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 147.132.114.147 netmask ffffff80 broadcast 147.132.114.255
bge3: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 4inet 172.16.0.129 netmask ffffff80 broadcast 172.16.0.255
ether 0:3:ba:c1:d:d9
bge3:2: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 4
inet 172.16.194.6 netmask fffffffc broadcast 172.16.194.7
bge2: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 5inet 172.16.1.1 netmask ffffff80 broadcast 172.16.1.127
ether 0:3:ba:c1:d:d9
alice#ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
lo0:1: flags=1008849<UP,LOOPBACK,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 8232 index 1inet 172.16.193.2 netmask ffffffff
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 147.132.179.42 netmask ffffff80 broadcast 147.132.179.127
ether 0:3:ba:c0:59:4d
bge0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 147.132.179.13 netmask ffff0000 broadcast 147.132.255.255
bge1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 147.132.114.162 netmask ffffff80 broadcast 147.132.114.255
ether 0:3:ba:c0:59:4d
bge1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 147.132.114.196 netmask ffff0000 broadcast 147.132.255.255
bge3: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 4inet 172.16.0.130 netmask ffffff80 broadcast 172.16.0.255
ether 0:3:ba:c0:59:4d
bge3:1: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 4
inet 172.16.194.5 netmask fffffffc broadcast 172.16.194.7
bge2: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 5inet 172.16.1.2 netmask ffffff80 broadcast 172.16.1.127
ether 0:3:ba:c0:59:4d
With /etc/netmasks, both are same as below:
root # cat /etc/netmasks
#
# The netmasks file associates Internet Protocol (IP) address
# masks with IP network numbers.
#
#network-number netmask
#
# The term network-number refers to a number obtained from the Internet Network
# Information Center. Currently this number is restricted to being a class
# A, B, or C network number. In the future we should be able to support
# arbitrary network numbers per the Classless Internet Domain Routing
# guidelines.
#
# Both the network-number and the netmasks are specified in
# "decimal dot" notation, e.g:
#
#128.32.0.0 255.255.255.0
#
147.132.0.0255.255.255.128
I think both servers have the unique netmask for 147.132.0.0 networks.
However, when cluster servers created logical interfaces such as bge1:2 , bge0:2, it always considers it as a class B network -255.255.0.0.
BTW, for balrog, I have to update it using ifconfig so it looks fine. In fact, whenever we swap nodes, we are always having this problem.
Jeff