MIB Discovery
1856 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 52 (ciscoIpEncryptionMIB). 1 (ciscoIpEncryptionMIBObjects). 4 (cieTestConnection). 1 (cieTestConnTable). 1 (cieTestConnEntry)
OID : 1.3.6.1.4.1.9.9.52.1.4.1.1
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. ciscoIpEncryptionMIB. ciscoIpEncryptionMIBObjects. cieTestConnection. cieTestConnTable. cieTestConnEntry
Enfants
D├ętails
OID1.3.6.1.4.1.9.9.52.1.4.1.1
Module CISCO-IP-ENCRYPTION-MIB (CISCO)
NomcieTestConnEntry
Statuscurrent
DescriptionA 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.