MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 6486 (alcatel). 801 (alcatelIND1BaseMIB). 1 (alcatelIND1Management). 2 (managementIND1Software). 1 (softwareIND1Entities). 43 (softentIND1IPsec). 1 (alcatelIND1IPsecMIB). 1 (alcatelIND1IPsecMIBObjects). 3 (alaIPsecSecurityPolicyRuleTable). 1 (alaIPsecSecurityPolicyRuleEntry). 1 (alaIPsecSecurityPolicyRuleIndex)
OID : 1.3.6.1.4.1.6486.801.1.2.1.43.1.1.3.1.1
TXT : iso. org. dod. internet. private. enterprises. alcatel. alcatelIND1BaseMIB. alcatelIND1Management. managementIND1Software. softwareIND1Entities. softentIND1IPsec. alcatelIND1IPsecMIB. alcatelIND1IPsecMIBObjects. alaIPsecSecurityPolicyRuleTable. alaIPsecSecurityPolicyRuleEntry. alaIPsecSecurityPolicyRuleIndex
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.4.1.6486.801.1.2.1.43.1.1.3.1.1
Module ALCATEL-IND1-IPSEC-MIB (Alcatel)
NomalaIPsecSecurityPolicyRuleIndex
Accesnoaccess
Statuscurrent
DescriptionIndex specifying the order in which multiple rules for the same security policy will be applied. Rules are indexed by the order in which they are applied to the original payload. For example, for a security policy where an IPv6 payload should be protected by an ESP header, which should be protected by an AH header, there would be two Rule Table entries. The ESP entry would have an index of 1 (first rule applied to the payload). The AH entry would have an index of 2 (second rule applied).
SyntaxeUnsigned32 (1...10)