9 Implementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Command View UpgradeThe hp StorageWorks command view xp 2.0 contains major architecture changes to support the new XP12000 array, enhanced user security and other new features.Unlike earlier hp StorageWorks command view xp (CV XP) version, CV XP 2.0 is known to be incompatible with XP1024 and XP128 array firmware version of /00 and earlier.As a result, existing customers with XP128 and XP1024 with incompatible firmware cannot use CV XP 2.0 to manage their arrays.If the customers decide to purchase a XP12000, the customers must use CV XP 2.0 to manage this new array architecture. Please refer to the CV XP compatibility white paper for compatibility matrix. The white paper will be available in PIT.Sept 2004HP RestrictedSept 2004

12 Multiple Version of CV/PA Existing in the SANImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Multiple Version of CV/PA Existing in the SANCV 1.8 MSCV 2.0 MSXP 128 with new FWXP 128 with older firmwareXP 1024 with older firmwareXP 12000Host 1 with CV 1.8 Host AgentHost 2 with CV 1.8 Host AgentHost 3 with CV 2.0 Host AgentHost 4 with CV 2.0 Host AgentManages ArraysCV 2.0 management server can only manage array with firmware version equal or greater than firmware specified in streams document.Some user may maintain both earlier CV version and CV 2.0 on the same SAN.For Path Connectivity, user needs to use the corresponding host agent from the CV release. For example, host connected to the arrays managed by CV 1.8 needs to use CV 1.8 host agent for the CV 1.8 MS to see ALL path Connectivity data.In the above figure , CV 1.8 is needed to manage arrays with older firmware and CV 2.0 is needed to manage XP12000 and array with newer firmware. Host 1 and Host 2 are connected to the arrays managed by CV 1.8 and so required CV 1.8 host agent. Host 2 will not be able to gather array information from the XP128 managed by CV 2.0; therefore, the CV 1.8 Path Connectivity will not be able to show array specific and connectivity health information for this array.Sept 2004HP RestrictedSept 2004

13 Launching Array Management GUIImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Launching Array Management GUIFor XP128, XP1024 and XP12000 array types, the Web Console (GUI) can be launched directly (without CV XP) using the following URL: IP Address>The main differences between the Web Console GUI and the CV GUI will be that there will be no Online help icon. Hence the Online help icon functionality is not available in Web Console GUI when launched directly (without CV XP) using the above URL.Another significant difference is that you cannot list or kill web console GUI sessions from Command View where as you can list or kill CV GUI sessions from command view.Sept 2004HP RestrictedSept 2004

14 Implementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Command View XP 2.0 GUICommand View XP 2.0 GUIThe Open Systems support is available in XP12000, XP1024, XP128, XP512 and XP48 through GUI, API and CLI.Mainframe support is available in XP12000, XP1024 and XP128 through GUI only.Note: There is no support for XP256 arrays from Command View 2.0 version forward. To manage XP256 arrays, the user needs to have CV1.8 or earlier versions.Support for XP1024/128/ No support for XP256.Sept 2004HP RestrictedSept 2004

15 Array Manager - device launcherImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Array Manager - device launcherFor XP512/48 – Opens in the same CV window.Command View 2.0The image above shows the Command View XP 2.0 GUI.Open Systems support is available in XP12000, XP1024, XP128, XP512 and XP48 through GUI, API and CLI.Mainframe support is available in XP12000, XP1024 and XP128 through GUI only.For XP12000, XP1024 and XP128 array, only one link is available in Device launcher.When the user clicks on this link, a new browser is launched. This new browser is always launched in the default View Mode.For XP512 and XP48 array types, two links for View and Modify are available in Device launcher screen.Note: There is no support for XP256 array types from CV2.0 version onwards. To manage XP256 arrays, the user needs to have CV1.8 or earlier versions. It is recommended that for actively managing XP256 arrays, Remote Control XP be used.For XP128/1024/12000 – Opens a new browser window.Sept 2004HP RestrictedSept 2004

16 Array Manager - device administrationImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Array Manager - device administrationTo add or register a disk array:From the Device Administration window, enter the disk array’s IP address in the Agent IP Address field.Press Enter or click Submit.The Serial Number, Product Type, and Product Number fields are filled in automatically.If the Device Name field is blank, enter a name for the disk array.For the XP1024/XP12000, select the left DKU type and right DKU type from the drop-down lists.If the Contact and Location fields are blank, enter a contact name and a location.Select the Manage Array check box. This check box is selected by default. If it is not selected, the disk array is added to Command View’s list, but it will not be managed by Command View. No configuration data will be retrieved.Click Save and then click OK to confirm.Device Administrator screen is used to add/delete new disk array, change array parametersSept 2004HP RestrictedSept 2004

17 Array Manager - Session AdministrationImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Array Manager - Session AdministrationUse Session Administration to view information about disk array sessions and to end sessions.Multiple users can access a disk array simultaneously. Only one user is allowed to be in Modify mode, but there can be many view-only users.View-only or modify status is determined by user permissions (set using the User Administration functions) and by whether another “modify” user is already managing a disk array. In that case, the second user’s permissions are downgraded to view-only.If a session is inactive after a certain period of time because a user has not used the system, Command View automatically terminates the session. The default is 60 minutes, which can be changed. To change the value, edit the SESSION_TIMEOUT_PLAN value in the CommandView.properties fileUse Session Administration to view information about disk array sessions and to end sessions.Sept 2004HP RestrictedSept 2004

18 Changing session timeout valueImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Changing session timeout valueThe session timeout value determines how long a session lasts after a user in Modify mode has not used the browser.The default is set to 60 minutes.You can change the value by editing a configuration file. To change the value, edit the SESSION_TIMEOUT_PLAN value in the CommandView.properties file.SESSION_TIMEOUT_PLAN value can be:ONCE:ValueUsing this setting, Command View checks the CommandView. properties file only once, when someone adds a device or restarts the server, and then sets the session timeout value at that time.ALWAYS:valueUsing this setting, Command View checks the CommandView. properties file every time a user in Modify mode clicks a tab to manage an XP128, XP1024 and XP12000 (Identity and Status tabs excluded).CV session timeoutTo change the session timeout value:Locate the CommandView.properties file in the C:\hpss\dm\tomcat\webapps\hpstmgmt\webroot\Stormgmt directory.Use a word processor or text editor to open the file. Look for the SESSION_TIMEOUT_PLAN setting by locating the following line:SESSION_TIMEOUT_PLAN=ONCE:60Replace 60 with the number of minutes you want a session to last before it times out due to inactivity. This setting is applicable to all XP disk arrays.If you are managing an XP128, XP1024 or XP12000, also consider changing ONCE to ALWAYS. The default is ONCE:60. Most users will want to choose the ONCE setting. Using this setting means that Command View checks the CommandView.properties file only once, when someone adds a device or restarts the server, and then sets the session timeout value at that time.Certain users may find they need the flexibility of the ALWAYS setting, which ensures that Command View always determines the timeout value. Using this setting means that Command View checks the CommandView.properties file every time a user in Modify mode clicks a tab to manage an XP128, XP1024 or XP12000 (Identity and Status tabs excluded). You may want to consider using this setting if you or someone else needs to change the timeout value on the SVP, but you want to override that when using Command View.Note: This setting adds an additional delay of approximately 45 seconds when loading a new window.Save and close the file.Restart Command View XP Services by clicking Start  Programs  HP StorageWorks Command View XP  Restart Services.Sept 2004HP RestrictedSept 2004

20 Implementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Control PanelUse the Control Panel to edit user accounts, set environment parameters, and download files containing log information.To access the Control Panel, click Option button in the Command View window. Option is only a tool tip which will be visible when you place the cursor on the icon.Sept 2004HP RestrictedSept 2004

21 Implementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0system pageThe System window provides information about the equipment and the port status of the connected subsystem.Displays port statusCommand View system pageThe System window is an array-dependent window, specific only to XP12000.The System window provides information about the equipment and the port status of the connected subsystem.The Base information pane provides the following information:Product name — Name of the device of the connected subsystemSerial Number — Serial number of the connected subsystemIP Address — IP address of the connected subsystem (SVP)Main FW Version — Version of the microprogram installed in the connected subsystemSVP Version — Version of the Java applet program installed in the SVP of the connected subsystemRMI Server Version — Version of the RMI server installed in the SVP of the connected subsystem Port StatusCluster 1 and Cluster 2 indicate the clusters. The ports belonging to Cluster 1 are listed on the upper part, and the ports belonging to Cluster 2 are listed on the lower part of the Port Status pane.Each cluster has eight printed circuit boards (PCBs) and the name of each PCB is displayed on the header of the port list.Sept 2004HP RestrictedSept 2004

22 Implementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0status pageThe status history is listed in the Status window.The XP12000 generates a service information message (SIM) whenever it detects an error or service requirement.The Status window provides information about the internal statuses (according to the SIM information reported to the host) of the connected subsystem.Sept 2004HP RestrictedSept 2004

23 Implementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0status detailsTo obtain status details:Select to highlight a row in the StatusRight-click and then click Detail.Status detailsTo obtain Status details:Select to highlight a row in the StatusRight-click and then click Detail.The following information is provided:Ref. Code — Displays the Service Information Message (SIM) reference code to identify an error.Error Level — Displays the following error levels:GoodServiceModerateSeriousAcuteStatus — Displays one of the following:Complete — If the SIM has been deleted from the SVP.Not Complete — If the error has not been deleted.Date — Displays the date that the SIM occurred.Error Section — The name of the component which is in error condition.Error Detail — A detailed description of the error.Sept 2004HP RestrictedSept 2004

24 Command View 2.0 log on operationsImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Command View 2.0 log on operationsMaximum number of concurrent usersThe XP12000 can support up to 32 concurrent users, but only one user can be in Modify mode at a time.Logging on to multiple web servers (SVPs)The same user can concurrently log on to more than one web server.Logging on to the same web server more than once ConcurrentlyThe same user (ID) may not have multiple concurrent sessions with the same web server (SVP).Logon historyAll logon information can be viewed by a user belonging to the Administrators group.Automatic logoff operationThe default is one minute, but a user belonging to the Administrators group can specify a different amount of time.Log on operationsThe XP12000 can support up to 32 concurrent users, but only one user can be in Modify mode at a time.Note: The total maximum number of concurrent users for displaying the Performance Monitor panel and executing the Export Tool is two users.The same user can concurrently log on to more than one web server, by opening an individual storage device list for each SVP, downloading the web client Java™ applet program from each SVP, and executing the Java™ applets on separate web browser windows.Note: If you execute multiple web client Java™ applet programs for multiple SVPs, insufficient memory may degrade performance.Sept 2004HP RestrictedSept 2004

27 Implementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Array HistoryTo configure an XP disk array to forward traps to Trap Distributor, refer to the Trap Distributor section of the “Integrating HP StorageWorks Command View XP with Other Platforms” page under the Support tab in Command View.Array Event History is similar to Event Notification with the primary difference that Event Notification will automatically record events and generate notifications for any managed disk array and Path Connectivity without requiring additional configuration. Trap Distributor can be used to record events from unmanaged disk arrays as well as managed disk arrays.Use the Array Event History pane to view recent disk array events and error conditions.To use Array Event History, you must configure one or more XP disk arrays to forward traps to Command View’s Trap Distributor and then you can choose to set up Trap Distributor to forward SNMP traps.Only SNMP traps received by Trap Distributor are recorded in the Array Event History pane.Sept 2004HP RestrictedSept 2004

28 Implementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Event NotificationUse the Event Notification pane to configure and dispatch notifications, configure the history log file, view events and notification history, and test notification dispatching. Event Notification also includes a history log of disk array events.Event Notification will automatically record events and generate notifications for any managed disk array and Path Connectivity without requiring additional configuration. Trap Distributor can be used to record events from unmanaged disk arrays as well as managed disk arrays.Sept 2004HP RestrictedSept 2004

29 Command View security architectureImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Command View security architectureCommand View security architectureCommand View 1.80 user administration and authentication system is fragmented where GUI, CLI and PC used one authentication system with its own user database and Command View API had another system with its own user database. Command View 2.0 user administration system is an integrated one, where all of GUI, CLI, API and Command View snap-in apps: PC, PA uses the same authentication system and user database, which is based on the CSSI security model.The CSSI security system provides only very basic authentication system, where the user can be authenticated, gets authorization token, which can be used to verify his access to various parts of the system. The Command View 2.0 model has a thin layer above CSSI security system basically to maintain rules for Command View imposed restrictions on users/groups so that any unauthorized, timed out, logged out users cannot use their access token to re-enter the security system.The layer above CSSI security system is provided through a separate module in CSSI layer. This module exposes various methods for authentication, authorization checks, management of users/groups (add/delete/modify users/groups etc.). This component makes necessary checks for the user rights before passing on the information to the actual CSSI security system. The clients (GUI, API, CLI) can contact this new module to use these services.This new module is a separate RMI service running on Management station. This RMI service is an extension of security RMI Service provided by CSSI security system with Command View specific code. Thus RMI server will be used by Command View CLI, Command View GUI and PA (with or without Command View).Sept 2004HP RestrictedSept 2004

