ZONE: a zona da VM do cliente. Essa zona precisa estar na mesma região que o balanceador de carga.
SUBNET: a sub-rede da VM do cliente.
Enviar tráfego IPv6 para o balanceador de carga
Agora que você configurou o balanceador de carga, é possível testar a implantação
enviando tráfego para o endereço IP dele. Pode levar alguns minutos para que a configuração do balanceador de carga seja propagada após a primeira implantação.
Conecte-se à instância da VM cliente.
gcloud compute ssh CLIENT_VM_NAME \
--zone=ZONE
Substitua:
CLIENT_VM_NAME: o nome da VM do cliente.
ZONE: a zona da VM do cliente.
Receba o endereço IP do balanceador de carga.
Para conseguir o endereço IPv6, use o seguinte comando:
Agora que você configurou o balanceador de carga, é possível testar a implantação
enviando tráfego para o endereço IP dele. Pode levar alguns minutos para que a configuração do balanceador de carga seja propagada após a primeira implantação.
Conecte-se à instância da VM cliente.
gcloud compute ssh CLIENT_VM_NAME \
--zone=ZONE
Substitua:
CLIENT_VM_NAME: o nome da VM do cliente.
ZONE: a zona da VM do cliente.
Receba o endereço IP do balanceador de carga.
Para encontrar o endereço IPv4, use o seguinte comando:
Substitua IPV4_FORWARDING_RULE_NAME pelo nome da regra de encaminhamento IPv4.
Enviar tráfego ao balanceador de carga
Em clientes com conectividade IPv4, execute o seguinte comando:
curl -m 10 -s http://LB_IPV4_ADDRESS:80
Substitua LB_IPV4_ADDRESS pelo endereço IPv4 do
balanceador de carga.
Testar o balanceador de carga TCP externo
Enviar tráfego IPv6 para o balanceador de carga
Agora que você configurou o balanceador de carga, é possível testar a implantação
enviando tráfego para o endereço IP dele. Pode levar alguns minutos para que a configuração do balanceador de carga seja propagada após a primeira implantação.
Anote o endereço IP do balanceador de carga.
Para conseguir o endereço IPv6, use o seguinte comando:
Substitua IPV6_FORWARDING_RULE_NAME pelo nome da regra de encaminhamento IPv6.
Envie tráfego para o balanceador de carga usando curl para contatar o endereço
IP dele.
Em clientes com conectividade IPv6, execute o seguinte comando:
while true; do curl -m1 http://LB_IPV6_ADDRESS; done
Substitua LB_IPV6_ADDRESS pelo endereço IPv6 do
balanceador de carga.
Por exemplo, se o endereço IPv6 atribuído for
[2001:db8:1:1:1:1:1:1/96]:80, o comando será semelhante a este:
while true; do curl -m1 http://[2001:db8:1:1:1:1:1:1]:80; done
Observe o texto retornado pelo comando curl. O nome da VM de back-end
que gera a resposta é exibido nesse texto. Por exemplo: Page served
from: VM_NAME.
A resposta do comando curl alterna aleatoriamente entre as instâncias de
back-end. Se ocorrer falha na resposta, aguarde
cerca de 30 segundos para que a configuração seja totalmente carregada e
as instâncias sejam marcadas como íntegras antes de tentar novamente:
Enviar tráfego IPv4 para o balanceador de carga
Agora que você configurou o balanceador de carga, é possível testar a implantação
enviando tráfego para o endereço IP dele. Pode levar alguns minutos para que a configuração do balanceador de carga seja propagada após a primeira implantação.
Anote o endereço IP do balanceador de carga.
Para encontrar o endereço IPv4, use o seguinte comando:
Substitua IPV4_FORWARDING_RULE_NAME pelo nome da regra de encaminhamento IPv4.
Envie tráfego para o balanceador de carga usando curl para contatar o endereço
IP dele.
Em clientes com conectividade IPv4, execute o seguinte comando:
while true; do curl -m1 LB_IPV4_ADDRESS; done
Substitua LB_IPV4_ADDRESS pelo endereço IPv4 do
balanceador de carga.
Observe o texto retornado pelo comando curl. O nome da VM de back-end
que gera a resposta é exibido nesse texto. Por exemplo: Page served
from: VM_NAME.
A resposta do comando curl alterna aleatoriamente entre as instâncias de
back-end. Se ocorrer falha na resposta, aguarde
cerca de 30 segundos para que a configuração seja totalmente carregada e
as instâncias sejam marcadas como íntegras antes de tentar novamente:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-04 UTC."],[],[],null,["# Test shared how-to NetLB test modules\n\nTest internal TCP LB\n--------------------\n\n### Create client VM\n\nThis example creates a client VM in the same region as the backends. You then\nsend traffic from the client to the load balancer.\n\nThe client VM can be in any zone in the same region as the load balancer, and it\ncan use any subnet in that region. \n\n### Console\n\n1. In the Google Cloud console, go to the **VM instances** page.\n\n [Go to VM instances](https://console.cloud.google.com/compute/instances)\n2. Click **Create instance**.\n\n3. In the **Name** field, enter a name.\n\n4. For **Region**, select the same region as the load balancer.\n\n5. For **Zone**, select a zone.\n\n6. Click **Networking**.\n\n7. Configure the following fields and click **Done**:\n\n - For **Network tags** , enter `allow-ssh`.\n - For **Network interfaces**, select a network and a subnet. You can use the same network and subnet as the backends.\n - For **IP stack type** , choose **IPv6 (single-stack)**.\n8. Click **Create**.\n\n### gcloud\n\n```\ngcloud compute instances create CLIENT_VM_NAME \\\n --zone=ZONE \\\n --image-family=debian-12 \\\n --image-project=debian-cloud \\\n --stack-type=IPV6_ONLY \\\n --tags=allow-ssh \\\n --subnet=SUBNET\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eCLIENT_VM_NAME\u003c/var\u003e: the name of the client VM.\n- \u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e: the zone for the client VM. This zone must be in the same region as the load balancer.\n- \u003cvar translate=\"no\"\u003eSUBNET\u003c/var\u003e: the subnet for the client VM.\n\n### Send IPv6 traffic to the load balancer\n\nNow that you have configured your load balancer, you can test your deployment by\nsending traffic to the load balancer's IP address. It might take a few minutes\nfor the load balancer configuration to propagate after you first deploy it.\n\n1. Connect to the client VM instance.\n\n ```\n gcloud compute ssh CLIENT_VM_NAME \\\n --zone=ZONE\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eCLIENT_VM_NAME\u003c/var\u003e: the name of the client VM.\n - \u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e: the zone of the client VM.\n2. Get the IP address of the load balancer.\n\n To get the IPv6 address, use the following command. \n\n ```\n gcloud compute forwarding-rules describe IPV6_FORWARDING_RULE_NAME \\\n --region=REGION\n ```\n\n Replace \u003cvar translate=\"no\"\u003eIPV6_FORWARDING_RULE_NAME\u003c/var\u003e with the name of the\n IPv6 forwarding rule.\n3. Send traffic to the load balancer.\n\n From clients with IPv6 connectivity, run the following command: \n\n ```\n curl -m 10 -s http://LB_IPV6_ADDRESS:80\n ```\n\n Replace \u003cvar translate=\"no\"\u003eLB_IPV6_ADDRESS\u003c/var\u003e with the IPv6 address of the\n load balancer.\n\n For example, if the assigned IPv6 address is\n `[fd20:1db0:b882:802:0:46:0:0/96]:80`, the command should look like: \n\n ```\n curl -m 10 -s http://[fd20:1db0:b882:802:0:46:0:0]:80\n ```\n\n### Send IPv4 traffic to the load balancer\n\nNow that you have configured your load balancer, you can test your deployment by\nsending traffic to the load balancer's IP address. It might take a few minutes\nfor the load balancer configuration to propagate after you first deploy it.\n\n1. Connect to the client VM instance.\n\n ```\n gcloud compute ssh CLIENT_VM_NAME \\\n --zone=ZONE\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eCLIENT_VM_NAME\u003c/var\u003e: the name of the client VM.\n - \u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e: the zone of the client VM.\n2. Get the IP address of the load balancer.\n\n To get the IPv4 address, use the following command. \n\n ```\n gcloud compute forwarding-rules describe IPV4_FORWARDING_RULE_NAME \\\n --region=REGION\n ```\n\n Replace \u003cvar translate=\"no\"\u003eIPV4_FORWARDING_RULE_NAME\u003c/var\u003e with the name of the\n IPv4 forwarding rule.\n3. Send traffic to the load balancer.\n\n From clients with IPv4 connectivity, run the following command: \n\n ```\n curl -m 10 -s http://LB_IPV4_ADDRESS:80\n ```\n\n Replace \u003cvar translate=\"no\"\u003eLB_IPV4_ADDRESS\u003c/var\u003e with the IPv4 address of the\n load balancer.\n\nTest external TCP LB\n--------------------\n\n### Send IPv6 traffic to the load balancer\n\nNow that you have configured your load balancer, you can test your deployment by\nsending traffic to the load balancer's IP address. It might take a few minutes\nfor the load balancer configuration to propagate after you first deploy it.\n\n1. Get the load balancer's IP address.\n\n To get the IPv6 address, use the following command. \n\n ```\n gcloud compute forwarding-rules describe IPV6_FORWARDING_RULE_NAME \\\n --region=REGION\n ```\n\n Replace \u003cvar translate=\"no\"\u003eIPV6_FORWARDING_RULE_NAME\u003c/var\u003e with the name of the\n IPv6 forwarding rule.\n2. Send traffic to your load balancer by using `curl` to contact its IP\n address.\n\n From clients with IPv6 connectivity, run the following command: \n\n ```\n while true; do curl -m1 http://LB_IPV6_ADDRESS; done\n ```\n\n Replace \u003cvar translate=\"no\"\u003eLB_IPV6_ADDRESS\u003c/var\u003e with the IPv6 address of the\n load balancer.\n\n For example, if the assigned IPv6 address is\n `[2001:db8:1:1:1:1:1:1/96]:80`, the command is similar to the following: \n\n ```\n while true; do curl -m1 http://[2001:db8:1:1:1:1:1:1]:80; done\n ```\n\n Note the text returned by the `curl` command. The name of the backend VM\n generating the response is displayed in that text; for example: `Page served\n from: `\u003cvar translate=\"no\"\u003eVM_NAME\u003c/var\u003e.\n\n The response from the `curl` command alternates randomly among the backend\n instances. If your response is initially unsuccessful, you might need to wait\n approximately 30 seconds for the configuration to be fully loaded and for\n your instances to be marked healthy before trying again.\n\n### Send IPv4 traffic to the load balancer\n\nNow that you have configured your load balancer, you can test your deployment by\nsending traffic to the load balancer's IP address. It might take a few minutes\nfor the load balancer configuration to propagate after you first deploy it.\n\n1. Get the load balancer's IP address.\n\n To get the IPv4 address, use the following command. \n\n ```\n gcloud compute forwarding-rules describe IPV4_FORWARDING_RULE_NAME \\\n --region=REGION\n ```\n\n Replace \u003cvar translate=\"no\"\u003eIPV4_FORWARDING_RULE_NAME\u003c/var\u003e with the name of the\n IPv4 forwarding rule.\n2. Send traffic to your load balancer by using `curl` to contact its IP\n address.\n\n From clients with IPv4 connectivity, run the following command: \n\n ```\n while true; do curl -m1 LB_IPV4_ADDRESS; done\n ```\n\n Replace \u003cvar translate=\"no\"\u003eLB_IPV4_ADDRESS\u003c/var\u003e with the IPv4 address of the\n load balancer.\n\n Note the text returned by the `curl` command. The name of the backend VM\n generating the response is displayed in that text; for example: `Page served\n from: `\u003cvar translate=\"no\"\u003eVM_NAME\u003c/var\u003e.\n\n The response from the `curl` command alternates randomly among the backend\n instances. If your response is initially unsuccessful, you might need to wait\n approximately 30 seconds for the configuration to be fully loaded and for\n your instances to be marked healthy before trying again."]]
