Translations of this page:

Osmius

Osmius Agent Cisco Router
Agent name: osm_ag_CIROUTER Agent Code: CIROUTER
Contenido: User manual for Osmius Agent gor Cisco Routers
Date Created: 01/12/2009 Date Reviewed:

General Information

This is a generic Agent that is able to monitor all Cisco Routers Series. It can monitor several parameters device collecting events through snmp pooling (“Pool Events”) and through traps reception (“Trap Events”). We have tested this agent against all “Cisco Series Routers”.

Like other Osmius agents this one has been developed using ACE C++ libraries that provides general features like superior performance, real multiplatform capabilities and robustness, so you need to install ACE properly in order to install and run this agent in case you want to compile it your self (You can forget this if you install Osmius agents using the wizard installer). More about installation here.

This agent also needs the Net-SNMP fantastic libraries Net-SNMP.

The Osmius CIROUTER agent offers several basic events and up to ten customizable events using configuration parameters such as the OID, to allow the user to create new events and adapt this agent to a particular Cisco Router device. The basic events have been chosen by network experts with the idea of develop an generic Cisco Router Agent.

Using the Osmius Web Console the users access to a MIB Navigator to load MIBS and to search for the appropriate snmp oid to create their own events.

Osmius also has an agent to receive and process **SNMP Traps** and to redirect them into the event correlation system as they were Osmius “normal” events. For each Agent Type (Instance Type) we can configure several “Trap Events” and in this Cisco Router Agent we have chosen the most interesting with the idea, again, of developing an generic Cisco Router Agent.

In this agent all the provided events are non-intrusive events, this is remote events, so they can be retrieved from the network outside of the Instance being monitored. Events are build upon the versions 1 and 2 (2c) of SNMP protocol.

Here you can find a good SNMP C API programming guide.

Instances

As a general rule each Osmius agent can monitor only one Instance Type. If you are not familiar with these concepts please review the Concepts Glossary. Each Instance is defined in the configuration file (more information in agents & instances) and depending on the agent we need to provide the Instance Connection INFO.

CONNECTION_INFO

The connection information or connection_info is data that the agent needs to know to connect to the instance. (See more about the connection_info)

In the particular case of Cisco agent the CONNECTION_INFO field has no information needs as it uses the generic SNMP fields like Nodename, read community and snmp port.

CONNECTION_INFO= 

TYPE

The type defines the Instance Type to be monitored. Every Osmius instance have to be associated to a specific type as you can review here

In this case:

TYPE= CIROUTER

Pool Events Summary Table

EVENT DESCRIPTION c tsegundos w a Extra Parameters / Observations
CINTERFZ Name and Descriptions of device interfaces1 86400 0 0 [-Q timeout] [-V 1,2] silent mode ( -s) recommended. “info” Event don't configurable with the console
CISROMID System Bootstrap description and version identification1 86400 0 0 [-Q timeout] [-V 1,2] silent mode ( -s) recommended. “info” Event don't configurable with the console
CISWHYRL The reason why the system was last restarted1 86400 0 0 [-Q timeout] [-V 1,2] silent mode ( -s) recommended. “info” Event don't configurable with the console
CISHOSTN The name of the host 1 86400 0 0 [-Q timeout] [-V 1,2] silent mode ( -s) recommended. “info” Event don't configurable with the console
CIDOMNAM The domain portion of the domain name of the host1 86400 0 0 [-Q timeout] [-V 1,2] silent mode ( -s) recommended. “info” Event don't configurable with the console
CICONTAC The cisco's name and address 1 86400 0 0 [-Q timeout] [-V 1,2] silent mode ( -s) recommended. “info” Event don't configurable with the console
CICONFIG The name of the system boot image 1 86400 0 0 [-Q timeout] [-V 1,2] silent mode ( -s) recommended. “info” Event don't configurable with the console
CICONADR The address of the host that supplied the system boot image1 86400 0 0 [-Q timeout] [-V 1,2] silent mode ( -s) recommended. “info” Event don't configurable with the console
CICONPRT The protocol that supplied the system boot image 1 86400 0 0 [-Q timeout] [-V 1,2] silent mode ( -s) recommended. “info” Event don't configurable with the console
CIBUSPER CPU busy percentage in the last 5 seconds period0 5 85 95 [-Q timeout] [-V 1,2] silent mode ( -s) recommended.
CIAVGBY1 1 minute exponentially-decayed moving average of the CPU busy percentage0 60 85 95 [-Q timeout] [-V 1,2] silent mode ( -s) recommended.
CIAVGBY5 5 minute exponentially-decayed moving average of the CPU busy percentage. This is the instance availability event 0 300 85 95 [-Q timeout] [-V 1,2] silent mode ( -s) recommended.
CIUS0001 a CIUS0010 These are user events prepared to read the oid parameter and send it back to the Osmius process. 0 600 1 1 -O “oid” [-N nodename] [-K community_name] [-P port] [-Q timeout] [-V 1,2]
CICINTE0 to CICINTE9 This event checks interfaces status 0 300 1 1 [-I “iface1,iface2,ifacen”] [-Y “ifType1,ifTypen”] [-N nodename] [-K community_name] [-P port] [-Q timeout] [-V 1,2]
  • If your Capacity Plannings needs some of these events don't use the silent mode in the configuration parameters.

