VLAN Config from CXi to HP Procurve

[RDECIT]

I'm having a bit of a dumb moment with a setup that I'm trying to get working. It's simple enough on paper but I can't get it sorted.

The customer has a CXi MCD4, setup on one subnet, phones plug into the internal switch and work fine.

The CXi LAN port is plugged into a HP Procurve, this has been setup with Default VLAN (1) and Voice (2)
The uplink port that the Mitel is in is configured as Default (No) and Voice (Untagged) To me this is pretty standard config. Each vlan has it's own IP and our default gateway (A SonicWall if interested) has a route that points all traffic to this switch to get onto the Mitel. So management of the Mitel works fine from the data side. There is also a MBG server plugged into this switch, which is also working fine.

My problem is this. They have run out of ports on the Mitel, no problem, I'll just use the Procurve as it's POE. It boot up's but never gets the right VLAN and I get option missing. Plug it into the Mitel it;s fine. I've done this loads for times with MXe's and never had a problem. Does the CXi with the switch have to be setup slightly differently. The Switch Config is below: Ports 2-3 are the Mitel and Teleworker.

Note: If I make the Mitel uplink port Default (Untagged) and Voice (Tagged), it appears to work, but then I lose all management of it from the LAN.

Startup configuration:

; J9087A Configuration Editor; Created on release #R.11.60

hostname "ProCurve Switch 2610-24-PWR"
trunk 25-26 Trk1 Trunk
ip default-gateway 192.168.16.254
ip routing
timesync sntp
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged 1,4-24,27-28,Trk1
ip address 192.168.15.8 255.255.255.0
no untagged 2-3
exit
vlan 2
name "Voice"
untagged 2-3
ip address 10.0.0.8 255.255.255.0
qos priority 6
tagged 4-24,27-28,Trk1
voice
exit
ip route 0.0.0.0 0.0.0.0 192.168.16.254
sntp unicast
sntp server 192.168.15.5
spanning-tree Trk1 priority 4
password manager
password operator

 

[DoubleUT]

The fact that your phones work on the Mitel direct would mean that DHCP for the phones is set to vlan 1. For the HP ports the phones need to use Vlan 2.
The easyest option is to manually programm the phones in Vlan 2 (those that are going to be connected to the HP switch and leave the rest as is.

 

[RDECIT]

I would agree that this appears to be the case. However, I don't want to program the sets manually and have never had to on the MXe units. Is this a CXi thing?

 

[sarond]

Not sure if this will help.

http://h17007.www1.hp.com/docs/interoperability/Mitel/4AA2-1398EEE.pdf

Look at LLDP.

As a test what happens if you program a port on the switch as untagged vlan 2 and connect a phone. Does it boot?
Do you have vlan 2 in your option 125, make sure it is not blank.

I don't believe there is any difference when programming the MXe and CXi.

 

[danramirez]

MXe and CXi behave exactly the same way in terms of L2 switching, have a look at the tech. manual, at the end of the book there are a couple of examples of different scenarios with external switches (L2/L3) and CXi.

How many DHCP have you got? Why don't you create two DHCP scopes in the 3300 and tell your L3 switch to forward DHCP requests (DHCP Helper) to your 3300?

Here is how to program DHCP Helper in HP. You need to do it on both Vlans:

First you need to enable DHCP Helper: dhcp-relay <Enter>
Then go to every Vlan and do: ip helper-address <x.x.x.x> <Enter>

Let us know if need additional help, regards,

Daniel

http://www.hatkana.com

http://www.wtelecom.com

 

[LoopyLou]

I would enable LLDP on the HP to hand out the right VLAN info.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[danramirez]

What LoopyLou suggests is also another acceptable way to do it, however I haven't done LLDP on HP switches before.

What it is very important that you understand what you are doing. regards,

Daniel

http://www.hatkana.com

http://www.wtelecom.com

 

[RDECIT]

Problem appeared to be fixed by leaving the uplink on the HP the default. I.e Default (untagged) Voice (Tagged) thus appears to be working fine with no cross over of dhcp scopes and is also working between HP switches which are trunkrd, which kinda goes against every other VLAN setup I've done with a Mitel.