ipspActionNotification
IPSEC-POLICY-MIB ·
.1.3.6.1.2.1.153.2.0.1
Object
notification
Notification that an action was executed by a rule. Only
actions with logging enabled will result in this notification
getting sent. The objects sent must include the
ipspActionExecuted object which will indicate which
action was executed within the scope of the rule.
Additionally the ipspIPSourceType,
ipspIPSourceAddress, ipspIPDestinationType, and
ipspIPDestinationAddress objects must be included to
indicate the packet source and destination of the packet that
triggered the action. Finally the
ipspIPInterfaceType, ipspIPInterfaceAddress,
and ipspPacketDirection objects are included to
indicate which interface the action was executed in
association with and if the packet was inbound or outbond
through the endpoint.
Note that compound actions with multiple
executed subactions may result in multiple notifications
being sent from a single rule execution.
Context
- MIB
- IPSEC-POLICY-MIB
- OID
.1.3.6.1.2.1.153.2.0.1- Type
- notification
- Status
- current
- Parent
- ipspNotifications
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workNotifications are emitted by an agent; they cannot be read with snmpget or walked.
Inspect the notification definition
/usr/bin/snmptranslate -Pud -Ir -Td -m 'IPSEC-POLICY-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'IPSEC-POLICY-MIB::ipspActionNotification'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'IPSEC-POLICY-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'IPSEC-POLICY-MIB::ipspActionNotification'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Conformance
Member of