1. © 2004 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice Training Documentation SISP tool and supported services (SISP release 6.2)

2. February 2006SISP release 6.22 Table of contents  Overview: Tool, process and supported services Overview: Tool, process and supported services  Submitting a SISP Submitting a SISP  Configuration sections Configuration sections −SISP ExpressSISP Express −SISP Expert ModeSISP Expert Mode  File attachments File attachments  Item configuration Item configuration  Review, change report, and Status Quo Review, change report, and Status Quo  Templates Templates  Superdome and partitionable servers – specific features Superdome and partitionable servers – specific features  Appendix Appendix −LVM detailsLVM details −Template detailsTemplate details

3. Overview: Tool, process and supported services

4. February 2006SISP release 6.24 Overview – What is SISP? Short for “Solution Integration Service Plan” Web based tool used to capture customer intent Used to transport customization information into the factory/integration center Supports specific service offerings, such as HP Factory Express Supports customization of Superdome solutions Note: Term “SISP” often used to reference tool and resulting output file.

5. February 2006SISP release 6.25 SISP tool is/is not IsIs not pre-integration and pre-configuration ordered via a service product −which is part of a hardware product (high end, e.g. Superdome) −ordered with a specific product number −an ordering channel – SISP tool adds value, not material −a means to correct wrong orders or overwrite order information a means of transporting customer intent, asking the customer to provide configuration information before order gets into production including interactive communication with the customer to get the configuration information a tool to −avoid re-racking, re-installation, re-work onsite −allow the CE to concentrate on complex configuration a service to avoid all onsite activities a defined scope of services (configuration of frequently used or basic parameters for a high volume of orders) a service for all kinds of configurations (factory specials, integration centers) −similar configuration for a small amount of orders −all possible configuration options (3rd party etc.) feeding processes within the manufacturing cycle time a service which delays the delivery

6. February 2006SISP release 6.26 HP Factory Express What can be configured using SISP? Customized hardware integration and configuration, e.g. Customized operating system load, e.g. flexible rack configuration of all products ordered factory integrated Customized I/O card integration and configuration Cabling within the rack and between racks Labeling of disks and cables Full bus/split bus configuration Shared bus (2 server) configuration Customized operating system (OS) load on internal and external disks (incl. connecting external disk to server and related disk and card set-up) Kernel parameter settings Basic host and network configuration Partition sizes and LVM parameter settings Mirroring and striping More details on Factory Express available at −http://www.hp.com/go/factory-express (outside HP firewall)http://www.hp.com/go/factory-express −http://factoryexpress.corp.hp.com (inside HP firewall)http://factoryexpress.corp.hp.com

7. February 2006SISP release 6.27 Process Overview The order specifies WHAT goes into the system. The SISP tool specifies HOW the ordered parts go together and software has to be installed.  Information flow for order and SISP information exist independently! (SISP tool has no order link.)  Information entered into the SISP tool has to be checked carefully to be sure it matches the order! Superdome and partitioned servers process, some HP Factory Express orders: Sales configurator data are also sent to the SISP database.  Order information is partially available in SISP tool and can be used as a basis for configuration. OMS database SAP SISP database ItemProduct no. SPU SubitemProduct no. SISP Subitem...... Operating system configuration Rack configuration... WhatHow OrderSISP Sales configurator order informationconfiguration information EMEA only

8. February 2006SISP release 6.28 Basic Ordering Guidelines I Customer desired configuration of several racks, each containing one or more severs ALL components need to be placed on only ONE order section. The special code ‘SO’ (Single Order Solution) must be added in WWOMS. Single Order Solutions Server1 Rack1 Server2 Server3 Rack2 Server4 Server5 Rack3 Order section 001 ‘SO’ Rack1 Server2 Server3 Rack2 Server4 Server5 Rack3 Server1

9. February 2006SISP release 6.29 Basic Ordering Guidelines II Multiple Order Sections Customer changes order from simple one rack/one server configuration to complex solution. Server2 Server3 Rack2 Server1 Rack1 For coordinated delivery every order section needs the special code ‘MS’ (Multiple Order Sections) in WWOMS. No hardware integration from one order section into another! Server1 Rack1 Server3 Order section 001Order section 002 Order section 003 MS Server2 Rack2

10. February 2006SISP release 6.210 Detailed Order Layout Server 1 Disk Array Server 2 1.Place SISP product (e.g. HP Factory Express) as a sub-item of the SPU 2.For Single Order Solutions (code ‘SO’) add SISP product to each SPU to be configured ‘SO’ Order Section 001 0100Rack 0200Server … 0212HP Factory Express … 0300Server … 0317HP Factory Express …

11. February 2006SISP release 6.211 What is not possible using SISP SISP configuration does NOT overwrite the order! This means in particular: Hardware integration from one order section into another is not possible. Parts ordered as factory integrated cannot be shipped separately. Server1 Server2 Order section 1 Rack1 Order section 2 Rack2 Server1 Server2 Rack1 Order section 3 ‘SO’ Server2

12. Submitting a SISP

13. February 2006SISP release 6.213 Starting point for submitting information Information needs to be entered on the web: http://www.sisp.hp.com http://www.sisp.hp.com (users outside HP network) http://sisp.bbn.hp.com http://sisp.bbn.hp.com (users inside HP network) External users need to apply for a login: Fill in the fields on the login page and select “register” Wait for an e-mail reply with a password Internal users can choose an alias and password to login: Fill in the fields on the login page and select “request” Use the chosen alias and password to login

