Forum Discussion

chris_connell_1's avatar
chris_connell_1
Icon for Nimbostratus rankNimbostratus
Nov 23, 2009

command to make a slot primary/secondary

Hi,

 

On a viprion system I am looking for a command to make the slot primary or secondary, either by forcing another slot to be primary, or the current primary to be secondary. I am talking about the blade which is displayed as S1-P and S2-S.

 

 

I cant seem to find out to do it in b cluster. This displays the primary slot with b cluster current primary slot id show but doesnt seem to allow to change another slot to be primary.

 

 

Thanks
config
design
  • spark_86682's avatar
    spark_86682
    Historic F5 Account
    Nov 23, 2009
    There is no way to manually specify what blade is primary or secondary. What is it that you're really trying to accomplish?
  • chris_connell_1's avatar
    chris_connell_1
    Icon for Nimbostratus rankNimbostratus
    Nov 24, 2009
    OK, I will explain

     

     

    We have 2 blades in the viprion chassis. There is the cluster IP and management IP for each blade. Each blade has its management port connected to a different switch for redundancy. If for example the first switch fails which is connected to the first blade, we are not able to reach the cluster IP or the first blade IP (as there is no failover mechanism for the management port). We can get on the gui and ssh to the second blade ip but cant make changes, since the first blade internally is still primary.

     

     

    The only way I know to make the second blade primary (thus able to make changes on the gui and access the cluster ip), is to reboot the first blade, but I am sure there must be a quicker way to do it. This is why I want to know if there is a simple command to change a slot to be primary.

     

     

    • brad_11480's avatar
      brad_11480
      Icon for Nimbostratus rankNimbostratus
      Jul 13, 2017

      From what I'm gathering running a guest across slots/blades is not a good approach. Keep each guest on a single blade. Unless you are running a single copy of a guest and want to have some availability if a blade fails. Running two guests in HA with each guest on a separate blade would achieve the same with better availability.