2 Core switch 6513 linked with TenGig trunk ports, with same vlans on both (can ping accross on same vlan no problem).
ok, I setup a vlan 172 on both switchs that already has a bunch of vlans.
I have 2 hosts on vlan 172 with addresses of 172.16.0.3 and .4
The gateway is .1 which is the vlan interface of SW1 and SW2 with HSRP.
Both hosts can ping each other and the gateway.
I also have a DNS server residing on vlan 104 with IP 10.98.4.22. It's gateway is also .1 but the gateway is actualy a firewall.
The firewall does not know about VLAN 172
The hosts on VLAN 172 cannot ping any other hosts on any vlans.
I thought that having the switch do vlan routing that they would know that 10.98.4.0 is physicaly connected as it shows up in the routing table of the switches...
sh ip route on the SW1 and SW2 shows:
10.0.0.0/23 is subnetted, 5 subnets
C 10.98.8.0 is directly connected, Vlan108
C 10.98.0.0 is directly connected, Vlan1
C 10.98.2.0 is directly connected, Vlan102
C 10.98.4.0 is directly connected, Vlan104
C 10.98.6.0 is directly connected, Vlan106
I'm kinda confused a bit... I'm using Ethereal and I'm trying to see if I find the issue.
My intuition says that the ping packets are getting to 10.98.4.20 although the response is getting lost comming back to 172.16.0.3 because the 10.98.4.20 host is sending it to the firewall which has no idea where 172 is or how to get there... But I need to see this in ethereal, just not sure how to do this.