Forum Discussion

Junaid_Subhani_'s avatar
Junaid_Subhani_
Icon for Nimbostratus rankNimbostratus
Jan 23, 2015

Unable to connect multiple networks

Hi all,   I downloaded the trial VM for F5 LTM load balancer and ran it in my vCloud environment. eth0 is able to get an IP from the corporate network using DHCP.   The issue is that when I try...
availability
deployment
design
management
virtualization
  • Brad_Parker_139's avatar
    Brad_Parker_139
    Jan 23, 2015

    eth0 is going to be the management interface, which by default is un-tagged and can use DHCP. eth1 and eth2 are going to be traffic interfaces. To assign a self IP to a traffic interface it needs to be associated with a VLAN either un-tagged or tagged. You can create VLANs, assign interfaces to them, and create self IPs either from tmsh or the GUI. Self IPs are created in VLANs and VLANs are assigned to interfaces. It sounds like in your case you want one selfIP assigned to each interface and each virtual interface is in a different port group in vCloud. In this case, you will create a VLAN named "Internal" and assign eth1 to that VLAN un-tagged. You will then also, create a VLAN named "External" and assign eth2 to that VLAN un-tagged. The you can create you selfIPs for each of the VLANs. All of this should be able to be done in tmsh via "create net ..." https://support.f5.com/kb/en-us/solutions/public/14000/900/sol14961.html

     

Brad_Parker_139's avatar
Brad_Parker_139
Icon for Nacreous rankNacreous
Jan 23, 2015

eth0 is going to be the management interface, which by default is un-tagged and can use DHCP. eth1 and eth2 are going to be traffic interfaces. To assign a self IP to a traffic interface it needs to be associated with a VLAN either un-tagged or tagged. You can create VLANs, assign interfaces to them, and create self IPs either from tmsh or the GUI. Self IPs are created in VLANs and VLANs are assigned to interfaces. It sounds like in your case you want one selfIP assigned to each interface and each virtual interface is in a different port group in vCloud. In this case, you will create a VLAN named "Internal" and assign eth1 to that VLAN un-tagged. You will then also, create a VLAN named "External" and assign eth2 to that VLAN un-tagged. The you can create you selfIPs for each of the VLANs. All of this should be able to be done in tmsh via "create net ..." https://support.f5.com/kb/en-us/solutions/public/14000/900/sol14961.html

 

  • Junaid_Subhani_'s avatar
    Junaid_Subhani_
    Icon for Nimbostratus rankNimbostratus
    Jan 23, 2015
    Thank You Brad Ok so here is what I did: Using cli in tmsh mode: create net vlan internal interfaces add { 1.1 } eth1 for internal traffic create net vlan external interfaces add { 1.2 } eth2 for external traffic Using Web Console: Goto Netwrok -> Self IPs -> Create Name: Internal IP Address: 10.1.1.1 Netmask: 255.255.255.0 VLAN: internal the one I made above --Update-- Name: External IP Address: 12.1.1.1 Netmask: 255.255.255.0 VLAN: external the one I made above --Update-- Should this be enough to set the IPs on the interfaces on the load balancer ? BR, Junaid
  • Brad_Parker_139's avatar
    Brad_Parker_139
    Icon for Nacreous rankNacreous
    Jan 23, 2015
    Yep, that should give you basic layer 2 connectivity in those two subnets. Now if you want basic "routing" through the LTM from the internal VLAN to the outside world you will need a default route and a wildcard Forwarding IP virtual server(0.0.0.0:0) and possibly a SNAT configuration on that if your network requires it. That should do it for the basic connectivity. https://support.f5.com/kb/en-us/solutions/public/7000/500/sol7595.html