Meta tags:

Headings (most frequently used words):

roce, vpc, networks, for, supported, and, falcon, instances, metal, rdma, network, profiles, overview, zones, specifications, unsupported, features, multi, nic, considerations, number, of, connections, limit, what, next, vm, bare, products, pricing, support, resources, engage,

Text of the page (most frequently used words):
vpc (203), networks (143), #network (133), for (127), the (122), #support (104), roce (100), instances (91), don (76), cloud (59), and (53), rdma (49), metal (48), private (48), bare (44), falcon (42), access (41), nics (39), google (38), subnets (34), services (31), addresses (30), service (30), overview (30), see (29), instance (27), profile (26), more (25), only (25), with (24), create (23), about (21), nic (21), subnet (21), information (20), interfaces (20), same (19), following (19), that (19), connect (18), purpose (18), supported (17), configure (17), are (16), using (15), routes (15), ipv6 (15), published (14), profiles (13), use (13), have (13), mrdma (13), can (13), attachments (13), ranges (13), manage (12), other (12), address (12), from (12), multi (12), features (12), you (12), add (12), dynamic (12), peering (12), connections (11), firewall (11), static (11), external (11), internal (11), which (11), types (11), connection (10), consequently (10), load (10), connectivity (10), packet (10), mirroring (10), ipv4 (10), apis (10), resources (9), policies (9), nat (9), mode (9), alias (9), nic0 (9), value (9), gce_endpoint (9), all (8), each (8), gpu (8), must (8), created (8), range (8), zone (8), thumb (7), rules (7), regular (7), security (7), hybrid (7), two (6), including (6), backends (6), balancing (6), ncc (6), vpn (6), interconnect (6), connecting (6), auto (6), creation (6), forwarding (6), assigning (6), such (6), attribute (6), used (6), predefined (6), irdma (6), property (6), virtual (6), type (6), regional (6), policy (6), mtu (6), zones (6), center (5), code (5), ngfw (5), count (5), limit (5), when (5), first (5), considerations (5), endpoints (5), migrating (5), between (5), migration (5), reference (5), table (5), vms (5), português (4), español (4), down (4), this (4), details (4), aren (4), rail (4), vnics (4), multiple (4), over (4), cross (4), uses (4), attached (4), resource (4), provided (4), allowing (4), limited (4), set (4), implied (4), machine (4), available (4), view (4), networking (4), tools (4), management (4), application (4), troubleshoot (4), monitor (4), audit (4), logging (4), flow (4), logs (4), port (4), mapping (4), composite (4), health (4), global (4), architecture (3), samples (3), system (3), content (3), send (3), specific (3), destination (3), maximum (3), number (3), has (3), workloads (3), communication (3), data (3), psc_blocked (3), allowpsc (3), private_google_access_blocked (3), allowprivategoogleaccess (3), balancer (3), armor (3), load_balancing_blocked (3), allowloadbalancing (3), spoke (3), hub (3), ncc_blocked (3), allowncc (3), tunnels (3), vpn_blocked (3), allowvpn (3), vlan (3), interconnect_blocked (3), allowinterconnect (3), routers (3), cloud_router_blocked (3), allowcloudrouter (3), router (3), cloud_nat_blocked (3), allowcloudnat (3), packet_mirroring_blocked (3), allowpacketmirroring (3), static_routes_blocked (3), allowstaticroutes (3), vpc_peering_blocked (3), allowvpcpeering (3), auto_mode_subnet_blocked (3), allowautomodesubnet (3), network_migration_blocked (3), allownetworkmigration (3), ip_forwarding_blocked (3), allowipforwarding (3), allowaliasipranges (3), allowpscinterface (3), subinterfaces_blocked (3), allowsubinterfaces (3), internet (3), external_ip_access_blocked (3), allowexternalipaccess (3), configuring (3), attaching (3), not (3), default_nic_attachment_blocked (3), allowdefaultnicattachment (3), special (3), shared_loadbalancer_vip (3), addresspurposes (3), proxy (3), purposes (3), subnet_purpose_private (3), subnetworkpurposes (3), name (3), default (3), dual (3), stack (3), subnetworkstacktypes (3), unique (3), also (3), multi_nic_in_same_network_allowed (3), allowmultinicinsamenetwork (3), virtio_net (3), gvnic (3), interfacetypes (3), feature (3), lists (3), unsupported (3), 8896 (3), compute (3), based (3), your (3), guides (3), serverless (3), traffic (3), routing (3), migrate (3), accessing (3), shared (3), prefixes (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), sign (2), terms (2), site (2), youtube (2), started (2), notes (2), pricing (2), products (2), understand (2), need (2), last (2), updated (2), 2026 (2), utc (2), page (2), licensed (2), under (2), license (2), feedback (2), cases (2), 000 (2), might (2), aligned (2), becomes (2), another (2), queue (2), vnic (2), example (2), source (2), given (2), tuple (2), performance (2), latency (2), nccl (2), through (2), alias_ip_range_blocked (2), psc_interface_blocked (2), ephemeral (2), naming (2), where (2), network_name (2), matches (2), single (2), automatically (2), properties (2), ula_ipv6_range (2), prefix (2), additional (2), described (2), local (2), ula (2), because (2), reserved (2), valid (2), subnet_stack_type_ipv4_only (2), attach (2), interface (2), tests (2), allow (2), different (2), differences (2), bytes (2), zonal (2), specifications (2), a4x (2), running (2), memory (2), documentation (2), sdk (2), languages (2), frameworks (2), infrastructure (2), costs (2), usage (2), storage (2), observability (2), monitoring (2), industry (2), solutions (2), distributed (2), multicloud (2), databases (2), analytics (2), pipelines (2), hosting (2), development (2), legacy (2), advanced (2), tags (2), constraints (2), premises (2), hosts (2), update (2), delete (2), failover (2), own (2), deprovision (2), change (2), byoip (2), sub (2), public (2), reserve (2), console (2), product (2), technology (2), areas (2), close (2), subscribe, newsletter, our, third, decade, climate, action, join, cookies, privacy, tech, twitter, events, blog, engage, training, certification, getting, github, status, release, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, otherwise, noted, java, registered, trademark, oracle, its, affiliates, developers, apache, creative, commons, attribution, what, next, goes, beyond, new, failures, but, existing, impacted, starts, communicator, engaging, opens, pair, remains, communicates, initial, assume, both, routable, established, communicate, time, share, receive, transmit, pairs, per, item, benefit, placing, affect, increased, attempts, align, transfers, even, pxn, copy, nvlink, before, transferring, firewall_policy_blocked, allowfirewallpolicy, vpc_firewall_rules_blocked, allowvpcfirewallrules, either, reserving, address_creation_blocked, allowaddresscreation, creating, subnetwork_creation_blocked, allowsubnetworkcreation, format, exactly, nameprefix, ipv6range, predefinedsubnetworkranges, convention, row, subnet_stack_type_ipv6_only, one, isn, configurable, predefinednetworkinternalipv6range, multi_nic_in_same_subnetwork_allowed, allowmultinicinsamesubnetwork, link, fe80, badd, c0de, cafe, 120, udp, ports, they, 13882, 13895, 3882, 3895, addition, limitations, apply, alias_ip_ranges_allowed, psc_interface_allowed, sections, describe, section, doesn, parameters, within, depends, ingress, egress, then, best, recommend, allows, driver, guest, operating, smaller, mtus, needed, transmission, unit, byte, non, supports, located, region, contains, associated, during, effects, constraint, regions, locations, alternatively, intend, their, list, corresponding, max, ultra, converged, ethernet, h4d, transport, protocol, useful, hypercomputer, let, provide, low, high, bandwidth, gpus, engine, provides, remote, direct, save, categorize, preferences, stay, organized, collections, home, concepts, topics, problems, custom, control, partner, providers, organization, flows, records, producer, overlap, dns, configuration, publish, controlling, producers, consumer, deploy, automation, backend, propagated, consumers, make, accessible, balanced, deployment, patterns, compatibility, choose, option, disable, prepare, provision, peer, spokes, capabilities, dns64, nat64, destinations, verify, jumbo, frame, bgp, announcement, delegated, advertised, planning, bring, move, project, get, discover, start, free, skip, main,

