NE20E-S2 V800R022C00SPC600 Diagnose
System Debugging Diagnostic Commands
- clear memory tail-protection logfiles
- clear system cpu statistics
- debug comp-service component
- debug exception-delay-reset
- debug log filter
- debug log output
- debug memory tail-protection enable
- debug message receive-trace
- debug message trace
- debug system memory handle-type switch-to-block
- debug system memory leak
- debug system memory leak handle
- debug system private-log
- display comp-service component
- display component starvation threshold
- display cpu-monitor information process
- display cpu-monitor switch-states
- display cpu-usage history (Diagnostic view)
- display cpu-usage process
- display cpu-usage
- display exception
- display error-information
- display exception-delay-reset switch status
- display fd
- display inspect infrastructure
- display inspect process
- display log output
- display memory (Diagnostic view)
- display memory cid
- display memory cid mid
- display memory mid
- display memory tail-protection information
- display memory(Diagnostic view)
- display memory-monitor switch-states
- display memory-usage all
- display message exhaust reset-delay-time
- display message pipe-statistic
- display message receive-trace rule
- display message send-receive-statistic
- display message trace srccomp
- display message
- display message-process statistic process
- display message-usage component
- display message-usage
- display os-information slot
- display pipe-memory time process
- display assert
- display reset-reason
- display schedule-trace
- display semaphore
- display starvation
- display system cam-subscription
- display system component
- display system cpu statistics
- display system deadloop configuration
- display system debug configuration flow-control
- display system debug diagnostic-log
- display system debug queue info
- display system debug seccomp
- display system error
- display system memory handle-alloc process
- display system memory leak information
- display system memory process simple-to-block status
- display system memory statistics
- display system memory statistics(Diagnostic view)
- display system memory verbose process
- display system memory verbose(Diagnostic view)
- display system message alloc process
- display system message alloc-failed
- display system message statistic
- display system os-memory process
- display system os-memory slot
- display system os-process
- display system thread
- display thread callstack
- display thread schedule
- display timer slot
- display timer statistics process
- reset message pipe-statistic
- reset message send-receive-statistic
- reset message-process statistic
- reset record
- reset assert record
- schedule-trace
- set component starvation threshold
- set cpu-usage process
- set message exhaust reset-delay-time
- set message send-receive-statistic
- set message statistic
- set message-process statistic
- timer statistics
- trace next-start
- trace trigger message enable
- trace trigger packet enable
- trace trigger timer enable
- trace trigger { on | off }
clear memory tail-protection logfiles
Function
The clear memory tail-protection logfiles command clears memory tail protection information in logfiles.
Parameters
Parameter | Description | Value |
---|---|---|
slot slotID |
Clears memory tail damage statistics recorded in logs on a specified board. |
The value is an string ranging from 1 to 31 |
all |
Clears memory tail damage information about all boards. |
- |
clear system cpu statistics
Parameters
Parameter | Description | Value |
---|---|---|
slot slotID |
Specifies the slot ID of a board. If this parameter is not specified, CPU statistics about the device. |
- |
Usage Guidelines
Usage Scenario
To query accurate CPU statistics about the device or the specified board using the display system cpu statistics command, run the clear system cpu statistics command to clear historical CPU statistics about the device or the specified board first.
Precautions
This command is supported only on the admin VS.
debug comp-service component
Function
The debug comp-service component command sets a component framework maintenance operation for a specified component.
Format
debug comp-service component comp-cid log-box { shift { realtime-shift | full-shift | off } | trigger-shift }
Parameters
Parameter | Description | Value |
---|---|---|
comp-cid |
The value ranges from 0 to FFFFFFFF, in hexadecimal notation. |
Specifies a component ID. |
log-box |
Indicates the log black box. |
- |
shift |
Indicates the dump mode of the log black box. |
- |
realtime-shift |
Sets the dump mode of the log black box to real-time dump. |
- |
full-shift |
Sets the dump mode of the log black box to full-triggered dump. |
- |
off |
Disables the dump function of the log black box. |
- |
trigger-shift |
Manually triggers the dump of the log black box. |
- |
debug exception-delay-reset
Function
The debug exception-delay-reset off command disables the function of delaying restart upon an exception.
The debug exception-delay-reset on command enables the exception delay function.
Format
debug exception-delay-reset { all | slot slotid } off
debug exception-delay-reset time timevalue valid-num num { all | slot slotid } on
Parameters
Parameter | Description | Value |
---|---|---|
all |
Indicates all slots. |
- |
slot slotid |
Specifies a slot ID. |
- |
time timevalue |
Delay after which the faulty board is reset. |
The value is an integer ranging from 15 to 1440, unit is min. |
valid-num num |
Number of remaining times for delayed reset to take effect. |
The value is an integer, ranging from 1 to 100. |
Usage Guidelines
This command applies only to scenarios involve the board reset codes 1010093, 101008b, 1010000, 10100f3, and 10100c1. Exercise caution when using this function on the live network. If this function is enabled and an exception occurs, the device may be disconnected and services may be interrupted.
Example
<HUAWEI> system-view [~HUAWEI] diagnose Warning: Enter diagnose view, return user view with Ctrl+Z. Info: The diagnose view is used to debug system hardware and software. Misuse of certain commands in this view may affect system performance. Therefore, use these commands with the guidance of Huawei engineers. [~HUAWEI-diagnose] debug exception-delay-reset time 15 valid-num 2 all on Warning: If this function is enabled, the board delays to restart in the case of an exception. As a result, the management network interface may be disconnected and services may be interrupted. Are you sure you want to continue? [Y/N]:y
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI] dia Warning: Enter diagnose view, return user view with Ctrl+Z. Info: The diagnose view is used to debug system hardware and software. Misuse of certain commands in this view may affect system performance. Therefore, use these commands with the guidance of Huawei engineers. [~HUAWEI-diagnose] debug exception-delay-reset all off
debug log filter
Format
debug log filter filterid [ process processid | comp compid ] filtercond filtercond0 [ filtercond1 [ filtercond2 [ filtercond3 [ filtercond4 [ filtercond5 [ filtercond6 [ filtercond7 [ filtercond8 [ filtercond9 ] ] ] ] ] ] ] ] ] on
debug log filter filterid off
debug log filter all off
Parameters
Parameter | Description | Value |
---|---|---|
filterid |
Specifies a filtering rule ID. |
The value is an integer ranging from 0 to 9. |
process processid |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
comp compid |
The component ID. |
The value is a hexadecimal number ranging from 0 to 0xffffffff. |
filtercond |
The filter condition element. |
- |
filtercond0 |
The filter condition element. |
The value is a string of 1 to 31 characters. |
filtercond1 |
The filter condition element. |
The value is a string of 1 to 31 characters. |
filtercond2 |
The filter condition element. |
The value is a string of 1 to 31 characters. |
filtercond3 |
The filter condition element. |
The value is a string of 1 to 31 characters. |
filtercond4 |
The filter condition element. |
The value is a string of 1 to 31 characters. |
filtercond5 |
The filter condition element. |
The value is a string of 1 to 31 characters. |
filtercond6 |
The filter condition element. |
The value is a string of 1 to 31 characters. |
filtercond7 |
The filter condition element. |
The value is a string of 1 to 31 characters. |
filtercond8 |
The filter condition element. |
The value is a string of 1 to 31 characters. |
filtercond9 |
The filter condition element. |
The value is a string of 1 to 31 characters. |
on |
Enables the filtering function for the specified filtering rule. |
- |
off |
Disables debugging information filtering. |
- |
all |
Disables all filtering rules. |
- |
Usage Guidelines
Usage Scenario
Generally, debugging information contains a lot of unconcerned information. To obtain key debugging information, run the debug log filter command to enable the system to display debugging information based on the specified filtering rule.
Precautions
This command is supported only on the admin VS.
debug log output
Function
The debug log output file on command configures a device to output debugging information to a file.
The debug log output off command restores the default configuration.
By default, debugging information is output to the information center.
Format
debug log output { screen | PC | PC_combined } on
debug log output file on
debug log output off
Parameters
Parameter | Description | Value |
---|---|---|
screen |
Output to screen. |
- |
PC |
Output to PC. |
- |
PC_combined |
Output to PC combined. |
- |
on |
Open switch. |
- |
off |
Close switch. |
- |
Usage Guidelines
Usage Scenario
By default, debugging information is output to the information center. If the debugging information output rate is inconsistent with the data processing rate of the information center, for example, the debugging information output rate is higher than the data processing rate of the information center, some data may be discarded by the information center. To resolve this issue, run the debug log output file on command to configure the device to output debugging information to the buffer and then to a file to improve reliability.
Precautions
This command is supported only on the admin VS.
debug memory tail-protection enable
Function
The debug memory tail-protection enable command enables the memory tail protection function.
The undo debug memory tail-protection enable command disables the memory tail protection function.
Format
debug memory tail-protection enable { slot slotid | all }
undo debug memory tail-protection enable { slot slotid | all }
Parameters
Parameter | Description | Value |
---|---|---|
slot slotid |
Specifies the slot ID of a board. |
The value is an string ranging from 1 to 32 |
all |
Specifies all boards. |
- |
Usage Guidelines
To enable memory tail damage protection function, run the debug memory tail-protection enable command.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] debug memory tail-protection enable all
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] undo debug memory tail-protection enable all
debug message receive-trace
Function
The debug message receive-trace on command enables message receiving tracing for a specified rule process.
The debug message receive-trace off command disables the message tracing function.
By default, the message tracing function is disabled.
Format
debug message receive-trace process processid rule ruleid [ srccomp srccompcid ] [ destcomp destcompcid ] [ { intf intfvalue | all-intf } { subintf subintfvalue | all-subintf } ] [ message-type msgtype-value ] [ timeout timeout-value ] on
debug message receive-trace process processid rule ruleid off
Parameters
Parameter | Description | Value |
---|---|---|
rule ruleid |
Specifies a rule ID. |
The value is an integer ranging from 0 to 4. |
srccomp srccompcid |
Specifies the ID of the component that sends messages. |
The value ranges from 0 to FFFFFFFF, in hexadecimal notation. |
destcomp destcompcid |
Specifies the ID of the component that receives messages. |
The value ranges from 0 to FFFFFFFF, in hexadecimal notation. |
intf intfvalue |
Specifies a message category. |
The value is an integer ranging from 0 to 255. |
all-intf |
Displays information about all message categories. |
- |
subintf subintfvalue |
Specifies a message sub-category. |
The value is an integer ranging from 0 to 255. |
all-subintf |
Displays information about all message sub-categories. |
- |
message-type msgtype-value |
Specifies a message type. |
The value is an integer ranging from 0 to 4294967295. |
timeout timeout-value |
Specifies a timeout period. |
The value is an integer ranging from 0 to 480000, in milliseconds. |
process processid |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
To analyze a message processing performance problem, run the debug message receive-trace on command to enable message receiving tracing for a specified rule process. The tracing function records processing information about the messages meeting the specified rule.
Precautions
This command is supported only on the admin VS.
debug message trace
Function
The debug message trace on command enables message tracing between specified components.
The debug message trace off command disables message tracing between specified components.
Format
debug message trace srccomp srcompid all destcomp dstcompid [ dump-size size ] on
debug message trace srccomp srcompid intf intfid subintf subintfid message-type msgtype destcomp dstcompid [ dump-size size ] on
debug message trace off
Parameters
Parameter | Description | Value |
---|---|---|
all |
Traces all types of messages. |
- |
destcomp dstcompid |
Specifies the ID of the component that receives messages. |
The value ranges from 0 to FFFFFFFF, in hexadecimal notation. |
dump-size size |
Specifies the length of the message to be printed. |
The value is an integer ranging from 1 to 48. The default value is 20, in bytes. |
srccomp srcompid |
Specifies the ID of the component that sends messages. |
The value ranges from 0 to FFFFFFFF, in hexadecimal notation. |
intf intfid |
Specifies message interface id. |
The value is an integer ranging from 0 to 4294967295. |
subintf subintfid |
Specifies message sub interface id. |
The value is an integer ranging from 0 to 4294967295. |
message-type msgtype |
Message type id. |
The value is an integer ranging from 0 to 4294967295. |
debug system memory handle-type switch-to-block
Function
The debug system memory handle-type switch-to-block command configures conversion from simple memory to block memory in a specified process.
Format
debug system memory handle-type switch-to-block { enable process processid timeout interval-value | disable process processid }
Parameters
Parameter | Description | Value |
---|---|---|
enable |
Enables conversion from simple memory to block memory. |
- |
process processid |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
timeout interval-value |
Specifies a timeout period. If the disable keyword is not used to disable the conversion from simple memory to block memory, this function is automatically disabled based on the specified timeout period. |
The value is an integer ranging from 1 to 1440, in minutes. |
disable |
Disables conversion from simple memory to block memory. |
- |
debug system memory leak
Function
The debug system memory leak on command enables the function of collecting memory leak call stack statistics.
The debug system memory leak off command disables the function of collecting memory leak call stack statistics.
The debug system memory leak reset command resets the function of collecting memory leak call stack statistics.
Format
debug system memory leak on process procId
debug system memory leak off process procId
debug system memory leak reset process procId
Parameters
Parameter | Description | Value |
---|---|---|
off |
Disables the function of collecting memory leak call stack statistics. |
- |
process procId |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
reset |
Resets the function of collecting memory leak call stack statistics. |
- |
on |
Enables the function of collecting memory leak call stack statistics. |
- |
Usage Guidelines
Usage Scenario
To locate a memory abnormality, run the debug system memory leak on, debug system memory leak off, or debug system memory leak reset command to enable, disable, or reset the function of collecting memory leak call stack statistics.
Precautions
This command is supported only on the admin VS.
debug system memory leak handle
Function
The debug system memory leak handle on command enables the function to collect call stack statistics when a memory leak occurs.
The debug system memory leak handle off command disables the function to collect call stack statistics when a memory leak occurs.
The debug system memory leak handle reset command clears the call stack statistics collected when a memory leak occurs.
Format
debug system memory leak handle on process procId cid cid-value mid mid-value [ partition { common | simple | pipe | temp } ] min min-size max max-size
debug system memory leak handle off process procId
debug system memory leak handle reset process procId
Parameters
Parameter | Description | Value |
---|---|---|
cid cid-value |
Specifies a component ID. |
The value is a hexadecimal number ranging from 0 to ffffffff. |
mid mid-value |
Specifies a module ID. |
The value is a hexadecimal number ranging from 0 to ffffffff. |
partition |
Indicates a partition. |
- |
common |
Indicates a Common partition. |
- |
simple |
Indicates a Simple partition. |
- |
pipe |
Indicates a Pipe partition. |
- |
temp |
Indicates a Temp partition. |
- |
min min-size |
Specifies the minimum memory capacity. |
The value is an integer ranging from 0 to 4294967295. |
max max-size |
Specifies the maximum memory capacity. |
The value is an integer ranging from 0 to 4294967295. |
off |
Disables the function to collect call stack statistics when a memory leak occurs. |
- |
process procId |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
reset |
Clears the call stack statistics collected when a memory leak occurs. |
- |
on |
Enables the function to collect call stack statistics when a memory leak occurs. |
- |
Usage Guidelines
Usage Scenario
To locate a memory abnormality, run the debug system memory leak handle on, debug system memory leak handle off, or debug system memory leak handle reset command to enable, disable, or reset the function to collect call stack statistics when a memory leak occurs.
Precautions
This command is supported only on the admin VS.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] debug system memory leak handle on process 1000 cid 80A80439 mid 0 partition pipe min 10 max 100 Info: Operation succeeded.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] debug system memory leak handle off process 1000
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] debug system memory leak handle reset process 1000
debug system private-log
Function
The debug system private-log command enables the function of periodically uploading private logs to the main control board.
Format
debug system private-log transfer { off | period trans-period number trans-number [ slot slot-id ] }
Parameters
Parameter | Description | Value |
---|---|---|
off |
Close switch. |
- |
period trans-period |
Uploads private logs. |
The value is an integer that ranges from 1 to 1000 . |
number trans-number |
Specifies the maximum number of private log compression packages that can be retained on the main control board. |
The value is an integer that ranges from 1 to 10 . |
slot slot-id |
Specifies a slot ID. If this parameter is not specified, private logs of all boards are uploaded. |
The value is a string of 1 to 32 case-sensitive characters, spaces not supported. |
transfer |
Transfer private log. |
- |
display comp-service component
Function
The display comp-service component command displays information about the component framework used by a specified component.
Format
display comp-service component comp-id { summary | service-id sid-value [ sub-id bid-value [ param ] ] }
display comp-service process proc-id log-box
Parameters
Parameter | Description | Value |
---|---|---|
comp-id |
Specifies a component ID. |
The value is a hexadecimal number ranging from 0 to ffffffff. |
summary |
Displays summary information about the component framework used by a specified component. |
- |
service-id sid-value |
Specifies a service ID. |
The value is an integer ranging from 0 to 4294967295. |
sub-id bid-value |
Specifies a level-2 service ID. |
The value is an integer ranging from 0 to 4294967295. |
param |
Specifies an optional parameter. |
The value is an integer ranging from 0 to 4294967295. |
process proc-id |
Specifies the process ID of log-box. |
The value is an integer ranging from 0 to 4294967295. |
log-box |
Dopra?log?box. |
- |
Usage Guidelines
Usage Scenario
When the communication or data synchronization between components is abnormal, run the display comp-service component command to check information about the component framework used by a specified component.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display comp-service component 8128003c summaryCCF service help ---------------------------------------------------------------------------------------- sid name description ---------------------------------------------------------------------------------------- 0 help enter service id 0 get help info 1 log enter service id 1 get log info 2 timer enter service id 2 get timer info 3 session enter service id 3 get session info 4 metro enter service id 4 get metro info 5 fsm enter service id 5 get fsm info 6 ccf enter service id 6 get ccf info ----------------------------------------------------------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display comp-service component 8128003c service-id 3 ---------------------------------------------------------------------------------------- subid name description ---------------------------------------------------------------------------------------- 1 brief session brief information 2 detail specified session detal information 3 record specified session record information ----------------------------------------------------------------------------------------
display component starvation threshold
Function
The display component starvation threshold command displays the threshold for the component scheduling timeout period.
Parameters
Parameter | Description | Value |
---|---|---|
all |
Displays the thresholds for the component scheduling timeout periods of all processes. |
- |
slot slotId |
Displays the threshold for the component scheduling timeout period of a specified board. |
- |
process ProcessId |
Displays the threshold for the component scheduling timeout period of a specified process. |
The value is an integer ranging from 1 to 4294967295. |
Usage Guidelines
Usage Scenario
In the case of a component scheduling failure, run the display component starvation threshold command to check the threshold for the component scheduling timeout period.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display component starvation threshold ------------------------------------------------------------ Slot ProcessID Threshold (s) IsResetProcess ------------------------------------------------------------ 1 10004 0 NO 1 10003 0 NO 1 1016 0 NO ------------------------------------------------------------
Item | Description |
---|---|
Slot | Slot ID. |
ProcessID | Process ID. |
Threshold (s) | Threshold for the component scheduling timeout period. |
IsResetProcess | Processing method when the threshold is exceeded:
|
display cpu-monitor information process
Function
The display cpu-monitor information process command displays CPU overload information about a specified or all processes.
Parameters
Parameter | Description | Value |
---|---|---|
all |
Displays CPU overload information about all processes. |
- |
processid |
Specifies the ID of a process whose CPU overload information is to be queried. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
To check CPU overload information about a specified or all processes, run the display cpu-monitor information process command. The information includes CPU usage, overload threshold, overload detection period, overload status, and status of the overload detection function. CPU usage is collected during overload detection. It is not real-time data.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display cpu-monitor information process all Process cpuoverload information --------------------------------------------------------------------------- ProID Cpuuasge(%) Threshold(%) Interval(s) State SwitchStatus --------------------------------------------------------------------------- 1005 0 0 0 -- close 1006 0 0 0 -- close 2 0 0 0 -- close 3 0 0 0 -- close 4 0 20 10 unoverload open ---------------------------------------------------------------------------
Item | Description |
---|---|
ProID | Process ID. |
Cpuuasge(%) | Process-specific CPU usage. |
Threshold(%) | Process-specific CPU overload threshold. |
Interval(s) | Overload detection period. |
State | Process-specific CPU overload status:
|
SwitchStatus | Status of the overload detection function:
|
display cpu-monitor switch-states
Function
The display cpu-monitor switch-states command displays the status of CPU overload detection on a board.
Usage Guidelines
Usage Scenario
This command displays the status of CPU overload detection on a board.
Precautions
This command is supported only on the admin VS.
display cpu-usage history (Diagnostic view)
Function
The display cpu-usage history command displays information about historical CPU component usage.
Parameters
Parameter | Description | Value |
---|---|---|
component cid |
Specifies the ID of a CPU component. |
The value is a hexadecimal integer ranging from 0 to FFFFFFFF. |
Usage Guidelines
Usage Scenario
If the CPU usage is high, run the display cpu-usage history command to view information about historical CPU component usage.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display cpu-usage history component 80050103 ----------------------------------------------- TimeBefore AvgCPU MaxCPU TimeOfMaxCPU ----------------------------------------------- 00:01:00 0% 0% 00:00:00 00:02:00 6% 79% 00:01:25 00:03:00 0% 0% 00:02:00 00:04:00 0% 0% 00:03:00 00:05:00 0% 0% 00:04:00 00:06:00 0% 0% 00:05:00 00:07:00 0% 0% 00:06:00 00:08:00 0% 0% 00:07:00 00:09:00 0% 0% 00:08:00 00:10:00 0% 0% 00:09:00 -----------------------------------------------
display cpu-usage process
Function
The display cpu-usage command displays detailed process/thread CPU usage and thread call stack information.
Using the display cpu-usage process command, you can view the CPU usage of a specified process.
Format
display cpu-usage { process locid | component compcid }
display cpu-usage process [ slot slotid ]
Parameters
Parameter | Description | Value |
---|---|---|
process locid |
Specifies the ID of the process to be viewed. |
The value is an integer ranging from 0 to 4294967295. |
component compcid |
Specifies the ID of the component to be viewed. |
The value ranges from 0 to ffffffff, in hexadecimal notation. |
slot slotid |
Specifies a slot ID. |
- |
Usage Guidelines
Usage Scenario
To check detailed process/thread CPU usage and thread call stack information, run the display cpu-usage command. This helps locate faults in routine maintenance and when the device runs abnormally.
During the routine maintenance of the device or when the device cannot run normally, the display cpu-usage process command can be used to view the CPU usage and the CPU usage configuration of the specified process.Precautions
If the device starts with only basic configurations and the CPU usage is constantly higher than the alarm threshold (you can configure the alarm threshold), the CPU works abnormally. You should check the device and locate the fault.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display cpu-usage process 1001 CPU utilization statistics at 2017-04-09 22:43:08 936 ms Process ID : 3 Process name : CFG Process CPU use rate is : 0% Component CPU use rate : ------------------------------------------- ComponentCid ComponentName UseRate ------------------------------------------- 0x802B272F LCS 0% 0x80CF0009 APPCFG6 0% 0x80CE000A DBMS7 0% 0x80D02739 PM 0% 0x80D22737 LAM 0% 0x80D12735 AAA 0% 0x80E72715 FMSERVER 0% 0x80CD000B ADM8 0% 0x80CB000C CFG9 0% 0x802C000E SSPRPM11 0% 0x80CC000D ECM10 0% 0x80332713 DBG_AGENT 0% 0x80CA2713 CLI10002 0% 0x80602717 LOGSERVER 0% 0x0 OS 0% ------------------------------------------- Total = 15
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display cpu-usage component 802B272F CPU utilization statistics at 2011-11-09 22:48:12 705 ms Process ID : 3 Process name : CFG Process CPU use rate is : 0% Component CPU use rate : ------------------------------------------- ComponentCid ComponentName UseRate ------------------------------------------- 0x802B272F LCS 0% ------------------------------------------- Total = 1
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display cpu-usage process slot 1 Cpu utilization statistics at 2021-11-08 19:43:08 398 ms System cpu use rate is : 6% Cpu utilization for five seconds: 6% ; one minute: 6% ; five minutes: 6%. Max CPU Usage : 22% Max CPU Usage Stat. Time : 2021-11-06 18:17:08 710 ms Cpu use top process: ------------------------------------------------------------------------------ ProcessId ProcessName UseRate ProcessDescription ------------------------------------------------------------------------------ 0 OS 5% OS Kernel 4 LM 1% Board Management 10003 MCASTMB_SERVICE 0% MCASTMB_SERVICE 1015 PSM1 0% Protocol Stack Manager 1 1017 IFM 0% IFM 1013 CFG_COMMON 0% Configuration Management 1010 DHCP 0% DHCP 1012 LLP 0% LLP 1016 EWM 0% EWM 1014 LOGSERVER 0% Log Server 1011 PROTO4 0% PROTO4 ------------------------------------------------------------------------------
Item | Description |
---|---|
Process ID | Process ID. |
Process name | Process name. |
Process CPU use rate is | CPU usage of the process. |
Component CPU use rate | CPU usage list of a component. |
ComponentCid | Component CID. |
ComponentName | Component name. |
UseRate | CPU usage of the component. |
Cpu utilization for five seconds | Average CPU usage in 5 seconds. |
Cpu use top process | Process with the highest CPU usage. |
Cpu utilization statistics | Indicates the time when the CPU statistics are recorded. |
System cpu use rate | System CPU usage. |
Max CPU Usage | Maximum CPU usage. |
Max CPU Usage Stat. Time | Time when the maximum CPU usage occurs. |
ProcessId | Process ID. |
ProcessName | Name of a process. |
ProcessDescription | Function description of a process. |
One minute | Average CPU usage within 1 minute. |
Five minutes | Average CPU usage in 5 minutes. |
display cpu-usage
Function
The display cpu-usage command displays detailed information about the process CPU usage, thread CPU usage, and thread call stack.
Parameters
Parameter | Description | Value |
---|---|---|
slot slotid |
Specifies a slot ID. |
The value is a string of 1 to 31 characters. |
all |
Displays detailed process/thread CPU usage and thread call stack information about all boards. |
- |
top |
Displays the first N pieces of detailed information. |
- |
show-num |
Number of items to display. |
The value is an integer ranging from 1 to 10. |
Usage Guidelines
Usage Scenario
During routine maintenance or when a device cannot run properly, you are advised to run the display cpu-usage command to view detailed information about the process CPU usage, thread CPU usage, and thread call stack.
Precautions
If the device starts with only basic configurations and the CPU usage is constantly higher than the alarm threshold (you can configure the alarm threshold), the CPU works abnormally. You should check the device and locate the fault.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display cpu-usage slot 10 top 3 -------------------------------------------------------- Slot xx cpu information -------------------------------------------------------- Slot xx cpu use top 3 Process: -------------------------------------------------------- OsProcessID OsProcessname Usage -------------------------------------------------------- 1 monitor 0% 2 kthreadd 0% 3 migration/0 0% -------------------------------------------------------- Slot xx cpu use top 3 thread: ------------------------------------------------------------------------------------------ ProcessID ProcessName ThreadID ThreadType Bind Comp Bind Cpu Usage ------------------------------------------------------------------------------------------ 3 LM 1208090752 main thread Bind all 15% 3 LM 1259918512 DefSch0800 Free all 12% 3 LM 1260049584 ADMSESS0 Free all 0% ------------------------------------------------------------------------------------------ Thread call stack information: ----------------------------- Thread 1208090752 (Thread main thread): #00 libc.so.6(epoll_wait) #01 location(Frame_FdMainThread) #02 location(Frame_Main) #03 location(main) #04 kernel(System symbol) #05 kernel(System symbol) Thread 1222050992 (Thread DefSch0800): #00 libc.so.6(__select) #01 libdefault.so(VOS_TaskDelay) #02 libdefault.so(vosBoxextOutputTaskEntry) #03 libdefault.so(tskAllTaskEntry) #04 kernel(System symbol) #05 libc.so.6(clone) Thread 1222182064 (Thread ADMSESS0): #00 libc.so.6(__select) #01 libdefault.so(tskAllTaskEntry) #02 kernel(System symbol) #03 libc.so.6(clone) --------------------------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display cpu-usage all SlotID: 11 Cpu utilization statistics at 2022-03-22 17:31:10 967 ms System cpu use rate is : 2% Cpu utilization for five seconds: 0% ; one minute: 0% ; five minutes: 0%. Max CPU Usage : 53% Max CPU Usage Stat. Time : 2022-03-22 17:26:41 341 ms --------------------------- ServiceName UseRate --------------------------- SYSTEM 2% CMF 0% DEVICE 0% DHCP 0% FEA 0% FEC 0% IP STACK 0% LOCAL PKT 0% SVRO 0% --------------------------- CPU Usage Details ---------------------------------------------------------------- CPU Current FiveSec OneMin FiveMin Max MaxTime ---------------------------------------------------------------- cpu0 2% 0% 0% 0% 0% 2022-03-22 17:26:26 cpu1 2% 0% 0% 0% 0% 2022-03-22 17:26:26 ---------------------------------------------------------------- SlotID: 12 Cpu utilization statistics at 2022-03-22 17:31:11 041 ms System cpu use rate is : 3% Cpu utilization for five seconds: 3% ; one minute: 2% ; five minutes: 2%. Max CPU Usage : 41% Max CPU Usage Stat. Time : 2022-03-22 17:02:20 287 ms --------------------------- ServiceName UseRate --------------------------- SYSTEM 3% CMF 0% DEVICE 0% DHCP 0% FEA 0% FEC 0% IP STACK 0% LOCAL PKT 0% SVRO 0% --------------------------- CPU Usage Details ---------------------------------------------------------------- CPU Current FiveSec OneMin FiveMin Max MaxTime ---------------------------------------------------------------- cpu0 3% 3% 2% 2% 4% 2022-03-22 17:12:44 cpu1 3% 3% 2% 2% 4% 2022-03-22 17:27:14 ---------------------------------------------------------------- SlotID: 13 Cpu utilization statistics at 2022-03-22 17:31:11 116 ms System cpu use rate is : 3% Cpu utilization for five seconds: 3% ; one minute: 2% ; five minutes: 2%. Max CPU Usage : 44% Max CPU Usage Stat. Time : 2022-03-22 17:02:21 089 ms --------------------------- ServiceName UseRate --------------------------- SYSTEM 3% CMF 0% DEVICE 0% DHCP 0% FEA 0% FEC 0% IP STACK 0% LOCAL PKT 0% SVRO 0% --------------------------- CPU Usage Details ---------------------------------------------------------------- CPU Current FiveSec OneMin FiveMin Max MaxTime ---------------------------------------------------------------- cpu0 3% 3% 2% 2% 5% 2022-03-22 17:25:05 cpu1 3% 3% 2% 2% 4% 2022-03-22 17:12:35 ---------------------------------------------------------------- SlotID: 14 Cpu utilization statistics at 2022-03-22 17:31:11 189 ms System cpu use rate is : 4% Cpu utilization for five seconds: 4% ; one minute: 3% ; five minutes: 3%. Max CPU Usage : 46% Max CPU Usage Stat. Time : 2022-03-22 17:02:20 497 ms --------------------------- ServiceName UseRate --------------------------- SYSTEM 4% CMF 0% DEVICE 0% DHCP 0% FEA 0% FEC 0% IP STACK 0% LOCAL PKT 0% SVRO 0% --------------------------- CPU Usage Details ---------------------------------------------------------------- CPU Current FiveSec OneMin FiveMin Max MaxTime ---------------------------------------------------------------- cpu0 5% 5% 3% 3% 5% 2022-03-22 17:24:54 cpu1 3% 3% 3% 3% 5% 2022-03-22 17:12:54 ---------------------------------------------------------------- SlotID: 15 Cpu utilization statistics at 2022-03-22 17:31:11 263 ms System cpu use rate is : 11% Cpu utilization for five seconds: 12% ; one minute: 11% ; five minutes: 21%. Max CPU Usage : 42% Max CPU Usage Stat. Time : 2022-03-22 16:59:16 372 ms --------------------------- ServiceName UseRate --------------------------- SYSTEM 11% AAA 0% ARP 0% BRAS 0% CMF 0% CSP 0% DEVICE 0% DHCP 0% ETRUNK 0% EUM 0% FEA 0% FEC 0% FIBRESM 0% IFM 0% IP STACK 0% LDT 0% LINK 0% LOCAL PKT 0% MFLP 0% MSTP 0% ND 0% NETSTREAM 0% OAM 0% PKI 0% PNP 0% PTPA 0% RBS 0% RGM 0% RM 0% SLA 0% SMLK 0% SOC 0% SVRO 0% TNLM 0% TUNNEL 0% VLAN 0% --------------------------- CPU Usage Details ---------------------------------------------------------------- CPU Current FiveSec OneMin FiveMin Max MaxTime ---------------------------------------------------------------- cpu0 14% 14% 11% 20% 54% 2022-03-22 17:25:02 cpu1 10% 12% 10% 16% 29% 2022-03-22 17:28:22 cpu2 13% 12% 11% 17% 25% 2022-03-22 17:26:22 cpu3 14% 17% 18% 18% 28% 2022-03-22 17:28:12 cpu4 19% 19% 16% 21% 36% 2022-03-22 17:16:02 cpu5 6% 9% 8% 30% 81% 2022-03-22 17:29:02 cpu6 5% 7% 8% 24% 62% 2022-03-22 17:28:12 cpu7 10% 7% 6% 22% 56% 2022-03-22 17:16:22 ---------------------------------------------------------------- SlotID: 16 Cpu utilization statistics at 2022-03-22 17:31:11 947 ms System cpu use rate is : 6% Cpu utilization for five seconds: 0% ; one minute: 0% ; five minutes: 0%. Max CPU Usage : 23% Max CPU Usage Stat. Time : 2022-03-22 17:27:59 896 ms --------------------------- ServiceName UseRate --------------------------- SYSTEM 6% AAA 0% ARP 0% BRAS 0% CMF 0% CSP 0% DEVICE 0% DHCP 0% ETRUNK 0% EUM 0% FEA 0% FEC 0% FIBRESM 0% IFM 0% IP STACK 0% LDT 0% LINK 0% LOCAL PKT 0% MFLP 0% MSTP 0% ND 0% NETSTREAM 0% OAM 0% PKI 0% PNP 0% PTPA 0% RBS 0% RGM 0% RM 0% SLA 0% SMLK 0% SOC 0% SVRO 0% TNLM 0% TUNNEL 0% VLAN 0% --------------------------- CPU Usage Details ---------------------------------------------------------------- CPU Current FiveSec OneMin FiveMin Max MaxTime ---------------------------------------------------------------- cpu0 7% 0% 0% 0% 0% 2022-03-22 17:27:15 cpu1 4% 0% 0% 0% 0% 2022-03-22 17:27:15 cpu2 2% 0% 0% 0% 0% 2022-03-22 17:27:15 cpu3 8% 0% 0% 0% 0% 2022-03-22 17:27:15 cpu4 16% 0% 0% 0% 0% 2022-03-22 17:27:15 cpu5 4% 0% 0% 0% 0% 2022-03-22 17:27:15 cpu6 4% 0% 0% 0% 0% 2022-03-22 17:27:15 cpu7 4% 0% 0% 0% 0% 2022-03-22 17:27:15 ----------------------------------------------------------------
Item | Description |
---|---|
Slot cpu use top 3 Process | Top 3 processes with the highest CPU usage. |
Slot cpu use top 3 thread | Top 3 threads with the highest CPU usage. |
xx cpu information | Indicates the CPU usage of the board in slot xx. |
OsProcessID | Process ID of the operating system. |
Usage | CPU usage. |
ProcessID | Process ID. |
ProcessName | Process name. |
ThreadID | Thread ID. |
ThreadType | Thread type. |
Bind Comp | Whether a thread is bound to a component:
|
Bind Cpu | CPU bound to a thread. |
Cpu utilization for xxx | CPU usage in the xxx period. |
Thread call stack information | Thread call stack information. |
System cpu use rate is | System CPU usage. |
Max CPU Usage | Maximum CPU usage. |
Max | Maximum CPU usage. |
CPU Usage Details | CPU usage details. |
CPU | CPU ID. |
ServiceName | Service name. |
UseRate | CPU usage. |
Current | Current CPU usage. |
FiveSec | CPU usage in 5 seconds. |
OneMin | CPU usage within one minute. |
FiveMin | CPU usage within 5 minutes. |
MaxTime | Time when the CPU usage reaches the maximum. |
Process ID | Process ID. |
Process name | Process name. |
Process CPU use rate is | CPU usage of the process. |
Component CPU use rate | CPU usage list of a component. |
ComponentCid | Component CID. |
ComponentName | Component name. |
OsProcessName | Name of a process in the operating system. |
SlotID | Board ID. |
display exception
Function
The display exception command displays system exception information.
The display deadloop command displays deadloop information in the system.
Format
display exception show_num [ begin_num ] [ verbose ] [ all | slot slotId ]
display deadloop show_num [ begin_num ] [ verbose ] [ all | slot slotId ]
Parameters
Parameter | Description | Value |
---|---|---|
show_num |
Number of items to display. |
The value is an integer ranging from 1 to 20. |
begin_num |
Offset of begin item prior to most recent. |
The value is an integer ranging from 0 to 19. |
verbose |
Displays the detailed information. |
- |
all |
Indicates exceptions or dead loops that occur on all boards. |
- |
slot slotId |
Specifies the slot ID of an available slot. |
The value is a string of 1 to 15 case-sensitive characters, spaces not supported. |
Usage Guidelines
To check deadloop information when the system is busy, run the display deadloop command. Normal deadloop information does not affect services.
The To check system exceptions, run the display exception command. If a system exception has caused board resets, contact technical support personnel.Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display exception 1 ================= exception info (no: 0 idx: 0) ================= Exception Type: 11 Exception Subtype: 0 Exception Name: SIGSEGV Exception Exception Process: 4 Exception Process Name: LM4 Exception Time: 2011-03-17 02:33:04 Exception Tick: 0x00127259 (CPU Tick High) 0x374cd3c0 (CPU Tick Low) VRP Version: VRPV800R002C00B080.cc DOPRA Version: DOPRA V200R003C03SPC050 PATCH: V800R002SPH102 Show CallStack: Instruction Address: 0xffffe430, Func:[0xffffe430] Instruction Address: 0x0804e3ed, Func:location(LOC_ProcessPipeMsg+0x12d) [0x804e3ed] Instruction Address: 0x08051443, Func:location(LOC_LocationMain+0x4f3) [0x8051443] Instruction Address: 0x08051552, Func:location(main+0x32) [0x8051552] Instruction Address: 0xb777487c, Func:libc.so.6(__libc_start_main+0xdc) [0xb777487c] Instruction Address: 0x0804c2b1, Func:location [0x804c2b1]
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display deadloop 20 all ================= Deadloop info (no: 0 idx: 0) ================= Deadloop Deadloop Process: 1005 Deadloop Process Name: LM DOPRA Version: DOPRA V200R003C03SPC050 VRP Version: PATCH: V800R002SPH102 Times: 124320 Event id: 579014657 Comp id(send): 2163999799 Comp id(receive): 2161050676 Message iid: 256 Message intf: 1 Message subintf: 0 Deadloop Time: 2011-03-01 16:56:21 Deadloop Tick: 0x00000000 (CPU Tick High) 0x56306f21 (CPU Tick Low) Show CallStack: Func:semls.so(SEMLS_MemOvLoad_ProDetectTimerMsg+0) [0xf4072dc] Func:libpthread.so.0(pthread_cond_timedwait+0x1a8) [0xffa9970] Func:libdefault.so(vosSemaP+0x2d8) [0xfccc054] Func:libdefault.so(VOS_SemaP+0x98) [0xfccc214] Func:libdefault.so(tskEventRead+0x168) [0xfb447a4] Func:libdefault.so(VOS_EventRead+0x68) [0xfb44a60] Func:libdefault.so(rtfScmCompScheDefaultEntry+0xa8) [0xfcdb2a8] Func:libdefault.so(rtfScmTaskDeployDefaultCompEntry+0x24) [0xfcdb428] Func:libdefault.so(tskAllTaskEntry+0x90) [0xfb44950] Func:libpthread.so.0 [0xffa4e20] Func:libc.so.6(clone+0x84) [0xf72ef58]
Item | Description |
---|---|
Exception Type | Exception type. |
Exception Subtype | Exception sub-type. |
Exception Name | Exception name. |
Exception Process | ID of the abnormal process. |
Exception Process Name | Name of the abnormal process. |
Exception Time | Time when an exception occurs. |
Exception Tick | CPU tick when an exception occurs. |
VRP Version | VRP version. |
DOPRA Version | DOPRA version. |
Show CallStack | Information about the exception call stack. |
Show CallStack | Details about the call stack. |
Deadloop Process | ID of the process on which a deadloop occurs. |
Deadloop Process Name | Name of the process on which a deadloop occurs. |
Deadloop Time | Time when a deadloop occurs. |
Deadloop Tick | CPU tick when a deadloop occurs. |
Event id | Event ID. |
Comp id(send) | ID of the component sends messages. |
Comp id(receive) | ID of the component receives messages. |
Message iid | Message IID. |
Message intf | Message type. |
Message subintf | Message sub-type. |
PATCH | Patch version. |
Times | Time of processing when a deadloop occurs. |
display error-information
Parameters
Parameter | Description | Value |
---|---|---|
show_num |
Specifies the maximum number of errors to be displayed. |
The value is an integer ranging from 1 to 10. |
offset_value |
Specifies the number of errors to be displayed ahead of the latest error. |
The value is an integer ranging from 0 to 9. |
verbose |
Displays detailed information about errors in the system. |
- |
all |
Displays information about all errors in the system. |
- |
slot slotId |
Displays information about errors on the board in a specified slot. |
The value is an integer or a string of characters. You can enter a question mark ? and select a value from the displayed value range. |
Usage Guidelines
Usage Scenario
To check information about errors in the system, run the display error-information command.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display error-information 1 verbose ================= Error info (no: 0 idx: 0) ================= slot Process: 11 Process Name: LM Error Type: Memory Refree FreeAddress: 0xb2a54c30 Free File: dddd.c : 273 Free Time: 2015-03-26 18:12:52 Last Malloc File: abc.c : 123 Last Malloc Tick: 219353 Last Free File: dddd.c : 273 Dopra Version: DOPRA SSP V300R002C30B022 VRP Version: V800R010C00B180 Patch Version: Show CallStack: #00: liblocbase.so(VRP_Free_F) #01: location(_start) #02: kernel(System symbol) #03: kernel(System symbol) #04: kernel(System symbol) #05: kernel(System symbol) #06: kernel(System symbol) #07: kernel(System symbol) #08: kernel(System symbol) #09: kernel(System symbol)
Item | Description |
---|---|
Error Type | Error type. |
slot | Slot of the board on which an error occurs. |
Process | ID of the process in which an error occurs. |
Process Name | Name of the process in which an error occurs. |
Free File | File name recorded when a memory release error occurred. |
Free Time | Time when a memory release error occurred. |
Last Malloc File | File that last applied for memory. |
Last Malloc Tick | Tick that last applied for memory. |
Last Free File | File that last leased memory. |
Dopra Version | DOPRA version. |
VRP Version | VRP version. |
Patch Version | Patch version. |
Show CallStack | Information about call stacks. |
FreeAddress | Address recorded when a memory release error occurred. |
display exception-delay-reset switch status
Function
The display exception-delay-reset switch status command displays the status of the delayed reset function, remaining times for the delayed reset function to take effect, and delay after which the faulty board is reset.
Usage Guidelines
To check the status of the delayed reset function, remaining times for the delayed reset function to take effect, and delay after which the faulty board is reset.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display exception-delay-reset switch status all ----------------------------------------------------------- Slot status valid-times delay-time(min) ----------------------------------------------------------- 1/17 OFF NA NA 1/18 ON 1 15 1/3 ON 1 15 1/4 ON 1 15 -----------------------------------------------------------
display fd
Parameters
Parameter | Description | Value |
---|---|---|
process processid |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
all |
Displays file handle information about all processes. |
- |
Usage Guidelines
Usage Scenario
To check file handle information about one or more processes in a system commissioning scenario, run the display fd process command. The command output facilitates fault locating.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display fd process 3 -------------------------------------------------------------------------------- ProcId Fd LastAccessTime LastModifyTime LastStatusTime FileName -------------------------------------------------------------------------------- 3 0 2010-05-08 09:31:08 2010-05-08 09:31:08 2016-06-05 17:09:11 /dev/null 3 1 2016-07-29 02:31:29 2016-07-29 03:21:56 2016-07-29 03:21:56 /opt/svrp/startlog/svrp_start_0729_02:31:29.log 3 2 2016-07-29 02:31:35 2016-07-29 02:33:47 2016-07-29 02:33:47 /opt/svrp/router1/1-17/vrpv8/var/log/VrpStdErr.log 3 3 2016-06-05 17:09:08 2016-06-05 17:09:08 2016-06-05 17:09:08 anon_inode:[eventpoll] 3 4 2016-07-29 02:34:13 2016-07-29 02:34:13 2016-07-29 02:34:13 /opt/svrp/router1/1-17/vrpv8/var/log/VRP_STARTUP_STAMP_LOG 3 5 0000-00-00 00:00:00 0000-00-00 00:00:00 0000-00-00 00:00:00 socket:[40617763] 3 6 0000-00-00 00:00:00 0000-00-00 00:00:00 0000-00-00 00:00:00 socket:[40616877] 3 7 0000-00-00 00:00:00 0000-00-00 00:00:00 0000-00-00 00:00:00 socket:[40617765] 3 8 2016-07-27 07:28:27 2016-07-27 07:28:27 2016-07-29 02:31:29 /dev/shm/DOPRA-11880003-Alive 3 9 0000-00-00 00:00:00 0000-00-00 00:00:00 0000-00-00 00:00:00 socket:[40616885] 3 10 2016-07-27 07:28:27 2016-07-27 07:28:27 2016-07-29 02:31:29 /dev/shm/DOPRA-11880003-Alive 3 11 2016-07-29 02:31:38 2016-07-29 02:31:38 2016-07-29 02:31:38 /proc/76031/stat 3 12 2016-07-29 02:31:36 2016-07-29 02:31:36 2016-07-29 02:31:36 /proc/stat 3 13 2016-07-29 02:31:38 2016-07-29 02:31:38 2016-07-29 02:31:38 pipe:[40617756] 3 14 2016-07-29 02:31:36 2016-07-29 02:31:36 2016-07-29 02:31:36 /proc/stat 3 15 2016-07-29 02:31:38 2016-07-29 02:31:38 2016-07-29 02:31:38 /proc/76031/maps 3 16 2016-07-29 02:31:36 2016-07-29 02:31:36 2016-07-29 02:31:36 /proc/stat 3 17 2016-07-29 02:31:38 2016-07-29 02:31:38 2016-07-29 02:31:38 /proc/76031/stat 3 18 2016-06-05 17:09:08 2016-06-05 17:09:08 2016-06-05 17:09:08 anon_inode:[eventpoll] 3 19 2016-07-29 02:31:38 2016-07-29 02:31:38 2016-07-29 02:31:38 pipe:[40617788] 3 20 2016-07-29 02:31:38 2016-07-29 02:31:38 2016-07-29 02:31:38 pipe:[40617788] 3 21 2016-07-29 02:33:46 2016-07-29 02:33:46 2016-07-29 02:33:46 /opt/svrp/router1/1-17/vrpv8/var/log/.stdbuffhd_1_17 3 22 2016-07-29 03:21:55 2016-07-29 03:21:55 2016-07-29 03:21:55 pipe:[40617757] 3 23 2016-07-29 02:31:35 2016-07-29 02:33:46 2016-07-29 02:33:46 /opt/svrp/router1/1-17/vrpv8/var/log/VRP_STDBUFF_1_17 3 24 2016-07-29 02:34:44 2016-07-29 02:34:44 2016-07-29 02:34:44 /opt/svrp/router1/1-17/vrpv8/var/log/.stloghdr_1_17 3 25 2016-07-29 02:31:35 2016-07-29 02:34:44 2016-07-29 02:34:44 /opt/svrp/router1/1-17/vrpv8/var/log/SSP_START_LOG_1_17 3 26 2016-07-29 03:21:58 2016-07-29 03:21:58 2016-07-29 03:21:58 /opt/svrp/router1/1-17/vrpv8/var/log/HA_L3R1C1B17_s0.log 3 27 0000-00-00 00:00:00 0000-00-00 00:00:00 0000-00-00 00:00:00 socket:[40617796] 3 28 0000-00-00 00:00:00 0000-00-00 00:00:00 0000-00-00 00:00:00 socket:[40617797] 3 29 2016-07-29 02:31:38 2016-07-29 02:31:38 2016-07-29 02:31:38 /proc/76031/fd 3 30 2016-07-27 09:46:59 2016-07-27 09:46:59 2016-07-27 09:46:59 /opt/svrp/router1/1-17/V800R013C00B180/vrpv8/pkg_pool/program/current/res/cli/cli_final.cmd 3 31 0000-00-00 00:00:00 0000-00-00 00:00:00 0000-00-00 00:00:00 socket:[40617800] 3 32 2016-07-29 02:34:13 2016-07-29 02:34:13 2016-07-29 02:34:13 /opt/svrp/router1/1-17/vrpv8/var/log/rpm.log 3 33 0000-00-00 00:00:00 0000-00-00 00:00:00 0000-00-00 00:00:00 socket:[40617855] 3 34 2016-07-29 02:31:44 2016-07-29 02:31:44 2016-07-29 02:31:44 /opt/svrp/router1/1-17/vrpv8/tmp/tfs_lib_to_worker_channel_log_0_1_3 3 35 2016-06-05 17:09:08 2016-06-05 17:09:08 2016-06-05 17:09:08 anon_inode:[eventpoll] 3 36 2016-07-29 02:31:44 2016-07-29 02:31:44 2016-07-29 02:31:44 /opt/svrp/router1/1-17/vrpv8/tmp/tfs_lib_to_worker_channel_0_1_3 3 37 2016-07-29 03:18:50 2016-07-29 03:18:50 2016-07-29 03:18:50 /opt/svrp/router1/1-17/V800R013C00B180/vrpv8/var/log/LOGSERVER_blackbox -------------------------------------------------------------------------------- Total = 38
Item | Description |
---|---|
ProcId | Process ID. |
Fd | File descriptor. |
LastAccessTime | Time when the file was accessed last time. |
LastModifyTime | Time when the file was modified last time. |
LastStatusTime | Time when file information, such as file permission and owner information, was modified last time. |
FileName | File Name. |
display inspect infrastructure
Function
The display inspect infrastructure command displays infrastructure debugging information about a specified board.
Parameters
Parameter | Description | Value |
---|---|---|
cmdstring |
Infrastructure debug command.
|
It is a string data type. The value ranges from 1 to 31 characters. |
slot slotid |
Specifies a slot ID. |
- |
Usage Guidelines
To check information about a specified process in a system commissioning scenario, run the display inspect infrastructure command. The command output the information about the process of the infrastructure.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display inspect infrastructure slot 10 "show cpu 1" ******************************************************************************** Summary information: -------------------------------------------------------------------------------- Current queried CPU core id: 0 process_id process_name thread_id thread_name 1 systemd 1 systemd 2 kthreadd 2 kthreadd 3 ksoftirqd/0 3 ksoftirqd/0 5 kworker/0:0H 5 kworker/0:0H 7 migration/0 7 migration/0 8 rcu_bh 8 rcu_bh 9 rcuob/0 9 rcuob/0 10 rcuob/1 10 rcuob/1 --------------------------------------------------------------------------------
display inspect process
Format
display inspect process processid { memory | reltimer | dms_msg | rtf_info | procinfo | dms_pipe | handle | box | dms_cam | dms_mcfcm | dms_fcm | patchinfo | cfginfo | queueinfo | dms_hpc | simple-memory | dms_meshtcp | dms_mesh } cmdstring [ para1 [ para2 [ para3 [ para4 ] ] ] ]
Parameters
Parameter | Description | Value |
---|---|---|
memory |
Displays memory information about the specified process. |
- |
reltimer |
Displays real-time information about the specified process. |
- |
dms_msg |
Displays DMS_MSG information about the specified process. |
- |
rtf_info |
Displays RTF information about the specified process. |
- |
procinfo |
Displays process information. |
- |
dms_pipe |
Displays DMS_PIPE information about the specified process. |
- |
handle |
Displays handle information about the specified process. |
- |
box |
Displays dopra black box information about the specified process. |
- |
dms_cam |
Displays DMS_CAM information about the specified process. |
- |
dms_mcfcm |
Displays DMS_MCFCM information about the specified process. |
- |
dms_fcm |
Displays DMS_FCM information about the specified process. |
- |
patchinfo |
Displays patch debugging information about the specified process. |
- |
cfginfo |
Displays module configuration entry information about the specified process. |
- |
dms_hpc |
Displays dms_hpc information about the specified process. |
- |
simple-memory |
Display simple memory information about the specified process. |
- |
dms_meshtcp |
meshtcp communication module. |
- |
dms_mesh |
Mesh communication module. |
- |
Usage Guidelines
Usage Scenario
This command is used to query information about a specified process in the system commissioning scenario. The command output helps locate process-related faults.
Currently, this command can be used only on the main control board and interface board.- memory summary: displays usage information about all memory partitions
- memory usage-state <para1> <para2>: displays memory usage of all handles
- memory statistic <para1>: displays memory instance statistics
- memory brief <para1>: displays memory information of a specified partition
- memory detail-info <para1> <para2>: displays debugging information about the memory block that has been applied for
- reltimer summary: displays timer information of all handles
- reltimer brief <para1> <para2> <para3>: displays timer information of a specified handle
- reltimer brief-condition <para1> <para2> <para3>: displays information about the timer with a specified name
- reltimer detail <para1>: displays detailed information about the timer
- dms_msg IPC-overtime <para1> <para2> <para3> <para4>: displays information about IPC queue timeout messages
- dms_msg area-detail <para1>: displays detailed information about the message partition
- dms_msg area-summary <para1> <para2>: displays specifies the message partition information.
- dms_msg area-usage: displays message partition usage information
- dms_msg component-status <para1> <para2> <para3>: displays number of messages in different states on the component
- dms_msg damaged-info <para1> <para2> <para3>: displays message memory damage information
- dms_msg leaked-info <para1> <para2> <para3> <para4>: displays message packet leakage information
- dms_msg overtime-info <para1> <para2> <para3> <para4>: displays message timeout processing information
- dms_msg peak-info <para1> <para2>: displays peak information about the message cache and CID information in each message partition
- dms_msg recv-statistic <para1>: displays information about the receiver based on the component pair
- dms_msg send-statistic <para1>: displays component pair-based sender information
- dms_msg starved-info <para1>: displays information about the message packets that are starved.
- dms_msg usage-info <para1> <para2> <para3>: displays message snapshot of a specified message partition
- rtf_info comp <para1>: displays detailed rtf information about the component
- rtf_info comp-queue <para1>: displays detailed queue information about the component
- rtf_info comp-type <para1>: displays component priority information
- rtf_info container <para1>: displays scheduling container information
- rtf_info cpu-affinity <para1>: displays component information in different CPU cores
- procinfo task-affinity <para1>: displays device task information
- dms_pipe detail <para1>: displays trust data information of a specified pipe ID
- dms_pipe recv-schedule <para1> <para2>: displays scheduling information at the receive end of a pipe
- dms_pipe send-schedule <para1> <para2>: displays scheduling information at the transmit end of a pipe
- dms_pipe starved-info <para1> <para2>: displays information about pipe starvation or leakage
- dms_pipe state <para1>: displays status of a pipe with a specified ID
- dms_pipe statistic <para1>: displays statistics about a specified pipe
- handle detail <para1>: displays details about a specified handle
- handle summary: displays information about all handles
- box record <para1> <para2> <para3>: displays records of a specified box
- box summary: displays total box information
- dms_cam all <para1>: displays DMS component and process address information
- dms_cam component-info <para1>: displays DMS component address information
- dms_cam process-info <para1>: displays DMS process address information
- dms_fcm dest-token <para1>: displays destination token for unicast flow control
- dms_fcm src-token <para1>: displays source token for unicast flow control
- dms_fcm statistic <para1> <para2>: displays unicast statistics
- dms_fcm summary: displays total unicast information
- dms_mcfcm comp-status <para1> <para2>: displays status information about multicast components
- dms_mcfcm dest-token <para1>: displays token of the multicast destination end
- dms_mcfcm src-token <para1>: displays token of the multicast source end
- dms_mcfcm statistic <para1>: displays multicast statistics
- patchinfo detail <para1>: displays detailed information about a specified patch
- patchinfo summary: displays information about all patches
- cfginfo detail <para1>: displays configuration information about a specified module
- cfginfo startup-order: displays startup sequence of all modules
- cfginfo summary: displays information about all modules
- queueinfo detail-handle <para1>: displays queue information of a specified handle ID
- queueinfo detail-queue <para1>: displays information about a specified queue
- queueinfo summary: displays information about all queues
- dms_hpc detail-handle: displays detailed information about the HPC pipe
- dms_hpc summary: displays the sum of HPC pipe information.
- dms_hpc topn-handle: displays top N HPC pipe information
- simple-memory group: displays all simple memory information.
- simple-memory handle: displays simple memory information about all handles.
- dms_mesh help: displays the help information.
- dms_mesh link-info: displays process link information.
- dms_mesh local-info: displays process address information.
- dms_meshtcp help: displays the help information.
- dms_meshtcp link-info: displays process link information.
- dms_meshtcp mcgrp: displays HPP multicast group information.
- dms_meshtcp msg-stat: displays information about the message sender and receiver.
- dms_meshtcp queue-info: displays information about queues on the transmit end.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display inspect process 1001 procinfo task-affinity 0 ******************************************************************************** Summary information: -------------------------------------------------------------------------------- Current queried CPU core id: 0 -------------------------------------------------------------------------------- process_id process_name thread_id thread_name 1 init 1 init 2 kthreadd 2 kthreadd 3 ksoftirqd/0 3 ksoftirqd/0 5 kworker/u:0 5 kworker/u:0 6 migration/0 6 migration/0 83008 ose_sdv 83173 TaskTestCpu_98 83008 ose_sdv 83174 TaskTestCpu_99 -------------------------------------------------------------------------------- Tasks' count is 319. ********************************************************************************
<HUAWEI> system-view [~HUAWEI] diagnose Total Created Count = 19 Default Queue Size = 768 Queue Num In The First Page = 300 Queue Num In New created Page = 50 The Mem PtNo of Queue Use = 0 -------------------------------------------------------------------------------- QID QueMode TotLen CurLen MaxSize Block Block PeakLen Name TaskId(W) TaskId(R) -------------------------------------------------------------------------------- 1 FIFO|SYN 1000 0 32 0 0 0 rtfQueueName 2 FIFO|SYN 1000 0 32 0 0 0 evtQueName_0 3 FIFO|SYN 1000 0 32 0 0 0 rtfQueueName 4 FIFO|SYN 1000 0 32 0 0 0 evtQueName_0 5 FIFO|SYN 1000 0 32 0 0 0 rtfQueueName 6 FIFO|SYN 1000 0 32 0 0 0 evtQueName_0 7 FIFO|SYN 1000 0 32 0 0 0 evtQueName_1 8 FIFO|SYN 1000 0 32 0 0 0 rtfQueueName 9 FIFO|SYN 1000 0 32 0 0 0 evtQueName_0 10 FIFO|SYN 1000 0 32 0 0 0 rtfQueueName 11 FIFO|SYN 1000 0 32 0 0 0 evtQueName_0 12 FIFO|SYN 1000 0 32 0 0 0 rtfQueueName 13 FIFO|SYN 1000 0 32 0 0 0 evtQueName_0 14 FIFO|SYN 1000 0 32 0 0 0 rtfQueueName 15 FIFO|SYN 1000 0 32 0 0 0 evtQueName_0 16 FIFO|SYN 1000 0 32 0 0 0 rtfQueueName 17 FIFO|SYN 1000 0 32 0 0 0 evtQueName_0 18 FIFO|SYN 1000 0 32 0 0 0 rtfQueueName 19 FIFO|SYN 1000 0 32 0 0 0 evtQueName_0 ********************************************************************************
<HUAWEI> system-view [~HUAWEI] diagnose Queue Name = rtfQueueName Queue Handle = 527 Queue Mode = FIFO|SYN Queue Trace Switch = True Total Length = 1000 Current Length = 0 Used Percent = 0% Max Msg Size = 32 Queue Msg Start Addr = 0xf1436400 Queue Msg Head Index = 0 Queue Msg Tail Index = 0 Total Write Count = 0 Total Read Count = 0 Write Count For Msg Full = 0 (Asy Write) Write Count For Time Out = 0 (Syn Write) Read Count For No Msg = 0 (Asy Read) Read Count For Time Out = 0 (Syn Read) Count Of Waiting To Write = 0 Count Of Waiting To Read = 0 Task ID Created This Queue = -1 (0 For None) Task ID Last-Readed-OK = 0 (0 For None) Task ID Last-Writed-OK = 0 (0 For None) Task ID Writing-Blocked = 0 (0 For None) Task ID Reading-Blocked = 0 (0 For None) Peak Length = 0 Peak Time = 0000.00.00 00:00:00[LMT] Queue AutoFlex = Disable ********************************************************************************
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display inspect process 1001 memory summary ******************************************************************************** PtNo PtName PieceNum TotalSize(B) FreeSize(B) MaxUsableSize(B) Usage -------------------------------------------------------------------------------- 0 SYSPT 1 268,435,456 263,488,428 263,239,356 1% 1 EXTPT 1 268,435,456 268,432,596 268,431,852 0% 2 USRPT 1 4,000,000 3,997,140 3,996,396 0% 3 MSG_PT 1 5,194,304 526,396 525,652 89% 4 Pipe_Dbf 1 7,815,744 7,376,420 7,367,764 5% -------------------------------------------------------------------------------- Total 5 553,880,960 543,820,980 --- 1% ********************************************************************************
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display inspect process 1001 handle summary ******************************************************************************** Total module number : 142 -------------------------------------------------------------------------------- Id Name Status | Id Name Status -------------------------------------------------------------------------------- 0 vos.sys install | 1 VOS_PID_TIMER install 2 VOS_PID_SYSMT install | 3 VOS_PID_HTMAILS install 4 VOS_PID_ADAPT install | 5 VOS_PID_BAK install 6 VOS_PID_SMOOTH install | 7 VOS_PID_ARBAGNT install 8 VOS_PID_ARBSERV install | 9 VOS_PID_DBKNL install 10 VOS_PID_Monitor install | 11 VOS_PID_PATCH install 12 VOS_PID_PATCHLOAD install | 13 VOS_PID_INSPECT install 14 VOS_PID_HM install | 15 VOS_PID_MCC install 16 PID_NTPC install | 17 SMP_PID_SNMP install 18 SMP_PID_CMD_SNMP install | 19 PID_SNTPS install 20 PID_SNTPC install | 21 VOS_PID_ITEST install 22 VOS_PID_BAKTEST install | 23 VOS_PID_EVENT_PFM_TST1 install 24 VOS_PID_EVENT_PFM_TST2 install | 25 VOS_PID_MSG_PFM_TST1 install 26 VOS_PID_MSG_PFM_TST2 install | 27 VOS_PID_MSG_PFM_TST3 install 28 VOS_PID_MSG_PFM_TST4 install | 29 VOS_PID_MSG_PFM_TST5 install 30 VOS_PID_UEST install | 31 VOS_PID_TESTSTUDIO install 32 VOS_PID_AABAKDM install | 33 VOS_PID_ASOM install 34 VOS_PID_WNOM install | 35 VOS_PID_TFTP install 36 VOS_PID_VFS install | 37 VOS_PID_ZIP install 38 VOS_PID_RESERVE_38 install | 39 VOS_PID_RESERVE_39 install 40 VOS_PID_RESERVE_40 install | 41 VOS_PID_RESERVE_41 install 42 VOS_PID_RESERVE_42 install | 43 VOS_PID_RESERVE_43 install 44 VOS_PID_RESERVE_44 install | 45 PID_DBG_SERVER install 46 PID_DBG_AGENT install | 47 PID_DLOG_SERVER install 48 PID_DLOG_CLIENT install | 49 VOS_PID_RESERVE_49 install 50 VOS_PID_RESERVE_50 install | 51 VOS_PID_RESERVE_51 install 52 VOS_PID_RESERVE_52 install | 53 VOS_PID_RESERVE_53 install 54 VOS_PID_RESERVE_54 install | 55 VOS_PID_RESERVE_55 install 56 VOS_PID_RESERVE_56 install | 57 VOS_PID_RESERVE_57 install 58 VOS_PID_RESERVE_58 install | 59 VOS_PID_RESERVE_59 install 60 VOS_PID_RESERVE_60 install | 61 VOS_PID_RESERVE_61 install 62 VOS_PID_RESERVE_62 install | 63 VOS_PID_RESERVE_63 install 64 VOS_PID_RESERVE_64 install | 65 VOS_PID_RESERVE_65 install 66 VOS_PID_RESERVE_66 install | 67 VOS_PID_RESERVE_67 install 68 VOS_PID_RESERVE_68 install | 69 VOS_PID_RESERVE_69 install 70 VOS_PID_RESERVE_70 install | 71 VOS_PID_RESERVE_71 install 72 VOS_PID_RESERVE_72 install | 73 VOS_PID_RESERVE_73 install 74 VOS_PID_RESERVE_74 install | 75 VOS_PID_RESERVE_75 install 76 VOS_PID_RESERVE_76 install | 77 VOS_PID_RESERVE_77 install 78 VOS_PID_RESERVE_78 install | 79 VOS_PID_RESERVE_79 install 80 VOS_PID_RESERVE_80 install | 81 VOS_PID_RESERVE_81 install 82 VOS_PID_RESERVE_82 install | 83 VOS_PID_RESERVE_83 install 84 VOS_PID_RESERVE_84 install | 85 VOS_PID_RESERVE_85 install 86 VOS_PID_RESERVE_86 install | 87 VOS_PID_RESERVE_87 install 88 VOS_PID_RESERVE_88 install | 89 VOS_PID_RESERVE_89 install 90 VOS_PID_RESERVE_90 install | 91 VOS_PID_RESERVE_91 install 92 VOS_PID_RESERVE_92 install | 93 VOS_PID_RESERVE_93 install 94 VOS_PID_RESERVE_94 install | 95 VOS_PID_RESERVE_95 install 96 VOS_PID_RESERVE_96 install | 97 VOS_PID_RESERVE_97 install 98 VOS_PID_RESERVE_98 install | 99 VOS_PID_RESERVE_99 install 100 VOS_PID_RESERVE_100 install | 101 TEST_PID1_1 install 102 TEST_PID1_2 install | 103 TEST_PID1_3 install 104 TEST_PID1_4 install | 105 TEST_PID1_5 install 106 TEST_PID2_1 install | 107 TEST_PID2_2 install 108 TEST_PID2_3 install | 109 TEST_PID2_4 install 110 TEST_PID2_5 install | 111 TEST_PID3_1 install 112 vos.pid.reserve112$ install | 113 vos.pid.reserve113$ install 114 vos.pid.reserve114$ install | 115 vos.pid.reserve115$ install 116 vos.pid.reserve116$ install | 117 vos.pid.reserve117$ install 118 vos.pid.reserve118$ install | 119 vos.pid.reserve119$ install 120 vos.handle.invalid install | 121 vos_sema install 122 vos_task install | 123 vos_timer install 124 dms.msp install | 125 vos.memleakscan.memleakscanPIDinstall 126 vos_queue install | 127 dms.msq install 128 vos_rtsched install | 129 dms.tkm install 130 dms.cam install | 131 dms.pam install 132 dms.mcm install | 133 dms.dbg install 134 rtf.cma install | 135 rtf.ccm install 136 rtf.scm install | 137 vos_rtcom install 138 dms.fcm install | 139 dms.mcfcm install 140 dms.pipe install | 141 dms.dbf install 142 dms.pipeshow install ********************************************************************************
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display inspect process 1001 dms_pipe detail 2149056513 ************************************************************ ---------------------------------------- srcCommId : 0x806503f6 dstCommId : 0x8078271a localPipeId : 2149056513 peerPipeId : 3223322661 serviceId : 65536 status : SEND leftTokenNum : 5000 usedSchAreaTokenNum : 0 PreAllocTokenNum : 0 leftHighPrioTokenNum : 0 usedSchAreaHighPrioTokenNum : 0 PreAllocHighPrioTokenNum : 0 HighLowPrioTokenRadix : 0 Congest : NORMAL send package num : 0 PipeQueTokenNum : 0 BasicTokenNum : 5000 MaxApplyHighPrioTokenNum : 0 MaxApplyTokenNum : 0 TokenThreshold : 2500 PipeQueTokenNum : 0 PipeManNum : 0 AckNum : 0 CurTokenSeqNum : 0 OldSeqNum : 0 NewSeqNum : 0 ************************************************************
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display inspect process 1001 dms_msg leaked-info 100 0 1 100 ******************************************************************************** Leaked message info: No. SendCid RecvCid RecvIid Length MsgAddr Status PastTime(ms) 0001 0x00011111 0x00000000 0x0 300 0xc8300100 ALLOCATED 1001 The number of Leaked messages( >= 100(ms) ) is:1 ********************************************************************************
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display inspect process 1001 dms_mcfcm comp-status 1 2147483665 ******************************************************************************* McId SendId RecvId recvIid WorkStatus(yes/no) BlockStatus SpareToken ------------------------------------------------------------------------------- 1 0x80000010 0x80000011 0 JOINED UNBLOCK 40 *******************************************************************************
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display inspect process 1001 dms_fcm summary ************************************************************ sendCid recvCid spareTokenNum CompState 0x660407 0x6a0409 10 active 0xa60413 0x7a0404 10 active 0x660407 0x7a0404 10 active 0xa60413 0x6a0409 10 active 0xa60413 0x6a271b 15 active 0x670406 0x6a271b 10 active 0x57040e 0x7a0404 10 active 0x740412 0xad0414 10 active 0x57040e 0x6a0409 10 active 0x7703f5 0x7a0404 10 active 0x670406 0x7a0404 10 active 0xa80437 0x790405 10 active 0xb00416 0x712717 10 active 0x7703f5 0x6a0409 10 active 0x3de0418 0x7303f6 10 active 0x7303f6 0x3de0418 10 active 0x670406 0x6a0409 10 active 0xa80437 0x6a0409 15 active 0xa80437 0x7a0404 10 active 0x380417 0x7a0404 5 active 0x800303f8 0x6003f9 15 active 0xb00416 0x730443 10 active 0xb00416 0x7303f6 10 active 0x9a0410 0x7a0404 10 active 0x740412 0x702715 10 active 0x809c044b 0x80a8044c 10 active 0x80a8044c 0x809c044b 10 active 0xa60413 0x3de0418 30 active 0x3de0418 0xa60413 10 active 0x740412 0x212714 10 active 0x3de0418 0x7703f5 10 active 0x7703f5 0x3de0418 10 active 0x670406 0x8f03fe 10 active 0xaf0415 0x770442 30 active 0x740412 0x820435 10 active 0xaf0415 0x7703f5 10 active 0x6503f3 0x7203ff 10 active sendCid recvCid spareTokenNum CompState 0x830432 0xa80437 60 passive 0x6503eb 0x670406 60 passive 0x65040c 0x670406 10 passive 0x6503fc 0x670406 10 passive 0x65041e 0x670406 10 passive 0x65042f 0x670406 10 passive 0x650440 0x670406 10 passive 0x650402 0x670406 10 passive 0x840433 0xa80437 60 passive 0x650434 0x670406 29 passive 0x850431 0xa80437 60 passive 0xa50445 0xa80437 10 passive 0x78271a 0x670406 15 passive 0x782719 0x670406 10 passive ************************************************************
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display inspect process 1001 dms_cam component-info 2149656339 ************************************************************ Csi Cpi HA procPhyId ------------------------------------------------------------ 0x00212713 0x80212713 Standby 10001 ************************************************************
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display inspect process 1001 cfginfo summary ******************************************************************************** All module id and name info : -------------------------------------------------------------------------------- Id Module Name Id Module Name Id Module Name 0 dbg_cmd 1 dbg_cmdbase 2 dbg_cmdparse 3 dms_cam 4 dms_dbg 5 dms_dbgshow 6 dms_fcm 7 dms_fcmshow 8 dms_mcfcm 9 dms_mcfcmshow 10 dms_mcm 11 dms_msp 12 dms_msq 13 dms_pam 14 dms_pipe 15 dms_pipedebug 16 dms_pipeshow 17 dms_stats 18 dms_tipc 19 dms_token 20 dms_ucm 21 dms_ufpcom 22 mbak_bak 23 mbsc_callstack 24 mbsc_cpupos 25 mbsc_cpupproc 26 mbsc_cpuptask ********************************************************************************
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display inspect process 1001 box summary ******************************************************************************** RegionId Prio Type Mode RegionAddr RegionSize RecNum Resvsize CurSeg RegionName 1 High Sys Wrap 0xf610e7b0 0x850 8 0 0 Log_Info 2 High Sys Wrap 0xf610df60 0x850 6 0 0 Log_Warning 3 High Sys Wrap 0xf60cdf10 0x40050 883 0 0 Log_Error 4 High Sys Wrap 0xf60cd6c0 0x850 0 0 0 Log_Except 5 High Sys Wrap 0xf60cd5f0 0xd0 1 0 0 vos_printf 6 High Sys Wrap 0xf60cd1a0 0x450 0 0 0 Reboot 7 High Sys Wrap 0xf60cc150 0x1050 0 0 0 VOS_ASSERT 8 High Sys Wrap 0xf60c4100 0x8050 0 0 0 MemoryDamage 9 High Sys Wrap 0xf60c30b0 0x1050 0 0 0 CpupTrace 10 High Sys Wrap 0xf60c1f00 0x11b0 0 0 2 Exception 11 High Self --- 0xf60c0d98 0x1168 --- --- 0 Exception_status 12 High Sys Wrap 0xf60b8d48 0x8050 0 0 0 MemoryLeakscan 13 High Sys Wrap 0xf60b4e78 0x3ed0 0 0 0 DeadLoop 14 High Sys Wrap 0xf6034e28 0x80050 0 0 0 MemoryLeak 15 High Sys Wrap 0xf602cdd8 0x8050 0 0 0 RelTmrOverLoad 16 Low Self --- 0xf5f97720 0x28e0 --- --- 0 DmsDbgMsgTrace 17 High Sys Wrap 0xf6016b28 0x162b0 3 0 0 DmsMsgOvertime 18 High Sys Wrap 0xf6015750 0x13d8 0 0 0 DmsMsgLeaked 19 High Sys Wrap 0xf6014378 0x13d8 0 0 0 DmsMsgStarved 20 High Sys Wrap 0xf600f508 0x4e70 0 0 0 DmsPipeOvertime ********************************************************************************
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display inspect process 1001 simple-memory handle ******************************************************************************** Support·Modes: Fix(The·handle·can·apply·for·memory·of·only·a·specified·size) Dyn(The·handle·can·apply·for·memory·of·a·variety·of·sizes·that·are·less·than·252·bytes) MaxDyn(Similar·to·the·Dyn·mode·but·allows·you·to·define·the·maximum·value) FixAppend(Similar·to·the·Fix·mode·but·supports·independent·expansion) DynAppend(Similar·to·the·Dyn·mode·but·supports·independent·expansion) MaxDynAppend(Similar·to·the·MaxDyn·mode·but·supports·independent·expansion) -------------------------------------------------------------------------------- Handle=appcfg_80cf03ec_00000003·Mode=Dyn·MaxType=63·MaxUse=4160·CurUse=4160 0001:·Size=48····TotalBlock=42·····MallocBlock=6······CachedNum=36·····BaseSize=2048···Increase=1344 0002:·Size=60····TotalBlock=34·····MallocBlock=5······CachedNum=29·····BaseSize=2048···Increase=1075 0003:·Size=80····TotalBlock=25·····MallocBlock=2······CachedNum=23·····BaseSize=2048···Increase=806 0004:·Size=88····TotalBlock=69·····MallocBlock=28·····CachedNum=41·····BaseSize=4096···Increase=733 0005:·Size=108···TotalBlock=18·····MallocBlock=1······CachedNum=17·····BaseSize=2048···Increase=597 0006:·Size=140···TotalBlock=14·····MallocBlock=6······CachedNum=8······BaseSize=2048···Increase=460 ********************************************************************************
Item | Description |
---|---|
Current Queue Count | Total number of queues that are created and exist in the current process. |
Current Length | Currently used queue length. |
process_id | Process ID. |
process_name | Process name. |
thread_id | Thread ID. |
thread_name | Thread name. |
Total Created Count | Total number of queues created for the current process. |
Total Write Count | Number of times that a queue is written. |
Total Read Count | Number of times that a queue is read. |
Count Of Waiting To Write | Number of waiting times when the current synchronous message is fully written. |
Count Of Waiting To Read | Number of waiting times when the current synchronous message is not read. |
Default Queue Size | Default queue size. |
Queue Num In The First Page | Number of queues that can be created for a process. |
Queue Num In New created Page | Number of queues that can be created for each process expansion. |
Queue ID | Queue ID. |
Queue Name | Queue name. |
Queue Handle | ID of the handle to which a queue belongs. |
Queue Trace Switch | Whether the queue track function is enabled:
|
Queue Msg Start Addr | Start address of the queue message memory. |
Queue Msg Head Index | Index of the current queue header, that is, the position where the header is located. |
Queue Msg Tail Index | Index of the current queue tail, that is, the position where the tail is located. |
Queue AutoFlex | Whether the auto-scaling function is enabled:
|
The Mem PtNo of Queue Use | Memory partition number used to apply for memory during queue creation. |
QID | Queue ID. |
QueMode | Queue mode:
|
TotLen | Total length of the current queue. |
CurLen | Currently used queue length. |
MaxSize | Maximum length of a queue message. |
Block TaskId(W) | ID of the task that blocks the write queue when the queue is full. |
Block TaskId(R) | ID of the task that blocks the read queue when the queue is empty. |
PeakLen | Peak queue length. |
Name | Queue name. |
Used Percent | Use percentage of the current queue. |
Max Msg Size | Maximum length of a queue message. |
Write Count For Msg Full | Number of times that asynchronous messages are fully written. |
Write Count For Time Out | Number of waiting times when synchronous messages are fully written. |
Read Count For No Msg | Number of times that asynchronous messages are not read. |
Read Count For Time Out | Number of waiting times when synchronous messages are not read. |
Task ID Created This Queue | ID of the task used for creating a queue. |
Task ID Last-Readed-OK | ID of the last task that is successfully read. |
Task ID Last-Writed-OK | ID of the last task that is successfully written. |
Task ID Writing-Blocked | ID of the task that blocks the write queue when the queue is full. |
Task ID Reading-Blocked | ID of the task that blocks the write queue when the queue is full. |
Peak Time | Date and time when the queue length reaches the peak value. |
sendCid | ID of a transmitting component. |
recvCid | ID of a receiving component. |
spareTokenNum | Number of remaining tokens. |
CompState | Component status.
|
TotalBlock | Total·number·of·memory·blocks·in·the·memory·buffer·of·the·memory·block·of·the·corresponding·size·corresponding·to·the·handle. |
MallocBlock | Number·of·memory·blocks·that·have·been·applied·for·by·the·handle. |
CachedNum | The·number·of·free·memory·blocks·in·the·size·memory·buffer. |
BaseSize | Step·of·a·single·expansion·of·this·buffer. |
Increase | Total·Memory·Block·Threshold·for·Smooth·Memory·Reclamation. |
BlockType | Type·ID·of·a·memory·block. |
display log output
Function
The display log output command displays the configurations of debugging log output.
The display trace trigger command displays the status of the end-to-end message tracing function and the matching conditions configured for the tracing of common, timer, or pipe messages.
Format
display trace trigger [ process procId ] { traceswitch | msgconfig | packetconfig | timerconfig }
display log output [ process procId ] sspdebugconfig
display trace trigger user-def
Parameters
Parameter | Description | Value |
---|---|---|
process procId |
Specifies a process ID. |
The value ranges from 0 to 4294967295. |
traceswitch |
Displays the configuration of the message tracing function and the next-startup function configuration. |
- |
msgconfig |
Displays the matching conditions configured for the tracing of common messages. |
- |
packetconfig |
Displays the matching conditions configured for the tracing of pipe messages. |
- |
timerconfig |
Displays the matching conditions configured for the tracing of timer messages. |
- |
sspdebugconfig |
The configurations of debugging log output. |
- |
user-def |
The user define config condition. |
- |
Usage Guidelines
Usage Scenario
To check the configurations of debugging log output, run the display log output command.
To check the status of the end-to-end message tracing function and the matching conditions configured for the tracing of common, timer, or pipe messages, run the display trace trigger command.This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display log output sspdebugconfig ------------------------------------------------------------------------------------------------------------ Switch Trace Configure Information ------------------------------------------------------------------------------------------------------------ ProcessId OutputDirection BufferSize(KB) FlushTime(s) FilterId FilterCondition ------------------------------------------------------------------------------------------------------------ 2 Output to file 512 5 3 111 222 333 444 555 666 777 888 999 000 2 Output to file 512 5 4 aaa 3 Output to file 512 5 3 111 222 333 444 555 666 777 888 999 000 3 Output to file 512 5 4 aaa 4 Output to file 512 5 2 111 222 333 444 555 666 777 888 999 000 4 Output to file 512 5 3 111 222 333 444 555 666 777 888 999 000 4 Output to file 512 5 4 aaa 6 Output to file 512 5 3 111 222 333 444 555 666 777 888 999 000 6 Output to file 512 5 4 aaa 7 Output to file 512 5 3 111 222 333 444 555 666 777 888 999 000 7 Output to file 512 5 4 aaa
display memory (Diagnostic view)
Format
display memory slot slot-id
display memory [ all ]
display memory [ slot slot-id | all ] verbose
Parameters
Parameter | Description | Value |
---|---|---|
all |
Displays memory statistics of all boards. |
- |
slot slot-id |
Displays memory statistics of a specified board. |
- |
verbose |
Displays verbose memory statistics. |
- |
Usage Guidelines
Usage Scenario
The display memory command displays memory statistics on the main control board.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display memory Slot memory utilization statistics at 2011-03-18 02:53:43 429 ms -------------------------------------------------------------------------------- Slot OS memory utilization statistic: Slot OS Total Memory Is : 8248308 Kbytes Slot OS Total Memory Used Is : 607192 Kbytes Slot OS Freed Memory Is : 7641116 Kbytes Slot OS Memory Using Percentage Is : 7% -------------------------------------------------------------------------------- Slot vrp memory utilization statistic: Slot Total Memory Is : 1086963 Kbytes Slot Total Memory Used Is : 352808 Kbytes Slot Freed Memory Is : 734155 Kbytes Slot Memory Using Percentage Is : 32% -------------------------------------------------------------------------------- Slot simple memory utilization statistic: Slot Total Simple Memory Is : 17476 Kbytes Slot Total Simple Memory Used Is : 16730 Kbytes Slot Freed Simple Memory Is : 746 Kbytes Slot Simple Memory Using Percentage Is : 95% -------------------------------------------------------------------------------- Slot Memory use top 10 Process: -------------------------------------------------------------------------------- ProcessId ProcessName Total(Kbytes) Used(Kbytes) Free(Kbytes) Usage Factor -------------------------------------------------------------------------------- 3 CFG3 251481 143858 107623 27% --------------------------------------------------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display memory slot 1 Slot memory utilization statistics at 2011-04-11 09:55:18 384 ms -------------------------------------------------------------------------------- Slot OS memory utilization statistic: Slot OS Total Memory Is : 8248308 Kbytes Slot OS Total Memory Used Is : 1085752 Kbytes Slot OS Freed Memory Is : 7162556 Kbytes Slot OS Memory Using Percentage Is : 13% -------------------------------------------------------------------------------- Slot vrp memory utilization statistic: Slot Total Memory Is : 983533 Kbytes Slot Total Memory Used Is : 289392 Kbytes Slot Freed Memory Is : 694141 Kbytes Slot Memory Using Percentage Is : 29% -------------------------------------------------------------------------------- Slot simple memory utilization statistic: Slot Total Simple Memory Is : 244 Kbytes Slot Total Simple Memory Used Is : 121 Kbytes Slot Freed Simple Memory Is : 123 Kbytes Slot Simple Memory Using Percentage Is : 49% -------------------------------------------------------------------------------- Slot Memory use top 10 Process: -------------------------------------------------------------------------------- ProcessId ProcessName Total(Kbytes) Used(Kbytes) Free(Kbytes) Usage Factor -------------------------------------------------------------------------------- 3 CFG3 167507 90382 77125 53% 10001 PROTO2 209499 92006 117493 43% 10002 PROTO1 152144 33656 118488 22% 2 SM2 152144 28786 123358 18% 1000 CONSOLE 150095 24925 125170 16% 4 LM4 152144 19637 132507 12% --------------------------------------------------------------------------------
Item | Description |
---|---|
Slot OS memory utilization statistic | Statistics of a board's system memory. |
Slot OS Total Memory Is | Total size of a board's system memory. |
Slot OS Total Memory Used Is | Size of a board's system memory that has been used. |
Slot OS Freed Memory Is | Size of a board's system memory that has not been used. |
Slot OS Memory Using Percentage Is | Percentage of a board's system memory that has been used. |
Slot vrp memory utilization statistic | Statistics of a board's virtual memory. |
Slot Total Memory Is | Total size of a board's virtual memory. |
Slot Total Memory Used Is | Size of a board's virtual memory that has been used. |
Slot Freed Memory Is | Size of a board's virtual memory that has not been used. |
Slot Memory Using Percentage Is | Percentage of a board's virtual memory that has been used. |
Slot simple memory utilization statistic | Statistics of simple memory. |
Slot Total Simple Memory Is | Total size of simple memory. |
Slot Total Simple Memory Used Is | Size of simple memory that has been used. |
Slot Freed Simple Memory Is | Size of simple memory that has not been used. |
Slot Simple Memory Using Percentage Is | Percentage of simple memory that has been used. |
Slot Memory use top 10 Process | Top 10 processes with the highest memory usage. |
Freed Memory Is | Size of a process's memory that has not been used. |
Using | Percentage of a partition's memory that has been used. |
Using | Percentage of a component's memory that has been used. |
ProcessId | Process ID. |
ProcessName | Process name. |
Total(Kbytes) | Total memory size of a specified process. |
Total(Kbytes) | Total size of a partition's memory. |
Used(Kbytes) | Size of memory that has been used by a specified process. |
Used(Kbytes) | Size of a partition's memory that has been used. |
Used(Kbytes) | Size of a component's memory that has been used. |
Free(Kbytes) | Size of memory that is available for a specified process. |
Usage Factor | Percentage of memory that has been used by a specified process. |
Name | Partition name. |
display memory cid
Function
The display memory cid command displays component memory statistics.
The display pipe-memory time command displays information about the pipe memory that is occupied for a period of time in the system.
Format
display memory cid [ cidValue ]
display pipe-memory time times
display memory cid process process-id
Parameters
Parameter | Description | Value |
---|---|---|
cidValue |
Specifies a component ID. |
The value ranges from 1 to FFFFFFFF, in hexadecimal notation. |
time times |
Specifies the time interval. |
The value is an integer ranging from 0 to 4294967295, in seconds. |
process process-id |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
To check component memory statistics, run the display memory cid command.
When there is more pipe memory usage, you can use this command to check the pipe memory information of the system for a specified time.Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display pipe-memory time 10 cid pipe memory use utilization statistics at 2011-08-27 17:37:48 633 ms -------------------------------------------------------------------------------- cid pipe memory use information: -------------------------------------------------------------------------------- CID CidName Used(b) Total(b) Time ProcID Using -------------------------------------------------------------------------------- 0x8065040D SOCK 0 4115968 10 1003 0% 0x80660414 PP4 0 3077632 10 1003 0% --------------------------------------------------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display memory cid cid memory use utilization statistics at 2022-09-07 07:41:18 489 ms --------------------------------------------------------------------------------------------------------------------------------- cid memory use information: --------------------------------------------------------------------------------------------------------------------------------- CID CidName SimpleUsed(byte) SimpleTotal(byte) BlockUsed(byte) LightUsed(byte) ProcID LocalSize --------------------------------------------------------------------------------------------------------------------------------- 0x80030453 SEM_Agent 0 0 330508 0 10002 6360 0x1 LOCATION_LEVEL 0 0 120828 0 10002 0 0x80CF0454 APPCFG 4336 16032 42804 0 10002 1204 0x5 APPGLOBAL 0 0 0 0 10002 0 0x3 PIPE_PAGE 0 0 0 0 10002 0 0x4 PIPE_GLOBAL 0 0 0 0 10002 0 0x64 SMPGLOBAL 0 0 0 0 10002 0 0x8003044F SEM_Agent 0 0 420840 0 10001 6360 0x1 LOCATION_LEVEL 0 0 267336 0 10001 0 0x80717539 RM_IPV4 46240 272800 197464 0 10001 2068 0x80650451 SOCK 0 0 222300 0 10001 10536 0x80237538 RM_IPV6 31432 156340 166308 0 10001 2068 0x80227534 DIRECTRT_IPV6 12036 56452 151768 0 10001 3088 0x806F7535 DIRECTRT_IPV4 8612 48236 154368 0 10001 3088 0x87FF7533 DIX 0 0 150524 0 10001 832 0x8020753A TNLM 8460 52436 125068 0 10001 2000 0x80707537 STATICRT_IPV4 5444 38388 97248 0 10001 6376 ----------------------------------------------------------------------------------------------------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display memory cid 80F10426 mid 65 sid sid memory use information: ------------------------------------------------------------------------- CID MID SID SimpleUsed(byte) ------------------------------------------------------------------------- 0x80F10426 0x65 145 20 -------------------------------------------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display memory cid 80F10426 mid 65 sid 145 sid memory use detail information: ------------------------------------------------------------------------- CID MID SID UnitSize(byte) UnitSum ------------------------------------------------------------------------- 0x80F10426 0x65 145 20 1 -------------------------------------------------------------------------
Item | Description |
---|---|
CID | Component ID. |
CidName | Component name. |
Used(b) | Available memory (bytes). |
Total(b) | Total memory (bytes). |
Time | Memory occupation duration. |
ProcID | Process ID. |
Using | Percentage of occupied memory to total memory. |
SimpleUsed(byte) | Simple memory used, in bytes. |
SimpleTotal(byte) | Total simple memory, in bytes. |
BlockUsed(byte) | Block memory used, in bytes. |
LightUsed(byte) | Used light memory, in bytes. |
LocalSize | Size of a data area. |
MID | Module ID. |
SID | Structure ID. |
UnitSize(byte) | Unit size, in bytes. |
UnitSum | Unit quantity. |
display memory cid mid
Parameters
Parameter | Description | Value |
---|---|---|
cidValue |
Specifies a component ID. |
The value ranges from 1 to FFFFFFFF, in hexadecimal notation. |
mid midValue |
Specifies a module ID. |
The value ranges from 0 to FFFFFFFF, in hexadecimal notation. |
process process-id |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
To check component memory statistics, run the display memory cid command.
This command is supported only on the admin VS.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display memory verbose cid 8186041D mid 8410001 2022-04-06 11:18:18.604 mid memory use utilization statistics at 2022-04-06 11:18:18 613 ms ------------------------------------------------------------------------------------------------------------------------ mid memory use information: ------------------------------------------------------------------------------------------------------------------------ MID type SimpleUsed(byte) SimpleUseMax(byte) LightUse(byte) BlockUsed(byte) BlockTotal(byte) Using ------------------------------------------------------------------------------------------------------------------------- 0x8410001 Normal 0 0 0 0 47268 0% -------------------------------------------------------------------------------------------------------------------------
Item | Description |
---|---|
mid memory use utilization statistics | Indicates the memory usage of a module. |
mid memory use infomation | Memory usage of a module. |
MID | Module ID. |
type | Type. |
SimpleUsed(byte) | Used simple memory, in bytes. |
SimpleUseMax(byte) | Maximum size of the simple memory, in bytes. |
BlockUsed(byte) | Used block memory, in bytes. |
BlockTotal(byte) | Total memory size of a block, in bytes. |
Using | Utilization. |
LightUsed(byte) | Used light memory, in bytes. |
display memory mid
Parameters
Parameter | Description | Value |
---|---|---|
mid midValue |
Specifies a module ID. |
The value ranges from 1 to FFFFFFFF, in hexadecimal notation. |
sid |
Displays memory usage statistics about structures. |
- |
sidValue |
Specifies a structure ID. |
The value is an integer ranging from 0 to 255. |
cid cidValue |
Specifies a component ID. |
The value ranges from 1 to FFFFFFFF, in hexadecimal notation. |
Usage Guidelines
To check memory statistics about a specified or all components, run the display memory cid command.
This command is supported only on the admin VS.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display memory cid cid memory use utilization statistics at 2015-05-30 23:25:50 601 ms ---------------------------------------------------------------------------------------------------------------------------------- cid memory use information: ---------------------------------------------------------------------------------------------------------------------------------- CID CidName SimpleUsed(byte) SimpleTotal(byte) BlockUsed(byte) ProcID LocalSize ---------------------------------------------------------------------------------------------------------------------------------- 0x2 SIMPLE_PAGE 0 0 2690256 10001 0 0x1 LOCATION_LEVEL 0 0 1089296 10001 0 0x8003042E SEM_Agent 0 0 320684 10001 2920 0x80650436 SOCK 0 0 249012 10001 8080 0x80650431 SOCK 0 0 248704 10001 8080 0x80830434 OSPFV2LSDB 53772 145556 239472 10001 864 0x80840435 OSPFV2CRM 47348 135324 236100 10001 864 0x80712716 RM_IPV4 29244 76872 165932 10001 1140 0x806A040E FESDS 1547288 2269224 14965024 1001 71196 0x2 SIMPLE_PAGE 0 0 6758448 1001 0 0x3 PIPE_PAGE 0 0 2089120 1001 0 0x80D50407 SNMP 82720 185148 1519904 1001 36328 0x807A0409 IFM 60920 163108 1283456 1001 8104 0x1 LOCATION_LEVEL 0 0 940316 1001 0 ----------------------------------------------------------------------------------------------------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display memory cid 80F10426 mid 65 sid sid memory use information: ------------------------------------------------------------------------- CID MID SID SimpleUsed(byte) ------------------------------------------------------------------------- 0x80F10426 0x65 145 20 -------------------------------------------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display memory cid 80F10426 mid 65 sid 145 sid memory use detail information: ------------------------------------------------------------------------- CID MID SID UnitSize(byte) UnitSum ------------------------------------------------------------------------- 0x80F10426 0x65 145 20 1 -------------------------------------------------------------------------
Item | Description |
---|---|
CID | Component ID. |
CidName | Component name. |
SimpleUsed(byte) | Simple memory used, in bytes. |
SimpleTotal(byte) | Total simple memory, in bytes. |
BlockUsed(byte) | Block memory used, in bytes. |
ProcID | Process ID. |
LocalSize | Size of a data area. |
MID | Module ID. |
SID | Structure ID. |
UnitSize(byte) | Unit size, in bytes. |
UnitSum | Unit quantity. |
display memory tail-protection information
Function
The display memory tail-protection information command displays memory tail damage protection information such as process name, component name, and handle name.
Parameters
Parameter | Description | Value |
---|---|---|
slot slotID |
Specifies the slot ID of a board whose memory tail damage protection information is to be queried. |
The value is an string ranging from 1 to 32 |
all |
Displays memory tail damage protection information about all boards. |
- |
Usage Guidelines
To check memory tail damage information such as process name, component name, and switch state, run the display memory tail-protection information command. This helps locate memory tail damage or check switch state when the device runs abnormally.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] disp memory tail-protection infor all memory tail-damage informationn -------------------------------------------------------------------------------- Slot ProcessI ProcessName CompType Mid HandleName FileName Line HandleUsage AddSizeTim TailDamageTi d es mes -------------------------------------------------------------------------------- 17 10001 PROTO1 0 1 NULL compa_debug_api_test.c 1462 0% 0 1 memory tail-damage switch informationn ------------------------------------------ Slot ProcessId ProcessName Switch ------------------------------------------ 18 1013 PSM1 On 18 1012 PROTO2 On 17 2 SM On 17 3 CFG On 17 4 LM On 18 8 LM On 18 6 CFG On 18 7 SM On 17 1000 CONSOLE On 17 1001 PSM2 On 17 1002 PROTO5 On 17 1003 PSM1 On 17 1004 PROTO2 On 17 1005 RESP On 17 1006 FESMB On 17 1007 OPS On 17 1008 IGP_SR On 18 1009 OPS On 18 1010 FESMB On 18 1011 RESP On 4 10004 FES On 4 10005 PROTO3_FCTL_LC On 18 1014 PROTO5 On 18 1015 PSM2 On 18 1016 CONSOLE On 18 1017 PROTO1 On 18 1018 IGP_SR On 3 1019 LM On 4 1020 LM On 17 10001 PROTO1 On 3 10002 FES On 3 10003 PROTO3_FCTL_LC On ------------------------------------------
Item | Description |
---|---|
Slot | Indicates the slot ID. |
ProcessName | Process name. |
Mid | The value of Mid. |
HandleName | Handle ID of a memory tail damage. |
FileName | FileName. |
Line | Line. |
HandleUsage | Usage of a Handle. |
Switch | Switch state. |
ProID | Process ID. |
CompName | Component name. |
AddSizeTimes | The number of times this record is matched when malloc memory. |
TailDamageTimes | The number of times this record has memory tail damage. |
display memory(Diagnostic view)
Parameters
Parameter | Description | Value |
---|---|---|
procid |
Displays memory statistics of a specified process. |
The value is an integer ranging from 0 to 4294967295. |
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display memory 10002 Process memory utilization statistics at 2011-03-18 02:40:19 24 ms -------------------------------------------------------------------------------- Memory utilization statistic: Process Total Memory Is : 152144 Kbytes Process Total Memory Used Is : 32742 Kbytes Process Freed Memory Is : 119402 Kbytes Process Memory Using Percentage Is : 21% -------------------------------------------------------------------------------- Partition information in the Process: -------------------------------------------------------------------------------- NAME Using(Kbytes) Total(Kbytes) Using percent in Partition -------------------------------------------------------------------------------- SYSPT 2566 10240 25% dbPT 21917 122880 17% pipePT 376 4096 9% USRPT 3 3906 0% msq_node 781 781 100% commonPt 5306 6144 86% cbPt 1376 2048 67% simplePt 420 2048 20% -------------------------------------------------------------------------------- Component memory information in the process: -------------------------------------------------------------------------------- CID ComponentName Using(Kbytes) Using percent in location -------------------------------------------------------------------------------- 0x1 LOCATION_LEVEL 3598 10% 0x80712743 RM_IPV4 688 2% 0x80232742 RM_IPV6 685 2% 0x8065273D SOCK 455 1% 0x8003273A SEM_Agent 300 0% 0x2 LOCATION_LEVEL 277 0% 0x80212740 STATICRT_IPV6 155 0% 0x80702741 STATICRT_IPV4 154 0% 0x80202744 TNLM 135 0% 0x80CF273B APPCFG 89 0% 0x8022273E DIRECTRT_IPV6 82 0% 0x806F273F DIRECTRT_IPV4 81 0% 0x3 LOCATION_LEVEL 0 0% 0x4 LOCATION_LEVEL 0 0% --------------------------------------------------------------------------------
Item | Description |
---|---|
Memory utilization statistic | Memory statistics of a process. |
Memory Using Percentage Is | Percentage of a process's memory that has been used. |
Total Memory Is | Total size of a process's memory. |
Total Memory Used Is | Size of a process's memory that has been used. |
Freed Memory Is | Size of a process's memory that has not been used. |
Using | Percentage of a process's memory that has been used. |
Name | Partition name. |
Total(Kbytes) | Total memory size of a specified process. |
Component memory information in the process | Component memory statistics of a process. |
CID | Component ID. |
ComponentName | Component name. |
display memory-monitor switch-states
Function
The display memory-monitor switch-states command displays the status of memory overload detection on a board.
Usage Guidelines
Usage Scenario
This command displays the status of memory overload detection on a board.
Precautions
This command is supported only on the admin VS.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display memory-monitor switch-states slot 1 Memory monitor state ---------------------------------------- states : The states is open! ----------------------------------------
display memory-usage all
Usage Guidelines
Usage Scenario
In device routine maintenance or if a device cannot run normally, run this command to view memory utilization statistics.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display memory-usage all xx memory utilization Info: Memory utilization statistics at 2015-08-20 14:04:46 930 ms System Total Memory Is: 13502964 Kbytes Total Memory Used Is: 1770740 Kbytes Memory Using Percentage Is: 13% yy memory utilization Info: Memory utilization statistics at 2015-08-20 14:04:46 932 ms System Total Memory Is: 13502964 Kbytes Total Memory Used Is: 1770740 Kbytes Memory Using Percentage Is: 13%
Item | Description |
---|---|
xx memory utilization Info | Memory usage of xx. |
Memory utilization statistics | Date and time when memory utilization statistics were collected. |
Memory Using Percentage Is | Current memory usage on the board. |
System Total Memory Is | Total memory of the system. |
Total Memory Used Is | Memory used on the board. |
display message exhaust reset-delay-time
Function
The display message exhaust reset-delay-time command displays the timeout thresholds of message memory exhaustion durations.
Parameters
Parameter | Description | Value |
---|---|---|
all |
Displays the timeout thresholds of the message memory exhaustion durations of all processes on all boards. |
- |
slot slotId |
Specifies the slot ID of a board on which the timeout thresholds of the message memory exhaustion durations of all processes are to be queried. |
- |
process ProcessId |
Specifies the ID of the process for which the timeout threshold of the message memory exhaustion duration is to be queried. |
The value is an integer ranging from 1 to 4294967295. |
Usage Guidelines
Usage Scenario
To check the timeout thresholds of message memory exhaustion durations, run the display message exhaust reset-delay-time command.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display message exhaust reset-delay-time all ------------------------------------------------------------------ Slot ProcessID AppMessage (s) ManageMessage (s) ------------------------------------------------------------------ 3 1007 0 0 3 10003 0 0 3 10004 0 0 4 1008 0 0 4 10005 0 0 4 10006 0 0 17 2 0 0 17 3 0 0 17 4 0 0 17 1000 0 0 17 1001 0 0 17 1002 0 0 17 1003 0 0 17 1004 0 0 17 1005 0 0 17 1006 0 0 17 10001 0 0 17 10002 0 0 18 6 0 0 18 7 0 0 18 8 0 0 18 1009 0 0 18 1010 0 0 18 1011 0 0 18 1012 0 0 18 1013 0 0 18 1014 0 0 18 1015 0 0 18 1016 0 0 18 1017 0 0 ------------------------------------------------------------------
Item | Description |
---|---|
Slot | Slot ID. |
ProcessID | Process ID. |
AppMessage (s) | Timeout threshold of the message memory exhaustion duration. |
ManageMessage (s) | Timeout threshold for the memory exhaustion duration in the management message partition. |
display message pipe-statistic
Function
The display message pipe-statistic command displays statistics about the packets sent and received through the pipe.
Format
display message pipe-statistic process procid
display message pipe-statistic component compid
Parameters
Parameter | Description | Value |
---|---|---|
component compid |
Specifies a component ID. |
The value ranges is 0 to ffffffff , in hexadecimal notation. |
process procid |
Specifies the process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
When locating a pipe-related problem, run the display message pipe-statistic process command to check statistics about the packets sent and received through the pipe of a specified process or component.
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display message pipe-statistic process 1021 Send: -------------------------------------------------------------------------------- SrcCompId DesCompid LocalPipeId PeerPipeId ServiceId DopraSendNum DopraRecvNum FlowCtlNum FlowCtlLen(ms) AllocFailedNum InQueNum ConNum ConLen(ms) RunTime(us) MaxRunTime(us) AvgRunTime(us) CpuRunTime(us) MaxCpuRunTime(us) AvgCpuRunTime(us) TotalStarveTime(ms) SchCount -------------------------------------------------------------------------------- 0x80F1048F 0x80F20491 524289 1074266113 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 -------------------------------------------------------------------------------- Recv: -------------------------------------------------------------------------------- SrcCompId DesCompid LocalPipeId PeerPipeId ServiceId DopraSendNum DopraRecvNum FlowCtlNum FlowCtlLen(ms) AllocFailedNum InQueNum ConNum ConLen(ms) RunTime(us) MaxRunTime(us) AvgRunTime(us) CpuRunTime(us) MaxCpuRunTime(us) AvgCpuRunTime(us) TotalStarveTime(ms) SchCount -------------------------------------------------------------------------------- 0x80F1048F 0x80F20491 1074266113 524289 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 --------------------------------------------------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display message pipe-statistic component 80F1048F Send: -------------------------------------------------------------------------------- SrcCompId DesCompid LocalPipeId PeerPipeId ServiceId DopraSendNum DopraRecvNum FlowCtlNum FlowCtlLen(ms) AllocFailedNum InQueNum ConNum ConLen(ms) RunTime(us) MaxRunTime(us) AvgRunTime(us) CpuRunTime(us) MaxCpuRunTime(us) AvgCpuRunTime(us) TotalStarveTime(ms) SchCount -------------------------------------------------------------------------------- 0x80F1048F 0x80F20491 524289 1074266113 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 -------------------------------------------------------------------------------- Recv: -------------------------------------------------------------------------------- SrcCompId DesCompid LocalPipeId PeerPipeId ServiceId DopraSendNum DopraRecvNum FlowCtlNum FlowCtlLen(ms) AllocFailedNum InQueNum ConNum ConLen(ms) RunTime(us) MaxRunTime(us) AvgRunTime(us) CpuRunTime(us) MaxCpuRunTime(us) AvgCpuRunTime(us) TotalStarveTime(ms) SchCount -------------------------------------------------------------------------------- 0x80F20491 0x80F1048F 1074266113 524289 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 --------------------------------------------------------------------------------
Item | Description |
---|---|
SrcCompId | ID of the component that sends messages. |
DesCompid | ID of the component that receives messages. |
LocalPipeId | Local pipe ID. |
PeerPipeId | Peer pipe ID. |
ServiceId | Service ID of a pipe. |
DopraSendNum | Number of messages that the DOPRA interface sent to the TIPC interface. |
DopraRecvNum | Number of messages that the DOPRA interface received from the TIPC interface. |
FlowCtlNum | Number of times the receive end sent flow control messages. |
FlowCtlLen(ms) | Total flow control duration of the receive end. |
AllocFailedNum | Number of times the transmit end failed to invoke the application token. |
InQueNum | Number of messages that the DOPRA interface sent to the message processing queues of the receive end. |
ConNum | Number of backpressure times of the pipe transmit end. |
ConLen(ms) | Backpressure duration of the pipe transmit end. |
RunTime(us) | Message processing duration of the pipe. |
MaxRunTime(us) | Maximum pipe running duration. |
AvgRunTime(us) | Average pipe running duration. |
CpuRunTime(us) | Message processing duration of the pipe after the CPU is switched to process other transactions. |
MaxCpuRunTime(us) | Maximum pipe running duration after the CPU is switched to process other transactions. |
AvgCpuRunTime(us) | Average pipe running duration after the CPU is switched to process other transactions. |
TotalStarveTime(ms) | Staying duration of all packets in the queue of the pipe receive end. |
SchCount | Number of scheduling times. |
Send | Statistics about messages sent by the component. |
Recv | Statistics about messages received by the component. |
display message receive-trace rule
Function
The display message receive-trace rule command displays the rules configured for message receiving tracing.
Usage Guidelines
Usage Scenario
To check rules configured for message receiving tracing, run the display message receive-trace rule command. The command output facilitates problem locating.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display message receive-trace rule -------------------------------------------------------------------------------- ProcId RuleId SwitchFlag SrcCompId DstCompId MsgIntf MsgSubIntf MsgType TimeOut(ms) -------------------------------------------------------------------------------- 1001 0 1 0xFFFFFFFF 0xFFFFFFFF 255 255 6 0 10001 0 1 0xFFFFFFFF 0xFFFFFFFF 2 5 4294967295 0 --------------------------------------------------------------------------------
Item | Description |
---|---|
ProcId | Process ID. |
RuleId | Rule ID. |
SwitchFlag | Whether the function is enabled (Value 1 indicates that the function is enabled.). |
DstCompId | ID of the component that receives messages. |
MsgIntf | Message category (Value 255 indicates that all message categories are included.). |
MsgSubIntf | Message sub-category (Value 255 indicates that all message sub-categories are included.). |
MsgType | Message type (Value 4294967295 indicates that all message types are included.). |
TimeOut(ms) | Message processing timeout period, in ms. |
SrcCompid | ID of the component that sends messages. |
display message send-receive-statistic
Function
The display message send-receive-statistic component command displays statistics about the packets sent and received by a specified component.
The display message send-receive-statistic process command displays statistics about the packets sent and received by a specified process.
Format
display message send-receive-statistic process processid [ send | receive ]
display message send-receive-statistic component compid [ send | receive ]
Parameters
Parameter | Description | Value |
---|---|---|
send |
Displays statistics about the messages sent by a specified process or component. |
- |
receive |
Displays statistics about the messages received by a specified process or component. |
- |
component compid |
Specifies a component ID. |
The value ranges is 0 to ffffffff , in hexadecimal notation. |
process processid |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
When locating a problem related to the messages exchanged between components, run the display message send-receive-statistic component command to check statistics about the packets sent and received by a specified component. When locating a problem related to the messages exchanged between processes, run the display message send-receive-statistic process command to check statistics about the packets sent and received by a specified process.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display message send-receive-statistic process 1001 send Message statistics at 2015-11-03 10:41:34 Alloc message memory error times :0 Source component:ECM10, 0x80CC000E -------------------------------------------------------------------------------- DestComp DestCompid DestSlot DestProcId DopraSend TipcRej TipcSend TipcRecive DopraRecive AppFlowCtlNum FlowCtlNum FlowCtlLen(ms) ConNum ConLen(ms) -------------------------------------------------------------------------------- DBMS7 0x80CE000A 1 1001 10 10 10 10 10 10 10 10 10 10 -------------------------------------------------------------------------------- Alloc message memory error times :0 Source component:ECM11, 0x80CC011E -------------------------------------------------------------------------------- DestComp DestCompid DestSlot DestProcId DopraSend TipcRej TipcSend TipcRecive DopraRecive AppFlowCtlNum FlowCtlNum FlowCtlLen(ms) ConNum ConLen(ms) -------------------------------------------------------------------------------- DBMS8 0x80CE000B 1 1001 10 10 10 10 10 10 10 10 10 10 --------------------------------------------------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display message send-receive-statistic process 1001 receive Message statistics at 2015-11-03 11:43:53 Alloc message memory error times :0 Source component:ECM11, 0x80CC011E -------------------------------------------------------------------------------- DestComp DestCompid DestSlot DestProcId DopraSend TipcRej TipcSend TipcRecive DopraRecive AppFlowCtlNum FlowCtlNum FlowCtlLen(ms) ConNum ConLen(ms) -------------------------------------------------------------------------------- DBMS8 0x80CE000B 1 1001 10 10 10 10 10 10 10 10 10 10 -------------------------------------------------------------------------------- Alloc message memory error times :0 Dest component:ECM11, 0x80CC011E -------------------------------------------------------------------------------- SrcComp SrcCompid SrcSlot SrcProcId DopraSend TipcRej TipcSend TipcRecive DopraRecive AppFlowCtlNum FlowCtlNum FlowCtlLen(ms) ConNum ConLen(ms) -------------------------------------------------------------------------------- APPCFG10 0x80CF0011 1 1001 10 10 10 10 10 10 10 10 10 10 --------------------------------------------------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display message send-receive-statistic component 80CC000E send Message statistics at 2015-11-03 10:41:34 Alloc message memory error times :0 Source component:ECM10, 0x80CC000E -------------------------------------------------------------------------------- DestComp DestCompid DestSlot DestProcId DopraSend TipcRej TipcSend TipcRecive DopraRecive AppFlowCtlNum FlowCtlNum FlowCtlLen(ms) ConNum ConLen(ms) -------------------------------------------------------------------------------- DBMS7 0x80CE000A 1 1001 10 10 10 10 10 10 10 10 10 10 --------------------------------------------------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display message send-receive-statistic component 80CC000E receive Message statistics at 2015-11-03 10:41:34 Alloc message memory error times :0 Dest component:ECM10, 0x80CC000E -------------------------------------------------------------------------------- SrcComp SrcCompid SrcSlot SrcProcId DopraSend TipcRej TipcSend TipcRecive DopraRecive AppFlowCtlNum FlowCtlNum FlowCtlLen(ms) ConNum ConLen(ms) -------------------------------------------------------------------------------- APPCFG12 0x80CF0010 1 1001 10 10 10 10 10 10 10 10 10 10 --------------------------------------------------------------------------------
Item | Description |
---|---|
Source component | Name and ID of the component that sends messages. |
DestComp | Name of the component that receives messages. |
DestCompid | ID of the component that receives messages. |
DestSlot | Slot ID for the component that receives messages. |
DestProcId | Process ID of the component that receives messages. |
DopraSend | Number of times the APP successfully invoked the DOPRA interface to send messages. |
TipcRej | Number of times congestion occurs when the DOPRA interface invoked the TIPC interface. |
TipcSend | Number of messages that the DOPRA interface sent to the TIPC interface. |
TipcRecive | Number of messages that the DOPRA interface received from the TIPC interface. |
DopraRecive | Number of messages that the DOPRA interface sent to the message processing queues of the component. |
AppFlowCtlNum | Number of times the transmit end failed to invoke the application token. |
FlowCtlNum | Number of times the receive end sent flow control messages. |
FlowCtlLen(ms) | Total flow control duration of the receive end. |
ConNum | Number of backpressure times of the transmit end. |
ConLen(ms) | Backpressure duration of the transmit end. |
Dest component | Name and ID of the component that receives messages. |
SrcComp | Name of the component that sends messages. |
SrcCompid | ID of the component that sends messages. |
SrcSlot | Slot ID for the component that sends messages. |
SrcProcId | Process ID of the component that sends messages. |
display message trace srccomp
Function
The display message trace srccomp command displays tracing information about the messages sent by a specified component.
Parameters
Parameter | Description | Value |
---|---|---|
compid |
Specifies a component ID. |
The value ranges is 0 to ffffffff , in hexadecimal notation. |
Usage Guidelines
Usage Scenario
When locating a problem related to the messages sent by a specified component, run the display message trace srccomp command to view tracing information about the messages.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display message trace srccomp 80020011 Message Trace: --------------------------------------------------------------------------------- SrcCompId DestCompId SrcCompName DstCompName Intf IntfName subIntf SubIntfName MsgType AppSendTime IPCSendTime IPCRecvTime InQueueTime BeginSchTime EndSchTime MessageData --------------------------------------------------------------------------------- 0x80020011 0x80010006 SEM_LS17 SEM4 0 INTF_SSP 32 SSP_SUB_INTF_HA 143 2016-01-29 07:18:13 709 ms 2016-01-29 07:18:13 709 ms 2016-01-29 07:18:13 709 ms 2016-01-29 07:18:13 709 ms 2016-01-29 07:18:13 709 ms 2016-01-29 07:18:13 709 ms 00 42 01 8F 00 00 0 0x80020011 0x80010006 SEM_LS17 SEM4 0 INTF_SSP 32 SSP_SUB_INTF_HA 143 2016-01-29 07:18:01 702 ms 2016-01-29 07:18:01 702 ms 2016-01-29 07:18:01 702 ms 2016-01-29 07:18:01 702 ms 2016-01-29 07:18:01 702 ms 2016-01-29 07:18:01 702 ms 00 42 01 8F 00 00 0 0x80020011 0x80010006 SEM_LS17 SEM4 0 INTF_SSP 32 SSP_SUB_INTF_HA 143 2016-01-29 07:17:49 691 ms 2016-01-29 07:17:49 691 ms 2016-01-29 07:17:49 691 ms 2016-01-29 07:17:49 691 ms 2016-01-29 07:17:49 691 ms 2016-01-29 07:17:49 691 ms 00 42 01 8F 00 00 0 ---------------------------------------------------------------------------------
Item | Description |
---|---|
SrcCompId | ID of the component that sends messages. |
DestCompId | ID of the component that receives messages. |
SrcCompName | Name of the component that sends messages. |
DstCompName | Name of the component that receives messages. |
Intf | Message interface category. |
IntfName | Name of the message interface category. |
SubIntfName | Name of the message interface sub-category. |
MsgType | Message type. |
AppSendTime | Time when the component invoked the DOPRA interface to send messages. |
IPCSendTime | Time when the DOPRA interface sent messages. |
IPCRecvTime | Time when the DOPRA interface received messages. |
InQueueTime | Time when messages entered the APP queue. |
BeginSchTime | Time when the destination component started message processing. |
EndSchTime | Time when the destination component finished message processing. |
MessageData | Message contents. |
SubIntf | Message interface sub-category. |
display message
Function
The display message-usage command displays memory used by the messages of a process on a board.
Parameters
Parameter | Description | Value |
---|---|---|
procid |
Specifies the ID of a process. |
The value is an integer ranging from 1 to 4294967295. |
Usage Guidelines
Usage Scenario
This command displays memory used by the messages of a process on a board.
This command is supported only on the admin VS.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display message-usage 10001 Process message memory utilization statistics at 2011-03-18 02:34:11 514 ms ------------------------------------------------------------------------- Process Total Message Is : 31457280 bytes Process Total Message Used Is : 768 bytes Process Freed Message Is : 31456512 bytes Process Message Using Percentage Is : 0% -------------------------------------------------------------------------
Item | Description |
---|---|
Process Total Message Is | Total message memory of a process. |
Process Total Message Used Is | Memory used by the messages of a process. |
Process Freed Message Is | Free message memory of a process. |
Process Message Using Percentage Is | Percentage of memory used by the messages of a process. |
display message-process statistic process
Function
The display message-process statistic process command displays communication status statistics of the specified process.
Format
display message-process statistic process process-id
display message-process statistic message-type process process-id
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the process ID. |
The value is an integer ranging from 0 to 4294967295. |
message-type |
Displays a message type. If this parameter is specified, communication status statistics of a specified process can be viewed based on the message type. |
- |
Usage Guidelines
This command displays communication status statistics of a process, including the number of lost packets, reasons for packet loss, and number of packets sent and received by components.
This command is supported only on the admin VS.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display message-process statistic process 3 The message process statistics -------------------------------------------------------------------------------- CompType CompName CompCID Intf IntfName SubIntf SubIntfName Count RunTime(us) AvgRunTime(us) MaxRunTime(us) CpuRunTime(us) AvgCpuRunTime(us) MaxCpuRunTime(us) MaxStarveTime(ms) TotalStarveTime(ms) SendErrNum RecvErrNum -------------------------------------------------------------------------------- 3 SEM_Agent 0x800303F7 0 INTF_SSP 3 VOS_IID_TMR_TIMEOUT 1904529 170309075 89 4913 154479701 81 4907 0 74609 0 0 3 SEM_Agent 0x800303F7 0 INTF_SSP 32 SSP_SUB_INTF_HA 90542 12239643 135 28202 11570968 127 28200 0 36869 0 0 3 SEM_Agent 0x800303F7 0 INTF_SSP 36 SSP_SUB_INTF_DBG 58 4735 81 118 4255 73 105 0 51 0 0 3 SEM_Agent 0x800303F7 0 INTF_SSP 40 SSP_SUB_INTF_IMI 27399 421632 15 98 324716 11 97 0 1946 0 0 --------------------------------------------------------------------------------
Item | Description |
---|---|
CompType | Component type. |
CompName | Component name. |
CompCID | Component CID. |
Intf | Message interface ID. |
IntfName | Message interface name. |
SubIntf | Message sub-interface ID. |
SubIntfName | Message sub-interface name. |
Count | Total number of messages processed by a component. |
RunTime(us) | Total message processing duration of a component. |
AvgRunTime(us) | Average message processing duration of a component. |
MaxRunTime(us) | Maximum duration for a component to process a message. |
CpuRunTime(us) | Message processing duration of a component after the CPU is switched to process other transactions. |
AvgCpuRunTime(us) | Average message processing duration of a component after the CPU is switched to process other transactions. |
MaxCpuRunTime(us) | Maximum duration for a component to process a message after the CPU is switched to process other transactions. |
MaxStarveTime(ms) | Maximum staying duration of a packet in the queue of the pipe receive end. |
TotalStarveTime(ms) | Staying duration of all packets in the queue of the pipe receive end. |
SendErrNum | Number of messages that a component fails to send. |
RecvErrNum | Number of messages that a component fails to receive. |
MsgType | Message type. |
display message-usage component
Function
The display message-usage component command displays memory used by the messages of a process's component on a board.
Parameters
Parameter | Description | Value |
---|---|---|
procid |
Specifies the ID of a process. |
The value is an integer ranging from 0 to 4294967295. |
compcid |
Specifies the ID of a component. |
The value is an integer ranging from 0 to FFFFFFFF in hexadecimal notation. |
Usage Guidelines
Usage Scenario
This command is used to display information about memory used by the messages of a process's component on a board.
This command is supported only on the admin VS.
Precautions
This command is supported only on the admin VS.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display message-usage 10001 component 80D50406 ------------------------------------------------------ AllocMsgSize MaxMsgSize AreaName Percent ------------------------------------------------------ 0 1048576 AREA_SYS 0% 0 1048576 AREA_MGNT 0% 0 5242880 AREA_FLOWCTRL 0% 0 1048576 AREA_OTHER 0% 0 262144 AREA_CACHE 0% ------------------------------------------------------
display message-usage
Function
The display message-usage command displays memory used by the messages of a process on a board.
Parameters
Parameter | Description | Value |
---|---|---|
procid |
Specifies the ID of a process. |
The value is an integer ranging from 0 to 4294967295. |
verbose |
Displays detailed information about the memory used by the messages of a process with a specified ID. |
- |
Usage Guidelines
Usage Scenario
To query the memory used by the messages of a process on a board, run this command.
Precautions
This command is supported only on the admin VS.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display message-usage 10001 verbose Process message memory utilization statistics at 2014-10-29 08:39:56 550 ms ------------------------------------------------------------------------- Process Total Message Is : 8388608 bytes Process Total Message Used Is : 1024 bytes Process Freed Message Is : 8387584 bytes Process Message Using Percentage Is : 0% -------------------------------------------- CID allocsize percent -------------------------------------------- 0x800303F8 512 (B) 0 (%) 0xCC000B 256 (B) 0 (%) 0x8C0404 256 (B) 0 (%) --------------------------------------------
Item | Description |
---|---|
Process Total Message Is | Total message memory of a process. |
Process Total Message Used Is | Memory used by the messages of a process. |
Process Freed Message Is | Free message memory of a process. |
Process Message Using Percentage Is | Percentage of memory used by the messages of a process. |
CID | Component ID. |
allocsize | Memory usage, in bytes. |
percent | Percentage of used memory. |
display os-information slot
Parameters
Parameter | Description | Value |
---|---|---|
cmdstring |
The value is a string of characters. |
The value is a string of 1 to 63 case-sensitive characters. |
slot slot-id |
Slot ID. |
The value is a string of 1 to 31 case-sensitive characters. It cannot contain spaces. |
Usage Guidelines
Usage Scenario
You can run this command to view operating system information.
- cat /etc/RTOS-Release: displays RTOS release information.
- cat /proc/buddyinfo: information about diagnosing memory fragments
- cat /proc/interrupts: displays the number of interrupts of each CPU on each I/O device.
- cat /proc/meminfo: information about the memory usage of the system
- cat /proc/net/arp: displays dynamically learned and preprogrammed ARP entries.
- cat /proc/net/netstat: Linux network subsystem information
- cat /proc/net/snmp: displays the IP, ICMP, TCP, and UDP management information bases of the SNMP agent.
- cat /proc/sched_debug: displays information about the scheduler used for debugging.
- cat /proc/slabinfo: kernel cache information
- cat /proc/softirqs: displays softirq information.
- cat /proc/vmstat: displays virtual memory statistics.
- cat /proc/zoneinfo: displays memory area information.
- ps auxZ: information about the running processes
- ls - Z path: information about the running process with the selinux label. path is a parameter.
- Expected page cache size after cat /sys/kernel/mm/cache_limit/pagecache_reclaimed_mbytes: reclamation
- threshold of the page cache that is reclaimed and triggered by the cat /sys/kernel/mm/cache_limit/pagecache_watermark_mbytes:
- Expected slab cache size after cat /sys/kernel/mm/cache_limit/slabcache_reclaimed_mbytes: reclamation
- threshold of slab cache that triggers reclamation by the cat /sys/kernel/mm/cache_limit/slabcache_watermark_mbytes:
- The cat /sys/kernel/mm/cache_limit/pagecache_unmap: deletes the mapping between the page cache and the process in the page table.
- cat /sys/kernel/mm/cache_limit/cycle_s: recycling period, in seconds.
- cat /sys/kernel/mm/cache_limit/run: cache Recycling Switch Status
- sestatus: displays the status of the system running SELinux.
- getstatus: whitelist status
- kysec_get filename: whitelist label. The file name is a parameter and must be the absolute path of the attached file.
Precautions
In VS mode, this command is supported only by the admin VS.
display pipe-memory time process
Function
The display pipe-memory time process command displays information about memory leak along the pipe of the specified process in the specified period of time.
Parameters
Parameter | Description | Value |
---|---|---|
process procid |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
time times |
Specifies an interval. |
The value is an integer ranging from 0 to 4294967295, in seconds. |
Usage Guidelines
Usage Scenario
To check information about memory leak along the pipe of the specified process in the specified period of time, run the display pipe-memory time process command. The command helps troubleshooting.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display pipe-memory time 10 process 1006 cid pipe memory use information: -------------------------------------------------------------------------------- SendID RecvID State SendPipeID RecvPipeID Size WriteSize AllocID -------------------------------------------------------------------------------- 0x4 0x0 0 0 0 0 0 0 --------------------------------------------------------------------------------
Item | Description |
---|---|
SendID | ID of the component that sends the message. |
RecvID | ID of the component that receives the message. |
State | Pipe state. |
SendPipeID | Pipe ID of the sending end. |
RecvPipeID | Pipe ID of the receiving end. |
Size | Pipe memory size. |
WriteSize | Remaining pipe memory size. |
AllocID | ID of the party that applies for the pipe memory. |
display assert
Function
The display assert command displays assertions occurred in the system.
The display reportfailure command displays system fault information.
Format
display assert show_num [ begin_num ] [ verbose ] [ all | slot slotId ]
display reportfailure show_num [ begin_num ] [ verbose ] [ all | slot slotId ]
Parameters
Parameter | Description | Value |
---|---|---|
show_num |
Specifies the number of records to be displayed. |
The value is an integer ranging from 1 to 100, in percentage. |
begin_num |
Specifies the start record to be displayed. |
The value is an integer ranging from 0 to 99. |
verbose |
Displays the detailed information. |
- |
all |
Displays information about all boards. |
- |
slot slotId |
Specifies the slot ID of the board whose information is displayed. |
The value is a string of 1 to 15 case-sensitive characters. It cannot contain spaces. |
Usage Guidelines
The display assert command displays assertions when any system errors occur. This command can be also used as an inspection command.
The display reportfailure command queries system fault information. A system fault may cause a master/slave main control board switchover. If a master/slave main control board switchover occurs, contact technical support personnel.Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display reportfailure 20 verbose all ==============Comp report failure info (No.: 0 Idx: 0)==================== 2011-05-19 12:15:37-ERRINFO:slot, Process: PROTO1, CompID:0x8033274a Event: 1,Param: 2, Withlog: xxxxxxxxxxxx Call Stack: StackBase ReturnIns FuncEntry 00000000 B7AB3156 FFFFFFFF libsspbase.so(VRP_HafRepFailure+0x172) 00000000 B7AC4A17 FFFFFFFF libsspbase.so(HAF_ReportSelfFailureWithLog+0x50) 00000000 0804C3A0 FFFFFFFF location(_start+0) 00000000 8033274A FFFFFFFF [0x8033274a]
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display assert 20 all ======================assert info (no: 0 idx: 0)===================== 2012-02-09 23:15:05-ERRINFO:slot, Process: APPLocation1000(ID:1006) Errinfo at file: 'compa_dbg_funcs.c', Line:1196 Withlog: VRP Version: VRPV800R003C00B012.cc DOPRA Version: DOPRA V200R003C06SPC030 PATCH: V800R002SPH102 Call Stack: StackBase ReturnIns FuncEntry 00000000 B76FD814 FFFFFFFF libsspbase.so(VRP_Assert+0x124) 00000000 A938AD2C FFFFFFFF compa.so(COMPA_TriggerAssertionMsgHandler+0x4c) 00000000 A938F2A4 FFFFFFFF compa.so(COMPA_DispatchMsgHandle+0x74) 00000000 A938F98E FFFFFFFF compa.so(COMPA_MsgProc+0xde) 00000000 B7A3EACF FFFFFFFF libdefault.so(rtfScmMessageSchedule+0x309) 00000000 B7A3F3AB FFFFFFFF libdefault.so(rtfScmCompScheKernelEntry+0x1c2) 00000000 B7A3F60C FFFFFFFF libdefault.so(rtfScmCompScheDefaultEntry+0x1ec) wangjinxiang 00181183(w00181183) 2012-02-10 10:27:39 00000000 B7A3F832 FFFFFFFF libdefault.so(rtfScmTaskDeployDefaultCompEntry+0x32) 00000000 B786D052 FFFFFFFF libdefault.so(tskAllTaskEntry+0x248) 00000000 B7F0B34B FFFFFFFF libpthread.so.0 [0xb7f0b34b]
Item | Description |
---|---|
Call Stack | Details about the call stack. |
StackBase | Base of the function stack. |
ReturnIns | Memory address returned after the function is ended. |
FuncEntry | Entrance address of a function. |
Errinfo at file | Name of the file assertions occur. |
VRP Version | VRP version. |
DOPRA Version | DOPRA version. |
Process | Process ID of the component reporting a fault. |
CompID | ID of the component reporting a fault. |
Event | Fault type:
|
Param | Additional information recorded by a component. |
Withlog | Log information recorded by a component. |
Location | Name of the process on which assertions occur. |
Line | Number of the line assertions occur. |
PATCH | Patch version. |
display reset-reason
Parameters
Parameter | Description | Value |
---|---|---|
all |
Displays all the board reset causes. |
- |
last |
Displays the last board reset cause. |
- |
current |
Displays the current board reset cause. |
- |
slot slotID |
Displays the reset causes of a specified board. |
- |
Usage Guidelines
Usage Scenario
To check the board reset causes, run the display reset-reason command.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display reset-reason all slot 1 --------------------------------------------------------------------------------- All Information --------------------------------------------------------------------------------- 150830-05:26:22.284781 [MON][MID:0x01]==============VRP Start=================== 150830-05:27:07.600994 [L:0][MID:0x01]proc 0(1630) start cpu tick is H: 0x001eb464, L: 0x08d471c244. 150830-05:27:07.655541 [L:0][MID:0x01]Process(1630) 0 finish signal proces register. 150830-05:27:09.399191 [L:10002][MID:0x01]proc 10002(2364) start cpu tick is H: 0x001eb465, L: 0x08cddb3343. 150830-05:27:09.455249 [L:10002][MID:0x01]Process(2364) 10002 finish signal proces register. 150830-05:27:09.524821 [L:10003][MID:0x01]proc 10003(2377) start cpu tick is H: 0x001eb465, L: 0x08df47c73d. 150830-05:27:09.574496 [L:10003][MID:0x01]Process(2377) 10003 finish signal proces register.
display schedule-trace
Function
The display schedule-trace command displays message scheduling records after message scheduling tracing is enabled.
Parameters
Parameter | Description | Value |
---|---|---|
process process-id |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
To determine whether messages are lost or accumulated in the system, run the display schedule-trace command to check message scheduling records.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display schedule-trace process 1002 --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Type ThreadID SendCID RcvCID PipeID Phase MsgType Intf SubIntf RunTime(us) RunCpuTime(us) StarveTime(ms) Time --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- COMMON 0xf0973b70 0x10004 0x80CC000E 0x0 EXIT 3 01(INTF_SMP) 00(SMP_SUB_INTF_APPCFGI) 2544 2537 0 01-11 17:13:28:836.600 COMMON 0xf1aefb70 0x80CC000E 0x80030008 0x0 ENTRY 3 01(INTF_SMP) 00(SMP_SUB_INTF_APPCFGI) 0 0 0 01-11 17:13:28:836.589 COMMON 0xf0973b70 0x80CC000E 0x80030008 0x0 SEND 3 01(INTF_SMP) 00(SMP_SUB_INTF_APPCFGI) 0 0 0 01-11 17:13:28:836.514 COMMON 0xf0973b70 0x10004 0x80CC000E 0x0 ENTRY 3 01(INTF_SMP) 00(SMP_SUB_INTF_APPCFGI) 0 0 0 01-11 17:13:28:834.061 COMMON 0xf134eb70 0x80CA2713 0x80CA2713 0x0 EXIT 0 00(INTF_SSP) 03(VOS_IID_TMR_TIMEOUT) 66 56 0 01-11 17:13:28:834.023 COMMON 0xf134eb70 0x80CA2713 0x80CA2713 0x0 ENTRY 0 00(INTF_SSP) 03(VOS_IID_TMR_TIMEOUT) 0 0 0 01-11 17:13:28:833.967 ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Item | Description |
---|---|
Type | Message type:
|
ThreadID | ID of a Linux thread. |
SendCID | ID of a transmitting component. |
RcvCID | ID of a receiving component. |
PipeID | Pipe ID. |
Phase | Phase:
|
MsgType | Message type. |
Intf | Interface category. |
SubIntf | Interface subcategory. |
RunTime(us) | Message processing duration including the scheduling duration,in ?s. |
RunCpuTime(us) | Message processing duration excluding the scheduling duration,in ?s. |
StarveTime(ms) | Message starving duration, in ms. |
Time | Timestamp. |
display semaphore
Parameters
Parameter | Description | Value |
---|---|---|
slot slotId |
Displays semaphore information on the board in a specified slot. |
The value is a string of 1 to 15 case-sensitive characters, spaces not supported. |
process process-id |
Specify the process ID. |
The value is an integer ranging from 0 to 4294967295. |
sema-id |
The ID of semaphore. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
A large number of semaphores are generated when the system is running. To check the semaphore information, run the display semaphore command.
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display semaphore slot 1 -------------------------------------------------------------------------------- Semaphore Name Semaphore ID Count Mode Type Process ID -------------------------------------------------------------------------------- SemaName1 100000 10 FIFO Binary 10001 SemaName2 100001 0 FIFO Mutex 10002 SemaName3 100002 10 FIFO Count 10003 -------------------------------------------------------------------------------- Total = 3
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display semaphore process 1001 1 ================= Semaphore Information Begin ================= Semaphore Name: SemaName Semaphore ID: 100000 Semaphore Type: Mutex Semaphore Mode: 0 Process ID: 1001 Create Thread ID: 4294967295 Create Task ID: 342344 Create Task Name: CreateTaskName Mutex Owner Task Name: MutOwnTskName Mutex Owner Task ID: 2863311530 Mutex Owner Thread ID: 4294967295 Mutex Recur Lock Number: 100 Last P Time: 2015-03-13 11:22:33 Last V Time: 2015-03-13 11:22:33 Peak Time: 50 (ms) --------------------------------------------------------------- Block Owner Task List: --------------------------------------------------------------- NO. ThreadID TaskID Name 1 10 2863267840 B name 2 11 2863267841 B name 3 12 2863267842 B name 4 13 2863267843 B name 5 14 2863267844 B name ================= Semaphore Information End ===================
Item | Description |
---|---|
Semaphore Name | Name of a semaphore. |
Semaphore ID | ID of a semaphore. |
Semaphore Mode | Mode of a semaphore. |
Name | Task name. |
Count | Count. |
Mode | Mode of a semaphore. |
Type | Type of a semaphore:
|
Process ID | Process ID. |
Mutex Owner Task Name | Name of the task owned by the mutex semaphore. |
Mutex Owner Task ID | ID of the task owned by the mutex semaphore. |
Mutex Owner Thread ID | ID of the thread owned by the mutex semaphore. |
Mutex Recur Lock Number | Number of mutex semaphore resources. |
Create Thread ID | ID of the task created by the system. |
Create Task ID | ID of the task created by DOPRA. |
Create Task Name | Name of the task created by DOPRA. |
Last P Time | Last P time. |
Last V Time | Last V time. |
Peak Time | P-V peak. |
Block Owner Task List | List of blocked tasks. |
NO. | Number of blocked tasks. |
ThreadID | Thread ID. |
TaskID | Task ID. |
display starvation
Function
The display starvation command displays starvation information of a system thread or component.
Parameters
Parameter | Description | Value |
---|---|---|
show_num |
Displays the number of pieces of starvation information. |
The value is an integer ranging from 1 to 100. |
begin_num |
Displays the number of offsets counted based on the latest record. |
The value is an integer ranging from 0 to 99. |
all |
Displays the number of pieces of starvation information on all boards. |
- |
slot slotId |
Displays the number of pieces of starvation information on a specified board. |
- |
Usage Guidelines
Usage Scenario
To view starvation information to locate a fault, run the display starvation command to view the system threads or components that have not been scheduled within 10s or longer. To clear starvation information, run the reset starvation record command.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display starvation 20 all ============ Starvation Information Begin ============ Slot: 1/17 Process: 1004 Process Name: LM Component ID: 80110545 Component Name: semagt Time: 2015-01-01 16:35:20 Starvation Time: 100 Message IId: 1 Message intf: 0 Message subintf: 2 Dopra Version: DOPRA V100R006C09SPC871 VRP Version: VRPV8R10C00 Patch Version: V800R002SPH102 /17 Process: 1004 Process Name: LM Thread ID: 80110545 Thread Name: vctick Time: 2015-01-01 16:35:20 Starvation Time: 100 Dopra Version: DOPRA V100R006C09SPC871 VRP Version: VRPV8R10C00 Patch Version: V800R002SPH102 ============ Starvation Information End ============
Item | Description |
---|---|
Starvation Time | Duration in which a thread of component is starved. |
Process | Process ID of a starved thread or component. |
Process Name | Process name of a starved thread or component. |
Component ID | ID of a starved component. |
Component Name | Name of a starved component. |
Message IId | ID of the message displayed when a component is starved. |
Message intf | Type of the message displayed when a component is starved. |
Message subintf | Subtype of the message displayed when a component is starved. |
Dopra Version | DOPRA version number. |
VRP Version | VRP version number. |
Patch Version | Patch version number. |
Thread ID | ID of a starved thread. |
Thread Name | Name of a starved thread. |
Slot | Slot number of the board on which threads or components are starved. |
Time | Time when a thread of component is starved. |
display system cam-subscription
Function
The display system cam-subscription command displays the subscription information about the component ID table of a specified process.
Parameters
Parameter | Description | Value |
---|---|---|
procid |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
To view the subscription information about the component ID table of a specified process, run the display system cam-subscription command. The command output helps diagnose a fault, such as a message exchange failure.
Precautions
In VS mode, this command is supported only by the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system cam-subscription 3 Process CAM Information ------------------------------------------------------------ Process CompType Pid Cid HaRole ------------------------------------------------------------ 2 1 0x10004 0x80010006 STANDBY(1, 3) 7 1 0x10004 0x80010021 ACTIVE(1, 4) 4 2 0x80020011 0x80020011 ACTIVE(1, 4) 8 2 0x80020024 0x80020024 ACTIVE(1, 4) 9 2 0x80020028 0x80020028 NULL(0, 2) 10 2 0x8002002B 0x8002002B NULL(0, 2) ..... 8 252 0x80FC0025 0x80FC0025 ACTIVE(1, 4) 9 252 0x80FC0027 0x80FC0027 NULL(0, 2) 10 252 0x80FC002A 0x80FC002A NULL(0, 2) 11 252 0x80FC002D 0x80FC002D NULL(0, 2) 12 252 0x80FC0030 0x80FC0030 NULL(0, 2) 1005 252 0xFC0422 0x80FC0463 ACTIVE(1, 4) 1006 252 0xFC0432 0x80FC0476 ACTIVE(1, 4) ------------------------------------------------------------ Total = 190
Item | Description |
---|---|
Process | Process ID. |
CompType | Component type. |
Pid | Component PID. |
Cid | Component CID. |
HaRole | Peer status:
|
Total | Total number of the records. |
(a, b) | a indicates the process connection status:
b indicates the process arbitration status:
|
display system component
Parameters
Parameter | Description | Value |
---|---|---|
slot slot-id |
Displays information about components on a specified board. |
- |
Usage Guidelines
Usage Scenario
To view information about components on a board, run the display system component command. The information includes the primary/secondary state, CPU usage, memory usage, and process ID of each component on the board.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system component -------------------------------------------------------------------------------- Name CID CGID Process HaState CpuUsage MemUsage(B) -------------------------------------------------------------------------------- SSPRPM_LS41 0x80050029 0x80050029 9 PRIMARY 0% 2928 LLA 0x802403E9 0x2403E9 9 PRIMARY 0% 37264 TM_CLT 0x802703EA 0x2703EA 9 PRIMARY 0% 56 LCS 0x802B03EC 0x802B03EC 9 PRIMARY 0% 41528 DBG_AGENT 0x803303E8 0x3303E8 9 PRIMARY 0% 0 BOOTSERV 0x805003EA 0x805003EA 9 PRIMARY 0% 964 LDM 0x8078273D 0x8078273D 9 PRIMARY 0% 116052 TTY 0x809003EB 0x809003EB 9 PRIMARY 0% 30036 APPCFG14 0x80CF0037 0xCF000E 9 PRIMARY 0% 547868 DEVMA39 0x80FC0027 0x80FC0027 9 PRIMARY 0% 40812 TM_SVR 0x802603F3 0x2603F0 7 PRIMARY 0% 81616 DBG 0x80322726 0x322721 7 PRIMARY 0% 0 DBG_AGENT 0x803303F1 0x3303EE 7 PRIMARY 0% 0 SOCK 0x806503F2 0x6503EF 7 PRIMARY 0% 113000 APPCFG3 0x80CF0020 0xCF0003 7 PRIMARY 0% 544248 PDEVM2 0x80FA0016 0xFA0002 7 PRIMARY 0% 11600 LDEVM5 0x80FB0017 0xFB0005 7 PRIMARY 0% 7804 SSPRPM11 0x8004001E 0x4000B 6 PRIMARY 0% 3896 DBG_AGENT 0x803303FC 0x3303F7 6 PRIMARY 0% 0 LOGSERVER 0x80602716 0x602712 6 PRIMARY 0% 1366316 CLI10002 0x80CA2716 0xCA2712 6 PRIMARY 0% 7553244 CFG9 0x80CB001A 0xCB0009 6 PRIMARY 0% 6180692 ECM10 0x80CC001C 0xCC000A 6 PRIMARY 0% 31699724 ADM8 0x80CD001D 0xCD0008 6 PRIMARY 0% 630576 DBMS7 0x80CE001B 0xCE0007 6 PRIMARY 0% 5978232 APPCFG6 0x80CF0019 0xCF0006 6 PRIMARY 0% 1849500 PM 0x80D02734 0xD0272C 6 PRIMARY 0% 228928 AAA 0x80D12730 0xD1272A 6 PRIMARY 0% 125992 LAM 0x80D22732 0xD2272B 6 PRIMARY 0% 5560 FMSERVER 0x80E72714 0xE72711 6 PRIMARY 0% 237688 DBG_AGENT 0x803303EF 0x3303EC 1000 PRIMARY 0% 0 CONSOLE 0x80C903F0 0xC903ED 1000 PRIMARY 0% 0 APPCFG 0x80CF03EE 0xCF03EB 1000 PRIMARY 0% 394324 LLA 0x802403F8 0x2403F3 1001 PRIMARY 0% 36856 DBG_AGENT 0x803303F7 0x3303F2 1001 PRIMARY 0% 0 SYSLOG 0x80622725 0x622720 1001 PRIMARY 0% 2792 SOCK 0x806503F9 0x6503F4 1001 PRIMARY 0% 136940 PP4 0x8066271C 0x662717 1001 PRIMARY 0% 76416 CACHEM 0x8067271B 0x672716 1001 PRIMARY 0% 179140 SLA 0x8068272A 0x682724 1001 PRIMARY 0% 27736 DGNTL 0x8069272D 0x692727 1001 PRIMARY 0% 68288 FESDS 0x806A271D 0x6A2718 1001 PRIMARY 0% 17044324 PP6 0x80722718 0x722713 1001 PRIMARY 0% 73676 ND 0x807303FB 0x7303F6 1001 PRIMARY 0% 49680 GFD 0x8074272C 0x742726 1001 PRIMARY 0% 119256 ARP 0x807703FA 0x7703F5 1001 PRIMARY 0% 69196 GRESM 0x8079271A 0x792715 1001 PRIMARY 0% 120736 IFM 0x807A2719 0x7A2714 1001 PRIMARY 0% 1534740 FEISW 0x808C271E 0x8C2719 1001 PRIMARY 0% 1292 TELC 0x8091271F 0x91271A 1001 PRIMARY 0% 30424 SSHC 0x80922720 0x92271B 1001 PRIMARY 0% 153700 SSHS 0x80932723 0x93271E 1001 PRIMARY 0% 35024 FTPC 0x80942722 0x94271D 1001 PRIMARY 0% 337016 FTPS 0x80952724 0x95271F 1001 PRIMARY 0% 31644 TFTPC 0x80962721 0x96271C 1001 PRIMARY 0% 47108 NETCONF 0x80972728 0x972722 1001 PRIMARY 0% 3494328 EUM 0x80A6272F 0xA62729 1001 PRIMARY 0% 130620 TELS 0x80C82729 0xC82723 1001 PRIMARY 0% 122268 APPCFG 0x80CF03F6 0xCF03F1 1001 PRIMARY 0% 535920 LLA 0x80240401 0x2403FB 10001 PRIMARY 0% 36936 DBG_AGENT 0x803303FF 0x3303F9 10001 PRIMARY 0% 0 VLAN 0x8052272E 0x522728 10001 PRIMARY 0% 832060 MSTP 0x8054272B 0x542725 10001 PRIMARY 0% 452632 SOCK 0x80650400 0x6503FA 10001 PRIMARY 0% 112592 APPCFG 0x80CF03FE 0xCF03F8 10001 PRIMARY 0% 436384 TNLM 0x8020273C 0x202733 10002 PRIMARY 0% 43592 STATICRT_IPV6 0x80212738 0x21272F 10002 PRIMARY 0% 51312 DIRECTRT_IPV6 0x80222736 0x22272D 10002 PRIMARY 0% 79208 RM_IPV6 0x8023273A 0x232731 10002 PRIMARY 0% 127512 DBG_AGENT 0x80330404 0x3303FD 10002 PRIMARY 0% 0 SOCK 0x80650405 0x6503FE 10002 PRIMARY 0% 112440 DIRECTRT_IPV4 0x806F2737 0x6F272E 10002 PRIMARY 0% 79480 STATICRT_IPV4 0x80702739 0x702730 10002 PRIMARY 0% 50792 RM_IPV4 0x8071273B 0x712732 10002 PRIMARY 0% 135488 APPCFG 0x80CF0403 0xCF03FC 10002 PRIMARY 0% 418688 -------------------------------------------------------------------------------- Total = 75
Item | Description |
---|---|
Name | Component name. |
CID | Component ID. |
CGID | Component group ID. |
Process | Process ID of the component. |
HaState | Primary/secondary state of the component. |
CpuUsage | CPU usage of the component. |
MemUsage(B) | Memory usage of the component. |
display system cpu statistics
Parameters
Parameter | Description | Value |
---|---|---|
slot slotID |
Specifies the slot ID of a board. If this parameter is not specified, the command displays CPU statistics about the device. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. |
process processid |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
To display CPU usage statistics about a board, run the display system cpu statistics command in the diagnostic view. The command output helps diagnose and locate CPU faults.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system cpu statistics Cpu utilization statistics generate at 2015-11-03 10:25:32 Cpu utilization statistics at 2015-11-03 10:02:32 System start at 2015-11-03 10:02:32 Total: 1.66%, us: 0.77%, os: 0.0%, ni: 0.0%, wa: 0.47%, hi: 0.0%, si: 0.2%, st: 0.0% Cpu1 : 0.5%, us: 0.0%, os: 0.0%, ni: 0.0%, wa: 0.5%, hi: 0.0%, si: 0.0%, st: 0.0% Cpu2 : 0.32%, us: 0.0%, os: 0.0%, ni: 0.0%, wa: 0.27%, hi: 0.0%, si: 0.0%, st: 0.0% Cpu3 : 0.69%, us: 0.62%, os: 0.0%, ni: 0.0%, wa: 0.0%, hi: 0.0%, si: 0.0%, st: 0.0% Cpu4 : 0.54%, us: 0.14%, os: 0.0%, ni: 0.0%, wa: 0.14%, hi: 0.0%, si: 0.0%, st: 0.0% --------------------------------------------------------------------------------- ProcID ProcessName UseRate AvUse RunTime S Sched Pr TaskNum StartTime --------------------------------------------------------------------------------- 10643 monitor 2.48 0.0 0:0.14 S 0 120 22 2015-11-03 10:25:32 1 init 0.0 11.56 83:34.50S 0 120 1 2015-11-03 10:38:53 2727 acpid 0.0 0.0 0:0.0 S 0 120 1 2015-11-03 10:39:26 23015 acc-diskmon 0.0 0.0 0:0.1 S 0 120 1 2015-11-03 10:10:10 1189 udevd 0.0 0.0 0:0.2 S 0 116 1 2015-11-03 10:39:17 3750 owcimomd 0.0 0.0 0:0.0 S 0 120 3 2015-11-03 10:39:28 3998 pdflush 0.0 0.0 0:0.1 S 0 120 1 2015-11-03 10:19:50 2728 syslog-ng 0.0 0.0 0:0.20 S 0 120 1 2015-11-03 10:39:26 10858 monitor 0.0 0.0 0:0.0 S 0 120 17 2015-11-03 10:25:53 1132 reiserfs/2 0.0 0.0 0:0.0 S 0 115 1 2015-11-03 10:39:16 2857 hald 0.0 0.0 0:0.1 S 0 120 1 2015-11-03 10:39:26 1131 reiserfs/1 0.0 0.0 0:0.0 S 0 115 1 2015-11-03 10:39:16 3690 zmd 0.0 0.8 0:42.36 S 0 120 1 2015-11-03 10:12:04 1130 reiserfs/0 0.0 0.0 0:0.0 S 0 115 1 2015-11-03 10:39:16 1133 reiserfs/3 0.0 0.0 0:0.0 S 0 115 1 2015-11-03 10:39:16 3805 slpd 0.0 0.0 0:0.0 S 0 120 1 2015-11-03 10:39:29 10845 monitor 0.0 0.0 0:0.0 S 0 120 12 2015-11-03 10:25:53 --------------------------------------------------------------------------------- Process LM cpu use detail: Cpu used: 2.8, V8 processid: 4, System processid:10858 Task num:2 running num:1 sleeping num:1 stopped num:0 zombie num:0 --------------------------------------------------------------------------------- TaskID TaskName UseRate AvUse RunTime S Sched Pr BindC STimes StartTime --------------------------------------------------------------------------------- 10879 DefSch0100 0.0 0.0 0:0.0 R 0 120 1/1/1/1/0/0/0/0/ 1635 2015-11-03 10:26:15 --------------------------------------------------------------------------------- Bind comp cpu use information: --------------------------------------------------------------------------------- CompId CompName UseRate MsgProcTime PipeProcTime TotalTime Status --------------------------------------------------------------------------------- 0x80650431 comp_sock 0.15 0:0.0 0:0.0 0:0.0 MSG --------------------------------------------------------------------------------- --------------------------------------------------------------------------------- TaskID TaskName UseRate AvUse RunTime S Sched Pr BindC STimes StartTime --------------------------------------------------------------------------------- 10896 DefSch0e00 0.0 0.0 0:0.0 S 0 120 1/1/1/1/0/0/0/0/ 8625 2015-11-03 10:26:16 --------------------------------------------------------------------------------- Bind comp cpu use information: --------------------------------------------------------------------------------- CompId CompName UseRate MsgProcTime PipeProcTime TotalTime Status --------------------------------------------------------------------------------- 0x80650436 comp_sock 0.44 0:0.0 0:0.0 0:0.0 IDLE 0x80820437 onm 0.22 0:0.0 0:0.0 0:0.0 IDLE ---------------------------------------------------------------------------------
Item | Description |
---|---|
Cpu utilization statistics | CPU usage statistics. |
System start | Date and time when the system was started. |
ProcID | Process ID. |
ProcessName | Process name. |
UseRate | CPU usage of a process. |
AvUse | Average CPU usage of threads. |
RunTime | Process running period. |
S | Process status. |
S | Thread status. |
Sched | Whether a process is scheduled. |
Sched | Whether a thread is scheduled. |
Pr | Process priority. |
TaskNum | Number of threads in a process. |
StartTime | Date and time when a process was started. |
StartTime | Date and time when a thread was started. |
Process LM cpu use detail | CPU usage details about the process LM. |
Task num | Number of threads in the process LM. |
running num | Number of running threads. |
sleeping num | Number of threads in the sleeping state. |
stopped num | Number of stopped threads. |
zombie num | Number of zombie threads. |
TaskID | Thread ID. |
TaskName | Thread name. |
BindC | CPU mask bound to a thread. |
STimes | Number of thread switching times. |
Bind comp cpu use information | Usage of the CPU bound to a thread. |
CompId | Component ID. |
CompName | Component name. |
MsgProcTime | Message processing time. |
PipeProcTime | Pipe processing time. |
TotalTime | Total time. |
Status | Component status. |
Total | Total CPU usage. |
us | CPU usage of the user space. |
os | CPU usage of the kernel space. |
ni | CPU usage of user processes with their priorities changed. |
wa | CPU usage in the process of waiting for input and output. |
hi | CPU usage of hardware interrupt tasks. |
si | CPU usage of software interrupt tasks. |
display system deadloop configuration
Function
The display system deadloop configuration command is used to view information about the deadloop of a thread or component.
Format
display system component deadloop configuration process process-id
display system thread deadloop configuration process process-id
Parameters
Parameter | Description | Value |
---|---|---|
thread |
Displays infinite loop information about threads. |
- |
process process-id |
Specifies the ID of a process. |
The value is an integer ranging from 0 to 4294967295. |
component |
Displays infinite loop information about components. |
- |
Usage Guidelines
To check infinite loop information about threads or components, run the display system thread deadloop configuration or display system component deadloop configuration command, respectively. The command output facilitates fault diagnosis.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system thread deadloop configuration process 1008 -------------------------------------------------------------------------------- Thread ID Tid Thread Type Heart Beat time(s) Warning time(s) Exception time(s) Policy -------------------------------------------------------------------------------- 4122168128 72219 VCLK 10 60 480 0 4107639616 72538 DefSch0100 5 10 15 0 -------------------------------------------------------------------------------- Total = 2
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system component deadloop configuration process 1008 -------------------------------------------------------------------------------- CompType MsgType Intf IntfName SubIntf SubIntfName Level1 Warning time(s) Level2 Warning time(s) Level3 Warning time(s) Exception time(s) -------------------------------------------------------------------------------- 0x3 171 0 INTF_SSP 32 SSP_SUB_INTF_HA 1200 1201 1202 3000 0x3 2 0 INTF_SSP 33 SSP_SUB_INTF_RPM 1200 1201 1202 3000 0x3 5 1 INTF_SMP 0 SMP_SUB_INTF_APPCFGI 60 180 480 3000 0x3 7 1 INTF_SMP 0 SMP_SUB_INTF_APPCFGI 1200 1201 1202 3000 0x3 0 1 INTF_SMP 0 SMP_SUB_INTF_APPCFGI 1200 1201 1202 3000 0x4 255 255 ALL 255 ALL 4294967295 4294967295 4294967295 4294967295 0x5 255 255 Unknown 255 Unknown 1800 3600 7200 10800 0xCB 44 1 INTF_SMP 6 SMP_SUB_INTF_CFGI 480 481 482 4294967 0xCD 255 255 ALL 255 ALL 4294967295 4294967295 4294967295 4294967295 -------------------------------------------------------------------------------- Total = 9
Item | Description |
---|---|
Thread ID | Thread ID. |
Thread Type | Thread type. |
Tid | TID that is returned when the specified thread invokes a system interface. |
Heart Beat time(s) | Thread heartbeat time, in seconds. |
Warning time(s) | Threshold for generating a thread heartbeat timeout alarm, in seconds. When the period in which the thread does not work exceeds the threshold, an alarm is generated. |
Exception time(s) | Thread heartbeat timeout threshold that triggers exception handling, in seconds. When the period in which the thread does not work exceeds the threshold, the exception is handled. |
Policy | Policy for processing an infinite loop:
|
CompType | Component type. |
MsgType | Message type. |
Intf | Interface type. |
IntfName | Interface name. |
SubIntf | Sub-interface type. |
SubIntfName | Sub-interface name. |
Level1 Warning time(s) | Level-1 alarm threshold for infinite loops, in seconds. |
Level2 Warning time(s) | Level-2 alarm threshold for infinite loops, in seconds. |
Level3 Warning time(s) | Level-3 alarm threshold for infinite loops, in seconds. |
display system debug configuration flow-control
Function
The display system debug configuration flow-control command displays the configurations of long-time component flow control.
Format
display system debug configuration flow-control [ all | { slot SlotId } | { process ProcessId } ]
Parameters
Parameter | Description | Value |
---|---|---|
all |
Displays component flow control configurations of all boards. |
- |
slot SlotId |
Specifies the slot ID of a board. |
- |
process ProcessId |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
If the system experiences component flow control for a long time, run the display system debug configuration flow-control command to check the configurations of long-time component flow control, including the alarm threshold, exception threshold, and exception handling policy.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system debug configuration flow-control ------------------------------------------------------------------------------------------- Slot ProcessName PolicyMode OverTimeWarning (s) OverTimeLimit (s) ------------------------------------------------------------------------------------------- 17 SM unReset 3 600 17 CFG unReset 3 600 17 LM unReset 3 600 17 CONSOLE unReset 3 600 17 PROTO5 unReset 3 600 17 PSM1 unReset 3 600 17 RESP unReset 3 600 17 FESMB unReset 3 600 17 PROTO2 unReset 3 600 17 PSM2 unReset 3 600 17 OPS unReset 3 600 17 PROTO1 unReset 3 600 -------------------------------------------------------------------------------------------
Item | Description |
---|---|
Slot | Slot ID of a board. |
ProcessName | Process name. |
PolicyMode | Handling policy to be used when the component flow control period exceeds the exception threshold:
|
OverTimeWarning (s) | Threshold that triggers the reporting of an alarm in the case of long-time component flow control. |
OverTimeLimit (s) | Threshold that triggers the reporting of an exception in the case of long-time component flow control. |
display system debug diagnostic-log
Parameters
Parameter | Description | Value |
---|---|---|
slot slotId |
Displays attributes of the log file on a specified board. |
- |
all |
Displays attributes of log files on all boards. |
- |
Usage Guidelines
Usage Scenario
To view log file attributes, run the display system debug diagnostic-log command. The command output contains the log file name, size, and the number of compressed log files.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system debug diagnostic-log all -------------------------------------------------------------------------------- Slot ProcessId FileName FileMaxSize(KB) FileSize(bytes) ZipNumber LogId BufferSize(KB) WriteNumber WriteSize(bytes) DropNumber -------------------------------------------------------------------------------- 17 4 DevmKeyEvent.log 1024 5028 0 5 0 22 1863 0 17 4 devma.log 1024 36200 0 4 0 280 36196 0 17 4 bootpsrv_rpt.log 1024 2534 0 3 0 24 2530 0 17 4 patch.log 2048 37055 0 2 0 22 2553 0 17 4 rpmls.log 2048 13257 0 1 0 117 13253 0 17 3 rpm_other.log 2048 262 0 2 0 0 0 0 17 3 rpm.log 2048 20152 0 1 0 177 20148 0 17 2 ldevm.log 1024 8102 0 3 0 65 8098 0 17 2 DevmKeyEvent.log 1024 5028 0 2 0 37 3161 0 17 2 pdevm.log 1024 27665 0 1 0 207 27661 0 --------------------------------------------------------------------------------
Item | Description |
---|---|
Slot | Slot ID of a board. |
ProcessId | ID of a process. |
FileName | Name of a log file. |
FileMaxSize(KB) | Maximum size of a log file, in KB. |
FileSize(bytes) | Current size of a log file, in bytes. |
ZipNumber | Number of compressed log files. |
LogId | ID of a log file, which is unique in a process. |
BufferSize(KB) | Buffer size, in KB.
|
WriteNumber | Number of times that logs are recorded.
|
WriteSize(bytes) | Size of log contents, in bytes. |
DropNumber | Number of lost log files. |
display system debug queue info
Function
The display system debug queue info command displays queue information about the current system.
Parameters
Parameter | Description | Value |
---|---|---|
process procId |
Specifies the ID of a process. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
To check queue information about the current system, run the display system debug queue info command. The command output facilitates fault diagnosis.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system debug queue info System Queue Information: -------------------------------------------------------------------------------- ProcessID ProcessName CompCID CompName HandleID HandleName QueueID QueueName MaxLength CurLength -------------------------------------------------------------------------------- 2 SM 0x0 UNKNOW 527 vos_queue 1 rtfQueueName 1000 0 2 SM 0x0 UNKNOW 527 vos_queue 2 evtQueName_0 1000 0 2 SM 0x0 UNKNOW 527 vos_queue 3 rtfQueueName 1000 0 2 SM 0x0 UNKNOW 527 vos_queue 4 evtQueName_0 1000 0 2 SM 0x0 UNKNOW 527 vos_queue 5 rtfQueueName 1000 0 2 SM 0x0 UNKNOW 527 vos_queue 6 evtQueName_0 1000 0 2 SM 0x0 UNKNOW 527 vos_queue 7 rtfQueueName 1000 0 2 SM 0x0 UNKNOW 527 vos_queue 8 evtQueName_0 1000 0 2 SM 0x0 UNKNOW 527 vos_queue 9 evtQueName_1 1000 0 3 CFG 0x0 UNKNOW 527 vos_queue 1 rtfQueueName 1000 0 3 CFG 0x0 UNKNOW 527 vos_queue 2 evtQueName_0 1000 0 3 CFG 0x0 UNKNOW 527 vos_queue 3 rtfQueueName 1000 0 3 CFG 0x0 UNKNOW 527 vos_queue 4 evtQueName_0 1000 0 --------------------------------------------------------------------------------
Item | Description |
---|---|
System Queue Information | Queue information about the current system. |
ProcessID | Process ID. |
ProcessName | Process name. |
CompCID | Component ID. |
CompName | Component name. |
HandleID | Handle ID. |
HandleName | Handle name. |
QueueID | Queue ID. |
QueueName | Queue name. |
MaxLength | Maximum queue length. |
CurLength | Current queue length. |
display system debug seccomp
Function
The display system debug seccomp command displays the allowed and disabled systerm calls of a process.
Parameters
Parameter | Description | Value |
---|---|---|
all |
Specifies all board record. |
- |
slot SlotId |
Specifies a slot ID. |
- |
process ProcessId |
Specifies the ID of a process. |
The value is an integer that ranges from 0 to 4294967295. |
Usage Guidelines
You can run this command to view the allowed and disabled system calls of a process.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system debug seccomp ------------------------------------------------------------------------------- SlotID: 1 ProcessID: 1015 ProcessName: APPLocation10001 SysCalWhitelist: NA SysCalBlacklist: setuid setgid chown ------------------------------------------------------------------------------- SlotID: 1 ProcessID: 3 ProcessName: CFG SysCalWhitelist: read write open close SysCalBlacklist: NA ------------------------------------------------------------------------------- SlotID: 1 ProcessID: 1000 ProcessName: CONSOLE SysCalWhitelist: NA SysCalBlacklist: NA ------------------------------------------------------------------------------- SlotID: 1 ProcessID: 1002 ProcessName: FESMB SysCalWhitelist: NA SysCalBlacklist: NA ------------------------------------------------------------------------------- SlotID: 1 ProcessID: 4 ProcessName: LM SysCalWhitelist: NA SysCalBlacklist: NA ------------------------------------------------------------------------------- SlotID: 1 ProcessID: 1003 ProcessName: OPS SysCalWhitelist: NA SysCalBlacklist: NA ------------------------------------------------------------------------------- SlotID: 1 ProcessID: 10001 ProcessName: PROTO1 SysCalWhitelist: NA SysCalBlacklist: NA ------------------------------------------------------------------------------- SlotID: 1 ProcessID: 1001 ProcessName: PROTO2 SysCalWhitelist: NA SysCalBlacklist: NA ------------------------------------------------------------------------------- SlotID: 1 ProcessID: 2 ProcessName: SM SysCalWhitelist: NA SysCalBlacklist: NA -------------------------------------------------------------------------------
display system error
Function
The display system error command displays system error information about a specified board.
Parameters
Parameter | Description | Value |
---|---|---|
slot slotID |
Displays system error information about a specified board. |
- |
Usage Guidelines
Usage Scenario
To check the system error information about a specified board, run the display system error slot command in diagnostic view.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system error slot 1 --------------------------------------------------------------------------------- All Information --------------------------------------------------------------------------------- 150830-05:27:07.892510 [MON][MID:0x01]VRP_CreateTask error, please use VOS_TaskCreate 150830-05:27:08.145377 [MON][MID:0x01]VRP_CreateTask error, please use VOS_TaskCreate 150830-05:27:08.177402 [MON][MID:0x01]VRP_CreateTask error, please use VOS_TaskCreate
display system memory handle-alloc process
Function
The display system memory handle-alloc process command displays the memory allocation of a process.
Parameters
Parameter | Description | Value |
---|---|---|
process processid |
Displays the memory allocation of a process. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
To check the memory allocation of a specified process, run the display system memory handle-alloc process command in the diagnostic view.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system memory handle-alloc process 3 ---------------------------------------------------------------------------- HandleID HandleName UsedMemory(B) ---------------------------------------------------------------------------- 0 vos.sys 2,146,368 1 vos.handle.invalid 452,980 2 vos_sema 35,704 3 vos_task 267,184 4 v_db2 19,402,100 5 dms.msp 0 6 dms.msq 826,612 7 vos_timer 179,972 8 vos.memleakscan.memleakscanPID 0 9 vos_queue 687,712 10 vos_rtsched 1,788 11 dms.tkm 3,428 12 dms.cam 27,120 13 dms.pam 66,080 14 dms.tipc 8,352 15 dms.mcm 0 16 dms.dbg 12,384 17 rtf.cma 2,000 18 rtf.ccm 43,024 19 rtf.scm 20,284 20 vos_rtcom 9,452 21 dms.fcm 2,724 22 dms.mcfcm 1,344 23 dms.pipe 242,192 24 dms.dbf 1,104 25 00000001_00001234 74,212 26 00000001_00000000 92,652 27 00000001_00000001 16,392 28 00000001_00000002 84 29 00000001_00000003 84 30 00000001_00000004 84 31 00000001_00000005 84 32 00000001_00000006 876 33 00000005_00000001 272 34 00000005_00000002 0 35 00000001_00001235 17,096 36 00000002_00000001 52,295,952 37 00000001_00001236 28,856 38 00000003_00000001 0 39 00000001_00001237 6,284 40 00000004_00000001 0 41 00000001_00001238 23,344 ----------------------------------------------------------------------------
display system memory leak information
Function
The display system memory leak information command displays information about the memory leak call stack of a specified process.
Parameters
Parameter | Description | Value |
---|---|---|
show-num |
Specifies the number of memory leak call stacks. |
The value is an integer ranging from 1 to 100. |
process process-id |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
To locate a memory abnormality, run the display system memory leak information command to check information about the memory leak call stack of a specified process.
Prerequisites
The check result can be displayed only after you enable the check function using the debug system memory leak on process command.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system memory leak information 2 process 10001 -------------------------Show CallStack------------------------- #00: location(malloc+0x3c) [0x806260c] #01: libcommon.so(VRP_BoxReadDataInner+0x24) [0xb782f4e4] #02: libcommon.so(VRP_BoxReadDebugInfo+0x44) [0xb782f744] #03: libddma.so(DDMA_BSCReadBufferCycTimer+0xde) [0xb29c085e] #04: semagt.so(SEMAGT_CallbackFunctionForAppTmr+0xa5) [0xb2a544e5] #05: libapp_timer.so(twl_proc_by_timer+0x12a) [0xb6f6d27a] #06: libapp_timer.so(twl_tick+0x10c) [0xb6f6d93c] #07: libapp_timer.so(APPTMR_LibRcvMsg+0x1e1) [0xb6f6c461] #08: libsspbase.so(VRP_ProcTimerMsgWithAppTmr+0x32) [0xb6f50172] #09: semagt.so(SEMAGT_ProcMsg+0x227) [0xb2a5fdf7] -------------------------Show CallStack------------------------- #00: location(malloc+0x3c) [0x806260c] #01: libcommon.so(VRP_BoxReadDataInner+0x24) [0xb782f4e4] #02: libcommon.so(VRP_BoxReadDebugInfo+0x44) [0xb782f744] #03: libddma.so(DDMA_BSCReadBufferCycTimer+0xde) [0xb29c085e] #04: semagt.so(SEMAGT_CallbackFunctionForAppTmr+0xa5) [0xb2a544e5] #05: libapp_timer.so(twl_proc_by_timer+0x12a) [0xb6f6d27a] #06: libapp_timer.so(twl_tick+0x10c) [0xb6f6d93c] #07: libapp_timer.so(APPTMR_LibRcvMsg+0x1e1) [0xb6f6c461] #08: libsspbase.so(VRP_ProcTimerMsgWithAppTmr+0x32) [0xb6f50172] #09: semagt.so(SEMAGT_ProcMsg+0x227) [0xb2a5fdf7]
display system memory process simple-to-block status
Function
The display system memory process simple-to-block status command displays whether the conversion from simple memory to block memory is enabled in a specified process.
Parameters
Parameter | Description | Value |
---|---|---|
process processid |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
To check whether the conversion from simple memory to block memory is enabled in a specified process, run the display system memory process simple-to-block status command in the diagnostic view.
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system memory process 1004 simple-to-block status Simple memory change to block status: ------------------------------------------------- ProcessId Status Interval(min) RemainTime(sec) ------------------------------------------------- 1004 Disable 0 0 -------------------------------------------------
display system memory statistics
Parameters
Parameter | Description | Value |
---|---|---|
slot slot-id |
Displays the system memory statistics about a specified board. |
- |
Usage Guidelines
Usage Scenario
To check the memory statistics about the system or a system file, run the display system memory statistics command in diagnostic view.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system memory statistics slot 3 Slot 3 memory utilization statistics at 2021-02-08 03:09:31 183 ms ---------------------------------------------------------------------------------------------------------------------------------------- System Total : 12174260 kB System Used : 1902208 kB System Free : 10272052 kB HugePages Total : 0 HugePages Free : 0 Hugepagesize : 2048 kB ---------------------------------------------------------------------------------------------------------------------------------------- System Used : 1902208 kB ---------------------------------------------------------------------------------------------------------------------------------------- 1. Process Memory : 3030196 kB 2. Filesystem Memory : 31672 kB 3. Shared Memory : 0 kB 4. Other Memory : 0 kB ---------------------------------------------------------------------------------------------------------------------------------------- 1. Process Memory Detail : 3030196 kB ---------------------------------------------------------------------------------------------------------------------------------------- OsProcID ProcID ProcName VrpTotal MsgUsed PatchUsed Blackbox SoData Stack Libc Mmap Total ---------------------------------------------------------------------------------------------------------------------------------------- 104631 3 CFG 3072 10072 512 2984 2268 2100 0 360328 381336 1861 0 gnome-shell 0 0 0 0 5564 148 0 186876 192588 107829 0 java 0 0 0 0 2016 136 0 174956 177108 2411 0 java 0 0 0 0 2016 136 0 156288 158440 1177 0 messageservice 0 0 0 0 120 136 0 123676 123932 106095 1005 PROTO2 1792 8984 512 2984 2244 1420 0 102368 120304 106103 1008 OPS 1792 8984 512 2984 1444 1080 0 87036 103832 106088 1007 FESMB 1792 8984 512 2984 1272 944 0 73920 90408 2527 0 spesservice 0 0 0 0 120 136 0 74688 74944 ---------------------------------------------------------------------------------------------------------------------------------------- 2. Filesystem Memory Detail : 31668 kB ---------------------------------------------------------------------------------------------------------------------------------------- FileSysPath Used(kB) ---------------------------------------------------------------------------------------------------------------------------------------- /dev/shm 15436 /run 10152 /run/user/483 16 /sys/fs/cgroup 0 /run/user/0 0 /mnt/tmpfs/python 6064 /mnt/tmpfs 0 /mnt/tmpfs/pyrun/dev 0 ---------------------------------------------------------------------------------------------------------------------------------------- 3. Shared Memory Detail : 0 kB ---------------------------------------------------------------------------------------------------------------------------------------- shmid key Used(kB) ---------------------------------------------------------------------------------------------------------------------------------------- 0 0 0 ----------------------------------------------------------------------------------------------------------------------------------------
Item | Description |
---|---|
System Total | Total system memory. |
System Used | Used system memory. |
System Free | Available system memory. |
HugePages Total | The total number of huge pages. |
HugePages Free | The free number of huge pages. |
Hugepagesize | The size of huge page. |
Process Memory | Memory occupied by processes. |
Process Memory Detail | Details about process memory. |
Filesystem Memory | Memory occupied by system files. |
Filesystem Memory Detail | Details about system file memory. |
Shared Memory | Memory shared by processes. |
Shared Memory Detail | Details about shared memory. |
ProcID | Process ID. |
ProcName | Process name. |
VrpTotal | Total virtual memory of a board. |
MsgUsed | Memory used by messages. |
PatchUsed | Memory requested by the patch mechanism. |
Blackbox | The size of black box. |
SoData | SO data. |
Stack | Stack memory. |
Libc | Memory requested by the malloc function. |
Mmap | Memory requested by the mmap function. |
FileSysPath | System file path. |
Used(kB) | System file size. |
shmid | Shmid of sysvipc/shm. |
key | Key of sysvipc/shm. |
display system memory statistics(Diagnostic view)
Parameters
Parameter | Description | Value |
---|---|---|
slot slot-id |
Displays the system memory statistics about a specified board. |
- |
filesystem |
Displays the memory statistics about a specified system file. |
- |
Usage Guidelines
Usage Scenario
To check the memory statistics about the system or a system file, run the display system memory statistics command in diagnostic view.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system memory statistics filesystem slot 1 ------------------------------------------------------------------------------------------------------------------------ Type FileSysPath Used(kB) -------------------------------------------------------------------------------- FILE /opt/vrpv8/cc/V800R008C10B392-OC-CX-X1X2D05314228 FILE /dev/pShm_h000003e8 1040 FILE /dev/pShm_h00000000 1040 FILE /dev/pShm_h000003e9 1040 FILE /dev/pShm_h00000002 1040 FILE /dev/pShm_h00000003 1040 FILE /dev/pShm_h00002711 1040 FILE /tmp/sysmon.log 120 FILE /tmp/boot.log 80 FILE /tmp/chm.log 40 FILE /tmp/bspboot.log 24 FILE /dev/pShm_l00000000 24 FILE /tmp/bootinfo/bootinfo_slot_5.log 24 FILE /dev/pShm_l00000002 24 FILE /dev/pShm_l000003e8 24 FILE /dev/pShm_l000003e9 24 FILE /dev/pShm_l00002711 24 FILE /dev/pShm_l00000003 24 FILE /dev/000703e9_exp 12 FILE /dev/00070003_exp 12 FILE /dev/00070002_exp 12 FILE /dev/00072711_exp 12 FILE /dev/000703e8_exp 12 FILE /dev/00070000_exp 12 FILE /tmp/bootinfo/bootinfo_slot_7.log 8 FILE /mnt/tmpfs/R00B07L3/box/cfgdiff_0_12 4 FILE /tmp/startup_file_crc.txt 4 FILE /tmp/ver_desc.bin 4 FILE /var/lib/logrotate.status 4 ------------------------------------------------------------------------------------------------------------------------
display system memory verbose process
Function
The display system memory verbose process command displays information about the memory in a specified process.
Format
display system memory verbose process processid partition partitionid record reccount
display system memory verbose process processid partition partitionid memhandle memhandleid record reccount
display system memory handle-alloc process processid memhandle memhandleid
Parameters
Parameter | Description | Value |
---|---|---|
partition partitionid |
Displays information about the memory in a specified partition. |
The value is an integer ranging from 0 to 9. |
record reccount |
Specifies the number of records to be displayed. |
The value is an integer ranging from 1 to 65533. |
process processid |
Displays information about the memory in a specified process. |
The value is an integer ranging from 0 to 4294967295. |
memhandle memhandleid |
Specifies the memory handle ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
When the memory usage is high, you can run the display system memory verbose command to check the memory usage information.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system memory verbose process 10001 partition 2 ---------------------------------------------------------------------- PT No. 2 PT Name pipePT PT Algo Name DLM Piece Number 1 Total Size 1,048,576(B) Free Size 704,828(B) Max Block Size 643,256(B) Used Percent 32% ---------------------------------------------------------------------- PieceIndex Length(B) UsedSize(B) Begin End ---------------------------------------------------------------------- 0 1,048,576 341,012 [0xB6E0D008] [0xB6F0D008] ----------------------------------------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system memory verbose process 10001 partition 0 record 2 -------------------------------------------------------------------------------- HandleID Time(ms) Size(B) PartName MallocFileLine MallocFileName -------------------------------------------------------------------------------- 1 1357650 24 SYSPT 3451 SSP_dbg_base.c 4 1357760 12 SYSPT 3436 SSP_dbg_base.c -------------------------------------------------------------------------------- Total = 2
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system memory verbose process 10001 partition 0 memhandle 1 record 20 -------------------------------------------------------------------------------- HandleID Time(ms) Size(B) PartName MallocFileLine MallocFileName -------------------------------------------------------------------------------- 1 1308840 24 SYSPT 345 SSP_dbg_base.c 1 1308840 24 SYSPT 1024 SSP_dbg_base.c 1 1308840 32 SYSPT 33 SSP_dbg_base.c -------------------------------------------------------------------------------- Total = 3
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system memory handle-alloc process 3 ---------------------------------------------------------------------------- HandleID HandleName UsedMemory(B) ---------------------------------------------------------------------------- 0 vos.sys 2,146,368 1 vos.handle.invalid 452,980 2 vos_sema 35,704 3 vos_task 267,184 4 v_db2 19,402,100 5 dms.msp 0 6 dms.msq 826,612 7 vos_timer 179,972 8 vos.memleakscan.memleakscanPID 0 9 vos_queue 687,712 10 vos_rtsched 1,788 11 dms.tkm 3,428 12 dms.cam 27,120 13 dms.pam 66,080 14 dms.tipc 8,352 15 dms.mcm 0 16 dms.dbg 12,384 17 rtf.cma 2,000 18 rtf.ccm 43,024 19 rtf.scm 20,284 20 vos_rtcom 9,452 21 dms.fcm 2,724 22 dms.mcfcm 1,344 23 dms.pipe 242,192 24 dms.dbf 1,104 25 00000001_00001234 74,212 26 00000001_00000000 92,652 27 00000001_00000001 16,392 28 00000001_00000002 84 29 00000001_00000003 84 30 00000001_00000004 84 31 00000001_00000005 84 32 00000001_00000006 876 33 00000005_00000001 272 34 00000005_00000002 0 35 00000001_00001235 17,096 36 00000002_00000001 52,295,952 37 00000001_00001236 28,856 38 00000003_00000001 0 39 00000001_00001237 6,284 40 00000004_00000001 0 41 00000001_00001238 23,344 ----------------------------------------------------------------------------
Item | Description |
---|---|
PT No | Partition ID. |
PT Name | Partition name. |
PT Algo Name | Algorithm used in the partition. |
Piece Number | Number of pieces in the partition. |
Total Size | Memory size in the partition. |
Free Size | Remaining memory size in the partition. |
Max Block Size | Maximum available memory size. |
Used Percent | Memory usage in the partition. |
PieceIndex | Piece index. |
Length(B) | Piece length. |
UsedSize(B) | Used memory size. |
Begin | Start address of the piece. |
End | End address of the piece. |
HandleID | ID of the handle that applies for memory. |
Time(ms) | Time from memory application to the current time. |
Size(B) | Size of the memory to be applied for. |
PartName | Partition name. |
MallocFileLine | Number of an application line. |
MallocFileName | Indicates the name of the applied file. |
HandleName | Name of an operation group. |
UsedMemory(B) | Used memory. |
display system memory verbose(Diagnostic view)
Function
The display system memory verbose command displays information about the memory in a specified process or partition.
Parameters
Parameter | Description | Value |
---|---|---|
partition partitionid |
Displays information about the memory in a specified partition. |
The value is an integer ranging from 0 to 9. |
process processid |
Specifies a process ID. |
The value ranges from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
When the memory usage is high, you can run the display system memory verbose command to check the memory usage information.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system memory verbose process 10001 partition 2 ---------------------------------------------------------------------- PT No. 2 PT Name pipePT PT Algo Name DLM Piece Number 1 Total Size 1,048,576(B) Free Size 704,828(B) Max Block Size 643,256(B) Used Percent 32% ---------------------------------------------------------------------- PieceIndex Length(B) UsedSize(B) Begin End ---------------------------------------------------------------------- 0 1,048,576 341,012 [0xB6E0D008] [0xB6F0D008] ----------------------------------------------------------------------
Item | Description |
---|---|
PT No | Partition ID. |
PT Name | Partition name. |
PT Algo Name | Algorithm used in the partition. |
Piece Number | Number of pieces in the partition. |
Total Size | Memory size in the partition. |
Free Size | Remaining memory size in the partition. |
Max Block Size | Maximum available memory size. |
Used Percent | Memory usage in the partition. |
PieceIndex | Piece index. |
Length(B) | Piece length. |
UsedSize(B) | Used memory size. |
Begin | Start address of the piece. |
End | End address of the piece. |
display system message alloc process
Function
The display system message alloc process command displays the memory usage of messages of a process.
Parameters
Parameter | Description | Value |
---|---|---|
process processid |
Displays the memory usage of messages of a process. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
To check the memory usage of messages of a process, run the display system message alloc command in the diagnostic view. The command output helps query and locate faults.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system message alloc process 10001 ------------------------------------------------------------------------------- AllocMsgSize MaxMsgSize AreaName Percent UsedAreaNum TotalAreaNum ------------------------------------------------------------------------------- 0 1048576 AREA_SYS 0% 1 5 0 1048576 AREA_MGNT 0% 1 5 0 5242880 AREA_FLOWCTRL 0% 1 10 768 2097152 AREA_OTHER 0% 1 10 -------------------------------------------------------------------------------
Item | Description |
---|---|
AllocMsgSize | Size of the message memory that is being used. |
MaxMsgSize | Maximum message memory size that can be applied for. |
AreaName | Area name. |
Percent | Message memory usage. |
UsedAreaNum | Number of areas that are being used. |
TotalAreaNum | Total number of areas. |
display system message alloc-failed
Function
The display system message alloc-failed command displays information about failures to apply for memory.
Format
display system message alloc-failed process processid
display system message alloc-failed process processid verbose
Parameters
Parameter | Description | Value |
---|---|---|
process processid |
Displays information about failures to apply for memory in a specified process. |
The value is an integer ranging from 0 to 4294967295. |
verbose |
Displays the exported component information upon a memory application failure. |
- |
Usage Guidelines
Usage Scenario
Memory application failures cause system exceptions. If a system message exception occurs, view the cause for a memory application failure. To view information about the memory application failure, run the .
display system message alloc-failed command. The command output helps query and analyze faults. The display system message alloc-failed command output shows the memory application failure records, without any sensitive data.Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system message alloc-failed process 10001 ------------------------------------- CID AllocTime ------------------------------------- 0x712733 2013-08-11 21:27:39.509 0x712733 2013-08-11 21:27:32.911 0x800303FF 2013-08-11 21:26:54.477 -------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system message alloc-failed process 1001 verbose ********************* Process(1001) Msg Dump Begin 2014-1-15-7:45:13.334 ********************* Seq || SendCid || RecvCid || Intf || SubIntf || MsgType || MsgStatus || MsgLenth || Count || MaxTime || MsgData 0 0x8c0401 0xffffffff 3 77 0 1 8 1 65139 00000000 00000001 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 1 00000000 0xffffffff 0 0 0 1 65280 159 65082 03020100 07060504 0b0a0908 0f0e0d0c 000001f4 00030000 00030004 00000030 00000000 ffffffff 807803fb 00080000 ************************** Process(1001) Msg Timeout Dump End **************************
Item | Description |
---|---|
CID | Process ID. |
AllocTime | Time when memory application is processed. |
Seq | Serial number. |
SendCid | ID of a transmitting component. |
RecvCid | ID of a receiving component. |
Intf | Interface ID. |
SubIntf | Sub-interface ID. |
MsgType | Message type. |
MsgStatus | Message status. |
MsgLenth | Message length. |
Count | Count. |
MaxTime | Maximum time. |
MsgData | Message data. |
display system message statistic
Function
The display system message statistic command displays statistics about messages that are sent by components on a device.
The display system message statistic component command displays statistics about messages that are sent by a specific component on a device.
Parameters
Parameter | Description | Value |
---|---|---|
component cid |
Specifies a component. |
The value is a hexadecimal integer that ranges from 0-ffffffff. |
Usage Guidelines
Usage Scenario
To view statistics about communication messages sent by components on a device, run the display system message statistic command. The command output helps you diagnose a communication fault.
To view statistics about communication messages sent by a specified component on a device, run the display system message statistic component command. The command output helps you diagnose a communication fault.Prerequisites
The statistics collection function of components on a device has been enabled using the set message statistic on command.
After the statistics collection function is enabled on a device, the device will collect statistics about message sent by all components, affecting device system. Therefore, do not enable this function unless it is required.Precautions
- After the display system message statistic command is run, statistics about messages sent by all components on the device will be displayed.
- The communication IDs for the message sending end and receiving end can be PID or CID, depending on the APP code.
- Statistics collected are the number of messages and are irrelevant to message sizes.
- By default, statistics about messages sent by all components are not displayed. The display system message statistic command takes effect after you run the set message statistic on command.
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system message statistic component 2147680290 -------------------------------------------------------------------------------- From SendName To RecvName Number SendFail Wait-process -------------------------------------------------------------------------------- 2147681364 SEM_Agent 2147680290 SEM_Agent34 1 0 0 2147681364 SEM_Agent 2147680290 SEM_Agent34 1 0 0 2147681272 SEM_Agent 2147680290 SEM_Agent34 0 0 0 2147681272 SEM_Agent 2147680290 SEM_Agent34 0 0 0 6292475 LOGSERVER 2147680290 SEM_Agent34 1 0 0 6292475 LOGSERVER 2147680290 SEM_Agent34 1 0 0 2147681401 SEM_Agent 2147680290 SEM_Agent34 0 0 1 2147681401 SEM_Agent 2147680290 SEM_Agent34 1 0 1 2147680287 SEM_Agent31 2147680290 SEM_Agent34 1 0 0 2147680287 SEM_Agent31 2147680290 SEM_Agent34 1 0 0 2147681404 SEM_Agent 2147680290 SEM_Agent34 1 0 0 2147681404 SEM_Agent 2147680290 SEM_Agent34 1 0 0 2147680290 SEM_Agent34 2147680290 SEM_Agent34 417 0 0
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system message statistic -------------------------------------------------------------------------------- From SendName To RecvName Number SendFail -------------------------------------------------------------------------------- 2163998757 DEVMA37 0 - 0 0 7874329 LDM 6947843 FESDS 0 0 6947843 FESDS 7874329 LDM 3 0 2147614756 SEM_LS36 2147549190 SEM4 9 0 2147549190 SEM4 2147614756 SEM_LS36 9 0 2147614756 SEM_LS36 2147614756 SEM_LS36 1060 0 2147614756 SEM_LS36 2147614756 SEM_LS36 1060 0 2147680290 SEM_Agent34 6292475 LOGSERVER 1 0 6292475 LOGSERVER 2147680290 SEM_Agent34 1 0 ...... -------------------------------------------------------------------------------- Total = 1390
Item | Description |
---|---|
From | Communication ID of a message sending component. |
SendName | Name of a message sending component. |
To | Communication ID of a message receiving component. |
RecvName | Name of a message receiving component. |
Number | Number of messages sent successfully. |
SendFail | Number of messages sent unsuccessfully. |
Wait-process | Number of messages to be processed. |
Total | Total number of the messages. |
display system os-memory process
Parameters
Parameter | Description | Value |
---|---|---|
process process-id |
Displays the memory usage of an OS process with the specified process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
If a device encounters a high memory usage problem, run the display system os-memory slot command to identify the board with the highest memory usage, and then run the display system os-memory process command to learn the memory usage of specific OS processes.
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system os-memory process 3 Os process ID : 104631 Process stack memory : 3712 Kbytes Process thread numer : 29 limit stack memory : 128 Kbytes Process shared RSS memory : 36 Kbytes Process shared PSS memory : 24 Kbytes Process shared VM memory : 240 Kbytes Process data RSS memory : 354760 Kbytes Process data PSS memory : 354492 Kbytes Process data VM memory : 819508 Kbytes Process code RSS memory : 46752 Kbytes Process code PSS memory : 24113 Kbytes Process code VM memory : 59376 Kbytes Process black box RSS memory : 1060 Kbytes Process black box PSS memory : 1060 Kbytes Process black box VM memory : 2984 Kbytes Process total RSS memory : 402608 Kbytes Process total PSS memory : 379689 Kbytes Process total VM memory : 946832 Kbytes -------------------------------------------------------------------------------- Name Type Size(Kbytes) RSS(Kbytes) PSS(Kbytes) VM_Account -------------------------------------------------------------------------------- DATA rw-p 128 20 20 1 ld-2.22.so rw-p 4 4 4 1 ld-2.22.so r--p 4 4 4 1 ld-2.22.so r-xp 132 132 6 0 DATA r-xp 8 4 0 0 DATA r--p 12 0 0 0 DATA rw-p 8444 6108 6108 1 ...
Item | Description |
---|---|
Os process ID | OS process ID. |
Process stack memory | Size of the stack memory in a process. |
Process thread numer | Number of threads in a process. |
Process shared RSS memory | Physical memory size of the shared memory in a process. |
Process shared PSS memory | Size of the PSS of the shared memory in the process. |
Process shared VM memory | Virtual memory size of the shared memory in a process. |
Process data RSS memory | Physical memory size of the code segment in the process. |
Process data PSS memory | Size of the PSS of the data segment in the process. |
Process data VM memory | Virtual memory size of the data segment in the process. |
Process code RSS memory | Size of the physical memory of the code segment in the process. |
Process code PSS memory | Size of the PSS of the code segment in the process. |
Process code VM memory | Virtual memory size of the code segment in the process. |
Process black box RSS memory | Physical memory size of the black box in the process. |
Process black box PSS memory | Size of the PSS of the black box in the process. |
Process black box VM memory | Virtual memory size of the black box in the process. |
Process total RSS memory | Total physical memory size in a process. |
Process total PSS memory | Total size of the PSS in the process. |
Process total VM memory | Total virtual memory size in a process. |
limit stack memory | Limited stack size of a thread. |
Name | Area name. |
Type | Type. |
Size(Kbytes) | Size, expressed in Kbytes. |
RSS(Kbytes) | Rss size, expressed in Kbytes. |
PSS(Kbytes) | Pss size, expressed in Kbytes. |
VM_Account | Is a VM accounted object. |
display system os-memory slot
Function
The display system os-memory slot command displays the memory usage of OS processes on a board.
The display system os-memory slabinfo slot command displays the memory usage of the OS on a board.
Parameters
Parameter | Description | Value |
---|---|---|
slot slotID |
Displays the memory usage of OS processes on a board with the specified slot ID. |
- |
Usage Guidelines
If a device encounters a high memory usage problem, run the display system os-memory slot command to identify the board with the highest memory usage, and then run the display system os-memory process command to learn the memory usage of specific OS processes.
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system os-memory slot 3 Kernel Memory Used : 411556 Kbytes Kernel Reserve Memory : 0 Kbytes System Code Memory Used : 155156 Kbytes System Data Memory Used : 15884 Kbytes System Black Box Used : 41776 Kbytes System Stack Memory Used : 27776 Kbytes HighTotal : 0 Kbytes HighFree : 0 Kbytes LowTotal : 0 Kbytes LowFree : 0 Kbytes System Process Memory Used : -------------------------------------------------------------------------------- OsProcessId OsProcessName VMRSS(Kbytes) VMdata(Kbytes) MemoryUsage(Kbytes) -------------------------------------------------------------------------------- 2411 java 75092 3541680 3583428 105914 java 63324 3408552 3450300 1861 gnome-shell 151212 776564 1471844 1071 nscd 5096 1016176 1212200 1177 messageservice 21600 1040972 1076584 104631 monitor 401372 891216 955192 1841 gnome-settings- 32788 594324 954864 106095 monitor 126724 639608 702148 106103 monitor 94260 623264 661604 106068 monitor 77496 592228 652936 106088 monitor 77528 609948 646184 ...
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system os-memory slabinfo slot 3 proc slabinfo: -------------------------------------------------------------------------------- name active_objs num_objs objsize objperslab pagesperslab limit batchcount sharedfactor active_slabs num_slabs sharedavail squashfs_inode_cache 12485 12490 384 10 1 54 27 8 1249 1249 0 TIPC 14 30 384 10 1 54 27 8 3 3 0 tipc_queue_items 0 0 16 203 1 120 60 8 0 0 0 fib6_nodes 5 113 32 113 1 120 60 8 1 1 0 ip6_dst_cache 4 30 256 15 1 120 60 8 2 2 0 ndisc_cache 1 20 192 20 1 120 60 8 1 1 0 RAWv6 11 12 640 6 1 54 27 8 2 2 0 UDPLITEv6 0 0 640 6 1 54 27 8 0 0 0 --------------------------------------------------------------------------------
Item | Description |
---|---|
Kernel Memory Used | Kernel memory used. |
Kernel Reserve Memory | Kernel memory reserved. |
System Code Memory Used | System code memory used. |
System Data Memory Used | System data memory used. |
System Black Box Used | System black box memory used. |
System Stack Memory Used | System stack memory used. |
HighTotal | High-order address memory used. |
HighFree | High-order address memory unused. |
LowTotal | Low-order address memory used. |
LowFree | Low-order address memory unused. |
OsProcessId | OS process ID. |
OsProcessName | OS process name. |
VMRSS(Kbytes) | Physical memory usage (Kbytes). |
VMdata(Kbytes) | Size of data segments. |
MemoryUsage(Kbytes) | Memory usage, expressed in Kbytes. |
OsprocessID | OS process ID. |
Name | Area name. |
Type | Type. |
display system os-process
Parameters
Parameter | Description | Value |
---|---|---|
interval interval-time |
Displays the CPU usage of OS processes within the specified interval. |
The value is an integer ranging from 1 to 10, in seconds. |
slot slotID |
Displays the CPU usage of OS processes on a board with the specified slot ID. |
The value is an integer ranging from 1 to 31. |
Usage Guidelines
Usage Scenario
If a device encounters a high CPU usage problem, you can run the display system os-process command to determine whether the high CPU usage is caused by processes created by non-VRPv8 process frameworks.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system os-process slot 10 interval 3 Info: This operation needs several seconds. Info: Operating, please wait for a moment...done. -------------------------------------------------------- OsProcessID OsProcessname Usage -------------------------------------------------------- 1 init 0% 2 kthreadd 0% 3 migration/0 0% 4 ksoftirqd/0 0% 5 watchdog/0 0% 6 migration/1 0% 7 ksoftirqd/1 0% 8 watchdog/1 0% 9 migration/2 0% 10 ksoftirqd/2 0% 11 watchdog/2 0% 12 migration/3 0% 13 ksoftirqd/3 0% 14 watchdog/3 0% 15 events/0 0% 16 events/1 0%
display system thread
Function
The display system thread command displays CPU usage and stack memory of all threads of a device.
Parameters
Parameter | Description | Value |
---|---|---|
process processId |
Displays CPU usage and stack memory of all threads of a specified process. |
The value is an integer ranging from 0 to 4294967295. |
interval interval-time |
Displays CPU usage and stack memory of all threads in a specified interval. |
The value is an integer ranging from 1 to 10, in seconds. |
slot slotId |
Displays CPU usage and stack memory of all threads of a specified board. |
The value is a string of 1 to 31 |
Usage Guidelines
To view CPU usage and stack memory of all threads of a device, run the display system thread command. This helps maintain device performance in time.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display system thread process 3 interval 10 Info: Operating, please wait for a moment...............done. -------------------------------------------------------------------------------- Process ID Thread ID Tid Thread Type BindComp BindCpu BindFlag Usage StackMem(kb) -------------------------------------------------------------------------------- 3 4136863552 23443 monitor Free all Free 0% 116 3 3961846592 23553 ADMSESS0 Free all Free 0% 132 3 3861379904 23554 ADMSESS1 Free all Free 0% 132 3 3989433152 23481 CFGSYNCFGDI2 Free all Free 0% 132 3 3998088000 23479 CFGSYNCFGDI0 Free all Free 0% 132 3 3989568320 23480 CFGSYNCFGDI1 Free all Free 0% 132 3 3989297984 23478 DefSch0100 Free all Free 0% 132 3 3759164224 23556 ADMAPPDB1 Free all Free 0% 132 3 3916495680 23563 DefSch0300 Free all Free 0% 132 3 3504274240 24506 DefSch0600 Bind all Free 0% 68 3 3753519936 23557 ADMAPPDB2 Free all Free 0% 132 3 3510565696 24505 DefSch0400 Free all Free 0% 132 3 3727891264 24498 DefSch0400 Bind all Free 0% 68 3 3545480000 24504 DefSch0500 Bind all Free 0% 68 3 3523345216 24507 DefSch0500 Free all Free 0% 132 3 4025998144 23477 DefSch0800 Bind all Free 0% 68 3 3995765568 23475 DefSch0300 Bind all Free 0% 516 3 4114725696 23450 RtSchedTask Free all Free 0% 32 3 4070349632 23451 DMS_TIPC_SEND Free all Free 0% 68 3 4084005696 23449 BOX_Out Free all Free 0% 132 3 4115135296 23447 VCLK Free 0 Free 0% 32 3 4115102528 23448 TICK Free all Free 0% 32 3 3993893696 23476 DefSch0700 Bind all Free 0% 68 3 4064475968 23453 IPC0000 Free all Free 0% 68 3 4060015424 23460 SoLoad_0 Free all Free 0% 132 3 4057393984 23465 DefSch0101 Bind all Free 0% 132 3 4088789824 23454 DefSch0200 Bind all Free 0% 68 3 4057529152 23464 DefSch0100 Bind all Free 0% 132 3 4061723456 23461 DefSch0900 Bind all Free 0% 68 3 3764595520 34011 CliGetThreadCpu Free all Free 0% 132 -------------------------------------------------------------------------------- Total = 30
Item | Description |
---|---|
Process ID | Process ID. |
Thread ID | Thread ID. |
Thread Type | Thread type. |
Tid | The system thread ID. |
BindComp | Whether the thread is bound to a component. |
BindCpu | CPU to which the thread is bound. |
BindFlag | Whether the thread is bound to a CPU. |
Usage | CPU usage of the thread. |
StackMem(kb) | Stack memory(kb). |
Total | Total number of the thread. |
display thread callstack
Function
The display thread callstack command displays callstack information of all threads in a specified process.
Parameters
Parameter | Description | Value |
---|---|---|
thread-id |
Displays callstack information of a specified thread in the process. |
The value is an integer ranging from 0 to 18446744073709551615. |
process process-id |
Displays callstack information of all threads in a specified process. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
When callstack scheduling is blocked and you need to know whether a dead loop occurred in the process or a function occupies a thread for a long time, you can run this command to view callstack information of all threads in a specified process.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display thread callstack process 3 Thread 0 (Thread MainThread): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] #02 0xb7ab294d libsspbase.so(SSP_sleep+0x1d) [0xb7ab294d] #03 0x0804e39c location(LOC_BlockMainThread+0xac) [0x804e39c] #04 0x08051158 location(LOC_LocationMain+0x3b8) [0x8051158] #05 0x08051442 location(main+0x32) [0x8051442] #06 0xb783087c libc.so.6(__libc_start_main+0xdc) [0xb783087c] #07 0x0804cbf1 location [0x804cbf1] Thread 1 (Thread BOX_Out): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 2 (Thread VCLK): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 3 (Thread TICK): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 4 (Thread DMS_TIPC_SEND): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 5 (Thread IPC0000): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 6 (Thread DefSch0200): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 7 (Thread DefSch0900): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 8 (Thread DefSch0100): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 9 (Thread DefSch0101): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 10 (Thread DefSch0300): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 11 (Thread DefSch0800): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 12 (Thread DefSch0700): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 13 (Thread DefSch0a00): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 14 (Thread DefSch0400): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 15 (Thread DefSch0500): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410] Thread 16 (Thread DefSch0600): #00 0xb7aa8496 libsspbase.so(SSP_ProcCallStackSigFunc+0x116) [0xb7aa8496] #01 0xffffe410 [0xffffe410]
display thread schedule
Function
The display thread schedule command displays scheduling distribution relationships among schedule containers, scheduling threads, and components in a process.
Parameters
Parameter | Description | Value |
---|---|---|
process process-id |
Specifies the process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
When components in the scheduler cannot be scheduled because a component spends a long time in processing messages, the display thread schedule command displays the distribution relationship among schedulers, scheduling threads, and components in a process for you to confirm component scheduling.
Precautions
This command is supported only on the admin VS.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display thread schedule process 2 ---------------------------------------------------------------------------- Schedule container: 1 Type: nobind Schedule threads list: Task-id Thread-id 9 1269589168 10 1270637744S Schedule components list: Bind-component Component-type Component-cid PDEVM2 250 0x80FA0003 LDEVM5 251 0x80FB0007 SOCK 101 0x806503F6 LCSS 77 0x804D2711 MPE 79 0x804F2712 TM_SVR 38 0x80262713 ---------------------------------------------------------------------------- Schedule container: 2 Type: bind Task-id Thread-id Bind-component Component-type Component-cid 6 1260139696 SEM_Agent4 3 0x80030004 ---------------------------------------------------------------------------- Schedule container: 3 Type: bind Task-id Thread-id Bind-component Component-type Component-cid 8 1263289520 APPCFG3 207 0x80CF0005 ---------------------------------------------------------------------------- Schedule container: 4 Type: bind Task-id Thread-id Bind-component Component-type Component-cid 7 1262240944 SEM4 1 0x80010006 ---------------------------------------------------------------------------- Schedule container: 5 Type: bind Task-id Thread-id Bind-component Component-type Component-cid 12 1282696368 DBG 50 0x80322728 ---------------------------------------------------------------------------- Schedule container: 6 Type: bind Task-id Thread-id Bind-component Component-type Component-cid 11 1281647792 DBG_AGENT 51 0x803303F5 ----------------------------------------------------------------------------
Item | Description |
---|---|
Schedule container | Scheduler ID. |
Schedule threads list | List of scheduling threads in a non-binding scheduler. |
Schedule components list | List of scheduling components. |
Task-id | ID of a system task. |
Thread-id | ID of a scheduling thread. |
Bind-component | Name of the component bound to a scheduler. |
Component-type | Type of the component bound to a scheduler. |
Component-cid | CID of the component bound to a scheduler. |
Type | Scheduler type. |
display timer slot
Function
The display timer slot command displays the number of timers and application handles within all processes on a board. Handles are carried during timer application to identify timer applicants.
Parameters
Parameter | Description | Value |
---|---|---|
slot slot-id |
Specifies the slot ID of an available slot.. |
- |
process proc-id |
Specifies the process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
This command displays the timer information for solving problems such as leakage and high resource usage due to too many applications when too many components use timers in the system. To check the Dopra timer usage in a specified process on a specified board, run the display system timer slot process command in the diagnostic view.
Precautions
This command is supported only on the admin VS.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display timer slot XX process 10001 Ssp apptimer: -------------------------------------------------------------------------------- ProcessId ProcessName TwlCycle TwlInterval(ms) TwlTimeOutCount TwlTicks AppTmrInterval(ms) AppTmrTimeOutCount AppTmrType AppTmrPara AppTmrFlag AppTmrRem(ms) TmrType CompCID CompName LastTimeOutTime -------------------------------------------------------------------------------- 10001 PROTO1 100 1000 8598 87 30000 615 0x1F 0xF0204828 0x80000008 28000 1 0x80222712 DIRECTRT_IPV6 20190822-16:52:51 059 ms 10001 PROTO1 100 1000 8598 81 30000 615 0x16 0xF02035C8 0x80000008 22000 1 0x80222712 DIRECTRT_IPV6 20190822-16:52:51 059 ms 10001 PROTO1 100 1000 8598 80 60000 307 0x2E 0xF02031C8 0x80000008 21000 1 0x80222712 DIRECTRT_IPV6 20190822-16:52:51 059 ms 10001 PROTO1 100 1000 8598 69 20000 922 0x34 0x4 0x80000002 10000 1 0x80222712 DIRECTRT_IPV6 20190822-16:52:51 059 ms 10001 PROTO1 100 1000 8598 63 5000 3690 0x36 0x0 0x80000002 4000 1 0x80222712 DIRECTRT_IPV6 20190822-16:52:51 059 ms 10001 PROTO1 100 1000 10790 88 30000 615 0x1F 0xF02048A8 0x80000008 29000 1 0x806F2713 DIRECTRT_IPV4 20190822-16:52:51 058 ms 10001 PROTO1 100 1000 10790 80 30000 615 0x16 0xF02036E8 0x80000008 21000 1 0x806F2713 DIRECTRT_IPV4 20190822-16:52:51 058 ms 10001 PROTO1 100 1000 10790 80 60000 307 0x2E 0xF0203788 0x80000008 21000 1 0x806F2713 DIRECTRT_IPV4 20190822-16:52:51 058 ms 10001 PROTO1 100 1000 10790 80 60000 307 0x2C 0xF02026E8 0x80000008 21000 1 0x806F2713 DIRECTRT_IPV4 20190822-16:52:51 058 ms 10001 PROTO1 100 1000 10790 63 5000 3690 0x36 0x0 0x80000002 4000 1 0x806F2713 DIRECTRT_IPV4 20190822-16:52:51 058 ms 10001 PROTO1 100 1000 10790 63 20000 921 0x34 0x4 0x80000002 4000 1 0x806F2713 DIRECTRT_IPV4 20190822-16:52:51 058 ms 10001 PROTO1 1000 1000 64823 600 300000 61 0x74 0x0 0x80000002 141000 1 0x8065042D SOCK 20190822-16:53:08 017 ms --------------------------------------------------------------------------------
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display timer slot XX Ssp apptimer: -------------------------------------------------------------------------------- ProcessId ProcessName TwlCycle TwlInterval(ms) TwlTimeOutCount TwlTicks AppTmrInterval(ms) AppTmrTimeOutCount AppTmrType AppTmrPara AppTmrFlag AppTmrRem(ms) TmrType CompCID CompName LastTimeOutTime -------------------------------------------------------------------------------- 1000 CONSOLE 600 100 271767 560 1200000 15 0x0 0x1040000 0x80000002 730400 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 552 10000 1847 0x10004 0x0 0x80000002 9600 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 506 5000 0 0x0 0x1160000 0x80000002 5000 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 496 10000 1846 0x0 0x1050000 0x80000002 4000 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 490 600000 30 0x0 0x1080000 0x80000002 123400 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 480 10000 1851 0x0 0x1030000 0x80000002 2400 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 473 3000 6155 0x0 0x1020000 0x80000002 1700 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 468 2000 9234 0x0 0x10A0000 0x80000002 1200 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 466 6000 3077 0x0 0x1010000 0x80000002 1000 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 464 1000 18455 0x0 0x1060000 0x80000002 800 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 463 1000 18457 0x0 0x1070000 0x80000002 700 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 461 1000 18454 0x0 0x1090000 0x80000002 500 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 459 60000 308 0x0 0x10E0000 0x80000002 300 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 458 1000 18451 0x0 0x1110000 0x80000002 200 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 457 500 36902 0x10002 0xF4B988A1 0x80000002 100 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 457 500 36902 0x10003 0xF4B988A0 0x80000002 100 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 457 1000 18451 0x10001 0x0 0x80000002 100 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 344 180000 102 0x0 0x1100000 0x80000002 48800 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms 1000 CONSOLE 600 100 271767 33 28800000 0 0x0 0x10F0000 0x80000002 10337700 1 0x800303EF SEM_Agent 20190822-16:53:10 004 ms
Item | Description |
---|---|
Ssp apptimer | Timer information. |
ProcessId | Process ID. |
ProcessName | Process name. |
TwlCycle | Time wheel cycle count. |
TwlInterval(ms) | Time wheel timeout precision (ms). |
TwlTimeOutCount | Timer weel timeout count. |
TwlTicks | Timer index on the time wheel. |
AppTmrInterval(ms) | App timer interval. |
AppTmrTimeOutCount | App timer timeout count. |
AppTmrType | App timer type. |
AppTmrPara | Input parameter during timer application. |
AppTmrFlag | Input flag during timer application. |
AppTmrRem(ms) | App timer interval remain. |
TmrType | Timer type. |
CompCID | CID Component CID. |
CompName | Component name. |
LastTimeOutTime | Last timeout time. |
display timer statistics process
Function
The display timer statistics process command displays timer statistics about the specified process.
Parameters
Parameter | Description | Value |
---|---|---|
procid |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
component compid |
Specifies a component ID. |
The value is a hexadecimal integer ranging from 00000001 to fffffff. |
Usage Guidelines
Usage Scenario
To check timer statistics about the specified process, run the display timer statistics process command.
Precautions
This command is supported only on the admin VS.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] display timer statistics process 3 =========Ssp apptimer statistics info========= Period Timer Cycle (ms): 100 Period Timer Count: 585964 App Timer Cycle (ms): 500 App Timer Count: 125020 App Timer Para: 4105162056 App Timer Remain: 400 App Timer Type: 65539 Component cid: 0x80030008 Component Name: SEM_Agent8 Max Process Time (ms): 0 Max Tick Overload Time (ms):540 Overload <0 : 0 0% Overload 0%~25% : 10 100% Overload 25%~50% : 0 0% Overload 50%~75% : 0 0% Overload >=75% : 0 0% Index TimeOutTime(ms) ProceTime(ms) 1 500 0 2 500 0 3 500 0 4 500 0 5 500 0 6 500 0 7 500 0 8 510 0 9 500 0 10 500 0
Item | Description |
---|---|
Period Timer Cycle (ms) | Time wheel cycle, in milliseconds. |
Period Timer Count | Number of timer invoking times in the current period. |
App Timer Cycle (ms) | Timer period, in milliseconds. |
App Timer Count | Number of timer invoking times. |
App Timer Para | Timer parameter. |
App Timer Remain | Time left before the next timer is triggered. |
App Timer Type | Timer type. |
Component cid | Component ID. |
Component Name | Component name. |
Max Process Time (ms) | Maximum time during which the timer callback function runs, in milliseconds. |
Max Tick Overload Time (ms) | Maximum timer offset, in milliseconds. |
Overload | Timer timeout details about each level. |
Index | Timer index (Value 1 indicates the latest timer.). |
TimeOutTime(ms) | Timer timeout period, in milliseconds. |
ProceTime(ms) | Processing time of the timer callback function, in milliseconds. |
reset message pipe-statistic
Function
The reset message pipe-statistic command clears statistics about the packets sent and received through the pipe of a specified component or the pipes of all components.
Parameters
Parameter | Description | Value |
---|---|---|
all |
Clears statistics about the packets sent and received through the pipes of all components. |
- |
component compid |
Specifies a component ID. |
The value ranges from 0 to FFFFFFFF, in hexadecimal notation. |
Usage Guidelines
Usage Scenario
When checking statistics about the packets sent and received through the pipe of a specified component or the pipes of all components during a certain period, run the reset message pipe-statistic command to clear historical statistics about the packets.
Precautions
This command is supported only on the admin VS.
reset message send-receive-statistic
Function
The reset message send-receive-statistic command clears statistics about the packets sent and received by components.
Usage Guidelines
Usage Scenario
When checking statistics about the packets sent and received by components during a certain period, run the reset message send-receive-statistic command to clear historical statistics about the packets.
To enable or disable the function to collect statistics about the packets sent and received by components, run the set message send-receive-statistic { on | off } command.Precautions
This command is supported only on the admin VS.
reset message-process statistic
Function
The reset message-process statistic command resets message status statistics for new statistics.
Parameters
Parameter | Description | Value |
---|---|---|
message-type |
Indicates a message type. If this parameter is specified, communication status statistics of a specified process can be viewed based on the message type. |
- |
process process-id |
Specifies the ID of a process. |
The value is an integer ranging from 0 to 4294967295. |
reset record
Function
The reset deadloop record command resets deadloop records on a board.
The reset error-information record command deletes error information in the system.
The reset exception record command resets exception records on a board.
The reset starvation record command clears starvation information of a system thread or component.
Format
reset exception record [ all | slot slotId ]
reset deadloop record [ all | slot slotId ]
reset starvation record [ all | slot slotId ]
reset error-information record [ all | slot slotId ]
Parameters
Parameter | Description | Value |
---|---|---|
all |
Clears starvation information on all boards. |
- |
slot slotId |
Clears starvation information on all specified board. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. |
Usage Guidelines
Usage Scenario
The reset deadloop record command resets deadloop records on a board.
After analyzing error information in the system, you can run the reset error-information record command to delete the information. The reset exception record command resets exception records on a board. To get precise starvation information to better locate a fault, run the reset starvation record command to clear the previous starvation information before the display starvation command is executed.Precautions
This command is supported only on the admin VS.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] reset starvation record all Info: Operation succeeded.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] reset exception record 1 Info: Operation succeeded.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] reset error-information record all Info: Operation succeeded.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] reset deadloop record all Info: Operation succeeded.
reset assert record
Function
The reset assert record command resets all current assertion records on a board.
The reset reportfailure record command resets historical failure records on a board.
Parameters
Parameter | Description | Value |
---|---|---|
all |
Clears all statistics. |
- |
slot slotId |
Specifies the slot ID of an in-position interface board. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. |
Usage Guidelines
Usage Scenario
This command is used to clear all assertions or fault records on the current board.
Precautions
This command is supported only on the admin VS.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] reset reportfailure record Info: Operation succeeded.
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] reset assert record Info: Operation succeeded.
schedule-trace
Function
The reset schedule-trace command deletes message scheduling tracing records.
The schedule-trace on command enables the message tracing function.
The schedule-trace off command disables the message tracing function.
Format
schedule-trace { all | slot slot-id | process process-id } { { thread thread-id | all-thread } | { intf-value { subintf-value | all-subintf } | all-intf } } { off }
schedule-trace { all | slot slot-id | process process-id } pipe { off }
schedule-trace { all | slot slot-id | process process-id } [ pipe ] interval interval-value [ record record-value ] [ output-mode { memory | file | both } ]
schedule-trace { all | slot slot-id | process process-id } { { thread thread-id | all-thread } | { intf-value { subintf-value | all-subintf } | all-intf } } { on }
schedule-trace { all | slot slot-id | process process-id } pipe { on }
reset schedule-trace { all | slot slot-id | process process-id }
Parameters
Parameter | Description | Value |
---|---|---|
all |
Enables message tracing function on all boards. |
- |
slot slot-id |
Enables message tracing function on a specified board. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. |
process process-id |
Enables message tracing function of a specified process. |
The value is an integer ranging from 0 to 4294967295. |
thread thread-id |
Enables message tracing function of a specified thread. |
The value is an integer ranging from 0 to 18446744073709551615. |
all-thread |
Enables message tracing function of all threads. |
- |
intf-value |
Enables tracing on a specified major category of messages. |
The value is an integer ranging from 0 to 3. |
subintf-value |
Enables tracing on a specified sub-category of messages. |
The value is an integer ranging from 0 to 254. |
all-subintf |
Enables tracing on all sub-categories of messages. |
- |
all-intf |
Enables tracing on all major categories of messages. |
- |
pipe |
Enables tracing function of pipe messages. |
- |
interval interval-value |
Specifies the interval of message tracing function. |
The value is an integer ranging from 1 to 1800. |
record record-value |
Specifies the message schedule trace record num. |
The value is an integer ranging from 1 to 104857600. |
output-mode |
Indicates an output end of message tracing records. If this parameter is not specified, message tracing records are output to the memory and a file by default. |
- |
memory |
Outputs message tracing records to the memory. |
- |
file |
Outputs message tracing records to a file. |
- |
both |
Outputs message tracing records to the memory and a file. |
- |
Usage Guidelines
Usage Scenario
To delete message scheduling tracing records, run the reset schedule-trace command.
To locate a fault based on messages recorded by the system, run the schedule-trace on command enables the message tracing function. The message tracing function enables a system to automatically record information about messages sent and received, including message contents and message exchange orders. From the preceding information, you can clearly check the communication process which helps you locate a problem, such as a hung process.Precautions
This command is supported only on the admin VS.
Once the message tracing function is enabled, the system will frequently write files, which affects system performance. Therefore, enable this function only when locating a problem.Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] schedule-trace process 1000 3 all-subintf on
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] reset schedule-trace all
set component starvation threshold
Function
The set component starvation threshold command sets a threshold for the component scheduling timeout period of a specified process.
The undo set component starvation threshold command restores the initial threshold for the component scheduling timeout period of a specified process.
By default, there is no threshold for the component scheduling timeout period of a specified process.
Format
set component starvation threshold ThresholdVal process ProcessId
undo set component starvation threshold process ProcessId
Parameters
Parameter | Description | Value |
---|---|---|
process ProcessId |
Specifies a process ID. |
The value is an integer ranging from 1 to 4294967295. |
threshold ThresholdVal |
set the threshold of the starvation time. |
The value is an integer ranging from 0 to 6000. |
Usage Guidelines
Usage Scenario
If the components of a process are not scheduled for a long time, run the set component starvation threshold command to set a threshold for the component scheduling timeout period of the process. If the period in which the components are not scheduled exceeds the threshold, and the processing method in this situation is configured as process resetting, the threshold-crossing event triggers a process reset. The processing method can be queried through the IsResetProcess field in the display component starvation threshold command output.
Precautions
This command is supported only on the admin VS.
This command is potentially service-affecting. Setting a small timeout threshold may cause the process to be frequently reset.set cpu-usage process
Function
The set cpu-usage process command sets a process-specific CPU overload threshold and overload detection period.
The undo set cpu-usage process command deletes the set process-specific CPU overload threshold and overload detection period.
Format
set cpu-usage threshold thresholdValue interval interval-value process processid
undo set cpu-usage process processid
Parameters
Parameter | Description | Value |
---|---|---|
thresholdValue |
Specifies a percentage of the process-specific CPU overload threshold. |
The value is an integer ranging from 1 to 100. |
interval interval-value |
Specifies an overload detection period. |
The value is an integer ranging from 1 to 60, in seconds. |
process processid |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
To set a process-specific CPU overload threshold and an overload detection period based on service deployment conditions, run the set cpu-usage threshold process command.
Follow-up Procedure
Run the display cpu-monitor information process command to check process-specific CPU overload information.
Precautions
This command is supported only on the admin VS.
set message exhaust reset-delay-time
Function
The set message exhaust app reset-delay-time command sets a timeout threshold for the APP message memory exhaustion duration of a specified process.
The undo set message exhaust app reset-delay-time command restores the default timeout threshold for the APP message memory exhaustion duration of a specified process.
The set message exhaust manage reset-delay-time command sets a timeout threshold for the memory exhaustion duration in the management message partition of a specified process.
The undo set message exhaust manage reset-delay-time command restores the default timeout threshold for the memory exhaustion duration in the management message partition of a specified process.
By default, there is no timeout threshold for the APP message memory exhaustion duration of a specified process.
Format
set message exhaust { manage | app } reset-delay-time delay-time-interval process processId
undo set message exhaust { manage | app } reset-delay-time process processId
Parameters
Parameter | Description | Value |
---|---|---|
delay-time-interval |
Specifies the timeout threshold of the message memory exhaustion duration. |
The value is an integer ranging from 0 to 4294967295, in seconds. 0 indicates that the process reset function is not enabled when message memory is exhausted. |
process processId |
Specifies a process ID. |
The value is an integer ranging from 1 to 4294967295. |
Usage Guidelines
Usage Scenario
To set a timeout threshold for the message memory exhaustion duration of a specified process, run the set message exhaust app reset-delay-time command in the diagnostic view. If the message memory exhaustion duration exceeds the threshold, the process is reset.
To set a timeout threshold for the memory exhaustion duration in the management message partition of a specified process, run the set message exhaust manage reset-delay-time command in the diagnostic view. If the memory exhaustion duration exceeds the threshold, the process is reset.Precautions
This command is supported only on the admin VS.
This command is potentially service-affecting. Setting a small timeout threshold may cause the process to be frequently reset.Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] set message exhaust app reset-delay-time 100 process 1003
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] set message exhaust manage reset-delay-time 10 process 1003
set message send-receive-statistic
Function
The set message send-receive-statistic command sets whether to enable or disable the function to collect statistics about the packets sent and received by components.
Parameters
Parameter | Description | Value |
---|---|---|
on |
Enables the function to collect statistics about the packets sent and received by components. |
- |
off |
Disables the function to collect statistics about the packets sent and received by components. |
- |
set message statistic
Function
The set pipe statistic on command enables the function to collect statistics about the packets sent and received through a pipe.
The set pipe statistic off command disables the function to collect statistics about the packets sent and received through a pipe.
By default, collection of statistics about the packets sent and received through a pipe is disabled.
The set message statistic on command enables collection of statistics about messages sent by components on a device.
The set message statistic off command disables collection of statistics about messages sent by components on a device.
By default, collection of statistics about messages sent by components on a device is disabled.
The clear message statistic command deletes statistics about messages that are sent by components on a device.
Usage Guidelines
Usage Scenario
To delete or learn about statistics about messages sent by components on a device in a specified period of time, run the clear message statistic command.
To enable collection of statistics about messages sent by components on a device, run the set message statistic on command. The command output helps locate a fault. To view statistics about the packets sent and received through the pipe of a specified component or process, run the set pipe statistic on command first to enable collection of statistics about the packets sent and received through a pipe. The command output helps locate faults.Follow-up Procedure
After running the clear message statistic command to clear historical statistics about messages sent by components on a device, you can run the display system message statistic or display system message statistic component cid command to view statistics about messages sent by a specified component or all components on the device.
Run the display message pipe-statistic component <compid> command or display message pipe-statistic process <procid> command to check statistics about messages sent and received through the pipe of a specified component or process. set pipe statistic { on | off } affects only the values of CpuRunTime(us), MaxCpuRunTime(us), AvgCpuRunTime(us), and SchCount.Precautions
This command is supported only on the admin VS.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] set pipe statistic on
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] set pipe statistic on
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] set message statistic on
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] set message statistic on
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] clear message statistic
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] clear message statistic
set message-process statistic
Function
The set message-process statistic enable command enables collection of statistics about messages processed by components on a device.
The set message-process statistic disable command enables collection of statistics about messages processed by components on a device.
By default, collection of statistics about messages processed by components on a device is disabled.
Format
set message-process statistic { enable | disable }
set message-process statistic message-type { process process-id | component compcid } enable
set message-process statistic message-type { process process-id | component compcid } disable
Parameters
Parameter | Description | Value |
---|---|---|
message-type |
Indicates a message type. You can specify this parameter to enable collection of statistics about a specific type of message processed by components on a device. By default, this parameter is not specified. |
- |
process process-id |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
component compcid |
Specifies a component ID. You can specify this parameter to enable collection of statistics about a specific type of message processed by a specific component of a process. |
The value ranges from 0 to FFFFFFFF, in hexadecimal notation. |
Usage Guidelines
Usage Scenario
To enable collection of statistics about messages processed by components on a device, run the set message-process statistic enable command. The command output helps locate a fault.
Follow-up Procedure
Run the display message-process statistic [ message-type ] process process-id command to view statistics about messages processed by a specified process.
Precautions
After you enable collection of statistics about messages processed by components on a device, the CPU usage and memory usage may increase. Exercise caution when you perform this operation.
Before you enable collection of statistics about a specific type of message processed by components on a device, run the set message-process statistic enable command to enable collection of statistics about all messages. Otherwise, statistics collection based on message type fails. After collection of statistics about all messages processed by components is disabled, statistics collection based on message type is invalid but not disabled. If you enable collection of statistics about messages processed by components again and statistics collection based on message type has been enabled, statistics collection based on message type becomes valid.This command is supported only on the admin VS.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] set message-process statistic enable
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] set message-process statistic message-type process 1001 enable
timer statistics
Function
The debug timer statistics process on command enables timer statistics collection for a specified process.
The debug timer statistics process off command disables timer statistics collection for a specified process.
The reset timer statistics command clears all timer statistics.
Format
debug timer statistics process procid [ component compid ] { on | off }
reset timer statistics
Parameters
Parameter | Description | Value |
---|---|---|
component compid |
Specifies a component ID. |
The value is a hexadecimal integer ranging from 00000001 to fffffff. |
process procid |
Specifies a process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
In a system debugging scenario, to enable timer statistics collection for a specified process, run the debug timer statistics process command. The command output helps locate timer faults.
After running the debug timer statistics process command, you can run the display timer statistics process command to check timer statistics or the reset timer statistics command to clear timer statistics. To clear all timer statistics, run the reset timer statistics command. The command output facilitates problem locating. After you run the reset timer statistics command, the statistics about all timers are cleared.Precautions
This command is supported only by the admin VS.
trace next-start
Function
The trace next-start on command enables the message tracing function to take effect upon the next startup.
The trace next-start off command disables the message tracing function from taking effect upon the next startup.
By default, the message tracing function does not take effect upon the next startup.
trace trigger message enable
Function
The trace trigger message eanble command enables the common message tracing function based on specified conditions.
The trace trigger message disable command disables the common message tracing function.
By default, the common message tracing function is disabled.
Format
trace trigger message infect-trace trace-id traceidvalue { srccomp srcompid | destcomp dstcompid | srccomp srcompid destcomp dstcompid } [ trace-num tracenumvalue ] all [ dump-debug ] { send | recv } enable
trace trigger message infect-trace trace-id traceidvalue { srccomp srcompid | destcomp dstcompid | srccomp srcompid destcomp dstcompid } [ trace-num tracenumvalue ] intf intfid all [ dump-debug ] { send | recv } enable
trace trigger message infect-trace trace-id traceidvalue { srccomp srcompid | destcomp dstcompid | srccomp srcompid destcomp dstcompid } [ trace-num tracenumvalue ] intf intfid subintf subintfid all [ dump-debug ] { send | recv } enable
trace trigger message infect-trace trace-id traceidvalue { srccomp srcompid | destcomp dstcompid | srccomp srcompid destcomp dstcompid } [ trace-num tracenumvalue ] intf intfid subintf subintfid message-type msgtype [ dump-debug ] { send | recv } enable
trace trigger message infect-trace all disable
trace trigger message infect-trace trace-id traceidvalue disable
Parameters
Parameter | Description | Value |
---|---|---|
srccomp srcompid |
Specifies the ID of the message sending component. |
The value ranges from 0 to ffffffff, in hexadecimal notation. |
destcomp dstcompid |
Specifies the ID of the message receiving component. |
The value ranges from 0 to ffffffff, in hexadecimal notation. |
trace-num tracenumvalue |
Specifies the number of message tracing times. If this parameter is not specified, the default number of message tracing times is 20. |
The value is an integer ranging from 1 to 255. |
all |
Indicates all common message tracing tasks. |
- |
dump-debug |
Enable the debug function. |
- |
send |
Matches messages against the conditions at the transmit end and enables the message tracing function when the conditions are met. |
- |
recv |
Matches messages against the conditions at the receive end and enables the message tracing function when the conditions are met. |
- |
infect-trace |
Displays message infection tracing information. |
- |
trace-id traceidvalue |
Specifies the ID of a message tracing task. |
The value is an integer ranging from 0 to 63. |
intf intfid |
Specifies the ID of the module to which a message belongs. |
The value is an integer ranging from 0 to 4294967295. |
subintf subintfid |
Specifies the ID of the sub-module to which a message belongs. |
The value is an integer ranging from 0 to 4294967295. |
message-type msgtype |
Specifies a message type. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
To trace common messages based on specified conditions after you enable the end-to-end message tracing function, run the trace trigger message enable command to configure matching conditions for common message tracing. After the matching succeeds, the common messages that meet the conditions are traced.
Prerequisites
The end-to-end message tracing function has been enabled using the trace trigger { all | slot slot-id | process processid } on command.
Precautions
Only one tracing task can be started within 5 minutes. That is, the interval between two tracing tasks must be greater than 5 minutes. After 5 minutes, if there are multiple tracing tasks in the system, ensure that the value of trace-id is unique on the same NE.
trace trigger packet enable
Function
The trace trigger packet enable command enables the pipe message tracing function based on specified conditions.
The trace trigger packet disable command disables the pipe message tracing function.
By default, the pipe message tracing function is disabled.
Format
trace trigger packet infect-trace trace-id traceidvalue srcompid { send | recv } { offset1 offsetvalue1 mask1 value1 | offset1 offsetvalue1 mask1 value1 offset2 offsetvalue2 mask2 value2 | offset1 offsetvalue1 mask1 value1 offset2 offsetvalue2 mask2 value2 offset3 offsetvalue3 mask3 value3 | offset1 offsetvalue1 mask1 value1 offset2 offsetvalue2 mask2 value2 offset3 offsetvalue3 mask3 value3 offset4 offsetvalue4 mask4 value4 | offset1 offsetvalue1 mask1 value1 offset2 offsetvalue2 mask2 value2 offset3 offsetvalue3 mask3 value3 offset4 offsetvalue4 mask4 value4 offset5 offsetvalue5 mask5 value5 } [ trace-num tracenumvalue ] [ dump-debug ] enable
trace trigger packet infect-trace trace-id traceidvalue srcompid { send | recv } user-def usrdefstr [ trace-num tracenumvalue ] [ dump-debug ] enable
trace trigger packet infect-trace { all | trace-id traceidvalue } disable
Parameters
Parameter | Description | Value |
---|---|---|
srcompid |
Specifies the ID of the message sending component. |
The value ranges from 0 to ffffffff, in hexadecimal notation. |
send |
Matches messages against the conditions at the transmit end and enables the message tracing function when the conditions are met. |
- |
recv |
Matches messages against the conditions at the receive end and enables the message tracing function when the conditions are met. |
- |
offset1 offsetvalue1 mask1 value1 |
Specifies an offset value relative to the packet header. |
The value is an integer ranging from 0 to 4294967295. |
offset2 offsetvalue2 mask2 value2 |
Specifies an offset value relative to the packet header. |
The value is an integer ranging from 0 to 4294967295. |
offset3 offsetvalue3 mask3 value3 |
Specifies an offset value relative to the packet header. |
The value is an integer ranging from 0 to 4294967295. |
offset4 offsetvalue4 mask4 value4 |
Specifies an offset value relative to the packet header. |
The value is an integer ranging from 0 to 4294967295. |
offset5 offsetvalue5 mask5 value5 |
Specifies an offset value relative to the packet header. |
The value is an integer ranging from 0 to 4294967295. |
trace-num tracenumvalue |
Specifies the number of message tracing times. If this parameter is not specified, the default number of message tracing times is 20. |
The value is an integer ranging from 1 to 255. |
dump-debug |
The debug flag. |
- |
infect-trace |
Displays message infection tracing information. |
- |
trace-id traceidvalue |
Specifies the ID of a message tracing task. |
The value is an integer ranging from 0 to 63. |
user-def usrdefstr |
User-defined concept. |
The value is a string of 1 to 127 characters. |
all |
Indicates all pipe message tracing tasks. |
- |
Usage Guidelines
Usage Scenario
To trace pipe messages based on specified conditions after you enable the end-to-end message tracing function, run the trace trigger packet enable command to configure matching conditions for pipe message tracing. After the matching succeeds, the pipe messages that meet the conditions are traced.
Prerequisites
The end-to-end message tracing function has been enabled using the trace trigger { all | slot slot-id | process processid } on command.
Precautions
Only one tracing task can be started within 5 minutes. That is, the interval between two tracing tasks must be greater than 5 minutes. After 5 minutes, if there are multiple tracing tasks in the system, ensure that the value of trace-id is unique on the same NE.
Example
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] trace trigger packet infect-trace trace-id 2 80F104A1 send offset1 1 2 3 enable
<HUAWEI> system-view [~HUAWEI] diagnose [~HUAWEI-diagnose] trace trigger packet infect-trace trace-id 1 80F104A1 send user-def ipv4=proto;srcip enable
trace trigger timer enable
Function
The trace trigger timer enable command enables the timer message tracing function based on specified conditions.
The trace trigger timer disable command disables the timer message tracing function.
By default, the timer message tracing function is disabled.
Format
trace trigger timer infect-trace trace-id traceidvalue srccomp srcompid timer-type timeridvalue [ timer-para timerparavalue [ timer-paramask ] ] [ trace-num tracenumvalue ] [ dump-debug ] enable
trace trigger timer infect-trace { all | trace-id traceidvalue } disable
Parameters
Parameter | Description | Value |
---|---|---|
srccomp srcompid |
Specifies the ID of the message sending component. |
The value ranges from 0 to ffffffff, in hexadecimal notation. |
timer-type timeridvalue |
Specifies a timer type. |
The value ranges from 0 to ffffffff, in hexadecimal notation. |
timer-para timerparavalue |
Specifies a timer parameter. |
The value ranges from 0 to ffffffff, in hexadecimal notation. |
timer-paramask |
Specifies a timer parameter mask. |
The value ranges from 0 to ffffffff, in hexadecimal notation. |
trace-num tracenumvalue |
Specifies the number of message tracing times. If this parameter is not specified, the default number of message tracing times is 20. |
The value is an integer ranging from 1 to 255. |
dump-debug |
The debug flag. |
- |
infect-trace |
Displays message infection tracing information. |
- |
all |
Indicates all timer message tracing tasks. |
- |
trace-id traceidvalue |
Specifies the ID of a message tracing task. |
The value is an integer ranging from 0 to 63. |
Usage Guidelines
Usage Scenario
To trace timer messages based on specified conditions after you enable the end-to-end message tracing function, run the trace trigger timer enable command to configure matching conditions for timer message tracing. After the matching succeeds, the timer messages that meet the conditions are traced.
Prerequisites
The end-to-end message tracing function has been enabled using the trace trigger { all | slot slot-id | process processid } on command.
Precautions
Only one tracing task can be started within 5 minutes. That is, the interval between two tracing tasks must be greater than 5 minutes. After 5 minutes, if there are multiple tracing tasks in the system, ensure that the value of trace-id is unique on the same NE.
trace trigger { on | off }
Function
The trace trigger frame-output on command enables the function of outputting message tracing logs.
The trace trigger frame-output off command disables the function of outputting message tracing logs.
The trace trigger on command enables the end-to-end message tracing function.
The trace trigger off command disables the end-to-end message tracing function.
Format
trace trigger { all | slot slotid | process processid } { on | off }
trace trigger { all | slot slotid | process processid } frame-output { on | off }
Parameters
Parameter | Description | Value |
---|---|---|
all |
Indicates all message tracing tasks. |
- |
slot slotid |
Specifies a slot ID. |
- |
process processid |
Process ID. |
The value is an integer ranging from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
By default, the function of outputting message tracing logs is enabled. This may cause a large number of logs to be generated, affecting device performance. To disable the function of outputting message tracing logs, run the trace trigger { all | slot <slotid> | process <processid> } frame-output off command.
To trace timers, pipes, or common messages, run the trace trigger { all | slot <slotid> | process <processid> } on command to enable the end-to-end message tracing function. After the message tracing function is enabled, the message sender or receiver matches a message based on specified message tracing matching conditions. If the matching is successful, the message is traced.Prerequisites
The trace trigger { all | slot <slotid> | process <processid> } on command has been executed to enable the end-to-end message tracing function.
Follow-up Procedure
Run the trace trigger timer, trace trigger packet, or trace trigger message command to configure matching conditions for the tracing of common, timer, or pipe messages.
- clear memory tail-protection logfiles
- clear system cpu statistics
- debug comp-service component
- debug exception-delay-reset
- debug log filter
- debug log output
- debug memory tail-protection enable
- debug message receive-trace
- debug message trace
- debug system memory handle-type switch-to-block
- debug system memory leak
- debug system memory leak handle
- debug system private-log
- display comp-service component
- display component starvation threshold
- display cpu-monitor information process
- display cpu-monitor switch-states
- display cpu-usage history (Diagnostic view)
- display cpu-usage process
- display cpu-usage
- display exception
- display error-information
- display exception-delay-reset switch status
- display fd
- display inspect infrastructure
- display inspect process
- display log output
- display memory (Diagnostic view)
- display memory cid
- display memory cid mid
- display memory mid
- display memory tail-protection information
- display memory(Diagnostic view)
- display memory-monitor switch-states
- display memory-usage all
- display message exhaust reset-delay-time
- display message pipe-statistic
- display message receive-trace rule
- display message send-receive-statistic
- display message trace srccomp
- display message
- display message-process statistic process
- display message-usage component
- display message-usage
- display os-information slot
- display pipe-memory time process
- display assert
- display reset-reason
- display schedule-trace
- display semaphore
- display starvation
- display system cam-subscription
- display system component
- display system cpu statistics
- display system deadloop configuration
- display system debug configuration flow-control
- display system debug diagnostic-log
- display system debug queue info
- display system debug seccomp
- display system error
- display system memory handle-alloc process
- display system memory leak information
- display system memory process simple-to-block status
- display system memory statistics
- display system memory statistics(Diagnostic view)
- display system memory verbose process
- display system memory verbose(Diagnostic view)
- display system message alloc process
- display system message alloc-failed
- display system message statistic
- display system os-memory process
- display system os-memory slot
- display system os-process
- display system thread
- display thread callstack
- display thread schedule
- display timer slot
- display timer statistics process
- reset message pipe-statistic
- reset message send-receive-statistic
- reset message-process statistic
- reset record
- reset assert record
- schedule-trace
- set component starvation threshold
- set cpu-usage process
- set message exhaust reset-delay-time
- set message send-receive-statistic
- set message statistic
- set message-process statistic
- timer statistics
- trace next-start
- trace trigger message enable
- trace trigger packet enable
- trace trigger timer enable
- trace trigger { on | off }