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

Alarm Handling

S9300, S9300E, and S9300X V200R013C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
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).
IFNET

IFNET

IFNET_1.3.6.1.4.1.2011.5.25.41.4.1 hwIfMonitorCrcErrorRising

Description

IFNET/1/CRCERRORRISING: OID [oid] The CRC error is rising. (hwIfMonitorIndex=[INTEGER], hwIfMonitorCrcErrorStatistics=[COUNTER64], hwIfMonitorCrcErrorThreshold=[INTEGER], hwIfMonitorCrcErrorInterval=[INTEGER], InterfaceName=[STRING])

The trap is generated if the number of CRC errors exceeds the specified value in the specified time.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.4.1 Critical other(1)

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

hwIfMonitorIndex

indicates the interface index.

hwIfMonitorCrcErrorStatistics

indicates statistics on CRC errors.

hwIfMonitorCrcErrorThreshold

indicates the threshold for CRC trap (a trap is generated if the number of CRCs exceeds the threshold).

hwIfMonitorCrcErrorInterval

indicates the time period for collecting CRC error statistics.

InterfaceName

indicates the interface name.

Impact on the System

Data of some services on the interface will be dropped.

Possible Causes

The number of packets that are dropped because they failed the CRC exceeded the threshold.

The possible causes are as follows:

1.The optical module was faulty.

2.The optical fiber was faulty.

Procedure

  1. Replace the optical module and then check whether the fault is rectified.
    1. If so, go to step 4.
    2. If not, go to step 2.
  2. Replace the optical fiber, and then check whether the fault is rectified.
    1. If so, go to step 4.
    2. If not, go to step 3.
  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

IFNET_1.3.6.1.4.1.2011.5.25.41.4.2 hwIfMonitorCrcErrorResume

Description

IFNET/1/CRCERRORRESUME: OID [oid] The CRC error resume. (hwIfMonitorIndex=[INTEGER], hwIfMonitorCrcErrorStatistics=[COUNTER64], hwIfMonitorCrcErrorThreshold=[INTEGER], hwIfMonitorCrcErrorInterval=[INTEGER], InterfaceName=[STRING])

The trap is cleared if the number of CRC errors is smaller than the specified value in the specified time.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.4.2 Critical other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwIfMonitorIndex

Indicates the interface index.

hwIfMonitorCrcErrorStatistics

Indicates statistics on CRC errors.

hwIfMonitorCrcErrorThreshold

Indicates the threshold for CRC trap (a trap is generated if the number of CRCs exceeds the threshold).

hwIfMonitorCrcErrorInterval

indicates the time period for collecting CRC error statistics.

InterfaceName

indicates the interface name.

Impact on the System

Services will be restored.

Possible Causes

The trap that the number of packets that are dropped because they failed the CRC exceeded the threshold was cleared.

Procedure

  1. This alarm message is informational only, and no action is required.

IFNET_1.3.6.1.4.1.2011.5.25.41.4.5 hwIfMonitorInputRateRising

Description

IFNET/4/INBWRATEEXCEED: OID [oid] Interface input flow bandwidth usage exceeded the trap threshold. (Interface=[INTEGER], BandWidthUsage=[INTEGER], TrapThreshold=[INTEGER], InterfaceName=[STRING])

The trap was generated when the percentage of the rate of received traffic to the total bandwidth on an interface was greater than the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.4.5 Warning other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Interface

Indicates the interface index.

BandWidthUsage

Indicates bandwidth usage.

TrapThreshold

Indicates the trap threshold of bandwidth usage.

InterfaceName

Indicates the interface name.

Impact on the System

When traffic rate is approximate to the maximum interface bandwidth, service packets may be dropped.

Possible Causes

The rate of traffic received by the interface was too large.

Procedure

  1. Run the display this interface command on the interface to check whether the traffic threshold is too low. The threshold range is specified by users according to actual services.

    • If so, go to Step 2.

    • If not, go to Step 3.

  2. Run the trap-threshold input-rate threshold_value command to reset the threshold and then check whether the alarm is cleared.

    • If so, go to Step 7.

    • If not, go to Step 3.

  3. Run the display this interface command in the interface view to check the number and types of packets on the interface. Determine whether the packet sending and receiving is abnormal due to a failure such as loop.

    • If so, go to Step 4.

    • If not, go to Step 5.

  4. Find out the abnormal packets and eliminate the impact of abnormal packets. Check whether the alarm is cleared.

    • If so, go to Step 7.

    • If not, go to Step 5.

  5. Expand capacity in any of the following ways:

    • Configure an Eth-Trunk to load balance traffic.
    • Migrate some services to idle devices.
    • Use the link with higher bandwidth to transmit service packets.

    After the operation, check whether the alarm is cleared.

    • If so, go to Step 7.

    • If not, go to Step 6.

  6. Collect trap messages, log messages, and configurations, and then contact the technical support personnel.
  7. End.

IFNET_1.3.6.1.4.1.2011.5.25.41.4.6 hwIfMonitorInputRateResume

Description

IFNET/4/INBWRATERESUME: OID [oid] Interface input flow bandwidth usage was restored to the trap threshold. (Interface=[INTEGER], BandWidthUsage=[INTEGER], TrapThreshold=[INTEGER], InterfaceName=[STRING])

The trap was generated when the percentage of the rate of received traffic to the total bandwidth on an interface became lower than the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.4.6 Warning other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Interface

Indicates the interface index.

BandWidthUsage

Indicates bandwidth usage.

TrapThreshold

Indicates the trap threshold of bandwidth usage.

InterfaceName

Indicates the interface name.

Impact on the System

None.

Possible Causes

The rate of traffic received by the interface became lower than the threshold.

Procedure

  1. This alarm message is informational only, and no action is required.

IFNET_1.3.6.1.4.1.2011.5.25.41.4.7 hwIfMonitorOutputRateRising

Description

IFNET/4/OUTBWRATEEXCEED: OID [oid] Interface output flow bandwidth usage exceeded the trap threshold. (Interface=[INTEGER], BandWidthUsage=[INTEGER], TrapThreshold=[INTEGER], InterfaceName=[STRING])

The trap was generated when the percentage of the rate of sent traffic to the total bandwidth on an interface was greater than the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.4.7 Warning other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Interface

Indicates the interface index.

BandWidthUsage

Indicates bandwidth usage.

TrapThreshold

Indicates the trap threshold of bandwidth usage.

InterfaceName

Indicates the interface name.

Impact on the System

When traffic rate is approximate to the maximum interface bandwidth, service packets may be dropped.

Possible Causes

The rate of traffic sent by the interface was too large.

Procedure

  1. Run the display this interface command on the interface to check whether the traffic threshold is too low. The threshold range is specified by users according to actual services.

    • If so, go to Step 2.

    • If not, go to Step 3.

  2. Run the trap-threshold input-rate threshold_value command to reset the threshold and then check whether the alarm is cleared.

    • If so, go to Step 7.

    • If not, go to Step 3.

  3. Run the display this interface command in the interface view to check the number and types of packets on the interface. Determine whether the packet sending and receiving is abnormal due to a failure such as loop.

    • If so, go to Step 4.

    • If not, go to Step 5.

  4. Find out the abnormal packets and eliminate the impact of abnormal packets. Check whether the alarm is cleared.

    • If so, go to Step 7.

    • If not, go to Step 5.

  5. Expand capacity in any of the following ways:

    • Configure an Eth-Trunk to load balance traffic.
    • Migrate some services to idle devices.
    • Use the link with higher bandwidth to transmit service packets.

    After the operation, check whether the alarm is cleared.

    • If so, go to Step 7.

    • If not, go to Step 6.

  6. Collect trap messages, log messages, and configurations, and then contact the technical support personnel.
  7. End.

IFNET_1.3.6.1.4.1.2011.5.25.41.4.8 hwIfMonitorOutputRateResume

Description

IFNET/4/OUTBWRATERESUME: OID [oid] Interface output flow bandwidth usage was restored to the trap threshold. (Interface=[INTEGER], BandWidthUsage=[INTEGER], TrapThreshold=[INTEGER], InterfaceName=[STRING])

The trap was generated when the percentage of the rate of sent traffic to the total bandwidth on an interface became lower than the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.4.8 Warning other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Interface

Indicates the interface index.

BandWidthUsage

Indicates bandwidth usage.

TrapThreshold

Indicates the trap threshold of bandwidth usage.

InterfaceName

Indicates the interface name.

Impact on the System

None.

Possible Causes

The rate of traffic sent by the interface became lower than the threshold.

Procedure

  1. This alarm message is informational only, and no action is required.

IFNET_1.3.6.1.6.3.1.1.5.3 linkDown

Description

IFNET/1/IF_LINKDOWN: OID [oid] Interface [interface-index] turned into DOWN state.(AdminStatus=[INTEGER],OperStatus=[INTEGER],InterfaceName=[OCTET])

The status of the link protocol on the interface became Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.6.3.1.1.5.3 Critical other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

interface-index

Indicates the interface index.

AdminStatus

Indicates the admin status, which means whether the interface has been disabled.
  • 1: undo shutdown
  • 2: shutdown

OperStatus

Indicates the operating status, which means the link layer protocol status of the interface.
  • 1: Up
  • 2: Down

InterfaceName

Indicates the interface name.

Impact on the System

The interface cannot forward packets normally.

Possible Causes

Cause 1:

The interface became Down and the link was disconnected.

Cause 2:

The VLANIF interface is deleted.

Procedure

  1. If the VLANIF interface is deleted, this trap message is informational only. No action is required, go to Step 7.
  2. Run the display this command in the interface view to check whether interfaces on both ends are shut down.

    • If so, go to Step 3.

    • If not, go to Step 4.

  3. Run the undo shutdown command in the interface view to check whether the alarm is cleared.

    • If so, go to Step 7.

    • If not, go to Step 4.

  4. Check whether the cable and optical module are loosened or dropped.

    • If so, go to Step 6.

    • If not, go to Step 5.

  5. Connect the physical link correctly and then check whether the alarm is cleared.

    • If so, go to Step 7.

    • If not, go to Step 6.

  6. Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

IFNET_1.3.6.1.6.3.1.1.5.4 linkUp

Description

IFNET/1/IF_LINKUP: OID [oid] Interface [interface-index] turned into UP state. (AdminStatus=[INTEGER],OperStatus=[INTEGER],InterfaceName=[OCTET])

The alarm was generated when the link protocol status of a trunk member interface became Up.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.6.3.1.1.5.4 Critical other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

interface-index

Indicates the interface index.

AdminStatus

Indicates the admin status.
  • 1: undo shutdown
  • 2: shutdown

OperStatus

Indicates the operating status.
  • 1: Up
  • 2: Down

InterfaceName

Indicates the interface name.

Impact on the System

Traffic will be recovered.

Possible Causes

1.

The undo shutdown command was run in the interface view.

2.

The interface became Up and the link was recovered.

3.

The link layer protocol was Up.

4.

The physical status of an Ethernet interface became Up.

Procedure

  1. This alarm message is informational only, and no action is required.

IFNET_1.3.6.1.4.1.2011.5.25.41.3.5 hwIfFlowDown

Description

IFNET/4/IF_FLOWDOWN:OID [OID] The state of interface turned to DOWN because of FLOW DOWN. (Interface=[INTEGER], InterfaceIndex=[INTEGER], SysUpTime=[TIMETICK], FlowStatus=[INTEGER], InterfaceName=[STRING])

The trap was generated when the traffic on a particular interface was interrupted and then the interface became Down. The time and cause for the status change was recorded.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.3.5 Warning processingErrorAlarm(4)

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

Interface

Indicates the unfixed index of an interface.

InterfaceIndex

Indicates the fixed index of an interface.

SysUpTime

Indicates the time for system startup.

FlowStatus

Indicates the traffic status on an interface.

InterfaceName

Indicates the name of interface.

Impact on the System

Traffic will be interrupted.

Possible Causes

  • The mVRRP backup group changed to the non-Master state.

  • When the mVRRP backup group was in the Master state or the interface was bound to the PW, the shutdown command was run on the interface or the link was faulty.

  • The PW configuration was deleted.

