No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

S12700 V200R013C00 Command Reference

This document describes all the configuration commands of the device, including the command function, syntax, parameters, views, default level, usage guidelines, examples, and related commands.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
OIDS Configuration Commands

OIDS Configuration Commands

Command Support

Commands provided in this section and all the parameters in the commands are supported by all switch models by default, unless otherwise specified. For details, see specific commands.

collect oids database file to system-master

Function

The collect oids database file to system-master command saves OIDS database files to the active MPU.

Format

collect oids database file to system-master

Parameters

None

Views

System view

Default Level

3: Management level

Usage Guidelines

Usage Scenario

After the OIDS function is enabled, the switch saves the collected data and fault diagnosis results to database files on the active MPU. When you view OIDS data within a period of time, the switch reads and displays only the OIDS database files on the active MPU. For a dual-MPU or cluster switch, if an active/standby MPU switchover has been performed before you view OIDS data within a certain period of time, the OIDS database files used before the switchover are stored on the current standby MPU. In this case, you need to save the OIDS database files on the standby MPU to the active MPU, and then view OIDS data in the files. Otherwise, you may view incomplete OIDS data.

After the collect oids database file to system-master command is executed, the device deletes the previously collected OIDS database files saved on the active MPU, and then saves OIDS database files on all standby MPUs to the active MPU. If standby MPUs are not installed or registered, the device deletes only the previously collected OIDS database files saved on the active MPU.

Precautions

The contents of OIDS database files cannot be manually modified.

Before running the collect oids database file to system-master command, ensure that the active MPU has sufficient storage space. To check the available storage space on the device, run the dir command. If the storage space is insufficient, run the delete /unreserved command to delete unnecessary files.

Example

# Save OIDS database files to the active MPU.

<HUAWEI> system-view
[HUAWEI] collect oids database file to system-master
Warning: After the command is run, the files in the directory flash:/oids/gather will be deleted. Continue? [Y/N]:y

display oids current-event

Function

The display oids current-event command displays information about OIDS events generated after the device starts.

Format

display oids current-event [ slot slot-id ]

Parameters

Parameter

Description

Value

slot slot-id

Specifies a slot ID.

The value depends on the device configuration.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

After the OIDS monitoring function is enabled, the device periodically collects and saves diagnosis object attribute data to database files based on diagnosis types, diagnosis objects, and diagnosis object attributes. The OIDS module sends key performance indicator (KPI) data to service modules based on the collected diagnosis object attribute data. Service modules compare the KPI data with the defined threshold range to determine whether to generate an event. If a service module generates an event, it sends the event information to the OIDS module, which then records the information to database files.For example, if the collected ARP_Usage data exceeds 85%, the OIDS module records the ARP Usage High event. If the collected ARP_Usage data falls below 75%, the OIDS module records the ARP Usage Normal event. For details about the OIDS events supported by the device, see Appendix 2: OIDS Events Supported by the Switch.

To check information about OIDS events generated after the device starts, run the display oids current-event command. If you just need to check the OIDS events generated within a certain period or OIDS events of the specified type, run the display oids history-event command. If you need to check the OIDS events registered on the device, run the display oids register-event command.

Example

# Display information about OIDS events generated in slot 5 after the device starts.

<HUAWEI> display oids current-event slot 5
Slot: 5
------------------------------------------------
Event name    : Temperature High
Object name   : Temp_Sensor_1
Attribute name: Temperature
State value   : 34C
Begin time    : 2018-04-23 16:08:59
End time      : 2018-04-23 16:08:59
------------------------------------------------

Info: At most 100 events that have been processed since each board starts can be displayed for this board. All events that have not been processed will also be displayed.
Table 3-107  Description of the display oids current-event command output

Item

Description

Slot

Slot ID.

Event name

Event name.

Object name

Name of a diagnosis object.

Attribute name

Name of a diagnosis object attribute.

State value

Diagnosis object attribute value when an event occurs.

Begin time

Event start time.

End time

Event end time.

display oids filter

Function

The display oids filter command displays information about a log or trap filter.

Format

display oids filter

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

The devices that support association between OIDS and OPS can filter OIDS events by using log or trap filters. Three log events and three trap events are preset on the device to improve the efficiency of filtering logs or traps. A maximum of three log filters and three trap filters can be configured on the same device. Each filter can be configured with the conditions for filtering logs or traps using the oids filter command. When the OIDS filter detects the logs or traps that meet the filter conditions, an OIDS event is generated. To check which logs and traps are filtered and how many times events are triggered, run the display oids filter command.

Example

# Display information about a log or trap filter.

<HUAWEI> display oids filter
Type  Module/Alias                                              TriggerTimes     
-------------------------------------------------------------------------------- 
LOG   ifnet/link_state                                             3             
TRAP  basetrap/entityregsuccess                                    1             
Table 3-108  Description of the display oids filter command output

Item

Description

Type

Type.

Module/Alias

Module name/Alias name.

TriggerTimes

Number of times an event is triggered.

display oids history-event

Function

The display oids history-event command displays information about OIDS events generated within a certain period.

Format

display oids history-event [ type type-name [ { object-index object-index | object-name object-name } [ { attribute-index attribute-index | attribute-name attribute-name } ] ] ] [ slot slot-id ] [ { before | after } date-time time date ] [ period { 1h | 24h } ]

Parameters

Parameter

Description

Value

type type-name

Specifies a diagnosis type name.

The value is of the enumerated type:
  • ACL: ACL diagnosis type

  • ARP: ARP diagnosis type

  • CPU: CPU diagnosis type

  • CPU-CHAN: CPU channel diagnosis type

  • DHCPv4: DHCPv4 diagnosis type

  • DHCPv6: DHCPv6 diagnosis type

  • FIBv4: IPv4 forwarding information table diagnosis type

  • FIBv6: IPv6 forwarding information table diagnosis type

  • Flash: Flash diagnosis type

  • L3table: Layer 3 hardware table diagnosis type

  • LOG: LOG diagnosis type

  • MAC: MAC diagnosis type

  • MCAST: multicast diagnosis type

  • Memory: memory diagnosis type

  • MPLS: MPLS diagnosis type

  • NAC: NAC diagnosis type

  • ND: IPv6 neighbor diagnosis type

  • NHP: next hop diagnosis type

  • Port: port diagnosis type

  • TEMP: temperature diagnosis type

  • TRAP: TRAP diagnosis type

object-index object-index

Specifies a diagnosis object index.

To check the diagnosis objects and diagnosis object attributes supported by the device, run the display oids register-status command or see Appendix 1: OIDS Monitoring and Diagnosis Items Supported by the Switch.

object-name object-name

Specifies a diagnosis object name.

attribute-index attribute-index

Specifies a diagnosis object attribute index.

attribute-name attribute-name

Specifies a diagnosis object attribute name.

slot slot-id

Specifies a slot ID.

The value depends on the device configuration.

before

Displays OIDS events generated before the specified time.

-

after

Displays OIDS events generated after the specified time.

-

date-time time date

Specifies a time value.

time is in HH:MM:SS format and ranges from 00:00:00 to 23:59:59.

date is in YYYY-MM-DD format and ranges from 2000-1-1 to 2099-12-31.

period { 1h | 24h }

Specifies the period during which OIDS events need to be displayed.

If period is not specified, OIDS events generated within 1 hour before or after the current time are displayed by default.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

After the OIDS monitoring function is enabled, the device periodically collects and saves diagnosis object attribute data to database files based on diagnosis types, diagnosis objects, and diagnosis object attributes. The OIDS module sends key performance indicator (KPI) data to service modules based on the collected diagnosis object attribute data. Service modules compare the KPI data with the defined threshold range to determine whether to generate an event. If a service module generates an event, it sends the event information to the OIDS module, which then records the information to database files.For example, if the collected ARP_Usage data exceeds 85%, the OIDS module records the ARP Usage High event. If the collected ARP_Usage data falls below 75%, the OIDS module records the ARP Usage Normal event. For details about the OIDS events supported by the device, see Appendix 2: OIDS Events Supported by the Switch.

You can run the display oids history-event command to check the OIDS events generated within a certain period or OIDS events of a specified type. If you need to check OIDS events generated after the device starts run the display oids current-event command. If you need to check OIDS events registered on the device, run the display oids register-event command.

Precautions

If no time parameter is specified during the execution of the display oids history-event command, OIDS events generated within 1 hour before the current time are displayed by default.

For a dual-MPU or cluster switch, run the collect oids database file to system-master command to save OIDS database files on the standby MPU to the active MPU before querying OIDS monitoring and diagnosis results within a certain period.

The contents of OIDS database files cannot be manually modified.

Example

# Display OIDS events generated within 1 hour before 17:00:00 on April 20, 2018.

<HUAWEI> display oids history-event before date-time 17:00:00 2018-04-20 period 1h
----------------------------------------------------------------------
Slot       : 4
ObjectName : Temp_Sensor_1
AttrName   : Temperature
Event      : Temperature High
Time       : 2018-04-20 16:35:11
State value: 33C
----------------------------------------------------------------------
Table 3-109  Description of the display oids history-event command output

Item

Description

Slot

Slot ID.

ObjectName

Name of a diagnosis object.

AttrName

Name of a diagnosis object attribute.

Event

Event name.

Time

Time when an event occurs.

State value

Diagnosis object attribute value when an event occurs.

display oids history-result

Function

The display oids history-result command displays OIDS diagnosis results within a certain period.

Format

display oids history-result [ type type-name [ { object-index object-index | object-name object-name } [ { attribute-index attribute-index | attribute-name attribute-name } ] ] ] [ slot slot-id ] [ { before | after } date-time time date ] [ period { 1h | 24h } ]

Parameters

Parameter

Description

Value

type type-name

Specifies a diagnosis type name.

The value is of the enumerated type:
  • ACL: ACL diagnosis type

  • ARP: ARP diagnosis type

  • CPU: CPU diagnosis type

  • CPU-CHAN: CPU channel diagnosis type

  • DHCPv4: DHCPv4 diagnosis type

  • DHCPv6: DHCPv6 diagnosis type

  • FIBv4: IPv4 forwarding information table diagnosis type

  • FIBv6: IPv6 forwarding information table diagnosis type

  • Flash: Flash diagnosis type

  • L3table: Layer 3 hardware table diagnosis type

  • LOG: LOG diagnosis type

  • MAC: MAC diagnosis type

  • MCAST: multicast diagnosis type

  • Memory: memory diagnosis type

  • MPLS: MPLS diagnosis type

  • NAC: NAC diagnosis type

  • ND: IPv6 neighbor diagnosis type

  • NHP: next hop diagnosis type

  • Port: port diagnosis type

  • TEMP: temperature diagnosis type

  • TRAP: TRAP diagnosis type

object-index object-index

Specifies a diagnosis object index.

To check the diagnosis objects and diagnosis object attributes supported by the device, run the display oids register-status command or see Appendix 1: OIDS Monitoring and Diagnosis Items Supported by the Switch.

object-name object-name

Specifies a diagnosis object name.

attribute-index attribute-index

Specifies a diagnosis object attribute index.

attribute-name attribute-name

Specifies a diagnosis object attribute name.

slot slot-id

Specifies a slot ID.

If slot-id specifies a slot ID, the display oids history-result command displays OIDS diagnosis results on the device in standalone state, regardless of whether the device is in standalone or stack state. If slot-id specifies a stack ID/slot ID, this command displays OIDS diagnosis results on the device in stack state.

before

Displays OIDS diagnosis results generated before the specified time.

-

after

Displays OIDS diagnosis results generated after the specified time.

-

date-time time date

Specifies a time value.

time is in HH:MM:SS format and ranges from 00:00:00 to 23:59:59.

date is in YYYY-MM-DD format and ranges from 2000-1-1 to 2099-12-31.

period { 1h | 24h }

Specifies the period during which OIDS diagnosis results need to be displayed.

If period is not specified, OIDS diagnosis results generated within 1 hour before or after the current time are displayed by default.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

After the OIDS diagnosis function is enabled, the switch records an OIDS event when finding that the KPI data exceeds the defined threshold, and the OIDS module determines whether to trigger OIDS diagnosis. If OIDS diagnosis is triggered, the OIDS module specifies a service module to perform diagnosis. The OIDS module records the diagnosis result received from the service module in the database. You can run the display oids history-result command to check OIDS diagnosis results generated within a certain period or OIDS diagnosis results of a specified type for fast fault location. This configuration can improve troubleshooting efficiency.

Precautions

If no time parameter is specified during the execution of the display oids history-result command, OIDS diagnosis results generated within 1 hour before the current time are displayed by default.

For a dual-MPU or cluster switch, run the collect oids database file to system-master command to save OIDS database files on the standby MPU to the active MPU before querying OIDS monitoring and diagnosis results within a certain period.

The contents of OIDS database files cannot be manually modified.

Example

# Display OIDS diagnosis results generated within 1 hour before 17:00:00 on April 20, 2018.

<HUAWEI> display oids history-result before date-time 17:00:00 2018-4-20 period 1h
----------------------------------------------------------------------
Slot               : 4
ObjectName         : CPCAR
AttrName           : CPCAR_Drop_Pkt
Event              : CPCAR Drop Pkt
Event time         : 2019-02-26 14:15:24
Diagnose begin time: 2019-02-26 14:15:24
Diagnose end time  : 2019-02-26 14:15:24
Record             : Packets are discarded for CPCAR limit, the top protocols are:Protocol = icmp, ExceededPacketCount = 16061939.
State value        : 16061939
Record from        : oids.py                     
Fault flag         : True
----------------------------------------------------------------------
Table 3-110  Description of the display oids history-result command output

Item

Description

Slot

Slot ID.

ObjectName

Name of a diagnosis object.

AttrName

Name of a diagnosis object attribute.

Event

Event name.

Event time

Time when an event occurs.

Diagnose begin time

OIDS diagnosis start time.

Diagnose end time

OIDS diagnosis end time.

Diagnose result

OIDS diagnosis result.

  • Normal: The device is working properly.
  • Fault: The device is not working properly.

Record

Diagnosis results.

State value

Diagnosis object attribute value.

Record from

Record source:

  • OIDS: The record is from OIDS.
  • Others: The record is from an OPS script, such as oids.py.

display oids monitor current-fault

Function

The display oids monitor current-fault command displays OIDS monitoring information that triggers abnormal events at the current time.

NOTE:

When the OIDS monitoring function is disabled, the display oids monitor current-fault command displays the OIDS monitoring information that triggers abnormal events and is recorded before the OIDS monitoring function is disabled.

Format

display oids monitor current-fault [ type type-name [ { object-index object-index | object-name object-name } [ { attribute-index attribute-index | attribute-name attribute-name } ] ] ] [ slot slot-id ]

Parameters

Parameter

Description

Value

type type-name

Specifies a diagnosis type name.

The value is of the enumerated type:
  • ACL: ACL diagnosis type

  • ARP: ARP diagnosis type

  • CPU: CPU diagnosis type

  • CPU-CHAN: CPU channel diagnosis type

  • DHCPv4: DHCPv4 diagnosis type

  • DHCPv6: DHCPv6 diagnosis type

  • FIBv4: IPv4 forwarding information table diagnosis type

  • FIBv6: IPv6 forwarding information table diagnosis type

  • Flash: Flash diagnosis type

  • L3table: Layer 3 hardware table diagnosis type

  • LOG: LOG diagnosis type

  • MAC: MAC diagnosis type

  • MCAST: multicast diagnosis type

  • Memory: memory diagnosis type

  • MPLS: MPLS diagnosis type

  • NAC: NAC diagnosis type

  • ND: IPv6 neighbor diagnosis type

  • NHP: next hop diagnosis type

  • Port: port diagnosis type

  • TEMP: temperature diagnosis type

  • TRAP: TRAP diagnosis type

object-index object-index Specifies a diagnosis object index.

To check the diagnosis objects and diagnosis object attributes supported by the device, run the display oids register-status command or see Appendix 1: OIDS Monitoring and Diagnosis Items Supported by the Switch.

object-name object-name Specifies a diagnosis object name.
attribute-index attribute-index Specifies a diagnosis object attribute index.
attribute-name attribute-name Specifies a diagnosis object attribute name.

slot slot-id

Specifies a slot ID.

The value depends on the device configuration.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

After the OIDS monitoring function is enabled, the device periodically collects and saves diagnosis object attribute data to database files based on diagnosis types, diagnosis objects, and diagnosis object attributes. The OIDS module sends key performance indicator (KPI) data to service modules based on the collected diagnosis object attribute data. Service modules compare the KPI data with the defined threshold range to determine whether to generate an event. If a service module generates an event, it sends the event information to the OIDS module. The OIDS module records the event in database files and sets diagnosis object attributes of abnormal events to Abnormal.

You can run the display oids monitor current-fault command to check diagnosis object attributes in Abnormal state to locate faulty services. If you need to check detailed OIDS monitoring information recorded on the device, run the display oids monitor status command.

Example

# Display OIDS monitoring information that triggers abnormal events at the current time.

<HUAWEI> display oids monitor current-fault
Slot Type-name  Object-name         Attribute-name      Status
-----------------------------------------------------------------
5    Port       GE5/0/12            Input_Usage         Abnormal
5    Port       GE5/0/12            CRC_Number          Abnormal
Table 3-111  Description of the display oids monitor current-fault command output

Item

Description

Slot

Slot ID.

Type-name

Name of a diagnosis type.

Object-name

Name of a diagnosis object.

Attribute-name

Name of a diagnosis object attribute.

Status

Faulty state.

display oids monitor kpi

Function

The display oids monitor kpi command displays KPI information generated within a certain period.

Format

display oids monitor kpi { data | graph } type type-name { object-index object-index | object-name object-name } { attribute-index attribute-index | attribute-name attribute-name } slot slot-id [ period { 60min | 24h | 72h } { before | after } date-time time date ]

Parameters

Parameter

Description

Value

data

Displays KPI information in data format.

-

graph

Displays KPI information in graph format.

-

type type-name

Specifies a diagnosis type name.

The value is of the enumerated type:
  • ACL: ACL diagnosis type

  • ARP: ARP diagnosis type

  • CPU: CPU diagnosis type

  • CPU-CHAN: CPU channel diagnosis type

  • DHCPv4: DHCPv4 diagnosis type

  • DHCPv6: DHCPv6 diagnosis type

  • FIBv4: IPv4 forwarding information table diagnosis type

  • FIBv6: IPv6 forwarding information table diagnosis type

  • Flash: Flash diagnosis type

  • L3table: Layer 3 hardware table diagnosis type

  • LOG: LOG diagnosis type

  • MAC: MAC diagnosis type

  • MCAST: multicast diagnosis type

  • Memory: memory diagnosis type

  • MPLS: MPLS diagnosis type

  • NAC: NAC diagnosis type

  • ND: IPv6 neighbor diagnosis type

  • NHP: next hop diagnosis type

  • Port: port diagnosis type

  • TEMP: temperature diagnosis type

  • TRAP: TRAP diagnosis type

object-index object-index Specifies a diagnosis object index.

To check the diagnosis objects and diagnosis object attributes supported by the device, run the display oids register-status command or see Appendix 1: OIDS Monitoring and Diagnosis Items Supported by the Switch.

object-name object-name Specifies a diagnosis object name.
attribute-index attribute-index Specifies a diagnosis object attribute index.
attribute-name attribute-name Specifies a diagnosis object attribute name.

slot slot-id

Specifies a slot ID.

The value depends on the device configuration.

period { 60min | 24h | 72h }

Specifies the period during which KPI information is displayed.

If period is not specified, KPI monitoring information generated within 1 hour before the current time is displayed by default.

before

Displays KPI information generated before the specified time.

-

after

Displays KPI information generated after the specified time.

-

date-time time date

Specifies a time value.

time is in HH:MM:SS format and ranges from 00:00:00 to 23:59:59.

date is in YYYY-MM-DD format and ranges from 2000-1-1 to 2099-12-31.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

After the OIDS monitoring function is enabled, the device periodically collects and saves diagnosis object attribute data to database files based on diagnosis types, diagnosis objects, and diagnosis object attributes. The OIDS module sends key performance indicator (KPI) data to service modules based on the collected diagnosis object attribute data. Service modules compare the KPI data with the defined threshold range to determine whether to generate an event. If a service module generates an event, it sends the event information to the OIDS module. The OIDS module records the event in database files and sets diagnosis object attributes of abnormal events to Abnormal.

KPIs relate to the running status of the switch at any given time. Currently, all diagnosis object attributes on the switch are KPIs.

You can run the display oids monitor kpi command to query KPI information recorded on the switch in data or graph format to quickly identify and rectify faults.

Precautions

For a dual-MPU or cluster switch, run the collect oids database file to system-master command to save OIDS database files on the standby MPU to the active MPU before querying OIDS monitoring and diagnosis results within a certain period.

The contents of OIDS database files cannot be manually modified.

Example

# Display KPI information generated 1 hour before 09:54:22 on April 23, 2018 in slot 1 based on the diagnosis type Temp, diagnosis object index 1, and diagnosis object attribute 0 in data format.

<HUAWEI> display oids monitor kpi data type temp object-index 1 attribute-index 0 slot 1 period 60min before date-time 09:54:22 2018-04-23

Object name: Temp_Sensor_1
Attribute name: Temperature
Slot: 1

----------------------------------------------------------------------------------------------
Time                                    Average                Maximum                Status
----------------------------------------------------------------------------------------------
2018-04-23 08:54:22-2018-04-23 08:55:22 48C                    48C                    normal
2018-04-23 08:55:22-2018-04-23 08:56:22 48C                    48C                    normal
2018-04-23 08:56:22-2018-04-23 08:57:22 48C                    48C                    normal
2018-04-23 08:57:22-2018-04-23 08:58:22 48C                    48C                    normal
2018-04-23 08:58:22-2018-04-23 08:59:22 48C                    48C                    normal
2018-04-23 08:59:22-2018-04-23 09:00:22 48C                    48C                    normal
2018-04-23 09:00:22-2018-04-23 09:01:22 48C                    48C                    normal
2018-04-23 09:01:22-2018-04-23 09:02:22 48C                    48C                    normal
2018-04-23 09:02:22-2018-04-23 09:03:22 48C                    48C                    normal
2018-04-23 09:03:22-2018-04-23 09:04:22 48C                    48C                    normal
2018-04-23 09:04:22-2018-04-23 09:05:22 48C                    48C                    normal
2018-04-23 09:05:22-2018-04-23 09:06:22 48C                    48C                    normal
2018-04-23 09:06:22-2018-04-23 09:07:22 48C                    48C                    normal
2018-04-23 09:07:22-2018-04-23 09:08:22 48C                    48C                    normal
2018-04-23 09:08:22-2018-04-23 09:09:22 48C                    48C                    normal
2018-04-23 09:09:22-2018-04-23 09:10:22 48C                    48C                    normal
2018-04-23 09:10:22-2018-04-23 09:11:22 48C                    48C                    normal
2018-04-23 09:11:22-2018-04-23 09:12:22 48C                    48C                    normal
2018-04-23 09:12:22-2018-04-23 09:13:22 48C                    48C                    normal
2018-04-23 09:13:22-2018-04-23 09:14:22 48C                    48C                    normal
2018-04-23 09:14:22-2018-04-23 09:15:22 48C                    48C                    normal
2018-04-23 09:15:22-2018-04-23 09:16:22 48C                    48C                    normal
2018-04-23 09:16:22-2018-04-23 09:17:22 48C                    48C                    normal
2018-04-23 09:17:22-2018-04-23 09:18:22 48C                    48C                    normal
2018-04-23 09:18:22-2018-04-23 09:19:22 48C                    48C                    normal
2018-04-23 09:19:22-2018-04-23 09:20:22 48C                    48C                    normal
2018-04-23 09:20:22-2018-04-23 09:21:22 48C                    48C                    normal
2018-04-23 09:21:22-2018-04-23 09:22:22 48C                    48C                    normal
2018-04-23 09:22:22-2018-04-23 09:23:22 48C                    48C                    normal
2018-04-23 09:23:22-2018-04-23 09:24:22 48C                    48C                    normal
2018-04-23 09:24:22-2018-04-23 09:25:22 -                      -                      NA
2018-04-23 09:25:22-2018-04-23 09:26:22 -                      -                      NA
2018-04-23 09:26:22-2018-04-23 09:27:22 -                      -                      NA
2018-04-23 09:27:22-2018-04-23 09:28:22 -                      -                      NA
2018-04-23 09:28:22-2018-04-23 09:29:22 -                      -                      NA
2018-04-23 09:29:22-2018-04-23 09:30:22 -                      -                      NA
2018-04-23 09:30:22-2018-04-23 09:31:22 -                      -                      NA
2018-04-23 09:31:22-2018-04-23 09:32:22 -                      -                      NA
2018-04-23 09:32:22-2018-04-23 09:33:22 -                      -                      NA
2018-04-23 09:33:22-2018-04-23 09:34:22 -                      -                      NA
2018-04-23 09:34:22-2018-04-23 09:35:22 -                      -                      NA
2018-04-23 09:35:22-2018-04-23 09:36:22 -                      -                      NA
2018-04-23 09:36:22-2018-04-23 09:37:22 -                      -                      NA
2018-04-23 09:37:22-2018-04-23 09:38:22 -                      -                      NA
2018-04-23 09:38:22-2018-04-23 09:39:22 -                      -                      NA
2018-04-23 09:39:22-2018-04-23 09:40:22 50C                    50C                    normal
2018-04-23 09:40:22-2018-04-23 09:41:22 50C                    50C                    normal
2018-04-23 09:41:22-2018-04-23 09:42:22 50C                    50C                    normal
2018-04-23 09:42:22-2018-04-23 09:43:22 50C                    50C                    normal
2018-04-23 09:43:22-2018-04-23 09:44:22 50C                    50C                    normal
2018-04-23 09:44:22-2018-04-23 09:45:22 46C                    46C                    abnormal
2018-04-23 09:45:22-2018-04-23 09:46:22 46C                    46C                    abnormal
2018-04-23 09:46:22-2018-04-23 09:47:22 46C                    46C                    abnormal
2018-04-23 09:47:22-2018-04-23 09:48:22 46C                    46C                    abnormal
2018-04-23 09:48:22-2018-04-23 09:49:22 46C                    46C                    abnormal
2018-04-23 09:49:22-2018-04-23 09:50:22 42C                    42C                    abnormal
2018-04-23 09:50:22-2018-04-23 09:51:22 42C                    42C                    abnormal
2018-04-23 09:51:22-2018-04-23 09:52:22 42C                    42C                    abnormal
2018-04-23 09:52:22-2018-04-23 09:53:22 42C                    42C                    abnormal
2018-04-23 09:53:22-2018-04-23 09:54:22 42C                    42C                    abnormal
----------------------------------------------------------------------------------------------

Abnormal Information:
----------------------------------------------
Time                 Abnormal Value
----------------------------------------------
2018-04-23 09:45:00  46
2018-04-23 09:50:00  42
Table 3-112  Description of the display oids monitor kpi data command output

Item

Description

Object name

Name of a diagnosis object.

Attribute name

