Link to home
Start Free TrialLog in
Avatar of rhwimmers
rhwimmersFlag for United States of America

asked on

Cisco 2910al Switch setup

Im more of a Cisco guy, but have a 2910al HP Switch im trying to setup..  In terms of vlans I want one voice and one data vlan.  Both will run off the same port (meaning PC plugged into phone, phone into switch).  I have a dhcp server (win2k8) that will run both scopes.  Whats the HP equivalent of switchport voice vlan?
The default vlan is already setup so guessing thats 1, and they are all untagged by default
I setup vlan 2.  I think to make them run 2 vlans they need to be "trunk" ports which mean TAGGED on vlan 1 and 2, that sound right?  Then how does it know to give PC vlan1 and phone vlan2 IP address?
ASKER CERTIFIED SOLUTION
Avatar of giltjr
giltjr
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
Avatar of rhwimmers

ASKER

Physical phones.  The default vlan 1 is all untagged and doesnt appear I can change the default.

It seems as though I leave vlan 1 all untagged for data, and then vlan 2 tagged for the VoIP vlan.  Do I use 2 NICs from my dhcp server (1 voice one data), or do I just turn on routing on the switch between the 2 vlans?  Any option better than the other?

It seems as though if I tag vlan 1 I hose myself and have to reset the switch.  I thought I would tag vlan 1 and 2 so it would be a trunk port but seems as though untag vlan 1 and tag vlan 2 if I want voice and data to work on the same port...
Ok so when I do untag vlan 1 and tag vlan 2 I get no DHCP on the data vlan (not sure on voice, trying to get data working first!
I'm not sure if HP supports it, I'll try and see if I can find any doc, but in the Cicso world you can code a IP forwarder address to forward bootp requests to a DHCP server.  

I beleive the DHCP server must be on a switch port that has both (all) VLAN's so that it can identify which VLAN the request came from so it can provide the correct IP address.

This way you don't need to have multiple NIC's on your DHCP, or multiple DHCP servers.
O.K.  It seems the 2910 may have ip helper function just like Cisco. You can read this post to see if it helps:

http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1297795700206+28353475&threadId=1369549
Ok was able to get 2 vlans setup and not use the native vlan 1.  One VoIP (with QOS) and 1 data.

Console in (have to do this to disable native vlan of 1) - create vlan 10 (or whatever number you want) for data, create vlan 20 for voice (again, number of your choice).
Set vlan 10 to default vlan, then set all ports to UNTAGGED
Set vlan 20 to TAGGED for any port that will have your VoIP traffic.  This is telling the switch that the packet will already have the packet tagged for vlan 20 (we manually typed this on our phones).
If you want a server in the 20 vlan then put that port to UNTAGGED in vlan 20.

Tagging options as best as I could figure out
NO - means that it will ALLOW traffic from other vlans on this port, but it is not the native vlan
Untagged - means to put all traffic on this port in that vlan (IE - PCs, as they dont specify what vlan they are in)
Tagged - means traffic is ALREADY tagged (phones)
Forbid - never used but guessing it would just not allow that vlan traffic from hitting it at all.

After ports are correct type ip routing to enable routing.  I did a route (voip traffic ip) vlan 20 (so it knew where all the VOIP traffic needed to get to.  Then do a 0.0.0.0 0.0.0.0 route that would go to your actual router or firewall (or last point before the internet.
I gave my vlan 10 and vlan 20 an ip address, and those IPs are what I used as the default gateway for each phone.

Trunk in HP means "port channel" in Cisco, meaning combining multiple ports for higher bandwidth.

So in summary, if your end device is putting the vlan tag on the frame - you set it for TAGGED (usually phones)
If your end device is NOT tagging the frame but you want it in a particular vlan, its UNTAGGED

You can only have one vlan as untagged obviously - so for a VoIP scenario where you have your PC plugged into your phone and phone into the switch - you do the untagged vlan as data, and tagged as VoIP and you will have good success.
Also, you do need the ip helper command to allow DHCP to forward its packets to the VoIP vlan (so in vlan 20 type ip helper x.x.x.x, where x.x.x.x is the ip of your dhcp server).

Hope this helps prevent the pain this caused me!
Thanks for getting me in the right direction.