SCSP-MIB: View SNMP OID List / Download MIB
VENDOR: INTERNET-STANDARD
Home | MIB: SCSP-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 |
scspMIB | 1.3.6.1.3.2001 |
This module defines a portion of the management information base (MIB) for managing Server Cache Synchronization protocols entities. |
||
scspObjects | 1.3.6.1.3.2001.1 | |||
scspServerGroupTable | 1.3.6.1.3.2001.1.1 | no-access |
The objects defined in this table are used to for the management of server groups. There is one entry in this table for each server group. |
|
1.3.6.1.3.2001.1.1.1 | no-access |
Each entry contains attributes associated with a scsp server group. |
||
scspServerGroupID | 1.3.6.1.3.2001.1.1.1.1 | integer32 | no-access |
This is the Group ID of this SCSP server group instance. |
scspServerGroupPID | 1.3.6.1.3.2001.1.1.1.2 | scsppidtype | no-access |
This is the protocol ID of this SCSP server group instance. |
scspServerGroupRowStatus | 1.3.6.1.3.2001.1.1.1.3 | rowstatus | read-only |
This object allows entries to be created and deleted from the scspServerGroupTable. This table is closely coupled with the scspLSTable, scspDCSTable, and the corresponding protocol dependent tables. A new row creation in this table results in creation of corresponding entries in the scspLSTable and scspDCSTable. In addition, entries in appropriate protocol dependent table may also be added. When the scspServerRowStatus is deleted by setting this object to destroy(6), this results in removing corresponding entries in scspLSTable, scspDCSTable, and those in corresponding protocol dependent table. |
scspLSTable | 1.3.6.1.3.2001.1.2 | no-access |
The objects defined in this table are for the management of SCSP local server (LS). |
|
1.3.6.1.3.2001.1.2.1 | no-access |
Information about the Local Server in a SCSP group. Each entry contains attributes associated a LS. |
||
scspLSID | 1.3.6.1.3.2001.1.2.1.1 | octet string | no-access |
This is the Local Server ID of this Local Server. |
scspLSHelloInterval | 1.3.6.1.3.2001.1.2.1.2 | integer32 | read-only |
This object contains the value for HelloInterval for the Local Server. It is the time (in seconds) between sending of consecutive Hello messages from this server. |
scspLSDeadFactor | 1.3.6.1.3.2001.1.2.1.3 | integer32 | read-only |
This object contains the value for DeadFactor. The DeadFactor along with HelloInterval are sent with outgoing 'Hello' messages. If the DCS does not received 'Hello' message from this LS within the time out interval 'HelloInterval*DeadFactor' (in seconds), then the DCS MUST consider the LS to be stalled. |
scspLSCAReXmInterval | 1.3.6.1.3.2001.1.2.1.4 | integer32 | read-only |
The time out interval (in seconds) for re-sending CA message to the DCS if no response is received. |
scspLSCSUSReXmtInterval | 1.3.6.1.3.2001.1.2.1.5 | integer32 | read-only |
The time out interval (in seconds) for re-sending CSUS Request to the DCS if not all CSA Records corresponding to the CSAS records in the CSUS message have been received. |
scspLSCSUReXmtInterval | 1.3.6.1.3.2001.1.2.1.6 | integer32 | read-only |
The time out interval (in seconds) for re-sending CSU Request to the DCS if not all CSA Records corresponding to the CSU request have not been acknowledged. |
scspLSCSAMaxReXmt | 1.3.6.1.3.2001.1.2.1.7 | integer32 | read-only |
The maximum number of retransmission of a CSA record. If acknowledge fails to occur when the maximum number is reached, an 'abnormal event' has happened between the LS/DCS link. |
scspLSRowStatus | 1.3.6.1.3.2001.1.2.1.8 | rowstatus | read-only |
This object allows entries to be created and deleted from the scspLSTable. This table is closely coupled with DCS table and its corresponding protocol dependent tables. A new row creation in this table results in creation of new rows in the DCS table for each of its configured DCSs (peer servers). In addition, entries are created in the appropriate protocol dependent tables. When the scspServerRowStatus is deleted by setting this object to destroy(6), this results in removing the corresponding entries in the DCS table of the same Server Group. In addition, entries in the corresponding protocol dependent table will also be removed. |
scspDCSTable | 1.3.6.1.3.2001.1.3 | no-access |
The objects defined in this table are used for the management of the DCS session between the LS and DCS. |
|
1.3.6.1.3.2001.1.3.1 | no-access |
Information about each DCS session between the LS and its DCSs. The table is indexed by scspServerGroupID, scspServerGroupPID, and scspDCSID. |
||
scspDCSID | 1.3.6.1.3.2001.1.3.1.1 | octet string | no-access |
This ID is used to identify a directly connected server(DCS). |
scspDCSCAFSMState | 1.3.6.1.3.2001.1.3.1.2 | scspcafsmstatetype | read-only |
The current state of the Cache Alignment Finite State Machine. The allowable states are: down(1), msNego(2), cacheSumm(3), cacheUpdate(4), aligned(5). |
scspDCSCASequence | 1.3.6.1.3.2001.1.3.1.3 | integer32 | read-only |
The current CA sequence number associated with this DCS. |
scspDCSCAIn | 1.3.6.1.3.2001.1.3.1.4 | counter32 | read-only |
The number of CA messages received from this DCS. |
scspDCSCAOut | 1.3.6.1.3.2001.1.3.1.5 | counter32 | read-only |
The number of CA messages sent to this DCS. |
scspDCSCAInvalidIn | 1.3.6.1.3.2001.1.3.1.6 | counter32 | read-only |
The number of invalid CA messages received from this DCS. During Master/Slave negotiation state, two types of messages are correct: 1) CA from the DCS has the M, I, and O bits on, with no CSAS records and sender's ID is larger than the LSID. 2) CA from the DCS has the M and I bits off and the sender's ID is smaller than the LSID. All other types of CA messages are invalid and ignored. During Cache Summarize State, two kinds of message errors are possible: 1) M bit in received CA is set incorrectly; 2) CA sequence number is neither equal nor one more than the current LS's CA sequence number when LS is slave or CA sequence number is neither equal nor one less than the current LS's CA sequence number when LS is master. Other common errors include failed check sum, failed authentication if applicable, errors in the message fields. |
scspDCSCADuplicateIn | 1.3.6.1.3.2001.1.3.1.7 | counter32 | read-only |
The number of duplicate CA messages received from this DCS. A CA message is considered duplicate when 1)LS is master and received a CA message with its sequence number one less than the current sequence number; or 2)LS is slave and received a CA message with its sequence number equal to the LS's current sequence number. |
scspDCSMSState | 1.3.6.1.3.2001.1.3.1.8 | integer | read-only |
The master/slave status of this DCS. This object should be ignored when CAFSM is in 'down' state. Enumeration: 'slave': 2, 'master': 1. |
scspDCSCSUSIn | 1.3.6.1.3.2001.1.3.1.9 | counter32 | read-only |
The number of CSUS sent from this DCS to the LS. |
scspDCSCSUSOut | 1.3.6.1.3.2001.1.3.1.10 | counter32 | read-only |
The number of CSUS sent from LS to this DCS. |
scspDCSCSUSInvalidIn | 1.3.6.1.3.2001.1.3.1.11 | counter32 | read-only |
The number of Invalid CSUS sent from this DCS to the LS. |
scspDCSCSURequestIn | 1.3.6.1.3.2001.1.3.1.12 | counter32 | read-only |
The number of CSU requests LS received from this DCS. |
scspDCSCSUReplyOut | 1.3.6.1.3.2001.1.3.1.13 | counter32 | read-only |
The number of CSU replies sent from LS to this DCS. |
scspDCSCSURequestOut | 1.3.6.1.3.2001.1.3.1.14 | counter32 | read-only |
The number of CSU requests sent from LS to this DCS. |
scspDCSCSUReplyIn | 1.3.6.1.3.2001.1.3.1.15 | counter32 | read-only |
The number of CSU replies LS received from this DCS. |
scspDCSCSUInvalidRequestIn | 1.3.6.1.3.2001.1.3.1.16 | counter32 | read-only |
The number of invalid CSU requests LS received from this DCS. The possible errors in the CSU request messages: the received CSU request's Receiver ID is not equal to the LSID, etc. Other common errors include failed authentication if applicable, errors in the message fields, etc. |
scspDCSCSUInvalidReplyIn | 1.3.6.1.3.2001.1.3.1.17 | counter32 | read-only |
The number of invalid CSU replies LS received from this DCS. The possible errors in the CSU reply messages: the received CSU reply's Receiver ID is not equal to the LSID, etc. Other common errors include failed authentication if applicable, errors in the message fields, etc. |
scspDCSCSAIn | 1.3.6.1.3.2001.1.3.1.18 | counter32 | read-only |
The total number of CSA records received from this DCS to this LS. |
scspDCSCSAOut | 1.3.6.1.3.2001.1.3.1.19 | counter32 | read-only |
The total number of CSA records sent from LS to this DCS. |
scspDCSCSAReXmted | 1.3.6.1.3.2001.1.3.1.20 | counter32 | read-only |
The total number of CSA records re-transmited from LS to this DCS. |
scspDCSCSAReXmtQDepth | 1.3.6.1.3.2001.1.3.1.21 | integer32 | read-only |
The depth of CSA Re-transmit queue associated with this DCS. The CSAs in the Re-transmit queue are pending to acknowledged. |
scspDCSRowStatus | 1.3.6.1.3.2001.1.3.1.22 | rowstatus | read-only |
This object allows DCS entries to be created and deleted from the scspDCSTable. This table is closely coupled with its corresponding protocol dependent table. A new row creation in this table results in creation of a new row in the corresponding protocol dependent table. When the scspServerRowStatus is deleted by setting this object to destroy(6), this results in removing the corresponding entries in its corresponding protocol dependent table. |
scspNotifications | 1.3.6.1.3.2001.2 | |||
scspCSAReXmExceed | 1.3.6.1.3.2001.2.1 |
Retransmission of a CSA to this DCS has exceeded maximum retry limit, indicating an 'abnormal event' has happened between the LS/DCS association. The HSFM associated with this DCS is transitioned into the 'Waiting' state, and a 'scspHFSMWaiting' trap is also generated. |
||
scspConformance | 1.3.6.1.3.2001.3 | |||
scspCompliances | 1.3.6.1.3.2001.3.1 | |||
scspCompliance | 1.3.6.1.3.2001.3.1.1 |
The compliance statement for entities that are required for the management of SCSP. |
||
scspGroups | 1.3.6.1.3.2001.3.2 | |||
scspLSGroup | 1.3.6.1.3.2001.3.2.1 |
A collection of objects which support the management of the Server group and the Local Server. This group is mandatory. |
||
scspDCSGroup | 1.3.6.1.3.2001.3.2.2 |
A collection of objects which support the management of the information exchange session between the LS and its associated DCS. This group is mandatory. |