< Home

MBR_1.3.6.1.4.1.2011.5.25.327.31.3.2.5 hwUniMbrAsServiceAbnormal

Description

MBR/4/ASSERVICEABNORMAL: OID [oid] The service abnormal on AS. (ASDeviceName=[STRING], ASIndex=[INTEGER], Description=[STRING])

Services on an AS become abnormal.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.327.31.3.2.5

Warning

qualityOfServiceAlarm (3)

Parameters

Name Meaning

oid

Indicates the ID of the alarm MIB object.

ASDeviceName

Indicates the name of as AS.

ASIndex

Indicates the index of an AS.

Description

Indicates the alarm description of an AS.

Impact on the System

Some commands delivered from the parent to this AS do not take effect. The AS needs to return the service error information to the parent and corresponding alarms need to be generated on the parent.

Possible Causes

  • The Description field in the alarm information describes MAC services:

    • Description=MAC address information. (Information=Type-Ifindex-Vlaninvalid-Vlanid-Mac-address).

      The MAC address changed.

    • Description=MAC move detected. (VlanId=[INTEGER], MacAddress=[STRING], Original-Port=[STRING], Flapping port=[STRING] and [STRING]).

      The MAC address in the VLAN flapped.

    • Description=MAC move detected. (VSI-Name=[STRING], MacAddress=[STRING], Original-Port=[STRING], Flapping port=[STRING]).

      The MAC address in the VSI flapped.

    • Description=MAC move detected. (Bridge-domain ID=[INTEGER], Original-port=[STRING], Flapping-port 1=[STRING], Flapping-port 2=[STRING], MacAddress=[STRING]).

      The MAC address in the BD domain flapped.

    • Description=The port was removed from the VLAN due to MAC flapping. (InterfaceName=[STRING], VLAN=[INTEGER]).

      MAC address flapping caused the port to be removed from the VLAN.

    • Description=The port is added to the VLAN again after it was removed from the VLAN due to MAC flapping. (InterfaceName=[STRING], VLAN=[INTEGER]).

      The port that was removed from the VLAN due to MAC flapping is added to the VLAN again.

  • The Description field in the alarm information describes port security services:

    • Description=The number of sticky or secure MAC address reaches the max.

      The number of sticky or secure MAC addresses learned by the device reached the maximum value.

    • Description=The port received an insecure MAC address. (MacAddress=[STRING], VLAN=[INTEGER], InterfaceName=[STRING], PortStatus=[INTEGER] (1:restrict;2:protect;3:error-down)).

      The port received packets with a new MAC address after the number of secure MAC addresses on the port exceeded the limit.

    • Description=The port received a packet with a flapping static MAC. (MacAddress=[STRING], VLAN=[INTEGER], InterfaceName=[STRING]).

      The source MAC address in the packet received by the interface already exists in the static MAC address table of another interface.

  • The Description field in the alarm information describes store control services:

    • Description=Storm-control alarm. (IfIndex=[STRING], IfName=[STRING], Action=[STRING], Interval=[STRING], Status=[STRING]).

      After store control was configured, the rate of broadcast, unknown multicast, and unknown unicast packets received on the interface within a detection interval exceeded the configured maximum limit.

  • The Description field in the alarm information describes voice VLAN services.

    • Description=Configure the organizationally unique identifier (OUI) address of the voice VLAN: MAC address=[STRING], mask=[STRING] failed because of no enough resources or hash collision.

      The voice-vlan mac-address mac-address mask oui-mask command used to configure an OUI for a voice VLAN does not take effect.

    • Description=Configure the 802.1p priority or DSCP value for a voice VLAN: 802.1p=[STRING], DSCP=[STRING] failed because of no enough resources or hash collision.

      The voice-vlan remark { 8021p 8021p-value| dscp dscp-value } command used to configure the 802.1p priority or DSCP priority for a voice VLAN does not take effect.

    • Description=Configure VLAN [STRING] as a voice VLAN and enable the voice VLAN function on [STRING] failed because of no enough resources or hash collision.

      The voice-vlan vlan-id enable [ include-untagged | include-tag0 ] command used to enable a voice VLAN does not take effect.

    • Description=Enable CDP-compatible LLDP on [STRING] failed because of no enough resources or hash collision.

      The voice-vlan legacy enable command used to configure a voice VLAN to be compatible with CDP does not take effect.

    • Description=Configure the voice VLAN to work in auto mode on [STRING] failed because of no enough resources or hash collision.

      The voice-vlan mode auto command used to configure a voice VLAN to work in automatic mode on an interface does not take effect.

    • Description=Configure the voice VLAN to work in manual mode on [STRING] failed because of no enough resources or hash collision.

      The voice-vlan mode manual command used to configure a voice VLAN to work in manual mode on an interface does not take effect.

    • Description=Enable the secure mode of the voice VLAN on [STRING] failed because of no enough resources or hash collision.

      The voice-vlan security enable command used to configure a voice VLAN to work in security mode does not take effect.

    • Description=Disable the secure mode of the voice VLAN on [STRING] failed because of no enough resources or hash collision.

      The undo voice-vlan security enable command used to configure a voice VLAN to work in normal mode does not take effect.

    • Description=Configure [STRING] to increase the priority of voice packets based on MAC addresses failed because of no enough resources or hash collision.

      The voice-vlan remark-mode mac-address command used to configure the switch to increase the priority of voice packets based on MAC addresses does not take effect.

    • Description=Configure [STRING] to increase the priority of voice packets based on VLAN IDs failed because of no enough resources or hash collision.

      The voice-vlan remark-mode vlan command used to configure the switch to increase the priority of voice packets based on VLAN IDs does not take effect.

    • Description=Add [STRING] to Eth-Trunk [STRING] failed because of no enough resources or hash collision.

      Failed to add an interface to an Eth-Trunk.

  • The Description field in the alarm information describes SACL services.

    • Description=Fail to apply SACL 'traffic-filter inbound acl [STRING]', insufficient rule resource on slot [STRING] globally.

      ACL resources are insufficient.

    • Description=Fail to apply SACL 'traffic-filter inbound acl [STRING]', insufficient slice resource on slot [STRING] globally.

      Slice resources are insufficient.

    • Description=Fail to apply SACL 'traffic-limit inbound acl [STRING]', insufficient counter resource on slot [STRING] globally.

      Counter resources are insufficient.

    • Description=Fail to apply SACL 'traffic-limit inbound acl [STRING]', insufficient meter resource on slot [STRING] globally.

      Meter resources are insufficient.

    • Description=Fail to apply SACL 'traffic-filter inbound acl [STRING]', insufficient UDF resource on slot [STRING] globally.

      UDF resources are insufficient.

    • Description=Fail to apply SACL 'port add-tag acl [STRING]', there is conflict between action "remark vlan-id" and "add-tag" on interface [STRING] of slot [STRING].

      A configuration conflict occurs.

  • The Description field in the alarm information describes MQC services.

    • Description=Add rule failed. Insufficient rule resource in policy [STRING] classifier [STRING] behavior [STRING] acl [STRING], rule [STRING] on slot [STRING] globally.

      ACL resources are insufficient.

    • Description=Add rule failed. Insufficient slice resource in policy [STRING] classifier [STRING] behavior [STRING] acl [STRING], rule [STRING] on slot [STRING] globally.

      Slice resources are insufficient.

    • Description=Add rule failed. Insufficient counter resource in policy [STRING] classifier [STRING] behavior [STRING] acl [STRING], rule [STRING]on slot [STRING] globally.

      Counter resources are insufficient.

    • Description=Add rule failed. Insufficient meter resource in policy [STRING] classifier [STRING] behavior [STRING] acl [STRING], rule [STRING] on slot [STRING] globally.

      Meter resources are insufficient.

    • Description=Add rule failed. Insufficient UDF resource in policy [STRING] classifier [STRING] behavior [STRING] acl [STRING], rule [STRING] on slot [STRING] globally.

      UDF resources are insufficient.

    • Description=Add rule failed, remark vlan can not be configured together with add-tag in current view or direction about policy [STRING], class [STRING], behavior [STRING] on slot [STRING] globally.

      A configuration conflict occurs.