Agent Pool Events

CINTERFZ

CINTERFZ event return the name and description of each of router interfaces. The “oid” is:

.iso.org.dod.internet.mgmt.mib-2.interfaces.ifNumber.0 -> Number of interfaces
.iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry.ifDescr.i -> for each interface i

Return Values:

VALUE MEANING
-1 Error
0 Failed to retrieve the value
1 Value correctly retrieved

Recommended Parameters Values:

Comparison Type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring Interval 86400 seconds
warning threshold 0
critical threshold 0

Example:

CINTERFZ = -t 86400 -c 1 -w 0 -a 0 -T "Router interfaces description"

Comments: This is an “info” event, then it doesn't configurable with the Osmius console. The interface information text will be into the event text.
This event uses the Net-SNMP libraries.

CISROMID

CISROMID event return the System Bootstrap description and version identification. The “oid” is:

.iso.org.dod.internet.private.enterprises.cisco.local.lcpu.romId.0 -> System Bootstrap

description and version.

Return Values:

VALUE MEANING
-1 Error
0 Failed to retrieve the value
1 Value correctly retrieved

Recommended Parameters Values:

Comparison Type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring Interval 86400 seconds
warning threshold 0
critical threshold 0

Example:

CISROMID = -t 86400 -c 1 -w 0 -a 0 -T "System Bootstrap description and version"

Comments: This is an “info” event, then it doesn't configurable with the Osmius console. The information text will be into the event text.
This event uses the Net-SNMP libraries.

CISWHYRL

CISWHYRL event return the reason why the system was last restarted. The “oid” is:

.iso.org.dod.internet.private.enterprises.cisco.local.lcpu.whyReload.0 -> reason of the last reload.

Return Values:

VALUE MEANING
-1 Error
0 Failed to retrieve the value
1 Value correctly retrieved

Recommended Parameters Values:

Comparison Type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring Interval 86400 seconds
warning threshold 0
critical threshold 0

Example:

CISWHYRL = -t 86400 -c 1 -w 0 -a 0 -T "reason why the system was last restarted"

Comments: This is an “info” event, then it doesn't configurable with the Osmius console. The information text will be into the event text.
This event uses the Net-SNMP libraries.

CISHOSTN

CISHOSTN event return name of the host . The “oid” is:

.iso.org.dod.internet.private.enterprises.cisco.local.lcpu.hostName.0 -> Host name.

Return Values:

VALUE MEANING
-1 Error
0 Failed to retrieve the value
1 Value correctly retrieved

Recommended Parameters Values:

Comparison Type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring Interval 86400 seconds
warning threshold 0
critical threshold 0

Example:

CISHOSTN = -t 86400 -c 1 -w 0 -a 0 -T "Name of the Host"

Comments: This is an “info” event, then it doesn't configurable with the Osmius console. The information text will be into the event text.
This event uses the Net-SNMP libraries.

CIDOMNAM

CIDOMNAM event return the domain portion of the domain name of the host. The “oid” is:

.iso.org.dod.internet.private.enterprises.cisco.local.lcpu.domainName.0 -> Domain name.

Return Values:

VALUE MEANING
-1 Error
0 Failed to retrieve the value
1 Value correctly retrieved

Recommended Parameters Values:

Comparison Type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring Interval 86400 seconds
warning threshold 0
critical threshold 0

Example:

CIDOMNAM = -t 86400 -c 1 -w 0 -a 0 -T "Domain name of the Host"

Comments: This is an “info” event, then it doesn't configurable with the Osmius console. The information text will be into the event text.
This event uses the Net-SNMP libraries.

CICONTAC

CICONTAC event return the cisco's name and address. The “oid” is:

.iso.org.dod.internet.private.enterprises.cisco.local.lcpu.ciscoContactInfo.0 -> Cisco's name and adress.

Return Values:

VALUE MEANING
-1 Error
0 Failed to retrieve the value
1 Value correctly retrieved

Recommended Parameters Values:

Comparison Type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring Interval 86400 seconds
warning threshold 0
critical threshold 0

Example:

CICONTAC = -t 86400 -c 1 -w 0 -a 0 -T "Cisco's name and address"

Comments: This is an “info” event, then it doesn't configurable with the Osmius console. The information text will be into the event text.
This event uses the Net-SNMP libraries.

CICONFIG

CICONFIG event return the name of the system boot image. The “oid” is:

.iso.org.dod.internet.private.enterprises.cisco.local.lcpu.sysConfigName.0 -> System Configuration Name.

Return Values:

VALUE MEANING
-1 Error
0 Failed to retrieve the value
1 Value correctly retrieved

Recommended Parameters Values:

Comparison Type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring Interval 86400 seconds
warning threshold 0
critical threshold 0

Example:

CICONFIG = -t 86400 -c 1 -w 0 -a 0 -T "Name of the system boot image"

Comments: This is an “info” event, then it doesn't configurable with the Osmius console. The information text will be into the event text.
This event uses the Net-SNMP libraries.

CICONADR

CICONADR event return the address of the host that supplied the system boot image. The “oid” is:

.iso.org.dod.internet.private.enterprises.cisco.local.lcpu.sysConfigAddr.0 -> System Configutation Adress.

Return Values:

VALUE MEANING
-1 Error
0 Failed to retrieve the value
1 Value correctly retrieved

Recommended Parameters Values:

Comparison Type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring Interval 86400 seconds
warning threshold 0
critical threshold 0

Example:

CICONADR = -t 86400 -c 1 -w 0 -a 0 -T "Address of the host that supplied the system boot image"

Comments: This is an “info” event, then it doesn't configurable with the Osmius console. The information text will be into the event text.
This event uses the Net-SNMP libraries.

CICONPRT

CICONPRT event return the protocol that supplied the system boot image. The “oid” is:

.iso.org.dod.internet.private.enterprises.cisco.local.lcpu.sysConfigProto.0 -> System Configuration Protocol.

Return Values:

VALUE MEANING
-1 Error
0 Failed to retrieve the value
1 Value correctly retrieved

Recommended Parameters Values:

Comparison Type Inverted. The higher the value the lesser the severity. (-c 1)
Monitoring Interval 86400 seconds
warning threshold 0
critical threshold 0

Example:

CICONPRT = -t 86400 -c 1 -w 0 -a 0 -T "Protocol that supplied the system boot image"

Comments: This is an “info” event, then it doesn't configurable with the Osmius console. The information text will be into the event text.
This event uses the Net-SNMP libraries.

CIBUSPER

CIBUSPER event return the CPU busy percentage in the last 5 seconds period. The “oid” is: .iso.org.dod.internet.private.enterprises.cisco.local.lcpu.busyPer.0 → CPU busy percentage in the last 5 seconds.

Extra parameters:

This event use two extra parameters:

PARAMETER MEANING Mandatory
-Q -Q “timeout” - timeout in seconds for the snmpget operations. Defaults to 0, no timeout. No
-V -V “version” - SNMP protocol version. Allowed values are [1, 2]. Defaults 2 (v2c). No

Return Values:

VALUE DESCRIPTION
-1 Error
N CPU busy percentage in the last 5 seconds period

Recommended Parameters:

Comparison Type Direct.
monitoring interval 5 seconds –> Depending on the relative importance of the instance
warning threshold 85
critical threshold 95

Example:

CIBUSPER = -t 5 -c 0 -w 85 -a 95 -T "CPU busy percentage in the last 5 second period"

Comments: The associated SNMP text will be into the event text.
This event uses the Net-SNMP libraries

CIAVGBY1

CIAVGBY1 event return the 1 minute exponentially-decayed moving average of the CPU busy percentage. The “oid” is: .iso.org.dod.internet.private.enterprises.cisco.local.lcpu.avgBusy1.0

