[cisco-voip] TFTP error when phone resets

Tue Dec 19 10:26:07 EST 2006

Change it to "YES", reset, and then back to NO... and reset.

The thing here is we need to clear this crap out of the phone, somehow,
somewhere, it picked up this IP...

Jonathan

On 12/19/06, Ruben Montes (Europe) <Ruben.Montes at eu.didata.com> wrote:
>
>  Hello,
>
> I have verified some of the phones having problems, and all of them say
> "NO" under 'alternate TFTP'... What else could I check?
>
> Thanks,
>
> Ruben
>
> ------------------------------
> *De:* Jonathan Charles [mailto:jonvoip at gmail.com]
> *Enviado el:* lun 18/12/2006 18:29
> *Para:* Ruben Montes (Europe)
> *CC:* Wes Sisk; cisco-voip at puck.nether.net
> *Asunto:* Re: [cisco-voip] TFTP error when phone resets
>
> Understood, but the question is, where are the phones getting the bogus
> TFTP server IP?
>
> The most obvious thinking is that someone manually overrode the default
> settings for the phones.
>
> So, on the phone, go to settings, hit option 3 (for a 7960), scroll down
> to number 32, see if says under 'alternate TFTP", it says YES, if so, unlock
> the phone (**#), and change it to "NO" and hit save.
>
> Reset the phone.
>
> See if the bogus TFTP address is still there.
>
> If not, then change the TFTP server IP to all zeros (I know that is what
> you are trying to avoid, but doing so clears it out (go down to option 42,
> and change it to all zeros (0*0*0*0) and hit save, this will cause it to
> pick up the DHCP IP...
>
>
>
> Jonathan
>
> On 12/18/06, Ruben Montes (Europe) <Ruben.Montes at eu.didata.com> wrote:
> >
> >  Hi,
> >
> > the error is posted in my first e-mail (at the end of this page). My
> > DHCP scope doesn't have option 66, only option 150.
> > This problem is affecting many of my phones, not only one (maybe 100 or
> > 150).
> >
> > Regards,
> >
> > Ruben
> >
> > ------------------------------
> > *De:* Jonathan Charles [mailto:jonvoip at gmail.com]
> > *Enviado el:* lun 18/12/2006 18:07
> > *Para:* Ruben Montes (Europe)
> > *CC:* Wes Sisk; cisco-voip at puck.nether.net
> > *Asunto:* Re: [cisco-voip] TFTP error when phone resets
> >
> >  It says where? The phone, or the DCHP scope?
> >
> > Check your DHCP scope for an option 66.
> >
> > Now, the phone should get its TFTP server via option 150, but if that
> > fails, it will get it from option 66. If option 66 is set (but blank), that
> > could account for the all zeros address assignment.
> >
> > If either option 150 or 66 are blank (all zeros), fill them in with the
> > IP of your publisher and reset the phone(s) in question.
> >
> >
> >
> > Jonathan
> >
> >
> > On 12/18/06, Ruben Montes (Europe) <Ruben.Montes at eu.didata.com> wrote:
> > >
> > >  Hello,
> > >
> > > yes, we have the 'lease' in the official DHCP. The strange thing here
> > > is it says the address of the TFTP server is 0.0.0.0. Does it make
> > > sense?
> > > There is no secondary TFTP server...
> > >
> > > Thanks in advance,
> > >
> > > Ruben
> > >
> > > ------------------------------
> > > *De:* Jonathan Charles [mailto:jonvoip at gmail.com]
> > > *Enviado el:* lun 18/12/2006 17:45
> > > *Para:* Ruben Montes (Europe)
> > > *CC:* Wes Sisk; cisco-voip at puck.nether.net
> > > *Asunto:* Re: [cisco-voip] TFTP error when phone resets
> > >
> > >  Is their a lease for that device in the DHCP pool?
> > >
> > > I ask only because it is possible it is picking up an option 150 (or
> > > 66) from a different box that you aren't aware of (a rogue DHCP server, a
> > > switch or router with a DHCP pool configured that is intercepting the DHCP
> > > request and issuing an IP).
> > >
> > > Easier than that, go to the phone and check the IP address of the DHCP
> > > server it is using, check that scope. Also, is TFTP server 2 (and the
> > > Alternate TFTP set to yes) enabled on the phone? If so, it may be getting an
> > > IP address from the DHCP server and ignoring the option 150 settings with
> > > its own overriding settings, and then failing (because the address is bogus)
> > > and using the real option 150 address (when the manual address doesn't
> > > respond).
> > >
> > > Also, don't rule out the rogue DHCP server immediately. Generally,
> > > most large networks have rogue DHCP servers (and non-rogue servers that have
> > > rogue scopes on them). This is because Microsoft failed to integrate their
> > > DHCP servers together so that they know about one another and can share
> > > pools (IOW, the MS DHCP model does not prevent you from having overlapping
> > > pools and assigning the same IP more than once... It is a feature apparently
> > > (integrated, but only to a point, as they say).
> > >
> > >
> > >
> > >
> > > Jonathan
> > >
> > > On 12/18/06, Ruben Montes (Europe) <Ruben.Montes at eu.didata.com> wrote:
> > >
> > > >
> > > >  Hi,
> > > >
> > > > all the phones are DHCP configured. I've checked the DHCP scope
> > > > options and the ip address of the TFTP server is correct (included in the
> > > > CTL).
> > > > Any idea why it tries to access a TFTP at the address 0.0.0.0?
> > > >
> > > > Thanks in advance,
> > > >
> > > > Ruben
> > > >
> > > > ------------------------------
> > > > *De:* Wes Sisk [mailto:wsisk at cisco.com]
> > > > *Enviado el:* vie 15/12/2006 20:01
> > > > *Para:* Ruben Montes (Europe)
> > > > *CC:* cisco-voip at puck.nether.net
> > > > *Asunto: *Re: [cisco-voip] TFTP error when phone resets
> > > >
> > > >  Looks like your phone obtained a CTL certificate which includes a
> > > > list of authorized TFTP servers.  Now by either manual config or network
> > > > resolution, the phone is being pointed to a TFTP server that is not included
> > > > in the CTL file.
> > > >
> > > > /Wes
> > > >
> > > > Ruben Montes (Europe) wrote:
> > > >
> > > > Hello,
> > > >
> > > > I have this error every time I reset a phone:
> > > >
> > > >
> > > >
> > > > *Error: StationEventAlert - Station alert.*
> > > >
> > > > *TCP ProcessID: 9.100.129.1954*
> > > >
> > > > *Device Text: 34: Name=SEP0019E74DA3B2Load= 7.0(3.0S) TFTP NOT
> > > > AUTHORIZED: 0.0.0.0*
> > > >
> > > > *Param1: 0*
> > > >
> > > > *Param2: 0*
> > > >
> > > > *App ID: Cisco CallManager*
> > > >
> > > > *Cluster ID: StandAloneCluster*
> > > >
> > > > *Node ID: MCS7825CTP01*
> > > >
> > > > *Explanation: Station device sent an alert to Cisco CallManager.*
> > > >
> > > > *Recommended Action: Ensure that the configuration for identified
> > > > device is proper..*
> > > >
> > > >
> > > >
> > > > Anyway, the phone boots normally and we're not having any problem
> > > > except this message...
> > > >
> > > > Regards,
> > > >
> > > >
> > > >
> > > > Ruben
> > > >
> > > > ------------------------------
> > > >
> > > > _______________________________________________
> > > > cisco-voip mailing list
> > > > cisco-voip at puck.nether.net
> > > >
> > > >
> > > >
> > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > >
> > > >
> > > > _______________________________________________
> > > > cisco-voip mailing list
> > > > cisco-voip at puck.nether.net
> > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > >
> > > >
> > > >
> > >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061219/14a563cc/attachment-0001.html 