Name of a diagnosis object attribute.

Slot

Slot ID.

Time (appears the first time)

Time range.

  • If period is set to 60min, 60min is divided into 60 consecutive time ranges at the interval of 1 minute.
  • If period is set to 24h, 24h is divided into 48 consecutive time ranges at the interval of 0.5 hour.
  • If period is set to 72h, 72h is divided into 72 consecutive time ranges at the interval of 1 hour.

Average

Average value of diagnosis object attributes within a time range. If this field displays -, the database is empty within this time range.

Maximum

Maximum value of diagnosis object attributes within a time range. If this field displays -, the database is empty within this time range.

Status

Status of a diagnosis object attribute:
  • normal: The diagnosis object attribute is normal.
  • abnormal: The diagnosis object attribute is abnormal.
  • NA: The status is empty, and no data is recorded in the database.

Abnormal Information

Information about the diagnosis object attribute in abnormal state.

Time (appears the second time)

Record time.

Abnormal Value

Data of a diagnosis object attribute.

# Display KPI information generated 24 hours before 17:40:00 on March 30, 2018 in slot 3 based on the diagnosis type Port, diagnosis object index 22, and diagnosis object attribute 0 in graph format.

<HUAWEI> display oids monitor kpi graph type port object-index 22 attribute-index 0 slot 3 period 24h before date-time 17:40:00 2018-03-30

Object name: GE3/1/18
Attribute name: Input_Usage
Slot: 3

                                                 111
TOP: 000000000000000000000000000000000000000000000000
     000000000000000000000000000000000000000000000000
ALM:                                             AAA
100%|                                            ***
 90%|                                            ***
 80%|                                            ***
 70%|                                            ***
 60%|                                            ***
 50%|                                            *#*
 40%|                                            ##*
 30%|                                            ###
 20%|                                            ###
 10%|                                            ###
     +----+----+----+----+----+----+----+----+----+---->
     0    5    10   15   20   25   30   35   40   45
                Per Half Hour (24 hour)
        * = Maximum   # = Average  A = Abnormal

Abnormal Information:
----------------------------------------------
Time                 Abnormal Value
----------------------------------------------
2018-03-30 15:45:00 85%
2018-03-30 15:50:00 100%
2018-03-30 15:55:00 100%
2018-03-30 16:45:00 100%
2018-03-30 16:50:00 100%
2018-03-30 16:55:00 94%
2018-03-30 16:00:00 100%
2018-03-30 16:05:00 100%
2018-03-30 16:10:00 100%
2018-03-30 16:15:00 100%
2018-03-30 16:20:00 100%
2018-03-30 16:25:00 100%
2018-03-30 16:30:00 100%
2018-03-30 16:35:00 100%
2018-03-30 16:40:00 100%

Figure 3-1 explains some fields in the preceding command output.

Figure 3-1  Fields in the preceding command output

# Display KPI information generated within 1 hour before the current time in slot 6 based on the diagnosis type MAC, diagnosis object index 0, and diagnosis object attribute 1 in graph format.

<HUAWEI> display oids monitor kpi graph type mac object-index 0 attribute-index 1 slot 6 

Object name: MAC
Attribute name: MAC_Number
Slot: 6

                            11111
TOP: 777888888888877777788880000077777888888888877777888888888880
     555777777777755555577770000055555777777777755555777777777770
ALM:
100%|                       #####
 90%|                       #####
 80%|   ##########      #########     ##########     ###########
 70%|###########################################################
 60%|###########################################################
 50%|###########################################################
 40%|###########################################################
 30%|###########################################################
 20%|###########################################################
 10%|###########################################################
     +----+----+----+----+----+----+----+----+----+----+----+----+->
     0    5    10   15   20   25   30   35   40   45   50   55   60
                Per Minute (60 minutes * 8)
        * = Maximum   # = Average  A = Abnormal

Abnormal Information:
----------------------------------------------
Time                 Abnormal Value
----------------------------------------------
Table 3-113  Description of the display oids monitor kpi graph command output

Item

Description

Object name

Name of a diagnosis object.

Attribute name

Name of a diagnosis object attribute.

Slot

Slot ID.

TOP

Maximum value of the diagnosis object attribute in each time step of the horizontal axis. The value is in percentage format (data needs to be viewed from top to bottom).

If the maximum value of the diagnosis object attribute registered on the device is smaller than or equal to 100:
  • When Per Minute (60 minutes) is displayed in the horizontal axis, this field displays the maximum value in every minute.
  • When Per Half Hour (24 hour) is displayed in the horizontal axis, this field displays the maximum value in every 0.5 hour.
  • When Per Half Hour (72 hour) is displayed in the horizontal axis, this field displays the maximum value in every 1 hour.
If the registered maximum value of the diagnosis object attribute is larger than 100 or the maximum value of the diagnosis object attribute is not registered:
  • When Per Minute (60 minutes * max) is displayed in the horizontal axis, this field displays Maximum value in every minute/max*100%.
  • When Per Half Hour (24 hour * max) is displayed in the horizontal axis, this field displays Maximum value in every 0.5 hour/max*100%.
  • When Per Hour (72 hour * max) is displayed in the horizontal axis, this field displays Maximum value in every 1 hour/max*100%.
max indicates the maximum value of the diagnosis object attribute within the period.

This field displays NA when the database is empty within the time step.

ALM

The vertical axis indicates the value of the diagnosis object attribute, in percentage.
  • * = Maximum

    * indicates the maximum value of the diagnosis object attribute within the time step of the horizontal axis.

  • # = Average

    # indicates the average value of the diagnosis object attribute within the time step of the horizontal axis.

  • A = Abnormal

    A indicates that the value of the diagnosis object attribute within the time step of the horizontal axis is incorrect.

Per Minute (60 minutes)

Per Minute (60 minutes * max)

The horizontal axis indicates the time.
  • Per Minute (60 minutes) or Per Minute (60 minutes * max): The period is 60 minutes and is divided into 60 consecutive time ranges at the interval of 1 minute.

  • Per Half Hour (24 hour) or Per Half Hour (24 hour * max): The period is 24 hours and is divided into 48 consecutive time ranges at the interval of 0.5 hour.

  • Per Hour (72 hour) or Per Hour (72 hour * max): The period is 72 hours and is divided into 72 consecutive periods at the interval of 1 hour.

When the maximum value of the diagnosis object attribute is registered, and the registered maximum value is smaller than or equal to 100, max is not displayed, and the horizontal axis is Per Minute (60 minutes), Per Half Hour (24 hour), or Per Hour (72 hour).

When the maximum value (larger than 100) of the diagnosis object attribute is registered or the maximum value is not registered, max indicates the maximum value of the diagnosis object attribute within the period.

Per Half Hour (24 hour)

Per Half Hour (24 hour * max)

Per Hour (72 hour)

Per Hour (72 hour * max)

Abnormal Information

Information about the diagnosis object attribute in abnormal state.

Time

Record time.

Abnormal Value

Data of a diagnosis object attribute.

display oids monitor status

Function

The display oids monitor status command displays OIDS monitoring information at the current time.

Format

display oids monitor status [ type type-name [ { object-index object-index | object-name object-name } [ { attribute-index attribute-index | attribute-name attribute-name } ] ] ] [ slot slot-id ]

Parameters

Parameter

Description

Value

type type-name

Specifies a diagnosis type name.

The value is of the enumerated type:
  • ACL: ACL diagnosis type

  • ARP: ARP diagnosis type

  • CPU: CPU diagnosis type

  • CPU-CHAN: CPU channel diagnosis type

  • DHCPv4: DHCPv4 diagnosis type

  • DHCPv6: DHCPv6 diagnosis type

  • FIBv4: IPv4 forwarding information table diagnosis type

  • FIBv6: IPv6 forwarding information table diagnosis type

  • Flash: Flash diagnosis type

  • L3table: Layer 3 hardware table diagnosis type

  • LOG: LOG diagnosis type

  • MAC: MAC diagnosis type

  • MCAST: multicast diagnosis type

  • Memory: memory diagnosis type

  • MPLS: MPLS diagnosis type

  • NAC: NAC diagnosis type

  • ND: IPv6 neighbor diagnosis type

  • NHP: next hop diagnosis type

  • Port: port diagnosis type

  • TEMP: temperature diagnosis type

  • TRAP: TRAP diagnosis type

object-index object-index Specifies a diagnosis object index.

To check the diagnosis objects and diagnosis object attributes supported by the device, run the display oids register-status command or see Appendix 1: OIDS Monitoring and Diagnosis Items Supported by the Switch.

object-name object-name Specifies a diagnosis object name.
attribute-index attribute-index Specifies a diagnosis object attribute index.
attribute-name attribute-name Specifies a diagnosis object attribute name.

slot slot-id

Specifies a slot ID.

The value depends on the device configuration.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

After the OIDS monitoring function is enabled, the device periodically collects and saves diagnosis object attribute data to database files based on diagnosis types, diagnosis objects, and diagnosis object attributes. The OIDS module sends key performance indicator (KPI) data to service modules based on the collected diagnosis object attribute data. Service modules compare the KPI data with the defined threshold range to determine whether to generate an event. If a service module generates an event, it sends the event information to the OIDS module. The OIDS module records the event in database files and sets diagnosis object attributes of abnormal events to Abnormal.

To check OIDS monitoring information recorded on the switch, run the display oids monitor status command. The displayed information includes the current values, upper thresholds, and status of diagnosis object attributes. Based on the status of diagnosis object attributes, you can quickly detect service faults. To check only abnormal diagnosis object attributes, run the display oids monitor current-fault command.

Example

# Display OIDS monitoring information related to the ARP diagnosis type at the current time.

<HUAWEI> display oids monitor status type arp
Slot Type-name  Object              Attribute           Current              Upper   Status
                name                name                value                value
---------------------------------------------------------------------------------------------
2    ARP        ARP                 ARP_Usage           0%                   85%     Normal
3    ARP        ARP                 ARP_Usage           0%                   85%     Normal
5    ARP        ARP                 ARP_Usage           0%                   85%     Normal
Table 3-114  Description of the display oids monitor status command output

Item

Description

Slot

Slot ID.

Type-name

Name of a diagnosis type.

Object name

Name of a diagnosis object.

Attribute name

Name of a diagnosis object attribute.

Current value

Current value of a diagnosis object attribute.

When the OIDS monitoring function is disabled, this field displays -.

Upper value

Upper threshold of a diagnosis object attribute. Service modules compare the collected current diagnosis object attribute value with the defined upper threshold to determine whether to generate an event.

When a diagnosis object attribute does not have the upper threshold, this field displays -.

Status

Status of a diagnosis object attribute:
  • Init: The diagnosis object attribute is in initial state.
  • Normal: The diagnosis object attribute is in normal state.
  • Abnormal: The diagnosis object attribute is in abnormal state.
  • Disable: The OIDS monitoring function is disabled.

display oids register-event

Function

The display oids register-event command displays information about OIDS events registered on the switch.

Format

display oids register-event [ slot slot-id ]

Parameters

Parameter

Description

Value

slot slot-id

Specifies a slot ID.

The value depends on the device configuration.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

After the OIDS monitoring function is enabled, the device periodically collects and saves diagnosis object attribute data to database files based on diagnosis types, diagnosis objects, and diagnosis object attributes. The OIDS module sends key performance indicator (KPI) data to service modules based on the collected diagnosis object attribute data. Service modules compare the KPI data with the defined threshold range to determine whether to generate an event. If a service module generates an event, it sends the event information to the OIDS module, which then records the information to database files.For example, if the collected ARP_Usage data exceeds 85%, the OIDS module records the ARP Usage High event. If the collected ARP_Usage data falls below 75%, the OIDS module records the ARP Usage Normal event. For details about the OIDS events supported by the device, see Appendix 2: OIDS Events Supported by the Switch.

You can run the display oids register-event command to check all registered OIDS events on the switch.

Example

# Display information about OIDS events registered on the board in slot 2.

<HUAWEI> display oids register-event slot 2
Slot Event-name                      Event      Type-name  Occur      Restrain
                                     category              times      times
--------------------------------------------------------------------------------
2    CPU Usage High                  Warning    CPU        0          0
2    CPU Usage Normal                Recovery   CPU        0          0
2    Memory Usage High               Warning    Memory     0          0
2    Memory Usage Normal             Recovery   Memory     0          0
2    Temperature High                Warning    TEMP       0          0
2    Temperature Normal              Recovery   TEMP       0          0
2    ARP Usage High                  Warning    ARP        0          0
2    ARP Usage Normal                Recovery   ARP        0          0
2    ND Usage High                   Warning    ND         0          0
2    ND Usage Normal                 Recovery   ND         0          0
2    FIBv4 Usage High                Warning    FIBv4      0          0
2    FIBv4 Usage Normal              Recovery   FIBv4      0          0
2    FIBv6 Usage High                Warning    FIBv6      0          0
2    FIBv6 Usage Normal              Recovery   FIBv6      0          0
2    NHP Usage High                  Warning    NHP        0          0
2    NHP Usage Normal                Recovery   NHP        0          0
2    L3ENTRY Usage High              Warning    L3table    0          0
2    L3ENTRY Usage Normal            Recovery   L3table    0          0
2    L3DEFIP Usage High              Warning    L3table    0          0
2    L3DEFIP Usage Normal            Recovery   L3table    0          0
2    L3INTF Usage High               Warning    L3table    0          0
2    L3INTF Usage Normal             Recovery   L3table    0          0
2    ECMP Usage High                 Warning    L3table    0          0
2    ECMP Usage Normal               Recovery   L3table    0          0
2    IPMC Usage High                 Warning    MCAST      0          0
2    IPMC Usage Normal               Recovery   MCAST      0          0
2    IPMC_VLAN Usage High            Warning    MCAST      0          0
2    IPMC_VLAN Usage Normal          Recovery   MCAST      0          0
2    VC_AND_SWAP Usage High          Warning    MPLS       0          0
2    VC_AND_SWAP Usage Normal        Recovery   MPLS       0          0
2    MPLS_ENTRY Usage High           Warning    MPLS       0          0
2    MPLS_ENTRY Usage Normal         Recovery   MPLS       0          0
2    EGR_MPLS Usage High             Warning    MPLS       0          0
2    EGR_MPLS Usage Normal           Recovery   MPLS       0          0
2    MAC Usage High                  Warning    MAC        0          0
2    MAC Usage Normal                Recovery   MAC        0          0
2    Bandwidth Usage Overload        Warning    Port       0          0
2    Bandwidth Usage Normal          Recovery   Port       0          0
2    CRC Packets                     Report     Port       0          0
2    Packets Discard                 Report     Port       0          0
2    Burst Traffic                   Report     Port       0          0
2    Multicast Hash Conflict         Report     MCAST      0          0
2    CPU Port Drop Pkt               Report     CPU-CHAN   0          0
2    CPU Queue Drop Pkt              Report     CPU-CHAN   0          0
2    CPCAR Drop Pkt                  Report     CPU-CHAN   0          0
2    ACL Usage High                  Warning    ACL        0          0
2    ACL Usage Normal                Recovery   ACL        0          0
Table 3-115  Description of the display oids register-event command output

Item

Description

Slot

Slot ID.

Event-name

Event name.

Event category

Event type:
  • Warning: warning event
  • Recovery: recovery event
  • Report: report event

Type-name

Diagnosis type.

Occur times

Number of times an event occurs.

Restrain times

Number of times an event is suppressed.

display oids register-status

Function

The display oids register-status command displays information about OIDS monitoring and diagnosis items registered on the switch.

Format

display oids register-status [ type type-name ] [ slot slot-id ]

Parameters

Parameter

Description

Value

type type-name

Specifies a diagnosis type name.

The value is of the enumerated type:
  • ACL: ACL diagnosis type

  • ARP: ARP diagnosis type

  • CPU: CPU diagnosis type

  • CPU-CHAN: CPU channel diagnosis type

  • DHCPv4: DHCPv4 diagnosis type

  • DHCPv6: DHCPv6 diagnosis type

  • FIBv4: IPv4 forwarding information table diagnosis type

  • FIBv6: IPv6 forwarding information table diagnosis type

  • Flash: Flash diagnosis type

  • L3table: Layer 3 hardware table diagnosis type

  • LOG: LOG diagnosis type

  • MAC: MAC diagnosis type

  • MCAST: multicast diagnosis type

  • Memory: memory diagnosis type

  • MPLS: MPLS diagnosis type

  • NAC: NAC diagnosis type

  • ND: IPv6 neighbor diagnosis type

  • NHP: next hop diagnosis type

  • Port: port diagnosis type

  • TEMP: temperature diagnosis type

  • TRAP: TRAP diagnosis type

slot slot-id

Specifies a slot ID.

The value depends on the device configuration.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

You can run the display oids register-status command to check information about the diagnosis types, diagnosis objects, and diagnosis object attributes registered on the switch, as well as the status of the OIDS monitoring and diagnosis functions. For details about the diagnosis types, diagnosis objects, and diagnosis object attributes supported by the switch, see Appendix 1: OIDS Monitoring and Diagnosis Items Supported by the Switch.

Example

# Display information about OIDS monitoring and diagnosis items related to the ARP diagnosis type registered on the switch.

<HUAWEI> display oids register-status type arp
Slot Type-name  Object Object              Attribute Attribute           Monitor        Diagnose
                index  name                index     name                enable-status  enable-status
-----------------------------------------------------------------------------------------------------
1    ARP        0      ARP                 0         ARP_Usage           Enable         Disable
2    ARP        0      ARP                 0         ARP_Usage           Enable         Disable
3    ARP        0      ARP                 0         ARP_Usage           Enable         Disable
4    ARP        0      ARP                 0         ARP_Usage           Enable         Disable
Table 3-116  Description of the display oids register-status command output

Item

Description

Slot

Slot ID.

Type-name

Diagnosis type.

Object index

Index of a diagnosis object.

Object name

Name of a diagnosis object.

Attribute index

Index of a diagnosis object attribute.

Attribute name

Name of a diagnosis object attribute.

Monitor enable-status

OIDS monitoring function status:
  • Enable: The OIDS monitoring function is enabled.
  • Disable: The OIDS monitoring function is disabled.

To configure the OIDS monitoring function, run the oids monitor enable command.

Diagnose enable-status

OIDS diagnosis function status:
  • Enable: The OIDS diagnosis function is enabled.
  • Disable: The OIDS diagnosis function is disabled.

To configure the OIDS diagnosis function, run the oids diagnose enable command.

display oids script

Function

The display oids script command displays script information of the currently subscribed OIDS event.

Format

display oids script

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

When monitoring and diagnosis are implemented through association between OIDS and OPS, run the display oids script command to check the mapping between scripts and intelligent diagnostic events and how many times the events trigger scripts.

Example

# Display script information of the currently subscribed OIDS event.

<HUAWEI> display oids script
The status of temp.py:                                                                                                             
TypeName                        EventName                     TriggerTimes                                                          
--------------------------------------------------------------------------------                                                    
TEMP                            Temperature High                1                                                                   
Table 3-117  Description of the display oids script command output

Item

Description

TypeName

Type of an event.

EventName

Name of the event.

TriggerTimes

Number of times the event is triggered.

TEMP

TEMP diagnosis type.

Temperature High

High sensor temperature.

oids diagnose enable

Function

The oids diagnose enable command enables the OIDS diagnosis function.

The undo oids diagnose enable command disables the OIDS diagnosis function.

By default, the OIDS diagnosis function is disabled.

Format

oids diagnose enable { type type-name | all }

undo oids diagnose enable { type type-name | all }

Parameters

Parameter

Description

Value

type type-name

Specifies a diagnosis type name.

The value is of the enumerated type:

CPU-CHAN: CPU channel diagnosis type

all

Indicates all diagnosis types.

-

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the OIDS diagnosis function is enabled, the switch records an OIDS event when finding that the KPI data exceeds the defined threshold, and the OIDS module determines whether to trigger OIDS diagnosis. If OIDS diagnosis is triggered, the OIDS module specifies a service module to perform diagnosis. The OIDS module records the diagnosis result received from the service module in the database. To check OIDS diagnosis results for fast fault location, run the display oids history-result command.

Precautions

Before enabling the OIDS diagnosis function, run the oids monitor enable command to enable the OIDS monitoring function for the corresponding diagnosis type.

Example

# Enable the OIDS diagnosis function for the CPU-CHAN diagnosis type.

<HUAWEI> system-view
[HUAWEI] oids diagnose enable type cpu-chan

# Enable the OIDS diagnosis function for all diagnosis types.

<HUAWEI> system-view
[HUAWEI] oids diagnose enable all

oids filter

Function

The oids filter command configures a log or trap filter.

The undo oids filter command deletes a log or trap filter.

By default, no log or trap filter is configured in the system.

Format

oids filter { log | trap } index module module-name alias alias-name

undo oids filter { log | trap } index

Parameters

Parameter Description Value
log

Configures a log filter.

-

trap

Configures a trap filter.

-

index

Specifies the index of a log or trap filter.

The value is an integer that ranges from 1 to 3.

module module-name

Specifies the log or trap module name.

The name is a string of 1 to 31 case-insensitive characters without spaces.

alias alias-name

Indicates a log or trap alias name.

The value is a string of 1 to 63 case-insensitive characters without spaces.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

The devices that support association between OIDS and OPS can filter OIDS events by using log or trap filters. Three log events and three trap events are preset on the device to improve the efficiency of filtering logs or traps. A maximum of three log filters and three trap filters can be configured on the same device. Each filter can be configured with the conditions for filtering logs or traps using the oids filter command. When the OIDS filter detects the logs or traps that meet the filter conditions, an OIDS event is generated. To view information about log or trap filters, run the display oids filter command.

Example

# Configure log filter 1.

<HUAWEI> system-view
[HUAWEI] oids filter log 1 module alml alias entreset

oids monitor enable

Function

The oids monitor enable command enables the OIDS monitoring function.

The undo oids monitor enable command disables the OIDS monitoring function.

By default, the OIDS monitoring function is enabled.

Format

oids monitor enable { type type-name | all }

undo oids monitor enable { type type-name | all }

Parameters

Parameter

Description

Value

type type-name

Specifies a diagnosis type name.

The value is of the enumerated type:
  • ACL: ACL diagnosis type

  • ARP: ARP diagnosis type

  • CPU: CPU diagnosis type

  • CPU-CHAN: CPU channel diagnosis type

  • DHCPv4: DHCPv4 diagnosis type

  • DHCPv6: DHCPv6 diagnosis type

  • FIBv4: IPv4 forwarding information table diagnosis type

  • FIBv6: IPv6 forwarding information table diagnosis type

  • Flash: Flash diagnosis type

  • L3table: Layer 3 hardware table diagnosis type

  • LOG: LOG diagnosis type

  • MAC: MAC diagnosis type

  • MCAST: multicast diagnosis type

  • Memory: memory diagnosis type

  • MPLS: MPLS diagnosis type

  • NAC: NAC diagnosis type

  • ND: IPv6 neighbor diagnosis type

  • NHP: next hop diagnosis type

  • Port: port diagnosis type

  • TEMP: temperature diagnosis type

  • TRAP: TRAP diagnosis type

all

Indicates all diagnosis types.

-

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The OIDS monitoring function is enabled for all diagnosis types by default. The following describes the OIDS process after the OIDS monitoring function is enabled:

  1. The switch periodically collects diagnosis object attribute data based on diagnosis types, diagnosis objects, and diagnosis object attributes and records the data in database files.
  2. The OIDS module sends KPI data to service modules based on the collected diagnosis object attribute data. Service modules then determine whether the data is within the normal range.
  3. Service modules compare the KPI data with the defined threshold range to determine whether to generate an event.
    • If a service module generates an event, it sends the event information to the OIDS module, and the process goes to step 4.
    • If no service module generates any event, service modules perform no further operations and the process ends.
  4. The OIDS module records the event in the database. If the OIDS diagnosis function is enabled for the switch using the oids diagnose enable command, the OIDS module determines whether to trigger OIDS diagnosis.

OIDS monitoring and event information enables you to learn about the switch and service running status and to detect faults in a timely manner.

Precautions

If an interface is Down, the switch does not collect attribute data from the interface or record the data in the database files.

Example

# Disable the OIDS monitoring function for the MAC diagnosis type.

<HUAWEI> system-view
[HUAWEI] undo oids monitor enable type mac

# Disable the OIDS monitoring function for all diagnosis types.

<HUAWEI> system-view
[HUAWEI] undo oids monitor enable all
Related Topics

Appendix 1: OIDS Monitoring and Diagnosis Items Supported by the Switch

Table 3-118  ACL diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

x (the same as a chip ID)

Unitx_ACL (x is the same as a chip ID)

ACL rule usage of chip x

0

VACL_Rule_Usage

VACL rule usage

N

5 minutes

1

VACL_Slice_Usage

VACL slice usage

N

5 minutes

2

IACL_Rule_Usage

IACL rule usage

N

5 minutes

3

IACL_Slice_Usage

IACL slice usage

N

5 minutes

4

EACL_Rule_Usage

EACL rule usage

N

5 minutes

5

EACL_Slice_Usage

EACL slice usage

N

5 minutes

6

ACL_Usage

ACL rule usage

N

5 minutes

7

EXT_ACL_Usage

EXT_ACL rule usage

N

5 minutes

NOTE:

For the ACL diagnosis type, X series cards support only attribute indexes 6 and 7. Other cards support only attribute indexes 0, 1, 2, 3, 4, and 5.

Table 3-119  ARP diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

ARP

ARP software entries

0

ARP_Usage

ARP software entry usage of LPUs

N

5 minutes

Table 3-120  CPU diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

CPU

CPU

0

CPU_Usage

CPU usage of LPUs or MPUs

N

5 minutes

Table 3-121  CPU-CHAN diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

CPU_Port

CPU port statistics

0

CPU_Port_Drop_Pkt

Dropped packet statistics of the CPU port

N

10 minutes

1

CPU_Que0

CPU queue 0 statistics

0

CPU_Que_Drop_Pkt

Dropped packet statistics of CPU queue 0

N

10 minutes

2

CPU_Que1

CPU queue 1 statistics

0

CPU_Que_Drop_Pkt

Dropped packet statistics of CPU queue 1

N

10 minutes

3

CPU_Que2

CPU queue 2 statistics

0

CPU_Que_Drop_Pkt

Dropped packet statistics of CPU queue 2

N

10 minutes

4

CPU_Que3

CPU queue 3 statistics

0

CPU_Que_Drop_Pkt

Dropped packet statistics of CPU queue 3

N

10 minutes

5

CPU_Que4

CPU queue 4 statistics

0

CPU_Que_Drop_Pkt

Dropped packet statistics of CPU queue 4

N

10 minutes

6

CPU_Que5

CPU queue 5 statistics

0

CPU_Que_Drop_Pkt

Dropped packet statistics of CPU queue 5

N

10 minutes

7

CPU_Que6

CPU queue 6 statistics

0

CPU_Que_Drop_Pkt

Dropped packet statistics of CPU queue 6

N

10 minutes

8

CPU_Que7

CPU queue 7 statistics

0

