Do you have a document that will tell me how to do this? I'm kind of new at configuring vlans and I don't want to screw up anything already in place. How do I verify if the first switch is already trunked? Thanks a lot for your quick response.

The little ***** mean s c r e w up, not the other word. I just wanted to make that clear. Again thanks!! 

Just put this on both of the ports that will be connected

switchport mode trunk

switchport trunk encap dot1q

switchport trunk native vlan (followed by the number for your data vlan)

Also copy the configuration from your data vlan of the original switch to the new switch but give it a new and unused IP address.

Cool, I'll give it a try. Thanks a lot!

Fabio

Before you go and create the trunk and connect the switches up we need to know what the state of VTP is otherwise you could overwrite your existing vlans.

On the existing switch can you post the output of "sh vtp status".

Also the commands supplied to configure the trunk are fine but there is no guarantee that your native vlan is the data vlan although if it is vlan 1 there is a good chance it is.

Can you post output of "sh vlan" from the existing switch and clarify which is the data vlan and which is the voice vlan.

Jon

No problem, I will get the output requested and let you know. I'm new at this network, so I'm just learning as I go. Thanks.

Here is the output after running the sh vtp status:

Tyco-MDF>sh vtp status

VTP Version                     : running VTP1 (VTP2 capable)

Configuration Revision          : 13

Maximum VLANs supported locally : 1005

Number of existing VLANs        : 10

VTP Operating Mode              : Client

VTP Domain Name                 : SCPlant

VTP Pruning Mode                : Disabled

VTP V2 Mode                     : Disabled

VTP Traps Generation            : Disabled

MD5 digest                      : 0x02 0xBD 0xFC 0xFF 0x22 0x64 0x2F 0x2F

Configuration last modified by 10.4.2.254 at 12-31-09 14:55:15

Tyco-MDF>

__________________

I have 10 VLANs, now the question is how do I know what's voice and what's data? Is there a command to tell that? Thanks.

fabman696 wrote:
Here is the output after running the sh vtp status:
Tyco-MDF>sh vtp status
VTP Version                     : running VTP1 (VTP2 capable)
Configuration Revision          : 13
Maximum VLANs supported locally : 1005
Number of existing VLANs        : 10
VTP Operating Mode              : Client
VTP Domain Name                 : SCPlant
VTP Pruning Mode                : Disabled
VTP V2 Mode                     : Disabled
VTP Traps Generation            : Disabled
MD5 digest                      : 0x02 0xBD 0xFC 0xFF 0x22 0x64 0x2F 0x2F
Configuration last modified by 10.4.2.254 at 12-31-09 14:55:15
Tyco-MDF>
__________________
I have 10 VLANs, now the question is how do I know what's voice and what's data? Is there a command to tell that? Thanks.

Fabio

On the above switch you should make it a VTP server ie.

Tyco-MDF(config)# vtp mode server

this will not affect your existing setup.

On your new switch, before you connect it to the other switch log in and do the following -

1) newswitch(config)# vtp mode transparent

2) newswitch(config)# vtp mode client

then do a "sh vtp status" on the new switch and check the "Configuration Revision" number = 0.

Then connect the new switch to the existing switch with a trunk link and your new switch should automatically be updated with the vlans from your existing switch.

As for which vlan is which. If you know the IP subnet of the data and voice vlan then on the existing switch -

Tyco-MDF# sh ip int brief

and the output will list the IP address of each L3 vlan interface. You should be able to match it up from there. If in doubt post the output.

Jon

First of all thanks a lot for your help guys. I'm just getting back to this project now after putting out a few other fires. After some more troubleshooting, I need a little more help.

This is the original configuration of the switch I'm trying to add (SWITCH 1):

scp-3560-idf2-3#sh vtp status

VTP Version                     : 2

Configuration Revision          : 13

Maximum VLANs supported locally : 1005

Number of existing VLANs        : 10

VTP Operating Mode              : Client

VTP Domain Name                 : SCPlant

VTP Pruning Mode                : Disabled

VTP V2 Mode                     : Disabled

VTP Traps Generation            : Disabled

MD5 digest                      : 0x02 0xBD 0xFC 0xFF 0x22 0x64 0x2F 0x2F

Configuration last modified by 10.4.2.254 at 12-31-09 14:55:15

_____________________________________________________

This is the vtp status of the 3560 already in place (SWITCH 2):

Tyco-MDF>sh vtp status

VTP Version                     : running VTP1 (VTP2 capable)

