CISCO-IP-ENCRYPTION-MIB: View SNMP OID List / Download MIB
VENDOR: CISCO
| Home | MIB: CISCO-IP-ENCRYPTION-MIB | |||
|---|---|---|---|---|
| Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
| Object Name | OID | Type | Access | Info |
| ciscoIpEncryptionMIB | 1.3.6.1.4.1.9.9.52 | |||
| ciscoIpEncryptionMIBObjects | 1.3.6.1.4.1.9.9.52.1 | |||
| cieConfig | 1.3.6.1.4.1.9.9.52.1.1 | |||
| cieConfiguredAlgorithms | 1.3.6.1.4.1.9.9.52.1.1.1 | octet string | read-only |
Type of encryption configured on a particular router, encoded as a bit-string. A router can support multiple encryption algorithms i.e. 56 bit des with 8 bit cipher feedback AND 40 bit des with 64 bit cipher feedback. |
| cieEncryptionKeyTimeout | 1.3.6.1.4.1.9.9.52.1.1.2 | integer32 | read-only |
Interval at which keys expire for a session and they are is re-negotiated. |
| cieNumberOfCryptoEngines | 1.3.6.1.4.1.9.9.52.1.1.3 | gauge32 | read-only |
Total number of encryption engines. |
| cieEngineStatus | 1.3.6.1.4.1.9.9.52.1.2 | |||
| cieEngineStatusTable | 1.3.6.1.4.1.9.9.52.1.2.1 | no-access |
A table describing status of all encryption engines present within the router. |
|
| 1.3.6.1.4.1.9.9.52.1.2.1.1 | no-access |
Each entry in this table describes public key associated with each engine, with its unique ID. In case of hardware assisted encryption each entry also describes status of encryption port adaptor. |
||
| cieEngineID | 1.3.6.1.4.1.9.9.52.1.2.1.1.1 | integer32 | read-only |
Unique value identifying the crypto engine, in case of RP and other software only platforms, this is the processor ID. In case of ESA, this will be a unique ID retrieved from ESA. |
| cieEngineCardIndex | 1.3.6.1.4.1.9.9.52.1.2.1.1.2 | integer32 | read-only |
Corresponds to cardIndex in the chassis mib, if value is 0 then this is a software encryption engine. |
| cieEnginePublicKey | 1.3.6.1.4.1.9.9.52.1.2.1.1.3 | octet string | read-only |
Public key for a particular crypto engine. |
| cieEsaTampered | 1.3.6.1.4.1.9.9.52.1.2.1.1.4 | truthvalue | read-only |
Indicates whether encryption port adaptor has been tampered with. NOTE: This object is not present for software encryption engines. |
| cieEsaAuthenticated | 1.3.6.1.4.1.9.9.52.1.2.1.1.5 | truthvalue | read-only |
Indicates whether encryption port adaptor has been properly authenticated for this router. NOTE: This object is not present for software encryption engines. |
| cieEsaMode | 1.3.6.1.4.1.9.9.52.1.2.1.1.6 | integer | read-only |
Indicates current operating mode of the ESA card. This variable directly corresponds to LED status shown on ESA. NOTE: This object is not present for software encryption engines. Enumeration: 'error': 3, 'boot': 2, 'enableActive': 1. |
| cieConnections | 1.3.6.1.4.1.9.9.52.1.3 | |||
| cieNumberOfConnections | 1.3.6.1.4.1.9.9.52.1.3.1 | gauge32 | read-only |
Total number of active, pending and dead crypto connections. |
| cieConnTable | 1.3.6.1.4.1.9.9.52.1.3.2 | no-access |
A table that describes all encrypted IP traffic created by the router, between the protected entity (cieProtectedAddr) and the unprotected entity (cieUnprotectedAddr). Each entry in this table describes a virtual encrypted IP tunnel. |
|
| 1.3.6.1.4.1.9.9.52.1.3.2.1 | no-access |
This entry describes a connection viz. the protected and unprotected node, status of the connection and number of packets encrypted, decrypted per connection and algorithm used for encrypting data. Each entry also contains a pointer to crypto engine that is performing the encryption. |
||
| cieConnIndex | 1.3.6.1.4.1.9.9.52.1.3.2.1.1 | integer32 | no-access |
A monotonically increasing integer for the sole purpose of indexing the cieConnTable. When it reaches the maximum value, the agent wraps the value back to 1 and may flush existing entries. |
| cieProtectedAddr | 1.3.6.1.4.1.9.9.52.1.3.2.1.2 | ipaddress | read-only |
The IP address for protected (secure) node. |
| cieUnprotectedAddr | 1.3.6.1.4.1.9.9.52.1.3.2.1.3 | ipaddress | read-only |
The IP address of the unprotected (insecure) node in the network. |
| cieConnStatus | 1.3.6.1.4.1.9.9.52.1.3.2.1.4 | integer | read-only |
Integer describing status/type of connection. The pending and bad connections may be removed after 4 minutes of non-activity. Open (active) connections may be removed if they have not transmitted/received traffic in the last cieEncryptionKeyTimeout minutes. Enumeration: 'pendingConnection': 1, 'exchangeKeys': 3, 'badConnection': 4, 'openConnection': 2. |
| ciePktsEncrypted | 1.3.6.1.4.1.9.9.52.1.3.2.1.5 | counter32 | read-only |
Total number of packets encrypted for this connection. |
| ciePktsDecrypted | 1.3.6.1.4.1.9.9.52.1.3.2.1.6 | counter32 | read-only |
Total number of packets decrypted for this connection. |
| ciePktsDropped | 1.3.6.1.4.1.9.9.52.1.3.2.1.7 | counter32 | read-only |
Total number of packets dropped for this connection. The packets are dropped only in cases where encryption keys are not established between the protected entity and the unprotected entity. An increase in this value indicates the possibility of mis-configured keys. |
| cieLocalTimeEstablished | 1.3.6.1.4.1.9.9.52.1.3.2.1.8 | timestamp | read-only |
Value of sysUpTime at which the connection was established or re-established. |
| cieAlgorithmType | 1.3.6.1.4.1.9.9.52.1.3.2.1.9 | integer | read-only |
Type of encryption algorithm used for this connection. Enumeration: 'des40bitCfb64': 3, 'des40bitdesCfb8': 4, 'des56bitCfb64': 1, 'des56bitCfb8': 2. |
| cieTestConnection | 1.3.6.1.4.1.9.9.52.1.4 | |||
| cieTestConnTable | 1.3.6.1.4.1.9.9.52.1.4.1 | no-access |
A table of test crypto session entries. |
|
| 1.3.6.1.4.1.9.9.52.1.4.1.1 | no-access |
A encryption test entry. A management station wishing to create an entry should first generate a pseudo-random serial number to be used as the index to this sparse table. The station should then create the associated instance of the row status and row owner objects. It must also, either in the same or in successive PDUs, create the associated instance of the address objects. Once the appropriate instance of all the configuration objects have been created, either by an explicit SNMP set request, the row status should be set to active to initiate the request. Note that this entire procedure may be initiated via a single set request which specifies a row status of createAndGo. Once the connection sequence has been activated, it cannot be stopped -- it will run until a crypto connection has been established between source and destination. Once the sequence completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out 30 minutes after they are created. |
||
| cieTestConnSerialNumber | 1.3.6.1.4.1.9.9.52.1.4.1.1.1 | integer32 | no-access |
Object which specifies a unique entry in the cieTestConnTable. A management station wishing to initiate a crypto session test operation should use a pseudo-random value for this object when creating an instance of a cieTestConnEntry. The RowStatus semantics of the cieTestConnEntryStatus object will prevent access conflicts. |
| cieTestConnProtectedAddr | 1.3.6.1.4.1.9.9.52.1.4.1.1.2 | ipaddress | read-write |
The IP address of the protected (secure) node, for the test connection. |
| cieTestConnUnprotectedAddr | 1.3.6.1.4.1.9.9.52.1.4.1.1.3 | ipaddress | read-write |
The IP address of the unprotected (insecure) node for the test connection. |
| cieTestConnTrapOnCompletion | 1.3.6.1.4.1.9.9.52.1.4.1.1.4 | truthvalue | read-write |
Specifies whether or not a cieTestCompletion trap should be issued on completion of test crypto session. If such a trap is desired, it is the responsibility of the management entity to ensure that the SNMP administrative model is configured in such a way as to allow the trap to be delivered. |
| cieTestConnCryptoMapName | 1.3.6.1.4.1.9.9.52.1.4.1.1.5 | displaystring | read-write |
Specifies name of the crypto map already configured on the router. A crypto map along with its tag number fully specifies the enryption policy, such as type of algorithm to be used, the name of the peer router and access list. |
| cieTestConnCryptoMapTagNumber | 1.3.6.1.4.1.9.9.52.1.4.1.1.6 | integer32 | read-write |
Specifies tag number of the crypto map already configured on the router. A crypto map along with its tag number fully specifies the enryption policy, such as type of algorithm to be used, the name of the peer router and access list. |
| cieTestConnSessionStatus | 1.3.6.1.4.1.9.9.52.1.4.1.1.7 | integer | read-only |
Set to a value that indicates whether a crypto session was successfully established, failed or the connection establishment process is in progress. If the specified crypto map is not configured, value is set to badCryptoMapName. Enumeration: 'fail': 2, 'inProgress': 1, 'badCryptoMapName': 4, 'success': 3. |
| cieTestConnEntryOwner | 1.3.6.1.4.1.9.9.52.1.4.1.1.8 | ownerstring | read-write |
The entity that configured this entry. |
| cieTestConnEntryStatus | 1.3.6.1.4.1.9.9.52.1.4.1.1.9 | rowstatus | read-write |
The status of this table entry. Once the entry status is set to active, the associate entry cannot be modified until the sequence completes (cieTestConnSessionStatus has value other than inprogress ). |
| cieMIBTrapPrefix | 1.3.6.1.4.1.9.9.52.2 | |||
| cieMIBTraps | 1.3.6.1.4.1.9.9.52.2.0 | |||
| cieMIBConformance | 1.3.6.1.4.1.9.9.52.3 | |||
| cieMIBCompliances | 1.3.6.1.4.1.9.9.52.3.1 | |||
| cieMIBCompliance | 1.3.6.1.4.1.9.9.52.3.1.1 | |||
| cieMIBGroups | 1.3.6.1.4.1.9.9.52.3.2 | |||
| cieMIBGroup | 1.3.6.1.4.1.9.9.52.3.2.1 | |||
| cieTestCompletion | 1.3.6.1.4.1.9.9.52.20.1 |
A cieTestCompletion trap is sent at the completion of a crypto session establishment if such a trap was requested when the sequence was initiated. |
||