Extra parameters:

This event use two extra parameters:

PARAMETER MEANING Mandatory
-Q -Q “timeout” - timeout in seconds for the snmpget operations. Defaults to 0, no timeout. No
-V -V “version” - SNMP protocol version. Allowed values are [1, 2]. Defaults 2 (v2c). No

Return Values:

VALUE DESCRIPTION
-1 Error
N CPU busy percentage in the last 1 minute

Recommended Parameters:

Comparison Type Direct.
monitoring interval 60 seconds –> Depending on the relative importance of the instance
warning threshold 85
critical threshold 95

Example:

CIAVGBY1 = -t 5 -c 0 -w 85 -a 95 -T "CPU busy percentage in the last 1 minute"

Comments: The associated SNMP text will be into the event text.
This event uses the Net-SNMP libraries

CIAVGBY5

CIAVGBY5 event return the 5 minute exponentially-decayed moving average of the CPU busy percentage. This is the instance availability event. The “oid” is: .iso.org.dod.internet.private.enterprises.cisco.local.lcpu.avgBusy5.0

Extra parameters:

This event use two extra parameters:

PARAMETER MEANING Mandatory
-Q -Q “timeout” - timeout in seconds for the snmpget operations. Defaults to 0, no timeout. No
-V -V “version” - SNMP protocol version. Allowed values are [1, 2]. Defaults 2 (v2c). No

Return Values:

VALUE DESCRIPTION
-1 Error
N CPU busy percentage in the last 5 minute

Recommended Parameters:

Comparison Type Direct.
monitoring interval 300 seconds –> Depending on the relative importance of the instance
warning threshold 85
critical threshold 95

Example:

CIAVGBY5 = -t 300 -c 0 -w 85 -a 95 -T "CPU busy percentage in last 5 minutes"

Comments: The associated SNMP text will be into the event text.
This event uses the Net-SNMP libraries

CIUS0001 a CIUS0099

CIUS0001 event returns the texto or the numeric value in the snmp device related to tje “iod” used as a customized parameter. If the oid is numeric the return value is this number. If the oid is a string the return value is 1 if the retrieval worked properly and the string will be attached into the event text. In case of error the return value is 0.

Extra parameters:

PARAMETER MEANING Mandatory
-O -O “oid”- oid to recover. Try first one of these commands “snmpwalk -v1 -O f -c community target_IP” or “snmpget -v1 -c community -o oid target_IP. Yes
-N -L “nodename” - This node name overrides the one in the Instance CONNECTION_INFO and the default one (agent hostname). No
-K -K “community” - This “community name” overrides the one in the instance CONNECTION_INFO and the default one (“public”). No
-P -P “port” - This “port” overrides the one in the instance CONNECTION_INFO and the default one (161). No
-Q -Q “timeout” - timeout in seconds for the snmpget operations. Defaults to 0, no timeout. No
-V -V “version” - SNMP protocol version. Allowed values are [1, 2]. Defaults 2 (v2c). No

Return Values:

VALOR SIGNIFICADO
-1 Error
0 Failed to retrieve
1 String value correctly retrieved
N Numeric value correctly retrieved

Recommended Parameters:

Comparison Type Inverted or Direct. Depending on the oid parameter.
monitoring interval 300 segundos – 1 hora –> depende de la importancia de la instancia
warning threshold 0 or N depending on the oid type
critical threshold or N depending on the oid type

Example:

CIUS0001 = -t 300 -c 1 -w 0 -a 0 -T "ciscoMemoryPoolUtilization5Min" -O ".1.3.6.1.4.1.9.9.48.1.2.1.2" -K secret_community -P 177 -Q 3 -V 1

Comments: The associated SNMP text will be into the event text.
This event uses the Net-SNMP libraries

CICINTE0

The event CICINTE0 checks net interfaces ifOperStatus. User is able to define an interfaces list, to check only desired interfaces. User is able to define an interface types list, to check only desired types. The event will report down interfaces. User is able to set up to 10 events, from CICINTE0 to CICINTE9

Extra parameters:

