cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2576
Views
5
Helpful
4
Replies

MSE often unreachable from WCS

madhankumar.g
Level 1
Level 1

Hi,

I have upgraded MSE in my network from 7.0.105.0 to 7.0.201.204 a week ago.

After the upgrade, often MSE is going to unreachable state from WCS. A restart on MSE with "shutdown -r now" resolves the issue. But again after 2-3 days, it becomes unreachable from WCS. The IP reachability is fine from WCS and WCS communication password also matches.

"/etc/init.d/msed stop" command keep on showing "Shutting down MSE Platform ..." but never actually shuts down. only "shutdown -r now" helps.

getserverinfo is not giving any results.

Please let me know, what can be the possible issue.

Regards,

Madhan kumar G

4 Replies 4

madhankumar.g
Level 1
Level 1

Hi,

After restarting MSE, here is the output of Getserverinfo. Can "DB free size (kbytes): 0" be an issue?

Starting MSE Platform, Waiting to check the status.

MSE Platform is up, getting the status

-------------

Server Config

-------------

Product name: Cisco Mobility Service Engine

Version: 7.0.201.204

Hw Version: V01

Hw Product Identifier: AIR-MSE-3350-K9

Hw Serial Number: MXQ008A5S4

Use HTTP: false

Legacy HTTPS: false

Legacy Port: 8001

Log Modules: -1

Log Level: INFO

Days to keep events: 2

Session timeout in mins: 30

DB backup in days: 2

-------------

Services

-------------

Service Name: Context Aware Service

Service Version: 7.0.200.204

Admin Status: Enabled

Operation Status: Up

Service Name: Wireless Intrusion Protection Service

Service Version: 1.0.2077.0

Admin Status: Disabled

Operation Status: Down

--------------

Server Monitor

--------------

Server start time: Sun May 20 10:42:40 AST 2012

Server current time: Sun May 20 10:46:05 AST 2012

Server timezone: Asia/Riyadh

Server timezone offset: 10800000

Restarts: 4

Used Memory (bytes): 443802112

Allocated Memory (bytes): 994770944

Max Memory (bytes): 1908932608

DB virtual memory (kbytes): 0

DB virtual memory limit (bytes): 0

DB disk memory (bytes): 7104153216

DB free size (kbytes): 0

---------------

Active Sessions

---------------

Session ID: 12713

Session User ID: 2

Session IP Address: 172.18.5.15

Session start time: Sun May 20 10:43:06 AST 2012

Session last access time: Sun May 20 10:45:08 AST 2012

-------------

Context Aware Service

-------------

Total Active Elements(Wireless Clients, Tags, Rogue APs, Rogue Clients, Interferers, Wired Clients): 1107

Active Wireless Clients: 1107

Active Tags: 0

Active Rogue APs: 0

Active Rogue Clients: 0

Active Interferers: 0

Active Wired Clients: 0

Active Elements(Wireless Clients, Rogue APs, Rogue Clients, Interferers, Wired Clients, Tags) Limit: 6000

Active Sessions: 1

Wireless Clients Not Tracked due to the limiting: 250

Tags Not Tracked due to the limiting: 0

Rogue APs Not Tracked due to the limiting: 0

Rogue Clients Not Tracked due to the limiting: 0

Interferers Not Tracked due to the limiting: 0

Wired Clients Not Tracked due to the limiting: 0

Total Elements(Wireless Clients, Rogue APs, Rogue Clients, Interferers, Wired Clients) Not Tracked due to the limiting: 250

-------------------------

Context Aware Sub Services

-------------------------

Subservice Name: Aeroscout Tag Engine

Admin Status: Disabled

Operation Status: Down

Subservice Name: Cisco Tag Engine

Admin Status: Enabled

Operation Status: Up

Regards,

Madhan kumar G

Please make sure that your WCS is running 7.0.172.0 which is the compliant version with your current MSE version.

Check this:

http://www.cisco.com/en/US/docs/wireless/mse/3350/release/notes/mse7_0_201.204.html#wp1133800

cheers

--------------------------------------------------------------------------------------------

Please make sure to rate corrrect answer

Hi Maldehne,

Yes, The WCS is running on 7.0.172.0. Are you able to think of any other causes for the problem?

Regards,

Madhan kumar G

Welll Well,

So try the following my friend

have the logging level set to trace on your WCS , wait for the issue to happen , record the timestamp of the incident.

upload WCS logs to verify why MSE appears unreachable from WCS

Cheers

Review Cisco Networking products for a $25 gift card