If configured for Frame Relay with a non-zero LMI inactivity timer
the unit will monitor the status of LMI and, if proper messaging
is not detected, will attempt to emulate either Frame Relay DTE or
DCE devices in attempt to restore LMI to any attached equipment and
provide managed access for diagnostic purposes. Typically frads/routers
are Frame Relay DTE while switches are Frame Relay DCE but this model
may vary. In the absence of full-duplex LMI, the unit will cycle
through various states in attempt to adapt to an LMI partner. The
unit will try each state for the duration of the LMI Inactivity timer
and then advance to the next one if satisfactory handshaking is not
established. While in any of these states if full-duplex LMI handshaking
does appear, the unit will immediately revert to the passthrough state.
(1) initializing
(2) Passthrough: not sourcing any LMI messages.
(3) Status Enquiries out DTE interface: unit is emulating a Frame
Relay DTE device out the its (physical) DTE interface.
(4) Status Enquiries out WAN interface: unit is emulating a Frame
Relay DTE device out the its WAN interface.
(5) Status Responses out the DTE interface: unit is emulating a
Frame Relay DCE device out the its (physical) DTE interface
(provisioning the single default management DLCI).
(6) Status Responses out the WAN interface: unit is emulating a
Frame Relay DCE device out the its WAN interface (provisioning
the single default management DLCI).
(7) Disabled - LMI Inactivity timer is zero or unit not configured
for a Frame Relay application.
(8) Status Responses out both DTE and WAN interfaces: unit is
configured for Fixed DCE mode of management and emulates a Frame
Relay DCE independently on both ports (provisioning
the single default management DLCI).
Parsed from file TFRAP.MIB.txt
Company: None
Module: TFRAP-MIB
If configured for Frame Relay with a non-zero LMI inactivity timer
the unit will monitor the status of LMI and, if proper messaging
is not detected, will attempt to emulate either Frame Relay DTE or
DCE devices in attempt to restore LMI to any attached equipment and
provide managed access for diagnostic purposes. Typically frads/routers
are Frame Relay DTE while switches are Frame Relay DCE but this model
may vary. In the absence of full-duplex LMI, the unit will cycle
through various states in attempt to adapt to an LMI partner. The
unit will try each state for the duration of the LMI Inactivity timer
and then advance to the next one if satisfactory handshaking is not
established. While in any of these states if full-duplex LMI handshaking
does appear, the unit will immediately revert to the passthrough state.
(1) initializing
(2) Passthrough: not sourcing any LMI messages.
(3) Status Enquiries out DTE interface: unit is emulating a Frame
Relay DTE device out the its (physical) DTE interface.
(4) Status Enquiries out WAN interface: unit is emulating a Frame
Relay DTE device out the its WAN interface.
(5) Status Responses out the DTE interface: unit is emulating a
Frame Relay DCE device out the its (physical) DTE interface
(provisioning the single default management DLCI).
(6) Status Responses out the WAN interface: unit is emulating a
Frame Relay DCE device out the its WAN interface (provisioning
the single default management DLCI).
(7) Disabled - LMI Inactivity timer is zero or unit not configured
for a Frame Relay application.
(8) Status Responses out both DTE and WAN interfaces: unit is
configured for Fixed DCE mode of management and emulates a Frame
Relay DCE independently on both ports (provisioning
the single default management DLCI).
Parsed from file TFRAP-MIB.mib
Module: TFRAP-MIB
Vendor: Sync Research, Inc.
Module: TFRAP-MIB
[Automatically extracted from oidview.com]
tfrapLmiSourcing OBJECT-TYPE SYNTAX INTEGER { initializing (1), passthrough (2), user-dte (3), user-t1 (4), network-dte (5), network-t1 (6), disabled (7), both-ports (8) } ACCESS read-only STATUS mandatory DESCRIPTION "If configured for Frame Relay with a non-zero LMI inactivity timer the unit will monitor the status of LMI and, if proper messaging is not detected, will attempt to emulate either Frame Relay DTE or DCE devices in attempt to restore LMI to any attached equipment and provide managed access for diagnostic purposes. Typically frads/routers are Frame Relay DTE while switches are Frame Relay DCE but this model may vary. In the absence of full-duplex LMI, the unit will cycle through various states in attempt to adapt to an LMI partner. The unit will try each state for the duration of the LMI Inactivity timer and then advance to the next one if satisfactory handshaking is not established. While in any of these states if full-duplex LMI handshaking does appear, the unit will immediately revert to the passthrough state. (1) initializing (2) Passthrough: not sourcing any LMI messages. (3) Status Enquiries out DTE interface: unit is emulating a Frame Relay DTE device out the its (physical) DTE interface. (4) Status Enquiries out WAN interface: unit is emulating a Frame Relay DTE device out the its WAN interface. (5) Status Responses out the DTE interface: unit is emulating a Frame Relay DCE device out the its (physical) DTE interface (provisioning the single default management DLCI). (6) Status Responses out the WAN interface: unit is emulating a Frame Relay DCE device out the its WAN interface (provisioning the single default management DLCI). (7) Disabled - LMI Inactivity timer is zero or unit not configured for a Frame Relay application. (8) Status Responses out both DTE and WAN interfaces: unit is configured for Fixed DCE mode of management and emulates a Frame Relay DCE independently on both ports (provisioning the single default management DLCI)." ::= { tfrapStatus 6 }
tfrapLmiSourcing OBJECT-TYPE SYNTAX INTEGER { initializing (1), passthrough (2), user-dte (3), user-t1 (4), network-dte (5), network-t1 (6), disabled (7), both-ports (8) } ACCESS read-only STATUS mandatory DESCRIPTION "If configured for Frame Relay with a non-zero LMI inactivity timer the unit will monitor the status of LMI and, if proper messaging is not detected, will attempt to emulate either Frame Relay DTE or DCE devices in attempt to restore LMI to any attached equipment and provide managed access for diagnostic purposes. Typically frads/routers are Frame Relay DTE while switches are Frame Relay DCE but this model may vary. In the absence of full-duplex LMI, the unit will cycle through various states in attempt to adapt to an LMI partner. The unit will try each state for the duration of the LMI Inactivity timer and then advance to the next one if satisfactory handshaking is not established. While in any of these states if full-duplex LMI handshaking does appear, the unit will immediately revert to the passthrough state. (1) initializing (2) Passthrough: not sourcing any LMI messages. (3) Status Enquiries out DTE interface: unit is emulating a Frame Relay DTE device out the its (physical) DTE interface. (4) Status Enquiries out WAN interface: unit is emulating a Frame Relay DTE device out the its WAN interface. (5) Status Responses out the DTE interface: unit is emulating a Frame Relay DCE device out the its (physical) DTE interface (provisioning the single default management DLCI). (6) Status Responses out the WAN interface: unit is emulating a Frame Relay DCE device out the its WAN interface (provisioning the single default management DLCI). (7) Disabled - LMI Inactivity timer is zero or unit not configured for a Frame Relay application. (8) Status Responses out both DTE and WAN interfaces: unit is configured for Fixed DCE mode of management and emulates a Frame Relay DCE independently on both ports (provisioning the single default management DLCI)." ::= { tfrapStatus 6 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.5.4.6.0 | tfrapLmiSourcing | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.5.4.1 | tfrapStatusIntfTable | 9 | 18 | tfrapStatusIntftable |
| 1.3.6.1.4.1.485.5.4.2 | tfrapVnipTopologyTable | 1 | 23 | VNIP topology is a feature that, for each interface, maps all compatible VNIP peers, their DLCI value, ip address and relative lo… |
| 1.3.6.1.4.1.485.5.4.3 | tfrapStatusMgmtTable | 5 | 10 | None |
| 1.3.6.1.4.1.485.5.4.4 | tfrapStatusLedTable | 7 | 14 | None |
| 1.3.6.1.4.1.485.5.4.5 | tfrapVnipTransitDelayClear | 1 | 1 | Allows the user to clear all the VNIP Transit Delay data collected in the VNIP topology database. (1) Clear entire Transit Delay … |
| 1.3.6.1.4.1.485.5.4.11 | tfrapVBertClear | 1 | 1 | Allows the user to clear all the VBERT data collected in the VNIP topology database as long as the entry is not in a test status.… |
| 1.3.6.1.4.1.485.5.4.12 | tfrapStatusLmiAutosense | 1 | 1 | This indicates the current status of LMI Auto Sensing if it's enabled. (1) Disabled: LMI is configured as Type 1, Annex-D, or Ann… |