This value indicates whether an LC-ATM is directly
or indirectly (by means of a VP) connected. If set to
true(1), indicates that this interface is directly
connected LC-ATM; otherwise, it MUST be set to
false(2). Note that although it can be intimated
from RFC 3057 that multiple VPs may be used,
in practice only a single one is used, and therefore
the authors of this MIB module have chosen to model
it as such.
Parsed from file rfc4368-MPLS-LC-ATM-and-FR-MIBs.mib-1.txt
Company: None
Module: MPLS-LC-ATM-STD-MIB
This value indicates whether an LC-ATM is directly
or indirectly (by means of a VP) connected. If set to
true(1), indicates that this interface is directly
connected LC-ATM; otherwise, it MUST be set to
false(2). Note that although it can be intimated
from RFC 3057 that multiple VPs may be used,
in practice only a single one is used, and therefore
the authors of this MIB module have chosen to model
it as such.
Parsed from file MPLS-LC-ATM-STD-MIB.mib
Module: MPLS-LC-ATM-STD-MIB
Vendor: IETF RFCs
Module: MPLS-LC-ATM-STD-MIB (rfc4368-MPLS-LC-ATM-and-FR-MIBs.mib-1)
Type: TABULAR
Access: read-create
Syntax: TruthValue
Automatically extracted from www.mibdepot.com
mplsLcAtmVcDirectlyConnected OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "This value indicates whether an LC-ATM is directly or indirectly (by means of a VP) connected. If set to true(1), indicates that this interface is directly connected LC-ATM; otherwise, it MUST be set to false(2). Note that although it can be intimated from RFC 3057 that multiple VPs may be used, in practice only a single one is used, and therefore the authors of this MIB module have chosen to model it as such." DEFVAL { true } ::= { mplsLcAtmStdInterfaceConfEntry 6 }
mplsLcAtmVcDirectlyConnected OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "This value indicates whether an LC-ATM is directly or indirectly (by means of a VP) connected. If set to true(1), indicates that this interface is directly connected LC-ATM; otherwise, it MUST be set to false(2). Note that although it can be intimated from RFC 3057 that multiple VPs may be used, in practice only a single one is used, and therefore the authors of this MIB module have chosen to model it as such." DEFVAL { true } ::= { mplsLcAtmStdInterfaceConfEntry 6 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.10.166.9.1.1.1.1 | mplsLcAtmStdCtrlVpi | 0 | 0 | This is the VPI value over which this LSR is willing to accept control traffic on this interface. |
| 1.3.6.1.2.1.10.166.9.1.1.1.2 | mplsLcAtmStdCtrlVci | 0 | 0 | This is the VCI value over which this LSR is willing to accept control traffic on this interface. |
| 1.3.6.1.2.1.10.166.9.1.1.1.3 | mplsLcAtmStdUnlabTrafVpi | 0 | 0 | This is the VPI value over which this LSR is willing to accept unlabeled traffic on this interface. |
| 1.3.6.1.2.1.10.166.9.1.1.1.4 | mplsLcAtmStdUnlabTrafVci | 0 | 0 | This is the VCI value over which this LSR is willing to accept unlabeled traffic on this interface. |
| 1.3.6.1.2.1.10.166.9.1.1.1.5 | mplsLcAtmStdVcMerge | 0 | 0 | If set to true(1), indicates that this interface is capable of ATM VC merge; otherwise, it MUST be set to false(2). |
| 1.3.6.1.2.1.10.166.9.1.1.1.7 | mplsLcAtmLcAtmVPI | 0 | 0 | This is the VPI value used for indirectly connected LC-ATM interfaces. For these interfaces, the VPI field is not available to MP… |
| 1.3.6.1.2.1.10.166.9.1.1.1.8 | mplsLcAtmStdIfConfRowStatus | 0 | 0 | This object is used to create and delete entries in this table. When configuring entries in this table, the corresponding ifEntry… |
| 1.3.6.1.2.1.10.166.9.1.1.1.9 | mplsLcAtmStdIfConfStorageType | 0 | 0 | The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any colu… |