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

Cisco Frame Relay MIB

Table of Frame Relay LMI information that are either supplemental to the frDlcmiTable of RFC 1315 or specific to Cisco's implementation.

Each entry of the table contains information of Frame Relay LMI over one physical interface. They are mostly FR generic and some Cisco specific.

Data link status via LMI. Enumeration: 'down': 2, 'up': 1.

Frame Relay link type. Enumeration: 'dce': 2, 'nni': 3, 'dte': 1.

Number of Status Enquiry messages received.

Number of Status Enquiry messages sent.

Number of Status messages received.

Number of Status messages sent.

Number of Update Status messages received.

Number of Update Status messages sent

Number of times when timeout occurred on waiting for Status message

Number of times when timeout occurred on waiting for Status Enquiry message

LMI error threshold for DCE interface. For DTE, value becomes 0.

LMI monitored event count for DCE interface. For DTE, value becomes zero (0).

DCE polling verification timer for DCE interface For DTE, the value becomes zero (0).

Table of descriptive and statistics information that are generic to Frame Relay virtual circuits.

Each entry of the table contains information of a circuit that are not included in frCircuitTable of RFC1315 but are generic to Frame Relay.

Number of packets received with the Discarded Eligibility indictor (the DE bit) set.

Number of packets transmitted with DE bit set.

Number of discarded packets that were to be sent.

Basic circuit type Enumeration: 'pvc': 1, 'svc': 2.

Table of Cisco implementation specific FR circuit information. This is a Cisco extension for the frCircuitTable of RFC 1315.

Each entry of the table contains information of a Frame Relay virtual circuit that are specific to Cisco implementation.

The textual name of the main interface or the subinterface that this DLCI is associated with. This is the same name string of an interface used in the configuration and all console displays, such as 'serial 0', 'serial 3/0.3', etc.

Type of the subinterface this DLCI is associated with, if configured. Enumeration: 'multipoint': 3, 'mainInterface': 1, 'pointToPoint': 2.

For value greater than zero (0), it indicates the network management interface index for the subinterface associated with this DLCI. Value 0 means the DLCI is not associated with any subinterface.

The mapping protocols (internally considered as the 'link type') applied on this circuit. The value ranges from 0 to 2047. For point-to-point DLCI, the value stays zero. Otherwise, the value is a sum. It initially takes the value zero, then, for each type of Protocol, 2 raised to a power is added to the sum. The following table presents respective power and equivalent value for each applicable type: Protocol Power Value -------- ----- ----- IP 0 1 IPX 1 2 Appletalk 2 4 XNS 3 8 VINES 4 16 DECnet 5 32 CLNS 6 64 Bridging 7 128 RSRB 8 256 STUN 9 512 LLC2 10 1024 For example, value 3 means the circuit's mapping protocols include IP and IPX. (3 = 2**1 + 2**0, where 0 corresponds to IP and 1 to IPX.) Value 0 means there is currently no mapping protocol for the circuit. See cfrMapTable for more mapping information.

Identify the last source of the circuit's creation. Enumeration: 'static': 2, 'dynamic': 1.

Indicate if this DLCI is a multicast DLCI.

The routed DLCI to pair up with this DLCI for switching function. NOTE: Value zero (0) indicates that there is no such routed DLCI corresponding to this DLCI.

The interface for the routed DLCI that pairs up with this DLCI for switching. Value greater than 0 is the InterfaceIndex for that interface. Value zero (0) indicates that there is no such routed DLCI corresponding to this DLCI.

Number of inbound octets of the data packets, accounted at Frame Relay level after FRF.9 payload decompression is applied. In the case of non-FRF.9, this value could be identical to frCircuitReceivedOctets, unless otherwise noted.

Number of outbound octets of the data packets, accounted at Frame Relay level before FRF.9 payload compression is applied. In the case of non-FRF.9, this value could be identical to frCircuitSentOctets, unless otherwise noted.

Total number of frames sent out to the network indicating forward congestion.

Total number of frames sent out to the network indicating backward congestion.

Circuit's outgoing minimal Throughput based on configuration.

Circuit's incoming minimal Throughput based on configuration.

Total number of broadcast packets sent out to the network.

Total number of bytes sent out to the network in broadcast packets.

Bandwidth of the virtual circuit, acquired from Cisco typed LMI Full Status message.

Maximum number of tokens a token bucket can hold in any time interval in case of traffic shaping.

Committed rate measurement interval.

Number of tokens added into the token bucket per time interval in case of traffic shaping.

Total number of packets that went through traffic shaping.

Total number of bytes that went through traffic shaping.

Total number of packets that were delayed by the traffic shaper.

Total number of bytes that were delayed by the traffic shaper.

Shows whether shaping is active or not.

Type of Adaptive Shaping configured. none(1) - No adaptive shaping configured becn(2) - Backward Explicit Congestion Notification foreSight(3) - ForeSight is the network traffic control software used in Cisco WAN switches Enumeration: 'foreSight': 3, 'none': 1, 'becn': 2.

The average rate (bytes/second) at which data is transmitted in this circuit.

The average number of packets sent in a second in this circuit.

The average rate (bytes/second) at which data is received in this circuit.

The average number of packets received in a second in this circuit.

Table of protocols and addresses mapping information of FR virtual circuit.

Each entry of the table contains one mapping information of a Frame Relay virtual circuit.

An arbitrary Index to the mapping information associated with a certain circuit. The maximum value is arbitrarily picked which is considered sufficient for usual configuration.

Mapping protocol for this circuit.

Mapping protocol address at remote end for this DLCI. NOTE: For point-to-point DLCI, the string is fixed to be point-to-point.

Type for the map creation. Enumeration: 'dynamic': 2, 'static': 1, 'svc': 3.

Indication of the encapsulation type for this mapping protocol. Enumeration: 'ietf': 1, 'cisco': 2.

Broadcast enabled or disabled.

Indicate if payload compression is enabled.

TCP header compression type, if applicable. Enumeration: 'passive': 2, 'active': 3, 'inapplicable': 1.

RTP header compression type, if applicable. The value 'passive' means that the header of an outgoing RTP/IP packet is compressed only if an incoming RTP/IP packet had a compressed header. The value 'active' means the header of every outgoing RTP/IP packet is compressed. Enumeration: 'passive': 2, 'active': 3, 'inapplicable': 1.

FR payload compression type, if applicable. FRF.9 is the Frame Relay Forum Implementation Agreement on FR payload compression. The compression can be done by either software or hardware (when equipped with the supporting hardware), depending on configuration. Enumeration: 'frf9Software': 3, 'inapplicable': 1, 'frf9Hardware': 4, 'cisco': 2.

Table of FR SVC specific, descriptive and statistics information.

Each entry of the table contains circuit information specific to a Frame Relay Switched Virtual Circuit.

Local E.164/X.125 address for the circuit.

Remote E.164/X.125 address for the circuit.

Circuit's incoming throughput. For outgoing throughput (commonly referred to as CIR) see frCircuitThroughput per RFC1315.

Circuit's outgoing minimal Throughput.

Circuit's incoming minimal Throughput.

Circuit's incoming Committed Burst Rate. See ANSI and/or ITU specifications for definition and calculations. For outgoing CBR, see frCircuitCommittedBurst per RFC 1315.

Circuit's incoming Excess Burst Rate. See ANSI and/or ITU specifications for definition and calculations. For outgoing EBR, see frCircuitExcessBurst per RFC 1315.

Circuit's idle time period. If expires, the circuit is cleared.

This object represents the Management address of the device used for address registration. Network management station can send management messages to this IP address. This can be user configured address or the address of one of the interfaces on the device. If address registration is disabled then this will have a value of 0.0.0.0. This object is accessible only if the ELMI protocol is supported on the device

Table of CISCO Frame Relay ELMI information that is specific to CISCO implementation

Each entry of the table contains information about a physical interface. The table can be accessible only if the device supports ELMI protocol and if LMI is enabled on the interface.

This variable states whether Enhanced Link Management Interface(ELMI) protocol is enabled or not on a frame relay interface. Enumeration: 'disabled': 2, 'enabled': 1.

This variable states whether the Enhanced Link Management Interface(ELMI) address registration(AR) mechanism is enabled or not on a frame relay interface. A value of 1 indicates ELMI AR is supported on the interface. A value of 2 indicates ELMI AR is supported but the user disabled the exchange of IP address and ifIndex with the neighboring device. This object doesn't have any significance if cfrElmiLinkStatus is disabled on the interface. Enumeration: 'disabled': 2, 'enabled': 1.

This variable states the Enhanced Link Management(ELMI) status on the other end of the interface. If cfrElmiLinkStatus is enabled on the other end a value of 1 will be returned, else 2 will be returned. This object doesn't have any significance if cfrElmiLinkStatus is disabled on the interface Enumeration: 'disabled': 2, 'enabled': 1.

