- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Understanding VLAN Trunking Protocol and VirtualCo...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2010 09:25 AM
05-03-2010 09:25 AM
Understanding VLAN Trunking Protocol and VirtualConnect
Scott needed some clarification around VLAN Trunking Protocol(VTP):
*******************************************************************************************************************
I understand we don’t support Cisco’s proprietary VTP and I have to admit I don’t fully understand it and it a bit over my head but a customer has asked;
If a VTP domain is presented to a VC uplink port (a number of Trunked VLAN’s) can the VC see the VLANS if individually added to the port profile in VC?
When VTP domains have similar VLAN’s, i.e VTP #1 has VLAN1 and VTD #2 has a VLAN1 can these VLANS be isolated between servers, or assigned to different servers? Or is this question completely irrelevant?
Maybe I need to ask how somebody using VTP domains connects to VC?
Thanks in advance and sorry if this is a dumb question.
****************************************************************************************************************
But to Paul there are no dumb questions:
************************************************************************************************************
So, from Cisco defining VTP
http://www.cisco.com/en/US/tech/tk389/tk689/technologies_tech_note09186a0080094c52.shtml
VLAN Trunk Protocol (VTP) reduces administration in a switched network. When you configure a new VLAN on one VTP server, the VLAN is distributed through all switches in the domain. This reduces the need to configure the same VLAN everywhere. VTP is a Cisco-proprietary protocol that is available on most of the Cisco Catalyst series products.
So, VTP does nothing but propogate the VLAN config throughout the Cisco environment. The fact that a VLAN was created on a switch via VTP doesn’t change how the VLAN works, nothing special about it.
Within a layer 2 network ( a collision domain, everything on the same side of a router), VLANx =VLANx=VLANx.
***********************************************************************************************************************
Hopes this helps. Do you use VTP from Cisco?