cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
584
Views
0
Helpful
8
Replies

DOT1q Trunking Problems between 4506 and 5513

paul.merritt
Level 1
Level 1

heres the deal

I have a Single mode GBIC set up going between a Cisco 4506 and our core 5513. The trunk shows up, both switches show up on CDP neighbor tables, they are in the same VTP domain and are allowing all our VLANS onto the trunk. Yet I can't ping or connect to the 4506 from anywhere other than our Managment VLAN (the .1) need some help.. don't hesitate to ask for additional information

8 Replies 8

lgijssel
Level 9
Level 9

Have you checked vtp configuration revision?

sh vtp stat

The revision number should be the same on both sides.

Is there a vtp password in use?

What happens if you manually add a vlan in the vlan database on the 4506? This should result in having layer2 connectivity in the particular vlan.

Regards,

Leo

we dont have a VTP password in use.. and the 4506 is set up in "client" mode with our 75 VLANS having come from the core via a VTP update... both switches have the same revision number

What happens if you put a pc on the 4500 is vlan x and another one in the same vlan on the 5500? Can they reach eachother?

If so, this means that you have layer2 connectivity which is what on should expect if trunks are OK.

Then the next question is how do you handle inter-vlan routing? RSM on the 5500?

Regards,

Leo

lgijssel
Level 9
Level 9

You are running dot1Q on the 5500 and not ISL?

yea we are actually running Dot1Q.. should we be running ISL?

If both sides are using the same protocol, all is well. I was just asking while the default on the 5500 is ISL. Did you also check on my first posting?

If your trunk is up and vlan1 is up, the other vlans may be (administratively) shut down. Alternatively, they may not exist on the 4500. This can be checked by the command: sh vlan

Leo

we fixed it... it ended up that we had to add a default route pointing the 4506 back to the Router interface for the managment VLAN.. I have never seen that before.. but I don't have a lot of experiece with L3 switches

So it wasn't a trunking problem after all.

What plain old IP routing can do!

Still glad to be of any help.

Leo