Page tree
Skip to end of metadata
Go to start of metadata

This topic describes how to configure and use the BMC - TrueSight Capacity Optimization Gateway VIS files parser. This ETL loads daily performance and configuration data from a running Capacity Optimization Gateway Server instance. It can also be used for loading recovery data from a running Capacity Optimization Gateway VIS files parser server instance.

Note

You can automatically create BMC - TrueSight Capacity Optimization Gateway VIS files parser(s) from Gateway Manager. Select the Auto create ETLs to populate data from this gateway server option when you add a Gateway Server. For more information, see Adding a gateway server.

This topic contains the following sections:

To integrate TrueSight Capacity Optimization using VIS files parser

Note

If your imported data includes workloads, you can optionally activate the hierarchy rule to create aggregated workloads. For more information, see Activating the CO Aggregated Workloads hierarchy in BMC TrueSight Capacity Optimization.

Integration steps

To integrate TrueSight Capacity Optimization with the Gateway Server File Parser, perform the following task:

  1. Navigate to Administration > ETL & SYSTEM TASKS > ETL tasks.

  2. In the ETL tasks page, click Add > Add ETL under the Last run tab.

  3. In the Add ETL page, set values for the following properties under each expandable tab.

    Note

    Basic properties are displayed by default in the Add ETL page. These are the most common properties that you can set for an ETL, and it is acceptable to leave the default selections for each as is.

    Basic properties

    Property Description
    Run configuration
    ETL task name By default, this field is populated based on the selected ETL module. You can specify a different name for the ETL Task. Duplicate names are allowed.
    Run configuration name Default name is already filled out for you. This field is used to differentiate different configurations you can specify for the ETL task. You can then run the ETL task based on it.
    Deploy status You can select Production or Test to mark the ETL tasks. For example, you can start by marking the task as Test and change it to Production after you have seen that you are getting what you wanted.
    Description (Optional) Enter a brief description for this ETL.
    Log level Select how detailed you want the ETL log to be. The log includes Error, Warning and Info type of log information.
    • 1 - Light: Add bare minimum activity logs to the log file.
    • 5 - Medium: Add medium-detailed activity logs to the log file.
    • 10 - Verbose: Add detailed activity logs to the log file. Info,

    Note: Log levels 5 and 10 are typically used for debugging or troubleshooting ETL issues. Using a log level of 5 is general practice, however, you may choose level 10 to get a high level of detail while troubleshooting.

    Execute in simulation mode Select Yes if you want to to validate the connectivity between the ETL engine and the target, and to ensure that the ETL does not have any other configuration issues.
    When set to Yes, the ETL will not store actual data into the data warehouse. This option is useful while testing a new ETL task.
    Module selection

    Ensure that the Based on datasource option is selected.

    Note

    If you select Based on Open ETL template, TrueSight Capacity Optimization is integrated with a Generic extractor based on the selected Open ETL template. For more information, see  Generic ETL based on a template.

    ETL module (BMC recommends you to make this selection first) Select BMC - TrueSight Capacity Optimization Gateway VIS files parser.
    Module description A link in the user interface that points you to technical documentation for this ETL.
    Platform Select the appropriate option.
    If you select a platform, the Object relationships tab appears.
    Data type Select the appropriate data type.
    Import HMC data This option is only available if you select AIX Power VM/WPAR platform. By default, yes is selected. If you do not want to import HMC data, select no.
    Entity catalog
    Sharing status Select any one:
    • Shared entity catalog: Select this option if, for the same entities, data is coming from multiple sources. For example, BPA ETL.
      • Sharing with Entity Catalog: Select an entity catalog from the drop-down list.
    • Private entity catalog: Select this option if, for the same entity, data is coming from a single source.
    Object relationships (displayed if you select a platform)
    Associate new entities to

    Specify the domain where you want to add the entities created by the ETL. You can select an existing domain or create a new one.

    Additional Information

    By default, a new domain is created for each ETL, with the same name of the extractor module. As the ETL is created, a new hierarchy rule with the same name of the ETL task is automatically created, with an active status; if you update the ETL specifying a different domain, the hierarchy rule will be updated automatically. The hierarchy rule will be created with status ACTIVE.

    Select any one of the following options:

    • New domain: Create a new domain. Specify the following properties under New domain:
      • Parent: Select a parent domain for your new domain from the domain selector control.
      • Name: Specify a name for your new domain.
    • Existing domain: Select an existing domain. Make a selection for the following property:
      • Domain: Select an existing domain from the domain selector control.

    If the domain is already used by any other hierarchy rule, a Domain conflict option is displayed. You can select one of the following solutions:

      • Enrich domain tree: Create a new independent hierarchy rule to add a new set of entities and/or relations not defined by other ETLs (for example this ETL is managing storage while others are managing servers)
      • ETL Migration: This configuration is recommended if new ETL manages same set of entities and/or relations (already defined in current domain tree). Typical use case is the migration from one or more ETLs to a new ETL instance. It will stop all relations imported by ETL instances and restore only valid relations after first run; this configuration reuses existing hierarchy rule to correctly manage relation updates
        • Select a Hierarchy Rule to be used for current ETL from among the rules that are populating the selected domain.
          Additional information of the ETL using the selected rule is also displayed.

    Vis parser configuration
    Extractor mode Select any one:
    • via gateway service: Extract the Vis parser through gateway service.
      • Gateway Server: Select any of the Gateway Server from the drop-down list.
      • Manager run list: Specify the manager run. You can separate the manager run by ";". For example, vcenter.msf; Test.msf; vcenter5.1.msf; Test1.msf.
    • via file
    File location (applicable only for via file option)
    File location Select any one of the following methods to retrieve the CSV file:
    • Local directory: Specify a path on your local machine where the CSV file resides.
    • Windows share: Specify the Windows share path where the CSV file resides.
    • FTP: Specify the FTP path where the CSV file resides.
    • SCP: Specify the SCP path where the CSV file resides.
    • SFTP: Specify the SFTP path where the CSV file resides.
    Directory Path of the directory that contains the CSV file.
    File list pattern A regular expression that defines which data files should be read. The default value is (?$<$!done)\$, which tells the ETL to read every file whose name does not end with the string "done". For example, my_file_source.done.
    Recurse into subdirs? Select Yes or No. When set to Yes, BMC TrueSight Capacity Optimization also inspects the subdirectories of the target directories.
    After parse operation Choose what to do after the CSV file has been imported. The available options are:
    • Do nothing: Do nothing after import.
    • Append suffix to parsed file: Append a suffix you add here to the imported CSV file. For example, _done or _impoted, and so on.
    • Archive parsed file in directory: Archive the parsed file in the specified directory.
      • Archive directory (local): Default archive directory path is filled out for you. For example, %BASE/../repository/imprepository
      • Compress archived files: Select Yes or No.
    • Archive bad files in directory: Archive erroneous files in the specified directory.
      • Archive directory (local): Default archive directory path is filled out for you. For example, %BASE/../repository/imprepository
      • Compress archived files: Select Yes or No.

    Note

    You can configure automatic cleaning of parsed files using the Filesystem cleaner task. For more information, see Configuring the FileSystem Cleaner task.

    Parsed files suffix The suffix that will be appended parsed files; default is .done.
    Remote host (Applies to FTP, SFTP, SCP) Enter the name or address of the remote host to connect to.
    Username (Applies to Windows share, FTP, SFTP, SCP) Enter the username to connect to the file location server.
    Password required (Applies to Windows share, FTP, SFTP, SCP) Select Yes or No.
    Password (Applies to Windows share, FTP, SFTP, SCP) Enter a password to connect to the file location server. Applicable if you selected Yes for Password required.
    ETL task properties
    Task group Select a task group to classify this ETL into. it is not necessary to group it into a task group.
    Running on scheduler Select the scheduler you want to run the ETL on.
    Maximum execution time before warning The number of hours, minutes or days to execute the ETL for before generating warnings or alerts, if any.
    Frequency Select the frequency for ETL execution. Available options are:
    • Predefined: Select a Predefined frequency from Each DayEach Week orEach Month.
    • Custom: Enter a Custom frequency (time interval) as the number of minutes, hours, days or weeks to run the ETL in.
    Start timestamp: hour\minute (Applies to Predefined frequency) The HH:MM start timestamp to add to the ETL execution running on a Predefined frequency.
    Custom start timestamp Select a YYYY-MM-DD HH:MM timestamp to add to the ETL execution running on a Custom frequency.

    Note

    To view or configure Advanced properties, click Advanced. You do not need to set or modify these properties unless you want to change the way the ETL works. These properties are for advanced users and scenarios only.

    Advanced properties

    Property Description
    Run configuration
    Datasets

    Enables you to select or deselect metric groups for which data will be populated Available datasets. The OpenStack connector allows you to choose only from the given list of datasets, and you cannot include additional datasets to the run configuration of the ETL.

    1. Click Edit.
    2. Select one (click) or more (shift+click) datasets that you want to exclude from Available datasets and click >> to move them to Selected datasets.
    3. Click Apply.
    4.x compatibility Select any one:
    • Do not Import Virtual Machine metrics at Host level, but only at VM level 
    • Import Virtual Machine metrics at Host level [BYGM, BYZN, BYLP] to ensure compatibility of 4.x reports.
    Enable platform filtering Select any one:
    • Yes: Select Yes to enable the platform filtering.
    • No: Select No to disable the platform filtering
    Default last counter Set the default last counter in dd/mm/yyy hh:mm:ss format.
    Collection level
    Metric profile selection

    Select any one:

    • Use Global metric profile: Select this to use an out-of-the-box global profile, that is available on the Adding and modifying metric profiles page. By default, all ETL modules use this profile.
    • Select a custom metric profile: Any metric profiles you add in the Add metric profile page (Administration > DATAWAREHOUSE > Metric profiles).

    For more information, see Adding and modifying metric profiles.

    Levels up to

    The metric level defines the amount of metric imported into the data warehouse. If you increase the level, additional load is added to the data warehouse while decreasing the metric level reduces the number of imported metrics.

    Choose the metric level to apply on selected metrics:

    • [1] Essential
    • [2] Basic
    • [3] Standard
    • [4] Extended

    For more information, see Aging Class mapping.

    Metric filter
    Metric list <for selected dataset>

    Click Edit and select the metrics that will be loaded for each dataset that you selected under Run configuration > Datasets. If no metric is specified, all metrics will be loaded.

    Vis file parser configuration
    Split hierarchy by platform

    Select yes if you want to create subdomains with platform name under the selected destination domain. Systems are split by platform and added to the respective subdomains.

    By default, no is selected.

    Data recovery mode If data was not imported accurately in an earlier run of the ETL, you can run the ETL again with the Data recovery mode property set to True to import the data for the failed time period. By default, this property is set to False. If you select True, you can choose to delete the recovered local files by setting the Delete recovered files (only for local files) property to True. Also, the latest object relationship in the workspace is retained.  
    Extractor mode Select any one:
      • Select any one:
        • via gateway service: Extract the Vis parser through gateway service.
          • Gateway Server: Select any of the Gateway Server from the drop-down list.
          • Manager run list: Specify the manager runs. You can separate multiple manager runs by ";". For example, vcenter.msf; Test.msf; vcenter5.1.msf; Test1.msf.

            Available manager runs
          • Wait configured manager run completion: Select either Yes or No.
          • Manager run name match: Select whether the included manager runs are based on exact match or a substring match. 
          • Archive parsed file in directory: Specifies the archive parsed file in the directory.
          • Compress archived files
            • Yes: Select Yes to compress the archived files.
            • No: Do not compress the archived files.
        • via file
          • Manager run list: Click Add to add the manager list.
          • Disable node check: Select Yes or No.
    File location (applicable only for via file option)
    Subdirectories to exclude (separated by ';' ) (Local directory) Names of subdirectories to exclude from parsing.
    Input file external validator (Local directory, Windows share, FTP) Select any one of the following options:
    • No external validation: Do not use external validation of the CSV file structure.
    • Use external validation script: Use the following script to validate the CSV file:
      • Script to execute: Specify the validation script to use to validate the input file.
    Additional properties
    List of properties
    1. Click Add.
    2. Add an additional property in the etl.additional.prop.n box.
    3. Click Apply.
      Repeat this task to add more properties.
    Loader configuration
    Empty dataset behavior Choose one of the following actions if the loader encounters an empty dataset:
    • Abort: Abort the loader.
    • Ignore: Ignore the empty dataset and continue parsing.
    ETL log file name Name of the file that contains the ETL execution log; the default value is: %BASE/log/%AYEAR%AMONTH%ADAY%AHOUR%MINUTE%TASKID
    Maximum number of rows for CSV output A number which limits the size of the output files.
    CSV loader output file name Name of the file generated by the CSV loader; the default value is: %BASE/output/%DSNAME%AYEAR%AMONTH%ADAY%AHOUR%ZPROG%DSID%TASKID.
    Capacity Optimization loader output file name Name of the file generated by the BMC TrueSight Capacity Optimization loader; the default value is: %BASE/output/%DSNAME%AYEAR%AMONTH%ADAY%AHOUR%ZPROG%DSID%TASKID.
    Detail mode Select the level of detail:
    • Standard: Data will be stored on the database in different tables at the following time granularities: Detail (configurable, by default: 5 minutes), Hourly, Daily, Monthly.
    • Raw also: Data will be stored on the database in different tables at the following time granularities: Raw (as available from the original data source), Detail (configurable, by default: 5 minutes), Hourly, Daily, Monthly.
    • Raw only: Data will be stored on the database in a table only at Raw granularity (as available from the original data source).

    For more information on granularities, see Accessing data using public views and Sizing and scalability considerations.

    Reduce priority
    • Normal:
    • High:
    Remove domain suffix fromdatasourcename (Only for systems) If set to True, the domain name is removed from the data source name. For example, server.domain.com will be saved as server.
    Leave domain suffix to system name (Only for systems) If set to True, the domain name is maintained in the system name. For example: server.domain.com will be saved as such.
    Update grouping object definition If set to True, the ETL will be allowed to update the grouping object definition for a metric loaded by an ETL.
    Skip entity creation (Only for ETL tasks sharing lookup with other tasks) If set to True, this ETL does not create an entity, and discards data from its data source for entities not found in BMC TrueSight Capacity Optimization. It uses one of the other ETLs that share lookup to create the new entity.
    Scheduling options
    Hour mask Specify a value to execute the task only during particular hours within the day. For example, 0 – 23 or 1,3,5 – 12.
    Day of week mask Select the days so that the task can be executed only during the selected days of the week. To avoid setting this filter, do not select any option for this field.
    Day of month mask Specify a value to execute the task only during particular days within a month. For example, 5, 9, 18, 27 – 31.
    Apply mask validation By default this property is set to True. Set it to False if you want to disable the preceding Scheduling options that you specified. Setting it to False is useful if you want to temporarily turn off the mask validation without removing any values.
    Execute after time Specify a value in the hours:minutes format (for example, 05:00 or 16:00) to wait before the task must be executed. This means that once the task is scheduled, the task execution starts only after the specified time passes.
    Enqueueable Select one of the following options:
    • False (Default): While a particular task is already running, if the next execution command arises – it is ignored.
    • True: While a particular task is already running, if the next execution command arises – it is placed in a queue and is executed as soon as the current execution ends.
  4. Click Save.
    You return to the Last run tab under the ETL tasks page.
  5. Validate the results in simulation mode: In the ETL tasks table under ETL tasks > Last run, locate your ETL (ETL task name), click  to run the ETL.
    After you run the ETL, the Last exit column in the ETL tasks table will display one of the following values:
    • OK: The ETL executed without any error in simulation mode.
    • WARNING: The ETL execution returned some warnings in simulation mode. Check the ETL log.
    • ERROR: The ETL execution returned errors and was unsuccessful. Edit the active Run configuration and try again.
  6. Switch the ETL to production mode: To do this, perform the following task:
    1. In the ETL tasks table under ETL tasks > Last run, click the ETL under the Name column.
    2. In the Run configurations table in the ETL details page, click  to edit the active run configuration.
    3. In the Edit run configuration page, navigate to the Run configuration expandable tab and set Execute in simulation mode to No.
    4. Click Save.
  7. Locate the ETL in the ETL tasks table and click  to Run it, or schedule an ETL run.
    After you run the ETL, or schedule the ETL for a run, it will extract the data form the source and transfer it to the BMC TrueSight Capacity Optimization database.

