|
|
Description:
|
rdnCableAgilityHopAbortReason OBJECT-TYPE
SYNTAX INTEGER {invalidSnrResults(0), spareFrequencyInUse(1), spareFrequencyPoorQuality(2), snrTimeout(3), modProfileChanTypeMismatch(4), modProfileNotOptimal(5)}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This entry contains a reason code for the
rdnCableFrequencyHopFailureTrap or
rdnCableModulationProfileHopFailureTrap.
invalidSnrResults(0) means that the SNR measurement of the spare
frequency failed, for an attempted frequency hop, for any reason.
spareFrequencyInUse(1) means that the spare frequency assessed
by the CMTS card is in use by another receiver in the spectrum group.
spareFrequencyPoorQuality(2) means that the spare frequency for
an attempted frequency hop was too noisy to run at the optimal
modulation level, and needed to be downgraded by an additional
modulation hop. The frequency hop action itself DID occur, and should
have produced a separate rdnCableFrequencyHopTrap.
The rdnCableFrequencyHopFailureTrap in this case is simply warning
that the new frequency is running a lower modulation.
snrTimeout(3) means that the SNR measurement did not complete
on the spare spectrum, for a frequency hop (no response).
modProfileChanTypeMismatch(4) means that the BSR attempted to do a
modulation profile hop, and found a number of configured
configured hops, but none of the profiles had an appropriate
channel type. No modulation profile hop took place. For this status,
the docsIfUpChannelModulationProfile varbind will show a dummy value
of 0.
modProfileNotOptimal(5) means that a modulation profile hop DID take
place, but the BSR could not find a profile having a modulation level
that was appropriate for the impaired channel, based on the
configured SNR threshold levels. The BSR did the next-best thing,
by using the lowest of the modulation level that it could find."
|
|
|
|
