From 5842b6a3d74bbd1119228d0a4dddba325a375d0f Mon Sep 17 00:00:00 2001 From: Jithin Raju Date: Tue, 18 Feb 2025 16:23:49 +0530 Subject: [PATCH] Adding a note about the usage of tagging Physical Networks Adding a note about the usage of tagging Physical Networks --- source/adminguide/networking/advanced_zone_config.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/source/adminguide/networking/advanced_zone_config.rst b/source/adminguide/networking/advanced_zone_config.rst index 3d8299c819..5915f40fa8 100644 --- a/source/adminguide/networking/advanced_zone_config.rst +++ b/source/adminguide/networking/advanced_zone_config.rst @@ -80,6 +80,7 @@ configure the base guest Network: .. note:: * In security groups-enabled Advanced zones and Basic zones, creation of VPC and isolated Networks are not supported. * MTU options will be shown in the UI and considered only when zone configuration - `allow.end.users.to.specify.vr.mtu` is set to true. Maximum allowed values for public and private MTU can be controlled by zone-level configurations, `vr.public.interface.max.mtu` and `vr.private.interface.max.mtu` respectively. + * We can configure a zone with multiple Physical Networks having guest traffic type. In such zones, we need to tag the additional Physical networks. We must have one Physical Network that is not tagged for isolated/L2 network offerings not configured with any tags. For example the default network offerings. Configure Public Traffic in an Advanced Zone ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~