Viprion Guest Spanning Multiple Slots and Primary Member - Question
I am involved in a very difficult case where one of our Viprion guests has been unstable since January and we've incurred countless hours trying to get one of the guests in a traffic group back to normal operation in the traffic group etc.
Currently, the guest is severed from the network to allow support to attempt to resolve the issue. They've tried countless ideas but none have worked.
At this point, I am thinking a complete deletion of the guest from both slot 1 and 2 on the severed host and a reprovision of the guest is in order. F5 support indicates that this won't work as "slot 2 is primary for this guest, and it needs to be slot 1 or it won't work." They indicate that re-provisioning the guest will fail as slot 2 will still become the primary member for this guest.
This does not make much sense to me as I did not know there was a difference of which slot number in a guest spanning multiple slots becomes active. For instance, I could provision a guest to only exist on slot 2 and it would be functional. Why does it matter if slot 1 is primary and 2 is not, so long as they sync properly?
I've asked the engineer for written verification of this issue because it doesn't make any sense to me. Can anyone elaborate on why he is indicating a complete re-provision of this faulty guest on the chassis would not work?
Thank you in advance. It is appreciated.