nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Reset Enterasys Wireless Controller

anc

Hi Folks!

I want to reset an Enterasys Wireless Controller via CatTools but it seems that I can't use privileged mode (enable mode). If I do this manually I use the following commands (bold):

telnet <IP adddress>
Username: admin
Password: <Initial Password>
rt_wan1> enable
Enter password: <Enable Password>
rt_wan1# reset system

In CatTools I've added the device (as Enterasys.Matrix.Switch), entered the AAA account data and enable password. In the corresponding CatTools activitiy for resetting the device the "Enter commands in enable mode" option is ticked and the only command is "reset system".

If I activate the debug mode, following is logged for activitiy:

<NEWSESSION CatTools 3.5.0 7/8/2010 9:08:18 AM>
<PROTOCOL=Telnet>
<DEVICE TYPE=Enterasys.Matrix.Switch>
<ACTIVITY TYPE=Device.CLI.Send commands>
<ACTIVITY SCRIPT=C:\Program Files\CatTools3\Scripts\Client.Device.CLI.Send commands.txt>
<USERS NAME FOR DEVICE=Enterasys Wireless Controller>
<C OK 9:08:19 AM><R-9:08:19 AM>[13][10][13][10]Copyright (c) 2005 - 2008 Enterasys, Inc. All rights reserved.[13][10][10][13][10][13][10][13][00]Username: <W-9:08:19 AM>admin[13]<R-9:08:19 AM>a<R-9:08:19 AM>dmin[10][13][00]Password: <W-9:08:19 AM><Password removed>[13]<R-9:08:19 AM>[10][13][00]<R-9:08:19 AM>[13][10]rt_wan1> <W-9:08:19 AM>[13]<R-9:08:19 AM>[10][13][00]<R-9:08:19 AM>rt_wan1> <W-9:08:20 AM>disable<R-9:08:20 AM>d<R-9:08:20 AM>isable<W-9:08:20 AM>[13]<R-9:08:20 AM>[10][13][00]<R-9:08:20 AM>Unrecognized command in this mode: disable[13][10]rt_wan1> <W-9:08:20 AM>[13]<R-9:08:20 AM>[10][13][00]<R-9:08:20 AM>rt_wan1> <W-9:08:20 AM>exit[13]<D 9:08:20 AM>
<SCRIPT VALUES>
<HOSTNAME="rt_wan1">
<PROMPT VTY="rt_wan1#">
<PROMPT ENABLE="rt_wan1>">
<PROMPT CONFIG="rt_wan1(">

I suppose there's no "enable" command because CatTools thinks it's in enable mode after first login already (according to given script values). Do you have any suggestions for me? Can I change these values or something else?

Find more posts tagged with

Accepted answers

All comments

Spartacus

Hi anc,

The only Enterasys device types in CatTools which negotiate 'enable' mode, are the Enterasys.Router and Enterasys.XSR1800.

Try using one of these scripts and see if you get better luck with is supporting your Enterasys Wireless Controller.

If you don't get any luck, then you may want to raise a support ticket as a feature request and include (as a zip file) a PuTTY or similar session capture from your device, so we have something to review. The following KB article lists the type of information we need within the capture: http://www.kiwisyslog.com/kb/how-to:-get-support-for-your-device-added-to-cattools/

Regards,

Steve

anc

Thanks for your reply.

I changed the device to Enterasys.Router.General and now it sends the enable command. One step further. But now it doesn't send the "reset system" command when it's in privileged mode because it's waiting for prompt. But the rt_wan1# prompt was still received. Do you have any suggestion?

<NEWSESSION CatTools 3.5.0 7/9/2010 8:54:49 AM>
<PROTOCOL=Telnet>
<DEVICE TYPE=Enterasys.Router.General>
<ACTIVITY TYPE=Device.CLI.Send commands>
<ACTIVITY SCRIPT=C:\Program Files\CatTools3\Scripts\Client.Device.CLI.Send commands.txt>
<USERS NAME FOR DEVICE=Enterasys Wireless Controller>
<C OK 8:54:49 AM><R-8:54:49 AM>[13][10][13][10]Copyright (c) 2005 - 2008 Enterasys, Inc. All rights reserved.[13][10][10][13][10][13][10][13][00]Username: <W-8:54:49 AM>admin[13]<R-8:54:50 AM>a<R-8:54:50 AM>dmin[10][13][00]Password: <W-8:54:50 AM>%fhb@1865%[13]<R-8:54:50 AM>[10][13][00]<R-8:54:50 AM>[13][10]rt_wan1> <W-8:54:50 AM>[13]<R-8:54:50 AM>[10][13][00]<R-8:54:50 AM>rt_wan1> <W-8:54:50 AM>enable[13]<R-8:54:50 AM>e<R-8:54:51 AM>nable[10][13][00][13][10]Enter password: <W-8:54:51 AM><Password removed>[13]<R-8:54:51 AM>[10][13][00]<R-8:54:51 AM>[13][10]rt_wan1# SYS Jul 09 06:29:23.481838 NOTICE User admin(telnetd) switched to enable mode[13][10]
================================================================================
WFMDRetVal=1 Waiting for: "[00]rt_wan1#"
WFMDRetVal=2 Waiting for: "Password:"
WFMDRetVal=3 Waiting for: "% Authentication failed."
WFMDRetVal=4 Waiting for: "Access denied"
WFMDRetVal=5 Waiting for: "Invalid password"
WFMDBuffer="[10][13][00][13][10]rt_wan1# sys jul 09 06:29:23.481838 notice user admin(telnetd) switched to enable mode[13][10]"
================================================================================

Spartacus

Thanks for the debuglog.

The problem appears to be that your device is intermittently returning a Null [00] before the device hostname prompt.

After initial login, it didn't "rt_wan1>", but during the routine where CatTools determines your device hostname (i.e. after CatTools sent a Carriage-Return [13]) it did: "[00]<R-8:54:50 AM>rt_wan1>"

After entering Enable mode, because the device didn't send the Null, CatTools reports this as an error as its expecting one: "[00]rt_wan1#"

I'd therefore recommend raising a support ticket as this will either require a script modification, or possibly a new script to be developed. Please remember send the device capture with the details requested in my previous posting.

Regards,

Steve

anc

Thanks for your hint. We use the free CatTools only so I suppose that we can't raise a support ticket. Is the use of a custom script the only way to solve this issue?

christineb

Hi Anc - it's ok if you can't raise a support ticket - it looks like we need to update or create a new script - so that's really a feature request. I can go ahead and enter that and we'll work to get it done in the next release or so (but as always, we can't make any promises as to exactly what release).

--Christine

anc

Hi!

It would be great if you can take this. I'll look forward to a new version.

Thanks a lot for your help!

christineb

Of course - sorry it isn't working for you now - but we'll get it in there. For internal folks, it's being tracked at FB#21505.

--Christine