Cisco Network Module Enhanced Application Performance Assurance User Guide, Rel 2.0.0 - Operations [Cisco Application Networking Services Modules]

Table Of Contents

Operations

Upgrading NME-APA Module Firmware

Monitoring the Operational Status of the NME-APA Module

Displaying the Current Operational Status of the NME-APA Module

Displaying the NME-APA Module Version Information

Displaying the NME-APA Module Inventory

Displaying the System Uptime

Operations

This module describes basic operations necessary for managing the NME-APA module.

•Upgrading NME-APA Module Firmware

•Monitoring the Operational Status of the NME-APA Module

•Displaying the NME-APA Module Version Information

•Displaying the NME-APA Module Inventory

•Displaying the System Uptime

Upgrading NME-APA Module Firmware

Cisco distributes upgrades to the firmware on the NME-APA module. The firmware can be upgraded only from the ISR.

Monitoring the Operational Status of the NME-APA Module

Table 4-1 lists the operational states of the NME-APA module. You can monitor the operational status of the NME-APA module via:

•The Status LED on the NME-APA module front panel

•The show system operation-status CLI command

Table 4-1 NME-APA Module Operational States

NME-APA Module Operational Status

Description

Status LED State

Booting

Initial state after reset

Orange

Operational

NME-APA module becomes operational after completing the following process:

•Boot is completed

•Power self-tests are completed without failure

•Module configuration is applied

Flashing green

Warning

NME-APA module is fully operational (as above) but one of the following occurred:

•Link on one of the line ports is down

•Management port link is down

•Temperature raised above threshold

•Voltage not in required range

•Fans problem

•Power supply problem

•Insufficient space on the disk

Note: If the condition that caused the NME-APA module to be in Warning state is resolved (for example, link is up) the NME-APA module reverts to Operational state.

Flashing orange

Failure

System is in Failure state after Boot due to one of the following conditions:

•Power on test failure

•Three abnormal reboots in less than 20 minutes

•Module configured to enter Failure mode consequent to failure-induced reboot (this is configurable using CLI command)

Note Depending on the cause of failure, the management interface and the module configuration may or may not be active/available.

Red

Displaying the Current Operational Status of the NME-APA Module

show system operation-status

Step 1 From the NME-APA> prompt, type show system operation-status and press Enter.

Example:

This example shows how to display the current operational status of the NME-APA module.
NME-APA>show system operation-status 
System Operation status is Operational 
Port status is: 
Link on port #1 is down 
Link on port #2 is down
Displaying the NME-APA Module Version Information

show version

Use this command to display global static information on the NME-APA module, such as software version, image build time, system uptime, last open packages names and information on the SLI application assigned.

Step 1 From the NME-APA> prompt, type show version and press Enter.

Example:

This example shows how to display the NME-APA module version information.
NME-APA>show version 
NME-APA version: 0.1.4.8 
SCOS version: Version 3.1.0 Build 31-tcchen - Branch: TH 
Build time:Aug  4 2007, 02:47:08 
Module Type: NME-APA - 2xFE 
Module S/N:  FOC10222NMQ 
Chassis Type: C3845 
Chassis S/N:  FHK0831F06N 
SML Application information is:  
Application file: /root/tffs0/tmp.sli 
Application name: Starfleet SML Version 0.0.0 build 09 
Using Lib - PL_Starfleet_1.0.0 
Using Lib - Classifier_StarfleetB1.0.0 
Application help: Entry point of Starfleet 
Original source file: 
/auto/wskzhao/work/App/SML/Engage/Starfleet/v1.0.0/dev/src/com/pcube/apptemplate/main/temp
late_app_main.san 
Compilation date: Fri, August 03, 2007 at 00:18:11 
Compiler version: SANc v3.05 Build 16 gcc_codelets=true built on: Tue 03/01/2007 
09:59:46.;SME plugin v1.1 
Capacity option used: 'StarfleetDefaultNME-APA'. 
Logger status: Enabled 
Management agent interface version: SCE Agent 3.1.0 Build 177 
NME-APA  uptime is 3 days, 8 hours, 41 minutes, 8 seconds
Displaying the NME-APA Module Inventory

show inventory

Unique Device Identification (UDI) is a Cisco baseline feature that is supported by all Cisco modules. This feature allows network administrators to remotely manage the assets in their network by tracing specific devices through either CLI or SNMP. The user can display inventory information for a remote device via either:

•Entity MIB

•CLI show inventory command

The show inventory CLI command displays the following information:

•Device name

•Description

•Product identifier

•Version identifier

•Serial number

Step 1 From the NME-APA> prompt, type show inventory and press Enter.

Example:

This example shows how to display the inventory (UDI) of the NME-APA module.
NME-APA>show inventory 
NAME: "Cisco Service Control Engine", DESCR: "Integrated Service Engine for Application 
Performance Assur." 
PID: NME-APA-E3        , VID: V01, SN: FOC10222NMQ 
NME-APA>
Displaying the System Uptime

show system-uptime

Use this command to see how long the system has been running since the last reboot.

Step 1 From the NME-APA> prompt, type show system-uptime and press Enter.

Example:
NME-APA>show system-uptime 
NME-APA uptime is 21 minutes, 37 seconds 
NME-APA>