Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

VTP v2 vs v3 Questions

I am going through the network and bringing it into compliance with Cisco SAFE and Best Practices.  I have a few questions that I hope one or more of you can help me with -

1) I am going to move to VTP v2 at a minimum and am considering VTP v3.  Anyone used VTP v3 yet ?

2) In keeping with best practices, I am going to move to transparent mode.  Should I still set a vtp password for general principles if for no other reason ?

3) I am looking at the private vlan feature of VTP v3 because of a request that I have received for a "sandbox" configuration.  I am also looking at this to keep our "Guest" network traffic even more isolated. My question is how to setup a port in the vlan as a "Gatewa" to the Internet.  I have been looking into this but havent found a good document.

Thanks,

Ron

1 REPLY

VTP v2 vs v3 Questions

1) I have not, so can offer no useful advice here.

2) I have typically set a "dummy" domain and password just because, but that may be overkill and pointless configuration.  Open to other ideas on this question.

Not to get basic on you, but remember that your current VLAN databases/configuration is tied to your VTP domain, so when you start configuring from server/client to transparent mode you're going to start losing VLAN configs in devices.  Depending on the size of your network and criticality, this may not be a trivial issue.

3) Private VLANs are a method of keeping ports in the same VLAN, but restricting traffic between those ports.  An example would be a set of servers (say mail, DNS, web) that are on the same subnet, in the same VLAN, but you ONLY want those servers to have access to the Internet, and NOT each other.  The servers could be on the same private VLAN with an Internet port set as the promiscuous port.  The servers could talk to the promiscuous port, but not each other.  I would recommend the Guest VLAN as its own vlan (no devices other than guest devices), thus negating the need for the private VLAN.  But to answer your question, the "gateway" port would be the promiscuous port.  You'll find a plethora of information on the Cisco site, but here is one starting point:

http://www.cisco.com/en/US/tech/tk389/tk814/technologies_configuration_example09186a008017acad.shtml

Good luck!

Ed

977
Views
0
Helpful
1
Replies
CreatePlease to create content