Verifying the communication path
Each installation of HP Command View EVA software on a management server is called a management agent. The management agent is the interface to the array and must have access to the array through the SAN. To verify the communication path between the array and the management agent, select an array in the Navigation pane. If the array icon is green, communication is good and you may continue with the array conguration. If the array icon is gray with a yellow triangle over it, there is a communication failure. To resolve the communication failure, see "Troubleshooting HP Command View EVA" on page 35.
Creating an array password
A password is a security feature that allows you to access specied arrays through an HP Command View EVA session. A management agent can control multiple arrays, and multiple management agents can control a single array, but only one agent can actively control an array at a time. The password you enter in HP Command View EVA must match the array password entered on the operator control panel (OCP) of the controller. For information about the OCP, see the Enterprise Virtual Array user guide for your array model. If you have already set the array password on the OCP, you must enable it in HP Command View EVA to see that array. If the array password has not been set on the OCP, you can use the Enable function to create the password. However, the password is not enabled until you enter it on the OCP. The array password must meet the following requirements: Can be 8-16 characters Can include upper and lower case letters Can include numbers 0-9 Can include the following characters: ! " # $ % & ( ) * + , -. / : ; < = > ? @ [ ] ^ _ { | } Cannot include spaces or the following characters: ~ \
NOTE: You must be running HP Command View EVA 6.0 or later to use passwords with more than eight characters. If you enter a password that is longer than eight characters, you can no longer manage that array if you are running an earlier version of HP Command View EVA. In this situation, you must delete this password and enter a new password that does not exceed eight characters. To enable a password: 1. Click Agent Options in the Session pane. The Management Agent Options window opens. 2. Select Storage system password access. The Storage System Password Access window opens. 3. Click Enable. The Enable Password Access to a Storage System window opens. 4. Select the array to enable in the Storage System World Wide Node Name List box. Only world wide node names that do not have an enabled password are displayed. 5. Enter the array password in the Password box. Enter the password again in the Conrm Password box. NOTE: This password must match the one set on the OCP. 6. Click Enable Password.

The Enable password access dialog box opens. 7. Click OK. A status window opens, indicating success or failure. 8. Click OK to return to the Storage System Password Access window.

Initializing the array

When you install an array, it appears as an uninitialized storage system. Initializing an array makes it ready for use, binds the controllers as an operational pair, and establishes preliminary data structures on the array. Initializing also sets up the rst disk group, which is called the default disk group. If you are upgrading an existing version of HP Command View EVA, the arrays remain initialized and any other existing components are retained. If WEBES is installed on the management server, see the WEBES documentation for instructions on adding entitlement details for the new array. For more information, go to the Service Tools web site: http://h18000.www1.hp.com/support/svctools. NOTE: When you initialize (or reinitialize) an array, you must restart the HP Command View EVA service on any standby management servers. See "Restarting the HP Command View EVA service" on page 35 and "Using multiple management servers to manage arrays" on page 27 for more information. When initializing an array, you must: Enter a name for the array. Enter the number of disks to be included in the default disk group.
You can also perform the following additional/optional tasks:
Set the drive type. Set the array date and time. Enter a console LUN ID. Select a disk failure protection level. Enter comments.
See the online help for instructions to complete these tasks.
Entering replication license keys
A license key is not required to activate the EVA controller software, but license keys are required to use replication features. An HP Business Copy EVA license key activates snapshot, snapclone, and mirrorclone features. An HP Continuous Access EVA license key activates the data replication feature. Each license is sold with the individual product. You can enter a license key before or after initializing the array. To avoid text entry errors, HP recommends that you copy and paste license keys from the e-mail message or online source. Be careful not to copy any non-ASCII characters, which can prevent license key validation. For license keys received by e-mail, rst set the default message format to ASCII. The method for changing the message format varies by e-mail application.
TIP: To change the Microsoft Outlook message format to ASCII: 1. Select Tools > Options. 2. Click the Mail Format tab. 3. Under Message format, select Plain Text. 4. Click OK. For license keys obtained from an online source, copy each license key into a le using a text editor such as Microsoft Notepad or Wordpad. To enter a license key: 1. Click Agent Options in the Session pane. The Management Agent Options window opens. 2. Click Licensing options. The Licensing Options window opens. 3. Click Enter new license key. The Add a license window opens. 4. Copy only the license key text from the e-mail or online source. For example, copy the following text for an HP Business Copy EVA license key: FEATURE HSV110-SNAPSHOT Compaq 3.0 permanent uncounted 22222222222F

