XEDIA-MIB: View SNMP OID List / Download MIB

This MIB module is used to configure the community strings and trap destinations for SNMPv1 and SNMPv2c agents for Xedia products. It was originally written for the Xedia MADswitch product (based on a MIB developed by Avatar Consulting). This version of the MIB has been converted to SNMPv2 SMI but is still semantically equivalent to the original version (meaning the implementation of the MIB in the MADswitch is still compliant with this version of the MIB). Besides this conversion to the new SMI (MIB syntax) and many editorial changes, this MIB has one new object: trapSnmpVersion. See the DESCRIPTION clause for more information. (Note that adding new objects is a legal change to make to new revisions of a MIB.)

This variable is a password that allows access to the agentConfig group. The password is really a community name that must be used in order to view/modify objects on the agentConfig group. For obvious reasons, noSuchName error is returned on a GET/GET-NEXT request (for any object under agentConfig), unless the community name used is the password.

This is the community table. Each entry is composed of a community name, access based on network address, community access and a table of community views. This table can only be accessed if the community name matches configPassword. To add any entry the community name communityName must be created first. These defaults are assigned to the new entry all hosts, read-only access and no restriction on view (outside of agentConfig of course). To delete an entry, set communityName to NULL. Note that multiple rows can exist with the same Name/NetAddress values. The access granted will be the highest level of access. If two entries exist with the same Name but one with a wildcarded NetAddress and the other with a specific NetAddress, the specific address entry overrides the wildcarded entry. This way, for example, read-only access can be granted to everyone using the public community string, but notaccessible access (no access) can be given if they come from IP address 1.2.3.4.

Information about a specific community.

Unique number identifing this entry.

This is the community name for SNMPv1/v2 requests, or the user name for SNMPv3 requests. For SNMPv1/v2 access using the cli, the username/password combination specifies the community string. When interpreted for SNMPv3, only the username portion of the string is used. Received snmp pdus determine a match with a table entry if the username/community name matches, AND the IP Address match is sufficient. See the ip address below, and the network mask. Although it is not prohibited, named entries in the table should not overlap. During authentication, the first active communityName match will be used. Name overlap is only allowed since it may be desirable in some environments to have some name overlap while taking advantage of the notInService row status.

This restricts access to the agent using the above community/user name to only the network host address or the host network that is given here, with the applied mask value. A value of 0 will allow access to all host networks.

Sets the access permissions of the community/user name.

This mask associated with the community IP Address. This value can be used to provide individual host, or host network restrictions to the agent.

The acceptable SNMP versions for this community/user name.

The acceptable SNMPv3 authentication models for this community/user name.

The acceptable SNMPv3 security modes for this community/user.

This security view mask associated with this community/user name. By default, the entries relative index position bit is set.

The type of authentication being used for SNMPv3.

The type of privacy algorithm being used for SNMPv3.

The type of hash algorithm used for key manipulation for the password to key or key update actions. The AuthApp uses the existing authentication algorithm selected. But, the Md5/Sha selections can be used to specify the exact method needed.

The authentication key used for SNMPv3. Use 16 bytes for MD5 keys and 20 bytes for SHA keys. Typically, when this object is read, a zero length value is returned, and setting the key to a zero length string has no affect on the key value. The contents of the key can be viewed if the top level agent option displaySecretKeysis set.

The privacy key used for SNMPv3. Use 16 bytes for DES keys. Typically, when this object is read, a zero length value is returned, and setting the key to a zero length string has no affect on the key value. The contents of the key can be viewed if the top level agent option displaySecretKeysis set.

The password used to create the authentication key. When read, a null string will be returned. The key will be generated based on the value of the authentication application that is specified at the time of the request. The resulting key will be of the proper length to match the authentication application. Using a zero length password will result in no change being made to the key.

The password used to create the privacy key. When read, a null string will be returned. The key will be generated based on the value of the privacy application that is specified at the time of the request. The resulting key will be of the proper length to match the privacy application. Using a zero length password will result in no change being made to the key.

The random+delta offset used to re-calculate the privacy key. Both the random and delta components must be of key length (16-md5, or 20-sha). Therefor, the length of the whole value must be 32 or 40 bytes. Using a zero length offset will result in no change being made to the key.

The random + delta offset used to re-calculate the privacy key. Both the random and delta components must be of key length 16. Therefor, the length of the whole value must be 32 bytes. Using a zero length offset will result in no change being made to the key.

The status of the row.

This is the community view table. Each entry is the allowable group that this community can view. To add a view, the community entry must exist. To delete it set the view name to NULL.

Information about a specific community view.

Unique number identifing this view.

The view name for this community. This value must be a MIB variable that the agent will recognize (eg. iso, ip, interfaces). To delete this view, set value to NULL.

