Hi, Today, I want to create a Network Pool in the vCloud Director.
What is Network Pool?
A network pool is a collection of isolated layer-2 network segments that you can use to create vApp networks and certain types of organization VDC networks on demand.
Network pools must be created before organization VDC networks and vApp networks. If they do not exist, the only network option available to an organization is the direct connection to an external network.
Only a system administrator can create a network pool.
Port Groups Backed
VLAN ID Backed
Geneve Backed (NSX-T Overlay Transport Zone)
VXLAN Backed (NSX-V)
Each organization VDC can have one Network Pool
Multiple organization VDC can share a Network Pool
With VCD 10.3, You can create a provider VDC without any Network Pools.
1-Log into https://vCloud_IP/provider –> Resources –>Network Pools –> NEW
2- Enter a name and description for the new network pool.
3- Select Network Pool Type Geneve Backed
4- Select NSX-T Manager to provide the Geneve transport zone that this network pool will use.
5- Select your Transport Zone that you have created before in NSX-T console.
A tier-0 gateway has downlink connections to tier-1 gateways and external connections to physical networks.
You can configure the HA (high availability) mode of a tier-0 gateway to be active-active or active-standby. The following services are only supported in active-standby mode:
Tier-0 and tier-1 gateways support the following addressing configurations for all interfaces (external interfaces, service interfaces, and downlinks) in both single-tier and multi-tiered topologies.
You can configure the tier-0 gateway to support EVPN (Ethernet VPN).
1- Go to the Networking –> Connectivity –> Tier-0 Gateways –> Add Gateway –> Click Add Tier-0 Gateway.
2- Enter a name for the gateway.
3- Select an HA (high availability) mode.
The default mode is active-active. In the active-active mode, traffic is load balanced across all members. In active-standby mode, all traffic is processed by an elected active member. If the active member fails, a new member is elected to be active.
4- If the HA mode is active-standby, select a failover mode.
If the preferred node fails and recovers, it will preempt its peer and become the active node. The peer will change its state to standby.
If the preferred node fails and recovers, it will check if its peer is the active node. If so, the preferred node will not preempt its peer and will be the standby node.
5- (Optional) Select an NSX Edge cluster.
6- (Optional) Click Additional Settings
In the Internal Transit Subnet field, enter a subnet. This is the subnet used for communication between components within this gateway. The default is 169.254.0.0/24.
In the T0-T1 Transit Subnets field, enter one or more subnets. These subnets are used for communication between this gateway and all tier-1 gateways that are linked to it. After you create this gateway and link a tier-1 gateway to it, you will see the actual IP address assigned to the link on the tier-0 gateway side and on the tier-1 gateway side. The address is displayed in Additional Settings > Router Links on the tier-0 gateway page and the tier-1 gateway page. The default is 100.64.0.0/16.
In the Forwarding Up Timer field, enter a time. The forwarding up timer defines the time in seconds that the router must wait before sending the up notification after the first BGP session is established. This timer (previously known as forwarding delay) minimizes downtime in case of fail-overs for active-active or active-standby configurations of logical routers on NSX Edge that use dynamic routing (BGP). It should be set to the number of seconds an external router (TOR) takes to advertise all the routes to this router after the first BGP/BFD session. The timer value should be directly proportional to the number of northbound dynamic routes that the router must learn. This timer should be set to 0 on single-edge node setups.
7- Click Route Distinguisher for VRF Gateways to configure a route distinguisher admin address. This is only needed for EVPN in Inline mode.
8- (Optional) Click EVPN Settings to configure EVPN.
Select an EVPN mode. The options are:
Inline – In this mode, EVPN handles both data plane and control plane traffic.
Route Server – Available only if this gateway’s HA mode is active-active. In this mode, EVPN handles control plane traffic only.
If EVPN mode is Inline, select an EVPN/VXLAN VNI pool or create a new pool by clicking the menu icon (3 dots).
If EVPN mode is Route Server, select an EVPN Tenant or create a new EVPN tenant by clicking the menu icon (3 dots).
In the EVPN Tunnel Endpoint field, click Set to add EVPN local tunnel endpoints. For the tunnel endpoint, select an Edge node and specify an IP address. Optionally, you can specify the MTU.
9- To configure route redistribution, click Route Redistribution and Set.
Select one or more of the sources:
Tier-0 subnets: Static Routes, NAT IP, IPsec Local IP, DNS Forwarder IP, EVPN TEP IP, Connected Interfaces & Segments. Under Connected Interfaces & Segments, you can select one or more of the following: Service Interface Subnet, External Interface Subnet, Loopback Interface Subnet, or Connected Segment.
Advertised tier-1 subnets: DNS Forwarder IP, Static Routes, LB VIP, NAT IP, LB SNAT IP, IPSec Local Endpoint, Connected Interfaces & Segments. Under Connected Interfaces & Segments, you can select Service Interface Subnet and/or Connected Segment.
A tier-1 gateway is typically connected to a tier-0 gateway in the northbound direction and to segments in the southbound direction.
1- Go to the Networking–> Connectivity –> Tier-1 Gateways –> Add Tier-1 Gateways
2- Enter a name for the gateway: T1
(Optional) Select a tier-0 gateway to connect to this tier-1 gateway to create a multi-tier topology.
(Optional) Select an NSX Edge cluster if you want this tier-1 gateway to host stateful services such as NAT, load balancer, or firewall. If an NSX Edge cluster is selected, a service router will always be created, affecting the north/south traffic pattern.
I choose Edge-Cluster, Because I want to use load balancer and NAT in future post.
If you selected an NSX Edge cluster, select a failover mode or accept the default.
If the preferred NSX Edge node fails and recovers, it will preempt its peer and become the active node. The peer will change its state to standby.
If the preferred NSX Edge node fails and recovers, it will check if its peer is the active node. If so, the preferred node will not preempt its peer and will be the standby node. This is the default option.
(Optional) Click the Enable Standby Relocation toggle to enable or disable standby relocation. Standby relocation means that if the Edge node where the active or standby logical router is running fails, a new standby logical router is created on another Edge node to maintain high availability. If the Edge node that fails is running the active logical router, the original standby logical router becomes the active logical router and a new standby logical router is created. If the Edge node that fails is running the standby logical router, the new standby logical router replaces it.
(Optional) Click Route Advertisement.
Select one or more of the following:
All Static Routes
All NAT IP’s
All DNS Forwarder Routes
All LB VIP Routes
All Connected Segments and Service Ports
All LB SNAT IP Routes
All IPsec Local Endpoints
(Optional) Click Route Advertisement.
In the Set Route Advertisement Rules field, click Set to add route advertisement rules.
(Optional) Click Service Interfaces and Set to configure connections to segments. Required in some topologies, such as VLAN-backed segments or one-arm load balancing.
a. Click Add Interface.
b. Enter a name and IP address in CIDR format.
c. Select a segment.
d. In the MTU field, enter a value between 64 and 9000.
f. Add one or more tags.
g. In the ND Profile field, select or create a profile.
h. Click Save.
(Optional) Click Static Routes and Set to configure static routes.
a. Click Add Static Route.
b. Enter a name and a network address in the CIDR or IPv6 CIDR format.
c. Click Set Next Hops to add next hop information.
d. Click Save.
(Optional) Click Multicast and then the toggle to enable multicast. You must select an Edge cluster for this gateway. Also, this gateway must be linked to a tier-0 gateway that has multicast enabled.