Cloud Cruiser became HPE Consumption Analytics on Nov. 1, 2018. You'll still see the old name in places while we update this site.

 

 

Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 for HPE GreenLake Flex Capacity > Working in Cloud Cruiser > Onboarding FC customers > Configuring lookup tables

Configuring lookup tables

Lookup tables store data used by workbooks. They allow workbooks to be data-driven, which means that the result produced by a workbook can change without requiring you to make changes to the workbook itself.

Cloud Cruiser includes the 00000_Customer2AccountID table to map the customer IDs you define to account IDs defined in the Cloud Cruiser account structure. You must configure a row in that table for each FC customer.

Optionally, you have the option to report by location, report by tier, or report by both location and tier. The FC Customer Template workbook defaults most services to report by location, and 3PAR to also report by tier. Generally, you won't need to set up a lookup table to report by location unless the customer has a non-standard way of identifying location. You might also need to customize the way equipment is mapped to tiers, such as for individual blades. Examples of these customized lookup tables are specified in the Creating customer-specific lookup tables section below.

Naming conventions

Global tables (such as 00000_Customer2AccountID), which are used by all batch jobs, should be prefaced by 00000 so they will appear at the top of the list of tables.

Be aware that modifying global tables affects many workbooks.

All customer specific table names should be prefaced by the customer ID you selected for the customer. For example, 00008_AceRunTable. In these customer-specific tables you can perform various translation actions that apply only to one customer.

Configuring the 00000_Customer2AccountID table

The 00000_Customer2AccountID table defines the relationship between a customer ID and the Cloud Cruiser account ID.

Before you begin

Before you begin this procedure, you must know the full path in the account structure for the customer. You will create that account in a later procedure, but you must know what that path will be before starting this procedure. For more information about customers and the account structure, see Creating customers.

Do not create multiple revisions for this table, there should only be one revision with a date range of 01/01/2000 - 12/31/2999.

To configure the 00000_Customer2AccountID lookup table for a customer

  1. Click Data > Setup > Lookup Tables.
  2. In the list of tables, select 00000_Customer2AccountID.
    The table opens in the display pane.
    lookupTable1.jpg
  3. Find the row in the table that has the customer alias that is immediately before the customer alias you are entering (when sorted). The customer alias is the part of the usage filename in the email attachment that identifies the customer (highlighted in bold in the following examples). .For example,
    3PARreport_AceRun_172.16.142.60_201505041543.txt.enc
    or
    3PARreport_HP-EMEA-999-DEU-00021_1650383_201505020230.txt.enc
    This table should be kept in sorted order to make it easier to find customer entries.  The only exception to this is when a customer alias exactly matches the beginning of another customer alias, i.e. ALCATEL-LUCENT and ALCATEL-LUCENT-OSIRIS.  In this case, the shorter customer alias needs to follow the longer one, to prevent lookups for the longer customer alias from matching the shorter one.
  4. Click Add Row.
    A new, empty row is added to the table.
  5. In the Low ID column, enter the customer alias.
  6. In the Target ID column, enter the account ID path for the customer as a pipe-separated list. For example, HP|EMEA|999|DEU|00021.
  7. Drag the new row into the correct order so the table is alphabetic by Low ID.
    lookupTable2.jpg
  8. Click Save to save your changes to the table.

Creating customer-specific lookup tables

When onboarding customers, you have the option to report by location, report by tier, or report by both location and tier. You might also need to exclude equipment that was previously used but has been deprecated. The FC Customer Template workbook defaults most services to report by location, and 3PAR to also report by tier. It also provides a placeholder step called Exclude Equipment that can be enabled to ignore equipment. The following table shows the default fields that provide location and tier for each service. (Empty cells indicate that there is no default field for location or tier for that service):

Service Location Tier
3PAR DeviceID Type-Capacity
Azure    
Blades DeviceID  
Bulk DL Servers DeviceID  
P2000 DeviceName  
PerCoreUtil DeviceID  
PerHostVM DeviceID  
SAN DeviceID  
SDS LeftHand Storage DeviceID  
StoreOnce HostName  
VMs Datacenter  
XP7 Serial#-PoolID  


