AXP 1.6 User Guide
Verifying and Troubleshooting
Downloads: This chapterpdf (PDF - 165.0KB) The complete bookPDF (PDF - 3.06MB) | Feedback

Verifying and Troubleshooting

Table Of Contents

Verifying and Troubleshooting

Viewing the Application Status Monitor

Viewing the Virtual Instance

Viewing Processes

Verifying Swap Space Support

Viewing Statistics

Viewing Application Data

Viewing Running Configuration

Verifying Resource Utilization Limits

Resource Limits in Cisco AXP EXEC mode

Resource Limits Detail in Cisco AXP EXEC mode

Resource Limits in Cisco AXP Application Service EXEC mode

Additional References


Verifying and Troubleshooting


This section consists of:

Viewing the Application Status Monitor

Viewing the Virtual Instance

Viewing Processes

Verifying Swap Space Support

Viewing Statistics

Viewing Application Data

Viewing Running Configuration

Verifying Resource Utilization Limits

Additional References

Viewing the Application Status Monitor

SUMMARY STEPS

1. app-service application-name

2. show status-monitor

3. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

app-service application-name

Enters application service EXEC mode.

Step 2 

show status-monitor

Shows the status of the application.

Step 3 

exit

Exits EXEC mode.

Viewing the Virtual Instance

SUMMARY STEPS

1. show app-service state [detail]

2. exit

3. app-service application-name

4. show state

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

show app-service state [detail]

Example:

SE-module> show app-service state

Displays a list of the installed applications and their state and health in system EXEC mode.

System EXEC mode is similar to privileged EXEC mode in Cisco IOS software.

State—Online or offline. Indicates if the virtual environment is running.

Health—Alive or down.

Health refers to the status of the internal application.

This status is communicated back to the Cisco AXP environment through an API call by the application monitoring process.

detail—For each offline application, shows a detailed reason why the application is offline.

Example:

se-Module# show app-service state detail   
APPLICATION     STATE               HEALTH
helloworld      online               ---             
myapp1         offline              ---
myapp2          offline              ---
myapp3          offline              ---
myapp4          offline              ---
myapp5          offline              ---
myapp6          offline              ---


APPLICATION      OFFLINE-REASON
myapp1        Administratively down [shutdown]
myapp2        Integrity check failed
myapp3        Invalid license
myapp4        Thirdparty authorization expired
myapp5        Application start failed
myapp6        Dependency check failed,upgrade 
required

Step 2 

exit

Exits EXEC mode.

Step 3 

app-service application-name

Enters application service EXEC mode.

Step 4 

show state [detail]

Displays the state and health of the specified application as:

State—Online, Offline, Pending-online, Pending-offline.

Health—Alive or Down.

detail—For each offline application, shows a detailed reason why the application is offline.

Viewing Processes

SUMMARY STEPS

1. app-service application-name

2. show process

3. show process running

4. show process all

5. show process pid process-id

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

app-service application-name

Enters application service mode.

Step 2 

show process

Shows all processes running in the application environment sorted by process ID in ascending order.

Step 3 

show process running

Shows all running processes in the application environment sorted by CPU usage in descending order.

Step 4 

show process all

Shows all processes running in the application environment with a summary of CPU and memory tasks in the application environment.

Step 5 

show process pid process-id

Shows the process, specified by the process ID, running in the application environment.

Verifying Swap Space Support

Use the show swap usage command in Application Service EXEC mode to view swap space usage of each application. The show tech-support command also displays the available swap partition on the blade.

SUMMARY STEPS

1. app-service application-name

2. show tech-support

3. show swap usage

4. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

app-service application-name

Enters application service EXEC mode.

Step 2 

show tech-support

Dumps information on the terminal provided by the third-party application.

Displays running-config, state, resource limits, and statistics of the application environment.

Executes the /bin/techsupport binary or script file to display application specific information if provided by the third-party application.

Displays the available swap partition on the blade and shows swap turned on or off.

Example: Swap turned on

swap is turned ON

Filename    Type       Size     Used  Priority
/dev/sda3   partition  1959920  0       -2

Example: Swap is turned off.

Swap is turned off.

Step 3 

show swap usage

Displays swap space usage of each application. This CLI is available inside each application's context.

