rsInvalidSpiTrap

RAPID-IPSEC-SA-MON-MIB-EXT · .1.3.6.1.4.1.4355.3.1.4.0.7
Commands MIB view Table view

Object

notification 
A packet with an unknown SPI was detected from the
specified peer with the specified SPI using the specified
protocol. The destination address of the received packet is
specified by 'ipsecLocalAddress'.
          
The value 'ifIndex' may be 0 if this optional linkage is
unsupported.
          
If the object 'ipsecSecurityProtocol' has the value for
IPCOMP, then the 'ipsecSPI' object is the CPI of the packet.
Implementations SHOULD send one trap per peer (within a
reasonable time period), rather than sending one trap per
packet.

Context

MIB
RAPID-IPSEC-SA-MON-MIB-EXT
OID
.1.3.6.1.4.1.4355.3.1.4.0.7
Type
notification
Status
current
Parent
rsSaTraps

Net-SNMP examples

How SNMP and these commands work

Notifications are emitted by an agent; they cannot be read with snmpget or walked.

Inspect the notification definition
/usr/bin/snmptranslate -Pud -Ir -Td -m 'RAPID-IPSEC-SA-MON-MIB-EXT' -M '/opt/observium/mibs/watchguard:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'RAPID-IPSEC-SA-MON-MIB-EXT::rsInvalidSpiTrap'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'RAPID-IPSEC-SA-MON-MIB-EXT' -M '/opt/observium/mibs/watchguard:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'RAPID-IPSEC-SA-MON-MIB-EXT::rsInvalidSpiTrap'

Syntax

No syntax metadata recorded.

Values & Constraints

No enumerated values or constraints recorded.