DeviceID can be an IP address, host name, or some other identifier for a device.  DeviceID is the most common dimension used as the Low ID in lookup tables, but you can also user other dimensions such as Serial Number or HostName.

As an optional procedure, you can create new, customer-specific lookup tables to set locations and tiers, or to exclude equipment. Do this only if the default behavior doesn't work for the customer. For example, you might have two or more DeviceIDs that are considered to be the same location, or blades might need to be in different tiers based on their serial numbers. To handle these scenarios you would create customer specific lookup tables, as shown in the following procedures. Note that equipment that is being excluded does not need to be added to the customized location or tier lookup tables.


Lookup tables should be named based on what field is being used for the lookup and what value is the result of a lookup.  Also, lookup tables should start with the customer ID to easily identify which tables are associated with which customers.  Here are some examples (NNNNN would be replaced with the customer ID):

NNNNN_Blade2Location

NNNNN_Blade2Tier

NNNNN_ExcludedBlades

NNNNN_Server2Location

NNNNN_Server2Tier

NNNNN_ExcludedServers

NNNNN_HostName2Location

NNNNN_HostName2Tier

NNNNN_ExcludedHostNames

This is not a complete list, but should serve as examples of commonly used lookup table names.  Note that the lookup table name must match the name of the table in the customer workbook.

To create customer-specific lookup tables to map 2 DeviceIDs to the same location

  1. Click Data > Setup > Lookup Tables.
  2. Create a table to map blades to locations:
    1. In the list of tables, right-click and select Add New Lookup Table.
      The Create New Lookup Table dialog box appears.
    2. In the Name field, enter a name for the table, prefaced with the customer ID to which this table applies.
      For example, to create a table to assign blades by location to AceRun (which has a customer ID of 00021), enter 00021_DeviceID2Location.
    3. Optionally, enter a Description for the table.
    4. Click OK.
    5. The new table is added to the display pane.
    6. Click the plus sign to the right of the Effective Dates field to add a starting date for the table lookup.
      By default, the end date is set as December 31, 2999.
    7. Click Add Row to add the first row.
    8. In the Low ID column, enter a DeviceID, such as 01.01.01.33.
    9. In the Target ID column, enter the location, such as LOC_A.
    10. Repeat for each DeviceID.
    11. Click Save to save the table.
  3. Update the customer workbook to use the new lookup table:
    1. Click Data > Workbooks.
    2. Select the sheet in the customer workbook that uses the customized location value (_3PAR, Blades, and so on).
    3. Click on the arrow to open the Set Location step.
    4. Right-click on the first processor SetDimensionFromDimension and disable it.
    5. Right-click on the second processor SetDimensionFromLookup and enable it.
    6. Double-click on the second processor SetDimensionFromLookup.
    7. The Edit Processor dialog box appears.
    8. In the Lookup Table field, select the new lookup table name (such as 00021_DeviceID2Location) and then click OK. (This replaces the default lookup table name NNNNN_DeviceID2Location.)
    9. Click the Save button to save the changes to the workbook.

To create customer-specific lookup tables to map blade serial numbers to different tiers

  1. Click Data > Setup > Lookup Tables.
  2. Create a table to map blade serial numbers to tiers:
    1. In the list of tables, right-click and select Add New Lookup Table.
      The Create New Lookup Table dialog box appears.
    2. In the Name field, enter a name for the table, prefaced with the customer ID to which this table applies.
      For example, 00021_Blade2Tier.
    3. Optionally, enter a Description for the table.
    4. Click OK.
    5. The new table is added to the display pane.
    6. Click the plus sign to the right of the Effective Dates field to add a starting date for the table lookup.
      By default, the end date is set as December 31, 2999.
    7. Click Add Row to add the first row.
    8. In the Low ID column, enter a blade serial number, such as SGH00001AAA.
    9. In the Target ID column, enter the tier, such as Tier 1.
    10. Add new rows for each serial number to tier mapping.
    11. Click Save to save the table.
  3. Update the customer-specific workbook to use the new lookup tables:
    1. Click Data > Workbooks.
    2. Open your customer-specific workbook.
    3. Click the Blades sheet tab, click the arrow in the Set Tier step to expand the step.
    4. Right click on the SetDimensionFromLookup processor and enable it.
    5. Double-click the SetDimensionFromLookup processor.
      The Edit Processor dialog box appears.
    6. In the Lookup Table field, select the new lookup table name (such as 00021_Blade2Tier) and then click OK. (This replaces the default lookup table name NNNNN_Blade2Tier.)
    7. Click the Save button to save the changes to the workbook.

