Cisco Context-Aware Service Configuration Guide Release 7.0
Chapter 4: Configuring and Viewing System Properties
Downloads: This chapterpdf (PDF - 583.0KB) The complete bookPDF (PDF - 10.62MB) | Feedback

Configuring and Viewing System Properties

Table Of Contents

Configuring and Viewing System Properties

Editing General Properties and Viewing Performance

Editing General Properties

Viewing Performance Information

Modifying NMSP Parameters

Viewing Active Sessions on a System

Adding and Deleting Trap Destinations

Adding Trap Destinations

Deleting Trap Destinations

Viewing and Configuring Advanced Parameters

Viewing Advanced Parameters Settings

Initiating Advanced Parameters

Configuring Advanced Parameters

Initiating Advanced Commands

Rebooting or Shutting Down a System

Clearing the System Database

Defragmenting The Database


Configuring and Viewing System Properties


This chapter describes how to configure and view system properties on the mobility services engine.

This chapter contains the following sections:

Editing General Properties and Viewing Performance

Modifying NMSP Parameters

Viewing Active Sessions on a System

Adding and Deleting Trap Destinations

Viewing and Configuring Advanced Parameters

Initiating Advanced Parameters

Editing General Properties and Viewing Performance

General Properties—You can use WCS to edit the general properties of a mobility services engine such as contact name, username, password, services enabled on the system, enabling or disabling a service or enabling the mobility services engine for synchronization. See the "Editing General Properties" section.


Note You would use the general properties to modify the username and password that you defined during initial setup of the mobility services engine.


Performance—You can use WCS to view CPU and memory use for a given mobility services engine. See the "Viewing Performance Information" section.

This section consists of the following topics:

Editing General Properties

Viewing Performance Information

Editing General Properties

To edit the general properties of a mobility services engine, follow these steps:


Step 1 In WCS, choose Services > Mobility Services to display the Mobility Services page.

Step 2 Click the name of the mobility services engine you want to edit. Two tabs appear with the following headings: General and Performance (see Figure 4-1).

Figure 4-1 Services > Mobility Services > General Properties

If the General Properties page does not appear by default, from the left sidebar menu, choose System > General Properties.

Step 3 Modify the parameters as appropriate in the General page. Table 4-1 describes each parameter.

Table 4-1 General Properties  

Parameter
Configuration Options

Contact Name

Enter a contact name for the mobility services engine.

Username

Enter the login username for the WCS server that manages the mobility services engine. This replaces any previously defined username including any set during initial setup.

Password

Enter the login password for the WCS server that manages the mobility services engine.This replaces any previously defined password including any set during initial setup.

Port

8001

This is a default value.

HTTP

Select the Enable check box to enable HTTP. By default, HTTPS is enabled.

Note HTTP is primarily enabled to allow third-party applications to communicate with the mobility services engine.

Note WCS always communicates through HTTPS.

Legacy Port

Enter the mobility services port number that supports HTTPS communication. The Legacy HTTPS option must also be enabled.

Legacy HTTPS

This parameter does not apply to mobility services engines. It applies only to location appliances.

Delete synchronized service assignments and enable synchronization

Select this check box if you want to permanently remove all service assignments from the mobility services engine. This option will show up only if the delete synchronized service assignments check box was unselected while adding an mobility services engine.

Mobility Services

To enable a service (CAS, wIPS) on a mobility services engine, select the Admin Status check box next to the service you want to enable.

Note Once selected, the service displays as Up (active). All inactive services are noted as Down (inactive) on the selected (current) system and on the network.

Note CAS and wIPS can operate on a mobility services engine at the same time.

Note All mobility services engines are shipped with an evaluation license of CAS and wIPS. Evaluation copies are good for a period of 60 days (480 hours) and have preset device limits for each service. Licenses are usage-based (time is decremented by the number of days you use it rather than by calendar days passed).

