Forum Discussion

donnieatbowie_2's avatar
donnieatbowie_2
Icon for Altostratus rankAltostratus
Apr 12, 2017
Solved

F5 BIGIP 13 VE - Uninitialized interfaces

Hi Guys. i'm "trialing" the ve edition of the product. I've deployed the ova. the management interface is working well, but all the other interfaces are "uninitialized".

 

I've added those to a vlan, but still - nothing. any advice ?

 

  • The problem was with the F5 90 days trial license. i got a temporary 45 days full trial license from F5 and that solved the issue.

     

    sounds stupid? indeed

     

5 Replies

  • I just had a look in my lab, with esxi server and a VE with v13. The interface shows uninitialized only if is not associate with a vlan.

     

    I tried to change the vm settings in the esxi, changing the interface to disconnected and changing the vlan, but does not have effect in the interface status.

     

  • Configure a VLAN using 1.1

     

    Configure a Self IP using the new VLAN

     

    Go back and view interfaces. Is 1.1 still uninitialized?

     

    • donnieatbowie_2's avatar
      donnieatbowie_2
      Icon for Altostratus rankAltostratus

      Hi, thanks so much for replying. Unfortunately, still uninitialized after trying what you have suggested.

       

    • Kevin_Davies_40's avatar
      Kevin_Davies_40
      Icon for Nacreous rankNacreous

      Ok then you are likely hitting a virtualization status bug. Is the virtual interface connected to a known VLAN? Is the selfIP in that VLAN? Then try pinging an address in that VLAN from the command line on the F5. If the ping is successful then it is the status bug then the network will be fine, it is just not reflected in the GUI. It may show as UP after a reboot.

       

  • The problem was with the F5 90 days trial license. i got a temporary 45 days full trial license from F5 and that solved the issue.

     

    sounds stupid? indeed