Sets sitting at DHCP after replacing a controller.

[LoopyLou]

Have a site where we are replacing an older MX controller at Release 9 and going to MCD 4 SP4 on an MXe ( OpsMan still in the picture because of an SX2000 in the cluster ). Did all the upgrading on the new controller so that night of cut we just unplug the old controller and plug in the new. Problem is that all the phones just site there at DHCP discovery and its a bitch to try them to connect to the new system. This has happened twice at two different locations. What am I missing. I understand the phones would need to update to the newer firmware but they have problems getting that far. Should I be issuing the reload command before taking the old controller off line?

An apple a day keeps the doctor away. Anyone else and you need to throw it harder.

 

[bobcheese]

I seem to remember an issue with DHCP at some point and the issue was based around a VLAN tag. I know its a bit tentative but do you have a VLAN configured on DHCP? Also, is this the 1st time 125 has been used?

 

[LoopyLou]

125 was configured. Will check the VLAN tag

An apple a day keeps the doctor away. Anyone else and you need to throw it harder.

 

[Lundah]

I've seen phones running on 9 firmware connect with no issues to an MCD 4.0 system, so that shouldn't be a problem. Definitely check your DHCP options & VLAN settings.