Viprion Guest Spanning Multiple Slots and Primary Member - Question

Thanks for the reply, Brad. That is what I would expect. We have to slots in a Viprion Chassis and slot 1 is offline and is not communicating properly. Slot 2 is primary. We are trying to bring this cluster up and the support engineer states the following: **The support engineer states:** The crux of the current issue is that the cluster/management IP address is not being propagated to slot 1. Unfortunately, any changes need to be made on the Primary slot, which is slot 2. "A floating management IP address that you use to manage the guest. The BIG-IP system assigns this IP address to the primary cluster member for the guest." There are a few options that we can try before the action plan we discussed earlier. 1) "Modify" the cluster/management IP address: 'Change' the cluster IP (DON'T UPDATE), then change it back to the original value and update the 'changed config. This should be occurring already (propagation of cluster iP from slot 2 --> slot 1 for the guest) System --> Cluster --> Management IP 2) Change the guest stated from Deployed --> Provisioned, then back to Deployed. 3) Create an UCS archive for the guest, delete the guest entirely, then re-create the guest and restore the UCS archive. ***Please keep in mind that the propagation of the cluster/management IP address should already be occurring, and as such, we do not believe there is a high degree of probability that the above step(s) would work.***

I'm not going to get involved too much with your support case, but know that the primary slot for the vCMP guest can be a different slot than the primary for the vCMP host.