Just for fun, here's a puzzle to figure out.
SVR----L3 switchA----FW----L3 switch B----L3 switch C----L2 switchD---client.
SVR address is 200.200.200.200/24
L3 switch has interfaces into numerous 10.10.X.X/24 networks.
L3 switch B and C has numerous interfaces in 10.20.x.x/24 networks.
client IP is 10.20.20.20, L3 switch C is the default gateway for this network.
SVR trace to client stops a L3 switch C
L3 switchA trace to client GOOD
L3 switchB trace to client GOOD
SVR trace to any switch interface GOOD
Routing protocol is EIGRP, the firewall separates the two ASs. Default route of the firewall interfaces is respectively injected into each AS.
Any device can ping/trace to client except for nodes or interfaces in the 200.200.200.0/24 net.
What could the problem be? And more importantly, why. The firewall is not performing NAT/PAT of any kind and can be considered a L3 device.
You have been given all the information you need to know.
good luck, and have fun.
SVR----L3 switchA----FW----L3 switch B----L3 switch C----L2 switchD---client.
SVR address is 200.200.200.200/24
L3 switch has interfaces into numerous 10.10.X.X/24 networks.
L3 switch B and C has numerous interfaces in 10.20.x.x/24 networks.
client IP is 10.20.20.20, L3 switch C is the default gateway for this network.
SVR trace to client stops a L3 switch C
L3 switchA trace to client GOOD
L3 switchB trace to client GOOD
SVR trace to any switch interface GOOD
Routing protocol is EIGRP, the firewall separates the two ASs. Default route of the firewall interfaces is respectively injected into each AS.
Any device can ping/trace to client except for nodes or interfaces in the 200.200.200.0/24 net.
What could the problem be? And more importantly, why. The firewall is not performing NAT/PAT of any kind and can be considered a L3 device.
You have been given all the information you need to know.
good luck, and have fun.