Problems with OIDs in templates. Need for wildcards?

[felipe.castelar]

felipe.castelar [http://community.zenoss.org/people/felipe.castelar] created the discussion

"Re: RE: Problems with OIDs in templates. Need for wildcards?"

To view the discussion, visit: http://community.zenoss.org/message/70739#70739

--------------------------------------------------------------
That one explaned well what was happening here, my friend!

Nevertheless, when I apply the ifOperStatus threshold on ethernetcsmacd every single port that is down on my component list from devices under /Devices gets an Event of exceeded threshold.

Is it possible to apply a new monitoring template to a component? Or will I have to edit ethernetcsmacd template on every single interface I want to monitor this data source?

I'm implementing this because of TRAP losses, that sometimes compromise my network operation. Is there any other way to "double check" my "link down" events?

Thanks in advance!
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70739#70739]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[nilie]

nilie [http://community.zenoss.org/people/nilie] created the discussion

"Re: RE: Problems with OIDs in templates. Need for wildcards?"

To view the discussion, visit: http://community.zenoss.org/message/70730#70730

--------------------------------------------------------------
If you want to double-check link down events then syslog is your best friend, you don't need to mess around with transforms, or template editing. Now if you want to check the current status of an interface, use Zenoss 4.2.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70730#70730]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[felipe.castelar]

felipe.castelar [http://community.zenoss.org/people/felipe.castelar] created the discussion

"Re: RE: Problems with OIDs in templates. Need for wildcards?"

To view the discussion, visit: http://community.zenoss.org/message/70807#70807

--------------------------------------------------------------
I've implemented syslog on some devices. Nevertheless, I’ve got another problem now! I have to classify each syslog message to determine its severity. Do you know any zenpack tha does this classification?
...     for i in d.os.interfaces():
...         if i.getIpAddress() == None:
... i.monitor = False
...

commit()

Here I’ve used the if clause to set False the monitor attributes on interfaces with has no IP address assigned. You can use other if clause to filter interfaces of your interest.

Thanks for your help.

Best Regards,
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70807#70807]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[nilie]

nilie [http://community.zenoss.org/people/nilie] created the discussion

"Re: RE: Problems with OIDs in templates. Need for wildcards?"

To view the discussion, visit: http://community.zenoss.org/message/70846#70846

--------------------------------------------------------------
You don't really have to do that for each event. Zenoss offers an automatic mapping of syslog severity into its own severity levels so you can start using it right away. If you're not happy with it, you modify this event mapping and assign the severity level you desire. The first time you see one of the syslog events you need to re-classify, you click on it in the event console and use the map event button (you can map it to an existing event class or you can create a new class for it). Then you edit the new event class and change its properties. Besides playing with severity levels, you can also chose to ignore a certain class of syslog evants or send them directly to archive.
I got deep into several other network management systems but Zenoss beats each and every one when it comes to syslog processing.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70846#70846]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]