- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Re: Odd cphaprob output
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Odd cphaprob output
Having an unusual issue with a cluster firewall interface. Firewall was rebooted and post reboot one side of the sync interface is showing an issue where the inbound is up but the outbound is down. The other side is UP & UP.
fw1-cxl1:0]# cphaprob -a if
Required interfaces: 7
Required secured interfaces: 1
eth7 Inbound: UP Outbound: DOWN (6062.3 secs) sync(secured), multicast
eth5 UP non sync(non secured), multicast (eth5.71 )
bond2 UP non sync(non secured), multicast, bond Load Sharing (bond2.32 )
bond0 UP non sync(non secured), multicast, bond Load Sharing (bond0.17 )
bond1 UP non sync(non secured), multicast, bond Load Sharing (bond1.80 )
bond0 UP non sync(non secured), multicast, bond Load Sharing (bond0.245 )
eth5 UP non sync(non secured), multicast (eth5.246 )
Any obvious (to you!) ideas what might cause this before I roll up my sleeves?
TIA
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just to close the circle on this. My issue turned out to be a problem with mis-matching count of CoreXL instances on both nodes. Visible under cpview 'SysInfo'. Once I matched the number of instances by changing the config in cpconfig and rebooting, the previous stable status was restored.
Why it stopped using the sync interface IP addresses while the mismatch occurred is unknown.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What is the physical setup of the sync interface? Just an Ethernet cable or connected through a switch?
Exclusively at CPX 2025 Las Vegas Tuesday Feb 25th @ 1:00pm
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
igmp snooping on switch side could be a cause too.
you can verify that by setting the cluster to unicast or broadcast for testing purpose.
See sk20576.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just to close the circle on this. My issue turned out to be a problem with mis-matching count of CoreXL instances on both nodes. Visible under cpview 'SysInfo'. Once I matched the number of instances by changing the config in cpconfig and rebooting, the previous stable status was restored.
Why it stopped using the sync interface IP addresses while the mismatch occurred is unknown.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
