ENTERASYS-TLS-MIB
The ENTERASYS-TLS-MIB provides configuration and monitoring controls for Transport Layer Security (TLS) sessions on Enterasys Networks embedded systems, specifically managing the authentication and encryption parameters for remote system management interfaces. This module enables administrators to enforce secure socket connections by exposing TLS-specific state variables and policy settings required for securing SNMP and other management traffic.
Imported Objects
Objects
20 total| Object Name |
|---|
etsysTlsMIBThis MIB module defines a portion of the SNMP enterprise MIBs under Enterasys Networks' enterprise OID pertaining to Transport Layer Security (TLS) system [RFC2246] management functionality, specifically for embedded system implementations. This is a subset of the objects that would be required for a full-featured, host-based implementation. It provides configuration controls for Enterasys Networks' Secure Socket system management -- a feature that enhances system security by authenticating and encrypting the remote system management function. MODULE-IDENTITY .1.3.6.1.4.1.5624.1.2.30 |
etsysTlsObjects OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.30.1 |
etsysTlsGeneralBranch OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.30.1.1 |
etsysTlsEnabledControls 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.rw Enumeration .1.3.6.1.4.1.5624.1.2.30.1.1.1 |
etsysTlsNumSoftConnectsThe 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.rw INTEGER .1.3.6.1.4.1.5624.1.2.30.1.1.2 |
etsysTlsNumHardConnectsThe 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.rw INTEGER .1.3.6.1.4.1.5624.1.2.30.1.1.3 |
etsysTlsMaxHardConnectsThe maximum number of concurrent connections a platform supports. Allows managed entities to enforce implementation specific limits on the upper limit of the etsysTlsNumHardConnects object.ro INTEGER .1.3.6.1.4.1.5624.1.2.30.1.1.4 |
etsysTlsNetworkBranch OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.30.1.2 |
etsysTlsKeepOpenTimeoutHow long in time a 'Keep-Alive' connection is kept open if new requests are not seen. The timeout is given in seconds.rw INTEGER .1.3.6.1.4.1.5624.1.2.30.1.2.1 |
etsysTlsHttpsPortThe TCP port that the HTTPs server will listen to.rw INTEGER .1.3.6.1.4.1.5624.1.2.30.1.2.2 |
etsysTlsServerKeyBranch OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.30.1.3 |
etsysTlsGenerateKeysCauses 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.rw Enumeration .1.3.6.1.4.1.5624.1.2.30.1.3.1 |
etsysTlsAdminKeyTypeDetermines 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.rw Enumeration .1.3.6.1.4.1.5624.1.2.30.1.3.2 |
etsysTlsOperKeyTypeIndicates 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.ro Enumeration .1.3.6.1.4.1.5624.1.2.30.1.3.3 |
etsysTlsSignatureTypeDenotes 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 Hashrw Enumeration .1.3.6.1.4.1.5624.1.2.30.1.3.4 |
etsysTlsConformance OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.30.2 |
etsysTlsGroups OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.30.2.1 |
etsysTlsBaseGroupA collection of objects providing configuration information for the TLS service. Unknown .1.3.6.1.4.1.5624.1.2.30.2.1.1 |
etsysTlsCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.30.2.2 |
etsysTlsComplianceThe compliance statement for devices that support the Enterasys Secure Socket (TLS) MIB. Unknown .1.3.6.1.4.1.5624.1.2.30.2.2.1 |
More MIBs from Enterasys
Browse all EnterasysMIBs →The ENTERASYS-OIDS-MIB module provides the foundational Object Identifier (OID) definitions required for SNMP-based monitoring of Enterasys Networks hardware system attributes, including device identity, software versions, and hardware inventory. It serves as the structural registry enabling network management systems to map and retrieve specific system-level metrics from Enterasys switches, routers, and wireless controllers.
The ENTERASYS-CLASS-OF-SERVICE-MIB manages transmission and reception attributes for Quality of Service (QoS) classification on Extreme Networks (formerly Enterasys) edge and access devices. It enables SNMP-based configuration and monitoring of traffic prioritization policies, including queue mapping, scheduling, and bandwidth allocation parameters.
The ENTERASYS-FIREWALL-MIB enables SNMP-based configuration, policy management, and real-time monitoring of Enterasys firewall appliances, specifically exposing metrics for access control rules, session states, and interface traffic statistics.
The ENTERASYS-LSNAT-MIB provides management access to Layer 4 Session NAT (LSNAT) entities on Enterasys Networks hardware, enabling the monitoring of active session states, translation table entries, and packet/byte counters for protocol-specific NAT mappings.
The ENTERASYS-POLICY-PROFILE-MIB enables SNMP-based monitoring and configuration of per-user policy profiles on Enterasys network edge and access devices. It facilitates the retrieval and management of specific user authentication and authorization parameters, including assigned access control lists and traffic shaping rules, to enforce granular network access policies.
The ENTERASYS-TWCB-MIB-2 module enables monitoring and management of Time-Weighted Cost-Based (TWCB) routing metrics and interface attributes on Enterasys Networks switches. It provides specific counters and gauges for tracking path costs and link states to support advanced traffic engineering and load balancing decisions.