14. February 2006SISP release 6.214 SISP naming conventions A regular SISP (contains order no.) A quote SISP (contains quote no.) Can be saved Can be sent Can be saved Can be linked to an order number If sent, can be processed by the factory. Order number provides the connection between order and configuration information Cannot be sent and therefore not be processed by the factory! The HP order number is used to identify a SISP. If the order number is not known a preliminary quote number can be used instead. Once the order number is known, it needs to be linked to the quote SISP. The order number is unique. A quote number can be assigned several times. SISP Information Order number: ABCD-12345-001 Quote number: test-990823 Customer: test Sales admin contact: who Order configuration: Rack:... Database entry

15. February 2006SISP release 6.215 Main Page Available SISP actions: Create new/open existing SISP Review contents of a SISP Display Status Quo report Display change report to compare order content to SISP Manage SISPs (SISP Actions) −Copy/move/delete an existing SISP −Link a quote SISP to an order number −Create a new SISP from a template List a user’s/group’s SISPs Manage templates Edit user profile Get help Sign out and return to login screen

16. February 2006SISP release 6.216 Main Page Actions I New/Open:Create a new or open an existing SISP. Enter an order number or a quote number or both. If the SISP is still in use or has not been closed correctly (browser crash) a warning message with the user data for the SISP is shown. User can “Take Ownership” of the SISP, but should contact the other user to avoid conflicts. Review:Show a summary of data entries for a specified SISP. Status Quo:Show a summary of the customer intent status of a specified order including factory default configuration where applicable. Change report:Display a table containing the contents of the SISP and the corresponding (most recent) sales configurator data. User needs to compare these data and decide if changes to the SISP are necessary. The order and/or quote number have to be entered. For all actions where order and quote numbers are required: If one of the entered numbers (order or quote) cannot be found, a list containing possible selections will be displayed.

17. February 2006SISP release 6.217 Main Page Actions II Link:If a SISP was created based on a quote number (“quote SISP”) the final order number needs to be assigned to activate the SISP. If items were specified in the quote SISP, the item numbers can be renamed now to match the order structure. Copy:Copy an existing SISP to up to five destinations. If an activated (sent) SISP is copied to another order number, the copy is activated as well. Copy modules:Create a new SISP out of several other SISPs. Copy from template:Create a new SISP from a template. Move:Move an existing SIS to a new name (rename). If an activated SISP is moved to a quote SISP it will no longer be activated! Delete:Delete an existing SISP.

18. February 2006SISP release 6.218 Main Page Actions III List my SISP’s:Display information about all SISPs created and/or changed by the user. Search can be restricted by selection SISP status (sent, saved, locked etc.). List group SISP’s:List SISPs of group members. Template management: Provides options to search for templates, create new modular or super templates or modify them, and delete templates. Also allows to assign modular or super templates to a SISP. User profile:Change user information like password, e-mail address etc. Help:Display the help pages. Technical support:Display a list of support personnel. FAQ:Display a page with frequently asked questions. Sign out:Return to the SISP login screen.

19. February 2006SISP release 6.219 Order Information Section Mandatory information for a new SISP: SISP type, operating system, and customer company. Information on this page can be changed later. Superdome and partitionable servers, HP Factory Express orders: If sales configurator data are available, the correct SISP type will be pre-selected. No other SISP options will be shown. It is recommended to wait for sales configurator (WATSON) data before entering a SISP for Superdome and partitionable servers.

20. February 2006SISP release 6.220 Lock message when trying to work on a SISP: An item gets locked if the device with the item number comes into production. A locked item cannot be changed in the SISP any longer. If a locked item has not been specified separately the order configuration will be locked as well. Lock message when trying to open a SISP: A SISP can be blocked by a user because: he/she is working on the SISP the SISP has not been closed correctly (e.g. browser crash) It is recommended to contact the SISP owner before taking ownership (to make sure nobody is working on the SISP). Lock Messages

21. February 2006SISP release 6.221 What to do after SISP is filled out? save:Brings a SISP from a temporary storage area into the database. send and close:SISP is activated, i.e. SISP can be processed by manufacturing. If sent, the ‘save’ command will no longer be available. A SISP can only be updated by the ‘send’ command. save as template:SISP is stored in the personal template archive. Any attachments are saved with the SISP. It is possible to add a comment for the template. close:SISP is closed. Always exit a SISP with ‘close’, otherwise changes may be left in the temporary storage area. If a SISP has not been closed the user will be asked to “Take Ownership” of the SISP the next time he/she tries to open it.

22. Configuration sections

23. February 2006SISP release 6.223 SISP Express vs. SISP Expert Mode SISP Express  Allows quick and easy configuration using templates and/or attachments  No tables  Guided data entry SISP Expert Mode  For in-depth customization  Full range of configuration pages and tables

24. SISP Express

25. February 2006SISP release 6.225 SISP Express – step 1 Assign template – search  Enter search parameters: −Template name (optional) −Owner (HP Best Practice and User Templates pre- selected)  Select “Next” to display search results or  Select “Next” to skip template assignment

26. February 2006SISP release 6.226 SISP Express – step 1 Assign template – select from results  Select template from search results  Select “Next” to continue with step 2 or  Select “Next” to skip template assignment and continue with step 2

