CISCO-CRYPTO-ACCELERATOR-MIB

        The MIB module for monitoring the identity, status,
activity and faults of crypto accelerator (CA) modules
used in devices implementing security services.
        
  The purpose of this MIB is to facilitate the following:
    1) facilitate the discovery of hardware crypto 
     accelerator modules installed in a security device
    2) monitor the activity, faults and performance of 
     hardware crypto accelerators and help the Network 
     Management Station (NMS) correlate the performance 
     of the CA modules with that of the security services 
     (IPsec, SSL, SSH, PKI etc) using the modules.
    
Source file
CISCO-CRYPTO-ACCELERATOR-MIB
Last revised
Identity
ciscoCryptoAcceleratorMIB
Base OID
1.3.6.1.4.1.9.9.467
Imported Objects
CISCO-ENTITY-FRU-CONTROL-MIB ModuleOperType
CISCO-SMI ciscoMgmt
CISCO-TC EntPhysicalIndexOrZero
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter64 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) TimeTicks Unsigned32
SNMPv2-TC TEXTUAL-CONVENTION (no object page) TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-CRYPTO-ACCELERATOR-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-CRYPTO-ACCELERATOR-MIB::ciscoCryptoAcceleratorMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-CRYPTO-ACCELERATOR-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-CRYPTO-ACCELERATOR-MIB::ciscoCryptoAcceleratorMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (81)
.1.3.6.1.4.1.9.9.467
.1.3.6.1.4.1.9.9.467.0
.1.3.6.1.4.1.9.9.467.1
.1.3.6.1.4.1.9.9.467.1.1
.1.3.6.1.4.1.9.9.467.1.1.1
.1.3.6.1.4.1.9.9.467.1.1.2
Integer32
.1.3.6.1.4.1.9.9.467.1.1.3
megabits per secondSNMPv2-SMIUnsigned32
.1.3.6.1.4.1.9.9.467.1.1.4
.1.3.6.1.4.1.9.9.467.1.1.5
.1.3.6.1.4.1.9.9.467.1.2
.1.3.6.1.4.1.9.9.467.1.2.1
.1.3.6.1.4.1.9.9.467.1.2.1.1
.1.3.6.1.4.1.9.9.467.1.2.1.2
.1.3.6.1.4.1.9.9.467.1.2.1.3
.1.3.6.1.4.1.9.9.467.1.2.1.4
.1.3.6.1.4.1.9.9.467.1.2.1.5
.1.3.6.1.4.1.9.9.467.1.2.1.6
.1.3.6.1.4.1.9.9.467.1.2.1.7
.1.3.6.1.4.1.9.9.467.1.2.2
.1.3.6.1.4.1.9.9.467.1.2.2.1
Unsigned32
.1.3.6.1.4.1.9.9.467.1.2.2.1.1
.1.3.6.1.4.1.9.9.467.1.2.2.1.10
.1.3.6.1.4.1.9.9.467.1.2.2.1.11
.1.3.6.1.4.1.9.9.467.1.2.2.1.12
.1.3.6.1.4.1.9.9.467.1.2.2.1.13
.1.3.6.1.4.1.9.9.467.1.2.2.1.14
.1.3.6.1.4.1.9.9.467.1.2.2.1.15
.1.3.6.1.4.1.9.9.467.1.2.2.1.16
.1.3.6.1.4.1.9.9.467.1.2.2.1.17
.1.3.6.1.4.1.9.9.467.1.2.2.1.18
.1.3.6.1.4.1.9.9.467.1.2.2.1.19
.1.3.6.1.4.1.9.9.467.1.2.2.1.2
.1.3.6.1.4.1.9.9.467.1.2.2.1.20
.1.3.6.1.4.1.9.9.467.1.2.2.1.21
.1.3.6.1.4.1.9.9.467.1.2.2.1.22
.1.3.6.1.4.1.9.9.467.1.2.2.1.23
.1.3.6.1.4.1.9.9.467.1.2.2.1.24
.1.3.6.1.4.1.9.9.467.1.2.2.1.25
.1.3.6.1.4.1.9.9.467.1.2.2.1.26
.1.3.6.1.4.1.9.9.467.1.2.2.1.27
.1.3.6.1.4.1.9.9.467.1.2.2.1.28
.1.3.6.1.4.1.9.9.467.1.2.2.1.29
.1.3.6.1.4.1.9.9.467.1.2.2.1.3
.1.3.6.1.4.1.9.9.467.1.2.2.1.30
.1.3.6.1.4.1.9.9.467.1.2.2.1.31
.1.3.6.1.4.1.9.9.467.1.2.2.1.32
.1.3.6.1.4.1.9.9.467.1.2.2.1.33
.1.3.6.1.4.1.9.9.467.1.2.2.1.34
.1.3.6.1.4.1.9.9.467.1.2.2.1.35
.1.3.6.1.4.1.9.9.467.1.2.2.1.36
.1.3.6.1.4.1.9.9.467.1.2.2.1.37
.1.3.6.1.4.1.9.9.467.1.2.2.1.38
.1.3.6.1.4.1.9.9.467.1.2.2.1.4
.1.3.6.1.4.1.9.9.467.1.2.2.1.5
.1.3.6.1.4.1.9.9.467.1.2.2.1.6
.1.3.6.1.4.1.9.9.467.1.2.2.1.7
.1.3.6.1.4.1.9.9.467.1.2.2.1.8
.1.3.6.1.4.1.9.9.467.1.2.2.1.9
.1.3.6.1.4.1.9.9.467.1.2.3
.1.3.6.1.4.1.9.9.467.1.2.3.1
.1.3.6.1.4.1.9.9.467.1.2.3.1.1
.1.3.6.1.4.1.9.9.467.1.2.3.1.1.1
.1.3.6.1.4.1.9.9.467.1.2.3.1.1.10
.1.3.6.1.4.1.9.9.467.1.2.3.1.1.11
.1.3.6.1.4.1.9.9.467.1.2.3.1.1.12
.1.3.6.1.4.1.9.9.467.1.2.3.1.1.2
.1.3.6.1.4.1.9.9.467.1.2.3.1.1.3
.1.3.6.1.4.1.9.9.467.1.2.3.1.1.4
.1.3.6.1.4.1.9.9.467.1.2.3.1.1.5
.1.3.6.1.4.1.9.9.467.1.2.3.1.1.6
.1.3.6.1.4.1.9.9.467.1.2.3.1.1.7
.1.3.6.1.4.1.9.9.467.1.2.3.1.1.8
.1.3.6.1.4.1.9.9.467.1.2.3.1.1.9
.1.3.6.1.4.1.9.9.467.1.3
.1.3.6.1.4.1.9.9.467.1.3.1
.1.3.6.1.4.1.9.9.467.1.3.2
.1.3.6.1.4.1.9.9.467.1.3.3
.1.3.6.1.4.1.9.9.467.1.3.4
.1.3.6.1.4.1.9.9.467.2
.1.3.6.1.4.1.9.9.467.2.1
.1.3.6.1.4.1.9.9.467.2.2
Dependencies (11) 7 direct · 4 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (3)
Unsigned32
Enumeration
other(1)
software(2)
integrated(3)
sep(4)
sepe(5)
a1700VpnModule(6)
aimVpnIBp(7)
aimVpnIEp(8)
aimVpnIIBp(9)
aimVpnIIEp(10)
aimVpnIIHp(11)
isa(12)
vam(13)
vam2(14)
vam2plus(15)
vpnsm(16)
caviumNitrox(17)
caviumNitroxII(18)
caviumNitroxLite(19)
Enumeration
other(1)
ikev1(2)
ikev2(3)
ipsec(4)
ssl(5)
ssh(6)
srtp(7)
Conformance Groups (6)
This group consists of all the MIB variables
defined under crAcCapacity using which the management
station may determine the limits of capacity of the
managed device with regards to the support of
crypto accelerators.
.1.3.6.1.4.1.9.9.467.2.2.1
This group consists of the counters which model the
summary activity of the crypto accelerators in the
managed entity.
.1.3.6.1.4.1.9.9.467.2.2.2
This group consists of the counters which model the
summary activity of the crypto accelerators in the
managed entity.

Following are definitions of some terms used in
this compliance group:

Crypto Accelerator
'Crypto Accelerator' denotes a hardware or software
device which the managed entity uses to offload some
or all computations pertaining to cryptographic
operations. A crypto accelerator module may be
implemented as a Field Removable Unit or an
integrated hardware element such an Application
Specific Integrated Chip (ASIC).

Module
The term 'Module' has been used in this MIB to
denote a hardware crypto accelerator.

Diffie-Hellman
The Diffie-Hellman key agreement protocol (also called
exponential key agreement) was developed by Diffie and
Hellman in 1976. The protocol allows two users to
exchange a secret key over an insecure medium without
any prior secrets.

RSA
An Internet encryption and authentication system that
uses an algorithm developed in 1977 by Ron Rivest,
Adi Shamir, and Leonard Adleman.

DSS
Digital Signature Standard (DSS) is the digital
signature algorithm (DSA) developed by the U.S.
National Security Agency (NSA) to generate a digital
signature for the authentication of electronic
documents.

IPsec
IP security protocol.

SSL
Secure Socket Layer Protocol.

SSH
Secure Shell Protocol.

PKI
Public Key Infrastructure
.1.3.6.1.4.1.9.9.467.2.2.3
This group consists of the counters which model
the protocol-specific activity of the crypto
accelerators in the managed entity.
.1.3.6.1.4.1.9.9.467.2.2.4
This group consists of all the MIB variables which
allow the network management station to control the
emission of the notifications defined in this MIB.

Per a different compliance clause dfined in this
module, the agent is not required to provide write
access to these MIB variables.
.1.3.6.1.4.1.9.9.467.2.2.5
This group consists of all the notifications defined
to signal the change in status and operation of crypto
accelerator modules.
.1.3.6.1.4.1.9.9.467.2.2.6
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.467.2.1.1
The compliance statement for entities which
implement the CISCO Crypto Accelerator MIB.
Required groups
mandatory ciscoCryAccCapacityGroup
mandatory ciscoCryAccSummaryActivityGroup
optional ciscoCryAccModuleActivityGroup This group is optional.
optional ciscoCryAccProtocolActivityGroup This group is optional.
optional ciscoCryAccNotifsGroup This group is optional.
optional ciscoCryAccNotifsCntlGroup This group is mandatory if and only if
the SNMP agent on the managed entity
implements the group 'ciscoCryAccNotifsGroup'.
Notifications / Traps (4)
NameOIDDescription
.1.3.6.1.4.1.9.9.467.0.1
A crypto accelerator module has been inserted into the
managed device.
.1.3.6.1.4.1.9.9.467.0.2
A crypto accelerator module has been removed from the
managed device.
.1.3.6.1.4.1.9.9.467.0.3
A crypto accelerator module has become operational.
.1.3.6.1.4.1.9.9.467.0.4
A crypto accelerator module has become non-operational.