Logging In to SPOCC SPOCC is accessed through a management workstation, which is a machine that has been defined in the SP’s public firewall rules. One or more management workstations are typically defined as part of the installation and setup of the storage system and SP, as described in the installation/deinstallation guide for your version of the HP 3PAR StoreServ Storage system. To log in to SPOCC: 1. Enter the IP address or hostname of the SP in the web browser, and then press Enter. Enter your user ID and password, and then click OK.
NOTE: For a current list of supported browsers for SPOCC, see the Single Point of Connectivity Knowledge for HP Storage Products (SPOCK), located. Changing the SP Password by Using SPOCC To protect the Service Processor against unauthorized access, HP recommends that you change the default passwords and maintain the new passwords so that they are available for support personnel. To change the Service Processor password: 1. Log in to SPOCC. In the left navigation pane, click SPmaint. Under Service Processor - SP Maintenance, click SP Control/Status.
Under Service Processor - SP Control Menu, click SP User Access Control. Under Service Processor - SP User Access Control Menu, click Change User Password. In the Select User list, select the user name whose password you want to change. In the New Password field, enter the new password. NOTE: A valid password is between 7 and 32 characters long and uses only alphanumeric characters and the following special characters:. Period (.).
Forward slash (/). Plus sign (+).
Equals sign (=). Hyphen (-) 8. In the Confirm Password field, enter the new password again. Click Change Password.
SPMAINT Overview The SPMAINT utility is an interface for the support (configuration, maintenance, and update) of both the storage system and its SP. Use SPMAINT as a backup method for accessing the SP; SPOCC is the preferred access method. In this guide, the features of the SPMAINT utility are divided into the following major categories:.
Control of the SP (for more information, see ). Network configuration (for more information, see ) 10 Overview.
. page 16. page 19.
page 20. HP 3PAR StoreServ 7000 Storage SmartStart 1.2 Software User's Guide Abstract This document provides the information needed to use HP 3PAR SmartStart to install and configure HP 3PAR StoreServ 7000 Storage systems. HP Part Number: QL226-96854 Published: June 2013. © Copyright 2012–2013 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 1 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Contents I Using SmartStart to Configure Storage.6 Welcome.7 1 Prepare to Configure.9 FAQ.11 2 Setting Up the Service Processor.13 Accessing the Service Processor Setup Wizard.13 Configuring Service Processor Networking.14 Configuring Remote Support.14 Configuring System Support Information.15 Configuring Your Time Zone.15 Changing Passwords.15 Troubleshooting.16 Troubleshooting the Connection to the Service Processor.16. Summary: iSCSI Host Configuration.30 6 Configure Storage.31 Create Hosts.32 Welcome to the Create Host Wizard.32 Host Settings.33 Fibre Channel Settings.33 iSCSI Settings.33 Summary.34 Create Virtual Volumes.34 Welcome to the Create Virtual Volumes Wizard.34 Configure Virtual Volume.34 Policies and Geometry.35 Summary.36 Export Virtual Volumes.36 Welcome to the Export Virtual Volumes Wizard.36 Export.36. 18 Documentation feedback.61 Glossary.62 Contents.
Part I Using SmartStart to Configure Storage Gather the information you will need to use SmartStart to “Prepare to Configure” (page 9) configure your HP 3PAR StoreServ 7000 Storage system. Learn more about how HP 3PAR storage systems work. “Understanding Storage” (page 40) NOTE: If you are not familiar with HP 3PAR storage systems, HP highly recommends that you read this short introduction. Welcome Welcome to HP 3PAR SmartStart for HP 3PAR StoreServ 7000 Storage systems.
SmartStart helps you configure: HP 3PAR StoreServ 7200 Storage system HP 3PAR StoreServ 7400 Storage system HP 3PAR StoreServ 7450 Storage system NOTE: If you are setting up multiple HP 3PAR StoreServ 7000 Storage systems, be sure to set up each storage system completely before starting to set up the next storage system. Accessing Online Help To view online help, do one of the following: Press F1. Select Help Online Help. 1 Prepare to Configure Prerequisites IMPORTANT: Before using SmartStart to configure your system, you must complete the setup tasks detailed in the HP 3PAR StoreServ 7000 Storage Installation Guide. To access the HP 3PAR StoreServ 7000 Storage Installation Guide, go to the HP 3PAR StoreServ Storage site and click the Support link for your product: A DHCP network is no longer required to set up a virtual Service Processor (VSP). ◦ The HP 3PAR storage system setup is verified, the storage system is powered on, and the LEDs are functioning correctly. ◦ Either the physical Service Processor is installed and powered on and you have assigned it an IP address, or the virtual Service Processor is installed and connected and you have determined the temporary IP address.
– IP address (IPv4 only) Subnet mask – Gateway IP address – New password to assign to the user account for the storage system (3paradm) – NOTE: Passwords for the 3paradm user account are between six and eight characters in length and can include all printable characters. CAUTION: Do not run more than one instance of SmartStart on the same host system. HP 3PAR SmartStart includes online help. To access online help, do one of the following: Press F1. Select Help Online Help. You can also find storage-related information at: Prepare to Configure.
2 Setting Up the Service Processor Use SmartStart wizard step 2, Set up systems, to set up the Service Processor and the HP 3PAR StoreServ Storage system. You need to set up the Service Processor and the storage system only once for each new HP 3PAR storage system. For more information about determining the temporary IP address or assigning the Service Processor IP address, see the HP 3PAR StoreServ 7000 Storage Installation Guide.
In the User name field, enter setupusr. You do not need to enter a password for setupusr to access this wizard for the first time. for HP to perform fault detection and analysis on your HP 3PAR StoreServ Storage system that help maximize your storage availability.
All remote communications are encrypted and transferred securely to HP 3PAR Central, and no customer application data is ever transferred. No other business information is collected, and the data is managed according to the HP Data Privacy policy. Troubleshooting Troubleshooting the Connection to the Service Processor If the Check Your Connection dialog box appears during the setup process in Service Processor Setup wizard step 7, Apply Settings, the Service Processor Setup wizard might be unable to connect to the Service Processor. Verify the following: Your browser is still connected to the network.
3 Setting Up the HP 3PAR StoreServ Storage System Before you can configure the HP 3PAR StoreServ Storage system, you must initialize it. The Storage System Setup wizard verifies your HP 3PAR storage system configuration, initializes the storage system, and runs initialization tests on the storage system. To set up and configure the HP 3PAR storage system: Verify that the Service Processor is on the same subnet of the network as the HP 3PAR StoreServ 7000 Storage system you are setting up. Figure 1 StoreServ Serial Number Configuring Networking Enter the name and IP address information for your new HP 3PAR StoreServ Storage system. For more information, see your completed Storage System Software Installation Checklist from the HP 3PAR StoreServ 7000 Site Planning Manual. Configuring Your Time Zone You can do the following: Copy the time zone settings from the Service Processor to the HP 3PAR StoreServ Storage.
Continuing SmartStart Setup After the Storage System Setup wizard initializes the HP 3PAR StoreServ Storage system, do the following: Click Finish in the Setup Progress and Results step to exit the Storage System Setup wizard. NOTE: The wizard continues to run tests in the background after you have exited the Storage System Setup wizard. Click Home to return to the SPOCC home page.
The Transfer Status entry indicates the overall status of SP file transfer. To access the SP File Transfer Monitor, click Transfer Status. Verify that SP file transfer is successful: The Last transfer status entry should include information about the last SP transfer, including the date and time and a status of OK. Zip the downloaded log files. Contacting HP Support about System Setup For worldwide technical support information, see the HP support website: Before contacting HP about accessing the Service Processor Setup wizard or the Storage System Setup wizard, collect the following information: SmartStart log files Service Processor log files Product model names and numbers. 4 Connect to the HP 3PAR StoreServ 7000 Storage System Click the Connect to the storage system link.
In the IP Address or Name field, do one of the following: If this is the first time you are connecting to the HP 3PAR storage system, enter the name or IP address of the HP 3PAR StoreServ 7000 Storage system. 5 Configure the Hosts export (or present) virtual volumes to hosts—which enables the host system to write data to and read data from the HP 3PAR StoreServ Storage system—you must configure either Fibre Channel host connections or iSCSI host connections.
For more information about exporting volumes, see “Exporting Virtual Volumes”. To ensure that your HP 3PAR StoreServ Storage system remains available if a path fails, connect the host system to the HP 3PAR storage system using multiple paths.
Before using SmartStart to configure Fibre Channel connections, do one of the following: If you are connecting the host and HP 3PAR StoreServ Storage systems directly, verify that the appropriate cabling is in place between the host system and the HP 3PAR storage system. iSCSI Connections To set up iSCSI connections: Verify that your network supports 10-GB iSCSI connections. Connect the host system to the HP 3PAR StoreServ Storage system using multiple paths to ensure that your HP 3PAR storage system remains available if a path fails.
Configuring iSCSI Connections To access the iSCSI Host Configuration wizard and configure iSCSI connections, click the Configure iSCSI host link in the SmartStart wizard. Configuring Local and Remote Connections You can use SmartStart to do the following: Connect the local host (the Windows Server 2008 R2 or Windows Server 2012 server into which you inserted the SmartStart media) to the HP 3PAR StoreServ Storage system Connect a remote host (any Windows Server 2008 R2 or Windows Server 2012 server other than the Windows Server 2008 R2 or Windows Server 2012 server into which you inserted the SmartStart media) to the HP 3PAR storage system. Even if you can configure and validate only one Fibre Channel connection, you can still configure the Fibre Channel host. CAUTION: If you are using only one supported Fibre Channel connection and that connection fails, the host will not be able to access (read from or write data to) the HP 3PAR storage system.
Summary: Fibre Channel Host Configuration Review your Fibre Channel setup. Click Finish. If you are connected to the local host and you rebooted the host system, the local host reboots. After the local host has finished rebooting, launch SmartStart and continue setup.
If you are connected to the remote host and you rebooted the host system, the remote host reboots. Configure Multipath I/O (MPIO) Multipath I/O (MPIO) helps ensure the stability of the connection between the host and HP 3PAR StoreServ Storage systems. To configure MPIO: Click Configure. If the wizard displays the Reboot when finished check box, select it. In order to complete this MPIO configuration, the wizard will reboot the host system at the end of the iSCSI host configuration process. Configure the iSCSI Target Select the IP address of the iSCSI initiator on the host system. Click Configure.
Troubleshooting the iSCSI Connection If the iSCSI initiator on the host system cannot connect to the HP 3PAR StoreServ Storage system, verify your configuration: Verify your IP settings: IP address. 6 Configure Storage The steps in SmartStart wizard step 5, Configure storage, guide you through creating basic storage on your HP 3PAR StoreServ 7000 Storage system. NOTE: You can use the HP 3PAR Management Console to delete any hosts, virtual volumes, or exports you create using SmartStart. Default CPGs The setup process automatically creates default CPGs on your HP 3PAR StoreServ 7000 Storage system. The CPGs that are created depend on your HP 3PAR storage system’s drive types, number of drive cages, and RAID types, as described in the following table. Drive Type RAID Type Default CPG Created.
Host Settings In the General group box: System - Select the system to create the new host. Domain - Select the domain in which to create the new host. Select if not applicable.
Name - Enter the host name. Names are case-sensitive. Set Name - Select the host set in which to create the new host. If required, click the Target CHAP check box. The CHAP Name field displays the system name. Enter a secret/password in the CHAP Secret field for Target CHAP. NOTE: Rules for the CHAP group box in the following step are as follows: When the Initiator CHAP check box is selected, CHAP Name is initialized with the host name (default).
In the Allocation group box: Select how the volume will be provisioned. Selecting Thinly Provisioned results in the creation of a Thinly Provisioned Virtual Volume (TPVV). Selecting Fully Provisioned results in the creation of a base volume. NOTE: To create TPVVs, the HP 3PAR Thin Provisioning Software license is required. Size - Enter the size of the volume. In the Policies group box, enable any of the following, as needed: Allow stale snapshots Restrict export to one host Enable zero detect (default) Retention Time — If you enable this, enter a value in the corresponding field, and then select either days or hours. In the Export To group box: Select either Host (Host Sees) or Host Set (Host in Set).
From the host or host set list, select the hosts that you want to export the virtual volumes CAUTION: If you make any changes in the advanced options and then click to clear the Show advanced options check box, a warning dialog is displayed to warn you that the selected advanced options will be lost. Add Virtual Volumes to Windows Select the virtual volume that you want to configure as a Windows disk. The virtual volume is displayed as a virtual volume device.
If the volume is less than 2 TB, SmartStart initializes the Windows disk as Master Boot Record (MBR). 7 Install the HP 3PAR Management Console To manage your HP 3PAR StoreServ Storage systems and access advanced features and functionality, use the HP 3PAR Management Console.
To install the Management Console, click the Install the HP 3PAR Management Console link. Accessing the Management Console To access the HP 3PAR Management Console do one of the following: If you are an administrator, launch the Management Console from the Management Console.
Part II Understanding Storage For more information about storage concepts, see the HP 3PAR StoreServ Storage Concepts Guide. To access this document, go to the HP 3PAR StoreServ Storage site and click the Support link for your product: For information about supported hardware and software platforms, go to the Single Point of Connectivity Knowledge (SPOCK) website: For conceptual information about. 8 Storage Software Components HP 3PAR StoreServ Storage systems include both the hardware components that physically store your data and the software applications that manage your data. An HP 3PAR storage system is composed of the following logical data layers: Physical disks Chunklets—On an HP 3PAR StoreServ 7000 Storage system, chunklets are 1-GB units of disk space. Each layer is created from elements of the layer above, as follows: Chunklets are drawn from physical disks. Logical disks are created from groups of chunklets. Common Provisioning Groups (CPGs) are groups of logical disks.
Virtual volumes use storage space provided by CPGs. Physical Disks physical disk is a disk drive mounted on a. You can create the following types of virtual volumes: Fully provisioned virtual volumes—Volume size is fixed. No separate license is required to create fully provisioned virtual volumes.
Thinly provisioned virtual volumes—Also known as Thin volumes, these volumes allocate space on demand in small increments. To create Thin volumes, the HP 3PAR Thin Provisioning Software license is required. 9 Hosts The HP 3PAR StoreServ Storage system sees a host as a set of Fibre Channel World Wide Names (WWNs) or iSCSI names, or in other words, a set of host I/O paths. The host system uses these I/O paths to perform read/write operations on exported virtual volumes on the storage system.
The HP 3PAR storage system automatically detects hosts that are physically connected to ports on the storage system. to the storage system. The information gathered from the Host Explorer agent is visible to uncreated hosts and assists with creating hosts and diagnosing host-connectivity issues. How Host Explorer Helps You Create Hosts When you create a host, the system displays the unassigned WWNs or iSCSI names as follows: When the Host Explorer agent is running on the attached hosts, the system automatically groups the WWNs or iSCSI names for the host together, which helps you create the host. 10 Common Provisioning Groups A common provisioning group (CPG) creates a virtual pool of storage space that allows up to 4,095 virtual volumes to share the CPG's resources.
When you create virtual volumes (fully provisioned virtual volumes or Thin volumes), the volumes draw storage space from the CPG's storage space pool. 1 1 Virtual Volumes Virtual volumes are the only data layer visible to host systems. Virtual volumes draw storage space from CPGs. Virtual volumes become visible to host systems when you export (present) them to hosts. Virtual volumes are exported as LUNs to hosts. You can create physical copies or virtual copies (snapshots) of virtual volumes. Fully provisioned virtual volumes and Thin volumes have three separate data components: User space contains the user data.
The user space is the area of the volume that corresponds to the regions in the CPG that are available to the host. Thus, the user space is the part of the virtual volume you export to the host as a LUN.
Virtual copies are created using copy-on-write techniques, which are available only with the HP 3PAR Virtual Copy Software license. Thousands of snapshots of each virtual volume can be created, up to the amount of storage space available.
Depending on your system configuration, you can make up to 500 virtual copies of a base volume. 12 Exporting Virtual Volumes Virtual volumes are the only data layer you can make visible to hosts. In order to make virtual volumes visible to hosts, you must export (present) the virtual volume to the host. The export process creates an association between the volume and a LUN. You configure the characteristics of this association when you create the Virtual Volume-LUN pairing (VLUN). 13 RAID RAID is a storage functionality that distributes data in units called chunklets across physical disks in order to create redundancy and therefore increase the stability of your stored data. On the HP 3PAR StoreServ 7000 Storage system, a chunklet is 1 GB.
RAID is one of the parameters of a CPG, the storage pool from which volumes allocate storage space. 14 User Roles and Rights To access an HP 3PAR StoreServ Storage system, you must have a user account. Each HP 3PAR OS user is assigned a role, and each role is assigned a set of rights. The roles and rights assigned to the user determine the tasks the user is allowed to perform on a system.
15 Managing Storage To manage your HP 3PAR StoreServ Storage system, use the HP 3PAR Management Console. To install the Management Console, go to SmartStart wizard step 6, Install the Management Console. For more information about using the Management Console, do one of the following: ◦.
The 3PAR SSMC (StoreServ Management Console) is now the go to management tool for 3PAR systems. In this how to guide we will be covering how to download and install the 3PAR StoreServ Management Console. If you are working with an older system running 3PAR OS 3.1.3 you will need to use the 3PAR Management Console. Be sure to checkout my post on installing the to get up and running. StoreServ Management Console Requirements As above first assure your system is running 3PAR OS 3.1.3 or above. SSMC is a web based console which requires you to install the SSMC server on either a Linux or Windows based server. This post will deal with the procedure to get SSMC installed on a Windows server.
First ensure your SSMC server meets the following requirements taken from the. Supported host platforms Supported browsers. Microsoft Internet Explorer. Microsoft Edge. Google Chrome. Mozilla Firefox The minimum physical requirements. Two logical processors.
4 GB RAM. 2 GB free disk space. Supported 64-bit operating system Whilst the above is the minimum recommended specs for installation. The table below shows the recommended specs depending on the scale of your 3PAR infrastructure. Port 8443 on the SSMC server must be open to inbound connections. SSMC Install Before you begin you will need to download SSMC from the 1 Double click the setup file to begin 2 Read through the introduction and click next 3 Agree to the license agreement 4a If you are upgrading from a previous version of SSMC, a box will pop up advising that a previous version was detected just click OK.
If you are not upgrading skip to step 7. 4b You will then see a screen informing you the old version is being removed 4c Next you are given the option to use existing SSMC data which preserves the connections to existing systems. If you are upgrading move to step 7, for a fresh install read on.
5 If you are not upgrading next you will select the install location. Just leave it at default unless you have reason to change it and choose next 6 The default port is 8443, leave it at this unless you have a specific reason to change it 7 You will see a summary screen of your options just click install 8 You will then see a screen reminding you that inbound connections to port 8443 need to be open Finally you will see the install summary screen followed by the install complete screen Next you will need to add your 3PAR systems to SSMC.
I have covered this in my post. If you wish to install any of the other 3PAR management tools check out these related posts: Finally you can read more about the SSMC install process and more in the. I have tried to upgrade SSMC from 2.3. I uninstalled old version and have run new version, at the end of installation I got message that SSMC Service is not in the running state. When I checked under services, SSMC service was not there. I tried a few more times but same result. Then I uninstalled 2.3.1 and tried to install old version (2.3) that was running on this server before I tried upgrade, but got same message.
I am logged as local administrator on this server, I also tried to run installation.exe file as administrator still no luck. I have tried to install 2.3.1 on other server (VM) and installation is successful. It seems that problem in in my Windows 2008 R2 server. Any idea what can be the reason for installation to fail. I have tried everything and no luck. Even thou I uninstalled old version of the software and have choose option to delete all data during uninstall process, removed everything from registry, when I install new version it discovers that this software was already installed and asks me if I want to use settings from previous installation.
At the end of installation process I am getting error that service can’t start. I have reformatted disk drive and reinstalled OS. After this I was able to install new version of the software and it was working fine.
Upgrading To Inform OS 3.1.2 Before beginning an upgrade of the 3PAR Inform OS to version 3.1.2 it is recommended to use the following guides:. HP 3PAR Service Processor Software Installation Instructions When performing the upgrade, 3PAR Support will either want to be onsite or on the phone remotely. They will ask for the following details:. Host Platform e.g. StoreServe 7200.
Architecture e.g. SPARC/x86. OS e.g. 3.1.1. DMP Software. HBA details.
Switch details. 3PAR license details A few useful commands here are:. showsys. showfirmwaredb.
showlicense. shownode A quick run threw of the items that are recommended to be checked. The first item is your current Inform OS version as this will determine how the upgrade has to be performed Log into your 3PAR via SSH and issue the command ‘showversion’ This will give you your release version and patches which have been applied. Here our 3PAR’s is on 3.1.1 however it doesn’t specify if we have a direct upgrade path to 3.1.2 or not, see table below. If going from 3.1.1 to 3.1.2 then Remote Copy groups can be left replicating, if you are upgrading from 2.3.1 then the Remote Copy groups must be stopped.
Any scripts you may have running against the 3PAR should be stopped, the same goes for any environment changes (common sense really). The 3PAR must be in a health state and each node should be multipatted and a check should be undertaken to confirm that all paths have active I/O. If the 3PAR is attached to a vSphere Cluster, then the path policy must be set to Round Robin. Once you have verified these, you are good to go.
3PAR Virtual Port s – NPIV NPIV allows an NPort which is that of the 3PAR HBA to assume the identity of another port without multipath dependency. Why is this important Well it means that if the storage controller is lost or rebooted it is transparent to the host paths meaning connectivity remains albeit with less interconnects. When learning any SAN, you need to get used to the naming conventions. For 3PAR they roll with it is Node:Slot:Port or N:S:P for short. Each host facing port has a ‘Native’ identify (primary path) and a ‘Guest’ identity (backup path) on a different 3PAR node in case of node failure. It is recommended to use when working with 3PAR and to connect the Native and Backup ports to the same switch.
S1 – N0:S0:p1 S2 – N:S0:P2 S3 – N0:S0:P1 S4 – N0:S0:P2 For NPIV to work, you need to make sure that the Fabric switches support NPIV and the HBA’s in the 3PAR do. Note the HBA’s in the Host do not need to support NPIV as the change to the WWN will be transparent to the Host facing HBA’s. How does it actually work? Well if the Native port goes down, the Guest port takes over in two steps:.
Guest port logs into Fabric switch with the Guest identity. Host path from Fabric switch to the 3PAR uses Guest path The really cool thing as part of the online upgrade, the software will check:. Validate Virtual Ports to ensure the same WWN’s appear on the Native and Guest ports. Validate that the Native and Guest ports are plugged into the same Fabric switch If everything is ‘tickety boo’ then Node 0 will be shutdown and transparently failed over to Node 1.
After reboot Node 0 will have the new 3PAR OS 3.1.2 and then Node 1 is failed over to Node 0 Guest ports and Node 1 is upgraded. This continues until all Nodes are upgraded. When performing an upgrade it shouldn’t require any user interaction, however as we all know things can go wrong.
A few useful commands to have in your toolbox are:. showport. showportdev. statport/histport. showvlun/statvlun Posted in, Tagged.
Let’s say that we have had our StoreServ in and running for a few months and everything has been ‘tickety boo’ until we have an error or as I prefer to call it a ‘man down’ scenario. What are the issues we are going to encounter? Well these can be broken down into three areas.
Configuration Errors Err we the awesome StoreServ administrator has configured the 3PAR in an unsupported manner. Component Failure Not so bad, as it wasn’t caused by us! We have a component failure e.g.
DIMM, Drive etc 3. Data Path We have an interconnect failure or perhaps even faulty e.g. SAS cable In the following section we are going to cover these in a little more detail. Configuration Errors These would mostly come from incorrect cabling, adding more cages than is supported and adding a cage to the wrong enclosure. The good news is that configuration errors are detected by the StoreServ and you will receive an alert. Let’s say that you have cabled incorrectly, most likely if you loose a cage, then you will loose connectivity to all the other cages downstream.
The correct cabling diagram is shown below. Fixing an issue where you have to many Disk Enclosures above the supported maximum e.g. Six enclosure on a StoreServ 7200 two node, this is pretty simple, unplug it!
It’s pretty obvious really, but make sure that all your devices are supported, two which aren’t are:. SAS-1. SAS connected SATA drives Component Failure I think the first thing to remember is that connectivity issues can be caused by component failures. Components can be broken down into two areas Cage and Data Path. The good news is that if everything is cabled correctly we have dual paths. The only exception to this is the back plane. Any failure of a Cage component e.g.
Power Supply, Fan, Battery, Interface Card, will result in an alarm and an Amber LED being displayed until the component can be replaced. Right so what happens then if we have a back plane failure? Well if it’s the original StoreServe 7000 enclosure you want to shut the system down and phone HP! If you a Disk Enclosure back plan failure then your choices are as follows:.
If you have enough space on existing disks, then the disks can be vacated and the back plane replaced. If you don’t have enough space on existing disks, but another Disk Enclosure can be added. Then add another Disk Enclosure, vacate the disks and then remove the failed Disk Enclosure. If you have no space and you cannot add another Disk Enclosure, then err work quickly! Data Path Faults The data path is essentially the SAS interconnects. It is comprised of:.
SAS Controller or HBA. SAS Port. SAS Expander (Drive Enclosures). SAS Drives. SAS Cables W e have two types of ‘phy’ ports, narrow and wide. Narrow consists of a single physical interconnect and wide consists of two physical interconnects.
I prefer working in pictures as they make more sense to me. We can see the SAS Controller and Disk Enclosures are connected via 4 x Wide Physical Ports (Phys). Whereas the individual Disk Drives are connected to SAS Expander (Drive Enclosure) the by a 1 x Narrow Physical Port (phys). In exactly the same way as we can have ethernet alignment mismatches when negotiating e.g.
2 x 1 Gb links, one negotiates at 100 Mb Half Duplex the same occurrence can happen with SAS. 4 x Wide Ports into 4 x Wide Ports and one port doesn’t negotiate correctly. If you do receive a mismatch then this will result in poorer performance, CRC errors or device resets. Perhaps one of the hardest issues to resolve are intermittent errors which only become apparent when the StoreServ is under load. In the above scenario where we have 4 x Wide Ports connected to another 4 x Wide Ports but one port hasn’t negotiated correctly then it’s won’t be until we need to utilize 75% or more of the link that we experience the problem. Robert beverly hale gesture drawing.
The good news is that these issues can be detected in the ‘phy error log’. To view the link connection speeds issue the command showport -c Naturally the link speeds should represent your fabric interconnects.
How to Download Online Valentine's Day Videos; Part 2. Top 5 Happy Videos for Valentine's Day; Part 1. Download Online Valentine's Day Videos in 1 Click Although there are plenty of online services to download the videos from different sources but most of them are not reliable and are filled with the Ads and everything. Free valentine video. Videos 1 album. 11 video Add to. The Valentine's Day. Phil lester & dan howell. 21 views three years ago. YouTube 6:52. If you want to download it. I once watched the Phan Valentine’s Day video out of. Phan valentine's day video phan vday video valentines day video stay.
Posted in, Tagged. This is where things start to pick up a bit as we venture onto adding the StoreServ 7000 into the Virtual Service Processor. Browse to your VSP using the IP Address you configured in and login with your credentials. A quick side note you may here the term SPOCC banded around quite a bit it stands for ‘Sevice Processor Onstie Customer Care’. Any how, click on SPMaint Select Inserv Configuration Management Guess what we need to Add A New InServ Enter the IP Address of your StoreServ 7000 Verify the details and click ‘Add New InServ’ Man Down – Replacing a Failed Hard Drive A slightly over exaggerated title, but I’m sure it grabbed your attention. The StoreServ has a feature called ‘Guided Maintenance’ this essentially shows you how to perform a number of tasks e.g.
Replace a DIMM, Fiber Channel Adapter. This can be found under Support Guided Maintenance Perhaps the most common failure you will encounter is replacing a fauly disk. This can be done via the CLI by SSH onto your StoreServ or via the VSP by going to SPMaint Execute a CLI Command and entering ‘servicemag status’. As I don’t have a failed disk it shows ‘No servicemag operations logged’ If you did have a failed disk, you will be told which Cage and Magazine has a failure and that the Magazine has been taken offline to allow you to replace the faulty HDD. Once you have replaced the disk, give it 15 minutes and re issue the servicemag status command and when complete you will see ‘No Servicemag operations logged’.
You can also check via the GUI in the 3pAR Inform Management Console by going to ‘System’ Physical Disks and then looking down the cages. Double check the HDD if Failed and that Free Capacity and Allocated Capacity is displayed as all zeroes. If this is the case, then pop the badboy out and pop a new one in. Man Down – Servicing a Power & Cooling Module (PCM) This is only available via SSH onto your StoreServ or via the VSP by going to SPMaint Execute a CLI Command To confirm if the PCM is down issue the command shownode -ps As you can see mine are OK, however, if you had a failure then replace the SPM and run the command again until you see both PCM are OK. Note this can be done live without any downtime. Man Down – Replacing and Power & Cooling Module (PCM) Battery The Power and Cooling Module Battery is again only available via SSH onto your StoreServ or via the VSP by going to SPMaint Execute a CLI Command.
The battery is located at the top of the PCM. To verify your battery status issue the command showbattery Again if it was failed replace the part and re issue the showbattery command to verify it’s healthy. Drive Enclosure Expansion The StoreServ 7200 is limited to five extra drive enclosures. Two can be connected via DP1 and three can be connected via DP2. The StoreServ 7400 with two nodes is limited to nine extra drive enclosures. Four can be connected via DP1 and five can be connected via DP2.
Note these figures double to a four node StoreServ 7400. You might be thinking why does DP2 have more connections? Well the answer if that DP1 is also responsible for the internal connections, which evens things out. The procedure to add an additional drive enclosure is:.
Rack the Drive Enclosure. Install Power & Cooling Modules. Power On. Install Hard Drives.
Run command ‘servicecage startfc’ this will move all I/O to Node 1 (remember Node 0 is the first Node). Connect the SAS cable, the first connection should be out IFC 0 and in IFC0 on the new Drive Enclosure.
3par Service Processor
Run command ‘servicecage endfc’ and this will restore I/O to Node 0. Repeat for same procedure for Node 1. Connect the Drive Enclosure to the Controller Nodes One of the slightly tricky parts is the disk shelf cabling. Some rules to follow:. Event Nodes go to Even Controllers.
Odd Nodes go to Odd Controllers. Odd Nodes connect to the highest Disk Shelf first. Even Nodes connect to the lowest Disk Shelf first Run the showcage command to verify you new Disk Enclosure is recognised.
Disk Upgrade Rules These are the golden rules which need to be followed. You need to add the same number of disk drives to the Drive Enclosure as are in the Node Enclosure e.g. If you are using 24 disks in your Node Enclosure you will need to add 24 disks to your rive Enclosure. When adding disks to a StoreServ 7200 without a Disk Enclosure they should be done in pairs and placed in the lowest slots. On a 2.5″ Disk Enclosure this is left to right. On a 3.5″ Disk Enclosure this is per column left to right and top to bottom within the column. For a StoreServ 74000 without a Disk Enclosure four node system the same rules apply except you have to add four disks at a time.
If you have a StoreServ 7200 with a Disk Enclosure. You would need to add a minimum of four disks. Two to the Node Enclosure and two to the Drive Enclosure.
Posted in, Tagged. In the blog post we covered an overview of the StoreServ 7000 hardware the next stage is looking at ‘what we do next’. Setup A StoreServ VSP The Virtual Service Processor comes as an Virtual Appliance in the OVF format, this can only be installed on.
From a design perspective it’s not a good idea to have the VSP on the StoreServ. Why’s this you ask?
Well, the VSP is responsible for reporting back any issues to 3PAR Central that the StoreServ has. If the VSP is on the Virtual Volumes provided by the StoreServ then how can it report back? The answer is it can’t. Recommended practice is to place the VSP on a RAID protected local HDD of an ESXi host. I’m not able to walk through deploying the OVF VSP as it doesn’t appear to have been released for download and therefore it’s likely to only come with a DVD media kit when ordering the product.
From the installation guide, the only thing to note is that it’s recommended to use Thin Provisioning. After launching the OVF you need to login to the VSP, my understanding this will be via SSH like the F400’s.
U: root P: hp3par Once logged in, the VSP would have obtained an IP Address from DHCP, run the command ifconfig -a Which will return the IP Address to enable the HP SmartStart software to connect to allow configuration of the VSP. SmartStart SmartStart requires Windows Server 2008. It is the software used to configure your StoreServ 7000. A couple of items to note:. You require Administrator access on the Windows Server 2008. VSP and the StoreServ 7000 much be on the same subnet as the Windows Server 2008 running are running SmartStart on. The screen shots below are taking from the HP training, hopefully the process makes sense without me actually having an actual StoreServ to configure!
Initial SmartStart Welcome Screen Prepare to Configure This is the part where you now want to ‘click’ on Setup Service Processor and enter the IP Address you received from running the ifconfig -a command and login using root hp3par The SP Setup Wizard will then launch on a Web Page. Next you will enter some basic networking details which are:. Service Processor ID, I believe this is obtained from HP. Service Processor Hostname e.g. StoreServ-VSP001. IP Address. Subnet Mask.
Default Gateway. Domain Name.
DNS Server(s) Next you need to configure the support package. You have three choices:. Active – this allows HP to remotely perform maintenance tasks on the Virtual Service Processor and StoreServ.
Log files are automatically sent to HP. Passive – this sends log files only. No Support – you need to send log files manually Next enter your Time Zone and enter a NTP server. My recommendation is to use an internal DC as your NTP server to avoid time skew. Lastly, you confirm your settings and apply them.
Naturally, your IP address will change so remember that you will need to reconnect to this to make any further changes. Setup StoreServ 7000 Back to the SmartStart and the next thing we want to do is select ‘Set up the Storage System’. This takes you back to the Virtual Service Processor, so you need to login with U: root P: hp3par Click next a couple of times and then at this point you will need to enter the ‘assembly serial number’ which is on the StoreServ or your HP 3PAR System Assurance Document. To be clear this is the serial number for the complete StoreServ not an individual component. The StoreServ is then verified with the model, 3PAR OS version and the number of Nodes, hits next.
Enter networking information for:. Hostname e.g. StoreServ-001. IP Address. Subnet Mask.
Default Gateway Next we configure the time, it is recommended to get the time from the Virtual Service Processor Lastly, click Next and verify the installation. Posted in, Tagged. This is the first in a series of blog posts as I work towards the One of the issues I have had when learning the new range of HP products is the naming convention, so below is my ‘dummies guide’. If I have gotten any of these wrong, please let me know. Old 3PAR New StoreServ Old LeftHand New StoreVirtual Old ‘X’ NAS Range New StoreEasy Old P2000 New StoreSure Old Storage Networking New StoreFabric Old Tape Drives New StoreEver Old IBRIX New StoreAll Old DataProtector New StoreOnce StoreServ 7000 Essentially this is a replacement for the F200 and F400, it is meant to be customer installable, but as you can see from the issues that had when installing a StoreServ 7200, I think this is a work in progress whilst HP get to grips with the ‘SmartStart’. The StoreServ 7000 comes with a Virtual Appliance (OVF) aptly named the ‘Virtual Service Processor’ which runs on ESXi5 or above.
It is recommended not to install the Service Processor on the StoreServ rather on either local drives. Note you can obtain a Physical Service Processor if required.
The Service Processor used to come as a 1U server and is used to send remote error detection and reporting to ‘HP 3PAR Central’ The StoreServ 7000 can use SAS and SATA drives in both SFF and LFF. For both hard drive type SSD are available. Note that no Fiber Channel drives are available.
StoreServ likes to use ‘0’ alot, so you need to remember that Nodes start with 0 same with Drive Bays! The StoreServ 7000 comes in two flavors: 7200 – Two Node Chassis The base enclosure comes with:.
2 Nodes. 4 FC Ports. 24 SFF Slots. 24GB Cache (8GB Control Cache & 4GB Data Cache Per Node). 1.8 GHz Quad Core CPU.
2 x 1 Gb ports for Management & Remote Copy For extra storage capacity upto five additional disk cages can be added either SFF or LFF giving a total of 144 drives. 7400 – Two Node Chassis The base enclosure comes with:. 2 Nodes. 4 FC Ports. 24 SFF Slots. 32GB Cache (8GB Control Cache & 8GB Data Cache Per Node). 1.8 GHz Hexa Core CPU.
2 x 1 Gb ports for Management & Remote Copy For extra storage capacity upto nine additional disk cages can be added either SFF or LFF giving a total of 240 drives. Can be upgraded to four node configuration. For HBA’s you can add an optional:. 4 Port 8 Gb/s FC which can be used for SAN connectivity or Remote Copy. 2 Port 10 Gb/s iSCSI/FCoE, note that FCoE isn’t yet supported. Sometimes a picture speaks a thousand words, the picture below shows the connectivity at the back of each StoreServ node 7400 4 Node Interconnect When deploying a 7400 4 Node we need to follow the correct cabling schema. HP have been quite smart and introduced a ‘black to white’ and ‘white to black’ chema, however it’s not clearly labelled, so for the avoidance of doubt.
Controller A, Node 0, Interconnect 0 Controller B, Node 2, Interconnect 1 Controller A, Node 0, Interconnect 1 Controller B, Node 3, Interconnect 0 Controller A, Node 1, Interconnect 0 Controller B, Node 3, Interconnect 1 Controller A, Node 1, Interconnect 1 Controller B, Node 2, Interconnect 0 Disk Shelves Disk Shelves comes in two flavors: H6710 which is a 2U 24 Bay SFF Drive Chassis. Drives should be installed left to right with a minimum of two drive increments. H6720 which is a 4U 24 Bay LFF Drive Chassis Drives should be installed bottom to top with a minimum of two drive increments.
Note that all columns should contain the same drive type e.g. 600GB 15K SAS On both disk shelves, DP-1 is IN and connects to the original Nodes.
DP-2 is OUT and connects to additional disk shelves. One of the slightly tricky parts is the disk shelf cabling. Some rules to follow:.
What Is A Service Processor
Event Nodes go to Even Controllers. Odd Nodes go to Odd Controllers. Odd Nodes connect to the highest Disk Shelf first.
Even Nodes connect to the lowest Disk Shelf first Posted in, Tagged, Posts navigation.
HP 3PAR Service Processor Software SP-4.3.0.MU1 Upgrade Instructions: Service Edition Abstract This guide explains how to update the HP 3PAR Service Processor software from version SP-4.1.0.GA-97 or SP-4.2.0 and later to SP-4.3.0 MU1 at a customer site via physical media, the HP 3PAR Secure Service Architecture or SPOCC. This guide is for qualified technicians authorized by HP to update storage system software.
3par Service Processor User's Guide
Authorized technicians include HP field engineers, HP Partner and Channel Partners, certified self-maintaining customers, and authorized third-party field technicians. This guide is for HP INTERNAL AND PARTNER USE ONLY. HP Part Number: QR482-96848 Published: December 2014 Edition: 1 HP Confidential © Copyright 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S.
Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments Microsoft®, Windows®, Windows XP®, and Windows NT® are U.S.
Registered trademarks of Microsoft Corporation.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |