Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

5550IP on lateset MCD query

Status
Not open for further replies.

pea123

Technical User
Aug 26, 2009
380
Hie to you all.

I have observed that if I swap my DHCP server from Windows to Mitel, the red light then goes off.

Does this mean that on the latest MCD the 5550 only works when DHCP enabled is on the Mitel only or there is some special tweaking required.

The explained problem is even more persistent were vlans are used, which brings me to this question:- Is the 5550 vlan aware? If not then what is the work around?

Configuring the 5550 with a static ip address on the MCD DHCP STATIC fails to turn off the red light as well.

Please advise.
 
The 5550 can receive its address via either DHCP server, windows or 3300 but it does not support CDP or LLDP, connect the keypad to an untagged voice VLAN port on the L2 switch
 
The problem still occurs on a flat network were there is only the default vlan but is resolved by switching from the Win DHCP server to the Mxe DHCP server. Does the tagging & untagging apply in this case? Then why in this scenario does the red light not go off.

Also could someone take me through the "boot process" of the 5550 and explain what it means if the red light stays on or goes off.

I would like a different view from MrMitel as stated above for wanting to learn more. No disrespect.
 
I just worked on one tonight

It was connected via a switch port forced into the voice vlan , we had to add option 125 to the DATA DHCP server (SBS2008) that provided the Voice Vlan ID , MCD ip TFTP IP etc.

The keypad when it boots does a dhcp discovery in the untagged network it is connected to .
Now the SBS 2008 Data DHCP server responds and gives it option 125 which it accepts
THE keypad then does another DHCP discovery in the voice vlan and gets an IP from the Mitel ..


Console PC works like its connected to an IP handset , just gets Data DHCP address - all is sweet


If I never did anything I'd never done before , I'd never do anything.....
 
Billz66, your post has the right solution but i cant grasp your DHCP option setup on the external DHCP. Kindly post a screen shot of your configs were possible.
If I get you correctly this is what you are saying:-

ICP = Data VLan
PHONES = Voice vLan
Switchport to ICP = Data vLan
Switchport to PHONES = Data Access port with Voice vLan
Switchport to 5550 = Data vLan only

On external DHCP server
Data Scope = Option 125
Voice Scope = Option 125

Also consider a case were the entire network is one subnet = one vlan but external DHCP server. what will be the approach?

Thanks.
 
I have no remote access , off the top of my head

We had HP 2620 POE switch with Data Vlan 1 Voice Vlan 20

MCD was 192.168.1.2 Subnet 255.255.255.0 GW 192.168.1.254
MCD internal dhcp Scope 192.168.1.100 - 192.168.1.150
MCD Option 125 Call Server 192.168.1.2 TFTP 192.168.1.2 Vlan 20
Pri 6 6 3 DSCP 46 46 26

DATA DHCP server was SBS 2008
- added option 125 as an option for the Data network scope
Used Mitel DHCP Config helper app to generate hex for the above settings
Pasted this into the option 125




If I never did anything I'd never done before , I'd never do anything.....
 
Anytime you manage to log on post the actual configs you used. I notice you have a vlan 20 on your MCD Option 125. I always leave the vlan part of it on default. could you please explain why I have to change it from default and to what value, according to what kind of setup.
 
Just checking if anyone out there has some information. Thought I should repost.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top