30 Command View CSSI securityImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Command View CSSI securityCommand View 1.80User administration and authentication system is fragmentedGUI, CLI and PC used one authentication system with its own user databaseCommand View API had another system with its own user database.Command View 2.0User administration system is integratedAll GUI, CLI, API and Command View snap-in applications (for example, Performance Advisor) use the same authentication system and user databaseAuthentication system is based on the CSSI security model.Command view securityThe overall design of CSSI is loosely based on the Windows security model.Much of the terminology used here is the same as that used in the Windows security documentation.The CSSI security system provides only very basic authentication system, where the user can be authenticated, gets authorization token, which can be used to verify his access to various parts of the system.The Command View 2.0 model has a thin layer above CSSI security system basically to maintain rules for Command View imposed restrictions on users/groups so that any unauthorized, timed out, logged out users cannot use their access token to re-enter the security system.The layer above CSSI security system is provided through a separate module in CSSI layer. This module exposes various methods for authentication, authorization checks, management of users/groups (add/delete/modify users/groups etc.). This component makes necessary checks for the user rights before passing on the information to the actual CSSI security system. The clients (GUI, API, CLI) can contact this new module to use these services.This new module is a separate RMI service running on Management station. This RMI service is an extension of security RMI Service provided by CSSI security system with Command View specific code. Thus RMI server will be used by Command View CLI, Command View GUI and PA (with or without Command View ).Sept 2004HP RestrictedSept 2004

31 Implementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Users and groupsUsers in Command View 2.0 are classified in four categories:Normal UsersBasic group with read only access to entire Command View FrameworkStorage AdministratorsThese users are storage administrators for one or more arrays.Command View AdministratorsThese users are the super administrators of the Command View management station. They have modify access to everything.Command View 2.0 user categoriesNormal/Ordinary usersThese users are basically read-only users who can only view the configuration of the command View. These users always are member of Users group.Storage administratorsThese users are storage administrators for zero or more arrays. These users have modify permissions on zero or more arrays but rest of the permissions are same as that of Normal users. These users always are members of StorageAdmins group.Command View administratorsThese users are the super administrators of the Command View management station. They have modify access to everything. These users will always be the members of Administrators group.Sept 2004HP RestrictedSept 2004

32 Default users and permissionsImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Default users and permissionsUser-idUser GroupadministratorAdministratorsstorageadminStorageAdminsuserUsersCommand View usersCommand View maintains users and groups information in the user.xml and group.xml in hpss\security\store folder. The information in these files is encrypted as base-64 encoded string. When the server comes up, it checks to see if these files exist. If not it creates these files with default users (mentioned in subsequent sections) and groups. So if users & groups database are accidentally removed, at least default users/groups information can be restored in this way.AdministratorThere is one default super user with user-id administrator and belongs to the Administrators group.This default user will always be part of Administrators group and cannot be deleted by any user.Only this user can change the password of this user.This user can create additional users in any of the groups.Default password is administratorPassword of administrator can’t be changed by other AdministratorsStorageAdminThere is one default user with user id storageadmin and is part of StorageAdmins group.Always be part of StorageAdmins group and cannot be deleted from it.Cannot be deleted by any other user, including administrator.Only storageadmin or members of Administrators group can change password of storageadmin.UserThere is one default read-only user with user id user who belongs to the Users groupThis user will always be part of Users group and cannot be deleted from it.This user cannot be deleted by any user.Although this user belongs to the Users group (the members of which have no array access initially), this will have by default read only access to all the arrays added to the Command View and the access cannot be removed or changed.Sept 2004HP RestrictedSept 2004

33 Implementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Command View SVP usersAll users of Command View will have the same web console user name for all of the arrays (XP128, XP1024, and XP12000 only) to which they have access.The same user name should be used to gain GUI or RSD API access to the arrays.Following are the scenarios where users are created in SVPWhen a device is added to Command ViewThe device addition will be successful only when the all users in Administrators group could be added to the SVP of that device. Otherwise, device will not be added.When a user is created with Administrators groupThe user will be created in all arrays added in the Command View XP station. If user addition fails on any one of the array (due to network problem, unavailability of lock, and so on), the user will not be added to the Command View.When a user of Users or StorageAdmins group is assigned to one or more arrays ,this user will be created in those arrays.If the user addition fails on any array, that array will not be assigned to the user and a message will be shown in GUI or CLI indicating which array could not be assigned.Sept 2004HP RestrictedSept 2004

