HP Cisco Nexus 5000 Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1)
HP Cisco Nexus 5000 - Converged Network Switches Manual
 |
View all HP Cisco Nexus 5000 manuals
Add to My Manuals
Save this manual to your list of manuals |
HP Cisco Nexus 5000 manual content summary:
- HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 1
Send documentation comments to [email protected] Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1) Current Release: 4.1(3)N1(1) -July 31, 2009 Part Number: OL-16601-01 H0 This document describes the features, caveats, and limitations for Cisco Nexus - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 2
page 5 • Limitations, page 7 • Caveats, page 9 • Cisco Fabric Manager, page 23 • Related Documentation, page 26 • Obtaining Documentation and Submitting a Service Request, page 26 Introduction This section includes the following topics: • Cisco Nexus 5000 Series Switches, page 2 • Cisco Nexus 2000 - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 3
Form Factor Pluggable Plus (SFP+) ports. Sixteen of the forty fixed ports support both Gigabit Ethernet and 10-Gigabit Ethernet. The default is 10-Gigabit Cisco Nexus 5010 switch, see the Cisco Nexus 5000 Series Hardware Installation Guide. Note The Cisco Nexus 5020 switch and the N5K-M1404 and N5K - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 4
as automatic configuration. This integration allows large numbers of servers and hosts to be supported using the same feature set as the parent Nexus 5000 Series switch, including security and quality of service (QoS) configuration parameters, with a single point of management as shown in Figure - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 5
switch. No software is included with the Nexus 2148T. Software is downloaded and upgraded from its parent Cisco Nexus 5000 Series switch. The Nexus ports over FEX-fabric Port-Channel • PVLAN Isolated and Promiscuous Trunk • Support for 512 VLANs (512 minus number of VSANs configured) • Native 802. - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 6
new format. Downgrading from Cisco NX-OS 4.1(3)N-Based Releases • Downgrade is only supported for the following releases: - Cisco NX-OS 4.0(1a)N1(1) release - new CLI in this release. • The class-maps, policy-maps, and service-policies of different types but sharing the same name are combined into a - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 7
switch, all host facing ports are connected and each host facing interface has large configuration ( supporting the maximum permissible ACEs per interface). • The Cisco Nexus 2000 Fabric Extender does not support PVLANs over VLAN trunks used to connect to another switch. The PVLAN trunks are only - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 8
Limitations Send documentation comments to [email protected] • VACLs of more than one type on a single VLAN are unsupported. NX-OS software supports only a single type of VACL (either MAC, IPv4, or IPv6) applied on a VLAN. When a VACL is applied to a VLAN, it replaces the existing VACL if - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 9
Caveats Send documentation comments to [email protected] 11 and the switch port 1/5 sends multicast traffic on VLAN 11 in a multicast group, and hosts connected to FEX ports 100/1/3-12 are interested in receiving that mutlicast traffic (through IGMP), then that multicast traffic goes out - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 10
Caveats Send documentation comments to [email protected] • 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 - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 11
intr src_id 41 - kernel The error message is when an unused interrupt in the MAC fires. The error message does not indicate any functional problem. Workaround: None • CSCta78541 Symptom: VSH crashes and generate a core when you do the following: attach fex 102 show system error-id list The Cisco - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 12
all four user qos classes (except class-default and class-fcoe) under system qos service-policy to span all ACL drop traffic. • CSCsw21301 Symptom: Cisco NX-OS does not provide offline configuration support. The creation of a FEX interface depends on the FEX coming online after a fabric interface - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 13
may show invalid calibration for DOM-supported 1 G SFP. Workaround: None that the ACL cannot be applied to the interface. This problem occurs only with a configuration session, and only after a online as SD is to manually set the speed 2 G or 4 G. Workaround: Configure the speed manually to 2 G or 4 - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 14
output currently displays an incorrect MTU value of 1500 bytes. Workaround: None. • CSCsm03765 Symptom: The Set operation on the CISCO-IP-IF-MIB is not supported. You cannot set the mgmt0 IP address using SNMP. Workaround: Use the CLI to set the mgmt0 IP address. Cisco Nexus 5000 Series and Cisco - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 15
mode 4. The i10k v9.2.0.8 is supported by MDS in SAN-OS 3.2(2c), and 3.2(3) with interop mode 1 and 4. Workaround: None. • CSCso74872 Symptom: When two SNMP walks are started simultaneously, one of them may fail with the following error: OID not increasing This problem does not occur with a single - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 16
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 - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 17
Caveats Send documentation comments to [email protected] Workaround: Use the Ethernet SPAN destination port to SPAN Fibre Channel traffic. FCoE packet going out of the Ethernet SPAN destination port will contain VSAN information in the Ethernet VLAN tag. • CSCsv93278 Symptom:The logging - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 18
This is only seen with ipv6 addresses.IPV4 addresses do not have this problem. Workaround: Bring back the deleted VLAN interface, delete the IPv6 address values map to no-drop classes in the system qos service-policy configuration, the service-policy application will fail. The impact is the traffic - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 19
resolved in 4.0(0)N1(2) and 4.0(0)N1(2a). Workaround: After a downgrade, manually copy the startup configuration to the running configuration and reboot the system. -s)# commit Failed to complete Verification: no free label This problem occurs with large VACL configurations. Once the Cisco Nexus 5000 - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 20
up properly unless the default VRF is configured. Workaround: The Cisco Nexus 5000 Series switch supports two possible VRFs, the default and the management. Configure the desired VRF when using TACACS+ service. You can configure the desired VRF using either of these configurations: aaa group server - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 21
a role may fail and display the following error: entry already exists The problem occurs when you execute the following steps: • Delete all role scopes for by POST for one of the ASICs. As a result, all the ports serviced by the ASIC on the GEM are marked for hwFailure. Workaround: Bypass POST at - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 22
Caveats Send documentation comments to [email protected] Workaround: None. • CSCsv30392 Symptom: The Cisco Nexus 5020 switch has a Pktmgr memory leak in version 4.0(0)N1(2). This causes STP to stop functioning after awhile causing a Layer 2 Loop. After breaking the redundant connections, - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 23
be reported by POST for one of the ASICs. As a result, all the ports serviced by the ASIC on the GEM are marked for hardware failure. Workaround: Do not V power supply, the following problems occur: • The syslog displays warnings at bootup. Although the hardware supports the 110 V input, the - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 24
ports fail the loopback test. Workaround: Reload the switch to confirm that it is a hardware defect. • CSCsq27576 Symptom: FC-SP authentication is supported only with a switch over the E/TE port. Authentication with native Fibre Channel (FC) and Fibre Channel over Ethernet (FCoE) initiator or target - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 25
Ethernet port channels between Cisco Nexus 5000 Series switches. Port channels using the Catalyst 6500 Series switches do not have this problem. Workaround: Disable receive and transmit Link Layer Discovery Protocol (LLDP) on the port channel members by entering the following configuration under - HP Cisco Nexus 5000 | Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 26
MDS 9000 and Nexus 5000 Series Fabric Manager Software Configuration Guide, Cisco Fabric Manager Release 4.1 • Cisco Nexus 5000 Series desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0. CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence
-
1 -
2 -
3 -
4 -
5 -
6 -
7 -
8
-
9
-
10
-
11
-
12
-
13
-
14
-
15
-
16
-
17
-
18
-
19
-
20
-
21
-
22
-
23
-
24
-
25
-
26
 |
 |
