Networking Features Upon completion of this module, you should be able to: Discuss and configure VNX networking features This module continues the discussion.

Networking Features Upon completion of this module, you should be able to: Discuss and configure VNX networking features This module continues the discussion of networking features supported by the VNX, which offer high availability functionality. Networking Features Networking Features

Networking Features Lesson 1: Networking Features Overview
During this lesson the following topics are covered: Basic network concepts and terminology VLANs and VLAN tagging Roles of networking features Types of virtual devices Physical, virtual and logical interfaces on a Data Mover This lesson covers basic networking concepts, terminology and describes VLANs and virtual devices. Networking Features Networking Features

Networking Devices Overview
Ethernet hub (EMC recommends no hubs in VNX environment) Layer 1 All traffic sent to all ports Half duplex mode only Ethernet switch Layer 2 Sends traffic to specific port 100Mbps+/Full duplex support Managed Ethernet switch Allow control and traffic management Includes features such as Ethernet Channel, LACP and VLANs Can operate at Layer 3 Infrastructure must support VNX feature The Ethernet hub operates at the Physical layer of the network (Layer 1) and incorporates no software or intelligence. Because the hub is incapable of making any decisions, it sends all traffic to all ports in order to ensure that a packet reaches its destination. This imposes unwanted overhead on all of the components involved, which results in unsatisfactory performance. Additionally, because hubs cannot provide dedicated node-to-node communication, they cannot support full duplex communication. When nodes communicate in half duplex mode, one node will transmit while the other receives. In full duplex mode, both network nodes transmit and receive simultaneously, thus doubling the theoretical network throughput. Although some Fast Ethernet (FE) hubs are capable of 100Mbps transmission, many models are limited to 10Mbps. Ethernet hubs are not recommended in any VNX environments. The Ethernet switch operates at the Data Link layer of the network (Layer 2), providing software capable of directing network traffic only to the port(s) specified in the destination of the packet. A switched network offers direct node-to-node communication, thus supporting full duplex communication. While the 10Mbps limitation is common with hubs, switches provide 100Mbps or higher transmission speeds. There are standard Ethernet switches that do not offer any management functionality. These switches are also known as “plug and play” switches. Managed switches are more common today. They provide a variety of software enhancements that allow the network administrator to control and manage network traffic through various methods, such as serial console, telnet, SSH or SMTP. Some of the features that will be of interest for VNX management are Ethernet Channel, LACP and VLANs. There are some switches that can also operate at the Network layer (Layer 3), which allows for routing between VLANs. These switches are called Multilayer switches. Networking Features Networking Features

Virtual Local Area Network (VLANs)
Groupings of switch ports Divides large number of ports Confines broadcasts Contributes to security Can combine physically separate LANs A VNX Physical device may be required to participate in multiple network segments VLAN Tagging VLANs (Virtual Local Area Networks) are a method of grouping switch ports together into a virtual LAN, as the name would indicate. Switch ports, as well as router interfaces, can be assigned to VLANs. VLANs can be employed for seemingly opposite uses. VLANs can be used to break up a very large LAN into smaller virtual LANs. This may be useful to control network traffic, such as broadcasts (another name often used for a VLAN is a Broadcast Domain). Although VLANs are not a security vehicle unto themselves, they can be used as part of an overall security scheme in the network. VLANs can also be used to combine separate physical LANs into one virtual LAN. For example, the sales staff of Hurricane Marine is physically dispersed along both the east and west coasts of the United States (WAN), yet all of the network clients have similar network needs and should rightly be in the same logical unit. By employing VLANs, all of the Hurricane Marine sales staff can be in the same logical network, the same virtual LAN. Typically, each IP network segment is assigned to a separate VLAN. Additionally, in order to transmit from one VLAN to another, the traffic has to go through a router, or Layer 3 device. Each router interface or sub-interface can be assigned an IP address and subnet within a specific VLAN. That interface can act as the default gateway for hosts on that VLAN and route traffic to hosts on other VLANs to which the router is also connected. Networking Features Networking Features

VLANs Top diagram illustrates a “public network”
Bottom diagram illustrates three “private networks” Physical location is not relevant to VLAN number VLAN numbers are defined by the local administrator InterVLAN traffic must be routed VLANs create separate broadcast domains (Layer 2 network) on one physical device. This is accomplished by breaking a single switch into multiple broadcast domains, or multiple Layer 2 segments, which limit broadcast traffic. The traffic between VLANs then needs to be routed. Networking Features Networking Features

VLAN Tagging A single network interface card can be assigned multiple logical interfaces Different VLAN can be assigned to each interface Destination IP address must match the interface IP address The packet's VLAN tag must match the interface's VLAN ID Zero (or blank) is the default value of VLAN ID Packets are sent without tags (default value) VLAN Tag (ID) Written by device that transmits the frame Switch port settings Type trunk Protocol setting 802.1Q VLANs are logical networks that function independently of the physical network configuration. For example, VLANs enable you to put all of a department’s computers on the same logical subnet, which can increase security and reduce network broadcast traffic. VLAN Tagging can increase network flexibility by allowing a single network interface to be assigned multiple logical interfaces. A different VLAN can be assigned to each interface. A packet is accepted if the destination IP address is the same as the IP address of the interface, and the packet's VLAN tag is the same as the interface's VLAN ID. Zero (0) is the default value of VLAN ID (blank is also accepted and means the same as 0) and means VLAN tagging is not enabled. If a VLAN tag is being used, the transmitting device will add the proper header to the frame. The switch port should be set to trunk or there could be connectivity problems between the switch port and device. Networking Features Networking Features

VLAN Tagging (continued)
Protocol 802.1Q Individual Ethernet switch port is classified as a trunk port Administrator must allow specific VLANs to use the trunk port VLAN tagging is seen in many enterprise networking environments A trunk line carries traffic from multiple VLANs on a single trunk port. It most often goes from switch to switch, but can also go from server to switch. Cisco has a proprietary trunking protocol called ISL, which works in a similar fashion to the 802.1Q protocol. By default, all VLANs are allowed across trunk links. For security reasons, the administrator should configure trunk ports on the switch to drop traffic from unused VLANs. This can also cut down on the amount of broadcast traffic sent to each switch and port. Networking Features Networking Features

Roles of Networking Features
High Availability: Ethernet Channel Link aggregation Fail-Safe Network Increase Network Flexibility: VLAN Tagging A key feature to almost any EMC product is its ability to handle single point of failure issues. Addressing the Ethernet network is no different. Today’s environments are highly complex, and the number of possible combinations to address all solutions can be difficult. We can ensure proper deployment by understanding how the technology performs. Networking Features Networking Features

Virtual Device Overview and Usage
Virtual device is a combination of multiple physical devices defined by a single MAC address. You cannot individually assign same IP address to different physical devices on a Data Mover Duplicate IP Different MAC addresses Virtual devices are used to distribute data among multiple physical ports in case of failure A virtual device is not required in order to access resources in a simple environment. However, if customers have a desire to increase fault tolerance, virtual devices are used. Virtual devices are a combination of 2 or more physical devices, of physical device(s) and virtual device(s) or of 2 or more virtual devices. Networking Features Networking Features

Types of VNX Virtual Devices
Ethernet Channel Dependent on pre-existing Ethernet configuration (customer must provide) Link Aggregation Fail Safe Network Independent of pre-existing Ethernet configuration Should be configured across two Ethernet switches These are the three types of VNX virtual devices. They are explained in more detail later in this module. Networking Features Networking Features

Ethernet Channel and LACP
Static configuration No support for Port Aggregation Protocol (PAgP) Works with Cisco EtherChannel Link Aggregation (LACP) Industry standard (802.3ad) alternative to EtherChannel Both provide more overall bandwidth than a single port Connection to any single client runs through one physical port, and is therefore limited by the port’s bandwidth When the connection to one port fails, the switch automatically switches traffic to the remaining ports Ethernet Channel combines multiple physical ports (two, four or eight) into a single logical port for the purpose of providing fault tolerance for Ethernet ports and cabling. Ethernet Channel was not originally designed for load balancing or to increase bandwidth, but has been updated since to include these features. Ethernet Channel does not provide increased bandwidth from the client’s (Data Mover) perspective. Because each interface is connected only to a single port, the client does not receive any added performance. Any increased bandwidth on the side of the channeled host (the Data Mover) is incidental. However, this is not an issue because the objective of Ethernet Channel is to provide fault tolerance, not to increase aggregate bandwidth. Link Aggregation Control Protocol (LACP) is an alternative to EtherChannel. The IEEE 802.3ad Link Aggregation Control Protocol also allows multiple Ethernet links to be combined into a single virtual device on the Data Mover. Like Ethernet Channel, by combining many links into a single virtual device you get: Increased Availability (A single link failure does not break the link) Port Distribution (The link used for communication with another computer is determined from the source and destination MAC addresses) Better Link Control (LACP is able to detect broken links passing LACPDU, Link Aggregation Control Protocol Data Unit, frames between the Data Mover and the Ethernet switch) Networking Features Networking Features

Ethernet Channel and LACP Comparison
Feature Ethernet Channel Link Aggregation Switch Support Switch must use IEEE standard, Fast or Gig Ethernet Switch must support IEEE 802.3ad Link Aggregation Link Speeds Allows links of different speeds Disables links with a different speed than the majority Duplex Full or half Full Number of Ports 2, 4, or 8 2 - 12 Availability Broken links are physically marked as “up” on the Data Mover, but the switch will detect the down link and redirect traffic to the Data Mover down other links Better link control: LACPDU frames are transmitted on each link in the aggregation to ensure they are not broken Misconfiguration Protection Misconfigured links difficult to detect Detects misconfigured links and marks them as down Shown here is a comparison of Ethernet Channel and Link Aggregation. A customer may have reasons to utilize one technology over another. Networking Features Networking Features

VNX Use of Statistical Load Distribution
Applies for Ethernet Channels and Link Aggregation devices Three methods of statistical load distribution MAC address IP address (default) IP address and TCP port Port Failure Traffic redirect to live port Incoming and outgoing traffic ports may differ Once an Ethernet Channel (or LACP aggregation) is configured, the Ethernet switch must make a determination as to which physical port to use for a connection. Three statistical load distribution methodologies are available on the VNX; distribution by MAC address, by IP address or by a combination of IP address and TCP port. MAC Address - The Ethernet switch will hash enough bits (1 bit for 2 ports, 2 bits for 4 ports, and 3 bits for 8 ports) of the source and/or destination MAC addresses of the incoming packet through an algorithm (the addresses and the algorithm used are specific to the IOS of the Ethernet switch). The result of the hashing will be used to decide which physical port through which to make the connection. Example: The example below shows the four possible algorithm results of hashing two bits, as well as the port that will be used for that connection. Binary Result - Switch port , , , Keep in mind that traffic coming from a remote network will contain the source MAC address of the router interface nearest the switch. This could skew the algorithm’s outcome and mean that all traffic from the remote network will be directed through the same interface in the channel. IP address - The source and destination IP ports are considered when determining the output port. IP is the default setting. IP address and TCP port - The source and destination IP addresses and ports are considered when determining the output port Configuration - Statistical load distribution can be configured for the whole system by setting the LoadBalance= parameter in the global or local parameters file. It can also be configured per trunk by using the server_sysconfig command. Configuring load distribution on a per trunk basis overrides the entry in the parameters file. Configured via: Parameters file entry : LoadBalance=mac, tcp, or ip server_sysconfig (per aggregation) Networking Features Networking Features

Fail Safe Network Extends link failover by providing switch-level redundancy A FSN appears as a single link with a single MAC address, and potentially multiple IP addresses A FSN is comprised of a physical port, Ethernet Channel, Link Aggregation or any combination of the three Only one connection in a FSN is active at a time There is no requirement that the connections making up a FSN be the same type, or that the connections be made to the same network switch Fail Safe Network (FSN) is a virtual network interface feature of the VNX. Like Ethernet Channel and Link Aggregation, FSN supplies fault tolerance out beyond the physical box of the Data Mover, providing redundancy for cabling and switch ports. But, unlike Ethernet Channel and Link Aggregation, FSN can also provide fault tolerance in the case of switch failure. While Ethernet Channel provides redundancy across active ports (all ports in the channel carrying traffic), FSN is comprised of an active and a standby interface. The standby interface does not send or respond to any network traffic. FSN operation is independent of the switch. Ethernet Channel and Link Aggregation both require an Ethernet switch that supports their corresponding protocols. This is not the case with FSN because it is simply a combination of an active and standby interfaces with failover being orchestrated by the Data Mover itself. Additionally, the two members of the FSN device can be connected to separate Ethernet switches. Networking Features Networking Features

Cross-Stack EtherChannel
Cross-Stack Switches Stack A Switch 1 Switch 2 Switch 3 Cross-Stack EtherChannel In addition to FSNs, VNX supports Ethernet Channel or Link Aggregation configurations that span multiple switches in a single stack, provided the switches support the Cross-Stack feature. There is no additional configuration required on the Data Movers, but there will be specific configuration required by the network administrator. Refer to the switch vendor documentation for details on this configuration. Cross- Stack can span an EtherChannel across two switches. All of the links of the EtherChannel will be active at any time. So if you configured an EtherChannel using four ports on a Data Mover and connected two ports to each of two switches configured for Cross-Stack, your traffic would be flowing across all 4 ports. If you made the same configuration with FSN, you would only be able to have traffic flowing across two active ports, while the other 2 ports would be in a standby state. If the network environment has Cross-Stack capable switches, this configuration would provide greater aggregate bandwidth than an FSN implementation, as there are no active/passive links in a Cross-Stack EtherChannel unless there are more links configured than the standard supports. Networking Features Networking Features

Networking Features Lesson 1: Summary
During this lesson the following topics were covered: Basic network concepts and terminology VLANs and VLAN tagging Roles of networking features Types of virtual devices Physical, virtual and logical interfaces on a Data Mover This lesson covered basic networking concepts, terminology and described VLANs and virtual devices. Networking Features Networking Features

Networking Features Lesson 2: Networking Features Configuration
During this lesson the following topics are covered: Creating an Ethernet Channel device Creating a LACP device Creating a FSN device Creating VLAN IDs on an interface This lesson will demonstrate how to create an Ethernet Channel, a LACP device, a FSN device and VLAN IDs. Networking Features Networking Features

VNX Network Terminology Review
Physical Device (device name) The actual ports on the Data Mover (e.g., cge-1-0, fge-2-3) Not a variable Virtual Device (device name) User assigned variable name Combination of multiple physical devices Logical Interface (interface name) User/System assigned variable name Assigned an IP address These terms are commonly confused, which can lead to improper implementation. They are referred to throughout this module. Networking Features Networking Features

Physical Device (device name)
The physical port on a Data Mover cge = Copper Gigabit Ethernet fge = Optical Gigabit Ethernet fxg = Optical 10 Gigabit Ethernet Not a variable Can support multiple interfaces/IP addresses with VLAN Tagging 10/100/1000 Mbps or 10 Gbps Half/Full/Auto This is a VNX Data Mover enclosure physical device component review. The I/O modules available for the VNX are shown (left to right): 4 port copper Gigabit Ethernet module 2 port copper Gigabit Ethernet and 2 port Optical Gigabit Ethernet module 2 port Optical 10 Gigabit Ethernet module Networking Features Networking Features

Physical - Logical (device – interface)
No virtual devices in this configuration An interface name is created and an IP address is assigned using a physical copper Gigabit Ethernet port on a primary Data Mover Other IP addresses can be created on the same physical interface Interface name must differ VLAN Tagging may be required Differentiating between physical and logical can be difficult. This is especially true if the device name and interface name are the same value. Example: It is possible to create an interface called “cge-1-0” on physical device cge-1-0. Networking Features Networking Features

Physical - Virtual - Logical
Two physical devices (cge-1-0 and cge-1-1) are used to create a virtual device lacp0 using the LACP Protocol An IP address is assigned using the virtual device lacp0 Other IP address can be created on the same virtual interface interface name must differ VLAN Tagging As stated in the previous slide, differentiating between physical and logical can be difficult. In order to represent multiple physical devices as one logical device, a virtual device must be created. Networking Features Networking Features

Creating a Virtual Device
Cannot use physical devices that have previously been used They will not be displayed Standby Data Mover(s) will inherit configuration Ethernet switch should be setup in advance (required for Ethernet Channel and Link Aggregation) Primary Variables Data Mover Type Ethernet Channel Link Aggregation Fail Safe Network Device Name User must configure Settings > Network > Settings for File > Devices > Create This is a slide meant to address the general topic of virtual device creation. The possible selections and options are explored in further detail in later slides. Networking Features Networking Features

Creating an Ethernet Channel Virtual Device
Settings > Network > Settings for File > Devices (tab) > Create Select Data Mover Select Ethernet Channel Enter Device Name Select Ports Select Speed/Duplex Should be set to match Ethernet switch settings This slide shows how to configure an Ethernet Channel virtual device using Unisphere. To create an Ethernet Channel virtual device via CLI, use the following commands to combine the Data Mover’s physical network ports into one logical device. Command: server_sysconfig <movername> –virtual –name <virtual_device_name> –create trk –options “device=<device>,<device> [lb=<mac|ip|tcp>]” Example: Combine ports cge-1-0 and cge-1-1 into a virtual device using Ethernet Channel named trk0 server_sysconfig server_2 –virtual –name trk0 –create trk –options “device=cge-1-0,cge-1-1” From Device tab Networking Features Networking Features

Creating a Link Aggregation Virtual Device
Settings > Network > Settings for File > Devices (tab) > Create Select Data Mover Select Link Aggregation Enter Device Name Select ports Select Speed/Duplex Should be set to match Ethernet switch settings Note: cge-1-0 and cge-1-1 are not listed because they are already in use This slide shows how to configure a Link Aggregation virtual device using Unisphere. To create a Link Aggregation virtual device via CLI, use the following commands to combine the Data Mover’s physical network ports into one logical device. Command: server_sysconfig server_x –virtual –name <virtual_device_name> –create trk –options “device=<device,device> protocol=lacp” Example: server_sysconfig server_2 -virtual –name lacp0 -create trk -options "device=cge-1-2,cge-1-3 protocol=lacp” Verifying that ports are up and running: One way to verify all of the ports are up and running would be to run show port lacp-channel statistic (on a Cisco Systems switch). Each time the command is run you can see that the LACPDU packet reports have changed for active ports. Monitoring the number of Ibytes and Obytes: Use the server_netstat -i command to monitor the number of Ibytes and Obytes (Input and Output bytes) for each port. From Device tab Networking Features Networking Features

Creating a FSN Virtual Device
Settings > Network > Settings for File > Devices (tab) > Create Select Data Mover Select Fail Safe Network Enter Device Name Select Devices Primary (optional) Standby Can combine Dissimilar Ethernet devices Virtual and physical devices Like Ethernet Channel and Link Aggregation, the FSN virtual device is created using the server_sysconfig command. The FSN device is used for the -Device parameter in the server_ifconfig IP configuration. The FSN virtual device can be based of any combination of like or dissimilar physical or virtual devices. Example: FE with FE GbE with GbE GbE with FE Ethernet Channel with FE Ethernet Channel with GbE Link Aggregation with FE Link Aggregation with GbE Ethernet Channel with Link Aggregation The slide shows a FSN created using an Ethernet Channel and a Link Aggregation virtual device. They are configured as a standby/standby with trk0 coming up as the active side of the FSN. Command: server_sysconfig server_x –virtual –name <virtual_device_name> –create fsn –options “device=<device,device>” Example: server_sysconfig server_2 -virtual -name fsn0 -create fsn -option “device=lacp0,trk0" From Device tab Networking Features Networking Features

FSN Role of Primary and Standby
Primary should be used if members are not equal The primary is a better data path More reliable Faster Optional Standby Will support failed link Will not fail back when primary failure is corrected This slide shows how to configure a FSN device with a primary device defined using Unisphere. The FSN is configured with lacp0 set as the primary and trk0 as standby. When the “primary” option is specified, the primary device will always be the active device (except when it is in a failed state). This is generally not recommended because of the adverse effect on network performance when operating in conjunction with a degraded primary device. To create a FSN specifying a primary device (not recommended) use the configuration shown here, or from the CLI do the following: Command: server_sysconfig server_x –virtual –name <fsn_name> –create fsn –option “primary=<primary_dev> device=<standby_dev>” Example: server_sysconfig server_2 –virtual –name fsn0 –create fsn –option “primary=lacp0 device=lacp0,trk0” From Device tab Networking Features Networking Features

Creating a Data Mover Interface
IP address are assigned to Virtual devices same as Physical devices Physical devices used by Virtual devices will not be selectable Auto calculating Broadcast Address Default optional values Name: The IP address with the value “-” replacing “.” would be MTU: 1500 VLAN ID: 0 This information was discussed in detail in the Basic Network Configuration module. Once the virtual device has been created, use the server_ifconfig command to assign an IP address to the virtual device. Be sure to use the name designated for the –name parameter in the server_sysconfig command as the device parameter in the server_ifconfig statement. Example: In the command below, the –Device fsn0 parameter refers to the virtual device that was created (on the previous page) using the –name fsn0 parameter. The –name parameter used in this command here defines the interface name. After the protocol IP statement, provide the IP address, the subnet mask and the broadcast address. server_ifconfig server_2 –create –Device fsn0 –name fsn0-1 –protocol IP Networking Features Networking Features

Managing Virtual Devices
Settings > Network > Settings for File > Devices Right-click on device and select properties for more detail Adjust speed and duplex This slide shows how to list all virtual devices using Unisphere. To display a list of virtual devices via CLI: Command: server_sysconfig <movername> –virtual ~]$ server_sysconfig server_2 -virtual server_2 : Virtual devices: fsn0 active=lacp0 primary=lacp0 standby=trk0 lacp0 devices=cge-1-2 cge-1-3 :protocol=lacp trk0 devices=cge-1-0 cge-1-1 fsn failsafe nic devices : fsn0 trk trunking devices : lacp0 trk0 Networking Features Networking Features

Deleting Virtual Devices
Settings → Network → Settings for File → Devices Select item for removal; right click > select delete, or click on delete button Can only delete one virtual device at a time Cannot delete devices that have dependencies In use by CIFS server In use by another virtual device Virtual devices must be deleted in the reverse order from how they were created This slide shows how to delete virtual devices using Unisphere. To delete virtual devices via CLI: Command: server_sysconfig server_x –virtual –delete <device> Example: server_sysconfig server_2 –virtual –delete fsn0 Networking Features Networking Features

During this lesson the following topics were covered: Creating an Ethernet Channel device Creating a LACP device Creating a FSN device Creating VLAN IDs on an interface This lesson covered Ethernet Channel, LACP, and FSN devices, as well as VLAN IDs. Networking Features Networking Features

Networking Features Lesson 3: Complex Examples and Considerations
During this lesson the following topics are covered: Network features to support a complex environment VNX and Ethernet switch requirements Active data paths in case of failure Networking high availability considerations This lesson covers requirements and consideration when it comes to implementing networking features. Networking Features Networking Features

VNX Configuration lacp1 fsn0 lacp0
Two physical devices (cge-1-0 and cge-1-1) are used to create a virtual device “lacp0” on a Data Mover Two physical devices (cge-1-2 and cge-1-3) are used to create another virtual device “lacp1” on a Data Mover Both Virtual devices (lacp0,lacp1) are used to create another Virtual device “fsn0” An IP address is assigned using the virtual device fsn0 This slide explains VNX Network configuration for LACP and FSN. Networking Features Networking Features

Optional: Creating Multiple Logical Interfaces
If connection to a single network segment is not enough, use VLAN Tagging IP addresses are on different network segments (different VLANs) VLAN value provided by Ethernet switch administrator Set VLAN ID to match Ethernet switch value Example: If fsn0 uses all ports and customer needs to connect to multiple network segments, VLAN Tagging should be used To configure multiple logical interfaces using one physical device and assign a VLAN tag, use the following commands: Command: server_ifconfig server_x -create –Device <device name> -name <interface name> -protocol IP <IP address> <subnet mask> <broadcast address> vlan=<VLAN ID> Examples: server_ifconfig server_2 –create –Device fsn0 -name fsn0-1 -protocol IP vlan=45 server_ifconfig server_2 –create –Device fsn0 -name fsn0-2 -protocol IP vlan=41 To assign a VLAN tag to an existing interface: server_ifconfig server_x <interface name> vlan=<VLAN ID> server_ifconfig server_2 fsn0-1 vlan=45 server_ifconfig server_2 fsn0-2 vlan=41 To remove the VLAN tag: Example: server_ifconfig server_2 fsn0-1 vlan=0 Networking Features Networking Features

Ethernet Switch Configuration
lacp0=cge-1-0,cge-1-1 (primary) fsn0 lacp1=cge-1-2,cge-1-3 (secondary) Switch Switch This slide shows a FSN device that consists of a LACP device called lacp0 (comprised of cge-1-0, cge-1-1) and another LACP device called lacp1 (comprised of cge-1-2, cge-1-3). Both virtual devices connect to different switches, and the switches would need to be configured to support the LACP configuration. The active device, lacp0, is used for all network traffic, unless both paths in that virtual device fail, or if the switch fails. If that occurred, lacp1 with its associated switch would take over network traffic for the Data Mover. Network Networking Features Networking Features

Example: Active Data Path
Phase 1: Normal Operation Phase 3: Port failures Phase 5: Failure resolved (no primary) Device Virtual Device Status cge-1-0 lacp0 fsn0 Active cge-1-1 cge-1-2 lacp1 Standby cge-1-3 Device Virtual Device Status cge-1-0 lacp0 fsn0 Off-line cge-1-1 cge-1-2 lacp1 Active cge-1-3 Device Virtual Device Status cge-1-0 lacp0 fsn0 Standby cge-1-1 cge-1-2 lacp1 Active cge-1-3 Phase 2: Port failure Phase 4: Port failures Phase 5: Failure resolved (primary=lacp0) Device Virtual Device Status cge-1-0 lacp0 fsn0 Off-line cge-1-1 Active cge-1-2 lacp1 Standby cge-1-3 Device Virtual Device Status cge-1-0 lacp0 fsn0 Off-line cge-1-1 cge-1-2 lacp1 cge-1-3 Active Device Virtual Device Status cge-1-0 lacp0 fsn0 Active cge-1-1 cge-1-2 lacp1 Standby cge-1-3 The five phases illustrated above show how the data path is altered as failures occur. In this example consider data passing through cge0, and trace the data path through each failure. Phase 1: This phase shows normal operation. Phase 2: The network connection between the Ethernet switch and cge-1-0 has failed. Traffic from cge-1-0 is being redirected towards cge-1-1. Note: lcap0 is still the active path. Phase 3: The network connection between the Ethernet switch and cge-1-1 has failed. This causes lacp0 to be unavailable and the VNX (via FSN) redirects the traffic towards lacp1. The data path is now on cge-1-2 and cge-1-3. Phase 4: The network connection between the Ethernet switch and cge-1-2 has failed. Traffic from cge-1-2 is being redirected towards cge-1-3. Phase 5: (no primary) When the links are restored, the Data Mover does not redirect the FSN data path to lacp0. Data may flow back through cge-1-2, but the data path will be via lacp1. Lacp0 is now in standby mode. Phase 5: (primary = lacp0) When the links are restored, the Data Mover redirects the FSN data path to lacp0. Data will flow back through cge-1-0 and cge-1-1. Lacp1 is now in standby mode. Networking Features Networking Features

Speed and Duplex Considerations
VNX speed and duplex setting must match Ethernet switch Failure to address has negative results Failure to connect Performance problems Creation of an Ethernet Channel or Link Aggregation device requires user to set speed and duplex (default = 1000 FD) An FSN device inherits speed and duplex currently configured on member devices See Basic Network Configuration module for more information The speed and duplex setting on each interface must match the settings on the Ethernet switch. If the switch is set to auto-negotiate the speed and duplex, and the interface is hard-coded for 1000FD, the link will fail to connect and give performance problems. A FSN device inherits the speed and duplex settings configured on its member devices. For additional information on speed and duplex settings, see the Basic Network Configuration module in this course. Networking Features Networking Features

Data Mover Failover Network Considerations
Failed network connections do not trigger Data Mover failover Data Mover is operating normally, network is not Standby Data Mover requires identical configuration Any Ethernet Channels or Link Aggregation devices require same configuration on Ethernet switch Any trunk ports used with VLAN tagging require same configuration on Ethernet switch Test configuration when deploying configuration Incorrect configuration for standby Data Mover could cause service interruption in failover situation Any failed network connections will not trigger a Data Mover failover. To protect the environment from service interruption or data unavailability, utilize the network features that help protect against port, cable and switch failures. The standby Data Mover will inherit any configuration from the primary Data Mover that fails over, but the switch ports that are attached to the standby Data Mover must be configured with the same options as the ports attached to the primary Data Mover. If the primary Data Mover has two LACP trunks configured with two ports each, then the ports attached to the standby Data Mover must have two LACP trunks configured with two ports each as well. In addition, if there is manual VLAN pruning in use, the trunks to the standby Data Mover must also be configured to allow the necessary VLANs for the same VLANs that the primary Data Movers’ trunks are configured to allow. To ensure that the configuration is correctly deployed, test failover before utilizing the machine for production. Configure a CIFS share or NFS export on each primary Data Mover and ensure there is connectivity before and after failover. If this is not tested before a real failover situation, it could cause data unavailability or service interruption for clients until the configuration can be corrected or the primary Data Mover is restored. Networking Features Networking Features

Confirming the Ethernet Switch
Confirm channels have been created (if required) Cisco EtherChannel LACP Typical for EMC personnel not to have access to Ethernet Switch devices Dependency on customer to provide information Confirm trunk ports have been created (if required) Commands used to create channels are issued on the VNX AND Ethernet Switch To confirm that the configuration has been successfully completed, verify that the trunks have been configured on the switch. Typically, EMC personnel will not have access to the switches in the environment. If this is the case, there is a dependency on the site network administrator to provide the information. For specific switch configuration information, reference “Configuring and Managing Network High Availability on VNX 7.0” available on Powerlink. The commands to create the channels are issued independently to the VNX and to the Ethernet switch. The order doesn’t matter, as the links will not connect until both sides have been correctly configured. Networking Features Networking Features

LACP Considerations A LACP link can be created with any number of physical devices Only Full Duplex Ethernet ports can be used to create the link If a mixture of port speeds is given, the Data Mover will choose the greatest number of ports at the same speed In case of a tie, the fastest ports are chosen Although multiple links are joined, no one client will gain an advantage from this configuration with regards to network speed or throughput Link determined by source/destination IP address Can also load balance based on source/destination MAC address or source/destination IP address AND source/destination TCP/UDP ports A LACP link can be created with any number of physical devices, but only full duplex can be utilized over the link. This means that if one side is hard-coded for full duplex and the other side is coded to auto-negotiate, the auto-negotiate side will be unsuccessful in link negotiations and will default to half duplex and the LACP trunk will not form. In addition, if a mixture of port speeds is used to configure the link, the LACP standard specifies that the greatest number of ports with the same speed will be used for the link. In other words, if there are four links running at 100 Mbps and two links running at 1000 Mbps, the link will disable the two links running 1000 Mbps and use the four slower 100 Mbps links instead. However, if there are four links at 100 Mbps and four links at 1000 Mbps, the four links at 1000 Mbps will be used. Although multiple links are joined and aggregate bandwidth is increased over the trunk, no single client will necessarily receive an increase in throughput depending upon the type of load balancing utilized over the trunk. In order to get the best load balancing per host possible, use the load balancing algorithm that includes TCP/UDP port numbers. By default, the source and destination IP addresses are used to determine load balancing. Networking Features Networking Features

During this lesson the following topics were covered: Network features to support a complex environment VNX and Ethernet switch requirements Active data paths in case of failure Networking high availability considerations This lesson covered requirements and consideration when it comes to implementing networking features. Networking Features Networking Features

Summary Key points covered in this module:
Virtual network devices extend fault tolerance into the network by providing port redundancy FSN protects against switch failures High Availability solution need to include aligned switch port configurations for Primary and Standby Data Movers Listed are the key points covered in this module. Networking Features Networking Features

Networking Features Networking Features

Networking Features Upon completion of this module, you should be able to: Discuss and configure VNX networking features This module continues the discussion.

Similar presentations

Presentation on theme: "Networking Features Upon completion of this module, you should be able to: Discuss and configure VNX networking features This module continues the discussion."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Networking Features Upon completion of this module, you should be able to: Discuss and configure VNX networking features This module continues the discussion.

Similar presentations

Presentation on theme: "Networking Features Upon completion of this module, you should be able to: Discuss and configure VNX networking features This module continues the discussion."— Presentation transcript:

Similar presentations

About project

Feedback