Category:HowTo:SNMP

From Snom User Wiki

Jump to: navigation, search

Enabling SNMP

By default, the phone will not accept SNMP requests. This is necessary because SNMP might introduce unwanted security threats. To enable SNMP, you must specify what IP addressed may send SNMP requests to the phone. This can be done via Web Interface > SNMP Section

Two formats are allowed for the settings:

  • SNMP port - you may specify a different port than 161 for SNMP. Because the phone only runs one SNMP server on the device, changing the port should usually not be necessary
  • The IP address (e.g. “192.168.4.5”) of the SNMP manager or the subnet address (address/subnet* e.g. 192.168.5.0/24 allows accesses from hosts 192.168.5.0 to 192.168.5.255) can be specified. You may use several entries separated by space. For example, “192.168.5.6 192.168.5.7” will allow accesses from the two listed IP addresses.

*The subnet indicates how many bits of the address are significant.

Reading Information

The phone only supports the GET request of SNMP. SET or other requests are not supported. For configuration and advances usage of the phone, please use the web server of the phone. The table on this page shows the available object identifiers (OID) on the phones.

The statistics covers data send and received on all interfaces of the phone. This includes all VLAN interfaces and the standard interface, but not the loopback device. The traffic of the built-in switch which by-passes the phone is not measured.

The number of calls is incremented whenever the phone writes a log into the local call statistics dictionary (for redial, missed calls, etc.).

The number of registrations can be used for sanity-checking of the phones. If the number goes down to zero, the phone has a problem and the SNMP manager should generate an alarm.

OID Name Unit Description
1.3.6.1.2.1.7526.2.1.1Rx BytesIntegerThe total number of bytes received
1.3.6.1.2.1.7526.2.1.2Rx PacketsIntegerThe total number of packets received
1.3.6.1.2.1.7526.2.2.1Tx BytesIntegerThe total number of bytes sent
1.3.6.1.2.1.7526.2.2.2Tx PacketsIntegerThe total number of packets sent
1.3.6.1.2.1.7526.2.3.xRegistrationIntegerRegistration status of registration x (1..12) (works with v6.5 or newer)
1.3.6.1.2.1.7526.2.4Firmware & U-Boot VersionStringThe currently used firmware & uboot version (for example, “snom 360-SIP 3.60d 113-m”)
1.3.6.1.2.1.7526.2.5RegistrationsIntegerThe number of registrations on the phone
1.3.6.1.2.1.7526.2.6CallsIntegerThe number of successful and unsuccessful calls
1.3.6.1.2.1.7526.2.7MemfreeIntegerThe free memory on the phone
1.3.6.1.2.1.7526.2.8UptimeStringThe running time of the phone
1.3.6.1.2.1.7526.2.9CPU load averageStringThe CPU load average of last 1min., 5min. and 15min. (> V8.2.6)
1.3.6.1.2.1.7526.2.10MeminfoStringInfo about memory: used, free, cached, lid (phone lowlevel app.), lcs (phone highlevel app.) (> V8.2.6)
1.3.6.1.2.1.7526.2.11LCS UptimeStringThe running time of the phone highlevel application (> V8.2.6)
1.3.6.1.2.1.7526.2.12PacketsStringThe incoming and outgoing messages (> V8.2.6)
1.3.6.1.2.1.7526.2.13ConnectionsStringThe connections (> V8.2.6)
1.3.6.1.2.1.7526.2.14TimeoutsStringThe number of timeouts running (> V8.2.6)
1.3.6.1.2.1.7526.2.15SubscriptionsStringThe subscriptions (> V8.2.6)

SNMP Test Tools

There is a SNMP Test Suite available at http://www.net-snmp.org/.

Basic GET requests can be run in order to check the functionality:

snmpget -v1 -c public 192.168.X.X 1.3.6.1.2.1.7526.2.4
SNMPv2-SMI::mib-2.7526.2.4 = STRING: "snom360-SIP 6.2.2"

snmpget -v1 -c public 192.168.X.X 1.3.6.1.2.1.7526.2.1.1
SNMPv2-SMI::mib-2.7526.2.1.1 = INTEGER: 290555143 

snmpget -v1 -c public 192.168.X.X 1.3.6.1.2.1.7526.2.1.2
SNMPv2-SMI::mib-2.7526.2.1.2 = INTEGER: 1941870

This category currently contains no pages or media.

Personal tools
Interoperability