cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5420
Views
0
Helpful
7
Replies

VLAN not showing up on adjacent switch

smiths@prpa.org
Level 1
Level 1

I've got a 4500 series switch that has a number of VLANs on it, VTP server enabled on all switches in my environment. I've got a 2960 series connected to this 4500 series via a fiber link and that link is configured as a trunk port dot1q, etc. I need to extend vlan 192 over from the 4500 to the 2960. By default shouldn't I see 192 on the 2960 switch?

I'm not pruning VLANs on either switch.

Any input would be appreciated.

~Steve

7 Replies 7

darren.g
Level 5
Level 5

smiths@prpa.org wrote:

I've got a 4500 series switch that has a number of VLANs on it, VTP server enabled on all switches in my environment. I've got a 2960 series connected to this 4500 series via a fiber link and that link is configured as a trunk port dot1q, etc. I need to extend vlan 192 over from the 4500 to the 2960. By default shouldn't I see 192 on the 2960 switch?

I'm not pruning VLANs on either switch.

Any input would be appreciated.

~Steve

Have you confirmed all your switches are in the same VTP domain? VTP domain names are case sensitive, as are VTP passwords.

Also, why do you have *every* switch in VTP server mode? You should have one (or maybe two) "server" switches and everything else in VTP client mode.

Can you post the output of "show vtp status" from the 4500 and 2960 switches?

Cheers.

2960G-01#show vtp status
VTP Version                     : 2
Configuration Revision          : 3
Maximum VLANs supported locally : 255
Number of existing VLANs        : 8
VTP Operating Mode              : Server
VTP Domain Name                 :
VTP Pruning Mode                : Disabled
VTP V2 Mode                     : Disabled
VTP Traps Generation            : Disabled
MD5 digest                      : 0xFD 0x7A 0xC7 0x16 0x99 0xE1 0x4D 0xAE
Configuration last modified by 10.10.1.22 at 12-12-94 15:01:33
Local updater ID is 10.10.1.22 on interface Vl10 (lowest numbered VLAN interface found)

HQ4510#sh vtp status
VTP Version                     : 2
Configuration Revision          : 17
Maximum VLANs supported locally : 1005
Number of existing VLANs        : 11
VTP Operating Mode              : Client
VTP Domain Name                 : prpa
VTP Pruning Mode                : Disabled
VTP V2 Mode                     : Disabled
VTP Traps Generation            : Disabled
MD5 digest                      : 0xB8 0x87 0xFA 0x14 0x55 0x68 0x40 0x1A

Ah the domain name isn't there on the 2960G...right!?!

~Steve

smiths@prpa.org wrote:

2960G-01#show vtp status
VTP Version                     : 2
Configuration Revision          : 3
Maximum VLANs supported locally : 255
Number of existing VLANs        : 8
VTP Operating Mode              : Server
VTP Domain Name                 :
VTP Pruning Mode                : Disabled
VTP V2 Mode                     : Disabled
VTP Traps Generation            : Disabled
MD5 digest                      : 0xFD 0x7A 0xC7 0x16 0x99 0xE1 0x4D 0xAE
Configuration last modified by 10.10.1.22 at 12-12-94 15:01:33
Local updater ID is 10.10.1.22 on interface Vl10 (lowest numbered VLAN interface found)

HQ4510#sh vtp status
VTP Version                     : 2
Configuration Revision          : 17
Maximum VLANs supported locally : 1005
Number of existing VLANs        : 11
VTP Operating Mode              : Client
VTP Domain Name                 : prpa
VTP Pruning Mode                : Disabled
VTP V2 Mode                     : Disabled
VTP Traps Generation            : Disabled
MD5 digest                      : 0xB8 0x87 0xFA 0x14 0x55 0x68 0x40 0x1A

Ah the domain name isn't there on the 2960G...right!?!

~Steve

You've got two different VTP domain names - the 2960 has no configured VTP domain name, and the 4500 has the vtp domain name configured as "prpa". And your 4500 is configured in "client" mode, which means it's getting its VLAN information from somewhere else.

Try issuing the following commands on the 2960

vtp mode client

vtp domain prpa

WARNING : This will OVERWRITE the VLAN database on the 2960 switch - so if you have VLAN's on the 2960 which don't exist in your VTP environment (on your VTP server), DON'T DO IT!!!

If all the VLAN's on the 2960 already exist on the 4500 (and, by inference, in the VTP environment), then the extras will be added to the 2960.

I can't stress enough how badly you can stuff the 2960 config if you do this, so check your VLAN's, then check them again, and just to be sure ask someone else to check them for you. Use the "show vlan" command on both switches and make sure.

You should try to find out which switch is running as the VTP server in the "prpa" VTP domain before you make any changes - especially since the 2960 is in "server" mode, and will attempt to over-write the VLAN database if you add it tot he existing "prpa" VTP domain.

Cheers.


smiths@prpa.org
Level 1
Level 1

Folks,

I've cleared up the client server issues on the adjacent switches and can confirm that vtp is enabled, but the outlining switch still isn't getting the new VLANs propigating to it from the vtp server switch.

Here is the sequence:

[Switch 1/VTP Server] ---- [Switch 2/VTP Client] ----[Switch 3/VTP Client]---[Switch 4/VTP Client]

VLANs added to switch 1 appear in switch 2, but not 3 or 4.

Suggestions on what to try next?

~Steve

Did you check the port configuration between 2 and 3? Did you check the spanning-tree settings?

Eugen

Yes, between 2 and 3...

VTP status

VTP Version 2

VTP mode is client

Trunk is active and not pruning.

smiths@prpa.org
Level 1
Level 1

Thanks everyone...I traced it down and discovered that the link between switch 2 and 3 is not a trunk port. Just an access port. I'll make the changes after hours so I don't kick anyone off the network.

Regards,

~Steve