alertSourceDeviceName

VISION-MIB · .1.3.6.1.4.1.89.35.10.1.9
Commands MIB view Table view

Object

scalar RFC1213-MIBDisplayString 
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.

Context

MIB
VISION-MIB
OID
.1.3.6.1.4.1.89.35.10.1.9
Type
scalar
Access
readonly
Status
current
Parent
alerts

Net-SNMP examples

How SNMP and these commands work

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'VISION-MIB' -M '/opt/observium/mibs/radware:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'VISION-MIB::alertSourceDeviceName.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'VISION-MIB' -M '/opt/observium/mibs/radware:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'VISION-MIB::alertSourceDeviceName'

Syntax

RFC1213-MIBDisplayString
Source
RFC1213-MIBDisplayString
Base type
OctetString

Values & Constraints

No enumerated values or constraints recorded.