Showing posts with label 3PAR. Show all posts
Showing posts with label 3PAR. Show all posts
How to Upgrade 3PAR SSMC Appliance
How to check physical disk license on 3PAR
Recently we were involved in disk upgrade task on an HPE 3PAR storage array. The task was pretty simple with two action items. First one was to verify the newly added physical disk and second task was to verify additional physical licenses.
To complete the task, we have used few commands with additional options. The main commands were,
To complete the task, we have used few commands with additional options. The main commands were,
HPE 3PAR StoreServ Remote Copy configuration using RCIP
We have already discussed about 3PAR Remote Copy configuration using RCFC ports. In this post we will try to explain the prerequisites and configuration rules for Remote Copy using RCIP ports on 3PAR StoreServ storage arrays.
How to add SNMP manager details on 3PAR Storeserv
Simple Network Management Protocol (SNMP) is basically used for monitoring your system behavior by forwarding system change notification to a manager server and manager will notify the customer either through email or ticket management system. We generally use SNMP for all kinds of systems like, servers, network equipments, storage arrays etc,
How to check 3PAR StoreServ system health
On a day to day basis, the most common thing which system administrators do is to check on every storage array is its system health, to determine whether the array is in good shape or working with a partially failed or fully failed component.
Most of the storage system administrators face issues with such task as they have to depend lot many software to get a clear idea of what is happening with the system,
Most of the storage system administrators face issues with such task as they have to depend lot many software to get a clear idea of what is happening with the system,
Poll Result- Which Storage Array you support
Thanks to all the readers who participated in the Blog poll. The over all results were promising and following is the summary of the results.
54% of the readers voted for 3PAR and made it as the leader. There were readers who supported multiple array technologies, but over all winner was 3PAR.
Will come with more polls in future.
54% of the readers voted for 3PAR and made it as the leader. There were readers who supported multiple array technologies, but over all winner was 3PAR.
Will come with more polls in future.
HP 3PAR StoreServ troubleshooting commands part-2
In the previous article about Performance Troubleshooting we covered few commands which may be useful while troubleshooting the issues on StoreServ systems.
In this article, we will try to explore the remaining commands and its options.
In this article, we will try to explore the remaining commands and its options.
HP 3PAR StoreServ troubleshooting commands
Storage system administrators will often come across situations like performance degrade and other related issues. Though we have sophisticated tools to analyze the storage array, the best method is to use the native commands to understand the IO load and port statistics. In this article we will try to explore the possible options of HP 3PAR StoreServ performance troubleshooting.Find CPG information for a 3PAR virtual volume (vv)
Most of the storage administrators who manage 3PAR storage will be facing tough situations when they deal with adaptive optimization (AO) configuration, especially when you want to see the CPG wise information and growth factors.
showvlun command to get information about VLUNs in a 3PAR StoreServ
In our previous article, we discussed about showvv command which is basically used for collecting 3PAR virtual volume information. In this article, we will explore showvlun command which is used for collecting information about VLUNs in the system.
Showvv command to collect 3par virtual volume information
Storage System Administrators will often come across situations like collecting disk information and generating reports. In most of the situations management GUI won't provide much help and you will end up using CLI to collect system related information .
HP 3PAR StoreServ 8000 and 20000 comparison
Recently HP has announced new portfolio for their trademark 3PAR storage arrays with improvement in specification and performance. Based on this latest additions, this storage is setting the benchmark for other vendors and planning to hit the number one position. This new series named 8000 and 20000 will replace the existing 7000 and 10000 series respectively and HP has already started shipping the new StoreServ models to their customers.
configuring 3PAR Multipathing in Windows
In case of SAN storage, most of the time we will be dealing with multipathing software to enable redundancy and load balancing of disks. The same is with 3PAR StoreServ.3PAR has HPDSMs for windows 2003 systems, but from windows 2008 onwards they are purely using native multipathing option to enable redundancy and load-balancing for SAN attached disks.
Creating a 3PAR CPG using SSMC
A CPG(Common Provisioning Group) is basically a set of policies which defines/creates a virtual pool of logical disks(LDs) that allows 3PAR virtual volumes to share the resources and allocates space on demand. When we create thick and thin volumes, that draw space from the CPG's LD pool. By default, CPG is defined to automatically grow the LDs when the amount of available space on underlying LDs falls below a configured threshold.
Finding 3PAR serial number (How To)
The Most common problem while dealing with support is of course related to finding the serial number of the storage box which you manage. There are various methods available to find the serial number. If you are located in the data center, you can very well go and check the serial number of the box which is commonly available in the chassis. Think about a situation in which you are managing the box remotely?.
Check 3PAR event log using CLI
Most of the time system administrators have to deal with system failures and troubleshooting issues related to hardware and software bugs, the same applies to 3PAR as well. When we deal with system events and other logs, we will be relying on CLI commands rather than GUI tools. CLI commands are easy to dig in and it gives you a better option to capture the logs using PuTTy or any SSH tools which has log capturing feature.
3par Implementation Guide for Operating Systems
We have been searching for operating system configuration rules and method while connecting to 3PAR StoreServ storage arrays and finally we got some documents and decided to keep links in a common place where we can access it anytime when we need, rather than searching for it all the time.
3PAR SSMC - Adding License
In order to enable licensed features on HP 3PAR storage systems, you need license keys and to install them you can either use HP 3PAR SSMC or 3PAR CLI. In our earlier 3PAR license article we covered the method using IMC and CLI. In this topic, we will be concentrating on the new 3PAR management software which is called, SSMC (StoreServ Management Console).
Before you start ensure that you have the license
keys available and downloaded from HP Webware. You can generate the license file using an Entitlement Order Number(EON)
To add an HP 3PAR storage system license, you must copy the license key file to the SSMC server or copy and paste the encrypted license key characters into HP 3PAR SSMC screen.
On the mega menu, go to Storage Systems and select Systems.
Once the storage systems are listed, select the storage system on which you want to add the license , and then access Actions menu which is on the right side and select Add license from the list.
We are done with the license installation just like that!
Failover/failback 3PAR ports
HP 3PAR Persistent Ports technology enables each host port on an HP 3PAR StoreServ node to carry a “Native” and a “Guest” identity(WWN information) almost all the time. The host ports on the Nodes will carry Guest WWN of the corresponding port on the partner node in a node pair. 3PAR Persistent Ports technology effectively configures the host path to redirect I/O requests from the “Native” port on one node to the “Guest” port on partner node in case of firmware upgrades, node failure or loss_sync events.The port failover is really transparent and most of the time the connected hosts will not trigger a nofication about the port failover from host side.
There is no Persistent Ports support on HP 3PAR OS 3.1.2 releases. Persistent Ports functionality is supported for HP 3PAR OS 3.1.2 and later only. Starting with HP 3PAR OS 3.1.3 support for FCoE connected hosts and iSCSI connected hosts has been added. .
For HP 3PAR StoreServ FC host ports, the following requirements must be met:
• The same host port on host facing HBAs in the nodes in a node pair must be connected to the same FC fabric and
preferably different FC switches on the fabric (for example, 0:1:1 and 1:1:1).
• The host facing HBAs must be set to “target” mode.
• The host facing HBAs must be configured for point-to-point connection (no support for “loop”).
• The FC fabric being used must support NPIV and have NPIV enabled.
When a Persistent Port failover occurs the Failover State of the host ports can be one of the following states:
• none—Failover not in operation.
• failover_pending—Failover to partner request has been issued but not yet completed (transient state).
• failed_over—This port is failed over to its partner.
• failback_pending—Failback request has been issued but not yet completed (transient state).
• active—The partner port is failed over to this port.
• active_down—The partner port failed over to this port, but this port is down, e.g., cable missing.
• active_failed—The partner port failed over to this port, but the action failed, e.g., FC switch did not have NPIV enabled.
On most occasions we will have to failback the port to restore the port state. Let's see the practical side of this,
with this command.
SYNTAX
From the output it is visible that the port is running on its normal state with failover status as none.
There is no Persistent Ports support on HP 3PAR OS 3.1.2 releases. Persistent Ports functionality is supported for HP 3PAR OS 3.1.2 and later only. Starting with HP 3PAR OS 3.1.3 support for FCoE connected hosts and iSCSI connected hosts has been added. .
For HP 3PAR StoreServ FC host ports, the following requirements must be met:
• The same host port on host facing HBAs in the nodes in a node pair must be connected to the same FC fabric and
preferably different FC switches on the fabric (for example, 0:1:1 and 1:1:1).
• The host facing HBAs must be set to “target” mode.
• The host facing HBAs must be configured for point-to-point connection (no support for “loop”).
• The FC fabric being used must support NPIV and have NPIV enabled.
When a Persistent Port failover occurs the Failover State of the host ports can be one of the following states:
• none—Failover not in operation.
• failover_pending—Failover to partner request has been issued but not yet completed (transient state).
• failed_over—This port is failed over to its partner.
• failback_pending—Failback request has been issued but not yet completed (transient state).
• active—The partner port is failed over to this port.
• active_down—The partner port failed over to this port, but this port is down, e.g., cable missing.
• active_failed—The partner port failed over to this port, but the action failed, e.g., FC switch did not have NPIV enabled.
On most occasions we will have to failback the port to restore the port state. Let's see the practical side of this,
3parLab cli% showportIn the above example, we can see that most of the ports are in "failed_over" state and some are "active_failed" state. We should use "controlport" command along with the "failback" option. Failback option Reverts a port failover status to the default. if port failover is currently active. The failed-over port should be specified
N:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol Label Partner FailoverState
2:2:3 target ready 2AE80002AD009247 22230002AD009247 free FC - 3:2:3 failed_over
2:2:4 target ready 2AE80002AD009247 22240002AD009247 free FC - 3:2:4 failed_over
3:2:3 target ready 2AE80002AD009247 23230002AD009247 free FC - 2:2:3 active_failed
3:2:4 target loss_sync 2AE80002AD009247 23240002AD009247 free FC - 2:2:4 active_failed
4:2:3 target ready 2AE80002AD009247 24230002AD009247 free FC - 5:2:3 failed_over
4:2:4 target ready 2AE80002AD009247 24240002AD009247 free FC - 5:2:4 failed_over
5:2:3 target ready 2AE80002AD009247 25230002AD009247 free FC - 4:2:3 active
5:2:4 target ready 2AE80002AD009247 25240002AD009247 free FC - 4:2:4 active
5:5:1 target ready 2AE80002AD009247 25510002AD009247 free FC - 4:5:1 none
5:5:2 target ready 2AE80002AD009247 25520002AD009247 free FC - 4:5:2 none
6:2:1 target ready 2AE80002AD009247 26210002AD009247 free FC - 7:2:1 failed_over
6:2:2 target ready 2AE80002AD009247 26220002AD009247 free FC - 7:2:2 failed_over
6:2:3 target ready 2AE80002AD009247 26230002AD009247 free FC - 7:2:3 failed_over
6:2:4 target ready 2AE80002AD009247 26240002AD009247 free FC - 7:2:4 failed_over
6:5:1 target ready 2AE80002AD009247 26510002AD009247 free FC - 7:5:1 failed_over
6:5:2 target ready 2AE80002AD009247 26520002AD009247 free FC - 7:5:2 failed_over
7:2:1 target ready 2AE80002AD009247 27210002AD009247 free FC - 6:2:1 active
7:2:2 target ready 2AE80002AD009247 27220002AD009247 free FC - 6:2:2 active
7:2:3 target ready 2AE80002AD009247 27230002AD009247 free FC - 6:2:3 active
7:2:4 target ready 2AE80002AD009247 27240002AD009247 free FC - 6:2:4 active
7:5:1 target ready 2AE80002AD009247 27510002AD009247 free FC - 6:5:1 active
7:5:2 target ready 2AE80002AD009247 27520002AD009247 free FC - 6:5:2 active
-------------------------------------------------------------------------------------------------------
with this command.
SYNTAX
controlport failback node:slot:port
3parLab cli%the host port 3:2:4 is failed_over to to it's partner port 2:2:4 and we should failback the partner port(2:2:4) to restore the state.
3parLab cli% showport 3:2:4
N:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol Label Partner FailoverState
3:2:4 target loss_sync 2AE80002AD009247 23240002AD009247 free FC - 2:2:4 active_failed
----------------------------------------------------------------------------------------------------
1
3parLab cli% controlport failback 2:2:4
Are you sure you want to run controlport failback on port 2:2:4?
select q=quit y=yes n=no: y
3parLab cli% showport 3:2:4
N:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol Label Partner FailoverState
3:2:4 target loss_sync 2AE80002AD009247 23240002AD009247 free FC - 2:2:4 none
----------------------------------------------------------------------------------------------------
1
3parLab cli%
From the output it is visible that the port is running on its normal state with failover status as none.
Changing 3PAR SSMC administrator account
When you install 3PAR SSMC (3PAR StoreServ Management Console), the first time when you open SSMC, you will see a popup to set your administrator credential for your SSMC instance. You must set up the user name and password for the Administrator account if you want to proceed. But once you set the password you don't have an option to fix the credentials and password without logging in to the console. Think about a situation where you forgot the password or username? Let's see how to fix this.
By Default HP 3PAR StoreServ Management Console Server will be installed under folder C:\Program Files\Hewlett-Packard\SSMC and this will contain so many binaries to ease the SSMC operation. If you forget the SSMC Administrator credentials, clear the password by executing the script called ClearAdminCredential.bat which is available in the SSMC\ssmcbase folder. You must run the script from a command prompt with administrator privileges.
open command prompt and execute ClearAdminCredential.bat
C:\Users\admin>"c:\Program Files\Hewlett-Packard\SSMC\ssmcbase\ClearAdminCredential.bat"This command will clear the SSMC Administrator Credential.Do you want to continue? [Y=Yes,N=No](default=N) Y
C:\Users\admin>
this will erase the current SSMC administrator credential and will prompt you to enter new credentials at the next login.