Table of CISCO Frame Relay Neighbor ELMI information that is specific to CISCO implementation.

Each entry of the table contains information of the neighboring device connected to a physical interface. The entry will be present only if ELMI is enabled on the neighboring device interface. If the value of the cfrElmiRemoteStatus in the cfrElmiEntry is 1 then a valid entry exists for the interface. If ELMI is not supported on the remote end then, the neighbor information for the interface will not be present

This variable indicates the status of ELMI Address registration(AR) on the neighboring device. A value of 1 indicates ELMI AR is not supported on the neighboring device. A value of 2 indicates ELMI AR is enabled on the interface. A value of 3 indicates AR is supported, but user disabled the exchange of IP address and ifIndex with the neighbor. Enumeration: 'disabled': 3, 'notsupported': 1, 'enabled': 2.

The Management IP address of the neighboring device to which the other end of this interface is connected. Network management system can use this address to send management messages to the device. If address registration is not supported on the remote end then the value will be 0.0.0.0. NMS uses this object in the topology discovery of the network.

The Interface index of the neighboring device to which this interface is connected. If the value of cfrElmiNeighborArStatus is 2 then this will have a valid value. If the value of cfrElmiNeighborArStatus is 3 or 1 then value of this object will be 0. NMS uses this object in the topology discovery of the network.

Vendor name of the neighboring device to which the other end of this interface is connected.

Platform name of the neighboring device to which the other end of this interface is connected.

Device name of the neighboring device to which the other end of this interface is connected.

Table of Frame Relay Fragmentation information. These are specific to Cisco's implementation.

Each entry of the table contains details of fragmentation configured on this circuit.

cfrFragSize defines the payload size of a fragment and it excludes the FR headers and any FR fragmentation header.

Fragmentation type configured by the user. The types supported are end-to-end, VoFR-cisco and VoFR.

Total number of frames received that have a fragmentation header.

Total number of fragments that are transmitted with a fragmenation header.

Total number of bytes received in frames that have a fragmentation header. The number of bytes include the FR header.

Total number of bytes that are transmitted in frames with a fragmenation header. The number of bytes also includes the FR header.

Total number of frames received that do not require reassembly and therefore will not contain the fragmentation header. This counter is valid only when end-to-end fragmentation type is set.

Total number of frames transmitted without fragmenting and therefore will not contain the fragmentation header. This counter is valid only when end-to-end fragmentation type is set.

Total number of bytes received in frames that do not require reassembly and therefore will not contain the fragmentation header. This counter is valid only when end-to-end fragmentation type is set.

Total number of bytes transmitted in frames that are not fragmented and therefore will not contain the fragmentation header. This counter is valid only when end-to-end fragmentation type is set.

Total number of fully reassembled frames. It also counts the number of packets received without FR fragmentation header (i.e. in un-fragmentated pkts).

Total number of bytes received in fully reassembled frames. It also counts the number of packets received without FR fragmentation header (i.e.in un-fragmentated pkts).

Total number of frames fragmented and trasmitted. It also counts the number of packets trasmitted without FR fragmentation header (i.e. in un-fragmentated pkts).

Total number of bytes transmitted in fragmented frames. It also counts the number of bytes trasmitted in frames without FR fragmentation header (i.e. in un-fragmentated pkts).

Number of received fragments dropped for reasons such as : running out of memory, receiving segments out of sequence, receiving an unexpected frame with a B bit set, timing out on a reassembling frame.

Number of fragments dropped because of running out of memory.

Number of reassemble timer timeouts for this circuit. A frame requiring more than two minutes to fully reassemble is dropped and timeout will be incremented by one.

Indicates the total number of packets received with an unexpected sequence number. All fragments being reassembled are dropped. Start a new packet with the received segment only if the B bit is set on the segment. Otherwise the new segment is also dropped.

Number of fragments received in this circuit with a B bit set. All fragments being reassembled are dropped and a new packet is started with this segment.

Number of fragments received in this circuit with skipped sequence number.

Number of packets that have been interleaved between segments.

Table of Frame Relay/Frame Relay and Frame Relay/ATM Network/Service Interworking connection information. These are specific to Cisco's implementation.

Each entry of the table contains information of a connection that is established for Frame Relay/Frame Relay and Frame Relay/ATM Network/Service Interworking.

