- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- 8212 and Multiple vlan questions
Switches, Hubs, and Modems
1819682
Members
3764
Online
109605
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
Discussions
Forums
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
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
тАО02-12-2011 09:48 AM
тАО02-12-2011 09:48 AM
8212 and Multiple vlan questions
Dear sirs,
As you can see from the attached file, Our new office contains 3 floors.
Each floor has 3 department and each department (excluding dept. 5) has an edge switch 2910 and same switch 2610 and 2610 PoE.
Ced's Administrator has planned one Vlan for each floor (192.168.128 - 132 - 136 /22),
a vlan for Voip (172.16.100.x/24) and a vlan for the Server farm (192.168.140.x /24).
He did'n want a management vlan.
Also, the second 8212zl (backup) of the control room is not yet available
so I'm doing all configurations without it (no vrrp etc.)
The fibers that go toward the floor are the odd ones (A1 to A19)
Now, from a temporary supervision server (on the second floor 192.168.132.80) i can see all the switches.
Can i ask you advice on current configuration?
How do I configure the vlan 1, on all switches? (similar to the floor vlan?)
VLANs "voip" e serverfarm" must be configured on all switches (edge and slave)?
In the PoE switches vlan "voip" is all tagged. Is that correct?
The connection port between edge and slave switches is always 26 but, strangely, on the slave switches, in the second floor, for proper connectivity,
i had to untag all port of floor's vlan, unlike the other plans.
I don't know why.
When the 8212 BACKUP arrives, I think set it up out of the network
How it should be the initial configuration?
Thanks in advance.
8212zl MASTER
; J9091A Configuration Editor; Created on release #K.15.02.0005
hostname "CSMASTERIP128004"
module 1 type J8706A
module 2 type J8702A
module 3 type J8702A
ip default-gateway 192.168.128.4
ip routing
vlan 1
name "DEFAULT_VLAN"
tagged A1,A3,A5,A7,A9,A11,A13,A15,A17,A19
no untagged A2,A4,A6,A8,A10,A12,A14,A16,A18,A20-A24,B1-B24,C1,C12
no ip address
exit
vlan 10
name "floor0"
tagged A1,A3,A5
ip address 192.168.128.4 255.255.252.0
exit
vlan 11
name "floor1"
ip address 192.168.132.4 255.255.252.0
tagged A7,A9,A11,A19
exit
vlan 12
name "floor2"
ip address 192.168.136.4 255.255.252.0
tagged A13,A15,A17
exit
vlan 99
name "voip"
ip address 172.16.100.1 255.255.252.0
tagged A1,A3,A5,A7,A9,A11,A13,A15,A17,A19
exit
vlan 98
name "serverfarm"
ip address 192.168.140.1 255.255.255.0
tagged A1,A3,A5,A7,A9,A11,A13,A15,A17,A19
exit
power-over-ethernet pre-std-detect
snmp-server community "public" unrestricted
EDGE1
; J9145A Configuration Editor; Created on release #W.14.38
hostname "0CCSIP128013"
module 1 type J9145A
module 2 type J9149A
module 3 type J9008A
ip default-gateway 192.168.128.4
vlan 1
name "DEFAULT_VLAN"
tagged 1-24,A1-A2,B1-B2
no ip address
exit
vlan 10
name "floor0"
untagged 1-18,A1-A2,B1-B2
ip address 192.168.128.13 255.255.252.0
tagged 19-24
exit
vlan 99
name "voip"
tagged 19-24
no ip address
exit
vlan 98
name "serverfarm"
tagged 19-24
no ip address
exit
snmp-server community "public" unrestricted
spanning-tree
SLAVE11
; J9085A Configuration Editor; Created on release #R.11.30
hostname "0CSW01IP128014"
ip default-gateway 192.168.128.4
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
no ip address
tagged 1-28
exit
vlan 10
name "floor0"
untagged 1-25,27-28
ip address 192.168.128.14 255.255.252.0
tagged 26
exit
vlan 99
name "voip"
tagged 26
exit
vlan 98
name "serverfarm"
tagged 26
exit
spanning-tree
SLAVE-POE11
; J9087A Configuration Editor; Created on release #R.11.30
hostname "0CPW01IP128016"
ip default-gateway 192.168.128.4
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
no ip address
tagged 1-28
exit
vlan 10
name "floor0"
untagged 1-25,27-28
ip address 192.168.128.16 255.255.252.0
tagged 26
exit
vlan 99
name "voip"
tagged 1-28
exit
vlan 98
name "serverfarm"
tagged 26
exit
spanning-tree
EDGE4
; J9145A Configuration Editor; Created on release #W.14.38
hostname "1CCSIP132009"
module 1 type J9145A
module 2 type J9149A
module 3 type J9008A
vlan 1
name "DEFAULT_VLAN"
tagged 1-24,A1-A2,B1-B2
no ip address
exit
vlan 11
name "floor1"
untagged 1-15,A1-A2,B1-B2
ip address 192.168.132.9 255.255.252.0
tagged 16-24
exit
vlan 99
name "voip"
tagged 16-24
no ip address
exit
vlan 98
name "serverfarm"
tagged 16-24
no ip address
exit
snmp-server community "public" unrestricted
spanning-tree
SLAVE41
; J9085A Configuration Editor; Created on release #R.11.30
hostname "1CSW01IP132010"
ip default-gateway 192.168.132.9
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
no ip address
tagged 1-28
exit
vlan 11
name "floor1"
untagged 1-25,27-28
ip address 192.168.132.10 255.255.252.0
tagged 26
exit
vlan 99
name "voip"
tagged 26
exit
vlan 98
name "serverfarm"
tagged 26
no ip address
exit
spanning-tree
SLAVE-POE 41
; J9087A Configuration Editor; Created on release #R.11.30
hostname "1CPW01IP132013"
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
no ip address
tagged 1-28
exit
vlan 11
name "floor1"
untagged 1-25,27-28
ip address 192.168.132.13 255.255.252.0
tagged 26
exit
vlan 99
name "voip"
tagged 1-28
exit
vlan 98
name "serverfarm"
tagged 26
no ip address
exit
spanning-tree
EDGE7
; J9145A Configuration Editor; Created on release #W.14.38
hostname "2CCSIP136009"
module 1 type J9145A
module 2 type J9149A
module 3 type J9008A
ip default-gateway 192.168.136.4
vlan 1
name "DEFAULT_VLAN"
tagged 23-24
no untagged 1-22,A1-A2,B1-B2
no ip address
exit
vlan 12
name "floor2"
untagged 1-22,A1-A2,B1-B2
ip address 192.168.136.9 255.255.252.0
tagged 23-24
exit
vlan 99
name "voip"
tagged 19-24
no ip address
exit
vlan 98
name "serverfarm"
tagged 19-24
no ip address
exit
snmp-server community "public" unrestricted
spanning-tree
SLAVE71
; J9085A Configuration Editor; Created on release #R.11.30
hostname "2CSW01IP136010"
ip default-gateway 192.168.136.4
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
ip address dhcp-bootp
no untagged 1-28
exit
vlan 12
name "floor2"
untagged 1-28
ip address 192.168.136.10 255.255.252.0
exit
vlan 99
name "voip"
tagged 26
exit
vlan 98
name "serverfarm"
tagged 26
no ip address
exit
spanning-tree
SLAVE-POE 71
; J9087A Configuration Editor; Created on release #R.11.30
hostname "2CPW01IP136012"
ip default-gateway 192.168.136.4
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
no ip address
no untagged 1-28
exit
vlan 12
name "floor2"
untagged 1-28
ip address 192.168.136.12 255.255.252.0
exit
vlan 99
name "voip"
tagged 1-28
exit
vlan 98
name "serverfarm"
tagged 26
no ip address
exit
spanning-tree
As you can see from the attached file, Our new office contains 3 floors.
Each floor has 3 department and each department (excluding dept. 5) has an edge switch 2910 and same switch 2610 and 2610 PoE.
Ced's Administrator has planned one Vlan for each floor (192.168.128 - 132 - 136 /22),
a vlan for Voip (172.16.100.x/24) and a vlan for the Server farm (192.168.140.x /24).
He did'n want a management vlan.
Also, the second 8212zl (backup) of the control room is not yet available
so I'm doing all configurations without it (no vrrp etc.)
The fibers that go toward the floor are the odd ones (A1 to A19)
Now, from a temporary supervision server (on the second floor 192.168.132.80) i can see all the switches.
Can i ask you advice on current configuration?
How do I configure the vlan 1, on all switches? (similar to the floor vlan?)
VLANs "voip" e serverfarm" must be configured on all switches (edge and slave)?
In the PoE switches vlan "voip" is all tagged. Is that correct?
The connection port between edge and slave switches is always 26 but, strangely, on the slave switches, in the second floor, for proper connectivity,
i had to untag all port of floor's vlan, unlike the other plans.
I don't know why.
When the 8212 BACKUP arrives, I think set it up out of the network
How it should be the initial configuration?
Thanks in advance.
8212zl MASTER
; J9091A Configuration Editor; Created on release #K.15.02.0005
hostname "CSMASTERIP128004"
module 1 type J8706A
module 2 type J8702A
module 3 type J8702A
ip default-gateway 192.168.128.4
ip routing
vlan 1
name "DEFAULT_VLAN"
tagged A1,A3,A5,A7,A9,A11,A13,A15,A17,A19
no untagged A2,A4,A6,A8,A10,A12,A14,A16,A18,A20-A24,B1-B24,C1,C12
no ip address
exit
vlan 10
name "floor0"
tagged A1,A3,A5
ip address 192.168.128.4 255.255.252.0
exit
vlan 11
name "floor1"
ip address 192.168.132.4 255.255.252.0
tagged A7,A9,A11,A19
exit
vlan 12
name "floor2"
ip address 192.168.136.4 255.255.252.0
tagged A13,A15,A17
exit
vlan 99
name "voip"
ip address 172.16.100.1 255.255.252.0
tagged A1,A3,A5,A7,A9,A11,A13,A15,A17,A19
exit
vlan 98
name "serverfarm"
ip address 192.168.140.1 255.255.255.0
tagged A1,A3,A5,A7,A9,A11,A13,A15,A17,A19
exit
power-over-ethernet pre-std-detect
snmp-server community "public" unrestricted
EDGE1
; J9145A Configuration Editor; Created on release #W.14.38
hostname "0CCSIP128013"
module 1 type J9145A
module 2 type J9149A
module 3 type J9008A
ip default-gateway 192.168.128.4
vlan 1
name "DEFAULT_VLAN"
tagged 1-24,A1-A2,B1-B2
no ip address
exit
vlan 10
name "floor0"
untagged 1-18,A1-A2,B1-B2
ip address 192.168.128.13 255.255.252.0
tagged 19-24
exit
vlan 99
name "voip"
tagged 19-24
no ip address
exit
vlan 98
name "serverfarm"
tagged 19-24
no ip address
exit
snmp-server community "public" unrestricted
spanning-tree
SLAVE11
; J9085A Configuration Editor; Created on release #R.11.30
hostname "0CSW01IP128014"
ip default-gateway 192.168.128.4
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
no ip address
tagged 1-28
exit
vlan 10
name "floor0"
untagged 1-25,27-28
ip address 192.168.128.14 255.255.252.0
tagged 26
exit
vlan 99
name "voip"
tagged 26
exit
vlan 98
name "serverfarm"
tagged 26
exit
spanning-tree
SLAVE-POE11
; J9087A Configuration Editor; Created on release #R.11.30
hostname "0CPW01IP128016"
ip default-gateway 192.168.128.4
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
no ip address
tagged 1-28
exit
vlan 10
name "floor0"
untagged 1-25,27-28
ip address 192.168.128.16 255.255.252.0
tagged 26
exit
vlan 99
name "voip"
tagged 1-28
exit
vlan 98
name "serverfarm"
tagged 26
exit
spanning-tree
EDGE4
; J9145A Configuration Editor; Created on release #W.14.38
hostname "1CCSIP132009"
module 1 type J9145A
module 2 type J9149A
module 3 type J9008A
vlan 1
name "DEFAULT_VLAN"
tagged 1-24,A1-A2,B1-B2
no ip address
exit
vlan 11
name "floor1"
untagged 1-15,A1-A2,B1-B2
ip address 192.168.132.9 255.255.252.0
tagged 16-24
exit
vlan 99
name "voip"
tagged 16-24
no ip address
exit
vlan 98
name "serverfarm"
tagged 16-24
no ip address
exit
snmp-server community "public" unrestricted
spanning-tree
SLAVE41
; J9085A Configuration Editor; Created on release #R.11.30
hostname "1CSW01IP132010"
ip default-gateway 192.168.132.9
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
no ip address
tagged 1-28
exit
vlan 11
name "floor1"
untagged 1-25,27-28
ip address 192.168.132.10 255.255.252.0
tagged 26
exit
vlan 99
name "voip"
tagged 26
exit
vlan 98
name "serverfarm"
tagged 26
no ip address
exit
spanning-tree
SLAVE-POE 41
; J9087A Configuration Editor; Created on release #R.11.30
hostname "1CPW01IP132013"
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
no ip address
tagged 1-28
exit
vlan 11
name "floor1"
untagged 1-25,27-28
ip address 192.168.132.13 255.255.252.0
tagged 26
exit
vlan 99
name "voip"
tagged 1-28
exit
vlan 98
name "serverfarm"
tagged 26
no ip address
exit
spanning-tree
EDGE7
; J9145A Configuration Editor; Created on release #W.14.38
hostname "2CCSIP136009"
module 1 type J9145A
module 2 type J9149A
module 3 type J9008A
ip default-gateway 192.168.136.4
vlan 1
name "DEFAULT_VLAN"
tagged 23-24
no untagged 1-22,A1-A2,B1-B2
no ip address
exit
vlan 12
name "floor2"
untagged 1-22,A1-A2,B1-B2
ip address 192.168.136.9 255.255.252.0
tagged 23-24
exit
vlan 99
name "voip"
tagged 19-24
no ip address
exit
vlan 98
name "serverfarm"
tagged 19-24
no ip address
exit
snmp-server community "public" unrestricted
spanning-tree
SLAVE71
; J9085A Configuration Editor; Created on release #R.11.30
hostname "2CSW01IP136010"
ip default-gateway 192.168.136.4
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
ip address dhcp-bootp
no untagged 1-28
exit
vlan 12
name "floor2"
untagged 1-28
ip address 192.168.136.10 255.255.252.0
exit
vlan 99
name "voip"
tagged 26
exit
vlan 98
name "serverfarm"
tagged 26
no ip address
exit
spanning-tree
SLAVE-POE 71
; J9087A Configuration Editor; Created on release #R.11.30
hostname "2CPW01IP136012"
ip default-gateway 192.168.136.4
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
no ip address
no untagged 1-28
exit
vlan 12
name "floor2"
untagged 1-28
ip address 192.168.136.12 255.255.252.0
exit
vlan 99
name "voip"
tagged 1-28
exit
vlan 98
name "serverfarm"
tagged 26
no ip address
exit
spanning-tree
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2011 12:51 PM
тАО02-12-2011 12:51 PM
Re: 8212 and Multiple vlan questions
Hi Alexmanto
How do I configure the vlan 1, on all switches? (similar to the floor vlan?)
The VLAN1 is already configure in all switches (Default-Vlan), and you dont remove it.
VLANs "voip" e serverfarm" must be configured on all switches (edge and slave)?
If you want to use this VLANs on a switch, it must be configured in that switch.
In the PoE switches vlan "voip" is all tagged. Is that correct?
If you want to trasmit that VLAN, the ports must be tagged.
The connection port between edge and slave switches is always 26 but, strangely, on the slave switches, in the second floor, for proper connectivity,
i had to untag all port of floor's vlan, unlike the other plans.
I don't know why.
Usually the connection port must be tagged for all VLANs you want to use
When the 8212 BACKUP arrives, I think set it up out of the network
How it should be the initial configuration?
In that case, you have several switches, you can use Procurve Manager for monitoring and configuring all switches, its more easy to manage.
Regards, Jorge
How do I configure the vlan 1, on all switches? (similar to the floor vlan?)
The VLAN1 is already configure in all switches (Default-Vlan), and you dont remove it.
VLANs "voip" e serverfarm" must be configured on all switches (edge and slave)?
If you want to use this VLANs on a switch, it must be configured in that switch.
In the PoE switches vlan "voip" is all tagged. Is that correct?
If you want to trasmit that VLAN, the ports must be tagged.
The connection port between edge and slave switches is always 26 but, strangely, on the slave switches, in the second floor, for proper connectivity,
i had to untag all port of floor's vlan, unlike the other plans.
I don't know why.
Usually the connection port must be tagged for all VLANs you want to use
When the 8212 BACKUP arrives, I think set it up out of the network
How it should be the initial configuration?
In that case, you have several switches, you can use Procurve Manager for monitoring and configuring all switches, its more easy to manage.
Regards, Jorge
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2011 12:40 AM
тАО02-14-2011 12:40 AM
Re: 8212 and Multiple vlan questions
Hi alex,
- "tagged" means a vlan-tag is added before sending packet
- "untagged" means vlan-tag is stripped before sending packets.
and accept untagged packets for the PVID.
- "no untagged" means : "do not accept untagged packets"
on the 8212 you tag all vlans on the port connecting to the edges
>>>
8212zl MASTER
vlan 1
tagged A1,A3,A5.....
exit
vlan 10
tagged A1,A3,A5
exit
<<<
but on the edge you do not!
(I assume connected to one of A1-B2)
>>>
EDGE1
vlan 1
tagged 1-24,A1-A2,B1-B2
exit
vlan 10
untagged 1-18,A1-A2,B1-B2
tagged 19-24
exit
<<<
you must tag vlan's on both sides of the link.
change to
====
vlan 1
tagged .....,A1-A2,B1-B2
exit
vlan 10
tagged .....,A1-A2,B1-B2
exit
=====
in your config, packets from vlan-10 on the edge are stripped from the vlan-tag before sending to the 8212,
NB! the "tagged" for vlan-1 makes SENT packets to have a vlan-tag added.
and because " no untagged" is not set on these ports they are received as entering vlan-1 (the default vlan, or the PVID).
same may go for the slaves.
- "tagged" means a vlan-tag is added before sending packet
- "untagged" means vlan-tag is stripped before sending packets.
and accept untagged packets for the PVID.
- "no untagged" means : "do not accept untagged packets"
on the 8212 you tag all vlans on the port connecting to the edges
>>>
8212zl MASTER
vlan 1
tagged A1,A3,A5.....
exit
vlan 10
tagged A1,A3,A5
exit
<<<
but on the edge you do not!
(I assume connected to one of A1-B2)
>>>
EDGE1
vlan 1
tagged 1-24,A1-A2,B1-B2
exit
vlan 10
untagged 1-18,A1-A2,B1-B2
tagged 19-24
exit
<<<
you must tag vlan's on both sides of the link.
change to
====
vlan 1
tagged .....,A1-A2,B1-B2
exit
vlan 10
tagged .....,A1-A2,B1-B2
exit
=====
in your config, packets from vlan-10 on the edge are stripped from the vlan-tag before sending to the 8212,
NB! the "tagged" for vlan-1 makes SENT packets to have a vlan-tag added.
and because " no untagged" is not set on these ports they are received as entering vlan-1 (the default vlan, or the PVID).
same may go for the slaves.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2011 03:21 AM
тАО02-14-2011 03:21 AM
Re: 8212 and Multiple vlan questions
Many thanks to Jorge and Pieter,
Pieter, sorry, I was not clear on the connection port of edge switches.
(fiber) ports 23 and 24 are always connected with 8212 (master e backup)
Ports with the lowest number (22,21 etc) are connected with the slave switches.
So, your advice confirm me, that (on the edge) I have to tag ports 23 and 24
for correspondence with the (two) 8212 and lowest port because go to the slave switches, right?
(At a glance, Edge1 has 6 links : 2 8212, 4 slaves, so i tagged 19 to 24 ports)
Finally,
sorry but sorry but I did'n understand your advice about "no untagged" ports
in default vlan (vlan-1)
Thanks in advance
Pieter, sorry, I was not clear on the connection port of edge switches.
(fiber) ports 23 and 24 are always connected with 8212 (master e backup)
Ports with the lowest number (22,21 etc) are connected with the slave switches.
So, your advice confirm me, that (on the edge) I have to tag ports 23 and 24
for correspondence with the (two) 8212 and lowest port because go to the slave switches, right?
(At a glance, Edge1 has 6 links : 2 8212, 4 slaves, so i tagged 19 to 24 ports)
Finally,
sorry but sorry but I did'n understand your advice about "no untagged" ports
in default vlan (vlan-1)
Thanks in advance
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.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP