Cisco AP776A - Nexus Converged Network Switch 5020 Release Note - Page 16

Browse online or download pdf Release Note for Switch Cisco AP776A - Nexus Converged Network Switch 5020. Cisco AP776A - Nexus Converged Network Switch 5020 26 pages. Cisco nexus 5000 series release notes release 4.1(3)n1(1) (ol-16601-01 h0, july 2009)
Also for Cisco AP776A - Nexus Converged Network Switch 5020: Release Note (48 pages), Release Note (44 pages), Release Note (26 pages), Release Note (22 pages), Quick Reference Manual (14 pages), Release Note (3 pages)

Cisco AP776A - Nexus Converged Network Switch 5020 Release Note
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)
16
CSCsq17571
Symptom: When an SNMP user creates or deletes virtual interface group (VIG), virtual Ethernet
(VEth) or virtual FC (VFC) interfaces, the accounting log displayed by the show accounting log
command does not get updated.
Workaround: Use the CLI for the configuration, which will update the accounting log.
CSCsq35527
Symptom: When IGMP snooping is enabled on a switch, and the switch is the STP root and an STP
topology change occurs, the IP multicast traffic may take a long time to converge. During this time,
the IP multicast traffic may get affected.
Workaround: Configure a shorter query interval on the IGMP router to reduce the time it takes for
ip-multicast traffic to converge in this topology.
CSCsq35728
Symptom: When a SAN port channel is created, the following syslog message is displayed:
2008 May 20 06:09:13 switch %PORT_CHANNEL-3-MSG_SEND_FAILURE: failed to send
MAP_PARAM_FROM_CHANNEL to sap 45: Broken pipe"
There is no functionality loss and this message can be ignored.
Workaround: None.
CSCso01268
Symptom: The following error message is displayed when a module is hot-swapped out:
2005 Jan
1 00:08:23 switch %KERN-4-SYSTEM_MSG: SI-VDC map entry <0, 0x0> does not
exist! - kernel"
There is no functionality loss and the message can be ignored.
Workaround: None.
CSCsq57558
Symptom: Enhanced Inter Switch Link (EISL) encapsulation is not supported on a Fibre Channel
SPAN destination port. When EISL encapsulation is configured on the SPAN destination (SD) port,
a VFT header is added to the packets going out of the SD port. The VFT header has VSAN
information that helps distinguish traffic for various VSANs. This applies to any Fibre Channel
SPAN source. By default, EISL encap is not added and packets are sent out without a VFT header,
and independent of the type of SPAN source port. For a Cisco Nexus 5000 Series switch, the
switchport encap EISL command does not have any effect.
Workaround: Use the Ethernet SPAN destination port to SPAN Fibre Channel traffic. FCoE packets
going out of the Ethernet SPAN destination port will contain VSAN information in the Ethernet
VLAN tag.
CSCsq90423
Symptom: EISL encapsulation is not supported on Fibre Channel SPAN destination port in NPV
mode. When EISL encapsulation is configured on the SPAN destination (SD) port, a VFT header is
added to the packets going out of the SD port. The VFT header has VSAN information, which helps
distinguish traffic for various VSANs. This applies to any Fibre Channel SPAN source. By default,
EISL encapsulation is not added and packets are sent out without a VFT header, and independent of
the type of SPAN source port. For a Cisco Nexus 5000 Series switch, the switchport encap EISL
command does not have any effect.
OL-16601-01