Cisco Prime Infrastructure 2.1 error-disable alert

[kcchankeith]

We have a cisco PI 2.1 managing switches and a lot of switchports have BPDUGuard enabled. When occur error-disable , request send email notification to administrator .

By default, when a port of a switch goes down, the Prime generates alarm for that. (this is a problem, because every laptop disconnection will generate alarm for administrator)

Can i change the alert just for error-disable and how to ?

Thanks

[Moin Ilyas]

Hide acknowledged alarms—When the check box is selected, Acknowledged alarms do not appear on the Alarm Summary page. This option is enabled by default. Emails are not generated for acknowledged alarms, regardless of severity change.

Please refer: http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-0/administrator/guide/PIAdminBook/maint_network_health.html#pgfId-1062413

Hope that helps.

Regards,

Moin.

[kcchankeith]

Hi Moin,

Thanks your support.

I concern that is a lot of email generate to administrator like below,

========================================================================

Virtual Domain: ROOT-DOMAIN 

PI has detected one or more alarms of category Switches and Hubs and severity Critical in Virtual Domain ROOT-DOMAIN for the following items: 

1. Message: Port 'GigabitEthernet1/0/1' is down on device '192.168.98.186'. 
2. Message: Port 'GigabitEthernet1/0/10' is down on device '192.168.98.186'. 
3. Message: Port 'GigabitEthernet1/0/11' is down on device '192.168.98.186'. 

========================================================================

I just interest that which ports down by error-disable features. Could you help for this?

Thanks

Keith

[mohanak]

Causes of Errdisable

This feature was first implemented to handle special collision situations in which the switch detected excessive or late collisions on a port. Excessive collisions occur when a frame is dropped because the switch encounters 16 collisions in a row. Late collisions occur after every device on the wire should have recognized that the wire was in use. Possible causes of these types of errors include:

• A cable that is out of specification (either too long, the wrong type, or defective)

• A bad network interface card (NIC) card (with physical problems or driver problems)

• A port duplex misconfiguration

  A port duplex misconfiguration is a common cause of the errors because of failures to negotiate the speed and duplex properly between two directly connected devices (for example, a NIC that connects to a switch). Only half-duplex connections should ever have collisions in a LAN. Because of the carrier sense multiple access (CSMA) nature of Ethernet, collisions are normal for half duplex, as long as the collisions do not exceed a small percentage of traffic.

There are various reasons for the interface to go into errdisable. The reason can be:

• Duplex mismatch

• Port channel misconfiguration

• BPDU guard violation

• UniDirectional Link Detection (UDLD) condition

• Late-collision detection

• Link-flap detection

• Security violation

• Port Aggregation Protocol (PAgP) flap

• Layer 2 Tunneling Protocol (L2TP) guard

• DHCP snooping rate-limit

• Incorrect GBIC / Small Form-Factor Pluggable (SFP) module or cable

• Address Resolution Protocol (ARP) inspection

• Inline power

Note: Error-disable detection is enabled for all of these reasons by default. In order to disable error-disable detection, use the no errdisable detect cause command. The show errdisable detect command displays the error-disable detection status.