Supported platforms and available metrics

Click a link in the Available metrics (PDF) column to view the metrics in PDF format OR

Right-click the link in the Available metrics (Excel) column and select Save link as to download the Excel file that includes all metrics.

Vendor/OSSupported virtualization technologiesAvailable metrics (PDF)Available metrics (Excel)
StandaloneStandaloneStandalone_metrics

 

 

 

 

All_metrics

IBMPowerVM DLPAR/SPLPAR, WPARIBM_PowerVM_metrics
HP

IVM, nPar/vPar

HP-UX_metrics
RHEVLinux KVMLinux_KVM_metrics
MicrosoftHyper-VHyper-V_metrics
OracleSolaris LDOM, Zone, DSD, Oracle VMOracle_virtualization_metrics
XenOpen source, CitrixXen_metrics
VirtualVirtual NodeVirtual_metrics

Lookup information

EntityEntitytypeColumn mappingLookup fieldsEntity name in Workspace
Strong  Weak
Generic 

genNAME=CAXPSYS.Host_NameHOSTNAMENAMENAME
 HOSTNAME=CAXPSYS.Host_Name+DOMAIN   
 _COMPATIBILITY_=CAXPSYS.Host_Name   
Virtual Host - AIX PowerVM

vh:lpNAME=CAXPSYS.Host_NameNAME  ALIAS_NAME
 ALIAS_NAME=CAXPSYS.Alias   
 _COMPATIBILITY_=CAXPSYS.Host_Name   
Physical Pool - AIX PowerVM

rp:aixNAME=CAXPOOL.Pool_NamePOOL_ID  NAME
 POOL_ID=CAXPOOL.Pool_Id_COMPATIBILITY_  
 _COMPATIBILITY_=CAXPOOL.Pool_Id   
Shared ProcessorPool

rp:sppNAME=CAXPOOL.Pool_NamePOOL_ID  NAME
 POOL_ID=CAXPOOL.Pool_Id_COMPATIBILITY_  
 _COMPATIBILITY_=CAXPOOL.Pool_Id   
Virtual Machine - AIX LPAR, Virtual Machine -
AIX Shared Processor LPAR,
Virtual Machine - AIX VIO LPAR


gm:splp, gm:lp, gm:violpNAME=CAXVM.Partition_NameNAME&&HMC_NAMENAMEHOSTNAME 
 HOSTNAME=CAXVM.NODE_NAMEHOSTNAME   
 HMC_NAME=CAXVM.HMC_NAME   
 _COMPATIBILITY_=CAXVM.UUID   
Generic  (WPAR Host)genericNAME=CAXPSYS.Host_NameHOSTNAME NAME
(Standalone Host) HOSTNAME=CAXPSYS.Host_Name   
 _COMPATIBILITY_=CAXPSYS.Host_Name   
