Forum Discussion

Eric_Stewart_36's avatar
Eric_Stewart_36
Icon for Nimbostratus rankNimbostratus
Dec 12, 2018

Verify Routing

Hello

 

I am using an i4600 and wondering how to verify routing. I am trying to setup a remote server location for syslog and I want to have those send out the management interface. Is there a way for me to ping the remote server from the F5 and validate that it exists the management interface? I am still a newbie at this so detailed info is best if you can.

 

Thanks! Eric

 

application delivery
LTM
  • Philip_Jonsson's avatar
    Philip_Jonsson
    Icon for MVP rankMVP
    Dec 12, 2018

    Hey Eric!

    You could try and use the -I switch for the ping command to select either eth0 for the management address or the VLAN name for a TMM interface. Just use the following syntax:

    Management Interface:

    ping -I eth0 8.8.8.8

    TMM Interface:

    ping -I [VLAN Name] 8.8.8.8

    I also usually check which routes the BIG-IP will use based on destination IP by running the ip route command. For example:

    Management Port:

    [root@bigip1.f5labs.com:Active:In Sync] ~  ip route get 172.16.1.44
172.16.1.44 dev mgmt  src 172.16.2.10
    cache

    TMM Interface:

    [root@bigip1.f5labs.com:Active:In Sync] ~  ip route get 192.168.10.1
192.168.10.1 via 192.168.15.1 dev Servers  src 192.168.15.6
    cache

    Since the BIG-IP have routing subtables, one for the Linux part and one for the TMM, if equal routes exists in both TMM and Linux kernel, it will choose the TMM routes because it has a lower metric. In these cases you might need to create more specific management routes in order to force traffic through the management port. Check out the following article:

    K13284: Overview of management interface routing (11.x - 14.x)

    I hope this helps! 🙂

    Let me know if you have follow-up questions.