vCommander® Application Server


You can monitor the following on the vCommander Application Server:

Windows Services


vCommander installs several Windows services, whose running state/availability may be monitored. If your solution allows for it, monitor for operating status of the services.



Service Name Description
vCommander (vlm) The primary vCommander service. Must always be running in order for normal operations to occur. Startup type set to Automatic.
vCommander Hyper-V Adapter (vlm-hyperv) The service which brokers communications with Microsoft System Center Virtual Machine Manager. Will always be installed, but can be set to Manual startup or disabled entirely if you have no plans to manage a Hyper-V private cloud.
vCommander Database (vlm-db) The postgreSQL service which is installed when not using Microsoft SQL. Startup type set to Automatic.


Resources


The resources consumed by vCommander's operation vary depending on the specifics of your environment and usage. Refer to the knowledgebase article Scaling vCommander Hardware Requirements for more information on expected resources required to run vCommander successfully based on our experiences. Once you have provided adequate resources to vCommander, before starting to monitor resource availability, you must first get a baseline of the utilization over a typical work-week at a minimum. This allows you to set thresholds for alerting which will fire only when your attention is required.

Performance Counter  Instance Description
Processor - % Processor Time  tomcat7 % Processor Time is the percentage of elapsed time that all of process threads used the processor to execution instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.
LogicalDisk - % Free Space  (Choose the disk where vCommander is installed) % Free Space is the percentage of total usable space on the selected logical disk drive that was free.
Memory - Pages/sec N/A Pages/sec is the rate at which pages are read from or written to disk to resolve hard page faults. This counter is a primary indicator of the kinds of faults that cause system-wide delays. It is the sum of Memory\\Pages Input/sec and Memory\\Pages Output/sec. It is counted in numbers of pages, so it can be compared to other counts of pages, such as Memory\\Page Faults/sec, without conversion. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.

Network Ports


The following TCP ports must be open on the application server in order for the associated functionality to work as expected. The table displays the default ports only; if you have installed using custom ports, these must be monitored instead. Refer to Testing TCP Ports for a description on how to confirm the ports are open.

Connection Type Default Port Protocol Direction
vCommander
Service Portal
VM Access Proxy
443 TCP Inbound
Database (Microsoft SQL) * 1433 TCP Outbound
Database (PostgreSQL) 5432 TCP Outbound
VM Access Proxy (secure connections) 8443 TCP Inbound
SCVMM console port for connection to VMM management server 8100 TCP Inbound
Hyper-V Adapter port (SCVMM only) 8732 TCP Outbound
File Transfer 139 or 445 TCP Outbound
WMI Scanning 135 TCP Outbound
VM Console Access via SSH
Linux Guest OS Scan
Legacy Datastore Scan
22 TCP Outbound
VM console access for RDP connections 3389 TCP Outbound
VM console access for VNC connections 5900 TCP Outbound
VM console access for Hyper-V 2179 TCP Outbound
Splunk server (optional integration) 8089 TCP  Outbound
BlueCat server (optional integration) 80 TCP Outbound
Kerberos Key Distribution Center 88 TCP and UDP Outbound
Active Directory Domain Controller 686 TCP Outbound
Active Directory Domain Controller for remote LDAP traffic 389 TCP and UDP Outbound
Active Directory Domain Controller for remote Global Catalog traffic 3268 TCP Outbound


Log Files


vCommander writes out to a number of text log files whose contents may be monitored for errors or other conditions of note. The log files are located by default in: 

  • <Install Location>\Embotics\vCommander\tomcat\logs\


The primary log is vcommander.log, but some environments may be configured to use more than one log.  See also the article Configuring Log File Count and Size


Embotics® does not recommend that log file monitoring be configured unless you are tracking a specific issue for a specific version of vCommander. This is because much of the contents of the logs are obfuscated on a per-release basis so the string for an exception may change from release to release. On the other hand, casting a wide net by monitoring simply for strings like Error or Exception could yield many false alerts as messages are sometimes logged as a reaction to environmental issues (for example a user entering an incorrect password), or in some cases may simply not be relevant to your use of the product. As such, when possible, using monitors for the other check points discussed in this article is preferred.


Some strings that may be useful include:



  • Null pointer exception
  • Connection refused
  • Error persisting observation set to database

Another approach is to check the timestamps in the logs for specific issues you encountered, and capture useful strings. Remember that these strings may change between releases!

API


There are a few API calls that are useful for statuses. As with the performance monitoring of resources, you'll want to baseline typical usage over a week or so before setting any kind of alerting threshold.

Monitor the observation queue:


VM Access Proxy


Resources


The resources consumed by the VM Access Proxy vary depending on the number of concurrent connections your users open. Generally, the default resources for the appliance will be sufficient for up to 100 concurrent users, but you may find that providing more CPU or memory to be of benefit. Generally, you should discuss this with Embotics technical support before proceeding. Before starting to monitor resource availability, you must first get a baseline of the utilization over a typical work-week at a minimum. This allows you to set thresholds for alerting which will fire only when your attention is required.

Network Ports


The following TCP ports must be open on the application server in order for the associated functionality to work as expected. The table displays the default ports only; if you have installed using custom ports, these must be monitored instead.

Connection Type Default Port Protocol Direction
vCenter & Hyper-V Console 443 TCP Inbound
RDP, VNC, SSH  8443 TCP Inbound
WebMKS connections to vCenter 5.5 7343  TCP Outbound
WebMKS connections to vCenter 6.0
 9443  TCP Outbound


vCommander Database Server


Windows Services


Any default SQL monitoring you can perform will be useful, but make sure it includes specifics for the vCommander instance itself. If your solution allows for it, monitor for operating status of the services.



Service Name Description
SQL Server (MSSQLSERVER) The default service for Microsoft SQL. Make sure that you are monitoring for the correct named if not using the default instance. Startup type should be Automatic.


Resources


The resources consumed by vCommander's database operation vary depending on the specifics of your environment and usage. Refer to the knowledgebase article Scaling vCommander Hardware Requirements for more information on expected resources required to run vCommander successfully based on our experiences. Once you have provided adequate resources to the vCommander database, before starting to monitor resource availability, you must first get a baseline of the utilization over a typical work-week at a minimum. This allows you to set thresholds for alerting which will fire only when your attention is required.


Performance Counter  Instance Description
Processor - % Processor Time  _Total % Processor Time is the percentage of elapsed time that all of process threads used the processor to execution instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.
Process - % Processor Time  sqlservr  % Processor Time is the percentage of elapsed time that all of process threads used the processor to execution instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.
LogicalDisk - % Free Space  (Choose the disk or disks where vCommander data file (mdf) and log file (ldf)  are stored) % Free Space is the percentage of total usable space on the selected logical disk drive that was free.
Memory - Pages/sec N/A Pages/sec is the rate at which pages are read from or written to disk to resolve hard page faults. This counter is a primary indicator of the kinds of faults that cause system-wide delays. It is the sum of Memory\\Pages Input/sec and Memory\\Pages Output/sec. It is counted in numbers of pages, so it can be compared to other counts of pages, such as Memory\\Page Faults/sec, without conversion. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.


Network Ports


The following TCP ports must be open on the database server in order for the associated functionality to work as expected. The table displays the default ports only; if you have installed using custom ports, these must be monitored instead.


Connection Type Default Port Protocol Direction
Database (Microsoft SQL) 
1443 TCP Inbound


See also Configuration Based Requirements for Microsoft SQL for additional information required in some circumstances.