XEDIA-FRAME-RELAY-MIB
AI MIB Summary
The XEDIA-FRAME-RELAY-MIB extends standard IETF Frame Relay management capabilities to monitor and configure vendor-specific Frame Relay interface states, DLCI statistics, and protocol parameters on Xedia network devices. This module enables granular visibility into Frame Relay virtual circuit performance and error counters beyond the baseline definitions provided in generic MIBs.
This module defines additional objects for management of Frame Relay in Xedia devices, above and beyond what is defined in the IETF's Frame Relay MIBs.
Main OID:
xediaFrameRelayMIB.1.3.6.1.4.1.838.3.19
16
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
16 total| Object Name |
|---|
xediaFrameRelayMIBThis module defines additional objects for management of Frame Relay
in Xedia devices, above and beyond what is defined in the
IETF's Frame Relay MIBs. MODULE-IDENTITY .1.3.6.1.4.1.838.3.19 |
xfrObjects OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.19.1 |
xfrArpTableThe IP Address Translation table used for mapping from IP
addresses to physical addresses, in this case frame relay DLCIs.
This table contains much of the same information that is in the
ipNetToMediaTable. SEQUENCE OF XfrArpEntry .1.3.6.1.4.1.838.3.19.1.1 |
xfrArpEntryEach entry contains one IpAddress to `physical' address
equivalence. XfrArpEntry .1.3.6.1.4.1.838.3.19.1.1.1 |
xfrArpIfIndexThe interface on which this entry's equivalence is
effective. The interface identified by a particular value
of this index is the same interface as identified by the
same value of RFC 1573's ifIndex.rw INTEGER .1.3.6.1.4.1.838.3.19.1.1.1.1 |
xfrArpNetAddressThe IpAddress corresponding to the frame relay DLCI.rw IpAddress .1.3.6.1.4.1.838.3.19.1.1.1.2 |
xfrArpTypeThe type of mapping.
Setting this object to the value invalid(2) has the effect
of invalidating the corresponding entry in the
xfrArpEntryTable. That is, it effectively disassociates
the interface identified with said entry from the mapping
identified with said entry. It is an implementation-
specific matter as to whether the agent removes an
invalidated entry from the table. Accordingly, management
stations must be prepared to receive tabular information
from agents that corresponds to entries not currently in
use. Proper interpretation of such entries requires
examination of the relevant xfrArpEntryType object.rw Enumeration .1.3.6.1.4.1.838.3.19.1.1.1.3 |
xfrArpDlciThe DLCI attached to the IP address.rw INTEGER .1.3.6.1.4.1.838.3.19.1.1.1.4 |
xfrArpIfStackA description of the interface stack containing this frame
relay interface, with the IP interface, the frame relay interface,
and the device interface.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.838.3.19.1.1.1.5 |
xFrCircuitTableA table containing additional information about specific Data
Link Connection Identifiers and corresponding virtual circuits. SEQUENCE OF XFrCircuitEntry .1.3.6.1.4.1.838.3.19.1.2 |
xFrCircuitEntryThe additional information regarding a single Data Link
Connection Identifier. XFrCircuitEntry .1.3.6.1.4.1.838.3.19.1.2.1 |
xfrCircuitTypeThe type of DLCIro Enumeration .1.3.6.1.4.1.838.3.19.1.2.1.1 |
xfrNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.19.2 |
xfrConformance OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.19.3 |
xfrCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.19.3.1 |
xfrGroups OBJECT IDENTIFIER .1.3.6.1.4.1.838.3.19.3.2 |