Home > Networking Solutions > Converged and Hyperconverged Solutions > VxRail Networking Solutions > Guides > Dell EMC Networking SmartFabric Services Deployment with VxRail 7.0 > Additional configuration steps for L3 uplinks
Note: If using L2 uplinks, skip this section and go to Validate and build VxRail cluster.
Traffic on the External Management network, VLAN 1811, must be able to reach the DNS server on the external network during VxRail deployment. To accomplish this with L3 uplinks, an IP address is assigned to each leaf switch on virtual network 1811. An anycast gateway address shared by all leafs is also configured on the same network.
Since this is on virtual network 1811, available IP addresses in the 172.18.11.0/24 address block are used per the planning data in Table 3.
Table 10. Leaf switch External Management network IP addresses and anycast gateway
Item |
IP address/prefix |
Leaf1A IP address |
172.18.11.253/24 |
Leaf1B IP address |
172.18.11.252/24 |
Gateway IP address |
172.18.11.254/24 |
Note: If present, additional leaf switches in the fabric will also need one IP address per leaf on this network.
The IP addresses and gateway are configured as follows:
Figure 54. Update network configuration window
Note: When IPv4 is selected, additional fields appear, as shown in Figure 55.
Note: If you plan to expand the fabric, additional leaf switches will also need IP addresses on this network, with one IP address per leaf. This is covered in Expand SmartFabric and VxRail cluster to multi-rack.
When complete, the Update Network Configuration window appears, as shown in Figure 55.
Figure 55. Update network configuration window
Note: If static routes are used, proceed to the Validate and build VxRail cluster section. (Static route validation was done earlier in the Validate static route example section of this guide).
If BGP is used on the uplinks, ensure the external switches have learned the routes to the VxRail External Management network, 172.18.11.0/24 in this example, to reach the VxRail nodes and VxRail Manager. This is done with the show ip route command. The BGP-discovered route to 172.18.11.0/24 is shown in bold in the output below.
Note: The command output shown is for the External-A switch. The output for External-B is similar. BGP verification from the leaf switches was done in Show command output on Leaf1A (BGP example).
Note: Command output from a Cisco Nexus switch is shown in Appendix C: BGP validation on N9K-External-A during VxRail deployment.
External-A# show ip route
Codes: C - connected
S - static
B - BGP, IN - internal BGP, EX - external BGP
O - OSPF, IA - OSPF inter area, N1 - OSPF NSSA external type 1,
N2 - OSPF NSSA external type 2, E1 - OSPF external type 1,
E2 - OSPF external type 2, * - candidate default,
+ - summary route, > - non-active route
Gateway of last resort is not set
Destination Gateway Dist/Metric Change
----------------------------------------------------------------------------------
C 10.0.2.1/32 via 10.0.2.1 loopback0 0/0 18:36:55
B IN 10.0.2.2/32 via 192.168.3.21 200/0 18:16:18
C 172.19.11.0/24 via 172.19.11.252 vlan1911 0/0 18:29:16
B EX 172.18.11.0/24 via 192.168.1.1 20/0 16:02:33
via 192.168.1.3
C 192.168.1.0/31 via 192.168.1.0 ethernet1/1/21 0/0 21:10:53
C 192.168.1.2/31 via 192.168.1.2 ethernet1/1/22 0/0 18:36:56
B IN 192.168.2.0/31 via 192.168.3.21 200/0 21:10:51
B IN 192.168.2.2/31 via 192.168.3.21 200/0 18:16:18
C 192.168.3.20/31 via 192.168.3.20 vlan4000 0/0 18:29:12