To create customer-specific lookup tables to exclude equipment

  1. Click Data > Setup > Lookup Tables.
  2. Create a table to list DeviceIDsSerialNumbers, or HostNames to exclude from processing:
    1. In the list of tables, right-click and select Add New Lookup Table.
      The Create New Lookup Table dialog box appears.
    2. In the Name field, enter a name for the table, prefaced with the customer ID to which this table applies.
      For example, to create a table to exclude a 3PAR array from AceRun (which has a customer ID of 00021), enter 00021_Excluded.
    3. Optionally, enter a Description for the table.
    4. Click OK.
    5. The new table is added to the display pane.
    6. Click the plus sign to the right of the Effective Dates field to add a starting date for the table lookup.
      By default, the end date is set as December 31, 2999.
    7. Click Add Row to add the first row.
    8. In the Low ID column, enter a DeviceID, SerialNumber, or HostName, such as 01.01.01.33.
    9. In the Target ID column, enter the value DELETE_ME
    10. Repeat for each DeviceID, SerialNumber, or HostName.
      Lookup_8.PNG
    11. Click Save to save the table.
  3. Update the customer workbook to use the new lookup table:
    1. Click Data > Workbooks.
    2. Select the sheet in the customer workbook that has equipment that needs to be excluded.
    3. Click on the arrow to open the Exclude Equipment step.
    4. Right-click on the processor DeleteRow() and enable it.
    5. Double-click on the processor DeleteRow().
    6. The Edit Processor dialog box appears.
    7. Toggle Show Condition to YES.
    8. In the Lookup Table field, select the new lookup table name (such as 00021_Excluded) and then click OK. (This replaces the default lookup table name NNNNN_Excluded.)
    9. Click the Save button to save the changes to the workbook.

To create customer-specific lookup tables to exclude or include 3PAR equipment by Cage Position

This is basically the same process as described in the previous section, but is specific to 3PAR.  To exclude or include equipment by Cage Position, use the previous section with the following changes:

  1. If excluding equipment by Cage Position, create a lookup table as described in steps 1 and 2 of the previous section, except that in step 2h the Low ID will be a combination of DeviceID and CagePos, separated by a pipe, i.e. 10.0.0.1|0:1:2.  You will also enable processor 3 in step 3 below.
  2. If including equipment by Cage Position, create a lookup table as described in steps 1 and 2 of the previous section (but name it NNNNN_IncludedCagePos), and step 2h the Low ID will be a combination of DeviceID and CagePos, separated by a pipe, i.e. 10.0.0.1|0:1:2.  However, in this case, you will only be entering Cage Position IDs for the the equipment you want to include, and all other equipment will be excluded.  You will also enable processor 4 in step 3 below.
  3. Update the customer workbook as described in step 3 of the previous section, except that you can only apply this to the 3PAR sheet in a customer workbook (step 3b), and in step 3d you will be enabling processors 2 and 5.  You will also enable either processor 3 or processor 4 based on whether excluding or including equipment (see steps 1 and 2).

  4.  

Note: When creating the lookup table for including or excluding Cage Positions, the format of the Cage Position values should not have leading zeroes (i.e. 0:1:2, not 00:01:02).  There are no leading zeroes in the raw usage file, however, if you use Excel to create a CSV file to import into the lookup table, Excel may add leading zeroes to the Cage Positions because it assumes the values are times (HH:MM:SS).  You should change the format of the Cage Position column from General to Text to avoid this issue.

Last modified

Tags

Classifications

This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP