For point-to-point ATM VP and VC cross-connections, this managed object identifies the cross-connection relationship between two instances of the vpCTPBidirectional object class or vcCTPBidirectional object class, respectively. The vpCTPBidirectional or vcCTPBidirectional object instances being cross-connected are identified by the fromTermination and toTermination attributes inherited from the crossConnection object class defined in ITU-T Recommendation M.3100. For multipoint ATM VP and VC cross-connections, this managed object identifies the cross-connect relationship between an instance of the vpCTPBidirectional object class or vcCTPBidirectional object class and an instance of the multipointBridge object class. For multipoint ATM VP and VC cross-connections, each vpCTPBidirectional or vcCTPBidirectional object instance connected to the multipointBridge object is identified by the fromTermination attribute of the atmCrossConnection object, while the instance of the multipointBridge object class is identified by the toTermination attribute. Note that multipoint ATM cross- connections are established by cross-connecting multiple instances of the vpCTPBidirectional or vcCTPBidirectional object class (each with its own atmCrossConnection object) to a single instance of the multipointBridge object class. The administrativeState attribute inherited by this managed object may be used by the managing system to inhibit (lock) and allow (unlock) ATM cell flow through the ATM cross-connection being represented. The recoveryType attribute identifies whether the ATM cross-connection is recoverable (default) or non- recoverable. Recoverable cross-connections remain intact regardless of the operational state of the cross- connection. Non-recoverable ATM cross-connections are cross-connections that are automatically released by the managed system upon detection of a service affecting failure. Instances of this object class are automatically created and deleted by the managed system based on operations performed on the containing atmFabric or atmMpFabric object. All ATM VP/VC cross-connections are, by definition, bi-directional; therefore, the directionality attribute, inherited from the crossConnection object class, shall be set to the fixed value of bidirectional. The value of the signalType attribute is for further study.
OID reference
atmCrossConnection
1.3.6.1.4.1.353.5.1.1.0.3.2
Description
For point-to-point ATM VP and VC cross-connections, this managed object identifies the cross-connection relationship between two instances of the vpCTPBidirectional object class or vcCTPBidirectional object class, respectively. The vpCTPBidirectional or vcCTPBidirectional object instances being cross-connected are ide…
Identification
Identifier and names
- Parent
- 1.3.6.1.4.1.353.5.1.1.0.3 (3)
- Node code
- 2
- Node name
- atmCrossConnection
- Numeric OID
- 1.3.6.1.4.1.353.5.1.1.0.3.2
- URN notation
- urn:oid:1.3.6.1.4.1.353.5.1.1.0.3.2
ASN.1, OID-IRI and named path variants
- ASN.1 notation
-
{1 3 6 1 4 1 353 5 1 1 0 3 2}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 3 atmCrossConnection(2)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/4/1/353/5/1/1/0/3/2
- /ISO/Identified-Organization/6/1/4/1/353/5/1/1/0/3/2
- /ISO/3/6/1/4/1/353/5/1/1/0/3/2
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/atmForum/atmForumNetworkManagement/atmfM4/1/0/3/atmCrossConnection
- /iso/identified-organization/dod/internet/private/enterprise/atmForum/atmForumNetworkManagment/atmfM4/1/0/3/atmCrossConnection
- /iso/identified-organization/dod/internet/private/enterprises/atmForum/atmForumNetworkManagement/atmfM4/1/0/3/atmCrossConnection
- /iso/identified-organization/dod/internet/private/enterprises/atmForum/atmForumNetworkManagment/atmfM4/1/0/3/atmCrossConnection
- /iso/identified-organization/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagement/atmfM4/1/0/3/atmCrossConnection
- /iso/identified-organization/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagment/atmfM4/1/0/3/atmCrossConnection
- /iso/identified-organization/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagement/atmfM4/1/0/3/atmCrossConnection
- /iso/identified-organization/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagment/atmfM4/1/0/3/atmCrossConnection
- /iso/org/dod/internet/private/enterprise/atmForum/atmForumNetworkManagement/atmfM4/1/0/3/atmCrossConnection
- /iso/org/dod/internet/private/enterprise/atmForum/atmForumNetworkManagment/atmfM4/1/0/3/atmCrossConnection
- /iso/org/dod/internet/private/enterprises/atmForum/atmForumNetworkManagement/atmfM4/1/0/3/atmCrossConnection
- /iso/org/dod/internet/private/enterprises/atmForum/atmForumNetworkManagment/atmfM4/1/0/3/atmCrossConnection
- /iso/org/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagement/atmfM4/1/0/3/atmCrossConnection
- /iso/org/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagment/atmfM4/1/0/3/atmCrossConnection
- /iso/org/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagement/atmfM4/1/0/3/atmCrossConnection
- /iso/org/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagment/atmfM4/1/0/3/atmCrossConnection
- Additional combinations skipped.
Published definition
The displayed source records contain one distinct definition. Compare its source records.
atmCrossConnection MANAGED OBJECT CLASS
DERIVED FROM "ITU-T M.3100": crossConnection;
CHARACTERIZED BY
"ITU-T M.3100": createDeleteNotificationsPackage,
atmCrossConnectionPkg PACKAGE
BEHAVIOUR atmCrossConnectionBeh;
ATTRIBUTES
recoveryType
GET-REPLACE;;;
REGISTERED AS {atmfM4ObjectClass 2};
Meaning
Descriptions
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Evidence
Source records
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Records for description 1ATM Forum M4 official CMIP specifications
atmCrossConnection · deprecatedATM Forum M4 official CMIP specifications
Status in source: deprecated.
Names: atmCrossConnection
Technical details
{
"gdmo_kind": "MANAGED OBJECT CLASS",
"definition": [
"atmCrossConnection",
"MANAGED",
"OBJECT",
"CLASS",
"DERIVED",
"FROM",
[
"literal",
"224954552d54204d2e3331303022"
],
":",
"crossConnection",
";",
"CHARACTERIZED",
"BY",
[
"literal",
"224954552d54204d2e3331303022"
],
":",
"createDeleteNotificationsPackage",
",",
"atmCrossConnectionPkg",
"PACKAGE",
"BEHAVIOUR",
"atmCrossConnectionBeh",
";",
"ATTRIBUTES",
"recoveryType",
"GET-REPLACE",
";",
";",
";",
"REGISTERED",
"AS",
"{",
"atmfM4ObjectClass",
"2",
"}",
";"
]
}- ATM Forum M4 official CMIP specifications
· Publisher's source file: ATM Forum af-nm-0027.001 — original M4 specification PDF
See published definition above
Source data warning: The publisher places this definition in Annex B, Deprecated Information Model Entities.
· Download ATM Forum af-nm-0027.001 — original M4 specification PDFRelated source files and packages:
Registration