27. February 2006SISP release 6.227 SISP Express – step 2 Attachments  For each file to be attached choose scope and file type and select “upload”  Select “Next” when finished or  Select “Next” to continue with step 3

28. February 2006SISP release 6.228 SISP Express – step 3 Review and confirm  Review settings  Confirm by selecting −“save” −“send & close” (i.e. activate for production) or  Cancel action with “discard changes”

29. SISP Expert Mode

30. February 2006SISP release 6.230 Configuration Pages Configuration information can be given (1, 2) and certain SISP actions can be performed (1). The status bar shows general SISP information (customer name, order/quote number, service type, attachments) (3) and SISP status (4). A SISP can be in different states (4): a.New - nothing shown in status line b.Saved - SISP was saved, but not sent c.Sent - SISP was sent and activated Note: First page contents (here: rack configuration) may vary depending on ordered service type and operating system. (1) (2) (4) (3)

31. February 2006SISP release 6.231 OS dependent configuration SISP supports 3 operating system platforms: HP-UX Microsoft Windows Linux Most configuration options were designed for HP-UX, basic Windows/Linux configuration exists (more to be added in future releases)

32. February 2006SISP release 6.232 Configuration Sections – Rack I Follow these steps to enter data: Select a rack type. Select ‘list’ to get a list of rackable products and populate the table. Consider top of the table as top of the rack. When done, ‘fill up’ unused slots. Only products in the list are allowed. For special products and cabling a Visio drawing can be attached. If the rack section is not filled, rack definition from the sales configurator tool (WATSON) or default racking will be used.

33. February 2006SISP release 6.233 Configuration Sections – Rack II If rack information available from sales configurator tool (WATSON): Rack type pre-selected Rack table populated with products ordered rack integrated Order of components in rack based on Watson rack layout or factory default rules No deletion or addition of components possible, just moving components up and down within the rack.

34. February 2006SISP release 6.234 Configuration Sections – Cabling Cabling information can be entered On order level, clearly separating server, storage or rack items On item level (per server) Cable type selectable from pull-down menu, all other fields free-entry text. Mandatory fields: Cable type Location (from/to) Port (from/to)

35. February 2006SISP release 6.235 Configuration Sections – Disks I Define all disks to be configured, including internal disks. Mirror target disks should be omitted. Add disk of desired type to configuration Use one entry for each disk product (internal disks, external disks, disk array, virtual array) If applicable, enter product number and description Superdome and partitionable servers: Disks are imported automatically when the SISP is opened the first time.* In most cases, all available disks on the order are present in each partition domain (PD) configuration. Define detailed layout of a certain disk only in the PD the disk is connected to. The physical device path can be selected from a pull-down menu* and needs to be completed with SCSI-ID and LUN. Changes in disk configuration will not automatically be taken into account in LVM and Mirror configuration *) If WATSON data available!

36. February 2006SISP release 6.236 Configuration Sections – Disk II Disk Arrays: Enter the quantity of modules to be joint in a logical unit Select the raid level for that unit Specify the physical device path and the volume group for the logical unit Changes in disk configuration will not automatically be taken into account in LVM and Mirror configuration

37. February 2006SISP release 6.237 Configuration Sections – Storage overview Basic RAID configuration of internal and external storage devices Complex storage (e.g. EVA5000, XP, MSA1000) cannot be configured here  use file attachment for detailed configuration Complex storage will be referenced in the high end storage section

38. February 2006SISP release 6.238 Configuration Sections – Storage I RAID configuration for a server’s internal disks: Select RAID level from storage type pull-down menu SISP will automatically create array sets for this connection in the background If desired, select “edit” to modify array set layout suggested by SISP (see slides on storage details)

39. February 2006SISP release 6.239 Configuration Sections – Storage II RAID configuration for a server’s external disks: On a storage shelf row, select server from host pull-down menu Select RAID level from storage type pull-down menu SISP will automatically create array sets for this connection in the background If desired, select “edit” to modify array set layout suggested by SISP (see slides on storage details)

40. February 2006SISP release 6.240 Configuration Sections – Storage details Access through “edit” action on overview page Displays all storage connections for one particular server as selected on overview page SISP suggests array set layout based on built-in rules Array set layout can be adjusted by user

41. February 2006SISP release 6.241 Configuration Sections – Storage details: array set creation rules Array set names reference the RAID controller they are connected to (e.g. ‘0A’ and ‘0B’: array sets A and B, respectively, on embedded controller; ‘1A’: A on first installed controller etc.) Array sets may only contain disks of the same type, i.e. of same speed and size. Starting from the embedded controller (then 1 st, 2 nd, 3 rd ), for each controller sort disks by highest quantity in descending order. If array sets have equal amounts of disks, those containing the disks with bigger size and higher speed have higher priority. The embedded controller will initially be suggested with a RAID 1 RAID level, all subsequent controllers will have RAID 5. If the array set's disk quantity is not sufficient for the intended RAID level, SISP will automatically reduce the RAID level to an appropriate value. RAID levels can be changed by the user given that enough disks are available to support the selected configuration.

42. February 2006SISP release 6.242 Configuration Sections – Windows Select from pull-down menus to assign Array set (A, B, C, …) Partition name (C, D, E, …) File system type (FAT32, NTFS) and enter sizes for partitions Legacy BCS (Integrity servers) configuration options only allow to specify Target disk Partition size

43. February 2006SISP release 6.243 Configuration Sections – Linux Select from pull-down menus to assign Array set (A, B, C, …) Additional mount points File system type and enter sizes for mount points (minimum sizes cannot be reduced further) Legacy BCS (Integrity servers) configuration options only allow to specify Target disk

44. February 2006SISP release 6.244 Configuration Sections – OS/LVM I Specify parameters for the layout of the operating system/logical volume manager. Basic functionality includes: de-select free software (HP-UX 11.00 only) defer automatic increase of logical volumes Note: If automatic increase of logical volumes is deselected, user needs to ensure that enough space is left in each logical volume for the ordered software. Selected file system (FS) will be used regardless of what has been ordered. If no FS is selected, the default (or the ordered FS) will be applied. Superdome and partitionable servers: OS will be selected automatically.* *) If WATSON data available! page continues.... (next slide)

45. February 2006SISP release 6.245 Configuration Sections – OS/LVM II Functionality includes: free names for volume groups and logical volumes selectable block size for each logical volume selection of physical device path from pull down menu (values predefined in disk configuration section) distribution of logical volumes over several disks (select ‘ALL’ in physical device path) Changes in LVM configuration will not automatically be taken into account in disk and Mirror configuration page continues.... (next slide)

46. February 2006SISP release 6.246 Configuration Sections – OS/LVM III Striping: Each volume group can be selected to be striped. The requirements/limitations are: at least two disks in the volume group “ALL” in the physical device path in LVM configuration selected SWAP, DUMP and RAW devices will not be striped number of stripes ≤ number of disks in the volume group striped vg’s cannot be mirrored Extended disk layout: maximum number of physical volumes per volume group physical extent size maximum number of physical extents Additionally, the maximum disk size needs to be entered.

47. February 2006SISP release 6.247 Configuration Sections – Mirror Disks defined on the OS/LVM page can be selected to be mirrored. ONLY disks specified on OS/LVM page are selectable for mirroring. Disks listed as ‘Source Disk’ are not allowed as ‘Mirror Disk’. If ALL was specified in the physical device path (LVM section) all disks of that volume group need to be mirrored. If DEFAULT was selected in the physical device path (LVM section) only “default mirror” can be chosen. Disks in a striped volume group cannot be mirrored. Changes in disk and LVM configuration will not automatically be taken into account in Mirror configuration

48. February 2006SISP release 6.248 Recommended fill-in sequence DisksOS/LVM Mirror Specified disks can be selected on OS/LVM page Only disks (physical device paths) defined here can be selected for mirroring Mirror settings depend on OS/LVM Changes in one configuration section will not automatically be taken into account for the other sections.

49. February 2006SISP release 6.249 Configuration Sections – Kernel Kernel parameters can be entered −in decimal format −in hexadecimal format (preceded by “0x”) −as a formula (preceded by “=“) Kernel limits and dependencies need to be checked carefully. Default values and short description of the kernel parameters can be found on the help pages.

50. February 2006SISP release 6.250 Configuration Sections – Network If a time zone is assigned a hostname needs to be entered Systems with multiple network devices: IP addresses can be assigned to each card LAN cards are identified by logical number or physical device paths. No mix of LAN numbers and device paths is allowed. Network devices are numbered (lan0, lan1 etc.) by ascending physical device path (i.e. lan0 will be assigned to the lowest physical device path). Network interface type in LAN port configuration is optional; can be used for the identification of the LAN cards, but will not be taken into account for card placement.

51. February 2006SISP release 6.251 Configuration Sections – Asset Design your standard HP asset tag 1.Select from the list of asset tag fields 2.Provide an asset tag number or number range 3.Specify tag placement Note: Asset tags will be printed on HP supplied labels. Customized tags can be ordered separately.

52. February 2006SISP release 6.252 Configuration Sections – Firmware Customize system firmware/system BIOS version 1.Select system model/server family from pull-down menu 2.Select firmware/BIOS revision from pull-down menu Note: SISP will only show valid revisions for a particular model, as using incompatible firmware might lead to undesirable results.

53. File attachments

54. February 2006SISP release 6.254 File attachments Files containing detailed instructions can be attached to SISP to be used in the manufacturing process.  Attachments page can be accessed through −“Attachments” link on the left hand navigation menu −File icon in the right hand corner of the status bar  Attachments can be made on −order level (content applies to all items on the order) −item level (content applies to a specific item only).  A scope is assigned to highlight an attachment’s purpose (e.g. rack, cabling instructions). Due to the depth of information, a questionnaire’s scope is “general”.  Optionally, comments can be entered for additional information.  The original file name is displayed in the attachments list.  Attachments will be saved with templates.

55. February 2006SISP release 6.255 File attachments – overview page Attachments referenced by file name, scope, creator/owner and attachment date/time. Files can be Uploaded from the local file system Copied from another SISP or from a template Deleted by checking the box before the file name

56. February 2006SISP release 6.256 File attachments – upload file Upload a file: 1.Select a file type 2.Browse for the file on a local or networked file system 3.Enter a comment or description (optional) 4.Select “Upload” Restrictions:  Limited number of files per scope  need to overwrite attachments if maximum reached  File type needs to be unique per scope

57. February 2006SISP release 6.257 File attachments – copy file Scope selected on overview page  Copy file from another SISP (1): 1.Enter order number or quote number 2.Select “Copy”  Copy file from template (2): 1.Select template from pull- down list (order templates or modular templates) 2.Select “Copy”  Select file(s)  Mark file(s) to be copied in results list (3)  Select “Copy” (1) (2) (3)

58. Item configuration

59. February 2006SISP release 6.259 Item vs. Order Configuration I 1.If there are several servers/racks which should be configured in different ways, item configuration needs to be used. Use separate items for racks and servers. 2.To identify the item use its item number (not the item number of the SISP product!) 3.For a quote SISP preliminary item numbers can be chosen. When the quote SISP is linked to an order number the item numbers need to be adjusted according to the order. 0100Rack1 0200Server1... 0212HP Factory Express... 0400Rack2 0500Server2... 0517HP Factory Express... 0600Server3... 0614HP Startup... ‘SO’ Order Section 001 For Superdomes and partitionable servers, all partition domains (PD’s) need to be configured as a separate “item”. The “item number” of a PD consists of the complex number and the PD number, e.g. 01-0002 for the second PD of the first Superdome or partitionable server. If sales configurator (WATSON) data are available, PD information will be imported automatically when creating a new SISP.

60. February 2006SISP release 6.260 Item vs. Order Configuration II If configuration parameters (e.g. kernel parameters) have the same values for several items, order configuration can be used to facilitate the input. The values of the filled configuration sections (in order configuration) will be used for each item unless the respective sections have been specified separately in item configuration. Superdome and partitionable servers: Some details of the Partition Domain (PD) configuration will automatically be filled in for each PD (disks and part of OS/LVM).* Disk, OS/LVM and Mirror sections for PD’s should not be specified on order configuration level. *) If WATSON data available!

61. February 2006SISP release 6.261 Configuration of items Define any additional server or rack items separately (add new server/rack item) Use item number from order (not the item of the SISP product number!) Quote SISPs: use preliminary item numbers (need to be corrected when linking the SISP to an order number) Item information will be pre-populated for some HP Factory Express orders* Any item numbers in a SISP must match the item numbers on the order. *) If WATSON data available!

62. February 2006SISP release 6.262 Difference between Rack and Server Items Rack itemServer item Can contain several server itemsDescribes only one item No configuration tabs shown (only rack configuration possible) Configuration tabs according to ordered services – EXCEPT rack tab “Reset” clears all fields in rack table“Reset” clears all fields, link to order is broken, i.e. changes in order configuration are not considered for the item “Reset to order” does not exist“Reset to order” fills all fields with order values, link to order configuration is established

63. February 2006SISP release 6.263 Order  Item Configuration I The two colors represent certain configuration sections, e.g. kernel and network All items (e.g. SPUs) will be configured in the same way. Changes in order configuration will affect all items Item specific configuration overwrites order configuration Changes in order configuration will not affect the item configuration section (link to order configuration does no longer exist, even for unfilled fields of this section) Only order configuration filled item order Item specific data in one configuration section Configuration of item specific values item order

64. February 2006SISP release 6.264 Order  Item Configuration II Example Order configuration will be used for any unfilled item specific configuration sections Item specific configuration will be used where section is filled. rackserverrackserver

65. February 2006SISP release 6.265 Item Handling I Item management options: delete items copy to other item number(s) move to other item number Move/copy will not overwrite an existing destination item (destination needs to be deleted/moved first). Destination item number needs to be specified; the item name is optional. Partitioned servers: Destination complex number (two digits) and partition domain number (four digits) need to be specified; the partition domain name is optional. Item management options will not be available for HP Factory Express orders where item information was pre-populated based on order data.

66. February 2006SISP release 6.266 Item Handling II Some HP Factory Express orders orders* will pre-populate item information/item structure based on order data: Server items Partition domains Virtual partitions Rack items Items are referenced by item number and description. Note: If item configuration pages are not filled, respective order configuration will be applied (see order - item configuration details). *) If WATSON data available!

67. Review, change report, and Status Quo

68. February 2006SISP release 6.268 Review Function Review: summary of which sections are filled on order and item level can be selected −from Main Page: show last saved/sent configuration −during configuration: show current state, including changes shows the configuration information in detail will be sent to the SISP creator if the SISP is sent or updated will be shipped with the system

69. February 2006SISP release 6.269 Change Report displayed from Main Page menu compares current order/quote data (sales configurator) and SISP data SISP section shows −all partition domains (PD’s) defined, incl. OS and boot device paths assigned −device paths used in SISP but not available in sales configurator (WATSON) data sales configurator section shows −all partition domains (PD’s) defined, incl. OS and boot device paths assigned −available disk devices sent to SISP creator if order is changed or if an order number is assigned to a quote Differences between SISP and sales configurator data need to be corrected manually!

70. Templates

71. February 2006SISP release 6.271 Templates Provide easy storage of and access to frequently used configurations Facilitate the creation of SISPs with similar layout Template types: −SISP Template: Order specific; contains all configuration information entered in the configuration tabs on order and item level, including attachments −Modular Template: Not order specific; contains configuration parameters stored for a single configuration tab −Super Template (new): Set of modular templates linked together Template archives: −user’s personal template archive −general templates (“HP Best Practice”): contain HP recommended values managed by HP template administrators; visible to all users Any files attached to a template carrying order number specific information should be updated before activating the SISP.

72. February 2006SISP release 6.272 Template creation SISP Template: save a complete SISP as template  by selecting “Save as Template” from the left hand navigation menu Modular Template: save the parameters for a specific configuration tab  by selecting “Save as modular template” from the respective page  by creating the template from scratch on the “template management” page Super Template: link modular templates together  by creating the template on the “template management” page

73. February 2006SISP release 6.273 Using templates Manual template selection – SISP Express  Select a super template and assign all Customer Intent data with a single click Manual template selection – SISP Expert Mode −SISP Template (entire SISP)  Select “Copy from template” in the navigation menu and check a template out of the result list. −Modular/Super Template  Use “Assign Template” to assign modular/super templates to specific configuration tabs on order or item level. Automatic template selection −Create SISP automatically based on predefined criteria (service product number, feature code) and pre-select modular templates  Service product number and feature code must be setup  Modular template needs to be associated to product number and feature code  Modular template needs to be flagged as “automatic” by a template administrator

74. February 2006SISP release 6.274 Modular templates – Concept Store configuration information of a specific configuration tab  Configuration Template:stores parameters entered on a specific configuration tab Can be associated to additional information in an attached document  Attachment Only Template:uses file attachment to store customer intent information (e.g. rack drawing) Creation of modular templates −Based on the current SISP by saving the current configuration tab into a template −From scratch by entering the configuration information on the configuration page and/or attaching a document with information −By copying an existing template (own or from other users) −By copying a Super Template from another user: modular user templates are automatically copied into own template archive Modular Templates can be shared within pre-defined user groups −Grant access to other users to use, copy, modify or delete your templates

75. February 2006SISP release 6.275 user group 1user group 2 enter your templates user store your templates in the database grant access to group 2 only grant access to all groups grant access to group 1 only Modular templates – User Concept Store your preferred configuration data in a template Share your templates with other users Use your templates to easily define your configuration for a given order Use your templates to automatically create the configuration of a given order  allow template to be used for automatic pre-population

76. February 2006SISP release 6.276 Modular templates: Identifiers Name (mandatory): Give your template a name you can easily remember. Note: Different template modules (e.g. scope rack, cabling) can use the same name. Module (mandatory): Configuration tab/scope this template belongs to, e.g. network. Product No + #(Option) (optional): Additional parameters. Can be used in the “Search” functionality. Mandatory entry if a template shall be used for “automatic” SISP creation. The final activation of a template for automatic use can only be performed by a template administrator. Comment (optional): Recommended to provide more information about the content as name field is limited. Give access to (optional): By default access to a template is limited to the creator, but you can grant access to other members of a group you belong to, or to all your groups User Groups are set up by a SISP adminstrator upon request.

77. February 2006SISP release 6.277 Super templates – Concept I Link modular templates together Allow for fast assignment of a set of configuration information (set of modular templates) with a single click Creation of super templates −From scratch by linking modular templates to the super template −By copying an existing template (own or from other users) Super templates can be shared within pre-defined user groups −Grant access to other users to use, copy, modify or delete your templates Notes: −A user can only link his/her own modular templates to a super template; other users’ modules need to be copied. −Only one modular template per scope allowed (e.g. 1 rack, 1 cabling etc). −Super templates only reference data; configuration information still needs to be modified in module itself

78. February 2006SISP release 6.278 create your template Super templates – Concept II Start creating a new super template or modify an existing one Use your super template to define your configuration for a given order with “one click” Link modular templates to the super template Modular Templates own templates other users’ templates “Best Practice” copy template Super Template Asset Kernel LVM other scope

79. February 2006SISP release 6.279 Super templates: Identifiers Name (mandatory): Give your template a name you can easily remember. Note: A super template can use the same name as a modular template. Product No + #(Option) (optional): Additional parameters. Can be used in the “Search” functionality. Comment (optional): Recommended to provide more information about the content as name field is limited. Give access to (optional): By default access to a template is limited to the creator, but you can grant access to other members of a group you belong to, or to all your groups. User Groups are set up by a SISP adminstrator upon request.

80. February 2006SISP release 6.280 Template management Search parameters – modular templates Name Search for template name; wildcard (*) allowed Product No + Option Search for product number/option; wildcard (*) allowed Dates Search for templates created or modified in a specific date range Automatic Pre-Population Search for templates flagged for automatic SISP creation Modules Search for all modules or selected scopes Owner −HP Best Practice: include general templates with HP recommended values −my templates: search your templates only −my group: search your templates and those of your groups for which you were granted access −other user (feature for internal users only): enter the login name of a user to search his/her templates

81. February 2006SISP release 6.281 Template Management Search results – modular templates Two sections in results list: −HP Best Practice: templates with HP recommended values −User defined templates: templates belonging to SISP users Available actions: −Review: show template content −Modify*: change template identifiers and/or configuration parameters −Delete*: remove template from the repository −Copy: create a copy *) user defined templates only

82. February 2006SISP release 6.282 Template management Search parameters – super templates Name Search for template name; wildcard (*) allowed Product No + Option Search for product number/option; wildcard (*) allowed Dates Search for templates created or modified in a specific date range Owner −HP Best Practice: include general templates with HP recommended values −my templates: search your templates only −my group: search your templates and those of your groups for which you were granted access −other user (feature for internal users only): enter the login name of a user to search his/her templates

