Prime Infrastructure 2.1 - Fan-Failure SNMP-Trap Issue

Hello,
I am facing the following Prime Infrastructure (v2.1) issue:
- A Fan-Failure SNMP-Trap from a Cisco 3650 switch doesn't appear on Prime, but a Link-Failure from the same switch does.
- The both events appears on Prime with Syslog.
- The command "snmp-server enable traps envmon fan shutdown supply temperature status" is set up.
- The switch is in "Managed" state in PI, I have checked the ACL at the "snmp-server community" command, it is okay.
- I have set up an SNMP-Trace for the switch on PI, but only "SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex" arrived. Please find the log below.
07/02/14 12:39:53.211 TRACE [presence-9] [] Adding attributes for object Fan3KStats[151206060_,1012]
07/02/14 12:39:53.211 TRACE [presence-9] [] Index name : fanIndex
07/02/14 12:39:53.211 TRACE [presence-9] [] Index Value : 1012
07/02/14 12:39:53.211 TRACE [presence-9] [] Device MIB table index: .1012
07/02/14 12:39:53.211 TRACE [presence-9] [] MIB table row index: .1012
07/02/14 12:39:53.211 TRACE [presence-9] []     OID for : fanIndex = 1.3.6.1.2.1.47.1.1.1.1.1.1012
07/02/14 12:39:53.211 TRACE [presence-9] []     OID for : fanOperStatus = 1.3.6.1.4.1.9.9.13.1.4.1.3.1012
07/02/14 12:39:53.211 TRACE [presence-9] [] Get fragment
07/02/14 12:39:53.211 TRACE [presence-9] [] Creating PDU: Get
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.2.1.47.1.1.1.1.1.1010
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.4.1.9.9.13.1.4.1.3.1010
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.2.1.47.1.1.1.1.1.1011
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.4.1.9.9.13.1.4.1.3.1011
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.2.1.47.1.1.1.1.1.1012
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.4.1.9.9.13.1.4.1.3.1012
07/02/14 12:39:53.218 TRACE [presence-9] [] Error Status: 0
07/02/14 12:39:53.218 TRACE [presence-9] [] Error index: 0
07/02/14 12:39:53.218 TRACE [presence-9] [] SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex
07/02/14 12:39:53.218 TRACE [presence-9] []     Setting attribute: fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] []     SnmpInt Value : ?
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, storing result, class=com.cisco.server.managedobjects.bridge.Fan3KStats, attr=fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] [] SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex
07/02/14 12:39:53.218 TRACE [presence-9] []     Setting attribute: fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] []     SnmpInt Value : ?
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, storing result, class=com.cisco.server.managedobjects.bridge.Fan3KStats, attr=fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] [] SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex
07/02/14 12:39:53.218 TRACE [presence-9] []     Setting attribute: fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] []     SnmpInt Value : ?
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, storing result, class=com.cisco.server.managedobjects.bridge.Fan3KStats, attr=fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, assembling attributes
07/02/14 12:39:53.218 TRACE [presence-9] []     MIB lookup, OID for: powerSupplyIndex = 1.3.6.1.2.1.47.1.1.1.1.1
07/02/14 12:39:53.218 TRACE [presence-9] []     GetMultiAttributes needs class=com.cisco.server.managedobjects.bridge.PowerSupply3kStats, field=powerSupplyIndex
07/02/14 12:39:53.218 TRACE [presence-9] []     MIB lookup, OID for: powerSupplyOperStatus = 1.3.6.1.4.1.9.9.13.1.5.1.3
07/02/14 12:39:53.218 TRACE [presence-9] []     GetMultiAttributes needs class=com.cisco.server.managedobjects.bridge.PowerSupply3kStats, field=powerSupplyOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes invoked
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes building OIDs for next PDU
07/02/14 12:39:53.218 TRACE [presence-9] [] Adding attributes for object PowerSupply3kStats[151206060_,1009]
- The switch sends the SNMP Trap, based on the followings:
Jul 7 13:38:30 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:30 UTC: %PLATFORM_THERMAL-6-FRU_FAN_OIR: Switch 1: System fan 1 removed
Jul 7 13:38:30 UTC: %PLATFORM_THERMAL-1-FRU_FAN_NOT_PRESENT: Switch 1: System fan 1 not present
Jul 7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:30 UTC: SNMP: V2 Trap, reqid 33202, errstat 0, erridx 0
sysUpTime.0 = 576753333
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
ciscoEnvMonFanStatusEntry.3.1010 = 5
Jul 7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:30 UTC: SNMP: V2 Trap, reqid 33203, errstat 0, erridx 0
sysUpTime.0 = 576753333
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
ciscoEnvMonFanStatusEntry.3.1010 = 5
Jul 7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:30 UTC: SNMP: V2 Trap, reqid 33204, errstat 0, erridx 0
sysUpTime.0 = 576753333
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
ciscoEnvMonFanStatusEntry.3.1010 = 5
Jul 7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:30 UTC: SNMP: V2 Trap, reqid 33205, errstat 0, erridx 0
sysUpTime.0 = 576753333
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
ciscoEnvMonFanStatusEntry.3.1010 = 5
Jul 7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:45 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:51 UTC: %PLATFORM_THERMAL-6-FRU_FAN_OIR: Switch 1: System fan 1 inserted
Jul 7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:54 UTC: SNMP: V2 Trap, reqid 33206, errstat 0, erridx 0
sysUpTime.0 = 576755733
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
ciscoEnvMonFanStatusEntry.3.1010 = 1
Jul 7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:54 UTC: SNMP: V2 Trap, reqid 33207, errstat 0, erridx 0
sysUpTime.0 = 576755733
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
ciscoEnvMonFanStatusEntry.3.1010 = 1
Jul 7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:54 UTC: SNMP: V2 Trap, reqid 33208, errstat 0, erridx 0
sysUpTime.0 = 576755733
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
ciscoEnvMonFanStatusEntry.3.1010 = 1
Jul 7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:54 UTC: SNMP: V2 Trap, reqid 33209, errstat 0, erridx 0
sysUpTime.0 = 576755733
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
ciscoEnvMonFanStatusEntry.3.1010 = 1
Jul 7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
It seems like PI and the switch doesn't understand each other concerning the fan...
Thanks for any ideas, comments and feedbacks,
Csaba

I have the very same problem.
The switch has a power supply error (one of the two is down). There is the syslog message in PI about it, but no event has created, so nor alarm is there as well.
When I check the status of the switch in the Device Work Center, and choose the Environment in Device Details I can see that PI has not realized the power supply error.
However when I click on the Sync for this very device the power supply status is updated, but still no event or alarm.
This is the case with the FANs as well.

Similar Messages

Prime Infrastructure 2.0 Collection Failure for WLC 5508

Hi,
We have installed prime infrastructure 2.0 as a VM.
I added 2 WLCs (AIR-CT5508) in the device work center.
Both the WLCs are showing as "Managed" but under the collection status it says "Collection Failure".
When I hover over the message it reads:
Other Error: Wireless Controller added successfully but some tables had their records dropped as their key fields failed validation"
Any ideas?
Thanks
Satyaki

Hi Satyaki,
Try to reboot the WLC ,if possible and then check the status of the issue.
Regards-
Afroz
**Ratings Encourages Contributors ****

3750 sw is not sending SSH login failure SNMP trap

Hi experts,
I want to make my switch send trap when failed SSH login is detected. I found the "login Enhancement" feature and enabled the trap and logging for the failed attempt.
3750# sh run | in login
aaa authentication login default local
login delay 1
login on-failure
3750# sh login
     A login delay of 1 seconds is applied.
     No Quiet-Mode access list has been configured.
     All failed login is logged and generate SNMP traps.
     Router NOT enabled to watch for login Attacks
