Phones won't boot up

[jvetter]

We have a couple of phones that won't boot up. I was moving our network server yesterday and this morning a couple of phones had the wrong date and time. I tried rebooting them and it just sits on the DHCP screen. I tried to manually insert the ip address, default gateway, ftp server, MGC and SNTP with not luck. Now it says, "looking for ftp server," and will finally go to, "no service." I got the addresses from watching another phone boot up. I got the ip address from ShoreWare Director, but it's still not working. Any thoughts? Thanks.

[eazeaz]

Boot

I think you have some switches that are set for vlans and some that are not. Moving a phone changes the switch/port it is in, changes the VLAN configuration, causes it not to work.

just my guess

[jvetter]

The phones didn't physically move, there still plugged into the same port on the switch. Is that what you meant?

[khitan]

Can you please be specific about "moving a network server". Do you mean physically and now its on a new port? Is it in a Data Center and plugged directly into a core switch? how is it connected to the network? Does it have dual NIC's? did you plug the network cable back into the original NIC (Director license is associated with the MAC address of the NIC).

K

[Wes W]

Did the network server you moved have anything to do with DHCP or FTP services? Did you move this server to a different LAN segment, or switch port?

If it's only a couple of phones that don't work (assuming these worked before the move), how do these few differ from the rest? A different LAN segment, or maybe your ran out of available IP addresses in the phone DHCP pool. If you physically assigned an IP address that is outside of the pool and it worked enough to try to access the FTP server, then you may not be able to reach the FTP server because of a firewall setting. Try pinging from the phone (mute 7464#) to see if you can reach it. Ping the gateway too. Ping the shoreman server and shoregear switch too. After the phone downloads its files from the FTP server, then it connects to the shoregear switch or choice. Since it's failing that too, it's sounds more like a problem with the IP settings of the phone.

[jvetter]

I think I got it figured out. Somehow, it lost the settings on the phones. It didn't have the VLAN ID and once I put that in, it came right up. Thanks for the help.

[msoho]

It's possible that your DHCP server is not on an untagged VLAN port on your switches. You should check this as you shouldn't have to manually enter anything on your phones; DHCP should tell the phones the VLAN id, etc. using Option 156.

[msoho]

Also, especially if your DHCP server is a VM on an ESX server, you should really get this issue straightened out or you will likely have a large number of phones with issues when their leases are up.

[jvetter]

Did the network server you moved have anything to do with DHCP or FTP services? Did you move this server to a different LAN segment, or switch port?

Yeah, it's a Windows Small Business Server, so the DHCP service is on that server. I think I need to move that servers new switch port into the port where it was before the move, right? Basically, the old connection was A24 and now that server connects through C5, so I need to move the patch cable from C5 into the same port that A24 was plugged into, right? Sorry if that's really confusing, I just don't know how else to explain it.

Thanks.

[msoho]

You can either move that port back to where it was originally, or you can set the new port as untagged for your regular VLAN (data). Also, you need to make sure that the ip helper ip address on the voice vlan's is set for the dhcp server's ip address. Hope that helps!