5-13
Cisco 3310 Mobility Services Engine Getting Started Guide
OL-17304-02
Chapter 5 Initial Configuration
Verifying the Mobility Services Engine Software State
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 this command:
/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: 5.1.26.0
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: Fri May 23 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: 5.1.26.0
--------------
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
