XEDIA-MIB

File: XEDIA-MIB.mib (33247 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC SNMPv2-CONF
XEDIA-REG

Imported symbols

MODULE-IDENTITY OBJECT-TYPE IpAddress
Integer32 Counter32 RowStatus
DisplayString MODULE-COMPLIANCE OBJECT-GROUP
xedia

Defined Types

CommunityEntry  
SEQUENCE    
  communityIndex Integer32
  communityName DisplayString
  communityNetAddress IpAddress
  communityAccess INTEGER
  communityNetMask IpAddress
  communityAuthVersions BIT STRING
  communityAuthModels BIT STRING
  communityAuthModes BIT STRING
  communityAuthViews BIT STRING
  communityAuthApp INTEGER
  communityPrivApp INTEGER
  communityPrivKeyApp INTEGER
  communityAuthKey OCTET STRING
  communityPrivKey OCTET STRING
  communityAuthKeyPW DisplayString
  communityPrivKeyPW DisplayString
  communityAuthKeyUp OCTET STRING
  communityPrivKeyUp OCTET STRING
  communityRowStatus RowStatus

CommunityViewEntry  
SEQUENCE    
  communityViewIndex Integer32
  communityViewName DisplayString

TrapEntry  
SEQUENCE    
  trapIndex Integer32
  trapCommunity DisplayString
  trapNetAddress IpAddress
  trapSnmpVersion INTEGER
  trapPort INTEGER
  trapAuthApp INTEGER
  trapPrivApp INTEGER
  trapPrivKeyApp INTEGER
  trapAuthKey OCTET STRING
  trapPrivKey OCTET STRING
  trapAuthKeyPW DisplayString
  trapPrivKeyPW DisplayString
  trapAuthKeyUp OCTET STRING
  trapPrivKeyUp OCTET STRING
  trapRowStatus RowStatus

Defined Values

agentConfig 1.3.6.1.4.1.838.1
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.)
MODULE-IDENTITY    

configPassword 1.3.6.1.4.1.838.1.1
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.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString  

communityTable 1.3.6.1.4.1.838.1.2
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    CommunityEntry

communityEntry 1.3.6.1.4.1.838.1.2.1
Information about a specific community.
Status: current Access: not-accessible
OBJECT-TYPE    
  CommunityEntry  

communityIndex 1.3.6.1.4.1.838.1.2.1.1
Unique number identifing this entry.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

communityName 1.3.6.1.4.1.838.1.2.1.2
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.
Status: current Access: read-create
OBJECT-TYPE    
  DisplayString  

communityNetAddress 1.3.6.1.4.1.838.1.2.1.3
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.
Status: current Access: read-create
OBJECT-TYPE    
  IpAddress  

communityAccess 1.3.6.1.4.1.838.1.2.1.4
Sets the access permissions of the community/user name.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER readonly(1), writeonly(2), readwrite(3), notaccessible(4)  

communityNetMask 1.3.6.1.4.1.838.1.2.1.5
This mask associated with the community IP Address. This value can be used to provide individual host, or host network restrictions to the agent.
Status: current Access: read-create
OBJECT-TYPE    
  IpAddress  

communityAuthVersions 1.3.6.1.4.1.838.1.2.1.6
The acceptable SNMP versions for this community/user name.
Status: current Access: read-create
OBJECT-TYPE    
  BIT STRING snmpv1(0), snmpv2(1), snmpv3(2)  

communityAuthModels 1.3.6.1.4.1.838.1.2.1.7
The acceptable SNMPv3 authentication models for this community/user name.
Status: current Access: read-create
OBJECT-TYPE    
  BIT STRING snmpv1(0), snmpv2(1), snmpv3(2)  

communityAuthModes 1.3.6.1.4.1.838.1.2.1.8
The acceptable SNMPv3 security modes for this community/user.
Status: current Access: read-create
OBJECT-TYPE    
  BIT STRING noAuthNoPriv(0), authNoPriv(1), authPriv(2)  

communityAuthViews 1.3.6.1.4.1.838.1.2.1.9
This security view mask associated with this community/user name. By default, the entries relative index position bit is set.
Status: current Access: read-create
OBJECT-TYPE    
  BIT STRING s10(0), s9(1), s8(2), s7(3), s6(4), s5(5), s4(6), s3(7), s2(8), s1(9)  

communityAuthApp 1.3.6.1.4.1.838.1.2.1.10
The type of authentication being used for SNMPv3.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER authNone(1), authMd5(2), authSha(3)  

communityPrivApp 1.3.6.1.4.1.838.1.2.1.11
The type of privacy algorithm being used for SNMPv3.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER privNone(1), privDes(2)  

communityPrivKeyApp 1.3.6.1.4.1.838.1.2.1.12
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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER privKeyAuthApp(1), privKeyMd5(2), privKeySha(3)  

communityAuthKey 1.3.6.1.4.1.838.1.2.1.13
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 'displaySecretKeys'is set.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(0|16|20)  

communityPrivKey 1.3.6.1.4.1.838.1.2.1.14
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 'displaySecretKeys'is set.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(0|16)  

communityAuthKeyPW 1.3.6.1.4.1.838.1.2.1.15
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.
Status: current Access: read-create
OBJECT-TYPE    
  DisplayString Size(0..32)  

communityPrivKeyPW 1.3.6.1.4.1.838.1.2.1.16
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.
Status: current Access: read-create
OBJECT-TYPE    
  DisplayString Size(0..32)  

communityAuthKeyUp 1.3.6.1.4.1.838.1.2.1.17
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.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(0|32|40)  

communityPrivKeyUp 1.3.6.1.4.1.838.1.2.1.18
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.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(0|32)  

communityRowStatus 1.3.6.1.4.1.838.1.2.1.19
The status of the row.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

communityViewTable 1.3.6.1.4.1.838.1.3
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    CommunityViewEntry

communityViewEntry 1.3.6.1.4.1.838.1.3.1
Information about a specific community view.
Status: current Access: not-accessible
OBJECT-TYPE    
  CommunityViewEntry  

communityViewIndex 1.3.6.1.4.1.838.1.3.1.1
Unique number identifing this view.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

communityViewName 1.3.6.1.4.1.838.1.3.1.2
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.
Status: current Access: read-create
OBJECT-TYPE    
  DisplayString  

trapTable 1.3.6.1.4.1.838.1.4
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    TrapEntry

trapEntry 1.3.6.1.4.1.838.1.4.1
Information about a specific trap destination.
Status: current Access: not-accessible
OBJECT-TYPE    
  TrapEntry  

trapIndex 1.3.6.1.4.1.838.1.4.1.1
Unique number identifing this trap destination entry.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

trapCommunity 1.3.6.1.4.1.838.1.4.1.2
This is the trap community/user name used to format the trap.
Status: current Access: read-create
OBJECT-TYPE    
  DisplayString  

trapNetAddress 1.3.6.1.4.1.838.1.4.1.3
The network address of the client to whom the trap is to be sent.
Status: current Access: read-create
OBJECT-TYPE    
  IpAddress  

trapSnmpVersion 1.3.6.1.4.1.838.1.4.1.4
The type of Trap-PDU to send to this manager since the PDU structure varies between the versions.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER snmpv1(1), snmpv2c(2), snmpv3(3)  

trapPort 1.3.6.1.4.1.838.1.4.1.5
The udp port number of the client to whom the trap is to be sent.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER 1..65535  

trapAuthApp 1.3.6.1.4.1.838.1.4.1.6
The type of authentication being used for SNMPv3 traps.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER authNone(1), authMd5(2), authSha(3)  

trapPrivApp 1.3.6.1.4.1.838.1.4.1.7
The type of privacy being used for SNMPv3 traps.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER privNone(1), privDes(2)  

trapPrivKeyApp 1.3.6.1.4.1.838.1.4.1.8
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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER privKeyAuthApp(1), privKeyMd5(2), privKeySha(3)  

trapAuthKey 1.3.6.1.4.1.838.1.4.1.9
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 'displaySecretKeys'is set.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(0|16|20)  

trapPrivKey 1.3.6.1.4.1.838.1.4.1.10
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 'displaySecretKeys'is set.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(0|16)  

trapAuthKeyPW 1.3.6.1.4.1.838.1.4.1.11
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.
Status: current Access: read-create
OBJECT-TYPE    
  DisplayString Size(0..32)  

