TN-SECURITY-AAA-MIB: View SNMP OID List / Download MIB
VENDOR: TRANSITION ENGINEERING INC.
Home | MIB: TN-SECURITY-AAA-MIB | |||
---|---|---|---|---|
Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
Object Name | OID | Type | Access | Info |
tnSecurityAAAMIB | 1.3.6.1.4.1.868.2.5.3.1.1.20 | |||
tnAAAServerTimeout | 1.3.6.1.4.1.868.2.5.3.1.1.20.1 | integer | read-write |
Common Configuration Server Timeout (seconds). |
tnAAAServerDeadTime | 1.3.6.1.4.1.868.2.5.3.1.1.20.2 | integer | read-write |
Common Configuration Server Dead Time (seconds). |
tnAAAServerTable | 1.3.6.1.4.1.868.2.5.3.1.1.20.3 | no-access |
AAA Server Table |
|
1.3.6.1.4.1.868.2.5.3.1.1.20.3.1 | no-access |
Each entry represents a Server on a device. |
||
tnAAAProtocol | 1.3.6.1.4.1.868.2.5.3.1.1.20.3.1.1 | tnaaaprotocol | no-access |
The variable denotes the protocol used by the managed device with the AAA server corresponding to this entry in the table. |
tnAAAType | 1.3.6.1.4.1.868.2.5.3.1.1.20.3.1.2 | tnaaatype | no-access |
AAA commonly stands for authentication, authorization and accounting. It refers to a security architecture for distributed systems, which enables control over which users are allowed access to which services, and how much of the resources they have used. |
tnAAAServerIndex | 1.3.6.1.4.1.868.2.5.3.1.1.20.3.1.3 | unsigned32 | no-access |
A management station wishing to initiate a new AAA server configuration should use a random value for this object when creating an instance of tnAAAServerEntry. |
tnAAAServerEnable | 1.3.6.1.4.1.868.2.5.3.1.1.20.3.1.4 | truthvalue | read-write |
To enable or disable a server. |
tnAAAServerAddrType | 1.3.6.1.4.1.868.2.5.3.1.1.20.3.1.5 | inetaddresstype | read-write |
The IP address type of the server. For a detailed description of this type, please refer to INET-ADDRESS-MIB. |
tnAAAServerAddr | 1.3.6.1.4.1.868.2.5.3.1.1.20.3.1.6 | inetaddress | read-write |
The IP address of the server. For a detailed description of this type, please refer to INET-ADDRESS-MIB. |
tnAAAServerPort | 1.3.6.1.4.1.868.2.5.3.1.1.20.3.1.7 | integer | read-write |
The port to use on theServer. |
tnAAAServerSecret | 1.3.6.1.4.1.868.2.5.3.1.1.20.3.1.8 | displaystring | read-write |
The secret - up to 29 characters long - shared between the Server and the switch. |
tnStatisticsTable | 1.3.6.1.4.1.868.2.5.3.1.1.20.4 | no-access |
Table providing statistics for each server. |
|
1.3.6.1.4.1.868.2.5.3.1.1.20.4.1 | no-access |
Statistical information about a particular server. Objects in this table are read-only and appear automatically whenever a row in the tnStatisticsTable is made active. |
||
tnAcceptPkts | 1.3.6.1.4.1.868.2.5.3.1.1.20.4.1.1 | counter32 | read-only |
The number of Accept packets (valid or invalid) received from the server. |
tnRejectPkts | 1.3.6.1.4.1.868.2.5.3.1.1.20.4.1.2 | counter32 | read-only |
The number of Reject packets (valid or invalid) received from the server. |
tnChallengesPkts | 1.3.6.1.4.1.868.2.5.3.1.1.20.4.1.3 | counter32 | read-only |
The number of Challenge packets (valid or invalid) received from the server. |
tnMalResponsePkts | 1.3.6.1.4.1.868.2.5.3.1.1.20.4.1.4 | counter32 | read-only |
The number of malformed packets received from the server. Malformed packets include packets with an invalid length. Bad authenticators or Message Authenticator attributes or unknown types are not included as malformed access responses. |
tnBadAuthPkts | 1.3.6.1.4.1.868.2.5.3.1.1.20.4.1.5 | counter32 | read-only |
The number of packets containing invalid authenticators or Message Authenticator attributes received from the server. |
tnUnknownTypePkts | 1.3.6.1.4.1.868.2.5.3.1.1.20.4.1.6 | counter32 | read-only |
The number of packets of unknown types that were received from the server on the port. |
tnDroppedPkts | 1.3.6.1.4.1.868.2.5.3.1.1.20.4.1.7 | counter32 | read-only |
The number of packets that were received from the server on the port and dropped for some other reason. |
tnRequestPkts | 1.3.6.1.4.1.868.2.5.3.1.1.20.4.1.8 | counter32 | read-only |
The number of packets sent to the server. This does not include retransmissions. |
tnRetransPkts | 1.3.6.1.4.1.868.2.5.3.1.1.20.4.1.9 | counter32 | read-only |
The number of packets retransmitted to the server. |
tnPendRequestPkts | 1.3.6.1.4.1.868.2.5.3.1.1.20.4.1.10 | counter32 | read-only |
The number of packets destined for the server that have not yet timed out or received a response. This variable is incremented when a Request is sent and decremented due to receipt of a Response, timeout, or retransmission. |
tnTimeouts | 1.3.6.1.4.1.868.2.5.3.1.1.20.4.1.11 | counter32 | read-only |
The number of timeouts to the server. After a timeout, the client may retry to the same server, send to a different server, or give up. A retry to the same server is counted as a retransmit as well as a timeout. A send to a different server is counted as a Request as well as a timeout. |
tnState | 1.3.6.1.4.1.868.2.5.3.1.1.20.4.1.12 | integer | read-only |
Shows the state of the server. It takes one of the following values: Disabled - The selected server is disabled. Not Ready - The server is enabled, but IP communication is not yet up and running. Ready - The server is enabled, IP communication is up and running, and the module is ready to accept accounting or access attempts. Dead - Accounting or access attempts were made to this server, but it did not reply within the configured timeout. The server has temporarily been disabled, but will get re-enabled when the dead-time expires. The number of seconds left before this occurs is displayed in parentheses. This state is only reachable when more than one server is enabled. Enumeration: 'disabled': 1, 'notready': 2, 'ready': 3, 'dead': 4. |
tnRoundTripTime | 1.3.6.1.4.1.868.2.5.3.1.1.20.4.1.13 | counter32 | read-only |
The time interval (measured in milliseconds) between the most recent Response and the Request that matched it from the server. The granularity of this measurement is 100 ms. A value of 0 ms indicates that there hasn't been round-trip communication with the server yet. |