34 Single sign-on for Command ViewImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Single sign-on for Command ViewOnce logged into the Command View XP GUI, users are able to access array managers and Command View XP snap-in components (for example, Priority Port Control (PPC) and Performance Advisor (PA)) without being challenged for authorization and authentication.The Security or user admin system will be the common user management platform for all snap-in applications.Command View sign-onOnly Performance Advisor (PA) may have the requirement of running alone without CommandView.The user admin panel of Command View can be directly reused in the PA if it has to run as a stand-alone. As mentioned in the introduction section, the user admin applet has to contact the CSSI RMI service to get the user administration facilities.If PA is installed with Command View 2.0 or later, PA will share the user admin and security components with Command View XP.Command View and PA will have same security, user administration GUI and security back-end.If PA runs standalone without Command View XP, it will have the security binaries installed in \hpss\security\bin directory. PA will use its own set of Administrators for creating PA users and accessing PA functionality. If Command View is installed on the same management station later, the installer must install the Command View from \hpss directory. The installer will downgrade all user IDs in the Administrators group, other than default administrator to StorageAdmins group. It will also force the password of the default administrator to be changed during installation of Command View over PA. PA will now use the user administration GUI screen available in Command View browser GUI.Sept 2004HP RestrictedSept 2004

35 Access to Command View featuresImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Access to Command View featuresAccess to Command View XP framework featuresUsers who wish to access features of the Command View XP framework, such as Path Connectivity, Performance Advisor and so on, must login to the Command View XP management station.Access to Command View XP device managers (Web consoles)There are two ways for users to access the Web Consoles. One is from within the Command View framework by utilizing links provided there. Alternately, users can launch the web console directly without having to login to Command View XP.Access to Command View XP CLIsAny user who has an account in Command View XP framework except default API users, can use CLI by logging-in with the user ID and password with which the user has been defined in Command View XP. However there is no single sign-on between the CLI, GUI and API sessions.If the user is using the GUI after logging in, to use the CLI the user has to login again.Web Console access Via Command View XPCommand View XP provides a centralized place for users to access their arrays. Once the user is logged into the Command View XP framework, they can proceed directly to the device manager and Web Console without re-login, if permissions have been setup properly by the administrator. The web console and device manager are launched in a new screen, leaving the two web sessions.Command View XP Framework URL:Web Console access Via Direct ConnectionUsers who choose to access the web console directly can do so by using a predefined URL. Upon accessing that URL, they will be challenged for a username and password.Command View XP Web Console/Device Manager URL (direct launch): of the SVPNote: Command View XP Framework and Web Console share the same user database.Sept 2004HP RestrictedSept 2004

36 Centralized user administratorImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Centralized user administratorAll user permissions are managed through Command View, and users are permitted to directly access the Web Console using those accounts.Command View will push updates to each affected array at the time array is added to Command View. To minimize synchronization problems, administrators are not permitted to make any user admin changes on the Web Console.If the array is off-line (communication problem, SVP failed and so on) while changes are made to Command View XP user database, the changes are not be allowed.If the array is being modified by some other user the operations are not allowed.Some operations like deleting a user from command view is allowed even if the array is offline or being managed by another user.Sept 2004HP RestrictedSept 2004

37 Command View XP Data SecurityImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Command View XP Data SecuritySVP security – firewall white paper will be available.Security for storage of user login informationThe user and group information will be encryptedImport exports are not allowed in Command View to prevent hacking user account information from one Command View station and installing on anotherThere is an encrypted data exchange between Command View client and server and also with Web console to reduce the risk of being hacked.Book marking a URL with login information to gain access to Command View XP is not allowed as the URL contains a random ID and it is valid for that point of time.Security for RMI communicationThe Command View XP clients/server to RSD SVP communication is through RMI over SSLSept 2004HP RestrictedSept 2004

38 Accessing Security GUIImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Accessing Security GUICommand View 2.0 securityCommand View’s integrated security system provides the capability to authenticate and authorize Command View users. Each user is provided with a user name and assigned to a user group, which determines the tasks the user can perform. For example, members of the Administrators group can use the security functions to perform the following tasks:Add a new userChange passwordsDetermine or modify array membershipDelete a userView group propertiesTo access the Security functions, click Security in the left pane. The Security pane is displayed:The pane consists of two tabs. Users belonging to the Administrators group can select the Users and Groups tabs to view and modify security information. Other users can view security information but cannot make modifications.Add UserDelete UserChange PasswordChange array membershipSept 2004HP RestrictedSept 2004

