Cisco Cisco Nexus 5010 Switch

Pagina di 28
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 e x u s 5 k d o c s @ c i s c o . c o m
10
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Releases 4.2(1)N1(1), 4.2(1)N2(1), and 4.2(1)N2(1a)
OL-16601-01
Limitations
If the module is not seated properly, an error message is displayed as follows:
2009 Aug  3 23:45:16 Edge-2 %PFMA-2-MOD_INSERTION_FAILED: Module 2 insertion fai led. 
Module might not be seated properly. Please try removing the module and the n 
re-insert after five seconds or more. 
For details see, the Expansion Modules section of the Cisco Nexus 5000 Series Hardware Installation 
Guide.
Limitations
This section describes the limitations in Nexus 5000 Series switches and the Cisco Nexus 2000 Series 
Fabric Extenders for the Cisco NX-OS 4.2(1)N2(1a), Cisco NX-OS 4.2(1)N2(1) and Cisco NX-OS 
4.2(1)N1(1) releases.
When upgrading from pre Cisco NX-OS 4.2(1)N1(1) releases, to any release, policy description is 
lost.  This problem does not exist when ugprading from Cisco NX-OS Release 4.2(1)N1(1) and 
beyond and any future releases. You should re-configure policy description after an upgrade. For 
details see, CSCth14225.
Staring with the with Cisco NX-OS Release 4.2(1)N2(1) release, LACP rate fast is supported. If you 
would like to downgrade to previous releases, install all prints the following warning:
"Configuration not supported - Lacp fast rate is enabled",
  "Use \"lacp rate normal\" on those interfaces"
You should change the Lacp rate to normal before downgrading.  If you ignore the warning and force 
install all to proceed, then it is possible that the leftover LACP rate fast configuration would still be 
active with previous releases of software but the behavior would be unpredictable and link flap may 
occur. It is recommended that you follow the warning from install all and change the lacp rate 
setting to normal. For details see, CSCth93787
When an FC SPAN dest port is changed from SD to F mode and back to SD mode on a NPV switch, 
the port goes into error-disabled state. Perform a shut/no-shut after the mode change recovers the 
port. This problem is only with NPV mode. For details, see CSCtf87701
If you configure a Nexus 2248TP port to 100Mbps speed instead of auto-negotiation , 
auto-negotiation does not occur. This is expected behavior. Both sides of the link should be 
configured to both hardwired speed or both autonegotiate.
no speed autonegotiates, advertises all speeds (only full duplex) 
speed 1000 autonegotiates only for a 802.3x pause 
speed 100 does NOT autonegotiate, pause cannot be advertised. Peer must be set to NOT 
autonegotiate and fix at 100Mbps (similar to the N2248TP) 
For details, see CSCte81998
Given the implementation of single CPU ISSU, stp root on pvst region with the switches on mst 
region is not supported. The pvst simulation on the boundary ports go into pvst sim inconsistent 
blocked state. So the stp active path is broken. In order to avoid this, to avoid the above, move all 
stp root on mst region. By doing so you cannot support non-disruptive ISSU since it will fail for No 
Non-Edge Designated Forwarding Ports required for ISSU . For details see CSCtf51577. Refer to 
the configuration guide for scenarios and topology in which non disruptive upgrade is supported.
IGMP queries sent in CSCtf94558 are group-specific queries which are sent with destination 
IP/MAC address as the group's address.