Header Only - DO NOT REMOVE - Extreme Networks
Question

Extreme Wireless - V10.41 - Remote Shell - Limitations


Userlevel 6
Because i support several bigger Identify WLAN environments for customers i love the new V10.41 feature of having a quick "remote shell" to an AP for a deeper analyses!

But in real life usage there are several limitation that reduce the advantage this feature dramatically:

+ There is no copy and paste
+ no logging option (compare to a putty client)
+ no resizing of the screen possible if you need more space (means more columns)
(try several browsers - open a GTAC case - this is now a FR 😢 )
+ Only AP38xx and AP39xx are supported - AP37xx are not included
(not clear why AP37xx are not offering this)

i hope there happens some improvements in the near future to make this feature more powerful in our daily business real life usage.

Regards

10 replies

Userlevel 5
Hello Matthias,

I completely agree with that.

Best regards
Stephan
Userlevel 7
I'm just curious, what information do you pull or configure from the ap shell that's not available in the web gui?
Userlevel 6
Doug wrote:

I'm just curious, what information do you pull or configure from the ap shell that's not available in the web gui?

Hi Doug,

that is funny - you wonna tell me that is would be not so seroius that basic functions are not able if you use remote shell, because most customers do not need that ?

I am sure that PLM trigger this feature because there is a seroius demand and i am also sure competitive products offer that too.

So i hope because Netsight guys have the same problems with their WebTerminal improvements will return in near future versions.

Why AP37xx APs not kicked out to this feature although they are fully supported with 10.41.xx is not explainable to me.

Regards,
Matthias
Userlevel 5
Hello Doug,

For me the most used commands via shell are:

set authipaddr...

and

tail -f /tmp/log/ap.log

for debugging if problems occur and and then you need the above mentioned functions (like via putty).

Best regards
Stephan
SH wrote:

Hello Doug,

For me the most used commands via shell are:

set authipaddr...

and

tail -f /tmp/log/ap.log

for debugging if problems occur and and then you need the above mentioned functions (like via putty).

Best regards
Stephan

Being able to grep the logs for a particular client is also very helpful, can't do that in a gui (not that you can get the AP logs in the gui anyway?)
Userlevel 1
SH wrote:

Hello Doug,

For me the most used commands via shell are:

set authipaddr...

and

tail -f /tmp/log/ap.log

for debugging if problems occur and and then you need the above mentioned functions (like via putty).

Best regards
Stephan

I fully agree with the intial post and Stephans comment using the shell for troubleshooting and debugging the for example ap.log files.

There is no feature in the gui for that.
Userlevel 7
SH wrote:

Hello Doug,

For me the most used commands via shell are:

set authipaddr...

and

tail -f /tmp/log/ap.log

for debugging if problems occur and and then you need the above mentioned functions (like via putty).

Best regards
Stephan

https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-Collect-Access-Point-Logging-Inform...

Run your test then generate your log from the GUI, trace bundle includes the ap.log
Userlevel 7
SH wrote:

Hello Doug,

For me the most used commands via shell are:

set authipaddr...

and

tail -f /tmp/log/ap.log

for debugging if problems occur and and then you need the above mentioned functions (like via putty).

Best regards
Stephan

Or use the AP log mgmt to upload all AP logs 1,2,4 or 6x per day to local or remote....

SH wrote:

Hello Doug,

For me the most used commands via shell are:

set authipaddr...

and

tail -f /tmp/log/ap.log

for debugging if problems occur and and then you need the above mentioned functions (like via putty).

Best regards
Stephan

Yeah, I have the log collection enabled, which is great for historical analysis, but when I'm in the guts of debugging a problem using the shell is much quicker than downloading a trace and unzipping it all the time. So s/get/view/ the AP logs in the gui is what I meant.
Userlevel 5
SH wrote:

Hello Doug,

For me the most used commands via shell are:

set authipaddr...

and

tail -f /tmp/log/ap.log

for debugging if problems occur and and then you need the above mentioned functions (like via putty).

Best regards
Stephan

Like James said the live view via SSH is quicker while debugging and like Matthias said if the CLI is not needed why do we have the CLI via Web as feature in the new release 😉?

Best regards
Stephan

Reply