PARAMETER MEANING Mandatory
-I -I “iface1,ifacen”- Interfaces list. If it is not set, agent will check all interfaces. No
-Y -Y “ifType1,ifTypen”- Interface Types list. See types list. If it is not set, agent will check all interface types. No
-N -L “nodename” - This node name overrides the one in the Instance CONNECTION_INFO and the default one (agent hostname). No
-K -K “community” - This “community name” overrides the one in the instance CONNECTION_INFO and the default one (“public”). No
-P -P “port” - This “port” overrides the one in the instance CONNECTION_INFO and the default one (161). No
-Q -Q “timeout” - timeout in seconds for the snmpget operations. Defaults to 0, no timeout. No
-V -V “version” - SNMP protocol version. Allowed values are [1, 2]. Defaults 2 (v2c). No

Return Values:

VALOR SIGNIFICADO
-1 Error
N Number of down interfaces

Recommended Parameters:

Comparison Type Direct (-c 0). The higher value the higher severity.
monitoring interval 300 seconds – 1 hour –> Depends on instance importance
warning threshold 1
critical threshold 1

Example:

CICINTE0 = -t 300 -c 0 -w 1 -a 1 -T "Down Ifaces" -I "1,3,5,7" -Y "9,10,11" -P 177 -Q 3 -V 1

Comments: The associated text will show down interfaces (ifOperStatus = 2).
This event uses the Net-SNMP libraries

Trap Events Summary Table

Here is briefly the capabilities of this agent about its trap events, further down on this page we will describe each of the trap events in more detail.

EVENT DESCRIPTION
SNMPSTTE State of the router
LINKSTTE State of the router's interfaces
CIFALLRM RMON falling alarm
CIRISSRM RMON rising alarm
CIFALCPU CPU falling alarm
CIRISCPU CPU rising alarm
CIENVSTE Router's Environment status
CIEVENTF EVENT trigger alarm of type boolean or existence

Agent Trap Events

SNMPSTTE

This event give us the general state of the router. It is received when the router throw some of the generic traps.

  • TRAP: .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.coldStart
  • DESCRIPTION: A coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered.
  • VARBINDS: No
  • SEVERITY: 0 → OK.


  • TRAP: .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.warmStart
  • DESCRIPTION: A warmStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself such that its configuration is unaltered.
  • VARBINDS: No
  • SEVERITY: 0 → OK.


  • TRAP: .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.authenticationFailure
  • DESCRIPTION: An authenticationFailure trap signifies that the SNMP entity has received a protocol message that is not properly authenticated. While all implementations of SNMP entities MAY be capable of generating this trap, the snmpEnableAuthenTraps object indicates whether this trap will be generated.
  • VARBINDS: No
  • SEVERITY: 1 → Warning.


  • TRAP: .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.egpNeighborLoss
  • DESCRIPTION: An egpNeighborLoss trap signifies that an EGP neighbor for whom the sending protocol entity was an EGP peer has been marked down and the peer relationship no longer obtains.
  • VARBINDS: egpNeighAddr: The IP address of this entry's EGP neighbor.
  • SEVERITY: 1 → Warning.

LINKSTTE

This event give us the state of any of the router's interface. The interface is sent in the bind variable ifIndex of the trap (correlation key), and it is used for event correlation. For example, we will have two diferent events if two router's interfaces have gone down, but if the router is reinitializing itself and send a colStart trap, this trap correlate these two events.

  • TRAP: .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.linkDown
  • DESCRIPTION: linkDown trap signifies that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links is about to enter the down state from some other state (but not from the notPresent state). This other state is indicated by the included value of ifOperStatus.
  • VARBINDS: ifIndex: Interface number.
    ifAdminStatus: Configuration state (up,down,testing).
    ifOperStatus: Interface State (up,down,testing,unknown,dormant,notPresent,lowerLayerDown)
  • SEVERITY: 2 → Critical.


  • TRAP: .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.linkUp
  • DESCRIPTION: A linkUp trap signifies that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links left the down state and transitioned into some other state (but not into the notPresent state). This other state is indicated by the included value of ifOperStatus.
  • VARBINDS: ifIndex: Interface number.
    ifAdminStatus: Configuration state (up,down,testing).
    ifOperStatus: Interface State (up,down,testing,unknown,dormant,notPresent,lowerLayerDown)
  • SEVERITY: 2 → Critical.


  • TRAP: .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.coldStart
  • DESCRIPTION: A coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered.
  • VARBINDS: No
  • SEVERITY: 0 → OK.

CIFALLRM