Then I enabled all the traps except the one for the syslog (because I don't want all the log messages are sent as SNMP traps...)
(config)# snmp-server enable traps
(config)# no snmp-server enable traps syslog
(config)# snmp-server host 10.1.1.1 mysnmpkey
Now when I try to login with incorrect password I do see the log but I don't receive the trap...
Nov 23 12:39:27: %SEC_LOGIN-4-LOGIN_FAILED: Login failed [user: admin] [Source: 10.1.1.1] [localport: 22] [Reason: Login Authentication Failed] at 12:39:27 EST Wed Nov 23 2011
Of course when I enable the "syslog" trap I see something but that's more just for this log message
Any idea why??
My 3750-24TS-E is running
Cisco IOS Software, C3750 Software (C3750-IPSERVICESK9-M), Version 12.2(55)SE3, RELEASE SOFTWARE (fc1)
Thanks!
Difan

Hey Smitesh thanks for the reply. However my switch doesn't support the aaa_server trap...
#snmp-server enable traps ?
auth-framework    Enable SNMP CISCO-AUTH-FRAMEWORK-MIB traps
bgp               Enable BGP traps
Mine is a 3750 switch. Is this command for routers?
Thanks,
Difan

Cisco Prime Infrastructure 1.2 and Aironet 1250 + VSS issues

Hi,
I am new to the NCS implementations and configurations. I have one very specific case with Cisco Prime Infrastructure 1.2 and autonomnous APs and several issues with Cisco VSS on 6500 switches.
So here is the version from Prime:
NCS/admin# show version
Cisco Application Deployment Engine OS Release: 2.0
ADE-OS Build Version: 2.0.1.038
ADE-OS System Architecture: x86_64
Copyright (c) 2005-2010 by Cisco Systems, Inc.
All rights reserved.
Hostname: NCS
Version information of installed applications
Cisco Prime Network Control System
Version : 1.2.1.012
IOS version on our APs (which are autonomnous) is:
AP-N-1>show ver
Cisco IOS Software, C1250 Software (C1250-K9W7-M), Version 12.4(25d)JA1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 11-Aug-11 03:23 by prod_rel_team
Well the issue what we have now is that access point has been added but its not recognized by the NCS prime. I have tried all three versions of SNMP but I get the same result. The SNMP configuration is valid since I use the same for my switching infrastructure. When I enter "debug snmp packets" and "terminal monitor" I can see the SNMP communication between Prime and Aironet 1250 which is standalone.
When I switch to Lifecycle theme and go to Operate > Device Monitor Center I see all devices I have added. The Aironet 1250 is reachable but under collection status I get Managed with Warnings. When I hover over with my mouse I get "None available".
I have successfully added my switching infrastructure in total, which is operating perfectly for Catalyst 2960/3650/3750/4500 series but for 6500 under VSS I have some warnings. The device is recognized by the system which is excellent and all is operational. I get the following errors under Collection Status:
feature_sensor
SNMP request timed out
feature_powerSupplyFanStatus-6k
SNMP request timed out
IdentityCapability
The device is unreachable.
feature_flashdevice
SNMP request timed out
sam_ipsla_feature
The device is unreachable.
What can be done to resolve these issues ? I have attached a screenshot of this particular issue. The affected access point is 172.16.165.241.
Predrag Petrovic

Hi rajeeshp,
Currently I am not allowed to upgrade it because of internal procedures involved in upgrading a specific piece of software (obtaining permissions from various departments). Is it free to upgrade from 1.2 to 1.3 or there is a specific charge for that.
Predrag Petrovic

Prime Infrastructure 2.0 - Fan Status

Hi,
I created a Custom SNMP template to check the devices' Fan status.
I deployed this template for all my devices (3750, 4510R, Nexus 7k and Nexus 5596). I noticed that is getting data for all unless Nexus 5596 ( 5.1(3)N2(1b)).
The strange is that's possible to check fan status in the Device Details. Check below
Does anybody know what's the problem???
THanks,
Patricia Oliveira

Disable the trap from the configuration on the switches you don't want to get messages from. So depending on what kind of switch it would be something like:
conf t
no snmp-server enable traps linkdown linkup
Your string may different, there are several options that can be included in this line. You may have to remove the whole line and readd it with only the options you want.
If this posts answers your question or is helpful, please consider rating it and/or marking as answered.

Docsis CMTS SNMP traps issue

Hi all ,
If anyone can help me ( maybe with config issue )
When cable modem goes offline / online i get this messages
This is happening whit any type of modem .
Does someone using traps on CMTS , any working config example ?
Cable modem goes offline
Dec 19 14:41:23.327: SNMP: V1 Trap, ent ciscoDocsExtMIB.2, addr xx.xx.xx.xx, gentrap 6, spectrap 1
docsIfCmtsCmStatusEntry.2.4475717 = H{&65
docsIfCmtsCmStatusEntry.3.4475717 = 10.5.5.87
docsIfCmtsCmStatusEntry.4.4475717 = 0
docsIfCmtsCmStatusEntry.5.4475717 = 8113
cdxCmCpeEntry.5.6.200.251.38.182.53.157 = 2885
cdxCmtsCmStatusExtEntry.1.4475717 = 1
Dec 19 14:41:23.339: SNMP: Queuing packet to xx.xx.xx.xx
Dec 19 14:41:23.339: SNMP: V1 Trap, ent ciscoDocsExtMIB.2, addr xx.xx.xx.xx, gentrap 6, spectrap 1
docsIfCmtsCmStatusEntry.2.4475717 = H{&65
docsIfCmtsCmStatusEntry.3.4475717 = 10.5.5.87
docsIfCmtsCmStatusEntry.4.4475717 = 0
docsIfCmtsCmStatusEntry.5.4475717 = 8113
cdxCmCpeEntry.5.6.200.251.38.182.53.157 = 2885
cdxCmtsCmStatusExtEntry.1.4475717 = 1
Dec 19 14:41:23.379: SNMP: Packet sent via UDP to xx.xx.xx.xx
Dec 19 14:41:23.379: SNMP: Queuing packet to xx.xx.xx.xx
Cable modem comes online
Dec 19 14:41:42.340: SNMP: V1 Trap, ent ciscoDocsExtMIB.2, addr xx.xx.xx.xx, gentrap 6, spectrap 1
docsIfCmtsCmStatusEntry.2.4475717 = H{&65
docsIfCmtsCmStatusEntry.3.4475717 = 10.5.5.87
docsIfCmtsCmStatusEntry.4.4475717 = 0
docsIfCmtsCmStatusEntry.5.4475717 = 8113
cdxCmCpeEntry.5.6.200.251.38.182.53.157 = 2885
cdxCmtsCmStatusExtEntry.1.4475717 = 12
Dec 19 14:41:42.352: SNMP: Queuing packet to xx.xx.xx.xx
Dec 19 14:41:42.352: SNMP: V1 Trap, ent ciscoDocsExtMIB.2, addr xx.xx.xx.xx, gentrap 6, spectrap 1
docsIfCmtsCmStatusEntry.2.4475717 = H{&65
docsIfCmtsCmStatusEntry.3.4475717 = 10.5.5.87
docsIfCmtsCmStatusEntry.4.4475717 = 0
docsIfCmtsCmStatusEntry.5.4475717 = 8113
cdxCmCpeEntry.5.6.200.251.38.182.53.157 = 2885
cdxCmtsCmStatusExtEntry.1.4475717 = 12
Dec 19 14:41:42.592: SNMP: Packet sent via UDP to xx.xx.xx.xx
bg-b45-c-1#scm 10.5.5.87
                                                                                 D
MAC Address    IP Address     I/F           MAC           Prim RxPwr Timing Num I
                                            State         Sid (dBmv) Offset CPE P
c8fb.26b6.359d 10.5.5.87      C5/1/3/U0     online(pt)    2885!-2.00 823    0   N
Otherwise, normally it should be like this
Dec 19 14:42:36.836: SNMP: V1 Trap, ent ciscoDocsExtMIB.2, addr 89.216.7.28, gentrap 6, spectrap 1
docsIfCmtsCmStatusEntry.2.4478568 = C8 FB 26 F8 D6 28
docsIfCmtsCmStatusEntry.3.4478568 = 10.5.26.57
docsIfCmtsCmStatusEntry.4.4478568 = 0
docsIfCmtsCmStatusEntry.5.4478568 = 0
cdxCmCpeEntry.5.6.200.251.38.248.214.40 = 5736
cdxCmtsCmStatusExtEntry.1.4478568 = 12
Dec 19 14:42:36.848: SNMP: Queuing packet to xx.xx.xx.xx
Second problem is that CMTS is not sending all trap messages when cable modem goes offline
What we lack are the messages that the modem goes offline (which are more importantly), and as far as online reaches 99% of messages. Something that we observed is that for example in the first 10 modems that we reset CMTS send traps for three only (not consecutive).After ten messsage CMTS send all of them  (the test is usually reset the modem 20-30). There is not any connection about the type of modem that sends the trap.
Suspicion fell on PRE card but the tests were tried on various (2 CMTS with pre2, 2 CMTS with pre4 and 1 CMTS pre5). and different IOS from the SCF3 - SCH1.
Config is :
interface Cable3/0
cable enable-trap cmonoff-notification
cable enable-trap cmonoff-interval 60
snmp-server trap-source Loopback0
snmp-server enable traps cable cm-onoff
snmp-server host xx.xx.xx.xx public-cmts
snmp-server host xx.xx.xx.xx public-cmts
Thanks
VZ

I looked at the trap PDUs that correspond the timestamps in the log output, and I do not see any problems. Is there additional debugging you can enable in the Smarts application that will indicate why it thinks these traps are mangled?
The traps themselves come from RME because it looks like you have enabled Inventory and Config collection failure notification, and RME cannot fetch the config from certain devices. It appears that perhaps RME is doing periodic config collection or polling around 11:30 pm when these traps start to get generated.

Ask the Expert: Cisco Prime Infrastructure - Implementation and Deployment

Welcome to the Cisco Support Community Ask the Expert conversation.
This Ask The expert Session will cover questions spanning Cisco Prime Infrastructure on Implementation and Deployment on Wired and Wireless. This will be more specific to Customer’s and Partners questions product covering PI on configuration, Features and Menu, Network Monitoring, Maps, Implementation, High Availability and Maintenance and t/s parts.
Monday, February 2nd, 2015 to Friday, February 13th, 2015
Dhiresh Yadav is a customer support engineer in High-Touch Technical Services (HTTS) handling supporting Wireless and Network Management based Cisco products and is based in Bangalore. His areas of expertise include Cisco Prime Infrastructure and Cisco Wireless products. He has over 7 years of industry experience working with large enterprise and service provider networks. He also holds CCNP (RS) and CCIE (DC) certifications.
Afroz Ahmad is a customer support engineer in High-Touch Technical Services (HTTS) handling supporting Wireless and Network Management based Cisco products and is based in Bangalore. His areas of expertise include Cisco NMS products like Prime Infrastructure, LMS, IP SLA and SNMP etc. He has over 7 years of industry experience working with large enterprise and service provider networks. He also holds CCNP (RS),CCIE (DC), and SCJP (Sun Certified Java Professional )
Vinod Kumar Arya is a customer support engineer in High-Touch Technical Services (HTTS) handling supporting Wireless and Network Management based Cisco products and is based in Bangalore. His areas of expertise include Cisco NMS products like Prime Infrastructure, LMS, IP SLA and SNMP etc. He has over 8 years of industry experience working with large enterprise and service provider networks. He also holds VCP 5 and RHCE certifications.
** Remember to use the rating system to let the experts know you have received an adequate response.**
Because of the volume expected during this event, the experts might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure community, > Network Management, shortly after the event. This event lasts through February 13th 2015. Visit this forum often to view responses to your questions and those of other Cisco Support Community members.

Hello Wilson,
Thanks for joining us.
1841 should just work fine for net flow . Hope you have a valid "PI Assurance license" installed on the server.
"PI Assurance license" is required for "net-flow" feature
Devices supporting Netflow in PI ::
1400, 1600, 1700 & 1800
2500, 2600 & 2800
3600, 3700, 3750 & 3800
4500 & 4700
AS5300 & 5800
7200, 7300, 7400 & 7500
Catalyst 4500 ASCI
Catalyst 5000, 6500, & 7600 ASCI
ESR 10000 ASCI
GSR 12000 ASCI
Cisco IOS Software Release Version
Supported Cisco Hardware Platforms
11.1CA, 11.1CC
Cisco 7200 and 7500 series, RSP 7200 series
12.0
Cisco 1720, 2600, 3600, 4500, 4700, AS5800
RSP 7000 and 7200 series
uBR 7200 and 7500 series
RSM series
12.0T, 12.0S
Cisco 1720, 2600, 3600, 4500, 4700, AS5800
RSP 7000 and 7200 series
uBR 7200 and 7500 series
RSM series, MGX8800RPM series, and BPx8600 series
12.0(3)T, 12.0(3)S
Cisco 1720, 2600, 3600, 4500, 4700, AS5300, AS5800
RSP 7000 and 7200 series
uBR 7200 and 7500 series
RSM series, MGX8800RPM series, and BPx8650 series
12.0(4)T
Cisco 1400, 1600, 1720, 2500, 2600, 3600, 4500,
4700, AS5300, AS5800
RSP 7000 and 7200 series
uBR 7200 and 7500 series
RSM series, MGX8800RPM series, and BPx8650 series
12.0(4)XE
Cisco 7100 series
12.0(6)S
Cisco 12000 series
NetFlow is also supported by these devices Cisco 800, 1700, 1800, 2800, 3800, 6500, 7300, 7600, 10000, CRS-1 and these Catalyst series switches: 45xx, 55xx, 6xxx.
NetFlow export is also supported on other Cisco switches when using a NetFlow Feature Card (NFFC) or NFFC II and the Route Switch Module (RSM), or Route Switch Feature Card (RSFC). However, check whether version 5 is supported, as most switches export version 7 by default.
You can check the below steps to diagnose the issue::
To verify that NetFlow is exported from a device to PI, follow the steps below:
1)   Browse to Administration > Data Sources page. Check the value in column ‘Last Active Time’ for the ‘Device Data Sources’ table. If the table is empty or the value does not represent recent time, then
it is possible that the device is not exporting NetFlow or PI Assurance license is not applied / expired.
2)   Login to PI console ( via SSH) as root user and run the command:
                netstat –an | grep 9991 – Output of this should be like : udp        0      0 :::9991         :::*
                Check the firewall settings on PI server using the command: firewall -L
1)   Check the configuration on an IOS / IOS –XE device. Run the commands
a)   sh running-config | inc destination
1)   This should list the IP address of the PI SERVER ( along with other outputs if any)
b)   sh running-config | inc 9991
1)   This should list at least one entry.
c)   If the above are fine, then verify that the flow monitor, flow exporter and the flow records are correctly configured on the device.
Refer to the URLs below to configure NetFlow export.
http://preview.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/2.0/user/guide/setup_monitor.html#wp1056427
Thanks-
Afroz
***Ratings Encourages Contributors ****

