Type of message being counted. These map directly to the COPS opcodes in RFC 2748.
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.4998.1.1.115.1.1.65.1.3
Type of message being counted. These map directly to the COPS opcodes in RFC 2748.
Identification
{1 3 6 1 4 1 4998 1 1 115 1 1 65 1 3}
Notes below names come from selected MIB definitions.
| Value | Name and source notes |
|---|---|
| 0 | tcpCxt indicates a TCP layer connection |
| 1 | copsReq |
| 2 | copsDec |
| 3 | copsRpt |
| 4 | copsDrq |
| 5 | copsSsq |
| 6 | copsOpn |
| 7 | copsCat |
| 8 | copsCC |
| 9 | copsKa |
| 10 | copsSsc |
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.
In CADANT-CMTS-PACKETCABLE-MIB, the row index consists of these components in order:
cadPCCopsServer (IpAddress): four numeric subidentifiers, one per IPv4 address octet.cadPCCopsDirection (INTEGER): one numeric subidentifier for the non-negative value.cadPCCopsOpcode (INTEGER): one numeric subidentifier for the non-negative value.An instance has the form .1.3.6.1.4.1.4998.1.1.115.1.1.65.1.3.<cadPCCopsServer: four octets>.<cadPCCopsDirection>.<cadPCCopsOpcode>. Use values present on the device and permitted by its MIB. Other definitions can differ.
A query example is omitted because the source variants do not establish compatible read access.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
cadPCCopsOpcode OBJECT-TYPE
SYNTAX INTEGER {
tcpCxt(0), -- indicates a TCP layer connection
copsReq(1),
copsDec(2),
copsRpt(3),
copsDrq(4),
copsSsq(5),
copsOpn(6),
copsCat(7),
copsCC(8),
copsKa(9),
copsSsc(10)
}
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Type of message being counted. These map directly to the COPS
opcodes in RFC 2748."
REFERENCE "'The COPS (Common Open Policy Service) Protocol: RFC2748';
'C4 Product Specification Agreement: PacketCable Deployment Tools
on the C4 CMTS' requirement 2.3.1.2-110"
::= { cadPCCopsCountEntry 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Type of message being counted. These map directly to the COPS opcodes in RFC 2748.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: cadPCCopsOpcode
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"cadPCCopsOpcode",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"tcpCxt",
"(",
"0",
")",
",",
"copsReq",
"(",
"1",
")",
",",
"copsDec",
"(",
"2",
")",
",",
"copsRpt",
"(",
"3",
")",
",",
"copsDrq",
"(",
"4",
")",
",",
"copsSsq",
"(",
"5",
")",
",",
"copsOpn",
"(",
"6",
")",
",",
"copsCat",
"(",
"7",
")",
",",
"copsCC",
"(",
"8",
")",
",",
"copsKa",
"(",
"9",
")",
",",
"copsSsc",
"(",
"10",
")",
"}",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"Type of message being counted. These map directly to the COPS opcodes in RFC 2748.\"",
"REFERENCE",
"\"'The COPS (Common Open Policy Service) Protocol: RFC2748'; 'C4 Product Specification Agreement: PacketCable Deployment Tools on the C4 CMTS' requirement 2.3.1.2-110\"",
"::=",
"{",
"cadPCCopsCountEntry",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"tcpCxt",
0
],
[
"copsReq",
1
],
[
"copsDec",
2
],
[
"copsRpt",
3
],
[
"copsDrq",
4
],
[
"copsSsq",
5
],
[
"copsOpn",
6
],
[
"copsCat",
7
],
[
"copsCC",
8
],
[
"copsKa",
9
],
[
"copsSsc",
10
]
]
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Type of message being counted. These map directly to the COPS opcodes in RFC 2748."
],
[
"REFERENCE",
"'The COPS (Common Open Policy Service) Protocol: RFC2748'; 'C4 Product Specification Agreement: PacketCable Deployment Tools on the C4 CMTS' requirement 2.3.1.2-110"
],
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: CADANT-CMTS-PACKETCABLE-MIB
See published definition above
{'IF-MIB': ['ifIndex', 'InterfaceIndex'], 'CADANT-TC': ['CardId', 'AdminState'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'TruthValue', 'DisplayString', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'IpAddress', 'Unsigned32', 'Counter32'], 'DOCS-QOS3-MIB': ['IfDirection'], 'CADANT-PRODUCTS-MIB': ['cadCable'], 'CADANT-CMTS-PROCESS-MIB': ['cadOvSysCpuStatus'], 'CADANT-CMTS-DOWNCHANNEL-MIB': ['cadIfCmtsCardNumber']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.4998.1.1.115.1.1.65.1.1 | cadPCCopsServer | 0 | 0 | |
| 1.3.6.1.4.1.4998.1.1.115.1.1.65.1.2 | cadPCCopsDirection | 0 | 0 | |
| 1.3.6.1.4.1.4998.1.1.115.1.1.65.1.4 | cadPCCopsCount | 0 | 0 |