SNMP in NexnetaStor

来源:互联网 发布:可用端口号范围 编辑:程序博客网 时间:2024/06/14 07:29
SNMP
Simple Network Management Protocol (SNMP) is a legacy network management protocol used to monitor and administer devices on the IP network. SNMP is standardized by the Internet Engineering Task Force (IETF).

An SNMP-managed network consists of three key components:

• Managed device (for instance NexentaStor appliance)
• SNMP agent (for instance, NexentaStor built-in agent)
• SNMP manager that executes SNMP Get, GetNext, Set operations37 to monitor and control the device.


NexentaStor provides a built-in SNMP agent that implements MIB-II a. k. a RFC-1213. More
exactly, the agent supports SNMPv2-MIB (MIB-II), HOST-RESOURCES-MIB, DISMANEVENT-
MIB, NOTIFICATION-LOG-MIB, and provides basic information to monitoring system
using SNMP protocol. This includes:
• Basic system (hostname, uptime, contacts, etc)
• Network interfaces (IP/MAC addresses, inbound/outbound traffic, errors, other)
• System load (CPUs, memory, folder usage)
• Processes
NexentaStor supports SNMP traps.
NexentaStor supports all three versions of SNMP protocol, including SNMPv3.
Setting up SNMP agent

Basic setup will be done using the following NMC command (example):


nmc:/$ setup network service snmp-agent configure

Read-only community string : public
Read-write community string : private
User name for SNMPv3 agent : alpha
Password for SNMPv3 agent. Must be at least 8 characters : pass1234
Destination of SNMP-traps :

192.168.1.55
The example above configures SNMP agent with a (sample) user account. Note that SNMPv3 usesMD5 for authentication and DES for privacy.

Once SNMP agent on the appliance is configured, you can execute a simple MIB walk from a
remote appliance, for instance:
# snmpwalk -v 3 -a md5 -A pass1234 -u alpha -l authPriv -x DES -X pass1234 <ip_of_appliance> sysUpTime
The example above assumes that the remote host has snmpwalk utility (NexentaStor does include
it), and that the user/password is specified as 'alpha' and 'pass1234', respectively. A sample
output follows below:
-------------------------------------
SNMPv2-MIB::sysDescr.0 = STRING: abc
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.3
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (25964852) 3 days, 0:07:28.52
SNMPv2-MIB::sysContact.0 = STRING: johnsmith
SNMPv2-MIB::sysName.0 = STRING: devel119
SNMPv2-MIB::sysLocation.0 = STRING: corpoffice
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (6) 0:00:00.06
SNMPv2-MIB::sysORID.1 = OID: SNMP-FRAMEWORK-MIB::snmpFrameworkMIBCompliance
...
IF-MIB::ifNumber.0 = INTEGER: 2
IF-MIB::ifIndex.1 = INTEGER: 1
IF-MIB::ifIndex.2 = INTEGER: 2
IF-MIB::ifDescr.1 = STRING: lo0
IF-MIB::ifDescr.2 = STRING: ae0
IF-MIB::ifType.1 = INTEGER: softwareLoopback(24)
IF-MIB::ifType.2 = INTEGER: other(1)
IF-MIB::ifMtu.1 = INTEGER: 8232
IF-MIB::ifMtu.2 = INTEGER: 1500
IF-MIB::ifSpeed.1 = Gauge32: 127000000
IF-MIB::ifSpeed.2 = Gauge32: 10000000
IF-MIB::ifPhysAddress.1 = STRING:
...

RFC1213-MIB::atIfIndex.2.1.192.168.1.111 = INTEGER: 2
RFC1213-MIB::atIfIndex.2.1.192.168.1.119 = INTEGER: 2
RFC1213-MIB::atIfIndex.2.1.192.168.1.200 = INTEGER: 2
...
RFC1213-MIB::atIfIndex.2.1.224.0.0.0 = INTEGER: 2
RFC1213-MIB::atPhysAddress.2.1.192.168.1.55 = Hex-STRING: 00 1F D0 9E D2 25
RFC1213-MIB::atPhysAddress.2.1.192.168.1.77 = Hex-STRING: 00 22 15 D4 F5 BC
RFC1213-MIB::atPhysAddress.2.1.192.168.1.111 = ""
RFC1213-MIB::atPhysAddress.2.1.192.168.1.119 = Hex-STRING: 00 0C 29 8A 55 2A

RFC1213-MIB::atPhysAddress.2.1.192.168.1.200 = Hex-STRING: 00 0C 29 17 16 6D

RFC1213-MIB::atPhysAddress.2.1.224.0.0.0= Hex-STRING: 01 00 5E 00 00 00

RFC1213-MIB::atNetAddress.2.1.192.168.1.55= Network Address: C0:A8:01:37

RFC1213-MIB::atNetAddress.2.1.192.168.1.77= Network Address: C0:A8:01:4D

RFC1213-MIB::atNetAddress.2.1.192.168.1.111= Network Address: C0:A8:01:6F

RFC1213-MIB::atNetAddress.2.1.192.168.1.119= Network Address: C0:A8:01:77

RFC1213-MIB::atNetAddress.2.1.192.168.1.200= Network Address: C0:A8:01:C8

RFC1213-MIB::atNetAddress.2.1.224.0.0.0= Network Address: E0:00:00:00

IP-MIB::ipForwarding.0 =INTEGER: notForwarding(2)

IP-MIB::ipDefaultTTL.0 =INTEGER: 255

IP-MIB::ipInReceives.0 =Counter32: 77366

IP-MIB::ipInHdrErrors.0 =Counter32: 0

IP-MIB::ipInAddrErrors.0= Counter32: 0

IP-MIB::ipForwDatagrams.0= Counter32: 0

IP-MIB::ipInUnknownProtos.0= Counter32: 0

IP-MIB::ipInDiscards.0 =Counter32: 0

IP-MIB::ipInDelivers.0 =Counter32: 80748

IP-MIB::ipOutRequests.0 =Counter32: 62375

IP-MIB::ipOutDiscards.0 =Counter32: 18

IP-MIB::ipOutNoRoutes.0 =Counter32: 0

IP-MIB::ipReasmTimeout.0= INTEGER: 15 seconds

IP-MIB::ipReasmReqds.0 =Counter32: 0

IP-MIB::ipReasmOKs.0 =Counter32: 0

IP-MIB::ipReasmFails.0 =Counter32: 0

IP-MIB::ipFragOKs.0 =Counter32: 0

...

------------------

Alternatively, use any compliant MIB browser to walk the appliance's MIB.

Advanced configuration of the NexentaStor SNMP agent can be done via:

nmc:/$ setup networkservice snmp-agent edit-settings

For details on SNMP configuration, please see 'help snmpd.conf'.

nmc:/$ help snmpd.conf