Cisco Prime Infrastructure 1.4 SNMP Traps are not converted into Alarms

Hi everybody,
I just configured SNMP Traps on a Cisco Catalyst 3750-x to send to our Cisco Prime Infrastructure 1.4 Appliance.
Now I forced the Switch to send some traps (Power off a Power Supply, Interface errdisable). The only events I see in Alarms & Events on PI is the same information message everytime:
Configuration management event has been recorded in ccmHistoryEventTable.
I think the forced traps should be converted into alarms? Why can't I see them?
Thanks,
Marc

Ok, I started debugging as you said. I get the following output:
Mar 13 09:28:13.711: SNMP: V2 Trap, reqid 11689, errstat 0, erridx 0
sysUpTime.0 = 198609846
snmpTrapOID.0 = ciscoSyslogMIB.2.0.1
clogHistoryEntry.2.1688 = PM
clogHistoryEntry.3.1688 = 5
clogHistoryEntry.4.1688 = ERR_RECOVER
clogHistoryEntry.5.1688 = Attempting to recover from bpduguard err-disable state on Gi1/0/13
clogHistoryEntry.6.1688 = 198609844
Mar 13 09:28:13.737: SNMP: Queuing packet to xx.xx.xx.xx
Looks like the Switch is sending SNMP Traps from the ciscoSyslogMIB. Is this why PI can't show the Traps and convert it into a alarm?
After this test I configured logging (syslog) to the PI. Now the errors are showed but still not converted into alarms. I just want to be notified by email when such errors occurs.
Thanks,
Marc

