Forum Discussion
perryzou_317374
Altocumulus
AltocumulusVIP is not working
Great ones, Would you help take a look at my problem. Thanks.
I have an Openstack instance with F5 lbaasv2. It uses under cloud F5 VE instance with VXLAN overlay. But I won't be able reach vip of cr...
perryzou_317374Altocumulus
AltocumulusI tried to ping vip on F5 VE instance, and looks it works. But it failed when curl vip. Also listed route fyi.
I recreated another loadbalancer with vip of 192.168.0.16.
[root@host-192:Active:Standalone] Project_3b04b644e8a642f4acbc4275f2488d22 ping 192.168.0.16
PING 192.168.0.16 (192.168.0.16) 56(84) bytes of data.
64 bytes from 192.168.0.16: icmp_seq=1 ttl=255 time=0.418 ms
64 bytes from 192.168.0.16: icmp_seq=2 ttl=255 time=0.283 ms
[root@host-192:Active:Standalone] Project_3b04b644e8a642f4acbc4275f2488d22 curl 192.168.0.16 -v
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
* About to connect() to 192.168.0.16 port 80 (0)
* Trying 192.168.0.16... connected
* Connected to 192.168.0.16 (192.168.0.16) port 80 (0)
> GET / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 OpenSSL/1.0.1l zlib/1.2.3 libidn/0.6.5
> Host: 192.168.0.16
> Accept: */*
>
* Closing connection 0
* Failure when receiving data from the peer
curl: (56) Failure when receiving data from the peer
[root@host-192:Active:Standalone] tmp tmsh show /net route
------------------------------------------------------------------------------------
Net::Routes
Name Destination Type NextHop Origin
------------------------------------------------------------------------------------
fe80::/64 fe80::/64 interface tmm0 connected
ff02::/64 ff02::/64 interface tmm0 connected
ff02:ffd::/64 ff02:ffd::/64 interface /Common/lb-data connected
ff02:ffe::/64 ff02:ffe::/64 interface /Common/lb-ha connected
fe80::%vlan4093/64 fe80::%vlan4093/64 interface /Common/lb-data connected
fe80::%vlan4094/64 fe80::%vlan4094/64 interface /Common/lb-ha connected
fe80::/64 fe80::/64 interface /Common/socks-tunnel connected
ff02::/64 ff02::/64 interface /Common/tunnel-vxlan-1 connected
fe80::/64 fe80::/64 interface /Common/tunnel-vxlan-1 connected
fe80::/64 fe80::/64 interface /Common/http-tunnel connected
fe80::%vlan4095/64 fe80::%vlan4095/64 interface tmm_bp connected
ff02:fff::/64 ff02:fff::/64 interface tmm_bp connected
fe80::%1/64 fe80::%1/64 interface tmm0%1 connected
ff02::%1/64 ff02::%1/64 interface tmm0%1 connected
127.1.1.0/24 127.1.1.0/24 interface tmm0 connected
192.168.250.0/24 192.168.250.0/24 interface /Common/lb-data connected
192.168.253.0/24 192.168.253.0/24 interface /Common/lb-ha connected
127.20.0.0/16 127.20.0.0/16 interface tmm_bp connected
192.168.0.0/22 192.168.0.0/22 interface /Common/tunnel-vxlan-1 connected
127.1.1.0%1/24 127.1.1.0%1/24 interface tmm0%1 connected
internal-bm 10.153.36.64/27 gw 192.168.250.1 static
[root@host-192:Active:Standalone] tmp route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.153.36.64 192.168.250.1 255.255.255.224 UG 0 0 0 lb-data
127.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 tmm0
127.3.0.0 0.0.0.0 255.255.255.0 U 0 0 0 mgmt_bp
192.168.250.0 0.0.0.0 255.255.255.0 U 0 0 0 lb-data
192.168.253.0 0.0.0.0 255.255.255.0 U 0 0 0 lb-ha
192.168.254.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.252.0 U 0 0 0 tunnel-vxlan-1
127.7.0.0 127.1.1.254 255.255.0.0 UG 0 0 0 tmm0
0.0.0.0 192.168.254.1 0.0.0.0 UG 9 0 0 eth0
