Home/Catalog/AVAYA-IPSEC-MIB

AVAYA-IPSEC-MIB

AI MIB Summary

The AVAYA-IPSEC-MIB provides management interfaces for configuring and monitoring IPsec security associations, tunnel states, and cryptographic parameters on Avaya converged gateways. It enables administrators to track IPSec session establishment, phase negotiation status, and traffic statistics to ensure secure tunnel integrity across the network.

The MIB module for configuring IPSec functionality in Avaya converged Gateways.
Main OID:
avayaIpsecMib.1.3.6.1.4.1.6889.2.6.1
161
Objects
Active
Status
4
Dependencies

Imported Objects

Objects

161 total
Object Name
avayaIpsecMibThe MIB module for configuring IPSec functionality in Avaya converged Gateways.
MODULE-IDENTITY
.1.3.6.1.4.1.6889.2.6.1
avipsMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.6889.2.6.1.1
avipsGlobals
OBJECT IDENTIFIER
.1.3.6.1.4.1.6889.2.6.1.1.1
avipsGlobalsInvalidSpiRecoveryThis object determines whether invalid-spi-recovery is enabled (true) or disabled (false). When enabled, the device shall open an IKE SA, if it does not already exist, in order to send DELETE message to the remote peer when receiving an invalid spi or invalid cookie with SIP of that remote peer. This causes faster recovery times in case of SADB inconsistency, but may cause D/DoS attack on the remote peer.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.1.1
avipsNatTEnabledThis object specifies whether IPSec NAT-T is invoked in the device. If this object is True then NAT-T is enabled.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.1.2
avipsNatTKeepaliveIntervalThis object determines the NAT-T keepalive interval in seconds. If this object is set to 0 then NAT-T keepalives are disabled.rw
Integer32 UNITS "seconds"
.1.3.6.1.4.1.6889.2.6.1.1.1.3
avipsCryptoEngineAccelEnabledThe value of this object determines whether IPSec HW acceleration is enabled or disabled. In case the HW does not support acceleration the value of this object shall be false.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.1.4
avipsIsakmpGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.6889.2.6.1.1.2
avipsIsakmpPeerTableThis table contains a list of all the remote peers and peer-groups we are willing to establish an IPSec VPN connection with. Each entry represents a peer or a peer-group, and is indexed by the peer's IKE identification (type and value), or the peer-group name. Each peer entry points to the ISAKMP policy that will be used for IKE negotiations (as an initiator or a responder). Note that in case this entry represents a peer-group the value of IsakmpIdentityType shall be set to peerGroup. In that case certain columns in this row are N/A.
SEQUENCE OF AvipsIsakmpPeerEntry
.1.3.6.1.4.1.6889.2.6.1.1.2.1
avipsIsakmpPeerEntryA specific entry.
AvipsIsakmpPeerEntry
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1
avipsIsakmpPeerIdTypeThis object is an enumeration identifying the type of the Identity value. Note that value can also be peerGroup, in that case avipsIsakmpPeerId contains the peer-group's name. Also note that certain columns in this row are N/A for peer-group (refer to specific objects' descriptions for details). This is also the first index component of this table.
IsakmpIdentityType
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1.1
avipsIsakmpPeerIdThis object contains an Identity filter to be used to match against the identity payload in an IKE request. This is also the second index component of this table.
IsakmpIdentityValue
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1.2
avipsIsakmpPeerDescriptionFree text describing this row.rw
DisplayString
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1.3
avipsIsakmpPeerIsaPlcyId1This object contains the ID of the ISAKMP policy to be used in IKE Phase I negotiation with this peer. A value of 0 indicates that this object is empty. This object is N/A if avipsIsakmpPeerIdType is peerGroup.rw
Integer32
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1.4
avipsIsakmpPeerInitiateModeThis object specifies how to initiate IKE when communicating with this peer: none(1) - Never initiate IKE with this peer (i.e. respond only) main(2) - Initiate Main Mode (MM) aggressive(3) - Initiate Aggressive Mode (AM) This object is N/A if avipsIsakmpPeerIdType is peerGroup.rw
Enumeration
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1.5
avipsIsakmpPeerSelfIdTypeThis object is an enumeration identifying the type of the Identity value which the local peer shall use in the its identity payload during Phase-1 negotiation. This object is N/A if avipsIsakmpPeerIdType is peerGroup.rw
IsakmpIdentityType
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1.6
avipsIsakmpPeerSelfIdIf not empty, this object specifies the identity value which the local peer will send in the identification payload during IKE Phase-1 negotiation. If this object is empty, the default local identity shall be sent, according to the value of avipsIsakmpPeerSelfIdType. This object is N/A if avipsIsakmpPeerIdType is peerGroup.rw
IsakmpIdentityValue
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1.7
avipsIsakmpPeerKeepaliveMetricThe worry-metric to be used for deciding when to send R-U-THERE message to the remote peer. This object is N/A if avipsIsakmpPeerIdType is peerGroup.rw
IsakmpDpdKeepaliveMetric
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1.8
avipsIsakmpPeerKeepaliveIntervalThe minimal interval, in seconds, between two consecutive R-U-THERE sent by the local peer, when the previous R-U-THERE message has been answered. The actual interval is based on this value and other parameters, such as the worry-metric. This object is N/A if avipsIsakmpPeerIdType is peerGroup.rw
Integer32 UNITS "seconds"
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1.9
avipsIsakmpPeerKeepaliveRetryIntervalThe actual interval, in seconds, between R-U-THERE retries sent by the local peer, when the previous R-U-THERE message has not been answered. This object is N/A if avipsIsakmpPeerIdType is peerGroup.rw
Integer32 UNITS "seconds"
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1.10
avipsIsakmpPeerKeepaliveTrackIdBind the status of this peer to an object-tracker by specifying the ID of the object-tracker (avstrTrackerId in AVAYA-SAA-TRACK-MIB). A value of 0 means that peer is not bound to any object-tracker. This object is N/A if avipsIsakmpPeerIdType is peerGroup.rw
Integer32
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1.11
avipsIsakmpPeerContChannelThis object determines whether continuous channel IKE mode is used for contacting the peer. Continuous channel IKE means that local peer tries to establish an IKE SA with the remote peer as soon as possible, also when there is no outbound traffic that requires it. This object is N/A if avipsIsakmpPeerIdType is peerGroup.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1.12
avipsIsakmpPeerRowStatusThis object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. If active, this object must remain active if it is referenced by a row in another table. Use createAndGo (not createAndWait) to create this row.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1.13
avipsIsakmpPeerGroupFailbacktoPrimaryIntervalThe amount of time in seconds that secondary peer shall be up (after primary peer went down) before there will be failback to primary peer (in case it is up again). The default value is 24 hours. Relevant for peer-group only (values 1 and up). For peer return value of 0.rw
Integer32 UNITS "seconds"
.1.3.6.1.4.1.6889.2.6.1.1.2.1.1.14
avipsPeerGroupPeersTableThis table contains all the associations between peer-groups and isakmp peers. The relation between peer-group and isakmp peer is many-to-many. A valid peer-group (i.e. a peer-group that can be associated with an active crypto-list) contains one or more isakmp peers. An isakmp peer may be contained in zero or more peer-groups.
SEQUENCE OF AvipsPeerGroupPeersEntry
.1.3.6.1.4.1.6889.2.6.1.1.2.2
avipsPeerGroupPeersEntryA specific entry.
AvipsPeerGroupPeersEntry
.1.3.6.1.4.1.6889.2.6.1.1.2.2.1
avipsPeerGroupPeersPGrpNameThe name of the peer-group associated with this isakmp peer. Note that there must exist a matching active entry in avipsIsakmpPeerTable which avipsIsakmpPeerIdType is peerGroup, otherwise a 'set' operation shall fail.
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.2.2.1.1
avipsPeerGroupPeersPeerIndexThe ordered index of the peer within the peer-group.
Integer32
.1.3.6.1.4.1.6889.2.6.1.1.2.2.1.2
avipsPeerGroupPeersPIdTypeThis object is an enumeration identifying the type of the Identity value of the peer associated with this IPSec connection. Note that value cannot be peerGroup. The contents of this object object is interpreted along with avipsPeerGroupPeersPIdValue.rw
IsakmpIdentityType
.1.3.6.1.4.1.6889.2.6.1.1.2.2.1.3
avipsPeerGroupPeersPIdValueThis object contains value of the peer ID. The contents of this object object is interpreted along with avipsPeerGroupPeersPIdType.rw
IsakmpIdentityValue
.1.3.6.1.4.1.6889.2.6.1.1.2.2.1.4
avipsPeerGroupPeersRowStatusThis object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. If active, this object must remain active if it is referenced by a row in another table. Use createAndWait (not createAndGo) to create this row. This object is active(1) after avipsPeerGroupPeersPIdType and avipsPeerGroupPeersPIdValue are set.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.2.2.1.5
avipsIsakmpPlcyTableThe table containing the list of all ISAKMP policy entries configured by the operator.
SEQUENCE OF AvipsIsakmpPlcyEntry
.1.3.6.1.4.1.6889.2.6.1.1.2.3
avipsIsakmpPlcyEntryEach entry contains the attributes associated with a single ISAKMP Policy entry.
AvipsIsakmpPlcyEntry
.1.3.6.1.4.1.6889.2.6.1.1.2.3.1
avipsIsakmpPlcyIdThe ID of this ISAKMP Policy entry. This is also the index of this table.
Integer32
.1.3.6.1.4.1.6889.2.6.1.1.2.3.1.1
avipsIsakmpPlcyDescriptionFree text describing this object.rw
DisplayString
.1.3.6.1.4.1.6889.2.6.1.1.2.3.1.2
avipsIsakmpPlcyDhGroupThis object specifies the Oakley group used for Diffie Hellman exchange in the Main Mode. If this policy item is selected to negotiate Main Mode with an IKE peer, the local entity chooses the group specified by this object to perform Diffie Hellman exchange with the peer.rw
DiffHellmanGrp
.1.3.6.1.4.1.6889.2.6.1.1.2.3.1.3
avipsIsakmpPlcyEncrAlgoThe encryption transform specified by this ISAKMP policy specification. The Internet Key Exchange (IKE) tunnels setup using this policy item would use the specified encryption transform to protect the ISAKMP PDUs.rw
IkeEncryptAlgo
.1.3.6.1.4.1.6889.2.6.1.1.2.3.1.4
avipsIsakmpPlcyHashAlgoThe hash transform specified by this ISAKMP policy specification. The IKE tunnels setup using this policy item would use the specified hash transform to protect the ISAKMP PDUs.rw
IkeHashAlgo
.1.3.6.1.4.1.6889.2.6.1.1.2.3.1.5
avipsIsakmpPlcyLifetimeThis object specifies the lifetime, in seconds, of the IKE tunnels generated using this policy specification.rw
Integer32
.1.3.6.1.4.1.6889.2.6.1.1.2.3.1.6
avipsIsakmpPlcyAuthThe peer authentication method specified by this ISAKMP policy specification. If this policy entity is selected for negotiation with a peer, the local entity would authenticate the peer using the method specified by this object.rw
Enumeration
.1.3.6.1.4.1.6889.2.6.1.1.2.3.1.7
avipsIsakmpPlcyRowStatusThis object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. If active, this object must remain active if it is referenced by a row in another table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.2.3.1.8
avipsIpsecGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.6889.2.6.1.1.3
avipsCryptoMapTableThis table contains all the crypto maps configured by the user. A crypto map essentially concentrates all the IPSec protection policy required for establishing IKE Phase-1 and Phase-2 connections.
SEQUENCE OF AvipsCryptoMapEntry
.1.3.6.1.4.1.6889.2.6.1.1.3.1
avipsCryptoMapEntryA specific crypto map entry.
AvipsCryptoMapEntry
.1.3.6.1.4.1.6889.2.6.1.1.3.1.1
avipsCryptoMapIdThe ID of the crypto map entry. This is also the index of this table.
Integer32
.1.3.6.1.4.1.6889.2.6.1.1.3.1.1.1
avipsCryptoMapDescriptionFree text describing this object.rw
DisplayString
.1.3.6.1.4.1.6889.2.6.1.1.3.1.1.2
avipsCryptoMapPeerIdTypeThis object is an enumeration identifying the type of the Identity value of the peer associated with this IPSec connection. The contents of this object object is interpreted along with avipsCryptoMapPeerIdValue.rw
IsakmpIdentityType
.1.3.6.1.4.1.6889.2.6.1.1.3.1.1.3
avipsCryptoMapPeerIdValueThis object contains an Identity filter to be used to select the remote peer or peer-group when initiating IKE, and to match against the identity payload in an IKE request when responding to IKE. The contents of this object object is interpreted along with avipsCryptoMapPeerIdType.rw
IsakmpIdentityValue
.1.3.6.1.4.1.6889.2.6.1.1.3.1.1.4
avipsCryptoMapTranSetName1The name of the transforms-set for this crypto map. This object is the index into the avipsTranSetTable.rw
DisplayString
.1.3.6.1.4.1.6889.2.6.1.1.3.1.1.5
avipsCryptoMapIsReadyThis field is true if and only if this crypto map entry and all the descendent configuration objects pointed by it are in the ready state. Note that crypto list activation requires that all the crypto maps it points to be ready.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.3.1.1.6
avipsCryptoMapTunnelDscpThe method used to set the high 6 bits of the TOS in the outer IP header. A value of -1 indicates that the bits are copied from the payload's header. A value between 0 and 63 inclusive indicates that the bit field is set to the indicated value.rw
Integer32 (-1 | 0..63)
.1.3.6.1.4.1.6889.2.6.1.1.3.1.1.7
avipsCryptoMapContChannelThis object determines whether continuous channel IPSec mode is used for the rule pointing to this crypto map. Continuous channel IPSec means that local peer tries to establish an IPSec SA with the remote peer as soon as possible, also when there is no outbound traffic that requires it.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.3.1.1.8
avipsCryptoMapRowStatusThis object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. If active, this object must remain active if it is referenced by an active crypto list.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.3.1.1.9
avipsTranSetTableThis table lists all the transform-sets which can be used to build or accept IPsec proposals.
SEQUENCE OF AvipsTranSetEntry
.1.3.6.1.4.1.6889.2.6.1.1.3.2
avipsTranSetEntryAn entry containing the information on an IPsec transform-set.
AvipsTranSetEntry
.1.3.6.1.4.1.6889.2.6.1.1.3.2.1
avipsTranSetNameThe name of this particular transform-set be referred to by an avipsCryptoMapEntry. This is the index of this table.
DisplayString
.1.3.6.1.4.1.6889.2.6.1.1.3.2.1.1
avipsTranSetEspEncrTranThis object specifies the transform ID of the ESP encryption algorithm.rw
EspEncrTransform
.1.3.6.1.4.1.6889.2.6.1.1.3.2.1.2
avipsTranSetEspHashTranThis object specifies the ESP hash algorithm ID.rw
EspHashTransform
.1.3.6.1.4.1.6889.2.6.1.1.3.2.1.3
avipsTranSetLifetimeThis object specifies how long, in seconds, the security association (SA) derived from this transform should be used. The value 0 is reserved for future use.rw
Integer32 (0 | 120..86400) UNITS "seconds"
.1.3.6.1.4.1.6889.2.6.1.1.3.2.1.4
avipsTranSetLifesizeThis object specifies how long, in Kilobytes, the security association (SA) derived from this transform should be used. The value -1 means that no size based lifetime will be offered to the other side. The value 0 is reserved for future use.rw
Integer32 (-1 | 0 | 2560..536870912) UNITS "KBytes"
.1.3.6.1.4.1.6889.2.6.1.1.3.2.1.5
avipsTranSetPfsGroupThis object specifies the DH group that shall be used for PFS in quick mode exchange, when creating the security association (SA) derived from this transform. The reserved value 'none' means that PFS shall not be used.rw
DiffHellmanGrp
.1.3.6.1.4.1.6889.2.6.1.1.3.2.1.6
avipsTranSetEncapModeThis object determines the ESP encapsulation mode that will be used. Possible values are 'tunnel' and 'transport'. In case transport mode is configured, it shall be used only if possible, i.e. the SIP and DIP of the relevant rule are equivalent to the LTEP and RTEP. Otherwise tunnel mode is used.rw
IpsecEncapMode
.1.3.6.1.4.1.6889.2.6.1.1.3.2.1.7
avipsTranSetEspCompTranThis object specifies the ESP compression algorithm: none(1) - no compression algorithm. ippcpLzs(2) - IPPCP with LZS compression.rw
Enumeration
.1.3.6.1.4.1.6889.2.6.1.1.3.2.1.8
avipsTranRowStatusThis object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. If active, this object must remain active if it is referenced by a row in another table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.3.2.1.9
avipsMonitoringGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.6889.2.6.1.1.4
avipsMonitoringTables
OBJECT IDENTIFIER
.1.3.6.1.4.1.6889.2.6.1.1.4.1
avipsMonitoringTablesGlobals
OBJECT IDENTIFIER
.1.3.6.1.4.1.6889.2.6.1.1.4.1.1
avipsMonitorRstCntrsUse this object to reset all the IPSec counters. Set this object to reset(2) in order to do that. This operation is equivalent to issuing the 'clear crypto sa counters' command in the CLI.rw
Enumeration
.1.3.6.1.4.1.6889.2.6.1.1.4.1.1.1
avipsMonitorRstCntrsLastChangesysUpTime when last IPSec counters reset by avipsMonitorRstCntrs or 'clear crypto sa counters' in CLI, in hundredths of a second.ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.4.1.1.2
avipsPeerTableThis table contains entries for every active isakmp peer in the system. The word 'active' suggests that in case the peer is part of a redundant list of peers within a crypto map, only the peer that is currently active will be included.
SEQUENCE OF AvipsPeerEntry
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2
avipsPeerEntryA specific peer entry.
AvipsPeerEntry
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1
avipsPeerLocalIdA synthetic ID that uniquely identifies the local peer for monitoring purpose. Note that this ID is persistent for this peer. This is also the first index component of this table.
Unsigned32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.1
avipsPeerRemoteIdA synthetic ID that uniquely identifies the remote peer for monitoring purpose. Note that this ID is persistent for this peer. This is also the second index component of this table.
Unsigned32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.2
avipsPeerLocalTypeThe type of the local peer identity, as it was configured. If the local peer ID was configured as an interface name, the value of this object shall be ifName.ro
IsakmpIdentityType
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.3
avipsPeerLocalValueThe value of the local peer identity. If the local peer type is an IP Address, then this is the IP Address used to identify the local peer. If the local peer type is an interface name, then this is the name of the interface which IP is used to identify the local peer. If the local peer type is a fqdn, then this is the fqdn used to identify the local peer.ro
IsakmpIdentityValue
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.4
avipsPeerRemoteTypeThe type of the remote peer identity.ro
IsakmpIdentityType
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.5
avipsPeerRemoteValueThe value of the remote peer identity. If the remote peer type is an IP Address, then this is the IP Address used to identify the remote peer. If the remote peer type is a fqdn, then this is the fqdn used to identify the remote peer.ro
IsakmpIdentityValue
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.6
avipsPeerRemoteDescriptionFree text describing the remote peer or peer-group. The value of this field is taken from avipsIsakmpPeerDescription.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.7
avipsPeerLocalAddressThe IP address of the local peer. This is derived from the local-address specified in the crypto-list that creates this connection. If the local peer type is an IP Address, then this is identical to avipsPeerLocalValue.ro
IpAddress
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.8
avipsPeerRemoteAddressThe IP address of the remote peer. If the remote peer type is an IP Address, then this is identical to avipsPeerRemoteValue. If the remote peer type is a fqdn, then this is the IP address that was received by DNS resolution of the fqdn specified in IsakmpIdentityValue.ro
IpAddress
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.9
avipsPeerRemotePeerGrpActiveIndexIn case the remote is a peer-group, i.e. avipsPeerRemoteType is peerGroup, this object specifies the index within the peer-group of the currently active peer. This value is taken from avipsPeerGroupPeersPeerIndex of the active peer in this peer-group.ro
Integer32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.10
avipsPeerRemotePeerGrpActiveIdTypeIn case the remote is a peer-group, i.e. avipsPeerRemoteType is peerGroup, this object specifies the id-type of the currently active peer. This value is taken from avipsIsakmpPeerIdType of the active peer in this peer-group.ro
IsakmpIdentityType
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.11
avipsPeerRemotePeerGrpActiveIdValueIn case the remote is a peer-group, i.e. avipsPeerRemoteType is peerGroup, this object specifies the id-value of the currently active peer. This value is taken from avipsIsakmpPeerId of the active peer in this peer-group.ro
IsakmpIdentityValue
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.12
avipsPeerIsakmpStateThis object specifies the state of the IKE connection between the peers. 1. closed - No IKE SA exists between peers because it was not negotiated yet, or because last IKE closed normally due to hard timeout, clear by admin, or DELETE received from the remote peer. This is also the initial state of the row when it is created. 2. inProgress - No IKE SA exists between peers, but it is currently being negotiated in Phase-1. 3. established - IKE SA exists between peers. 4. failed - No IKE SA exists between peers because of a failure. Possible reasons are: 1. Last time we tried to establish IKE the negotiation failed. 2. Last time we tried to establish IKE the remote peer DNS resolution failed. 3. During last connection DPD signaled a connection failure. 4. During last connection a track object signaled a connection failure. 5. The interface used for local-address does not have an IP address asigned to it 1 minute or more after this row was created. 6. Last time we negotiated Phase-2 the negotiation timed-out, and the current IKE was subsequently deleted. NOTE: When continuous-channel IKE is used, the state shall remain 'established' during the normal transition time between one IKE SA and the next. However, if the IKE SA was deleted due to a suspected problem then the state will change normally during the transition (i.e. 'closed' and then 'inProgress'). [Suspected problem: if the last IKE SA was DELETEd by the remote peer after less then 5 minutes,or if it was deleted by local admin]ro
Enumeration
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.13
avipsPeerIsakmpStateLastChangesysUpTime when the last change in avipsPeerIsakmpState occured, in hundredths of a second.ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.14
avipsPeerTunnelsClosedThe number of IPSec tunnels associated with these peers, which are in the 'closed' state.ro
Gauge32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.15
avipsPeerTunnelsInProgressThe number of IPSec tunnels associated with these peers, which are in the 'inProgress' state.ro
Gauge32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.16
avipsPeerTunnelsEstablishedThe number of IPSec tunnels associated with these peers, which are in the 'established' state.ro
Gauge32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.17
avipsPeerTunnelsFailedThe number of IPSec tunnels associated with these peers, which are in the 'failed' state.ro
Gauge32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.18
avipsPeerInOctetsThe aggregate number of octets (bytes) successfully received through all the tunnels between the peers. This value is accumulated BEFORE determining whether or not the packet should be decompressed. This number is the sum of avipsTunnelInOctets together with avipsTunnelInOctetsWraps as a single 64-bit integer, for all the IPSec tunnels pertaining to the peers. See also avipsPeerInOctetsWraps for the number of times this counter has wrapped.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.19
avipsPeerInOctetsWrapsThe number of times avipsPeerInOctets has wrapped.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.20
avipsPeerInDecompOctetsThe aggregate number of decompressed octets (bytes) successfully received through all the tunnels between the peers. This value is accumulated AFTER the packet is decompressed. If compression is not being used in any of the tunnels, this value will match the value of avipsPeerInOctets. This number is the sum of avipsTunnelInDecompOctets together with avipsTunnelInDecompOctetsWraps as a single 64-bit integer, for all the tunnels pertaining to the peers. See also avipsPeerInDecompOctetsWraps for the number of times this counter has wrapped.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.21
avipsPeerInDecompOctetsWrapsThe number of times avipsPeerInDecompOctets has wrapped.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.22
avipsPeerInDecompRatioThe overall decompression ratio * 100. This is the ratio between the number of octets received after decompression and the number of octets received before decompression. It is calculated as the integer of {[(avipsPeerInDecompOctetsWraps*2^32 + avipsPeerInDecompOctets) / (avipsPeerInOctetsWraps*2^32 + avipsPeerInOctets)] * 100}ro
Gauge32 UNITS "Ratio * 100"
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.23
avipsPeerInPktsThe aggregate number of packets successfully received through all the tunnels between the peers. This number is the sum of avipsTunnelInPkts for all the tunnels pertaining to the peers.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.24
avipsPeerInDropPktsThe aggregate number of packets dropped after being received through any of the tunnels between the peers. This number is the sum of avipsTunnelInDropTotalPkts for all the tunnels pertaining to the peers.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.25
avipsPeerOutOctetsThe aggregate number of octets (bytes) successfully transmitted through all the tunnels between the peers. This value is accumulated AFTER determining whether or not the packet should be compressed. This number is the sum of avipsTunnelOutOctets together with vipsTunnelOutOctetsWraps as a single 64-bit integer, for all the tunnels pertaining to the peers. See also avipsPeerOutOctetsWraps for the number of times this counter has wrapped.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.26
avipsPeerOutOctetsWrapsThe number of times avipsPeerOutOctets has wrapped.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.27
avipsPeerOutUncompOctetsThe aggregate number of uncompressed octets (bytes) successfully transmitted through this IPsec Tunnel. This value is accumulated BEFORE the packet is compressed. If compression is not being used in any of the tunnels, this value will match the value of avipsPeerOutOctets. This number is the sum of avipsTunnelOutUncompOctets together with avipsTunnelOutUncompOctetsWraps as a single 64-bit integer, for all the tunnels pertaining to the peers. See also avipsPeerOutUncompOctetsWraps for the number of times this counter has wrapped.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.28
avipsPeerOutUncompOctetsWrapsThe number of times avipsPeerInDecompOctets has wrapped.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.29
avipsPeerOutCompRatioThe overall compression ratio * 100. This is the ratio between the number of outbound octets before compression and the number of outbound octets after compression. It is calculated as the integer of {[(avipsPeerOutUncompOctetsWraps*2^32 + avipsPeerOutUncompOctets) / (avipsPeerOutOctetsWraps*2^32 + avipsPeerOutOctets)]* 100}ro
Gauge32 UNITS "Ratio * 100"
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.30
avipsPeerOutPktsThe aggregate number of packets successfully transmitted through all the tunnels between the peers. This number is the sum of avipsTunnelOutPkts for all the tunnels pertaining to the peers.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.31
avipsPeerOutDropPktsThe aggregate number of packets dropped before being transmitted through any of the tunnels between the peers. This number is the sum of avipsTunnelOutDropTotalPkts for all the tunnels pertaining to the peers.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.32
avipsTunnelTableThis table contains a entries for all the tunnels in the system. A 'tunnel' is a rule within an active crypto-list.
SEQUENCE OF AvipsTunnelEntry
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3
avipsTunnelEntryA specific tunnel entry.
AvipsTunnelEntry
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1
avipsTunnelPeerLocalIdA synthetic ID that uniquely identifies the local peer for monitoring purpose. Note that this ID is persistent for this peer.
Unsigned32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.1
avipsTunnelPeerRemoteIdA synthetic ID that uniquely identifies the remote peer for monitoring purpose. Note that this ID is persistent for this peer.
Unsigned32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.2
avipsTunnelIndexThe ID of the crypto-list containing the rule that creates this tunnel. This is also the fifth index component of this table.
Integer32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.3
avipsTunnelSubIndexThe index of the crypto-list rule that creates this tunnel. This is also the sixth index component of this table.
Integer32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.4
avipsTunnelPeerLocalTypeThe type of the local peer identity, as it was configured. If the local peer ID was configured as an interface name, the value of this object shall be ifName. This is also the first index component of this table.ro
IsakmpIdentityType
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.5
avipsTunnelPeerLocalValueThe value of the local peer identity. If the local peer type is an IP Address, then this is the IP Address used to identify the local peer. If the local peer type is an interface name, then this is the name of the interface which IP is used to identify the local peer. If the local peer type is a fqdn, then this is the fqdn used to identify the local peer. This is also the second index component of this table.ro
IsakmpIdentityValue
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.6
avipsTunnelPeerRemoteTypeThe type of the remote peer identity. This is also the third index component of this table.ro
IsakmpIdentityType
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.7
avipsTunnelPeerRemoteValueThe value of the remote peer identity. If the remote peer type is an IP Address, then this is the IP Address used to identify the remote peer. If the remote peer type is a fqdn, then this is the fqdn used to identify the remote peer. This is also the fourth index component of this table.ro
IsakmpIdentityValue
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.8
avipsTunnelDescriptionFree text describing this tunnel. The value of this field is taken from the description specified for the crypto-list rule that creates this tunnel.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.9
avipsTunnelLocalAddressThe IP address of the local peer.ro
IpAddress
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.10
avipsTunnelRemoteAddressThe IP address of the remote peer.ro
IpAddress
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.11
avipsTunnelProxyLocalSubnetThe local subnet address this tunnel protects.ro
IpAddress
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.12
avipsTunnelProxyLocalMaskThe local subnet mask this tunnel protects.ro
IpAddress
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.13
avipsTunnelProxyRemoteSubnetThe remote subnet address this tunnel protects.ro
IpAddress
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.14
avipsTunnelProxyRemoteMaskThe remote subnet mask this tunnel protects.ro
IpAddress
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.15
avipsTunnelStateThis object specifies the state of this tunnel. 1. closed - The tunnel does not exist between the peers because it was not negotiated yet, or because last tunnel closed normally due to hard timeout, clear by admin or DELETE received from the remote peer. This is also the initial state of the row when it is created. 2. inProgress - The tunnel does not exist between peers, but it is currently being negotiated in IKE Quick Mode. 3. established - The tunnel exists between peers. 4. failed - The tunnel does not exist between peers because of a failure: 1. Last time we tried to establish this tunnel the negotiation failed. 2. The connection with the remote peer has failed due to one of the following, and hence all the corresponding ipsec tunnels were closed: a. Last time we tried to establish IKE the negotiation failed. b. During last connection a track object signaled a connection failure. c. The interface used for local-address does not have an IP address asigned to it 1 minute or more after this row was created. NOTE: The word 'tunnel' in this context refers to 1 or more IPSec SAs (ESP or AH) between the peers, pertaining to the proxy addresses specified in this entry. As long as there is at least 1 SA established, the tunnel state shall remain 'established'.ro
Enumeration
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.16
avipsTunnelStateLastChangesysUpTime when the last change in avipsTunnelState occured, in hundredths of a second.ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.17
avipsTunnelLastCntrsResetsysUpTime when last counter reset for this tunnel occured, in hundredths of a second. Counters are zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.18
avipsTunnelInOctetsThe total number of octets (bytes) successfully received through this IPSec tunnel. This value is accumulated BEFORE determining whether or not the packet should be decompressed. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config). See also avipsTunnelInOctetsWraps for the number of times this counter has wrapped.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.19
avipsTunnelInOctetsWrapsThe number of times avipsTunnelInOctets has wrapped. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.20
avipsTunnelInDecompOctetsThe total number of decompressed octets (bytes) successfully received through this IPsec Tunnel. This value is accumulated AFTER the packet is decompressed. If compression is not being used, this value will match the value of avipsTunnelInOctets. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config). See also avipsTunnelInDecompOctetsWraps for the number of times this counter has wrapped.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.21
avipsTunnelInDecompOctetsWrapsThe number of times avipsTunnelInDecompOctets has wrapped. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.22
avipsTunnelInDecompRatioThe overall decompression ratio * 100. This is the ratio between the number of octets received after decompression and the number of octets received before decompression. It is calculated as the integer of {[(avipsTunnelInDecompOctetsWraps*2^32 + avipsTunnelInDecompOctets) / (avipsTunnelInOctetsWraps*2^32 + avipsTunnelInOctets)] * 100}ro
Gauge32 UNITS "Ratio * 100"
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.23
avipsTunnelInPktsThe number of packets succesfully received through this tunnel. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.24
avipsTunnelInDropTotalPktsThe total number of packets discarded after being received through this tunnel. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.25
avipsTunnelInDropAntiReplayPktsThe number of packets discarded after being received through this tunnel due to anti-replay verification failure. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.26
avipsTunnelInDropHmacFailPktsThe number of packets discarded after being received through this tunnel due to HMAC verification failure. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.27
avipsTunnelInDropBadTrailerPktsThe number of packets discarded after being received through this tunnel due to bad ESP trailer format received failure. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.28
avipsTunnelInDropInvalidIdPktsThe number of packets discarded after being received through this tunnel due to invalid identity: inner (original) IP header address doesn't match the configured tunnel proxy IPs. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.29
avipsTunnelInDropUnprotectPktsThe number of packets discarded after being received in the clear (unprotected) although they were expected to arrive protected by this tunnel (i.e. unprotected packets with source and destination IP matching the proxy IPs of this tunnel). This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.30
avipsTunnelInDropInvalidLenPktsThe number of packets discarded after being received through this tunnel due to length being not aligned to cipher block. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.31
avipsTunnelInDropSaExpiredPktsThe number of packets discarded after being received through this tunnel due to SA KB lifetime being smaller then the external IP packet total length. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.32
avipsTunnelOutOctetsThe total number of octets (bytes) successfully transmitted through this IPSec tunnel. This value is accumulated AFTER determining whether or not the packet should be compressed. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config). See also avipsTunnelOutOctetsWraps for the number of times this counter has wrapped.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.33
avipsTunnelOutOctetsWrapsThe number of times avipsTunnelOutOctets has wrapped. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.34
avipsTunnelOutUncompOctetsThe total number of uncompressed octets (bytes) successfully transmitted through this IPsec Tunnel. This value is accumulated BEFORE the packet is compressed. If compression is not being used, this value will match the value of avipsTunnelOutOctets. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config). See also avipsTunnelOutUncompOctetsWraps for the number of times this counter has wrapped.ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.35
avipsTunnelOutUncompOctetsWrapsThe number of times avipsTunnelInDecompOctets has wrapped. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.36
avipsTunnelOutCompRatioThe overall compression ratio * 100. This is the ratio between the number of outbound octets before compression and the number of outbound octets after compression. It is calculated as the integer of {[(avipsTunnelOutUncompOctetsWraps*2^32 + avipsTunnelOutUncompOctets) / (avipsTunnelOutOctetsWraps*2^32 + avipsTunnelOutOctets)]* 100}ro
Gauge32 UNITS "Ratio * 100"
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.37
avipsTunnelOutPktsThe number of packets succesfully transmitted through this tunnel. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.38
avipsTunnelOutDropTotalPktsThe total number of packets dropped before being transmitted through this tunnel. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.39
avipsTunnelOutDropNoSaPktsThe number of packets dropped before being transmitted through this tunnel due to no IPSec SA existed when the packet arrived. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.40
avipsTunnelOutDropSeqRolPktsThe number of packets dropped before being transmitted through this tunnel due to sequence number rollover: the sequence number of the IPSec SA reached its capacity. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.41
avipsTunnelOutDropSaExpiredPktsThe number of packets dropped before being transmitted through this tunnel due to SA expired: SA KB lifetime is smaller then the external IP packet total length. This counter is zeroized when: o Issuing 'clear crypto sa counters' in CLI. o Setting avipsMonitorRstCntrs in MIB (equivalent to above). o Issuing 'clear crypto sa all' in CLI. o Activating the crypto-list on an interface for the first time. o Failing-over to a different peer. o Learning a new local-address (DHCP, PPPoE, user config).ro
Counter32
.1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.42
avipsMIBNotificationPrefix
OBJECT IDENTIFIER
.1.3.6.1.4.1.6889.2.6.1.2
avipsMIBNotifications
OBJECT IDENTIFIER
.1.3.6.1.4.1.6889.2.6.1.2.0
avipsIskampEstablishedThis notification is sent whenever avipsPeerIsakmpState moves into the 'established' state.
NOTIFICATION-TYPE
.1.3.6.1.4.1.6889.2.6.1.2.0.1
avipsIskampClosedThis notification is sent whenever avipsPeerIsakmpState moves into the 'closed' state, excluding during row creation.
NOTIFICATION-TYPE
.1.3.6.1.4.1.6889.2.6.1.2.0.2
avipsIskampFailedThis notification is sent whenever avipsPeerIsakmpState moves into the 'failed' state.
NOTIFICATION-TYPE
.1.3.6.1.4.1.6889.2.6.1.2.0.3
avipsIpsecTunnelEstablishedThis notification is sent whenever avipsTunnelState moves into the 'established' state.
NOTIFICATION-TYPE
.1.3.6.1.4.1.6889.2.6.1.2.0.4
avipsIpsecTunnelClosedThis notification is sent whenever avipsTunnelState moves into the 'closed' state, excluding during row creation.
NOTIFICATION-TYPE
.1.3.6.1.4.1.6889.2.6.1.2.0.5
avipsIpsecTunnelFailedThis notification is sent whenever avipsTunnelState moves into the 'failed' state.
NOTIFICATION-TYPE
.1.3.6.1.4.1.6889.2.6.1.2.0.6
avipsMIBConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.6889.2.6.1.3
avipsMIBGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.6889.2.6.1.3.1
avipsConfigurationGroupThis group consists of: 1) Global configuration objects. 2) Isakmp configuration objects. 3) IPsec configuration objects.
Unknown
.1.3.6.1.4.1.6889.2.6.1.3.1.1
avipsMonitorGroupThis group consists of: 1) Global monitoring objects. 2) Peer monitoring objects. 3) IPSec tunnels monitoring objects.
Unknown
.1.3.6.1.4.1.6889.2.6.1.3.1.2
avipsMIBCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.6889.2.6.1.3.2
avipsMIBComplianceThe compliance statement for SNMP entities the IP Security Protocol.
Unknown
.1.3.6.1.4.1.6889.2.6.1.3.2.1
AVAYA-IPSEC-MIB - SNMP MIB Reference | MIBs Explorer