Need help with finding the correct OID for use with check_sn

Hi Everyone,

I need help with finding the correct OID for checking the message queue on a Symantec Mail Security 8340 device. I want to use check_snmp to monitor this but don’t know what OID to use. I have the MIB for this device, see below. Can anyone determine the OID for checking the QueueMessages object? Or do I need more information to get this?

Thanks,

[blockquote]SYMANTEC-EMAIL-SECURITY DEFINITIONS ::= BEGIN

IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
Gauge32,
enterprises, Integer32
FROM SNMPv2-SMI
DisplayString
FROM SNMPv2-TC;

mailSecurityAppliance MODULE-IDENTITY
LAST-UPDATED “200506200000Z”
ORGANIZATION “Symantec Corporation”
CONTACT-INFO
" Symantec Corporation
20300 Stevens Creek Blvd.
Cupertino, CA 95104
US

	    408-517-8000"
DESCRIPTION
	"The MIB module to describe MTA instances running on
	SMS appliances.."
REVISION	"200506200000Z"
DESCRIPTION
	"Initial revision."
::= { sms 2 }

symantec OBJECT IDENTIFIER ::= { enterprises 393 }
products OBJECT IDENTIFIER ::= { symantec 200 }
sms OBJECT IDENTIFIER ::= { products 130 }

hardware OBJECT IDENTIFIER ::= { mailSecurityAppliance 1 }
mta OBJECT IDENTIFIER ::= { mailSecurityAppliance 2 }

app8240 OBJECT IDENTIFIER ::= { hardware 1 }
app8260 OBJECT IDENTIFIER ::= { hardware 2 }

– MTA related OIDs

instanceTable OBJECT-TYPE
SYNTAX SEQUENCE OF InstanceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
“A list of Instance Entries containing information about the
MTA instances running on the appliance.”
::= { mta 1 }

instanceEntry OBJECT-TYPE
SYNTAX InstanceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
“Describes a single MTA instance running on the appliance.”
INDEX { instanceIndex }
::= { instanceTable 1 }

InstanceEntry ::=
SEQUENCE {
instanceIndex Integer32,
instanceDescr DisplayString,
connections Gauge32,
dataRate Gauge32,
deferredMessages Gauge32,
messageRate Gauge32,
queueSize Gauge32,
queuedMessages Gauge32
}

instanceIndex OBJECT-TYPE
SYNTAX Integer32 (0…8)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“The instance index for this MTA instance”
::= { instanceEntry 1 }

instanceDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0…255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“The instance name for this instance of the MTA object.”
::= { instanceEntry 2 }

connections OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“The number of connections for this MTA instance”
::= { instanceEntry 3 }

dataRate OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“The data rate for this MTA instance”
::= { instanceEntry 4 }

deferredMessages OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“The number of deferred messages for this MTA instance”
::= { instanceEntry 5 }

messageRate OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“The message rate for this MTA instance”
::= { instanceEntry 6 }

queueSize OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“The queue size for this MTA instance”
::= { instanceEntry 7 }

queuedMessages OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“The number of queued messages for this MTA instance”
::= { instanceEntry 8 }

– Hardware related OIDs

powerSupplyRedundancy OBJECT-TYPE
SYNTAX INTEGER {
fullyRedundant(1),
redundancyLost(2),
redundancyUnknown(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“Redundancy status of the appliance power supplies.”
::= { app8260 1 }

fanRedundancy OBJECT-TYPE
SYNTAX INTEGER {
fullyRedundant(1),
redundancyLost(2),
redundancyUnknown(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“Redundancy status of the appliance fans.”
::= { app8260 2 }

systemBlowerFan OBJECT-TYPE
SYNTAX INTEGER {
Pass(1),
Fail(2),
Unknown(3),
Unavailable(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“Pass/Fail status of the system blower fan”
::= { app8240 1 }

systemMemoryFan OBJECT-TYPE
SYNTAX INTEGER {
Pass(1),
Fail(2),
Unknown(3),
Unavailable(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“Pass/Fail status of the system memory fan”
::= { app8240 2 }

systemPciFan OBJECT-TYPE
SYNTAX INTEGER {
Pass(1),
Fail(2),
Unknown(3),
Unavailable(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“Pass/Fail status of the system PCI fan”
::= { app8240 3 }

internalAmbientTemperature OBJECT-TYPE
SYNTAX INTEGER {
Pass(1),
Fail(2),
Unknown(3),
Unavailable(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“Pass/Fail status of the internal ambient temperature”
::= { app8240 4 }

CpuInternalTemperature OBJECT-TYPE
SYNTAX INTEGER {
Pass(1),
Fail(2),
Unknown(3),
Unavailable(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“Pass/Fail status of the CPU internal temperature”
::= { app8240 5 }

END[/blockquote]

Run snmpwalk from the terminal. Syntax:

If that doesn’t work do a complete snmpwalk:

and find the one that suits you, and to get the OID in numbers, run it with the -On switch:

x.x.x.x is of course ip address of the host

You da man Albin. Thanks for your help.

It took me awhile to discover that I needed to import the MIB for Albin’s suggestion to work. Once I did that everything started to come together. Using the commands snmpwalk and snmptranslate, I was able to get the OID’s that I needed. I wanted to post this information in hopes that it will help someone else with this device.

Use the following OID’s for monitoring a Symantec Mail Security 8240 or 8340 network appliance with the Nagios Check_snmp command.

System uptime - 1.3.6.1.2.1.1.3.0
Delivery queue # of Messages - 1.3.6.1.4.1.393.200.130.2.2.1.1.8.1
Delivery deferred queue # of Messages - 1.3.6.1.4.1.393.200.130.2.2.1.1.5.1
Delivery queue size in KB - 1.3.6.1.4.1.393.200.130.2.2.1.1.7.1

Inbound queue # of Messages - 1.3.6.1.4.1.393.200.130.2.2.1.1.8.2
Inbound deferred queue # of Messages - 1.3.6.1.4.1.393.200.130.2.2.1.1.5.2
Inbound queue size in KB - 1.3.6.1.4.1.393.200.130.2.2.1.1.7.2

Outbound queue # of Messages - 1.3.6.1.4.1.393.200.130.2.2.1.1.8.3
Outbound deferred queue # of Messages - 1.3.6.1.4.1.393.200.130.2.2.1.1.5.3
Outbound queue size in KB - 1.3.6.1.4.1.393.200.130.2.2.1.1.7.3