| OID symbolic | OID numeric | Type | Access | Description |
| accMsp | 1.3.6.1.4.1.5.1.1.76 | | | |
| accMspGeneralScalars | 1.3.6.1.4.1.5.1.1.76.1 | | | |
| INT accMspAdminState | 1.3.6.1.4.1.5.1.1.76.1.1 | INTEGER | read-write | MSP Adminstrative state. |
| INT accMspMode | 1.3.6.1.4.1.5.1.1.76.1.2 | INTEGER | read-write | MSP 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 request |
| INT accMspDelivery | 1.3.6.1.4.1.5.1.1.76.1.3 | INTEGER | read-write | Sets the delivery mechanism for MSP packets. |
| INT accMspGroupId | 1.3.6.1.4.1.5.1.1.76.1.4 | INTEGER | read-write | MSP Group Identifier, should be the same value on all
MSP NASs. |
| IP accMspInterfaceAddress | 1.3.6.1.4.1.5.1.1.76.1.5 | IpAddress | read-write | The interface address in which the MSP protocol is to
operate over |
| INT accMspUdpPort | 1.3.6.1.4.1.5.1.1.76.1.6 | INTEGER | read-write | Changes the default UDP port number that MSP uses when
sending and listening for MSP packets. |
| INT accMspMaximumTimeout | 1.3.6.1.4.1.5.1.1.76.1.7 | INTEGER | read-write | Maximum amount of time MSP will wait for an MSP neighbor
to respond to a request. |
| INT accMspMaximumRetransmissions | 1.3.6.1.4.1.5.1.1.76.1.8 | INTEGER | read-write | Used to configure the maximum number of retransmissions
that MSP will send to an MSP neighbor before designating
the neighbors as 'non-responding'. |
| INT accMspMaximumHistorySize | 1.3.6.1.4.1.5.1.1.76.1.9 | INTEGER | read-write | Used to configure the maximum history buffer size. Must
be in powers of 2. |
| INT accMspMessageLevel | 1.3.6.1.4.1.5.1.1.76.1.10 | INTEGER | read-write | Used to set the message level for MSP. 7 being most
robust. |
| INT accMspDebugMask | 1.3.6.1.4.1.5.1.1.76.1.11 | INTEGER | read-write | Used to selectively enable and disable MSP trap messages
used for debugging. The debug messages are different from
regular traps. |
| CTR accMspStatInPackets | 1.3.6.1.4.1.5.1.1.76.1.12 | Counter | read-only | Indicates the total number of MSP packets received from
all MSP neighbors, both unicast and multicast packets. |
| CTR accMspStatOutPackets | 1.3.6.1.4.1.5.1.1.76.1.13 | Counter | read-only | Indicates the total number of MSP packets sent, including
both unicast and multicast packets. |
| CTR accMspStatInQueries | 1.3.6.1.4.1.5.1.1.76.1.14 | Counter | read-only | Indicates the number of MSP Query Requests that have been
received from MSP neighbors. |
| CTR accMspStatOutQueries | 1.3.6.1.4.1.5.1.1.76.1.15 | Counter | read-only | Indicates 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. |
| CTR accMspStatInAcks | 1.3.6.1.4.1.5.1.1.76.1.16 | Counter | read-only | Indicates the number of MSP acknowledge packets received by
this RAC |
| CTR accMspStatOutAcks | 1.3.6.1.4.1.5.1.1.76.1.17 | Counter | read-only | Indicates the number of MSP acknowledges sent by this RAC. |
| CTR accMspStatInRequests | 1.3.6.1.4.1.5.1.1.76.1.18 | Counter | read-only | Indicates the number of times a MSP neighbor has requested a
remote client session from this RAC. |
| CTR accMspStatOutRequests | 1.3.6.1.4.1.5.1.1.76.1.19 | Counter | read-only | Indicates the number of times This RAC has requested a
remote client session from a MSP neighbor. |
| CTR accMspStatInDiscards | 1.3.6.1.4.1.5.1.1.76.1.20 | Counter | read-only | Indicates 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. |
| CTR accMspStatProcessingErrors | 1.3.6.1.4.1.5.1.1.76.1.21 | Counter | read-only | Indicates 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. |
| CTR accMspStatNotForMes | 1.3.6.1.4.1.5.1.1.76.1.22 | Counter | read-only | Indicates 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. |
| CTR accMspStatProtocolErrors | 1.3.6.1.4.1.5.1.1.76.1.23 | Counter | read-only | Indicates the number of times this MSP protocol entity has
encountered MSP protocol errors in processing a MSP packet. |
| CTR accMspStatInQueryPiggys | 1.3.6.1.4.1.5.1.1.76.1.24 | Counter | read-only | Along 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. |
| CTR accMspStatOutQueryPiggys | 1.3.6.1.4.1.5.1.1.76.1.25 | Counter | read-only | Along 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. |
| CTR accMspStatInAckPiggys | 1.3.6.1.4.1.5.1.1.76.1.26 | Counter | read-only | Along 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. |
| CTR accMspStatOutAckPiggys | 1.3.6.1.4.1.5.1.1.76.1.27 | Counter | read-only | Along 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. |
| CTR accMspStatQueryTimeouts | 1.3.6.1.4.1.5.1.1.76.1.28 | Counter | read-only | Indicates 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. |
| CTR accMspStatMemoryFails | 1.3.6.1.4.1.5.1.1.76.1.29 | Counter | read-only | Indicates the number of times this MSP protocol entity has
failed to acquire memory when performing its protocol
operations. |
| GAU accMspStatAverageQueryClosure | 1.3.6.1.4.1.5.1.1.76.1.30 | Gauge | read-only | Indicates 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. |
| GAU accMspStatCurrentTimeout | 1.3.6.1.4.1.5.1.1.76.1.31 | Gauge | read-only | indicates 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. |
| accMspNeighbor | 1.3.6.1.4.1.5.1.1.76.2 | | | |
| accMspNeighborTable | 1.3.6.1.4.1.5.1.1.76.2.1 | | not-accessible | Displays all active MSP Neighbors. |
| accMspNeighborEntry | 1.3.6.1.4.1.5.1.1.76.2.1.1 | | not-accessible | |
| IP accMspNeighborAddress | 1.3.6.1.4.1.5.1.1.76.2.1.1.1 | IpAddress | read-only | The remote IP Address of the MSP Neighbor. |
| CTR accMspNeighborIDs | 1.3.6.1.4.1.5.1.1.76.2.1.1.2 | Counter | read-only | Number of times the MSP Neighbor failed to respond to
an MSP request |
| CTR accMspNeighborVersions | 1.3.6.1.4.1.5.1.1.76.2.1.1.3 | Counter | read-only | |
| CTR accMspNeighborStates | 1.3.6.1.4.1.5.1.1.76.2.1.1.4 | Counter | read-only | |
| CTR accMspNeighborAckTimeOuts | 1.3.6.1.4.1.5.1.1.76.2.1.1.5 | Counter | read-only | |
| CTR accMspNeighborRetransmissions | 1.3.6.1.4.1.5.1.1.76.2.1.1.6 | Counter | read-only | |
| accMspTraps | 1.3.6.1.4.1.5.1.1.76.3 | | | |
| NTF accMspIpBindTrap | 1.3.6.1.4.1.5.1.1.76.3.0.1 | | | When 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 |
| NTF accMspInvIntfAddrTrap | 1.3.6.1.4.1.5.1.1.76.3.0.2 | | | if 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 |
| NTF accMspShutdownTrap | 1.3.6.1.4.1.5.1.1.76.3.0.3 | | | While 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 |
| STR accMspTrapMsg | 1.3.6.1.4.1.5.1.1.76.3.1 | DisplayString | read-only | Enterprise Trap Message for Msp |