Anyone ever see these in event logs on a phone that is
up and running just fine and has no problems, other
then this in event logs? I thought this was a bug in a
older 6.x phoneload but this is 7.2(2). I have also
seen this on a system where they use 7.0(2). =


EventID: 0xE0000003 (3) - Error: StationEventAlert -
Station alert.
TCP ProcessID: 2.100.132.90858816
Device Text: 6: Name=3DSEP0014F2E98072
Load=3D7.2(2.0)File Not Found

Thanks


=

 ________________________________________
__ =

Yahoo! DSL =96 Something to write home about. =

Just $16.99/mo. or less. =

dsl.yahoo.com =

[ Post a follow-up to this message ]

during one phone bootup the 7.2(2) load was not available from the  =

TFTP server. tftp server may have been rebuilding or shutdown at the  =

time.  Unfortunately those logs are not cleaned up consistently on  =

the phone.  there is a way to clear the log so you can be certain you  =

are only seeing new messages:

Under settings->(5)Status->(2)Network Statistics, the 3rd line shows the
last phone reset reason.

It appears most of our phone loads have a debug display:
1. while onhook enter **##**3 on the keypad
2. look under settings->(5)Status

These new items may appear in the status menu:
(5) Stack Statistics
(6) Debug Display
(7) hardware Information

access the debug display screen and there should be a softkey to  =

erase all current messages.

/Wes

On Jan 10, 2006, at 1:14 PM, Erick Bergquist wrote:

Anyone ever see these in event logs on a phone that is
up and running just fine and has no problems, other
then this in event logs? I thought this was a bug in a
older 6.x phoneload but this is 7.2(2). I have also
seen this on a system where they use 7.0(2).

EventID: 0xE0000003 (3) - Error: StationEventAlert -
Station alert.
TCP ProcessID: 2.100.132.90858816
Device Text: 6: Name=3DSEP0014F2E98072
Load=3D7.2(2.0)File Not Found

Thanks


=

 ________________________________________
__
Yahoo! DSL =96 Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com

 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]

Thanks, but wouldn't a reboot of phone or unplugging
of phone and plugging it back in so it lost power
clear the debugs or are they stored in NVRAM?

--- Wes Sisk <wsisk@cisco.com> wrote:

> during one phone bootup the 7.2(2) load was not
> available from the  =

> TFTP server. tftp server may have been rebuilding or
> shutdown at the  =

> time.  Unfortunately those logs are not cleaned up
> consistently on  =

> the phone.  there is a way to clear the log so you
> can be certain you  =

> are only seeing new messages:
> =

> Under settings->(5)Status->(2)Network Statistics,
> the 3rd line shows the
> last phone reset reason.
> =

> It appears most of our phone loads have a debug
> display:
> 1. while onhook enter **##**3 on the keypad
> 2. look under settings->(5)Status
> =

> These new items may appear in the status menu:
> (5) Stack Statistics
> (6) Debug Display
> (7) hardware Information
> =

> access the debug display screen and there should be
> a softkey to  =

> erase all current messages.
> =

> /Wes
> =

> On Jan 10, 2006, at 1:14 PM, Erick Bergquist wrote:
> =

> Anyone ever see these in event logs on a phone that
> is
> up and running just fine and has no problems, other
> then this in event logs? I thought this was a bug in
> a
> older 6.x phoneload but this is 7.2(2). I have also
> seen this on a system where they use 7.0(2).
> =

> EventID: 0xE0000003 (3) - Error: StationEventAlert -
> Station alert.
>    TCP ProcessID: 2.100.132.90858816
>    Device Text: 6: Name=3DSEP0014F2E98072
> Load=3D7.2(2.0)File Not Found
> =

> Thanks
> =

> =

> 		=

>  ________________________________________
__
> Yahoo! DSL =EF=BF=BD Something to write home about.
> Just $16.99/mo. or less.
> dsl.yahoo.com
> =

>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> =

> =



 ________________________________________
__________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around =

http://mail.yahoo.com =

[ Post a follow-up to this message ]

Erick,

Here is what TAC told us: =


1. TFTP Caching
TFTP Caching is enabled on your server. This may cause a problem where =

the TFTP cache does not have the requested file in cache when a phone =

makes the request. When the phone reboots and makes the second request =

the phone would be in the cache. To get around this we can try disabling =

the TFTP caching.


-----Original Message-----
From: cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck
.ne=
ther.net] On Behalf Of Erick Bergquist
Sent: Wednesday, January 11, 2006 9:57 AM
To: Wes Sisk
Cc: ciscovoip
Subject: Re: [cisco-voip] Load 7.2(2.0) file not found error in event lo
g

Thanks, but wouldn't a reboot of phone or unplugging of phone and plugging =
it back in so it lost power clear the debugs or are they stored in NVRAM?

--- Wes Sisk <wsisk@cisco.com> wrote:

> during one phone bootup the 7.2(2) load was not available from the =

> TFTP server. tftp server may have been rebuilding or shutdown at the =

> time.  Unfortunately those logs are not cleaned up consistently on the =

> phone.  there is a way to clear the log so you can be certain you are =

> only seeing new messages:
> =

> Under settings->(5)Status->(2)Network Statistics, the 3rd line shows =

> the last phone reset reason.
> =

> It appears most of our phone loads have a debug
> display:
> 1. while onhook enter **##**3 on the keypad 2. look under =

> settings->(5)Status
> =

> These new items may appear in the status menu:
> (5) Stack Statistics
> (6) Debug Display
> (7) hardware Information
> =

> access the debug display screen and there should be a softkey to erase =

> all current messages.
> =

> /Wes
> =

> On Jan 10, 2006, at 1:14 PM, Erick Bergquist wrote:
> =

> Anyone ever see these in event logs on a phone that is up and running =

> just fine and has no problems, other then this in event logs? I =

> thought this was a bug in a older 6.x phoneload but this is 7.2(2). I =

> have also seen this on a system where they use 7.0(2).
> =

> EventID: 0xE0000003 (3) - Error: StationEventAlert - Station alert.
>    TCP ProcessID: 2.100.132.90858816
>    Device Text: 6: Name=3DSEP0014F2E98072 Load=3D7.2(2.0)File Not Found
> =

> Thanks
> =

> =

> 		=

>  ________________________________________
__
> Yahoo! DSL =EF=BF=BD Something to write home about.
> Just $16.99/mo. or less.
> dsl.yahoo.com
> =

>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> =

> =



 ________________________________________
__________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around http://mail=
.yahoo.com  ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]

Thanks, tried this to and didn't clear the errors in
event log.

The phone is up and running fine, no visible or
apparrent issues on phone other then this annoying
entry in event log every few seconds. The phone has
been rebooted several times, cat5 unplugged (no power
for a minute) then cat5 plugged back in and comes back
and works normal, but errors in event about file not
found. Only 1 phone doing this error in event logs and
all other phones using the same load fine also. =


It's just the errors are annoying and put noise in
logs.

--- "Leetun, Rob" <rleetun@co.boulder.co.us> wrote:

> Erick,
> =

> Here is what TAC told us: =

> =

> 1. TFTP Caching
> TFTP Caching is enabled on your server. This may
> cause a problem where =

> the TFTP cache does not have the requested file in
> cache when a phone =

> makes the request. When the phone reboots and makes
> the second request =

> the phone would be in the cache. To get around this
> we can try disabling =

> the TFTP caching.
> =

> =

> -----Original Message-----
> From: cisco-voip-bounces@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net] On
> Behalf Of Erick Bergquist
> Sent: Wednesday, January 11, 2006 9:57 AM
> To: Wes Sisk
> Cc: ciscovoip
> Subject: Re: [cisco-voip] Load 7.2(2.0) file not
> found error in event log
> =

> Thanks, but wouldn't a reboot of phone or unplugging
> of phone and plugging it back in so it lost power
> clear the debugs or are they stored in NVRAM?
> =

> --- Wes Sisk <wsisk@cisco.com> wrote:
> =
 
> available from the =
 
> or shutdown at the =
 
> consistently on the =
 
> be certain you are =
 
[vbcol=seagreen] 
> the 3rd line shows =
 
[vbcol=seagreen] 
> look under =
 
[vbcol=seagreen] 
[vbcol=seagreen] 
> be a softkey to erase =
 
[vbcol=seagreen] 
[vbcol=seagreen] 
> wrote: 
[vbcol=seagreen] 
> that is up and running =
 
> event logs? I =
 
> but this is 7.2(2). I =
 
> 7.0(2). 
[vbcol=seagreen] 
> - Station alert. 
> Load=3D7.2(2.0)File Not Found 
[vbcol=seagreen] 
[vbcol=seagreen] 
[vbcol=seagreen] 
[vbcol=seagreen] 
[vbcol=seagreen] 
> https://puck.nether.net/mailman/listinfo/cisco-voip 
[vbcol=seagreen] 
[vbcol=seagreen]
> =

> =

>  ________________________________________
__________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam
> protection around http://mail.yahoo.com
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> =



 ________________________________________
__________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around =

http://mail.yahoo.com =

[ Post a follow-up to this message ]

it's stored in nvram.

On Jan 11, 2006, at 11:57 AM, Erick Bergquist wrote:

Thanks, but wouldn't a reboot of phone or unplugging
of phone and plugging it back in so it lost power
clear the debugs or are they stored in NVRAM?

--- Wes Sisk <wsisk@cisco.com> wrote:

> during one phone bootup the 7.2(2) load was not
> available from the
> TFTP server. tftp server may have been rebuilding or
> shutdown at the
> time.  Unfortunately those logs are not cleaned up
> consistently on
> the phone.  there is a way to clear the log so you
> can be certain you
> are only seeing new messages:
>
> Under settings->(5)Status->(2)Network Statistics,
> the 3rd line shows the
> last phone reset reason.
>
> It appears most of our phone loads have a debug
> display:
> 1. while onhook enter **##**3 on the keypad
> 2. look under settings->(5)Status
>
> These new items may appear in the status menu:
> (5) Stack Statistics
> (6) Debug Display
> (7) hardware Information
>
> access the debug display screen and there should be
> a softkey to
> erase all current messages.
>
> /Wes
>
> On Jan 10, 2006, at 1:14 PM, Erick Bergquist wrote:
>
> Anyone ever see these in event logs on a phone that
> is
> up and running just fine and has no problems, other
> then this in event logs? I thought this was a bug in
> a
> older 6.x phoneload but this is 7.2(2). I have also
> seen this on a system where they use 7.0(2).
>
> EventID: 0xE0000003 (3) - Error: StationEventAlert -
> Station alert.
>    TCP ProcessID: 2.100.132.90858816
>    Device Text: 6: Name=3DSEP0014F2E98072
> Load=3D7.2(2.0)File Not Found
>
> Thanks
>
>
> 		=

>  ________________________________________
__
> Yahoo! DSL =EF=BF=BD Something to write home about.
> Just $16.99/mo. or less.
> dsl.yahoo.com
>
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>


 ________________________________________
__________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[ Post a follow-up to this message ]