Forum Discussion

Yassine_135161's avatar
Yassine_135161
Icon for Nimbostratus rankNimbostratus
Oct 10, 2013

Network configuration for the virtual edition of Big-IP LTM

Hi, I'm running Big-IP LTM VE (the trial license) under VMware workstation 9. And before configuring the features (the most important i guess), i have some questions about networking : I m new with the product and i have a specific deployment for a customer, so i m trying with the trial license before moving to the customer site. (virtual too) Here are details about NICs and IP adresses : vmnet1 (host only): 192.168.2.1 vmnet8 (host only): 192.168.3.1

 

Management IP (bridged network): 192.168.235.128 Internal Self IP (vmnet 1, host only): 192.168.2.10 External Self IP (vmnet 8, host only): 192.168.3.10

 

Apache Web server's:192.168.2.129 / 192.168.2.130 Virtual Server : 192.168.2.111

 

When using all the internal subnet, it's OK, it works fine, and load balancing occurs. (tested from internal to internal) I want to use the external IP address, but i can't even ping it. I can't ping my vmnet 8 ip address from big-ip too !!! Can you try to give some explanations about that !!

 

All this because i want to test something : i want to deploy BIG-IP LTM to load balance traffic for servers under the interface 1.1 (internal) and to use the interface 1.2 as a second internal interface (such it's an ethernet interface), for web-caching purpose (servers deployed behind the 1.2 interface) Is that possible ??

 

Thank you for your help, i remain available to give you further details if needed. And i'll let you know if i find answers to that.

 

Regards,

 

deployment
design
management

14 Replies

Sort By
  • Yassine_135161's avatar
    Yassine_135161
    Icon for Nimbostratus rankNimbostratus
    Oct 10, 2013

    • Here are details about NICs and IP adresses* vmnet1 (host only): 192.168.2.1* vmnet8 (host only): 192.168.3.1

       

    • Management IP (bridged network): 192.168.235.128

       

    • Internal Self IP (vmnet 1, host only): 192.168.2.10* External Self IP (vmnet 8, host only): 192.168.3.10

       

    • Apache Web server's:192.168.2.129 / 192.168.2.130

       

    • Virtual Server : 192.168.2.111
    • Dan_Lowry_5655_'s avatar
      Dan_Lowry_5655_
      Icon for Nimbostratus rankNimbostratus
      Oct 18, 2014
      HI, I'm attempting to bring up GNS 3 in the same configuration. Are you able to see the pools active for the Apache Web Server, and also access the server via an Emulated PC on the External Vlan? Thanks, Dan
  • What_Lies_Bene1's avatar
    What_Lies_Bene1
    Icon for Cirrostratus rankCirrostratus
    Oct 10, 2013

    OK, I'm not too familiar with VMware Workstation but I'll try to help. Can you describe your VLAN setup please? From the F5 VE point of view, are the interfaces up? Are you tagging or not etc?

     

  • Yassine_135161's avatar
    Yassine_135161
    Icon for Nimbostratus rankNimbostratus
    Oct 10, 2013

    Thank you,

     

    * Vlan internal : Tag=4094 (by default) ---> untagged interface 1.1 : Self IP=192.168.2.10/24

     

    * Vlan external : Tag=4093 (by default) ---> untagged interface 1.2 : Self IP=192.168.3.10/24

     

    Interfaces' status is shown up

     

    • What_Lies_Bene1's avatar
      What_Lies_Bene1
      Icon for Cirrostratus rankCirrostratus
      Oct 10, 2013
      OK, thanks and these VLANs are configured in VMWare too via port groups and also untagged? What/where are the .1 addresses?
    • Yassine_135161's avatar
      Yassine_135161
      Icon for Nimbostratus rankNimbostratus
      Oct 10, 2013
      In VMware workstation; i don't think that we can configure port groups or other vswitch purposes... But in customer environment, i will have to deal with that (VMware ESXi)
  • Yassine_135161's avatar
    Yassine_135161
    Icon for Nimbostratus rankNimbostratus
    Oct 17, 2013

    To update the issue : I've tried to add a virtual NIC to my VM (in VMware workstation), i can see the new interface 1.3, but it's always displayed as "uninitialized" with a MAC address of "0:0:0:0:0:0" !!!

     

    Another question, can i install the trial version (10.1) and upgrade it to a full version when purchasing the license ?

     

    Thank you,

     

  • What_Lies_Bene1's avatar
    What_Lies_Bene1
    Icon for Cirrostratus rankCirrostratus
    Oct 17, 2013

    Just on the first issue, I suspect it's tagging related. In VMW 4094 is untagged by default but I suspect it's not for other VLANs so maybe looking into that.

     

    Regarding the trial version you probably can but as it's v10.1 and we're up to v11.4 it's probably going to be a little tricky. If you're serious about using (or just fully testing) LTM I'd suggest you get a trial for a more recent version via F5 or your reseller (or purchase a relatively cheap lab edition). v11 also improves on a fair number of the virtualisation related features so will probably be easier to setup.

     

  • What_Lies_Bene1's avatar
    What_Lies_Bene1
    Icon for Cirrostratus rankCirrostratus
    Oct 17, 2013

    That's a steep learning curve for you then but at least with VE you can 'break' it and still start again.

     

    I don't see any reason why you couldn't upgrade to a full product from a trial version with a simple license key. Whether the trail version is good enough only depends on the expected traffic throughput; that's the only restriction. I know the Lab edition is restricted to 10Mb (combined in and out I think), not sure about the trial edition.

     

    An upgrade shouldn't be too much trouble if the configuration isn't too complex or large scale but I'd highly recommend starting on v11.3 at least if you can get a Lab/evaluation license for it. The virtualisation will be easier, the default license limits are more generous and there are many new features and enhancements that you'll benefit from.

     

    If you can get in touch with a good reseller or F5 directly it shouldn't be hard to get a v11 trial and possibly more importantly some useful support and advice.

     

  • szakaria_137124's avatar
    szakaria_137124
    Icon for Nimbostratus rankNimbostratus
    Nov 06, 2013

    I tried also VMware Workstation 9 with BIGIP Virtual Edition but encountered the same issues. I will try VMware Workstation 7 and update this post in few days.

     

    • Yassine_135161's avatar
      Yassine_135161
      Icon for Nimbostratus rankNimbostratus
      Nov 06, 2013
      Hi, In fact, i think it could be a bug in the trial version. this is how i solve it : I tested the trial version in ESXi this time and when i add a new NIC to the VM, i can see the new NIC 1.3 UP with the correct MAC address. the old interface 1.2 (named external above) begins to function correctly and the problem occurs for just the newly added NIC (1.3), and so on. I'll deal with a prodcution version soon, i'll let you know if the problem persists
  • Said_01_134591's avatar
    Said_01_134591
    Icon for Nimbostratus rankNimbostratus
    Nov 09, 2013

    I uninstalled Vmware workstation 9 and I replaced it with vmware workstation 10. I created a fresh BIGIP VM with a new license, created 1 internal and 1 external interfaces and I can see that their MAC addresses are shown correctly. I used GNS3 to create a small setup with switches, hosts, BIGIP...etc everything works fine now. I will not go further and test Vmware workstation 7 because it should work as well. I think only Vmware 9 is not compatible with BigIP virtual edition.