Proper Order of Configuration?

[vegas5882010]

I need to setup VLANs, VTP, and EtherChannels. I have 2 3560G-24 port switches. Is there a particular order that I need to configure these features? For example, should I setup the EtherChannel first (which will be used as a trunk between the two switches) and then setup the VTP domain and then the VLAN or does it really matter what I setup first? Based on what I am reading, (having not done this is a while), if I establish the EtherChannel on switch 1, the config should automatically transfer to switch 2 because the ports will autonegotiate and recognize that an EtherChannel has been established. Is this correct?

[Jon Marshall]

vegas5882010 wrote:
this is switch two.
What should the mode be? I chose dynamic desirable, but is that correct?

The mode is up to you. Dynamic desirable runs DTP which negotiates at either end to become a trunk link. As mentioned previously you can simply type - "switchport mode trunk" which means you permanently turn on the trunk. You would also then add  "switchport nonegotiate" to turn off DTP.

I personally usually configure them as on but it's a matter of preference really.

Jon

[vegas5882010]

OK, understood. This is all good stuff...thanks for the help. I switched it back to switchport mode trunk and also switchport nonegotiate to handle the DTP issue. Still showing the mismatch though.

[Federico Coto Fajardo]

Issue a ''sh vtp password'' on both switches.

If you don't get the same output, that's what you need to correct.

Federico.

[vegas5882010]

I issued a show vtp password on both switches and both are not set. Yet, I still have an MD5 checksum error.

[Federico Coto Fajardo]

James,

Make sure that both switches (VTP server and VTP client) are configured with the same VTP password and domain.

The commands:

vtp password

vtp domain

vtp mode

Also, make sure that the link between both switches is a trunk and that it shows up/up when doing ''sh interface x/x''

Federico.

[vegas5882010]

So now I have a misconfigured switch....Cannot get into it anymore. None of my passwords are working. How do I reset this and reload

the IOS?

As I said, it's been a long while since I have configured this kind of stuff.

[Mohamed Sobair]

Here is password recovery procedure:

http://www.cisco.com/en/US/products/hw/switches/ps628/products_password_recovery09186a0080094184.shtml

HTH

Mohamed

[vegas5882010]

I figured out a way around it. I just restarted the switch and it brought me back into the initial configuration dialog. I

decided to completely wipe out both switches and start from scratch. I will not put a password on the vtp domain and let's see if I can get this trunk to work.

[vegas5882010]

When I setup the vtp domain, do I need to configure it on both switches or just the primary switch and then it will propagate over the trunk? I guess the second switch will need to be manually configured for vtp client.

[Federico Coto Fajardo]

If you configure one switch as the VTP server with a domain name, the domain name will propagate across the trunks to other switches (which they don't have a domain name yet configured for VTP).

However, it's better to manually configure the domain name manually on every switch.

Also, you need to log into the VTP client switch to configure it as VTP client (and set the domain).

To avoid this domain propagation, you can create a VTP password.

Federico.

[vegas5882010]

I established the vtp domain on switch 1 and then I went to switch 2 and it showed the vtp domain correctly. So that means that it propagates automatically. MD5 checksum was fine. I put no passwords on the vtp domain. I then changed switch 2 to vtp client and then it showed the MD5 error again.

[vegas5882010]

MD5 checksum error disappeared. ? Strange.

Anyway, everything seems to be ok for now. Will proceed with creating the VLANs we need and assigning the necessary ports.

Is there any reason to use vtp version 3? Using 1 now.

What about vtp pruning?

Your help has been most appreciated!

[jalex]

this is an old thread at this point, but I came across it, so others may have as well.

See: http://www.networknoob.net/2012/11/ccnp-vtp-and-etherchannel/
Possibly the client got out of sync with the server? Creating and deleting a vlan might have resolved the issue, by forcing a VTP update.