XEDIA-MIB

All MIBs › XEDIA-MIB

Organization: Xedia Corp.

Last Updated: 1996-12-20

Description: Xedia SNMP agent configuration MIB for managing community strings and trap destinations on Xedia devices, originally developed for the Xedia MADswitch product

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is XEDIA-MIB?

XEDIA-MIB is the base Xedia Corporation vendor MIB for configuring the SNMP agent itself on Xedia products, originally developed for the Xedia MADswitch and later converted from SNMPv1 to the SNMPv2 SMI while remaining semantically compatible. It exposes SNMP community string configuration (name, network address/mask, access level) via the community table, along with objects for configuring trap destinations and general agent statistics. Rather than exposing hardware performance data, this MIB's role is managing and monitoring the SNMP management plane itself; confirming which communities and trap destinations are configured, tracking agentStats for management traffic, and verifying the agent's access-control settings are correctly restricting or permitting management access. It underlies practically every other Xedia-specific MIB, since those modules' data is retrieved through the SNMPv1/v2c agent this MIB configures. It is deployed on all Xedia devices (originally MADswitch, and later products) wherever SNMP-based management is used. Engineers can download the XEDIA-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in XEDIA-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Xedia MADswitch
Xedia networking device

Monitoring Examples

An administrator would poll communityTable/communityEntry to audit configured communityName, communityNetAddress, communityNetMask, and communityAccess values, confirming that only expected management stations have read or read-write access. The agentStats objects would be checked to see SNMP request/response volume and error counts, which could reveal a management station hammering the device or an access-control mismatch causing repeated authentication failures. configPassword would be checked (with appropriate caution) to confirm device-level configuration access is still protected.

What Can Be Monitored

SNMP community configuration
community network address/mask/access level
trap destination configuration
agent SNMP statistics

Imported Objects

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString
RowStatus

From XEDIA-REG

xedia

OBJECT-IDENTITY

How to Use in IPNetwork Monitor

Example using agentStatsBadUserNameUses OID:

