Login into switch Command line interface using Putty
CMD:
portname <slot>/<portnumber> -n <PortName>
Ex: if you want to rename the portname on blade 1 port 1
portname 1/1 -n newhost_hba1
FLARE Code Upgrade Steps
A CLARiiON/VNX FLARE upgrade usually takes 2 to 3 hours, depending on the current and target code, and on the array model and configuration.
A FLARE upgrade is considered to be an online upgrade (or "NDU", a Non-Disruptive Upgrade). However, there are certain conditions that MUST be met for the upgrade to be non-disruptive:
1. All hosts connected to the CLARiiON/VNX should be connected to both SPA and SPB, the recommendation is to attach each host twice to each SP for high availability.
2. All hosts should have up-to-date and supported multipathing software.
3. Array utilization should be below 100%. The combined SPA Utilization in % + SPB Utilization in % should be less than 100%.
RCM can perform CLARiiON/VNX FLARE code upgrades remotely via ESRS, WebEx or Modem, depending on the customer's environment and availability.
Tasks that should be performed prior to a CLARiiON/VNX FLARE upgrade:
Steps to validate your configuration:
Hosts
Hosts can be verified using the following tools:
· For UNIX and VMware - EMC Grab
· For Windows: EMCReports
These tools can be found on support.emc.com, select your product, Downloads. When you have collected this data, you can send it to E-Lab Advisor to be validated:
· For UNIX and Windows: HEAT
· For VMware: VMHEAT
You can batch files and submit them together (details can be found on the HEAT pages).
The input from these files is matched up against the current E-Lab Interoperability Navigator and you will receive back an email containing an analysis of your hosts that indicates any issues that were found. It is your responsibility to address these issues.
Switches
You can do the same review for your switches using the SWAT tool which can be found on E-Lab Advisor. This page will tell you what diagnostic file(s) to gather from your switches, and guide you through sending the information to EMC. Again, you will receive an analysis and recommendations for your equipment, and it is your responsibility to address any issues.
Connectivity
High Availability Verification Tool (HAVT)
HEAT and SWAT will check the configuration of your hosts and switches, but they will not check state of the connectivity of your hosts to the storage system. This is done via HAVT. This utility is part of the Unisphere (Navisphere) Server Utility, which can be found on support.emc.com. Select your product, then Downloads.
Select the Verify Server High Availability option. This will generate a report that indicates the number of paths to SPs and reports any issues with those paths. Also, if it cannot detect any failover software, it will inform you of that fact. See the attached matrix for currently supported operating systems and failover software. See the linked Failover Software Operating Systems tables. This tool must be run on each host that you want to remain on-line during the upgrade. The resulting output can be automatically transferred to the storage system for inclusion in the host checking done by the Software Assistant in the Navisphere Service Taskbar.
If your host is not listed, you will have to manually check that:
1. The host has at least two valid paths, one to each Storage Processor in the storage system, from each of at least two HBAs.
2. All expected initiators show in the connectivity status for the storage system (in Navisphere Manager or Unisphere) as registered and logged in. (Note that HP-UX will only show as logged in if there is active I/O on that path.)
3. Failover software is installed and configured correctly.
Array Settings
These control how the host and the storage system will communicate with each other. The CLARiiON Failovermode, Arraycommpath, Initiator Type and Unit Serial Number settings must be verified for each host. Currently recommended settings can be found in Knowledgebase solution [Link Error:UrlName "emc99467-What-are-the-Initiator-Arraycommpath-and-Failovermode-settings-for-PowerPath-DMP-PVLinks-and-native-failover-software" not found]. (This information can be seen in the XML output generated by the Server Utility or in Navisphere Manager Connectivity Status.)
Other actions
· EMC Technical Advisories (ETAs)
Review any EMC Technical Advisories (ETAs) that have been issued for storage system models, software, or 3rd party hardware that you have in your environment. These are warnings of hardware or software issues that may affect your environment. You can choose to be automatically notified of those pertaining to your particular configuration, and there are lists by product family and a complete list of all ETAs. These are available on support.emc.com. Select your product, and then review the ETAs on the left-hand pane.
· Unisphere Service Manager (USM)/Navisphere Service Taskbar (NST) Technical Advisories
these are notifications that are displayed when you first start up USM/NST. They contain information about issues that could affect the activity you are about to perform, or the general behavior of your storage system.
· E-Lab Interoperability Navigator
This provides access to EMC interoperability support matrices. Using a guided query, you can retrieve information about supported configurations. If you have run HEAT or SWAT, you have already used this tool. It can be found at on support.emc.com. Select E-Lab Interoperability Navigator under Product and Support Tools. If you have questions as to whether certain versions of software are supported together, then use this tool.
· PowerPath Configuration Checker (PPCC)
This is a utility that can be used to check that hardware and software for a particular host is configured to support PowerPath failover. (It also verifies other PowerPath multipathing features.) EMCReports (Windows hosts) and EMC Grab (UNIX hosts) are used as input. It can be found on Powerlink at Home > Support > Product and Diagnostic Tools > Environment Analysis Tools > PowerPath Configuration Checker (PPCC) .
After performing these checks, run the Prepare for Install option in NST/USM. This option verifies that all servers are in an expected availability state using the files created in the HAVT step above.
If the upgrade is going to be performed by modem (via a management station or attached NAS control station), or via WebEx connections, please make sure you download the code bundle on the local machines. This is so the RCM Engineers can perform the upgrade at the scheduled time (without any delays). Also make sure that the customer has Unisphere Service Manager (USM) and NaviSphere CLI installed.
FLARE code can be downloaded from ftp.emc.com/pub/rcm/code/block or http://support.emc.com
The tools (USM and Naviseccli) can be downloaded from ftp://ftp.emc.com/pub/rcm/app/vnx/ or http://support.emc.com
If the upgrade is over ESRS, RCM will stage the code remotely, provided that the ESRS connection is stable enough. If not, RCM will ask for local assistance to stage the code.
The RCM Engineer will perform pre-upgrade health checks prior to the upgrade by analyzing pre-upgrade SPCollects. The customer or CE will be notified of any issues found before starting the actual upgrade.
What to expect during a FLARE upgrade:
After scheduling an upgrade with RCM, it will be assigned automatically to an RCM Engineer. The Engineer will perform health checks, notify relevant parties and start the upgrade as scheduled. The actual upgrade sequence is:
1. Install software on Secondary SP.
2. Reboot Secondary SP.
3. Wait for Secondary SP to come back from reboot and start accepting I/O requests (also called the NDU Delay).
4. Install software on Primary SP.
5. Reboot Primary SP.
6. Make sure LCC upgrade is complete and no hardware faults exist.
7. Commit Code.
8. Perform post upgrade health checks.
After the Software upgrade, Perform the following checks:
· View the event logs of both SPs to ensure there are no unexpected events that could signal a problem that occurred during or immediately after the software upgrade
· Restart all stopped SAN Copy sessions and any other replication software activities that were stopped prior to this upgrade
· Is PowerPath running on the hosts?
· If yes, are the LUNs listed under their default owner?
· If no, perform a powermt restore. Confirm that all LUNs are now listed under their default owner.
For AIX hosts only: If it is necessary to use the powermt restore command, see Knowledgebase article ETA 2753: AIX, PowerPath: AIX Host Lost access to storage during powermt restore.
· If required, upgrade ESRS IP Client for CLARiiON to the version that corresponds to the FLARE that was upgraded to in this procedure.
· Using Unisphere Release Notes and E-Lab Interoperability Navigator, check that all host based and array-based software is at an acceptable/compatible revision. If not, then update as required.
· Confirm that there are no array faults (note that the SPS units may still be charging based upon the SP reboots; this is normal). Write cache will automatically re-enable if it was enabled prior to the NDU as soon as one SPS is fully charged and ready
· Confirm that the cache settings are set properly. If new replication software (layered applications) is being added, cache settings may not be able to be set as they were previously
· Are there any unowned private LUNs?
· If yes, refer to EMC Knowledgebase article [Link Error:UrlName "emc105448--Clone-Private-LUNs-CPLs-or-MirrorView-write-intent-log-WIL-private-LUNs-or-SnapView-reserved-pool-LUNs-become-unowned-after-NDU" not found]. CPLs, WIL private LUNs, or SnapView reserved pool LUNs may show as un-owned after a code upgrade. If the storage processor (SP) is not tracking changes, the LUN will be un-owned. Once the clones, mirrors, or snapshots start up, the ownership will revert to the status of "owned". You can also try de-alllocating/re-allocating LUNs from the CPL, WIL, or reserved LUN pool to reinstate ownership to these LUNs. Refer to EMC Knowledgebase article emc105448 for more information.
· Is there a VMware server attached to the array?
· If yes, are all the LUNs are on the same SP? After a non-disruptive upgrade (NDU), all VMware LUNs are on one storage processor (SP). If yes, follow as below.
VMware currently does not use PowerPath. Its native failover will not restore LUNs back to their default SPs after a path or SP has been restored. VMware failover is configured (or should have been configured ) for MRU (Most Recently Used) path. This means if a LUN with a default owner of SP B was trespassed to SP A, then the ESX server continues to access it through SP A. It does not test to see whether the old path has been restored. The most extreme example of this would be an NDU where both SPs have rebooted, and all the LUNs will end up on the first SP that rebooted. It would appear that all the LUNs are on SP B and not on A. Since the ESX server does not automatically restore the LUNs, the LUNs will have to be manually trespassed from Navisphere Manager or by command line using the CLI command: navicli -h <default SP_IP_address> trespass mine. This must be issued to both SPs.
How to schedule a FLARE upgrade with RCM:
If you would like to schedule an upgrade with RCM, please contact rcmscheduling@emc.com or use the RCM Schedule
Performing TimeFinder/Clone operations
|
1.
|
Open
the dialog
Right-click
the device group and select Replication,
TimeFinder/Clone to open the
TimeFinder/Clone Wizard.
 |
£
|
|
2.
|
Enter information
Select the Clone Type Local
and the Action Full Establish.
|
£
|
|
3.
|
Select Pairs
Click Select All to
select all pairs; otherwise, use the Shift and Ctrl keys to select specific
pairs.
(STD to STD) - (BCV to STD)
- (Copies from BCV)
|
£
|
|
4.
|
Click Next.
 |
£
|
|
5.
|
Optional: Select any of the operation Options:
·
Consistent:
Creates Clone copies that are consistent with the database up to the point in
time that the activation occurs. It suspends writes to the source devices
during the activation.
·
NotReady:
Sets the target devices as Not Ready.
·
Force:
Overrides any restrictions and forces the operation, even though one or more
of the paired devices may not be in the expected state. Use caution when
checking this option because improper use may result in data loss.
|
£
|
|
6.
|
Click Finish.
|
£
|
|
7.
|
View
the session status
To view the status of the TimeFinder session, select the device group
(in Properties view) and click the Clone Query tab.
The key things to
verify are the
|
£
|
Creating TimeFinder/Clone device pairs
|
1.
|
Open
the dialog
Right-click
the device group and select Replication,
TimeFinder/Clone to open the
TimeFinder Wizard.
Select
the Clone Type.
|
£
|
|
2.
|
Edit Pairs
Click the Edit
Pairs button.
|
£
|
|
3.
|
Select Pairs
Optional: Use
the Filters to populate the device lists with specific configurations, device
emulation types, and/or device capacity sizes.
When you click on a Source device, the Target devices that
can be paired with that device display in the Target table. Select both
Source and Target devices and click Add
to move them to the Device Pair List.
Click Apply to
save the device pairs and continue pairing devices; click OK when finished.
|
£
|
|
4.
|
Select pairs
Select the Action Create.
Select the device pairs or click Select All to select all pairs. Click Next.
|
£
|
|
5.
|
Optional: Select any of the operation Options:
·
Copy: Create full data copy. By omitting this
option (default), the device pair state will be in the CopyOnAccess state
when activated. Actual copying of the data is deferred until either tracks on
the source device are written to, or tracks on the target device are read or
written
·
Differential:
Used with either the Copy or Precopy
option to create an SDDF session for maintaining changed track information.
Must be used when creating copy sessions on which you plan on issuing a
Restore action
·
PreCopy:Used with the create and recreate actions
to start copying tracks in the background before the Clone session is
activated
·
Force:
Overrides any restrictions and forces the operation, even though one or more
of the paired devices may not be in the expected state. Use caution when
checking this option because improper use may result in data loss.
|
£
|
|
6.
|
Click Finish.
|
£
|
|
7.
|
View
the session status
To view the status of the TimeFinder session, select the device group
(in Properties view) and click the Clone Query tab.
The key things to
verify are the
|
£
|
Updating Emulex HBA driver for Windows 2003
|
1.
|
Grab
AutoPilot from the site:
To update the Emulex HBA
driver, use the latest version of the Emulex AutoPilot Installer as follows:
a. Create
a directory that will be used to save the downloaded files.
b. Open
a web browser and access the Emulex Website at http://www.emulex.com
c. Click
Downloads on the navigation
bar on the top of the homepage.
d. On
the next page under Storage and System
Supplier Qualified and Supported HBAs, select the EMC link.
e. On
the Support Resources for EMC page,
select the link for the correct Emulex HBA model.
f. Locate
the Resources panel on the
right-hand side of the webpage and select Windows under the CurrentDrivers
heading.
On the next page, select the operating system version link under the appropriate driver type column.
g. Select
the Download link for the AutoPilot
Install Kitand save the file to the
directory you created earlier.
|
|
2.
|
Hot
fix considerations for Windows 2003 STORPort drivers:
Currently, the
shipping version of Windows Server 2003 requires post-RTM hot fixes to
resolve some known issues. For all Windows Server 2003 STORPort
installations, obtain the current Microsoft QFE hot fix listed in the E-Lab
Interoperability Navigator (ESM) with
the HBA driver revisions. Current hotfixes are also listed with the appropriate
HBA driver on the Qlogic/EMC driver pages.
Install the
current Microsoft QFE Hotfix and reboot before updating the HBA driver.
Note: If you are about to upgrade your system to Service Pack 1
for Windows Server 2003, you should upgrade the HBA drivers to the latest
supported version prior to installing the service pack.
|
|
3.
|
Update the driver:
Update the Emulex HBA driver
using the Emulex AutoPilot Installer as follows:
a.
Navigate to the directory containing either the emcfcportkit_<version>.exeor the storportminiportkit_<version>.exe and double-click the .exe file.
b.
Follow the screen prompts to guide you through
the installation, accepting all defaults.
Note:If a previous version of the utility is detected, the screen will display a confirmation prompt to uninstall the current version before continuing. 
c.
When
the installation is complete, select the Start AutoPilot Installer checkbox
(if not alreadychecked) and click Finish. The AutoPilot Installer program will open
displaying a screen similar to the following:
The AutoPilot Installer program automatically discovers the HBAs in the system. Note:If no HBAs are discovered:
·
Verify
the HBA is properly seated into the bus and powered on. The LEDs should be
lit.
·
Verify
the HBAs are visible in Computer Management/DeviceManager/SCSI and RAID
controllers.
d.
Select Next to continue. A screen similar to the following will
appear displaying the available drivers.
e.
For
each HBA, use the drop-down menu to select the new driver to be installed and
selectNext to continue.
f.
On
the next screen, select the appropriate answer regarding PowerPath software,
and click Next.
NOTE: This question will only appear if you are installing the SCSIPort driver.
g.
On the topology screen that appears, select the topology of the storage network and
click Next.
·
Select
Arbitrated Loop when directly
connected to the array (no Fibre Channel switch).
·
Select
Point-to-Point when connected to a
SAN (using a Fibre Channel switch).
h.
After
installation is complete, a reboot warning will appear as shown below. Click OK.
i.
Click
Next on the AutoPilotInstaller window to continue.
j.
On
the Summary screen that appears, you can either view or print the driver
installation report. Note that the
report is saved in the C:\Program Files\Emulex\AutoPilot Installer\reports.
k.
Click Finish to close the AutoPilot
Installer program.
l.
When prompted to restart your computer, clickYes.
NOTE:When the AutoPilot Installer installation is complete, there will benew Emulex programs under Start>Programs>Emulex. |
Refresh the Symmetrix director with VCMDB data
Update the Symmetrix array with the
configuration changesby performing a director refresh operation.This causes the
Symmetrix director to refresh its WWN/iSCSI-related profile tables in cache
with the content data from the device masking VCMDB.
The symmaskdb refresh command is used to force a Symmetrix
director to refresh its profile tables with the contents of the Device Masking
VCMDB. The syntax for this command is:
symmask -sid SymmID refresh
-noprompt
where:
SymmID= The ID of a specific Symmetrix the symmaskdb command is to be executed against.
For example, to force a Symmetrix director to refresh its
profile tables with the contents of the Device Masking VCMDB for a Symmetrix with an ID of 000000012345, execute the followingcommand:
symmask
–sid 12345 refresh –noprompt
When this command
is executed, you should see a message that looks something like this:
Symmetrix FA directors updated with
contents of SymMask Database 000000012345
!
Caution: Before executing this command, make sure no HBAs are accessing devices
in the masked channel (in other words, make sure that no application or user
activity is taking place on the HBAs that are about to be refreshed). !
Backup the VCMDB
Backup the VCMDB
The symmaskdb backup command is used to create a backup copy of
the Device Masking VCMDB. The syntax for this command is:
symmaskdb -sid SymmID backup–file
BkupFileName-noprompt
where:
SymmID= The ID of a specific Symmetrix the symmaskdb command is to be executed against.
BkupFileName= The name of the file to be used to store the backup copy of the
Device Masking VCMDB created.
(You cannot reuse backup file names; a new file name must be provided each time
this command is executed.) The backup copy will be stored in the file specified
and that file will be written to the current directory (i.e., the directory
that this command is executed from).
For example, to store a backup
copy of an existing Device Masking VCMDB for a Symmetrix with an ID of 000000012345in
a file named BackupDevMaskDB_1, execute the followingcommand:
symmaskdb
–sid 12345 backup –file BackupDevMaskDB_1 –noprompt
When this command
is executed, you should see a message that looks something like this:
Symmetrix
SymMask database backed up to file BackupDevMaskDB_1
from
Symmetrix 000000012345
Installing PowerPath software on a Windows 2003 host
|
Overview
This procedure describes how to install PowerPath on Windows Server
2003.
Note:This procedure is
specific to the installation of PowerPath versions 4.5 to 5.0, which is the
current shipping version for Windows 2003 hosts. For instructions on installing older
versions of PowerPath, refer to the applicable PowerPath installation manual
available on PowerLink.
This procedure is based on content from the following EMC manual:
This document can
be obtained from the EMC Powerlink website at:
You must be logged in as the Local System Administrator to proceed.
Verify the following prior to the installation of PowerPath:
·
Review
the patch ReadMe files to determine which patches (if any) you want to
install after PowerPath, and whether those patches have any added
prerequisites that must be met before you install PowerPath.
·
Determine
if the PowerPath software you are installing requires the removal or presence
of a previous version of PowerPath.
Some full versions require the previous version to be removed while
others do not. Also, some patches
require the full version to be present while others require it to be
removed. Refer to the PowerPath
Release Notes and/or PowerPath patch readme files for your specific version
to determine what needs to be present/removed and if and when a reboot is
necessary in order to install your specific PowerPath software version and/or
patch. These documents are available on http://Powerlink.EMC.com.
Note:A “failed redundancy” state can occur if
PowerPath is installedon a host with mirrored disks. This state only happens
if diskmanagement applications (that use the dmadmin service) arerunning when PowerPath is
installed. To prevent this, close all disk management applications(including diskmgmt.msc and diskpart.exe) and stop thedmadmin service before installing PowerPath.
If applicable,
stop all I/O and close all applications that access storage devices.
|
|
MPIO
framework considerations:
Note that PowerPath
4.6.x requires Microsoft MPIO framework 1.16 or later.
·
If
the MPIO framework is not installed on the host, the PowerPath 4.6.1
installer installs MPIO framework 1.16.; PowerPath 5.0.0 will install 1.17
·
If a
version of the MPIO framework less than 1.16 is installed on the host, the
PowerPath installer prompts you to upgrade to version 1.16. If you do not
upgrade, PowerPath installation aborts.
If a version of
the MPIO framework is greater than 1.16 is installed on the host, the
PowerPath installer notifies you and then continues with the installation.
|
|
Verify
single device paths:
Ensure that there
is only one logical connection per logical device. If necessary, disconnect
all additional HBAs/NICs, hubs, switches other than the primary
channels.
Note: Doing this prevents the host from seeing
the same LUN twice before PowerPath is configured.
|
|
Insert
the PowerPath CD-ROM:
Insert the
PowerPath installation CD in the CD-ROM drive and begin the installation. If autoplay is enabled, your browser launches and
displays the Getting Started page. You can install the software from the
Installation section by clicking the appropriate link for your operating
system. Then either:
|
|
Begin
Install:
In the Run
window, either browse to or enter the name of the PowerPath installation
program and click OK.
|
|
Continue
Install:
Complete the information as prompted on the next four
screens.
|
|
Select
your options:
Use the Destination
Folder screen to installPowerPath in a directory other than the default
directory (ifdesired).
Note: It’s best to install PowerPath in the
default directory as no additional action is required to install in the
default directory.
·
If
you are going to install PowerPath in itsdefault directory (recommended), clickNext and skip the remainder of this
step to continue with the next step below.
·
To
install PowerPath in a different (non-default) directory,click Change. The setup wizard prompts you
to browse toyour destination folder. Select the destination folder, and clickOK.
Caution:Do not specify the Windows System directory for yoursystem (specified by the %SYSTEMROOT% environmentvariable). PowerPath will not function correctly if it isinstalled in this directory. Click Next. |
|
Continue
Install:
In the Ready to Install the Program dialog
box, click Install.
Note:If you do not already have a license in
the registry, the EMCLicensing Tool displays.
|
|
Register
PowerPath
When prompted by
the EMC Licensing Tool, enter your PowerPath registration number in the License Key field. Click Add and then OK.
Note: The PowerPath registration numberis printed
on the License Key Card, which was delivered with the PowerPath media kit. You may enter multiple registration numbers
as PowerPath is supported on different storage systems. If you are upgrading
from a previous version, PowerPath saves the existing license key, and no
input is required.
Caution: Failing
to enter a registration number will result in the installation of PowerPath SE, which is the default policy without a
valid PowerPath license. If you fail to enter the registration number during
installation, it can be entered at a later point.
|
|
Finish:
Click Finish
in the next dialog box and
when prompted to reboot the host,click No.
Instead, from the
Start menu, select Shut Down and then click OK.
|
|
Reconnect
other I/O interfaces:
Reconnect the
additional HBAs/NICs, hubs, switches, etc. that you disconnected earlier.
|
|
Power
up boot:
Power up the
system. PowerPath is fully configured with multiple paths to logical devices
at boot up.
|
|
Check
for patches
If necessary, install any PowerPath patches from the
following URL:
http://powerlink.emc.com
Note: A readme file that explains how to install
the patch that accompanies every patch release. This file will also state whether you need
to reboot the host after the installation of the patch.
|
|
Verify
PowerPath sees new paths
The operating system must recognize new
paths before PowerPath can do so. Normally, no action is needed; the
operating system detects new paths automatically. Depending on the type of
HBA installed, you may have to scan for hardware changes in the device
manager. Alternately, reboot.
To verify that
PowerPath sees all new HBAs and paths to storage devices, use the following
command in the PowerPath utility:
powermt display dev=all
To test and validate any new path(s) with
PowerPath functionality, enter:
powermt restore
|
Subscribe to:
Posts (Atom)