ENTERASYS-RADIUS-ACCT-CLIENT-EXT-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ENTERASYS-RADIUS-ACCT-CLIENT-EXT-MIB

Organization: Enterasys Networks

Last Updated: 2009-08-07

Category: Protocol: RADIUS, RADIUS and AAA, Vendor: Enterasys/Cabletron

Description: Enterasys Networks RADIUS accounting client extension MIB providing writable configuration objects beyond RFC 2620.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is ENTERASYS-RADIUS-ACCT-CLIENT-EXT-MIB?

This Enterasys Networks enterprise MIB extends the standard RADIUS Accounting Client MIB (RFC 2620) with additional read-write configuration objects for the RADIUS accounting client function on a switch, covering global enable/interval settings and a table of accounting server destinations. It provides configuration data such as update interval, minimum retry interval, and per-server address, port, shared secret, and retry-timeout objects. Its monitoring relevance is largely configuration/status-oriented rather than counter-based: it lets an operator confirm which RADIUS accounting servers are configured and reachable, and whether accounting is currently enabled, foundational to verifying that user session accounting records are actually generated and sent. It explicitly depends on and supplements RFC 2620 (RADIUS Accounting Client MIB) and by extension RFC 2866 (RADIUS Accounting protocol). It is deployed on Enterasys switches and wireless controllers that perform RADIUS accounting for authenticated user sessions, tracked via the ENTERASYS-RADIUS-ACCT-CLIENT-EXT-MIB MIB.

IPNetwork Monitor allows you to monitor SNMP objects defined in ENTERASYS-RADIUS-ACCT-CLIENT-EXT-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Enterasys switch or wireless controller

Monitoring Examples

An administrator would inspect etsysRadiusAcctClientServerTable/etsysRadiusAcctClientServerEntry (indexed by etsysRadiusAcctClientServerIndex) to confirm the etsysRadiusAcctClientServerAddress and etsysRadiusAcctClientServerPortNumber match the intended accounting server, and check etsysRadiusAcctClientEnable to verify accounting is turned on. If accounting records are missing, etsysRadiusAcctClientServerRetryTimeout and etsysRadiusAcctClientUpdateInterval would be reviewed to rule out a timing mismatch with the RADIUS server.

What Can Be Monitored

  • RADIUS accounting client enable status
  • accounting update interval
  • configured accounting server addresses/ports
  • accounting server retry timeout
  • shared secret configuration status
Imported Objects

From ENTERASYS-MIB-NAMES

etsysModulesOBJECT-IDENTITY

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

RowStatus
TruthValue
OIDs

RFC description

Extended RADIUS accounting client configuration for Enterasys networks beyond standard RFC2620.

Start monitoring Enterasys/Extreme Networks wireless switch/controller (RADIUS accounting client extensions) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download ENTERASYS-RADIUS-ACCT-CLIENT-EXT-MIB