- CheckMates
- :
- Products
- :
- General Topics
- :
- How to determine a cause of the VS being in the IN...
- 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
How to determine a cause of the VS being in the INIT state?
Virtual Devices Status on each Cluster Member
=============================================
ID | Weight | VSX-01 | VSX-02
| | |
| | | [local]
-------+-------+-----------+-----------
2 | 10 | STANDBY | ACTIVE
3 | 10 | ACTIVE | INIT
6 | 20 | ACTIVE | STANDBY
---------------+-----------+-----------
TAC says use “fw ctl setsync off; fw ctl setsync on” and “cpstop;cpstart” if bouncing Sync doesn’t help
Can anyone suggest a method to determine a reason for this VS being stuck in “INIT” state?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What does vsx stat -v say? SIC ok on the VS? Policy installed on? cphaprob?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'll find out and let you know.
But the point is that even if the current state of the VS is not optimal, it was normal some time ago, permitting re-balancing of the VS', policy installations, etc...
I do want to fix the current state of affairs, but am interested to know the root cause of us getting there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Vladimir, how was the INIT issue solved?
Thanks!