Forum Discussion
Jon_43169
Nimbostratus
NimbostratusLogs say no route to host. Routing table and tcptrraceroute say otherwise. Reset packets being sent as a result.. halp
I've not seen this before and am honestly stumped.
From the logs:
Thu Jun 5 12:00:34 CDT 2014 err F5 tmm[9502] 01230140 RST sent from 10.180.48.237:80 to 10.180.48.3:58937, [0x174f...
Jon_43169Nimbostratus
Nimbostratusroot@(F5)(cfg-sync Changes Pending)(Active)(/NONPROD)(tmos) show /net route
-------------------------------------------------------------------------------
Net::Routes
Name Destination Type NextHop Origin
-------------------------------------------------------------------------------
fe80::/64 fe80::/64 interface tmm0 connected
ff02::/64 ff02::/64 interface tmm0 connected
fe80::%vlan4095/64 fe80::%vlan4095/64 interface tmm_bp connected
ff02:fff::/64 ff02:fff::/64 interface tmm_bp connected
fe80::%vlan52/64 fe80::%vlan52/64 interface /Common/NONPROD connected
ff02:34::/64 ff02:34::/64 interface /Common/NONPROD connected
fe80::%vlan12/64 fe80::%vlan12/64 interface /Common/PCI connected
ff02:c::/64 ff02:c::/64 interface /Common/PCI connected
fe80::%vlan4094/64 fe80::%vlan4094/64 interface /Common/HA connected
ff02:ffe::/64 ff02:ffe::/64 interface /Common/HA connected
fe80::%vlan32/64 fe80::%vlan32/64 interface /Common/PROD connected
ff02:20::/64 ff02:20::/64 interface /Common/PROD connected
fe80::%vlan48/64 fe80::%vlan48/64 interface /Common/nonprod48 connected
ff02:30::/64 ff02:30::/64 interface /Common/nonprod48 connected
fe80::%vlan28/64 fe80::%vlan28/64 interface /PROD/Prod_vip28 connected
ff02:1c::/64 ff02:1c::/64 interface /PROD/Prod_vip28 connected
127.1.1.0/24 127.1.1.0/24 interface tmm0 connected
127.20.0.0/16 127.20.0.0/16 interface tmm_bp connected
10.170.32.0/22 10.170.32.0/22 interface /Common/PROD connected
10.160.12.0/22 10.160.12.0/22 interface /Common/PCI connected
10.180.52.0/22 10.180.52.0/22 interface /Common/NONPROD connected
192.168.25.0/30 192.168.25.0/30 interface /Common/HA connected
10.170.28.0/22 10.170.28.0/22 interface /PROD/Prod_vip28 connected
[root@F5:Active:Changes Pending] config route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.192.53 192.168.193.1 255.255.255.255 UGH 9 0 0 eth0
192.168.192.52 192.168.193.1 255.255.255.255 UGH 9 0 0 eth0
192.168.25.0 0.0.0.0 255.255.255.252 U 0 0 0 HA
127.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 tmm0
192.168.193.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.3.0.0 0.0.0.0 255.255.255.0 U 0 0 0 mgmt_bp
127.2.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0.1
10.101.120.0 192.168.193.1 255.255.255.0 UG 9 0 0 eth0
10.170.32.0 0.0.0.0 255.255.252.0 U 0 0 0 PROD
10.180.52.0 0.0.0.0 255.255.252.0 U 0 0 0 NONPROD
10.170.28.0 0.0.0.0 255.255.252.0 U 0 0 0 Prod_vip28
10.160.12.0 0.0.0.0 255.255.252.0 U 0 0 0 PCI
0.0.0.0 192.168.193.1 0.0.0.0 UG 9 0 0 eth0
So it's in the kernel routing table, but not LTMs. I suppose a static route should resolve that?
If that's the case, I'm curious why the pool is passing the health monitor:
[root@F5:Active:Changes Pending] config tmsh show ltm pool /NONPROD/crmqa members | egrep 'Ltm::Pool|Avail|State|Monit'
Ltm::Pool: /NONPROD/crmqa
Availability : available
State : enabled
Monitor : /NONPROD/MON-HTTP
| Ltm::Pool Member: /NONPROD/SA1W-PIVWEB-Q1:80
| Availability : available
| State : enabled
| Monitor : /NONPROD/MON-HTTP (pool monitor)
| Monitor Status : up
| Ltm::Pool Member: /NONPROD/SA1W-PIVWEB-Q2:80
| Availability : available
| State : enabled
| Monitor : /NONPROD/MON-HTTP (pool monitor)
| Monitor Status : up
