CISCO-IPSEC-POLICY-MAP-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for CISCO-IPSEC-POLICY-MAP-MIB.
23
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
23 total| Object Name |
|---|
ciscoIpSecPolMapMIB OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.172 |
SNMPv2-SMI-v1 Unknown .1.3.6.1.4.1.9.9.172 |
ciscoIpSecPolMapMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.172.1 |
ipSecPhaseOnePolMap OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.172.1.1 |
ikePolMapTableThe IPSec Phase-1 Internet Key Exchange Tunnel
to Policy Mapping Table. There is one entry in
this table for each active IPSec Phase-1
Tunnel. SEQUENCE OF IkePolMapEntry .1.3.6.1.4.1.9.9.172.1.1.1 |
ikePolMapEntryEach entry contains the attributes associated
with mapping an active IPSec Phase-1 IKE Tunnel
to it's configured Policy definition. IkePolMapEntry .1.3.6.1.4.1.9.9.172.1.1.1.1 |
ikePolMapTunIndexThe index of the IPSec Phase-1 Tunnel to Policy
Map Table. The value of the index is the number
used to represent this IPSec Phase-1 Tunnel in
the IPSec MIB (ikeTunIndex in the
ikeTunnelTable). Integer32 .1.3.6.1.4.1.9.9.172.1.1.1.1.1 |
ikePolMapPolicyNumThe number of the locally defined ISAKMP policy
used to establish the IPSec IKE Phase-1 Tunnel.
This is the number which was used on the crypto
command. For example, if the configuration command
was:
==> crypto isakmp policy 15
then the value of this object would be 15.
If ISAKMP was not used to establish this tunnel,
then the value of this object will be zero.ro Integer32 .1.3.6.1.4.1.9.9.172.1.1.1.1.2 |
ipSecPhaseTwoPolMap OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.172.1.2 |
ipSecPolMapTableThe IPSec Phase-2 Tunnel to Policy Mapping Table.
There is one entry in this table for each active
IPSec Phase-2 Tunnel. SEQUENCE OF IpSecPolMapEntry .1.3.6.1.4.1.9.9.172.1.2.1 |
ipSecPolMapEntryEach entry contains the attributes associated
with mapping an active IPSec Phase-2 Tunnel
to its configured Policy definition. IpSecPolMapEntry .1.3.6.1.4.1.9.9.172.1.2.1.1 |
ipSecPolMapTunIndexThe index of the IPSec Phase-2 Tunnel to Policy
Map Table. The value of the index is the number
used to represent this IPSec Phase-2 Tunnel in
the IPSec MIB (ipSecTunIndex in the
ipSecTunnelTable). Integer32 .1.3.6.1.4.1.9.9.172.1.2.1.1.1 |
ipSecPolMapCryptoMapNameThe value of this object should be the name of
the IPSec Policy (cryptomap) as assigned by the
operator while configuring the policy of
the IPSec traffic.
For instance, on an IOS router, the if the command
entered to configure the IPSec policy was
==> crypto map ftpPolicy 10 ipsec-isakmp
then the value of this object would be 'ftpPolicy'.ro DisplayString -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.9.172.1.2.1.1.2 |
ipSecPolMapCryptoMapNumThe value of this object should be the priority
of the IPSec Policy (cryptomap) assigned by the
operator while configuring the policy of
this IPSec tunnel.
For instance, on an IOS router, the if the command
entered to configure the IPSec policy was
==> crypto map ftpPolicy 10 ipsec-isakmp
then the value of this object would be 10.ro Integer32 .1.3.6.1.4.1.9.9.172.1.2.1.1.3 |
ipSecPolMapAclStringThe 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'.ro DisplayString -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.9.172.1.2.1.1.4 |
ipSecPolMapAceStringThe value of this object is the access control
entry (ACE) within the ACL that caused this IPSec
tunnel to be established.
For instance, if an ACL defines access for two
traffic streams (FTP and SNMP) as follows:
access-list 101 permit tcp 172.16.14.0 0.0.0.255
172.16.16.0 0.0.0.255 eq ftp
access-list 101 permit udp 172.16.14.0 0.0.0.255
host 172.16.16.1 eq 161
When associated with an IPSec policy, the second
element of the ACL gives rise to an IPSec tunnel
in the wake of SNMP traffic. The value of the
object 'ipSecPolMapAceString' for the IPSec tunnel
would be then the string
'access-list 101 permit udp 172.16.14.0 0.0.0.255
host 172.16.16.1 eq 161'ro DisplayString -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.9.172.1.2.1.1.5 |
ciscoIpSecPolMapMIBNotifPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.172.2 |
ciscoIpSecPolMapMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.172.3 |
ipSecPolMapMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.172.3.1 |
ipSecPhaseOnePolMapGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.172.3.1.1 |
ipSecPhaseTwoPolMapGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.172.3.1.2 |
ipSecPolMapMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.172.3.2 |
ipSecPolMapMIBCompliance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.172.3.2.1 |