Step 4 

exit

Exits application service EXEC mode.

Viewing Statistics

SUMMARY STEPS

1. app-service application-name

2. show statistics

3. show statistics app

4. end

5. show app-service statistics

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

app-service application-name

Enters application service mode.

Step 2 

show statistics

Displays statistics such as CPU utilization and memory for a virtual instance in the application environment.

Example:

CTX PROC  VSZ   RSS   userTIME  sysTIME  UPTIME  NAME
2    3    6.6M  2.5M  0m00s12   0m00s40  3h04m08 Test1 

CTX = context number for the virtual instance 
PROC = quantity of processes in the context
VSZ = number of pages of virtual memory
RSS = Resident set size limits for memory
userTime = utime User-mode CPU time accumulated
sysTime = ctime Kernel-mode CPU time accumulated
upTime = uptime

Step 3 

show statistics app

Displays statistics of third-party applications integrated into the application environment.

When you use this command, /bin/appstats is executed. The third-party application must provide the appstats file, in binary or script format, to plug in for its statistics.

Step 4 

end

Exits application service mode.

Step 5 

show app-service statistics

Example:

Se-Module> show app-service statistics

(System EXEC mode) Lists all the installed virtual instances and applications, and displays the application instance's memory and processing time information.

Viewing Application Data

SUMMARY STEPS

1. app-service application-name

2. show tech-support

3. show tech-support details

4. exit

In System EXEC mode:

5. show tech-support

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

app-service application-name

Enters application service mode.

Step 2 

show tech-support

Dumps information on the terminal provided by the
third-party application.

Displays a summary of diagnostic information of the application environment such as running-config, state, resource limits, and statistics.

Executes the /bin/techsupport binary or script file to display application-specific information if provided by the third-party application.

Step 3 

show tech-support details

Displays detailed technical support information for the third-party application. This command displays output from the show commands applied to the third-party application.

Step 4 

exit

Exits application service mode.

 

In system EXEC mode:

Note System EXEC mode is similar to Privileged EXEC mode in Cisco IOS software.

Step 5 

show tech-support

Displays a summary of diagnostic information.

Viewing Running Configuration

SUMMARY STEPS

1. app-service application-name

2. show running-configuration

3. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

app-service application-name

Enters application service mode.

Step 2 

show running-configuration

Displays running configuration only for the application environment.

Step 3 

exit

Exits application service mode.

Verifying Resource Utilization Limits

The following commands verify the resource utilization limits. The commands are variations of the
show resource limits command, executed in either Cisco AXP EXEC mode or Cisco AXP application EXEC mode.

Resource Limits in Cisco AXP EXEC mode

Resource Limits Detail in Cisco AXP EXEC mode

Resource Limits in Cisco AXP Application Service EXEC mode

Resource Limits in Cisco AXP EXEC mode

show resource limits (Cisco AXP EXEC Mode)

Use the show resource limits command in Cisco AXP EXEC mode to view the new resource limits.

Memory Limits

The memory limit displayed in the first example below is 100 MB—the sum of the tempfs memory and memory limit.

se-module> show resource limits 
APPLICATION       CPU(INDEX)   MEMORY(MB)   DISK(MB) LOG(MB)
perm_kernel_none    500          100         50       5

SYSTEM TOTAL
ALLOCATED          800          180          11089     -

RESOURCES
AVAILABLE          9200        828          99308     -

In the following example, the show resource limits memory command displays the total memory limit, which matches the memory limit of 100 MB in the previous show resource limits example:

se-Module> sh resource limits memory
APPLICATION            perm_kernel_none
Packaged Memory Limit     84 MB
Configured Memory Limit    -
Current Memory Limit      84 MB
Packaged TMPFS Limit      16 MB
Total Memory Limit        100 MB
Memory Wildcard           False

For resource limits that are not currently effective after the last change, the show resource limits command appends an * after each limit value to indicate that the new values are in a pending state.

If you do not execute the write memory command, the CLI configured value is lost after a reboot.

Table 13 shows example output values from the command show resource limits.

Values with * indicate that the user has not yet executed write memory and reload.

Table 13 show resource limits (EXEC Mode)

Application
CPU (Index)
Memory (MB)
Disk (MB)
Log (MB)