trapPrivKeyPW 1.3.6.1.4.1.838.1.4.1.12
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.
Status: current Access: read-create
OBJECT-TYPE    
  DisplayString Size(0..32)  

trapAuthKeyUp 1.3.6.1.4.1.838.1.4.1.13
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.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(0|32|40)  

trapPrivKeyUp 1.3.6.1.4.1.838.1.4.1.14
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.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(0|32)  

trapRowStatus 1.3.6.1.4.1.838.1.4.1.15
The status of the row.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

agentConfiguration 1.3.6.1.4.1.838.1.6
OBJECT IDENTIFIER    

agentStats 1.3.6.1.4.1.838.1.7
OBJECT IDENTIFIER    

agentEngineID 1.3.6.1.4.1.838.1.6.1
The configured SNMP EngineID used for SNMPv3 packets. This object can be used to override automatic engine id assignment. If this object is set, care must be taken to ensure its uniqueness within the SNMP Domain. Additionally, setting this object may result in the initialization of snmpEngineBoots. Normally, this has the desired affect, but if the engine ID is reset to an old value, previously captured PDUs may again apear to be valid, since the number of restarts has been reset. Setting this value results in the following: > a null EngineID results in the normal 'MAC address' of the SNMP EngineID encoding as per rfc2271. > an ASCII string results in the normal 'Text' administratively assigned value. > 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.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString Size(0..32)  

agentOptions 1.3.6.1.4.1.838.1.6.2
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 .
Status: current Access: read-write
OBJECT-TYPE    
  BIT STRING v3ReportsOn(0), xediaSpecificErrors(1), suppressTrapsForUserInitial(2), suppressTrapsForTimeliness(3), displaySecretKeys(4)  

agentInTimeWindowSize 1.3.6.1.4.1.838.1.6.3
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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER 1..150  

agentCfgTrapIpAddress 1.3.6.1.4.1.838.1.6.4
The configured IP address that will be used as the Agent's 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.
Status: current Access: read-create
OBJECT-TYPE    
  IpAddress  

agentOperTrapIpAddress 1.3.6.1.4.1.838.1.6.5
The operational IP address that will be used as the Agent's IP address for all outbound traps. note: once the operation ID has been learned, it remains in use until a node reset.
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

agentTrapOptions 1.3.6.1.4.1.838.1.6.6
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.
Status: current Access: read-write
OBJECT-TYPE    
  BIT STRING extendedLinkTrapInfo(0)  

agentStatsBadUserNameUses 1.3.6.1.4.1.838.1.7.1
The number of SNMPv3 requests from a user that could not be satisfied because of inadequeate access of the user.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

agentStatsBadUserVersions 1.3.6.1.4.1.838.1.7.2
The number of SNMPv3 requests from a user that could not be satisfied because of invalid user snmp-pdu-version configuration.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

agentStatsBadCommunityVersions 1.3.6.1.4.1.838.1.7.3
The number of SNMPv1/v2 requests from a user that could not be satisfied because of invalid user snmp-pdu-version configuration.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

agentStatsBadUserAddress 1.3.6.1.4.1.838.1.7.4
The number of SNMPv3 requests from a user that could not be satisfied because of invalid ip address/mask configuration.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

agentStatsBadCommunityAddress 1.3.6.1.4.1.838.1.7.5
The number of SNMPv1/v2 requests from a user that could not be satisfied because of invalid ip address/mask configuration.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

agentConfigConformance 1.3.6.1.4.1.838.1.5
OBJECT IDENTIFIER    

agentConfigCompliances 1.3.6.1.4.1.838.1.5.1
OBJECT IDENTIFIER    

agentConfigGroups 1.3.6.1.4.1.838.1.5.2
OBJECT IDENTIFIER    

agentConfigCompliance 1.3.6.1.4.1.838.1.5.1.1
The compliance statement for all agents that support this MIB. A compliant agent implements all objects defined in this MIB.
Status: current Access: read-only
MODULE-COMPLIANCE    

agentConfigGeneralGroup 1.3.6.1.4.1.838.1.5.2.1
The set of all accessible objects in this MIB.
Status: current Access: read-only
OBJECT-GROUP