Monitoring and Troubleshooting BPA Data Quality in BCO TSCO Capacity Optimization 10.0
|
Legacy ID:KA391161 The term "virtual" has many definitions and connotations. However, when using the specific phrase "virtual node" or sometimes "virtual server", it means something very specific within Performance Assurance and the Capacity Optimization console integration with Performance Assurance. More specifically, this is how/where you can look at this performance and capacity data:
Note that Perceiver does not have the Virtual Server views enabled by default. The system administrator needs to carefully assess whether the understanding of the data consumers is sufficient to deal with virtualized guest data, which may be anywhere from misleading to just plain incorrect. It can also be incredibly useful for specific use cases.
Similar techniques can be used to analyze the contents of .vis files, but are not described in detail here. The most basic determination can be made by observing the system name in the SYSTEMS section, and looking for the "VIRTUAL" designation on the same line as the system name. For example: T;SYSTEMS ;VXPIP-ERIRPT01 0bfxp_tUQtGhMdI,'Generic Xeon X5660 hex core at 2800 MHz',UNA142P,INTEL_XEON_X566,12011.691406,-1.000000,4,,,,INTEL_XEON_X566,Linux,,,VXPIP-ERIRPT01,SPECINTRATE2000,NA,VXPIP-ERIRPT01,VIRTUAL,4,VMware ESX,,,lmig.com,'VMware-42 00 d4 6a fa b2 28 a0-da 51 24 ',2.6.18-164.el5 (Red Hat Enterprise Linux Server release 5.4 (Tik,10.177.72.186,'VMware Virtual Platform','VMware, Inc.',,'440BX Desktop Reference Platform','Intel Corporation','Intel(R) Xeon(R) CPU X5660 @ 2.80GHz',GenuineIntel,,vxpip-erirpt01,2,2799,1,1, So in this example, "VXPIP-ERIRPT01" is the name of the VM. "VIRTUAL,4,VMware ESX" indicates that it's been classified as a VIRTUAL node ("inside" data collection), it has 4 virtual processors configured, and that it's hosted by VMware. In this particular example, the metrics that have triggered the identification as virtual are also reported in this row of data, "'VMware Virtual Platform','VMware, Inc.'", which are recorded as part of the System Configuration udr metrics.
(2) As described above, you can use the Perceiver "mouse over" feature for the Computer drop down list. Simply select the type of view you want, then see which computers are presented in the selection list. If you see either "SYSTEM_TYPE=virtual_UNIX" or "SYSTEM_TYPE=virtual_NT", Perceiver has discovered this system as "VIRTUAL".
BCO CONSOLE
The single most important point here is that if you have intended VIRTUAL nodes as described above, you must use a ETL specifically enabled to import data from those servers into the BCO console. These ETLs are labelled and/or documented as importing "Virtual Node"s. Note that this is a separate ETL for BCO versions 9.5 (and earlier) -- in version 10.0, there is a single ETL used and you need to select Virtual Node under the Platform selection of the Run configuration. Only Virtual Nodes of the following types will be imported: VMware, Hyper-V, Xen, KVM, RHEV, and HP IVMs. Note that systems which are supposed to be tagged as Virtual nodes will be imported as "Generic" entities instead of as "Virtual Node" entities if the BPA support for that virtualization hasn't been properly implemented (adequate data collector and BPA console version). This can have major effects on licensing reports as well as available metrics until the BPA versions have been properly upgraded. Then be aware that what appear as similar metrics for the same server can and will have different values, simultaneously. It's important to assess the understanding level of the consumer of this data before enabling this type of data import. Also carefully consider if you want to enable "Shared lookup" -- enabling Shared lookup will cause the data from the ETL which runs later to overwrite data imported by the earlier running ETL. Even when data isn't being overwritten, you will see apparently incompatible values for similar-sounding metrics. Importing with Shared lookup disabled means that you will have two entities with the same name, but different values for metrics which could have identical labels. These two entries will be located in different sections of the hierarchy tree.
BCO/BPA AUTOMATION SUPPORT
When using the automation support tools for tracking data import from BPA into BCO (described in KA385227), be sure to use the "-v" option to exclude consideration of VIRTUAL nodes if you are not importing them.
Related Products:
|