Forum Discussion
NimbostratusThe Virtual Server cann't be reachable, but the members in the pool and the pool itself is fine. why ?
There are two NICs on my notebook, NIC1 and NIC2, and i'm using VMWare WorkStation 8 to running the BIG-IP LTM VE 10.1, the relationship between the Physical NICs and vitual NICs in VMWare WorkStation is following.
NIC1(Microsoft Lookback Adapter)
IP Address : 192.168.135.21
Net Mask : 255.255.255.0
GW : 192.168.135.1
NIC2(Wireless LAN)
IP Address : 192.168.1.21
Net Mask : 255.255.255.0
GW : 192.168.1.1
vnet0 - bind to NIC1 -> f5 eth0:mgmt -> 192.168.135.245
vnet1 - bind to NIC2 -> internal -> 192.168.1.11 (self ip)
vnet2 - bind to NIC2 -> external -> active but not assign ip address to it
WebLogic Server Pool :
192.168.1.21:7003
192.168.1.22:7003
WebLogic Virtual Server :
192.168.1.210:80
The self ip 192.168.1.11 is pingable, and the status of virtual server, pool, nodes,is Available, but i cann't access the web page by using 192.168.1.210, and it's not be pingable, Why ?
2 Replies
Dongyun_Tian_90[root@bigip:Active] config route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.1.1.0 * 255.255.255.0 U 0 0 0 tmm0
192.168.135.0 * 255.255.255.0 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 internal
default 192.168.1.1 0.0.0.0 UG 0 0 0 internal
default 192.168.135.1 0.0.0.0 UG 9 0 0 eth0
[root@bigip:Active] config ifconfig|head -30
eth0 Link encap:Ethernet HWaddr 00:0C:29:02:98:F5
inet6 addr: fe80::20c:29ff:fe02:98f5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:79149 errors:0 dropped:0 overruns:0 frame:0
TX packets:103816 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11909878 (11.3 MiB) TX bytes:30176536 (28.7 MiB)
Interrupt:169 Base address:0x1080
eth0:mgmt Link encap:Ethernet HWaddr 00:0C:29:02:98:F5
inet addr:192.168.135.245 Bcast:192.168.135.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:169 Base address:0x1080
external Link encap:Ethernet HWaddr 00:0C:29:02:98:09
inet6 addr: fe80::20c:29ff:fe02:9809/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:198 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15070 (14.7 KiB) TX bytes:468 (468.0 b)
internal Link encap:Ethernet HWaddr 00:0C:29:02:98:FF
inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe02:98ff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16783 errors:0 dropped:0 overruns:0 frame:0
TX packets:22057 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1059138 (1.0 MiB) TX bytes:1376834 (1.3 MiB)I can access the web page normally with the following url also.
http://192.168.1.21
http://192.168.1.22
qe_102628Do you have SNAT enabled on the Virtual Server?
It looks like a local area network routing triangle issue - wherein the client contacts the virtual server, the connection is then sent to a pool member, and the pool member directly responds to the client instead of routing the response back through the LTM. If SNAT is enabled, the forwarded connection to the pool member will inherit an LTM configured IP address, and as such responses will route back through the BIG-IP before reaching the client.
