problem accessing WLSE's GUI after upgrading to 2.7.1

[micheljean]

Hi,

I tried to upgrade from 2.5 to 2.7 and then to 2.7.1, and I can't connect to WLSE anymore with web browser.

In fact, when i'm going to : http://wlse_ip_address:1741, i have the page where i can enter my login/password (which work with telnet as well as console connection) and then there's a loading page which never stops.

So then I tried to install 2.7 from the recovery CD... But same problem again.

Do you have any idea ?

Thanks for your help

PS : I already checked the possible solutions from "faq".

[rmushtaq]

Use the Recovery CD again, but this time, use the 'Local Installation of Recovery CD using the CD-ROM drive of appliance' method which to boot off the Recovery CD and not use the other Win2K method.

[o-ziltener]

What is the main benefit to use 2.7.1 instead 2.7?

[rmushtaq]

2.7.1 is mainly a maintenance/bug fix release in which not much new functionality is added. It is recommended over 2.7. See the Release Notes for 2.7.1 at: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cwparent/cw_1105/wlse/2_7_1/wlsern.htm#wp1046785 for details.

[wififofum]

Rizwan,

Where do we download the WLSE 2.7.1 patch?

Thanks,

[rmushtaq]

Goto http://www.cisco.com/kobayashi/sw-center/sw-wireless.shtml and follow the link for WLSE software which will take you to the download page.

[wififofum]

Thanks Rizwan!

[fbroussey]

Hi Rizwan

I've the same problem with a WLSE 2.9.

When I tried to connect to the WLSE 2.9 , I've the http prompt asking for my login/password but then i've a web page saying :

"WLSE is currently loading information. You will automatically be logged on when loading is complete"

But nothing !!! After a long time the message is : "session timeout "

I tried you solution : boot from the recovery CD but i still have the problem.

Any idea

[rmushtaq]

From the CLI, check to see what is the status of the Tomcat process, is it running or not?. Also, make sure that there is a default gateway ip address configured on the WLSE and that it can be pinged from the WLSE CLI. Also via the show tomcatlog from the CLI check to see if it show any error messages related to snmp

[fbroussey]

Hi rizwan,

Since my last message i 've used thr recovery CD to solve my pb but i've a new customer who has the same pb. And he has error related to snmp in the tomcatlog.

Errors are:

main message: snmplibhandler:about to initialize snmp errors found while parsing community strings

main fatal error: snmplibhandler:unable to read snmp communities files /var/adm/cscoets/config/cwsi/anisnmp.conf

What must he do ?

Thanks a lot for your help.

Fr?d?ric

[leighsanders]

hi, i am having the same problem, did you ever resolve this issue?

[fbroussey]

I found this command last day with a search on the cisco web site on "snmphandler" and i think this can be very helpfull. I will try it this morning with my customer:

reset device-snmp

Resets the WLSE's community strings to the default.

Caution This command is intended as a last resort; use it only if you cannot restart the WLSE in any other way. You will lose the community strings and must re-enter them as described below under Usage Guidelines.

Syntax Description

reset [ device-snmp | help ]

Usage Guidelines

This command is intended for restarting the WLSE if the tomcat process fails and the cause for the failure was corruption of the SNMP community string file. In that case, the Web interface will not be available, but the CLI will be available. The procedure follows.

Step 1 Log in to the CLI as admin <http://www.cisco.com/en/US/partner/products/sw/cscowork/ps3915/products_user_guide_chapter09186a008052db78.html> or as another user who has the System Administrator role.

Step 2 Run the service status command to check the status of the tomcat process. If the status is "Failed to run", proceed to the next step.

Step 3 Run the show tomcatlog command. It should contain these error messages about the SNMP community file:

MESSAGE: SnmpLibHandler: About to initialize SNMP Errors found while

parsing community strings.

FATAL ERROR: SnmpLibHandler: unable to read SNMP communities file:

/var/adm/CSCOets/config/cwsi/anisnmp.conf

Step 4 Run the reset device-snmp command.

? The file is reset and previously defined communties are lost.

? The community strings are reset to *.*.*.*:public::10:1:::public.

? The old SNMP community file is placed in the WLSE's log area. To view the file, select Admin > Appliance > Status > View Log File. Select the anisnmp.conf.log file.

Step 5 Log into the Web interface as admin <http://www.cisco.com/en/US/partner/products/sw/cscowork/ps3915/products_user_guide_chapter09186a008052db78.html> or as another user who has the System Administrator role.

Step 6 Select Devices > Discover > Device Credentials > SNMP Communities and re-enter your community strings.