H3C S7500E-X Series Configuration Manual
H3C S7500E-X Series Configuration Manual

H3C S7500E-X Series Configuration Manual

Comware 7 evi switch
Hide thumbs Also See for S7500E-X Series:

Advertisement

Quick Links

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

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the S7500E-X Series and is the answer not in the manual?

Questions and answers

Summary of Contents for H3C S7500E-X Series

  • Page 1 H3C S7500E-X Switch Series Comware 7 EVI Configuration Guide New H3C Technologies Co., Ltd. http://www.h3c.com Software version: Release 7577P01 and later versions Document version: 6W100-20190110...
  • 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 Configuring EVI basic features: • (Optional.) Configuring a site ID • An EVI tunnel can provide services (Required.) Configuring an EVI tunnel: for only one EVI network. (Required.) Assigning a network ID to the EVI tunnel An extended VLAN can be (Required.) Specifying extended VLANs on the EVI tunnel...
  • Page 16: Configuring An Evi Tunnel

    Configuring an EVI tunnel Step Command Remarks Enter system view. system-view By default, no tunnel interface exists. Create an EVI The endpoints of a tunnel must use the same tunnel tunnel interface and interface tunnel mode. enter tunnel number mode evi For more information about this command, see interface view.
  • Page 17: Assigning A Network Id To The Evi Tunnel

    Assigning a network ID to the EVI tunnel Assign the same network ID to the EVI tunnels of all edge devices in an EVI network. On an edge device, the network ID assigned to an EVI tunnel must be unique. To assign a network ID to an EVI tunnel: Step Command...
  • Page 18: Enabling Evi On Transport-Facing Physical Interfaces

    • To guarantee that each edge device can obtain the addresses of all its EVI neighbors, make sure the ENDSs are the same across the EVI network. • To improve security, enable ENDP authentication. Make sure all authentication-enabled ENDCs and ENDSs in an EVI network use the same authentication key. Configuring the edge device as an ENDS on the EVI tunnel Step Command...
  • Page 19: Tuning Evi Is-Is Parameters

    Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view or Layer 3 interface-number 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.
  • Page 20: Optimizing An Evi Is-Is Network

    • Perform network optimization tasks (see "Optimizing an EVI IS-IS network") except configuring the LSP refresh interval and the maximum LSP lifetime. 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 Step Command Remarks interval is one-third of the hello interval set with this command. 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.
  • Page 22 To configure the CSNP transmit interval on a DED: 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.
  • 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

    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 | area-mismatch | buffsize-mismatch | id-length-mismatch | link-disconnect | lsp-parse-error | lsp-size-exceeded | Enable EVI IS-IS By default, all EVI IS-IS max-seq-exceeded | notifications.
  • Page 26: Enabling Evi Arp Flood Suppression

    To increase this number to accommodate all local MAC address entries, create virtual systems. Each virtual system represents an increase of 55 x 2 MAC address entries. If n virtual systems are created, the maximum number of MAC address entries in an LSP is (n+1) x 55 x 2 To configure EVI IS-IS virtual system: Step Command...
  • 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 statistics interface On an ENDS, display ENDS statistics. tunnel interface-number Display IPv4 ENDC information. display evi neighbor-discovery client summary display evi neighbor-discovery client member [ interface Display IPv4 neighbors that an ENDC tunnel interface-number | [ local local-ip | remote client-ip | has learned.
  • Page 29: Evi Configuration Examples

    Task Command reset evi neighbor-discovery server statistics interface Clear ENDP packet statistics on an ENDS. tunnel interface-number EVI configuration examples Single-homed EVI network configuration example Network requirements As shown in Figure • Use EVI to extend VLANs 21 through 100 across site 1, site 2, and site 3 over an IPv4 network. •...
  • Page 30 [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. [SwitchA-Tunnel1] source 1.1.1.1 # Set the tunnel keepalive interval to 20 seconds and the maximum number of transmissions to [SwitchA-Tunnel1] keepalive 20 2...
  • Page 31 # 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. [SwitchB-Tunnel1] evi neighbor-discovery client enable 1.1.1.1 [SwitchB-Tunnel1] quit # Enable EVI on GigabitEthernet 1/0/1.
  • Page 32 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 Last clearing of counters: Never...
  • Page 33 # 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) # Verify that Switch A has remote MAC addresses in VLAN 100.
  • Page 34 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. [SwitchB] display evi neighbor-discovery client member Interface: Tunnel1 Network ID: 1...
  • Page 35: Multiple-Evi-Networks Configuration Example

    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 Status Vpn-instance Tunnel1 1.1.3.1 1.1.1.1 disabled [No Vrf] # Display neighbor entries that Switch C has learned.
  • Page 36 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 Tunnel101 Site 1 Tunnel102 EVI 1 Site 3 VLANs 100-101 Tunnel101 GE1/0/1...
  • Page 37 [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. [Site4] interface gigabitethernet 1/0/1 [Site4-GigabitEthernet1/0/1] evi enable [Site4-GigabitEthernet1/0/1] quit...
  • Page 38 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 2013/01/01 01:00:46 172.16.4.1 000F-0001-0004 2013/01/01 01:02:13 Interface: Tunnel102 Network ID: 2 Vpn-instance: [No Vrf] IP Address: 172.16.4.1 Client Address System ID Expire...

Table of Contents