> For the complete documentation index, see [llms.txt](https://docs.vngcloud.vn/vng-cloud-document/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vngcloud.vn/vng-cloud-document/glb/network-glb/getting-started-with-network-glb.md).
# Getting Started with Network GLB
In this section, we will learn how to use and manage a Network GLB in the most basic way, providing an overall understanding of how Network GLB works.
#### Trước khi bắt đầu
* Tìm hiểu cách **truy cập GreenNode Portal** với Root User Account hoặc IAM User Account, tham khảo hướng dẫn [How to Login into GreenNode](/vng-cloud-document/identity-and-access-management-iam.md).
#### 1. Access the GLB Console
The GLB Console is a web-based user interface that allows you to manage Global Load Balancers in your cloud environment. It provides an intuitive interface for controlling and managing your GLBs.
**How to Access the GLB Console**
* Access from the vConsole homepage:
* Under the “GreenNode Service” section in the interface, select “vServer”, then choose “GLB” from the corresponding product/service list on the right.
* Or directly access the vLB Portal via::
#### 2. Create a Network GLB
**How to Create a Network GLB**
1. From the Global Load Balancer homepage, click “Create Global Load Balancer”.
2. Select Load Balancer Configuration
* **Global Load Balancer Name:** If the user does not manually provide a GLB name, the system will automatically generate one.
* **Layer:** Select “Network - TCP”.
3. Configure Listener
* **Listener Name:** If the user does not manually provide a Listener name, the system will automatically generate one.
* Protocol & Port
* If **Protocol = TCP**, the user must select a Port (Port 80 is pre-filled by default).
4. Configure Global Pool
* **Global Pool Name:** If the user does not manually provide a Pool name, the system will automatically generate one.
* **Protocol:** TCP/Proxy (for TCP Listener).
* **Algorithm:** Select an appropriate load balancing algorithm.
* **Health Check Settings:** Protocol options include TCP / HTTP / HTTPS (for TCP/Proxy Pool).
5. Select Global Pool Members**:** Add backend servers to the Global Pool Member.
Global Pool Members allow users to add backend servers from multiple Regions.
* Select Region and VPC for the Global Pool Member.
* Next, attach backend servers (from subnets within the same VPC) to the pool.
6. Review Configuration Information**:** Users can review the configuration information before completing the creation process. This information will be displayed on the right side of the input screen.
* “Summary” Tab:
Review the configuration details for:
* GLB
* Global Listener
* Global Pool
* Global Pool Member
7. Complete the Creation Process**:** After completing the configuration and reviewing the information, click “Create Global Load Balancer / Create Load Balancer” to finish creating the GLB.
#### 3. Monitor and Verify NGLB
* After successful creation, the system will redirect users to the Global Load Balancer list page. Here, users can monitor the GLB status from **Creating** to **Active** (successfully created).
* Once the creation process is complete, users can access the Global Load Balancer detail page to monitor and verify the correctness of the GLB configuration.
---
# 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.vngcloud.vn/vng-cloud-document/glb/network-glb/getting-started-with-network-glb.md?ask=&goal=
```
`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.