CloudEngine 6800&5800 V100R001C00 Configuration Guide - TRILL 04 PDF

CloudEngine 6800&5800 Series Switches
V100R001C00
Configuration Guide - TRILL
Issue 04
Date 2013-07-10
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
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 a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://enterprise.huawei.com
Issue 04 (2013-07-10) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i
About This Document
Intended Audience
This document describes TRILL features on the device and provides configuration procedures
and configuration examples.
This document is intended for:
l Data configuration engineers
l Commissioning engineers
l Network monitoring engineers
l System maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
DANGER
Indicates a hazard with a high level or medium level of risk
which, if not avoided, could result in death or serious injury.
WARNING
Indicates a hazard with a low level of risk which, if not
avoided, could result in minor or moderate injury.
CAUTION
Indicates a potentially hazardous situation that, if not
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
TIP
Provides a tip that may help you solve a problem or save time.
NOTE
Provides additional information to emphasize or supplement
important points in the main text.

Command Conventions
The command conventions that may be found in this document are defined as follows.
Configuration Guide - TRILL About This Document
ii
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[ ] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by
vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by
vertical bars. One item is selected or no item is selected.
{ x | y | ... }
*
Optional items are grouped in braces and separated by
vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]
*
Optional items are grouped in brackets and separated by
vertical bars. You can select one or several items, or select
no item.
&<1-n> The parameter before the & sign can be repeated 1 to n times.
# A line starting with the # sign is comments.

Interface Numbering Conventions
Interface numbers used in this manual are examples. In device configuration, use the existing
interface numbers on devices.
Change History
Changes between document issues are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Changes in Issue 04 (2013-07-10)
This version has the following updates:
The following information is modified:
l 1.2 TRILL Features Supported by the Device
l 1.6.1 Configuring TRILL Packet Authentication
l 1.6.2 Configuring TRILL Interface Authentication
iii
l 1.2 TRILL Features Supported by the Device
l 1.8.1 Example for Configuring Basic TRILL Functions
Initial commercial release.
iv
Contents
About This Document.....................................................................................................................ii
1 TRILL Configuration....................................................................................................................1
1.1 Introduction to TRILL....................................................................................................................................................2
1.2 TRILL Features Supported by the Device......................................................................................................................3
1.3 Configuring Basic TRILL Functions..............................................................................................................................5
1.3.1 Enabling TRILL Globally...........................................................................................................................................6
1.3.2 Enabling TRILL on an Interface..................................................................................................................................9
1.3.3 (Optional) Configuring a Link Cost for a TRILL Interface......................................................................................10
1.3.4 Checking the Configuration.......................................................................................................................................12
1.4 Implementing Refined Control over TRILL Route Selection......................................................................................12
1.4.1 Selecting the DVLAN...............................................................................................................................................13
1.4.2 Configuring TRILL Load Balancing.........................................................................................................................14
1.5 Adjusting the TRILL Network Convergence Speed....................................................................................................14
1.5.1 Adjusting the Interval at Which Neighbor Status Is Detected...................................................................................15
1.5.2 Adjusting Flooding Parameters of SNPs and LSPs...................................................................................................16
1.5.3 Adjusting the SPF Calculation Interval.....................................................................................................................19
1.6 Improving TRILL Network Security............................................................................................................................21
1.6.1 Configuring TRILL Packet Authentication...............................................................................................................21
1.6.2 Configuring TRILL Interface Authentication...........................................................................................................22
1.7 Maintaining TRILL......................................................................................................................................................23
1.7.1 Resetting TRILL........................................................................................................................................................23
1.8 Configuration Examples...............................................................................................................................................24
1.8.1 Example for Configuring Basic TRILL Functions....................................................................................................24
Configuration Guide - TRILL Contents
v
1 TRILL Configuration
About This Chapter
Transparent Interconnection of Lots of Links (TRILL) uses Intermediate System to Intermediate
System (IS-IS) to enable communication over Layer 2 networks. TRILL boasts easy deployment,
highly-efficient forwarding, high-speed convergence, and loop prevention. Therefore, it meets
data centers' requirements for large-scale Layer 2 networks.
1.1 Introduction to TRILL
Transparent Interconnection of Lots of Links (TRILL) is a protocol that applies Layer 3 link
state routing technologies to Layer 2 networks. TRILL extends Intermediate System to
Intermediate System (IS-IS) and uses the Shortest Path First (SPF) algorithm to calculate routes.
1.2 TRILL Features Supported by the Device
1.3 Configuring Basic TRILL Functions
Basic TRILL functions allow all devices to communicate with each other on TRILL networks.
1.4 Implementing Refined Control over TRILL Route Selection
To better control route selection and use network resources more efficiently, you can implement
refined control over Transparent Interconnection of Lots of Links (TRILL) route selection.
1.5 Adjusting the TRILL Network Convergence Speed
Shortest Path First (SPF) parameters and link state protocol data unit (LSP) fast flooding control
the Transparent Interconnection of Lots of Links (TRILL) network convergence speed.
1.6 Improving TRILL Network Security
Transparent Interconnection of Lots of Links (TRILL) authentication can improve TRILL
network security.
1.7 Maintaining TRILL
Resetting Transparent Interconnection of Lots of Links (TRILL) helps diagnose network faults.
1.8 Configuration Examples
This section provides several TRILL configuration examples. The configuration examples
include networking requirements, precautions, the configuration roadmap, and the configuration
procedure.
Configuration Guide - TRILL 1 TRILL Configuration
1
1.1 Introduction to TRILL
Transparent Interconnection of Lots of Links (TRILL) is a protocol that applies Layer 3 link
state routing technologies to Layer 2 networks. TRILL extends Intermediate System to
Intermediate System (IS-IS) and uses the Shortest Path First (SPF) algorithm to calculate routes.
Overview
Traditional data center operators provide basic infrastructure-based services for users. As the
Internet develops constantly, services increase dramatically, users require more efficient, secure,
and reliable services. At the same time, data center operators need to reduce costs and provide
more value-added services. Cloud computing that provides a new service mode for data center
operators is an effective solution. However, data centers using cloud computing require more
bandwidth resources. In addition, virtual device technologies that connect data centers
seamlessly and support file sharing and data copying between data centers are necessary for
capacity expansion and disaster recovery. However, virtual device relocation multiplies the
difficulty in network deployment and management. In this situation, large-scale Layer 2
networks are required.
TRILL extends IS-IS and combines configuration flexibility of Layer 2 networks and the large
scale of Layer 3 networks. It boasts easy deployment, highly-efficient forwarding, high-speed
convergence, and loop prevention and provides a better solution to data centers.
Characteristics
Compared with other Layer 2 protocols or Layer 3 IP running on data centers, TRILL has the
following advantages:
l Easy deployment: Compared with Layer 3 IP, TRILL is easier to deploy because you do
not need to configure interface IP addresses.
l Loop prevention: The hop field in the TRILL header can minimize the impact of temporary
loops.
l High-speed convergence: TRILL detects the network in real time, and routes can be
converged within sub-seconds.
l Highly-efficient forwarding: Devices on a TRILL network use the Shortest Path First (SPF)
algorithm to generate the unicast and multicast forwarding tables and transmit traffic based
on the forwarding tables.
Basic Concepts
Table 1-1 lists the basic concepts related to a TRILL network.
Table 1-1 Basic concepts about TRILL
Concept Description
Routing bridge (RB) Switch that runs TRILL.
2
Concept Description
Designated routing bridge (DRB) RB that communicates with each device on
broadcast networks and sends complete
sequence number protocol data units
(CSNPs) to synchronize all the link state
databases (LSDBs). DRB is only exist in
broadcast network.
Appointed forwarder (AF) RB that is selected by a DRB to transmit user
packets.
Carrier VLAN VLAN that transmits TRILL data and
protocol packets.
Custom edge VLAN (CE VLAN) VLAN that is used for CE users to access
TRILL networks and that transmits Ethernet
data packets only.
Designated VLAN (DVLAN) VLAN that is selected to transmit TRILL data
and control packets.
Admin VLAN VLAN that is used by administrators to
maintain and manage RBs through remote
login.
Nickname ID that uniquely identifies an RB.

1.2 TRILL Features Supported by the Device
TRILL enables user information to be efficiently and quickly transmitted between routing
bridges (RBs) and between an RB and a server.
NOTE
The CE series switches cannot terminate TRILL packets at Layer 2 and then forward them at Layer 3.
Table 1-2 shows the TRILL configuration outline.
Table 1-2 TRILL configuration outline
Objectives Procedures Description
To transmit information by
TRILL.
1.3 Configuring Basic
TRILL Functions
This configuration is
mandatory.
NOTE
This procedure is a prerequisite
for the following ones.
3
Objectives Procedures Description
To use network resources
efficiently and reduce
network congestion.
1.3 Configuring Basic
TRILL Functions
l 1.3.3 (Optional)
Configuring a Link Cost
for a TRILL Interface
1.4 Implementing Refined
Control over TRILL Route
Selection
l 1.4.1 Selecting the
DVLAN
l 1.4.2 Configuring
TRILL Load Balancing
These configurations are
optional.
Before the configuration,
familiarize yourself with the
following:
TRILL Route Selection
Rules
To adjust the TRILL network
convergence speed
1.5 Adjusting the TRILL
Network Convergence
Speed
l 1.5.1 Adjusting the
Interval at Which
Neighbor Status Is
Detected
l 1.5.2 Adjusting
Flooding Parameters of
SNPs and LSPs
l 1.5.3 Adjusting the SPF
Calculation Interval
optional.
following:
Factors Determining the
TRILL Network
Convergence Speed
To improve TRILL network
security.
1.6 Improving TRILL
Network Security
l 1.6.1 Configuring
TRILL Packet
Authentication
l 1.6.2 Configuring
TRILL Interface
Authentication
optional.
following:
TRILL NSR

TRILL Route Selection Rules
On a TRILL network, routes are selected based on the following rules:
l The Shortest Path First (SPF) algorithm is used, and the route with the smallest link cost
is selected.
l Equal-cost routes (if there are) load-balance traffic. Load balancing is enabled on TRILL
networks by default.
Factors Determining the TRILL Network Convergence Speed
The network convergence speed is critical to network performance. The factors that determine
the TRILL network convergence speed are described as follows:
4
l Interval at which neighbor status is detected
RBs periodically exchange Hello packets to maintain the neighbor relationship between
them. By default, if one RB does not receive any response from the other after sending
three consecutive Hello packets, this RB considers the neighbor Down. Therefore, the
interval at which Hello packets are sent and the number of consecutive Hello packets that
are sent before an RB considers the neighbor Down determine the TRILL network
convergence speed.
l Flooding parameters of sequence number PDUs (SNPs) and link state protocol data units
(LSPs)
LSPs carry status changes on networks, and SNPs carry complete or partial LSP
information. LSPs and SNPs are periodically updated to synchronize link state databases
(LSDBs) so that nickname forwarding tables can keep pace with network changes.
The LSP refresh interval, sending interval, maximum lifetime, and SNP sending interval
determine the broadcast network convergence speed. The LSP retransmission interval
determines the P2P network convergence speed.
l SPF calculation interval
After LSDBs are synchronized, RBs perform the SPF algorithm to calculate routes.
Therefore, SPF calculation interval determines the network convergence speed.
TRILL NSR
NSR ensures uninterrupted traffic transmission if a fault occurs on the control plane and a backup
control plane is available to take over the traffic. During the switchover, the fault is transparent
to the control plane of a neighbor.
TRILL Authentication Modes
TRILL authentication improves network security.
TRILL supports simple, MD5, hmac-sha256 and keychain authentications. Hello packets, LSPs,
and SNPs carry authentication information, and packets that fail the authentication are discarded.
TRILL authentication prevents unauthorized users from tampering with packets and improves
network security.
1.3 Configuring Basic TRILL Functions
Basic TRILL functions allow all devices to communicate with each other on TRILL networks.
Applicable Environment
This section describes how to configure basic TRILL functions to allow switches to
communicate with each other on Layer 2 networks.
The configurations of basic TRILL functions involve enabling TRILL globally and then on each
interface.
5
Configuration Procedures
Figure 1-1 Flowchart of configuring basic TRILL functions
Enabling TRILL Globally
Enabling TRILL on an
Interface
Mandatory
procedure
Optional
procedure
(Optional) Configuring a Link
Cost for a TRILL Interface

