Forum Discussion

Dana_Knudson_24's avatar
Dana_Knudson_24
Icon for Nimbostratus rankNimbostratus
Jan 20, 2016

vCMP and Trunk configuration

I'm new to working with vCMPs...

 

I have two 52550v set up as vCMP hosts. Each host has two 10GB fiber connections that connect to the pair of core switches. I have created a trunk and added the interfaces. I have then created several VLANs (with tagging) and added the trunk to the VLANs. Then I added the VLANs to the vCMPs.

 

Now when I log into the vCMP, I see the VLANs, but when I try to set up HA using the VLANs, I get a message that the the VLAN doesn’t have an interface. When I look at the VLAN the interface is empty. I can see the Trunk in the list, but I can't add it to the VLAN, which makes sense, because I should only add it to the VLAN from the HOST.

 

Am I missing something? Is there something wrong with me using the same trunk for more than one VLAN?

 

9 Replies

  • There shouldn't be any issue with what you have tried. You do not do anything with interfaces from within a vCMP guest. Couple questions. When you say you added the VLANs to the vCMPs, does that mean you added the VLANs to the guests from the hosts? Also, what software version are you running?

     

    • Dana_Knudson_24's avatar
      Dana_Knudson_24
      Icon for Nimbostratus rankNimbostratus
      Yes, I add the VLANs to the guests from the host. I am running software version 12.0. Additionally, the guests were created before the the VLANs were created on the host. However when I created the VLANs and added them to the guest they showed up with no issues inside the guest.
    • Brad_Parker_139's avatar
      Brad_Parker_139
      Icon for Nacreous rankNacreous
      What you are doing is correct, adding VLANs after the guest has been created is supported. However, v12.0 is brand spanken new. I would recommend opening a support case with F5.
  • There shouldn't be any issue with what you have tried. You do not do anything with interfaces from within a vCMP guest. Couple questions. When you say you added the VLANs to the vCMPs, does that mean you added the VLANs to the guests from the hosts? Also, what software version are you running?

     

    • Dana_Knudson_24's avatar
      Dana_Knudson_24
      Icon for Nimbostratus rankNimbostratus
      Yes, I add the VLANs to the guests from the host. I am running software version 12.0. Additionally, the guests were created before the the VLANs were created on the host. However when I created the VLANs and added them to the guest they showed up with no issues inside the guest.
    • Brad_Parker's avatar
      Brad_Parker
      Icon for Cirrus rankCirrus
      What you are doing is correct, adding VLANs after the guest has been created is supported. However, v12.0 is brand spanken new. I would recommend opening a support case with F5.
  • Turns out that the vCMP guest will get the message that the the VLAN doesn’t have an interface, and is expected behavior. The vCMP will not show the interface in the VLAN. As long as the HOST has the VLANs configured correctly nothing need to to be set on the guest and ignore the interface warning when setting the VLANs for HA.

     

  • My issue also relates to the mentioned thread topic, therefor I place my question here as well instead of starting a new thread.

     

    We have a cluster out of 3 BIG-IP 5250v using vCMP. The hosts are running on 11.5.4 HF2 and the guests on 12.1.0 HF1. Currently we have guest1 with 4 cores assigned and guest2 with 2 cores (2 cores free for later use). On the hosts we created a trunk for interfaces 2.1 - 2.4. This trunk is available for all three guest2-instances, but only for one guest1-instance. Not sure if this is related to the issue, but guest1 is currently not yet in use and only has HB-VLANs assign, which are not part of the trunk. Guest2 has already several VLANs assigned, which were part of the trunk. The guest1-instance where the trunk is available is the Active one.

     

    So the question is, did I something wrong, is there something missing, is this normal and how can I fix this?

     

    If you need any more information or have ideas what I should check or test, please let me know.

     

    Thank you!

     

    Ciao Stefan :)

     

  • Seems I found the reason for this behavior.

     

    The trunk is first available on the guests, when you create a VLAN on that trunk and assign this VLAN to the guest. But why was it already there for one out of the three LBs? Probably I was assigning one VLAN for guest2 by mistake to guest1, which triggered to have the trunk available/visible on guest1. After removing the VLAN again from guest1 the trunk is still available. I double checked this with the second LB from this cluster and it behaves exactly as described above.

     

    Maybe this might be a helpful information for someone else out there.

     

    Ciao Stefan :)