sets reset randomly then come back asking for registration

[ccuster]

I have 6 sets/DNs on a 3300ICP (running MCD 5.0) of around 70 phones. these same 6 sets inexplicably reset themselves then come back up asking for a PIN - user registers the phone; as well, if the user merely resets the phone again, it comes back up with there extension as though nothing was wrong and it is fine for a day or two.

It is always the same DNs! we have replaced the sets, removed and recreated the user profiles/DNs and switched the switch ports - all other phones on the 3300 are unaffected.

[x-man]

have you tried switching an affected DN to a non affected phone.....?(so do a swap between two sets; one thats ok and on ethat has the trouble)

[Mattmayn]

Do you have a resilient controller programmed for them?

[ccuster]

have you tried switching an affected DN to a non affected phone.....?(so do a swap between two sets; one thats ok and on ethat has the trouble)

we have replace with new sets but never w/ sets that are already in use

[ccuster]

Do you have a resilient controller programmed for them?

none of the sets are resilient

[ralph]

I'm with Mattmayn on this one.
If you have a resilient controller in the network it could do this even if the phones are not programmed to be resilient. 
Odds are pretty good that the phones are trying to go resilient and hitting another controller that the phones are programmed on.  This will cause the phones to say "enter pin".

Check your DHCP options for those phones to see if you have more than one controller programmed.

Ralph

[ccuster]

Sorry, something I neglected to mention. The system ran flawlessly for a year. Installed and added to cluster  w/ 4.1 upgraded when 4.2 released and the problem started within days of 5.0 upgrade.

[Mattmayn]

If you go into the config mode of the actual phone do they have an ICP 2 IP listed?

I had a phone in our office that did that once. It thought it was supposed to failover to a secondary controller even though ESM didn't show it. I didn't want to mess with it so I put a static entry into that phone for ICP 1 and went with it.

[LoopyLou]

You mention a cluster so it sounds like their is another system that they could try to register with if they were resilient. What options are in your DHCP for Option 125 i.e are more then one RTC defined. It sounds like the phones lose connection to their MCD and reboot. At that point they can only find some other controller where they attempt to register. The hard reset allows them to find the primary again. Are you using the double fetch method of DHCP by any chance.

[ralph]

Are you using the double fetch method of DHCP by any chance.

LoopyLou,
Glad to see you jumping in.   I know you bring a lot to the party. 

What is a "double fetch" method?

Ralph

[LoopyLou]

Double fetch is what I call it when the layer 2 switches are not using either LLDP or CDP to give the phones their VLAN info on boot. With double fetch the phones are seen as any other data device. They then go to the data VLAN DHCP server again like any other device. In the data VLAN DHCP server there are options setup that mean something to the phones ( Option 125 or the combination of older options like 130,132 etc ). Anyway the phone gets the options which give it the voice VLAN number and at this point the phone drops the data VLAN IP resets and issues another DHCP request on the voice VLAN.

The method I prefer is using CDP on Cisco L2 or LLDP on HP L2 switches to give the phone its voice VLAN number up front. Also I use the 3300 for phone DHCP. The set then only has to issue its DHCP request once because its directly on the voice VLAN and the 3300 can act as the DHCP server.

Either method works just fine.

[ccuster]

We deliver DHCP from the 3300 and use HP L2 w/ LLDP

Tagged for voice untagged for date

[LoopyLou]

These are the only sets on the layer 2?

[ralph]

You may have to wireshark that port as the phone boots.   
Paste it here and we can take a look at it.

Ralph

[ccuster]

I am just arranging to have a LT setup on the switch that these sets are connected to (system in another location). In the mean time however, i have had a developement. one of our techs at the site in question was registering a couple of new sets for me from his desk last week. he unplugged his phone, plugged the new ones in and registered them from his connection. he then plugged his phone back in.

ever since then, his phone too has been doing the same thing. reseting over the course of a night and comming back asking for PIN. if he reboots it a second time, it comes back with his extension as though nothing was wrong.