Shane Ketterman
2013-07-06 04:55:39 UTC
Shane Ketterman [http://community.zenoss.org/people/shaneketterman] created the discussion
"Issues With Traps - Need a little help"
To view the discussion, visit: http://community.zenoss.org/message/73847#73847
--------------------------------------------------------------
I'm pretty sure and I also hope that I'm just missing something simple but why is it so hard to get traps sent to Zenoss, associate them with the device sending them, and have them show up as an event attached to the specific device? On a cisco 3600 metro switch, the only way I could get traps sent to zenoss was to enable ALL snmp traps and then the strangest thing happens....all trap messages come in one single event:
| clogHistFacility | PLATFORM_ENV |
| clogHistFacility.20638 | LINK |
| clogHistFacility.20639 | PLATFORM_ENV |
| clogHistMsgName | DUAL_PWR |
| clogHistMsgName.20638 | UPDOWN |
| clogHistMsgName.20639 | DUAL_PWR |
| clogHistMsgText | Faulty internal power supply 2 detected |
| clogHistMsgText.20638 | Interface GigabitEthernet0/8, changed state to down |
| clogHistMsgText.20639 | Faulty internal power supply 2 detected |
Not only do I want these separate but I also need to display the actual message and instead the even shows up as this in the summary:
snmp trap ciscoConfigManEvent
I've attatched the snmp config on my router if it provides any insight.
Basically, I just want traps to come in, be readable like all other events, and have a nice simple way to facilitate this.
Thanks in advance for any help/advice/direction
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73847#73847]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"Issues With Traps - Need a little help"
To view the discussion, visit: http://community.zenoss.org/message/73847#73847
--------------------------------------------------------------
I'm pretty sure and I also hope that I'm just missing something simple but why is it so hard to get traps sent to Zenoss, associate them with the device sending them, and have them show up as an event attached to the specific device? On a cisco 3600 metro switch, the only way I could get traps sent to zenoss was to enable ALL snmp traps and then the strangest thing happens....all trap messages come in one single event:
| clogHistFacility | PLATFORM_ENV |
| clogHistFacility.20638 | LINK |
| clogHistFacility.20639 | PLATFORM_ENV |
| clogHistMsgName | DUAL_PWR |
| clogHistMsgName.20638 | UPDOWN |
| clogHistMsgName.20639 | DUAL_PWR |
| clogHistMsgText | Faulty internal power supply 2 detected |
| clogHistMsgText.20638 | Interface GigabitEthernet0/8, changed state to down |
| clogHistMsgText.20639 | Faulty internal power supply 2 detected |
Not only do I want these separate but I also need to display the actual message and instead the even shows up as this in the summary:
snmp trap ciscoConfigManEvent
I've attatched the snmp config on my router if it provides any insight.
Basically, I just want traps to come in, be readable like all other events, and have a nice simple way to facilitate this.
Thanks in advance for any help/advice/direction
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73847#73847]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]