From Silver Peak’s website, you can download the Standard and the Silver Peak proprietary MIBs (Management Information Base) files, for loading into whatever MIBs browser you’re using:
|
•
|
The Standard list and the Silver Peak file list share the same first three files. These are highlighted in green below.
|
|
•
|
If you choose to load both the Standard and the Silver Peak MIBs, load either list completely and then append the non-common files from the remaining list.
|
Use this page to configure the appliance's SNMP agent, the trap receiver(s), and how to forward appliance alarms as SNMP traps to the receivers.
 |
|
n
|
The Silver Peak appliance supports the Management Information Base (MIB) II, as described in RFC 1213, for cold start traps and warm start traps, as well as Silver Peak proprietary MIBs.
|
|
n
|
|
n
|
The appliance sends a trap every time an alarm is raised or cleared. Traps contain additional information about the alarm, including severity, sequence number, a text-based description of the alarm, and the time the alarm was created. For additional information, see SILVERPEAK-MGMT-MIB.TXT in the MIBS directory.
|
|
The SNMP application needs to present this text string (secret) in order to poll this appliance's SNMP agent. The default value is public, but you can change it.
|
|
|
The trap receiver needs to receive this string in order to accept the traps being sent to it. The default value is public, but you can change it.
|
For additional security when the SNMP application polls the appliance, you can select Enable Admin User for SNMP v3, instead of using v1 or v2c. This provides a way to authenticate without using clear text:
|
n
|
|
n
|
For SNMP v3, authentication between the user and the server acting as the SNMP agent is bilateral and required. You can use either the MD5 or SHA-1 hash algorithm.
|
|
n
|
Using DES or AES-128 to encrypt for privacy is optional. If you don't specify a password, the appliance uses the default privacy algorithm (AES-128) and the same password you specified for authentication.
|
You can configure up to 3 trap receivers:
|
The trap receiver needs to receive a specific string in order to accept the traps being sent to it. By default, this field is blank because it uses the Default Trap Community string, which has the value, public. If the trap receiver you're adding has a different Community string, enter the community string that's configured on the trap receiver.
|
|
|
Select either v1 (RFC 1157) or v2c (RFC 1901) standards. For both, authentication is based on a community string that represents an unencrypted password.
|
|