83. February 2006SISP release 6.283 Template Management Search results – Super Templates Two sections in results list: −HP Best Practice: templates with HP recommended values −User defined templates: templates belonging to SISP users Available actions: −Review: show template content −Modify*: change template identifiers and/or configuration parameters −Delete*: remove template from the repository −Copy: create a copy *) user defined templates only

84. February 2006SISP release 6.284 Template Assignment SISP template Select “Copy from Template” from left hand navigation menu Select template out of the results list −Section 1: HP general templates −Section 2: User defined templates Press “Proceed” and enter order number or quote number to copy template content to the order. Note: It might be necessary to adjust your SISP to the order structure

85. February 2006SISP release 6.285 Template Assignment Main page  Open SISP by selecting “New/Open” from the left hand navigation menu  Go to “SISP Expert Mode” (1) and select “Template Assignment” (2)  On the Start page (3) select those SISP items to be assigned templates  Select “Assign Super Template” to assign a set of modular templates linked together into a super template  Select “Assign Modular Template” to assign individual modular templates to the SISP Note: The next page will be displayed based on the template type. It is possible to switch between “Assign Super Template” and “Assign modular template. (1) (2) (3)

86. February 2006SISP release 6.286 Template Assignment Super templates I The “Super Template Assignment” page shows a summary of all possible configuration tabs on order and item level based on order content 1.Define search parameters and retrieve the templates from the template archive by selecting “Populate Pull- Down Menus” (menus are already populated with “HP Best Practice” and user templates) 2.Select templates as necessary Redo steps 1 and 2 for different search parameters

87. February 2006SISP release 6.287 Template Assignment Super templates II The overview shows whether the configuration −is still not specified yet  empty or “attachment only scope” −has been entered manually  manually filled −is based on a template  template name and owner Using the checkboxes for each module you can −Reset data if no modular template linked to this scope −Keep the assigned modular template −Select the linked modular template Manually filled modules will be changed when a template is assigned.

88. February 2006SISP release 6.288 Template Assignment Super templates III If a modular template was removed from the repository but is still referenced by a super template the data stored with the related scope will be reset. “Reset All” will clear any template content from the SISP; manually filled data will be kept. “Apply Selection” will copy the data into the corresponding configuration pages Special note on rack templates: The content of the rack tab will be overwritten by the content of a rack template.

89. February 2006SISP release 6.289 Template Assignment Modular templates I The “Manual Template Assignment” page shows a summary of all possible configuration tabs on order and item level based on order content 1.Define search parameters and retrieve the templates from the template archive by selecting “Populate Pull- Down Menus” 2.Select templates as necessary and apply them with “Use Selected Templates in SISP” Redo steps 1 and 2 for different search parameters Note: Selections will be applied to the SISP on leaving the page or starting a new action on the navigation menu.

90. February 2006SISP release 6.290 Template Assignment Modular templates II  The overview shows whether the configuration is not specified yet  empty has been entered manually  manually filled is based on a template  template name and owner  For each configuration scope you can remove the template  select “none” keep the assigned template,  select “keep assigned template” assign a template  select from the pull down menu  “Reset All” will clear any template content from the SISP  Manually filled configuration scopes will be changed when a template is assigned.

91. Superdome and partitionable servers – specific features

92. February 2006SISP release 6.292 Superdome and partitionable servers Features, Differences The sales configurator tool (WATSON) delivers basic configuration information which will be imported into the SISP tool. This results in: pre-definition of partition domain items* pre-definition of disk devices and corresponding hardware paths* selection menu for physical device paths (I/O card placement)* automatic information about order changes (help to avoid mismatch between order and configuration) *) if sales configurator data available Note: The SISP configuration will not change automatically after an order change!

93. February 2006SISP release 6.293 Superdome and partitionable servers Features, Differences Rules for entering a SISP for Superdome and partitionable servers: Wait for WATSON data! (avoid start from scratch, copy, move...) Superdome quote numbers imported from sales configurator should be entered in capital letters and without dash (US20001000 instead of us2-00010-00) SISP needs to be checked for necessary changes every time the order changes. All changes need to be done manually (no automatic SISP update). The change report can be used to find the differences between order and SISP. Any additional server items in a quote only have a preliminary item number. This item number needs to be set to the correct value when the quote becomes an order. If device paths are entered manually, they will be marked with a red frame if they are not in the respective selection lists. This red frame will only go away if a device path from the list is entered/selected and an action has taken place (i.e. go to another configuration page and back). Note: The red frame is NOT an error in the application.

94. February 2006SISP release 6.294 WATSON – SISP information flow Rev 1 Rev 2 Rev 3 Rev 4 Rev 5 Rev 6 Rev 1 (reference 3) Rev 2 (reference 4) Rev 2 (reference 4) Rev 3 (reference 5) Rev 3 (reference 5) Rev 4 (reference 6) Rev 4 (reference 6) config files config files config files config files Sales configurator (xml files) SISP (xml files) Factory scripts Quote created (no order number) Order placed (order number) import (automatically) change report (sync manually) change report (sync manually) change report (sync manually) save link (manually)

