HP 5900, 5920 Configuration Manual
広告
広告
HP 5920 & 5900 Switch Series
TRILL
Configuration Guide
Part number: 5998-6656
Software version: Release 2416
Document version: 6W100-20150130
Legal and notice information
© Copyright 2015 Hewlett-Packard Development Company, L.P.
No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Contents
i
ii
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 TRILL 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 —To 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.
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 TRILL 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.
header are added to the original Ethernet frame.
1
Figure 1 TRILL data frame format
describes the fields in the TRILL header.
Table 1 TRILL header fields
Field Description
Ethertype The Ethertype is fixed to TRILL.
V
R
M
Op-Length
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:
• 0 —Known unicast frame.
• 1 —Multidestination frame (multicast, broadcast, or unknown unicast frame).
Length of the Options field. 0 indicates that the Options field does not exist.
Hop Count
Egress RB Nickname
Ingress RB Nickname
Options
Hop count, which is used to avoid loops. An RB drops a TRILL frame whose hop count is decremented to 0.
Nickname of the egress RB.
Nickname of the ingress RB.
Options field. This field exists when the Op-Length field is non-zero.
2
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 entries destined to other RBs.
TRILL forwarding mechanisms
TRILL uses different mechanisms to forward Layer 2 and Layer 3 traffic. The following sections describe these mechanisms.
Layer 2 forwarding mechanisms
TRILL forwards the traffic within a VLAN by using the following mechanisms:
• Unicast frame forwarding mechanism.
As shown in Figure 2 , a unicast frame is forwarded as follows:
a.
When a unicast frame enters the TRILL network, the ingress RB encapsulates the original
Ethernet frame with the following headers:
− A TRILL header (similar to an IP header).
− An outer Ethernet header (similar to the Ethernet header of a regular Ethernet frame). b.
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. c.
Upon receiving the TRILL frame, the egress RB de-encapsulates it to obtain the original Ethernet frame, and sends the frame to the target device.
Figure 2 Layer 2 unicast frame forwarding flow
S1
Ingress RB
RB 1
Transit RB
RB 2
Egress RB
RB 3
S2
VLAN 10 VLAN 200 VLAN 300 VLAN 10
Inner D-MAC = S2
Inner S-MAC = S1
Inner VLAN = 10
Payload
Ethernet frame
Unicast frame
Outer D-MAC = RB 2
Outer S-MAC = RB 1
Outer VLAN = 200
Egress RB = RB 3
Ingress RB = RB 1
Inner D-MAC = S2
Inner S-MAC = S1
Inner VLAN = 10
Payload
TRILL frame
Outer D-MAC = RB 3
Outer S-MAC = RB 2
Outer VLAN = 300
Egress RB = RB 3
Ingress RB = RB 1
Inner D-MAC = S2
Inner S-MAC = S1
Inner VLAN = 10
Payload
TRILL frame
Inner D-MAC = S2
Inner S-MAC = S1
Inner VLAN = 10
Payload
Ethernet frame
3
The outer Ethernet header enables traditional Ethernet switches to forward TRILL frames 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 by 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. 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 to the destination station S2. Because the network segment where RB 4 resides does not have a receiver of this frame, RB 4 drops the frame.
Figure 3 Layer 2 multicast frame forwarding flow
RB 4
VLAN 200
TRILL network
S1
RB 1 RB 3
S2
VLAN 10 VLAN 10
RB 2
Inner D-MAC = Multi
Inner S-MAC = S1
Inner VLAN = 10
Payload
Ethernet frame
Outer D-MAC = All RBs
Outer S-MAC = RB 1
Outer VLAN = 200
Egress RB = RB 2
Ingress RB = RB 1
Inner D-MAC = Multi
Inner S-MAC = S1
Inner VLAN = 10
Payload
TRILL frame
Outer D-MAC = All RBs
Outer S-MAC = RB 2
Outer VLAN = 200
Egress RB = RB 2
Ingress RB = RB 1
Inner D-MAC = Multi
Inner S-MAC = S1
Inner VLAN = 10
Payload
TRILL frame
Inner D-MAC = Multi
Inner S-MAC = S1
Inner VLAN = 10
Payload
Ethernet frame
Multicast frame
Distribution tree of VLAN 10
Root bridge of distribution tree
Leaf of distribution tree
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
, 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
4
at RB 4 select the link. For more information about pseudonode IDs, see Layer 3—IP Routing
Configuration Guide .
Figure 4 Multicast ECMP
RB 1
Co st =
3
Cost = 2
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.
{
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.
Layer 3 forwarding mechanisms
, distribution layer devices RB 1 and RB 2 are gateways of a data center network.
Because of hardware limitations, RBs cannot perform Layer 3 forwarding before TRILL encapsulation or after removing TRILL encapsulation.
To support Layer 3 forwarding, TRILL virtualizes the gateway RBs into a virtual router (VR). The VR provides gateway services at a virtual IP address.
5
Figure 5 TRILL Layer 3 forwarding
A TRILL VR contains multiple member RBs that are configured with the same virtual IP address. All member RBs participate in Layer 3 forwarding. A master RB responds to ARP or ND requests. The master
RB is elected by using the following rules:
• The member RB with the highest priority is elected as the master RB. The master election priority is
64 by default, and it is not configurable.
• If member RBs have the same priority, the member RB with the highest system ID is elected.
TRILL uses the following mechanisms to forward Layer 3 traffic:
• Unicast traffic forwarding mechanism — Access RBs forward original unicast frames to the TRILL VR.
Member RBs of the VR then perform Layer 3 forwarding for the frames.
• Multidestination traffic forwarding mechanism — To forward multidestination traffic, you must enable IGMP/MLD snooping and dropping unknown multicast data on all RBs. In this way, router ports and member ports in Layer 2 multicast forwarding entries are appointed along TRILL distribution trees. Access RBs forward original multidestination frames to the TRILL VR through TRILL distribution trees. Member RBs of the VR then perform Layer 3 forwarding for the frames.
Each VLAN supports only one TRILL distribution tree. If you configure multiple distribution trees for a VLAN, the distribution tree with the lowest root nickname takes effect.
Protocols and standards
• RFC 6325: Routing Bridges (RBridges): Base Protocol Specification
• 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
6
Configuration restrictions and guidelines
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 interface and its member ports.
Configuration on the member port of an aggregate interface takes effect after the member port leaves the aggregation group.
• To connect a spanning tree network to a TRILL network, make sure the following requirements are met:
{
The spanning tree protocol is disabled on the TRILL network.
{
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 finished. This prevents multiple DRBs from being elected.
For more information about spanning tree protocols, see Layer 2—LAN Switching Configuration
Guide .
• HP recommends not enabling 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 configuration, 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. HP recommends that you use other Layer 3 multicast protocols.
TRILL configuration task list
Tasks at a glance
(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.) Configuring the link cost for a TRILL port
(Optional.) Configuring announcing VLANs and the designated VLAN
(Optional.) Configuring TRILL timers
7
Tasks at a glance
(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.) Configuring a TRILL VR
(Optional.) Permitting a non-TRILL device to learn the MAC address of the TRILL VR
(Optional.) Enabling MAC address retaining on TRILL ports
(Optional.) Enabling logging of TRILL neighbor changes
(Optional.) Configuring SNMP for TRILL
(Optional.) Enabling TRILL to forward traffic from EVB S-channels
(Optional.) Configuring TRILL GR
(Optional.) Associating a TRILL port with a track entry
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 Configuration 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 networks shown in Figure 6
and
{
shows a typical network where two TRILL neighbors are established for the same port of an RB.
{
In Figure 7 , 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.
8
Figure 6 Two TRILL neighbors are established for a port (1)
RB 1
Traditional Ethernet switch
RB 2 RB 3
TRILL enabled port
Figure 7 Two TRILL neighbors are established for a port (2)
Configuration procedure
To enable TRILL:
1.
Enter system view.
2.
Enable TRILL globally and enter TRILL view. system-view trill
3.
Return to system view. quit
4.
Enter Layer 2 Ethernet or aggregate interface view.
5.
Enable TRILL on the port. interface trill interface-type interface-number enable
N/A
By default, TRILL is disabled globally.
N/A
N/A
By default, TRILL is disabled on a port.
Configuring the system ID and nickname for an RB
The system ID and nickname of an RB are identifiers of the RB in the TRILL network.
• System ID —Unique identifier of an RB in the TRILL network. The system ID can be automatically assigned or manually configured.
• Nickname —Address of an RB in the TRILL network. The address can be automatically assigned or manually configured. When multiple RBs in the TRILL network have the same nickname, the RB with the highest priority uses the nickname. When the RBs also have the same priority, the RB with the
9
highest system ID uses the nickname. The system automatically assigns new nicknames to the other
RBs.
The system resets the TRILL process when the RB's system ID changes.
To configure the system ID and nickname for the RB:
Step Command Remarks
1.
Enter system view. system-view N/A
2.
Enter TRILL view. trill N/A
3.
Configure the system
ID for the RB.
4.
Configure the nickname for the RB. system-id system-id nickname nickname [ priority priority ]
By default, the RB automatically generates a system ID based on its MAC address upon startup.
By default, TRILL automatically assigns nicknames to RBs, and the priority for a RB to hold a nickname is 64.
Configuring the link type of a TRILL port
The following link types are available for a TRILL port:
• Access —Access ports include access ports without the alone attribute and access ports with the alone attribute. Access ports with the alone attribute do not send or receive Hello frames and do not participate in DRB election or AVF negotiation. Access ports without the alone attribute can process only local data frames and Hello frames.
• Hybrid —A hybrid port combines the attributes of an access port and a trunk port, and can process local data frames and passing data frames.
• Trunk —A trunk port can process passing data frames and some of Layer 2 protocol frames (for example, LLDP frames), but it cannot process local data frames.
• VR —A VR port is a virtual router port that can forward the following traffic:
{
{
{
TRILL data frames.
Layer 3 unicast data traffic.
Layer 2 and Layer 3 multidestination data traffic.
Configuration restrictions and guidelines
• For the TRILL network to forward Layer 3 traffic, you must configure the link type as VR for TRILL ports that are connected to an RB.
• VR ports are used only on P2P links, and both ends of a P2P link must be VR ports.
• A VR port trunks all VLANs. HP recommends that you reduce the number of announcing VLANs on
VR ports to reduce Hello frames.
Configuration procedure
To configure the link type of a TRILL port:
10
Step Command Remarks
1.
Enter system view.
2.
Enter Layer 2 Ethernet or aggregate interface view. system-view interface interface-type interface-number
3.
Configure the link type of the TRILL port. trill link-type { access [ alone ] | hybrid | trunk | vr }
N/A
N/A
By default, the link type of a TRILL port is access without the alone attribute.
Configuring the DRB priority of a TRILL port
On a broadcast network, TRILL must elect a DRB. An RB with a higher DRB priority is preferred in DRB election. When two RBs have the same DRB priority, the RB with a higher MAC address takes precedence.
To configure the DRB priority of a TRILL port:
1.
Enter system view.
2.
Enter Layer 2 Ethernet or aggregate interface view.
3.
Configure the DRB priority of the TRILL port. system-view interface interface-type interface-number trill drb-priority priority
N/A
N/A
By default, the DRB priority of a TRILL port is
64.
Configuring the link cost for a TRILL port
The link cost of a TRILL port can be automatically calculated by the system or manually configured.
• A manually configured link cost takes precedence over a calculated link cost.
• If no configured link cost exists and automatic link cost calculation is enabled, the calculated link cost takes effect.
• If no configured link cost exists and automatic link cost calculation is disabled, the default link cost of 2000 is used.
The system automatically calculates the link cost of a TRILL port by using the following formula: link cost
= 20000000000000/interface baud rate.
To configure the link cost for a TRILL port:
1.
Enter system view.
2.
Enter TRILL view.
3.
Enable automatic link cost calculation for TRILL ports.
4.
Return to system view. system-view trill auto-cost enable quit
11
N/A
N/A
By default, automatic link cost calculation is enabled for TRILL ports.
N/A
5.
Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view.
6.
Configure the link cost for the
TRILL port.
interface interface-type interface-number trill cost value
N/A
The default setting is 2000.
Configuring announcing VLANs and the designated VLAN
The concepts and symbols used to describe a VLAN on a port are as follows:
• Enabled VLAN —A VLAN enabled on the port.
• Forwarding VLAN —A VLAN for which the port is the appointed port.
• ∩ and ∪ —Set operation symbols. ∩ indicates set-theoretic intersection, and ∪ indicates set-theoretic union.
RBs send Hello frames in a set of VLANs. The VLAN set is calculated as follows:
• DRB —Enabled VLANs ∩ (announcing VLANs ∪ designated VLAN).
• Non-DRB —Enabled VLANs ∩ (designated VLAN ∪ (announcing VLANs ∩ forwarding VLANs)).
To prevent Hello frames from consuming an excessive amount of CPU resources, reduce the number of announcing VLANs.
RBs use the designated VLAN to forward TRILL protocol frames (except Hello frames) and local data frames. For RBs to establish adjacencies and forward TRILL data frames, make sure the designated VLAN is an enabled VLAN.
To configure announcing VLANs and the designated VLAN:
Step Command Remarks
1.
Enter system view.
2.
Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view. system-view interface interface-type interface-number
N/A
N/A
3.
Configure announcing
VLANs.
4.
Configure the designated
VLAN. trill announcing-vlan { vlan-list | null } trill designated-vlan vlan-id
By default, no announcing VLAN is configured, and announcing
VLANs are enabled VLANs.
By default, no designated VLAN is configured. The system automatically selects an enabled
VLAN as the designated VLAN.
Configuring TRILL timers
You can configure the following TRILL timers:
12
• Hello interval and Hello multiplier —The RB advertises Hello frames at the Hello interval to maintain a TRILL adjacency. The shorter the Hello interval, the faster the network convergence. However, a shorter Hello interval consumes more system resources. The adjacency holding time is obtained by multiplying the Hello interval by the Hello multiplier. The RB advertises the adjacency holding time to neighbors through Hello frames. If a neighbor does not receive any Hello frame from the RB within the adjacency holding time, it removes the TRILL adjacency with the RB.
• AVF inhibition time —As the AVF of a VLAN, the RB guarantees that frames of the VLAN enter and leave a broadcast network through the same port. Other RBs on the broadcast network do not process frames from the VLAN.
To avoid loops, the RB suppresses its AVF role during the inhibition time when one of the following conditions exists:
{
{
The RB detects a root bridge change on the broadcast network.
Other RBs advertise a different AVF for the VLAN.
When the inhibition time expires, the RB restores its AVF role if it is still the AVF of the VLAN.
• CSNP interval —On a broadcast network, the RB advertises CSNPs at the CSNP interval to perform network-wide LSDB synchronization if it is elected as the DRB. A CSNP records all LSP digests of the
RB's local LSDB. A remote RB compares a received CSNP against its local LSDB to verify whether some LSPs are aged out or missing. If the CSNP has an LSP digest that the local LSDB does not have, the remote RB sends a PSNP packet to request the LSP.
To configure TRILL timers:
1.
Enter system view.
2.
Enter Layer 2 Ethernet or aggregate interface view. system-view interface interface-type interface-number
N/A
N/A
3.
Configure the Hello interval. trill timer hello interval
The default setting is 10 seconds.
This command sets the Hello interval for an
RB. The Hello interval of a DRB is 1/3 of the
Hello interval of an RB. This allows for DRB failures to be quickly detected.
4.
Configure the Hello multiplier.
5.
Configure the AVF inhibition time.
6.
Configure the CSNP interval. trill timer holding-multiplier count trill timer avf-inhibited time trill timer csnp interval
The default setting is 3.
The default setting is 30 seconds.
The default setting is 10 seconds.
Configuring TRILL LSP parameters and features
Setting TRILL LSP parameters
You can set the following LSP parameters:
13
• LSP maximum age —The RB uses the LSP maximum age as the remaining lifetime of the LSPs that it originates. When the RB detects that the remaining lifetime of an LSP reaches 0 seconds in the LSDB, the RB performs the following tasks:
{
Removes the LSP's content.
{
{
Keeps the LSP's digest.
Sets the LSP's remaining lifetime to 0 and purges the LSP from the network by advertising the LSP to other RBs.
• LSP refresh interval —A locally originated LSP is forcibly refreshed when its remaining lifetime is no greater than n: n = LSP maximum age – LSP refresh interval. This mechanism avoids frequent LSP aging and ensures network stability.
• LSP generation timer parameters —By adjusting the TRILL LSP generation timer parameters, you can prevent frequent network changes from consuming an excessive amount of bandwidth and device resources.
When the network is stable, the LSP generation timer is set to the minimum interval for each LSP generation. When the network is unstable, the LSP generation timer is added by the incremental interval for each LSP generation until the maximum interval is reached.
• Maximum length of originated LSPs —The RB selects the smallest value from the following values as the actual maximum length of LSPs to be sent to a neighbor:
{
{
{
The configured maximum length of originated LSPs.
The interface MTU.
The maximum originated LSP length carried in the LSPs sent by the neighbor.
• Maximum length of received LSPs —When the RB receives an LSP that exceeds the length, the RB drops the LSP.
• Overload bit of LSPs —The RB sets the Overload bit in LSPs if the RB fails and cannot correctly perform route selection and packet forwarding. When the RB cannot record the complete LSDB because of insufficient memory, routing calculation errors occur. To make troubleshooting easier, temporarily exclude the RB from the TRILL network by setting the Overload bit for the LSPs sent by the
RB.
• Minimum LSP interval and maximum number of LSPs transmitted per interval —To avoid frequent
LSP aging in the network, RBs periodically advertise LSPs. The actual refresh interval of an LSP is determined by both the minimum LSP interval and the maximum number of LSPs transmitted per interval. To prevent LSPs from being aged out accidentally, set the LSP maximum age and the LSP refresh interval appropriately.
To set TRILL LSP parameters:
1.
Enter system view.
2.
Enter TRILL view.
3.
Set the LSP maximum age.
4.
Set the LSP refresh interval. system-view N/A trill N/A timer lsp-max-age time The default setting is 1200 seconds. timer lsp-refresh time The default setting is 900 seconds.
14
5.
Set the TRILL LSP generation timer parameters.
6.
Configure the maximum length of originated LSPs.
7.
Configure the maximum length of received LSPs. timer lsp-generation maximum-interval
[ minimum-interval
[ incremental-interval ] ] lsp-length originate size lsp-length receive size
8.
Set the Overload bit of
LSPs and set the lifetime for the set Overload bit. set overload [ timeout ]
By default, the maximum LSP generation interval is 2 seconds, the minimum interval is 10 milliseconds, and the incremental interval is 20 milliseconds.
The default setting is 1458 bytes.
To prevent the system from generating error messages, do not set the maximum length of originated LSPs to be greater than the maximum length of received LSPs.
The default setting is 1492 bytes.
To prevent the system from generating error messages, do not set the maximum length of originated LSPs to be greater than the maximum length of received LSPs.
By default, the Overload bit is not set.
Do not perform this task on the root RB of a
TRILL distribution tree. The root RB cannot forward traffic when the Overload bit of
LSPs is set on the RB.
N/A 9.
Return to system view. quit
10.
Enter Layer 2 Ethernet or aggregate interface view. interface interface-type interface-number
11.
Configure the minimum
LSP interval and the maximum number of
LSPs transmitted per interval. trill timer count ] lsp interval [ count
Enabling TRILL LSP fast advertisement
N/A
By default, the minimum LSP interval is 10 milliseconds, and the maximum number of
LSPs transmitted per interval is 5.
LSP fast advertisement enables TRILL to immediately advertise the specified number of LSPs that invoke
SPF calculation. This mechanism improves network convergence time.
To enable TRILL LSP fast advertisement:
Step Command
1.
Enter system view. system-view
2.
Enter TRILL view. trill
3.
Enable TRILL LSP fast advertisement. flash-flood [ flood-count flooding-count | max-timer-interval flooding-interval ] *
Remarks
N/A
N/A
By default, TRILL LSP fast advertisement is disabled.
15
Enabling TRILL pseudonode bypass
This feature disables a DRB from generating LSPs for the pseudonode when the DRB has only one neighbor on a broadcast network. This reduces the number of LSPs in the network.
To enable the pseudonode bypass feature:
Step Command
1.
Enter system view.
2.
Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view.
3.
Enable the pseudonode bypass feature. system-view interface interface-type interface-number trill bypass-pseudonode enable
Remarks
N/A
N/A
By default, the pseudonode bypass feature is disabled.
Setting the SPF algorithm parameters
The RB uses the SPF algorithm to calculate a shortest path tree with itself as the root based on the LSDB.
The RB uses the shortest path tree to determine the next hop to a destination network. By adjusting the SPF calculation intervals, you can prevent resource overconsumption when the network is unstable.
When the network is stable, the SPF calculation interval for continuous calculations is reduced to minimum-interval . When the network is unstable, the SPF calculation interval is added by incremental-interval × 2 n-2 (n is the number of continuous SPF calculation times) for each SPF calculation until the maximum interval is reached.
To set the SPF algorithm parameters:
1.
Enter system view.
2.
Enter TRILL view. system-view trill
3.
Set the SPF calculation interval for TRILL. timer spf maximum-interval
[ minimum-interval
[ incremental-interval ] ]
N/A
N/A
By default, the maximum SPF calculation interval is 10 seconds, the minimum SPF calculation interval is 10 milliseconds, and the SPF calculation incremental interval is 20 milliseconds.
Configuring TRILL distribution trees
Setting basic distribution tree parameters
In a TRILL network, RBs perform the following tasks:
• Compute TRILL distribution trees according to the LSDB.
• Use the TRILL distribution trees to guide the forwarding of multidestination frames.
An RB with a higher priority is selected as the root bridge of a TRILL distribution tree.
16
An LSP sent by an RB carries the following TRILL distribution tree information:
• The number of TRILL distribution trees that the RB wants all RBs to compute.
• The maximum number of TRILL distribution trees that the RB can compute (this number is fixed at 15).
• The number of TRILL distribution trees that the RB has computed.
Each RB can compute a maximum of m TRILL distribution trees. An RB determines the number of TRILL distribution trees to compute ( n ) by selecting the lower value from the following two values:
• The number of TRILL distribution trees that the highest-priority RB wants all RBs to compute.
• The smallest m value across the TRILL network.
The RB selects the first n nicknames from the nickname list advertised by the highest-priority RB. The RB uses the selected nicknames as the root nicknames for computing distribution trees.
To set basic TRILL distribution tree parameters:
1.
Enter system view.
2.
Enter TRILL view.
3.
Set a priority for the RB.
4.
Configure the number of
TRILL distribution trees that the RB wants all RBs to compute. system-view N/A trill N/A tree-root priority priority The default setting is 32768. trees calculate count The default setting is 1.
Enabling TRILL distribution tree multithread calculation
This feature enables a multicore CPU device to improve TRILL distribution tree calculation efficiency by using each thread to calculate a distribution tree.
To enable TRILL distribution tree multithread calculation:
Step Command
1.
Enter system view. system-view
2.
Enter TRILL view.
3.
Enable TRILL distribution tree multithread calculation.
Remarks
N/A trill N/A multicast multi-thread enable By default, this feature is disabled.
Enabling load balancing over TRILL distribution trees
By default, ingress traffic is not load balanced over TRILL distribution trees after a forwarding VLAN is deleted on the RB. To load balance ingress traffic of the remaining forwarding VLANs over the existing distribution trees, you can enable load balancing over TRILL distribution trees.
Ingress traffic is load balanced in any of the following conditions, regardless of whether load balancing is enabled or not:
• A forwarding VLAN is added.
• A distribution tree is added or deleted.
17
When a distribution tree is added, the RB switches ingress traffic to the new tree to implement load balancing. However, the RB cannot use the new distribution tree to forward traffic before other RBs are ready to use the new tree. In this case, you can set a delay timer for the RB to switch ingress traffic to the new distribution tree.
If traffic is not evenly distributed over distribution trees, you can also perform one-time load balancing over TRILL distribution trees.
To enable load balancing over TRILL distribution trees:
Step Command
1.
Enter system view. system-view
2.
Enter TRILL view.
Remarks
N/A trill N/A
3.
Enable load balancing over
TRILL distribution trees.
4.
Set the delay timer for the RB to switch ingress traffic to a new TRILL distribution tree.
5.
Perform one-time load balancing over TRILL distribution trees. ingress assign-rule load-balancing ingress assign-delay seconds set ingress-load-balancing
By default, load balancing over
TRILL distribution trees is disabled.
The default delay timer is 300 seconds.
Perform this task when load balancing over TRILL distribution trees is disabled.
Configuring TRILL ECMP routes
TRILL unicast ECMP routes share traffic to the same destination. You can configure the maximum number of TRILL unicast ECMP routes.
The maximum number of TRILL unicast ECMP routes is restricted by the maximum number of ECMP routes.
The maximum number of ECMP routes can be configured by using the max-ecmp-num command. It is in the range of 1 to 32. After you configure the maximum number of ECMP routes as n , the value range for the number argument of the max-unicast-load-balancing command is 1 to n . For more information about the max-ecmp-num command, see Layer 3—IP Routing Command Reference .
When TRILL multicast ECMP is disabled, TRILL distribution trees do not use equal-cost routes to share traffic. When TRILL multicast ECMP is enabled, TRILL assigns equal-cost routes to multiple TRILL distribution trees to improve load sharing performance.
To configure TRILL ECMP routes:
1.
Enter system view.
2.
Enter TRILL view.
3.
Configure the maximum number of TRILL unicast ECMP routes. system-view N/A trill N/A max-unicast-load-balancing number
The default maximum number is 8.
4.
Enable TRILL multicast ECMP. multicast-ecmp
[ p2p-ignore ] enable
By default, TRILL multicast ECMP is disabled.
Make sure the status of TRILL multicast
ECMP is the same across the TRILL
18
network.
Enabling incremental flush for TRILL multicast routing entries
TRILL multicast routing entries are classified into three levels according to the following key combinations:
• RB —Root bridge of a TRILL distribution tree.
• RB+VLAN —Root bridge and VLAN of a TRILL distribution tree.
• RB+VLAN+MAC —Root bridge and VLAN of a TRILL distribution tree and a MAC address.
An entry that is identified by fewer keys is at a higher level.
The incremental flush feature enables the device to compare the outgoing port list and local receiving flag of an entry with its next higher level entry. If the two entries have the same outgoing port list and local receiving flag, the higher level entry is issued to the TRILL FIB. For example, if entry RB 2 and entry RB
2+VLAN 10 have the same outgoing port list and local receiving flag, entry RB 2 is issued.
This feature reduces the number of flushed entries in the scenarios where an entry and its next higher level entry have the same outgoing port list and local receiving flag. Enabling this feature in other scenarios causes the system to issue a large number of entries at the same time and degrades the device performance.
To enable incremental flush for TRILL multicast routing entries:
1.
Enter system view.
2.
Enter TRILL view.
3.
Enable incremental flush for
TRILL multicast routing entries. system-view N/A trill N/A flush-policy difference
By default, incremental flush is disabled for TRILL multicast routing entries.
Configuring a TRILL VR
Configure a TRILL VR for the TRILL network to forward Layer 3 traffic.
Creating a TRILL VR
When you create a TRILL VR, you must assign a virtual IP address to the VR. If a VLAN interface connects to multiple subnets, you can assign multiple virtual IP addresses to the TRILL VR on the interface.
Configuration restrictions and guidelines
• On a VLAN interface, the virtual IP addresses assigned to a TRILL VR must meet the following requirements:
{
The virtual IP addresses must be on the same network segment as the IP address of the VLAN interface.
19
{
The VR cannot use the IP address of the VLAN interface as a virtual IP address.
• The member RBs of a VR must use the same VLAN configurations, virtual IP addresses, and
VLAN-interface-to-VPN bindings. The VR cannot use the real IP address of a member RB as a virtual
IP address.
• On a VLAN interface, TRILL VRs operate only when the interface is up.
Configuration procedure
To create a TRILL VR:
Step Command Remarks
1.
Enter system view. system-view N/A
2.
Enter VLAN interface view.
3.
Create a TRILL VR and assign a virtual IP address to the VR. interface vlan-interface vlan-interface-number
• Create an IPv4 VR: trill vr vrid vr-id virtual-ip virtual-address
• Create an IPv6 VR: trill vr ipv6 vrid vr-id virtual-ip virtual-address [ link-local ]
N/A
By default, no TRILL VRs exist.
Associating a TRILL VR with a track entry
A TRILL VR can collaborate with network quality analyzer (NQA) or bidirectional forwarding detection
(BFD) through a track entry to monitor the uplinks of the member RBs. NQA or BFD sends the uplink status changes to the Track module. Based on the detection results, the Track module changes the state of the track entry and informs the TRILL module of the change. Then the TRILL module can react to the change to avoid traffic interruption and network performance degradation.
For information about NQA, see Network Management and Monitoring Configuration Guide .
For more information about BFD and Track, see High Availability Configuration Guide .
To associate a TRILL VR with a track entry:
1.
Enter system view. system-view
2.
Enter VLAN interface view. interface vlan-interface vlan-interface-number
3.
Associate a TRILL VR with a track entry. trill vr [ ipv6 ] vrid vr-id track track-entry-number
N/A
N/A
By default, a TRILL VR is not associated with any track entry.
You can associate a track entry only to an existing TRILL VR. A TRILL VR can be associated with a maximum of eight track entries.
20
Permitting a non-TRILL device to learn the MAC address of the TRILL VR
A non-TRILL device is a device that does not support TRILL or is not enabled with TRILL. When a non-TRILL device is connected to an access RB, the device cannot learn the MAC address of the TRILL VR. User packets destined for the TRILL VR are flooded by the device.
To avoid the flooding traffic, enable TRILL VR simulation on the access RB interface that connects to the non-TRILL device. This feature enables the interface to send a packet that uses the MAC address of the
TRILL VR as the source MAC address at a specified interval.
To permit a non-TRILL device to learn the MAC address of the TRILL VR:
Remarks
N/A
Step Command
1.
Enter system view. system-view
2.
Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view. interface interface-type interface-number
3.
Enable TRILL VR simulation. trill vr packet simulate
4.
Set the packet sending interval. trill vr packet timer time
N/A
By default, this feature is disabled.
By default, the packet sending interval is 280 seconds.
Enabling MAC address retaining on TRILL ports
On an access RB, the system deletes all MAC addresses on a TRILL port when the port is down. If the TRILL
VR has an ARP entry for a removed MAC address, the VR will forward frames destined for the MAC address to the access RB. As a result, the access RB floods the frames in the TRILL network.
To prevent such floods, enable MAC address retaining on TRILL ports. The system retains the MAC addresses on TRILL ports when the ports are down.
To enable MAC address retaining on TRILL ports:
Step Command
1.
Enter system view. system-view
2.
Enter TRILL view. trill
3.
Enable MAC address retaining on TRILL ports. mac-deleting forbidden
Remarks
N/A
N/A
By default, the system deletes all
MAC addresses on a TRILL port when the port is down.
This feature takes effect only on
TRILL ports of which the link type is access or hybrid.
Enabling logging of TRILL neighbor changes
Perform this task to output logs of TRILL neighbor changes to the configuration terminal.
21
To enable logging of TRILL neighbor changes:
1.
Enter system view.
2.
Enter TRILL view.
3.
Enable logging of TRILL neighbor changes. system-view N/A trill N/A log-peer-change enable
By default, logging of TRILL neighbor changes is enabled.
Configuring SNMP for TRILL
To report critical TRILL events to an NMS, enable SNMP notifications for TRILL. For TRILL event notifications to be sent correctly, you must also configure SNMP as described in Network Management and
Monitoring Configuration Guide .
TRILL shares the standard IS-IS MIB with IS-IS. The standard IS-IS MIB provides only single-instance MIB objects. For SNMP to correctly identify TRILL's management information in the standard IS-IS MIB, you must configure a unique context for TRILL.
Context is a method introduced to SNMPv3 for multiple-instance management. For SNMPv1/v2c, you must specify a community name as a context name for protocol identification.
To configure SNMP for TRILL:
Step Command
1.
Enter system view. system-view
Remarks
N/A
2.
Enable SNMP notifications for TRILL. snmp-agent trap enable trill
[ adjacency-state-change | area-mismatch | buffsize-mismatch | id-length-mismatch | lsdboverload-state-change | lsp-parse-error | lsp-size-exceeded | max-seq-exceeded | maxarea-mismatch | new-drb | own-lsp-purge
| protocol-support | rejected-adjacency | skip-sequence-number | topology-change | version-skew ] *
3.
Enter TRILL view. trill
By default, SNMP notifications are enabled for
TRILL.
N/A
4.
Configure the context name for TRILL. snmp context-name context-name
By default, no context name is configured for TRILL.
Enabling TRILL to forward traffic from EVB
S-channels
Perform this task on the interface that is directly connected to a server. TRILL will forward the packets received from the EVB S-channels on the interface to the TRILL network.
Before you perform this task, you must enable EVB on the interface.
To enable TRILL to forward traffic from EVB S-channels:
22
1.
Enter system view.
2.
Enter Layer 2 Ethernet or aggregate interface view.
3.
Configure the link type of the port as trunk.
4.
Enable EVB. system-view interface interface-type interface-number port link-type trunk evb enable
5.
Enable TRILL to forward traffic from EVB
S-channels. trill evb-support
N/A
N/A
The default link type of a port is access.
By default, EVB is disabled on a port.
By default, TRILL does not support forwarding traffic from EVB S-channels.
The trill evb-support command and TRILL commands (including trill enable ) are mutually exclusive. Do not configure both EVB and TRILL on an interface.
Configuring TRILL GR
Graceful Restart (GR) ensures the continuity of packet forwarding when a protocol restarts or an active/standby switchover occurs on the RB. The RB advertises the restart status to its neighbors, and allows the neighbors to re-establish connections. GR involves the following roles:
• GR restarter —Graceful restarting router. It must be GR capable.
• GR helper —A neighbor of the GR restarter. It helps the GR restarter to complete the GR process.
By default, the device acts as the GR helper. Configure TRILL GR on the target GR restarter.
To configure TRILL GR:
1.
Enter system view.
2.
Enter TRILL view.
3.
Enable GR for TRILL.
4.
(Optional.) Configure the GR interval for TRILL.
5.
(Optional.) Suppress the
SA bit during graceful restart. system-view graceful-restart interval interval
N/A trill N/A graceful-restart By default, GR is disabled for TRILL.
The default setting is 300 seconds. graceful-restart suppress-sa
By default, the SA bit is set during graceful restart.
Associating a TRILL port with a track entry
Associate a track entry with a TRILL port to fast detect the loss of connectivity to the neighbor on the port.
Track can collaborate with Connectivity Fault Detection (CFD) to monitor the link state of the neighbor.
For more information about CFD and Track, see High Availability Configuration Guide .
To use CFD to detect link failures in a TRILL network, you must configure the outward-facing MEPs. CFD supports only single-hop detection. CFD packets cannot be forwarded by RBs.
23
To associate a TRILL port with a track entry:
1.
Enter system view.
2.
Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view.
3.
Associate a track entry with the interface. system-view interface interface-type interface-number trill track track-entry-number
Displaying and maintaining TRILL
N/A
N/A
By default, an interface is not associated with any track entries.
Execute the display commands in any view and the reset command in user view.
Task Command
Display TRILL ardency table information. display trill adjacent-table [ count | nickname nickname interface interface-type interface-number ]
Display brief TRILL information. display trill brief
Display TRILL FIB information. display trill fib [ count | nickname nickname ] display trill graceful-restart status Display TRILL GR status.
Display TRILL ingress forwarding information. display trill ingress-route [ vlan vlan-list ] display trill interface [ interface-type interface-number | verbose ] display trill lsdb [ local | lsp-id lsp-id | verbose ] *
Display TRILL port information.
Display TRILL LSDB information.
Display all ingress entries in the TRILL multicast FIB (MFIB).
Display all egress entries in the TRILL
MFIB.
Display information about the TRILL multicast routing table.
Display the TRILL neighbor table.
Display TRILL neighbor statistics.
Display the TRILL RPF check table information. display display
| vlan display vlan-id mac-address display trill trill trill trill mfib mfib
[ mac-address multicast-route
] ] ] ingress transit rpf-table
[
[ vlan nickname
[ tree-root vlan-id [ nickname local-entry nickname mac-address tree-root
[
] ] ]
| remote-entry prune-entry nickname [ vlan
| vlan-list display trill neighbor-table display trill peer [ interface interface-type interface-number ]
] ] rpf-entry
[ mac
Display TRILL topology information. display trill topology [ verbose ]
Display information about the TRILL unicast routing table. display trill unicast-route [ nickname nickname ] [ verbose ]
Display TRILL VR information. display trill vr [ ipv6 ] [ verbose [ vrid vr-id [ interface interface-type interface-number ] ] | vrid vr-id ]
Display the TRILL VR adjacency table. display trill vr-adjacent-table [ count | nickname nickname interface interface-type interface-number ]
24
Task Command
Display information about the TRILL
VR unicast FIB. display trill vr-fib [ count | mac mac-address vlan vlan-id ]
Display the TRILL VR multiport unicast
MAC address table. display trill vr-route [ vrid vrid ] [ vlan vlan-id ] [ mac-address mac-address ]
Clear dynamic running statistics of the TRILL process. reset trill
TRILL configuration example
Network requirements
, a data center network has three layers: the core layer, the distribution layer, and the access layer. A port connected to a higher layer device is an uplink port, and a port connected to a lower layer device is a downlink port.
Configure TRILL in the network as follows:
• Enable TRILL on both uplink and downlink ports of access layer devices, and enable TRILL on downlink ports of distribution layer devices.
• Configure two TRILL distribution trees that are rooted at RB 1 and RB 2. Configure a higher priority for RB 1 to be a distribution tree root.
• Configure a TRILL VR and multicast routing for the TRILL network to forward Layer 3 traffic.
Figure 8 Network diagram
25
Configuration procedure
This section provides only TRILL-related configurations.
1.
Configure the downlink ports of access layer devices:
# Enable TRILL globally on RB 3.
<RB3> system-view
[RB3] trill
[RB3-trill] quit
# Enable TRILL on downlink port Ten-GigabitEthernet 1/0/1, and configure the port's link type as access without the alone attribute.
[RB3] interface ten-gigabitethernet 1/0/1
[RB3-Ten-GigabitEthernet1/0/1] trill enable
[RB3-Ten-GigabitEthernet1/0/1] trill link-type access
[RB3-Ten-GigabitEthernet1/0/1] quit
# Configure RB 4 through RB 6 in the same way you configured RB 3.
2.
Configure the uplink ports of access layer devices:
# On RB 3, enable TRILL on uplink ports Ten-GigabitEthernet 1/0/2 and Ten-GigabitEthernet
1/0/3, and configure these ports as VR ports.
[RB3] interface ten-gigabitethernet 1/0/2
[RB3-Ten-GigabitEthernet1/0/2] trill enable
[RB3-Ten-GigabitEthernet1/0/2] trill link-type vr
[RB3-Ten-GigabitEthernet1/0/2] quit
[RB3] interface ten-gigabitethernet 1/0/3
[RB3-Ten-GigabitEthernet1/0/3] trill enable
[RB3-Ten-GigabitEthernet1/0/3] trill link-type vr
[RB3-Ten-GigabitEthernet1/0/3] quit
# Configure RB 4 through RB 6 in the same way you configured RB 3.
3.
Configure the downlink ports of distribution layer devices:
# Enable TRILL globally on RB 1.
<RB1> system-view
[RB1] trill
[RB1-trill] quit
# Enable TRILL on downlink ports Ten-GigabitEthernet 1/0/1 through Ten-GigabitEthernet 1/0/4, and configure these ports as VR ports.
[RB1] interface ten-gigabitethernet 1/0/1
[RB1-Ten-GigabitEthernet1/0/1] trill enable
[RB1-Ten-GigabitEthernet1/0/1] trill link-type vr
[RB1-Ten-GigabitEthernet1/0/1] quit
[RB1] interface ten-gigabitethernet 1/0/2
[RB1-Ten-GigabitEthernet1/0/2] trill enable
[RB1-Ten-GigabitEthernet1/0/2] trill link-type vr
[RB1-Ten-GigabitEthernet1/0/2] quit
[RB1] interface ten-gigabitethernet 1/0/3
[RB1-Ten-GigabitEthernet1/0/3] trill enable
[RB1-Ten-GigabitEthernet1/0/3] trill link-type vr
[RB1-Ten-GigabitEthernet1/0/3] quit
26
[RB1] interface ten-gigabitethernet 1/0/4
[RB1-Ten-GigabitEthernet1/0/4] trill enable
[RB1-Ten-GigabitEthernet1/0/4] trill link-type vr
[RB1-Ten-GigabitEthernet1/0/4] quit
# Configure RB 2 in the same way you configured RB 1.
4.
Configure the Layer 3 interfaces on the distribution layer devices:
# On RB 1, enable IP multicast routing, and enable PIM-SM on core-facing interface
VLAN-interface 5. Configure the core layer device interface with the IP address 1.1.1.1 as the
C-BSR and C-RP.
[RB1] multicast routing
[RB1-mrib] quit
[RB1] interface vlan-interface 5
[RB1-Vlan-interface5] pim sm
[RB1-Vlan-interface5] quit
[RB1] pim
[RB1-pim] c-bsr 1.1.1.1
[RB1-pim] c-rp 1.1.1.1
[RB1-pim] quit
# On RB 1, perform the following tasks on access-facing interfaces VLAN-interface 10 and
VLAN-interface 20:
{
{
{
Assign an IPv4 address to the interface.
Create an IPv4 TRILL VR and assign a virtual IPv4 address to the VR.
Enable IGMP and PIM-SM.
[RB1] interface vlan-interface 10
[RB1-Vlan-interface10] ip address 10.1.1.253 24
[RB1-Vlan-interface10] trill vr vrid 1 virtual-ip 10.1.1.1
[RB1-Vlan-interface10] igmp enable
[RB1-Vlan-interface10] pim sm
[RB1-Vlan-interface10] quit
[RB1] interface vlan-interface 20
[RB1-Vlan-interface20] ip address 20.1.1.253 24
[RB1-Vlan-interface20] trill vr vrid 1 virtual-ip 20.1.1.1
[RB1-Vlan-interface20] igmp enable
[RB1-Vlan-interface20] pim sm
[RB1-Vlan-interface20] quit
# On RB 2, enable IP multicast routing, and enable PIM-SM on core-facing interface
VLAN-interface 5. Configure the core layer device interface with the IP address 1.1.1.1 as the
C-BSR and C-RP.
[RB2] multicast routing
[RB2-mrib] quit
[RB2] interface vlan-interface 5
[RB2-Vlan-interface5] pim sm
[RB2-Vlan-interface5] quit
[RB2] pim
[RB2-pim] c-bsr 1.1.1.1
[RB2-pim] c-rp 1.1.1.1
[RB2-pim] quit
27
# On RB 2, perform the following tasks on access-facing interfaces VLAN-interface 10 and
VLAN-interface 20:
{
Assign an IPv4 address to the interface.
{
{
Create an IPv4 TRILL VR and assign a virtual IPv4 address to the VR.
Enable IGMP and PIM-SM.
[RB2] interface vlan-interface 10
[RB2-Vlan-interface10] ip address 10.1.1.254 24
[RB2-Vlan-interface10] trill vr vrid 1 virtual-ip 10.1.1.1
[RB2-Vlan-interface10] igmp enable
[RB2-Vlan-interface10] pim sm
[RB2-Vlan-interface10] quit
[RB2] interface vlan-interface 20
[RB2-Vlan-interface20] ip address 20.1.1.254 24
[RB2-Vlan-interface20] trill vr vrid 1 virtual-ip 20.1.1.1
[RB2-Vlan-interface20] igmp enable
[RB2-Vlan-interface20] pim sm
[RB2-Vlan-interface20] quit
5.
Configure IGMP snooping:
# On RB 1, enable IGMP snooping globally, and enable IGMP snooping and dropping unknown multicast data on VLAN 10 and VLAN 20.
[RB1] igmp-snooping
[RB1-igmp-snooping] quit
[RB1] vlan 10
[RB1-vlan10] igmp-snooping enable
[RB1-vlan10] igmp-snooping drop-unknown
[RB1] vlan 20
[RB1-vlan20] igmp-snooping enable
[RB1-vlan20] igmp-snooping drop-unknown
# Configure RB 2 through RB 6 in the same way you configured RB 1.
6.
Configure TRILL distribution trees:
# Set RB 1's priority to 65535, and set the number to 2 for TRILL distribution trees that the RB wants all RBs to compute.
[RB1] trill
[RB1-trill] tree-root priority 65535
[RB1-trill] trees calculate 2
[RB1-trill] quit
# Set RB 2's priority to 65534, and set the number to 2 for TRILL distribution trees that the RB wants all RBs to compute.
[RB2] trill
[RB2-trill] tree-root priority 65534
[RB2-trill] trees calculate 2
[RB2-trill] quit
28
Verifying the configuration
Suppose that the nicknames of RB 1 through RB 6 are 0x5801 through 0x5806. The system IDs of RB 1 and RB 2 are 0000.0000.0001 and 0000.0000.0002.
# Display brief information about all entries in the TRILL unicast routing table on an access layer device
(for example, RB 3).
[RB3] display trill unicast-route
Destination Interface NextHop
-----------------------------------------------
0x5801 XGE1/0/2 Direct
0x5802 XGE1/0/3 Direct
0x5803 N/A N/A
0x5804 XGE1/0/2 0x5801
XGE1/0/3 0x5802
0x5805 XGE1/0/2 0x5801
XGE1/0/3 0x5802
0x5806 XGE1/0/2 0x5801
XGE1/0/3 0x5802
# Display all entries in the TRILL multicast routing table.
[RB3] display trill multicast-route
Root Flag
-------------------------------------
0x5801 Valid
0x5802 Valid
# Display multicast routing information for the TRILL distribution tree rooted at RB 1.
[RB3] display trill multicast-route tree-root 5801
Root: 0x5801
LocalRcvFlag: True
List of VLANs:
1
List of outgoing ports:
XGE1/0/2
# Display brief information about all IPv4 TRILL VRs.
[RB1] display trill vr
VRID Partner RB State Local
----------------------------------------------
1 0000.0000.0001 Backup Y
0000.0000.0002 Master N
# Display all entries in the TRILL VR multiport unicast MAC address table.
[RB3] display trill vr-route
VRID MAC address VLAN Port
---------------------------------------
1 0cda-41ed-be01 10 XGE1/0/2
XGE1/0/3
1 0cda-41ed-be01 20 XGE1/0/2
XGE1/0/3
29
# Display information about the multicast forwarding entries on a distribution layer device (for example,
RB 1).
[RB1] display multicast forwarding-table
Total 1 entries, 1 matched
00001. (0.0.0.0, 225.1.1.1)
Flags: ox
Uptime: 00:25:57
Incoming interface: Vlan-interface5
List of 2 outgoing interfaces:
1: Vlan-interface10
2: Vlan-interface20
Matched 105 packets(174 bytes), Wrong If 0 packets
Forwarded 105 packets(174 bytes)
30
Support and other resources
Contacting HP
For worldwide technical support information, see the HP support website: http://www.hp.com/support
Before contacting HP, collect the following information:
• Product model names and numbers
• Technical support registration number (if applicable)
• Product serial numbers
• Error messages
• Operating system type and revision level
• Detailed questions
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/go/wwalerts
After registering, you will receive email notification of product enhancements, new driver versions, firmware updates, and other product resources.
Related information
Documents
To find related documents, browse to the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals
• For related documentation, navigate to the Networking section, and select a networking category.
• For a complete list of acronyms and their definitions, see HP FlexNetwork Technology Acronyms.
Websites
• HP.com http://www.hp.com
• HP Networking http://www.hp.com/go/networking
• HP manuals http://www.hp.com/support/manuals
• HP download drivers and software http://www.hp.com/support/downloads
• HP software depot http://www.software.hp.com
• HP Education http://www.hp.com/learn
31
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Description
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic
[ ]
{ x | y | ... }
[ x | y | ... ]
{ x | y | ... } *
[ x | y | ... ] *
&<1-n>
Italic text represents arguments that you replace with actual values.
Square brackets enclose syntax choices (keywords or arguments) that are optional.
Braces enclose a set of required syntax choices separated by vertical bars, from which you select one.
Square brackets enclose a set of optional syntax choices separated by vertical bars, from which you select one or none.
Asterisk-marked braces enclose a set of required syntax choices separated by vertical bars, from which you select at least one.
Asterisk-marked square brackets enclose optional syntax choices separated by vertical bars, from which you select one choice, multiple choices, or none.
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
Symbols
Convention Description
Boldface
Window names, button names, field names, and menu items are in bold text. For example, the New User window appears; click OK .
> Multi-level menus are separated by angle brackets. For example, File > Create > Folder .
Convention Description
WARNING
An alert that calls attention to important information that if not understood or followed can result in personal injury.
CAUTION
An alert that calls attention to important information that if not understood or followed can result in data loss, data corruption, or damage to hardware or software.
IMPORTANT
NOTE
An alert that calls attention to essential information.
An alert that contains additional or supplementary information.
TIP
An alert that provides helpful information.
32
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 switching 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.
Port numbering in examples
Represents a security card, such as a firewall, load-balancing, NetStream, SSL VPN, IPS, or ACG card.
The port numbers in this document are for illustration only and might be unavailable on your device.
33
Index
A access
TRILL access port link,
advertisement
TRILL LSP fast advertisement, 15
algorithm
TRILL SPF algorithm parameter, 16
appointed VLAN-x forwarder.
See
associating
TRILL port+track entry,
TRILL VR-Track entry,
AVF
AVF (TRILL),
C calculating
TRILL link cost configuration,
CFD
TRILL port+track entry association, 23
changing
TRILL neighbor change logging, 21
configuring
TRILL announcing VLAN,
TRILL ECMP routes,
TRILL forwarding for EVB S-channel traffic, 22
TRILL LSP parameter and feature,
TRILL port DRB priority,
TRILL port link type,
TRILL RB system ID,
TRILL SNMP,
TRILL timers,
cost
TRILL ECMP route configuration,
TRILL link cost configuration,
creating
CSNP
TRILL CSNP interval,
D designated
TRILL designated routing bridge,
displaying
TRILL,
distributing load balancing over TRILL distribution trees,
TRILL distribution tree,
TRILL distribution tree basics,
DRB
TRILL distribution tree multithread calculation,
TRILL port priority,
E enabling incremental flush for TRILL multicast routing
load balancing over TRILL distribution trees,
MAC address retaining on TRILL port,
TRILL,
TRILL distribution tree multithread calculation,
TRILL LSP fast advertisement,
TRILL neighbor change logging, 21
TRILL pseudonode bypass,
F flush incremental flush for TRILL multicast routing
format
TRILL data frame format,
forwarding
Layer 3 TRILL mechanisms,
TRILL configuration,
TRILL forwarding for EVB S-channel traffic, 22
TRILL frame formats,
TRILL GR configuration,
TRILL mechanisms,
TRILL SNMP configuration,
frame
TRILL data frame format,
34
G
Graceful Restart (GR)
TRILL GR helper,
H hello
TRILL hello interval,
hybrid
TRILL hybrid port link,
I
ID
TRILL RB system ID,
interval
TRILL CSNP interval,
TRILL hello interval,
IS-IS
L
Layer 2
TRILL forwarding mechanisms,
Layer 3
TRILL forwarding mechanisms,
link
TRILL link cost configuration,
TRILL link state database,
TRILL link state protocol data unit, 1
TRILL port link type,
load balancing
load balancing over TRILL distribution trees, 17
logging
TRILL neighbor change logging, 21
LSDB
TRILL LSP parameter,
,
LSP
TRILL LSP fast advertisement, 15
TRILL LSP parameter,
TRILL LSP parameter and feature,
M
MAC address
MAC address retaining on TRILL port, 21
TRILL VR MAC address learning for non-TRILL device,
maintaining
TRILL,
N naming
TRILL RB nickname,
neighbor
TRILL neighbor change logging, 21
network incremental flush for TRILL multicast routing
Layer 2 TRILL forwarding mechanisms,
Layer 3 TRILL forwarding mechanisms,
load balancing over TRILL distribution trees,
MAC address retaining on TRILL port,
pseudonode bypass,
TRILL designated VLAN,
TRILL distribution tree,
TRILL distribution tree basics,
TRILL distribution tree multithread calculation,
TRILL ECMP route configuration,
TRILL enable,
TRILL forwarding for EVB S-channel traffic, 22
TRILL forwarding mechanisms, 3
TRILL frame formats,
TRILL GR configuration,
TRILL LSP fast advertisement,
TRILL LSP parameter and feature, 13
TRILL neighbor change logging, 21
TRILL RB nickname,
TRILL RB system ID,
TRILL routing bridge network, 1
TRILL SNMP configuration,
TRILL SPF algorithm parameter,
TRILL VR MAC address learning for non-TRILL
TRILL VR-Track entry association,
network management
TRILL configuration,
,
NMS
TRILL SNMP configuration,
notifying
TRILL SNMP configuration,
2
P parameter
TRILL LSP max age parameter,
,
TRILL LSP max number transmitted,
,
TRILL LSP min interval, 13 , 13
TRILL LSP refresh interval,
permitting
TRILL VR MAC address learning for non-TRILL device,
port
TRILL link cost configuration,
TRILL port DRB priority,
TRILL port link type,
priority
TRILL distribution tree, 16 , 16
TRILL port DRB priority,
procedure
associating TRILL port+track entry, 23
associating TRILL VR-Track entry, 20
configuring TRILL announcing VLAN,
12 configuring TRILL designated VLAN, 12
configuring TRILL distribution tree, 16 configuring TRILL distribution tree basics, 16
configuring TRILL ECMP routes,
configuring TRILL LSP parameter and
configuring TRILL port DRB priority,
11 configuring TRILL port link cost, 11
configuring TRILL port link type,
configuring TRILL RB nickname, 9
configuring TRILL RB system ID,
configuring TRILL SNMP,
configuring TRILL timers,
creating TRILL VR,
enabling incremental flush for TRILL multicast
enabling load balancing over TRILL distribution
enabling MAC address retaining on TRILL port,
enabling TRILL,
enabling TRILL distribution tree multithread
enabling TRILL forwarding for EVB S-channel traffic,
enabling TRILL LSP fast advertisement,
enabling TRILL neighbor change logging,
3
enabling TRILL pseudonode bypass, 16
permitting TRILL VR MAC address learning for
setting TRILL LSP parameters,
setting TRILL SPF algorithm parameters,
protocols and standards
TRILL,
pseudonode
TRILL pseudonode bypass,
R
RB
restrictions
TRILL configuration,
TRILL port link type configuration, 10
TRILL VR creation restrictions, 19
route
TRILL ECMP route configuration,
routing bridge
TRILL,
TRILL distribution tree,
TRILL distribution tree basics,
S setting
TRILL distribution tree basics,
TRILL SPF algorithm parameters,
SNMP
TRILL SNMP configuration,
SPF
TRILL SPF algorithm parameter,
system
TRILL RB nickname,
TRILL RB system ID,
T timer
TRILL AVF inhibition time,
TRILL configuration,
TRILL CSNP interval,
Track
TRILL VR-Track entry association,
TRansparent Interconnection of Lots of Links.
Use
TRILL basic concepts,
basic distribution tree configuration, 16
configuration,
,
configuration restrictions,
displaying,
distribution tree configuration, 16
distribution tree multithread calculation, 17
EVB S-channel traffic forwarding,
GR configuration,
how it works,
incremental flush for TRILL multicast routing
Layer 2 forwarding mechanisms, 3
Layer 3 forwarding mechanisms, 5
load balancing over TRILL distribution trees, 17
LSP fast advertisement,
MAC address retaining on TRILL port, 21
neighbor change logging,
port DRB priority configuration, 11
port link cost configuration,
port link type configuration,
10 port link type configuration restrictions, 10
protocols and standards,
RB nickname configuration,
TRILL port+track entry association, 23
TRILL VR MAC address learning for non-TRILL device,
VR configuration,
VR creation,
VR creation restrictions,
VR-Track entry association, 20
trunk
TRILL trunk port link,
V
VLAN
TRILL announcing VLAN,
TRILL appointed VLAN-x forwarder, 1
TRILL appointed VLAN-x port,
TRILL VR-Track entry association, 20
4
ダウンロード
ドキュメントの公開リンク
広告