marsVcCtrlType OBJECT-TYPE
SYNTAX INTEGER {
pointToPointVC (1),
clusterControlVC (2),
serverControlVC (3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Control VC type used to specify a particular connection.
pointToPointVC (1):
used by the ATM endpoints (clients) or the MCS for
registration and queries. This VC is set up from
a MARS client and MCS to this MARS. It is a
bi-directional VC.
clusterControlVC (2):
used by MARS to issue asynchronous updates to ATM
an ATM client. This VC is established from the
MARs to the ATM client.
serverControlVC (3):
used by MARS to issue asynchronous update to ATM
multicast servers. This type of VC exists when at
least a MCS is being used."
View at oid-info.com
Control VC type used to specify a particular connection.
pointToPointVC (1):
used by the ATM endpoints (clients) or the MCS for
registration and queries. This VC is set up from
a MARS client and MCS to this MARS. It is a
bi-directional VC.
clusterControlVC (2):
used by MARS to issue asynchronous updates to ATM
an ATM client. This VC is established from the
MARs to the ATM client.
serverControlVC (3):
used by MARS to issue asynchronous update to ATM
multicast servers. This type of VC exists when at
least a MCS is being used.
Parsed from file IPATM-IPMC-MIB.mib
Module: IPATM-IPMC-MIB
Automatically extracted from RFC2417
marsVcCtrlType OBJECT-TYPE SYNTAX INTEGER { pointToPointVC (1), clusterControlVC (2), serverControlVC (3) } MAX-ACCESS read-create STATUS current DESCRIPTION "Control VC type used to specify a particular connection. pointToPointVC (1): used by the ATM endpoints (clients) or the MCS for registration and queries. This VC is set up from a MARS client and MCS to this MARS. It is a bi-directional VC. clusterControlVC (2): used by MARS to issue asynchronous updates to ATM an ATM client. This VC is established from the MARs to the ATM client. serverControlVC (3): used by MARS to issue asynchronous update to ATM multicast servers. This type of VC exists when at least a MCS is being used." ::= { marsVcEntry 8 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.57.2.5.1.1 | marsVcVpi | 0 | 0 | The value of virtual path identifier (VPI). Since a VPI can be numbered 0, this sub-index can take a value of 0. |
| 1.3.6.1.2.1.57.2.5.1.2 | marsVcVci | 0 | 0 | The value of virtual circuit identifier (VCI). Since a VCI can be numbered 0, this sub-index can take a value of 0. |
| 1.3.6.1.2.1.57.2.5.1.5 | marsVcPartyAddr | 0 | 0 | An ATM party address in which this VC is linked. The party type is identified by the marsVcPartyAddrType. |
| 1.3.6.1.2.1.57.2.5.1.6 | marsVcPartyAddrType | 0 | 0 | The party type is associated with the party address. The 'called (1)' indicates that the party address is a destination address … |
| 1.3.6.1.2.1.57.2.5.1.7 | marsVcType | 0 | 0 | Circuit Connection type: permanent virtual circuit or switched virtual circuit. |
| 1.3.6.1.2.1.57.2.5.1.9 | marsVcIdleTimer | 0 | 0 | The idle timer associated with this VC. The minimum suggested value is 1 minute and the recommended default value is 20 minutes. |
| 1.3.6.1.2.1.57.2.5.1.10 | marsVcCmi | 0 | 0 | Cluster member identifier (CMI) which uniquely identifies each endpoint attached to the cluster. This variable applies to each '… |
| 1.3.6.1.2.1.57.2.5.1.11 | marsVcEncapsType | 0 | 0 | The encapsulation type used when communicating over this VC. |
| 1.3.6.1.2.1.57.2.5.1.12 | marsVcNegotiatedMtu | 0 | 0 | The negotiated MTU when communicating over this VC. |
| 1.3.6.1.2.1.57.2.5.1.13 | marsVcRowStatus | 0 | 0 | The object is used to create, delete or modify a row in this table. A row cannot be made 'active' until instances of all correspon… |