Procedure

  1. Determine the service module to which the alarm is related based on the Description field in this alarm.

    • The alarm is related to MAC services.
      • If the MAC address changed, rectify the fault according to hwMacTrapAlarm.
      • If the MAC address in a VLAN flapped, rectify the fault according to hwMflpVlanAlarm.
      • If the MAC address in a VSI flapped, rectify the fault according to hwMflpVsiAlarm.
      • If the MAC address in a BD domain flapped, rectify the fault according to hwMflpBdAlarm.
      • If the port was removed from the VLAN due to MAC address flapping, rectify the fault according to hwMflpQuitVlanAlarm.
      • The port that was removed from the VLAN due to MAC flapping is added to the VLAN again. This alarm is informational, and no action is required.
    • The alarm is related to port security services.
      • If the number of sticky or secure MAC addresses learned by the device reached the maximum value, rectify the fault according to hwPortStickyReachMaxAlarm.
      • If the port received packets with a new MAC address after the number of secure MAC addresses on the port exceeded the limit, rectify the fault according to hwPortSecRcvInsecurePktAlarm.
      • If the source MAC address in the packet received by the interface already exists in the static MAC address table of another interface, rectify the fault according to hwPortsecStaticFlpAlarm.
    • If the alarm is related to storm control services, run the display storm-control [ interface interface-type interface-number ] command to check the storm control configuration on the specified interface. Determine whether to cancel or change the storm control configuration based on service requirements. To change the configuration or threshold, run the storm-control command.
    • If the alarm is related to voice VLAN services, modify the configuration command based on the alarm cause. For example, in case of "Description=Enable CDP-compatible LLDP on [STRING] failed because of no enough resources or hash collision", you can run the undo voice-vlan legacy enable command.
    • If the alarm indicates insufficient resources of the SACL or MQC service, run the display acl resource command to check resources and then delete unnecessary services to release ACL resources. For example, in case of "Description=Fail to apply SACL 'traffic-limit inbound acl [STRING]', insufficient counter resource on slot [STRING] globally", you can run the display acl resource command to check the Counter field, delete unnecessary services to release ACL resources, and then reconfigure the command that needs to be delivered.
    • If the alarm is related to the SACL or MQC configuration, modify the configuration based on the specific alarm information. For example, in case of "Description=Add rule failed, remark vlan can not be configured together with add-tag in current view or direction about policy [STRING], class [STRING], behavior [STRING] on slot [STRING] globally", modify the configuration based on the alarm information that remark vlan-id vlan-id and add-tag vlan-id vlan-id cannot be configured together.

      There are a large number of SACL or MQC-related configuration conflict alarms. For details about the troubleshooting procedure, see the specific alarm description.

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

Related Information

None

Parent Topic: MBR
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >