Shows the mode that DLCI In-band Management is set up for -
inactive (1) - Inband management is not enabled;
local (2) - Inband managed using a dedicated private
PVC with access exclusively through the
DTE interface;
remote (3) - Inband managed using a dedicated private
PVC with access exclusively through the
WAN interface;
bidirectional (4) - Inband managed using a dedicated private
PVC with access supported through either
interface;
piggyback (5) - Inband managed using any provisioned PVC,
statistically multiplexed with user data;
fixedDCE (6) - Inband managed mode similar to piggyback
mode except for LMI behavior; The unit
will always source LMI Responses separately
on each interface (emulating a Frame Relay
DCE device). A single PVC will be provisioned
and is used for both user data and management
traffic. This mode of operation is useful in
an environment that does not include a Frame
Relay switch but does include a pair of
interconnected Frame Relay FRADs or Routers
which can only be configured as a Frame Relay
DTE device.
Parsed from file MFRAP.MIB.txt
Company: None
Module: MFRAP-MIB
Shows the mode that DLCI In-band Management is set up for -
inactive (1) - Inband management is not enabled;
local (2) - Inband managed using a dedicated private
PVC with access exclusively through the
DTE interface;
remote (3) - Inband managed using a dedicated private
PVC with access exclusively through the
WAN interface;
bidirectional (4) - Inband managed using a dedicated private
PVC with access supported through either
interface;
piggyback (5) - Inband managed using any provisioned PVC,
statistically multiplexed with user data;
fixedDCE (6) - Inband managed mode similar to piggyback
mode except for LMI behavior; The unit
will always source LMI Responses separately
on each interface (emulating a Frame Relay
DCE device). A single PVC will be provisioned
and is used for both user data and management
traffic. This mode of operation is useful in
an environment that does not include a Frame
Relay switch but does include a pair of
interconnected Frame Relay FRADs or Routers
which can only be configured as a Frame Relay
DTE device.
Parsed from file MFRAP-MIB.mib
Module: MFRAP-MIB
Vendor: Sync Research, Inc.
Module: MFRAP-MIB
[Automatically extracted from oidview.com]
mfrapCfgFrDLCIMode OBJECT-TYPE SYNTAX INTEGER { inactive (1), local (2), remote (3), bidirectional (4), piggyback (5), fixedDCE (6) } ACCESS read-write STATUS mandatory DESCRIPTION "Shows the mode that DLCI In-band Management is set up for - inactive (1) - Inband management is not enabled; local (2) - Inband managed using a dedicated private PVC with access exclusively through the DTE interface; remote (3) - Inband managed using a dedicated private PVC with access exclusively through the WAN interface; bidirectional (4) - Inband managed using a dedicated private PVC with access supported through either interface; piggyback (5) - Inband managed using any provisioned PVC, statistically multiplexed with user data; fixedDCE (6) - Inband managed mode similar to piggyback mode except for LMI behavior; The unit will always source LMI Responses separately on each interface (emulating a Frame Relay DCE device). A single PVC will be provisioned and is used for both user data and management traffic. This mode of operation is useful in an environment that does not include a Frame Relay switch but does include a pair of interconnected Frame Relay FRADs or Routers which can only be configured as a Frame Relay DTE device." ::= { mfrapCfgFrDLCITable 1 }
mfrapCfgFrDLCIMode OBJECT-TYPE SYNTAX INTEGER { inactive (1), local (2), remote (3), bidirectional (4), piggyback (5), fixedDCE (6) } ACCESS read-write STATUS mandatory DESCRIPTION "Shows the mode that DLCI In-band Management is set up for - inactive (1) - Inband management is not enabled; local (2) - Inband managed using a dedicated private PVC with access exclusively through the DTE interface; remote (3) - Inband managed using a dedicated private PVC with access exclusively through the WAN interface; bidirectional (4) - Inband managed using a dedicated private PVC with access supported through either interface; piggyback (5) - Inband managed using any provisioned PVC, statistically multiplexed with user data; fixedDCE (6) - Inband managed mode similar to piggyback mode except for LMI behavior; The unit will always source LMI Responses separately on each interface (emulating a Frame Relay DCE device). A single PVC will be provisioned and is used for both user data and management traffic. This mode of operation is useful in an environment that does not include a Frame Relay switch but does include a pair of interconnected Frame Relay FRADs or Routers which can only be configured as a Frame Relay DTE device." ::= { mfrapCfgFrDLCITable 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.8.2.1.5.1.0 | mfrapCfgFrDLCIMode | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.8.2.1.5.2 | mfrapCfgFrDLCIValue | 1 | 1 | The DLCI identifier, the value of the DLCI field in the frame. |
| 1.3.6.1.4.1.485.8.2.1.5.3 | mfrapCfgFrDLCIEncap | 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.8.2.1.5.4 | mfrapCfgFrDLCIMgmtDE | 1 | 1 | Provides user control over the state of the Frame Relay Discard Eligibility bit of all management frames generated by the unit. F… |