In-band Frame Relay management mode. A variety of options
exist which are differentiated by how PVCs can be provisioned
to manage the unit and the resulting impact to the logical
processing of Link Management Protocol messages (LMI spoofing
and sourcing). The unit is designed to support these management
modes even in non-provisioned or failed frame relay networks.
This setting also has implications upon how networking protocols
such as ARP and InARP are handled by the unit.
(1) inactive: in-band management is not enabled
(2) local DLCI mode: in-band managed using a private dedicated DLCI
accessible via the DTE port only. A DLCI value is configured
which, through LMI spoofing, will only be visible to the DTE
equipment and need not be provisioned on the WAN. All traffic on
this DLCI will be terminated by the unit.
(3) remote DLCI mode: in-band managed using a private dedicated DLCI
accessible via the WAN port only. A DLCI value is configured
which, through LMI spoofing, will only be visible from the WAN
side and will not be seen by any DTE equipment. All traffic on
this DLCI will be terminated by the unit.
(4) bidirectional mode: in-band managed using a private dedicated DLCI
accessible through either port. A DLCI value is configured
which is expected to be fully provisioned in the frame relay
network but dedicated to the management function of this particular
unit. All traffic on this DLCI will be terminated by the unit.
(5) piggyback mode: in-band managed using any DLCI on any interface. A
DLCI value is defined that becomes the default DLCI that will be
maintained by the unit during network or LMI failure conditions.
The unit will terminate and respond accordingly to management and
networking data while transparently passing on user data.
(6) fixed DCE mode: special mode of operation to support frame relay
applications that do not include a switch (frame relay DCE). The
unit will independently respond to LMI requests on each interface
and will provision the configured DLCI to each Frame Relay DTE device.
Except for this, the unit behaves like piggyback.
Parsed from file TFRAP.MIB.txt
Company: None
Module: TFRAP-MIB
In-band Frame Relay management mode. A variety of options
exist which are differentiated by how PVCs can be provisioned
to manage the unit and the resulting impact to the logical
processing of Link Management Protocol messages (LMI spoofing
and sourcing). The unit is designed to support these management
modes even in non-provisioned or failed frame relay networks.
This setting also has implications upon how networking protocols
such as ARP and InARP are handled by the unit.
(1) inactive: in-band management is not enabled
(2) local DLCI mode: in-band managed using a private dedicated DLCI
accessible via the DTE port only. A DLCI value is configured
which, through LMI spoofing, will only be visible to the DTE
equipment and need not be provisioned on the WAN. All traffic on
this DLCI will be terminated by the unit.
(3) remote DLCI mode: in-band managed using a private dedicated DLCI
accessible via the WAN port only. A DLCI value is configured
which, through LMI spoofing, will only be visible from the WAN
side and will not be seen by any DTE equipment. All traffic on
this DLCI will be terminated by the unit.
(4) bidirectional mode: in-band managed using a private dedicated DLCI
accessible through either port. A DLCI value is configured
which is expected to be fully provisioned in the frame relay
network but dedicated to the management function of this particular
unit. All traffic on this DLCI will be terminated by the unit.
(5) piggyback mode: in-band managed using any DLCI on any interface. A
DLCI value is defined that becomes the default DLCI that will be
maintained by the unit during network or LMI failure conditions.
The unit will terminate and respond accordingly to management and
networking data while transparently passing on user data.
(6) fixed DCE mode: special mode of operation to support frame relay
applications that do not include a switch (frame relay DCE). The
unit will independently respond to LMI requests on each interface
and will provision the configured DLCI to each Frame Relay DTE device.
Except for this, the unit behaves like piggyback.
Parsed from file TFRAP-MIB.mib
Module: TFRAP-MIB
Vendor: Sync Research, Inc.
Module: TFRAP-MIB
[Automatically extracted from oidview.com]
tfrapCfgFrDLCIMode OBJECT-TYPE SYNTAX INTEGER { inactive (1), local (2), remote (3), bidirectional (4), piggyback (5), fixedDCE (6) } ACCESS read-write STATUS mandatory DESCRIPTION "In-band Frame Relay management mode. A variety of options exist which are differentiated by how PVCs can be provisioned to manage the unit and the resulting impact to the logical processing of Link Management Protocol messages (LMI spoofing and sourcing). The unit is designed to support these management modes even in non-provisioned or failed frame relay networks. This setting also has implications upon how networking protocols such as ARP and InARP are handled by the unit. (1) inactive: in-band management is not enabled (2) local DLCI mode: in-band managed using a private dedicated DLCI accessible via the DTE port only. A DLCI value is configured which, through LMI spoofing, will only be visible to the DTE equipment and need not be provisioned on the WAN. All traffic on this DLCI will be terminated by the unit. (3) remote DLCI mode: in-band managed using a private dedicated DLCI accessible via the WAN port only. A DLCI value is configured which, through LMI spoofing, will only be visible from the WAN side and will not be seen by any DTE equipment. All traffic on this DLCI will be terminated by the unit. (4) bidirectional mode: in-band managed using a private dedicated DLCI accessible through either port. A DLCI value is configured which is expected to be fully provisioned in the frame relay network but dedicated to the management function of this particular unit. All traffic on this DLCI will be terminated by the unit. (5) piggyback mode: in-band managed using any DLCI on any interface. A DLCI value is defined that becomes the default DLCI that will be maintained by the unit during network or LMI failure conditions. The unit will terminate and respond accordingly to management and networking data while transparently passing on user data. (6) fixed DCE mode: special mode of operation to support frame relay applications that do not include a switch (frame relay DCE). The unit will independently respond to LMI requests on each interface and will provision the configured DLCI to each Frame Relay DTE device. Except for this, the unit behaves like piggyback." ::= { tfrapCfgFrDLCITable 1 }
tfrapCfgFrDLCIMode OBJECT-TYPE SYNTAX INTEGER { inactive (1), local (2), remote (3), bidirectional (4), piggyback (5), fixedDCE (6) } ACCESS read-write STATUS mandatory DESCRIPTION "In-band Frame Relay management mode. A variety of options exist which are differentiated by how PVCs can be provisioned to manage the unit and the resulting impact to the logical processing of Link Management Protocol messages (LMI spoofing and sourcing). The unit is designed to support these management modes even in non-provisioned or failed frame relay networks. This setting also has implications upon how networking protocols such as ARP and InARP are handled by the unit. (1) inactive: in-band management is not enabled (2) local DLCI mode: in-band managed using a private dedicated DLCI accessible via the DTE port only. A DLCI value is configured which, through LMI spoofing, will only be visible to the DTE equipment and need not be provisioned on the WAN. All traffic on this DLCI will be terminated by the unit. (3) remote DLCI mode: in-band managed using a private dedicated DLCI accessible via the WAN port only. A DLCI value is configured which, through LMI spoofing, will only be visible from the WAN side and will not be seen by any DTE equipment. All traffic on this DLCI will be terminated by the unit. (4) bidirectional mode: in-band managed using a private dedicated DLCI accessible through either port. A DLCI value is configured which is expected to be fully provisioned in the frame relay network but dedicated to the management function of this particular unit. All traffic on this DLCI will be terminated by the unit. (5) piggyback mode: in-band managed using any DLCI on any interface. A DLCI value is defined that becomes the default DLCI that will be maintained by the unit during network or LMI failure conditions. The unit will terminate and respond accordingly to management and networking data while transparently passing on user data. (6) fixed DCE mode: special mode of operation to support frame relay applications that do not include a switch (frame relay DCE). The unit will independently respond to LMI requests on each interface and will provision the configured DLCI to each Frame Relay DTE device. Except for this, the unit behaves like piggyback." ::= { tfrapCfgFrDLCITable 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.5.2.1.5.1.0 | tfrapCfgFrDLCIMode | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.5.2.1.5.2 | tfrapCfgFrDLCIValue | 1 | 1 | If in-band management is being used this DLCI value should be defined. In all modes of in-band management with the LMI Sourcing … |
| 1.3.6.1.4.1.485.5.2.1.5.3 | tfrapCfgFrDLCIEncap | 1 | 1 | This is the protocol used for enacapsulating and formatting ip data for Frame Relay transmission. This setting is specific to man… |
| 1.3.6.1.4.1.485.5.2.1.5.4 | tfrapCfgFrDLCIMgmtDE | 1 | 1 | Provides user control over the state of the Frame Relay Discard Eligibility bit of all management frames generated by the unit. F… |