Note When you are applying an evaluation license to MSE, the behavior is slightly different from a permanent license. Firstly, an evaluation license for MSE will only increase the evaluation period but not the count of the licensed elements. Secondly, when an evaluation license is applied, there is no license file copied to MSE. Instead the update is made directly in the MSE database. Also, you will not see the license information under License Center > Files > MSE page.

Click the here link to see the number of devices that can be assigned for the current system (see Figure 4-1).

On the License Center page (see Figure 4-2), click MSE sidebar menu option to see details on licenses for all mobility services engines on the network (see Figure 4-3).

Note For more information on purchasing and installing licenses, see the following URL:

http://www.cisco.com/en/US/prod/collateral/wireless/ps9733/ps9742/data_sheet_c07-473865.html



Note The following tcp ports are in use on a mobility services engine (MSE) in Release 6.0: tcp 22: MSE SSH port, tcp 80: MSE HTTP port, tcp 443: MSE HTTPS port, tcp 1411: AeroScout, tcp 1999: AeroScout internal port, tcp 4096: AeroScout notifications port, tcp 5900X: AeroScout (X could vary from 1 to 10), and tcp 8001: Legacy port. Used for location APIs.



Note The following udp ports are in use on a mobility services engine (MSE) in release 6.0: udp 123: NTPD port (open after NTP configuration), udp 162: AeroScout SNMP, udp/tcp 4000X: AeroScout proxy (X could vary from 1 to 5), udp 12091: AeroScout devices (TDOA Wi-Fi Receivers, chokepoints), udp 12092: AeroScout devices (TDOA Wi-Fi Receivers, chokepoints), udp 32768: Location internal port, udp 32769: AeroScout internal port, and udp 37008: AeroScout internal port.


Figure 4-2 License Summary for Selected Mobility Services Engine

Figure 4-3 License Summary for All Mobility Services Engines

Step 4 Click Save to update the WCS and mobility services engine databases.


Viewing Performance Information

To view performance details, follow these steps:


Step 1 In WCS, choose Services > Mobility Services to display the Mobility Services page.

Step 2 Click the name of the mobility services engine you want to view. Two tabs appear with the following headings: General and Performance.

Step 3 Click the Performance tab (see Figure 4-4).

Click a time period (such as 1w) on the y-axis to see performance numbers for periods greater than one day.

To view a textual summary of performance, click the second icon under CPU.

To enlarge the screen, click the icon at the lower right.

Figure 4-4 CPU and Memory Performance


Modifying NMSP Parameters

Network Mobility Services Protocol (NMSP) is the protocol that manages communication between the mobility services engine and the controller. Transport of telemetry, emergency, and chokepoint information between the mobility services engine and the controller is managed by this protocol.


NoteNo change in the default parameter values is recommended unless the network is experiencing slow response or excessive latency.

Telemetry, emergency and chokepoint information is only seen on controllers and WCS installed with Release 4.1 software or later.

The TCP port (16113) that the controller and mobility services engine communicate over must be open (not blocked) on any firewall that exists between the controller and mobility services engine for NMSP to function.

To configure NMSP parameters, follow these steps:


Step 1 In WCS, choose Services > Mobility Services.

Step 2 Click the name of the mobility services engine whose properties you want to edit.

Step 3 Choose System > NMSP Parameters. The configuration options appear.

Step 4 Modify the NMSP parameters as appropriate. Table 4-2 describes each parameter.

Table 4-2 NMSP Parameters  

Parameter
Description

Echo Interval

How frequently an echo request is sent from a mobility services engine to a controller. The default value is 15 seconds. Allowed values range from 1 to 120 seconds.

Note If a network is experiencing slow response, you can increase the values of the echo interval, neighbor dead interval, and the response timeout values to limit the number of failed echo acknowledgements.

Neighbor Dead Interval

The number of seconds that the mobility services engine waits for a successful echo response from the controller before declaring the neighbor dead. This timer begins when the echo request is sent.

