Previous page Next page

show medic

Displays information about CNA.

Syntax
show medic [ detail ] 
 
           [ <slot> | all ] 
 
           [ <service> [ <routine> | <parameter> ] ]
 
           [ | { include | exclude | begin } <exp> ] 
 
           [ > <url> ]
 
Arguments
Prerequisites

System operations mode, login-level access.

Description

Omit the detail keyword to see a summary of conditions.

Use the keyword detail to see a more comprehensive report.

If you are connected to a peripheral CNA module (anything other than the management module), the show medic command operates in local mode and the data displayed refers only to the local module.

If you enter the show medic command with the keyword all and without the keyword detail, a one line status report will be displayed for each module, similar to the following:

Module     Slot Status Uptime          Services CPU Mem
 
ustat       1   up     35 min           13/14   2   33
 
ustat       2   up     36 min           13/14   2   33
 
ustat       3   up     35 min           13/14   2   32
 
engine      4   up     35 min           13/14   54  94
 
reporting   5   up     35 min           12/13   2   10
 
management  0   up     35 min           9/10    21  14
 

 

The Module and Slot columns identify the module.

The Status column can contain one of the following:

The Uptime column tells how long the module has been operating (d for days, h for hours, m for minutes, s for seconds; the numbers following a d entry refer to additional hours and minutes--1d, 6:05 means the module has been operating for one day, six hours and five minutes).

The Services column identifies how many services are currently running, out of the total number of services on that module.

The CPU and Mem columns show percentage of use (an entry of 17 means 17% of total capacity is currently being used).

If you enter the show medic command with the keyword all and the keyword detail, the status of each module will be expanded into a block of detailed text. Output will look similar to the following block of text for a USTAT module:

CNA> show medic detail all
 
 1   ustat       up 19:28            srv: 13/13  cpu: 2%   mem: 34%
 
       PASS  active-measurement-process         eval: 21:58:29 (5s ago)
 
               [ Running ]
 
               routine: restart INIT (never run)
 
       PASS  environment-monitor                eval: 21:58:20 (14s ago)
 
       PASS  host-resources                     eval: 21:58:20 (14s ago)
 
               max-pcpu = 80 (def = 80) SNMP trap max % CPU utilized
 
               max-pmem = 80 (def = 80) SNMP trap max % memory utilized
 
               max-prdisk = 99 (def = 99) SNMP trap max % root disk utilized
 
               min-pcpu = 50 (def = 50) SNMP trap min % CPU utilized
 
               min-pmem = 50 (def = 50) SNMP trap min % memory utilized
 
               min-prdisk = 80 (def = 80) SNMP trap min % root disk utilized
 
       PASS  interface-resources                eval: 21:58:31 (3s ago)
 
       PASS  klogd                              eval: 21:58:29 (5s ago)
 
       PASS  logfilterd                         eval: 21:58:29 (5s ago)
 
       PASS  measurement-process                eval: 21:58:30 (4s ago)
 
               [ Running ]
 
               routine: restart INIT (never run)
 
       PASS  mount                              eval: Thu 02:32 (19h26m ago)
 
       PASS  mount-hd                           eval: Thu 02:32 (19h26m ago)
 
       PASS  ping-management                    eval: 21:58:31 (3s ago)
 
       PASS  snmpd                              eval: 21:58:33 (1s ago)
 
       PASS  ustat-web-server                   eval: 21:58:31 (3s ago)
 
               [ Running ]
 
               routine: restart INIT (never run)
 
       PASS  verify-flash                       eval: Thu 02:32 (19h26m ago)
 

 

The first line in each block identifies the slot number and module name. Two asterisks following the slot number (N**) indicate a problem in one of the routines.

The next column in the first line tells you the status of the module.

In the example, the USTAT module in slot 1 has been operating (status is up) for 19 hours and 28 minutes. Operating time is shown in UNIX/Linux uptime format. If the system has been operating for more than 24 hours, the time will be presented in number of days plus hours and minutes (for example, up 1 day, 19:28 would mean the module had been operating for one day, 19 hours and 28 minutes).

The next column tells you how many Medic services are running out of how many total. In the example shown, srv: 13/13 means that 13 of the 13 services on the module were successfully initialized and are currently available.

The next two columns tell you what percentage of total CPU capacity and RAM are currently being used.

Services, and their routines and parameters, are then itemized.

One of the following status labels precedes the service name:

The column following the service’s name gives the date and time the service was last evaluated by the Medic process, with an interval in parentheses telling how long ago that was.

In the following example, the service was last evaluated by Medic on Thursday at 4:01 p.m., which was 3 days, 18 hours ago from the present:

eval: Thu 16:01 (3d18h ago)
 

 

If the service is currently running (not all will be running at all times), the next line will show the following:

[ Running ]
 

 

If the service has a user-accessible routine, it will be identified, along with its status:

routine: restart INIT (never run)
 

 

This line shows that the service’s restart routine is in the INIT state, which means it has never been run. Possible routine states are:

You can pipe the command through one of the following filters:

The vertical-line pipe character | is required when a filter is used.

You can send the output to a remote file location, by piping the display to a remote URL (leading > required). See the copy command for URL syntax.


Previous page Next page