Virtual Machine - AIX LPAR, Virtual Machine - AIX Shared Processor LPAR, Virtual Machine - AIX VIO LPAR (WPAR Host)


vh:lpNAME=CAXVM.Partition_NameNAME&&HMC_NAMENAMEHOSTNAME 
 HOSTNAME=CAXVM.NODE_NAMEHOSTNAME   
 HMC_NAME=CAXVM.HMC_NAME   
 _COMPATIBILITY_=CAXVM.UUID   
Workload Partition - AIX WPAR

gm:wparNAME=CAXWPAR.Config_Name HOSTNAMENAMEHOSTNAME 
 HOSTNAME=CAXWPAR.Node_Name   
 _COMPATIBILITY_=CAXWPAR.Partition_Name   
Virtual Host - Solaris (LDOM Host)

vh:znNAME=CAXPSYS.Host_NameHOSTNAME  NAME
 _COMPATIBILITY_=CAXPSYS.Host_Name   
 HOST_NAME=CAXPSYS.Host_Name   
Virtual Machine - Solaris LDOM

gm:ldomNAME=CAXVM.Partition_NameHOSTNAMENAMENAME (default, can be changed to HOSTNAME by using a config parameter in ETL)
 HOSTNAME=CAXVM.NODE_NAME   
 _COMPATIBILITY_=CAXVM.UUID   
