Introduction
Mobility Services Engine (MSE) platform status check up not working
Question
User has installed MSE on a Virtual Machine (Windows 2003 Server) and facing issues.
Getting Error while checking the state:-
etc/init.d/msed status
It loads a little and then shows Error:-
Starting MSE Platform, Waiting to check the Status
like 10 times and then an error comes up: "Failed to get the Status"
This Error comes when:-
- Restart
- Shutdown
- Configure and Save the configuration
- Executing getserverinfo command
The username and password hs been changed in order to associate it with WCS but when i go into the WCS and try to set it up, it says that there is an error in the username/password whereas i am using the same previously configured information in the MSE.
WCS version is 6.0 but not sure about MSE version since it doesn't show it due to the error on the status.
Answer
User deleted the Virtual Machine where he had that MSE and downloaded the new MSE v7 as a VM workstation and now works perfectly.
Question
How to configure RF Tags? If we have AP 1131-N-K9, why can't we use its 802.11a RF? When I do a show run it says its interface is down and I can bring it up because it mentions an error about not being compatible with a Regulatory Domain.
Answer
We have similar issues with certain AP that the a radio show down although it is admin enabled. Check on your AP if that a radio is admin disabled then you might have to enable it.
Question
Similar Issue with MSE 7.4.100 on hardware platform.
[root@MSE ~]# /etc/init.d/msed status
STATUS:
Health Monitor is running
Starting MSE Platform, Waiting to check the status.
Starting MSE Platform, Waiting to check the status.
Starting MSE Platform, Waiting to check the status.
...
MSE stops successfully, but doesn't start
[root@MSE ~]# /etc/init.d/msed restart
Stopping MSE Platform
.......................Flushing firewall rules: [ OK ]
Setting chains to policy ACCEPT: nat filter [ OK ]
Unloading iptables modules: [ OK ]
Starting MSE Platform
Flushing firewall rules: [ OK ]
Setting chains to policy ACCEPT: filter [ OK ]
Unloading iptables modules: [ OK ]
Starting Health Monitor, Waiting to check the status.
Health Monitor successfully started
Starting Admin process...
Started Admin process.
Database started successfully. Starting framework and services ...
Database started successfully. Starting framework and services ..........................
Answer
If the MSE is virtual then make sure that the resources are there that is required. Many time when we mess around with lab MSE this happens and usually a restart of the VM host fixes it. A few times it was basically me bringing up a new VM or reverting back to a snapshot that worked.
Verifying the Mobility Services Engine Software State
You can verify the mobility services engine software state at any time. In the mobility services engine CLI interface, enter: /etc/init.d/msed status
If the mobility services engine is running, the command output looks like this example:
-------------
Server Config
-------------
Product name: Cisco Mobility Service Engine
Version: x.x.x.x
Hw Version: none
Hw Product Identifier: none
Hw Serial Number: none
Use HTTPS: true
HTTPS Port: 443
Use HTTP: false
HTTP Port: 80
Legacy HTTPS: false
Legacy Port: 8001
Session timeout in mins: 30
DB backup in days: 0
--------------
Server Monitor
--------------
Start time: Wed Sept 30 15:24:36 EDT 2008
Server current time: Fri May 30 19:08:15 EDT 2008
Server timezone: America/New_York
Server timezone offset: -18000000
--------------
Service Engine (1):
--------------
NAME: Location Service
VERSION: x.x.x.x
--------------
Location Service Monitor
--------------
Log Modules: 262143
Log Level: INFO
Days to keep events: 2
Keep absent data in mins: 1440
Restarts: 1
Used Memory (bytes): 129851856 Allocated Memory (bytes): 3087007744
Max Memory (bytes): 3087007744
DB virtual memory (kbytes): 0
DB virtual memory limit (bytes): 256000000
DB disk memory (bytes): 4128768
DB free size (kbytes): 2856
Active Elements: 0
Active Clients: 0
Active Tags: 0
Active Rogues: 0
Active Elements Limit: 18000
Active Sessions: 0
Clients Not Tracked due to the limiting: 0
Tags Not Tracked due to the limiting: 0
Rogues Not Tracked due to the limiting: 0
Total Elements Not Tracked due to the limiting: 0
If the mobility services engine is not running, the command output looks like this example:
com.aes.common.util.AesException: Failed to connect to server: http://localhost:8001
at com.aes.client.AesClient.connect(AesClient.java:218)
at com.aes.location.test.AesAbstractTest.init(AesAbstractTest.java:181)
at com.aes.location.test.admin.AesTestGetServerInfo.main
(AesTestGetServerInfo.java:75)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.zerog.lax.LAX.launch(DashoA8113)
at com.zerog.lax.LAX.main(DashoA8113)
Reference
Verifying the Mobility Services Engine Software State
This document was generated from the following discussion: MSE platform status check up not working
