- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- VLAN routing
Switches, Hubs, and Modems
1752679
Members
5189
Online
108789
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-12-2011 08:58 AM
04-12-2011 08:58 AM
VLAN routing
I am fairly new to networking. We have a E5412zl switch on order. When it gets here I am not going to have a lot of time to configure this switch. Most of the configuration I have figured out. One of the things I am not sure about is the following.
I will have 3 VLANs 100, 103, 200
VLAN 103 will only have two ports on it for two printers. I need both the other VLANs to be able to access the printers. But I need to make sure that VLAN 100 and VLAN 200 are completely issolated from each other.
From what I have read I believe the following should work.
enable routing
assign an ip address to VLAN 103
make all the ports in VLAN 100 and VLAN 200 tagged members of VLAN 103
I realize I can do this with my router but it will be located in a different building and I would like to try and reduce the traffic over the trunk.
Any help would be greatly appreciated.
I will have 3 VLANs 100, 103, 200
VLAN 103 will only have two ports on it for two printers. I need both the other VLANs to be able to access the printers. But I need to make sure that VLAN 100 and VLAN 200 are completely issolated from each other.
From what I have read I believe the following should work.
enable routing
assign an ip address to VLAN 103
make all the ports in VLAN 100 and VLAN 200 tagged members of VLAN 103
I realize I can do this with my router but it will be located in a different building and I would like to try and reduce the traffic over the trunk.
Any help would be greatly appreciated.
- Tags:
- VLAN
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2011 09:37 PM
04-13-2011 09:37 PM
Re: VLAN routing
This is incorrect from what I am reading. This is a layer 3 switch, so yes you can keep this intervlan routing on that switch, but your statement of "make all the ports in VLAN 100 and VLAN 200 tagged members of VLAN 103" will not do what your wanting it to so in regards to isolating VLAN 100 and VLAN 200.
When you create VLANs on switches, you are operating at later 2 and by default, VLANs do not talk with other VLANs. This is where layer 3 comes into play by being able to route between those VLANs. The two things that make this happen is defining an ip address to the VLAN interface and globally enabling ip routing. Once you do this, the VLANs (that have IP addresses defined at the VLAN interfaces), route between each other completely. The only way to stop traffic from one VLAN to another VLAN is to define ACL (access control lists) to permit or deny traffic (do a google search for some examples as this is a lengthy discussion on it's own).
Untagging and Tagging(called trunking in Cisco lingo) ports operates in layer 2, so this would not route between VLANs.
When you create VLANs on switches, you are operating at later 2 and by default, VLANs do not talk with other VLANs. This is where layer 3 comes into play by being able to route between those VLANs. The two things that make this happen is defining an ip address to the VLAN interface and globally enabling ip routing. Once you do this, the VLANs (that have IP addresses defined at the VLAN interfaces), route between each other completely. The only way to stop traffic from one VLAN to another VLAN is to define ACL (access control lists) to permit or deny traffic (do a google search for some examples as this is a lengthy discussion on it's own).
Untagging and Tagging(called trunking in Cisco lingo) ports operates in layer 2, so this would not route between VLANs.
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