Skip to main content

Optical Prime How To Run New Discovery UI

Team Live Optics
  • Updated

Overview

This article outlines the new Optical Prime user interface.

 

This feature only changes the UI of the collector for Optical Prime discovery.  There are no functional changes to how Optical Prime collects or to the workflow for Optical Prime.

Running Optical Prime

  1. To run Optical Prime, first Download the Live Optics Collector.
  1. Click through the introductory screens of the Live Optics Collector application and navigate to the main screen for Optical Prime.

Discovery_UI_pic_1.png

 

3. From this screen on, the Optical Prime workflow is unchanged.

4. On the Optical Prime import screen, the “add servers” buttons act in the same original way.

 

Discovery_UI_pic_2.png

 

5. However, the display of items once added is changed from the legacy UI.

 

Optical_Discovery_UI__3_.png

 

      1. Physical Servers
          • This root node is only shown if there are physical servers.
          • Servers are sorted alphabetically by Host Name.
          • The number of servers is shown as a count on the top left.
      2. Hypervisors

Discovery_UI_pic_3.png

 

 

    • This root node is only shown if there are hypervisors.
    • The summary label for Hypervisors shows the vCenter count, the Cluster count, the hypervisors (servers) count, and the guest VM count.
    • vCenters count is only shown if there are vCenter targets.
    • Hypervisors contains up to three child nodes (depending on what is there).
      • The summary count for vCenters is the number of vCenter targets.
      • The summary count for Hyper-V is the number of hyper-v servers.
      • The summary count for Other is the number of Linux based hyper-v servers (Xen/KVM)
    • The vCenter, Hyper-V, and Other nodes are only shown if they are populated.
    • Each of these child nodes under hypervisors is expandable:
      • The children under vCenter are each cluster that belongs to the vCenter
      • "(Not in cluster)" is only shown if there are any ESX servers that are not clustered.
      • The summary counts for each of these child nodes is the number of ESX servers in the cluster (or the not-in-cluster group).
      • Finally, the cluster nodes expand into the lists of the individual ESX servers.

3. Virtual Machines (Directly targeted)

    • This is only shown if there are virtual machines that were directly targeted and are not also hypervisors.

4. Shared Cluster Disks and Local Disks

    • The shared cluster disk summary count is just the count of shared cluster disks. This is the count of unique shared cluster disks (same cluster ID) not the count of the number of disk nodes.

5. A summary “Tile” view has also been added, which can be toggled from the top right corner.

 

Discovery_UI_pic_4.png

 

  1. Physical Servers shows the count of physical servers. A server is considered physical if it is not a hypervisor and if it is not a virtual machine.
    • The Windows and Linux counts are based on whether the protocol was WMI or SSH. We acknowledge that Solaris and HP-UX will be misidentified as Linux.
  2. The Hypervisors Tile has a count of all Hypervisor servers.
    • If a server is both a hypervisor and virtual, it will show in the hypervisors tile and not the virtual tile.
    • The number of vCenter targets is shown. vCenters will map 1:1 to VmwareTargets.
    • The number of Clusters is also shown.
  1. The Virtual Machines Tile has two display modes:
    • The first mode is when there are only Guest VMs and no servers directly targeted that are virtual.
    • The second mode is only shown when there are some directly targeted servers that are virtual (and are not hypervisors).