Snmp Status Reporting And Traps; Retrieving Status Information Using Snmp; Check Firewall Rules; Enable Snmp Service - Tripp Lite B092-016 Owner's Manual

Console server management switch console server with poweralert console server
Hide thumbs Also See for B092-016:
Table of Contents

Advertisement

Chapter 15: Advanced Configuration

15.5 SNMP Status Reporting and Traps

Console Servers can send traps/messages to multiple remote SNMP Network Managers on defined trigger events (as detailed
in Chapter 7). Console Servers also contain an SNMP Service (snmpd) which can provide status information on demand. From
the snmpd manual page:
snmpd is an SNMP agent which binds to a port and awaits requests from SNMP management software. Upon receiving
a request, it processes the request(s), collects the requested information and/or performs the requested operation(s) and
returns the information to the sender.

15.5.1 Retrieving status information using SNMP

Console Servers can provide serial and device status information through SNMP . This includes
• Serial port status
• Active users
• Remote Power Control (RPC) and Power Distribution Unit (PDU) status
• Environmental Monitoring Device (EMD) status
• Signal alert status
• Environmental alert status and
• UPS alert status
The MIBs in your Console Server are located in /etc/snmp/mibs.
OG-STATUS-MIB
This new MIB contains serial and connected device status information (for snmpstatusd & snmpalertd)
OG-SMI-MIB
Enterprise structure of management information
OGTRAP-MIB
SMIv1 traps from old MIBS (as smilint will not let SMIv1 structures coexist with SMIv2)

15.5.2 Check firewall rules

• Select System: Firewall and ensure the SNMP daemon box has been checked for the interface required
This will allow SNMP requests through the firewall for the specified interface.

15.5.3 Enable SNMP service

The Console Server supports different versions of SNMP including SNMPv1, SNMPv2c and SNMPv3.
SNMP , although an industry standard, brings with it a variety of security concerns. For example, SNMPv1 and SNMPv2c offer
no inherent privacy, while SNMPv3 is susceptible to man-in-the-middle attacks. Recent IETF developments suggests tunnelling
SNMP over widely accepted technologies such as SSH (Secure Shell) or TLS (Transport Layer Security) rather than relying on a
less mature security systems such as SNMPv3's USM (User-based Security Model).
Additional information regarding SNMP security issues and SNMPv3 can be found at:
http://net-snmp.sourceforge.net/wiki/index.php/TUT:Security
http://www.ietf.org/html.charters/snmpv3-charter.html.
• Select Alerts & Logging: SNMP
214

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents