ACC-MSP
AI MIB Summary
Standard SNMP MIB module defining data structures for ACC-MSP.
48
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
48 total| Object Name |
|---|
accMsp OBJECT IDENTIFIER .1.3.6.1.4.1.5.1.1.76 |
IMPORTS Unknown .1.3.6.1.4.1.5.1.1.76 |
accMspGeneralScalars OBJECT IDENTIFIER .1.3.6.1.4.1.5.1.1.76.1 |
accMspAdminStateMSP Adminstrative state.rw Enumeration .1.3.6.1.4.1.5.1.1.76.1.1 |
accMspModeMSP Mode : WAIT means that MSP requires its neighbors to
respond only if they want the call. ACKNOWLEDGE causes all
the MSP neighbors to respond to every requestrw Enumeration .1.3.6.1.4.1.5.1.1.76.1.2 |
accMspDeliverySets the delivery mechanism for MSP packets.rw Enumeration .1.3.6.1.4.1.5.1.1.76.1.3 |
accMspGroupIdMSP Group Identifier, should be the same value on all
MSP NASs.rw INTEGER .1.3.6.1.4.1.5.1.1.76.1.4 |
accMspInterfaceAddressThe interface address in which the MSP protocol is to
operate overrw IpAddress .1.3.6.1.4.1.5.1.1.76.1.5 |
accMspUdpPortChanges the default UDP port number that MSP uses when
sending and listening for MSP packets.rw INTEGER .1.3.6.1.4.1.5.1.1.76.1.6 |
accMspMaximumTimeoutMaximum amount of time MSP will wait for an MSP neighbor
to respond to a request.rw INTEGER .1.3.6.1.4.1.5.1.1.76.1.7 |
accMspMaximumRetransmissionsUsed to configure the maximum number of retransmissions
that MSP will send to an MSP neighbor before designating
the neighbors as 'non-responding'.rw INTEGER .1.3.6.1.4.1.5.1.1.76.1.8 |
accMspMaximumHistorySizeUsed to configure the maximum history buffer size. Must
be in powers of 2.rw INTEGER .1.3.6.1.4.1.5.1.1.76.1.9 |
accMspMessageLevelUsed to set the message level for MSP. 7 being most
robust.rw INTEGER .1.3.6.1.4.1.5.1.1.76.1.10 |
accMspDebugMaskUsed to selectively enable and disable MSP trap messages
used for debugging. The debug messages are different from
regular traps.rw INTEGER .1.3.6.1.4.1.5.1.1.76.1.11 |
accMspStatInPacketsIndicates the total number of MSP packets received from
all MSP neighbors, both unicast and multicast packets.ro Counter .1.3.6.1.4.1.5.1.1.76.1.12 |
accMspStatOutPacketsIndicates the total number of MSP packets sent, including
both unicast and multicast packets.ro Counter .1.3.6.1.4.1.5.1.1.76.1.13 |
accMspStatInQueriesIndicates the number of MSP Query Requests that have been
received from MSP neighbors.ro Counter .1.3.6.1.4.1.5.1.1.76.1.14 |
accMspStatOutQueriesIndicates the number of MSP Query requests that have been
sent by this RAC. A MSP Query request is sent for each new
Multilink call that the RAC receives.ro Counter .1.3.6.1.4.1.5.1.1.76.1.15 |
accMspStatInAcksIndicates the number of MSP acknowledge packets received by
this RACro Counter .1.3.6.1.4.1.5.1.1.76.1.16 |
accMspStatOutAcksIndicates the number of MSP acknowledges sent by this RAC.ro Counter .1.3.6.1.4.1.5.1.1.76.1.17 |
accMspStatInRequestsIndicates the number of times a MSP neighbor has requested a
remote client session from this RAC.ro Counter .1.3.6.1.4.1.5.1.1.76.1.18 |
accMspStatOutRequestsIndicates the number of times This RAC has requested a
remote client session from a MSP neighbor.ro Counter .1.3.6.1.4.1.5.1.1.76.1.19 |
accMspStatInDiscardsIndicates the number of times the local MSP protocol has
discarded MSP packets.This counter increases if MSP receives
a MSP packet that is not a member of its group. This counter
will also increase whenever a MSP packet fails to be
processed.ro Counter .1.3.6.1.4.1.5.1.1.76.1.20 |
accMspStatProcessingErrorsIndicates the number of times the MSP protocol has failed to
process a MSP packet. Failures arise from conditions where the
packet could not be correctly processed, possibly because of
resource limitations.ro Counter .1.3.6.1.4.1.5.1.1.76.1.21 |
accMspStatNotForMesIndicates number of times an MSP acknowledgment to a query not
generated by this RAC has been received by this MSP protocol
entity. This is normal for piggybacked responses, which are
broadcast to the entire MSP community comprising the virtual
machine.ro Counter .1.3.6.1.4.1.5.1.1.76.1.22 |
accMspStatProtocolErrorsIndicates the number of times this MSP protocol entity has
encountered MSP protocol errors in processing a MSP packet.ro Counter .1.3.6.1.4.1.5.1.1.76.1.23 |
accMspStatInQueryPiggysAlong with Out Query Piggy, In Ack Piggy, and Out Ack Piggy
indicates how well MSP is operating. As MSP activity increases,
the MSP protocol is designed to piggyback Query Requests and
Query Acknowledgments in the same response packet to optimize
network traffic and to address scaling issues.ro Counter .1.3.6.1.4.1.5.1.1.76.1.24 |
accMspStatOutQueryPiggysAlong with Out Query Piggy, In Ack Piggy, and Out Ack Piggy
indicates how well MSP is operating. As MSP activity increases,
the MSP protocol is designed to piggyback Query Requests and
Query Acknowledgments in the same response packet to optimize
network traffic and to address scaling issues.ro Counter .1.3.6.1.4.1.5.1.1.76.1.25 |
accMspStatInAckPiggysAlong with Out Query Piggy, In Ack Piggy, and Out Ack Piggy
indicates how well MSP is operating. As MSP activity increases,
the MSP protocol is designed to piggyback Query Requests and
Query Acknowledgments in the same response packet to optimize
network traffic and to address scaling issues.ro Counter .1.3.6.1.4.1.5.1.1.76.1.26 |
accMspStatOutAckPiggysAlong with Out Query Piggy, In Ack Piggy, and Out Ack Piggy
indicates how well MSP is operating. As MSP activity increases,
the MSP protocol is designed to piggyback Query Requests and
Query Acknowledgments in the same response packet to optimize
network traffic and to address scaling issues.ro Counter .1.3.6.1.4.1.5.1.1.76.1.27 |
accMspStatQueryTimeoutsIndicates the number of times the local MSP protocol entity
has timed out while waiting for a query response. This is
normal in TIMEOUT mode of operation. However, if an excessive
number of timeouts are indicated in ACKNOWLEDGE mode, there
may be a problem with a particular RAC or excessive network
traffic may be resulting in lost packets.ro Counter .1.3.6.1.4.1.5.1.1.76.1.28 |
accMspStatMemoryFailsIndicates the number of times this MSP protocol entity has
failed to acquire memory when performing its protocol
operations.ro Counter .1.3.6.1.4.1.5.1.1.76.1.29 |
accMspStatAverageQueryClosureIndicates the average time to close a MSP Query Request. When
in TIMEOUT mode, this value coincides with the configured
maximum timeout parameter value. The default value for this
parameter is 100 ms. In ACKNOWLEDGE mode, this value varies
and usually is a good indicator of MSP responsiveness. A 'good'
response time would be less than the configured timeout
interval.ro Gauge .1.3.6.1.4.1.5.1.1.76.1.30 |
accMspStatCurrentTimeoutindicates the current timeout value being used. In TIMEOUT mode,
this will always be the maximum timeout value. In ACKNOWLEDGE mode,
this value varies, but in steady state, it should be close to
the Average Closure interval. If it is not, and this value continues
to vary, it may indicate MSP activity problems such as high packet
loss due to network congestion.ro Gauge .1.3.6.1.4.1.5.1.1.76.1.31 |
accMspNeighbor OBJECT IDENTIFIER .1.3.6.1.4.1.5.1.1.76.2 |
accMspNeighborTableDisplays all active MSP Neighbors. SEQUENCE OF AccMspNeighborEntry .1.3.6.1.4.1.5.1.1.76.2.1 |
accMspNeighborEntry AccMspNeighborEntry .1.3.6.1.4.1.5.1.1.76.2.1.1 |
accMspNeighborAddressThe remote IP Address of the MSP Neighbor.ro IpAddress .1.3.6.1.4.1.5.1.1.76.2.1.1.1 |
accMspNeighborIDsNumber of times the MSP Neighbor failed to respond to
an MSP requestro Counter .1.3.6.1.4.1.5.1.1.76.2.1.1.2 |
accMspNeighborVersionsro Counter .1.3.6.1.4.1.5.1.1.76.2.1.1.3 |
accMspNeighborStatesro Counter .1.3.6.1.4.1.5.1.1.76.2.1.1.4 |
accMspNeighborAckTimeOutsro Counter .1.3.6.1.4.1.5.1.1.76.2.1.1.5 |
accMspNeighborRetransmissionsro Counter .1.3.6.1.4.1.5.1.1.76.2.1.1.6 |
accMspTraps OBJECT IDENTIFIER .1.3.6.1.4.1.5.1.1.76.3 |
accMspIpBindTrapWhen the MSP multi cast binding to a IP is
attempted, if this fails then this trap is generated.
SEVERITY-DEFAULT: Warning
EVENTTYPE-DEFAULT: 10
ADDITIONAL-TEXT-VARIABLES: { accTrapLogSeqNum,accMspTrapMsg }
PCAUSE-DEFAULT: 7 TRAP-TYPE .1.3.6.1.4.1.5.1.1.76.3.0.1 |
accMspInvIntfAddrTrapif The MSP interface address is not 0.0.0.0 then only
it is a valid interface address. So, if this check fails
this trap is generated
SEVERITY-DEFAULT: Warning
EVENTTYPE-DEFAULT: 10
ADDITIONAL-TEXT-VARIABLES: { accTrapLogSeqNum,accMspTrapMsg }
PCAUSE-DEFAULT: 7 TRAP-TYPE .1.3.6.1.4.1.5.1.1.76.3.0.2 |
accMspShutdownTrapWhile creating a MSP neighbor, if the allocation
to that fails due to allocc failure, then this is
REAL bad situation as this could break the hello
protocol. MSP has to be SHUTDOWN
SEVERITY-DEFAULT: Major
EVENTTYPE-DEFAULT: 10
ADDITIONAL-TEXT-VARIABLES: { accTrapLogSeqNum,accMspTrapMsg }
PCAUSE-DEFAULT: 32 TRAP-TYPE .1.3.6.1.4.1.5.1.1.76.3.0.3 |
accMspTrapMsgEnterprise Trap Message for Mspro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.5.1.1.76.3.1 |