Cisco Cisco IOS Software Release 12.0 S

Seite von 678
359
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
  Caveats
Resolved Caveats—Cisco IOS Release 12.0(33)S11
Resolved Caveats—Cisco IOS Release 12.0(33)S11
All the caveats listed in this section are resolved in Cisco IOS Release 12.0(33)S11. This section 
describes only severity 1, severity 2, and select severity 3 caveats
CSCtw53776
Symptoms: A Cisco 12000 linecard crashes when NetFlow version 1 is configured on the router.
Conditions: The crash occurs if the “ip flow export x.x.x.x <port>” command is used instead of the 
“ip flow export destination x.x.x.x <port>” command.
Workaround: Configure NetFlow version 5 or version 9. 
CSCty77445
Symptoms: The SPA-2X1GE-V2 interface is in down/down status on RJ45 connection after moving 
the cable from RJ45 to SFP and back to RJ45 (SFP removed at the end).
Conditions: This symptom is observed when following these steps:
1.
Make the interface up in RJ-45 mode (configure interface to RJ-45 mode with “media rj45” and 
you may also need to reboot the router without the SFP installed, if it is already in faulty 
condition).
2.
Have the transceiver inserted into the corresponding SFP port and move the cable to the SFP.
3.
Now, remove the transceiver and the cable together. Then move the cable to the RJ-45 port and 
that should trigger the problem. Port will not come up. Make sure that before you insert the 
cable into the RJ-45 port, the transceiver should be removed from the corresponding SFP port.
Workaround:
1.
Use the SFP port.
2.
Reload the router. 
CSCud28759
Symptoms: SPA crash is seen when invoking spa_choc_dsx_cleanup_atlas_ci_config with no data 
packed.
Conditions: This symptom is observed when the packed data size should be 1 and the status should 
be success.
Workaround: There is no workaround. 
CSCud28937
Symptoms: Two issues are observed:
1.
Fasttag rewrite is not updated with new label after a route flap. 
2.
There are 2 load-shared paths and when one of the paths (say path2) goes down, the fasttag 
rewrite is not being set using path1. The clear ip route affected prefix command is needed to 
set the fasttag rewrite. Now if the path2 comes up, fasttag rewrite is not removed until you do a 
clear ip route affected prefix command.
Conditions: These symptoms are seen under the following conditions:
1.
For the first issue, a Cisco 12000 series router connected to a non-Cisco device, which will send 
a new MPLS label to the Cisco 12000 series router after each session flap.
2.
For the second issue, there should be two load-shared MPLS paths for a recursive destination 
prefix.
For both cases, the prefix should be a recursive prefix.