Re: wepstatus

Provided your test gateway and endpoint
were running consistently within the set period, then it would seems to
me there's some malfunction in your TME! Unfortunately I don't have any
"internals" document I can refer you to with regards to 'wepstatus'.
Hope you find help.

Kindly,
Napo
 
***************************************************************
JPMorganChase - Systems & Service Management Tools Engineer
Tel: 614-213-8599
Pager: 888-636-2381
"If you look in your dictionary, you'll find that the meaning of the
word 'single' is not single!" - UNKNOWN
************************************************************* 


Joel N Mokoetle

Christopher J Petrina <cjp8@xxxxxxxxxxxxxxxx> Sent by: owner-tme10@xxxxxxxxxxxxxxxx 02/28/2005 05:15 PM Please respond to tme10

To:        tme10@xxxxxxxxxxxxxxxx         cc:                 Subject:        Re: [tme10] wepstatus

Correct I understand that it reads from a cache file.  We have epcheck_interval
at 3600 seconds (1 hour).   The problem is that I can verify that
a endpoint is alive and wepstatus shows connected.  some time later
under 1 hour I can run the wepstatus command again and the same device
will now show unreachable.  And if I do a wep eplabel status 1 it
shows aliev again.  I am trying to understand why it always reverts
back to unavailable.   we also have the diag_interval ont he end point
itself set to check every 2600 seconds.

joel_n_mokoetle@xxxxxxxxxxx
Sent by: owner-tme10@xxxxxxxxxxxxxxxx

02/28/2005 05:04 PM

Please respond to
tme10@xxxxxxxxxxxxxxxx

To	tme10@xxxxxxxxxxxxxxxx
cc
Subject	Re: [tme10] wepstatus

Hi Christopher, 

The wepstatus command reads from the gateways cache. In other words its
gives the last known status of the endpoint as at the last time the gateway
checked per the interval configured for the checks. The following will
give you the current status, and force the gateways to refresh it's knowledge
of the endpoint's status: 
wep endpoint_label status 1 

Hope that helps, 
Napo 

***************************************************************
JPMorganChase - Systems & Service Management Tools Engineer
Tel: 614-213-8599
Pager: 888-636-2381
"If you look in your dictionary, you'll find that the meaning of the
word 'single' is not single!" - UNKNOWN
************************************************************* 


Joel N Mokoetle

Christopher J Petrina <cjp8@xxxxxxxxxxxxxxxx> Sent by: owner-tme10@xxxxxxxxxxxxxxxx 02/28/2005 03:57 PM Please respond to tme10

To:        tme10@xxxxxxxxxxxxxxxx       cc:               Subject:        [tme10] wepstatus

Can someone give a more indepth detail about wepstatus command and function.
 I understand what its purpose is, and what it does.  What I
am looking for is HOW it does waht it does.  From things I have to
see I have to beleive that wepstatus is using some cache file which it
calls from.  This specifically when you issue a wepstatus -a.  

Our problem:  I issue a wepstatus -a and pull out all unreachable
entries.   I then do a wep endpoint  status on those in
the unreachable area, and a fair amoutn of them come back alive.  Thus
changing them from unrechable to connected.   15 minutes later if
I rerun the wepstatus -a command again the same devices that were alive
are back to unreachable.   

Is there some documentation about what wepstatus is actually doing when
it is checking?    we have increased epcheck_sess_timeout to
90 seconds and it still seems to be occuring. 

Thank you 
Chris Petrina 

________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service._______________________________________________________________

This electronic message contains information from MeadWestvaco
Corporation or subsidiary companies, which may be confidential,
privileged or otherwise protected from disclosure. The
information is intended to be used solely by the recipient(s)
named. If you are not an intended recipient, be aware that
any review, disclosure, copying, distribution or use of this
transmission or its contents is prohibited. If you have
received this transmission in error, please notify MeadWestvaco
immediately at postmaster@xxxxxxxxxxxxxxxxx
_______________________________________________________________________


This transmission may contain information that is privileged, confidential
and/or exempt from disclosure under applicable law. If you are not the
intended recipient, you are hereby notified that any disclosure, copying,
distribution, or use of the information contained herein (including any
reliance thereon) is STRICTLY PROHIBITED. If you received this transmission
in error, please immediately contact the sender and destroy the material
in its entirety, whether in electronic or hard copy format. Thank you.

________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service._______________________________________________________________

________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service._______________________________________________________________

This electronic message contains information from MeadWestvaco
Corporation or subsidiary companies, which may be confidential,
privileged or otherwise protected from disclosure. The
information is intended to be used solely by the recipient(s)
named. If you are not an intended recipient, be aware that
any review, disclosure, copying, distribution or use of this
transmission or its contents is prohibited. If you have
received this transmission in error, please notify MeadWestvaco
immediately at postmaster@xxxxxxxxxxxxxxxxx
_______________________________________________________________________