Earlier this year around the March timeframe, I published a white paper providing network configuration guidance for deploying Virtual SAN across L2 and L3 networks. In the white paper, I covered all of the necessary configuration artifacts required to prepare and build a routed network for the deployment of Virtual SAN. In the paper, I provided all of the required configuration examples for all of the necessary networking devices (L2 and L3 devices) for two different vendors (Cisco and Brocade)
My intentions for the article and the paper was to provide prescriptive guidance for the preparation and configuration of the network infrastructure to support the deployment of Virtual SAN over across routed and non-routed networks based on two of the most utilized/popular networking vendors in the industry today and their respective devices.
My original intentions were to use three vendors and provide the configuration examples for all three vendors (Cisco, Brocade Arista). At the time of the publishing of the paper, I wasn’t able to include in the Arista configuration in the paper at the time of the original publishing. Well, thanks to David Boone, a member of the Virtual SAN solutions architecture team who recently reminded me of the Arista configuration. The Arista configurations examples listed below follow the logical infrastructure scenario defined in the VMware Virtual SAN Layer 2 and Layer 3 Network Topology Deployments white paper.
The Arista configuration examples are based on the logical design and infrastructure covered in the VMware Virtual SAN Layer 2 and Layer 3 Network Topology Deployments white paper. For further information and full context and details, please download the white paper from the provided link above.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 |
Layer 2 Network Configuration Switch 1 (S1) conf t ip igmp snooping vlan 172 name Private-vsan ip igmp snooping vlan 172 static 224.1.2.3 ip igmp snooping vlan 172 static 224.2.3.4 Switch 2 (S2) conf t ip igmp snooping vlan 172 name Private-vsan ip igmp snooping vlan 172 querier address 172.16.10.253 ip igmp snooping querier ip igmp snooping vlan 172 static 224.1.2.3 ip igmp snooping vlan 172 static 224.2.3.4 Switch 3 (S3) conf t ip igmp snooping vlan 172 name Private-vsan ip igmp snooping vlan 172 static 224.1.2.3 ip igmp snooping vlan 172 static 224.2.3.4 WITH ROUTERS S1 conf t ip igmp snooping vlan 172 name Private-vsan ip igmp snooping vlan 172 ip igmp snooping vlan 172 S2 conf t ip igmp snooping vlan 192 name Private-vsan ip igmp snooping vlan 192 ip igmp snooping vlan 192 S3 conf t ip igmp snooping vlan 10 name Private-vsan ip igmp snooping vlan 10 ip igmp snooping vlan 10 Layer 3 Network Configuration Configuration on Router #1 using PIM sparse mode and static RP: Note: This example assumes unicast routing between the subnets configured on individual routers is established using OSPF on Area 0. Switch Model: Arista DCS-7050S-64-R EOS Version: 4.14.7M Router process ID: 9 OSPF Area: 0 Rendezvous Point: Router 2, Loopback 0 Router 1 (R1) conf t ip pim rp-address 2.2.2.2 override (To enforce static over dynamic RP) ip pim rp-address 2.2.2.2 224.1.2.3/32 ip pim rp-address 2.2.2.2 224.1.2.3/32 interface vlan 172 ip address 172.16.10.253/24 ip pim sparse-mode sg-expiry-timer 120 router ospf 9 interface loopback 0 ip address 1.1.1.1/32 ip pim sparse-mode sg-expiry-timer 120 router ospf 9 exit router ospf 9 router-id X.X.X.X passive-interface Vlan172 passive-interface loopback0 (If Loopback 0 is not the interface where the OSPF adjacency is formed and used for LSA exchange) redistribute connected area 0.0.0.0 network 172.16.10.0/24 area 0.0.0.0 network X.X.X.X area 0.0.0.0 (The interface used for OSPF adjancency and will be the same one as router-id) max-lsa 12000 ! Router 2 (R2) conf t ip multicast-routing ip mfib activity polling-interval 5 ip pim rp-address 2.2.2.2 override (To enforce static over dynamic RP) ip pim rp-address 2.2.2.2 224.1.2.3/32 ip pim rp-address 2.2.2.2 224.1.2.3/32 interface vlan 192 ip address 192.16.10.253/24 ip pim sparse-mode sg-expiry-timer 120 router ospf 9 interface loopback 0 ip address 2.2.2.2/32 ip pim sparse-mode sg-expiry-timer 120 router ospf 9 exit router ospf 9 router-id X.X.X.X passive-interface Vlan192 passive-interface loopback0 (If Loopback 0 is not the interface where the OSPF adjacency is formed and used for LSA exchange) redistribute connected area 0.0.0.0 network 192.16.10.0/24 area 0.0.0.0 network X.X.X.X area 0.0.0.0 (The interface used for OSPF adjancency and will be the same one as router-id) max-lsa 12000 ! Router 2 (R2) conf t ip pim rp-address 2.2.2.2 override (To enforce static over dynamic RP) ip pim rp-address 2.2.2.2 224.1.2.3/32 ip pim rp-address 2.2.2.2 224.1.2.3/32 interface vlan 10 ip address 10.16.10.253/24 ip pim sparse-mode sg-expiry-timer 120 router ospf 9 interface loopback 0 ip address 3.3.3.3/32 ip pim sparse-mode sg-expiry-timer 120 router ospf 9 exit router ospf 9 router-id X.X.X.X passive-interface Vlan10 passive-interface loopback0 (If Loopback 0 is not the interface where the OSPF adjacency is formed and used for LSA exchange) redistribute connected area 0.0.0.0 network 10.16.10.0/24 area 0.0.0.0 network X.X.X.X area 0.0.0.0 (The interface used for OSPF adjancency and will be the same one as router-id) max-lsa 12000 ! Note: (1) Assuming VLAN 172 is being used for L2 VSAN. (2) Used an unsed IP in the VLAN as the IGMP querier if no router interface is used as the querier and the VLAN is local to the LAN. This is the case in current example. (3) Subnet: 172.16.10.0/24 (VLAN ID: 172) conf t VLAN 172 name Private-vsan ip igmp snooping vlan 172 querier address 172.16.10.253 ip igmp snooping querier ip igmp snooping vlan 172 static 224.1.2.3 interface ethernet INTERFACE_RANGE (Optional, if the host uplink ports on the switch are identified and need to be manually configured with allotted MCAST IPs) ip igmp snooping vlan 172 static 224.2.3.4 interface ethernet INTERFACE_RANGE |
-Enjoy
For future updates on Virtual SAN (VSAN), vSphere Virtual Volumes (VVol) and other Storage and Availability technologies, as well as vSphere Integrated OpenStack (VIO), and Cloud-Native Applications (CNA) be sure to follow me on Twitter: @PunchingClouds.
