OID reference
1.3.6.1.4.1.89.35.10.1.9
The values differ according to the alert type. For SNMP traps, the value is the name of the device that generated them. For APSolute Vision auditing events, which have device context (configuration, monitoring), the value is the name of the device to which the event relates. When the alert is generated by the APSolute…
Identification
{1 3 6 1 4 1 89 35 10 1 9}
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.
alertSourceDeviceName OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS current
DESCRIPTION
"The values differ according to the alert type. For SNMP traps, the value is the name of the device that generated them.
For APSolute Vision auditing events, which have device context (configuration, monitoring), the value is the name of the device to which the event relates.
When the alert is generated by the APSolute Vision server, no device name is displayed."
DEFVAL { "" }
::= { alerts 9 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The values differ according to the alert type. For SNMP traps, the value is the name of the device that generated them. For APSolute Vision auditing events, which have device context (configuration, monitoring), the value is the name of the device to which the event relates. When the alert is generated by the APSolute Vision server, no device name is displayed.
Radware MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: alertSourceDeviceName
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"alertSourceDeviceName",
"OBJECT-TYPE",
"SYNTAX",
"DisplayString",
"ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The values differ according to the alert type. For SNMP traps, the value is the name of the device that generated them. For APSolute Vision auditing events, which have device context (configuration, monitoring), the value is the name of the device to which the event relates. When the alert is generated by the APSolute Vision server, no device name is displayed.\"",
"DEFVAL",
"{",
[
"literal",
"2222"
],
"}",
"::=",
"{",
"alerts",
"9",
"}"
],
"syntax_tree": [
[
"row",
"DisplayString"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The values differ according to the alert type. For SNMP traps, the value is the name of the device that generated them. For APSolute Vision auditing events, which have device context (configuration, monitoring), the value is the name of the device to which the event relates. When the alert is generated by the APSolute Vision server, no device name is displayed."
],
null,
null,
null,
[
"DEFVAL",
"\"\""
]
]
}Vendor MIB copy from the Observium Community archive. Radware support.
Module: VISION-MIB
See published definition above
{'RFC-1215': ['TRAP-TYPE'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'Counter64'], 'RADWARE-MIB': ['rndApplications'], 'RFC1213-MIB': ['DisplayString'], 'SNMPv2-CONF': ['OBJECT-GROUP']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.89.35.10.1.0 | 0 | 1 | 1 | |
| 1.3.6.1.4.1.89.35.10.1.1 | alertId | 0 | 0 | |
| 1.3.6.1.4.1.89.35.10.1.2 | alertMessage | 0 | 0 | |
| 1.3.6.1.4.1.89.35.10.1.3 | alertUser | 0 | 0 | |
| 1.3.6.1.4.1.89.35.10.1.4 | alertSeverity | 0 | 0 | |
| 1.3.6.1.4.1.89.35.10.1.5 | alertModule | 0 | 0 | |
| 1.3.6.1.4.1.89.35.10.1.6 | alertCategory | 0 | 0 | |
| 1.3.6.1.4.1.89.35.10.1.7 | alertTimeString | 0 | 0 | |
| 1.3.6.1.4.1.89.35.10.1.8 | alertTimeMillis | 0 | 0 | |
| 1.3.6.1.4.1.89.35.10.1.10 | alertSourceDeviceIp | 0 | 0 |