Configuration Revision          : 13

Maximum VLANs supported locally : 1005

Number of existing VLANs        : 10

VTP Operating Mode              : Client

VTP Domain Name                 : SCPlant

VTP Pruning Mode                : Disabled

VTP V2 Mode                     : Disabled

VTP Traps Generation            : Disabled

MD5 digest                      : 0x02 0xBD 0xFC 0xFF 0x22 0x64 0x2F 0x2F

Configuration last modified by 10.4.2.254 at 12-31-09 14:55:15

_________

Issues:

1.     I need to configure SWITCH1 as a slave of SWITCH2, not sure how to accomplish that via SFP’s.

2.     I don’t know if by making SWITCH2 the master/server vtp will mess up my other switches

3.     I need both switches to be able to see all my VLAN’s.

4.     When I connect my VoIP Cisco phone to SWITCH1 works just fine, but it does not on SWITCH2

I think I'm almost there, but not quite yet. Your help is greatly appreciated.

Personally I am not one to favor using VTP in any network. The potential exisits for someone to plug a switch into your network and wipe your entire vlan configuration accross your enterprise if its not secured correctly. To answer your question though,

It looks like you have both switches in the right VTP domain  To keep things consistant accross your switches I would change the VTP version on switch 2 to version 2. This can be done by entering the config command VTP version 2

If you are still not seeing Vlans from Switch 1 on switch 2 then please send the show run interface command of the two interfaces connecting your switches.

Adrien,

Thanks a lot for your response.

When I entered vtp vertsion 2 this is what I get:

1. SWITCH2# vtp version 2

Cannot modify version in VTP client mode

I think I need to put this one in transparent mode to be able to modify, correct?

2. I just verified that I have three more switches set to server mode, so setting this one to client mode will be just fine and I'm hoping that then SWITCH1 will learn the config, is that a correct assumption?

Here is the running config:

Tyco-MDF#show running-config

Building configuration...

Current configuration : 3854 bytes

!

version 12.2

no service pad

service timestamps debug datetime msec localtime show-timezone

service timestamps log datetime msec localtime show-timezone

service password-encryption

!

hostname Tyco-MDF

!

boot-start-marker

boot-end-marker

!

enable secret 5 $#1$VIg6$F.AnH.WPWqlKHjej.tSEc.

!

no aaa new-model

clock timezone EST -5

clock summer-time EDT recurring

system mtu routing 1500

ip subnet-zero

!

!

spanning-tree mode pvst

spanning-tree etherchannel guard misconfig

spanning-tree extend system-id

!

vlan internal allocation policy ascending

!

!

!

interface FastEthernet0/1

description Connection to 2811 f0/0

switchport access vlan 201

switchport mode access

!

interface FastEthernet0/2

description Connection to Bridge

switchport trunk encapsulation dot1q

switchport trunk native vlan 20

switchport mode trunk

!

interface FastEthernet0/3

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/4

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/5

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/6

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/7

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/8

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/9

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/10

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/11

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/12

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/13

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/14

description Connection to LWAPP AP

switchport access vlan 20

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/15

description Connection to LWAPP AP

switchport access vlan 20

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/16

description Connection to LWAPP AP

switchport access vlan 202

switchport mode access

switchport voice vlan 300

spanning-tree portfast

!

interface FastEthernet0/17

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/18

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/19

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/20

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/21

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/22

switchport access vlan 202

switchport mode access

switchport voice vlan 300

spanning-tree portfast

!

interface FastEthernet0/23

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/24

switchport access vlan 201

switchport mode access

spanning-tree portfast

!

interface GigabitEthernet0/1

description Connection to IDF Upstairs port G0/1

switchport trunk encapsulation dot1q

switchport mode trunk

!

interface GigabitEthernet0/2

!

interface Vlan1

no ip address

no ip route-cache

shutdown

!

interface Vlan200

description Management

ip address 10.4.2.218 255.255.255.0

!

ip default-gateway 10.4.2.254

ip classless

ip http server

!

!

control-plane

!

!

line con 0

password 7 023503544A545B

login

line vty 0 4

password 7 107D0E16444546

login

line vty 5 15

password 7 107D0E16444546

login

!

end

Tyco-MDF#

Thanks a lot for your assistance.

Yes I belive if you change your VTP mode to Transparent and then change the the VTP version, then change it back to client. I also make sure if you are using a VTP password that this is set.

As long as your uplink is configured correctly you should start propagating Vlans.