SHIVA-ACCT-MIB: View SNMP OID List / Download MIB
VENDOR: SHIVA CORPORATION
Home | MIB: SHIVA-ACCT-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 |
acctConf | 1.3.6.1.4.1.166.1.21.1 | |||
acctEnabled | 1.3.6.1.4.1.166.1.21.1.1 | integer | read-only |
Indicates if connection accounting is enabled. Enumeration: 'disabled': 2, 'enabled': 1. |
acctRadiusEnabled | 1.3.6.1.4.1.166.1.21.1.2 | integer | read-only |
Indicates if connection accounting via RADIUS is enabled. See SHIVA-RADIUS-MIB. Enumeration: 'disabled': 2, 'enabled': 1. |
acctEventLogEnabled | 1.3.6.1.4.1.166.1.21.1.3 | integer | read-only |
Indicates if connection accounting via Event Loggging is enabled. Enumeration: 'disabled': 2, 'enabled': 1. |
acctMaxDram | 1.3.6.1.4.1.166.1.21.1.4 | integer | read-only |
Maximum amount of system heap (DRAM) that the connection accounting is allowed to use if non-volatile memory (SRAM) is not available. |
acctMinHeap | 1.3.6.1.4.1.166.1.21.1.5 | integer | read-only |
Minimum amount of system heap (DRAM) that the connection accounting must leave free when using DRAM because non-volatile memory (SRAM) is not available. See memoryFree in SHIVA-MEM-MIB. |
acctMaxSram | 1.3.6.1.4.1.166.1.21.1.6 | integer | read-only |
Maximum amount of system heap (SRAM) that the connection accounting is allowed to use if pre-allocated memory (SRAM) is not available. This variable is not used by the LanRover Access Switch. |
acctStat | 1.3.6.1.4.1.166.1.21.2 | |||
acctCurrentTotalRecordCount | 1.3.6.1.4.1.166.1.21.2.1 | integer | read-only |
The total number of accounting records that are active or are waiting to be safely stored by the active accounting protocols. This includes records in non-volatile (SRAM) and volatile (DRAM) memory. |
acctCurrentVolatileRecordCount | 1.3.6.1.4.1.166.1.21.2.2 | integer | read-only |
The total number of volatile accounting records that are active or are waiting to be safely stored by the active accounting protocols. This includes only accounting events stored in volatile (DRAM) memory, which would be lost in the case of a power failure. |
acctRecordCount | 1.3.6.1.4.1.166.1.21.2.3 | counter | read-only |
The total number of accounting records processed. |
acctEventCount | 1.3.6.1.4.1.166.1.21.2.4 | counter | read-only |
The total number of accounting events processed. |
acctDropCount | 1.3.6.1.4.1.166.1.21.2.5 | counter | read-only |
The total number of accounting records dropped for lack of memory. |
acctLostRecordsRestart | 1.3.6.1.4.1.166.1.21.2.6 | counter | read-only |
The total number of accounting records that were in volatile memory the last time the system restarted, and thus were lost. |
acctLostEventsRestart | 1.3.6.1.4.1.166.1.21.2.7 | counter | read-only |
The total number of accounting events that were in volatile memory the last time the system restarted, and thus were lost. (Events are incomplete components of records.) |
acctTraps | 1.3.6.1.4.1.166.1.21.3 | |||
acctLostRecordTrap | 1.3.6.1.4.1.166.1.21.30.1 |
This trap is generated when the system restarts, and determines that there had been accounting records or events stored in volatile memory when the system went down. Volatile memory being volatile, those records and events have been lost, and will not be sent to an accounting server. |
||
acctMemoryUnavailableTrap | 1.3.6.1.4.1.166.1.21.30.2 |
This trap is generated when the accounting system runs out of volatile memory to store accounting records in. |
||
acctMemoryAvailableTrap | 1.3.6.1.4.1.166.1.21.30.3 |
This trap is generated when the accounting system is no longer out of volatile memory to store accounting records in. |
||
acctVolatileTrap | 1.3.6.1.4.1.166.1.21.30.4 |
This trap is generated when the system runs out of memory in non-volatile memory for accounting records, and starts using volatile memory that could be lost in a power failure. |