The default value is 30 seconds. Allowed values range from 1 to 240 seconds.

Note This value must be at least two times the echo interval value.

Response Timeout

How long the mobility services engine waits before considering the pending request as timed out. The default value is 1 second. Minimum value is 1. There is no maximum value.

Retransmit Interval

Interval of time that the mobility services engine waits between notification of a response timeout and initiation of a request retransmission. The default setting is 3 seconds. Allowed values range from 1 to 120 seconds.

Maximum Retransmits

The maximum number of retransmits that are sent in the absence of a response to any request. The default setting is 5. Allowed minimum value is 0. There is no maximum value.


Step 5 Click Save to update the WCS and mobility services engine databases.


Viewing Active Sessions on a System

You can view active user sessions on the mobility services engine.

For every session, WCS displays the following information:

Session identifier

IP address from which the mobility services engine is accessed

Username of the connected user

Date and time when the session started

Date and time when the mobility services engine was last accessed

How long the session was idle since it was last accessed

To view active user sessions, follow these steps:


Step 1 In WCS, choose Services > Mobility Services.

Step 2 Click the name of the mobility services engine for which you want to view active sessions.

Step 3 Choose System > Active Sessions.


Adding and Deleting Trap Destinations

You can specify which WCS or Cisco Security Monitoring, Analysis, and Response System (CS-MARS) network management platform is the recipient of SNMP traps generated by the mobility services engine.

When a user adds a mobility services engine using WCS, that WCS platform automatically establishes itself as the default trap destination. If a redundant WCS configuration exists, the backup WCS is not listed as the default trap destination unless the primary WCS fails and the backup system takes over. Only an active WCS is listed as a trap destination.

This section consists of the following topics:

Adding Trap Destinations

Deleting Trap Destinations

Adding Trap Destinations

To add a trap destination, follow these steps:


Step 1 In WCS, choose Services > Mobility Services.

Step 2 Click the name of the mobility services engine for which you want to define a new SNMP trap destination server.

Step 3 Choose System > Trap Destinations.

Step 4 From the Select a command drop-down list, choose Add Trap Destination. Click Go.

Step 5 Enter the IP address of the destination SNMP server.

Step 6 The Port number default of 162 is auto-populated. You can modify this as needed.

Step 7 The Community default value of public is auto-populated. You can modify this as needed.

Step 8 The Destination default value of other auto-populates.


Note All trap destinations are identified as other except for the automatically created default trap destination.


Step 9 Click Save.

You are returned to the trap destinations summary page and the newly defined trap is listed.


Deleting Trap Destinations

To delete a trap destination, follow these steps;


Step 1 In WCS, choose Services > Mobility Services.

Step 2 Click the name of the mobility services engine for which you want to delete a SNMP trap destination server.

Step 3 Choose System > Trap Destinations.

Step 4 Select the check box next to the trap destination entry that you want to delete.

Step 5 From the Select a command drop-down list, choose Add Trap Destination. Click Go.

Step 6 In the message box that appears, click OK to confirm deletion.


Viewing and Configuring Advanced Parameters

In the WCS Advanced Parameters page (see Figure 4-5) you can view general system level settings of the mobility services engine and configure monitoring parameters.

Refer to the "Viewing Advanced Parameters Settings" section to view current system- level advanced parameters.

Refer to the "Initiating Advanced Commands" section to modify the current system- level advanced parameters or initiate advanced commands such as system reboot, system shutdown, clear a configuration file, or defragment the system database.

Viewing Advanced Parameters Settings

To view the advanced parameter settings of the mobility services engine, follow these steps:


Step 1 In WCS, choose Services > Mobility Services.

Step 2 Click the name of a mobility services engine to view its status.

Step 3 Choose System > Advanced Parameters (see Figure 4-5).

Figure 4-5 Services > Mobility Services > System > Advanced Parameters


Initiating Advanced Parameters