95. February 2006SISP release 6.295 Configuration tools order information Visio drawing SIP other documents... configuration information basic configuration information order status trigger SISP input order information PLATO SISP Sales configurator Manufacturing OMS Production systems (SAP)

96. February 2006SISP release 6.296 Where to find more information SISP tool web sites http://www.sisp.hp.comhttp://www.sisp.hp.com (external users) http://sisp.bbn.hp.comhttp://sisp.bbn.hp.com (internal users)

97. Appendix

98. LVM details

99. February 2006SISP release 6.299 Physical device paths Example for the use of ‘ALL’ Using separate device paths lvol3 cannot be spread over two disks. Only one device path allowed per logical volume. Using “All” in device path lvol3 can be spread over two disks. Both disks are defined in disk configuration section and ‘ALL’ is used in physical device path for vg01. Logical volumes will be arranged automatically. Disk space wasted lvol3 lvol2 lvol1 vg01 disk2 disk1 lvol3 lvol2 lvol1 lvol3 No disk space wasted vg01 disk2 disk1

100. February 2006SISP release 6.2100 Volume group parameters A volume group can consist of up to max_physical_vols disks (physical volumes). The physical volumes (disks) are split into physical extents. The physical extent size (physical_ext_size) is the same value for all disks within one volume group. The maximum number of physical extents (max_physical_ext) must be such that all disks can be totally covered with physical extents (e.g. 12 in the example). This means physical_ext_size * max_physical_ext ≥ max_disk_size, where max_disk_size is the maximum size of a disk to be included in that volume group. disk 1 e.g. 30Mb disk 2 e.g. 48Mb vg00 Physical extent, e.g. 4 Mb 1234567 123456789101112

101. February 2006SISP release 6.2101 Volume group parameters – limits max_physical_vols:1…255 physical_ext_size:1…256, power of 2 max_physical_ext:1…65535 max_physical_ext * physical_ext_size ≥ max_disk_size Layout of a ‘normal’ physical volume (not a bootable disk) Every physical extent is mapped into the VGRA area. The VGRA size is fixed, so for large disks and a small physical extent size not all physical extents can be mapped. In this case the physical extent size has to be increased. If a large physical extent size is selected, disk and memory space could be wasted for small disks within the volume group. PVRA Physical Volume Reserved Area VGRA Volume Group Reserved Area User Data Area Bad Block Pool

102. Template details

103. February 2006SISP release 6.2103 Template Management Review modular template Review opens a new window with a summary of the template: −Template identifiers −Template configuration −Template history (see SISP review)

104. February 2006SISP release 6.2104 Template Management Review super template Review opens a new window with a summary of the template: −Template identifiers −Template configuration ( list of linked modular templates) −Content information for each linked modular template −Template history (see SISP review)

105. February 2006SISP release 6.2105 Template creation Complete SISP Create a SISP Template 1.Open SISP or use your current SISP 2.Enter or modify configuration parameters as required 3.Select “Save as template” from left hand navigation menu 4.Enter name for template 5.Select “Proceed” to save the template Note: no blanks allowed in template name

106. February 2006SISP release 6.2106 Template creation Modular template I Create a modular template from an existing SISP 1.Open SISP or use your current SISP 2.Enter or modify configuration parameters as required 3.Select “Save as template” on the configuration page 4.Enter template identifiers (required: Name) 5.Select “Save” to save your template and return to the last configuration page

107. February 2006SISP release 6.2107 Template creation Modular template II Create a modular template from scratch 1.Select “Create modular template” from left hand navigation menu 2.Enter template identifiers and select a configuration tab (“module”) from the pull-down menu 3.Select “Content” to open the respective configuration screen 4.Enter configuration parameters as required 5.Select “Save & Close” on the navigation menu

108. February 2006SISP release 6.2108 Template creation Modular template – attachments Attach a file to a modular template 1.Select “Attachments” from the navigation panel or get directly to the attachments page for “attachment only” templates 2.Upload the file from a local or networked file system 3.Select “Save & Close” from the navigation menu

109. February 2006SISP release 6.2109 Template creation Super template I Create a super template 1.Select “Create super template” from left hand navigation menu 2.Enter template identifiers and select “Content” to edit the super template 3.Select modular templates to be linked to the super template Notes: Pull-down menus are already pre-set with “HP Best Practice” and “User Templates” Refine content of the pull-down menus using different filter criteria (next page)

110. February 2006SISP release 6.2110 Template creation Super template II Refine menu content 1.“Assign Selected Modules” to link the modular templates to the super template 2.Refine your search and link additional modular templates as necessary 3.Press “Save Super Template” to store the super template in the database (1) (3) (2)

111. February 2006SISP release 6.2111 Template Management Copy modular template Copy template from another user:  Make an exact copy  optionally change template name and/or content Note: access defaults to “myself” Copy template out of your template archive:  New template name required

112. February 2006SISP release 6.2112 Template Management Modify modular template Allows modification of −Product No and Option value −Access rights −Comment text −Configuration parameters (select “Content”) If template is flagged for automatic pre-population of SISPs, a user cannot change parameters before removing the automatic flag.

113. February 2006SISP release 6.2113 Template Management Delete template Modular/Super templates −Select “delete” for entry in search results list −Note: Due to the group concept, users may delete templates of their groups, even if they do not own them! SISP Templates: −Select “Delete Template” from the left hand navigation menu −Check the templates to be deleted out of the result list