- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Help a newbie with VLANS
Switches, Hubs, and Modems
1753659
Members
5877
Online
108798
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
10-13-2010 03:20 AM
10-13-2010 03:20 AM
Help a newbie with VLANS
Hi there,
Never configured a VLAN before, and trying to work my head around a current setup that telephone engineers created when they originally setup our Mitel 3300 Phone System on the network.
All the PC's connect to the network through Mitel 5212 IP phones (they share a network port).
**Current Setup**
We have 5 x HP 2626 switches with POE.
Switch-1 = Stack Commander (This is also the default GW)
Switch-2 = Stack Member
Switch-3 = Stack Member
Switch-4 = Stack Member
Switch-5 = Stack Member
-----------------------------------------
Switch-1 Setup (Core Switch)
hostname "Switch-0"
ip default-gateway 192.168.1.251
ip routing
snmp_server community "public" Unrestricted
vlan 1
name "Data_Vlan"
untagged 2,4-10,12-26
ip address 192.168.1.251 255.255.255.0
no untagged 1,3,11
vlan 2
name "voice_vlan"
forbid 24
untagged 1,3,11
ip address 192.168.2.251 255.255.255.0
qos priority 6
tagged 2,4-10,12-23,25-26
voice
exit
ip route 0.0.0.0 0.0.0.0 192.168.1.10
ip route blar blar .... list goes on here...
stack commander "XXXXX"
stack auto-grab
stack member1 mac-address xxxxxxxxxxxxxx
stack member2 mac-address xxxxxxxxxxxxxx
stack member3 mac-address xxxxxxxxxxxxxx
stack member 4 mac-address xxxxxxxxxxxxxx
stack member 5 mac-address xxxxxxxxxxxxxx
---------------------------------------
Example Member Switch setup...
hostname "Switch-1"
ip default-gateway 192.168.1.251
snmp_server community "public" Unrestricted
vlan 1
name "Data_Vlan"
untagged 1-25
ip address 192.168.1.253 255.255.255.0
no untagged 1,3,11
vlan 2
name "voice_vlan"
ip address 192.168.2.253 255.255.255.0
qos priority 6
tagged 1-26
voice
exit
stack join 001708218500
-----------------------------------------
Now what I plan to do, is add another two switches.
However, I need to add another subnet for a new network (192.168.16.0) for a company moving into our premises.
They will be using the same phones and phonesystem as us so will need to connect to the voice Vlan via their switches and also their new VLAN subnet (192.168.16.0)
They will also need to be able to access the original data_vlan network which has a few servers on it they will need access too.
So basically the original core switch (192.168.1.251) layout will be something like
vlan 1
name "Data_Vlan"
untagged 2,4-10,12-26
ip address 192.168.1.251 255.255.255.0
no untagged 1,3,11
vlan 2
name "voice_vlan"
forbid 24
untagged 1,3,11
ip address 192.168.2.251 255.255.255.0
qos priority 6
tagged 2,4-10,12-23,25-26
voice
exit
vlan 3
name "Data2_Vlan"
untagged ???? <---- I dont know what to change this to.
ip address 192.168.16.251 255.255.255.0
tagged ??? <---- Not sure what to put here either.
--------------------
The new member switches could possibly just have voice_vlan and Data2_Vlan on it ? Or would it need the original data_vlan too?
Would I be routing via a default gateway to get back to the original VLAN?
I know it sounds a bit confusing but I've never done this before so finding my way around in the dark a bit!
Cheers!
Jonathan.
Never configured a VLAN before, and trying to work my head around a current setup that telephone engineers created when they originally setup our Mitel 3300 Phone System on the network.
All the PC's connect to the network through Mitel 5212 IP phones (they share a network port).
**Current Setup**
We have 5 x HP 2626 switches with POE.
Switch-1 = Stack Commander (This is also the default GW)
Switch-2 = Stack Member
Switch-3 = Stack Member
Switch-4 = Stack Member
Switch-5 = Stack Member
-----------------------------------------
Switch-1 Setup (Core Switch)
hostname "Switch-0"
ip default-gateway 192.168.1.251
ip routing
snmp_server community "public" Unrestricted
vlan 1
name "Data_Vlan"
untagged 2,4-10,12-26
ip address 192.168.1.251 255.255.255.0
no untagged 1,3,11
vlan 2
name "voice_vlan"
forbid 24
untagged 1,3,11
ip address 192.168.2.251 255.255.255.0
qos priority 6
tagged 2,4-10,12-23,25-26
voice
exit
ip route 0.0.0.0 0.0.0.0 192.168.1.10
ip route blar blar .... list goes on here...
stack commander "XXXXX"
stack auto-grab
stack member1 mac-address xxxxxxxxxxxxxx
stack member2 mac-address xxxxxxxxxxxxxx
stack member3 mac-address xxxxxxxxxxxxxx
stack member 4 mac-address xxxxxxxxxxxxxx
stack member 5 mac-address xxxxxxxxxxxxxx
---------------------------------------
Example Member Switch setup...
hostname "Switch-1"
ip default-gateway 192.168.1.251
snmp_server community "public" Unrestricted
vlan 1
name "Data_Vlan"
untagged 1-25
ip address 192.168.1.253 255.255.255.0
no untagged 1,3,11
vlan 2
name "voice_vlan"
ip address 192.168.2.253 255.255.255.0
qos priority 6
tagged 1-26
voice
exit
stack join 001708218500
-----------------------------------------
Now what I plan to do, is add another two switches.
However, I need to add another subnet for a new network (192.168.16.0) for a company moving into our premises.
They will be using the same phones and phonesystem as us so will need to connect to the voice Vlan via their switches and also their new VLAN subnet (192.168.16.0)
They will also need to be able to access the original data_vlan network which has a few servers on it they will need access too.
So basically the original core switch (192.168.1.251) layout will be something like
vlan 1
name "Data_Vlan"
untagged 2,4-10,12-26
ip address 192.168.1.251 255.255.255.0
no untagged 1,3,11
vlan 2
name "voice_vlan"
forbid 24
untagged 1,3,11
ip address 192.168.2.251 255.255.255.0
qos priority 6
tagged 2,4-10,12-23,25-26
voice
exit
vlan 3
name "Data2_Vlan"
untagged ???? <---- I dont know what to change this to.
ip address 192.168.16.251 255.255.255.0
tagged ??? <---- Not sure what to put here either.
--------------------
The new member switches could possibly just have voice_vlan and Data2_Vlan on it ? Or would it need the original data_vlan too?
Would I be routing via a default gateway to get back to the original VLAN?
I know it sounds a bit confusing but I've never done this before so finding my way around in the dark a bit!
Cheers!
Jonathan.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2010 06:44 AM
10-13-2010 06:44 AM
Re: Help a newbie with VLANS
Here is a diagram... http://static.spiceworks.com/attachments/post/0003/3363/proposed-vlan-setup.png
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