> For the complete documentation index, see [llms.txt](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/integrations/connectivity/insight-point/ova-v2/ova.md).

# Deploy with Virtual Appliance (Legacy)

{% hint style="info" %}
If you are deploying a new Insight Point, Veza recommends using the latest version of the Insight Point OVA. Please follow the instructions in the [Insight Point - Oracle Virtual Appliance](/4yItIzMvkpAvMVFAamTf/integrations/connectivity/insight-point/ova-v2.md) for the most current deployment instructions.
{% endhint %}

### Operation and Troubleshooting

After the Insight Point deploys, verify that it has successfully connected to the Veza platform. Log in to the Veza platform and follow these steps:

1. On the left navigation pane, under **Configuration**, click **Insight Point**
2. Verify that a new Insight Point has registered with the platform.

**Note**: One Insight Point will exist by default, named "Veza Insight Point".

#### Verifying Container Status

If the newly deployed Insight Point does not appear on the Veza platform, verify the status of the container on the virtual machine:

1. Log into the virtual machine console or use SSH
2. List running Docker processes with the command: `docker ps -a`
3. Examine the output

The Insight Point's container ID should include a **Status** column showing `Running`.

#### Accessing Insight Point Logs

If the Insight Point does not appear to be in a running state, or if requested by Veza support, follow these steps to access the Insight Point logs:

1. Log into the virtual machine console or use SSH
2. Run the following command: `docker ps -a`
3. Note the value in the `Container ID` field
4. Run the following command to output the Insight Point logs: `docker logs <container_id>`, substituting the actual container ID
5. The logs are in JSON format and can be output to a file or copied from the terminal for debugging


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.veza.com/4yItIzMvkpAvMVFAamTf/integrations/connectivity/insight-point/ova-v2/ova.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.