CPU_Que_Drop_Pkt

Dropped packet statistics of CPU queue 7

N

10 minutes

9

CPCAR

CPCAR statistics

0

CPCAR_Drop_Pkt

CPCAR dropped packet statistics

Y

10 minutes

Table 3-122  DHCPv4 diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

DHCPv4

DHCPv4

0

DHCPv4_Usage

Address usage of an IPv4 address pool (percentage of used IP addresses in the current address pool)

N

5 minutes

Table 3-123  DHCPv6 diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

DHCPv6

DHCPv6

0

DHCPv6_Usage

Address usage of an IPv6 address pool (percentage of used IP addresses in the current address pool)

N

5 minutes

Table 3-124  FIBv4 diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

FIBv4

IPv4 FIB table

0

FIBv4_Usage

IPv4 FIB table usage of LPUs

N

5 minutes

Table 3-125  FIBv6 diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

FIBv6

IPv6 FIB table

0

FIBv6_Usage

IPv6 FIB table usage of LPUs

N

5 minutes

Table 3-126  Flash diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

FLAG

Flag tag (Flag is an identification area in the flash memory.)

0

FLAG_RD_CNT

Total number of times the flag tag is read within the detection period.

N

60 minutes

1

FLAG_WR_CNT

Total number of times the flag tag is written within the detection period.

N

60 minutes

1

FLASH

Storage

2

NOR_ERASE_CNT

Total number of times the NOR flash is erased within the detection period.

N

60 minutes

Table 3-127  L3table diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

L3ENTRY

L3 ENTRY hardware entries

0

L3ENTRY_Usage

L3 ENTRY entry usage of LPUs

N

5 minutes

1

L3DEFIP

L3 routing hardware entries

0

L3DEFIP_Usage

L3 routing entry usage of LPUs

N

5 minutes

2

L3INTF

L3 host hardware entries

0

L3INTF_Usage

L3 host entry usage of LPUs

N

5 minutes

3

ECMP

Equal-cost routing hardware entries

0

ECMP_Usage

Equal-cost route usage of LPUs

N

5 minutes

4

NPFIBv4

NP IPv4 forwarding information entries

0

NPFIBv4_Usage

NP IPv4 forwarding information entry usage

N

5 minutes

5

NPFIBv6

NP IPv6 forwarding information entries

0

NPFIBv6_Usage

NP IPv6 forwarding information entry usage

N

5 minutes

Table 3-128  MAC diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

MAC

MAC address entries

0

MAC_Usage

MAC address entry usage of boards

N

5 minutes

1

MAC_Number

Number of MAC address entries of boards

N

5 minutes

Table 3-129  MCAST diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

IPMC

IPMC hardware entries

0

IPMC_Usage

IPMC entry usage of LPUs

N

5 minutes

1

IPMC_VLAN

IPMC_VLAN hardware entries

0

IPMC_VLAN_Usage

IPMC_VLAN entry usage of LPUs

N

5 minutes

2

Hash_Conflict

Entry hash collision

0

Occur_Times

Number of hash collisions during entry delivery

N

5 minutes

Table 3-130  Memory diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

Memory

Memory

0

Memory_Usage

Memory usage

N

5 minutes

Table 3-131  MPLS diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

VC_AND_SWAP

VC_AND_SWAP hardware entries

0

VC_AND_SWAP_Usage

VC_AND_SWAP entry usage of LPUs

N

5 minutes

1

MPLS_ENTRY

MPLS_ENTRY hardware entries

0

MPLS_ENTRY_Usage

MPLS_ENTRY entry usage of LPUs

N

5 minutes

2

EGR_MPLS

EGR_IP_TUNNEL_MPLS hardware entries

0

EGR_MPLS_Usage

EGR_IP_TUNNEL_MPLS entry usage of LPUs

N

5 minutes

Table 3-132  NAC diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

Wire_PreAuth

Wired pre-connection users

0

User_Number

Number of users

N

5 minutes

1

Wire_Auth

Wired authenticated users

0

User_Number

Number of users

N

5 minutes

2

Wireless_PreAuth

Wireless pre-connection users

0

User_Number

Number of users

N

5 minutes

3

Wireless_Auth

Wireless authenticated users

0

User_Number

Number of users

N

5 minutes

4

NAC

NAC

1

User_Usage

User usage

N

5 minutes

Table 3-133  ND diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

ND

IPv6 neighbor software entries

0

ND_Usage

IPv6 neighbor software entry usage of LPUs

N

5 minutes

Table 3-134  NHP diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

0

NHP

Next-hop software entries

0

NHP_Usage

Next-hop software entry usage of LPUs

N

5 minutes

Table 3-135  Port diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

The value depends on the device configuration.

Interface name, consisting of the interface type and number, for example, XGE1/0/1. The value depends on the device configuration.

Interface name

0

Input_Usage

Inbound bandwidth usage of the interface

N

5 minutes

1

Output_Usage

Outbound bandwidth usage of the interface

N

5 minutes

2

CRC_Number

Number of incoming CRC error packets of the interface

N

10 minutes

3

Discard_Number

Number of packets dropped in the outbound direction of the interface

N

10 minutes

4

Buffer_Used

Buffer size used by the interface, in KB.

N

10 minutes

Table 3-136  TEMP diagnosis type

Object Index

Object Name

Object Description

Attribute Index

Attribute Name

Attribute Description

Whether OIDS Diagnosis Is Supported

Detection Period

x (temperature sensor ID of a board)

Temp_Sensor_x (x is the temperature sensor ID of a board)

Temperature sensor

0

Temperature

Temperature sensor temperature of a board

N

5 minutes

Appendix 2: OIDS Events Supported by the Switch

Table 3-137  OIDS events supported by the ACL diagnosis type

Event

Type

Description

Reason

Suppression

ACL Usage High

Warning

ACL hardware entry usage is high.

ACL hardware entry usage exceeds 80%.

None

ACL Usage Normal

Recovery

ACL hardware entry usage returns to the normal range.

ACL hardware entry usage falls below 70%.

None

Table 3-138  OIDS events supported by the ARP diagnosis type

Event

Type

Description

Reason

Suppression

ARP Usage High

Warning

ARP software entry usage is high.

ARP software entry usage of LPUs exceeds 85%.

None

ARP Usage Normal

Recovery

ARP software entry usage returns to the normal range.

ARP software entry usage of LPUs falls below 75%.

None

Table 3-139  OIDS events supported by the CPU diagnosis type

Event

Type

Description

Reason

Suppression

CPU Usage High

Warning

CPU usage of boards is high.

CPU usage of boards exceeds 90%.

None

CPU Usage Normal

Recovery

CPU usage of boards returns to the normal range.

CPU usage of boards falls below 85%.

None

Table 3-140  OIDS events supported by the CPU-CHAN diagnosis type

Event

Type

Description

Reason

Suppression

CPU Port Drop Pkt

Report

Packets are dropped on the CPU port.

Packets are dropped because they exceed the rate limit of the CPU port or each queue.

None

CPU Queue Drop Pkt

Report

Packets are dropped from the CPU queue.

Packets are dropped because they exceed the rate limit of the CPU queue.

None

CPCAR Drop Pkt

Report

Packets are dropped due to CPCAR exceeding.

Packets are dropped because they exceed the CPCAR.

None

Table 3-141  OIDS events supported by the DHCPv4 diagnosis type

Event

Type

Description

Reason

Suppression

DHCPv4 Usage High

Warning

IP address usage of an IPv4 address pool is high.

IP address usage of an IPv4 address pool exceeds 85%.

None

DHCPv4 Usage Normal

Recovery

IP address usage of an IPv4 address pool returns to the normal range.

IP address usage of an IPv4 address pool falls below 85%.

None

Table 3-142  OIDS events supported by the DHCPv6 diagnosis type

Event

Type

Description

Reason

Suppression

DHCPv6 Usage High

Warning

IP address usage of an IPv6 address pool is high.

IP address usage of an IPv6 address pool exceeds 85%.

None

DHCPv6 Usage Normal

Recovery

IP address usage of an IPv6 address pool returns to the normal range.

IP address usage of an IPv6 address pool falls below 85%.

None

Table 3-143  OIDS events supported by the FIBv4 diagnosis type

Event

Type

Description

Reason

Suppression

FIBv4 Usage High

Warning

IPv4 FIB table usage is high.

IPv4 FIB table usage of LPUs exceeds 85%.

None

FIBv4 Usage Normal

Recovery

IPv4 FIB table usage returns to the normal range.

IPv4 FIB table usage of LPUs falls below 75%.

None

Table 3-144  OIDS events supported by the FIBv6 diagnosis type

Event

Type

Description

Reason

Suppression

FIBv6 Usage High

Warning

IPv6 FIB table usage is high.

IPv6 FIB table usage of LPUs exceeds 85%.

None

FIBv6 Usage Normal

Recovery

IPv6 FIB table usage returns to the normal range.

IPv6 FIB table usage of LPUs falls below 75%.

None

Table 3-145  OIDS events supported by the L3table diagnosis type

Event

Type

Description

Reason

Suppression

L3ENTRY Usage High

Warning

L3 ENTRY hardware entry usage is high.

