Reference record for OID 1.3.6.1.4.1.9.10.18.1.1.33
- Parent
- 1.3.6.1.4.1.9.10.18.1.1 (atmAcctngDataObjects)
- Node code
- 33
- Node name
- atmAcctngRecordCrc16
- Numeric OID
- 1.3.6.1.4.1.9.10.18.1.1.33
- URN notation
- urn:oid:1.3.6.1.4.1.9.10.18.1.1.33
- Type
- OBJECT-TYPE
- ASN.1 notation
-
{1 3 6 1 4 1 9 10 18 1 1 33}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoExperiment(10) atmAccountingInformationMIB(18) atmAcctngMIBObjects(1) atmAcctngDataObjects(1) atmAcctngRecordCrc16(33)}
- OID-IRI notation
- /1/3/6/1/4/1/9/10/18/1/1/33
- /ISO/Identified-Organization/6/1/4/1/9/10/18/1/1/33
- /ISO/3/6/1/4/1/9/10/18/1/1/33
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/identified-organization/dod/internet/private/vendor-objects/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/org/dod/internet/private/enterprise/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/org/dod/internet/private/enterprises/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/org/dod/internet/private/ldap-enterprise/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/org/dod/internet/private/vendor-objects/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/iso-identified-organization/dod/internet/private/vendor-objects/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/iso-organization/dod/internet/private/enterprise/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/iso-organization/dod/internet/private/enterprises/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/iso-organization/dod/internet/private/ldap-enterprise/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
- /iso/iso-organization/dod/internet/private/vendor-objects/cisco/ciscoExperiment/atmAccountingInformationMIB/atmAcctngMIBObjects/atmAcctngDataObjects/atmAcctngRecordCrc16
Descriptions may differ between sources. The primary description is shown first.
Primary description: Cisco
The value of the CRC-16 checksum (as defined by ISO 3309
(HDLC) and/or ITU X.25) calculated over the accounting
record containing this object.
While the mechanism for calculating/encoding the checksum
value is specific to the method of encoding the accounting
record, an accounting record containing this object is
typically generated by initializing the value of this object
to the all-zeros string ('0000'H), with the location of
these zeros being saved. After generating the record, the
checksum is calculated over the whole connection record and
then the all-zeros value is overwritten (at the saved
location) by the calculated value of the checksum.
(HDLC) and/or ITU X.25) calculated over the accounting
record containing this object.
While the mechanism for calculating/encoding the checksum
value is specific to the method of encoding the accounting
record, an accounting record containing this object is
typically generated by initializing the value of this object
to the all-zeros string ('0000'H), with the location of
these zeros being saved. After generating the record, the
checksum is calculated over the whole connection record and
then the all-zeros value is overwritten (at the saved
location) by the calculated value of the checksum.
Source file: Download ATM-ACCOUNTING-INFORMATION-MIB.my · Publisher's file SHA-256: c7115c441d39eec92e61bf5d85674bf55cbf84c027e11ef5df6d6bb0ea8d9dbc
Alternative description: Cisco SMIv1
The value of the CRC-16 checksum (as defined by ISO 3309
(HDLC) and/or ITU X.25) calculated over the accounting
record containing this object.
While the mechanism for calculating/encoding the checksum
value is specific to the method of encoding the accounting
record, an accounting record containing this object is
typically generated by initializing the value of this object
to the all-zeros string ('0000'H), with the location of
these zeros being saved. After generating the record, the
checksum is calculated over the whole connection record and
then the all-zeros value is overwritten (at the saved
location) by the calculated value of the checksum.
(HDLC) and/or ITU X.25) calculated over the accounting
record containing this object.
While the mechanism for calculating/encoding the checksum
value is specific to the method of encoding the accounting
record, an accounting record containing this object is
typically generated by initializing the value of this object
to the all-zeros string ('0000'H), with the location of
these zeros being saved. After generating the record, the
checksum is calculated over the whole connection record and
then the all-zeros value is overwritten (at the saved
location) by the calculated value of the checksum.
Source file: Download ATM-ACCOUNTING-INFORMATION-MIB-V1SMI.my · Publisher's file SHA-256: a4931aa1523046685a4e089396b5f982775ec2eeccc67a2db0ae89658e64295c
Source file: Download cisco/ATM-ACCOUNTING-INFORMATION-MIB-V1SMI.my.txt SHA-256: 70bb3572eac0596a481904b61896ef08d633c44c7990e006edb29922b67a94d1
Alternative description: MIBdepot
The value of the CRC-16 checksum (as defined by ISO 3309
(HDLC) and/or ITU X.25) calculated over the accounting
record containing this object.
While the mechanism for calculating/encoding the checksum
value is specific to the method of encoding the accounting
record, an accounting record containing this object is
typically generated by initializing the value of this object
to the all-zeros string ('0000'H), with the location of
these zeros being saved. After generating the record, the
checksum is calculated over the whole connection record and
then the all-zeros value is overwritten (at the saved
location) by the calculated value of the checksum.
(HDLC) and/or ITU X.25) calculated over the accounting
record containing this object.
While the mechanism for calculating/encoding the checksum
value is specific to the method of encoding the accounting
record, an accounting record containing this object is
typically generated by initializing the value of this object
to the all-zeros string ('0000'H), with the location of
these zeros being saved. After generating the record, the
checksum is calculated over the whole connection record and
then the all-zeros value is overwritten (at the saved
location) by the calculated value of the checksum.
Source file: Download cisco/ATM-ACCOUNTING-INFORMATION-MIB.my.txt SHA-256: e15ed8683d3b3b5381e6442d609deafe167c402fa24004d561a2b171f0843173
Information from Cisco SMIv1
atmAcctngRecordCrc16 OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(2))
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The value of the CRC-16 checksum (as defined by ISO 3309
(HDLC) and/or ITU X.25) calculated over the accounting
record containing this object.
While the mechanism for calculating/encoding the checksum
value is specific to the method of encoding the accounting
record, an accounting record containing this object is
typically generated by initializing the value of this object
to the all-zeros string ('0000'H), with the location of
these zeros being saved. After generating the record, the
checksum is calculated over the whole connection record and
then the all-zeros value is overwritten (at the saved
location) by the calculated value of the checksum."
::= { atmAcctngDataObjects 33 }
Information from OID Repository
Child arc 0 is used to translate between SNMPv1 and SNMPv2 notification parameters as explained in IETF RFC 2576, section 3.
Information from MIBdepot
atmAcctngRecordCrc16 OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(2))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of the CRC-16 checksum (as defined by ISO 3309
(HDLC) and/or ITU X.25) calculated over the accounting
record containing this object.
While the mechanism for calculating/encoding the checksum
value is specific to the method of encoding the accounting
record, an accounting record containing this object is
typically generated by initializing the value of this object
to the all-zeros string ('0000'H), with the location of
these zeros being saved. After generating the record, the
checksum is calculated over the whole connection record and
then the all-zeros value is overwritten (at the saved
location) by the calculated value of the checksum."
::= { atmAcctngDataObjects 33 }
Information from Cisco
atmAcctngRecordCrc16 OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(2))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of the CRC-16 checksum (as defined by ISO 3309
(HDLC) and/or ITU X.25) calculated over the accounting
record containing this object.
While the mechanism for calculating/encoding the checksum
value is specific to the method of encoding the accounting
record, an accounting record containing this object is
typically generated by initializing the value of this object
to the all-zeros string ('0000'H), with the location of
these zeros being saved. After generating the record, the
checksum is calculated over the whole connection record and
then the all-zeros value is overwritten (at the saved
location) by the calculated value of the checksum."
::= { atmAcctngDataObjects 33 }
First Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)
Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)
Direct children (1)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.10.18.1.1.33.0 | atmAcctngRecordCrc16 | 0 | 0 |
Siblings (34)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.10.18.1.1.1 | atmAcctngConnectionType | 1 | 1 | The type of connection. |
| 1.3.6.1.4.1.9.10.18.1.1.2 | atmAcctngCastType | 1 | 1 | An indication of whether the connection is point-to-point or point-to-multipoint. |
| 1.3.6.1.4.1.9.10.18.1.1.3 | atmAcctngIfName | 1 | 1 | A textual name for the interface on which the data for the connection was collected. If the local SNMP agent supports the object… |
| 1.3.6.1.4.1.9.10.18.1.1.4 | atmAcctngIfAlias | 1 | 1 | The 'alias' name for the interface as specified by a network manager, e.g., via a management set operation to modify the relevant… |
| 1.3.6.1.4.1.9.10.18.1.1.5 | atmAcctngVpi | 1 | 1 | The VPI used for the connection. |
| 1.3.6.1.4.1.9.10.18.1.1.6 | atmAcctngVci | 1 | 1 | The VCI used for the connection. |
| 1.3.6.1.4.1.9.10.18.1.1.7 | atmAcctngCallingParty | 1 | 1 | The connection's calling party. If unknown (e.g., for a PVC), then the value of this object is the zero-length string. |
| 1.3.6.1.4.1.9.10.18.1.1.8 | atmAcctngCalledParty | 1 | 1 | The connection's called party. If unknown (e.g., for a PVC), then the value of this object is the zero-length string. |
| 1.3.6.1.4.1.9.10.18.1.1.9 | atmAcctngCallReference | 1 | 1 | The connection's call reference value (e.g., from Q.2931). If unknown (e.g., for a PVC), then the value of this object is the zer… |
| 1.3.6.1.4.1.9.10.18.1.1.10 | atmAcctngStartTime | 1 | 1 | The time when the connection was established. |
| 1.3.6.1.4.1.9.10.18.1.1.11 | atmAcctngCollectionTime | 1 | 1 | The time at which the data in this record was collected. |
| 1.3.6.1.4.1.9.10.18.1.1.12 | atmAcctngCollectMode | 1 | 1 | The reason why this connection data was collected. |
| 1.3.6.1.4.1.9.10.18.1.1.13 | atmAcctngReleaseCause | 1 | 1 | If the connection data was collected because of the release of an SVC, then this is the cause code in the Release message for the… |
| 1.3.6.1.4.1.9.10.18.1.1.14 | atmAcctngServiceCategory | 1 | 1 | The connection's service category. |
| 1.3.6.1.4.1.9.10.18.1.1.15 | atmAcctngTransmittedCells | 1 | 1 | The number of cells, including OAM cells, transmitted by this switch on this connection. |
| 1.3.6.1.4.1.9.10.18.1.1.16 | atmAcctngTransmittedClp0Cells | 1 | 1 | The number of cells with CLP=0, including OAM cells, transmitted by this switch on this connection. |
| 1.3.6.1.4.1.9.10.18.1.1.17 | atmAcctngReceivedCells | 1 | 1 | The number of cells, including OAM cells, received by this switch on this connection. |
| 1.3.6.1.4.1.9.10.18.1.1.18 | atmAcctngReceivedClp0Cells | 1 | 1 | The number of cells with CLP=0, including OAM cells, received by this switch on this connection. |
| 1.3.6.1.4.1.9.10.18.1.1.19 | atmAcctngTransmitTrafficDescriptorType | 1 | 1 | The traffic descriptor type (as defined in RFC 1695 and its successors) in the direction in which the switch transmits cells on t… |
| 1.3.6.1.4.1.9.10.18.1.1.20 | atmAcctngTransmitTrafficDescriptorParam1 | 1 | 1 | The first traffic descriptor parameter in the direction in which this switch transmits cells on this connection. Interpretation o… |
| 1.3.6.1.4.1.9.10.18.1.1.21 | atmAcctngTransmitTrafficDescriptorParam2 | 1 | 1 | The second traffic descriptor parameter in the direction in which this switch transmits cells on this connection. Interpretation … |
| 1.3.6.1.4.1.9.10.18.1.1.22 | atmAcctngTransmitTrafficDescriptorParam3 | 1 | 1 | The third traffic descriptor parameter in the direction in which this switch transmits cells on this connection. Interpretation o… |
| 1.3.6.1.4.1.9.10.18.1.1.23 | atmAcctngTransmitTrafficDescriptorParam4 | 1 | 1 | The fourth traffic descriptor parameter in the direction in which this switch transmits cells on this connection. Interpretation … |
| 1.3.6.1.4.1.9.10.18.1.1.24 | atmAcctngTransmitTrafficDescriptorParam5 | 1 | 1 | The fifth traffic descriptor parameter in the direction in which this switch transmits cells on this connection. Interpretation o… |
| 1.3.6.1.4.1.9.10.18.1.1.25 | atmAcctngReceiveTrafficDescriptorType | 1 | 1 | The traffic descriptor type (as defined in RFC 1695 and its successors) in the direction in which this switch receives cells on t… |
| 1.3.6.1.4.1.9.10.18.1.1.26 | atmAcctngReceiveTrafficDescriptorParam1 | 1 | 1 | The first traffic descriptor parameter in the direction in which this switch receives cells on this connection. Interpretation of… |
| 1.3.6.1.4.1.9.10.18.1.1.27 | atmAcctngReceiveTrafficDescriptorParam2 | 1 | 1 | The second traffic descriptor parameter in the direction in which this switch receives cells on this connection. Interpretation o… |
| 1.3.6.1.4.1.9.10.18.1.1.28 | atmAcctngReceiveTrafficDescriptorParam3 | 1 | 1 | The third traffic descriptor parameter in the direction in which this switch receives cells on this connection. Interpretation of… |
| 1.3.6.1.4.1.9.10.18.1.1.29 | atmAcctngReceiveTrafficDescriptorParam4 | 1 | 1 | The fourth traffic descriptor parameter in the direction in which this switch receives cells on this connection. Interpretation o… |
| 1.3.6.1.4.1.9.10.18.1.1.30 | atmAcctngReceiveTrafficDescriptorParam5 | 1 | 1 | The fifth traffic descriptor parameter in the direction in which this switch receives cells on this connection. Interpretation of… |
| 1.3.6.1.4.1.9.10.18.1.1.31 | atmAcctngCallingPartySubAddress | 1 | 1 | The connection's calling party sub-address. If the connection has no calling party sub-address, or it's value is unknown, then t… |
| 1.3.6.1.4.1.9.10.18.1.1.32 | atmAcctngCalledPartySubAddress | 1 | 1 | The connection's called party sub-address. If the connection has no called party sub-address, or it's value is unknown, then the… |
| 1.3.6.1.4.1.9.10.18.1.1.34 | atmAcctngTransmittedPeakCells | 1 | 1 | The number of cells transmitted on the connection within the peak 5-second sub-interval, where the peak sub-interval is the one h… |
| 1.3.6.1.4.1.9.10.18.1.1.35 | atmAcctngReceivedPeakCells | 1 | 1 | The number of cells received on the connection within the peak 5-second sub-interval, where the peak sub-interval is the one havi… |