| CieTestConnEntry |
|
| SEQUENCE |
|
|
|
| |
cieTestConnSerialNumber |
Integer32 |
|
| |
cieTestConnProtectedAddr |
IpAddress |
|
| |
cieTestConnUnprotectedAddr |
IpAddress |
|
| |
cieTestConnTrapOnCompletion |
TruthValue |
|
| |
cieTestConnCryptoMapName |
DisplayString |
|
| |
cieTestConnCryptoMapTagNumber |
Integer32 |
|
| |
cieTestConnSessionStatus |
INTEGER |
|
| |
cieTestConnEntryOwner |
OwnerString |
|
| |
cieTestConnEntryStatus |
RowStatus |
|
| cieEngineStatusEntry |
1.3.6.1.4.1.9.9.52.1.2.1.1 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
CieEngineStatusEntry |
|
|
| cieConnEntry |
1.3.6.1.4.1.9.9.52.1.3.2.1 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
CieConnEntry |
|
|
| cieTestConnEntry |
1.3.6.1.4.1.9.9.52.1.4.1.1 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
CieTestConnEntry |
|
|
| cieTestConnEntryOwner |
1.3.6.1.4.1.9.9.52.1.4.1.1.8 |
| The entity that configured this entry. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
OwnerString |
|
|
| cieTestConnEntryStatus |
1.3.6.1.4.1.9.9.52.1.4.1.1.9 |
| 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 ). |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
RowStatus |
|
|
