Forum Discussion

greedysoul_1733's avatar
greedysoul_1733
Icon for Nimbostratus rankNimbostratus
Oct 09, 2014

network interfaces not connecting

Hello, I'm fairly new to F5 LTM VE and have recently deployed it on a Skytap configuration where I'm trying to get it to work with two VM's , but have been unsuccesful so far. I have configured 4 interfaces for it: mgmt (10.0.0.1), internal (192.168.0.3), external (10.0.1.1) and extra (10.0.2.1). The mgmt interface works fine but I cannot get the other interfaces to communicate correctly in Skytap. It's a very basic problem because I can't even ping the gateway on those subnets, except for the mgmt subnet where I can ping it fine. The configuration in Skytap is similar for all 4 networks. How can I go about troubleshooting this? thx in advance.

 

6 Replies

  • hadn't heard of skytap before, you might want to do a search on that in combination with F5 VE. also if you know the exact hypervisor technology you can search on that. it matters which interfaces you use i believe.
  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus
    Not familiar with skytap, presume it's cloud based. What hypervisor does it use? I'd double check the interface type in skytap with reference to the requirement in the installation guide
  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus
    Sorry boneyard...didn't see your comment (which I've pretty much copied...oops). Think it's because I was on the mobile version of DC. Glad we both agree however ;-)
  • It's VMware ESXi 5.5 as hypervisor on Skytap cloud. The network interfaces are automatic, as far as I know there isn't anything special about them, and as the mgmt interface works fine I think there's some configuration problem in the F5 networking layer but am not sure how I can troubleshoot. The following network adapters are in the F5 Big IP LTE 11.4 Virtual Edition virtual machine. Connected Network Adapter MAC address:00:50:56:3D:7D:02 Network adapter type:Vmxnet3 Network: Mgmt Network Network type:Automatic Hostname:f5bigip IP address:10.0.0.1 Published services:2 Connected Network Adapter MAC address:00:50:56:30:CE:F1 Network adapter type:Vmxnet3 Network: External Network Network type:Automatic Hostname:host-1 IP address:10.0.1.1 Published services:1 Connected Network Adapter MAC address:00:50:56:34:B9:44 Network adapter type:Vmxnet3 Network: Extra Network Network type:Automatic Hostname:host-1 IP address:10.0.2.1 Published services:None Connected Network Adapter MAC address:00:50:56:16:C8:EE Network adapter type:Vmxnet3 Network: Internal Network Disconnect from Network Network type:Automatic Hostname:host-2 IP address:192.168.0.3 Published services:None The F5 reports: [root@f5bigip:Active:Standalone] config tmsh list /net interface net interface 1.1 { if-index 48 lldp-tlvmap 114552 mac-address 00:50:56:30:ce:f1 media-fixed 10000T-FD media-max 10000T-FD mtu 9198 } net interface 1.2 { disabled if-index 64 mac-address 00:50:56:34:b9:44 media-fixed 10000T-FD media-max 10000T-FD mtu 9198 } net interface 1.3 { if-index 80 mac-address 00:50:56:16:c8:ee media-fixed 10000T-FD media-max 10000T-FD mtu 9198 } net interface mgmt { if-index 32 mac-address 00:50:56:3d:7d:02 media-active 100TX-FD } [root@f5bigip:Active:Standalone] config tmsh show /net route ------------------------------------------------------------------------------ Net::Routes Name Destination Type NextHop Origin ------------------------------------------------------------------------------ fe80::/64 fe80::/64 interface tmm0 connected ff02::/64 ff02::/64 interface tmm0 connected ff02:ffe::/64 ff02:ffe::/64 interface /Common/internal connected ff02:ffd::/64 ff02:ffd::/64 interface /Common/external connected fe80::%vlan4094/64 fe80::%vlan4094/64 interface /Common/internal connected fe80::%vlan4093/64 fe80::%vlan4093/64 interface /Common/external connected fe80::%vlan4092/64 fe80::%vlan4092/64 interface /Common/extra connected ff02:ffc::/64 ff02:ffc::/64 interface /Common/extra connected 127.1.1.0/24 127.1.1.0/24 interface tmm0 connected 10.0.2.0/24 10.0.2.0/24 interface /Common/extra connected 192.168.0.0/24 192.168.0.0/24 interface /Common/internal connected 10.0.1.0/24 10.0.1.0/24 interface /Common/external connected
  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus
    So things that jump out. Int 1.2 is disabled and they are running at 10gb. Other than that, any relevant info in ltm log file?
  • Yes, 1.2 is disabled because I'm not currently using that interface (eth2) for anything (see diagram below). Where can I find ltm log file? Thanks again.