- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- cluster member down after RMA
- 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
cluster member down after RMA
Hello,
After RMA of one of the cluster nodes we are unable to restore the cluster according to the sk160533.
SIC status: Communicating
cphaprob state on on the down node shows Event Code: CLUS-110800
cphaprob -a if on the active member shows Required interfaces: 13, while on the down member: 4. Why is that and is it a reason why the cluster is not working properly?
The CCP mode is Manual (Unicast) for both nodes.
The number of Virtual cluster interfaces is the same for both.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After changing the fwha_monitor_all_vlan=0 to =1 and rebooting, the cluster returned to operation.
Topic can be closed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Which version & JHF is this system and did you verify/restore the network interface levels configurations, are they properly connected?
Please contact TAC to help expedite resolution if not already having followed the process outlined in full.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
R80.40 T294
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You need to make sure both interfaces are the same between both cluster members.
Otherwise it will have cluster down.
Take a look at this sk125152 for more detail
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just throwing this out there...did you make sure that topology matches on both members? Meaning all interfaces that are supposed to be clustered are set as cluster in topology in smart console object?
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After changing the fwha_monitor_all_vlan=0 to =1 and rebooting, the cluster returned to operation.
Topic can be closed.
