Forum Discussion

Lions_229232's avatar
Lions_229232
Icon for Nimbostratus rankNimbostratus
Jan 10, 2016

LTM config issue

Hi, I am having an issue and would like your help on this. Below is my LTM network topology and it's working, but I am having one NEW issue when creating a new network (10.4.0.0/24) for another set of web servers, the LTM is unable to ping those gateway 10.4.0.1 and web servers (10.4.0.0/24), but the LTM can ping other networks fine.

 

  1. created a new selfip 10.4.0.145 and floating ip 10.4.0.155

     

  2. assigned an ip 10.4.0.5 to the web server and gateway as 10.4.0.1.Verified the web server is working from my PC.

     

LTM can't ping 10.4.0.1, so what am I missing here?

 

Outside network (192.168.0.0/24) selfip: 192.168.0.145 floatingip: 192.168.0.155

 

Internal network ( 10.2.0.0/24) selfip: 10.2.0.145 floatip: 10.2.0.155

 

management network: (10.1.0.0/24) selfip: 10.1.0.145

 

HA network: (10.3.0.0/24) selfip: 10.3.0.145 floatip: 10.3.0.155

 

web servers ips: web1: 10.2.0.16 web02: 10.2.0.27 web3: 10.2.0.18

 

Thanks

 

application delivery
LTM
  • BinaryCanary_19's avatar
    BinaryCanary_19
    Historic F5 Account
    Jan 11, 2016

    Is the LTM connected to the same LAN segment as the servers on 10.4.0.0/24 ?

     

    Also, this may seem trivial, but windows servers tend to not respond to ping by default, so make sure that this is not your problem (you can test http connection instead)

     

    • Lions_229232's avatar
      Lions_229232
      Icon for Nimbostratus rankNimbostratus
      Jan 11, 2016
      Hi The LTM is connected to the same LAN segment 10.4.0.0/24, the same way I setup for 10.2.0.0/24 ( this one is working for ping, ltm config, access, etc, happy). I ignored the ping issue on the LTM for now, but when I tried to add a new node using 10.4.0.0/24, LTM monitoring failed, right away I know something was not right. If you look at configs that I posted earlier, I added 10.4.0.0/24 on the internal interface, but that did not do any good. Any thoughts?
    • BinaryCanary_19's avatar
      BinaryCanary_19
      Historic F5 Account
      Jan 11, 2016
      back up a little. What vlan is "internal"? Is it tagged? What vlan is 10.4.0.0/24 supposed to be on? Have you assigned the self-IPs to the correct vlan? It's difficult to guess what's going on, except to suspect that you may have added the IP to the wrong vlan (if they are directly connected to the same lan segment), or if they are not directly connected, then you don't have a route configured or the router is not configured to forward the packets it's getting.
    • Lions_229232's avatar
      Lions_229232
      Icon for Nimbostratus rankNimbostratus
      Jan 11, 2016
      Hi, this is what I have is working right now meaning I can create VIP and it's accessible. All interfaces are configured untagged. 1. Internal Vlan (10.2.0.0/24) -> selfIP .145/floating .155 2. External Vlan (192.168.50.0/24) --> selfip .145/floating .155 3. HA Vlan (10.3.0.0/24)--> selfip--> 10.3.0.145/floating .155 4. Management (10.1.0.0/24) -->selfip-->10.1.0.145 5. Gateway--> 192.168.50.1 Now I am having a new network 10.4.0.0/24, GW 10.4.0.1, assigned .11/.12 to two web servers. The steps I configured in LTM and it's not working. How would you add config a new network in LTM? add a new config: 1. Vlan->new selfip--> 10. 4.0.145, float-->10.4.0.155 on internal VLan
  • Tamer_Ezzat_235's avatar
    Tamer_Ezzat_235
    Icon for Nimbostratus rankNimbostratus
    Jan 11, 2016

    Hi,

     

    Could you please check the interfaces on the F5 check the truck and VLANs ? May be something wrong there

     

    Regards,