Home/Catalog/ENTERASYS-TACACS-CLIENT-MIB

ENTERASYS-TACACS-CLIENT-MIB

AI MIB Summary

The ENTERASYS-TACACS-CLIENT-MIB enables SNMP-based monitoring and configuration of TACACS+ client parameters on Enterasys Networks devices, specifically tracking authentication server connectivity, session states, and access control policy enforcement metrics.

This MIB module defines a portion of the SNMP MIB under the Enterasys Networks enterprise OID pertaining to TACACS+ client configuration.
Main OID:
etsysTacacsClientMIB.1.3.6.1.4.1.5624.1.2.58
34
Objects
Active
Status
7
Dependencies

Imported Objects

Objects

34 total
Object Name
etsysTacacsClientMIBThis MIB module defines a portion of the SNMP MIB under the Enterasys Networks enterprise OID pertaining to TACACS+ client configuration.
MODULE-IDENTITY
.1.3.6.1.4.1.5624.1.2.58
etsysTacacsClientObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.5624.1.2.58.1
etsysTacacsClientControl
OBJECT IDENTIFIER
.1.3.6.1.4.1.5624.1.2.58.1.1
etsysTacacsClientSesnAuthEnabledControls the operation of the TACACS+ client for session authentication and authorization.rw
EnabledStatus (P-BRIDGE-MIB)
.1.3.6.1.4.1.5624.1.2.58.1.1.1
etsysTacacsClientSesnAcctEnabledControls the operation of the TACACS+ client for session accounting.rw
EnabledStatus (P-BRIDGE-MIB)
.1.3.6.1.4.1.5624.1.2.58.1.1.2
etsysTacacsClientCmdAuthEnabledControls the operation of the TACACS+ client for command level authorization.rw
EnabledStatus (P-BRIDGE-MIB)
.1.3.6.1.4.1.5624.1.2.58.1.1.3
etsysTacacsClientCmdAcctEnabledControls the operation of the TACACS+ client for command accounting.rw
EnabledStatus (P-BRIDGE-MIB)
.1.3.6.1.4.1.5624.1.2.58.1.1.4
etsysTacacsClientSingleConnectionAllows the TACACS+ client to send multiple TACACS+ requests on a single TCP connection. All configured TACACS+ servers MUST allow this NAS to use single connection mode.rw
EnabledStatus (P-BRIDGE-MIB)
.1.3.6.1.4.1.5624.1.2.58.1.1.5
etsysTacacsClientSesnAuth
OBJECT IDENTIFIER
.1.3.6.1.4.1.5624.1.2.58.1.2
etsysTacacsClientSesnAuthServiceThe service to be requested for management session authorization.rw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.5624.1.2.58.1.2.1
etsysTacacsClientSesnAuthTableA list of TACACS+ servers that this client may attempt to use.
SEQUENCE OF EtsysTacacsClientSesnAuthEntry
.1.3.6.1.4.1.5624.1.2.58.1.2.2
etsysTacacsClientSesnAuthEntryA TACACS+ server that this client may attempt to use.
EtsysTacacsClientSesnAuthEntry
.1.3.6.1.4.1.5624.1.2.58.1.2.2.1
etsysTacacsClientSesnAuthLevelThe authorization level for the corresponding attribute value pair. Managed entities are not required to support all authorization levels.
Enumeration
.1.3.6.1.4.1.5624.1.2.58.1.2.2.1.1
etsysTacacsClientSesnAuthAttributeThe attribute part of the attribute-value pair for this access level. The default value 'priv-lvl' is normally defined to have a corresponding value part with a value between '0' and '15' inclusive.rw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.5624.1.2.58.1.2.2.1.2
etsysTacacsClientSesnAuthValueThe value part of the attribute-value pair for this access level. To allow the leveraging of existing Cisco 'enable' mode configurations. When 1.) the etsysTacacsClientSesnAuthService object has the value 'enable', 2.) the attribute part of this attribute-value pair is 'priv-lvl', and 3.) the value part of this attribute-value pair represents a numeric value between 0 and 15, inclusive, then the value part of this attribute-value pair specifies the minimum value required for this access level. If any of the above conditions are not met then this value must be an exact match with the value returned from the TACACS+ server. The default values for this object are '0' for read-only, '1' for read-write, and '15' for superuser authorization.rw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.5624.1.2.58.1.2.2.1.3
etsysTacacsClientServer
OBJECT IDENTIFIER
.1.3.6.1.4.1.5624.1.2.58.1.3
etsysTacacsClientServerTableA list of TACACS+ servers that this client may attempt to use.
SEQUENCE OF EtsysTacacsClientServerEntry
.1.3.6.1.4.1.5624.1.2.58.1.3.1
etsysTacacsClientServerEntryA TACACS+ server that this client may attempt to use.
EtsysTacacsClientServerEntry
.1.3.6.1.4.1.5624.1.2.58.1.3.1.1
etsysTacacsClientServerIndexA number uniquely identifying each conceptual row in the etsysTacacsClientServerTable. In the event of an agent restart, the same value of etsysTacacsClientServerIndex must be used to identify each conceptual row in etsysTacacsClientServerTable as prior to the restart.
Integer32
.1.3.6.1.4.1.5624.1.2.58.1.3.1.1.1
etsysTacacsClientServerAddressTypeThe type of Internet address by which this TACACS+ server is reachable.rw
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.5624.1.2.58.1.3.1.1.2
etsysTacacsClientServerAddressThe Internet address for the TACACS+ server. The etsysTacacsClientServerAddress may not be empty due to the SIZE restriction. Also the size of a DNS name is limited to 64 characters. If a row is created administratively by an SNMP operation and the address type value is dns(16), then the agent stores the DNS name internally. A DNS name lookup must be performed on the internally stored DNS name whenever it is being used to contact the peer. If a row is created by the managed entity itself and the address type value is dns(16), then the agent stores the IP address internally. A DNS reverse lookup must be performed on the internally stored IP address whenever the value is retrieved via SNMP.rw
InetAddress
.1.3.6.1.4.1.5624.1.2.58.1.3.1.1.3
etsysTacacsClientServerPortNumberThe TCP port number (0-65535) the client is using to send requests to this server.rw
InetPortNumber (INET-ADDRESS-MIB)
.1.3.6.1.4.1.5624.1.2.58.1.3.1.1.4
etsysTacacsClientServerTimeoutThe number of seconds to wait for a TACACS+ server to respond to a request.rw
Integer32
.1.3.6.1.4.1.5624.1.2.58.1.3.1.1.5
etsysTacacsClientServerSecretThis object is the secret shared between the TACACS+ server and TACACS+ client.rw
OCTET STRING
.1.3.6.1.4.1.5624.1.2.58.1.3.1.1.6
etsysTacacsClientServerSecretEnteredThis indicates the existence of a shared secret.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.5624.1.2.58.1.3.1.1.7
etsysTacacsClientServerStatusLets users create and delete TACACS+ server entries on systems that support this capability. Rules 1. When creating a TACACS+ client, it is up to the management station to determine a suitable etsysTacacsClientServerIndex. To facilitate interoperability, agents should not put any restrictions on the etsysTacacsClientServerIndex beyond the obvious ones that it be valid and unused. 2. Before a new row can become 'active', values must be supplied for the columnar objects etsysTacacsClientServerAddress and etsysTacacsClientServerSecret. 3. The value of etsysTacacsClientServerStatus MAY need to be set to 'notInService' in order to modify a writable object in the same conceptual row. 4. etsysTacacsClientServer entries whose status is 'notReady' or 'notInService' will not be used for authentication.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.5624.1.2.58.1.3.1.1.8
etsysTacacsClientConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.5624.1.2.58.2
etsysTacacsClientCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.5624.1.2.58.2.1
etsysTacacsClientComplianceThe compliance statement for clients implementing the TACACS+ Client MIB.
Unknown
.1.3.6.1.4.1.5624.1.2.58.2.1.1
etsysTacacsClientGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.5624.1.2.58.2.2
etsysTacacsClientSessionGroupThe collection of objects required to do TACACS+ authentication, authorization, and accounting for management sessions.
Unknown
.1.3.6.1.4.1.5624.1.2.58.2.2.1
etsysTacacsClientCmdAuthGroupAdditional objects for TACACS+ command authorization.
Unknown
.1.3.6.1.4.1.5624.1.2.58.2.2.2
etsysTacacsClientCmdAcctGroupAdditional objects for TACACS+ command accounting.
Unknown
.1.3.6.1.4.1.5624.1.2.58.2.2.3
etsysTacacsClientSesnAuthGroupAdditional objects to map read-only, read-write, superuser, and debug authorization level into a service level and respective attribute-value pairs.
Unknown
.1.3.6.1.4.1.5624.1.2.58.2.2.4

More MIBs from Enterasys

Browse all EnterasysMIBs →
ENTERASYS-OIDS-MIB

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.

678 objects→
ENTERASYS-CLASS-OF-SERVICE-MIB

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.

361 objects→
ENTERASYS-FIREWALL-MIB

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.

220 objects→
ENTERASYS-LSNAT-MIB

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.

177 objects→
ENTERASYS-POLICY-PROFILE-MIB

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.

165 objects→
ENTERASYS-TWCB-MIB-2

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.

134 objects→