H3C H3C S7500E Series User manual

H3C S7500E Switch Series
Comware 7 EVI Configuration Guide
New H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: Release 7568
Document version: 6W101-20180802

Copyright © 2018, New H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior written
consent of New H3C Technologies Co., Ltd.
Trademarks
H3C, , H3CS, H3CIE, H3CNE,Aolynk, , H3Care, , IRF, NetPilot, Netflow, SecEngine,
SecPath, SecCenter, SecBlade, Comware, ITCMM and HUASAN are trademarks of New 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. 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.

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.
This preface includes the following topics about the documentation:
•Audience.
•Conventions.
•Documentation feedback.
Audience
This documentation is intended for:
•Network planners.
•Field technical support and servicing engineers.
•Network administrators working with the S7500E switch series.
Conventions
The following information describes the conventions used in the documentation.
Command conventions
Convention Description
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars,
from which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select a minimum of one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.
&<1-n> The argument or keyword and argument combination before the ampersand (&) sign
can be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Convention Description
Boldface Window names, button names, field names, and menu items are in Boldface. For
example, the New User window opens; click OK.

Convention Description
> Multi-level menus are separated by angle brackets. For example, File > Create >
Folder.
Symbols
Convention Description
WARNING! An alert that calls attention to important information that if not understood or followed
can result in personal injury.
CAUTION: An alert that calls attention to important information that if not understood or followed
can result in data loss, data corruption, or damage to hardware or software.
IMPORTANT: An alert that calls attention to essential information.
NOTE: An alert that contains additional or supplementary information.
TIP: An alert that provides helpful information.
Network topology icons
Convention Description
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that
supports Layer 2 forwarding and other Layer 2 features.
Represents an access controller, a unified wired-WLAN module, or the access
controller engine on a unified wired-WLAN switch.
Represents an access point.
Represents a wireless terminator unit.
Represents a wireless terminator.
Represents a mesh access point.
Represents omnidirectional signals.
Represents directional signals.
Represents a security product, such as a firewall, UTM, multiservice security
gateway, or load balancing device.
Represents a security module, such as a firewall, load balancing, SSL VPN, IPS, or
ACG module.
T
T
T
T





Examples provided in this document
Examples in this document might use devices that differ from your device in hardware model,
configuration, or software version. 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 [e-mail].
We appreciate your comments.

i
Contents
Configuring EVI ···············································································1
Overview··································································································································1
Layer 2 connectivity extension issues ······················································································1
Network topologies··············································································································2
Terminology·······················································································································3
Working mechanism ············································································································3
Placement of Layer 3 gateways······························································································6
ARP flood suppression·········································································································7
Selective flooding················································································································7
Path MTU··························································································································8
Configuration restrictions and guidelines·························································································8
Licensing requirements·········································································································8
Feature and hardware compatibility·························································································8
Feature compatibility requirements··························································································8
EVI configuration task list·············································································································8
Configuring EVI basic features······································································································9
Configuring a site ID ············································································································9
Configuring an EVI tunnel ···································································································10
Assigning a network ID to the EVI tunnel················································································11
Specifying extended VLANs on the EVI tunnel·········································································11
Configuring ENDP·············································································································11
Enabling EVI on transport-facing physical interfaces·································································12
Tuning EVI IS-IS parameters······································································································13
EVI IS-IS configuration task list ····························································································13
Creating an EVI IS-IS process······························································································13
Optimizing an EVI IS-IS network···························································································14
Specifying a routing policy for an EVI IS-IS process··································································17
Enabling adjacency change logging ······················································································18
Configuring SNMP notifications and context for EVI IS-IS ··························································18
Configuring Graceful Restart for an EVI IS-IS process·······························································19
Increasing the maximum number of MAC entries in an LSP for an EVI IS-IS process·······················19
Enabling EVI ARP flood suppression····························································································20
Enabling EVI flooding for all destination-unknown frames ·································································20
Enabling selective flooding for a MAC address···············································································21
Displaying and maintaining EVI···································································································21
EVI configuration examples········································································································23
Single-homed EVI network configuration example····································································23
Multiple-EVI-networks configuration example ··········································································29
Index···························································································33

1
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 1).
EVI enables long-distance virtual machine workload mobility and data mobility, disaster recovery,
and business continuity. For example, virtual machines can move between data center sites without
changing their IP addresses, so their movements are transparent to users and do not disrupt traffic.
Figure 1 Virtual machine migration
Layer 2 connectivity extension issues
EVI resolves the following Layer 2 connectivity extension issues:
•Site independence—EVI keeps protocol failures, such as broadcast storms, from propagating
across sites.
•Transport independence—EVI has no special requirements for site location or transport
network type, except that the transport network can forward IP packets.
•Link efficiency—EVI optimizes the inter-site multicast and broadcast transmission mechanism
and implements load-sharing on redundant links.
•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.

2
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.
Figure 2 EVI network
EVI supports multiple EVI networks on an edge device for extending different VLANs across the
Layer 3 network. One EVI network can convey multiple VLANs, but one VLAN can map to only one
EVI network. Each EVI network has separate network parameters and independently forwards
traffic.
As shown in Figure 3, EVI network 1 extends VLAN 100 and VLAN 101 to Site 2, Site 3, and Site 4
for Web access traffic. EVI network 2 extends VLAN 4000 (the management VLAN) to all sites, and
EVI network 3 extends VLANs 50 to 80 between Site 1 and Site 4 for database traffic.
Figure 3 Multiple EVI networks
Transport network Site network
Edge device
EVI link
EVI
Site network
Edge device
Site
network
Edge device
EVI link EVI link VLAN 10
VLAN 10
VLAN 10
Site 1
Site 2
Site 3
Site 1
Site 2
Site 4
Site 5
EVI 1
VLANs 100-101
EVI 2
VLAN 4000
EVI 3
VLANs 50-80
Site 3

3
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.
EVI link
An EVI link is a bidirectional virtual Ethernet channel between a pair of edge devices in an EVI
network. EVI links are conveyed on EVI tunnels. Each EVI link is uniquely identified by a pair of
source and destination EVI tunnel IP addresses.
EVI tunnel
An EVI tunnel is a point-to-many automatic GRE tunnel that conveys EVI links for an EVI network.
One EVI tunnel can provide services only for one EVI network.
EVI neighbor
All edge devices in an EVI network are EVI neighbors to one other.
ENDP
EVI Neighbor Discovery Protocol uses the client/server model to dynamically discover sites and
edge devices, establish and maintain EVI links, and exchange network membership information in
an EVI network.
ENDS
An EVI neighbor discovery server maintains all neighbor information in an EVI network. An EVI
network can have up to two ENDSs.
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.
DED
A DED is elected from between the edge devices on each EVI link to send CSNP packets for LSDB
synchronization.
Internal interface
Internal interfaces are site-facing Layer 2 interfaces that connect an edge device to switches or
routers in the site.
Working mechanism
An edge device uses the following process to set up an EVI network and forward traffic at Layer 2 to
remote sites:
1. Runs ENDP to discover EVI neighbors and set up EVI links between neighbors.
2. Runs EVI IS-IS to advertise MAC reachability information over EVI links in the EVI network.

4
3. 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:
1. ENDS is enabled on one edge device, and ENDC is enabled on all other edge devices.
2. The ENDCs register their IP addresses and other data with the ENDS.
3. The ENDS updates its ENDC database with received data and sends the updated database to
each ENDC.
4. After receiving the register reply, the ENDCs establish an EVI link with each other.
For high availability, you can configure up to two ENDSs for an EVI network.
MAC address learning
MAC reachability information on an EVI edge device comes from the following sources:
•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).
If the device learns the source MAC address when it sends out a packet at the egress, execute
the mac-address mac-learning ingress command. This command enables MAC address
learning at the ingress to reduce flood traffic and accelerate populating of the MAC address
table. For more information about MAC address learning, see MAC address table configuration
in Layer 2—LAN Switching Configuration Guide.
•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.
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 in Figure 4.

5
Figure 4 Layer 2 forwarding in a site
The following forwarding process (see Figure 5) takes place for unicast flows between sites:
1. 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.
2. If the outgoing interface is an EVI-Link interface instead of a physical port, the source edge
device encapsulates the frame in a GRE header, and then adds an IP header and a link layer
protocol header.
In the outer IP header, the source IP address is the source edge device's tunnel source IP
address, and the destination IP address is the destination edge device's tunnel source IP
address.
3. The source edge device forwards the encapsulated packet out of the EVI link to the destination
edge device across the IP transport network.
4. 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.
EVI
Site 1
EVI
Site 2
MAC table
VLAN MAC Interface
200 MAC1 GE1/0/1
200 MAC2 GE1/0/2
MAC1 MAC2
EVI
Transport network
GE1/0/1 GE1/0/2
Host A Host B

6
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.
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. ForARP packets, you can use
the ARP flood suppression feature (see "ARP flood suppression") to reduce ARP broadcasts.
•Destination-unknown unicast or multicast frame—Floods the frame to all internal interfaces
in the VLAN where the frame has been received. The edge device typically does not forward
destination-unknown frames to other sites. If a site-to-site flooding is desirable for a special
MAC address, use the selective flooding feature (see "Selective flooding").
To flood a frame to remote sites, an EVI edge device must replicate the frame, encapsulate each
replica in one unicast frame for each destination site, and send the unicast frames to the remote
edge devices.
Placement of Layer 3 gateways
For the hosts in an extended VLAN at a site, their Layer 3 gateway must be on the edge device at the
local site rather than a remote site.

7
ARP flood suppression
ARP flood suppression reduces ARP request broadcasts on the EVI network by enabling edge
devices to reply to ARP requests on behalf of remote-site hosts.
As shown in Figure 6, this feature snoops ARP packets on an EVI tunnel interface to populate the
ARP flood suppression table with remote MAC addresses. If an ARP request has a matching entry,
the local edge device replies to the request on behalf ofthe remote-site host. If nomatch is found, the
edge device floods the request to the EVI network.
ARP flood suppression uses the following workflow:
1. Host IP1 in site A sends an ARP request to obtain the MAC address of IP2.
2. Site A's edge device floods the ARP requests out of all interfaces, including the EVI tunnel
interfaces.
3. Site B's edge device de-encapsulates the ARP request and broadcasts the request.
4. IP2 sends an ARP reply back to site A's edge device over the EVI link.
5. Site A's edge device creates an ARP cache entry for the remote MAC address and forwards the
reply to the requesting host.
6. Site A's edge device replies to all subsequent requests for the MAC address of IP2.
Figure 6 ARP flood suppression
Selective flooding
Selective flooding enables an edge device to send an unknown unicast or multicast frame out of an
EVI tunnel interface.
This feature is designed for special multicast addresses that require flooding across sites but cannot
be added to a multicast forwarding table by IGMP snooping.

8
For example, you must configure selective flooding for PIM hellos, IGMPgeneral query packets, and
Microsoft NLBS cluster traffic to be sent out of an EVI tunnel interface.
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.
Because EVI does not support path MTU discovery, your EVI deployment must make sure the path
MTU of the transport network is higher than the maximum size of EVI tunneled frames.
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
When you configure EVI, follow these hardware restrictions:
•You can enable EVI only on interfaces on the following modules:
{SC interface modules:
−LSQM2GT24PTSSC0.
−LSQM2GT24TSSC0.
{SG interface modules.
•The S7503E-M switch does not support EVI.
Feature compatibility requirements
When you use EVI in conjunction with other features, follow these restrictions and guidelines:
•MPLS and EVI cannot work together. Do not configure both features on the device. For more
information about MPLS, see MPLS Configuration Guide.
•VXLAN and EVI cannot work together. Do not configure both features on the device. For more
information about VXLAN, see VXLAN Configuration Guide.
•If the link type of a site-facing interface is access, it can receive only tagged packets from the
VLAN to which the port has been assigned.
•Spanning tree protocols are not supported on site-facing interfaces that are assigned to
extended VLANs. Make sure the interfaces do not form loops with other devices.
•QoS policies are not supported on site-facing interfaces that are assigned to extended VLANs.
•VLAN-interface 1 cannot be used as a transport-facing interface.
EVI configuration task list
Perform the following tasks on all edge devices of an EVI network:

9
Tasks at a glance Remarks
Configuring EVI basic features:
•(Optional.) Configuring a site ID
•(Required.) Configuring an EVI tunnel:
{(Required.) Assigning a network ID to the EVI tunnel
{(Required.) Specifying extended VLANs on the EVI tunnel
{(Required.) Configuring ENDP
{(Required.) Enabling EVI on transport-facing physical
interfaces
An EVI tunnel can provide services
for only one EVI network.
An extended VLAN can be
assigned to only one EVI network.
(Optional.) Tuning EVI IS-IS parameters
EVI IS-IS automatically runs on an
EVI tunnel interface immediately
after the interface is created.
You can tune EVI IS-IS
parameters for optimizing network
performance.
(Optional.) Enabling EVI ARP flood suppression Perform this task to reduce ARP request broadcasts on an EVI
network.
(Optional.) Enabling EVI flooding for all destination-unknown frames Perform this task to flood frames with unknown MAC addresses to
the EVI tunnel interface.
(Optional.) Enabling selective flooding for a MAC address
Perform this task for special
multicast MAC addresses that
require Layer 2 inter-site
forwarding but cannot be learned
into the MAC address table.
Configuring EVI basic features
All tasks in this section are required for setting up an EVI network.
Configuring a site ID
By default, all edge devices in an EVI network have a site ID of 0.
To uniquely identify the sites in an EVI network, you can change their site IDs. To avoid site ID conflict,
follow these guidelines when you configure site IDs:
•An edge device can use the default or manually assigned site ID. Site conflict does not occur if
the edge devices at different sites all use the default site ID.
•Manually assigned site IDs must be unique among sites.
When the site IDs of two devices conflict, EVI IS-IS isolates the device with the lower MAC address.
The isolated device can only receive EVI IS-IS hello packets. It cannot exchange EVI IS-IS packets
with other neighbors. To identify isolated devices, use the display evi isis brief command or the
display evi isis peer command.
To assign a site ID to the device:
Step Command Remarks
1. Enter system view. system-view N/A
2. Assign a site ID to the
device. evi site-id site-id The default site ID is 0.

10
Configuring an EVI tunnel
Step Command Remarks
1. Enter system view. system-view N/A
2. Create an EVI
tunnel interface and
enter tunnel
interface view.
interface tunnel
number mode evi
By default, no tunnel interface exists.
The endpoints of a tunnel must use the same tunnel
mode.
For more information about this command, see
tunneling commands in Layer 3—IP Services
Command Reference.
3. Specify a source IP
address or interface
for the tunnel.
source { ipv4-address |
interface-type
interface-number }
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. For more
information about the source command, see
tunneling commands in Layer 3—IP Services
Command Reference.
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.
EVI networks can share a tunnel source IP address
or interface.
You must specify the same source IP address or
interface for tunnels that use the same
transport-facing physical interface.
IMPORTANT:
To avoid forwarding failure, do not use a GRE tunnel
interface or its IP address (configure with the ip
address command in tunnel interface view) as the
source interface or IP address of an EVI tunnel. For
more information about GRE, see Layer 3—IP
Services Configuration Guide.
4. Configure the EVI
link keepalive
interval and the
maximum number
of keepalive
transmissions.
keepalive [ seconds
[ times ] ]
By default, a keepalive packet is sent every five
seconds and the maximum number of transmissions
is two.
If no reply is received from the remote end on an EVI
link after the maximum number of keepalive
transmissions is reached, the local end considers the
EVI link as having failed.
5. (Optional.)
Generate a GRE
key for tunneled
packets based on
their VLAN IDs.
gre key vlan-id
By default, EVI tunneled packets do not contain a
GRE key.
The GRE key setting must be the same across an
EVI network. Perform this step if any remote edge
devices generate VLAN ID-based GRE keys for EVI
tunneled packets.
NOTE:
In addition to the EVI-specific commands described in this section, you can configure generic tunnel
interface commands on an EVI tunnel interface. These tunnel commands and tunneling basics are
described in the tunneling configuration in Layer 3—IP Services Configuration Guide.

11
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 Remarks
1. Enter system view. system-view N/A
2. Enter tunnel interface view. interface tunnel number
[ mode evi ] N/A
3. 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:
•You can specify an extended VLAN on only 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.
To assign extended VLANs to an EVI tunnel:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter EVI tunnel interface
view. interface tunnel number
[ mode evi ] N/A
3. Specify extended VLANs. evi extend-vlan vlan-list
By default, no VLANs are specified as
extended VLANs on any EVI tunnel.
To specify more extended VLANs,
repeat this step.
Configuring ENDP
ENDP enables the edge devices in an EVI network to discovery each other.
Configure an edge device as an ENDS to provide registration services or as an ENDC to register
with an ENDS.
Configuration guidelines
•For redundancy, you can configure up to two ENDSs on an EVI tunnel interface. These two
ENDSs work independently. The failure of one ENDS does not affect the neighbor discovery
and EVI link maintenance in the EVI network.
•When you enable ENDS on an EVI tunnel interface, an ENDC is automatically enabled. This
ENDC uses the source address of the EVI tunnel as the ENDS address.As a result, you can
use the evi neighbor-discovery client enable command to add only one ENDS address on an
ENDS-enabled EVI tunnel interface.
•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.

12
•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 Remarks
1. Enter system view. system-view N/A
2. Enter EVI tunnel
interface view. interface tunnel number
[ mode evi ] N/A
3. Enable ENDS. evi neighbor-discovery
server enable
By default, ENDS is disabled.
On an ENDS-enabled tunnel interface, you
can use the evi neighbor-discovery client
enable command to add one more ENDS,
and use the evi neighbor-discovery client
register-interval command to modify the
ENDC registration interval.
4. (Optional.) Enable
ENDP authentication. evi neighbor-discovery
authentication { cipher |
simple } string By default, ENDP authentication is disabled.
Configuring the edge device as an ENDC on the EVI tunnel
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter EVI tunnel
interface view. interface tunnel number
[ mode evi ] N/A
3. Configure the edge
device as the ENDC of
an ENDS. evi neighbor-discovery
client enable server-ip
By default, ENDC is disabled.
If ENDS is enabled on the EVI tunnel
interface, you can use this command to
specify only one more ENDS.
If ENDS is disabled, you can repeat this
command to specify up to two ENDSs.
ENDS address is the tunnel source address
configured on an ENDS-enabled EVI tunnel
interface.
4. (Optional.) Enable
ENDP authentication. evi neighbor-discovery
authentication { cipher |
simple } string
By default, ENDP authentication is disabled.
All ENDSs and ENDCs in an EVI network
must use the same authentication key.
5. Configure the interval
at which the ENDC
updates its registration
with ENDSs.
evi neighbor-discovery
client register-interval
interval
By default, an ENDC update its registration
with an ENDS every 15 seconds.
Enabling EVI on transport-facing physical interfaces
Enable EVI on all physical interfaces that provide transport network access for EVI tunnels.
To enable EVI on an interface:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2 Ethernet interface interface-type N/A

13
Step Command Remarks
interface view or Layer 3
Ethernet interface view. interface-number
3. Enable EVI on the interface. evi enable By default, EVI is disabled 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.
EVI IS-IS configuration task list
All EVI IS-IS configuration tasks are optional.
Tasks at a glance Remarks
Creating an EVI IS-IS process N/A
Optimizing an EVI IS-IS network:
•Configuring the EVI IS-IS hello interval
•Configuring the hello multiplier for calculating the
adjacency hold time
•Configuring the DED priority
•Configuring the CSNP transmit interval
•Configuring the minimum LSP transmit interval and
the maximum number of LSPs sent at each interval
•Configuring the maximum LSP lifetime
•Configuring the LSP refresh interval
•Associating an EVI tunnel interface with a track entry
Perform the EVI IS-IS network optimization
tasks to enable fast EVI link failure detection,
set appropriate MAC reachability information
update interval, and control the volume of LSP
and CSNP traffic on an EVI network.
Specifying a routing policy for an EVI IS-IS process Perform this task to advertise a subset of MAC addresses instead of all local MAC addresses
to remote sites.
Enabling adjacency change logging N/A
Configuring SNMP notifications and context for EVI IS-IS N/A
Configuring Graceful Restart for an EVI IS-IS process Perform this task for providing nonstop
services.
Increasing the maximum number of MAC entries in an LSP
for an EVI IS-IS process Perform this task depending on the MAC address table size on the edge device.
Creating an EVI IS-IS process
Each EVI network has one EVI IS-IS process. Before you can configure settings in EVI IS-IS process
view, you must create the process.
An EVI IS-IS process is created automatically when you perform any one of the following tasks on a
tunnel interface:
•Specify extended VLANs.
•Perform network optimization tasks (see "Optimizing an EVI IS-IS network") except configuring
the LSP refresh interval and the maximum LSP lifetime.

14
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.
•If EVI IS-IS settings exist on the EVI tunnel interface, the undo evi-isis command only deletes
settings configured in EVI IS-IS process view.
•If no EVI IS-IS settings exist on the EVI tunnel interface, the undo evi-isis command deletes
both the EVI IS-IS process and all settings configured in EVI IS-IS process view.
An automatically created EVI IS-IS process is automatically deleted when you delete all EVI IS-IS
settings from the EVI tunnel interface.
To create an EVI IS-IS process or enter its view:
Step Command Remarks
1. Enter system view. system-view N/A
2. Create an EVI IS-IS
process or enter EVI
IS-IS process view. evi-isis process-id
By default, no EVI IS-IS processes exist.
The process ID you specify must be the same as
the EVI tunnel interface number.
The EVI IS-IS process takes effect after you
configure extended VLANs on the tunnel
interface.
Optimizing an EVI IS-IS network
Perform the tasks in this section to optimize an EVI IS-IS network for bandwidth efficiency and high
performance.
Configuring the EVI IS-IS hello interval
EVI edge devices send EVI IS-IS hellos over EVI links to establish and maintain adjacencies and
elect a DED on each EVI link.
Set the hello interval depending on the network convergence requirement and system resources.
•To increase the speed of network convergence, decrease the hello interval.
•To conserve resources, increase the hello interval.
NOTE:
The hello interval of a DED is one-third of the hello interval set with the evi isis timer hello
command.
To configure the EVI IS-IS hello interval on an EVI tunnel interface:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter EVI tunnel interface
view. interface tunnel number [ mode
evi ] N/A
3. Configure the EVI IS-IS
hello interval. evi isis timer hello seconds
The default hello interval is 10
seconds.
If the edge device is a DED, its hello
interval is one-third of the hello
interval set with this command.