can we use SNMP to monitor both CAS and CAM

Unanswered Question
Jul 16th, 2009

We have deployed a full redundant CAS and CAM in our environment. Since this becomes crtical device in our network we would like to monitor the using SNMP. If this is not possible, then how are we to monitor these devices. Please note we are using 4.1(3) software version.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Lucien Avramov Fri, 07/17/2009 - 23:32

Edit the file /perfigo/snmp/snmpd.conf

Add line rocommunity XXX where XXX is your community string.

Then restart the snmpd daemon on the CAS / CAM and you can poll them via snmp version 2c with the community you specified in the snmpd.conf file.

NAC 4.5 and above have better support for mibs and traps.

These tables are defined in the UCD-SNMP-MIB, and can be walked:

prTable - contains a list of processes with a count of how many of each

process must be present

memory - memory currently used

diskTable - disks of the system and how full they are

loadTable - canonical unix load average.

-- prTable OBJECT IDENTIFIER ::= { ucdavis 2 }

-- memory OBJECT IDENTIFIER ::= { ucdavis 4 }

-- diskTable OBJECT IDENTIFIER ::= { ucdavis 9 }

-- loadTable OBJECT IDENTIFIER ::= { ucdavis 10 }

Definition here: http://en.wikipedia.org/wiki/Load_(computing)

The contents of these tables generate DISMAN-EVENT-MIB traps in the

following cases:

DISMAN-EVENT-MIB.txt:mteTriggerFalling is sent when the table being watched

goes from acceptable to unacceptable state.

OBJECT IDENTIFIER 1.3.6.1.2.1.88.2.0.3

DISMAN-EVENT-MIB.txt:mteTriggerRising is sent then the table being watched

goes from unacceptable to acceptable state.

OBJECT IDENTIFIER 1.3.6.1.2.1.88.2.0.2

Parsing the notification will indicate which table generated the

notification.

We send the following two traps:

IF-MIB.txt:linkDown NOTIFICATION-TYPE

OBJECT IDENTIFIER 1.3.6.1.6.3.1.1.5.3

IF-MIB.txt:linkUp NOTIFICATION-TYPE

OBJECT IDENTIFIER 1.3.6.1.6.3.1.1.5.4

Whenever a ethernet interface on the CAM goes up or down, sending linkDown

when the interface goes down and linkUp when it comes back up.

We send the following traps:

SNMPv2-MIB.txt:coldStart NOTIFICATION-TYPE

OBJECT IDENTIFIER 1.3.6.1.6.3.1.1.5.1

NET-SNMP-AGENT-MIB.txt:nsNotifyShutdown NOTIFICATION-TYPE

OBJECT IDENTIFIER 1.3.6.1.4.1.8072.4.0.2

When the SNMP system is started or stopped. The SNMP system is started

whenever the system starts up or the SNMP configuration is changed. The

SNMP system is stopped whenever the system shuts down or the SNMP

configuration is changed. ColdStart is sent when the system starts and a

nsNotifyShutdown is sent when the system stops.

val_devera Sun, 07/19/2009 - 22:14

Hi Lucien,

Apprecite your help... but I would like to clarify if this should be done at the CAM side? Also, is there a way for us to directly monitor the CASs?

Thanks

Lucien Avramov Sun, 08/16/2009 - 20:04

You can implement this on both and monitor both of them.

You can use an snmp trap receiver that will receive a trap from the CAM / CAS when it does up/down.

You can consider HP Open View for example.

Actions

This Discussion