BGP 세션에 사용할 수 있는 IPv4 및 IPv6 주소는 사용하는 제품에 따라 달라집니다. 자세한 내용은 BGP 피어링 주소를 참조하세요.
resource.bgp.asn 필드의 값이 잘못됨
다음 오류가 발생할 수 있습니다.
'resource.bgp.asn 필드의 값이 잘못됨: ######.
로컬 ASN이 동일한 리전 및 네트워크의 라우터가 지정한 피어 ASN과 충돌합니다.'
Cloud Router가 Cloud Router와 동일한 ASN을 가진 온프레미스 기기와의 BGP 세션 설정을 시도하고 있습니다. 이 문제를 해결하려면 기기 또는 Cloud Router의 ASN을 변경하세요.
IPv6 BGP 세션 설정 실패
IPv6 BGP 피어와의 연결을 설정하는 데 문제가 있는 경우 다음을 수행합니다.
해당 VLAN 연결 또는 HA VPN 터널이 구성되었는지 확인합니다.
VLAN 연결 또는 HA VPN 게이트웨이에 IPV4_IPV6의 필수 스택 유형이 있는지 확인합니다.
VLAN 연결에 대한 스택 유형이 잘못된 경우 VLAN 연결을 수정합니다. HA VPN 게이트웨이의 경우 HA VPN 게이트웨이 및 터널을 다시 만듭니다.
Cloud Router가 올바르게 구성되었는지, 온프레미스 라우터가 일치하는 IPv6 BGP 주소로 구성되어 있는지 확인합니다.
다음 명령어를 실행합니다.
gcloud compute routers describe ROUTER-NAME
명령어 출력에서 다음 값을 확인합니다.
bgpPeers.peerIpAddress는 온프레미스 라우터의 외부 인터페이스에 할당된 IPv6 주소입니다. 이 IPv6 주소는 HA VPN 터널 또는 Dedicated Interconnect VLAN 연결을 위해 Cloud Router와 BGP 피어링 주소로 사용됩니다.
bgpPeers.ipAddress는 Cloud Router의 인터페이스에 할당된 IPv6 주소이며 온프레미스 라우터에 피어 BGP IP 주소로 구성된 값과 일치합니다.
bgpPeers.peerAsn는 온프레미스 라우터의 ASN과 일치합니다.
bgp.asn은 온프레미스 라우터에 구성된 피어 ASN과 일치합니다.
Google Cloud 에서 시작된 BGP 재설정이 라우터에 표시됨
Cloud Router 태스크는 일반적으로 머신 간에 마이그레이션되는 Google Cloud컨트롤 플레인의 소프트웨어 프로세스입니다. 마이그레이션 중에 Cloud Router가 최대 60초 동안 다운될 수 있습니다. 일반적인 마이그레이션으로는 트래픽이 누락되지 않습니다.
Cloud Router는 데이터 경로에 없으며 Layer 3 스위치 역할을 하지 않지만 경로 프로그래밍 관리자 역할을 합니다. 라우팅은 실제로 VLAN 연결 또는 Cloud VPN 터널에서 처리됩니다.
BGP 재설정이 발생하면 Cloud Logging에서 영향을 받는 라우터의 항목을 추가합니다. Logging 로그에서 라우팅 ID를 검색하고 textPayload="Router Event: Router task activated 키를 사용하여 이벤트를 찾을 수 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-05(UTC)"],[],[],null,["# Troubleshoot BGP sessions\n=========================\n\nThis guide is for troubleshooting BGP sessions, such as BGP sessions that fail\nto establish and BGP resets.\n\nFor additional troubleshooting information, see the following:\n\n- [Troubleshoot BGP peering](/network-connectivity/docs/router/support/troubleshoot-bgp-peering)\n- [Troubleshoot BGP routes and route\n selection](/network-connectivity/docs/router/support/troubleshoot-bgp-routes)\n- [Troubleshoot Cloud Router log messages](/network-connectivity/docs/router/support/troubleshoot-log-messages)\n\nBGP session failed to establish\n-------------------------------\n\nCheck that the settings on your on-premises BGP router and the settings on\nyour Cloud Router are correct. For detailed information, view the\nCloud Router [logs](/network-connectivity/docs/router/how-to/viewing-logs-metrics).\n\nIf you're creating a Cloud VPN tunnel, check that the\n[status of the tunnel](/network-connectivity/docs/router/how-to/viewing-router-details) is\n`ESTABLISHED`. If it isn't, to troubleshoot the issue, see\n[Cloud VPN troubleshooting](/network-connectivity/docs/vpn/support/troubleshooting).\n\nIPv4 and IPv6 addresses for BGP sessions\n----------------------------------------\n\nSupport for IPv6 BGP sessions is in\n[Preview](/products#product-launch-stages).\n\nThe IPv4 and IPv6 addresses that you can use for a BGP session depend on the\nproduct you use. For complete details, see [BGP peering\naddresses](/network-connectivity/docs/router/how-to/configuring-bgp#bgp-peering-addresses).\n\nInvalid value for the field `resource.bgp.asn`\n----------------------------------------------\n\nYou may get the following error:\n\n*\"Invalid value for field `resource.bgp.asn`: `######`.\nLocal ASN conflicts with peer ASN specified by a router in the same region\nand network.\"*\n\nThe Cloud Router is attempting to establish a BGP session with an\non-premises device that has the same ASN as the Cloud Router. To resolve\nthis issue, change the ASN of your device or Cloud Router.\n\nIPv6 BGP session fails to establish\n-----------------------------------\n\nIf you are experiencing difficulty establishing a connection with your IPv6 BGP\npeer, do the following:\n\n1. Verify that the corresponding VLAN attachment or HA VPN\n tunnel is connected.\n\n2. Verify that the VLAN attachment or HA VPN gateway has the\n required stack type of `IPV4_IPV6`.\n\n If the stack type is incorrect for a VLAN attachment, modify\n the VLAN attachment. For a HA VPN gateway, recreate the\n HA VPN gateway and its tunnels.\n\n3. Ensure that the Cloud Router is configured correctly and that your\n on-premises router is configured with the matching IPv6 BGP addresses.\n\n Run the following command: \n\n gcloud compute routers describe ROUTER-NAME\n\n In the command output, check the following values:\n - `bgpPeers.peerIpAddress` is an IPv6 address assigned to the external\n interface on your on-premises router. This IPv6 address is used as the\n BGP peering address with Cloud Router for a\n HA VPN tunnel or a\n Dedicated Interconnect VLAN attachment.\n\n - `bgpPeers.ipAddress` is an IPv6 address assigned to the interface of the\n Cloud Router and matches the value configured as the peer BGP\n IP address on your on-premises router.\n\n - `bgpPeers.peerAsn` matches the ASN of your on-premises router.\n\n - `bgp.asn` matches the peer ASN configured on your on-premises router.\n\nBGP resets that originate from Google Cloud appear on your router\n-----------------------------------------------------------------\n\nCloud Router tasks are software processes in the Google Cloud\ncontrol plane that are normally migrated from machine to machine. During such\nmigrations, the Cloud Router might be down for periods of up to 60\nseconds. Normal migrations don't cause traffic to be dropped.\n\nThe Cloud Router is not located in the data path and is not acting as a\nLayer 3 switch, but as a manager for route programming. Routing is actually\nhandled by the VLAN attachment or the Cloud VPN tunnel.\n\nCloud Logging adds entries for the affected router when BGP resets occur. You\ncan find the events by searching the Logging logs for the routing\nID and using the key `textPayload=\"Router Event: Router task activated`.\n\nFor more information about viewing Logging logs, see [View logs\nand metrics](/network-connectivity/docs/router/how-to/viewing-logs-metrics).\n\nOn-premises router experiences BGP flap\n---------------------------------------\n\nBGP flaps can be caused by various issues, including Cloud Router\n[software maintenance](/network-connectivity/docs/router//concepts/how-cloud-router-works#maintenance).\n\nTo get details about completed maintenance events, see [Identifying router\nmaintenance events](/network-connectivity/docs/router/how-to/identifying-router-events). To get\ndetails about other Cloud Router events, see [Viewing\nCloud Router logs and\nmetrics](/network-connectivity/docs/router/how-to/viewing-logs-metrics).\n\nA Cloud Router maintenance event is not indicative of a problem if your\non-premises router is configured as follows:\n\n- The on-premises router can process graceful restart notifications.\n- The on-premises router's hold timer is set to at least 60 seconds.\n\nFor a comprehensive overview of timer settings, see [Managing BGP\ntimers](/network-connectivity/docs/router/how-to/managing-bgp-timers).\n\nFor help monitoring connectivity, see [Verify connectivity between the\non-premises router and the\nCloud Router](/network-connectivity/docs/router/how-to/identifying-router-events#verify-connectivity).\n\nWhat's next\n-----------\n\n- For more information about how to use Cloud Logging to monitor\n Cloud Router, see\n [View logs and metrics](/network-connectivity/docs/router/how-to/viewing-logs-metrics).\n\n- For additional support, see\n [Getting support](/network-connectivity/docs/router/support/getting-support).\n\n- For information about BGP session states, see\n [BGP session states](/network-connectivity/docs/router/concepts/bgp-states).\n\n- For information about diagnostic messages and session states related to\n Bidirectional Forwarding Detection (BFD), see\n [BFD diagnostic messages and session states](/network-connectivity/docs/router/concepts/bfd-states).\n\n- For issues related to using Cloud Router with Router appliance,\n see\n [Troubleshooting Router appliance](/network-connectivity/docs/network-connectivity-center/support/troubleshooting#troubleshooting-ra)\n in the Network Connectivity Center documentation."]]
