- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Cascading Multiple Procurve's ?
Switches, Hubs, and Modems
1753502
Members
4705
Online
108794
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
04-23-2008 07:29 AM
04-23-2008 07:29 AM
Re: Cascading Multiple Procurve's ?
Hi Karl,
Yes I'm using the term "uplink" generically - you could call it an inter-switch link too I guess. There is no dedicated function for this.
When you assign an IP address to a VLAN you are creating a virtual router. For management purposes (over network) each switch requires an IP address (in your management VLAN, which you may or may not have explicitly defined).
Think of the IP addresses on your mothership switch as routers downstream from your "real" router. A VLAN is a totally isolated network until you connect it to another network with a router (just like a real LAN).
The concept of tagging and untagging ports is to extend the logical boundary of the VLANs across switches (and other devices that understand 802.1Q tagging).
When you untag a port, that port is "physically" in the assigned VLAN. When you tag a port with a particular VLAN, you are encapsulating that traffic on top of the untagged traffic that is being carried by that port.
I've found it's helped me to wrap my head around the concept by understanding what how the tagging process works:
http://en.wikipedia.org/wiki/IEEE_802.1Q
Hope this clears any confusion.
Cheers,
Joel
Yes I'm using the term "uplink" generically - you could call it an inter-switch link too I guess. There is no dedicated function for this.
When you assign an IP address to a VLAN you are creating a virtual router. For management purposes (over network) each switch requires an IP address (in your management VLAN, which you may or may not have explicitly defined).
Think of the IP addresses on your mothership switch as routers downstream from your "real" router. A VLAN is a totally isolated network until you connect it to another network with a router (just like a real LAN).
The concept of tagging and untagging ports is to extend the logical boundary of the VLANs across switches (and other devices that understand 802.1Q tagging).
When you untag a port, that port is "physically" in the assigned VLAN. When you tag a port with a particular VLAN, you are encapsulating that traffic on top of the untagged traffic that is being carried by that port.
I've found it's helped me to wrap my head around the concept by understanding what how the tagging process works:
http://en.wikipedia.org/wiki/IEEE_802.1Q
Hope this clears any confusion.
Cheers,
Joel
- « Previous
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP