Domain authentication alert has been cleared
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.17163.1.1.4.0.1069
Domain authentication alert has been cleared
Identification
{1 3 6 1 4 1 17163 1 1 4 0 1069}
The displayed source records contain one distinct definition. Compare its source records.
smbAlertClear NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"Domain authentication alert has been cleared"
::= { alarmsPrefix 1069 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Domain authentication alert has been cleared
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: smbAlertClear
{
"smi_kind": "NOTIFICATION-TYPE",
"definition": [
"smbAlertClear",
"NOTIFICATION-TYPE",
"STATUS",
"current",
"DESCRIPTION",
"\"Domain authentication alert has been cleared\"",
"::=",
"{",
"alarmsPrefix",
"1069",
"}"
],
"syntax_tree": [
[],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Domain authentication alert has been cleared"
],
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: STEELHEAD-MIB
See published definition above
{'RBT-MIB': ['products'], 'SNMPv2-TC': ['DateAndTime'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'Unsigned32', 'TimeTicks', 'IpAddress', 'Counter32', 'Counter64']}Related source files and packages:
Same file in Observium Community.
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.17163.1.1.4.0.1031 | cfKeepaliveTimeoutClear | 0 | 0 | Keepalive restored after a prior timeout with the specified neighbor |
| 1.3.6.1.4.1.17163.1.1.4.0.1032 | cfAckTimeoutClear | 0 | 0 | Ack restored after a prior timeout with the specified neighbor |
| 1.3.6.1.4.1.17163.1.1.4.0.1033 | cfReadInfoTimeoutClear | 0 | 0 | Successfully read info from the specified neighbor after a prior timeout |
| 1.3.6.1.4.1.17163.1.1.4.0.1034 | cfLatencyExceededClear | 0 | 0 | Connection forwarding latency with the specified neighbor is back within the threshold |
| 1.3.6.1.4.1.17163.1.1.4.0.1035 | sslPeeringSCEPAutoReenrollClear | 0 | 0 | Automatic re-enrollment of SSL peering certificate is OK or is disabled |
| 1.3.6.1.4.1.17163.1.1.4.0.1036 | crlClear | 0 | 0 | crl polling is running normally |
| 1.3.6.1.4.1.17163.1.1.4.0.1037 | datastoreSyncFailureClear | 0 | 0 | Data store sync restored |
| 1.3.6.1.4.1.17163.1.1.4.0.1040 | secureVaultClear | 0 | 0 | Secure vault has been unlocked and is healthy |
| 1.3.6.1.4.1.17163.1.1.4.0.1045 | diskErrorClear | 0 | 0 | All disks are back online |
| 1.3.6.1.4.1.17163.1.1.4.0.1052 | admissionCpuErrorClear | 0 | 0 | Admission control CPU alarm has been cleared, and the service is running normally |
| 1.3.6.1.4.1.17163.1.1.4.0.1053 | admissionTcpErrorClear | 0 | 0 | Admission control TCP alarm has been cleared, and the service is running normally |
| 1.3.6.1.4.1.17163.1.1.4.0.1054 | systemDiskFullErrorClear | 0 | 0 | The system partitions are below usage thresholds |
| 1.3.6.1.4.1.17163.1.1.4.0.1055 | domainJoinErrorClear | 0 | 0 | A domain error on the appliance has been cleared |
| 1.3.6.1.4.1.17163.1.1.4.0.1056 | certsExpiringErrorClear | 0 | 0 | There are no expiring certificates |
| 1.3.6.1.4.1.17163.1.1.4.0.1057 | licenseErrorClear | 0 | 0 | The main Steelhead license error has been cleared |
| 1.3.6.1.4.1.17163.1.1.4.0.1058 | hardwareErrorClear | 0 | 0 | Hardware Error has been cleared |
| 1.3.6.1.4.1.17163.1.1.4.0.1059 | sysdetailErrorClear | 0 | 0 | Overall status of System Detail Report is back to OK |
| 1.3.6.1.4.1.17163.1.1.4.0.1060 | admissionMapiErrorClear | 0 | 0 | System will resume to optimize new MAPI connections since connection count has fallen below the threshold |
| 1.3.6.1.4.1.17163.1.1.4.0.1061 | neighborIncompatibilityClear | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.1062 | flashErrorClear | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.1063 | lanWanLoopClear | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.1064 | optimizationServiceStatusClear | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.1065 | upgradeFailureClear | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.1068 | clusterDisconnectedSHAlertClear | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.1070 | linkDuplexClear | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.1071 | linkIoErrorsClear | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.1074 | clusterIpv6IncompatiblePeerClear | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.1077 | pathSelectionPathDownClear | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.1080 | clusterNeighborIncompatibleClear | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.1081 | pathSelectionPathProbingErrorClear | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.20001 | rspGeneralError | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.20002 | rspServiceError | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.21001 | rspGeneralClear | 0 | 0 | |
| 1.3.6.1.4.1.17163.1.1.4.0.21002 | rspServiceClear | 0 | 0 |