SCSPATMARP-MIB
AI MIB Summary
The SCSPATMARP-MIB facilitates the monitoring and management of Server Cache Synchronization Protocol (SCSP) state transitions and cache consistency metrics specifically within ATM ARP server environments. It enables administrators to track synchronization status, cache entry validity, and protocol error counters to ensure reliable Address Resolution Protocol data propagation across ATM networks.
This module defines a portion of the management information base (MIB) for managing Server Cache Synchronizatio protocol applied to ATMARP servers.
Main OID:
scspAtmarpMIB.1.3.6.1.3.2002
41
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
41 total| Object Name |
|---|
scspAtmarpMIBThis module defines a portion of the management information base (MIB) for managing Server Cache Synchronizatio protocol applied to ATMARP servers. MODULE-IDENTITY .1.3.6.1.3.2002 |
scspAtmarpObjects OBJECT IDENTIFIER .1.3.6.1.3.2002.1 |
scspAtmarpServerGroupTableThe objects defined in this table are used to for the management of SCSP server groups with application to IP over ATM operation (Classic IP). These objects SHOULD be used along with the protocol independent part objects to support the management of the SCSP protocol applied to synchronizing the atmarp servers in a LIS. There is one entry in this table for each server group. In the case of IP over ATM, each server group corresponds to a Logical IP Subnet. SEQUENCE OF ScspAtmarpServerGroupEntry .1.3.6.1.3.2002.1.1 |
scspAtmarpServerGroupEntryInformation about SCSP server group running IP over ATM operation. This table is indexed by scspServerGroupID and scspServerGroupPID. The two indeces point to a corresponding entry in the scspServerGroupTable. ScspAtmarpServerGroupEntry .1.3.6.1.3.2002.1.1.1 |
scspAtmarpServerGroupNetMaskThe subnet mask associated with this Server Group.ro IpAddress .1.3.6.1.3.2002.1.1.1.1 |
scspAtmarpServerGroupSubnetAddrThe IP subnet address associated with this Server Group.ro IpAddress .1.3.6.1.3.2002.1.1.1.2 |
scspAtmarpServerGroupRowStatusThis object allows Atmarp Server Group Table entries to be created and deleted from the scspAtmarpServerGroupTable. Note that scspAtmarpServerGroupTable entry creation and deletion is coupled with scspServerGroupTable entry creation and deletion. A scspAtmarpServerGroupTable entry cannot be created until its corresponding scspServerGroupTable entry is created. When a scspServerGroupTable entry is deleted, it also removes the corresponding scspAtmarpServerGroupTable entry.rw RowStatus (SNMPv2-TC) .1.3.6.1.3.2002.1.1.1.3 |
scspAtmarpLSTableThe objects defined in this table are used to for the management of the Atmarp Local server in a SCSP server group for IP over ATM operation. These objects SHOULD be used along with the protocol independent part objects to support the management of the SCSP protocol applied to synchronizing the IP over ATM servers. SEQUENCE OF ScspAtmarpLSEntry .1.3.6.1.3.2002.1.2 |
scspAtmarpLSEntryInformation about Atmarp Local Server in a SCSP server group. This table is indexed by scspServerGroupID, scspServerGroupPID, and scspLSID. The three indeces point to a corresponding entry in the scspLSTable. ScspAtmarpLSEntry .1.3.6.1.3.2002.1.2.1 |
scspAtmarpLSLSIPAddrThe IP address of the Atmarp Local Server. Since an Atmarp server does not have to be assigned an IP address, this object is optional.ro IpAddress .1.3.6.1.3.2002.1.2.1.1 |
scspAtmarpLSLSAtmAddrThe ATM address of the Atmarp Local Server.ro AtmAddr (ATM-TC-MIB) .1.3.6.1.3.2002.1.2.1.2 |
scspAtmarpLSRowStatusThis object allows Atmarp Local Server Table entries to be created and deleted from the scspAtmarpLSTable. Note that scspAtmarpLSTable entry creation and deletion is coupled with scspLSTable entry creation and deletion. A scspAtmarpLSTable entry cannot be created until its corresponding scspLSTable entry is created. When a scspLSTable entry is deleted, it also removes the corresponding scspAtmarpLSTable entry.rw RowStatus (SNMPv2-TC) .1.3.6.1.3.2002.1.2.1.3 |
scspAtmarpPeerTableThe objects defined in this table are used to for the management of the ATMARP sever peers. SEQUENCE OF ScspAtmarpPeerEntry .1.3.6.1.3.2002.1.3 |
scspAtmarpPeerEntryInformation about each peer ATMARP server participated in the scsp Server group. The table is indexed by scspServerGroupID, scspServerGroupPID, and scspAtmarpPeerIndex. ScspAtmarpPeerEntry .1.3.6.1.3.2002.1.3.1 |
scspAtmarpPeerIndexThe table index of the peer Atmarp server table.ro Integer32 .1.3.6.1.3.2002.1.3.1.1 |
scspAtmarpPeerIPAddrThe IP address of the peer Atmarp server. Since an Atmarp server does not have to be assigned an IP address, this object is optional.ro IpAddress .1.3.6.1.3.2002.1.3.1.2 |
scspAtmarpPeerAtmAddrThe ATM address of the Peer. If SVC is used between LS and Peer, Peer's ATM address should be valid. However, if PVC is used instead SVC, the Peer's ATM address may be a Null OCTET STRING.ro AtmAddr (ATM-TC-MIB) .1.3.6.1.3.2002.1.3.1.3 |
scspAtmarpPeerVCTypeThe type of the virtual circuit between LS and Peer.ro AtmConnKind (ATM-TC-MIB) .1.3.6.1.3.2002.1.3.1.4 |
scspAtmarpPeerVPIThe VPI value for the virtual circuit between LS and Peer.ro SCSPVPIInteger (SCSP-MIB) .1.3.6.1.3.2002.1.3.1.5 |
scspAtmarpPeerVCIThe VCI value for the virtual circuit between LS and Peer.ro SCSPVCIInteger (SCSP-MIB) .1.3.6.1.3.2002.1.3.1.6 |
scspAtmarpPeerDCSIDThe DCS ID for this peer. When the peer tabel is created, DCS ID may not have been discovered. Tt is set to a Null string. It will be update when the DCS ID associated with this peer (ATM address) is discovered.ro OCTET STRING .1.3.6.1.3.2002.1.3.1.7 |
scspAtmarpPeerRowStatusThis object allows Atmarp Peer table entries to be created and deleted from the scspAtmarpPeerTable. Note that scspAtmarpPeerTable entry is created when a peer is configured loaclly or when a peer not previously configured connects to LS.rw RowStatus (SNMPv2-TC) .1.3.6.1.3.2002.1.3.1.8 |
scspAtmarpHFSMTableThe objects defined in this table are used to for the management of the HFSM between the LS and the DCS. SEQUENCE OF ScspAtmarpHFSMEntry .1.3.6.1.3.2002.1.4 |
scspAtmarpHFSMEntryInformation about SCSP HFSM session between the LS and its HFSMs. The table is indexed by scspServerGroupID, scspServerGroupPID, and scspAtmarpPeerIndex. ScspAtmarpHFSMEntry .1.3.6.1.3.2002.1.4.1 |
scspHFSMHFSMStateThe current state of the Hello Finite State Machine. The allowable states are: down(1), waiting(2), uniConn(3), biConn(4).ro ScspHFSMStateType (SCSP-MIB) .1.3.6.1.3.2002.1.4.1.1 |
scspHFSMHelloInThe number of 'Hello' messages received from this HFSM.ro Counter32 .1.3.6.1.3.2002.1.4.1.2 |
scspHFSMHelloOutThe number of 'Hello' messages sent from LS to this HFSM.ro Counter32 .1.3.6.1.3.2002.1.4.1.3 |
scspHFSMHelloInvalidInThe number of invalid 'Hello' messages received from this HFSM. Possible message errors include: Hello message when the HFSM is in 'Down' state; Hello message is too short to contain the number of Receiver ID records specified in the header, etc. Other common errors include failed authentication if applicable, errors in the message fields, etc.ro Counter32 .1.3.6.1.3.2002.1.4.1.4 |
scspHFSMHelloIntervalThis object contains the value for HelloInterval with the associated HFSM. It is the time (in seconds) between sending of consecutive Hello messages from the HFSM.rw Integer32 .1.3.6.1.3.2002.1.4.1.5 |
scspHFSMDeadFactorThis object contains the value for DeadFactor with this associated server. The DeadFactor along with HelloInterval are contained in 'Hello' messages sent from this HFSM. If 'Hello' messages are not received from this HFSM within the time out interval 'HelloInterval*DeadFactor' (in seconds), then the HFSM MUST be considered to be stalled.rw Integer32 .1.3.6.1.3.2002.1.4.1.6 |
scspHFSMFamilyIDThe family ID is used to refer an aggregate of Protocol ID/SGID pairs. Only a single HFSM is run for all Protocol ID/SGID pairs assigned to a Family ID. When the HFSM is not shared by an aggregate of Protocol ID/SGID pairs, this object should be set to 0.ro Integer32 .1.3.6.1.3.2002.1.4.1.7 |
scspAtmarpHFSMRowStatusThis object allows Atmarp HFSM table entries to be created and deleted from the scspAtmarpHFSMTable. Note that scspAtmarpHFSMTable entry creation and deletion is closely coupled with scspHFSMTable entry creation. A scspAtmarpHFSMTable entry cannot be created until its corresponding scspHFSMTable entry is created. When a scspHFSMTable entry is deleted, it also removes the corresponding scspAtmarpHFSMTable entry.rw RowStatus (SNMPv2-TC) .1.3.6.1.3.2002.1.4.1.8 |
scspAtmarpNotifications OBJECT IDENTIFIER .1.3.6.1.3.2002.2 |
scspHFSMDownThe Hello Finite State Machine associated with this LS/DCS pair enters 'Down' state. NOTIFICATION-TYPE .1.3.6.1.3.2002.2.1 |
scspHFSMWaitingThe Hello Finite State Machine associated with this LS/DCS pair enters 'Waiting' state. NOTIFICATION-TYPE .1.3.6.1.3.2002.2.2 |
scspHFSMBiConnThe Hello Finite State Machine associated with this LS/DCS pair enters 'Bidirectional connection' state. NOTIFICATION-TYPE .1.3.6.1.3.2002.2.3 |
scspAtmarpConformance OBJECT IDENTIFIER .1.3.6.1.3.2002.3 |
scspAtmarpCompliances OBJECT IDENTIFIER .1.3.6.1.3.2002.3.1 |
scspAtmarpComplianceThe compliance statement for entities that are required for the management of SCSP when applied to ATMARP servers. Unknown .1.3.6.1.3.2002.3.1.1 |
scspAtmarpGroups OBJECT IDENTIFIER .1.3.6.1.3.2002.3.2 |
scspAtmarpGroupThis group is mandatory when Atmarp is the client/server protocol running SCSP. Unknown .1.3.6.1.3.2002.3.2.1 |