27.03.2013 Views

Cisco Broadband Cable Command Reference Guide

Cisco Broadband Cable Command Reference Guide

Cisco Broadband Cable Command Reference Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

cable upstream power-adjust<br />

2-234<br />

<strong>Cisco</strong> <strong>Broadband</strong> <strong>Cable</strong> <strong>Command</strong> <strong>Reference</strong> <strong>Guide</strong><br />

Chapter 2 <strong>Cisco</strong> <strong>Cable</strong> Modem Termination System <strong>Command</strong>s<br />

Determining if the CM has Reached Its Maximum Power Level<br />

Per the DOCSIS specification, the CMTS does not adjust the CM power level by commanding the CM<br />

to set itself to an absolute power level. Instead, the CMTS changes the CM power levels by commanding<br />

the CM to make relative power adjustments, using increments of +/–0.25 dB (or multiples thereof).<br />

If the CMTS commands a CM to adjust its power level by a particular amount, but the measured power<br />

level afterwards shows that the CM has made a smaller adjustment than requested, the show cable<br />

flap-list and show cable modem commands show an exclamation point (!) for that particular CM. This<br />

typically indicates that the CM has reached its maximum power level.<br />

If the CM has not reached its maximum power level, but the show cable flap-list and show cable modem<br />

commands still show an exclamation point (!) for that CM, the problem could be a fault in the upstream<br />

path of the cable network. This fault is typically found as amplifier misalignment, where one upstream<br />

amplifier is adjusted with too much input attenuation, and the next has too little. The amplifier with too<br />

little attenuation enters non-linear operation and begins serious intermodulation.<br />

Another possible cause is a faulty CM or a faulty connection between the CM and cable network. For<br />

example, a faulty coaxial cable or bad F-connector could also create noise problems.<br />

Note A CM that shows an exclamation point (!) in the show cable flap-list and show cable modem displays<br />

is typically more prone to packet loss than other CMs.<br />

Setting the noise Option<br />

The noise option specifies that when the number of power adjustments beyond the threshold amount<br />

exceeds a certain percentage of the total Ranging Requests for a CM, the CMTS switches into its noise<br />

power-adjustment method. The noise power-adjustment method uses an averaging algorithm to make<br />

power adjustments for a particular CM, so that if a modem is experiencing wide swings in its power<br />

levels (known as “bouncing’), the CMTS averages the power levels before sending a power adjustment<br />

to the CM. The CMTS returns to the normal power adjust method after receiving ten Ranging Request<br />

messages with power adjustments below the threshold value.<br />

For example, the cable upstream power-adjust noise 30 command instructs the CMTS that when<br />

30 percent (3 out of the last 10) of the Ranging Responses for a particular CM resulted in a power<br />

adjustment beyond the threshold level, the CMTS begins using power averaging for that CM to adjust<br />

its power level.<br />

Tip The cable upstream power-adjust noise command is typically not needed during normal operations,<br />

but it can help in certain situations where the cable plant is experiencing ingress noise and other<br />

interference that is forcing many CMs to frequently re-range. If the show cable flap-list and show cable<br />

modem commands show a large number of CMs with asterisks (*), experiment with the noise option, so<br />

that the CMTS will average its CM power readings before sending any power adjustments to the CMs.<br />

Note When a CM is in power averaging mode, the show cable flap-list and show cable modem commands<br />

shows an asterisk (*) for that particular CM.<br />

OL-1581-05

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!