XEDIA-FRAME-RELAY-MIB: View SNMP OID List / Download MIB

VENDOR: XEDIA CORPORATION


 Home MIB: XEDIA-FRAME-RELAY-MIB
Download as:   

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 xediaFrameRelayMIB 1.3.6.1.4.1.838.3.19
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.
       xfrObjects 1.3.6.1.4.1.838.3.19.1
           xfrArpTable 1.3.6.1.4.1.838.3.19.1.1 no-access
The 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.
               xfrArpEntry 1.3.6.1.4.1.838.3.19.1.1.1 no-access
Each entry contains one IpAddress to `physical' address equivalence.
                   xfrArpIfIndex 1.3.6.1.4.1.838.3.19.1.1.1.1 integer read-only
The 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.
                   xfrArpNetAddress 1.3.6.1.4.1.838.3.19.1.1.1.2 ipaddress read-only
The IpAddress corresponding to the frame relay DLCI.
                   xfrArpType 1.3.6.1.4.1.838.3.19.1.1.1.3 integer read-only
The 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. Enumeration: 'static': 4, 'other': 1, 'dynamic': 3, 'invalid': 2.
                   xfrArpDlci 1.3.6.1.4.1.838.3.19.1.1.1.4 integer read-only
The DLCI attached to the IP address.
                   xfrArpIfStack 1.3.6.1.4.1.838.3.19.1.1.1.5 displaystring read-only
A description of the interface stack containing this frame relay interface, with the IP interface, the frame relay interface, and the device interface.
           xFrCircuitTable 1.3.6.1.4.1.838.3.19.1.2 no-access
A table containing additional information about specific Data Link Connection Identifiers and corresponding virtual circuits.
               xFrCircuitEntry 1.3.6.1.4.1.838.3.19.1.2.1 no-access
The additional information regarding a single Data Link Connection Identifier.
                   xfrCircuitType 1.3.6.1.4.1.838.3.19.1.2.1.1 integer read-only
The type of DLCI Enumeration: 'static': 2, 'dynamic': 1.
       xfrNotifications 1.3.6.1.4.1.838.3.19.2
       xfrConformance 1.3.6.1.4.1.838.3.19.3
           xfrCompliances 1.3.6.1.4.1.838.3.19.3.1
               xfrCompliance 1.3.6.1.4.1.838.3.19.3.1.1
The compliance statement for all agents that support this MIB. A compliant agent implements all objects defined in this MIB.
           xfrGroups 1.3.6.1.4.1.838.3.19.3.2
               xfrAllGroup 1.3.6.1.4.1.838.3.19.3.2.1
The set of all accessible objects in this MIB.