Page 2
SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V G, V G, PSPT, XGbus, N-Bus, TiGem, InnoVision and HUASAN are trademarks of Hangzhou H3C Technologies Co., Ltd. All other trademarks that may be mentioned in this manual are the property of their respective owners Notice The information in this document is subject to change without notice.
Page 3
The H3C S12500 documentation set includes 13 configuration guides, which describe the software features for the H3C S12500 Series Routing Switches and guide you through the software configuration procedures. These configuration guides also provide configuration examples to help you apply software features to different network scenarios.
Page 4
Layer 2 forwarding and other Layer 2 features. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your switch. About the H3C S12500 documentation set The H3C S12500 documentation set includes: Category...
Page 5
Obtaining documentation You can access the most up-to-date H3C product documentation on the World Wide Web at http://www.h3c.com. Click the links on the top navigation bar to obtain different categories of product documentation: [Technical Support & Documents > Technical Documents] –...
Page 6
Technical support service@h3c.com http://www.h3c.com Documentation feedback You can e-mail your comments about product documentation to info@h3c.com. We appreciate your comments.
Configuring EVI Overview Ethernet Virtualization 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 and...
Site and transport transparency—EVI is both site and transport network transparent. It has no • special site or transport network topology requirements. Easy management and maintenance—EVI requires deployment only on edge devices and does not • introduce any topology change or configuration within sites or the transport network. Network topologies As shown in Figure...
Figure 3 Multiple EVI networks Site 2 Site 1 EVI 1 VLANs 100-101 Site 3 EVI 2 VLAN 4000 EVI 3 VLANs 50-80 Site 4 Site 5 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.
ENDC An EVI neighbor discovery client works with an ENDS to learn neighbor information and triggers EVI link setup between neighbors. EVI IS-IS EVI IS-IS establishes adjacencies and advertises MAC reachability information among edge devices at different sites in an EVI network. EVI IS-IS runs independently of the Layer 3 routing protocols on the transport network and sites.
Page 12
MAC entries configured or learned in the data plane—The edge devices use the typical • source-MAC-based learning mechanism to learn unicast MAC addresses in their local sites (called "local MAC addresses"). • MAC entries learned through EVI IS-IS—After completing neighbor discovery, the edge devices run EVI IS-IS in the control plane to establish adjacencies and advertise MAC reachability information that has been learned or configured in the data plane to each other over EVI links.
Page 13
The source edge device forwards the encapsulated packet out of the EVI link to the destination edge device across the IP transport network. The destination edge device removes the headers of the original Ethernet frame, looks up the destination MAC address in the MAC address table, and sends the frame out of the matching outgoing interface.
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. IP2 sends an ARP reply back to site A's edge device over the EVI link. Site A's edge device creates an ARP cache entry for the remote MAC address and forwards the reply to the requesting host.
EVI configuration task list Tasks at a glance Remarks Configuring EVI basic functions: • (Required.) Configuring an IPv4 EVI tunnel All edge devices in an EVI network • must have the same network ID. (Required.) Assigning a network ID to the EVI tunnel •...
Step Command Remarks By default, no source IP address or source interface is specified for any tunnel. EVI uses the specified address or the primary IP address of the specified source interface as the source IP address of tunneled packets on the transport network.
An extended VLAN can be specified only on one EVI tunnel. • • To avoid loops, do not assign transport-facing ports to extended VLANs. To avoid data breach, make sure all edge devices in an EVI network maintain the same list of •...
Step Command Remarks By default, ENDS is disabled. An ENDS is always an ENDC of itself. You can use the evi neighbor-discovery client evi neighbor-discovery server Enable ENDS. enable command to add one more ENDS, enable and use the evi neighbor-discovery client register-interval command to modify the ENDC registration interval.
Step Command Remarks Enter Layer 2 or Layer 3 interface interface-type Ethernet interface view. interface-number By default, EVI function is disabled Enable EVI on the interface. evi enable on all 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.
If the EVI tunnel interface has been deleted, the undo evi-isis command deletes the EVI IS-IS process and clears the settings made in EVI IS-IS process view. If the EVI tunnel interface still exists, the undo evi-isis command only clears the settings made in EVI IS-IS process view. To create an EVI IS-IS process or enter its view: Step Command...
Page 22
device and recalculates routes if it does not receive an EVI IS-IS hello packet from the advertising edge device before the time value expires. To configure the multiplier for calculating the adjacency hold time on an EVI tunnel interface: Step Command Remarks Enter system view.
Page 23
Configuring the minimum LSP sending interval and the maximum number of LSPs sent at each interval When MAC reachability information changes, an edge device sends LSP updates to notify its adjacent EVI neighbors. To control EVI IS-IS LSP traffic on the EVI network: Step Command Remarks...
Step Command Remarks The default LSP refresh interval is 900 seconds. The minimum LSP sending interval and the maximum number of LSPs sent at each Configure the LSP refresh interval. interval can affect the actual timer lsp-refresh seconds LSP refresh interval. To avoid unnecessary age-outs, appropriately set the LSP refresh interval and...
Step Command Remarks The default restart interval is 300 seconds. graceful-restart interval If the restarting EVI process fails to Configure the restart interval. interval-value complete re-establishing the adjacency with the peer EVI process, the EVI link goes down. 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.
Single-homed EVI network configuration example Network requirements As shown in Figure 8, use EVI to connect site 1, site 2, and site 3 across an IP network into a large Layer 2 network, and extend VLAN 21 to VLAN 100 across the sites. Use network ID 1 to identify the EVI network.
Page 29
# Specify extended VLANs on the EVI tunnel interface. [SwitchA-Tunnel0] evi-isis extend-vlan 21 to 100 # Configure Switch A as an ENDS on the tunnel interface. [SwitchA-Tunnel0] evi neighbor-discovery server enable [SwitchA-Tunnel0] quit # Enable EVI on GigabitEthernet 3/0/1. [SwitchA] interface gigabitethernet 3/0/1 [SwitchA-GigabitEthernet3/0/1] evi enable [SwitchA-GigabitEthernet3/0/1] quit Configure Switch B:...
Page 30
# Create an IPv4 EVI tunnel interface. [SwitchC] interface tunnel 0 mode evi # Set the network ID of the EVI tunnel interface to 1. [SwitchC-Tunnel0] evi network-id 1 # Specify the IP address of VLAN-interface 10 as the source IP of the EVI tunnel. [SwitchC-Tunnel0] source 1.1.3.1 # Set the tunnel keepalive interval to 20 seconds and the maximum number of transmissions to 2.
Page 31
# Display ENDC information. [SwitchA] display evi neighbor-discovery client summary Status: I-Init E-Establish P-Probe Interface Local Address Server Address Network ID Auth Status Tunnel0 1.1.1.1 1.1.1.1 disabled # Display EVI neighbors registered with the ENDS. [SwitchA] display evi neighbor-discovery server member Interface: Tunnel0 Network ID: 1 IP Address: 1.1.1.1...
Page 32
Interface Local Address Server Address Network ID Auth Status Tunnel0 1.1.2.1 1.1.1.1 disabled # Display neighbor entries that Switch B has learned. [SwitchB] display evi neighbor-discovery client member Interface: Tunnel0 Network ID: 1 Local Address: 1.1.3.1 Server Address: 1.1.1.1 Neighbor System ID Created Time Expire...
Multiple-EVI-networks configuration example Network requirements Use EVI to connect the sites of the data center in Figure 9. To isolate different types of traffic and extend their VLANs to different sites, set up the following EVI networks: Database EVI network (network ID 1)—Extends VLANs 100 and 101 across sites 2, 3, and 4. •...
Page 34
[Site4-Tunnel101] quit # Configure the network management EVI network. [Site4] interface tunnel 102 mode evi [Site4-Tunnel102] source 172.16.4.1 [Site4-Tunnel102] evi network-id 2 [Site4-Tunnel102] evi-isis 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...
Configure all the other sites in the same way that site 1 is configured. Make sure extended VLANs are correctly configured at each site. 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 IP Address: 172.16.4.1...
Page 36
Figure 10 Network diagram Configuration procedure This example assumes that routes have been configured for the sites to reach each other. Configure the Router: # Enable IP multicast routing, and enable IGMP on VLAN-interface 100. <Router> system-view [Router] multicast routing-enable [Router] vlan 100 [Router-vlan100] quit [Router] interface vlan-interface 100...
Page 37
[SwitchA-Tunnel0] quit # Enable selective flooding for PIM hellos (destination MAC 0100-5e00-0001, and destination IP 224.0.0.1) and IGMP general query packets (destination MAC 0100-5e00-000D, and destination IP 224.0.0.13). These destination MAC addresses cannot be learned in the data plane. Selective flooding enables these packets to be sent between sites. [SwitchA-Tunnel0] evi selective-flooding mac-address 0100-5e00-0001 vlan 100 [SwitchA-Tunnel0] evi selective-flooding mac-address 0100-5e00-000D vlan 100 [SwitchA-Tunnel0] quit...
Page 38
# Enable global IGMP snooping. [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 100, assign GigabitEthernet 3/0/2 to the VLAN, and enable IGMP snooping in the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 3/0/2 [SwitchA-vlan100] igmp-snooping enable [SwitchA-vlan100] quit Verifying the configuration On Switch A: # Display EVI-Link interface information.
Index 3 2 H 3 3 H 3 4 H 3 5 H EVI configuration examples, 1 0 4 H EVI configuration task list, Configuring EVI basic functions, 1 0 5 H 1 0 0 H Overview, Displaying and maintaining EVI, 1 0 6 H 1 0 1 H Tuning EVI IS-IS parameters,...
Need help?
Do you have a question about the S12500 Series and is the answer not in the manual?
Questions and answers