Cisco Cisco IOS Software Release 12.2 Notas de publicación
11
Limitations and Restrictions
OL-3177-01B
Limitations and Restrictions
f.
In the Hyper Terminal window on the PC, click Transfer in the menu bar at the top of the window
and select Send File.
and select Send File.
g.
Select Xmodem as the protocol, and specify the name of the dboot2 image to copy to the DSLAM.
h.
Click Send to start the copy.
Note
It may take 1 hour or more for the copy to complete.
i.
When the download completes, the DSLAM boots automatically.
Step 6
To complete the recovery procedure, copy the dboot2 image to bootflash memory (for example,
using TFTP). If you do not perform this step, the dboot2 image will be lost when you reload the DSLAM.
using TFTP). If you do not perform this step, the dboot2 image will be lost when you reload the DSLAM.
Step 7
To finish booting the DSLAM, issue the following command:
DSLAM> reload
Limitations and Restrictions
The following sections describe the limitations and restrictions for Cisco IOS software DSLAM releases.
Redundant NI-2 Card Operation
When using NI-2 cards in a redundant fashion, we recommend that you issue the command redundancy
reload-peer on the active NI-2 card after the system has loaded. This causes the redundant NI-2 to reload
and ensures that the redundant configuration is operational.
reload-peer on the active NI-2 card after the system has loaded. This causes the redundant NI-2 to reload
and ensures that the redundant configuration is operational.
In rare instances during testing, a redundant NI-2 card sometimes appeared to be functional but was not.
Issuing the redundancy reload-peer command corrected the problem every time.
Issuing the redundancy reload-peer command corrected the problem every time.
Attainable Bit Rate Is Conservative on 4xflexi-DMT and 8xDMT
The reported DMT aggregate bit rate is less than the true attainable bit rate.
Limitations
Due to line condition variations between trains, the effect of trellis encoding, interleave delay, FEC
check bytes, and so forth, the attainable bit rate estimate is not always 100 percent accurate. A
conservative approach was taken in making the estimate; therefore, in general, you can get a higher rate
than what the estimate suggests. For a fast-path scenario, the results should track fairly closely for the
downstream rate and err on the conservative side for the upstream rate. For an interleave path scenario,
the results are highly dependent on configurations.
check bytes, and so forth, the attainable bit rate estimate is not always 100 percent accurate. A
conservative approach was taken in making the estimate; therefore, in general, you can get a higher rate
than what the estimate suggests. For a fast-path scenario, the results should track fairly closely for the
downstream rate and err on the conservative side for the upstream rate. For an interleave path scenario,
the results are highly dependent on configurations.
At a higher reach or where line conditions are not optimal, trellis encoding, interleave delay, and FEC
check bytes can provide a much higher rate than was estimated (greater than 128 kbps).
check bytes can provide a much higher rate than was estimated (greater than 128 kbps).