Forum Discussion
NimbostratusNetwork question
Hi all, as I'm a system person and trying to understand more on the network side. As below I have setup the Mgmt, internal and external IP.
From my understanding, Public IP will come to the firewall and on the firewall it should have a rule to reach the Virtual Server IP. From the Virtual IP, it will follow the Pool Load Balancer setting which will point to the internal Application server.
If there's a need to troubleshoot, will the internal and external IP play any part ? My thinking was that the internal IP is communicating to the internal application servers.
eth0
Link encap:Ethernet
HWaddr xx:xx:xx:xx:xx:xx inet addr:10.1.9.15
Bcast:10.1.9.255 Mask:255.255.255.0
eth1
Link encap:Ethernet
HWaddr xx:xx:xx:xx:xx:xx inet6 addr: fe80::250:56ff:fe84:f50/64
eth2
Link encap:Ethernet
HWaddr xx:xx:xx:xx:xx:xx inet6 addr: fe80::250:56ff:fe84:69d1/64
external
Link encap:Ethernet
HWaddr xx:xx:xx:xx:xx:xx inet addr:10.1.7.29
Bcast:10.1.7.255 Mask:255.255.255.0
internal
Link encap:Ethernet
HWaddr xx:xx:xx:xx:xx:xx inet addr:10.1.8.29
Bcast:10.1.8.255
Mask:255.255.255.0
4 Replies
Vitaliy_SavransNacreous
Of course, the first thing that comes into my mind is that the internal and external IP will play part in routing troubleshoot (connectivity troubleshoot).
IheartF5_45022If there's a need to troubleshoot (like running tcpdump), the client side will be ==> < virtual ip >
While serverside will be
==>
Or if using "SNAT automap"
==>
- IheartF5_45022Hmm that comment didn't come out as expected :-) the client side will be ==> < virtual ip > While serverside will be ==> or (if using SNAT automap) ==> Or if using "SNAT automap" ==>
IainThomson85_1Cumulonimbus
It depends on the complexity of whats in place.
When I'm diagnosing faults on live F5 devices. We often filter on Destination Host, or Source Host. With a combination of ports.
However in some circumstances, we capture on another device on the Snat'd address.
