cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5779
Views
0
Helpful
54
Replies

Can't ping vlans from Cisco 4500 as vtp client

Dan_17717
Level 1
Level 1

I have a Cisco 3560x as a vtp server and the 4500 and 2960s as vtp clients.  All the vlans have been propagated.  For some reason, I'm unable to ping certain vlans from the 4500.  All the 2960s are coming off the 4500.  The 2960s are able to ping vlans with the exception of 1 vlan which is 10.100.1.x. The 10.100.1.x switch is coming off the 3560x via virtual interface vlan 100 (10.100.1.1/24).  From the 3560x, I have no problem pinging all the 10.100.1.x devices.  However, from the 4500 and 2960s I'm unable to.  Is there something in the 4500 that I need to config for this to work?  Let me know if you need more info.

Thanks

54 Replies 54

Reza Sharifi
Hall of Fame
Hall of Fame

On the 4500 and 2960s do you have Managment IPs? if not create a mgmt ip on each device than try pinging from them

HTH
Sent from Cisco Technical Support iPhone App

Yes, I am able to ping each of the vlan 1 management IPs for Cisco 4500 and 2960s.  The management IPs for them are in same subnet.  I just can't ping the 10.100.1.x network from these devices.  However, from the 3560x (management ip same as 4500 and 2960s) I can ping the 10.100.1.x devices.

What device is doing the routing between vlans?

Sent from Cisco Technical Support iPhone App

The 3560x is doing the routing and acting as the vtp server.

So physically the 4500 and 2960s connect to 3560x right? Are the 4500 and 2960s configured as trunks? Also can you turn on IP routing on the 3560 x and test again
HTH

Sent from Cisco Technical Support iPhone App

The 2960s are connected directly to the 4500 and the 4500 is connected to the 3560x.  The 10.100.1.x switch (3Com) is connected to the 3560x on vlan 100 (10.100.1.1) which is not trunk.  The connections from the 2960s and 4500 are trunk and from the 4500 to the 3560x is trunked.

I tried to trunk the connection from the 10.100.1.2 /24 switch to the 3560x but that cause me not to be able to ping the other 10.100.1.x switches that are connected to the 10.100.1.2.

Would you be able to post the configs of the switches?

Attached is a sample layout of the network. 

Issue #1:  From the 4500, I can ping all the PCs set to vlan1.  However, I can not ping any ip phones set on vlan16 or devices set on vlan 10.  I can ping the virtual interface of vlan16 (10.40.16.1/22) and vlan 10 (10.40.10.1/22).  From the 2960s attached to the 4500, I can ping all the PCs and IP Phones and vlan 10 with no problem.  The 4500 can only ping the PCs that is attached to it and all the vlans virtual interface.

Issue #2: All the 2960s and the 4500 are not able to ping the vlan100 (10.100.1.x).  The only thing that it can ping is its virtual interface of vlan100 (10.100.1.1/24).

The 3560x has no problem pinging any of the devices and pcs.

If you do tracreoutes for these - do they die in a similar place?

From the 4500, doing the traceroute to vlan100 and to the IP Phone or vlan10 will not go anywhere.  From the 2960s, the traceroute to vlan100 will go to 10.40.1.2 and nothing after that, but no problems to the other vlans.

Does your 4500 have an ip default-gateway set?

What does your routing table look like for the vlan100 network?

Yes, the default route is set to 10.40.1.2 /22

Hello Dan,

By any chane did we  verify whether  the  SVI mac address for the vlan 10 , 100 in 3560 is getting reflected in 4500 and 2960.  I believe this schould be learned over the trunk port. and will be visible under the respective vlan mac address table. If not, try to create static mac entry and verify.

Regards

Partha

Correction, I am unable to ping from the 4500 to any virtual interfaces such as vlan16, vlan10, vlan100.  I tried adding ip route 10.100.1.0 255.255.255.0 10.40.1.2 but that did not work.  I can see all the vlans in 4500 since its set as vtp client.  The 2960s have no problem pinging all the virtual interface of the vlans.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco