Page 3
The H3C S9800 documentation set includes 17 configuration guides. These guides describe the software features for the H3C S9800 Switch Series running Release 2135 and later, and guide you through the software configuration procedures. These guides also provide configuration examples to help you apply software features to different network scenarios.
Page 4
Convention Description The argument or keyword and argument combination before the ampersand (&) sign can &<1-n> be entered 1 to n times. A line that starts with a pound (#) sign is comments. GUI conventions Convention Description Window names, button names, field names, and menu items are in Boldface. For Boldface example, the New User window appears;...
Page 5
The port numbers in this document are for illustration only and might be unavailable on your device. Obtaining documentation Access the most up-to-date H3C product documentation on the World Wide Web at http://www.h3c.com. Click the following links to obtain different categories of product documentation: [Technical Documents]—Provides hardware installation, software upgrading, and software feature...
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, and business continuity.
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 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.
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 11
NOTE: The mac-address max-mac-count command and the mac-address mac-learning enable command take effect only on local MAC addresses, which are learned in the data plane. They do not take effect on remote MAC addresses, which are learned in the control plane. Unicast flow For intra-site unicast flows, an edge device performs the typical MAC address table lookup, as shown Figure...
Figure 5 Layer 2 forwarding between sites Flooding flow An edge device handles flooding by frame type, as follows: • Broadcast frame—Floods the frame to all interfaces in the VLAN where the frame has been received, including internal interfaces and EVI-Link interfaces. Destination-unknown unicast or multicast frame—Floods the frame to all internal interfaces in the •...
Path MTU When encapsulating an Ethernet frame in EVI, the edge device does not modify the Ethernet frame, but it sets the DF bit in the IP header. For an Ethernet transport network, the total size of an EVI protocol packet increases by 46 bytes, and the total size of a data packet increases by 38 bytes.
Tasks at a glance Remarks Perform this task for special multicast MAC addresses that (Optional.) Enabling selective flooding for a MAC address require Layer 2 inter-site forwarding but cannot be learned into the MAC address table. Perform this task to ensure correct (Required.) Enabling MAC address learning at the ingress MAC address learning.
Step Command Remarks 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. Specify a source IP address source { ipv4-address | or interface for the tunnel.
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 extended VLANs.
Step Command Remarks By default, ENDS is disabled. On an ENDS-enabled tunnel interface, 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.
Specify extended VLANs. • Perform network optimization tasks (see "Optimizing an EVI IS-IS network") except configuring the • EVI IS-IS hello 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.
Page 20
Step Command Remarks The default hello interval is 10 seconds. Configure the EVI IS-IS If the edge device is a DED, its hello evi isis timer hello seconds hello interval. 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 sets how long one edge device can retain the adjacency with another edge device.
Page 21
Configuring the CSNP packet sending interval This configuration takes effect only on DEDs. The DEDs in an EVI network regularly send CSNP packets to advertise LSP summaries for LSDB synchronization. To configure the CSNP packet sending interval on a DED: Step Command Remarks...
Configuring the LSP refresh interval An edge device regularly sends LSP updates to remote edge devices for updating MAC reachability information. To change the LSP refresh interval: Step Command Remarks Enter system view. system-view Enter EVI IS-IS process evi-isis process-id view.
Step Command Remarks Enter system view. system-view Enter EVI IS-IS process view. evi-isis process-id Enable adjacency change By default, adjacency change log-peer-change enable logging. logging is enabled. Configuring SNMP notifications and context for EVI IS-IS To report critical EVI IS-IS events to an NMS, enable SNMP notifications for EVI IS-IS. For EVI IS-IS event notifications to be sent correctly, you must also configure SNMP as described in Network Management and Monitoring Configuration Guide.
If Graceful Restart is enabled, the adjacency hold time equals the EVI IS-IS hello interval multiplied by the holding-multiplier or the restart interval, whichever is greater. (For a DED, the hello interval is one-third of the hello interval set with the evi isis timer hello command.) To configure Graceful Restart for an EVI IS-IS process: Step Command...
To enable EVI flooding for all destination-unknown frames: Step Command Remarks Enter system view. system-view Enter EVI tunnel interface interface tunnel number view. [ mode evi ] Enable EVI flooding. evi flooding enable By default, EVI flooding is disabled. Enabling selective flooding for a MAC address CAUTION: Do not configure selective flooding for a unicast MAC address that might be learned at an edge device's data plane.
Step Command Remarks By default, the device learns MAC addresses at the egress. Enable MAC address For more information about this mac-address mac-learning ingress learning at the ingress. command, see MAC address table commands in Layer 2—LAN Switching Command Reference. Displaying and maintaining EVI Execute display commands in any view and reset commands in user view.
Task Command display evi mac-address interface tunnel interface-number [ vlan vlan-id ] [ slot slot-number ] [ count ] Display remote MAC addresses (in standalone mode). display evi mac-address interface tunnel interface-number mac-address mac-address vlan vlan-id [ slot slot-number ] display evi mac-address interface tunnel interface-number [ vlan vlan-id ] [ chassis chassis-number slot slot-number ] [ count ] Display remote MAC addresses (in IRF...
Page 28
<SwitchA> system-view [SwitchA] mac-address mac-learning ingress # Configure the site ID. [SwitchA] evi site-id 1 # Configure the EVI tunnel source interface (VLAN-interface 10 in this example), and assign the transport-facing physical interface Ten-GigabitEthernet 1/0/1 to the VLAN. [SwitchA] vlan 10 [SwitchA-vlan10] port ten-gigabitethernet 1/0/1 [SwitchA-vlan10] quit [SwitchA] interface vlan-interface 10...
Page 29
# Set the network ID of the EVI tunnel interface to 1. [SwitchB-Tunnel0] evi network-id 1 # Specify the IP address of VLAN-interface 10 as the source IP of the EVI tunnel. [SwitchB-Tunnel0] source 1.1.2.1 # Set the tunnel keepalive interval to 20 seconds and the maximum number of transmissions to 2. [SwitchB-Tunnel0] keepalive 20 2 # Specify extended VLANs on the EVI tunnel interface.
Page 30
[SwitchC-Ten-GigabitEthernet1/0/1] quit Verifying the configuration Verify the configuration on Switch A: # Display information about the EVI tunnel interface. [SwitchA] display interface tunnel 0 Tunnel0 Current state: UP Line protocol state: UP Description: Tunnel0 Interface Bandwidth: 64kbps Maximum Transmit Unit: 64000 Internet protocol processing: disabled Tunnel source 1.1.1.1 Tunnel keepalive enabled, Period(20 s), Retries(2)
Page 31
Local Address: 1.1.1.1 Server Address: 1.1.1.1 Neighbor System ID Created Time Expire Status 1.1.2.1 000F-0001-0002 2014/04/01 12:12:12 1.1.3.1 000F-0001-0003 2014/04/01 12:12:12 Verify the configuration on Switch B: # Display information about the EVI tunnel interface. [SwitchB] display interface tunnel 0 Tunnel0 Current state: UP Line protocol state: UP...
Line protocol state: UP Description: Tunnel0 Interface Bandwidth: 64kbps Maximum Transmit Unit: 64000 Internet protocol processing: disabled Tunnel source 1.1.3.1 Tunnel keepalive enabled, Period(20 s), Retries(2) Network ID 1 Tunnel protocol/transport GRE_EVI/IP Last clearing of counters: Never Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec Input: 0 packets, 0 bytes, 0 drops Output: 0 packets, 0 bytes, 0 drops...
Page 33
In each EVI network, use the edge device at site 4 as an ENDS and all other edge devices as its ENDCs. Figure 7 Network diagram Site 2 XGE3/0/1 Vlan-int10 172.16.2.1/16 Tunnel102 Tunnel101 Site 1 Tunnel102 EVI 1 Site 3 VLANs 100-101 Tunnel101 XGE3/0/1...
Page 34
[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 Ten-GigabitEthernet 1/0/1.
Page 35
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...
Index EVI IS-IS process LSP MAC entries max, EVI IS-IS SNMP context, adjacency EVI IS-IS SNMP notifications, EVI configuration, EVI site ID, EVI IS-IS adjacency change logging, EVI tunnel, EVI IS-IS hello multiplier for calculating EVI tunnel edge device as ENDC, adjacency hold time, EVI tunnel edge device as ENDS, EVI IS-IS process GR configuration,...
Page 37
EVI IS-IS hello multiplier, ENDP, EVI IS-IS LSP refresh interval, ENDP configuration, EVI IS-IS process routing policy, ENDS, EVI link, flooding enable (destination-unknown frames), EVI neighbor, flooding enable (selective MAC address), EVI path MTU, flooding flow, EVI selective flooding, how it works, EVI site ID configuration, internal interface, EVI tunnel edge device as ENDC,...
Page 38
tunnel network ID assignment, EVI IS-IS, unicast flow, EVI IS-IS parameter tuning, EVI IS-IS process LSP MAC entries max, EVI network, EVI network topologies, EVI path MTU, flooding IPv4 EVI flooding (destination-unknown frames), EVI tunnel configuration, EVI flooding enable (selective MAC IPv6 address), EVI tunnel configuration,...
Page 39
EVI IS-IS LSP sending interval, EVI ENDP configuration, EVI IS-IS max number LSPs sent, EVI ENDS, EVI flooding (destination-unknown frames), EVI flooding enable (selective MAC address), EVI IS-IS LSP lifetime max, EVI flooding flow, EVI IS-IS LSP refresh interval, EVI internal interface, EVI IS-IS LSP sending interval, EVI IS-IS, EVI IS-IS max number LSPs sent,...
Page 40
packet enabling EVI on transport-facing physical interface, EVI IS-IS LSP sending interval, enabling MAC address learning at the ingress, EVI IS-IS max number LSPs sent, maintaining EVI, EVI IS-ISCSNP packet sending interval, optimizing EVI IS-IS network, EVI path MTU, specifying EVI IS-IS process routing policy, path MTU specifying EVI tunnel extended VLAN, EVI support,...
Page 41
EVI transport-facing physical interface enable, EVI tunnel, EVI tunnel configuration, EVI tunnel edge device as ENDC, EVI tunnel edge device as ENDS, EVI tunnel extended VLAN, EVI tunnel network ID assignment, unicast EVI unicast flow, VLAN EVI broadcast frame, EVI DED, EVI destination-unknown multicast frame, EVI destination-unknown unicast frame, EVI flooding flow,...
Need help?
Do you have a question about the S9800 Series and is the answer not in the manual?
Questions and answers