Procedure

  1. Check whether the interface type is Virtual-Ethernet.

    • If so, go to Step 2.
    • If not, go to Step 7.

  2. Run the display l2vpn ccc-interface vc-type all command, to check whether there is the specified interface that the alarm occurs.

    • If so, go to Step 9.
    • If not, go to Step 3.

  3. Check whether a PW needs to be reconfigured.

    • If so, go to Step 4.
    • If not, go to Step 16.

  4. Reconfigure a PW. For details, see S9300, S9300E, and S9300X V200R013C00 Configuration Guide - VPN.
  5. Run the display l2vpn ccc-interface vc-type all command, to check whether there is the specified interface that the alarm occurs.

    • If so, go to Step 6.
    • If not, go to Step 15.

  6. Run the display interface command to check whether the physical status and link protocol status of the interface are Up.

    • If so, go to Step 16.
    • If not, go to Step 9.

  7. Run the display vrrp binding admin-vrrp command to check whether the interface is bound to the mVRRP backup group.

    • If so, go to Step 8.
    • If not, go to Step 15.

  8. Run the display vrrp admin-vrrp command to check whether the mVRRP backup group to which the interface is bound is in the Master state.

    • If so, go to Step 9.
    • If not, go to Step 12.

  9. Run the display this command in the interface view to check whether the shutdown command is configured on the interface.

    • If so, go to Step 10.
    • If not, go to Step 11.

  10. Run the undo shutdown command in the interface view. Then, run the display this interface command to check whether the interface status is Up.

    • If so, go to Step 16.
    • If not, go to Step 6.

  11. Check and change the physical link to ensure that the physical link works normally. Then, run the display this interface command to check whether the interface status is Up.

    • If so, go to Step 16.
    • If not, go to Step 15.

  12. Check whether the status of the mVRRP backup group needs to be switched.

    • If so, go to Step 13.
    • If not, go to Step 16.

  13. Switch the status of the mVRRP backup group. For details, see S9300, S9300E, and S9300X V200R013C00 Configuration Guide - Reliability VRRP Configuration.
  14. Run the display this interface command in the interface view to check whether the physical status and link protocol status of the interface are Up.

    • If so, go to Step 16.
    • If not, go to Step 15.

  15. Collect alarm information and configuration information, and then contact technical support personnel.
  16. End.

IFNET_1.3.6.1.4.1.2011.5.25.41.3.6 hwIfFlowUp

Description

IFNET/4/IF_FLOWUP:OID [oid] The state of interface turned to UP because of FLOW UP. (Interface=[INTEGER], InterfaceIndex=[INTEGER], SysUpTime=[TIMETICK], FlowStatus=[INTEGER], InterfaceName=[STRING])

The trap was generated when the traffic on a particular interface was recovered. The time and cause for the recovery was recorded.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.3.6 Warning other(1)

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

Interface

Indicates the unfixed index of an interface.

InterfaceIndex

Indicates the fixed index of an interface.

SysUpTime

Indicates the time for system startup.

FlowStatus

Indicates the traffic status on an interface.

InterfaceName

Indicates the name of interface.

Impact on the System

Traffic will be recovered.

Possible Causes

  • 1.

    The mVRRP backup group was switched to the Master state.

    2.

    When the mVRRP backup group was in the Master state or the interface was bound to the PW, the interface went Up.

    3.

    A PW was configured on the interface.

Procedure

  1. This alarm message is informational only, and no action is required.

IFNET_1.3.6.1.4.1.2011.5.25.41.3.7 hwIfNameChange

Description

IFNET/1/IF_CHANGE:OID [oid] When a single-chassis device is upgraded to a multi-chassis device, the interface information is changed.

The single-chassis device was expanded into the multi-chassis device, and consequently the interface information was changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.3.7 Critical equipmentAlarm(5)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Impact on the System

An interface is no longer defined in three dimensions, but in four dimensions.

Possible Causes

The device was upgraded from a single-chassis system to a multi-chassis system.

Procedure

  1. This alarm message is informational only, and no action is required.

IFNET_1.3.6.1.4.1.2011.5.25.41.3.8 hwIfNameChangeResume

Description

IFNET/1/IF_CHANGE_RESUME:OID [oid] When a multi-chassis restore a single-chassis device, the interface information is changed.

The multi-chassis device was changed back into the single-chassis device, and consequently the interface information was changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.3.8 Critical equipmentAlarm(5)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Impact on the System

An interface is no longer defined in four dimensions, but in three dimensions.

Possible Causes

The device was reverted from a multi-chassis device to a single-chassis device.

Procedure

  1. This alarm message is informational only, and no action is required.

IFNET_1.3.6.1.4.1.2011.5.25.41.3.26 hwEntityExtCfmOverSlot

Description

IFNET/4/IF_SLOT_CFMOVER: OID [oid] The configuration of the interface board is restored. (BoardName=[STRING])

The configuration of the interface board was restored.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.3.26 Warning other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

BoardName

Indicates the name of the interface board.

Impact on the System

After the configuration of the interface board is restored, the interface board is usable.

Possible Causes

The configuration restoration of the interface board completes after the entire device or the interface board was restarted.

Procedure

  1. This alarm information is informational only, and no action is required.

Related Information

None.

IFNET_1.3.6.1.4.1.2011.5.25.41.3.27 hwEntityExtCfmOverCard

Description

IFNET/4/IF_CARD_CFMOVER: OID [oid] The configuration of the interface card is restored. (CardName=[STRING])

The configuration of the interface card was restored.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.3.27 Warning other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

CardName

Indicates the name of the interface card.

Impact on the System

After the configuration of the interface card is restored, the interface card is usable.

Possible Causes

The entire device or the interface card was restarted.

Procedure

  1. This alarm information is informational only, and no action is required.

Related Information

None.

IFNET_1.3.6.1.4.1.2011.5.25.41.3.31 hwIfControlFlapSuppress

Description

IFNET/4/IF_SUPPRESS:OID [OID] The state of interface changed from unsuppress to suppress. (InterfaceIndex=[INTEGER], InterfaceExtIndex=[INTEGER], InterfaceName=[STRING], SuppressState=[INTEGER])

The flap control function was configured on an interface. An alarm was generated when the interface changed from the suppression status to non-suppression status.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.3.31 Warning communicationsAlarm(2)

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

InterfaceIndex

Indicates the interface index.

InterfaceExtIndex

Indicates the extended interface index.

InterfaceName

Indicates the interface name.

SuppressState

Indicates whether the interface is suppressed.
  • 0: indicates the interface is unsuppressed.
  • 1: indicates the interface is suppressed.

Impact on the System

After an interface enters the non-suppression status, the IFNET module will not report Up/Down events to the routing protocol module until the interface restores the suppression status.

Possible Causes

Cause 1:

The flap control function was configured on an interface. When alternating between Up and Down, the interface changed from the suppression status to the non-suppression status. This triggered the alarm. The threshold number of times that the interface alternates between Up and Down is configured using the control-flap command.

Procedure

  1. This alarm indicates that the interface was unstable. This is because the physical link of the interface was faulty or the link was unstable in a short period.

    • If the alarm was generated on a physical interface, check whether the physical link of the interface works properly.
    • If the alarm was generated on a sub-interface, check whether the physical link of the main interface works properly.

    • If the alarm was generated on a trunk interface, check whether the physical links of trunk member interface work properly.

  2. Collect alarm information and configuration information, and then contact technical support personnel.

IFNET_1.3.6.1.4.1.2011.5.25.41.3.42 hwIfControlFlapSuppressIPv6

Description

IFNET/4/IF_SUPPRESS_IP6:OID [OID] The IPv6 state of interface changed from unsuppress to suppress. (InterfaceIndex=[INTEGER], InterfaceExtIndex=[INTEGER], InterfaceName=[STRING], SuppressState=[INTEGER])

The IPv6 flap control function was configured on an interface. An alarm was generated when the interface changed from the suppression status to non-suppression status.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.3.42 Warning communicationsAlarm(2)

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

InterfaceIndex

Indicates the interface index.

InterfaceExtIndex

Indicates the extended interface index.