1.3.1 Enabling TRILL Globally
Context
Before configuring other TRILL features, enable TRILL globally. Configure the following
additional functions to facilitate future management and maintenance:
l Configure the administrative VLAN to allow administrators to maintain and manage
routing bridges (RBs) using remote login.
l Configure a network entity title (NET) or dynamic hostname because TRILL uses the MAC
address of each RB as its system ID by default, and the MAC address is difficult to
memorize.
l Configure a nickname for each RB to avoid nickname conflicts and facilitate management.
The nickname of each RB must be unique on TRILL networks. However, a nickname is
generated automatically by default, which may result in nickname conflicts.
l Configure RB interface modes based on their roles on TRILL networks.
Procedure
Step 1 Run:
system-view
The system view is displayed.
Step 2 Run:
trill
TRILL is enabled globally, and the TRILL view is displayed.
6
Step 3 Run:
carrier-vlan carrier-vlanid
A Carrier VLAN ID is specified.
Step 4 (Optional) Run:
network-entity net
The NET is configured.
NOTE
The NET must be unique on TRILL networks. Otherwise, route flapping may occur.
nickname nicknamevalue [ priority priorityvalue ] [ root-priority
rootpriorityvalue ]
A nickname is configured.
NOTE
The nickname must be unique on a network. If a nickname conflict occurs, TRILL performs either of the
following operations:
l If the nickname conflicts with an automatically generated nickname, the RB with the lowest priority
generates a new nickname.
l If the nickname conflicts with a configured nickname, the nickname of the RB with the lowest priority
is suppressed and is not advertised to other RBs.
port-mode { access | hybrid | p2p | trunk }
An interface mode is configured.
NOTE
By default, the interface mode is trunk. Configure an interface mode based on the following rules:
l Configure the interface mode as access if the interface is located at the edge of a TRILL network to
connect to users.
l Configure the interface mode as trunk if the interface is located within a TRILL network and you want
the interface to transmit TRILL packets.
l Configure the interface mode as p2p if the interface connects RBs on a P2P network.
l Configure the interface mode as hybrid if you want the interface to connect to users and transmit
TRILL packets.
In a stack scenario, if the interface mode is hybrid, the interface may not forward packets. Therefore, the
hybrid mode is not recommended.
Step 7 (Optional) Perform the following steps to configure a CE VLAN if an RB is located at the edge
of a TRILL network and connects to a server.
1. Run:
quit
Exit from the TRILL view.
2. Run:
vlan vlan-id
A VLAN is created, and the VLAN view is displayed.
3. Run:
quit
7
Exit from the VLAN view.
4. Run:
trill
The TRILL view is displayed.
5. Run:
ce-vlan { vlan-id1 [ to vlan-id2 ] } & <1-10>
The CE VLAN ID is specified.
NOTE
A CE VLAN must be a VLAN created using the vlan command. A VLAN cannot function as both
a CE VLAN and a Carrier VLAN.
trill-name symbolic-name
A dynamic hostname is configured.
After you run this command, the configured symbolic-name is carried in LSPs and advertised
to other devices in the same domain. When you use display commands to check TRILL
information on these devices configured with dynamic hostname mapping, the system ID is
replaced with symbolic-name.
Step 9 (Optional) Perform the following steps to configure a admin VLAN to allow administrators to
maintain and manage RBs through remote.
1. Run:
quit
2. Run:
vlan vlan-id
A VLAN is created, and the VLAN view is displayed.
3. Run:
quit
Exit from the VLAN view.
4. Run:
trill
5. Run:
admin-vlan vlan-id
The administrative VLAN ID is specified.
NOTE
A admin VLAN must be a VLAN created using the vlan command. A VLAN cannot function as
both a admin VLAN and a Carrier VLAN.
6. Run:
quit
7. Run:
interface vlanif vlan-id
A VLANIF interface is created and the VLANIF interface view is displayed.
8
8. Run:
ip address ip-address { mask | mask-length } [ sub ]
An IP address is assigned to the VLANIF interface.
NOTE
The IP addresses must be in the same network segment with the edge device interfaces that directly
connect the RB interfaces, to provide reachable nickname.
NOTE
After the administrative VLAN ID is specified, configure IP addresses for RB interfaces in the
administrative VLAN.
Step 10 Run:
commit
The configuration is committed.
----End
1.3.2 Enabling TRILL on an Interface
Context
After enabling TRILL globally, enable TRILL on each interface so that RBs can establish TRILL
neighbor relationships.
TRILL can be enabled only on trunk or hybrid interfaces. Access interfaces can only be used
for user access and cannot have TRILL enabled.
TRILL interfaces are classified into four modes, the default of which is trunk. You can configure
interface modes for RBs based on their roles on TRILL networks to reduce the number of packets
to be processed and to use bandwidth and system resources more efficiently.
In addition, DRBs on broadcast networks must have relatively high levels of performance
because they need to communicate with each RB. Therefore, configure a DRB priority for each
interface so that RBs with higher DRB priorities can be elected as DRBs.
Procedure
Step 1 Run:
system-view
NOTE
Perform either of the following operations to enable TRILL on interfaces:
l Perform Step 2 if you want to enable TRILL on a small number of interfaces or on interfaces with
nonconsecutive sequence numbers.
l Perform Step 3 if you want to enable TRILL on a large number of interfaces or on interfaces with
consecutive sequence numbers.
Step 2 Run:
interface interface-type interface-number
The interface view is displayed.
9
Step 3 Perform the following steps:
1. Run:
port-group port-group-name
An interface group is created.
2. Run:
group-member { interface-type interface-number1 [ to interface-type interface-
number2 ] } & <1-10>
An interface number range is specified for the interface group.
Step 4 Run:
trill enable [ port-mode { access | hybrid | p2p | trunk } ]
TRILL is enabled on the interface or interface group and the interface mode is configured..
NOTE
l If the interface is Down, enable the TRILL process in the interface view and run the undo shutdown
command to restart the interface.
l By default, the interface mode is trunk. Configure an interface mode based on the following rules:
l Configure the interface mode as access if the interface is located at the edge of a TRILL network
to connect to users.
l Configure the interface mode as trunk if the interface is located within a TRILL network and you
want the interface to transmit TRILL packets.
l Configure the interface mode as p2p if the interface connects RBs on a P2P network.
l Configure the interface mode as hybrid if you want the interface to connect to users and transmit
TRILL packets.
l In a stack scenario, if the interface mode is hybrid, the interface may not forward packets. Therefore,
the hybrid mode is not recommended.
l When both the stacking and TRILL functions are enabled on a device, you can only configure load
balancing based on the MAC addresses of user packets in the LAG load balancing profile, if LAG is
configured on an access-side interface of the TRILL network.
trill drb-priority priority
A DRB priority is configured on the interface.
By default, the DRB priority of an interface is 64. If you want the RB to be elected as a DRB,
configure a relatively high DRB priority.
Step 6 Run:
commit
----End
1.3.3 (Optional) Configuring a Link Cost for a TRILL Interface
Context
Because TRILL uses the Shortest Path First (SPF) algorithm to generate unicast and multicast
forwarding tables, the link cost is crucial to route selection. If you adjust the link costs of TRILL
interfaces, routes are reselected. The following link costs take effect on a TRILL interface in
ascending order of priority:
10
l Automatically calculated link cost: By default, the calculation formula is as follows: Link
cost of the interface = Bandwidth reference value/Interface bandwidth. You can change the
bandwidth reference value to adjust the link cost of an interface.
l Global link cost: the link cost shared by all TRILL interfaces on an RB
l Interface link cost: the link cost configured for a specified TRILL interface
Procedure
l Adjust the automatically calculated link cost.
1. Run:
system-view
2. Run:
trill
3. Run:
bandwidth-reference value
The bandwidth reference value is reconfigured.
4. Run:
commit
l Configure a global link cost.
1. Run:
system-view
2. Run:
trill
3. Run:
circuit-cost { cost | maximum }
A global link cost is configured.
4. Run:
commit
l Configure an interface link cost.
1. Run:
system-view
2. Run:
3. Run:
11
trill cost { cost | maximum }
An interface link cost is configured.
4. Run:
commit
----End
1.3.4 Checking the Configuration
Procedure
l Run the display trill interface [ verbose ] command to check detailed information about
TRILL interfaces.
l Run the display trill lsdb [ verbose ] command to check TRILL LSDB information.
l Run the display trill peer [ verbose ] command to check information about TRILL
neighbors.
l Run the display trill route [ nickname ] command to check information about TRILL
unicast routes.
l Run the display trill name-table command to check the mapping between the system ID
and dynamic hostname.
l Run the display trill mroute [ vlan-id ] command to check information about TRILL
multicast routes.
----End
1.4 Implementing Refined Control over TRILL Route
Selection
To better control route selection and use network resources more efficiently, you can implement
refined control over Transparent Interconnection of Lots of Links (TRILL) route selection.
After you configure basic TRILL functions, devices on the network use TRILL to communicate
with each other. TRILL uses the Shortest Path First (SPF) algorithm to generate unicast and
multicast forwarding tables based on link state databases (LSDBs) and transmits traffic based
on these forwarding tables. The TRILL mechanisms alone, however, cannot meet the
requirements for network planning and traffic management on large-scale networks. Because
TRILL uses SPF to generate unicast and multicast forwarding tables, some links with higher
link costs may be idle, while those with lower link costs may be overloaded. This load imbalance
wastes a great number of network resources and affects the transmission quality. To better control
route selection and use network resources more efficiently, you can implement refined control
over TRILL route selection.
To implement refined control over TRILL route selection, perform the following operations:
l 1.3.3 (Optional) Configuring a Link Cost for a TRILL Interface
12
NOTE
Adjust the link costs of TRILL interfaces when you configure basic TRILL functions because
adjusting link costs while TRILL services are running on large-scale networks causes route
recalculation and convergence.
l 1.4.1 Selecting the DVLAN
l 1.4.2 Configuring TRILL Load Balancing
Pre-configuration Task
Before implementing refined control over TRILL route selection, complete the following task:
l 1.3 Configuring Basic TRILL Functions
Select one or more configurations tasks.
1.4.1 Selecting the DVLAN
Context
In network planning, an operator may deploy multiple Carrier VLANs on the TRILL network.
However, only one of them can function as the DVLAN. In most cases, the designated routing
bridge (DRB) selects one Carrier VLAN as the DVLAN, but the DVLAN selected in this way
may not conform to the network planning. In this situation, select a DVLAN based on the network
planning. After a DVLAN is selected, only the DVLAN can transmit TRILL data packets.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
trill designated-vlan vlan-id
The DVLAN is specified.
NOTE
The DVLAN must be a Carrier VLAN.
Step 4 Run:
commit
----End
13
1.4.2 Configuring TRILL Load Balancing
Context
On large-scale TRILL networks, multiple equal-cost routes to the same destination may be
available. Without load balancing, traffic is transmitted randomly, which results in poor traffic
management. If these equal-cost routes load-balance traffic, network resource usage increases
and network congestion along overloaded routes is prevented.
Procedure
Step 1 Run:
system-view
Step 2 Run:
trill
Step 3 Run:
maximum load-balance number
The maximum number of equal-cost routes for load-balancing is configured.
NOTE
By default, the maximum number of equal-cost routes for load balancing is 16.
If equal-cost routes outnumber the configured value on a TRILL network, the TRILL network selects the
equal-cost routes in the following sequence:
l Route with the smaller outbound interface index
l Route whose next hop RB has the smaller system ID
Step 4 Run:
commit
----End
Procedure
l Run the display trill interface [ verbose ] command to check TRILL interface information.
l Run the display trill route [ nickname ] command to check information about TRILL
unicast routes.
----End
1.5 Adjusting the TRILL Network Convergence Speed
Shortest Path First (SPF) parameters and link state protocol data unit (LSP) fast flooding control
the Transparent Interconnection of Lots of Links (TRILL) network convergence speed.
14
The network convergence speed is critical to network performance. TRILL boasts high-speed
convergence, but when TRILL is deployed on large-scale data center networks, network
complexity slows down the convergence. In this situation, use the following approaches listed
in Table 1-3 to adjust the network convergence speed.
Table 1-3 Approaches to adjust the TRILL network convergence speed
TRILL Running Phase Approaches to Adjust the TRILL
Network Convergence Speed
Neighbor relationship establishment Adjust the interval at which neighbor status
is detected by changing the interval at which
Hello packets are sent and the hold time of
neighbors.
Link state database (LSDB) synchronization Adjust flooding parameters of sequence
number PDUs (SNPs) and LSPs.
SPF algorithm Adjust the SPF calculation interval.

Before adjusting the TRILL network convergence speed, complete the following task:
1.5.1 Adjusting the Interval at Which Neighbor Status Is Detected
Context
Routing bridges (RBs) exchange Hello packets to establish neighbor relationships on TRILL
networks. After establishing neighbor relationships, RBs send Hello packets at intervals to
maintain the neighbor relationships and detect neighbor status. If a local RB does not receive
any Hello packets from a neighboring device within a specified period (hold time), the local RB
considers the neighboring device Down and refreshes the local routing table. As a result, routes
are re-converged on the TRILL network. Perform the following operations to adjust the interval
at which neighbor status is detected:
l Adjust the interval at which Hello packets are sent.
l Configure the holding multiplier for neighboring devices.
Procedure
l Adjust the interval at which Hello packets are sent.
1. Run:
system-view
15
2. Run:
3. Run:
trill timer hello hello-interval
The interval at which Hello packets are sent is configured for the interface.
4. Run:
commit
l Configure the holding multiplier for neighboring devices.
1. Run:
system-view
2. Run:
3. Run:
trill timer holding-multiplier number
The holding multiplier is configured. The formula to calculate the hold time is as
follows: Hold time = Holding multiplier x Interval at which Hello packets are sent.
4. Run:
commit
----End
1.5.2 Adjusting Flooding Parameters of SNPs and LSPs
Context
When the network status changes, routing bridges (RBs) send LSPs to advertise these changes
on TRILL networks. SNPs carry complete or partial LSP information and are used to synchronize
LSDBs. SNPs are classified into complete SNPs (CSNPs) and partial SNPs (PSNPs). CSNPs
carry summaries of all LSPs in LSDBs, while PSNPs list only the sequence numbers of recently
received LSPs.
The LSDB synchronization process varies with the network type. The LSDB synchronization
processes on broadcast and P2P networks are described as follows:
l On broadcast networks, if a designated routing bridge (DRB) receives an LSP that is
unavailable in its LSDB, the DRB adds this LSP to its LSDB and sends CSNPs at intervals
to broadcast the updated LSDB. After receiving the CSNP, each RB checks whether its
LSDB is synchronous with the CSNP. If they are asynchronous, the RB sends a PSNP to
request the LSPs that are unavailable in its LSDB.
l On P2P networks, CSPNs are sent only when two ends are establishing an adjacency for
the first time. The local RB sends a CSNP, and the remote RB replies with a PSNP. If the
16
CSNP and the LSDB of the remote RB are asynchronous, the remote RB sends a PSNP to
request the LSPs that are unavailable in its LSDB. After receiving the PSNP, the local RB
replies with the required LSPs and starts the LSP timer at the same time. If the local RB
does not receive any PSNP as a response from the remote RB before the LSP timer expires,
the local RB re-sends the LSP.
To speed up LSDB synchronization, adjust the following parameters of SNPs and LSPs:
l Set the interval at which CSNPs are sent
l onfigure the intelligent timer to control LSP generation
l Set the refresh interval for LSPs
l Set the maximum lifetime for LSPs
l Set the minimum interval at which LSPs are sent
l Set the interval at which LSPs are retransmitted over a P2P link
Procedure
l Set the interval at which CSNPs are sent.
1. Run:
system-view
2. Run:
3. Run:
trill timer csnp csnpinterval
The interval at which CSNPs are sent is set for the interface.
4. Run:
commit
l Configure the intelligent timer to control LSP generation.
1. Run:
system-view
2. Run:
trill
3. Run:
timer lsp-generation max-interval [ init-interval [ incr-interval ] ]
The intelligent timer is configured to control LSP generation.
The parameters are described as follows:
If you specify max-interval only, the intelligent timer functions as an ordinary one-
time triggering timer, and LSPs are generated at the interval specified by max-
interval.
17
If you specify both max-interval and init-interval, init-interval determines the
delay in generating an LSP for the first time, and from the second time on, max-
interval determines the delay in generating an LSP. After the delay remains at the
value specified by max-interval for three times or the TRILL process is restarted,
the delay decreases to the value specified by init-interval.
If you specify max-interval, init-interval, and incr-interval, init-interval
determines the delay in generating an LSP for the first time, and incr-interval
determines the delay in generating the same LSP for the second time. From the
third time on, the delay in generating an LSP doubles each time until the delay
reaches the value specified by max-interval. After the delay remains at the value
specified by max-interval for three times or the TRILL process is restarted, the
delay decreases to the value specified by init-interval.
4. Run:
commit
l Set the refresh interval for LSPs.
1. Run:
system-view
2. Run:
trill
3. Run:
timer lsp-refresh refresh-time
The refresh interval is set for LSPs.
By default, the LSP refresh interval is 900s, and the maximum lifetime of an LSP is
1200s. The LSP refresh interval must be at least 300s shorter than the maximum LSP
lifetime. This implementation allows new LSPs to reach all RBs before existing LSPs
expire.
NOTE
The larger the network, the greater the deviation between the LSP refresh interval and the
maximum LSP lifetime.
4. Run:
commit
l Set the maximum lifetime for LSPs.
1. Run:
system-view
2. Run:
trill
3. Run:
timer lsp-max-age age-time
18
The maximum lifetime is set for LSPs.
When generating the system LSP, a switch fills in the maximum lifetime of this LSP.
If an RB does not receive any updated LSP 60s after the lifetime of this LSP decreases
to 0, the RB deletes this LSP from the LSDB.
4. Run:
commit
l Set the minimum interval at which LSPs are sent.
1. Run:
system-view
2. Run:
3. Run:
trill timer lsp-throttle throttleinterval [ count countnumber ]
The minimum interval at which LSPs are sent is set.
4. Run:
commit
l Set the interval at which LSPs are retransmitted over a P2P link.
1. Run:
system-view
2. Run:
3. Run:
trill timer lsp-retransmit retransmit-interval
The interval at which LSPs are retransmitted over a P2P link is set.
4. Run:
commit
----End
1.5.3 Adjusting the SPF Calculation Interval
Context
When the network status changes, TRILL performs the SPF algorithm to refresh route
information. If the network is unstable, TRILL performs frequent route calculation, which
consumes a large number of CPU resources and affects the running of services.
19
To solve this problem, configure an intelligent timer to control the SPF calculation interval.
Specifically, set the SPF calculation interval to a small value to speed up TRILL route
convergence, and set the interval to a large value after the TRILL network becomes stable.
Procedure
Step 1 Run:
system-view
Step 2 Run:
trill
Step 3 Run:
timer spf max-interval [ init-interval [ incr-interval ] ]
The SPF intelligent timer is configured.
Specify the parameters based on the following rules:
l If you specify max-interval only, the intelligent timer functions as an ordinary one-time
triggering timer, and TRILL performs the SPF algorithm after routes are converged and max-
interval expires.
l If you specify both max-interval and init-interval, init-interval determines the delay in SPF
calculation for the first time, and from the second time on, max-interval determines the delay
in SPF calculation. After the delay remains at the value specified by max-interval for three
times or the TRILL process is restarted, the delay decreases to the value specified by init-
interval.
l If you specify max-interval, init-interval, and incr-interval, init-interval determines the delay
in SPF calculation for the first time, and incr-interval determines the delay in SPF calculation
for the second time. From the third time on, the delay in SPF calculation doubles each time
until the delay reaches the value specified by max-interval. After the delay remains at the
value specified by max-interval for three times or the TRILL process is restarted, the delay
decreases to the value specified by init-interval.
Step 4 Run:
commit
----End
Procedure
l Run the display trill interface [ verbose ] command to check detailed information about
TRILL interfaces.
----End
20
1.6 Improving TRILL Network Security
Transparent Interconnection of Lots of Links (TRILL) authentication can improve TRILL
network security.
As the Internet develops, there has been considerable growth in all types of data, voice, and
video information exchanged on networks, requiring higher information security than before.
Therefore, operators must protect data packets from being intercepted or modified by attackers
and prohibit unauthorized users from accessing network resources.
A TRILL authentication-enabled device adds an authentication field to encapsulate a packet
before sending it to ensure network security. After receiving a TRILL packet from a remote
routing bridge (RB), the local RB discards the packet if the authentication password in the packet
is different than the local one. This authentication mechanism protects the local RB against
packets sent from unauthorized users. TRILL supports packet authentication and interface
authentication.
Before configuring TRILL authentication, complete the following task:
1.6.1 Configuring TRILL Packet Authentication
Context
In most cases, routing bridges (RBs) do not encapsulate authentication information into TRILL
packets before sending them or authenticate received TRILL packets. Therefore, networks are
open to attacks. To improve network security, configure TRILL authentication.
In TRILL packet authentication, link state protocol data units (LSPs) and sequence number
PDUs (SNPs) carry authentication information. After receiving the packets, the remote RB
authenticate them and discard those that fail the authentication.
RBs in the same area must share the same area authentication mode and password so that TRILL
packets can be properly flooded. Whether packets pass the authentication does not affect the
establishment of neighbor relationships.
Procedure
Step 1 Run:
system-view
21
Step 2 Run:
trill
Step 3 Run:
area-authentication-mode { {simple | md5 | hmac-sha256 key-id key-id } { [ cipher ]
password-key | plain password } | keychain keychain-name } [ snp-packet
{ authentication-avoid | send-only } | all-send-only ]
The authentication mode is configured.
Specify the parameters based on the following descriptions:
l If you want RBs to encapsulate the authentication information into LSPs and SNPs before
sending them, and authenticate received LSPs and SNPs and discard packets that fail the
authentication, do not specify snp-packet or all-send-only.
l If you want RBs to encapsulate authentication information only into LSPs before sending
them and authenticate only received LSPs, specify snp-packet authentication-avoid.
sending them and authenticate received LSPs only, specify snp-packet send-only.
sending them but not to perform authentication, specify all-send-only.
Step 4 Run:
commit
----End
1.6.2 Configuring TRILL Interface Authentication
Context
In TRILL interface authentication, Hello packets carry authentication information configured
on the interface of the local RB. After receiving the packets, the remote RB authenticate them
and discard those that fail the authentication.
If TRILL interface authentication is configured on both ends, they must share the same
authentication mode and password so that neighbor relationships can be established between
them.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
22
trill authentication-mode { { simple | md5 | hmac-sha256 key-id key-id }
{ [ cipher ] password-key | plain password } | keychain keychain-name } [ send-
only ]
The authentication mode and password are configured on the interface.
Specify the parameters based on the following descriptions:
l If you want a TRILL interface to encapsulate authentication information into Hello packets
before sending them but not to authenticate received Hello packets, specify send-only.
l If you want a TRILL interface to encapsulate authentication information into Hello packets
before sending them and also authenticate received Hello packets, do not specify send-
only. In addition, configure the same authentication information for all TRILL interfaces
within the same VLAN to ensure proper communication.
Step 4 Run:
commit
----End
Procedure
Step 1 Run the display trill lsdb [ verbose ] command to check TRILL LSDB information.
----End
1.7 Maintaining TRILL
Resetting Transparent Interconnection of Lots of Links (TRILL) helps diagnose network faults.
1.7.1 Resetting TRILL
Context
Resetting TRILL clears all TRILL data and tears down neighbor relationships.
CAUTION
Resetting TRILL may interrupt services. Therefore, exercise caution when running the
command.
Procedure
l Run the reset trill all command to reset TRILL.
----End
23
1.8 Configuration Examples
This section provides several TRILL configuration examples. The configuration examples
include networking requirements, precautions, the configuration roadmap, and the configuration
procedure.
1.8.1 Example for Configuring Basic TRILL Functions
Networking Requirements
Data centers require increasingly higher transmission reliability on networks that have a large
number of servers. TRILL, with easy deployment, highly-efficient forwarding, high-speed
convergence, and loop prevention, provides a solution to data centers. After TRILL is
configured, users can communicate with servers through devices on Layer 2 networks.
On large networks, there may be multiple valid routes to the same destination. According to the
Shortest Path First (SPF) algorithm, however, only the route with the smallest cost is selected
as the optimal route to transmit packets. This implementation may result in unbalanced traffic
on different routes. To address this problem, configure the number of equal-cost routes to
implement load balancing.
As shown in Figure 1-2, the five TRILL-capable RBs belong to the same VLAN. A TRILL
network is used to implement communication between servers, and between servers and the
Layer 3 network. RBs on the TRILL network use the SPF algorithm to generate the unicast and
multicast forwarding tables and transmit traffic based on the forwarding tables. By default, equal-
cost routes (if any) load-balance traffic.
Figure 1-2 Networking with basic TRILL functions
RB1
RB2
Server
NetWork
Server
10GE3
RB3
RB4
RB5
10GE1
10GE2
10GE1 10GE1
10GE1
10GE1
10GE2
...
10GE2
10GE3
10GE3
10GE3