This event is received when a “RMON falling alarm” is throwed for the router device. The alarm is confurated in the router and it is associated with an snmp variable whose oid is sent in the alarmVariable bind variable of the trap. This alarmVariable is the correlation key, then we can get different CIFALLRM events for differents alarmVariable oids, but if the router is reinitializing itself and send a colStart trap, this trap correlate these two events.

  • TRAP: .iso.org.dod.internet.mgmt.mib-2.rmon.rmonEventsV2.fallingAlarm
  • DESCRIPTION: The SNMP trap that is generated when an alarm entry crosses its falling threshold and generates an event that is configured for sending SNMP traps.
  • VARBINDS: alarmIndex: An index that uniquely identifies an entry in the alarm table. Each such entry defines a diagnostic sample at a particular interval for an object on the device.
    alarmVariable: The object identifier of the particular variable to be sampled. Only variables that resolve to an ASN.1 primitive type of INTEGER (INTEGER, Counter, Gauge, or TimeTicks) may be sampled.
    alarmSampleType: The method of sampling the selected variable and calculating the value to be compared against the thresholds (absoluteValue,deltaValue).
    alarmValue: The value of the statistic during the last sampling period. The value during the current sampling period is not made available until the period is completed.
    alarmFallingThreshold: A threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event will be generated.
  • SEVERITY: 2 → Critical.


  • TRAP: .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.coldStart
  • DESCRIPTION: A coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered.
  • VARBINDS: No
  • SEVERITY: 0 → OK.

CIRISSRM

This event is received when a “RMON rising alarm” is throwed for the router device. The alarm is confurated in the router and it is associated with an snmp variable whose oid is sent in the alarmVariable bind variable of the trap. This alarmVariable is the correlation key, then we can get different CIRISSRM events for differents alarmVariable oids, but if the router is reinitializing itself and send a colStart trap, this trap correlate these two events.

  • TRAP: .iso.org.dod.internet.mgmt.mib-2.rmon.rmonEventsV2.risingAlarm
  • DESCRIPTION: The SNMP trap that is generated when an alarm entry crosses its rising threshold and generates an event that is configured for sending SNMP traps.
  • VARBINDS: alarmIndex: An index that uniquely identifies an entry in the alarm table. Each such entry defines a diagnostic sample at a particular interval for an object on the device.
    alarmVariable: The object identifier of the particular variable to be sampled. Only variables that resolve to an ASN.1 primitive type of INTEGER (INTEGER, Counter, Gauge, or TimeTicks) may be sampled.
    alarmSampleType: The method of sampling the selected variable and calculating the value to be compared against the thresholds (absoluteValue,deltaValue).
    alarmValue: The value of the statistic during the last sampling period. The value during the current sampling period is not made available until the period is completed.
    alarmRisingThreshold: A threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event will be generated.
  • SEVERITY: 2 → Critical.


  • TRAP: .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.coldStart
  • DESCRIPTION: A coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered.
  • VARBINDS: No
  • SEVERITY: 0 → OK.

CIFALCPU

This event is received when a “CPU falling alarm” is throwed for the router device when the CPU busy porcentge of the router has falled below the value of the bind variable cpmCPUFallingThresholdValue.

  • TRAP: .iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoProcessMIB.
    ciscoProcessMIBNotifPrefix.ciscoProcessMIBNotifs.cpmCPUFallingThreshold
  • DESCRIPTION: A cpmCPUFallingThresholdTrap is sent when the configured falling threshold (cpmCPURisingThresholdValue) is reached and CPU utilization remained under threshold for configured interval (cpmCPUFallingThresholdPeriod) and such a notification is requested.
  • VARBINDS: cpmCPUFallingThresholdValue: The percentage falling threshold value configured by the user. The value indicates, if the percentage CPU utilization is equal to or below this value for cpmCPUFallingThresholdPeriod duration then send a cpmCPUFallingThreshold notification to the NMS.
    cpmCPUTotalMonIntervalValue y cpmCPUInterruptMonIntervalValue: CPU busy porcentage values.
  • SEVERITY: 2 → Critical.


  • TRAP: .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.coldStart
  • DESCRIPTION: A coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered.
  • VARBINDS: No
  • SEVERITY: 0 → OK.

CIRISCPU

