Disable snmp trap link-status only on access ports?

Hello,
I am searching for a way to disable the snmp trap link-status only on access ports.
The problem is that we have a lot of new devices which have no port scheme, so I can't say that everytime the router uplink on a switch is on port X or Y.
So I have to figure out where my uplinks to routers, accesspoints or other switches are and set all other ports to
no snmp trap link-status
no logging event link-status
spanning-tree portfast
Campus Manager knows the uplinks between the devices, but there is no way to perform such a change, right?
The next problem is, that there is nothing configured on the ports, so I can't search for a string by using compliance check in RME.
Is there any posibility to get the topology informations from CM together with the configuration feature from RME?
Thanks a lot!
Sven

Hello,
thanks for your reply.
I thought of something like you wrote...
There is a best practice report for disabling cdp on access ports.
Creating this report for a switch and click on "fix" the CM will configure the command "no cdp enable" on every access port.
So I will have a difference between uplinks and access ports.
The problem with that solution is, that I can't fix all my switches with one job.
And with >1000 switches it is not really possible to click every device.
Any further advice?
Thanks!
Sven

Similar Messages

SNMP Traps is not being sent clear event when DB is UP

Test Traps everything else is also coming fine. Listener, Database Errors, down etc are all coming in fine thru' SNMP. SNMP traps and OEM all working ok. Question is for database up event there is no CLEAR event being sent. Is there anything else that needs to be configured?
SQL> SELECT owner, name, enqueue_enabled, dequeue_enabled FROM dba_queues
2 WHERE name like '%NOTIFY%';
OWNER NAME ENQUEUE DEQUEUE
SYS AQ_PROP_NOTIFY YES YES
SYSMAN AQ$_MGMT_NOTIFY_QTABLE_E NO NO
SYSMAN MGMT_NOTIFY_Q YES YES
SYSMAN AQ$_MGMT_NOTIFY_INPUT_QTABLE_E NO NO
SYSMAN MGMT_NOTIFY_INPUT_Q YES YES

Hello,
Under interface for specific interface: snmp trap link-status
http://www.cisco.com/en/US/docs/ios/12_0/configfun/command/reference/frmonitr.html#wp1023375
Also in newer IOS
The snmp-server enable traps snmp [ linkup] [linkdown] form of this command replaces the snmp trap link-status interface configuration mode command.
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094a05.shtml
HTH
Saju
Pls rate helpful posts

SCOM 2012 SP1 - Show on event view all snmp trap (SNMP monitoring work)

Hello everybody,
Sorry for my english, I write normaly in french, but we have more result in english.
I have a problem with SCOM 2012. I try to catch all snmp traps sended by a 2960 CISCO switch on a EventView with a specific rule (Authoring->Rule->Collection Rules -> Event Based -> SNMP Trap (Event) based on the object target "Node")
I creat a specific management pack juste for the rule and the views.
SNMP Monitoring - CISOC 2960 => It's OK, I can have the processor state, utilization, etc ...
SNMP Monitoring Ubuntu computer => It's OK, I can have all the state I want.
SNMP Traps => The switch or the computer send traps over the network, and I can see in wireshark, the server receive the traps
SNMP Service (Windows service) => Disabled
SNMP trap (Windows service) => Disabled
Health Service (Windows service) => Enabled
Port 162 UDP => Open and listenning by the MonitoringHost.exe
Firewall rules => Everythinks is OK
SNMP Trap send version is => 2c
SNMP Monitoring device version is => 2c
I try too many of solution on different web site like :
http://scom-2012.blogspot.ch/2012/07/setting-up-snmp-monitoring-in-scom-2012.html
http://social.technet.microsoft.com/Forums/systemcenter/en-US/731661b9-10a1-4d3f-ba83-8e84d25ab760/event-collection-for-network-devices-scom-2012
http://social.technet.microsoft.com/Forums/systemcenter/en-US/a15bce49-fb62-4fd4-93cf-f87c3b734d58/snmp-trap-based-monitoring?forum=operationsmanagergeneral
http://social.technet.microsoft.com/Forums/systemcenter/en-US/41f5b6ef-c8b9-461d-bdcb-81fde5a89f50/scom-2012-unable-to-monitor-snmp-traps?forum=operationsmanagergeneral
http://social.technet.microsoft.com/Forums/systemcenter/en-US/4051fbd1-06f1-49e0-9ad4-4cbe4d2d7d4d/discover-windows-computer-as-network-device-w-snmp?forum=operationsmanagerauthoring
http://technet.microsoft.com/en-us/library/hh563870.aspx
http://social.technet.microsoft.com/Forums/en-US/cad1d3f9-594f-4f06-a5aa-660ccc2e9192/snmp-trap-based-monitoring-in-scom-2012-sp1?forum=operationsmanagerauthoring
http://social.technet.microsoft.com/Forums/en-US/41f5b6ef-c8b9-461d-bdcb-81fde5a89f50/scom-2012-unable-to-monitor-snmp-traps?forum=operationsmanagergeneral
http://social.technet.microsoft.com/Forums/en-US/e05a1c8f-7280-4f80-86cf-aabb4269bb87/scom-2012-customizing-snmp-trap-event-data?forum=operationsmanagergeneral
http://social.technet.microsoft.com/Forums/en-US/6826f6a6-bbc3-444b-9b18-288d7fedac3e/scom-unable-to-monitor-snmp-traps?forum=operationsmanagergeneral
http://social.technet.microsoft.com/Forums/en-US/7cd1571a-d292-4efc-9921-5a068f6f1691/scom-2012-sp1-ur2-snmp-monitoring?forum=operationsmanagermgmtpacks
Do you know a workaround? Or a different way to catch all the traps from a network device and show them (traps) on a event views.
Thank you in advance.
KimBaxZ
Computer expert system technology

Hello Yan Li,
I read your link, and I found this :
The network devices must be discovered and registered as ICMPSNMP devices.
And when I make the dicovery the first time, ICMP doesn't work, so I put only SNMP. This morning I tried with ICMP and SNMP, but the same problem come to me. And I found the rootcause of the problem with this post : http://www.code4ward.net/main/Blog/tabid/70/EntryId/105/Troubleshooting-Network-Discovery-in-SCOM-2012.aspx
I allowed the SNMP service, ping, and Health Service, just after I try a second time to dicover my device and it's work (ICMP and SNMP).
I recreat all my management pack and the rule. And now it's work! Thank you very much for your help!!
Have a nice day
Best regards
KimBAxZ
Computer expert system technology

SNMP traps with WLC 4402

Currently using WLC 4402 with about a dozen WAPs. I would like to start logging some messages to troubleshoot some association issues. The syslog does not seem adequate for this the issues I am having. I noticed the default SNMP traps but is only holds 255 traps. I have tried to setup an SNMP server to get the traps but I get no data, only OID values. I was successful in getting the MIBs for the OIDs but still not all the data that I see on the brief traps screen.

Hi,
I have tried it with solarwinds and works fine for me. Talking about the traps. But they are too many.
The OID is : 1.3.6.1.4.1.14179.1.1.2.4.1.22
snmp info for polling:
MIB Value Type: Raw Value
Format: None
SNMP Get Type: Get Table
Polling Type: node
On WLC go to Managemnet (top TAB)
Right hand select > SNMP > Traps Control.
In this menu select what traps to need to be logged.
These traps will be shows on the oid polled.

Link down and Link Up Snmp trap C#

Hi i've configure my cisco router to receive the SNMP traps if the link goes up or down. However i found out that when i plugged out the cable i'm not receiving any link down on the network management system. Until i plugged in again the link will then show up or down state. May i know whats the reason why i can't receive the link down when i plugged out my cable?

If your router has only fa0/0 as active interface, then this would be the interface that the router would use to communicate with the network management system. However when you unplug that interface now the router has no interface that it can use to send the link down trap to the network management system.
HTH
Rick

Configure WCS to limit SNMP Trap to only Rogue AP alert

Hello all,
Is there a way to limit SNMP traps sent by WCS to only Rogue AP Alert? I know I can configure WCS to send email notification for Rogue AP Alert, but couldn't find anything similar for SNMP traps.
Also, where can I find WCS MIBS and OID for Rogue AP Alert?
Thanks.

https://tools.cisco.com/bugsearch/bug/CSCue09354 may be this is root of problem, when I use native vlan on access port WLC can found rogue ap on wired network... but i use version 7.4.121

Zone shutdown error - SNMP request returned error status 6 (no access)

When trying to shutdown a zone though SunMC it get the following error from the web page
SNMP request returned error status 6 (no access) snmp://xx.xx.com:nnnn/mod/scm-container/Zones/ZoneTable/ZoneEntry/zoneState#zonename
the log on the agent has
[0000008f 00a8 ]warning Nov 28 12:20:10 agent preValidateSetPDU: zoneState(zonename) [1.3.6.1.4.1.42.2
.12.2.2.85.6.1.1.10.10.98.111.116.97.110.105.120.45.97.100] - noAccess
I probably am missing a simple undocumented permissions problem.
Any help would be appreciated
Thanks

marcusj99 wrote:
When trying to shutdown a zone though SunMC it get the following error from the web page
SNMP request returned error status 6 (no access) snmp://xx.xx.com:nnnn/mod/scm-container/Zones/ZoneTable/ZoneEntry/zoneState#zonename
the log on the agent has
[0000008f 00a8 ]warning Nov 28 12:20:10 agent preValidateSetPDU: zoneState(zonename) [1.3.6.1.4.1.42.2
.12.2.2.85.6.1.1.10.10.98.111.116.97.110.105.120.45.97.100] - noAccess
I probably am missing a simple undocumented permissions problem.
Any help would be appreciatedSCM security can be tricky to get right the first time you use it. Have you performed these operations in the global zone?:
- run es-config to add your SunMC userID to the scm-container ACL?
- made sure the Project Managment and Pool Management entries are in /etc/security/prof_attr and exec_attr files?
- added your SunMC userID to the Zone/Pool/Project entries in /etc/user_attr (or used the 'usermod' command to add the entries for you)?
If any of those steps were missed then SunMC (or Solaris) may not believe you have permisson to make changes to zones/pools etc. There are a couple of SCM docs listed in with the SunMC doc set:
http://docs.sun.com/app/docs/coll/810.8?l=en
Regards,
[email protected]
http://www.HalcyonInc.com
New !! : http://forums.HalcyonInc.com !!

Disable default snmp traps

Hello,
I am trying to disable the default snmp trap for x25. I tried to use the "no" form of the command (no snmp-server enable traps x25), but after typing:
no snmp-server enable traps ?
x25 is not even listed.
The other workaround was to specify exactly what type of traps I wanted to be sent to my snmp-server using the commands:
snmp-server host ip_address community flash tty snmp
(x25 was not included), but that didn't solve the problem.
Any assistance would be highly appreciated.
Regards,
Katerina

Hi,
I have tried it with solarwinds and works fine for me. Talking about the traps. But they are too many.
The OID is : 1.3.6.1.4.1.14179.1.1.2.4.1.22
snmp info for polling:
MIB Value Type: Raw Value
Format: None
SNMP Get Type: Get Table
Polling Type: node
On WLC go to Managemnet (top TAB)
Right hand select > SNMP > Traps Control.
In this menu select what traps to need to be logged.
These traps will be shows on the oid polled.

Prime Infrastructure 2.0 Link Status Alarms

Hi,
we are used SNMP traps sent from our core switches to our PI 1.3 server to notify us about link down events. In this scenario we got emails only for link down events on our core switches.
Now, we are using PI 2.0. It seems PI 2.0 checks link status of all devices on its own. We got an email for a link down event on any of our switches. To avoid that I configured PI 2.0 to treat Link down events as Informational instead of Critical (Administration > System Settings > Severity Configuration, Link down). Now, we don't get email notification for link down events at all.
Is there a way to configure PI 2.0 to inform us on link down events on our core switches, but not on a link down event on any of our other devices?
Timo

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.

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.

Monitoring PRi's with snmp traps

I am looking to monitor when my pri's go down and generate a trap.
Is this the best way:
snmp-server enable traps isdn layer2
or are there some other traps that I can enable?
Thanks,

Once I got my SNMP host to accept the correct attribute and configure the event trap all I had to do was add the trap command to the router. I then bounced one of my low usage PRI's (which had 0 calls on it ) and got the following event traps on the SNMP host:
Minor
May 19, 2010 2:21:00 PM EDT
A demandNbrLayer2Change notification has been received indicating that a D-channel on Rtr_Cisco device, named has layer 1 active but layer 2 not established. Interface Index = 83 Link Status = ISDNLinkInTransition
System
May 19, 2010 2:21:01 PM EDT
System
Major
May 19, 2010 2:20:59 PM EDT
A demandNbrLayer2Change notification has been received indicating that a D-channel on Rtr_Cisco device, named has both layers 1 and 2 inactive. Interface Index = 83 Link Status = ISDNLinkDown
System
May 19, 2010 2:21:00 PM EDT
System
It doesn't tell you specifically which interface is down but at least it narrows it down to the gateway/router. Most of our gateways have only one PRI anyway.
We use Spectrum One Click for network monitoring.
Here is L2 back on line:
May 19, 2010 2:21:01 PM EDT
A demandNbrLayer2Change notification has been received indicating that a D-channel on Rtr_Cisco device, named has layer 1 active and layer 2 established. Interface Index = 83 Link Status = ISDNLinkUp
System

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 ***

Manipulating SNMP Trap link_down severity level?

Dear Cisco experts,
I wonder if there's a way to manipulate sent traps from a switch with different severity levels?
I now see SNMP link_down traps in my NMS, but they're all of the same level, but a link_down from a desktop is 'normal', a server link_down would be 'warning', but when an uplink to another data center goes down, it should result in all alarms going off, so should be 'critical'.
Is there a way to tell my switch to send an SNMP trap on a different severity level dependent on the type of interface? This is most important because these links all have different SLAs.
Many thanks for your support and suggestions.
Marco van der Pal

This is not possible, Only one sort of trap is possible
You best approach woud be to disable up-down traps on ports that are not important.
LMS now has port groups. That feature could be usefull for doing this
Cheers,
Michel

SNMP traps on ports

I have a few 65xx and having some issues with getting "snmp traps mac-note change add/remove:on the ports
On my switch running IOS v12.2(33) SXH1 / ROM V12.2(17r) SX 3 i can enter the added/removed command on a range of ports no issues.
On my swithces running IOS V12.2 (18) SXF10 / ROM V12.2(17r) SX 3 i am unable, only commands is Link-Status when i enter ?
I am guessing this is due to the ISO version being different on the switches, is there a way to enable traps on the ports (snmp traps mac-note change added/remove) like on the other switch without having to upgrade the IOS?

Thanks for the info, guess i will move forward with update of the IOS. Its been a while since i have done an IOS upgrade, on the cisco site would i grab the Cat 6500 Supervisor Engine 32? It looks like the latest ISO here is from 30 may 2008.

SCOM 2012 SNMP Trap - Does anyone have it working?

I am wondering if anyone out there has had any luck with getting SNMP Traps to be captured by SCOM 2012? Probes work fine.
We have been unable to get SCOM 2012 to receive a SNMP Trap from network devices. We currently have a case open with Microsoft, but they dont have any answers as of yet.
Here are the cliff notes version of what we have done so far.
Discovery - OK
The nodes discover without issue. I made sure they were set to SNMP only. I did this to verify we were talking SNMP and not just ICMP.
Open Ports/Firewall Issues
No firewalls are in place on the SCOM server and none exist between devices we are trying to get traps from. Using a port tool, I can see that UDP 162 is listening as expected and its the System Center Management Host Process that is running the
process. We have tried having SNMP installed, but disabled, installed and running, and uninstalled. Currently we have the SNMP service installed and running. The SNMP Trap Service is NOT installed.
Data Validation
Using Wireshark running on the SCOM box I have been able to validate the OIDs we are searching for are hitting the SCOM server. I installed an SNMP Trap generator and Receiver on my local machine as well as Jalasoft SNMP Simulator. I was able
to discover my local machine as a network device and if I send a TRAP from the TRAP generator on my local machine to the receiver on my local machine I can validate the data is coming through ok.
What has been done on SCOM side
The simplest place to look for data is with an Event Collection Rule and then an Event View Monitor. We have set up an Event Based Monitor to search for an OID that I know to be accurate and then I set up an Event monitor to look for
anything hitting that Collection Rule. The Event monitor showed nothing so we changed the EVent Monitor to look for anything that hit Node which should show any SNMP traps that have hit from network devices. No results.
We tried to run WFAnalyzer from the 2007R2 Authoring Console, but it wont run against 2012 and from what I have found the 2012 edition doesnt exist anywhere yet.
So has anyone succesfully received a SNMP TRAP into SCOM 2012?

Hi,
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios.
In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.
Thanks,
Yog Li
TechNet Community Support
How could you possibly mark this as answered? No answer was given, it was quiet for a couple of days including one of which was a holiday in the US. The previous steps are NOT helpful. The question remains, Does anyone have it working?
People have given troubleshooting advice, but nobody has actually answered the simple question. Do they have it actually WORKING?

Disable snmp trap link-status only on access ports?

Similar Messages

Maybe you are looking for