User manual | NETGEAR XSM 7224S, M5300 52G3 Storage Networking Application Notes

Networking Solutions for Storage
Application Notes
Table of Contents
Introduction.............................................................................................................................................................. 3
How to Use this Document................................................................................................................................ 3
Reference Configuration.................................................................................................................................... 4
Assumptions........................................................................................................................................................ 4
Global Configuration Notes...................................................................................................................... 5
Sample Configuration Values.................................................................................................................... 5
CLI Configuration Steps................................................................................................................................. 5
XSM7224S..................................................................................................................................................... 5
M5300-52G3............................................................................................................................................... 8
Web GUI Configuration Steps...................................................................................................................... 9
XSM7224S..................................................................................................................................................... 9
M5300-52G3.............................................................................................................................................18
Page 2
Introduction
Unified storage that supports IP-based SAN (iSCSi) and Network-Attached Storage (NAS) protocols on 10G Ethernet
fabric, has emerged as an attractive storage option for mid-sized companies seeking an efficient, reasonably-priced
solution to handle the flood of data generated by twenty-first century businesses. Mid-sized companies can now take
the same fundamental approach to storage as large enterprises, using a storage area network (SAN) to store data, but
in a smaller scale than enterprises and without the expense and complexity of enterprise-scale fiber channel SANs.
Several factors are driving the trend towards NAS/SAN solutions for these companies.:
• Data volume. More data is being generated than ever before for operating systems, applications, and user data.
• Regulatory requirements. Government regulations are compelling businesses to maintain and back up data that
previously would have been deleted.
• Virtualization. With multiple virtual machines (VMs) running on the same server, centralized storage becomes a
necessity. NAS devices or dedicated SAN storage devices are needed to meet the VM storage demands.
Enterprise-scale companies have met storage challenges with fiber channel SANs, which can manage huge quantities of
data. However, they are not appropriate for mid-sized businesses, as they are complex, expensive to install and maintain,
and must be managed by experts with specialized training and skills.
The iSCSi protocol offers an alternative to fiber channel SANs that is appropriate for mid-sized businesses. iSCSi is an
extension of the ScSi protocol used for block transfers in most storage devices and in fiber channel architectures. The
Internet extension (the “i” in iSCSi) defines protocols for extending block transfers over IP, allowing standard Ethernet
infrastructure to be used as a SAN interconnect fabric. Basic iSCSi is supported in most operating systems today, and its
capabilities allow 10G Ethernet to compare favorably to fiber channel as a SAN interconnection fabric.
How to Use this Document
The Networking Solutions for Storage Solution Guide provides technical guidance and details for the NETGEAR storage
solution. Use the Solution Guide to plan your solution architecture and determine the needed equipment.
This Application Note is a companion document to the Solution Guide. After you have planned and have the equipment for
your network, use this guide to configure storage solution.
Page 3
Reference Configurations
The following figure shows a reference configuration. You can use the CLI or Web GUI for configuration.
Figure 1. Sample Solution
Assumptions
• Layer 3 licenses have been installed on XSM7224S switches as they are native Layer 2+ switches. No additional
license is needed for the M5300-52G3 switches, as they are native Layer 3 switches.
• An existing DHCP server is used to manage dynamic and static DHCP pools.
• Best practices are used to design and implement switch stacking and redundancy/failover.
• A NETGEAR ReadyData 5200 storage server is used with the recommended bonded gigabit interfaces using passive
LACP mode, Layer 3 /Layer 4 hash type, and short LACP Timer. By default, NETGEAR Layer 3 switches have LACP
enabled globally, LACP mode set to active, and LACP Timer set to short. For LACP to operate, only one side of the
link needs to be in the active mode. Refer to the storage vendor documentation for information on selecting optimal
settings, and modify LACP-related commands in this application note as necessary.
Page 4
Global Configuration Notes
• Be sure to save your configuration using the save or write memory CLI command. Alternatively, choose
Maintenance > Save Config in the GUI. Select the box, and click APPLY.
• When using link aggregation groups (LAGs), do not connect any ports in the LAG until both ends of all links are
configured.
• Amend routes on the M5300-52G3 stack to reflect the correct static routes, particularly the next-hop address to
the rest of the network.
• Screens in the GUI section of this application note were taken from an M5300-28G3 stack. However, all of the
configuration and features also apply to a M5300-52G3 stack.
Sample Configuration Values
The following values are used in the sample configuration. Modify the configuration as needed for your environment.
• Management VLAN: VLAN 5
• VLANs for the storage server’s 10G links: VLAN 80 (192.168.88.1/24) and VLAN 90 (192.168.89.1/24).
• VLAN for the storage server’s bonded 1G links: VLAN 10 (192.168.1.1/24)
• Load balance type: 6
CLI Configuration Steps
These steps provide an example CLI configuration. To use the Web GUI for configuration, see Web GUI Configuration Steps
on page 9.
XSM7224S
1. Use one VLAN for each of the storage server’s 10G links – VLAN 80 (192.168.88.1/24) and VLAN 90
(192.168.89.1/24). Use one VLAN for the storage server’s bonded 1G links – VLAN 10 (192.168.1.1/24). Declare the
VLANs with routing.
XSM7224S) #vlan database
(XSM7224S) (Vlan)#vlan 5,10,80,90
(XSM7224S) (Vlan)#vlan routing 5
(XSM7224S) (Vlan)#vlan routing 10
(XSM7224S) (Vlan)#vlan routing 80
(XSM7224S) (Vlan)#vlan routing 90
Page 5
2.Configure the VLAN interfaces.
(XSM7224S) #configure
(XSM7224S) (Config)#interface vlan 10
(XSM7224S) (Interface-vlan 10)#routing
(XSM7224S) (Interface-vlan 10)#ip address 192.168.1.1 255.255.255.0
(XSM7224S) (Interface-vlan 10)#exit
(XSM7224S) (Config)#interface vlan 80
(XSM7224S) (Interface-vlan 80)#routing
(XSM7224S) (Interface-vlan 80)#ip address 192.168.88.1 255.255.255.0
(XSM7224S) (Interface-vlan 80)#exit
(XSM7224S) (Config)#interface vlan 90
(XSM7224S) (Interface-vlan 90)#routing
(XSM7224S) (Interface-vlan 90)#ip address 192.168.89.1 255.255.255.0
(XSM7224S) (Interface-vlan 90)#exit
3.Enable routing globally.
(XSM7224S) (Config)#ip routing
4.
Configure the storage server’s 10G links. Match the correct VLAN interface with the storage server’s port
configuration.
(XSM7224S) (Config)#interface 1/0/22
(XSM7224S) (Interface 1/0/22)#vlan participation exclude 1
(XSM7224S) (Interface 1/0/22)#vlan participation include 80
(XSM7224S) (Interface 1/0/22)#vlan pvid 80
(XSM7224S) (Interface 1/0/22)#exit
(XSM7224S) (Config)#interface 2/0/22
(XSM7224S) (Interface 2/0/22)#vlan participation exclude 1
(XSM7224S) (Interface 2/0/22)#vlan participation include 90
(XSM7224S) (Interface 2/0/22)#vlan pvid 90
(XSM7224S) (Interface 2/0/22)#exit
5.Enable LAG globally. LAG is used to satisfy the bonding requirements of the storage server.
(XSM7224S) (Config)#port-channel adminmode all
6.
Set the load balance type on the ports. This must match with the hash type configured on the storage server. In this
case, the storage server’s ports are configured for Layer 3 and Layer 4. Set the load balance type to 6 (Src/Dest IP
and TCP/UDP Port fields) and apply it to all interfaces.
(XSM7224S) (Config)#port-channel load-balance 6 all
Page 6
7.
Configure the LAG interface for the storage server’s 1G links. When using LAGs, configuration is done on the LAG
interface much like it is done on a physical interface. Configuration of the LAG interface is done prior to configuring
the port, as the port inherits its configuration from the LAG interface.
(XSM7224S) (Config)#interface lag 1
(XSM7224S) (Interface-lag 1)#vlan participation exclude 1
(XSM7224S) (Interface-lag 1)#vlan participation include 10
(XSM7224S) (Interface-lag 1)#vlan pvid 10
(XSM7224S) (Interface-lag 1)#exit
8.Add the ports to be part of the LAG.
(XSM7224S) (Config)#interface 1/0/21
(XSM7224S) (Interface 1/0/21)#addport lag 1
(XSM7224S) (Interface 1/0/21)#exit
(XSM7224S) (Config)#interface 2/0/21
(XSM7224S) (Interface 2/0/21)#addport lag 1
(XSM7224S) (Interface 2/0/21)#exit
9.For distributed link aggregation between the XSM7224S stack and M5300-52G3 stack, configure the second LAG
interface with all VLAN needed to pass between the stacks like a normal trunk port.
(XSM7224S) (Config)#interface lag 2
(XSM7224S) (Interface-lag 2)#vlan participation exclude 1
(XSM7224S) (Interface-lag 2)#vlan participation include 5,10,80,90
(XSM7224S) (Interface-lag 2)#vlan tagging 5,10,80,90
(XSM7224S) (Interface-lag 2)#exit
10.Add uplink interfaces as members of the LAG.
(XSM7224S) (Config)#interface range 1/0/19-1/0/20
(XSM7224S) (conf-if-range-1/0/19-1/0/20)#addport lag 2
(XSM7224S) (conf-if-range-1/0/19-1/0/20)#exit
(XSM7224S) (Config)#interface range 2/0/19-2/0/20
(XSM7224S) (conf-if-range-2/0/19-2/0/20)#addport lag 2
(XSM7224S) (conf-if-range-2/0/19-2/0/20)#exit
(XSM7224S) (Config)#exit
Page 7
M5300-52G3
1.Declare the VLANs.
(M5300-52G3) #vlan database
(M5300-52G3) (Vlan)#vlan 5,10,80,90
(M5300-52G3) (Vlan)#exit
2.Enable IP routing globally and set a default route. Configure static routes as appropriate for your environment.
(M5300-52G3) #configure
(M5300-52G3) (Config)#ip routing
(M5300-52G3) (Config)#ip route 0.0.0.0 0.0.0.0 10.10.10.1
3.Enable LAG globally.
(M5300-52G3) (Config)#port-channel adminmode all
4.Set the load balance type on the ports. This must match the LAG interface configurations on the XSM7224S stack.
Set the load balance type to 6 (Src/Dest IP and TCP/UDP Port fields) and apply it to all interfaces.
(M5300-52G3) (Config)#port-channel load-balance 6 all
5.For distributed link aggregation between the XSM7224S stack and M5300-52G3 stack, configure the second
LAG interface with all VLANs needed to pass between the stacks like a normal trunk port. Both sides of the LAG
interfaces must match.
(M5300-52G3) (Config)#interface lag 2
(M5300-52G3) (Interface-lag 2)#no spanning-tree port mode
(M5300-52G3) (Interface-lag 2)#vlan participation exclude 1
(M5300-52G3) (Interface-lag 2)#vlan participation include 5,10,80,90
(M5300-52G3) (Interface-lag 2)#vlan tagging 5,10,80,90
(M5300-52G3) (Interface-lag 2)#exit
6.
Add the uplink interfaces as members of the LAG.
(M5300-52G3) (Config)#interface 1/0/23-1/0/24
(M5300-52G3) (Interface 1/0/23-1/0/24)#addport lag 2
(M5300-52G3) (Interface 1/0/23-1/0/24)#exit
(M5300-52G3) (Config)#interface 2/0/23-2/0/24
(M5300-52G3) (Interface 2/0/23-2/0/24)#addport lag 2
(M5300-52G3) (Interface 2/0/23-2/0/24)#exit
(M5300-52G3) (Config)#exit
Page 8
Web GUI Configuration Steps
These steps provide an example Web GUI configuration. For the CLI configuration, see CLI Configuration Steps on page 5.
XSM7224S
1.
Declare the VLANs. The configuration uses one VLAN for each of the storage server’s 10G links – VLAN 80
(192.168.88.1/24) and VLAN 90 (192.168.89.1/24). Use one VLAN for the storage server’s bonded 1G links – VLAN
10 (192.168.1.1/24). Choose Switching > VLAN > Advanced > VLAN Configuration. For each VLAN, enter the
correct VLAN ID and click ADD.
Page 9
2.Choose Routing > VLAN > VLAN Routing. Select each VLAN ID from the drop-down menu and enter its IP address
and subnet mask. Click ADD after configuring each VLAN.
Page 10
3.Choose Routing > IP > Basic > IP Configuration and enable Routing Mode. Click APPLY.
Page 11
4.
Configure ports for the storage server’s 10G links. Choose Switching > VLAN > Advanced > VLAN Membership.
For each port, select the corresponding VLAN ID from the drop-down menu and click the box under the port until
you see U for untagged. Click APPLY.
Page 12
5.Configure the VLAN PVID for each of the ports. Choose Switching > VLAN > Advanced > Port PVID
Configuration. For each port, select it and enter the correct Configured PVID value. Click APPLY.
Page 13
6.
Configure the LAG interfaces for the 1G bonded uplink to the storage server (LAG 1) and the 10G uplinks to the
M5300-52G3 stack (LAG 2). Choose Switching > LAG > LAG Configuration. Select the first LAG interface and
enable Admin Mode. Set the Hash Mode to “6 Src/Dest IP and TCP/UDP Port fields.” This setting is dictated by the
hash type set on the storage server. Click APPLY. Do the same for the second LAG interface using the same Hash
Mode.
Page 14
7.Configure the LAG interfaces in the same way as physical ports. Choose Switching > VLAN > Advanced > VLAN
Membership. For LAG 1 (for 1G bonded ports), select VLAN 10 from the drop-down menu and set LAG 1 U for
untagged under the LAG port list. Click APPLY. For LAG 2 (for uplink ports to the M5300-53G3 stack), select each
VLAN that needs to be transported across stacks from the drop-down menu and set LAG 2 to T for tagged under
the LAG port list. Click APPLY.
Page 15
8.Set the correct PVID for the 1G storage server ports. Choose Switching > VLAN > Advanced > Port PVID
Configuration. Click the LAGS option above the column headings to list the LAG interfaces. Select LAG 1 and s
et the Configured PVID to 10. Click APPLY.
Page 16
9.Add ports to the LAG groups. Choose Switching > LAG > LAG Membership. Select LAG 1 from the drop-down list
and select the box for the ports for the 1G links to the storage server. Click APPLY. Do the same for LAG 2 with our
uplink ports to the M5300-52G3 stack.
Page 17
M5300-52G3
1.Declare VLANs as was done for the XSM7224S stack. Choose Switching > VLAN > Advanced > VLAN
Configuration. For each VLAN, enter the correct VLAN ID and click ADD.
Page 18
2.Enable IP routing globally. Choose Routing > IP > Basic > IP Configuration. Enable Routing Mode and click APPLY.
Page 19
3.Choose Routing > Routing Table > Basic > Route Configuration. Configure the appropriate static routes for the
environment between stacks and to the rest of the network. Click ADD after each complete entry.
Page 20
4.Configure the LAG interface for the uplinks to the CSM7224S stack. Choose Switching > LAG > LAG
Configuration. Select LAG 2, enable Admin Mode, and set the Hash Mode to “6 Src/Dest IP and TCP/UDP Port
fields” Click APPLY. The Hash Mode must be the same on both sides of the uplinks.
Page 21
5.Configure LAG interfaces as for a physical port. Choose Switching > VLAN > Advanced > VLAN Membership. For
LAG 2 (for the uplink ports to the XSM7224S stack), select each VLAN that needs to be transported across stacks
from the drop-down menu, and set LAG 2 to T for tagged under the LAG port list. Click APPLY after each.
Page 22
6.
Add ports to the LAGs. Choose Switching > LAG > LAG Membership. Select LAG 2 from the drop-down list and
check the box for the ports for the uplinks to the XSM7224S stack. Click APPLY.
NETGEAR and the NETGEAR logo are trademarks and/or registered trademarks of NETGEAR, Inc. and/or its subsidiaries in the United States and/or other
countries. Other brand names mentioned herein are for identification purposes only and may be trademarks of their respective holder(s). Information is
subject to change without notice. ©2013 NETGEAR, Inc. All rights reserved.
Page 23