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:
> Date: Wed, 03 Jan 2007 19:40:44 -0500
> From: Lee Badman <[EMAIL PROTECTED]>
> Reply-To: 802.11 wireless issues listserv
> <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>
> To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
> Subject: [WIRELESS-LAN] Debug Cisco LWAPP
>
> Am working with Aironet 1500 Mesh nodes, but have seen the same problem
> with converted legacy APs that don't play well with controllers for
> whatever reason. For troubleshooting, command line debug is required at
> the controllers. In my case, I have 16 controllers- and there's often no
> obvious rhyme or reason to what controller trouble APs will try to
> associate to. Cisco's current answer is to open 16 command line windows-
> 1 for each controller- and issue multiple debug commands in each while
> looking for signs of trouble. This can be challenging, as these windows
> time out for inactivity and the process has to be repeated until the
> trouble is found. WCS doesn't appear to aggregate this debug data...
>
> Has anyone else found a way of dealing with this debug process when it
> needs to be distibuted accross a large number of controllers?
>
>
>
>
> Lee Badman
> Network/Wireless Engineer
> Syracuse University
> 315 443-3003
>
> **********
> Participation and subscription information for this EDUCAUSE Constituent
> Group discussion list can be found at http://www.educause.edu/groups/.
>
--
Todd M. Hall
Sr. Network Analyst
Information Technology Infrastructure
Mississippi State University
[EMAIL PROTECTED]
662-325-0728 (phone)
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
