The Administrator can configure the snmpd Simple Network Management Protocol (SNMP) agent that resides on the Opengear device to send SNMP trap alerts to a remote NMS management application. To do this you must configure a SNMP Manager (or multiple managers) telling where and how outgoing SNMP alerts and notifications are sent.
- Select Alerts & Logging: SNMP
- Select Primary SNMP Manager tab
- Select the Manager Protocol. SNMP is generally a UDP-based protocol though infrequently it uses TCP instead.
- Enter the host address of the SNMP Network Manager into the Manager Address field.
- Enter the TCP/IP port number into the Manager Trap Portfield (default =162).
- Select the Version to be used. The console server SNMP agent supports SNMP v1, v2 and v3
- Enter the Community name for SNMP v1 or SNMP v2c. At a minimum, a community needs to be set for either SNMP v1 or v2c traps to work. An SNMP community is the group to which devices and management stations running SNMP belong. It helps define where information is sent. SNMP default communities are private for Write and public for Read.
- Configure SNMP v3 if required. For SNMP v3 messages, the user’s details and security level must match what the receiving SNMP Network Manager is expecting. SNMP v3 mandates that the message will be rejected unless the SNMPv3 user sending the trap already exists in the user database on the SNMP Manager. The user database in a SNMP v3 application is actually referenced by a combination of the Username and the Engine ID for the given SNMP application you are talking to.
- Enter the Engine ID for the user sending messages as a hex number e.g. 0x8000000001020304.
- Specify the Security Level. The level of security has to be compatible with the settings of the remote SNMP Network Manager.
|
noAuthNoPriv |
No authentication or encryption. |
|
authNoPriv |
Authentication only. An authentication protocol (SHA or MD5) and password will be required. |
|
authPriv |
Uses both authentication and encryption. This is the highest level of security and requires an encryption protocol (DES or AES) and password in addition to the authentication protocol and password. |
- Complete the Username. This is the Security Name of the SNMPv3 user sending the message. This field is mandatory and must be completed when configuring the console server for SNMPv3.
- An Authentication Protocol (SHA or MD5) and Authentication Password must be given for a Security Level of either authNoPriv or authPriv. The password must contain at least 8 characters to be valid.
- A Privacy Protocol (DES or AES) must be specified for the authPriv level of security to be used as the encryption algorithm. AES is recommended for stronger security. A password of at least 8 characters must be provided for encryption to work.
- Click Apply
Note Console servers with V3.0 firmware (and later) also embed the net-snmpd daemon which can accept SNMP requests from remote SNMP management servers and provides information on serial port and device status
Note: Some new SNMP status and trap MIBs were created in firmware versions 3.10.2 and above, to provide more and better structured SNMP status and traps from the console servers. However there is an option to Use Legacy Notifications for the SNMP traps. Setting this option means the console server will send the older SNMP traps that are compatible with those sent in older firmware before the new MIBS were added - ensuring that the firmware upgrade won't upset existing SNMP management a user will already have in place.
Refer https://opengear.zendesk.com/entries/32422199-New-status-and-trap-MIBS for more details.
Comments
0 comments
Article is closed for comments.