OID reference
1.3.6.1.4.1.838.3.14.1.5.1.2
A numeric index to allow multiple Security Associations per tunnel or transport.
Identification
{1 3 6 1 4 1 838 3 14 1 5 1 2}
Definitions may combine these properties differently.
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.
Published row index variants: ifIndex, ipsecSaName, ipsecSaIndex; ifIndex, ipsecTunnelName, ipsecSaIndex.
A query example is omitted because the source variants do not establish compatible read access.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
Parsed from XEDIA-IPSEC-MIB.mib · XEDIA-IPSEC-MIB
Source file: Download XEDIA-IPSEC-MIB.mib
Source data warning: The file uses BIT STRING rather than the SMI BITS construct. The published spelling and declared bit positions are retained; no wire type or unspecified bit positions are inferred.
Description 2
Source file: Download ipsec.mi2.txt
Source data warning: The file uses BIT STRING rather than the SMI BITS construct. The published spelling and declared bit positions are retained; no wire type or unspecified bit positions are inferred.
Historical records
ipsecSaSpi OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Security profile index. For static or dynamic inbound SAs,
SPI is selected by us. For dynamic outbound SAs, SPI is
selected by peer. For static outbound SAs, SPI is manually
configured."
::= { ipsecSaEntry 2 }
ipsecSaIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A numeric index to allow multiple Security Associations per
tunnel or transport."
::= { ipsecSaEntry 2 }
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.838.3.14.1.5.1.1 | ipsecSaIndex, ipsecSaName | 0 | 0 | The name of the tunnel or transport that this Security Association is associated with. |
| 1.3.6.1.4.1.838.3.14.1.5.1.3 | ipsecSaCreation, ipsecSaSpi | 0 | 0 | Security profile index. For static or dynamic inbound SAs, SPI is selected by us. For dynamic outbound SAs, SPI is selected by pe… |
| 1.3.6.1.4.1.838.3.14.1.5.1.4 | ipsecSaDirection, ipsecSaCreation | 0 | 0 | Specifies how SA was created. Manually configured SAs will have the value static(1). Dynamical SAs such as those created by key m… |
| 1.3.6.1.4.1.838.3.14.1.5.1.5 | ipsecSaProtocol, ipsecSaDirection | 0 | 0 | SA direction. Traffic SAs are unidirectional whereas key management protocol SAs such as ISA-KMP are bidirectional. |
| 1.3.6.1.4.1.838.3.14.1.5.1.6 | ipsecSaEncryptionKey, ipsecSaProtocol | 0 | 0 | Specifies the SA protocol type. |
| 1.3.6.1.4.1.838.3.14.1.5.1.7 | ipsecSaAuthenticationKey, ipsecSaEncryptionKey | 0 | 0 | The SAs encryption key. For a dynamic SA, the encryption key is negotiated by the key management protocol such as ISAKMP and is n… |
| 1.3.6.1.4.1.838.3.14.1.5.1.8 | ipsecSaInOutPkts, ipsecSaAuthenticationKey | 0 | 0 | For dynamic SAs, the authentication keys have been negotiated by ISAKMP. For static SA, the keys have been configured. For stati… |
| 1.3.6.1.4.1.838.3.14.1.5.1.9 | ipsecSaInOutOctets, ipsecSaInOutPkts | 0 | 0 | It counts a total number of frames since the SA was created. For inbound SA it represents received frames. For outbound SA it rep… |
| 1.3.6.1.4.1.838.3.14.1.5.1.10 | ipsecSaRowStatus, ipsecSaInOutOctets | 0 | 0 | It counts a total number of bytes since the SA was created. For inbound SA it represents received bytes. For outbound SA it repre… |
| 1.3.6.1.4.1.838.3.14.1.5.1.11 | ipsecSaRowStatus | 0 | 0 | This object allows entries to be created and deleted in this table. The only supported values supported are active(1), createAndG… |