The corresponding bit is set to 1 to start the operation. The various bit positions are: BIT 0: clear call detail records BIT 1: clear H248 statistics
Sources for this description
Zyxel MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.890.1.5.13.5.14.6.1
The corresponding bit is set to 1 to start the operation. The various bit positions are: BIT 0: clear call detail records BIT 1: clear H248 statistics
Identification
{1 3 6 1 4 1 890 1 5 13 5 14 6 1}
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.890.1.5.13.5.14.6.1.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.
voipClearOps OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The corresponding bit is set to 1 to start the operation.
The various bit positions are:
BIT 0: clear call detail records
BIT 1: clear H248 statistics"
::= { voipClear 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The corresponding bit is set to 1 to start the operation. The various bit positions are: BIT 0: clear call detail records BIT 1: clear H248 statistics
Zyxel MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: voipClearOps
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"voipClearOps",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The corresponding bit is set to 1 to start the operation. The various bit positions are: BIT 0: clear call detail records BIT 1: clear H248 statistics\"",
"::=",
"{",
"voipClear",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The corresponding bit is set to 1 to start the operation. The various bit positions are: BIT 0: clear call detail records BIT 1: clear H248 statistics"
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive. Zyxel support.
Module: ZYXEL-IES5000-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['RowStatus', 'TEXTUAL-CONVENTION'], 'BRIDGE-MIB': ['MacAddress', 'Timeout', 'BridgeId', 'dot1dBasePort'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'Counter64', 'Counter32', 'Gauge32', 'Integer32', 'Unsigned32', 'IpAddress', 'NOTIFICATION-TYPE'], 'RFC1155-SMI': ['enterprises'], 'RFC1213-MIB': ['DisplayString', 'PhysAddress', 'ifIndex'], 'P-BRIDGE-MIB': ['dot1dTrafficClass', 'EnabledStatus'], 'Q-BRIDGE-MIB': ['VlanIndex', 'PortList', 'dot1qVlanIndex'], 'VDSL-LINE-MIB': ['vdslPhysSide', 'vdslChanCurrTxRate', 'vdslLineConfProfileName', 'vdslLineAlarmConfProfileName'], 'VDSL2-LINE-MIB': ['xdsl2PMChHist15MUnit', 'xdsl2PMChHist15MInterval', 'xdsl2PMLHist1DUnit', 'xdsl2PMLHist1DInterval', 'xdsl2PMLHist15MUnit', 'xdsl2PMLHist15MInterval', 'xdsl2PMChHist1DUnit', 'xdsl2PMChHist1DInterval', 'xdsl2PMLCurrUnit', 'xdsl2LConfProfProfileName', 'xdsl2ChConfProfProfileName', 'xdsl2LineAlarmConfProfileName', 'xdsl2LineBand', 'xdsl2LConfTempTemplateName', 'xdsl2LAlarmConfTempTemplateName', 'xdsl2ChAlarmConfProfileName', 'xdsl2SCStatusDirection', 'xdsl2SCStatusBand'], 'IEEE8021-CFM-MIB': ['dot1agCfmMdIndex', 'dot1agCfmMaIndex', 'dot1agCfmMepIdentifier', 'dot1agCfmMdMdLevel', 'dot1agCfmVlanPrimaryVid', 'dot1agCfmMepIdentifier'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}Related source files and packages:
Same file in Observium Community.
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.890.1.5.13.5.14.6.2 | voipClearH248TargetInterface | 0 | 0 |