Forum Discussion
installing viprion 2400 - problem with management IP
We are installating a viprion 2400 with 2 blade (B2250) in it.
The management IP was configured (floating IP) as also a cluster member IP for each module. (see hereunder --> tmsh show sys cluster command)
When unit was rebooted , the floating management IP was however no longer accessible . Instead we now need to connect to one of the cluster member IP's . (GUI is also indicating we're logged on from secondary slot , which is normal to me) When rebooting again , other cluster member IP comes available. But floating management IP stays unavailable .
I was thinking the floating IP should remain available ? Or am i doing something wrong in the config ?
Sys::Cluster: default
Address 10.0.0.10/23 Availability available State enabled Reason Cluster Enabled Primary Slot ID 2 Primary Selection Time 09/23/14 08:53:35
| Sys::Cluster Members | ID Address Availability State Licensed HA Clusterd Reason
| 1 10.0.0.11 available enabled true active running Run | 2 10.0.0.12 available enabled true active running Run | 3 :: unknown enabled false unknown shutdown Slot powered off or empty | 4 :: unknown enabled false unknown shutdown Slot powered off or empty
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com