Display Processes Monitored by OMU Daemon(DSP OMUPROCESS)

Function

An OM command that queries the information about the processes monitored by the Daemon.

Note

1. The local Daemon must be running.

2. You can query the information about only the processes monitored by the Daemon.

3. The number of times that a monitored process is restarted does not include the number of times that the monitored process is reset manually.

4. This command can be run on only the active GBAM.

Parameters

ID Name Description
BRDFLG OMU flag

Meaning: This parameter specifies whether the OMU is an active or standby one.

Value range: ACTIVE(Active), STANDBY(Standby)

Explanation: The value ACTIVE(Active) indicates that the status of the processes monitored by the Daemon on the active OMU is queried; the value STANDBY(Standby) indicates that the status of the processes monitored by the Daemon on the standby OMU is queried.

Default value: None

Example

Query the information about the process monitored by the Daemon on the active OMU:
DSP OMUPROCESS: BRDFLG=ACTIVE;
The result is as follows:
MML% DSP OMUPROCESS:BRDFLG=ACTIVE;
+++    HUAWEI        2008-07-17 16:04:31
O&M    #178
%%DSP OMUPROCESS:BRDFLG=ACTIVE;%%
RETCODE = 0  Operation succeeded

DSP OMUPROCESS Result
---------------------
               process name  =  omulocal
                  file name  =  /BSC6000/bscswm/omuroot/local/pomu_local.bin
          process parameter  =  0,2
                virtual PID  =  0
                 system PID  =  19872
               monitor type  =  heartBeat monitor
              process state  =  process start
            max reset times  =  4294967295
        already reset times  =  0
            CPU utilization  =  0.1%
       resident memory size  =  248712KB
resident memory utilization  =  11.9%
        virtual memory size  =  361456KB
               started time  =  Jul 7 10:05:30 2008

               process name  =  omucore
                  file name  =  /BSC6000/bscswm/omuroot/core/pomu_core.bin
          process parameter  =  0,2
                virtual PID  =  1
                 system PID  =  19700
               monitor type  =  heartBeat monitor
              process state  =  process start
            max reset times  =  0
        already reset times  =  0
            CPU utilization  =  0.2%
       resident memory size  =  926332KB
resident memory utilization  =  44.6%
        virtual memory size  =  1860516KB
               started time  =  Jul 7 10:05:25 2008
(Number of results = 2)


---    END

Output Description

Domain Name Description
process name

Name of the monitored process, such as omucore and omulocal.

file name

Path of the executable file of the monitored process, such as /BSC6000/bscswm/omuroot/local/pomu_local.bin.

process parameter

Startup parameter of the monitored process, such as "0, 23". The value 0 indicates the subrack number of the GOMU that runs the monitored process; the value 23 indicates the slot number.

virtual PID

Virtual PID that the Daemon assigns to its monitored process, such as 0.

system PID

PID that the operating system assigns to the monitored process, such as 10937.

monitor type

Type of monitoring by the Daemon on the process, such as heartBeat monitor.

process state

Current status of the monitored process, such as process start.

max reset times

Maximum number of times that the process can be reset, such as 4294967295.

already reset times

Number of times that the monitored process has been reset, such as 0.

CPU utilization

CPU usage of the monitored process.

resident memory size

Size of the physical memory occupied by the monitored process.

resident memory utilization

Usage of the physical memory occupied by the monitored process.

virtual memory size

Size of the virtual memory occupied by the monitored process.

started time

Time when the monitored process is started.


Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.