OID reference

connectTap

1.3.6.1.4.1.353.5.1.1.0.9.11

Description

This action will connect one TAP-PP or one TAP-VC to a resource to be tested. Each invocation will allow monitoring one direction of a cell stream. To monitor both sides of a bi-directional cell stream requires the connection of two TAP objects The action request contains the name of the resource to be monitored. For …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.353.5.1.1.0.9 (9)
Node code
11
Node name
connectTap
Numeric OID
1.3.6.1.4.1.353.5.1.1.0.9.11
URN notation
urn:oid:1.3.6.1.4.1.353.5.1.1.0.9.11
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 353 5 1 1 0 9 11}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagement(5) atmfM4(1) 1 0 9 connectTap(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagment(5) atmfM4(1) 1 0 9 connectTap(11)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/353/5/1/1/0/9/11
  • /ISO/Identified-Organization/6/1/4/1/353/5/1/1/0/9/11
  • /ISO/3/6/1/4/1/353/5/1/1/0/9/11
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/atmForum/atmForumNetworkManagement/atmfM4/1/0/9/connectTap
  • /iso/identified-organization/dod/internet/private/enterprise/atmForum/atmForumNetworkManagment/atmfM4/1/0/9/connectTap
  • /iso/identified-organization/dod/internet/private/enterprises/atmForum/atmForumNetworkManagement/atmfM4/1/0/9/connectTap
  • /iso/identified-organization/dod/internet/private/enterprises/atmForum/atmForumNetworkManagment/atmfM4/1/0/9/connectTap
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagement/atmfM4/1/0/9/connectTap
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagment/atmfM4/1/0/9/connectTap
  • /iso/identified-organization/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagement/atmfM4/1/0/9/connectTap
  • /iso/identified-organization/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagment/atmfM4/1/0/9/connectTap
  • /iso/org/dod/internet/private/enterprise/atmForum/atmForumNetworkManagement/atmfM4/1/0/9/connectTap
  • /iso/org/dod/internet/private/enterprise/atmForum/atmForumNetworkManagment/atmfM4/1/0/9/connectTap
  • /iso/org/dod/internet/private/enterprises/atmForum/atmForumNetworkManagement/atmfM4/1/0/9/connectTap
  • /iso/org/dod/internet/private/enterprises/atmForum/atmForumNetworkManagment/atmfM4/1/0/9/connectTap
  • /iso/org/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagement/atmfM4/1/0/9/connectTap
  • /iso/org/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagment/atmfM4/1/0/9/connectTap
  • /iso/org/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagement/atmfM4/1/0/9/connectTap
  • /iso/org/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagment/atmfM4/1/0/9/connectTap
  • Additional combinations skipped.

The displayed source records contain one distinct definition. Compare its source records.

connectTap ACTION
 BEHAVIOUR
 connectTapBeh BEHAVIOUR
 DEFINED AS
  " This action will connect one TAP-PP or one TAP-VC to a resource to be tested. Each invocation will allow
  monitoring one direction of a cell stream. To monitor both sides of a bi-directional cell stream requires the
  connection of two TAP objects The action request contains the name of the resource to be monitored. For physical
  port mirroring (PP) or virtual connection access (VC), this parameter contains a pointer to the tcAdaptor object
  that represents the cell stream to be monitored. For virtual connection access, this parameter will also identify the
  VPI value, and if necessary, the VCI value of the connection under test. The test access path to be used is
  identified in the action request by a pointer to a tapPP or tapVC object. If a value is not supplied, the ATM NE
  should select an available TAP of the appropriate type. The name of the selected tapPP or tapVC object shall be
  returned in the action reply. If the requested TAP is not available or if all TAPs of the requested type are
  unavailable, the action reply should indicate TAP not available. The value of the accessMode attribute of the TAP
  object is also defined in the action request.";;
 MODE CONFIRMED;
 WITH INFORMATION SYNTAX AtmMIBModV2.ConnectTapInfo;
 WITH REPLY SYNTAX AtmMIBModV2.ConnectTapReply;
REGISTERED AS {atmfM4Action connectTap(11)};

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

This action will connect one TAP-PP or one TAP-VC to a resource to be tested. Each invocation will allow monitoring one direction of a cell stream. To monitor both sides of a bi-directional cell stream requires the connection of two TAP objects The action request contains the name of the resource to be monitored. For physical port mirroring (PP) or virtual connection access (VC), this parameter contains a pointer to the tcAdaptor object that represents the cell stream to be monitored. For virtual connection access, this parameter will also identify the VPI value, and if necessary, the VCI value of the connection under test. The test access path to be used is identified in the action request by a pointer to a tapPP or tapVC object. If a value is not supplied, the ATM NE should select an available TAP of the appropriate type. The name of the selected tapPP or tapVC object shall be returned in the action reply. If the requested TAP is not available or if all TAPs of the requested type are unavailable, the action reply should indicate TAP not available. The value of the accessMode attribute of the TAP object is also defined in the action request.

Sources for this description

ATM Forum M4 official CMIP specifications

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1ATM Forum M4 official CMIP specifications1 record · 1 source

Description 1

connectTap · unspecifiedATM Forum M4 official CMIP specifications1 source

Status in source: unspecified.

Names: connectTap

Technical details
{
  "gdmo_kind": "ACTION",
  "definition": [
    "connectTap",
    "ACTION",
    "BEHAVIOUR",
    "connectTapBeh",
    "BEHAVIOUR",
    "DEFINED",
    "AS",
    [
      "literal",
      "22205468697320616374696f6e2077696c6c20636f6e6e656374206f6e65205441502d5050206f72206f6e65205441502d564320746f2061207265736f7572636520746f206265207465737465642e204561636820696e766f636174696f6e2077696c6c20616c6c6f770a20206d6f6e69746f72696e67206f6e6520646972656374696f6e206f6620612063656c6c2073747265616d2e20546f206d6f6e69746f7220626f7468207369646573206f6620612062692d646972656374696f6e616c2063656c6c2073747265616d207265717569726573207468650a2020636f6e6e656374696f6e206f662074776f20544150206f626a656374732054686520616374696f6e207265717565737420636f6e7461696e7320746865206e616d65206f6620746865207265736f7572636520746f206265206d6f6e69746f7265642e20466f7220706879736963616c0a2020706f7274206d6972726f72696e672028505029206f72207669727475616c20636f6e6e656374696f6e2061636365737320285643292c207468697320706172616d6574657220636f6e7461696e73206120706f696e74657220746f2074686520746341646170746f72206f626a6563740a20207468617420726570726573656e7473207468652063656c6c2073747265616d20746f206265206d6f6e69746f7265642e20466f72207669727475616c20636f6e6e656374696f6e206163636573732c207468697320706172616d657465722077696c6c20616c736f206964656e74696679207468650a20205650492076616c75652c20616e64206966206e65636573736172792c20746865205643492076616c7565206f662074686520636f6e6e656374696f6e20756e64657220746573742e20546865207465737420616363657373207061746820746f20626520757365642069730a20206964656e74696669656420696e2074686520616374696f6e2072657175657374206279206120706f696e74657220746f2061207461705050206f72207461705643206f626a6563742e20496620612076616c7565206973206e6f7420737570706c6965642c207468652041544d204e450a202073686f756c642073656c65637420616e20617661696c61626c6520544150206f662074686520617070726f70726961746520747970652e20546865206e616d65206f66207468652073656c6563746564207461705050206f72207461705643206f626a656374207368616c6c2062650a202072657475726e656420696e2074686520616374696f6e207265706c792e204966207468652072657175657374656420544150206973206e6f7420617661696c61626c65206f7220696620616c6c2054415073206f6620746865207265717565737465642074797065206172650a2020756e617661696c61626c652c2074686520616374696f6e207265706c792073686f756c6420696e64696361746520544150206e6f7420617661696c61626c652e205468652076616c7565206f6620746865206163636573734d6f646520617474726962757465206f6620746865205441500a20206f626a65637420697320616c736f20646566696e656420696e2074686520616374696f6e20726571756573742e22"
    ],
    ";",
    ";",
    "MODE",
    "CONFIRMED",
    ";",
    "WITH",
    "INFORMATION",
    "SYNTAX",
    "AtmMIBModV2",
    ".",
    "ConnectTapInfo",
    ";",
    "WITH",
    "REPLY",
    "SYNTAX",
    "AtmMIBModV2",
    ".",
    "ConnectTapReply",
    ";",
    "REGISTERED",
    "AS",
    "{",
    "atmfM4Action",
    "connectTap",
    "(",
    "11",
    ")",
    "}",
    ";"
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.353)

McCloghrie Keith

Siblings (20)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.353.5.1.1.0.9.1 addTpsToMultipointBridge00
1.3.6.1.4.1.353.5.1.1.0.9.2 connect00
1.3.6.1.4.1.353.5.1.1.0.9.3 connectMultipointBridge00
1.3.6.1.4.1.353.5.1.1.0.9.4 disconnect00
1.3.6.1.4.1.353.5.1.1.0.9.5 disconnectMultipointBridge00
1.3.6.1.4.1.353.5.1.1.0.9.6 loopbackOAMCell00
1.3.6.1.4.1.353.5.1.1.0.9.7 removeTpsFromMultipointBridge00
1.3.6.1.4.1.353.5.1.1.0.9.8 addTerminationPoint00
1.3.6.1.4.1.353.5.1.1.0.9.9 removeTerminationPoint00
1.3.6.1.4.1.353.5.1.1.0.9.10 changeAccessMode00
1.3.6.1.4.1.353.5.1.1.0.9.12 disconnectTap00
1.3.6.1.4.1.353.5.1.1.0.9.13 abortDiagnostic00
1.3.6.1.4.1.353.5.1.1.0.9.14 addTpsToMultipointBridgeR100
1.3.6.1.4.1.353.5.1.1.0.9.15 cancelReset00
1.3.6.1.4.1.353.5.1.1.0.9.16 connectMultipointBridgeR100
1.3.6.1.4.1.353.5.1.1.0.9.17 connectR100
1.3.6.1.4.1.353.5.1.1.0.9.18 invokeDiagnosticControl00
1.3.6.1.4.1.353.5.1.1.0.9.19 reportDiagnosticStatus00
1.3.6.1.4.1.353.5.1.1.0.9.20 reset00
1.3.6.1.4.1.353.5.1.1.0.9.21 restartSvcs00