Snmp issue

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
lannister
Posts: 28
Joined: Mon Apr 28, 2014 4:49 am

Re: Snmp issue

Post by lannister »

Hi ,

Please find the details, Clarioon .txt is not there now.

Code: Select all

[root@localhost snmp]# cat snmptt.conf
#
#
#
EVENT coldStart .1.3.6.1.6.3.1.1.5.1 "Status Events" Normal
FORMAT Device reinitialized (coldStart)
#EXEC qpage -f TRAP notifygroup1 "Device reinitialized (coldStart)"
SDESC
A coldStart trap signifies that the SNMPv2 entity, acting
in an agent role, is reinitializing itself and that its
configuration may have been altered.
EDESC
#
#
#
EVENT warmStart .1.3.6.1.6.3.1.1.5.2 "Status Events" Normal
FORMAT Device reinitialized (warmStart)
#EXEC qpage -f TRAP notifygroup1 "Device reinitialized (warmStart)"
SDESC
A warmStart trap signifies that the SNMPv2 entity, acting
in an agent role, is reinitializing itself such that its
configuration is unaltered.
EDESC
#
#
#
EVENT linkDown .1.3.6.1.6.3.1.1.5.3 "Status Events" Normal
FORMAT Link down on interface $1.  Admin state: $2.  Operational state: $3
#EXEC qpage -f TRAP notifygroup1 "Link down on interface $1.  Admin state: $2.  Operational state: $3"
SDESC
A 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.
EDESC
#
#
#
EVENT linkUp .1.3.6.1.6.3.1.1.5.4 "Status Events" Normal
FORMAT Link up on interface $1.  Admin state: $2.  Operational state: $3
#EXEC qpage -f TRAP notifygroup1 "Link up on interface $1.  Admin state: $2.  Operational state: $3"
SDESC
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.
EDESC
#
#
#
EVENT authenticationFailure .1.3.6.1.6.3.1.1.5.5 "Status Events" Normal
FORMAT SNMP athentication failure
#EXEC qpage -f TRAP notifygroup1 "SNMP authentication failure"
SDESC
An authenticationFailure trap signifies that the SNMPv2
entity, acting in an agent role, has received a protocol
message that is not properly authenticated.  While all
implementations of the SNMPv2 must be capable of generating
this trap, the snmpEnableAuthenTraps object indicates
whether this trap will be generated.
EDESC
#
#
#
#
MIB: CLARIION-MIB (file:/usr/share/snmp/mibs/clariion.mib) converted on Mon Jun 30 16:08:06 2014 using snmpttconvertmib v1.3
#
#
#
EVENT EventMonitorTrap .1.3.6.1.4.1.1981.0.2 "Status Events" Normal
FORMAT An EventMonitorTrap is generated in $*
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "An EventMonitorTrap is generated in $*"
SDESC
An EventMonitorTrap is generated in
response to a user-specified event.
Details can be found in Variables data.
Variables:
  1: hostName
  2: deviceID
  3: eventID
  4: eventText
  5: storageSystem
EDESC
#
#
#
EVENT EventMonitorTrapInfo .1.3.6.1.4.1.1981.0.3 "Status Events" Normal
FORMAT An Informational EventMonitorTrap is generated in $*
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "An Informational EventMonitorTrap is generated in $*"
SDESC
An Informational EventMonitorTrap is generated in
response to a user-specified event.
Details can be found in Variables data.
Variables:
  1: hostName
  2: deviceID
  3: eventID
  4: eventText
  5: storageSystem
EDESC
#
#
#
EVENT EventMonitorTrapWarn .1.3.6.1.4.1.1981.0.4 "Status Events" Normal
FORMAT A Warning EventMonitorTrap is generated in $*
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "A Warning EventMonitorTrap is generated in $*"
SDESC
A Warning EventMonitorTrap is generated in
response to a user-specified event.
Details can be found in Variables data.
Variables:
  1: hostName
  2: deviceID
  3: eventID
  4: eventText
  5: storageSystem
EDESC
#
#
#
EVENT EventMonitorTrapError .1.3.6.1.4.1.1981.0.5 "Status Events" Normal
FORMAT An Error EventMonitorTrap is generated in $*
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "An Error EventMonitorTrap is generated in $*"
SDESC
An Error EventMonitorTrap is generated in
response to a user-specified event.
Details can be found in Variables data.
Variables:
  1: hostName
  2: deviceID
  3: eventID
  4: eventText
  5: storageSystem
EDESC
#
#
#
EVENT EventMonitorTrapFault .1.3.6.1.4.1.1981.0.6 "Status Events" Normal
FORMAT A Fault EventMonitorTrap is generated in $*
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "A Fault EventMonitorTrap is generated in $*"
SDESC
A Fault EventMonitorTrap is generated in
response to a user-specified event.
Details can be found in Variables data.
Variables:
  1: hostName
  2: deviceID
  3: eventID
  4: eventText
  5: storageSystem
EDESC
- Lan
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: Snmp issue

Post by slansing »

Can you attach your snmptt.ini so we can see if the mib got configured in its own conf file? Thanks!
lannister
Posts: 28
Joined: Mon Apr 28, 2014 4:49 am

Re: Snmp issue

Post by lannister »

Hi ,

PFA

- Lan
You do not have the required permissions to view the files attached to this post.
sreinhardt
-fno-stack-protector
Posts: 4366
Joined: Mon Nov 19, 2012 12:10 pm

Re: Snmp issue

Post by sreinhardt »

Well you do have the clarion oids added correctly to snmptt.conf, however your snmptt.ini is specifying a clariion.txt first, so if that is getting picked up with improper settings, it will overtake the correct settings in snmptt.conf. Please attach the file /usr/share/snmp/mibs/processed_mibs/clariion.txt
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
lannister
Posts: 28
Joined: Mon Apr 28, 2014 4:49 am

Re: Snmp issue

Post by lannister »

It says there is no such file or directory :(


- Lan
sreinhardt
-fno-stack-protector
Posts: 4366
Joined: Mon Nov 19, 2012 12:10 pm

Re: Snmp issue

Post by sreinhardt »

Ok can you post the clarion mib that you need to import to get this working, and I can take a look at the output from importing it on my system.
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
lannister
Posts: 28
Joined: Mon Apr 28, 2014 4:49 am

Re: Snmp issue

Post by lannister »

Im sorry i did not understand the clarion mib?

- Lan
sreinhardt
-fno-stack-protector
Posts: 4366
Joined: Mon Nov 19, 2012 12:10 pm

Re: Snmp issue

Post by sreinhardt »

The file that you originally downloaded from the clarion manufacturer, that should have been imported into nagios, so that snmptt knows about the OIDs that it might send. This is the file we are looking for. We need to see if this has any OIDs that match the ones coming into snmptt.
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
Locked