Cisco Prime Infrastructure 2.0 - no traps/info are pushed from devices

Good evening,
I have setup Cisco Prime Infrastructure 2.0 and, though I have added manually my 4 network cores as devices without any problem, I can't get a single trap or a single SNMP information to be pushed into my Cisco Prime Infra.
Here is my SNMP config on my core :
snmp-server user *edited* *edited* v3
snmp-server group *edited* v3 noauth notify *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF0F
snmp-server community *edited* RO
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
snmp-server enable traps flowmon
snmp-server enable traps transceiver all
snmp-server enable traps call-home message-send-fail server-fail
snmp-server enable traps tty
snmp-server enable traps rf
snmp-server enable traps memory
snmp-server enable traps cpu_threshold
snmp-server enable traps eigrp
snmp-server enable traps ospf state-change
snmp-server enable traps ospf errors
snmp-server enable traps ospf retransmit
snmp-server enable traps ospf lsa
snmp-server enable traps ospf cisco-specific state-change nssa-trans-change
snmp-server enable traps ospf cisco-specific state-change shamlink interface
snmp-server enable traps ospf cisco-specific state-change shamlink neighbor
snmp-server enable traps ospf cisco-specific errors
snmp-server enable traps ospf cisco-specific retransmit
snmp-server enable traps ospf cisco-specific lsa
snmp-server enable traps flex-links status
snmp-server enable traps fru-ctrl
snmp-server enable traps entity
snmp-server enable traps ethernet cfm cc mep-up mep-down cross-connect loop config
snmp-server enable traps ethernet cfm crosscheck mep-missing mep-unknown service-up
snmp-server enable traps ether-oam
snmp-server enable traps aaa_server
snmp-server enable traps flash insertion removal
snmp-server enable traps l2tc threshold sys-threshold
snmp-server enable traps power-ethernet police
snmp-server enable traps rep
snmp-server enable traps vswitch dual-active vsl
snmp-server enable traps udld link-fail-rpt status-change
snmp-server enable traps vtp
snmp-server enable traps vlancreate
snmp-server enable traps vlandelete
snmp-server enable traps auth-framework sec-violation
snmp-server enable traps dot1x auth-fail-vlan guest-vlan no-auth-fail-vlan no-guest-vlan
snmp-server enable traps envmon fan shutdown supply temperature status
snmp-server enable traps entity-diag boot-up-fail hm-test-recover hm-thresh-reached scheduled-test-fail
snmp-server enable traps port-security
snmp-server enable traps ethernet evc status create delete
snmp-server enable traps energywise
snmp-server enable traps ipsla
snmp-server enable traps vstack
snmp-server enable traps bfd
snmp-server enable traps bgp
snmp-server enable traps bulkstat collection transfer
snmp-server enable traps cef resource-failure peer-state-change peer-fib-state-change inconsistency
snmp-server enable traps config-copy
snmp-server enable traps config
snmp-server enable traps config-ctid
snmp-server enable traps event-manager
snmp-server enable traps hsrp
snmp-server enable traps ipmulticast
snmp-server enable traps isis
snmp-server enable traps msdp
snmp-server enable traps pim neighbor-change rp-mapping-change invalid-pim-message
snmp-server enable traps bridge newroot topologychange
snmp-server enable traps stpx inconsistency root-inconsistency loop-inconsistency
snmp-server enable traps syslog
snmp-server enable traps isakmp policy add
snmp-server enable traps isakmp policy delete
snmp-server enable traps isakmp tunnel start
snmp-server enable traps isakmp tunnel stop
snmp-server enable traps ipsec cryptomap add
snmp-server enable traps ipsec cryptomap delete
snmp-server enable traps ipsec cryptomap attach
snmp-server enable traps ipsec cryptomap detach
snmp-server enable traps ipsec tunnel start
snmp-server enable traps ipsec tunnel stop
snmp-server enable traps ipsec too-many-sas
snmp-server enable traps errdisable
snmp-server enable traps ethernet cfm alarm
snmp-server enable traps vlan-membership
snmp-server enable traps mac-notification change move threshold
snmp-server enable traps vrfmib vrf-up vrf-down vnet-trunk-up vnet-trunk-down
snmp-server host *ip-address-edited* version 3 noauth *edited*
Basically all traps are enabled but absolutely nothing is showing up in my Prime Infra except that my 4 devices are "Reachable".
Here is a show snmp on the same device :
sh snmp
Chassis: *S/N Edited*
38554534 SNMP packets input
    0 Bad SNMP version errors
    14 Unknown community name
    0 Illegal operation for community name supplied
    0 Encoding errors
    38453185 Number of requested variables
    0 Number of altered variables
    17790703 Get-request PDUs
    20583581 Get-next PDUs
    0 Set-request PDUs
    0 Input queue packet drops (Maximum queue size 1000)