This event is received when a “CPU rising alarm” is throwed for the router device when the CPU busy porcentge of the router has raised above the value of the bind variable cpmCPURisingThresholdValue.

  • TRAP: .iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoProcessMIB.
    ciscoProcessMIBNotifPrefix.ciscoProcessMIBNotifs.cpmCPURisingThreshold
  • DESCRIPTION: A cpmCPURisingThreshold notification is sent when configured rising CPU utilization threshold (cpmCPURisingThresholdValue) is reached and CPU utilization remained above the threshold for configured interval(cpmCPURisingThresholdPeriod) and such a notification is requested.
  • VARBINDS: cpmCPURisingThresholdValue : The percentage rising threshold value configured by the user. The value indicates, if the percentage CPU utilization is equal to or above this value for cpmCPURisingThresholdPeriod duration then send a cpmCPURisingThreshold notification to the NMS
    cpmCPUTotalMonIntervalValue y cpmCPUInterruptMonIntervalValue: CPU busy porcentage values.
  • SEVERITY: 2 → Critical.


  • TRAP: .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.coldStart
  • DESCRIPTION: A coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered.
  • VARBINDS: No
  • SEVERITY: 0 → OK.

CIENVSTE

This event is received when an “Environment alarm” is throwed for the router device when the status of its Environmental Monitor has changed.

  • TRAP: .iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEnvMonMIB.
    ciscoEnvMonMIBNotificationPrefix.ciscoEnvMonMIBNotifications.
    ciscoEnvMonShutdownNotification
  • DESCRIPTION: A ciscoEnvMonShutdownNotification is sent if the environmental monitor detects a testpoint reaching a critical state and is about to initiate a shutdown. This notification contains no objects so that it may be encoded and sent in the shortest amount of time possible. Even so, management applications should not rely on receiving such a notification as it may not be sent before the shutdown completes.
  • VARBINDS:
  • SEVERITY: 2 → Critical.


  • TRAP: .iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEnvMonMIB.
    ciscoEnvMonMIBNotificationPrefix.ciscoEnvMonMIBNotifications.
    ciscoEnvMonVoltStatusChangeNotif
  • DESCRIPTION: A ciscoEnvMonVoltStatusChangeNotif is sent if there is change in the state of a device being monitored by ciscoEnvMonVoltageState
  • VARBINDS: ciscoEnvMonVoltageState: Voltage state (normal,warning,critical,shutdown,notPresent,notFunctioning). ciscoEnvMonVoltageStatusValue: Voltage value. ciscoEnvMonVoltageStatusDescr: Test description.
  • SEVERITY: Depend of ciscoEnvMonVoltageState:
    0 → normal. 1→ warning. 2→ critical o shutdown


  • TRAP: .iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEnvMonMIB.
    ciscoEnvMonMIBNotificationPrefix.ciscoEnvMonMIBNotifications.
    ciscoEnvMonTempStatusChangeNotif
  • DESCRIPTION: A ciscoEnvMonTempStatusChangeNotif is sent if there is change in the state of a device being monitored by ciscoEnvMonTemperatureState.
  • VARBINDS: ciscoEnvMonTemperatureState: Temperature state (normal,warning,critical,shutdown,notPresent,notFunctioning).
    ciscoEnvMonTemperatureStatusValue: Temperature value.
    ciscoEnvMonTemperatureStatusDescr: Test description.
  • SEVERITY: Depend of ciscoEnvMonTemperatureState:
    0 → normal. 1→ warning. 2→ critical o shutdown


  • TRAP: .iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEnvMonMIB.
    ciscoEnvMonMIBNotificationPrefix.ciscoEnvMonMIBNotifications.
    ciscoEnvMonFanStatusChangeNotif
  • DESCRIPTION: The current state of the fan being instrumented.
  • VARBINDS: ciscoEnvMonFanState: Fan state. (normal,warning,critical,shutdown,notPresent,notFunctioning).
    ciscoEnvMonFanStatusDescr: Test description.
  • SEVERITY: Depend of ciscoEnvMonFanState:
    0 → normal. 1→ warning. 2→ critical o shutdown


  • TRAP: .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.coldStart
  • DESCRIPTION: A coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered.
  • VARBINDS: No
  • SEVERITY: 0 → OK.

CIEVENTF

This event is received when a “EVENT Trigger” is throwed for the router device. The alarm is confurated in the router and it is associated with an snmp variable whose oid is sent in the mteHotOID bind variable of the trap. This mteHotOID is the correlation key, then we can get different CIEVENTF events for differents alarmVariable oids, but if the router is reinitializing itself and send a colStart trap, this trap correlate these two events.

  • TRAP: .iso.org.dod.internet.mgmt.mib-2.dismanEventMIB.

