I just successfully completed my first Hotfix upgrade on our production cluster. Although traffic is flowing and things appear to be normal, I have a question regarding the cphaprob state command.
According to my topology, 192.168.
32.44 and .45 are the sync interfaces. 192.168.
16.44 and .45 are actually one of the DMZ interfaces.
I have 'funny' results depending on if I use multicast or broadcast.
fw-ep1:
Quote:
[Expert@fw-ep1]# cphaconf set_ccp broadcast
[Expert@fw-ep1]# cphaprob state
Cluster Mode: New High Availability (Primary Up)
Number Unique Address Assigned Load State
1 (local) 192.168.32.44 100% active
2 192.168.16.45 0% standby |
fw-ep2:
Quote:
[Expert@fw-ep2]# cphaconf set_ccp broadcast
[Expert@fw-ep2]# cphaprob state
Cluster Mode: New High Availability (Primary Up)
Number Unique Address Assigned Load State
1 192.168.16.44 100% active
2 (local) 192.168.32.45 0% standby |
Also, if I set cphaconf set_ccp multicast, then i get different results:
fw-ep1:
Quote:
[Expert@fw-ep1]# cphaconf set_ccp multicast
[Expert@fw-ep1]# cphaprob state
Cluster Mode: New High Availability (Primary Up)
Number Unique Address Assigned Load State
1 (local) 192.168.16.44 0% down
2 192.168.16.45 100% active attention |
fw-ep2:
Quote:
[Expert@fw-ep2]# cphaconf set_ccp multicast
[Expert@fw-ep2]# cphaprob state
Cluster Mode: New High Availability (Primary Up)
Number Unique Address Assigned Load State
1 192.168.16.44 0% down
2 (local) 192.168.16.45 100% active attention |
Can anyone shed some light on what could be causing this?