Virtual Host - Solaris (DSD Host)

vh:znNAME=CAXPSYS.Host_NameHOSTNAME NAME
 HOSTNAME=CAXPSYS.Host_Name   
 _COMPATIBILITY_=CAXPSYS.Host_Name   
Virtual Machine - Solaris Dynamic System Domain

gm:dsdNAME=CAXVM.Partition_NameHOSTNAMENAMENAME (default, can be changed to HOSTNAME by using a config parameter in ETL)
 HOSTNAME=CAXVM.NODE_NAME   
 _COMPATIBILITY_=CAXVM.UUID   
Virtual Host - Solarisvh:znNAME=CAXPSYS.Host_NameHOSTNAME NAMENAME
(Standalone Host) HOSTNAME=CAXPSYS.Host_Name+DOMAIN   
 _COMPATIBILITY_=CAXPSYS.Host_Name   
Virtual Host - Solaris (LDOM host or DSD host)

vh:znNAME=CAXVM.Partition_NameHOSTNAMENAMENAME (default, can be changed to HOSTNAME by using a config parameter in ETL)
 HOSTNAME=CAXVM.NODE_NAME   
 _COMPATIBILITY_=CAXVM.UUID   
Virtual Machine - Solaris Zone

gm:znNAME=CAXWPAR.Config_Name HOSTNAMENAMEHOSTNAME 
 HOSTNAME=CAXWPAR.Node_Name   
 _COMPATIBILITY_=CAXWPAR.Partition_Name   
Virtual Host - HP nPar/vPar

nparcNAME=CAXPSYS.Host_NameNAME ALIAS_NAME
 ALIAS_NAME=CAXPSYS.Alias   
 _COMPATIBILITY_=CAXPSYS.Host_Name   
HP nPar/vPar Partition (for nPar)

vparNAME=CAXPOOL.POOL_NameHOSTNAMENAMENAME
 HOSTNAME=CAXPOOL.POOL_ID   
 _COMPATIBILITY_=CAXPOOL.POOL_ID   
HP nPartition

nparNAME=CAXVM.Partition_NameHOSTNAMENAMENAME (default, can be changed to HOSTNAME by using a config parameter in ETL)
 HOSTNAME=CAXVM.NODE_NAME   
 _COMPATIBILITY_=CAXVM.UUID   
HP vPartition

vparNAME=CAXVM.Partition_NameHOSTNAMENAMENAME (default, can be changed to HOSTNAME by using a config parameter in ETL)
 HOSTNAME=CAXVM.NODE_NAME   
 _COMPATIBILITY_=CAXVM.UUID   
Virtual Host - HP Integrity


vh:int    
 NAME=CAXPSYS.Host_NameHOSTNAMENAMENAME
 HOSTNAME=CAXPSYS.Host_Name+DOMAIN   
 _COMPATIBILITY_=CAXPSYS.Host_Name   
Virtual Machine - HP Integrity

hp:intNAME=CAXEMVM.VM_NameHOSTNAMENAMENAME
 HOSTNAME=CAXEMVM.Node_Name   
 _COMPATIBILITY_=CAXVM.UUID   
Virtual Host - Hyper-V

vh:hvNAME=CAXPSYS.Host_NameHOSTNAMENAMENAME
 HOSTNAME=CAXPSYS.Host_Name+DOMAIN   
 _COMPATIBILITY_=CAXPSYS.Serial_Number   
Virtual Machine - Hyper-V


gm:hvNAME=CAXVM.Partition_NameUUIDNAME&&
PARENT_CLUSTERNAME
NAME
 UUID=CAXVM.UUID NAME 
 _COMPATIBILITY_=CAXVM.UUID   
 PARENT_CLUSTERNAME=
CAXVMD.CLSR.Cluster_Name
   
Virtual Host - Xen

vh:xenNAME=CAXPSYS.Host_NameHOSTNAMENAMENAME
 HOSTNAME=CAXPSYS.Host_Name+DOMAIN   
 _COMPATIBILITY_=CAXPSYS.Serial_Number   
