The LMI type used in a Frame Relay application. This setting
must match the attached Frame Relay device configuration.
Annex-A and Annex-D use DLCI 0, and Type 1 uses DLCI 1023.
Type 1 is alternatively referred to as Cisco, Group of four,
or simply LMI. Annex-D may be referred to as ANSI T1.617.
Annex-A may be referred to as ITU or CCITT Q.933. Auto-sense
will either use the most recently detected LMI type or, in
the absence of any LMI, will attempt to instigate LMI
communications using each protocol.
(1) Annnex-A: conforms to ITU (CCITT) Q.933 annex A
(2) Annnex-D: conforms to ANSI T1.617 annex D
(3) Type 1: conforms to the original LMI as developed by
the Group of Four
(4) Auto-sense: unit will attempt to detect and synchronize
to the LMI type of the attached equipment.
Parsed from file TFRAP.MIB.txt
Company: None
Module: TFRAP-MIB
The LMI type used in a Frame Relay application. This setting
must match the attached Frame Relay device configuration.
Annex-A and Annex-D use DLCI 0, and Type 1 uses DLCI 1023.
Type 1 is alternatively referred to as Cisco, Group of four,
or simply LMI. Annex-D may be referred to as ANSI T1.617.
Annex-A may be referred to as ITU or CCITT Q.933. Auto-sense
will either use the most recently detected LMI type or, in
the absence of any LMI, will attempt to instigate LMI
communications using each protocol.
(1) Annnex-A: conforms to ITU (CCITT) Q.933 annex A
(2) Annnex-D: conforms to ANSI T1.617 annex D
(3) Type 1: conforms to the original LMI as developed by
the Group of Four
(4) Auto-sense: unit will attempt to detect and synchronize
to the LMI type of the attached equipment.
Parsed from file TFRAP-MIB.mib
Module: TFRAP-MIB
Vendor: Sync Research, Inc.
Module: TFRAP-MIB
[Automatically extracted from oidview.com]
tfrapCfgFrLmiType OBJECT-TYPE SYNTAX INTEGER { annexd (1), annexa (2), type1 (3), autosense (4) } ACCESS read-write STATUS mandatory DESCRIPTION "The LMI type used in a Frame Relay application. This setting must match the attached Frame Relay device configuration. Annex-A and Annex-D use DLCI 0, and Type 1 uses DLCI 1023. Type 1 is alternatively referred to as Cisco, Group of four, or simply LMI. Annex-D may be referred to as ANSI T1.617. Annex-A may be referred to as ITU or CCITT Q.933. Auto-sense will either use the most recently detected LMI type or, in the absence of any LMI, will attempt to instigate LMI communications using each protocol. (1) Annnex-A: conforms to ITU (CCITT) Q.933 annex A (2) Annnex-D: conforms to ANSI T1.617 annex D (3) Type 1: conforms to the original LMI as developed by the Group of Four (4) Auto-sense: unit will attempt to detect and synchronize to the LMI type of the attached equipment." ::= { tfrapCfgFrTable 3 }
tfrapCfgFrLmiType OBJECT-TYPE SYNTAX INTEGER { annexd (1), annexa (2), type1 (3), autosense (4) } ACCESS read-write STATUS mandatory DESCRIPTION "The LMI type used in a Frame Relay application. This setting must match the attached Frame Relay device configuration. Annex-A and Annex-D use DLCI 0, and Type 1 uses DLCI 1023. Type 1 is alternatively referred to as Cisco, Group of four, or simply LMI. Annex-D may be referred to as ANSI T1.617. Annex-A may be referred to as ITU or CCITT Q.933. Auto-sense will either use the most recently detected LMI type or, in the absence of any LMI, will attempt to instigate LMI communications using each protocol. (1) Annnex-A: conforms to ITU (CCITT) Q.933 annex A (2) Annnex-D: conforms to ANSI T1.617 annex D (3) Type 1: conforms to the original LMI as developed by the Group of Four (4) Auto-sense: unit will attempt to detect and synchronize to the LMI type of the attached equipment." ::= { tfrapCfgFrTable 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.5.2.5.3.0 | tfrapCfgFrLmiType | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.5.2.5.1 | tfrapCfgFrAddrLen | 1 | 1 | Defines the size of the DLCI address field of the Frame Relay header. This setting must correspond to the Frame Relay transmissio… |
| 1.3.6.1.4.1.485.5.2.5.2 | tfrapCfgFrCrcMode | 1 | 1 | This defines the manner in which the unit handles HDLC protocol errors (crc errors) in a Frame Relay application. If Discard is s… |
| 1.3.6.1.4.1.485.5.2.5.4 | tfrapCfgFrLmiInactivityTimeout | 1 | 1 | Timer used by the unit to determine that an attached device is not participating in the LMI protocol and that the unit should att… |
| 1.3.6.1.4.1.485.5.2.5.5 | tfrapCfgFrLmiKeepaliveTimeout | 1 | 1 | Timer used by the unit to determine the frequency at which Status Enquiries are issued during LMI sourcing states where the unit… |
| 1.3.6.1.4.1.485.5.2.5.6 | tfrapCfgFrAddrResMode | 1 | 1 | Enable ARP (2), INARP (3), both (4), or neither (1). |
| 1.3.6.1.4.1.485.5.2.5.7 | tfrapCfgFrAddrResInarpTimer | 1 | 1 | The frequency at which the unit issues INARP requests (in seconds) from 5 to 86400 (24 hours). |
| 1.3.6.1.4.1.485.5.2.5.8 | tfrapCfgFrLmiFullStatus | 1 | 1 | Timer used by the unit to determine if an LMI Full Status Report is missing. In the absence of a Full Status report for the durat… |
| 1.3.6.1.4.1.485.5.2.5.9 | tfrapCfgFrAddrResDlcis | 1 | 1 | Address Resolution Dlcis determines which dlcis are used for address resolution. Multiple DLCI support only applies to piggyback … |