[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1258
  • Last Modified:

bigip ltm new setup, node routing problem?

I'm setting up a new bigip box. I setup the interface, pools, virtual servers, etc. for a web site. When I tested it out the following statistics are shown.
                     |  bits  since       |  bits  in prior    |  current
                     |  Oct 14 11:00:14   |  5 seconds         |  time
BIG-IP      ACTIVE   |---In----Out---Conn-|---In----Out---Conn-|  12:52:48
bigip1.acompany.com 122032  43520     33      0      0      0

VIRTUAL ip:port      |---In----Out---Conn-|---In----Out---Conn-|-Nodes Up--
192.168.59.64:http    121600  43520     32      0      0      0      2
192.168.59.64:https        0      0      0      0      0      0      2

NODE ip:port         |---In----Out---Conn-|---In----Out---Conn-|--State----
192.168.55.46:http     30912      0     12      0      0      0 UNCHECKED
192.168.55.47:http     30912      0     12      0      0      0 UNCHECKED
192.168.55.43:38080    10304      0      4      0      0      0 UNCHECKED
192.168.55.44:38080    10304      0      4      0      0      0 UNCHECKED
192.168.55.43:38082        0      0      0      0      0      0 UNCHECKED
192.168.55.44:38082        0      0      0      0      0      0 UNCHECKED
192.168.55.43:38083        0      0      0      0      0      0 UNCHECKED
192.168.55.46:https        0      0      0      0      0      0 UNCHECKED
192.168.55.47:https        0      0      0      0      0      0 UNCHECKED

This is what netstat -rn shows
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
127.1.1.0       0.0.0.0         255.255.255.248 U         0 0          0 tmm0
192.168.55.32   0.0.0.0         255.255.255.224 U         0 0          0 internal
10.40.9.0       0.0.0.0         255.255.255.0   U         0 0          0 eth0
127.2.0.0       0.0.0.0         255.255.255.0   U         0 0          0 eth0
192.168.59.0    0.0.0.0         255.255.255.0   U         0 0          0 external
127.0.0.0       -               255.0.0.0       !         - -          - -
0.0.0.0         10.40.9.27      0.0.0.0         UG        0 0          0 eth0

So here are my questions.
1. What is my problem? Lets keep it specific to the problem described above. :)
2. Does the netstat -rn command need a gateway defined or is it sufficient to just have the interface defined?

Thanks in advanced.
0
jsfald
Asked:
jsfald
1 Solution
 
jsfaldAuthor Commented:
The problem was with the node/server. It didn't have a proper default route. Making the default route point to the floating ip of the f5 fixed the problem. I'll ask community support to close the question.
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now