Cisco Cisco IOS XR Software Release 3.2 Notas de publicación

Descargar
Página de 40
17
Release Notes for Cisco IOS XR Software Release 3.2.1
OL-8232-01
GSR16/80-CSC Cisco 12016 80 Gbps GSR Clock Scheduler Card 43
GSR16/80-SFC Cisco 12016 80 Gbps GSR Switch Fabric Card 35
GSR16/320-CSC Cisco 12416 320 Gbps GSR Clock Scheduler Card 106
GSR16/320-SFC Cisco 12416 320 Gbps Switch Fabric Card 93
CSC-256,GSR12816 Clock Scheduler Card(16) OC-768 177
SFC-256,GSR12816 Switch Fabric Card(16) OC-768 151
GSR04-FABRIC Alarm Board(404) 208
GSR6-ALRM GSR 12406 Alarm Module 26
GSR10-ALRM GSR 12410 Alarm Module 33
GSR16-ALRM Cisco 12016 Alarm Module 35
GSR6-BLOWER GSR 12406 Blower Module 178
GSR16-BLOWER GSR 12016 Blower Module 178
Bus Board(16) 20
RP/0/0/CPU0:c12k# 
If you plan to insert a new card, locate the entry for the card to be inserted and note the power consumed 
by it. If this power is less than the figure given in Worst Case Redundant Power Available (the figure is 
displayed in the show environment power-supply table command output), the card can be safely 
inserted. As long as the Worst Case Redundant Power Available is not zero, a PEM can be powered down 
for replacement without impact.
Note
No alerts are issued if more cards are inserted than the PEMs can support. It is your responsibility to 
determine your power budget for the chassis before making any changes to it. Exceeding the power 
budget may result in the PEM being overloaded and cards powering down due to insufficient power being 
provided.
Caveats
Caveats describe unexpected behavior in Cisco IOS XR software releases. Severity 1 caveats are the 
most serious caveats; severity 2 caveats are less serious.
Release 3.2.0 Caveats Resolved in Release 3.2.1
This section lists the caveats from Cisco IOS XRSoftware Release 3.2.0 that were resolved in 
Cisco IOS XR Software Release 3.2.1. 
CSCei14219
Basic Description: LDP installing “Unlabelled” as outgoing labels for prefixes over tunnel-te 
interface after RP Failover is performed.
Symptom: The traffic is not taking LDP label after RP Fail Over (FO) because prefixes pointing to 
a tunnel-te interface are marked as Unlabelled in show mpls forwarding
Furthermore, LDP targeted session over tunnel-te interface does not seem to come up.
Conditions: When MPLS LDP is enabled on a tunnel-te interface and prefixes are learned over that 
tunnel-te interface with autoroute announce, labels are assigned to these prefixes pointing to the 
tunnel-te interface. After an RP switchover, these prefixes are marked as “Unlabelled.”
Workaround: Restart the mpls_ldp process with process restart mpls_ldp.