Send documentation comments to [email protected]
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706
USA
Cisco Nexus 5000 Series and Cisco Nexus 2000
Series Release Notes, Release 4.1(3)N1(1)
Current Release: 4.1(3)N1(1) -July 31, 2009
Part Number: OL-16601-01 H0
This document describes the features, caveats, and limitations for Cisco Nexus 5000 Series switches and
the Cisco Necus 2000 Series Fabric Extenders. Use this document in combination with documents listed
in the
“Related Documentation” section on page 26
.
Note
Release notes are sometimes updated with new information about restrictions and caveats. See the
following website for the most recent version of the Cisco Nexus 5000 Series and Cisco Nexus 2000
Series Release Notes:
se_Notes.html
Note
Table 1
shows the online change history for this document.
Table 1
Online History Change
Part Number
Revision
Date
Description
OL-16601-01
A0
June 03, 2008
Created release notes.
OL-16601-01
B0
June 16, 2008
Added information for Release 4.0(0)N1(1a).
OL-16601-01
C0
June 30, 2008
Added information for Cisco Fabric Manager Release
3.4(1a).
OL-16601-01
D0
July 22, 2008
Added information for Release 4.0(0)N1(1a).
OL-16601-01
E0
August 13, 2008
Added information for Release 4.0(0)N1(2).
OL-16601-01
F0
September 29,
2008
Added information for Release 4.0(0)N1(2a).