HOW TO SQUELCH SNMP TRAPS FOR INTERFACE TRANSITIONS ON LEAF NODES?

Transcription

1 HOW TO SQUELCH SNMP TRAPS FOR INTERFACE TRANSITIONS ON LEAF NODES? The following technote is written against Application Policy Infrastructure Controller Version 2.2(2f) Maintenance Release. The following is a use case scenario that was asked by a customer. QUESTION After looking at the Cisco Documentation and Technotes online regarding SNMP configuration for ACI, I do not see a way to suppress interface transitions for the ACI Leaf & Spine nodes using SNMP. In NXOS, we can use "no snmp trap link-status" on the interfaces. Is this possible with switches in ACI mode? ANSWER The customer wants to turn off SNMP Traps for the following OIDs. Trap OID:.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoIfExtensionMIB.ciscoIfExtension MIBNotifications.cieLinkDown snmptrapoid [OID] cielinkdown Trap OID:.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoIfExtensionMIB.ciscoIfExtension MIBNotifications.cieLinkUp snmptrapoid [OID] cielinkup In ACI, there is no equivalent CLI command "no snmp trap link-status" for individual or group of interfaces. SNMP in ACI currently does not support disabling/enabling of individual traps. By default, all supported traps are enabled. That said, there is a workaround where you can squelch the events that send the cielinkdown & cielinkup SNMP traps. Event Code Identifiers: [OID] cielinkdown EventCode = " [OID] cielinkup EventCode = " Note: This workaround only applies to the front panel ports on the "Leaf" nodes. Fabric ports and Spine ports will continue to send SNMP traps for these events. This should not be an issue since this ports should not be transitioning as often or as frequently as the Leaf front panel ports. tdeleon@cisco.com Page 1 of 7 version1

2 Steps to Squelch SNMP Traps for cielinkdown & cielinkup events The following example shows ways to you can squelch the events that send the cielinkdown & cielinkup SNMP traps for Leaf Nodes in the ACI Fabric. Sample SNMP Traps received on external data collector: To configure this workaround for squelching the events that send the cielinkdown & cielinkup SNMP traps on the front panel ports of Leaf Nodes, you will need to customize the Fabric's Access Monitioring Policy. Configuration Steps from the APIC Admin UI: Access the APIC Admin GUI. Select FABRIC -> ACCESS POLICIES. In the Policies navigation panel on the left, select and expand the MONITORING POLICIES. Select and expand the DEFAULT monitoring policy Select EVENT SEVERITY ASSIGNMENT POLICIES In the Event Severity Assignment Policies configuration panel on the right, Click on the PENCIL Icon to the right of the "unspecified" Monitoring Object. Page 2 of 7 version1

3 In the ADD/DELETE MONITORING OBJECT window, you will need to find and select: "Aggregated Interface (ethpm.aggrif)" and "Physical Interface Runtime State (ethpm) (ethpm.physif)". Click SUBMIT to save changes. Click the Monitoring Object dropdown menu and Select "Aggregated Interface (ethpm.aggrif)" and then Click on the " + " to the right to add an Event Policy. tdeleon@cisco.com Page 3 of 7 version1

4 For the new Event Policy: - Click the CODE dropdown menu and Select Event "E [portinfodown]" - Click on the " + " to the right to add another Event Policy. - Click the CODE dropdown menu and Select Event "E [portup]" tdeleon@cisco.com Page 4 of 7 version1

5 Click the Monitoring Object dropdown menu and Select "Physical Interface Runtime State (ethpm) (ethpm.physif)" and then Click on the " + " to the right to add an Event Policy. tdeleon@cisco.com Page 5 of 7 version1

6 For the new Event Policy: - Click the CODE dropdown menu and Select Event "E [portinfodown]" - Click on the " + " to the right to add another Event Policy. - Click the CODE dropdown menu and Select Event "E [portup]" At this point, the cielinkdown & cielinkup SNMP traps will be squelched. Remember once again, This workaround only applies to the front panel ports on the "Leaf" nodes. Fabric ports and Spine ports will continue to send SNMP traps for these events. This should not be an issue since this ports should not be transitioning as often or as frequently as the Leaf front panel ports. tdeleon@cisco.com Page 6 of 7 version1

7 You can test new event policies by disabling an interface on a Leaf node that is has SWITCHING STATE of "ENABLED" and an OPERATION STATE of "UP". SNMP ACI RESOURCE INFORMATION Please always check for the latest version of document before sending out to customer. Technote: SNMP in the ACI Fabric Ask the ACI Experts: SNMP in the ACI Fabric tdeleon@cisco.com Page 7 of 7 version1