This is the trap table. Each entry is composed of a trap name and the network address of where the trap is to be sent. This table can only be accessed if the community name matches configPassword. To add an entry the trap name trapName must be created first. To delete an entry set trapName to NULL.

Information about a specific trap destination.

Unique number identifing this trap destination entry.

This is the trap community/user name used to format the trap.

The network address of the client to whom the trap is to be sent.

The type of Trap-PDU to send to this manager since the PDU structure varies between the versions.

The udp port number of the client to whom the trap is to be sent.

The type of authentication being used for SNMPv3 traps.

The type of privacy being used for SNMPv3 traps.

The type of hash algorithm used for key manipulation for the password to key or key update actions. The AuthApp uses the existing authentication algorithm selected. But, the Md5/Sha selections can be used to specify the exact method needed.

The authentication key used for SNMPv3. Use 16 bytes for MD5 keys and 20 bytes for SHA keys. Typically, when this object is read, a zero length value is returned, and setting the key to a zero length string has no affect on the key value. The contents of the key can be viewed if the top level agent option displaySecretKeysis set.

The privacy key used for SNMPv3. Use 16 bytes for DES keys. Typically, when this object is read, a zero length value is returned, and setting the key to a zero length string has no affect on the key value. The contents of the key can be viewed if the top level agent option displaySecretKeysis set.

The password used to create the authentication key. When read, a null string will be returned. The key will be generated based on the value of the authentication application that is specified at the time of the request. The resulting key will be of the proper length to match the authentication application. Using a zero length password will result in no change being made to the key.

The password used to create the privacy key. When read, a null string will be returned. The key will be generated based on the value of the privacy application that is specified at the time of the request. The resulting key will be of the proper length to match the privacy application. Using a zero length password will result in no change being made to the key.

The random+delta offset used to re-calculate the authentication key. Both the random and delta components must be of key length (16-md5, or 20-sha). Therefor, the length of the whole value must be 32 or 40 bytes. Using a zero length offset will result in no change being made to the key.

The random + delta offset used to re-calculate the privacy key. Both the random and delta components must be of key length 16. Therefor, the length of the whole value must be 32 bytes. Using a zero length offset will result in no change being made to the key.

The status of the row.

The compliance statement for all agents that support this MIB. A compliant agent implements all objects defined in this MIB.

The set of all accessible objects in this MIB.

an ASCII string beginning with a - results in a straight, display string implementation of only readable/printable bytes. This does NOT abide by the recommendation in rfc2271. Typically, this is only needed with primative manager stations that have trouble with non-ascii data.

This object controls how the agent will behave, according to which flags are enable: v3ReportsOn - allows the transmission of normal SNMPv3 reports when set. If this bit is NOT set, no reports will be generated. xediaSpecificErrors- allows the use of Xedia Specific error counters for SNMPv1/v2/v3 when applicable. This also results in the transmission of more specific v3 error reports as defined by Xedia. If this bit is not set, a mapping will be made to less specific SNMPv1/v2/v3 statistics and SNMPv3 reports. Typically, these errors include community/user access level, pdu level counters, that will be remapped to SNMP version specific bad community/name error indicators. suppressTrapsForUserInitial - allows the suppression of authentication failure traps and events for the user name initial. This name may be used as part of the EngineID discovery process as described in rfc274. suppressTrapsForTimeliness - allows the suppression of authentication failure traps and events Time Synchronization. displaySecretKeys - allows the retrieval of the Authentication and Privacy Keys to the super user. Normally, viewing the keys results in a NULL string .

The configured value for determining SNMPv3 packet timeliness. The standard 150 second window can be tuned below the standard value so that any replay attack will have even less impact on the nodes within the network. But, setting it too low could cause out of window errors, and additional clock sync.

The configured IP address that will be used as the Agents IP address for all outbound traps. If this object is left at 0.0.0.0, then any one of the active IP address will be used. If there is a routerID specified, that will be used first. note: once the operational ID has been learned, it remains in use until a node reset.

The operational IP address that will be used as the Agents IP address for all outbound traps. note: once the operation ID has been learned, it remains in use until a node reset.

This object controls how the agent will behave, according to which flags are enable: extendedLinkTrapInfo - provides additional link information in the standard LinkUp/Down traps. This info includes the interface descritpions, as well as the interface name.

The number of SNMPv3 requests from a user that could not be satisfied because of inadequeate access of the user.

The number of SNMPv3 requests from a user that could not be satisfied because of invalid user snmp-pdu-version configuration.

The number of SNMPv1/v2 requests from a user that could not be satisfied because of invalid user snmp-pdu-version configuration.

The number of SNMPv3 requests from a user that could not be satisfied because of invalid ip address/mask configuration.

The number of SNMPv1/v2 requests from a user that could not be satisfied because of invalid ip address/mask configuration.