Legacy Discussions

1.  Monitor and send alarm on important interfaces

Posted 8 days ago
I a running zenoss core 4.2.5.

I have important interface and trunks that I need to get alarmed on. How do you do this ease ? Today, I only send critical alarms to different people.


I have 50-60 cisco switch and 6-8 cisco core equipment  that have some interface to monitor and get alarm on.

-To many errors on a interface
-Interface goes down
-The interface goes full

/Stig


2.  RE: Monitor and send alarm on important interfaces

Posted 2 days ago
Hey, have you solved your problem? I have same question about my Huawei S3300, can you help me that?


3.  RE: Monitor and send alarm on important interfaces

Posted 22 hours ago
Hi

I have not solved this.

I have enable this commando on a test switch.

Logging 10.10.10.10 (zenoss server)
snmp-server host 10.10.10.10. version 2c public
logging trap debugging
snmp-server community public

No i have many snmp traps in zenoss.

But now I do no  what I need to do to be able to translate mibs in zenoss  and it should only apply some interface to this test switch

------------------------------
Stig
------------------------------



4.  RE: Monitor and send alarm on important interfaces

Posted 22 hours ago
So are the alarms that you want interface up/down events or are they threshold events when a performance target is exceeded?  What are the actual events, ie eventClasses that you are getting?  I am guessing that some of these events are low priority but others are the ones you want to escalate and turn into notifications?  Perhaps post a screenshot of a sample - it would also be helpful to know the agent that is sending the event - you can see this in the details of an event.

Cheers,
Jane

------------------------------
Jane Curry
Skills 1st United Kingdom
jane.curry@skills-1st.co.uk
------------------------------



5.  RE: Monitor and send alarm on important interfaces

Posted 22 hours ago
Hi

Is diffrent what i need on alla switches.

Some interface like cisco trunks and links to diffrent switches in other house i must now upp/and down.

I always have 2 ways from my core switch to all other switches. But I have to know that a link has gone down. Otherwise I can miss this.

The access switch still up with one link


On some interface I need to know that it has been full or that there are many errors on the port.


------------------------------
Stig
------------------------------



6.  RE: Monitor and send alarm on important interfaces

Posted 21 hours ago
  |   view attached
I have uploaded i picture.


------------------------------
Stig
------------------------------



7.  RE: Monitor and send alarm on important interfaces

Posted 21 hours ago
So I am guessing the events you are interested in are all those /Unknown traps in the top half of your screenshot?  We need to find a way to decide which ones are important.  Again, I am guessing that the different traps are from different types of Cisco device???  Double click on some of those traps and scroll into the event detail - there may be stuff down there with other OIDs that we can use to determine whether it is an "important" device / interface or not.  What I am thinking is there may be an attribute for interface name and we could then do a pattern match on such an attribute.

Cheers,
Jane

------------------------------
Jane Curry
Skills 1st United Kingdom
jane.curry@skills-1st.co.uk
------------------------------



8.  RE: Monitor and send alarm on important interfaces

Posted 17 hours ago
Hi

I try to unplug a rj45 cabel in the switch. Some test interface

port GigabitEthernet0/1 and GigabitEthernet0/6.

See the trap information further down.

 Then I agree with you how to name or how to know which interface is important. Can i give them a special name on the description field in cisco so zenoss can pick it up what is the best and easiest way to to this.?

I have try this event transform in the root, but no luck.

if evt.component=='GigabitEthernet0/1' and evt.device=='172.27.1.21':
evt.severity=5




Getting this events in zenoss.







From cisco

http://snmp.cloudapps.cisco.com/Support/SNMP/do/BrowseOID.do?local=en

1.3.6.1.6.3.1.1.5.41.3.6.1.6.3.1.1.5.4ifIndex ifAdminStatus ifOperStatus
"A linkUp trap signifies that the SNMP entity, acting in anagent role, has detected that the ifOperStatus object forone of its communication links left the down state andtransitioned into some other state (but not into thenotPresent state). This other state is indicated by theincluded value of ifOperStatus."




---------------------------1.3.6.1.6.3.1.1.5.3
Trap Components ifIndex ifAdminStatus ifOperStatus Description "A linkDown trap signifies that the SNMP entity, acting inan agent role, has detected that the ifOperStatus object forone of its communication links is about to enter the downstate from some other state (but not from the notPresentstate). This other state is indicated by the included valueof ifOperStatus."

------------------------------
Stig Wangdell
CompanyName
------------------------------