|
Home > Archive > CCNP > January 2001 > Cat6506 trunked to cat 3548 VLAN config
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Cat6506 trunked to cat 3548 VLAN config
|
|
|
| all,
Has anyone worked with this combination. I have successfully configured etherchannel/trunk. I have setup vtp domain/server on the cat6506 and client mode for the 3548. I am not getting updates to the client switch and therefore the cat3548 does not know about vlans configured on the cat6506. I can only move around using the default vlan 1 between both switches. Does any one have any suggestions..
suspect: on the cat6506/cmd-sh trunk detail, shows the peer port mode,encap and status as unknown.
thanks all, | |
|
| check the native vlan for the trunk and make sure they are both the same. if they are not, you may have to disable the trunk making it a regular port then put it in the same vlan then make it a trunk again. also, check your sh spantree stat blockedports to see if spanning tree is blocking certain ports on the trunk. make sure the 3000 series is for sure in client and not transparent. can't quite say more without seeing your configs | |
|
| Not only verify trunking, but make sure your VTP domain names match on both switches. Also verify the VTP version on both: if one is using Version 2 and the other version 1, you will have compatibility issues.
| |
|
| thanks for your input,
I have verified all your suggestions, everything is consistent on vtp server and client. I found this important piece of info on cisco website:
" Important Note: Currently, Catalyst 2900XL/3500XL switches do not support Dynamic Trunking Protocol (DTP). Thus, it is recommended that you use the nonegotiate option the other side of the trunk link as configured above on the Catalyst 4000, 5000, and 6000 switches. This way, the XL switch port will not receive DTP frames that are unfamiliar to it." http://www.cisco.com/warp/customer/473/43.html
This is the reason, trunk needs to be setup manually. (transparent mode on both sides)
Please advise if there is a way around this.
thanks, | |
|
| I don't think you should find a work around for it. I think you should configure the trunk links manually. This is not something I care to leave to chance. I like to explicitly set what vlans are allowed on a trunk link just as I explicitly set port speed and duplexing on uplinks and such.
MadChef |
|
|
|
|