The textual name of a for FR/FR or FR/ATM Network/Service Interworking connection.

The numerical identifier of a FR/FR or FR/ATM Network/Service Interworking connection.

Status of a FR/FR or FR/ATM Network/Service Interworking connection.

The textual name used to identify the first segment of a FR/FR or FR/ATM Network/Service Interworking connection.

The textual name used to identify the VC-Group in the first segment of a Frame Relay/ATM Network Interworking (FRF.5)connection. This field is not applicabe in case of, FRF.8 (Frame Relay/ATM Service Interworking) and FR-FR connectione.

The DLCI used as the first segment of a FR-FR or FR-ATM Network/Service Interworking connection.

The interface on which second segment of a FR-FR or FR-ATM Network/Service Interworking connection is configured.

The value of VPI, in the ATM connection, used as the second segment of a FR-ATM Network/Service Interworking connection. In case of FR-FR connection, the same will be used to display the DLCI used as the second segment.

The value of VCI, in the ATM connection, used as the second segment of a FR-ATM Network/Service Interworking connection. In case of FR-FR connection, this is not supported.

Shows whether Service Translation Mode is supported or not. Translation Mode is the interworking of internetworking (routed and/or bridged) protocols used in FR-ATM Service PVC Interworking(FRF.8). This is not supported in case of FRF.5 (FR-ATM network Interworking) and FR-FR connections. Enumeration: 'serviceTranslationNotEnabled': 2, 'serviceTranslationEnabled': 1.

The DLCI value used at the FR-SSCS layer. This is one of connection multiplexing methods used in Frame Relay/ATM Network Interworking. Not supported in case of FRF.8 (FR-ATM Service PVC Interworking) and FR-FR connections

Shows whether the FECN field in the FR frame is mapped to the ATM EFCI field of every cell generated out of the FR frame. This is used to indicate congestion in FR to ATM direction in case of Frame Relay/ATM Service PVC Interworking. Not supported in FRF.5 (Frame Relay/ATM Network Interworking and FR-FR connections. Enumeration: 'notMapFecn': 2, 'mapFecn': 1.

The method of operation for loss priority mapping in the B-ISDN to FR direction.. Not supported in case of FR-FR connection. Enumeration: 'noMapClp': 1, 'setDe1': 4, 'setDe0': 3, 'mapClp': 2.

The method of operation used to map loss priority mapping in the FR to ATM direction. Not supported in case of FR-FR connection. Enumeration: 'copyDeToFrsscsDeAndClp': 3, 'setClpTo0AndCopyDeToFrsscsDe': 1, 'setClpTo1AndCopyDeToFrsscsDe': 2, 'setClp0': 6, 'setClp1': 5, 'copyDeToClp': 4.

The compliance statement for entities which implement this Cisco Frame Relay MIB.

The compliance statement for entities which implement this Cisco Frame Relay MIB.

The compliance statement for entities which implement this Cisco Frame Relay MIB.

The compliance statement for entities which implement this Cisco Frame Relay MIB.

The compliance statement for entities which implement this Cisco Frame Relay MIB.

The compliance statement for entities which implement this Cisco Frame Relay MIB.

A collection of objects providing router's Frame Relay configuration and statistics information that are additional to the IETF standard Frame Relay DTE MIB.

A collection of objects providing router's Frame Relay LMI configuration and statistics information either supplemental to the frDlcmiTable of RFC 1315 or specific to Cisco's implementation.

A collection of objects providing information of a circuit that are not included in frCircuitTable of RFC1315 but are generic to Frame Relay.

A collection of objects that provide Cisco implementation specific FR circuit information. This is a Cisco extension for the frCircuitTable of RFC 1315.

A collection of objects that provide information about Frame Relay Traffic Shaping. These are additional to the IETF standard Frame Relay DTE MIB.

A collection of objects to provide mapping information of a Frame Relay virtual circuit. These are additional to the IETF standard Frame Relay DTE MIB.

A collection of objects to provide circuit information specific to a Frame Relay Switched Virtual Circuit.This is in addition to the IETF standard Frame Relay DTE MIB.

A collection of objects providing router's ELMI information.

A collection of objects providing router's ELMI information.

A collection of objects providing router's fragmentation information.

A collection of objects providing router's fragmentation information.

A collection of objects that provide Cisco implementation specific FR circuit information. This is a Cisco extension for the frCircuitTable of RFC 1315.