- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- 4108gl: Hard VLAN routing question.
Switches, Hubs, and Modems
1745907
Members
4187
Online
108723
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
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-15-2005 06:25 AM
04-15-2005 06:25 AM
4108gl: Hard VLAN routing question.
The question isn't all that hard, really, but understanding my current config may be. Then again, this may be child's play for someone who lives this stuff every day. Here's hoping.
We have 2 4108gl switches, stacked. Call them switch A and switch B (we do). They are stacked together via the Gigabit stacking kit, using port A3 on each switch. A is the stack commander.
We have VLANs set up based on Class C network membership.
The VLAN setup on each switch is as follows:
Switch ID Name Ports
A 1 OFFICE all ports untagged; A3 is a tagged member.
A 15 FLDSRV no ports are members
B 1 OFFICE A3 tagged; about 50 other untagged ports
B 2 CAD A3 tagged; about 40 other untagged ports
B 3 DMZ a few untagged ports
B 4 XYZ a few untagged ports
Switch B is configured to do VLAN routing between the OFFICE and CAD VLANs. The DMZ and XYZ VLANs are unrouted.
I want to extend VLAN B-2 to include ports on switch A. Is it as simple as creating VLAN 2, named CAD, on the A switch, making port A3 a tagged member of that VLAN, and everything should work since the VLAN ID's will match? Or will I need to so comething more complicated?
Eventually I'm going to bring in a connection from another switch into sswitch A using the already-defined FLDSRV VLAN and route it, and add another routed VLAN to the B-switch as well.
We have 2 4108gl switches, stacked. Call them switch A and switch B (we do). They are stacked together via the Gigabit stacking kit, using port A3 on each switch. A is the stack commander.
We have VLANs set up based on Class C network membership.
The VLAN setup on each switch is as follows:
Switch ID Name Ports
A 1 OFFICE all ports untagged; A3 is a tagged member.
A 15 FLDSRV no ports are members
B 1 OFFICE A3 tagged; about 50 other untagged ports
B 2 CAD A3 tagged; about 40 other untagged ports
B 3 DMZ a few untagged ports
B 4 XYZ a few untagged ports
Switch B is configured to do VLAN routing between the OFFICE and CAD VLANs. The DMZ and XYZ VLANs are unrouted.
I want to extend VLAN B-2 to include ports on switch A. Is it as simple as creating VLAN 2, named CAD, on the A switch, making port A3 a tagged member of that VLAN, and everything should work since the VLAN ID's will match? Or will I need to so comething more complicated?
Eventually I'm going to bring in a connection from another switch into sswitch A using the already-defined FLDSRV VLAN and route it, and add another routed VLAN to the B-switch as well.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2005 05:55 PM
04-17-2005 05:55 PM
Re: 4108gl: Hard VLAN routing question.
You are right that it is as simple as you think ;)
You allready did the same for VLAN 1. Having ports on both switches and let switch B do the routing. For VLAN 2 the setup is the same.
Tag port A3 on switch A for VLAN 2, and untag ports on switch A for VLAN 2 for your clients.
You allready did the same for VLAN 1. Having ports on both switches and let switch B do the routing. For VLAN 2 the setup is the same.
Tag port A3 on switch A for VLAN 2, and untag ports on switch A for VLAN 2 for your clients.
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