Virtual Machine - Xen

gm:xenNAME=CAXVM.Partition_NameUUIDNAMENAME
 UUID=CAXVM.UUID   
 _COMPATIBILITY_=CAXVM.UUID   
Virtual Host - KVM

vh:kvmNAME=CAXPSYS.Host_NameHOSTNAMENAMENAME
 HOSTNAME=CAXPSYS.Host_Name+DOMAIN   
 _COMPATIBILITY_=CAXPSYS.Serial_Number    
Virtual Machine - KVM


gm:kvmNAME=CAXEMVM.VM_NameUUIDHOSTNAMENAME 
 HOSTNAME=CAXEMVM.Node_Name NAME 
 UUID=CAXEMVM.UUID   
 _COMPATIBILITY_=CAXVM.UUID   
WorkloadwkNAME=CAXWCATS.Wkl_IDNAME NAME
 _COMPATIBILITY_=CAXWCATS.Wkl_ID   
Virtual Node - VMware, Virtual Node - Hyper-V, Virtual Node - Xen,
Virtual Node - KVM, Virtual Node - Oracle VM,
Virtual Node - HPIVM, Virtual Node - RHEV


gm:wvn, gm:hvvn,
gm:xenvn, gm:kvmvn, gm:oraclevn, gm:ivmvn, gm:rhevn
VN_NAME=CAXNODE.Node_AliasVN_HOSTNAMEVN_NAMEVN_NAME
 VN_HOSTNAME=CAXNODE.Node_Alias
+CAXNODE.Domain_Name
 VN_UUID 
 VN_UUID=CAXNODE.Serial_Number    
 _COMPATIBILITY_=CAXNODE.Node_Alias   

Entity relationship

For VMware platform

Parent entityChild entityRelationship
ClusterHostVHC_CONTAINS_VH

Cluster

Virtual machine VHC_CONTAINS_GM
ClusterData storeVHC_USES_DS
ClusterResource poolVHC_CONTAINS_RP
Host            Virtual machineVH_CONTAINS_GM
HostData storeVH_USES_DS
Host                      Resource poolVH_CONTAINS_RP
Data storeVirtual machineDS_CONTAINS_GM
Resource poolVirtual machineRP_CONTAINS_GM
Physical poolShared poolRP_CONTAINS_RP

For AIX platform

Parent entityChild entityRelationship

Power VM hosts        

Virtual machineVH_CONTAINS_GM
Power VM hostsPhysical poolVH_CONTAINS_RP

Physical pool

Shared poolRP_CONTAINS_RP
PoolVirtual machineRP_CONTAINS_GM
Power VM hostswparVH_CONTAINS_WPAR

Wpar logical hosts 

wparGM_CONTAINS_WPAR

For Solaris platform

Parent entityChild entityRelationship
HostVirtual machineVH_CONTAINS_GM
Physical hostZoneVH_CONTAINS_ZN
Zone logical hostZoneGM_CONTAINS_ZN

For HP IVM  platform

Parent entityChild entityRelationship
HostVirtual machineVH_CONTAINS_GM
Physical host

npar containg vPar

VH_CONTAINS_NPAR
nPar

npar containing vpar

NPAR_CONTAINS_VPAR

For HyperV platform 

Parent entityChild entityRelationship
ClusterHostVHC_CONTAINS_VH
ClusterVirtual machineVHC_CONTAINS_GM
HostVirtual machineVH_CONTAINS_GM

For XEN platform

Parent entityChild entityRelationship
HostVirtual machineVH_CONTAINS_GM

For KVM platform

Parent entityChild entityRelationship
HostVirtual machineVH_CONTAINS_GM
HostData storeVH_USES_DS
Data storeVirtual machineDS_CONTAINS_GM

For workload

Parent entityChild entityRelationship
SystemsWorkloadCONTAINS_WORKLOAD

16 Comments

  1.  

  2.  

  3.  

    1.  

  4.  

  5.  

    1.  

    2.  

  6.  

  7.  

    1.  

      1.  

  8.  

    1.  

  9.  

    @

     

    1.