ENTERASYS-TLS-MIB

INTEGER1 = enable2 = disable3 = reinitialize · Integer32

Controls the operation of the Transport Layer Security server task on the embedded system. When enabled, the TLS server will accept connection requests and create a secure transport layer on which to transmit target system configuration data.

INTEGER (1..65535) · Integer32

The soft limit for the maximum number of concurrent connections. If a new connection is initiated and it would exceed the soft limit, a '530 Service Unavailable' error will be reported to the client. Managed entities are free to enforce implementation specific limits on the upper limit of this object.

INTEGER (1..65535) · Integer32

The hard limit for the maximum number of concurrent connections. If a new connection is initiated and it would exceed the hard limit, the connection is closed unconditionally. Managed entities are free to enforce implementation specific limits on the upper limit of this object.

INTEGER (1..65535) · Integer32

The maximum number of concurrent connections a platform supports. Allows managed entities to enforce implementation specific limits on the upper limit of the etsysTlsNumHardConnects object.

INTEGER (1..65535) · Integer32

How long in time a 'Keep-Alive' connection is kept open if new requests are not seen. The timeout is given in seconds.

INTEGER (1..65535) · Integer32

The TCP port that the HTTPs server will listen to.

INTEGER1 = notInitiated2 = completed3 = failed4 = generate5 = completedPending · Integer32

Causes the host to generate a new key pair using the cipher algorithm currently selected in etsysTlsAdminKeyType. Note that this can be compute intensive on many platforms. The meaning of the values are as follows: notInitiated (1) On a write, this is a no-operation, on a read, it indicates that no key material generation operation has ever been initiated, at least since the last reset to factory defaults initialization of the managed entity. No key material exists. completed (2) On a write, this is a no-operation, on a read, this indicates that a key pair has been successfully generated. failed (3) On a write, this is a no-operation, on a read, it indicates that the key generation operation has failed. generate (4) On a write, this causes the managed entity to generate a new key pair, on a read, it indicates that the managed entity is still working on creating the new keys. completedPending (5) On a write, this is a no-operation, on a read, this indicates that a key pair has been successfully generated but its use is pending due to another required operation, such as a reboot.

INTEGER1 = dsa5122 = rsa5123 = dsa7684 = rsa7685 = dsa10246 = rsa10247 = dsa20488 = rsa20489 = dsa307210 = rsa3072 · Integer32

Determines the type of the key to be (re)created on the next key (re)creation operation. The etsysTlsOperKeyType object returns the type of key that is currently being used by the TLS server.

INTEGER1 = dsa5122 = rsa5123 = dsa7684 = rsa7685 = dsa10246 = rsa10247 = dsa20488 = rsa20489 = dsa307210 = rsa307299 = none · Integer32

Indicates the type of the key pair currently in effect on the managed entity. The value of the etsysTlsAdminKeyType object is copied to the etsysTlsOperKeyType object upon successful completion of the (re)creation of a key pair.

INTEGER1 = dhAnon2 = dsaSha13 = dsaSha4 = rsaSha15 = rsaMd26 = rsaMd5 · Integer32

Denotes the signature method that is used for authenticating the exchange of keys. DSS (Digital Signature Standard) DSA (Digital Signature Algorithm, DSS compliant) RSA (Rivest, Shamir and Adelman) Sha (Secure Hash Algorithm) Md5 (Message Digest 5) dhAnon (1) - Anonymous Diffie Hellmen, no signatures dsaSha1 (2) - DSS , Sha-1 Hash dsaSha (3) - DSS signatures, Sha Hash rsaSha1 (4) - RSA signatures, Sha-1 Hash rsaMd2 (5) - RSA signatures, Md2 Hash rsaMd5 (6) - RSA signatures, Md5 Hash