Professional Documents
Culture Documents
SNMP uses variables to read/write data which are known as object identifiers (OIDs). An OID
identifies a specific type of information using a sequence of numbers. All OIDs for a managed
device comprise a Management Information Base (MIB). An MIB contains all data that a device
can expose through SNMP. The manufacturer of the device provides this information in the form
of an MIB text file. The NMS uses these MIB files to translate OID strings into readable text.
2.1.2 Commands
SNMP uses four basic commands to enable communication between an SNMP agent and
NMS. An NMS can retrieve or set data stored within managed devices. Similarly, an SNMP
agent can broadcast data to the NMS.
The four basic SNMP operations are:
• READ: The READ command is used by the NMS to retrieve data from the SNMP agent.
This command is used to monitor managed devices. The NMS reads different variables
maintained by managed devices.
• WRITE: The WRITE command is used by the NMS to set the data stored within
managed devices. The NMS can change the values of the variables stored within the
managed devices.
• TRAP: The TRAP command is used by the managed devices to send a notification to
the NMS. A trap is sent to the NMS when a specific type of event is triggered on the
managed device.
• INFORM: The INFORM command is used by the NMS for traversal operations to know
which variables are supported by the managed device. The NMS stores this information
in variable tables.
• SNMPv2c: SNMPv2c includes support for data encryption and uses data types (such as
64-bit counters) not used in SNMPv1. SNMPv2c uses two types of community strings:
o The read-only community string allows read-only access to the MIB objects.
o The read-write community string allows users read and write access to the MIB
objects. The users can edit the configurations of SNMP-enabled devices by
logging into the SNMP manager.
• SNMPv3: SNMPv3 is the most secure version of SNMP allowing full encrypted
transmissions. The transmitted data cannot be accessed by external attackers.
Refer to the following figure demonstrating an example SNMP implementation using ELX1-LTE-
A.
In this implementation, the machine with IP 10.20.254.106 is used as the Network Manager.
ELX1-LTE-A acts as a managed device having a built-in SNMP agent. When ELX1-LTE-A
receives an NSM Request from the Manager, it frames the required Response and sends it in
the SNMP v2c/v3 format.
The SNMP agent uses the PROSOFT-ELX1-MIB file to store and retrieve management
information from the local environment. This MIB file contains the following read-only
parameters (as OIDs):
Description
Version Info
Cellular Connection IMEI Number, APN, Active SIM, SIM details, data usage
Details
The PROSOFT-ELX1-MIB file also defines specific trap messages and their alert conditions,
such as data usage alerts, activity alerts, memory alerts, digital IO alerts, and PSC tunnel alerts.
With SNMP traps, the SNMP agent informs the SNMP Manager once a significant event occurs
on ELX1-LTE-A, such as opening or closing tunnel by ProSoft Connect.
To set up communication between the SNMP Manager and the SNMP agent:
1. Configure the SNMP agent with the IP address of the SNMP Manager
2. Compile the MIB file of the SNMP agent into the SNMP Manager
2.1.3.2 Validation
This section describes a sample validation process performed on ELX1-LTE-A and the SNMP
Manager. The default SNMP port number is 161 and the default protocol is UDP.
On ELX1-LTE-A:
The following steps demonstrate checking the network statistics on the default SNMP port on
the ELX1-LTE-A and viewing the management information (such as LAN interface name, IP
Address, Subnet, Gateway, and DSN) stored inside the MIB file.
1. The SNMP agent runs on the ELX1-LTE-A and collects local information as defined in
MIBs. To check the connection on the default SNMP port, run the netstat command:
2. To fetch a sample LAN table information used on ELX1-LTE-A, run the cat command: