tmnxRadIsaPlcySrvAlgorithm

TIMETRA-RADIUS-MIB · .1.3.6.1.4.1.6527.3.1.2.79.1.6.1.1.106

Object

The value of tmnxRadIsaPlcySrvAlgorithm specifies the algorithm used
to select a RADIUS server from the list of configured servers
(tmnxRadIsaSrvTable).

Context

MIB
TIMETRA-RADIUS-MIB
OID
.1.3.6.1.4.1.6527.3.1.2.79.1.6.1.1.106
Type
column
Access
readwrite
Status
current
Default
direct
Parent
tmnxRadIsaPlcyEntry
Groups
1

Walk the column to discover its indexed instances, or supply every index to read one instance.

Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'TIMETRA-RADIUS-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-RADIUS-MIB::tmnxRadIsaPlcySrvAlgorithm'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'TIMETRA-RADIUS-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-RADIUS-MIB::tmnxRadIsaPlcySrvAlgorithm.<tmnxRadIsaPlcyName>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-RADIUS-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-RADIUS-MIB::tmnxRadIsaPlcySrvAlgorithm'

Syntax

Source
TIMETRA-TC-MIBTmnxSubRadIsaServAlgorithm
Base type
Enumeration
Type Description
The TmnxSubRadIsaServAlgorithm data type is an enumerated integer that
indicates the algorithm used to access the list of configured RADIUS
servers:
- direct         (1): The first server will be used as primary server for
                       all requests, the second as secondary and so on.
- roundRobin     (2): The first server will be used as primary server for
                       the first request, the second server as primary for
                       the second request, and so on. If the router gets
                       to the end of the list, it starts again with the
                       first server.
- hashBased      (3): The server will be selected based on a specified
                       hash value.
- directPriority (4): The first server will be used as primary server for
                       all requests, the second as secondary and so on.
                       Higher priority servers that are operationally down
                       will be probed and put back into service upon a
                       response.

Values & Constraints

Type Values
1direct
2roundRobin
3hashBased
4directPriority

Conformance