The time used to recognize if CDR message is valid. Once the CDR message is valid, it will be logged into CDR.
Sources for this description
ZTE MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.3902.1015.30.1.3.11
The time used to recognize if CDR message is valid. Once the CDR message is valid, it will be logged into CDR.
Identification
{1 3 6 1 4 1 3902 1015 30 1 3 11}
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.3902.1015.30.1.3.11.0
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
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.
zxAnMcastCdrRecognizeTime OBJECT-TYPE
SYNTAX Integer32
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The time used to recognize if CDR message is valid.
Once the CDR message is valid, it will be logged into CDR."
DEFVAL { 20 }
::= { zxAnCtrlMcastCdr 11 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The time used to recognize if CDR message is valid. Once the CDR message is valid, it will be logged into CDR.
ZTE MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: zxAnMcastCdrRecognizeTime
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"zxAnMcastCdrRecognizeTime",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"UNITS",
[
"literal",
"227365636f6e647322"
],
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The time used to recognize if CDR message is valid. Once the CDR message is valid, it will be logged into CDR.\"",
"DEFVAL",
"{",
"20",
"}",
"::=",
"{",
"zxAnCtrlMcastCdr",
"11",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32"
],
[
"UNITS",
"seconds"
],
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The time used to recognize if CDR message is valid. Once the CDR message is valid, it will be logged into CDR."
],
null,
null,
null,
[
"DEFVAL",
20
]
]
}Vendor MIB copy from the Observium Community archive. ZTE support.
Module: ZTE-AN-CTRL-MULTICAST-MIB
See published definition above
{'SNMPv2-TC': ['DisplayString', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'IpAddress', 'Counter32', 'Gauge32', 'Integer32'], 'ZTE-AN-TC-MIB': ['ZxAnIfindex', 'ZxAnPortList', 'ZxAnIdList', 'zxAn'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.3902.1015.30.1.3.1 | zxAnIptvCdrEnable | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.30.1.3.2 | zxAnIptvCdrManualSendAction | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.30.1.3.3 | zxAnMcastCdrServerIP | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.30.1.3.4 | zxAnIptvCdrAutoSendPeriod | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.30.1.3.5 | zxAnIptvCdrGenerationMode | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.30.1.3.6 | zxAnIptvCdrMaxRecordNumer | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.30.1.3.7 | zxAnIptvCdrCurrentRecordNumber | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.30.1.3.8 | zxAnIptvCdrOnlineMsgGenPeriod | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.30.1.3.9 | zxAnMcastCdrSizeThresh | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.30.1.3.10 | zxAnMcastIpv6CdrServerIP | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.30.1.3.12 | zxAnMcastCdrAutoSendSizeThresh | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.30.1.3.50 | zxAnMcastCdrServerTable | 1 | 8 |