Search results

System Storage Productivity Center (SSPC) V1.2 and V1.3 machines are pre-configured with HTTP 1.1 support disabled in Internet Explorer 7. Using the SVC Console (GUI) with this browser configuration may result in pages not loading correctly or blank screens when attempting to perform cluster management tasks.

What are the recommended settings for best performance with SAN Volume Controller when using Microsoft Windows operating systems and an application that generates a significant amount of I/O.

OpenVMS version 7.3-2 is unable to discover more than 16 vdisks without rebooting the operating system.

Some versions of 2145-8G4 hardware may have the Hard Disk Drive Activity LED illuminated continuously during normal operation.

This document provides answers for the following types of questions: What are the roles of the quorum disk and quorum disk candidates? How can the current quorum disk candidates be identified? What are the recommendations for changing the managed disks assigned as quorum candidate disks?

The configuration node in an SVC cluster will assert and warmstart if a command takes longer than 3 minutes to complete. This will be seen as a 2030 error in the cluster error log.

If a customer experiences a hard disk drive failure, leading to an IBM engineer removing the drive and installing a new one, they may encounter an error message on the front panel of the node: Node Error 572. This is caused by older versions of SVC software failing to recognize the new model of Hard Disk Drive. This problem affects 2145-8F2 and 2145-8F4 SVC nodes running any of these software levels: * V4.1 at a level below V4.1.1.7 * V4.2 at a level below V4.2.1.10 * V4.3.0 at any level An SVC clu

Prior to V4.3.0.0, certain cluster Ethernet configuration settings may result in connectivity problems when attempting to access the cluster from a host on a different network subnet.

V4.2.1.x versions of the SVC software prior to V4.2.1.5 may display an incorrect number of vdisks when viewing managed disk groups. This may result in the configuration node warmstarting to correct the disk count after performing vdisk migrations.

Configurations where an SVC node is connected to a storage subsystem (identified by WWNN) by only one node port will result in a 1627 error being logged by the cluster. This error code reports insufficient redundancy in the disk controller connectivity. Prior to SVC V4.2.1.8 and V4.3.0.0, this error may be logged erroneously when using a storage subsystem which presents multiple WWNNs to the cluster.