L3 ENTRY hardware entry usage of LPUs exceeds 85%.

None

L3ENTRY Usage Normal

Recovery

L3 ENTRY hardware entry usage of LPUs returns to the normal range.

L3 ENTRY hardware entry usage of LPUs falls below 75%.

None

L3DEFIP Usage High

Warning

L3 routing hardware entry usage is high.

L3 routing hardware entry usage of LPUs exceeds 85%.

None

L3DEFIP Usage Normal

Recovery

L3 routing hardware entry usage returns to the normal range.

L3 routing hardware entry usage of LPUs falls below 75%.

None

L3INTF Usage High

Warning

L3 host hardware entry usage is high.

L3 host hardware entry usage of LPUs exceeds 85%.

None

L3INTF Usage Normal

Recovery

L3 host hardware entry usage returns to the normal range.

L3 host hardware entry usage of LPUs falls below 75%.

None

ECMP Usage High

Warning

Equal-cost routing hardware entry usage is high.

Equal-cost routing hardware entry usage of LPUs exceeds 85%.

None

ECMP Usage Normal

Recovery

Equal-cost routing hardware entry usage returns to the normal range.

Equal-cost routing hardware entry usage of LPUs falls below 75%.

None

NPFIBv4 Usage High

Warning

NP IPv4 forwarding information entry usage is high.

IPv4 forwarding information entry usage of NP boards exceeds 85%.

None

NPFIBv4 Usage Normal

Recovery

NP IPv4 forwarding information entry usage returns to the normal range.

IPv4 forwarding information entry usage of NP boards falls below 75%.

None

NPFIBv6 Usage High

Warning

NP IPv6 forwarding information entry usage is high.

IPv6 forwarding information entry usage of NP boards exceeds 85%.

None

NPFIBv6 Usage Normal

Recovery

NP IPv6 forwarding information entry usage returns to the normal range.

IPv6 forwarding information entry usage of NP boards falls below 75%.

None

Table 3-146  OIDS events supported by the MAC diagnosis type

Event

Type

Description

Reason

Suppression

MAC Usage High

Warning

MAC address entry usage is high.

MAC address entry usage of LPUs exceeds 80%.

None

MAC Usage Normal

Recovery

MAC address entry usage returns to the normal range.

MAC address entry usage of LPUs falls below 70%.

None

Table 3-147  OIDS events supported by the MCAST diagnosis type

Event

Type

Description

Reason

Suppression

IPMC Usage High

Warning

IPMC hardware entry usage is high.

IPMC hardware entry usage of LPUs exceeds 85%.

None

IPMC Usage Normal

Recovery

IPMC hardware entry usage returns to the normal range.

IPMC hardware entry usage of LPUs falls below 75%.

None

IPMC_VLAN Usage High

Warning

IPMC_VLAN hardware entry usage is high.

IPMC_VLAN hardware entry usage of LPUs exceeds 85%.

None

IPMC_VLAN Usage Normal

Recovery

IPMC_VLAN hardware entry usage returns to the normal range.

IPMC_VLAN hardware entry usage of LPUs falls below 75%.

None

Multicast Hash Conflict

Report

Hash collisions occur during multicast entry delivery.

Hash collisions occur during multicast entry delivery on LPUs.

At most one Multicast Hash Conflict event occurs on each LPU every 12 hours.

After the Multicast Hash Conflict event occurs, the Occur_Times attribute is set to Abnormal. If no hash collision occurs for three consecutive days after the Multicast Hash Conflict event occurs, the Occur_Times attribute is set to Normal.

Table 3-148  OIDS events supported by the Memory diagnosis type

Event

Type

Description

Reason

Suppression

Memory Usage High

Warning

Memory usage of boards is high.

Memory usage of boards exceeds 80%.

None

Memory Usage Normal

Recovery

Memory usage of boards returns to the normal range.

Memory usage of boards falls below 75%.

None

Table 3-149  OIDS events supported by the MPLS diagnosis type

Event

Type

Description

Reason

Suppression

VC_AND_SWAP Usage High

Warning

VC_AND_SWAP hardware entry usage is high.

VC_AND_SWAP hardware entry usage of LPUs exceeds 85%.

None

VC_AND_SWAP Usage Normal

Recovery

VC_AND_SWAP hardware entry usage returns to the normal range.

VC_AND_SWAP hardware entry usage of LPUs falls below 75%.

None

MPLS_ENTRY Usage High

Warning

MPLS_ENTRY hardware entry usage is high.

MPLS_ENTRY hardware entry usage of LPUs exceeds 85%.

None

MPLS_ENTRY Usage Normal

Recovery

MPLS_ENTRY hardware entry usage returns to the normal range.

MPLS_ENTRY hardware entry usage of LPUs falls below 75%.

None

EGR_MPLS Usage High

Warning

EGR_IP_TUNNEL_MPLS hardware entry usage is high.

EGR_IP_TUNNEL_MPLS hardware entry usage of LPUs exceeds 85%.

None

EGR_MPLS Usage Normal

Recovery

EGR_IP_TUNNEL_MPLS hardware entry usage returns to the normal range.

EGR_IP_TUNNEL_MPLS hardware entry usage of LPUs falls below 75%.

None

Table 3-150  OIDS events supported by the NAC diagnosis type

Event

Type

Description

Reason

Suppression

NAC Usage High

Warning

There are many NAC users.

The number of NAC online users exceeds 85% of the specifications.

None

NAC Usage Normal

Recovery

The number of NAC users returns to the normal range.

The number of NAC users falls below 85% of the threshold.

None

Table 3-151  OIDS events supported by the ND diagnosis type

Event

Type

Description

Reason

Suppression

ND Usage High

Warning

IPv6 neighbor software entry usage is high.

IPv6 neighbor software entry usage of LPUs exceeds 85%.

None

ND Usage Normal

Recovery

IPv6 neighbor software entry usage returns to the normal range.

IPv6 neighbor software entry usage of LPUs falls below 75%.

None

Table 3-152  OIDS events supported by the NHP diagnosis type

Event

Type

Description

Reason

Suppression

NHP Usage High

Warning

Next-hop software entry usage is high.

Next-hop software entry usage of LPUs exceeds 85%.

None

NHP Usage Normal

Recovery

Next-hop software entry usage returns to the normal range.

Next-hop software entry usage of LPUs falls below 75%.

None

Table 3-153  OIDS events supported by the Port diagnosis type

Event

Type

Description

Reason

Suppression

Bandwidth Usage Overload

Warning

Interface bandwidth usage is high.

Interface bandwidth usage exceeds 50%.

None

Bandwidth Usage Normal

Recovery

Interface bandwidth usage returns to the normal range.

Interface bandwidth usage falls below 40%.

None

CRC Packets

Report

CRC error packets are received on an interface.

The interface receives more than 10 CRC error packets.

If an interface receives more than 10 CRC error packets for the first time, an event is recorded, and the CRC_Number attribute is set to Abnormal. If the interface does not receive any CRC error packets within 12 hours, the CRC_Number attribute is restored to Normal. If the interface receives CRC error packets again within 12 hours, the system checks whether the interface receives CRC error packets within the next 12 hours since the current time.

Packets Discard

Report

Outgoing packets are dropped on an interface.

More than 10 outgoing packets are dropped on the interface because the outgoing traffic volume exceeds the buffer.

If more than 10 outgoing packets are dropped on the interface for the first time, an event is recorded, and the Discard_Number attribute is set to Abnormal. If the number of dropped outgoing packets remains unchanged within 12 hours, the Discard_Number attribute is restored to Normal. If the number of dropped outgoing packets increases within 12 hours, the system checks whether the number of dropped outgoing packets increases within the next 12 hours since the current time.

Burst Traffic

Report

There is burst traffic.

An interface uses dynamic buffer.

If there is burst traffic within multiple consecutive periods, an event is recorded only for the first time.

Table 3-154  OIDS events supported by the TEMP diagnosis type

Event

Type

Description

Reason

Suppression

Temperature High

Warning

Sensor temperature is high.

Sensor temperature exceeds the threshold. To learn about the high temperature alarm threshold of each board, run the display temperature command.

None

Temperature Normal

Recovery

Sensor temperature returns to the normal range.

Sensor temperature returns to the normal range. To learn about the high temperature alarm clear threshold of each board, run the display temperature command.

None

Table 3-155  OIDS events supported by the LOG diagnosis type

Event

Type

Description

Reason

Suppression

Log1 Occured

Report

A specific log is generated on the switch.

The configured log filter detects a specific log.

None

Log2 Occured

Report

A specific log is generated on the switch.

The configured log filter detects a specific log.

None

Log3 Occured

Report

A specific log is generated on the switch.

The configured log filter detects a specific log.

None

Table 3-156  OIDS events supported by the TRAP diagnosis type

Event

Type

Description

Reason

Suppression

Trap1 Occured

Report

A specific trap is generated on the switch.

The configured trap filter detects a specific trap.

None

Trap2 Occured

Report

A specific trap is generated on the switch.

The configured trap filter detects a specific trap.

None

Trap3 Occured

Report

A specific trap is generated on the switch.

The configured trap filter detects a specific trap.

None

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065659

Views: 123151

Downloads: 88

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next