38490708 SNMP packets output
    0 Too big errors (Maximum packet size 1500)
    0 No such name errors
    0 Bad values errors
    0 General errors
    38371069 Response PDUs
    13 Trap PDUs
SNMP global trap: enabled
SNMP agent enabled
SNMP logging: enabled
    Logging to *edited*, 0/10, 13 sent, 0 dropped.
Can anyone point out what is wrong or missing in my configuration? I can't seem to single it out myself.
Thanks
Jeremy

Hi Jeremy,
SNMP traps are shown in the events and alerts section of PI.
SNMP config looks fine. Can you run the SNMP debug (debug snmp packets ) .check the logs and see if the device is actually sending the TRAPS to the PI server.
Thanks-
Afroz
[Do rate the useful post]
****Ratings Encourages Contributors ****

Prime Infrastructure 2.0: Running an inventory sync removes "snmp-server location" in running-config

Hello,
we're running Prime Infrastructure 2.0 (version VA-2.0.0.0.294).
I was scared as I figured out one hour ago that running an inventory sync (Device Work Center) removes the command snmp-server location and adds the command snmp-server host "PI-ip address" "snmp rw community" in the running-config.
Has someone the same behaviour or can reenact this scenario?!
Can someone imagine that this behaviour has something to do with a configuration setting in PI?
I'm perplexed and got gray hair now.
Thank you for your answers or tips.
Bastian

Hello Rob,
I just successfully installed the patch. The snmp-server location is not touched anymore while running a inventory job.
But PI still enters this string in the running-configuration:
snmp-server host "PI-IP address" " our snmp RW community- string"
although there already exists the entry:
snmp-server host "PI-IP address" version 2c "community-string (not the snmp rw-community-string)"
Do you or anyone else has the same behaviour that PI adds automaically himself as snmp trap receiver with the SNMP-RW community?
Regards
Bastian

Cisco Prime SNMP Traps Best Pratice

The Cisco Prime documentation recommends configuring switches to send SNMP traps. However it does not give any more details.
I was wondering what sorts of SNMP traps people in the community are using with Cisco Prime 2.1. I'm looking for some sort of best practice or for an idea of what traps would be the most useful to configure on the switches, to send to Prime.

Hi ,
Snmp traps need to be configured only on device end , there is no config need to be done on PI.
you can enable all the traps that you want. for e.g
snmp-server enable traps syslog
snmp-server enable traps ipsec start stop
snmp-server enable traps memory-threshold
snmp-server enable traps interface-threshold
snmp-server enable traps connection-limit-reached
snmp-server enable traps cpu threshold rising
etc......
and you can monitor then in PI (Administration > System Settings > Severity Configuration, Link down)
check the below link as well:
https://supportforums.cisco.com/discussion/11919481/prime-infrastructure-20-link-status-alarms
Thanks-
Afroz
***Ratings Encourages Contributors ***

Cisco Prime SNMP trap logs

Hi
In Cisco Prime Infrastructure, where can we find the snmp trap logs and can we do the snmp polling through webconsole, please suggest how we can troubleshoot if the device is not reachable, do we need to login through ssh and check or is there any other options available.
Can we find out the configuration details of the specific device, how we can do it.
Please advice

Hi abhishek ,
First of al you have to check on your devices SNMP is enable or not , its all depending on SNMP configuration , if possible check the running config , and paste the running configration , to solve your issue
rate it

How to enable the "SNMP TRAP" Funcation in Prime Infrasructure 2.0 for receiveing the Third Party Device's SNMP TRAP

I already uploaded the third party device's MIB to PI2.0, but could not recive the third party device's SNMP TRAP properly .
what do I need check for the PI ? or what do I need to setup for the PI?
Thanks

Duplicate post of :
https://supportforums.cisco.com/discussion/12148626/how-enable-snmp-trap-funcation-prime-infrasructure-20-receiveing-third-party
-Thanks
Vinod

Regarding SNMP trap on Backup Unity connection failure

Hi,
if backup of Unity connection failed, would a backup failure produce an SNMP trap?
thanks,
Kamran

RTMT has alerts for DRF backup failures... and can be set to trigger emails, but I am not aware of any SNMP Traps generated by DRS Backup failing.
Kind regards,
Craig

Prime Infrastructure 2.2 snmp-server location

We have implemented Cisco Prime Infrastructure 2.2 in our facility. We have each switch loaded in with an "snmp-server location" set for the switches for easier identification and quicker troubleshooting. We would like that location to show in the network topology map as well as in the email alerts it sends if one of those switches goes down. Is this something I am overlooking, and if so, can someone please explain to me how to make this happen?

Hi William,
snmp-server location is synced from the devices & also the info available in various report.
But, if i'm not wrong you want to customize the e-mail body of notifications sent out from the prime.
This functionality is no where discussed in PI user guide & i'm afraid not possible as of now.
Also, there's bug related to snmp-server location even retrieving it from the reports
CSCuj09556 : PI 2.0 corrupts device config by doing snmp set for location after sync
https://tools.cisco.com/bugsearch/bug/CSCuj09556
CSCuo16889 : PI 2.0 - Does not poll sysLocation for 3750 device
https://tools.cisco.com/bugsearch/bug/CSCuo16889
- Ashok
Please rate the post or mark as correct answer as it will help others looking for similar information

Prime Infrastructure 2.1 - Fan-Failure SNMP-Trap Issue

Similar Messages

Maybe you are looking for