H3C S12500 Series User manual

H3C S12500 Series Routing Switches
EVI Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: S12500-CMW710-R7128
Document version: 6W710-20121130

Copyright © 2012, Hangzhou 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 Hangzhou H3C Technologies Co., Ltd.
Trademarks
H3C, , Aolynk, , H3Care, , TOP G, , IRF, NetPilot, Neocean, NeoVTL,
SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V2G, VnG, 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. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Preface
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.
The EVI Configuration Guide describes the Ethernet Virtualization Interconnect (EVI) fundamentals and
configuration. 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.
This preface includes:
•Audience
•Conventions
•About the H3C S12500 documentation set
•Obtaining documentation
•Technical support
•Documentation feedback
Audience
This documentation is intended for:
•Network planners
•Field technical support and servicing engineers
•Network administrators working with the S12500 series
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Descri
p
tion
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 at least one.

Convention Descri
p
tion
[ 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 Descri
p
tion
Boldface Window names, button names, field names, and menu items are in Boldface. For
example, the New User window appears; click OK.
> Multi-level menus are separated by angle brackets. For example, File > Create > Folder.
Symbols
Convention Descri
p
tion
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
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.
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:
Cate
g
or
y
Documents Pur
p
oses
Product description and
specifications
Marketing brochures Describe product specifications and benefits.
Technology white papers
Provide an in-depth description of software features

Cate
g
or
y
Documents Pur
p
oses
and technologies.
Card datasheets Describe card specifications, features, and
standards.
Hardware specifications
and installation
Regulatory compliance
and safety information
Provides regulatory information and the safety
instructions that must be followed during installation.
Installation guide Provides a complete guide to hardware installation
and hardware specifications.
Quick start
Guides you through initial installation and setup
procedures to help you quickly set up and use your
switch with the minimum configuration.
H3C Pluggable SFP
[SFP+][XFP] Transceiver
Modules Installation
Guide
Guides you through installing SFP/SFP+/XFP
transceiver modules.
Adjustable Slider Rail
Installation Guide
Guides you through installing adjustable slider rails
to a rack.
H3C High-End Network
Products Hot-Swappable
Module Manual
Describes the hot-swappable modules available for
the H3C high-end network products, their external
views, and specifications.
Software configuration
Configuration guides Describe software features and configuration
procedures.
Command references Provide a quick reference to all available
commands.
Operations and
maintenance
System log messages Explains the system log messages.
Trap messages Explains the trap messages.
MIB Companion Describes the MIBs for the software release.
Release notes
Provide information about the product release,
including the version history, hardware and software
compatibility matrix, version upgrade information,
technical support information, and software
upgrading.
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] – Provides hardware installation, software
upgrading, and software feature configuration and maintenance documentation.
[Products & Solutions] – Provides information about products and technologies, as well as solutions.
[Technical Support & Documents > Software Download] – Provides the documentation released with the
software version.

Technical support
servi[email protected]
http://www.h3c.com
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················································································································································4
Placement of Layer 3 gateways ······························································································································7
ARP flooding suppression········································································································································7
Selective flooding ·····················································································································································8
Path MTU···································································································································································8
EVI configuration task list ·················································································································································9
Configuring EVI basic functions·······································································································································9
Configuring an IPv4 EVI tunnel ·······························································································································9
Assigning a network ID to the EVI tunnel············································································································ 10
Specifying extended VLANs on the EVI tunnel··································································································· 10
Configuring ENDP················································································································································· 11
Enabling EVI on transport-facing physical interfaces ························································································ 12
Tuning EVI IS-IS parameters ·········································································································································· 13
EVI IS-IS configuration task list ····························································································································· 13
Configuring an EVI IS-IS process ························································································································· 13
Optimizing an EVI IS-IS network·························································································································· 14
Configuring graceful restart for an EVI IS-IS process························································································· 17
Increasing the maximum number of MAC entries in an LSP for an EVI IS-IS process ···································· 18
Enabling EVI ARP flooding suppression······················································································································· 18
Enabling selective flooding for a MAC address········································································································· 19
Displaying and maintaining EVI··································································································································· 19
EVI configuration examples ·········································································································································· 20
Single-homed EVI network configuration example ···························································································· 21
Multiple-EVI-networks configuration example····································································································· 64H26
29HEVI Layer 2 multicast configuration example ····································································································· 65H28
30HIndex ···········································································································································································66H32

1
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 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 interrupt 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.
•High availability—EVI supports redundant edge devices and has a loop-free mechanism to prevent
loops for a multihomed network site.
•Link efficiency—EVI optimizes the inter-site multicast and broadcast transmission mechanism and
implements load-sharing on redundant links.

2
•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 2, an EVI network comprises one or multiple edge devices at each site. These sites are
connected through virtual links across an IP-based transport network 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.
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

3
Figure 3 Multiple EVI networks
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 serve only 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.
Site 1
Site 2
Site 4
Site 5
EVI 1
VLANs 100-101
EVI 2
VLAN 4000
EVI 3
VLANs 50-80
Site 3

4
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
Designated edge devices (DEDs) include inter-site DEDs and site DED.
An inter-site DED is elected from between the edge devices on each EVI link to send CSNP packets for
LSDB synchronization.
A site DED is elected from among the redundant edge devices at a multihomed site to distribute extended
VLANs among them so the traffic of a VLAN always enters or leaves the site from the same edge device.
The current software version does not support multihoming. In this document, DEDs only refer to inter-site
DEDs.
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.
3. Forwards traffic based on MAC reachability information that has been advertised from other sites.
This section describes these phases in detail.
Neighbor discovery
An EVI network runs ENDP to discover all its edge devices and establishes adjacencies between 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:

5
•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.
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.
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 rather than an internal 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.

6
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.
Figure 5 Layer 2 forwarding between sites
Multicast flow
Edge devices run IPv4 IGMP snooping or IPv6 MLD snooping on each extended VLAN and learn
multicast router port and multicast member port information on EVI-Link interfaces for Layer 2 multicast
forwarding as if they were Ethernet interfaces. In an extended VLAN, each edge device tunnels IGMP,
MLD, and PIM protocol packets to all its remote edge devices, and the remote edge devices flood the
packets in the VLAN.
For a site-to-site multicast data frame in an extended VLAN, the following process (see Figure 6) takes
place:
1. The DR in a site sends out a multicast frame.
2. The source edge device copies the frame and encapsulates one copy on each multicast member
EVI-Link interface.
3. The source edge device unicasts the encapsulated frames to the destination edge devices over the
EVI links.
4. Each destination edge device removes the headers of the multicast frame and copies the multicast
frame on each multicast member interface.
5. Each destination edge device sends the multicast frame out of all member interfaces to the
destination hosts.

7
Figure 6 Multicast data frame forwarding process
Flooding flow
An edge device handles floodings by frame type, as follows:
•Broadcast frame—Floods the frame out of all interfaces in the VLAN where the frame has been
received, including internal interfaces and EVI-link interfaces. For ARP packets, you can use the ARP
flooding suppression feature (see "ARP flooding suppression") to reduce ARP broadcasts.
•Destination-unknown unicast or multicast frame—Floods the frame out of all internal interfaces in
the VLAN where the frame has been received. The edge device typically does not propagate
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").
If a frame must be flooded to remote sites, the EVI edge device replicates the frame on each EVI link,
encapsulates each replica in a unicast frame, and sends the unicast frames to their respective destination
sites.
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.
ARP flooding suppression
ARP flooding 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 7, this feature snoops ARP
replies on an EVI tunnel interface to cache ARP entries for remote MAC addresses. If an ARP request has
a matching ARP entry, the local edge device replies to the request on behalf of the remote-site host. If no
matching ARP entry is found, the edge device floods the request to the EVI network.
ARP flooding suppression uses the following workflow:
1. Host IP1 in site A sends an ARP request to obtain the MAC address of IP2.
(1) Multicast stream
(2) Replicate & encapsulate (3) Unicast (4) Decapsulate & replicate
EVI
EVI
EVI
(5) Multicast stream
DR
Source
Receiver
Receiver
EVI
(3) Unicast Eth1/1
EVI-Link1
EVI-Link2
Eth1/1
EVI-Link1
Eth1/1
(4) Decapsulate &
replicate
(5) Multicast stream
EVI-Link1
VLAN R-port H-port
100 Eth1/1 EVI-Link1
EVI-Link2
VLAN R-port H-port
100 EVI-Link1 Eth1/1
VLAN R-port H-port
100 EVI-Link1 Eth1/1
Site 1
Site 2
Site 3

