Cisco AP776A - Nexus Converged Network Switch 5020 Примечание к выпуску - Страница 10

Просмотреть онлайн или скачать pdf Примечание к выпуску для Переключатель Cisco AP776A - Nexus Converged Network Switch 5020. Cisco AP776A - Nexus Converged Network Switch 5020 26 страниц. Cisco nexus 5000 series release notes release 4.1(3)n1(1) (ol-16601-01 h0, july 2009)
Также для Cisco AP776A - Nexus Converged Network Switch 5020: Примечание к выпуску (48 страниц), Примечание к выпуску (44 страниц), Примечание к выпуску (26 страниц), Примечание к выпуску (22 страниц), Краткое справочное руководство (14 страниц), Примечание к выпуску (3 страниц)

Cisco AP776A - Nexus Converged Network Switch 5020 Примечание к выпуску
Caveats
S e n d d o c u m e n t a t i o n c o m m e n t s t o n x 5 0 0 0 - d o c f e e d b a c k @ c i s c o . c o m
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
10
CSCta00231
Symptom: After a downgrade, the interface policy may silently get added to the system level
without a warning message. This may change the entire qos queuing policy.
Workaround: Remove the system policy BW/SPQ parameters, configure the queuing policy and
add the parameters again to the interfaces.
CSCsv39939
Symptom: Incorrect values are displayed for interface capabilities for ports for Cisco Nexus 2000
Series Fabric extenders connected to a Cisco Nexus 5000 Series switch. In particular, the number
of input and output queues for the ports are displayed as zero instead of two.
Workaround: This is a display issue and does not impact functionality.
CSCsz81365
Symptom: SPAN session should stop reflecting packets as soon as mapping is removed.
Workaround: None.
CSCta04383
Symptom: When you install a new image from one of two vPC switches, the vPC switch gets
upgraded. Also, each of the connected Fabric Extenders update their firmware with the new version,
but continue to run the current version and stay connected to the other vPC switch. When you reload
the upgraded switch, but revert back to the older version of software on the switch, both the vPC
switches and all the Fabric Extenders run the older version of software. However, the Fabric
Extenders have the more recent version of software in the firmware. When the Fabric Extenders
reload there is loss of connectivity with the hosts.
Workaround: Re-install the older version of software from either of the two switches while the
Fabric Extenders are connected to that switch.
CSCta13997
Symptom: When vpc peer-link is down on Cisco Nexus 5000 Series switches, ports fail to come up
on a Cisco Nexus 2000 Fabric Extender that is dual homed to the Nexus 5000 Series switches with
vPC.
Workaround: Restore the peer-link before making new connections to the Cisco Nexus 2000 Fabric
Extender.
CSCsx35870
Symptom: The CLI times out when a large number of VLANs are created and deleted followed by
PVLAN creation and deletion. The system indicates that the Ethernet Port Manager (ethpm) has
timed out to communicate with the SPAN manager or PVLAN manager. As a result, some of the
PVLAN interfacse will be error disabled.
Workaround: Perform shut and no shut on the error disabled interfaces.
CSCsx59489
Symptom: Call home notifications for events generated when both a switch and a Fabric Extender
are rebooting may contain a timestamp of January 1 1970 as shown in the following example:
System Notification from sample-system - environment:minor - 1970-01-01 00:00:00
GMT+0000
The most likely scenario where this would occur is after a power failure or after issuing the reload
all command. The event is generated before the Fabric Extender connects with the switch and before
the local time is updated for the Fabric Extender.
Workaround: None.
OL-16601-01