H3C S7500X Series Configuration Manual
H3C S7500X Series Configuration Manual

H3C S7500X Series Configuration Manual

Hide thumbs Also See for S7500X Series:

Advertisement

Quick Links

H3C S7500X Switch Series
Comware 7 EVI Configuration Guide
New H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: Release 7577P04 and later versions
Document version: 6W100-20190315

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the S7500X Series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for H3C S7500X Series

  • Page 1 H3C S7500X Switch Series Comware 7 EVI Configuration Guide New H3C Technologies Co., Ltd. http://www.h3c.com Software version: Release 7577P04 and later versions Document version: 6W100-20190315...
  • Page 2 The information in this document is subject to change without notice. All contents in this document, including statements, information, and recommendations, are believed to be accurate, but they are presented without warranty of any kind, express or implied. H3C shall not be liable for technical or editorial errors or omissions contained herein.
  • Page 3 Preface This configuration guide describes EVI fundamentals and configuration. It describes how to use MAC-in-IP technology Ethernet Virtual Interconnect (EVI) to provide Layer 2 connectivity between distant Layer 2 network sites across an IP routed network. EVI enables dynamic allocation and management of resources and transparent migration of virtual machines between network sites.
  • Page 4 Convention Description Multi-level menus are separated by angle brackets. For example, File > Create > > Folder. Symbols Convention Description An alert that calls attention to important information that if not understood or followed WARNING! can result in personal injury. An alert that calls attention to important information that if not understood or followed CAUTION: can result in data loss, data corruption, or damage to hardware or software.
  • Page 5 It is normal that the port numbers, sample output, screenshots, and other information in the examples differ from what you have on your device. Documentation feedback You can e-mail your comments about product documentation to info@h3c.com. We appreciate your comments.
  • Page 6: Table Of Contents

    Contents Configuring EVI ··············································································· 1     Overview ·································································································································· 1   Layer 2 connectivity extension issues ······················································································ 1   Network topologies ·············································································································· 2   Terminology ······················································································································· 3   Working mechanism ············································································································ 3   ARP flood suppression ········································································································· 6   Selective flooding ················································································································ 7  ...
  • Page 7: Configuring Evi

    Configuring EVI Overview Ethernet Virtual Interconnect (EVI) is a MAC-in-IP technology that provides Layer 2 connectivity between distant Layer 2 network sites across an IP routed network. It is used for connecting geographically dispersed sites of a virtualized large-scale data center that requires Layer 2 adjacency (see Figure EVI enables long-distance virtual machine workload mobility and data mobility, disaster recovery,...
  • Page 8: Network Topologies

    Network topologies As shown in Figure 2, an EVI network has one edge device at each site. These sites are connected through virtual links and run the EVI IS-IS protocol to advertise their MAC address entries to each other. EVI maintains MAC routing information on the edge devices without changing the forwarding or routing information within the sites or the transport network.
  • Page 9: Terminology

    Terminology Edge device An edge device performs typical Layer 2 learning and forwarding on the site-facing interfaces (internal interfaces) and performs tunneling and routing on the transport-facing interfaces. EVI network ID An edge device can belong to multiple EVI networks. Each EVI network is uniquely identified by a network ID.
  • Page 10 Forwards traffic based on MAC reachability information that has been received from other sites. This section describes this process in detail. Neighbor discovery An EVI network runs ENDP to discover all its edge devices and establishes adjacencies among the edge devices in the following process: ENDS is enabled on one edge device, and ENDC is enabled on all other edge devices.
  • Page 11 Figure 4 Layer 2 forwarding in a site Transport network MAC table VLAN Interface MAC1 GE1/0/1 MAC2 GE1/0/2 GE1/0/1 GE1/0/2 Host A Host B MAC1 MAC2 Site 1 Site 2 The following forwarding process (see Figure 5) takes place for unicast flows between sites: The source edge device learns the source MAC address of the incoming Ethernet frame, and looks up the destination MAC address in its MAC table for the outgoing interface.
  • Page 12: Arp Flood Suppression

    Figure 5 Layer 2 forwarding between sites Multicast flow The EVI implementation of the device does not support multicast forwarding between sites based on the multicast forwarding table. By default, the device does not forward multicast traffic to remote sites. To forward traffic destined for a multicast MAC address to remote sites, you must enable selective flooding for the address.
  • Page 13: Selective Flooding

    ARP flood suppression uses the following workflow: Host IP1 in site A sends an ARP request to obtain the MAC address of IP2. Site A's edge device floods the ARP requests out of all interfaces, including the EVI tunnel interfaces. Site B's edge device de-encapsulates the ARP request and broadcasts the request.
  • Page 14: Configuration Restrictions And Guidelines

    Configuration restrictions and guidelines For EVI to operate correctly, follow the restrictions and guidelines in this section. Licensing requirements EVI requires a license to run on the device. For information about feature licensing, see Fundamentals Configuration Guide. Feature and hardware compatibility You can enable EVI only on interfaces on the following modules: •...
  • Page 15: Configuring Evi Basic Features

    Tasks at a glance Remarks after the interface is created. You can tune EVI IS-IS parameters for optimizing network performance. Perform this task to reduce ARP (Optional.) Enabling EVI ARP flood suppression request broadcasts on an EVI network. Perform this task to flood frames (Optional.) Enabling EVI flooding for all destination-unknown frames with unknown MAC addresses to...
  • Page 16: Assigning A Network Id To The Evi Tunnel

    Step Command Remarks interface view. mode. For more information about this command, see tunneling commands in Layer 3—IP Services Command Reference. By default, no source IP address or source interface is specified for any tunnel. The source interface can be a Layer 3 Ethernet interface, Layer 3 aggregate interface, VLAN interface, or Layer 3 loopback interface.
  • Page 17: Specifying Extended Vlans On The Evi Tunnel

    Step Command Remarks Enter system view. system-view interface tunnel number Enter tunnel interface view. [ mode evi ] Specify a network ID. evi network-id number By default, no network ID is specified. Specifying extended VLANs on the EVI tunnel When configuring extended VLANs, follow these guidelines: •...
  • Page 18: Enabling Evi On Transport-Facing Physical Interfaces

    Configuring the edge device as an ENDS on the EVI tunnel Step Command Remarks Enter system view. system-view Enter EVI tunnel interface tunnel number interface view. [ mode evi ] By default, ENDS is disabled. On an ENDS-enabled tunnel interface, you can use the evi neighbor-discovery client evi neighbor-discovery Enable ENDS.
  • Page 19: Tuning Evi Is-Is Parameters

    Step Command Remarks Ethernet interface view. By default, EVI is disabled on all Enable EVI on the interface. evi enable interfaces. Tuning EVI IS-IS parameters EVI IS-IS automatically runs on an EVI link immediately after the link is set up. You can tune EVI IS-IS parameters to optimize the protocol performance.
  • Page 20: Optimizing An Evi Is-Is Network

    The ID of an automatically created process is the same as the EVI tunnel interface number. Alternatively, you can use the evi-isis command to create an EVI IS-IS process manually. To delete a manually created EVI IS-IS process, you must use the undo evi-isis command. •...
  • Page 21 Configuring the hello multiplier for calculating the adjacency hold time Adjacency hold time is the amount of time that the remote edge devices can retain the adjacency with the local edge device before an adjacency update. • If Graceful Restart is disabled, the adjacency hold time equals the EVI IS-IS hello interval multiplied by the hello multiplier.
  • Page 22 Step Command Remarks Enter system view. system-view interface tunnel number [ mode Enter tunnel interface view. evi ] Configure the CSNP transmit By default, a DED sends CSNP evi isis timer csnp seconds interval. packets every 10 seconds. Configuring the minimum LSP transmit interval and the maximum number of LSPs sent at each interval The edge device generates an LSP update when any LSDB content changes.
  • Page 23 Step Command Remarks Enter system view. system-view Enter EVI IS-IS evi-isis process-id process view. The default LSP refresh interval is 900 seconds. The minimum LSP transmit interval and the Configure the LSP maximum number of LSPs sent at each interval timer lsp-refresh seconds refresh interval.
  • Page 24: Specifying A Routing Policy For An Evi Is-Is Process

    Specifying a routing policy for an EVI IS-IS process You can configure a routing policy to match MAC reachability information that can be advertised to the remote EVI sites. The routing policy is also called a reachability information filtering policy. The routing policy for EVI IS-IS can only contain the following filters: •...
  • Page 25: Configuring Graceful Restart For An Evi Is-Is Process

    Context is a method introduced to SNMPv3 for multiple-instance management. For SNMPv1/v2c, you must specify a context name as a community name for protocol identification. To configure SNMP notifications and context for an EVI IS-IS process: Step Command Remarks Enter system view. system-view snmp-agent trap enable evi-isis [ adjacency-state-change |...
  • Page 26: Increasing The Maximum Number Of Mac Entries In An Lsp For An Evi Is-Is Process

    Increasing the maximum number of MAC entries in an LSP for an EVI IS-IS process An EVI IS-IS process advertises all local MAC reachability information in one LSP. By default, an LSP can convey up to 55 x 2 MAC address entries. To increase this number to accommodate all local MAC address entries, create virtual systems.
  • Page 27: Enabling Evi Flooding For All Destination-Unknown Frames

    Enabling EVI flooding for all destination-unknown frames By default, the device floods unknown unicast and multicast frames only to internal interfaces. EVI flooding enables the device to flood all destination-unknown frames to an EVI tunnel interface. To enable EVI flooding for all destination-unknown frames: Step Command Remarks...
  • Page 28 Task Command display evi neighbor-discovery server member [ interface On an ENDS, display IPv4 neighbors tunnel interface-number | [ local local-ip | remote client-ip ] that have registered with the ENDS. [ vpn-instance vpn-instance-name ] ] display evi neighbor-discovery server statistics interface On an ENDS, display ENDS statistics.
  • Page 29: Evi Configuration Examples

    Task Command reset evi isis all [ process-id ] Clear data for EVI IS-IS processes. Clear ENDP packet statistics on an reset evi neighbor-discovery client statistics interface tunnel ENDC. interface-number Clear ENDP packet statistics on an reset evi neighbor-discovery server statistics interface ENDS.
  • Page 30 [SwitchA-vlan10] port gigabitethernet 1/0/1 [SwitchA-vlan10] quit [SwitchA] interface vlan-interface 10 [SwitchA-Vlan-interface10] ip address 1.1.1.1 24 [SwitchA-Vlan-interface10] quit # Create an IPv4 EVI tunnel interface. [SwitchA] interface tunnel 1 mode evi # Set the network ID to 1 for the EVI tunnel interface. [SwitchA-Tunnel1] evi network-id 1 # Specify the IP address of VLAN-interface 10 as the source IP of the EVI tunnel.
  • Page 31 # Specify the IP address of VLAN-interface 10 as the source IP of the EVI tunnel. [SwitchB-Tunnel1] source 1.1.2.1 # Set the tunnel keepalive interval to 20 seconds and the maximum number of transmissions to [SwitchB-Tunnel1] keepalive 20 2 # Specify extended VLANs on the EVI tunnel interface. [SwitchB-Tunnel1] evi extend-vlan 21 to 100 # Configure Switch B as an ENDC of Switch A.
  • Page 32 [SwitchA] display interface tunnel 1 Tunnel1 Current state: UP Line protocol state: UP Description: Tunnel1 Interface Bandwidth: 64 kbps Maximum transmit unit: 64000 Internet protocol processing: Disabled Tunnel source 1.1.1.1 Tunnel keepalive enabled, Period(20 s), Retries(2) Network ID 1 Tunnel protocol/transport GRE_EVI/IP Output queue - Urgent queuing: Size/Length/Discards 0/100/0 Output queue - Protocol queuing: Size/Length/Discards 0/500/0 Output queue - FIFO queuing: Size/Length/Discards 0/75/0...
  • Page 33 1.1.2.1 000F-0001-0002 2013/01/01 12:12:12 1.1.3.1 000F-0001-0003 2013/01/01 12:12:12 # Verify that MAC addresses in VLAN 100 have been filtered by the routing policy on Switch A. [SwitchA] display evi isis local-mac dynamic Process ID: 0 Tunnel interface: Tunnel1 VLAN ID: 100 MAC address: 0001-0100-0001 (Filtered) MAC address: 0001-0100-0002 (Filtered) MAC address: 0001-0100-0003 (Filtered)
  • Page 34 Interface Status Source Destination EVI-Link0 1.1.2.1 1.1.1.1 EVI-Link1 1.1.2.1 1.1.3.1 # Display ENDC information. [SwitchB] display evi neighbor-discovery client summary Status: I-Init E-Establish P-Probe Interface Local Address Server Address Network ID Reg Auth Status Vpn-instance Tunnel1 1.1.2.1 1.1.1.1 disabled [No Vrf] # Display neighbor entries that Switch B has learned.
  • Page 35: Multiple-Evi-Networks Configuration Example

    # Display information about EVI links on Switch C. [SwitchC] display evi link interface tunnel 1 Interface Status Source Destination EVI-Link0 1.1.3.1 1.1.1.1 EVI-Link1 1.1.3.1 1.1.2.1 # Display ENDC information. [SwitchC] display evi neighbor-discovery client summary Status: I-Init E-Establish P-Probe Interface Local Address Server Address Network ID Reg Auth...
  • Page 36 Traffic type Network ID Extended VLANs Sites 50, 80 1, 4 In each EVI network, use the edge device at site 4 as an ENDS and all other edge devices as its ENDCs. Figure 8 Network diagram Site 2 GE1/0/1 Vlan-int10 172.16.2.1/24 Tunnel102...
  • Page 37 [Site4-Tunnel102] source 172.16.4.1 [Site4-Tunnel102] evi network-id 2 [Site4-Tunnel102] evi extend-vlan 4000 [Site4-Tunnel102] evi neighbor-discovery server enable [Site4-Tunnel102] quit # Configure the Web service EVI network. [Site4] interface tunnel 103 mode evi [Site4-Tunnel103] source 172.16.4.1 [Site4-Tunnel103] evi network-id 3 [Site4-Tunnel103] evi extend-vlan 50 to 80 [Site4-Tunnel103] evi neighbor-discovery server enable [Site4-Tunnel103] quit # Enable EVI on GigabitEthernet 1/0/1.
  • Page 38 Verifying the configuration # Display neighbors registered with the ENDS in each EVI network. [Site4] display evi neighbor-discovery server member Interface: Tunnel101 Network ID: 1 Vpn-instance: [No Vrf] IP Address: 172.16.4.1 Client Address System ID Expire Created Time 172.16.2.1 000F-0001-0002 2013/01/01 00:00:43 172.16.3.1 000F-0001-0003...

Table of Contents