All MIBs › ENTERASYS-RADIUS-DYNAMIC-AUTHOR-SERVER-EXT-MIB › etsysRadiusDynAuthorServerClientStatus
etsysRadiusDynAuthorServerClientStatus
Module: ENTERASYS-RADIUS-DYNAMIC-AUTHOR-SERVER-EXT-MIB
OID (symbolic): ENTERASYS-RADIUS-DYNAMIC-AUTHOR-SERVER-EXT-MIB::etsysRadiusDynAuthorServerClientStatus
OID (numeric): 1.3.6.1.4.1.5624.1.2.80.1.2.1.6
Node type: OBJECT-TYPE
Type: RowStatus
Access: read-create
Description: Lets users create and delete RADIUS Dynamic Authorization client entries on systems that support this capability.
Rules
1. When creating a RADIUS Dynamic Authorization Client, it is up to the management station to determine a suitable etsysRadiusDynAuthorServerClientIndex. To facilitate interoperability, agents SHOULD not put any restrictions on the etsysRadiusDynAuthorServerClientIndex 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 etsysRadiusDynAuthorServerClientAddress, etsysRadiusDynAuthorServerClientSecret, etsysRadiusDynAuthorServerClientAddress, and etsysRadiusDynAuthorClientServerClientVirtualRouterName.
3. The value of etsysRadiusDynAuthorServerClientStatus must be set to 'notInService' in order to modify a writable object in the same conceptual row.
4. etsysRadiusDynAuthorServerClient entries whose status is 'notReady' or 'notInService' will not be used for Dynamic Authorization.
What is etsysRadiusDynAuthorServerClientStatus?
This read-create RowStatus value creates and deletes RADIUS Dynamic Authorization client entries, requiring that the client address, secret, and virtual router name objects all be set before the row can become active, and requiring the row be set to notInService before any writable object in it can be modified; entries in notReady or notInService state are not used for dynamic authorization. An admin follows this multi-step provisioning sequence, setting the address, secret, and virtual router name, then activating the row, to bring a new RADIUS Dynamic Authorization client into service. For example, an admin adding a new client entry would configure its address and secret, then set this object to active, only after which the entry actually participates in processing dynamic authorization requests.
OID Breakdown
Upper-level ancestors (9 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.5624 | enterasys | ENTERASYS-MIB-NAMES |
| 1.3.6.1.4.1.5624.1 | etsysMibs | ENTERASYS-MIB-NAMES |
| 1.3.6.1.4.1.5624.1.2 | etsysModules | ENTERASYS-MIB-NAMES |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.5624.1.2.80 | etsysRadiusDynAuthorServerMIB | ENTERASYS-RADIUS-DYNAMIC-AUTHOR-SERVER-EXT-MIB |
| 1.3.6.1.4.1.5624.1.2.80.1 | etsysRadiusDynAuthorServerMIBObjects | ENTERASYS-RADIUS-DYNAMIC-AUTHOR-SERVER-EXT-MIB |
| 1.3.6.1.4.1.5624.1.2.80.1.2 | etsysRadiusDynAuthorServerClientTable | ENTERASYS-RADIUS-DYNAMIC-AUTHOR-SERVER-EXT-MIB |
| 1.3.6.1.4.1.5624.1.2.80.1.2.1 | etsysRadiusDynAuthorServerClientEntry | ENTERASYS-RADIUS-DYNAMIC-AUTHOR-SERVER-EXT-MIB |
| 1.3.6.1.4.1.5624.1.2.80.1.2.1.6 | etsysRadiusDynAuthorServerClientStatus | ENTERASYS-RADIUS-DYNAMIC-AUTHOR-SERVER-EXT-MIB |