- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Vlan Id
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
Forums
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
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
тАО01-18-2006 04:18 PM
тАО01-18-2006 04:18 PM
I it based on VlanId or something else TagId??
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2006 05:52 PM
тАО01-18-2006 05:52 PM
Re: Vlan Id
VLAN ID actually is the tag number.
Why do you need the same VLAN ID?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2006 07:51 PM
тАО01-18-2006 07:51 PM
Re: Vlan Id
Logically: This is not a good idea. This will a common misconfiguration/misunderstanding problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 07:47 AM
тАО01-19-2006 07:47 AM
Re: Vlan Id
If the two VLAN's need to communicate with eachother, just make sure that traffic between them is routed and not bridged.
If you care to state why you want to use the same VLAN ID twice, we may be able to supply you with an (better) alternative.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-27-2006 07:51 AM
тАО01-27-2006 07:51 AM
SolutionIn fact, this is the setup I work with.
Two sites, each has VLAN 1,2,3, & 8
VLAN 1 is for servers and network appliances.
VLAN 2 is for workstations.
VLAN 3 carries IP Telephony.
VLAN 8 acts as routing network between the two sites.
We could have simply extended the VLANs across the WAN link by passing tags, but using the aforementioned configuration keeps a lot of unnecessary traffic off our WAN link.
By using VLAN 8 strictly for routing, the delivery decision between VLANs in different sites is based on simple Layer-3 routing principles.
At the smaller site, we have two ProCurve 2650's that are joined in a 2Gb trunk.
Only traffic for VLANs 2 & 3 are allowed on the trunk, as all of our servers are located in the same area and (presently) are connected to the same switch. Whereas our workstations and phones are spread out over two floors. VLANs 2 & 3 are both tagged on the trunk, but only 3 is tagged on the "regular" ports workstations get connected to.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2006 05:20 PM
тАО01-29-2006 05:20 PM
Re: Vlan Id
It really helped me.