Link to home
Start Free TrialLog in
Avatar of djhath
djhathFlag for United States of America

asked on

Hp Procurve 2910 stacking and VLANs

I'm in the process of setting up (1) HP Procurve 2910-24 and (2) HP Procurve 2910-48 switches to replace an Enterasys switch stack that provides connectivity to my PCs and ShoreTel VoIP system.

The Enterasys switch stack is managed by a single IP and has a single config.  Since our PCs tether off of the phones, I desire to maintain managing the Procurve stack with a single IP and simply creating the necessary VLANs.

Right now, I have the Procurves in a stack, though each switch does currently have its own IP.  

Couple questions:

1) What do I need to do to be able to get the entire stack manageable by a single IP?
2) Creating the VLANs is pretty straightforward to me.  I have certain ports I need to tag specific to the voice VLAN, but, I'm curious if there's anything special I need to consider with the tagging since both voice and data traffic will be carried over the same wire.
3) Once the stack is manageable by the same IP, does each switch simply maintain a copy of the config, or does it become a single config managed by the 'commander'?  Also, will each switch still require its own IP? It's a not a problem, if so.

Sadly, when I was working on getting the stacking to work, I did come across a question that had a posted config of a stack of Procurve switches managed over the same IP, though now I'm struggling to find that question.  I figured I'd pose my question now while I try to find that in case I happen to get an answer here before stumbling across the other one with the config info I need that would pretty much answer my questions.

Thank you in advance for your help.
Avatar of djhath
djhath
Flag of United States of America image

ASKER

Looking over some things, here is what I've come up with for a config, assuming that each switch does have to maintain its own config:

**Commander Switch** (24-port switch)

hostname "HP_POE-0"
module 1 type J9146A
module 2 type J9165A
module 3 type J9165A
stack commander "HP_POE"
stack auto-grab
stack member 1 mac-address 28924A759C00
stack member 2 mac-address 28924A7724C0
ip default-gateway 192.168.1.1
vlan 1
   name "DEFAULT_VLAN"
   untagged 9-24,A1,B1
   ip address 192.168.1.2 255.255.255.0
   exit
vlan 2
   name "VoIP"
   ip address 192.168.3.1 255.255.255.0
   tagged 1-8
   no untagged 9-24
   exit
ip route 0.0.0.0 0.0.0.0 192.168.1.1
snmp-server community "public" unrestricted
spanning-tree
no autorun

**Switch 2** (1st 48-port switch)

hostname "HP_POE-1"
module 1 type J9148A
module 2 type J9165A
module 3 type J9165A
stack join 2C4138228700
ip default-gateway 192.168.1.1
vlan 1
   name "DEFAULT_VLAN"
   untagged 1-48,A1,B1
   ip address 192.168.1.2 255.255.255.0
   exit
vlan 2
   name "VoIP"
   ip address 192.168.3.1 255.255.255.0
   no untagged 1-48
   exit
ip route 0.0.0.0 0.0.0.0 192.168.1.1
snmp-server community "public" unrestricted
spanning-tree
no autorun

**Switch 3** (2nd 48-port switch)

hostname "HP_POE-2"
module 1 type J9148A
module 2 type J9165A
module 3 type J9165A
stack join 2C4138228700
ip default-gateway 192.168.1.1
vlan 1
   name "DEFAULT_VLAN"
   untagged 1-48,A1,B1
   ip address 192.168.1.2 255.255.255.0
   exit
vlan 2
   name "VoIP"
   ip address 192.168.3.1 255.255.255.0
   no untagged 1-48
   exit
ip route 0.0.0.0 0.0.0.0 192.168.1.1
snmp-server community "public" unrestricted
spanning-tree
no autorun

In the 24-port switch, the intention is to make ports 1-8 "ShoreTel-only" ports.  The rest of the ports should be able to have a phone plugged in and to then be able to tether a PC off of the phone.  

The other parts I'm uncertain about is if the ip route and ip default gateway statements are needed in the configs of the 48-port switches.  All-in-all, I'm sure this is pretty close to what I need, but just need a couple points of clarification.
Avatar of Paul Solovyovsky
You can manage a HP 2910 stack with 1 IP, check page 3 on the following guide

http://cdn.procurve.com/training/Manuals/2910-ATG-Feb09-6-Stacking.pdf
Avatar of djhath

ASKER

Thank you, paulsolov. I already have the stacking under control.  Does each switch maintain its own config?  If not, I'm trying to figure out how to refer to the ports on the 2nd and 3rd switch in the stack since I need to define tagging/untagging parameters on those, as well.
I believe that each switch maintains its own config.  Unlike Cisco and their stack you can't even create cross switch port groups so I would imagine that each switch is indepenedent.  If you don't have the 10GB stack modules that would be helpfull and offload the port densitiy as well as increase throughput
Avatar of djhath

ASKER

OK, that's good to know.  I do have the stacking modules, which is also good.

I guess the last piece is trying to get my hands wrapped around how ports need to be tagged, untagged, and "no untagged" relative to my configuration needs; which is the ability for voice and data to travel over the same wire, as the PCs tether off the phone.

For the ShoreTel only ports, those that I know need to be exclusive to my voice VLAN, I understand those need to be tagged.
ASKER CERTIFIED SOLUTION
Avatar of Paul Solovyovsky
Paul Solovyovsky
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
An easy way to set VLANs on ports and trunks is by typing "menu"   This will bring you to a menu driven interface and is sometimes easier visually to see what the configuration is.