4RF Aprisa LTE, User Manual

Page: 235 / 248

Managing the LTE | 235
Aprisa LTE User Manual 2.1
SNMP Management
The Aprisa LTE has a built-in SNMP agent to enable NMS (Network Management System) FCAPS (Fault,
Configuration, Administration, Provisioning and Security) management model. Any 3rd Party NMS supporting
SNMPv1/v2c/v3 can integrate with Aprisa LTE and manage it as part of a network wide management.
SNMPv1/v2c can be used to manage Aprisa LTE in a non-secure management connection.
SNMPv3 is used to manage the Aprisa LTE in a secure management connection. SNMPv3 support standard
USM model with the ability to configure user authentication and privacy (encryption) as per the standard
and with wider and strong authentication and privacy (encryption) protocols.
To set SNMP management connection, navigate to ‘ Security > SNMPv2/v3 ’ on page 180.
SNMPv2c and TRAP/Informs
The Aprisa LTE SNMP agent support v1 TRAP, v2c TRAP and inform. It supports configuration of multiple NMS
that shall receive TRAP and Inform from the Aprisa LTE when alarms/events are logged.
In general, a standard SNMP TRAP agent supports SNMP engine ID. This is supported by using the standard
method of negotiation between the NMS and Aprisa LTE where the Aprisa LTE provides this engine ID to the
NMS, thus it is not a configurable parameter in Aprisa LTE. The engine ID must be unique per each device in
the network and thus it is composed by a hash function of the Aprisa LTE MAC address.
To set multiple NMSs to receive the SNMP TRAP/Informs from the Aprisa LTE, navigate to ‘ Events > Trap
Setup ’ on page 199.
SNMP MIB Structure
The Aprisa LTE and in general other 4RF devices provide generic MIB interfaces for its products. This is to
help provide a common and easily extendable management interface across the 4RF product range.
To easily find an SNMP object/OID (Object ID) in Aprisa LTE using a MIB browser, navigate to the
.private.enterprises.fourRFRoot.fourRFGeneric node on the MIB tree structure and walk through the objects
within this node.
An example of the 4RF MIB Tree structure is shown as follows:
The generic interfaces are common across the family of 4RF products and will enable third party
management systems to manage the 4RF products in the same manner and use a common interface.