Select a Xedia MADswitch, Xedia networking device (SNMP community/trap-destination config status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type agentStatsBadUserNameUses into the Find box to locate it in the OID tree, then select it and click OK. The number of SNMPv3 requests from a user that could not be satisfied because of inadequeate access of the user. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
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.)
STR configPassword	1.3.6.1.4.1.838.1.1	DisplayString	read-write	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.
communityTable	1.3.6.1.4.1.838.1.2		not-accessible	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.
communityEntry	1.3.6.1.4.1.838.1.2.1		not-accessible	Information about a specific community.
I32 communityIndex	1.3.6.1.4.1.838.1.2.1.1	Integer32	read-only	Unique number identifing this entry.
STR communityName	1.3.6.1.4.1.838.1.2.1.2	DisplayString	read-create	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.
IP communityNetAddress	1.3.6.1.4.1.838.1.2.1.3	IpAddress	read-create	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.
INT communityAccess	1.3.6.1.4.1.838.1.2.1.4	INTEGER	read-create	Sets the access permissions of the community/user name.
IP communityNetMask	1.3.6.1.4.1.838.1.2.1.5	IpAddress	read-create	This mask associated with the community IP Address. This value can be used to provide individual host, or host network restrictions to the agent.
BIT communityAuthVersions	1.3.6.1.4.1.838.1.2.1.6	Bits	read-create	The acceptable SNMP versions for this community/user name.
BIT communityAuthModels	1.3.6.1.4.1.838.1.2.1.7	Bits	read-create	The acceptable SNMPv3 authentication models for this community/user name.
BIT communityAuthModes	1.3.6.1.4.1.838.1.2.1.8	Bits	read-create	The acceptable SNMPv3 security modes for this community/user.
BIT communityAuthViews	1.3.6.1.4.1.838.1.2.1.9	Bits	read-create	This security view mask associated with this community/user name. By default, the entries relative index position bit is set.
INT communityAuthApp	1.3.6.1.4.1.838.1.2.1.10	INTEGER	read-create	The type of authentication being used for SNMPv3.
INT communityPrivApp	1.3.6.1.4.1.838.1.2.1.11	INTEGER	read-create	The type of privacy algorithm being used for SNMPv3.
INT communityPrivKeyApp	1.3.6.1.4.1.838.1.2.1.12	INTEGER	read-create	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.
OCT communityAuthKey	1.3.6.1.4.1.838.1.2.1.13	OCTET STRING	read-create	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.
OCT communityPrivKey	1.3.6.1.4.1.838.1.2.1.14	OCTET STRING	read-create	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.
STR communityAuthKeyPW	1.3.6.1.4.1.838.1.2.1.15	DisplayString	read-create	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.
STR communityPrivKeyPW	1.3.6.1.4.1.838.1.2.1.16	DisplayString	read-create	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.
OCT communityAuthKeyUp	1.3.6.1.4.1.838.1.2.1.17	OCTET STRING	read-create	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.
OCT communityPrivKeyUp	1.3.6.1.4.1.838.1.2.1.18	OCTET STRING	read-create	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.
ROW communityRowStatus	1.3.6.1.4.1.838.1.2.1.19	RowStatus	read-create	The status of the row.
communityViewTable	1.3.6.1.4.1.838.1.3		not-accessible	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.
communityViewEntry	1.3.6.1.4.1.838.1.3.1		not-accessible	Information about a specific community view.
I32 communityViewIndex	1.3.6.1.4.1.838.1.3.1.1	Integer32	read-only	Unique number identifing this view.
STR communityViewName	1.3.6.1.4.1.838.1.3.1.2	DisplayString	read-create	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.
trapTable	1.3.6.1.4.1.838.1.4		not-accessible	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.
trapEntry	1.3.6.1.4.1.838.1.4.1		not-accessible	Information about a specific trap destination.
I32 trapIndex	1.3.6.1.4.1.838.1.4.1.1	Integer32	read-only	Unique number identifing this trap destination entry.
STR trapCommunity	1.3.6.1.4.1.838.1.4.1.2	DisplayString	read-create	This is the trap community/user name used to format the trap.
IP trapNetAddress	1.3.6.1.4.1.838.1.4.1.3	IpAddress	read-create	The network address of the client to whom the trap is to be sent.
INT trapSnmpVersion	1.3.6.1.4.1.838.1.4.1.4	INTEGER	read-create	The type of Trap-PDU to send to this manager since the PDU structure varies between the versions.
INT trapPort	1.3.6.1.4.1.838.1.4.1.5	INTEGER	read-create	The udp port number of the client to whom the trap is to be sent.
INT trapAuthApp	1.3.6.1.4.1.838.1.4.1.6	INTEGER	read-create	The type of authentication being used for SNMPv3 traps.
INT trapPrivApp	1.3.6.1.4.1.838.1.4.1.7	INTEGER	read-create	The type of privacy being used for SNMPv3 traps.
INT trapPrivKeyApp	1.3.6.1.4.1.838.1.4.1.8	INTEGER	read-create	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.
OCT trapAuthKey	1.3.6.1.4.1.838.1.4.1.9	OCTET STRING	read-create	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.
OCT trapPrivKey	1.3.6.1.4.1.838.1.4.1.10	OCTET STRING	read-create	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.
STR trapAuthKeyPW	1.3.6.1.4.1.838.1.4.1.11	DisplayString	read-create	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.
STR trapPrivKeyPW	1.3.6.1.4.1.838.1.4.1.12	DisplayString	read-create	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.
OCT trapAuthKeyUp	1.3.6.1.4.1.838.1.4.1.13	OCTET STRING	read-create	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.
OCT trapPrivKeyUp	1.3.6.1.4.1.838.1.4.1.14	OCTET STRING	read-create	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.
ROW trapRowStatus	1.3.6.1.4.1.838.1.4.1.15	RowStatus	read-create	The status of the row.
agentConfigConformance	1.3.6.1.4.1.838.1.5
agentConfigCompliances	1.3.6.1.4.1.838.1.5.1
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.
agentConfigGroups	1.3.6.1.4.1.838.1.5.2
agentConfigGeneralGroup	1.3.6.1.4.1.838.1.5.2.1			The set of all accessible objects in this MIB.
agentConfiguration	1.3.6.1.4.1.838.1.6
STR agentEngineID	1.3.6.1.4.1.838.1.6.1	DisplayString	read-write	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.
BIT agentOptions	1.3.6.1.4.1.838.1.6.2	Bits	read-write	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 .
INT agentInTimeWindowSize	1.3.6.1.4.1.838.1.6.3	INTEGER	read-write	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.
IP agentCfgTrapIpAddress	1.3.6.1.4.1.838.1.6.4	IpAddress	read-create	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.
IP agentOperTrapIpAddress	1.3.6.1.4.1.838.1.6.5	IpAddress	read-only	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.
BIT agentTrapOptions	1.3.6.1.4.1.838.1.6.6	Bits	read-write	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.
agentStats	1.3.6.1.4.1.838.1.7
C32 agentStatsBadUserNameUsesEx	1.3.6.1.4.1.838.1.7.1	Counter32	read-only	The number of SNMPv3 requests from a user that could not be satisfied because of inadequeate access of the user.
C32 agentStatsBadUserVersions	1.3.6.1.4.1.838.1.7.2	Counter32	read-only	The number of SNMPv3 requests from a user that could not be satisfied because of invalid user snmp-pdu-version configuration.
C32 agentStatsBadCommunityVersions	1.3.6.1.4.1.838.1.7.3	Counter32	read-only	The number of SNMPv1/v2 requests from a user that could not be satisfied because of invalid user snmp-pdu-version configuration.
C32 agentStatsBadUserAddress	1.3.6.1.4.1.838.1.7.4	Counter32	read-only	The number of SNMPv3 requests from a user that could not be satisfied because of invalid ip address/mask configuration.
C32 agentStatsBadCommunityAddress	1.3.6.1.4.1.838.1.7.5	Counter32	read-only	The number of SNMPv1/v2 requests from a user that could not be satisfied because of invalid ip address/mask configuration.

RFC description

SNMP agent configuration for community strings and trap destinations on Xedia routers.

Start monitoring Xedia MADswitch, Xedia networking device (SNMP community/trap-destination config status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download XEDIA-MIB