dismanEventMIBNotificationPrefix.dismanEventMIBNotifications.mteTriggerFired

  • DESCRIPTION: Notification that the trigger indicated by the object instances has fired, for triggers with mteTriggerType 'boolean' or 'existence'.
  • VARBINDS: mteHotTrigger: Trigger name.
    mteHotOID: The object identifier of the destination object related to the notification.
    mteHotValue: The value of the object when a trigger fired
  • SEVERITY: 2 → Critical.


  • TRAP: .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.coldStart
  • DESCRIPTION: A coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered.
  • VARBINDS: No
  • SEVERITY: 0 → OK.

Agent prerequisites

In order to compile, this agent requires a set of prerequisites, which are generic to compile any Osmius agent, you can see these prerequisites.

This agent needs also the Net-SNMP libraries and includes ( “libsnmp” in Ubuntu ) usually found here: http://net-snmp.sourceforge.net/.

Agent Makefiles and compilation

  • Make Project Creator (MPC) is used by Osmius, so creating Makefiles is a trivial task. If you want to learn more about MPC and Osmius check out the section of Makefiles on Osmius.
  • In the particular case of CIROUTER Osmius agent you can easily generate the Makefile as follows:

From the agent directory using console or terminal.

%ACE_ROOT%\bin\mpc.pl -type gnuace osm_ag_ciscorouter.mpc
  • Now that you created the Makefile, agent compiling is extremely simple.
gmake -f Osm_Ag_Ciscorouter_Osmius

Binaries are automatically installed in the bin directory of OSM_ROOT base directory.

Running the agente

Teh Osmius CIROUTER agent have the same running features of the other Osmius agents. You can check it out int he section Start and Stop Agents.

To run the CIROUTER agent without Osmius web console:

osm_ag_CIROUTER -c osm_ag_CIROUTER.ini -m MASTERAG -p 1950 -d [>> osm_ag_cirouter1.log]1)

Running in standalone mode

This Osmius agent, like the others Osmius agents, allows the execution in standalone mode. This option may be particularly useful when developing a new agent or to perform specific agent tests, but in CIROUTER agent stand alone mode we only can test “pool events” because “trap events” are received by Osmius SNMPTRAP Agent.

Basically you have to add a new value, called SNDCMD, to the Osmius agent configuration file (osm_ag_CIROUTER.ini) as shown here.

Then you must run the agent setting the Master Agent and communications port to zero, for example:

osm_ag_CIROUTER.exe -c osm_ag_CIROUTER.ini -m 00000000 -p 0 -d

Interface types

                        other(1),          
                        regular1822(2),
                        hdh1822(3),
                        ddn-x25(4),
                        rfc877-x25(5),
                        ethernet-csmacd(6),
                        iso88023-csmacd(7),
                        iso88024-tokenBus(8),
                        iso88025-tokenRing(9),
                        iso88026-man(10),
                        starLan(11),
                        proteon-10Mbit(12),
                        proteon-80Mbit(13),
                        hyperchannel(14),
                        fddi(15),
                        lapb(16),
                        sdlc(17),
                        ds1(18),           
                        e1(19),            
                        basicISDN(20),
                        primaryISDN(21),   
                        propPointToPointSerial(22),
                        ppp(23),
                        softwareLoopback(24),
                        eon(25),            
                        ethernet-3Mbit(26),
                        nsip(27),           
                        slip(28),           
                        ultra(29),          
                        ds3(30),            
                        sip(31),            
                        frame-relay(32)

Test List

Fecha: 01/12/2009
Test Results Comments
Creating an instance with all its events in silent mode N/A
Creating an instance with all its events with custom text N/A
Creating an instance with all its events but no custom text N/A
Declaration of 3 instances with all its events to 5 seconds and keep it
running for 48 hours
N/A
Declare 2 instances, cause a disconnect and then reconnect it can't be do in this agent N/A
Declare 1 instance and test each event OK N/A
Elimination of general parameter and check unbootable OK Delete RECONN
Elimination of instance CONN_INFO and check unbootable OK CIROUTER Instances don't need connection info
1) Optional, to store agent messages in a file
 
en/agentes/cirouter.txt · Last modified: 2012/12/05 19:03 by osmius
 
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki