What does 'PSUE, MCU P/S OFF' indicate on HP StorageWorks P9000?
The message 'PSUE, MCU P/S OFF' indicates that the primary storage system was powered off. No recovery procedure is required. The primary storage system automatically restores these Cnt Ac-J pairs when the primary storage system is powered on.
How to recover from a HP StorageWorks P9000 hardware blockade?
If hardware redundancy has been lost due to some blockade condition, remove the hardware blockade or failure according to the SIM. Restore the failed volume pairs (Pairresync). If a failure occurs during execution of the RAID Manager horctakeover command, secondary volumes in SSWS pair status may remain in the master journal. If these volumes remain, execute the pairresync -swaps command on the secondary volumes whose pair status is SSWS. This operation changes all volumes in the master journal to primary volumes. After this operation, restore the volume pairs (Pairresync).
How to resolve HP StorageWorks P9000 Storage communication failures?
If communication between the primary and secondary systems failed because the secondary system or network relay devices were not running, remove the failure from the primary and secondary systems or the network relay devices. If necessary, increase resources as needed (for example, the amount of cache, the number of paths between primary and secondary systems, the parity groups for journal volumes, etc.). Restore the failed pairs (Pairresync).
What does 'RIO overload or RIO failure' mean on HP StorageWorks P9000 Storage?
If an unrecoverable RIO (remote I/O) timeout occurred because the system or network relay devices were overloaded, release failed pairs (pairsplit-S). If necessary, increase resources as needed, such as cache, paths between primary and secondary systems, and parity groups for journal volumes. Re-establish failed pairs (Paircreate).
Why is HP StorageWorks P9000 monitoring data not updated?
If monitoring data isn't updating even though Monitoring Switch is set to Enable, it's because the time setting of SVP was changed. Set Monitoring Switch to Disable, and then set it back to Enable. For further information on Monitoring Switch, see HP StorageWorks P9000 Performance for Open and Mainframe Systems User Guide.
What to do if the HP StorageWorks P9000 Storage Remote Web Console hangs?
If the HP Storage Remote Web Console computer hangs, ensure the issue isn't with your PC, Ethernet hardware, or software. Restart your PC, noting this won't affect storage system operations. Also, verify that all Continuous Access Synchronous requirements are met, such as matching LU types. Confirm that both primary and secondary systems, including data paths, are powered on and fully operational, including NVS and cache. Lastly, double-check all input values and parameters entered on the Remote Web Console computer, such as the remote system S/N and ID, path parameters, and P-VOL and S-VOL IDs, to ensure they are correct.
What to do if HP StorageWorks P9000 Storage paircreate operation times out?
If a paircreate or pairresync operation on your HP Storage results in a timeout error, consider these possibilities: * **Hardware failure:** If a SIM is generated, contact service personnel and retry the Continuous Access Synchronous operations after the hardware issue is resolved. * **Heavy workload:** If no SIM was generated, wait 5 to 6 minutes and check the pair’s status. If the status changed correctly, the operation completed after the timeout message. If the pair status did not change as expected, retry the operation when the system load is lighter. * **Communication Error:** A communication error may have occurred between the Remote Web Console computer and SVP.
How to fix communication timeout on HP Storage?
To resolve a communication timeout on HP Storage, verify that the secondary system is powered on and fully functional, including NVS and cache. Ensure that all data path hardware is properly configured and functional, checking cables, connectors, switches, extender devices, communication lines, and any other connected devices. If issues persist, delete the failed path. You may need to adjust the minimum paths setting or delete the secondary system to delete the path, then add the path or secondary system again using Edit Path or Add RCU.
How to resolve HP StorageWorks P9000 serial number mismatch?
To resolve a serial number mismatch on your HP Storage, first, ensure that you have entered the correct primary system S/N, SSID, and path parameters, including port, link address, and logical address. If the issue persists, delete the failed path. You might need to change the minimum paths setting or delete the secondary system to delete the path. Then, add the path or secondary systems again using Edit Path or Add RCU. For Fibre connections, verify that you've entered the correct Controller ID and that the Fibre Channel topology settings on the primary and secondary systems ports are correct.
What causes HP StorageWorks P9000 Storage initialization to fail?
If your HP Storage initialization fails, ensure that the primary and secondary systems are physically and correctly connected. Verify that you entered the correct remote system S/N, SSID, and path parameters, including port, link address, and logical address. Also, confirm that the Fibre Channel topology settings on the primary and secondary systems ports are correct.
General| RAID Support | RAID 0, 1, 5, 6, 10 |
|---|---|
| Interface | Fibre Channel, iSCSI, FCoE |
| Form Factor | Rack-mountable |
| Model | P9000 |
| Operating System Compatibility | Windows, Linux, VMware, HP-UX |
| Host Interface | Fibre Channel, iSCSI, FCoE |
| Drive Interface | SAS, SSD |
| Drive Types Supported | SSD, SAS |
| Redundancy | Redundant controllers, power supplies, and fans |
| Management Software | HP StorageWorks Command View |
General introduction to the Data Exchange Code Converter functionality and its purpose.
Describes the operational flow and components involved in the Data Exchange Code Converter.
Details the process of converting alphanumeric character data, focusing on single-byte codes.
Explains double-byte character conversion, including mixed single and double-byte data.
Covers the conversion of numeric data fields, including process flow.
Lists the necessary hardware, software, and release notes for the Code Converter.
Details the files and their locations provided on the installation media for UNIX.
Step-by-step guide for installing, uninstalling, and upgrading on UNIX systems.
Explains how to input the license key required for Code Converter operation.
Illustrates the user's workflow for performing data conversion operations.
Describes the supported record formats and field positions for data files.
Introduces MTO conversion, including EBCDIC to ASCII and IBM Traditional Chinese to Big5.
Details the specific conversion of alphanumeric fields in MTO.
Introduces OTM conversion, including ASCII to EBCDIC and Big5 to IBM Traditional Chinese.
Explains how to customize the code conversion table for OTM.
Details the conversion of packed decimal numeric data.
Explains the process for converting zoned decimal numeric data.
Provides a high-level overview of the code conversion table customization process.
Describes the syntax rules for defining conversion statements used in customization.
Explains the command syntax for customizing tables on UNIX systems.
Lists and explains common error codes and their meanings.
Details the format and interpretation of messages generated by the ccnv utility.
Provides guidance on what information to gather before contacting HP support.
Lists other relevant HP documents for further information.
Information on how to obtain technical support from HP.
To Next Page