Articles in this section

Endpoint List and Connector Connection Status Reference

You can view the connector status on each and every server in Servers Tab > Status .

In order to add manage columns that are shown, click on Table Settings in the right-hand corner.  Explanation of all available columns below:

pasted_image_0.png

Status

Connection Status

Common Actions

 Untested

Untested: Machine was added to the list (from a discovery source or manually), but JetPatch has not yet attempted to communicate with it.

 To have JetPatch attempt communication (for example, to confirm valid credentials), select the endpoint and click Server Actions > Assign Account. You can also try to refresh the server’s status by clicking on Server Actions > Refresh Status

 Available

Available: Valid credentials are known to be available, but JetPatch has yet to install the JetPatch connector on the endpoint.

You can now install connector:

  1. Deploy the connector
  2. Deploy the connector on the endpoint itself

 Connected

Connected: The JetPatch connector is installed and running.

You're all set !

 Disconnected

Not reachable: Was Connected, but there is a communication problem. This status also appears while the JetPatch server is restarting. 

Try to refresh status on the server / Check if the machine is powered on.  

 Connector Down

Disconnected: This is a physical machine with the JetPatch connector installed, but Some issue with the connector. 
  1. Try to refresh status on the server
    • In Platform Configuration, go to Servers, and click the 'Server Actions' button.
    • Refresh server status
  2. Manually restart the connector.
  3. Manually remove and install the connector from the endpoint itself 

 Connector down

JetPatch down: Was connected, and the machine is reachable, but the JetPatch connector is not running.
  1. Try to refresh status on the server
    • In Platform Configuration, go to Servers, and click the 'Server Actions' button.
    • Refresh server status
  2. Manually restart the connector.
  3. Manually remove and install the connector from the endpoint itself 

Invalid_credentials 

Invalid credentials: The supplied credentials are not accepted by this endpoint, so it cannot be managed.

Assign valid server account for the server.

Pending 

Pending: A task was received but is not yet in progress.

 

 task_in_progress

In progress: JetPatch is performing an operation on this endpoint.

 

Suspended

  

 machinedown__1_.png

Powered off: This VM is down.

  

Last Status Collected

The last date and time the endpoint's status was checked

Name

A descriptive label for the machine. For vSphere VMs - taken from the vCenter; For other machines - defined when adding the machine to JetPatch.

Clicking on an endpoint's name in the Name column displays the endpoint's full managed agent information and controls, and logs.

Managed agents

All the managed agents installed on the machine. Non-functioning managed agents are marked to indicate their status:

 

 agent_stopped.png

Initializing: agent is starting to be deployed, the VAI file is opened and records are added to Connector data.

 

 n/a

Virtualize: agent is starting to be installed (actual installation of the product).

 

 agent_as_package.png

As_Package: only VAI file exists on the machine.

 

agent_stopped.png

Stopped: agent is not running on the endpoint (on purpose or not).

 

 agent_error.png Error: agent installation ran into a problem on the endpoint. 

 

 n/a Unvirtulize: agent is in uninstallation process.

 

 n/a Running: agent is running properly on the endpoint.

Management services

Service names of all managed agents installed on the machine

Type

One of:

 

icon_vmware.png

vSphere VM

 

icon_aws.png

AWS EC2 cloud instance

 

azure.gif

Microsoft Azure Cloud instance (ARM and ASM)

 

icon_physical.png

Physical or other non-discoverable endpoint

Protocol in Use

The communication protocol currently being used to communicate with this endpoint.

IP

Machine's IP address (for AWS EC2 cloud instances: the instance's private IP address; for Azure cloud instances, may include non-standard port number).

Hostname

Machine's DNS hostname (for EC2 cloud instances: the instance's private DNS name).

OS

Machine's operating system (for EC2 cloud instances: the instance's AMI).

Tags

Tags applied to this machine.

Group

Dynamic groups that are applied to this machine.

Core Server ID

Internal JetPatch parameter, defining a component of the JetPatch server.

Intigua Version

Version number of JetPatch connector on the endpoint.

Assigned Account

The user account being used to communicate with the endpoint.

Discovery Time

The time which JetPatch first discovered the machine.

In addition, there is an available column for each managed agent, with non-functioning managed agents marked as in the Managed agents column, and an informative tooltip. There is also a column for each JetPatch connector version.

The following columns are relevant only to vSphere virtual machines:

     

vCenter

The managing vSphere

VMware Status

One of:

 

machinedown.png

Tools not running: VMware Tools are not running.

 

tools-error.png

Old Tools

vHost

ESX server name

VMX Path

Location on ESX storage

Power

Whether the VM is up

Tools Status

Whether VMware Tools are running

Tools Version

VMware Tools version

Instance UUID

A vSphere identifier for the machine

CPU Cores

Number of CPU cores on a server (equivalent to CPU count column in vCenter)

CPU %

Percentage of CPU consumption on the server

Memory

Size of allocated memory

Memory In Use

Amount of memory consumption

Disk Space

Storage space

Disk Space In Use

Amount of used disk space

The following columns are relevant only to AWS EC2 cloud instances:

  • AWS Instance ID
  • AWS Instance Type
  • AWS Public IP Address
  • AWS Public DNS Name
  • AWS Region
  • AWS Zone
  • AWS Virtualization
  • AWS Instance Launch Time

Related articles

Comments

0 comments

Please sign in to leave a comment.