Hewlett Packard Enterprise 5920, 5900 Configuration Manual
HPE 5920 & 5900 Switch Series
TRILL Configuration Guide
P
Software
Document version: 6W100-20171115
art number: 5200-4558
version: Release 243x
© Copyright 2017 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty stat ement s ac c om pa ny i ng such
products and services. Nothing herein should be construed as constit ut i ng an add it i onal warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial err o rs or omis s ions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and T echnical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Ent erpr is e we bsite. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside lo go ar e trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are either registered trademarks or t rade marks of Microsoft Corporation in the
United States and/or other countries.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Contents
Configuring TRILL ··························································································· 1
Overview ···························································································································································· 1
Basic concepts ··········································································································································· 1
TRILL frame formats ·································································································································· 1
How TRILL works ······································································································································· 2
TRILL forwarding mechanisms ·················································································································· 3
Ping TRILL and tracert TRILL ···················································································································· 5
Protocols and standards ···························································································································· 7
Configuration restrictions and guidelines ··········································································································· 7
TRILL configuration task list ······························································································································· 8
Enabling TRILL ·················································································································································· 9
Configuration restrictions and guidelines ··································································································· 9
Configuration procedure ··························································································································· 10
Configuring the system ID and nickname for an RB ························································································ 10
Configuring the link type of a TRILL port ········································································································· 11
Configuration procedure ··························································································································· 11
Configuring the DRB priority of a TRILL port ··································································································· 11
Setting the link cost for a TRILL port ················································································································ 11
Configuring announcing VLANs and the designated VLAN ············································································· 12
Configuring TRILL timers ································································································································· 13
Configuring TRILL LSP parameters and features ···························································································· 14
Setting TRILL LSP parameters ················································································································ 14
Enabling TRILL LSP fast advertisement ·································································································· 15
Enabling TRILL pseudonode bypass ······································································································· 15
Setting the SPF algorithm parameters ············································································································· 16
Configuring TRILL distribution trees ················································································································ 16
Setting basic distribution tree parameters ································································································ 16
Enabling TRILL distribution tree multithread calculation ·········································································· 17
Enabling load balancing over TRILL distribution trees ············································································· 17
Configuring TRILL ECMP routes ····················································································································· 18
Enabling incremental flush for TRILL multicast routing entries ········································································ 18
Enabling logging of TRILL neighbor changes ·································································································· 19
Configuring SNMP for TRILL ··························································································································· 19
Enabling TRILL to forward traffic from EVB S-channels ·················································································· 20
Configuring TRILL GR ····································································································································· 20
Associating a TRILL port with a track entry ····································································································· 21
Using ping TRILL and tracert TRILL to test network connectivity ···································································· 21
Displaying and maintaining TRILL ··················································································································· 22
TRILL configuration example ··························································································································· 22
Network requirements ······························································································································ 22
Configuration procedure ··························································································································· 23
Verifying the configuration ························································································································ 25
Document conventions and icons ································································· 27
Conventions ····················································································································································· 27
Network topology icons ···································································································································· 28
Support and other resources ········································································ 29
Accessing Hewlett Packard Enterprise Support ······························································································ 29
Accessing updates ··········································································································································· 29
Websites ·················································································································································· 30
Customer self repair ································································································································· 30
Remote support ········································································································································ 30
Documentation feedback ························································································································· 30
Index ············································································································· 32
i
Configuring TRILL
•
•
•
•
•
•
•
•
TRansparent Interconnection of Lots of Links (TRILL) uses IS-IS to provide transparent Layer 2
forwarding.
Overview
TRILL combines the simplicity and flexibility of Layer 2 switching with the stability, scalability, and
rapid convergence capability of Layer 3 routing. All these advantages make TRI LL very suitable for
large flat Layer 2 networks in data centers.
Basic concepts
RBridge—Routing bridge (RB) that runs TRILL. RBs are classified into ingress RBs, transit
RBs, and egress RBs, depending on their positions in the TRILL network. A frame enters the
TRILL network through an ingress RB, travels along transit RBs, and leaves the TRILL network
through an egress RB, as shown in
TRILL network—A Layer 2 network comprised of RBs, as shown in Figure 3.
System ID—Unique identifier of an RB in the TRILL network. The system ID is 6-byte.
Nickname—Address of an RB in the TRILL network. The nickname is 2-byte.
Link State Database—The LSDB contains all link state information in the TRILL network.
Link State Protocol Data Unit—An LSP describes local link state information and is
advertised between neighbor devices.
Designated Routing Bridge (DRB)—Similar to the designated IS (DIS) in IS-IS, a DRB exists
in a broadcast network. It helps simplify network topology, and assigns AVFs and appointed
ports for the VLANs on each RB in the broadcast network.
Appointed VLAN-x Forwarder (AVF) and appointed port—T o avoid loops, TRILL requires all
traffic of a VLAN on a broadcast network to enter and leave the TRILL network through the
same port of an RB. The RB is the VLAN's AVF, and the port is the VLAN's appointed port.
Figure 2.
For more information about LSDB, LSPDU, and DIS, see Layer 3—IP Routing Configuration Guide.
TRILL frame formats
TRILL frames include protocol frames and data frames.
TRILL protocol frames include TRI LL Hello, LSP, CSNP, PSNP, MTU-probe, and MTU-ack. These
protocol frames use 802.1Q encapsulation and have a fixed destination multicast address
0180-C200-0041.
TRILL data frames have a specific format, as shown in Figure 1. A TRILL header and an outer
Ethernet header are added to the original Ethernet frame.
1
Figure 1 TRILL data frame format
Field
Description
Options
Outer Destination MAC Address
0 32
Outer Source MAC Address
Ethertype = 802.1Q
Outer VLAN Tag Information
Ethertype = TRILL
New FCS
16
V
Inner Destination MAC Address
Inner Source MAC Address
Ethertype = 802.1Q Inner VLAN Tag Information
Outer
Ethernet
header
Egress RB Nickname Ingress RB Nickname
R M Op-Length
Hop Count
TRILL
header
Inner
Ethernet
header
Original Ethernet Payload
Ethertype of Original Ethernet Payload
Payload
Table 1 describes the fields in the TRILL header.
Table 1 TRILL header fields
Ethertype The Ethertype is fixed to 0x22F3.
V
R
Version number, which is 0. When an RB receives a TRILL frame, it checks the V
field and drops the frame if the V field is not 0.
Reserved for future extension. An ingress RB sets the R field to 0 when adding a
TRILL header. Transit RBs and egress RBs ignore the field.
Multidestination attribute:
M
• 0—Known unicast frame.
• 1—Multidestination frame (multicast, broadcast, or unknown unicast frame).
Op-Length Length of the Options field. 0 indicates that the Options field does not exist.
Hop Count
Hop count, which is used to avoid loops. An RB drops a TRILL frame whose hop
count is decremented to 0.
Egress RB Nickname Nickname of the egress RB.
Ingress RB Nickname Nickname of the ingress RB.
Options Options field. This field exists when the Op-Length field is non-zero.
How TRILL works
TRILL establishes and maintains adjacencies between RBs by periodically advertising Hello frames,
distributes LSPs among RB neighbors, and generates an LSDB for all RBs in the network. Based on
the LSDB, each RB uses the SPF algorithm to calculate forwarding ent ri es destined to other RBs.
2
TRILL forwarding mechanisms
•
•
VLAN 10 VLAN 200
VLAN 300
VLAN
10
Ingress RB
RB 1
S1 S2
Ethernet frame TRILL frame TRILL frame
Ethernet frame
Egress RB
RB 3
Transit
RB
RB 2
Ingress RB =
RB 1
Outer VLAN
= 200
Egress RB = RB 3
Outer S-MAC
= RB 1
Outer D-MAC = RB 2
Payload
Inner VLAN = 10
Inner S-MAC = S1
Inner D
-MAC =
S2
Ingress RB = RB 1
Outer VLAN =
300
Egress RB = RB
3
Outer S-MAC = RB 2
Outer D-
MAC = RB 3
Payload
Inner VLAN = 10
Inner S-
MAC = S
1
Inner D-MAC = S
2
Payload
Inner VLAN = 10
Inner S-MAC = S1
Inner D-MAC = S2
Payload
Inner VLAN
= 10
Inner S-MAC = S1
Inner D-MAC
= S2
Unicast frame
Different types of frames are forwarded by using different forwarding mechanisms. The following
sections describe these mechanisms.
Unicast frame forwarding mechanism
As shown in Figure 2, a unicast frame is forwarded as follows:
1. When a unicast frame enters the TRILL network, the ingress RB encapsulat e s the orig in al
Ethernet frame with the following headers:
2. A TRILL header (similar to an IP header).
3. An outer Ethernet header (similar to the Ethernet header of a regular Ethernet fra me).
4. RBs forward the frame hop by hop according to the egress RB nickname in the TRILL header in
the same way routers forward IP packets. Each hop replaces the outer Ethernet header with an
appropriate outer Ethernet header, and decrements the hop count in the TRILL header.
5. Upon receiving the TRILL frame, the egress RB de-encapsulates it to obt a in the orig inal
Ethernet frame, and sends the frame to the target device.
Figure 2 Unicast frame forwarding flow
The outer Ethernet header enables traditional Ethernet switches to forward T R I L L f rames and
connect RBs.
Multidestination frame forwarding mechanism
In a TRILL network, RBs perform the following tasks:
Compute a TRILL distribution tree for each VLAN based on the LSDB.
Guide the forwarding of multidestination frames in each VLAN b y using its TRILL distribution
tree.
As shown in Figure 3, when a multicast frame from VLAN 10 enters the TRILL network, RB 1, which
is an ingress RB, encapsulates the multicast frame into a TRILL frame. In the frame, the egress RB is
RB 2, the root bridge of the TRILL distribution tree for VLAN 10, and the destination MAC address is
multicast address 0180-C200-0040. When the frame arrives at the root bridge, it is distributed
throughout the TRILL distribution tree. Then, the TRILL frame is de-encapsulated by RB 3 and sent
3
to the destination station S2. Because the network segment where RB 4 resides does not have a
VLAN 10
VLAN 10
S1 S2
VLAN 200
TRILL network
RB 1
Ethernet frame
Payload
Inner VLAN = 10
Inner S-MAC = S1
Inner D-MAC = Multi
TRILL frame
Ingress RB = RB 1
Outer VLAN = 200
Egress RB = RB 2
Outer S-MAC = RB 1
Outer D-MAC = All RBs
Payload
Inner VLAN = 10
Inner S-MAC = S1
Inner D-MAC = Multi
TRILL frame
Ingress RB = RB 1
Outer VLAN = 200
Egress RB = RB 2
Outer S-MAC = RB 2
Outer D-MAC = All RBs
Payload
Inner VLAN = 10
Inner S-MAC = S1
Inner D-MAC = Multi
RB 4
RB 3
Ethernet frame
Payload
Inner VLAN = 10
Inner S-MAC = S1
Inner D-MAC = Multi
RB 2
Multicast frame
Distribution tree
of VLAN 10
Root bridge of
distribution tree
Leaf of
distribution tree
receiver of this frame, RB 4 drops the frame.
Figure 3 Multicast frame forwarding flow
TRILL selects distribution trees for forwarding multidestination frames based on the VLANs to which
the frames belong. Because the topologies of TRILL distribution trees are different, traffic can be
load shared. However, equal-cost links are not used for load sharing.
When N equal-cost links exist in the network, each TRILL distribution tree selects the link with the
largest pseudonode ID for forwarding packets. As shown in Figure 4, two equal-cost links exist
between RB 1 and RB 3. Assume the link directly connecting RB 1 to RB 3 has the largest
pseudonode ID. Both the TRILL distribution tree rooted at RB 3 and the TRILL distribution tree rooted
at RB 4 select the link. For more information about pseudonode IDs, see Layer 3—IP Routing
Configuration Guide.
4
Figure 4 Multicast ECMP
•
•
Cost = 3
Cost = 2
Cost = 1
RB 1
RB 2 RB 3 RB 4
TRILL distribution trees support Equal Cost Multiple Path (ECMP), also known as multicast ECMP.
When multicast ECMP is enabled, TRILL assigns equal-cost links to multiple TRILL distributions
trees. This improves the load sharing performance.
When N equal-cost links exist in the network, each TRILL distribution tree selects an equal-cost link
for forwarding packets through J mod N in root bridge priority order. J is the priority sequence number
of a TRILL distribution tree and starts from 0.
As shown in Figure 4:
The link directly connecting RB 1 to RB 3 is assigned to the TRILL distribution tree rooted at RB
3.
The link RB 1-RB 2-RB 3 is assigned to the TRILL distribution tree rooted at RB 4.
TRILL distribution trees support fast root switching. When an RB detects that the root of a distribution
tree is unreachable, the RB deletes the LSP of the root from its LSDB. This triggers recalculation of
all distribution trees in the TRILL network. Multidestination traffic is switched to new distribution trees.
Ping TRILL and tracert TRILL
You can use ping TRILL and tracert TRILL to test TRILL network connectivity when network failure
occurs or new RBs are added to the network.
Ping TRILL and tracert TRILL are implemented through the TRILL Operation, Administration, and
Maintenance (OAM) protocol.
Ping TRILL
Use ping TRILL to determine if an RB is reachable.
As shown in Figure 5, the source RB sends OA M echo requests to ping the destination RB. Upo n
receiving the requests, the destination RB responds to the source RB with OAM echo replies. The
source RB outputs statistics about the ping TRILL operation, including the number of sent echo
requests, the number of received echo replies, and the round-trip time. Y ou can measure the network
performance by analyzing the statistics.
5
Figure 5 Ping TRILL packet forwarding
RB 1 RB 2 RB 3
ECHO-REQUEST
ECHO-REQUEST
ECHO-REPLY
ECHO-REPLY
Ingress RB = RB 1
Egress RB = RB 3
Hop Count = 63
Sequence number = 1
Ingress RB = RB 1
Egress RB = RB 3
Hop Count = 62
Sequence number = 1
Ingress RB = RB 3
Egress RB = RB 1
Hop Count = 63
Sequence number = 1
Ingress RB = RB 3
Egress RB = RB 1
Hop Count = 62
Sequence number = 1
Tracert TRILL
Tracert TRILL enables retrieval of the nicknames of RBs in the path to a destination RB. In the event
of network failure, use tracert TRILL to test network connectivity and identify failed nodes.
Tracert TRILL operates as shown in Figure 6.
1. RB 1 sends RB 3 an OAM echo request with a hop count value of 0.
2. The first hop RB 2 responds by sending a hop count error notification to the source RB because
the hop count of the request is 0. The notification uses the nickname of RB 2 as the ingress RB.
In this way, RB 1 can get the nickname of the first hop RB.
3. RB 1 sends RB 3 an OAM echo request with a hop count value of 1.
4. RB 2 forwards the request to RB 3 according to the TRILL unicast routing table and decrements
the hop count value by 1.
5. The second hop RB 3 responds to the source RB with a hop count error notificat i on . The
notification uses the nickname of RB 3 as the ingress RB.
6. RB 2 forwards the hop count error notification to RB 1. RB 1 gets the nickname of the second
hop RB 3.
6
Figure 6 Tracert TRILL packet forwarding
•
•
•
•
•
•
•
RB 1 RB 2 RB 3
ECHO-REQUEST
Ingress RB = RB 1
Egress RB = RB 3
Hop Count = 0
Hop Count = 0 error notification
Ingress RB = RB 2
Egress RB = RB 1
Hop Count = Default
ECHO-REQUEST
Ingress RB = RB 1
Egress RB = RB 3
Hop Count = 1
Hop Count = 0 error notification
Ingress RB = RB 3
Egress RB = RB 1
Hop Count = Default-1
ECHO-REQUEST
Ingress RB = RB 1
Egress RB = RB 3
Hop Count = 0
Hop Count = 0 error notification
Ingress RB = RB 3
Egress RB = RB 1
Hop Count = Default
Protocols and standards
Configuration restrictions and guidelines
RFC 6325, Routing Bridges (RBridges): Base Protocol Specific a t ion
RFC 6326, Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS
RFC 6327, Routing Bridges (RBridges): Adjacency
RFC 1195, Use of OSI IS-IS for Routing in TCP/IP and Dual Environments
RFC 7978, Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Header
Extension
RFC 6905, Requirements for Operations, Administration, and Maintenance (OAM) in
Transparent Interconnection of Lots of Links (TRI LL)
When you configure TRILL, follow these restrictions and guidelines:
Configuration in Layer 2 Ethernet interface view takes effect only on the current port.
Configuration in Layer 2 aggregate interface view takes effect on the current interf ac e and its
member ports. Configuration on the member port of an aggregate interf ac e t ak es effect after
the member port leaves the aggregation group.
7
•
•
•
•
•
•
•
Tasks at a glance
To connect a spanning tree network to a TRILL network, make sure the following requirements
are met:
The spanning tree protocol is disabled on TRILL ports.
An edge port is used to connect the spanning tree network to the TRILL network. The edge
port can transit to the forwarding state before DRB election is fini shed. This prevents
multiple DRBs from being elected.
For more information about spanning tree protocols, see Layer 2—L AN Switching
Configuration Guide.
As a best practice, do not enable loop detection on TRILL ports, because TRILL avoids loops.
For more information about loopback detection, see Layer 2—LAN Switching Configuration
Guide.
If IRF is used, retain the IRF bridge MAC address permanently. Otherwise, traffic interruption
might occur after an IRF split. For more information about IRF confi gur ation, see IRF
Configuration Guide.
Do not configure the TPID for VLAN tags on RBs. For more information about TPIDs, see Layer
2—LAN Switching Configuration Guide.
To avoid loops, do not connect multiple TRILL ports of an RB to a broadcast network, because
TRILL ports cannot detect each other when they are on a broadcast network. If there are
multiple TRILL ports, they might be elected as the appointed ports of a VLAN at the same time
and result in loops.
For the TRILL network to forward Layer 3 multidestination traffic correctly, make sure the
following requirements are met:
The IGMP/MLD snooping version must be the same on all RBs.
IGMP or MLD must be enabled on the access-facing VLAN interfaces on gateway RBs to
prevent topology changes from interrupting traffic.
Enabling PIM-DM or IPv6 PIM-DM on core layer and distribution layer devices might cause
multicast traffic duplication. As a best practice, use other Layer 3 multicast protocols.
TRILL configuration task list
(Required.) Enabling TRILL
(Required.) Configuring the system ID and nickname for an RB
(Optional.) Configuring the link type of a TRILL port
(Optional.) Configuring the DRB priority of a TRILL port
(Optional.) Setting the link cost for a TRILL port
(Optional.) Configuring announcing VLANs and the designated VLAN
(Optional.) Configuring TRILL timers
(Optional.) Configuring TRILL LSP parameters and features
(Optional.) Setting the SPF algorithm parameters
(Optional.) Configuring TRILL distribution trees
(Optional.) Configuring TRILL ECMP routes
(Optional.) Enabling incremental flush for TRILL multicast routing entries
(Optional.) Enabling logging of TRILL neighbor changes
(Optional.) Configuring SNMP for TRILL
8
Tasks at a glance
(Optional.) Enabling TRILL to forward traffic from EVB S-channels
•
•
•
•
Traditional Ethernet
switch
RB 1
RB 2 RB 3
TRILL enabled port
(Optional.) Configuring TRILL GR
(Optional.) Associating a TRILL port with a track entry
(Optional.) Using ping TRILL and tracert TRILL to test network connectivity
Enabling TRILL
After you enable TRILL on a port, TRILL can operate correctly by using default settings. A port with
TRILL enabled is called a TRILL port.
Configuration restrictions and guidelines
When you enable TRILL, follow these guidelines:
To enable TRILL on a port, first enable TRILL globally.
Enable or disable TRILL on all ports in a VLAN, so that the ports in a VLAN have the same
TRILL status (enabled or disabled).
Do not enable both TRILL and EVB on a port. If the trill evb-support command is not executed
on an EVB-enabled port, make sure the allowed VLANs of the port do not overlap with those of
a TRILL-enabled port. For more information about EVB, see EVB Conf iguration Guide.
When you set up a TRILL network, avoid the case that multiple TRILL neighbors are
established for one RB port. When you plan a network, avoid the networ k s sh own in
and Figure 8.
Figure 7 shows a typical network where two TRILL neighbors are established for the same
port of an RB.
In Figure 8, because TRILL is not enabled on the port connecting RB 2 to RB 3, the port will
transparently transmit the TRILL Hello frames from RB 3. As a result, two TRILL neighbors
are established for the port connecting RB 1 to RB 2.
Figure 7
Figure 7 Two TRILL neighbors are established for a port (1)
9
Loading...