Forum Discussion

David_130214's avatar
David_130214
Icon for Nimbostratus rankNimbostratus
Dec 17, 2014

Setting up new LTM VE locally. Ping connects to member I.P then fails on LTM IP

Hello,

 

I'm trying to set up a f5 LTM VE on our local QA environment for testing purposes. From the f5 VM, I'm trying to ping another server. Below it what I get back.

 

10.34.0.100 is the server I want to connect to 10.34.0.101 is the f5 internal and external VLAN (Since this is an internal only enviroment, I didn't need external but the setup config made me enter something)

 

[root@f5-1:Active:Standalone] config ping 10.34.0.100 PING 10.34.0.100 (10.34.0.100) 56(84) bytes of data. From 10.34.0.101 icmp_seq=1 Destination Host Unreachable From 10.34.0.101 icmp_seq=2 Destination Host Unreachable From 10.34.0.101 icmp_seq=3 Destination Host Unreachable From 10.34.0.101 icmp_seq=5 Destination Host Unreachable From 10.34.0.101 icmp_seq=6 Destination Host Unreachable From 10.34.0.101 icmp_seq=7 Destination Host Unreachable

 

Thanks,

 

David

 

5 Replies

  • David_130214's avatar
    David_130214
    Icon for Nimbostratus rankNimbostratus
    Dec 17, 2014
    Sorry that ping data is not readable [root@f5-1:Active:Standalone] config ping 10.34.0.100 PING 10.34.0.100 (10.34.0.100) 56(84) bytes of data. From 10.34.0.101 icmp_seq=1 Destination Host Unreachable From 10.34.0.101 icmp_seq=2 Destination Host Unreachable From 10.34.0.101 icmp_seq=3 Destination Host Unreachable From 10.34.0.101 icmp_seq=5 Destination Host Unreachable From 10.34.0.101 icmp_seq=6 Destination Host Unreachable From 10.34.0.101 icmp_seq=7 Destination Host Unreachable
    • David_130214's avatar
      David_130214
      Icon for Nimbostratus rankNimbostratus
      Dec 18, 2014
      Thanks for your responses. I may need to ask a different question based setup recommendations for internal use only.
  • Michael_Jenkins's avatar
    Michael_Jenkins
    Icon for Cirrostratus rankCirrostratus
    Dec 18, 2014

    In the past, we had a problem similar to this. I think we wound up having to add a route in the BIG-IP system because it wasn't there. You may want to check the route table on the server and the route table on the F5 device. Maybe there's not a default route... Worth a shot... 

    Network >> Routes
    or 
    route
    from the shell.