mscAtmIfVccPmFailureCause 1.3.6.1.4.1.562.36.2.1.114.5.14.10.1.3

This attribute indicates the failure cause of Performance Monitoring (PM) measurements. The following are possible causes: noError indicates no error. unknownCause indicates unknown failure cause. softwareResourcesUnavailable indicates software resources reserved for a maximum of 255 active PMs on the local FP card have been used up. hardwareResourcesUnavailable indicates hardware resources reserved for a maximum of 512 active PMs CLR have been used up on the Link Side local card. remoteEndNoResponse indicates no response from remote end. activationCollision indicates activation collision was detected. Usually this is caused by both ends of the connection being provisioned to request PM. Only one end should be so provisioned. remoteEndRejectedActivation indicates the remote end has rejected an activation request. Usually this is due to the remote end reaching a resource limit. pcrUnsupported indicates the Tx or Rx PCR was out of range between 0 and 409600. nextHopCardUnsupported indicates the next hop card type is not supported.

Informations

Access Type
readonly noError(0), unknownCause(1), softwareResourcesUnavailable(2), hardwareResourcesUnavailable(3), remoteEndNoResponse(4), activationCollision(5), remoteEndRejectedActivation(6), pcrUnsupported(7), nextHopCardUnsupported(8)

Parent

1.3.6.1.4.1.562.36.2.1.114.5.14.10.1 mscAtmIfVccPmStatusEntry