\HOSTID=HSVWWN=5000-2FF2-5555-CC44 NOTICE="Authorization =
\BB080CREAMER12345678, Qty 1, QM-00NOT-ZZ2.1, Business Copy 2TB \for
VCS V2.0x and V3.0x LTU EVA5000"
CAUTION: Do not copy any other text from the e-mail or online source; otherwise, HP Command View EVA will reject the license key. 5. Paste the license key in the text box. 6. Click Add license to save the information. 7. In the Navigation pane, select the icon for the array. The license key is propagated to the array and is available to other management agents. NOTE: If you are using multiple management servers to manage arrays and you must upgrade a replication license key, HP recommends that you wait for all running management commands and/or replication manager jobs and commands to complete before starting the upgrade. If the management server you use to upgrade the license key is not currently managing arrays, it will automatically become the server managing arrays when you perform the upgrade. This will cause any command or jobs initiated from another management server to fail. To resume these jobs and commands, return management control to the other management server. See "Using multiple management servers to manage arrays" on page 27.
2 Conguring HP Command View EVA
This chapter describes conguration options for the HP Command View EVA user interface. For information about other conguration options available from the Management Agent options window, see the HP Command View EVA online help.
Changing the port and timeout parameters
You can change the port that you use to log into the HP Command View EVA user interface. (The default port is 2372). You can also change the timeout parameter, which determines how much inactivity can occur before the browser session times out and requires you to log in again. To change these parameters, you must edit the cveva.cfg le, which is located in the C:\Program Files\Hewlett-Packard\SANworks\Element Manager for StorageWorks HSV\Bridge directory. (If you installed HP Command View EVA on an SMA, the directory is C:\Program Files\Compaq\SANworks\Element Manager for StorageWorks HSV\Bridge.) You can edit this le using a text le editor. Go to the following section: Section Webserver {
# The port for SSL connections

# Default: 2372

port 2372
# The time limit on HTTP sessions in seconds

# Default: 3600 (1 hour)

# Set the value to zero to disable the timeout feature

timeout 3600

Change the port and/or timeout parameter to the appropriate value and save the cveva.cfg le. You must restart the HP Command View EVA service for the changes to become effective. For instructions, see "Restarting the HP Command View EVA service" on page 35. NOTE: If you enter a port that is already in use, you will not be prompted that the port is busy when you restart the HP Command View EVA service. The status of the service shows it has started. You will only know when you attempt to open the user interface and the Page cannot be displayed error message appears that the port is busy. Also, an event is logged in the Windows application event log. You must open this le again, enter a different port, and then restart the service.

Setting user interface options
To set user interface options: 1. Click Agent Options in the Session pane. The Management Agent Options window opens. 2. Click User interface options. The User Interface Options window opens. 3. Under General Options, edit or select the desired settings: Tree objects displayedSet the maximum number of objects that can be displayed in the Navigation pane. The default number is 100. If you have a small number of objects, set Tree objects displayed to a number higher than the number of objects in the SAN. This ensures that the management agent sends the complete tree structure to your browser when you select the tree. If you have more than 100 objects, set Tree objects displayed to a number lower than the number of objects in the SAN, such as 20 or 50. This optimizes performance and ensures that the management agent sends a limited number of objects to the browser when you select the tree. A special page with navigation buttons opens in the browser, enabling you to request other tree objects. Default operating system for new hostsSelect an operating system from the list. This operating system is set as the default when you add a host. 4. Under Display Refresh Options, edit or select the desired settings for the Navigation pane or Content pane: Enable refreshSelect this check box to start the refresh interval for the selected pane. If you do not select this check box, the pane is not refreshed automatically. You must manually refresh all panes using the browser refresh tool. Refresh intervalEnter the amount of time between a refresh of the selected pane (valid values are 45 to 600 seconds). For example, if you enter 60, the selected pane is refreshed every 60 seconds. 5. Click Save changes.
Creating page footer messages
Use the Set Page Footer Message options to enter or edit a text message to display at the bottom of each Content pane for browser sessions on the management server. The message can be a security message or can contain other applicable information. The maximum length is 64 characters and the text appears in red. To set a page footer message: 1. Click Agent Options in the Session pane. The Management Agent Options window opens. 2. Click Page footer message options. The Set Page Footer Message window opens. 3. Enter text or edit the existing message in the text box. 4. Click Save changes. The new message appears in red at the bottom of the Content pane.
Conguring HP Command View EVA
Setting audit logging options
Use the Audit Logging Options feature to capture activities that occur in the HP Command View EVA user interface. These activities will generate events that are captured in a log le. Activities that generate events are: User login and logoff User accessibility (for example, the Access Denied event is generated for users with view only access) Actions that change the state of the EVA (for example, creating a virtual disk) Actions that change the conguration of HP Command View EVA (for example, changing the page footer message) You can have these events sent to one or both of the following logs and you can also specify a directory on a remote server to store the log: Audit log Operating system application log

To set audit logging:

1. Click Agent Options in the Session pane.
The Management Agent Options window opens.
2. Click Audit logging options.
The Audit logging options window opens.
3. Select the log in which to store these events, the directory where the log will be located, the size of the log, and the length of time to retain the log. See the HP Command View EVA online help for detailed instructions. 4. Click Save changes.
Setting a remote location for audit logs
When you set the audit logging options, you can choose a le location on a local or remote server. To use a location on a remote server, the remote server must be accessible to the management server on which HP Command View EVA is installed. If necessary, contact your network administrator to establish the necessary permissions for the CV EVA server to access the remote server. Once permissions are set, complete the following steps: 1. Open the Services window on the management server (where HP Command View EVA is installed). 2. Right-click the HP Command View EVA service and select Stop. 3. Right-click the service again and select Properties.
The Properties window for the HP Command View EVA service opens.
4. Select the LogOn tab. 5. In the Log on as box, select This account and enter a valid user name and password for the remote server. 6. Click OK and close the Properties window. 7. Right-click the service and select Start. NOTE: If you change the log location to the local server, you must enter the log location in the Log location box in the Log to a le section of the Audit Logging Options window in the user interface and then click Save Changes. If you select Disabled in the Log to a le section, this disables the audit log completely. It does not just disable logging to a remote server. If, for some reason, the logs cannot be placed in the requested location, an error message is displayed.
3 Managing your storage environment
This chapter describes how to use HP Command View EVA to manage your storage environment. See the HP Command View EVA online help for detailed procedures. When you install HP Command View EVA, an initial folder structure for an array is created in the Navigation pane. The initial folders are Virtual Disks, Hosts, Disk Groups, Data Replication, and Hardware. You can create subfolders to further organize and manage your hosts and virtual disks.

Troubleshooting HP Command View EVA
Error messages in the user interface
Symptom: When performing tasks in the user interface, an error message such as This page cannot be displayed may appear. Solution: Verify that the browser settings are correct. For more information, see the browser settings in the HP Command View EVA installation guide. If the browser settings are correct, refresh the browser: In Internet Explorer, press Ctrl+F5. In Mozilla, press Shift and click Reload simultaneously. The error message should no longer appear.
Failed communication link to iSCSI devices
Symptom: Several boxes on the iSCSI Controller Properties window display unavailable or unknown. This may indicate that the communication link between HP Command View EVA and the iSCSI device is down. Solution: Open a DOS prompt and ping the iSCSI device. If the ping is successful, click Refresh on the iSCSI Controller Properties window to refresh the communication status. If the state does not change, ensure that the Fibre Channel ports of the iSCSI controller(s) are zoned with the host ports of the EVA(s).
Failed connection warning for empty controller host ports
Symptom: The Connection state box on the Controller Properties window displays Connection failed for an empty host port. Solution: Insert an optical loop-back connector into the empty host port. The Connection state box will display Connected. For more information about optical loop-back connectors, contact your HP-authorized service provider.
Failed entities reported on the disk enclosure
Symptom: Failed entities on a disk enclosure may cause a red X to appear on the entire shelf in the Navigation pane. Solution: Use the following information to help determine the entity that is causing the failure.
Failed transceiver (or GBIC)
The symptoms of a failed transceiver (or GBIC) are: The controller event log contains the following entries: 0d8d9001 <Transceiver error> 0df00011 <Status Change on one or more drive enclosures> 09d50005 <Transitioned to Single Port on Fibre State> The Disk Enclosure Properties window displays the following information: On the Power tab, the operational state displays Good. On the Cooling tab, the status of the sensors displays OK. On the I/O-Comm tab, the operational state of the I/O modules displays Bad or Not Installed.

Failed I/O module

The symptoms of a failed I/O module are: The controller event log contains the following entries: 0ddd9311 <A drive enclosure I/O module error has occurred.> 061e4c13 <An HSV210 Controller has detected only one port of a Fibre Channel service.> 0df00011 <Status change of one or more drive enclosures.> The Disk Enclosure Properties window displays the following information: On the Power tab, the operational state displays Good. On the Cooling tab, the status of the sensors displays OK. On the I/O-Comm tab, the operational state of the I/O modules displays Not Installed or Failed.

Conguring HP Command View EVAPerf
To begin array monitoring, ensure that HP Command View EVAPerf is congured properly: EVA Data Collection service The service uses TCP port 860. You may need to open this port on your rewall. The service is set to manual start when you install HP Command View EVAPerf. When you run the HP Command View EVAPerf command line interface, the service starts and remains running until you reboot the host. Set the service to start automatically if you use Windows Performance Monitor for background logging. If you execute logging before starting this service, the startup time for the service may exceed the time that Windows Performance Monitor waits for the rst data samples. You can also start and stop the service using Windows Service Manager. HP Command View EVAPerf command line interface
Ensure that you run the command line interface from the directory on which it was installed. Otherwise, the necessary conguration les will not be found. Array Ensure that the array for which you want to gather performance metrics is initialized. Otherwise, the Failure to get metrics error message appears. This error message also appears if the array is unresponsive (due to other activities on the array) or if you attempt to gather metrics during a controller software upgrade. HP recommends that you use unique names for each array. For example, if you are adding an array to a SAN and the name for that array is the same as another array that exists in the SAN, you should change the name of the new array before adding it to the SAN. A SAN that contains arrays with duplicate names may result in unpredictable behavior.
Enabling access to password-protected arrays
If the array you want to monitor is password protected, you must identify the array's world wide name (WWN) and password. NOTE: The array password is rst entered on the operator control panel (OCP) of the array controller. When you enter the array WWN, you can use upper or lowercase letters and either include or eliminate hyphen separators. For example, 5000-1FE1-5000-CD30, 5000-1fe1-5000-cd30, and 50001FE15000cd30 are all valid WWN entries. To enable HP Command View EVAPerf access to a password-protected array: 1. Open a command window. 2. Change to the directory on which HP Command View EVAPerf is installed. 3. Enter the following command: evaperf spw array_WWN array_password
where: array_WWN is the WWN of the array. array_password is the password entered on the OCP of the array controller. For example: C:\evapmt>evaperf spw 50001FE15000A9F0 RSGHSVxx
Setting the password for array WWN: 50001FE15000A9F0

Password set

To verify the array password, enter the following command: evaperf vpw
Passwords are veried before they are added to the arraypass.conf le in encrypted format. The only way you can enter an incorrect password is if it was changed on the array.

Creating friendly names

You can associate the WWNs of objects, such as arrays, virtual disks, and hosts, with more readable identiers called friendly names. For example, you can identify an array that is known by its WWN of 5000-1FE1-5000-A9F0 as RSG14HSV1. You can extract this information from HP Command View EVA and use it in HP Command View EVAPerf.
Monitoring array performance
Creating the friendly names host le
To create the friendly names host le, you will need the account user name and password that was created for you during installation of HP Command View EVA. Complete the following procedure: 1. Open a command window. 2. Change to the directory on which HP Command View EVAPerf is installed. 3. Enter the following command: evaperf fnh [hostname] [username] [password]
where: hostname is the name of the management server running HP Command View EVA. username is the account user name that was created during HP Command View EVA installation. password is the account password that was created during HP Command View EVA installation. HP Command View EVAPerf veries that it can access HP Command View EVA before adding the information to the fnamehosts.conf le. NOTE: If you enter the fnh command without parameters, a list of known management servers running HP Command View EVA appears.

Adding friendly names

To add friendly names for arrays congured with the fnh command: 1. Open a command window. 2. Change to the directory on which HP Command View EVAPerf is installed. 3. Enter the following command: evaperf fn
The fnames.conf le is created. Any friendly name information that exists for the management servers running HP Command View EVA and listed in the fnamehosts.conf le is extracted from HP Command View EVA and stored in the fnames.conf le. Update the fnames.conf le when you make changes to the arrays. The fnames.conf le must reside in the directory in which HP Command View EVAPerf was installed.
Adding friendly names manually
You can create and maintain the fnames.conf le manually using a standard text editor. Each line in the le contains a WWN that uniquely identies an object and the friendly name of the object. When reading this le, HP Command View EVAPerf ignores blank lines and lines that begin with a pound sign (#). The following is a listing from a manually created le:

Using short names

If the friendly names you created in HP Command View EVA are impractical for the HP Command View EVAPerf command line interface, you can substitute contractions for full names in the fnames.dict le. When you install HP Command View EVAPerf, the fnames_sample.dict le is also installed. You can either: Rename this le to fnames.dict and modify its contents to include the short names. Create a separate le called fnames.dict using a standard editor.
Within the fnames.dict le, enter a short name for each long friendly name as follows:
<long name> <short name>
For example: # Sample contractions dictionary:
Test1\\Copy of Test1 Test1-c

chienchi cc

Test1\Test1 VV
Consider the following when creating names: If either the long or short name contains spaces, enclose the name in quotes. If a back slash appears within a string enclosed in quotes, you must add another back slash. Enter one long and short name combination per line. To use the short name you have entered in this le, add the cn modier to any command you enter in the HP Command View EVAPerf command line interface. The short name is substituted when a long name is encountered.
Using the command line interface
You can use the HP Command View EVAPerf command line interface to display EVA performance data in a tabular format. The procedures in this section assume you are familiar with command line interfaces.

Viewing arrays

To view arrays visible to HP Command View EVAPerf: 1. Open a command window. 2. Change to the directory in which HP Command View EVAPerf is installed. 3. Enter the following command: evaperf ls
The visible arrays are listed.

Specifying the output

This section describes the ways you can specify the command line interface output.

Refreshing data

The command line interface output does not refresh automatically while you are viewing it. To continuously refresh the array data, enter the following command: evaperf as -cont To set a refresh frequency (in seconds), include the n modier in the command: evaperf as -cont 10 NOTE: If you do not specify an interval, the default interval is one second.

Limiting data quantity

You can limit the amount of data that is collected and presented, which can be useful if your conguration includes numerous arrays, physical disks, and virtual disks. To limit the arrays for which HP Command View EVAPerf collects data, enter the following command: evaperf as -sz array1 array10 array32
The output contains data for the specied arrays only.
To limit the virtual disks for which HP Command View EVAPerf collects data, enter the following command:
evaperf vd -fvd disk2 disk4 disk8
The output contains data for the specied virtual disks only.

-dur n

-fd keyword

-fo lename

-fvd vdisk [vdisk]*
-KB -nfn -nh -nots -od -sz array [array]*

Modier

ts1 -ts2 -us
Adds a time stamp to the -csv output in the following format: Fri Jul 23 16:23:05 2004. Adds a time stamp to the -csv output in the following format: 23/Jul/2004 16:23:05 2004. This is the default format. Display times in microseconds (the default is milliseconds). Latencies are displayed in milliseconds (ms) by default. Use the -us option to show times in microseconds for more accuracy. The -us modier does not affect the following commands: vdrl vdrlg vdwl vdwlg
Using the graphical user interface
This section describes how to display and manage EVA performance metrics using the graphical user interface, Windows Performance Monitor, and assumes that you are familiar with the tool. Windows Performance Monitor does not permit more than one hierarchical object level. Therefore, objects, such as virtual disks, are grouped as a single list of instances, even though they may be located on different EVAs. The instance name indicates the array on which the virtual disk is located. To display EVA performance metrics: 1. Start Windows Performance Monitor.
The Performance window opens.
Figure 6 Performance window 2. Right-click in the graphics area. A menu opens. 3. Select Add Counters and click OK. The Add Counters dialog box opens.
Figure 7 Add Counters dialog box NOTE: To view a description of a counter, select a counter and click Explain. 4. Click Select counters from computer and, in the adjacent box, select the host on which HP Command View EVAPerf is running. 5. From the Performance object box, select an object to monitor (for example, HP EVA Storage Array). 6. Click All counters, or select counters to view. 7. Click All instances, or select instances to view. 8. Click Add to add the counters to the window. The utility begins displaying the performance metrics of the selected EVA object. 9. To add other objects, repeat the steps. To remove metrics, select the metric from the list and click the remove icon, which appears as an X. 10. To close the utility, click Close.

Data ltering

You can limit the amount of data that is collected and presented, which can be useful if your conguration includes numerous arrays, physical disks, and virtual disks. Windows Performance Monitor uses the evapmfilt.conf le, which contains the names of the virtual disks and arrays for which you want to retrieve data. Use the HP Command View EVAPerf command line interface to create or update the evapmfilt.conf le.

Congure ltering

To congure ltering for Windows Performance Monitor: 1. Stop Windows Performance Monitor. 2. Open the command line interface. 3. To lter data for specic arrays, enter the following command with the array names: pfa [array]*
This creates the evapmfilt.conf le. 4. To lter data for specic virtual disks, enter the following command with the virtual disk names: pfvd [vdisk]*

NOTE: You can use friendly names in these commands. 5. When ltering conguration is complete, restart Windows Performance Monitor. When you click Add counters in a new Windows Performance Monitor session, the evapmfilt.conf le is detected and data is ltered accordingly. Until you turn ltering off, the lters you congure remain active in successive sessions. (A message indicates that ltering is active.) To make changes, follow the same procedure and use the same commands to update the virtual disk or array names. To stop ltering: 1. Stop Windows Performance Monitor. 2. Open the command line interface. 3. Enter the following command: pfd
4. Restart Windows Performance Monitor.

Objects and counters

Use the objects and counters in Windows Performance Monitor to gather performance metrics. Objects are the items you can monitor, such as virtual disks, hosts, and controllers. The counters characterize the workload and performance for each object. The following identifying information is common to several objects: CtlrThe controller for which metrics are being reported. This eld shows the last four digits of the controller serial number. NodeThe array from which data has been collected. GroupIDThe disk group to which the virtual or physical disk belongs. NOTE: Not all metrics that are available in the command line interface are available in Windows Performance Monitor.

HP EVA DR tunnels

The HP EVA DR tunnels object reports the intensity and behavior of the link trafc between source and destination arrays. The counters for this object display information only if there is at least one active DR group on the array; otherwise, only the header appears. You can display metrics in either MBs or KBs. Although some arrays allow up to four open tunnels on a host port, only one tunnel is active for a single DR group. Multiple DR groups can share the same tunnel. Statistics for each tunnel are reported by both the source and destination arrays, but the directional counters are complementary. The port names are displayed as FP1 and FP2 for the HSV100, HSV110, and HSV200 controller series, and as FP1, FP2, FP3, and FP4 for the HSV210 series. The counters are: Round Trip DelayThe average time, in milliseconds, for a signal (ping) to travel from the source to the destination and back. In replication trafc, the signal is queued behind data transmissions, which increases the round trip delay. If the destination controller is busy, the value also increases. Round trip delay is reported for all active tunnels. Copy RetriesThe number of copies from the source EVA that were retransmitted due to a failed copy transmission. Each retry creates a 128KB copy. Retries are reported by both the source and destination arrays. Write RetriesThe number of writes from the source EVA that were retransmitted due to a failed write to the destination EVA. Each retry creates an 8KB copy. If the write contains multiple 8KB segments, only the failed segments are retransmitted. Retries are reported by both the source and destination arrays. Copy In MB/sThe rate at which data is copied to an array to populate the members of a DR group with data when an initial copy or full copy is requested. Copy Out MB/sThe rate at which data is copied from an array to populate the members of a DR group with data when an initial copy or full copy is requested. Write In MB/sThe rate at which data is written to an array because of write activity to the members of the source array. The write activity includes host writes, merges, and replication retries. A merge is an action initiated by the source array to write new host data that has been received and logged while a replication write to the destination array was interrupted, and now has been restored. Write Out MB/sThe rate at which data is written from an array because of write activity to the members of the source array. The write activity includes host writes, merges, and replication retries. Minimum Write ResourcesThe minimum number of free resources available for DR write operations. Minimum Copy ResourcesThe minimum number of free resources available for DR copy operations. Minimum Command ResourcesThe minimum number of free resources available for DR command operations.

Event code format

Controller and controller termination event codes appear as 32bit hexadecimal numbers (for example, 060f4013). The bits in the event code differ slightly for each controller event type. The bits of a controller event have the following format: Table 4 Controller event code bits
31.24 Software component ID 23.16 Event number 15.8 Corrective action code 7.1 Event information packet type
The bits of a controller termination event have the following format: Table 5 Controller termination event code bits
31.24 Software component ID 23.16 Event number 15.8 Corrective action code..7. Coupled crash control code 6.5 Dump/restart control code 4.0 Parameter count
The following table provides the interpretation of each bit. Table 6 Event code bit interpretation Bit

24:31 16:23

Interpretation
The software component ID (SCID or SCWID) identies the software component that generated the event. The ID ranges from 0x00 to 0xFF. The event number is unique for each software component and ranges from 0x00 to 0xFF. Each event code is uniquely identiable by the combination of the SCID and the event number in bits 16:23. The corrective action code is in the range 0x00 to 0xFF. (Controller events only) The event information packet type contains a reason for the event and a template that denes the meaning of the data in the packet. It is in the range 0x00 to 0x2F. (Controller termination events only) The coupled crash control code species whether both controllers are terminating operation. (Controller termination events only) The dump/restart control code species whether a crash dump is occurring as part of the termination and whether the controllers will restart following termination. The termination parameter count species the number of entries in the Termination Parameters array that are valid for this termination. If the parameter count is greater than zero, the termination code description in the parse le will describe the meaning of each parameter.

8:15 0:7

Event code types and descriptions
This section lists the event code types and descriptions.

Software component IDs

The software component IDs are: ID

b c d e 83 84

Executive Services Cache Management Component Storage System State Services Fault Management Fibre Channel Services Container Services RAID Services Storage System Management Interface System Services Data Replication Manager Component Disk Enclosure Environmental Monitoring Unit Services System Data Center Host Port Metadata Utilities Diagnostic Operations Generator Diagnostic Runtime Services

Corrective action codes

You can view the complete list of corrective action codes when you select Corrective action code in an event description.
Event information packet (EIP) types

The EIP types are: Code

Fault Manager Termination Processing Recursive Entry Event Fault Manager Termination Processing Unexpected Fault Manager Management Event Fibre Channel Services Physical Disk Drive Error Storage System Management Interface Entity State Change

Fault Manager Termination Event
HSV210 controller operation was terminated due to an unrecoverable event detected by either software or hardware or due to an action initiated via the Storage System Management Interface. HSV210 controller operation was terminated due to an unrecoverable event detected by either software or hardware or due to an action initiated via the Storage System Management Interface. General Storage System state information to be reported.
Fault Manager Termination Event (old Termination Event Information Header)
General Storage System State Services State Information Event
Coupled crash control codes
The coupled crash control codes are: Code
Other controller should not perform a coupled crash. Other controller should perform a coupled crash.
Dump/restart control codes
The dump/restart control codes are: Code
Perform crash dump then restart. Do not perform crash dump, just restart. Perform a crash dump and do not restart. Do not perform crash dump and do not restart.

Glossary

This glossary denes terms that are used in this guide or are related to the software. array client See storage system and virtual array. An intelligent device that requests services from other intelligent devices. In the context of HP Command View EVA, a client is a computer used to access the software remotely using a supported browser.
default disk group The disk group created when the array is initialized. The disk group must contain a minimum of eight disks. The maximum is the number of installed disks. disk group A named group of disks selected from available disks in an array. One or more virtual disks can be created from a disk group. Data replication group. A named group of virtual disks selected from one or more disk groups so that they replicate to the same destination, fail over together if a member virtual disk fails, and preserve write order within the group. Enterprise Virtual Array. An HP StorageWorks disk array product that allows pooled disk capacity to be presented to hosts as one or more variably sized physical devices. An EVA consists of disks, controllers, cables, power supplies, and controller software. Storage system, virtual array, and storage array are other names for an EVA. See also virtual disk. An operation that reverses replication direction so that the destination becomes the source and the source becomes the destination. Failovers can be planned or unplanned and can occur between DR groups, managed sets, fabrics or paths, and array controllers. A server that runs customer applications such as le and print services. HP Command View EVA and HP Replication Solutions Manager can be used on a general-purpose server in limited congurations. A computer that runs user applications and uses (or potentially uses) one or more virtual disks that are created and presented by the array controller. The installation of HP Command View EVA on a management server.