MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 172 (ciscoIpSecPolMapMIB). 1 (ciscoIpSecPolMapMIBObjects). 2 (ipSecPhaseTwoPolMap). 1 (ipSecPolMapTable). 1 (ipSecPolMapEntry). 4 (ipSecPolMapAclString)
OID : 1.3.6.1.4.1.9.9.172.1.2.1.1.4
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. ciscoIpSecPolMapMIB. ciscoIpSecPolMapMIBObjects. ipSecPhaseTwoPolMap. ipSecPolMapTable. ipSecPolMapEntry. ipSecPolMapAclString
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.4.1.9.9.172.1.2.1.1.4
Module CISCO-IPSEC-POLICY-MAP-MIB (CISCO)
NomipSecPolMapAclString
Accesreadonly
Statuscurrent
Description The value of this object is the number or the name of the access control string (ACL) that caused this IPSec tunnel to be established. The ACL that causes an IPSec tunnel to be established is referenced by the cryptomap of the tunnel. The ACL identifies the traffic that requires protection as defined by the policy. For instance, the ACL that requires FTP traffic between local subnet 172.16.14.0 and a remote subnet 172.16.16.0 to be protected is defined as ==>access-list 101 permit tcp 172.16.14.0 0.0.0.255 172.16.16.0 0.0.0.255 eq ftp When this command causes an IPSec tunnel to be established, the object 'ipSecPolMapAclString' assumes the string value '101'. If the ACL is a named list such as ==> ip access-list standard myAcl permit 172.16.16.8 0.0.0.0 then the value of this MIB element corresponding to IPSec tunnel that was created by this ACL would be 'myAcl'.
SyntaxeDisplayString (SNMPv2-TC)