07-05-2006 08:21 AM - edited 03-03-2019 03:55 AM
We have a 6513 with more than 10 IP VLAN interface. We found out the routing between those Vlans doesnt work after we upgrade IOS to Version 12.2(17d)SXB11a. Anyone knows have same experience? Thanks.
07-05-2006 08:53 AM
When you do show ip route, do the VLAN interfaces still show up in the table?
How about "ip routing" and the vlan interfaces...are they still in the running-config?
07-05-2006 09:44 AM
I am running 2- 6513s with 10 IP VLAN interfaces using ver 12.2(18)SXD6 with no problems. I assume it was working prior to the upgrade?
07-05-2006 09:48 AM
How are you verifying the problem? how was the issue troubleshot? Are the interface vlan up/up (show ip int brief)? Are you able to ping any of the interface vlan from the host that is on that vlan, for example host in vlan 10, can that host ping interface vlan 10? Can you ping that host from the switch? Are the interfaces showing up as directly connected (show ip route)?
07-05-2006 11:58 AM
It was working before the upgrade. We were using SXD5. The subnet in the IP Vlan interface can talk to the subnet in the IP port interface. But it cant talk to the subnet at another IP Vlan interface. I guess this is a bug for the IOS. But I couldnt find it from Cisco. Thanks,
07-05-2006 01:47 PM
got it it was working before. can you verify the following anyway?
How are you verifying the problem? how was the issue troubleshot? Are the interface vlan up/up (show ip int brief)? Are you able to ping any of the interface vlan from the host that is on that vlan, for example host in vlan 10, can that host ping interface vlan 10? Can you ping that host from the switch? Are the interfaces showing up as directly connected (show ip route)?
07-05-2006 02:00 PM
The host at vlan 10 can ping interface vlan 10 which is in the 6513. But it cant ping the host in vlan 20. I can ping both hosts in vlan 10 and vlan 20 from the switch. Thanks.
07-05-2006 04:41 PM
thanks, have you doen an extended ping from the 6513? ping host in either vlan,and source the ip address from another vlan, for example ping host in vlan 20 and use source ip address of vlan 10. This would show us if the switch is actually not switching the packet. Make sure that nothing had changed from the hosts configurations or the switch configuration after the upgrade. For example, the host default gateway might be .3 when our interface vlan 10 might be .2 now. Things that are obvious might be overlooked.
07-07-2006 07:07 AM
Actually I just find out the VLan 10 in blade one can't ping Vlan 20 in blade two. But it can ping Vlan 30 in Blade one. Guess the problem happen only between two Gigabit module.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide