Dell EMC Networking with Isilon Front-End Deployment and Best Practices Guide Dell EMC Networking Infrastructure Solutions June 2018
Revisions Date Rev Description Authors June 2018 1.0 Initial release Gerald Myres, Jordan Wilson The information in this publication is provided “as is.” Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any software described in this publication requires an applicable software license.
Table of contents 1 2 1.1 Typographical conventions .................................................................................................................................7 1.2 Attachments ........................................................................................................................................................7 Hardware overview .......................................................................................................................................
9 A 4 Isilon configuration .....................................................................................................................................................67 9.1 Building the cluster ...........................................................................................................................................67 9.2 Configuring LACP to each node .......................................................................................................................69 9.
1 Introduction Dell EMC Isilon is the leading scale-out network-attached storage (NAS) platform and offers the right blend of performance and capacity to support a wide range of unstructured data workloads including high-performance computing (HPC), file shares, home directories, archives, media content, video surveillance, and in-place data analytics. Isilon offers all-flash, hybrid, and archive storage systems that can be combined into a single cluster.
However, Dell EMC Networking's legacy OS9 is still prevalent in the industry and supported on a large crosssection of the currently-shipping portfolio. This document encompasses the use of both operating systems within the same network architecture. The Dell EMC S4048-ON will be used as leaf switches, and the Dell EMC Z9100-ON will be used in this guide as a spine switch.
1.1 Typographical conventions The CLI and GUI examples in this document use the following conventions: 1.2 Monospace Text CLI examples Underlined Monospace Text CLI examples that wrap the page. This text is entered as a single command. Italic Monospace Text Variables in CLI examples Bold Monospace Text Commands entered at the CLI prompt Bold text GUI fields and information entered in the GUI Attachments This .pdf includes switch configuration file attachments.
2 Hardware overview This section briefly describes the hardware used to validate the deployment example in this guide. Appendix A contains a complete listing of hardware and components. 2.1 Dell EMC Networking S3048-ON The Dell EMC Networking S3048-ON is a 1-Rack Unit (RU) switch with forty-eight 1GbE Base-T ports and four 10GbE SFP+ ports. In this guide, one S3048-ON supports management traffic in each rack. Dell EMC Networking S3048-ON 2.
Dell EMC PowerEdge R730xd 2.5 Dell EMC PowerEdge R640 This R640 server is a 2-socket, 1 RU server. This server is used in the second rack to connect to the Isilon storage. Dell EMC PowerEdge R640 2.6 Isilon X210 The Dell EMC Isilon X210 is a 2-RU, scale-out NAS system. The Isilon X210 is used to create a storage cluster to support an SMB share in this guide.
3 Management The S3048-ON is used as a Top of Rack (ToR) switch, that aggregates all of the management connections. Each switch has a connection from the out-of-band (OOB) management port to the ToR, as well as each Isilon Node and PowerEdge server. The first Isilon node management connections are shown, each additional node is cabled similarly. This can be seen in Figure 9 below, all equipment in other racks is configured in a similar fashion.
4 Leaf-spine overview The connections between leaf and spine switches can be layer 2 (switched) or layer 3 (routed). The terms “layer 3 topology” and “layer 2 topology” in this guide refer to these connections. In both topologies, downstream connections to servers, storage and other endpoint devices within the racks are layer 2 and connections to external networks are layer 3.
• If none of the layer 2 limitations are a concern, it may ultimately come down to a matter of preference. This guide provides examples of both topologies. In addition to the considerations for the L2 topology, some options need to be considered in the L3 topology. The primary design choice will be in the dynamic routing protocol that best fits the environment.
4.3 10GbE 38 380GbE 2 100GbE 80GbE 380/200 1.900 : 1 10GbE 38 380GbE 3 100GbE 120GbE 380/300 1.267 : 1 10GbE 38 380GbE 4 100GbE 160GbE 380/400 0.950 : 1 Scaling An example of scaling this solution in a two-tier leaf-spine is a configuration of up to 16 racks. The Dell/EMC Z9100-ON has thirty-two 40/100GbE interfaces that would support 16 leaf pairs using VLT. This provides one rack that contains WAN-edge connectivity and 15 racks for servers and storage nodes.
Scaling out the existing networking topology 4.4 Layer 3 leaf-spine topology In a layer 3 leaf-spine network, traffic between leafs and spines is routed. The layer 2/3 boundary is at the leaf switches. Spine switches are never connected to each other in a layer 3 topology. Equal cost multi-path routing (ECMP) is used to load balance traffic across the layer 3 network. Connections within racks from hosts to leaf switches are layer 2.
4.5 Layer 2 leaf-spine topology In a layer 2 leaf-spine network, traffic between leafs and spines is switched (except for a pair of edge leafs) as shown in Figure 13. VLT is used for multipathing and load balancing traffic across the layer 2 leaf-spine fabric. Connections from hosts to leaf switches are also layer 2. For connections to external networks, layer 3 links are added between the spines and a pair of edge leafs.
5 Layer 3 Topology preparation The layer 3 topology used in this example will use external border gateway protocol (eBGP) as well as ECMP. In order to correctly configure this topology, several things need to be considered and planned. 5.1 BGP ASN configuration When eBGP is used, an autonomous system number (ASN) is assigned to each switch. Valid private, 2-byte ASNs range from 64512 through 65534. Figure 14 shows the ASN assignments used for leaf and spine switches in the BGP examples in this guide.
10.0.1.1/32 10.0.2.1/32 10.0.2.2/32 10.0.1.2/32 10.0.2.3/32 Rack 1 10.0.2.4/32 Rack 2 Loopback addressing All loopback addresses used are part of the 10.0.0.0/8 address space with each address using a 32-bit mask. In this example, the third octet represents the layer, “1” for the spine and “2” for the leaf. The fourth octet is the counter for the appropriate layer. For example, 10.0.1.1/32 is the first spine switch in the topology while 10.0.2.4/32 is the fourth leaf switch. 5.
E Leaf 3 Eth1/1/49 .5 192.168.1.4/31 Spine 1 Eth1/1/3 .4 F Leaf 3 Eth1/1/50 .5 192.168.2.4/31 Spine 2 Eth1/1/3 .4 G Leaf 4 Eth1/1/49 .7 192.168.1.6/31 Spine 1 Eth1/1/4 .6 H Leaf 4 Eth1/1/50 .7 192.168.2.6/31 Spine 2 Eth1/1/4 .6 The point-to-point IP addresses used in this guide are shown in Figure 16: Point-to-point IP addresses 18 Dell EMC Networking with Isilon Front-End Deployment and Best Practices Guide | version 1.
6 Configuration of Layer 3 Topology This section will cover the configuration of the layer 3 topology. In the example provided there are three Isilon nodes connected to each leaf pair as well as two Dell PowerEdge servers that will be consuming the storage. The connections for the first node are shown in the diagram. Each subsequent node is cabled similarly. The configurations for all connections are detailed in the following sections.
OS10EE Spine Set the hostname, configure the OOB management interface and default gateway. Z9100-ON Spine 1 Z9100-ON Spine 2 configure terminal configure terminal hostname Z9100-Spine1 hostname Z9100-Spine2 interface mgmt 1/1/1 no ip address dhcp no shutdown ip address 100.67.169.37/24 interface mgmt 1/1/1 no ip address dhcp no shutdown ip address 100.67.169.36/24 management route 0.0.0.0/0 100.67.169.254 management route 0.0.0.0/0 100.67.169.
Z9100-ON Spine 1 Z9100-ON Spine 2 interface breakout 1/1/1 map 40g-1x interface breakout 1/1/2 map 40g-1x interface breakout 1/1/3 map 40g-1x interface breakout 1/1/4 map 40g-1x interface breakout 1/1/1 map 40g-1x interface breakout 1/1/2 map 40g-1x interface breakout 1/1/3 map 40g-1x interface breakout 1/1/4 map 40g-1x interface ethernet1/1/1:1 description “S4048-Leaf1” no shutdown no switchport mtu 9216 ip address 192.168.1.
Z9100-ON Spine 1 Z9100-ON Spine 2 route-map spine-leaf permit 10 match ip address prefix-list spine-leaf route-map spine-leaf permit 10 match ip address prefix-list spine-leaf ip prefix-list spine-leaf seq 10 permit 10.0.1.0/24 ge 32 ip prefix-list spine-leaf seq 10 permit 10.0.1.0/24 ge 32 Use these commands to configure BGP. First, enable eBGP with the router bgp ASN command. The ASN is from Figure 14. The bgp bestpath as-path multipath-relax command enables ECMP.
6.
OS10EE Leaf pair The interfaces for additional Isilon nodes and servers in this example can be found in the following table: Interface enumeration Server/Isilon Node Switch Leaf interface Node 01-1 Leaf 1 ethernet 1/1/1 Leaf 2 ethernet 1/1/1 Leaf 1 ethernet 1/1/3 Leaf 2 ethernet 1/1/3 Node 01-2 24 Dell EMC Networking with Isilon Front-End Deployment and Best Practices Guide | version 1.
Server/Isilon Node Switch Leaf interface Node 01-3 Leaf 1 ethernet 1/1/5 Leaf 2 ethernet 1/1/5 Leaf 1 ethernet 1/1/17 Leaf 2 ethernet 1/1/17 Leaf 1 ethernet 1/1/19 Leaf 2 ethernet 1/1/19 Server 01 Server 02 First, set the hostname, configure the OOB management interface and default gateway. Enable RSTP as a precaution against creating a networking loop. S4048-Leaf 1 is configured as the primary RSTP root bridge using the bridge-priority 0 command.
S4048-ON Leaf 1 S4048-ON Leaf 2 interface range ethernet 1/1/53-1/1/54 description VLTi no switchport interface range ethernet 1/1/53-1/1/54 description VLTi no switchport vlt-domain 127 backup destination 100.67.170.14 discovery-interface ethernet 1/1/53, 1/1/54 vlt-domain 127 backup destination 100.67.170.15 discovery-interface ethernet 1/1/53, 1/1/54 Next, the VLANs will be configured. There will be one VLAN for each Isilon subnet; this will also include the servers in each rack.
S4048-ON Leaf 1 S4048-ON Leaf 2 interface port-channel1 description “Isilon Node 1” no shutdown switchport access vlan 100 mtu 9216 vlt-port-channel 1 spanning-tree port type edge interface port-channel1 description “Isilon Node 1” no shutdown switchport access vlan 100 mtu 9216 vlt-port-channel 1 spanning-tree port type edge interface port-channel3 description “Isilon Node 2” no shutdown switchport access vlan 100 mtu 9216 vlt-port-channel 3 spanning-tree port type edge interface port-channel3 descrip
S4048-ON Leaf 1 S4048-ON Leaf 2 interface ethernet1/1/1 description “Isilon Node 1-10gige-1” no shutdown channel-group 1 mode active no switchport mtu 9216 flowcontrol receive on flowcontrol transmit off interface ethernet1/1/1 description “Isilon Node 1-10gige-2” no shutdown channel-group 1 mode active no switchport mtu 9216 flowcontrol receive on flowcontrol transmit off interface ethernet1/1/3 description “Isilon Node 2-10gige-1” no shutdown channel-group 3 mode active no switchport mtu 9216 flowcont
S4048-ON Leaf 1 S4048-ON Leaf 2 interface ethernet1/1/49 description “Spine 1” no shutdown no switchport mtu 9216 ip address 192.168.1.1/31 interface ethernet1/1/49 description “Spine 1” no shutdown no switchport mtu 9216 ip address 192.168.1.3/31 interface ethernet1/1/50 description “Spine 2” no shutdown no switchport mtu 9216 ip address 192.168.2.1/31 interface ethernet1/1/50 description “Spine 2” no shutdown no switchport mtu 9216 ip address 192.168.2.
S4048-ON Leaf 1 S4048-ON Leaf 2 uplink-state-group 1 enable downstream port-channel1 downstream port-channel3 downstream port-channel5 downstream port-channel101 downstream port-channel102 upstream ethernet1/1/49 upstream ethernet1/1/50 uplink-state-group 1 enable downstream port-channel1 downstream port-channel3 downstream port-channel5 downstream port-channel101 downstream port-channel102 upstream ethernet1/1/49 upstream ethernet1/1/50 Use these commands to configure eBGP.
S4048-ON Leaf 1 S4048-ON Leaf 2 router bgp 64701 bestpath as-path multipath-relax graceful-restart role receiver-only maximum-paths ebgp 2 router bgp 64702 bestpath as-path multipath-relax graceful-restart role receiver-only maximum-paths ebgp 2 address-family ipv4 unicast redistribute connected route-map spine-leaf address-family ipv4 unicast redistribute connected route-map spine-leaf template spine-leaf advertisement-interval 1 fall-over timers 3 9 template spine-leaf advertisement-interval 1
6.3 Configuration of S4048-ON OS9 Leaf Switches Configurations in this section cover leaf switches 3 and 4 running OS9 as seen in Figure 20. OS9 Leaf pair The ports for additional Isilon nodes and servers in this example can be found in the following table: Interface enumeration 32 Server/Isilon Node Switch Leaf interface Node 01-4 Leaf 3 tengigabitethernet 1/1/1 Leaf 4 tengigabitethernet 1/1/1 Dell EMC Networking with Isilon Front-End Deployment and Best Practices Guide | version 1.
Server/Isilon Node Switch Leaf interface Node 01-5 Leaf 3 tengigabitethernet 1/1/3 Leaf 4 tengigabitethernet 1/1/3 Leaf 3 tengigabitethernet 1/1/5 Leaf 4 tengigabitethernet 1/1/5 Leaf 3 tengigabitethernet 1/1/17 Leaf 4 tengigabitethernet 1/1/17 Leaf 3 tengigabitethernet 1/1/19 Leaf 4 tengigabitethernet 1/1/19 Node 01-6 Server 03 Server 04 First, set the hostname, configure the OOB management interface and default gateway. Next, enable LLDP as well as RSTP.
S4048-ON Leaf 3 S4048-ON Leaf 4 interface port-channel128 description VLTi channel-member fortyGigE 1/53 channel-member fortyGigE 1/54 no shutdown no switchport interface port-channel128 description VLTi channel-member fortyGigE 1/53 channel-member fortyGigE 1/54 no shutdown no switchport interface fortyGigE 1/53 description VLTi no shutdown no switchport interface fortyGigE 1/53 description VLTi no shutdown no switchport interface fortyGigE 1/54 description VLTi no shutdown no switchport interface f
S4048-ON Leaf 3 S4048-ON Leaf 4 interface tengigabitethernet 1/1 description “Isilon Node 4-10gige-1” no shutdown port-channel-protocol LACP port-channel 1 mode active mtu 9216 flowcontrol rx on tx off interface tengigabitethernet 1/1 description “Isilon Node 4-10gige-2” no shutdown port-channel-protocol LACP port-channel 1 mode active mtu 9216 flowcontrol rx on tx off interface tengigabitethernet 1/3 description “Isilon Node 5-10gige-1” no shutdown port-channel-protocol LACP port-channel 3 mode act
If the S4048-ON running OS9 is used for the first leaf pair the interfaces for the first Isilon node need to be left out of the port channel to facilitate the configuration of the LACP connections in OneFS. In this example that would be tengigabitethernet 1/1 on both switches. The configuration would be as follows for that example: interface tengigabitethernet 1/1 description “Isilon Node 4-10gige-1” switchport no shutdown mtu 9216 interface vlan200 no shutdown mtu 9216 ip address 172.16.2.
S4048-ON Leaf 3 S4048-ON Leaf 4 interface port-channel1 description “Isilon Node 4” no shutdown switchport mtu 9216 vlt-peer-lag port-channel 1 spanning-tree rstp edge-port interface port-channel1 description “Isilon Node 4” no shutdown switchport mtu 9216 vlt-peer-lag port-channel 1 spanning-tree rstp edge-port interface port-channel3 description “Isilon Node 5” no shutdown switchport mtu 9216 vlt-peer-lag port-channel 3 spanning-tree rstp edge-port interface port-channel3 description “Isilon Node 5”
S4048-ON Leaf 3 S4048-ON Leaf 4 interface vlan200 no shutdown mtu 9216 ip address 172.16.2.252/24 untagged port-channel 1,3,5,101,102 interface vlan200 no shutdown mtu 9216 ip address 172.16.2.253/24 untagged port-channel 1,3,5,101,102 vrrp-group 200 priority 150 virtual-address 172.16.2.254 vrrp-group 200 priority 100 virtual-address 172.16.2.254 The two upstream layer 3 interfaces connected to the spine switches are configured. Assign IP addresses per Table 3.
S4048-ON Leaf 3 S4048-ON Leaf 4 route-map spine-leaf permit 10 match ip address spine-leaf route-map spine-leaf permit 10 match ip address spine-leaf ip prefix-list spine-leaf description Redistribute loopback and leaf networks ip prefix-list spine-leaf description Redistribute loopback and leaf networks seq 10 permit 10.0.2.0/24 ge 32 seq 20 permit 172.16.0.0/16 ge 24 seq 10 permit 10.0.2.0/24 ge 32 seq 20 permit 172.16.0.
BGP neighbors are configured, and fast fall-over is enabled. Finally, exit configuration mode and save the configuration with the end and write commands.
7 Configuration of Layer 2 Topology This section will cover the configuration of the layer 2 topology. In the example provided there are three Isilon nodes connected to each leaf pair as well as two Dell PowerEdge servers that will be consuming the storage. The connections from the spine switches to the OS10EE leaf pair will be configured in port channel 49, while the connections to the OS9 leaf pair will be configured in port channel 50. The two spine switches will be configured in a VLT.
OS10EE Spine Set the hostname, configure the OOB management interface and default gateway. Additionally, with the spine switches configured in a VLT pair, RSTP will be configured at the spine layer. The priority for RSTP will be set on each spine switch. This ensures that the root bridge will always be one of the spine switches.
Z9100-ON Spine 1 Z9100-ON Spine 2 interface range ethernet1/1/31-1/1/32 description VLTi no shutdown no switchport interface range ethernet1/1/31-1/1/32 description VLTi no shutdown no switchport vlt-domain 127 backup destination 100.67.169.36 discovery-interface ethernet1/1/31-1/1/32 peer-routing vlt-domain 127 backup destination 100.67.169.37 discovery-interface ethernet1/1/31-1/1/32 peer-routing Next, configure the required VLANs on each spine switch.
Z9100-ON Spine 1 Z9100-ON Spine 2 interface breakout 1/1/3 map 40g-1x interface breakout 1/1/4 map 40g-1x interface breakout 1/1/3 map 40g-1x interface breakout 1/1/4 map 40g-1x interface port-channel49 description R1-Leaf-AandB no shutdown switchport mode trunk switchport trunk allowed vlan 100 mtu 9216 vlt-port-channel 49 interface port-channel49 description R1-Leaf-AandB no shutdown switchport mode trunk switchport trunk allowed vlan 100 mtu 9216 vlt-port-channel 49 interface port-channel50 des
Finally, exit configuration mode and save the configuration. 7.2 Configuration of S4048-ON OS10EE Leaf Switches Configurations of Leaf 1 and Leaf 2 running OS10EE will be shown next as seen in Figure 23. OS10EE Leaf pair 45 Dell EMC Networking with Isilon Front-End Deployment and Best Practices Guide | version 1.
The interfaces for additional Isilon nodes and servers in this example can be found in the following table: Interface enumeration Server/Isilon Node Switch Leaf interface Node 01-1 Leaf 1 ethernet 1/1/1 Leaf 2 ethernet 1/1/1 Leaf 1 ethernet 1/1/3 Leaf 2 ethernet 1/1/3 Leaf 1 ethernet 1/1/5 Leaf 2 ethernet 1/1/5 Leaf 1 ethernet 1/1/17 Leaf 2 ethernet 1/1/17 Leaf 1 ethernet 1/1/19 Leaf 2 ethernet 1/1/19 Node 01-2 Node 01-3 Server 01 Server 02 First, set the hostname, configure the
Note: Refer to Isilon Network Design Considerations for more information on specific protocols as they relate to OneFS. S4048-ON Leaf 1 S4048-ON Leaf 2 interface range ethernet 1/1/53-1/1/54 decription VLTi no switchport no shutdown interface range ethernet 1/1/53-1/1/54 description VLTi no switchport no shutdown vlt-domain 127 backup destination 100.67.170.14 discovery-interface ethernet 1/1/53-1/1/54 vlt-domain 127 backup destination 100.67.170.
S4048-ON Leaf 1 S4048-ON Leaf 2 interface port-channel1 description “Isilon Node 1” no shutdown switchport access vlan 100 mtu 9216 vlt-port-channel 1 spanning-tree port type edge interface port-channel1 description “Isilon Node 1” no shutdown switchport access vlan 100 mtu 9216 vlt-port-channel 1 spanning-tree port type edge interface port-channel3 description “Isilon Node 2” no shutdown switchport access vlan 100 mtu 9216 vlt-port-channel 3 spanning-tree port type edge interface port-channel3 descrip
S4048-ON Leaf 1 S4048-ON Leaf 2 interface ethernet1/1/1 description “Isilon Node 1-10gige-1” no shutdown channel-group 1 mode active no switchport mtu 9216 flowcontrol receive on flowcontrol transmit off interface ethernet1/1/1 description “Isilon Node 1-10gige-2” no shutdown channel-group 1 mode active no switchport mtu 9216 flowcontrol receive on flowcontrol transmit off interface ethernet1/1/3 description “Isilon Node 2-10gige-1” no shutdown channel-group 3 mode active no switchport mtu 9216 flowcont
S4048-ON Leaf 1 S4048-ON Leaf 2 interface port-channel49 description “Spine 1” no shutdown switchport mode trunk switchport trunk allowed vlan 100 mtu 9216 vlt-port-channel 49 interface port-channel49 description “Spine 1” no shutdown switchport mode trunk switchport trunk allowed vlan 100 mtu 9216 vlt-port-channel 49 interface ethernet1/1/49 description “Spine 1” no shutdown no switchport channel-group 49 mode active mtu 9216 interface ethernet1/1/49 description “Spine 1” no shutdown no switchport cha
OS9 Leaf pair The ports for additional Isilon nodes and servers in this example can be found in the following table: Interface enumeration Server/Isilon Node Switch Leaf interface Node 01-4 Leaf 3 tengigabitethernet 1/1/1 Leaf 4 tengigabitethernet 1/1/1 Leaf 3 tengigabitethernet 1/1/3 Leaf 4 tengigabitethernet 1/1/3 Leaf 3 tengigabitethernet 1/1/5 Leaf 4 tengigabitethernet 1/1/5 Node 01-5 Node 01-6 51 Dell EMC Networking with Isilon Front-End Deployment and Best Practices Guide | version
Server/Isilon Node Switch Leaf interface Server 03 Leaf 3 tengigabitethernet 1/1/17 Leaf 4 tengigabitethernet 1/1/17 Leaf 3 tengigabitethernet 1/1/19 Leaf 4 tengigabitethernet 1/1/19 Server 04 First, set the hostname, configure the OOB management interface and default gateway. Next, enable LLDP as well as RSTP. In OS10EE, LLDP is enabled by default, in OS9, it must be enabled.
S4048-ON Leaf 3 S4048-ON Leaf 4 interface port-channel128 description VLTi channel-member fortyGigE 1/53 channel-member fortyGigE 1/54 no shutdown no switchport interface port-channel128 description VLTi channel-member fortyGigE 1/53 channel-member fortyGigE 1/54 no shutdown no switchport interface fortyGigE 1/53 description VLTi no shutdown no switchport interface fortyGigE 1/53 description VLTi no shutdown no switchport interface fortyGigE 1/54 description VLTi no shutdown no switchport interface f
S4048-ON Leaf 3 S4048-ON Leaf 4 interface tengigabitethernet 1/1 description “Isilon Node 4-10gige-1” no shutdown port-channel-protocol LACP port-channel 1 mode active mtu 9216 flowcontrol rx on tx off interface tengigabitethernet 1/1 description “Isilon Node 4-10gige-2” no shutdown port-channel-protocol LACP port-channel 1 mode active mtu 9216 flowcontrol rx on tx off interface tengigabitethernet 1/3 description “Isilon Node 5-10gige-1” no shutdown port-channel-protocol LACP port-channel 3 mode active
S4048-ON Leaf 3 S4048-ON Leaf 4 interface port-channel1 description “Isilon Node 4” no shutdown switchport mtu 9216 vlt-peer-lag port-channel 1 spanning-tree rstp edge-port interface port-channel1 description “Isilon Node 4” no shutdown switchport mtu 9216 vlt-peer-lag port-channel 1 spanning-tree rstp edge-port interface port-channel3 description “Isilon Node 5” no shutdown switchport mtu 9216 vlt-peer-lag port-channel 3 spanning-tree rstp edge-port interface port-channel3 description “Isilon Node
The upstream interfaces and port channels will be configured as follows: S4048-ON Leaf 3 S4048-ON Leaf 4 interface port-channel50 description “Spine 1 and 2” no shutdown switchport mtu 9216 vlt-peer-lag port-channel 50 interface port-channel50 description “Spine 1 and 2” no shutdown switchport mtu 9216 vlt-peer-lag port-channel 50 interface fo 1/49 description “Spine 1” no shutdown port-channel-protocol LACP port-channel 50 mode active mtu 9216 interface fo 1/49 description “Spine 1” no shutdown port-c
S4048-ON Leaf 3 S4048-ON Leaf 4 uplink-state-group 1 downstream port-channel1 downstream port-channel3 downstream port-channel5 downstream port-channel101 downstream port-channel102 upstream port-channel 50 uplink-state-group 1 downstream port-channel1 downstream port-channel3 downstream port-channel5 downstream port-channel101 downstream port-channel102 upstream port-channel 50 end write memory end write memory Finally, exit configuration mode and save the configuration with the end and write command
8 Validation In addition to sending traffic between hosts, the configuration shown in both topologies can be validated with the commands shown in this section. The validation for the layer 2 topology will only reference sections 8.1.3 – 8.1.9 for OS10EE and sections 8.2.3 – 8.2.8 for OS9. Note: For more information on commands and output, see the Command Line Reference Guide for the applicable switch (links to documentation are provided in Appendix B.
S4048-Leaf1 has two paths to all other leafs and two paths to Server 3’s network, 172.16.2.0. There is one path through each spine. If all paths do not appear, make sure the maximum-paths statement in the BGP configuration is equal to or greater than the number of spines in the topology.
B EX 172.16.2.0/24 via 192.168.1.0 via 192.168.2.0 20/0 01:00:11 Note: The command show ip route can also be used to verify the information above as well as static routes and direct connections. 8.1.3 Show VLT This command is used to validate VLT configuration status on leaf switches in this topology. The VLTi Link Status must be up. The role of one switch in the VLT pair is primary (not shown), and its peer switch is assigned the secondary role. Ensure Peer-Routing is shown as enabled.
------------------------------------------------------------------------------1 port-channel1 up 1 1 * 2 port-channel1 up 1 1 vlt-port-channel ID : 3 VLT Unit ID Port-Channel Status Configured ports Active ports ------------------------------------------------------------------------------1 port-channel3 up 1 1 * 2 port-channel3 up 1 1 vlt-port-channel ID : 5 VLT Unit ID Port-Channel Status Configured ports Active ports ------------------------------------------------------------------------------1 port-cha
Uplink State Group: 1, Status: Enabled,up If an interface happens to be disabled by UFD, the show uplink-state-group command output will appear as follows: Uplink State Group: 1 Status: Enabled, down Upstream Interfaces:ethernet1/1/49(down) ethernet1/1/50(down) Downstream Interfaces:port-channel1(disabled) port-channel101(disabled) portchannel102(disabled) port-channel3(disabled) port-channel5(disabled) Note: When an interface has been disabled by UFD, the show interfaces interface command for affected inte
port-channel101 Desg port-channel102 Desg 8.1.9 128.2617 128 1000 FWD 128.2618 128 1000 FWD --- Output is truncated --- 0 0 AUTO AUTO Yes Yes Show vrrp brief This command is used to verify that VRRP is correctly configured and both switches in the VLT have the same virtual address.
S4048-Leaf3#show ip route bgp Destination Gateway ----------------B EX 10.0.1.1/32 via 192.168.1.4 B EX 10.0.1.2/32 via 192.168.2.4 B EX 10.0.2.1/32 via 192.168.1.4 via 192.168.2.4 B EX 10.0.2.2/32 via 192.168.1.4 via 192.168.2.4 B EX 10.0.2.4/32 via 192.168.1.4 via 192.168.2.4 B EX 172.16.1.0/24 via 192.168.1.4 via 192.168.2.
8.2.4 Show VLT detail This command is used to validate VLT LAG status on leaf switches in this topology. This command shows the status and active VLANs of all VLT LAGs. The local and peer status must both be up. S4048-Leaf3#show vlt detail Local LAG Id Peer LAG Id Local Status ------------ ----------- -----------1 1 UP 3 3 UP 5 5 UP 101 101 UP 102 102 UP 8.2.
S4048-Leaf3#show spanning-tree rstp brief Executing IEEE compatible Spanning Tree Protocol Root ID Priority 0, Address f48e.382e.a0f7 Root Bridge hello time 2, max age 20, forward delay 15 Bridge ID Priority 0, Address f48e.382e.a0f7 We are the root Configured hello time 2, max age 20, forward delay 15 8.2.8 Interface Name ---------Po 1 Po 3 Po 5 Po 101 Po 102 Po 128 PortID -------128.2 128.4 128.6 128.102 128.103 128.
9 Isilon configuration The following section outlines the steps necessary to add the Isilon X210 nodes into a cluster, setup a functioning SMB share, designate a secondary subnet, and configure the SmartConnect feature in OneFS. 9.1 Building the cluster The first step in configuring the Isilon array is building the cluster. Once the array is powered on, a serial connection can be made to each node. Connect to the first node and use the cluster creation wizard to build the cluster.
Parameter Value Interface int-a netmask 255.255.255.0 Interface int-a IP Range 10.10.10.1-253 Interface int-b netmask 255.255.255.0 Interface int-b IP Range 10.10.20.1-253 Failover IP range 10.10.30.1-253 Interface ext-1 netmask 255.255.255.0 MTU 1500 Interface ext-1 IP pool 100.67.170.140-148 ext-1 default gateway 100.67.170.254 SmartConnect Zone name Mgmtzone1 SmartConnect service IP 100.67.170.149 DNS servers 100.67.10.1 Search domain dell.
Join cluster 9.2 Configuring LACP to each node Once the cluster has been created, and each node has been added to the cluster, the rest of the configurations can be done through the OneFS web GUI. This section will cover the creation of two subnets and their associated IP pools, as well as the addition of static routes to ensure end to end connectivity. This will include ensuring that the LACP option is selected and the appropriate interfaces are selected. 1.
2. After successfully logging into the OneFS web GUI, navigate to Cluster Management > Network Configuration. This will allow changes to the network configuration. 3. Select the More option next to groupnet0, and Add subnet. Define values for the next two subnets. Refer to Table 9. Subnet Configurations Parameter Value Subnet Name subnet1 Netmask 255.255.255.0 Gateway Address 172.16.1.254 MTU 9000(Jumbo Frame) SmartConnect Service IP 172.16.1.249 SmartConnect Service Name sczone1.dell.
LACP configuration The next section will cover the configuration of static routes within OneFS. This is necessary to enable traffic to cross between the two subnets. 1. Navigate Network configurations>subnet1>pool1, Add static route to subnet 2. Parameter Value Subnet 172.16.2.0 Netmask 255.255.255.0 Gateway 172.16.1.254 2. Navigate Network configurations>subnet2>pool2, Add static route to subnet 1. 71 Parameter Value Subnet 172.16.1.0 Netmask 255.255.255.0 Gateway 172.16.2.
Static Routes In addition to the Isilon nodes, each Windows server is configured in an LACP NIC team that utilizes the address hash setting. The specific configuration steps for a Windows NIC team can be found in Microsoft’s documentation, Create a New NIC Team on a Host Computer or VM. 9.3 Configuring SMB share This section will cover the creation of a folder structure that will then be configured under OneFS Protocols Windows Sharing SMB.
Directory creation 4. Once the folder has been created, click the SMB folder. 5. Once again create a directory and assign the name, “Engineering,” user, group, and permissions settings. 6. When both folders have been created, navigate to the Protocols > Windows Sharing (SMB). 7. Select Create an SMB Share. 8. Assign a name, “Engineering SMB,” use the Browse button to navigate to the Engineering folder that was created previously. 9. Select the member's window and assign access permissions. 10.
Note: Refer to Microsoft's DNS Resource Record Management for the specific steps in creating a DNS server. 2. Navigate to Server Manager > Tools > DNS and configure the following: DNS parameters Parameter Value Forward Lookup Zone dell.local Reverse Lookup Zones 172.16.1, 172.16.2 Host A record for sczone1 sczonea, 172.16.1.249 Host A record for sczone2 sczoneb, 172.16.2.249 Delegation zone for sczone1 sczone1.dell.local, 172.16.1.249 Delegation zone for sczone2 sczone2.dell.local, 172.16.2.
Validation 1. Login to Server 01 and issue a Run command of \\sczone2.dell.local. This will bring up the folder structure that was created in the OneFS file system. 2. Create a file or a folder in order to verify read/write permissions. 3. Login to Server04 and issue the Run command \\sczone1.dell.local. This will display the same folder, and the previously created files will be present.
A Validated hardware and components The following tables list the hardware and components used to configure and validate the example configurations in this guide. A.1 A.2 A.3 Dell EMC Networking Switches Qty Item OS/Firmware version 2 Z9100-ON OS 10.4.0 R3 2 S4048-ON OS 10.4.0 R3 2 S4048-ON OS 9.13 (0.0) 1 S3048-ON OS 9.13 (0.0) Dell EMC Isilon Array Qty Item OS/Firmware version 6 Isilon X210 8.1.0.
B Product Manuals and technical guides Manuals and documentation for Dell Networking Z9100-ON Manuals and documentation for Dell Networking S4048-ON Manuals and documentation for Dell Networking S3048-ON Manuals and documentation for PowerEdge R730xd Manuals and documentation for PowerEdge R640 Isilon OneFS Isilon X210 Installation Guide Create a New NIC Team on a Host Computer or VM Microsoft's DNS Resource Record Management Dell EMC Leaf-Spine Deployment Guide Dell EMC Networking L3 Design for Leaf-Spine
C Support and feedback Contacting Technical Support Support Contact Information Web: http://support.dell.com/ Telephone: USA: 1-800-945-3355 Feedback for this document We encourage readers to provide feedback on the quality and usefulness of this publication by sending an email to Dell_Networking_Solutions@Dell.com. 78 Dell EMC Networking with Isilon Front-End Deployment and Best Practices Guide | version 1.