8
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 7 ARP flooding 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 and cannot be
added to a multicast forwarding table by IGMP snooping.
For example, you must configure selective flooding for PIM hellos, IGMP general 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
sets the DF bit in the IP header. For an Ethernet transport network, the total packet size increases by up
to 46 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.

9
EVI configuration task list
Tasks at a
g
lance Remarks
Configuring EVI basic functions:
•(Required.) Configuring an IPv4 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
All edge devices in an EVI network
must have the same network ID.
An extended VLAN can be
assigned only to 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 flooding suppression
Perform this task to reduce ARP
request broadcasts on an EVI
network.
(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 functions
All tasks in this section are required for setting up an EVI network.
Configuring an IPv4 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.

10
Step Command Remarks
3. Specify a source IPv4
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.
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.
The source interface can be a Layer 3
Ethernet interface, Layer 3 aggregate
interface, VLAN interface, or Layer 3
loopback interface.
EVI networks can share a tunnel
source IP address or 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.
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.
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 among all EVI tunnels.
To assign a network ID 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 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:

11
•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.
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 a list of extended
VLANs. evi-isis extend-vlan vlan-list
By default, no VLANs are specified 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
•You can configure up to two ENDSs on an EVI tunnel interface for redundancy. These two ENDSs
work separately. The failure of one ENDS does not affect the neighbor discovery and EVI link
maintenance in the EVI network.
•To guarantee that each edge device can get 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.
{If authentication is disabled on an ENDS, all ENDCs, including authentication-enabled ENDCs,
can register with the ENDS without authentication.
{If authentication is enabled on an ENDS, only authentication-enabled ENDCs that use the
same authentication key as the ENDS can register with the ENDS.
Configuring the edge device as an ENDS on the EVI tunnel
Ste
p
Command Remarks
1. Enter system view. system-view N/A
2. Enter EVI tunnel
interface view.
interface tunnel number [ mode
evi ] N/A

12
Ste
p
Command Remarks
3. Enable ENDS. evi neighbor-discovery server
enable
By default, ENDS is disabled.
An ENDS is always an ENDC of itself. 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 simple-password
By default, ENDP authentication is
disabled.
Configuring the edge device as an ENDC on the EVI tunnel
Ste
p
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.
An ENDS is always an ENDC of itself.
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 simple-password
By default, ENDP authentication is
disabled.
All ENDSs and ENDCs in an EVI
network must use the same
authentication password.
5. Configure the interval at
which the ENDC updates its
registration with ENDSs.
evi neighbor-discovery client
register-interval time-value
By default, an ENDC update its
registration with an ENDS every 15
seconds.
Enabling EVI on transport-facing physical interfaces
Enable EVI on all transport-facing physical interfaces that provide transport network access for EVI
tunnels.
To avoid forwarding failure, do not enable the spanning tree feature on these interfaces.
To enable EVI on an interface:
Ste
p
Command Remarks
1. Enter system view. system-view N/A

13
Ste
p
Command Remarks
2. Enter Layer 2 or Layer 3
Ethernet interface view.
interface interface-type
interface-number N/A
3. Enable EVI on the interface. evi enable By default, EVI function 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
g
lance Remarks
Configuring 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 packet sending interval
•Configuring the minimum LSP sending interval and the
maximum number of LSPs sent at each interval
•Configuring the maximum LSP lifetime
•Configuring the LSP refresh interval
•Enabling adjacency change logging
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.
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.
Configuring an EVI IS-IS process
When you create an EVI tunnel interface, the system automatically creates an EVI IS-IS process that has
the same number as the interface. You can access the EVI IS-IS process view to change EVI IS-IS
process-specific settings.
Alternatively, you can create an EVI IS-IS process before creating an EVI tunnel interface and configure
the process-specific settings, but the process and its settings take effect only after the interface is created.
An automatically created EVI IS-IS process can be manually deleted by using the undo evi-isis command
or automatically deleted when you delete its EVI tunnel interface. In contrast, to delete a manually
created EVI IS-IS process, you must use the undo evi-isis command. Deleting its EVI tunnel interface can
only invalidate the process.