If this is a re-occurring problem you could write a Perl script with
Net::Telnet and multithreading and have the script telnet in, turn on
debugging, and monitor the output for you and send only the relevant text to
screen.
Frank
-Original Message-
From: Lee Badman [mailto:[EMAIL PROTECTE
Badman [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 04, 2007 5:27 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Debug Cisco LWAPP
Thanks for the responses- the syslog option has merit, though WCS should
natively gather syslog as it's supposed to "manage"
Thanks for the responses- the syslog option has merit, though WCS should
natively gather syslog as it's supposed to "manage" the controllers-
this is one of those loose ends that hopefully gets better. As for the
AP templates- these only work if the AP joins the network- which
sometimes doesn't hap
Lee,
As others have mentioned, you can configure the controllers and APs to:
Using WCS you can create a controller template or configure each
controller. Under the Management section you can enable Syslog and put
in a single Syslog Host IP Address.
Also using WCS you can create an AP template
Someone has already mentioned the Syslog, and disabling the timeout.
One other thing. You can force AP's to associate to specific
controllers.
> -Original Message-
> From: Lee Badman [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 03, 2007 7:41 PM
> To: WIRELESS-LAN@LISTSERV.EDUCA
Can you send the output of the debug to a syslog server?
Ron Robinson
[EMAIL PROTECTED]
-Original Message-
From: Lee Badman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 6:41 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: [WIRELESS-LAN] Debug Cisco LWAPP
Am working w
Not sure how to tackle your entire problem, but you you prevent the timeouts by
changing your session timeout time. From the CLI, issue the following command:
config sessions timeout x
x is the number of minutes [0-160], 0 = no timeout.
On Wed, 3 Jan 2007, Lee Badman wrote:
> Da
