H3C S9800 Series Manual de usuario

H3C S9800 Switch Series

EVI Configuration Guide

Hangzhou H3C Technologies Co., Ltd.

http://www.h3c.com

Software version: Release 213x

Document version: 6W101-20151130

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, , H3CS, H3CIE, H3CNE, Aolynk, , H3Care, , IRF, NetPilot, Netflow,

SecEngine, SecPath, SecCenter, SecBlade, Comware, ITCMM 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 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.

The EVI Configuration Guide describes the application scenarios, fundamentals, and configuration of

EVI.

This preface includes:

•Audience

•Conventions

•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 S9800 series

Conventions

This section describes the conventions used in this documentation set.

Command conventions

Convention Descri

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.

[ x | y | ... ] *

Asterisk marked square brackets enclose optional syntax choices separated by vertical

bars, from which you select one choice, multiple choices, or none.

Convention Descri

tion

&<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

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

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.

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 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 card, such as a firewall, load-balancing, NetStream, SSL VPN, IPS,

or ACG card.

Port numbering in examples

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

configuration and maintenance documentation.

[Products & Solutions]—Provides information about products and technologies, as well as solutions.

[Software Download]—Provides the documentation released with the software version.

Technical support

servic[email protected]

http://www.h3c.com

Documentation feedback

You can e-mail your comments about product documentation to info@h3c.com.

We appreciate your comments.



Contents

Configuring EVI ···························································································································································· 1

Overview············································································································································································1

Layer 2 connectivity extension issues ·····················································································································1

Network topologies··················································································································································2

Terminology ······························································································································································3

Working mechanism················································································································································4

Selective flooding ·····················································································································································6

Path MTU···································································································································································7

Licensing requirements······················································································································································7

Prerequisites·······································································································································································7

EVI configuration task list ·················································································································································7

Configuring EVI basic functions·······································································································································8

Configuring a site ID················································································································································8

Configuring an EVI tunnel ·······································································································································8

Assigning a network ID to the EVI tunnel···············································································································9

Specifying extended VLANs on the EVI tunnel······································································································9

Configuring ENDP················································································································································· 10

Enabling EVI on transport-facing physical interfaces ························································································ 11

Tuning EVI IS-IS parameters ·········································································································································· 12

EVI IS-IS configuration task list ····························································································································· 12

Creating an EVI IS-IS process······························································································································· 12

Optimizing an EVI IS-IS network·························································································································· 13

Specifying a routing policy for an EVI IS-IS process·························································································· 16

Enabling adjacency change logging ·················································································································· 16

Configuring SNMP notifications and context for EVI IS-IS················································································ 17

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 flooding for all destination-unknown frames ························································································ 18

Enabling selective flooding for a MAC address········································································································· 19

Enabling MAC address learning at the ingress·········································································································· 19

Displaying and maintaining EVI··································································································································· 20

EVI configuration examples ·········································································································································· 21

EVI network configuration example····················································································································· 21

Multiple-EVI-networks configuration example····································································································· 26

Index ···········································································································································································30

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.

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.

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

Site 1

Site 2

Site 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 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.

Site 1

Site 2

Site 4

Site 5

EVI 1

VLANs 100-101

EVI 2

VLAN 4000

EVI 3

VLANs 50-80

Site 3

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

An inter-site 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.

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").

•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.

Otros manuales para S9800 Series

Tabla de contenidos

Otros manuales de Cambiar de H3C

H3C

H3C S6520X-EI Series Manual de usuario

H3C

H3C S3610 Series Instrucciones de instalación

H3C

H3C S9500E Series Manual de usuario

H3C

H3C S7500 Series Instrucciones de instalación

H3C

H3C S9505 SRP Manual de usuario

H3C

H3C S12500X-AF Series Manual de usuario

H3C

H3C S12500 Series Guía rápida

H3C

H3C S9500 Series Manual de usuario

H3C

H3C S5830V2 series Manual de usuario

H3C

H3C LSQM1TGS24QSA0 Manual de usuario

H3C

H3C S5830V2 series Manual de usuario

H3C

H3C s5820x series Manual de instalación

H3C

H3C S5590-HI Series Manual de usuario

H3C

H3C S5500-SI Series Manual de usuario

H3C

H3C S3610 Series Manual de usuario

H3C

H3C S7500 Series Instrucciones de instalación

H3C

H3C S5120-EI Series Manual de instalación

H3C

H3C S5500-SI Series Manual de usuario

H3C

H3C S7500 Series Manual de usuario

H3C

H3C S3100-8C-Sl Manual de usuario

H3C

H3C S9804 Manual de usuario

H3C

H3C S7500 Series Manual de usuario

H3C

H3C S3100-52P Instrucciones de instalación

H3C

H3C S9500 Series Manual de usuario

Manuales populares de Cambiar de otras marcas

URC

URC Total Control MFS-8 Manual de usuario

Azbil

Azbil HPQ-D11 Manual de usuario

Sony

Sony DFS-900M Manual de usuario

SICK

SICK i17S Manual de usuario

F&F

F&F SZR-277 Manual de usuario

Shure

Shure UAMS/BK Manual de usuario

Dräger

Dräger X-zone Switch Off Manual de usuario

Asco

Asco Joucomatic 349 Series Manual de usuario

BT Mini Hub Manual de usuario

D-Link

D-Link DES-1226G Manual de usuario

Johnson Controls

Johnson Controls FS80-C Manual de usuario

Alcatel-Lucent

Alcatel-Lucent 7450 ESS-12 Manual de usuario

MicroNet

MicroNet SP1200A Manual de usuario

Ruijie

Ruijie RG-PF2920 Series Manual de instalación y funcionamiento

Altinex

Altinex DA1914SX Manual de usuario

MiLAN

MiLAN MIL-SM2401M Manual de usuario

RJM

RJM MASTERMIND PBC/6X Manual de usuario

Atlas

Atlas MMK-KVM8 Manual de usuario