> For the complete documentation index, see [llms.txt](https://docs.vergeos-demo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vergeos-demo.com/plan-and-deploy/implementation-guide/post-installation.md).

# Post-installation configuration

## Introduction

After completing your VergeOS installation, there are a few essential steps to verify and optimize your system. This page will guide you through key post-installation steps to be completed after installing initial VergeOS nodes.

***

## 1. Verify System Status

* **Access the Web UI:**
  * Open a web browser and navigate to your VergeOS system's IP address.
  * Log in using your admin credentials created during installation.
* **Confirm System Health:**
  * Check the Main Dashboard (home page) for any warnings or alerts, including the *Logs* section at the bottom of the page.
  * Ensure all nodes are showing as online and healthy. The *Nodes* tile on the Main Dashboard should display all nodes online with a green status.

***

## 2. Verify Network Configuration

The Core Fabric Network at the heart of VergeOS is designed with redundancy and resiliency in mind. For this architecture to function as intended, administrators must verify two key attributes of the core networks: redundancy and isolation. Proper verification at this stage helps to ensure expected fault tolerance and performance as you move into production.

* **Test Core Network Redundancy**\
  To ensure the system can tolerate hardware or link failures without impacting workloads or data integrity:
  * Physically disconnect cables or power down one of the core switches to simulate a failure.
  * Within the VergeOS UI, navigate to *Nodes*. Wait several minutes to verify that all nodes appear with "Running"/green status.
  * After restoring the failed link or switch, repeat this test on the other physical core network.
* **Verify Isolation of Core Networks**\
  To maintain data integrity and prevent inter-system interference:
  * Verify each physical core network operates on its own isolated switch or, at minimum, a dedicated VLAN.
  * Ensure that no other VergeOS systems share these networks. For example, if your are running multiple VergeOS host systems within shared infrastructure, each system would need two unique and exclusive VLAN IDs.

{% hint style="warning" %}
**Avoid using VLANs 1 and 100-102 which are reserved for VergeOS internal system traffic.**
{% endhint %}

* **Verify External Connection Redundancy**\
  Ensure external redundancy for remote connectivity:
  * Simulate external connection loss to node 1 (disconnecting network cable, etc.)
  * Confirm you still have remote access to the VergeOS user interface

### Important Considerations

* Regular testing of network redundancy and failover is recommended.
* Document all configuration changes for future reference.

***

## 3. System Configuration

* VergeOS provides configuration options for you to secure and maximize the benefits of your new system. Follow the [**New System Configuration Checklist**](/run-the-platform/platform-overview/new-system-configuration.md) in the Product Guide to finish preparing your environment for production.

***

## Troubleshooting & Support

If issues arise during post-installation configuration:

* Check the system logs for any errors
* Review the [Knowledge Base](https://docs.vergeos-demo.com/knowledge-base/) for common solutions
* Contact [VergeOS Support](/support-and-services.md) for assistance


---

# 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:

```
GET https://docs.vergeos-demo.com/plan-and-deploy/implementation-guide/post-installation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.