The objects described here can be monitored with the IPHost Network Monitor.
You can start SNMP monitoring using free 30-day trial version of IPHost right now.
OID list for client server status
- Enterasys Load Sharing Network Address Translation Real Server Access Client Row Status
- etsysLsnatRealServerAccessClientRowStatus 1.3.6.1.4.1.5624.1.2.74.2.1.1.4 (defined in enterasys-lsnat-mib)
This object permits management of the table by facilitating actions such as row creation and deletion. The value of this object has no effect on whether other objects in the conceptual row can be modified. The only allowable row status of this conceptual row in the table are: active(1) - The Real Server Access Client entry is available for use in LSNAT operations. createAndGo(4) - This is the preferred mechanism for creating conceptual rows in this table. Errors resulting from invalid etsysLsnatRealServerAccessClientIp and etsysLsnatRealServerAccessClientPrefixLen when creating the LSNAT entry will result in the row not being created. There are no other writable leaves so a successful createAndGo will always transition a new entry to the active(1) state. destroy(6) - This will remove the etsysLsnatRealServerAccessClientEntry from the etsysLsnatRealServerAccessClientTable and make it unavailable for LSNAT operations. - Enterasys Radius Accounting Client Server Status
- etsysRadiusAcctClientServerStatus 1.3.6.1.4.1.5624.1.2.27.1.4.1.10 (defined in enterasys-radius-acct-client-ext-mib)
Lets users create and delete RADIUS Accounting server entries on systems that support this capability. Rules 1. When creating a RADIUS Accounting Client, it is up to the management station to determine a suitable etsysRadiusAcctClientServerIndex. To facilitate interoperability, agents should not put any restrictions on the etsysRadiusAcctClientServerIndex 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 etsysRadiusAcctClientClientServerAddress, and etsysRadiusAcctClientServerSecret. 3. The value of etsysRadiusAcctClientServerStatus must be set to 'notInService' in order to modify a writable object in the same conceptual row. 4. etsysRadiusAcctClientServer entries whose status is 'notReady' or 'notInService' will not be used for Accounting. - Enterasys Radius Authentication Client Server Status Encrypt
- etsysRadiusAuthClientServerStatusEncrypt 1.3.6.1.4.1.5624.1.2.5.1.6.1.7 (defined in enterasys-radius-auth-client-encrypt-mib)
Lets users create and delete RADIUS authentication server entries on systems that support this capability. Rules 1. When creating a RADIUS Authentication Client, it is up to the management station to determine a suitable etsysRadiusAuthServerIndexEncrypt. To facilitate interoperability, agents should not put any restrictions on the etsysRadiusAuthServerIndexEncrypt 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 etsysRadiusAuthClientServerAddressEncrypt, etsysRadiusAuthClientServerPortNumberEncrypt and etsysRadiusAuthClientServerSecretEncrypt. 3. The value of etsysRadiusAuthClientServerStatusEncrypt must be set to 'notInService' in order to modify a writable object in the same conceptual row. 4. etsysRadiusAuthClientServer entries whose status is 'notReady' or 'notInService' will not be used for authentication. - Enterasys Radius Authentication Client Server Status
- etsysRadiusAuthClientServerStatus 1.3.6.1.4.1.5624.1.2.4.1.5.1.8 (defined in enterasys-radius-auth-client-mib)
The row status of this conceptual row in the table. active - The server is available for performing RADIUS operations. Other writable leaves in this row MUST NOT be modified while the row is in the active state. notInService - The entry is fully configured but is not available for performing RADIUS operations. Conceptual rows with this status MAY be deleted at the discretion of the agent, at which time it will be treated as if destroy(6) was SET to this object. notReady - The entry exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instantiated); createAndGo - Not possible. createAndWait - Creates a new instance of a conceptual row, but does not make it available for use by the managed device. destroy - This will remove the conceptual row from the table and make it unavailable for RADIUS client operations. This MUST also cause any persistent data related to this row to be removed from the system. Maintaining active(1) entries across agent reboots is REQUIRED. - Enterasys Sntp Client U Server Last Attempt Status
- etsysSntpClientUServerLastAttemptStatus 1.3.6.1.4.1.5624.1.2.38.1.2.6.1.6 (defined in enterasys-sntp-client-mib)
The status of the last SNTP request to this server since agent reboot. If no requests have been made then this object should return 'other'. - Enterasys Sntp Client U Server Status
- etsysSntpClientUServerStatus 1.3.6.1.4.1.5624.1.2.38.1.2.6.1.9 (defined in enterasys-sntp-client-mib)
The row status of this conceptual row in the table. active - The server is available for use in SNTP client operations. Other writable leaves in this table MAY be modified while the row is in the active state. notInService - The entry is fully configured but is not available for use in SNTP client operations. Conceptual rows with this status MAY be deleted at the discretion of the agent, at which time it will be treated as if destroy(6) was SET to this object. createAndGo - This is the preferred mechanism for creating conceptual rows in this table. All writable leaves have default values so createAndGo will always transition a new entry to the active state. destroy - This will remove the conceptual row from the table and make it unavailable for SNTP client operations. This MUST also cause any persistent data related to this row to be removed from the system. Maintaining active(1) entries across agent reboots is REQUIRED. - Enterasys Tacacs Client Server Status
- etsysTacacsClientServerStatus 1.3.6.1.4.1.5624.1.2.58.1.3.1.1.8 (defined in enterasys-tacacs-client-mib)
Lets 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. - Cisco DNS Client DNS Server Status
- cdcDNSServerStatus 1.3.6.1.4.1.9.9.436.1.1.4.1.4 (defined in CISCO-DNS-CLIENT-MIB)
The Status of this row.
