HP Cisco MDS 9124 HP StorageWorks C-Series Fabric Switches for NX-0S 4.1(3a) R - Page 20

Hp Specific Known Issues - blade

Page 20 highlights

HP SPECIFIC KNOWN ISSUES Problem Description: Issuing an "End to End Connectivity" to the EVA4400/6400/8400 may crash both EVA controllers at the same time. Workaround: None. Problem Description: Issuing an fcping to the EVA4400/6400/8400 may crash the EVA controller Workaround: None. Problem Description: If it becomes necessary to move an EVA controller port to a different port on the same C-series switch, or to a port on a different C-series switch, the corresponding controller port may become unavailable. Workaround: Restart the EVA controller. Problem Description: EVA controllers running VCS 3.xxx may log into the C-series 4Gbps modules at 1Gbps instead of the default 2Gbps. Workaround: Set the switch port speed to 2Gbps. Problem Description: The EVA4400/6400/8400 and MSA2000 series storage arrays may display as servers in the Fabric Manager topology diagram. Workaround: Perform the following steps to change the display of the array from a host icon to a storage icon. 1. Log into Fabric Manager 2. Under "Physical Attributes" open "End Devices" 3. Select "Hosts" and click on the "Enclosures" tab in the Information Pane 4. Under "Device Type" for the desired device, select "Disk" 5. Save changes by selecting the "Apply Changes" icon on the top left corner of the Information Pane Problem Description: VMware ESX on HP c-Class BladeSystem Server Blade using QMH2462 HBAs and FC Pass-Thru Module may fail to log into the C-series 16-port 2Gbps switching module. Workaround: Set the switch port mode to F. Problem Description: If it becomes necessary to move an MSA1000/1500 controller port to a different port on the same C-series switch, or to a port on a different C-series switch, the corresponding controller port may become unavailable. Workaround: Restart the MSA 1000/1500 controller. Note: Refer to the Cisco MDS NX-OS release notes for a full list of open and closed caveats. 20 MDS Multilayer Director & Multilayer Fabric Switches Release Notes

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20

20
MDS Multilayer Director & Multilayer Fabric Switches Release Notes
HP SPECIFIC KNOWN ISSUES
Problem Description:
Issuing an “End to End Connectivity” to the EVA4400/6400/8400 may
crash both EVA controllers at the same time.
Workaround:
None.
Problem Description:
Issuing an fcping to the EVA4400/6400/8400 may crash the EVA
controller
Workaround:
None.
Problem Description:
If it becomes necessary to move an EVA controller port to a different
port on the same C-series switch, or to a port on a different C-series switch, the corresponding
controller port may become unavailable.
Workaround:
Restart the EVA controller.
Problem Description:
EVA controllers running VCS 3.xxx may log into the C-series 4Gbps
modules at 1Gbps instead of the default 2Gbps.
Workaround:
Set the switch port speed to 2Gbps.
Problem Description:
The EVA4400/6400/8400 and MSA2000 series storage arrays may
display as servers in the Fabric Manager topology diagram.
Workaround:
Perform the following steps to change the display of the array from a host icon to
a storage icon.
1.
Log into Fabric Manager
2.
Under “Physical Attributes” open “End Devices”
3.
Select “Hosts” and click on the “Enclosures” tab in the Information Pane
4.
Under “Device Type” for the desired device, select “Disk”
5.
Save changes by selecting the “Apply Changes” icon on the top left corner of the
Information Pane
Problem Description:
VMware ESX on HP c-Class BladeSystem Server Blade using
QMH2462 HBAs and FC Pass-Thru Module may fail to log into the C-series 16-port 2Gbps
switching module.
Workaround:
Set the switch port mode to F.
Problem Description:
If it becomes necessary to move an MSA1000/1500 controller port to a
different port on the same C-series switch, or to a port on a different C-series switch, the
corresponding controller port may become unavailable.
Workaround:
Restart the MSA 1000/1500 controller.
Note:
Refer to the Cisco MDS NX-OS release notes for a full list of open and closed caveats.