- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Early Learning for Aruba Vlans, help
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
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
07-23-2019 02:50 AM
07-23-2019 02:50 AM
Early Learning for Aruba Vlans, help
wondering if someone could explain how tagged and untagged works for vlans based on this scenario.
We've recently taken over a small setup and i'm trying to get my head round how the vlans work and how they cross talk to each other.
ID Name IP Untagged Tagged
1 MGMT 10.11.12.1 2,4,41-48 1
100 Data 192.168.100.100 3,7-40 1
105 Wifi Int 192.168.105.1 5 1-2,39-44
110 Wifi Guest 192.168.110.1 6 1-2,39-44
999 Edge WAN 192.168.99.1 1 None
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2019 08:09 AM
07-24-2019 08:09 AM
Re: Early Learning for Aruba Vlans, help
It's a shame you don't say what your networking background is i.e. Cisco, HP (ProCurve or Comware) etc.
I'm from a Comware background and tagged means trunked and untagged means access port. So whatever is connected to a port that is untagged only that VLAN's traffic is going through that port. When you need more than one VLAN to go through a port, this is when you tag VLANs. Furthermore, this is why you see the tagged ports more than once in your list.
Hope this is of some help and hope I'm not coming across as condescending.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2019 10:25 AM - last edited on 06-29-2021 05:01 AM by Ramya_Heera
07-26-2019 10:25 AM - last edited on 06-29-2021 05:01 AM by Ramya_Heera
Re: Early Learning for Aruba Vlans, help
Hello,
Just want to mention one more thing which you've asked about but was not explained already. Clients in VLANs "cross talking" to one another is simply called "routing" in networking terms. You didn't mention which switch model you have, but all HPE ProCurve/ArubaOS Switches from 29xx Series upwards support routing.
To enable it if the switch supports it, simply enter the CLI configuration context and run "ip routing" command to turn your Switch into a "Routing Switch". Now clients in different VLANs will be able to communicate as long as their gateway is the IP of the Routing Switch in their respective VLAN. Note that a VLAN without an IP address assigned to it on the Routing Switch will not be routed, so clients in that VLAN will only be able to communicate with one another.
Also note that ProCurve/ArubaOS does not bring a VLAN interface online until there is at least one port that is configured tagged/untagged in that VLAN and the port is up. So if you have set an IP on the device in VLAN X but the VLAN isn't assigned anywhere, you won't be able to ping the IP.
Hope that helps.
Justin
Working @ HPE