Text of the page (random words):
network profile this allows the rdma driver in the instance s guest operating system to use smaller mtus if needed if you create a vpc network with an rdma network profile then 8896 bytes is the default mtu firewall differences see the following information about firewall differences in vpc networks with an rdma network profile vpc networks with an rdma network profile use the following implied firewall rules which are different from the implied firewall rules used by regular vpc networks implied allow egress implied allow ingress cloud ngfw support depends on the type of vpc network for roce vpc networks see the following roce vpc networks for vm instances only support regional network firewall policies that have an roce firewall policy type the set of parameters for rules within a supported regional network firewall policy are limited for more information see cloud ngfw for roce vpc networks roce vpc networks for bare metal instances don t support configuring cloud ngfw rules or policies falcon vpc networks don t support configuring cloud ngfw rules or policies no connectivity tests support connectivity tests doesn t support vpc networks with an rdma network profile other vpc features vpc networks with an rdma network profile support a limited set of other vpc features for more information see the following supported and unsupported features section supported and unsupported features the following sections describe which vpc features are supported and unsupported for each type of vpc network that you can create by using an rdma network profile falcon vpc networks falcon roce vpc networks for vm instances roce roce vpc networks for bare metal instances roce metal falcon vpc networks falcon the following table lists the features that are supported by falcon vpc networks which are created by using the falcon network profile feature supported network profile property network profile property value details rdma nics interfacetypes irdma falcon vpc networks support only irdma nics other nic types such as mrdma gvnic and virtio_net aren t supported multi nic in the same network allowmultinicinsamenetwork multi_nic_in_same_network_allowed falcon vpc networks support multi nic instances allowing two or more rdma nics of the same instance to be in the same vpc network each nic must attach to a unique subnet in the vpc network ipv4 only subnets subnetworkstacktypes subnet_stack_type_ipv4_only falcon vpc networks support ipv4 only subnets including the same valid ipv4 ranges as regular vpc networks falcon vpc networks don t support dual stack or ipv6 only subnets for more information see types of subnets private subnet purpose subnetworkpurposes subnet_purpose_private falcon vpc networks support regular subnets which have a purpose attribute value of private falcon vpc networks don t support private service connect subnets proxy only subnets or private nat subnets for more information see purposes of subnets gce_endpoint address purpose addresspurposes gce_endpoint falcon vpc networks support ip addresses with a purpose attribute value of gce_endpoint which is used by internal ip addresses of instance nics falcon vpc networks don t support special purpose ip addresses such as the shared_loadbalancer_vip purpose for more information see the addresses resource reference private service connect interfaces allowpscinterface psc_interface_allowed falcon vpc networks support network attachments and connections from virtual private service connect interfaces dynamic network interfaces allowsubinterfaces subinterfaces_blocked falcon vpc networks don t support dynamic nics attachments from nic0 allowdefaultnicattachment default_nic_attachment_blocked falcon vpc networks don t support attaching the nic0 network interface of an instance to the network each rdma nic attached to the vpc network must not be nic0 external ip addresses for instances allowexternalipaccess external_ip_access_blocked falcon vpc networks don t support assigning external ip addresses to rdma nics consequently rdma nics don t have internet access alias ip ranges allowaliasipranges alias_ip_range_blocked falcon vpc networks don t support assigning alias ip ranges to rdma nics ip forwarding allowipforwarding ip_forwarding_blocked falcon vpc networks don t support ip forwarding instance network migration allownetworkmigration network_migration_blocked falcon vpc networks don t support migrating instance nics between networks auto mode allowautomodesubnet auto_mode_subnet_blocked falcon vpc networks can t be auto mode networks for more information see subnet creation mode vpc network peering allowvpcpeering vpc_peering_blocked falcon vpc networks don t support connecting to other vpc networks using vpc network peering consequently falcon vpc networks don t support connecting to services using private services access static routes allowstaticroutes static_routes_blocked falcon vpc networks don t support static routes packet mirroring allowpacketmirroring packet_mirroring_blocked falcon vpc networks don t support packet mirroring cloud nat allowcloudnat cloud_nat_blocked falcon vpc networks don t support cloud nat cloud router allowcloudrouter cloud_router_blocked falcon vpc networks don t support cloud routers and dynamic routes cloud interconnect allowinterconnect interconnect_blocked falcon vpc networks don t support cloud interconnect vlan attachments cloud vpn allowvpn vpn_blocked falcon vpc networks don t support cloud vpn tunnels network connectivity center allowncc ncc_blocked falcon vpc networks don t support ncc you can t add a falcon vpc network as a vpc spoke to a ncc hub cloud load balancing allowloadbalancing load_balancing_blocked falcon vpc networks don t support cloud load balancing consequently falcon vpc networks don t support load balancer features including google cloud armor private google access allowprivategoogleaccess private_google_access_blocked falcon vpc networks don t support private google access private service connect allowpsc psc_blocked falcon vpc networks don t support private service connect published services endpoints or backends roce vpc networks for vm instances roce the following table lists the features that are supported by roce vpc networks for vm instances which are created by using the roce network profile feature supported network profile property network profile property value details rdma nics interfacetypes mrdma roce vpc networks for vm instances support only mrdma nics other nic types such as irdma gvnic and virtio_net aren t supported multi nic in the same network allowmultinicinsamenetwork multi_nic_in_same_network_allowed roce vpc networks for vm instances support multi nic instances allowing two or more rdma nics of the same instance to be in the same vpc network each nic must attach to a unique subnet in the vpc network see also roce vpc network multi nic considerations ipv4 only subnets subnetworkstacktypes subnet_stack_type_ipv4_only roce vpc networks for vm instances support ipv4 only subnets including the same valid ipv4 ranges as regular vpc networks roce vpc networks for vm instances don t support dual stack or ipv6 only subnets for more information see types of subnets private subnet purpose subnetworkpurposes subnet_purpose_private roce vpc networks for vm instances support regular subnets which have a purpose attribute value of private roce vpc networks for vm instances don t support private service connect subnets proxy only subnets or private nat subnets for more information see purposes of subnets gce_endpoint address purpose addresspurposes gce_endpoint roce vpc networks for vm instances support ip addresses with a purpose attribute value of gce_endpoint which is used by internal ip addresses of instance nics roce vpc networks for vm instances don t support special purpose ip addresses such as the shared_loadbalancer_vip purpose for more information see the addresses resource reference alias ip ranges allowaliasipranges alias_ip_ranges_allowed roce vpc networks for vm instances support assigning alias ip ranges to mrdma nics for more information see considerations for roce vpc networks in the alias ip ranges overview attachments from nic0 allowdefaultnicattachment default_nic_attachment_blocked roce vpc networks for vm instances don t support attaching the nic0 network interfaces of an instance to the network each rdma nic attached to the vpc network must not be nic0 external ip addresses for instances allowexternalipaccess external_ip_access_blocked roce vpc networks for vm instances don t support assigning external ip addresses to rdma nics consequently rdma nics don t have internet access dynamic network interfaces allowsubinterfaces subinterfaces_blocked roce vpc networks for vm instances don t support dynamic nics private service connect interfaces allowpscinterface psc_interface_blocked roce vpc networks don t support network attachments or connections from private service connect interfaces ip forwarding allowipforwarding ip_forwarding_blocked roce vpc networks for vm instances don t support ip forwarding instance network migration allownetworkmigration network_migration_blocked roce vpc networks for vm instances don t support migrating instance nics between networks auto mode allowautomodesubnet auto_mode_subnet_blocked roce vpc networks for vm instances can t be auto mode networks for more information see subnet creation mode vpc network peering allowvpcpeering vpc_peering_blocked roce vpc networks for vm instances don t support connecting to other vpc networks using vpc network peering consequently roce vpc networks for vm instances don t support connecting to services using private services access static routes allowstaticroutes static_routes_blocked roce vpc networks for vm instances don t support static routes packet mirroring allowpacketmirroring packet_mirroring_blocked roce vpc networks for vm instances don t support packet mirroring cloud nat allowcloudnat cloud_nat_blocked roce vpc networks for vm instances don t support cloud nat cloud router allowcloudrouter cloud_router_blocked roce vpc networks for vm instances don t support cloud routers and dynamic routes cloud interconnect allowinterconnect interconnect_blocked roce vpc networks for vm instances don t support cloud interconnect vlan attachments cloud vpn allowvpn vpn_blocked roce vpc networks for vm instances don t support cloud vpn tunnels network connectivity center allowncc ncc_blocked roce vpc networks for vm instances don t support ncc you can t add a vpc network with an rdma network profile as a vpc spoke to a ncc hub cloud load balancing allowloadbalancing load_balancing_blocked roce vpc networks for vm instances don t support cloud load balancing consequently roce vpc networks for vm instances don t support load balancer features including google cloud armor private google access allowprivategoogleaccess private_google_access_blocked roce vpc networks for vm instances don t support private google access private service connect allowpsc psc_blocked roce vpc networks don t support private service connect published services endpoints or backends roce vpc networks for bare metal instances roce metal the following table lists the features that are supported by roce vpc networks for bare metal instances which are created by using the roce metal network profile in addition to the properties described in the table see the following limitations that apply to gpu bare metal instances gpu bare metal instances can t use the following udp ports in roce vpc networks because they are reserved by google cloud 3882 3895 and 13882 13895 gpu bare metal instances can t use the following ipv6 link local address range because it is reserved by google cloud fe80 badd c0de cafe 0 120 feature supported network profile property network profile property value details rdma nics interfacetypes mrdma roce vpc networks for bare metal instances support only mrdma nics other nic types such as irdma gvnic and virtio_net aren t supported multi nic in the same network allowmultinicinsamenetwork multi_nic_in_same_network_allowed roce vpc networks for bare metal instances support multi nic instances allowing two or more rdma nics of the same instance to be in the same vpc network see also roce vpc network multi nic considerations multi nic in the same subnet allowmultinicinsamesubnetwork multi_nic_in_same_subnetwork_allowed roce vpc networks for bare metal instances support multi nic instances allowing two or more rdma nics of the same instance to be in the same subnet of a vpc network see also roce vpc network multi nic considerations predefined network ula ipv6 range predefinednetworkinternalipv6range ula_ipv6_range roce vpc networks for bare metal instances support internal ipv6 and have a predefined 48 unique local address ula range the predefined range is provided by google cloud for each network profile instance and isn t configurable one ipv6 only subnet subnetworkstacktypes subnet_stack_type_ipv6_only roce vpc networks for bare metal instances support a single automatically provided ipv6 only subnet that uses a predefined ipv6 subnet range and naming convention as described in the following table row roce vpc networks for bare metal instances don t support dual stack or ipv4 only subnets or the creation of additional ipv6 only subnets for more information see types of subnets predefined ipv6 subnet range and name prefix predefinedsubnetworkranges ipv6range ula_ipv6_range nameprefix default subnet 1 roce vpc networks for bare metal instances have a single subnet that is automatically provided and has the following properties the subnet uses a predefined 48 ipv6 range that exactly matches the network s 48 range the subnet uses the following naming format default subnet 1 network_name where network_name is the name that you provided when you created the network private subnet purpose subnetworkpurposes subnet_purpose_private roce vpc networks for bare metal instances support regular subnets which have a purpose attribute value of private roce vpc networks for bare metal instances don t support private service connect subnets proxy only subnets or private nat subnets for more information see purposes of subnets gce_endpoint address purpose addresspurposes gce_endpoint roce vpc networks for bare metal instances support ip addresses with a purpose attribute value of gce_endpoint which is used by internal ip addresses of instance nics roce vpc networks for bare metal instances don t support special purpose ip addresses such as the shared_loadbalancer_vip purpose for more information see the addresses resource reference subnet creation allowsubnetworkcreation subnetwork_creation_blocked roce vpc networks for bare metal instances don t support creating subnets in the network attachments from nic0 allowdefaultnicattachment default_nic_attachment_blocked roce vpc networks for bare metal instances don t support attaching the nic0 network interfaces of a...