- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: VLAN 1
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
тАО03-25-2003 06:24 AM
тАО03-25-2003 06:24 AM
VLAN 1
Using Procurve 2524, I can regularly configure a port to carry tagged traffic for this VLAN but, using 9304 routing-switch, I cannot.
Do I need to define another VLAN for management?
- Tags:
- VLAN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-25-2003 07:41 AM
тАО03-25-2003 07:41 AM
Re: VLAN 1
If you use VLAN 1 for management, you have no need to tag the ports. You must tag the ports only if you want the link to carry information of more than one VLAN. There's no tagged traffic for VLAN if you have no tagged port for the VLAN.
In 93XX you can tag ports as well, the command sequence to tag 1st port of 1st module would be
enable
con t
vlan 1
tagged e 1/1
write mem
HTH,
Arimo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-25-2003 07:50 AM
тАО03-25-2003 07:50 AM
Re: VLAN 1
Every stack is connected by two redundant links to a couple of 9304 routing-switches.
The two links carry tagged traffic for all VLANs defined on 2524s.
If I leave VLAN1 as management VLAN on all 2524s, uplinks to 9304s need to carry traffic for this VLAN too. Or not?
Then, the sequence:
enable
con t
vlan 1
tagged e 1/1
doesn't work; I cannot use 'tagged ...' under 'vlan 1' config.
Can I redefine VLAN ID for DEFAULT_VLAN and create a new VLAN1 compatble with 2524s?
I attached a diagram of the network.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-25-2003 11:24 PM
тАО03-25-2003 11:24 PM
Re: VLAN 1
To your problem, I don't know why you can't tag ports in VLAN1 (no experience) but create another VLAN and make it management and use it instead.
/Marcus
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2003 12:50 AM
тАО03-26-2003 12:50 AM
Re: VLAN 1
By default, this is VLAN ID 1.
You can change this default VLAN ID in the CLI :
93xx(config)#default-vlan-id {unsed Vlan ID}
Note that you may have to reload the switch.
Then, you will be able to tag ports in the Vlan 1.
For more informations, you can look at :
ftp://ftp.hp.com/pub/networking/software/59903041_ch07.pdf
(7-4 and 7-13)
AP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-31-2003 10:01 PM
тАО03-31-2003 10:01 PM
Re: VLAN 1
Andreas