- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- A5500 VLAN Tagged and Untagged Ports
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
08-01-2012 02:53 PM
08-01-2012 02:53 PM
A5500 VLAN Tagged and Untagged Ports
If a A5500 switch hosts several VLANs (100 to 130) and the access ports (used by PCs) can only be untagged, how does the switch know to which VLAN a packet belongs to?
- Tags:
- VLAN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2012 06:08 PM
08-01-2012 06:08 PM
Re: A5500 VLAN Tagged and Untagged Ports
It will say:
interface GigabitEthernet 1/0/1
vlan 100 untagged
vlan 101 tagged
etc....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2012 04:47 AM
08-02-2012 04:47 AM
Re: A5500 VLAN Tagged and Untagged Ports
The above syntax is incorrect for all Comware versions i've used. You would instead use something like this:
vlan 100
description Nice long description
name short-name
vlan 101
description Another nice long description
name short-name-2
interface GigabitEthernet1/0/1
port link-mode bridge
description port description goes here
port link-type trunk
port trunk permit vlan 100 101
port trunk pvid vlan 100
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2012 06:45 PM - edited 08-02-2012 06:45 PM
08-02-2012 06:45 PM - edited 08-02-2012 06:45 PM
Re: A5500 VLAN Tagged and Untagged Ports
Let me describe the following scenario
- Two computers connected to one switch (A550-A) need to communicate to two other computers connected to another switch (A5500-B)
- The computers A and C are connected to ports assigned to the VLAN 100 and their port is access type. Therefore the VLAN 100 is untagged.
- The computers B and D are connected to ports assgined to the VLAN 101 and thier port is also access type. Hence untagged.
- The two switches are connected through fiber on port 25 on each end. Therefore this port is configured as trunk and permits VLAN 100 and 101 to pass through. On both switches the PVID is VLAN 100.
How will B and D communicate is the trunk port can only have 1 untagged VLAN? Do I need a separate fiber connection for another trunk port dedicated for VLAN 101?
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2012 07:34 PM
08-02-2012 07:34 PM
Re: A5500 VLAN Tagged and Untagged Ports
You have set up the switches exactly right for the different systems to communicate on their respective VLANs, as long as the PVID and tagging are set correctly on both ends of the switch-to-switch link.
You can verify the correct setup of the VLANs from the CLI by running 'display vlan 100' and 'display vlan 101' - this will tell you which ports are tagged and untagged. As long as this confirms what your intended setup is, it should be working.
If it's not working, there is likely some other issue, like local firewalls on the workstations.
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2012 07:42 PM
08-02-2012 07:42 PM
Re: A5500 VLAN Tagged and Untagged Ports
Right. But if the trunk port (which is only 1 for each switch) can only have 1 VLAN untagged (VLAN 100) the tagged VLAN 101 will not be able to communicate anything between PCs (B and D) since these are connected to an access port which has an untagged VLAN 101, right?. Therefore I believe I needed anothed trunk port just for VLAN 101 also untagged.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2012 07:46 PM
08-02-2012 07:46 PM
Re: A5500 VLAN Tagged and Untagged Ports
Tagged VLANs were designed with exactly this purpose in mind. You can add as many VLANs as required to the same inter-switch link by tagging them.
Paul