The Advanced Parameters section of WCS enables you to set the number of days events are kept and set session time out values. It also enables you to initiate a system reboot or shutdown, clear the system database, or defragment a database.


Note You can use WCS to modify troubleshooting parameters for a mobility services engine or a location appliance.


In the Advanced Parameters page, you can use WCS:

To set how long events are kept and how long before a session timesout.

For more information, see the Configuring Advanced Parameters.

To initiate a system reboot or shutdown, clear the system database, or defragment a database.

For more information, see the Initiating Advanced Commands.

Configuring Advanced Parameters

To configure advanced parameters, follow these steps:


Step 1 Choose Services > Mobility Services.

Step 2 Click the name of the mobility service whose properties you want to edit.

Step 3 From the left sidebar menu, choose System > Advanced Parameters.

Step 4 View or modify the advanced parameters as necessary.

General Information

Advanced Parameters

Number of Days to keep Events—Enter the number of days to keep logs. Change this value as required for monitoring and troubleshooting.

Session Timeout—Enter the number of minutes before a session times out. Change this value as required for monitoring and troubleshooting. Currently this option is not configurable for the mobility services engine but configurable for location appliance.

Cisco UDI

Product Identifier (PID)—The Product ID of the mobility services engine.

Version Identifier (VID)—The version number of the mobility services engine.

Serial Number (SN)—Serial number of the mobility services engine.

Advanced Commands

Reboot Hardware—Click to reboot the mobility services hardware. See Rebooting or Shutting Down a System for more information.

Shutdown Hardware—Click to turn off the mobility services hardware. See Rebooting or Shutting Down a System for more information.

Clear Database—Click to clear the mobility services database. See Clearing the System Database for more information. Unselect the Retain current service assignments in WCS check box to remove all existing service assignments from WCS and MSE. The resources have to be reassigned in the Services > Synchronize Services page. By default this option is selected.

Defragment Database—Click to initiate a defragmentation of the mobility services database. See Defragmenting The Database for more information.

Step 5 Click Save to update the WCS and mobility services engines databases.


Initiating Advanced Commands

You can initiate a system reboot or shutdown, clear the system database, or defragment a database by clicking the appropriate button in the Advanced Parameters page.

This section consists of the following topics:

Rebooting or Shutting Down a System

Clearing the System Database

Defragmenting The Database

Rebooting or Shutting Down a System

To reboot or shut down a mobility services engine, follow these steps:


Step 1 In WCS, choose Services > Mobility Services.

Step 2 Click the name of a mobility services engine you want to reboot or shut down.

Step 3 Choose System > Advanced Parameters (see Figure 4-5).

Step 4 In the Advanced Commands section of the page, click the appropriate button (Reboot Hardware or Shutdown Hardware).

Click OK in the confirmation dialog box to initiate either the reboot or shutdown process. Click Cancel to stop the process.


Clearing the System Database

To clear a mobility services engine configuration and restore its factory defaults, follow these steps:


Step 1 In WCS, click Services > Mobility Services.

Step 2 Click the name of the mobility services engine you want to configure.

Step 3 Choose System > Advanced Parameters.

Step 4 In the Advanced Commands section, unselect the Retain current service assignments in WCS check box to remove all existing service assignments from WCS and MSE.

The resources have to be reassigned in the Services > Synchronize Services page. By default this option is selected.

Step 5 In the Advanced Commands section, click Clear Database.

Step 6 Click OK to clear the mobility services engine database.


Defragmenting The Database

To defragment the database of a mobility services engine, follow these steps:


Step 1 In WCS, choose Services > Mobility Services.

Step 2 Click the name of a mobility services engine whose database you want to defragment.

Step 3 Choose System > Advanced Parameters (see Figure 4-5).

Step 4 In the Advanced Commands section, click Defragment Database.

Click OK in the confirmation dialog box to initiate the process. Click Cancel to stop the process.