Forum Discussion

zchriss's avatar
zchriss
Icon for Altostratus rankAltostratus
May 16, 2019

BIG-IP VE network interfaces and network adapters

Hi,

I'm deploying the virtual edition of BIG-IP and I am having trouble reconciling the link between the virtual network adapters (in VMWare or Hyper-V) and the interfaces on BIG-IP.

Example - VMWare has four virtual adapters on vSwitchs: 0 is on the management network, 1 is on the external network, 2 is on the internal network, and 3 is on a network just for HA (for two Big-IPs).

This seems to be reflected in TMOS:

[root@bigip1:Active:In Sync] config # tmsh lsit net interface
net interface 1.1 {
    if-index 48
    mac-address 00:50:56:af:48:08
    media-active 10000T-FD
    media-fixed 10000T-FD
    media-max auto
}
net interface 1.2 {
    if-index 64
    mac-address 00:50:56:af:6c:2a
    media-active 10000T-FD
    media-fixed 10000T-FD
    media-max auto
}
net interface 1.3 {
    if-index 80
    mac-address 00:50:56:af:46:b0
    media-active 10000T-FD
    media-fixed 10000T-FD
    media-max auto
}
net interface mgmt {
    if-index 32
    mac-address 00:50:56:af:39:b9
    media-active 100TX-FD
}

Ethmap also shows we have four network adapters:

[root@bigip1:Active:In Sync] config # cat /etc/ethmap
eth0 00_50_56_af_39_b9
eth1 00_50_56_af_48_08
eth2 00_50_56_af_6c_2a
eth3 00_50_56_af_46_b0

But what are all these devices listed in the Linux Kernel itself?

[root@bigip1:Active:In Sync] config # ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc mq master mgmt state UP qlen 1000
    link/ether 00:50:56:af:39:b9 brd ff:ff:ff:ff:ff:ff
6: mgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 00:50:56:af:39:b9 brd ff:ff:ff:ff:ff:ff
7: tmm: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9282 qdisc noqueue state UNKNOWN qlen 1
    link/ether 00:98:76:54:32:10 brd ff:ff:ff:ff:ff:ff
8: HA: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1
    link/ether 00:50:56:af:46:b0 brd ff:ff:ff:ff:ff:ff
9: external: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1
    link/ether 00:50:56:af:6c:2a brd ff:ff:ff:ff:ff:ff
10: internal: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1
    link/ether 00:50:56:af:48:08 brd ff:ff:ff:ff:ff:ff
11: tmm_bp: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1640 qdisc noqueue state UNKNOWN qlen 1
    link/ether 02:01:23:45:00:fe brd ff:ff:ff:ff:ff:ff

Testing on Hyper-V I also have extra interfaces named "mgmt", "tmm", "tmm_bp", "http-tunnel" and "socks-tunnel". This is from a clean install of BIG-IP VE.

How do I make sure that the configured interface for internal traffic is using the correct virtual network adapter in VMWare?

What are all these extra interfaces?

I hope my question isn't too open-ended.

Cheers,

Chris

3 Replies

  • Hi Chris,

     

    You're seeing many virtual and internal adapters in Linux. The adapters named HA, external and internal refer to configured TMM vlans. The adapters named tmm and tmm_bp are internal. You shouldn't expect to see the 1.1, 1.2, 1.3 interfaces here because TMM "owns" them. TMM handles these interfaces directly which prevents them from showing up in Linux. The view from TMM as seen in "tmsh show net interface" is what really matters since TMM processes the traffic using these interfaces.

     

    Lastly, your mgmt interface is probably the only one that works as you would expect, being a direct connection to the VMware e1000 nic.

     

    Hope this helps.

    -Danny

     

    • Ford_Prefect's avatar
      Ford_Prefect
      Icon for Cirrus rankCirrus

      Danny,

       

      Do I understand correctly that

      • 1.1
      • 1.2
      • 1.3
      • mgmt

      are virtual interfaces, that have appropriate vNICs or phisical cooper/optic interfaces depending on platform - virtual or phisical and

      • eth0
      • tmm
      • tmm_bp
      • http-tunnel
      • socks-tunnel
      • portal_profile - that appears in my case as well, when I run ip link show

      are internal F5 interfaces?

      • Daniel_Epperson's avatar
        Daniel_Epperson
        Icon for Employee rankEmployee

        Hello Ford. Yes, these internal interfaces are used by the Linux kernel and can be safely ignored. You may be asked to check these during the course of troubleshooting but otherwise they should be left alone.