LinuxPackage

100

100*

10*

5

TestPackage

200*

400

20

5

System Total

500

550

210

Resources available

480

10

78200


Resource Limits Detail in Cisco AXP EXEC mode

The following example of the show resource limits detail command executed in the top level Cisco AXP EXEC Mode includes "tmpfs(mem)" (packaged tmpfs limit):

se-192-168-24-9# show resource limits detail
 APPLICATION CPU(INDEX) MEMORY(MB) DISK(MB)
   app_a_100       1000        799      500
    packaged       1000        100      500
  tmpfs(mem)                    16
    wildcard          0          0        0

   app_b_100       1000        116      500
    packaged       1000        100      500
  tmpfs(mem)                    16
    wildcard          0          0        0

    app_c_10       1000         26      500
    packaged       1000         10      500
  tmpfs(mem)                    16
    wildcard          0          0        0

         AXP        300        100    14855

SYSTEM TOTAL      15400       2024   148550

SYSTEM TOTAL
   ALLOCATED       3300       1041    16355

   RESOURCES
   AVAILABLE      12100        983   132195

    WILDCARD
   RESOURCES          0          0        0

       TOTAL
   RESOURCES
   AVAILABLE      12100        983   132195



* Please note that the values in some columns may not add up due to rounding
  errors


 The following AXP add-ons are INACTIVE:

     ADDON CPU(INDEX) MEMORY(MB) DISK(MB)

vserialapi         10          5        0
    iosapi         10          8        0
cli_plugin         10          5        0
  eventapi         10         27        0

Resource Limits in Cisco AXP Application Service EXEC mode

Use the show resource limits command in Cisco AXP application service EXEC mode to view the resource limits in Table 14.

In the following example, the show resource limits command is executed in application service EXEC mode for the application tmpfs_mem_32:

se-module(exec-tmpfs_mem_32)# show resource limits
              APPLICATION              tmpfs_mem_32
      Packaged Disk Limit                    400 MB
    Configured Disk Limit                         -
       Current Disk Limit                    400 MB
       Current Disk Usage                     87 MB
            Disk Wildcard                     False

       Packaged Cpu Limit                      1000
     Configured Cpu Limit                         -
        Current Cpu Limit                      1000
             Cpu Wildcard                     False


    Packaged Memory Limit                   30.0 MB
  Configured Memory Limit                         -
     Current Memory Limit                  613.7 MB
     Packaged TMPFS Limit                   32.0 MB (mem)
       Total Memory Limit                  645.7 MB
          Memory Wildcard                      True

Table 14 show resource limits (application service EXEC mode) 

Limit
Example
Description

Packaged Disk Limit

400 MB

Generated by the packaging tool.

Configured Disk Limit

Resource limit configured through CLI config commands. If no limit is configured through CLI, a dash "-" is displayed.

Current Disk Limit

400 MB

Resource limit currently used by the system and vservers. The value may change if resources are rebalanced.

Current Disk Usage

87 MB

Resources currently being used by the disk.

Disk Wildcard

False

Generated by the packaging tool.

Packaged Cpu Limit

1000

Generated by the packaging tool.

Configured Cpu Limit

Resource limit configured through CLI config commands. If no limit is configured through CLI, a dash "-" is displayed.

Current Cpu Limit

1000

Resource limit currently used by the system and vservers. The value may change if resources are rebalanced.

Cpu Wildcard

False

Generated by the packaging tool.

Packaged Memory Limit

30.0 MB

Generated by the packaging tool.

Configured Memory Limit

Resource limit configured through CLI config commands. If no limit is configured through CLI, a dash "-" is displayed.

Current Memory Limit

613.7 MB

Resource limit currently used by the system and vservers. The value may change if resources are rebalanced.

Packaged TMPFS Limit

32.0 MB (mem)

(mem): Memory (RAM) based /tmp file space limit.
(disk): (disk): /tmp is a directory on the disk and is not using a tmpfs file system. No memory is used when /tmp is disk based.

Total Memory Limit

645.7 MB

Total of packaged TMPFS limit and current memory limit.

Memory Wildcard

True

Generated by the packaging tool.


Additional References

For more information on Viewing and Log and Core files, see the "Log File Management" section on page 111.