InterfaceName

Indicates the interface name.

SuppressState

Indicates whether the interface is suppressed.
  • 0: indicates the interface is unsuppressed.
  • 1: indicates the interface is suppressed.

Impact on the System

After an interface enters the non-suppression status, the IFNET module will not report Up/Down events to the routing protocol module until the interface restores the suppression status.

Possible Causes

Cause 1:

The flap control function was configured on an interface. When alternating between Up and Down, the interface changed from the suppression status to the non-suppression status. This triggered the alarm. The threshold number of times that the interface alternates between Up and Down is configured using the control-flap command.

Procedure

  1. This alarm indicates that the interface was unstable. This is because the physical link of the interface was faulty or the link was unstable in a short period.

    • If the alarm was generated on a physical interface, check whether the physical link of the interface works properly.
    • If the alarm was generated on a sub-interface, check whether the physical link of the main interface works properly.

    • If the alarm was generated on a trunk interface, check whether the physical links of trunk member interface work properly.

  2. Collect alarm information and configuration information, and then contact technical support personnel.

IFNET_1.3.6.1.4.1.2011.5.25.41.3.32 hwIfControlFlapResume

Description

IFNET/4/IF_SUPPRESS_RESUME:OID [OID] The state of interface changed from suppress to unsuppress. (InterfaceIndex=[INTEGER], InterfaceExtIndex=[INTEGER], InterfaceName=[STRING], SuppressState=[INTEGER])

The flap control function was configured on an interface. An alarm was generated when the interface changed from the suppression status to non-suppression status.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.3.32 Warning communicationsAlarm(2)

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

InterfaceIndex

Indicates the interface index.

InterfaceExtIndex

Indicates the extended interface index.

InterfaceName

Indicates the interface name.

SuppressState

Indicates whether the interface is suppressed.
  • 0: indicates the interface is unsuppressed.
  • 1: indicates the interface is suppressed.

Impact on the System

Services were restored to normal.

Possible Causes

The interface was in the suppression status. When the suppression penalty value of the interface reduced below the reuse threshold or the interface was deleted, the interface changed from the suppression status to non-suppression status. As a result, the alarm about that the interface restored the non-suppression status was generated.

Procedure

  1. This trap message is informational only, and no action is required.

IFNET_1.3.6.1.4.1.2011.5.25.41.3.43 hwIfControlFlapResumeIPv6

Description

IFNET/4/IF_SUPPRESS_RESUME_IP6:OID [OID] The IPv6 state of interface changed from suppress to unsuppress. (InterfaceIndex=[INTEGER], InterfaceExtIndex=[INTEGER], InterfaceName=[STRING], SuppressState=[INTEGER])

The IPv6 flap control function was configured on an interface. An alarm was generated when the interface changed from the suppression status to non-suppression status.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.3.43 Warning communicationsAlarm(2)

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

InterfaceIndex

Indicates the interface index.

InterfaceExtIndex

Indicates the extended interface index.

InterfaceName

Indicates the interface name.

SuppressState

Indicates whether the interface is suppressed.
  • 0: indicates the interface is unsuppressed.
  • 1: indicates the interface is suppressed.

Impact on the System

Services were restored to normal.

Possible Causes

The interface was in the suppression status. When the suppression penalty value of the interface reduced below the reuse threshold or the interface was deleted, the interface changed from the suppression status to non-suppression status. As a result, the alarm about that the interface restored the non-suppression status was generated.

Procedure

  1. This trap message is informational only, and no action is required.

IFNET_1.3.6.1.4.1.2011.5.25.41.3.33 hwExtInterfaceDelete

Description

IFNET/4/IF_DELETE :OID [OID] Interface [interface-index] was deleted. (InterfaceName=[STRING])

Interface was deleted.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.3.33 Warning communicationsAlarm(2)

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

Interface-index

Indicates the interface index.

InterfaceName

Indicates the interface name.

Impact on the System

Services will not be affected.

Possible Causes

Cause 1:

This alarm is generated when a specified interface is deleted.

Procedure

  1. This trap message is informational only, and no action is required.
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 5053

Downloads: 6

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