39 Implementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Adding a new userCommand View 2.0 new userEnter the User Name and Description.Enter and confirm the password.Click Next.Select the group to which the user is a member.Click the right arrow to add the user to the group.Click OK.Sept 2004HP RestrictedSept 2004

40 Implementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Add array membership-The Array Membership pane is used to view or change the arrays assigned to specified users.Only a member of the Administrators group can modify array membership.Command View 2.0 array membershipTo add a user to an array, perform the following:Click to highlight the user.Click Array Membership.Click to highlight the array to which the user will be member.Click the right arrow to add the user to the array.Click OK.Sept 2004HP RestrictedSept 2004

45 Implementing XP12000 Solution FundamentalsCLI overviewImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0A text-based interface used to manage and retrieve information about XP arraysCan run on a CV management station or supported hostSame version of CV must be installed on the CV management stationJRE (Windows) or JRE/RTE (HP-UX) is installed on client CLI platformHost must have network connectivity to the CV management stationInput can be single line entries or batch filesOutput can be displayed on screen or directed into a fileSept 2004HP RestrictedSept 2004

46 Implementing XP12000 Solution FundamentalsRunning the CLIImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Interactive ModeEnter one command at a timeCLI provides a command promptBatch ModeRun a file containing multiple CLI commandsUseful for submitting a large number of commandsCommands are not executed sequentially, instead similar commands are grouped and executed together to increase speed and efficiencySession ends after all commands in batch file have executedSept 2004HP RestrictedSept 2004

50 License key managementImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0License key managementClick the array on which you want to add license capacityClick LicensesArray selectionClick on the array in which you wish to install a license keySoftware license termsCertain software titles are licensed based upon the total physical capacity installed on a single array (excluding spare drives) rounded up to the nearest TB. The customer must have the total installed license capacity that is equal to or greater than the total raw capacity present on the array.Sept 2004HP RestrictedSept 2004

51 Display license key statusImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Display license key statusLicense key displayThis is the main license key management screen. It displays when the refresh completes and the license key information is received from the array.Functionality Option — Shows the list of software options.Status — Shows the installation status of the option (Installed or Not Installed).Key Type — Displays information about the key installed (Temporary, Emergency or Permanent). If no key is installed, the column displays “- -”.Days Left — Displays the number of days left before expiration of the key. This is valid only for temporary and emergency keys.Capacity (TB) — Shows the capacity of the license, in the case of permanent keys. An entry with See License Certificate means that the license is for TB.Buttons — The buttons are enabled for modify users and disabled for view-only users.Install — Takes you to the license key management (install) screen.Uninstall — Takes you to the license key management (uninstall) screen.Cancel — Returns you to the previous screen.Sept 2004HP RestrictedSept 2004

53 Configuration File LoaderNew feature supported in FW /00 or laterComes with a factory loaded license key.Enables user to define configuration of an XP 128/1024/12000 using import/export of spreadsheet fileAllows to download a spreadsheet file that includes the current configuration information, and to upload a new file with user defined configurationIt is used to set the LUN Management settings ONLY.Sept 2004HP Restricted

54 Steps involved in upload/downloadImplementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Steps involved in upload/downloadStudent Notes:Steps Involved in Upload/Download of file:1. File download - to download the spread sheet click download button on configuration file loader GUI. - JAVA WEB START will come up and start a Java application to download the file, specify a file name to be downloaded - configuration will be downloaded in csv format, can be viewed using excel or text editor - the downloaded configuration can be edited/modified to added or delete a configuration2. File Upload to upload the spread sheet click upload button on the screen in fig 3.1.2a JAVA WEB START will come up and start a Java application to upload the file, specify a file name to be uploaded- configuration will be uploaded.Sept 2004HP RestrictedSept 2004

56 Implementing XP12000 Solution Fundamentalshp StorageWorks Command View 2.0Command View XPCV/XP station is required to manage users on the SVPcurrently there is no way to manage users directly on the SVPbe careful when installing multiple CV stations managing the same XPthe last CV/XP station that is installed & configured to manage an XP will overwrite already existing user information on the SVPSept 2004HP RestrictedSept 2004

About project

Feedback

To ensure the functioning of the site, we use cookies. We share information about your activities on the site with our partners and Google partners: social networks and companies engaged in advertising and web analytics. For more information, see the Privacy Policy and Google Privacy &amp Terms.
Your consent to our cookies if you continue to use this website.