Cisco Cisco MDS 9000 NX-OS Software Release 6.2 Notas de publicación

Descargar
Página de 4
3
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(3n)
OL-29201-05
  Caveats
Symptom: An FCSP-ESP enabled (encrypted) port that was working fails to come up after 
ISSU/ISSD followed by link flap.
Condition: This issue only affects FCSP encrypted ports on MDS 9700 DS-X9448-768K9 and MDS 
9500 DS-X9248-256K9 and DS-X9232-256K9 switching modules after an ISSU or ISSD to an 
affected version of NX-OS.
Workaround: Only a switch reload will recover from this situation. The switch must be running a 
fixed release of NX-OS (NX-OS 6.2(11) or above) before the reload to prevent the issue from 
recurring after recovery.
None of the following steps alone will not recover the port functionality:
Shut/no-shut the affected port.
Reloading the affected linecard.
Removing the FCSP configuration and re-configuring FCSP.
Upgrading to NX-OS 6.2(11) or above. 
CSCuw82693
Symptom: An ISL connected over a DWDM path does not reach link up state.
Condition: This issue only applies to MDS 9700 DS-X9448-768K9 modules used with some 
DWDM vendors.
Workaround: None.
Further Problem Descriptionshow interface shows the link in "Link failure or not-connected" 
with OLS/LRR and NOS increasing in both directions.
CSCuw06365
Symptom: An ISL does not initialize quickly across a DWDM connection. The link can take 
minutes, hours or even days to connect. Once connected, it is stable.
Condition: This issue only applies to DS-X9248-256K9 and DS-X9232-256K9 modules when 
connecting an ISL over a Tellabs 7100 DWDM path.
Workaround: None.
Further Problem Descriptionshow interface shows the link in "Link failure or not-connected" 
with OLS/LRR and NOS increasing in both directions.
CSCuu76450
Symptom: MDS fabric switch running in NPV mode fails to generate port-monitor alerts.
Condition: Applies to all MDS fabric switches running in NPV mode using port-monitor.
Applies to all versions prior to NX-OS 6.2(13).
Will occur only in the following conditions:
- After one or more upstream NP or TNP ports goes down and then back up. 
- For each (T)NP port that flaps, one F port at the end of the range of ports
will no longer be scanned for port-monitor counter events. For example, if the
(T)NP port fc1/1 flaps then the last F port being used(ex. fc1/48) will no 
longer be scanned for port-monitor counter events.
Workaround: There are two workarounds, one temporary and one permanent:
1 - Contact the TAC and they can assist with killing the port-monitor process. Once the port-monitor 
process restarts, all ports will be once again scanned.