24
Configuration Roadmap
The configuration roadmap is as follows:
1. Enable TRILL globally on each RB, configure a network entity title (NET) and nickname
for each RB, and configure a Carrier VLAN and a CE VLAN.
2. Enable TRILL on interfaces that connect the RBs.
3. Check the TRILL database and unicast routing table of each RB.
4. Disable load balancing from RB1 and check its unicast routing table.
5. Enable load balancing on RB1 and check its unicast routing table.
Procedure
Step 1 Enable TRILL on each RB, configure the Carrier VLAN with ID 10, a NET and nickname for
each RB, and configure the CE VLAN with ID 100 for RB1 and RB3.
# Configure RB1.
<HUAWEI> system-view
[~HUAWEI] sysname RB1
[~HUAWEI] commit
[~RB1] vlan 100
[~RB1-vlan100] commit
[~RB1-vlan100] quit
[~RB1] trill
[~RB1-trill] carrier-vlan 10
[~RB1-trill] ce-vlan 100
[~RB1-trill] network-entity 00.0000.0000.1111.00
[~RB1-trill] nickname 100
[~RB1-trill] commit
[~RB1-trill] quit
# Configure RB2.
[~HUAWEI] commit
[~RB2] vlan 100
[~RB2-vlan100] quit
[~RB2] trill
[~RB2-trill] commit
[~RB2-trill] quit
# Configure RB3.
[~HUAWEI] commit
[~RB3] vlan 100
[~RB3-vlan100] quit
[~RB3] trill
[~RB3-trill] commit
[~RB3-trill] quit
# Configure RB4.
25
[~HUAWEI] commit
[~RB4] trill
[~RB4-trill] commit
[~RB4-trill] quit
# Configure RB5.
[~HUAWEI] commit
[~RB5] trill
[~RB5-trill] commit
[~RB5-trill] quit
Step 2 Configure TRILL functions for each interface.
# Enable TRILL on RB1 interfaces.
[~RB1] interface 10ge 1/0/1
[~RB1-10GE1/0/1] undo shutdown
[~RB1-10GE1/0/1] port link-type hybrid
[~RB1-10GE1/0/1] trill enable
[~RB1-10GE1/0/1] quit
[~RB1-10GE2/0/1] trill enable
[~RB1-10GE2/0/1] quit
[~RB1-10GE3/0/1] trill enable port-mode access
[~RB1-10GE3/0/1] port hybrid pvid vlan 100
[~RB1-10GE3/0/1] port hybrid untagged vlan 100
[~RB1-10GE3/0/1] commit
[~RB1-10GE3/0/1] quit
The configuration on other RBs is similar to that on RB1. For details about the configuration,
see Configuration Files.
Step 3 Check the TRILL database and unicast routing table of each RB.
# Run the display trill interface command on RB1 to check information about its TRILL-
enabled interfaces.
[~RB1] display trill interface
Interface information for TRILL
-------------------------------
Total Interface(s): 3
Interface ID State MTU Type DRB-State DVLAN
-----------------------------------------------------------------
10GE1/0/1 001 UP 1497 L1 Non-DRB 10
10GE2/0/1 002 UP 1497 L1 Non-DRB 10
10GE3/0/1 003 UP 1497 L1 Non-DRB 10
# Run the display trill nickname command on RB1 to check the nickname of each RB.
[~RB1] display trill nickname
Nickname information for TRILL
------------------------------
26
*-Local Nickname, A-Advertised, S-Suppressed / S-Static, D-Dynamic
Total Nickname(s): 5
Nickname Source ID State Priority RootPri
---------------------------------------------------
* 100 0000.0000.1111 A/C 192 32768
200 0000.0000.2222 A/C 192 32768
300 0000.0000.3333 A/C 192 32768
400 0000.0000.4444 A/C 192 32768
500 0000.0000.5555 A/C 192 32768
# Run the display trill route command on RB1 to check its unicast routing table.
[~RB1] display trill route
TRILL Unicast Routing Table
---------------------------
Flags: D-Downloaded
Total Route(s): 4
Nickname Cost Flag OutInterface OutVlan NextHop Hop
-------------------------------------------------------------------
200 400000 D 10GE1/0/1 10 3609-b654-1220 2
10GE2/0/1 10 3609-b655-1220 2
300 400000 D 10GE2/0/1 10 3609-b665-1220 2
400 200000 D 10GE1/0/1 10 3609-b664-1220 1
500 200000 D 10GE2/0/1 10 3609-b665-1220 1
Step 4 Disable load balancing from RB1 by setting the number of equal-cost routes for load balancing
to 1.
[~RB1-trill] maximum load-balance 1
[~RB1-trill] commit
# Check the unicast routing table of RB1.
[~RB1-trill] display trill route
---------------------------
Flags: D-Downloaded To Fib
Total Route(s): 4
-------------------------------------------------------------------
200 400000 D 10GE1/0/1 10 3609-b654-1220 2
300 400000 D 10GE2/0/1 10 3609-b665-1220 2
400 200000 D 10GE1/0/1 10 3609-b664-1220 1
500 200000 D 10GE2/0/1 10 3609-b665-1220 1
The preceding unicast routing table shows that the outbound interface of the route to RB2 is
10GE 1/0/0. After the maximum number of equal-cost routes for load balancing is configured
to 1, the route with the next hop RB4 is selected as the optimal route because the index of
10GE1/0/0 is smaller than that of 10GE2/0/0.
Step 5 Restore the default number of equal-cost routes for load balancing on RB1.
[~RB1-trill] undo maximum load-balance
[~RB1-trill] commit
# Check the unicast routing table of RB1.
[~RB1-trill] display trill route
---------------------------
Flags: D-Downloaded To Fib
Total Route(s): 4
27
-------------------------------------------------------------------
200 400000 D 10GE1/0/1 10 3609-b654-1220 2
10GE2/0/1 10 3609-b655-1220 2
300 400000 D 10GE2/0/1 10 3609-b665-1220 2
400 200000 D 10GE1/0/1 10 3609-b664-1220 1
500 200000 D 10GE2/0/1 10 3609-b665-1220 1
The preceding unicast routing table shows the two equal-cost routes destined for RB2 with the
next hop RB4 (3609-b654-1220) and RB5 (3609-b655-1220). By default, the maximum number
of equal-cost routes for load balancing is 16.
----End
Configuration Files
l Configuration file of RB1
#
sysname RB1
#
vlan batch 100
#
trill
network-entity 00.0000.0000.1111.00
nickname 100
carrier-vlan 10
ce-vlan 100
#
interface 10GE1/0/1
port link-type hybrid
trill enable
#
interface 10GE2/0/1
trill enable
#
interface 10GE3/0/1
port hybrid pvid vlan 100
port hybrid untagged vlan 100
trill enable port-mode access
#
return
#
sysname RB2
#
vlan batch 100
#
trill
network-entity 00.0000.0000.2222.00
nickname 200
carrier-vlan 10
ce-vlan 100
#
interface 10GE1/0/1
trill enable
#
interface 10GE2/0/1
trill enable
#
interface 10GE3/0/1
28
#
return
#
sysname RB3
#
vlan batch 100
#
trill
network-entity 00.0000.0000.3333.00
nickname 300
carrier-vlan 10
ce-vlan 100
#
interface 10GE1/0/1
trill enable
#
interface 10GE3/0/1
#
return
#
sysname RB4
#
trill
network-entity 00.0000.0000.4444.00
nickname 400
carrier-vlan 10
#
interface 10GE1/0/1
trill enable
#
interface 10GE2/0/1
trill enable
#
return
#
sysname RB4
#
trill
network-entity 00.0000.0000.5555.00
nickname 500
carrier-vlan 10
#
interface 10GE1/0/1
trill enable
#
interface 10GE2/0/1
trill enable
#
interface 10GE3/0/1
trill enable
#
29
return
30

CloudEngine 6800&5800 V100R001C00 Configuration Guide - TRILL 04 PDF

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CloudEngine 6800&5800 V100R001C00 Configuration Guide - TRILL 04 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

CloudEngine 6800&5800 Series Switches

Das könnte Ihnen auch gefallen