Tunnel Security Association (SA) table. Each entry in the
table is a Security Association. SA's are associated with
a single IPSec tunnel and indexed accordingly. Tunnel SA's
have the same ifIndex and name as the tunnel, plus an additional
SA index.
Dynamic site-to-site and dialin-client tunnels have dynamic
SA's created dynamically by IKE. Client group tunnels
do not have associated SA's since these represent a group of
client tunnels which individually have SA's. Static tunnels
have static SA's created manually.
Parsed from file ipsec.mi2.txt
Company: None
Module: XEDIA-IPSEC-MIB
Security Association (SA) table. Each entry in the table is a
Security Association. SA's are associated with a single IPSec
tunnel or transport and indexed accordingly. SA's associated
with a tunnel will have the same ifIndex and name as the tunnel.
SA's associated with a transport have a zero ifIndex and the
same name as the transport.
Dynamic site-to-site and dialin-client tunnels have dynamic
SA's created dynamically by ISAKMP. Dialin-group tunnels
do not have associated SA's since these represent a group of
dialin-client tunnels which individually have SA's. Static
tunnels have static SA's created manually.
Parsed from file XEDIA-IPSEC-MIB.mib
Module: XEDIA-IPSEC-MIB
Vendor: Lucent
Module: XEDIA-IPSEC-MIB (ipsec.mi2)
Type: TABLE
Access: not-accessible
Syntax: SEQUENCE OF
Automatically extracted from www.mibdepot.com
ipsecSaTable OBJECT-TYPE SYNTAX SEQUENCE OF IpsecSaEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Tunnel Security Association (SA) table. Each entry in the table is a Security Association. SA's are associated with a single IPSec tunnel and indexed accordingly. Tunnel SA's have the same ifIndex and name as the tunnel, plus an additional SA index. Dynamic site-to-site and dialin-client tunnels have dynamic SA's created dynamically by IKE. Client group tunnels do not have associated SA's since these represent a group of client tunnels which individually have SA's. Static tunnels have static SA's created manually." ::= { ipsecObjects 5 }
ipsecSaTable OBJECT-TYPE SYNTAX SEQUENCE OF IpsecSaEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Security Association (SA) table. Each entry in the table is a Security Association. SA's are associated with a single IPSec tunnel or transport and indexed accordingly. SA's associated with a tunnel will have the same ifIndex and name as the tunnel. SA's associated with a transport have a zero ifIndex and the same name as the transport. Dynamic site-to-site and dialin-client tunnels have dynamic SA's created dynamically by ISAKMP. Dialin-group tunnels do not have associated SA's since these represent a group of dialin-client tunnels which individually have SA's. Static tunnels have static SA's created manually." ::= { ipsecObjects 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.838.3.14.1.5.1 | ipsecSaEntry | 11 | 11 | Information about a specific Security Association. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.838.3.14.1.1 | ipsecSubsystemGroup | 2 | 4 | None |
| 1.3.6.1.4.1.838.3.14.1.2 | ipsecSecurityProfileTable | 1 | 13 | This table defines a set of security attributes that will be used to describe a security association (SA). There may be many SAs … |
| 1.3.6.1.4.1.838.3.14.1.3 | ipsecIfTable | 1 | 23 | ipsecIftable |
| 1.3.6.1.4.1.838.3.14.1.4 | ipsecTunnelTable | 1 | 32 | The tunnel table is used to configure and monitor VPN tunnels. There two cases here: site-to-site and remote dial-in. For site-to… |
| 1.3.6.1.4.1.838.3.14.1.6 | ipsecTransportIfTable | 1 | 25 | ipsecTransportIftable |
| 1.3.6.1.4.1.838.3.14.1.7 | ipsecTransportTable | 1 | 30 | Information associated with an IPSec Transport. |
| 1.3.6.1.4.1.838.3.14.1.8 | ipsecTransportSaTable | 1 | 11 | Transport Security Association (SA) table. Each entry in the table is a Security Association. SA's are associated with a single … |