Professional Documents
Culture Documents
Table of contents
Introduction............................................................................................................................................................................2
Solution overview..................................................................................................................................................................2
TRILL fundamentals ..............................................................................................................................................................3
Routing bridge (RBridge or RB) .......................................................................................................................................3
TRILL trunk ports...............................................................................................................................................................3
TRILL access ports ............................................................................................................................................................3
TRILL access alone ports..................................................................................................................................................3
TRILL hybrid ports .............................................................................................................................................................3
Designated routing bridge (DRB) ....................................................................................................................................3
Appointed VLAN forwarder (AVF) ....................................................................................................................................3
Distribution trees...............................................................................................................................................................4
TRILL timers .......................................................................................................................................................................4
HP IRF TRILL enhancement ..................................................................................................................................................5
TRILL deployment architectures .........................................................................................................................................6
Distributed spines .............................................................................................................................................................6
Consolidated spines ..........................................................................................................................................................7
Server ToR connectivity....................................................................................................................................................8
IRF LACP MAD Links...........................................................................................................................................................8
Layer 3 routing with distributed spine interconnects...................................................................................................8
Consolidated layer 3 routing using multitenant device contexts (MDC) ....................................................................9
TRILL deployment best practices ..................................................................................................................................... 10
Appendix: Sample TRILL configurations.......................................................................................................................... 12
Spine 1 ............................................................................................................................................................................. 12
Leaf 1 ............................................................................................................................................................................... 13
Additional links ................................................................................................................................................................... 15
Architecture guide | Guidelines for deploying TRILL in an HP data center
Introduction
Transparent Interconnection of Lots of Links (TRILL) is an evolutionary step in Ethernet technology designed to address
some of the shortcomings within Ethernet, specifically spanning tree and loop prevention. TRILL provides a mechanism that
allows every single node to have a tree rooted at itself, allowing the optimal (shortest path) distribution of traffic as well as
multipathing for failure recovery.
This architecture guide provides design guidelines and best practices for deploying simple, scalable, and stable TRILL
Ethernet Fabrics in data centers on HP Networking switches.
Solution 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 with increased East/West
server traffic patterns as shown in figure 1.
Figure 1.TRILL fabric supporting East/West server traffic
TRILL fabric
VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM
Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Servers
2
Architecture guide | Guidelines for deploying TRILL in an HP data center
TRILL fundamentals
The following TRILL fundamentals shown in figure 2 are critical for TRILL deployment.
Figure 2. TRILL fundamentals
Routing bridges
Routing
bridges
3
Architecture guide | Guidelines for deploying TRILL in an HP data center
TRILL prevents network loops with multihomed L2 switches using DRB/AVF as shown in figure 3.
VLANs
100-200
L2 switch L2 switches
VLANs 100-200
VLANs 100-200 VLANs 100-200 VLANs 100-200
TRILL TRILL
fabric fabric
Distribution trees
Distribution trees as shown in figure 4 are used to forward multicast, broadcast, and unknown unicast frames across a TRILL
network. RBs with higher priorities are selected as root bridges (or tree roots) of TRILL distribution trees, multiple tree roots
are advisable in order to load share traffic based on VLANs. The number of distribution trees is decided by the highest
priority RB and this number will be pushed down to all other RBs.
TRILL fabric
VLAN 150
VLAN 151
VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM
Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Servers
TRILL timers
HP recommends TRILL timers remain at their default values for production deployments. In lab and test environments,
failover might speed up at the expense of higher CPU, refer to TRILL configuration guides of the appropriate product for
guidance on tweaking timers.
4
Architecture guide | Guidelines for deploying TRILL in an HP data center
5
Architecture guide | Guidelines for deploying TRILL in an HP data center
L3 routers
Spine switches
TRILL fabric
10/40G
interconnects
Leaf switches
VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM
Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Servers
There are two variations to the typical TRILL deployment architecture: Distributed and consolidated spines.
Distributed spines
The design in figure 7 is typically used with fixed port spine switches and multiple 10G interconnects. Server PODs with leaf
switches may be replicated horizontally as the network grows.
L3 routers
2 x 5900s (IRF) 2 x 5900s (IRF) 2 x 5900s (IRF) 2 x 5900s (IRF) 2 x 5900s (IRF) 2 x 5900s (IRF)
VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM
Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor
6
Architecture guide | Guidelines for deploying TRILL in an HP data center
Consolidated spines
The design in figure 8 is typically used with modular chassis-based switches such as the HP FlexFabric 11900 or 12900 and
10G or 40G interconnects for a higher performance but even simpler network. Fixed port 5900 switches may also be used if
desired. Server PODs with leaf switches may be replicated horizontally as the network grows.
Figure 8. Consolidated spine network design
L3 routers
TRILL fabric
10 or 40G
interconnects
TRILL
leaf switches
2 x 5900s (IRF) 2 x 5900s (IRF) 2 x 5900s (IRF) 2 x 5900s (IRF) 2 x 5900s (IRF) 2 x 5900s (IRF)
VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM
Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor
Note:
Always refer to the product quick specs for hardware performance specifics such as MAC table sizes, forwarding rate,
bandwidth oversubscription calculations, and to determine what the appropriate products to be used are.
7
Architecture guide | Guidelines for deploying TRILL in an HP data center
TRILL fabric
TRILL leaf switches
Customers who do not require high availability for server uplinks may also choose to connect their servers into TRILL leaf
switches without multihoming enabled.
Customers should refer to their hypervisor/virtualization vendor for host configuration/deployment details.
8
Architecture guide | Guidelines for deploying TRILL in an HP data center
L3 routers
VRRP master VRRP backup
TRILL fabric
VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM
Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor Servers
TRILL Fabric
TRILL spine switches
9
Architecture guide | Guidelines for deploying TRILL in an HP data center
• interface Ten-G1/0/1
port link-mode bridge
• Simplify TRILL deployment and description ToTRILLRB
Dedicated VLAN for
troubleshooting by dedicating VLAN 1 undo stp enable
TRILL trunk ports
to TRILL trunk ports trill enable
trill link-type trunk
• Above configuration shows default VLAN 1 being used
• interface Ten-G1/0/4
• Remove VLAN used by TRILL trunk port link-mode bridge
ports on TRILL access ports
description ToServer
Minimize VLANs on • Only the required VLANs should be
permitted on TRILL access ports with port link-type trunk
TRILL access ports to
servers 802.1Q trunking to servers, this would undo port trunk permit vlan 1
prevent servers from receiving port trunk permit vlan 150 to 151
unnecessary broadcasts and
undo stp enable
consuming server resources
trill enable
• interface Ten-G1/0/4
port link-mode bridge
description ToServer
• If required, it is also possible to
Supporting 4K VLANs support 4K VLANs to servers by port link-type trunk
on TRILL access ports preventing TRILL hello frames from undo port trunk permit vlan 1
to servers being received or sent with the port trunk permit vlan 2 to 4094
following configuration
undo stp enable
trill enable
trill link-type access alone
10
Architecture guide | Guidelines for deploying TRILL in an HP data center
• <Spine1>
trill
tree-root priority 35000
• Implement customized TRILL trees calculate 2
Customized TRILL nicknames to simplify TRILL nickname 0001
nicknames troubleshooting when using display
commands • <Spine2>
trill
tree-root priority 34000
nickname 0002
• interface Bridge-Aggregation1
undo stp enable
• Enable LACP MAD on IRF switches to link-aggregation mode dynamic
LACP MAD on IRF
offset the risk of IRF virtual device
switches
partition mad enable
trill enable
trill link-type trunk
11
Architecture guide | Guidelines for deploying TRILL in an HP data center
TRILL fabric
Leaf 1
Spine 1
sysname Spine1
#
trill
tree-root priority 35000
trees calculate 2
graceful-restart
nickname 0001
#
lldp global enable
#
vlan 1
#
vlan 1000 to 4094
#
stp global enable
#
interface M-GigabitEthernet0/0/0
ip address 192.168.0.1 255.255.255.0
#
interface Ten-GigabitEthernet1/0/1
description ToLeaf1
undo stp enable
port link-mode bridge
trill enable
trill link-type trunk
#
interface Ten-GigabitEthernet1/0/2
description ToLeaf2
undo stp enable
port link-mode bridge
trill enable
trill link-type trunk
#
interface Ten-GigabitEthernet1/0/3
description ToLeaf3
undo stp enable
port link-mode bridge
trill enable
trill link-type trunk
#
interface Ten-GigabitEthernet1/0/24
description ToL3Routers
12
Architecture guide | Guidelines for deploying TRILL in an HP data center
Leaf 1
sysname Leaf1
#
irf domain 1
# domain IDs should differ for each RB
irf mac-address persistent timer
irf auto-update enable
undo irf link-delay
irf member 1 priority 32
#
trill
graceful-restart
nickname 0011
#
lldp global enable
#
vlan 1
#
vlan 150
name VM
#
vlan 151
name VMkernel
#
vlan 1000 to 4094
#
irf-port 1/1
port group interface Ten-GigabitEthernet1/0/45
port group interface Ten-GigabitEthernet1/0/46
#
irf-port 2/2
port group interface Ten-GigabitEthernet2/0/45
port group interface Ten-GigabitEthernet2/0/46
#
stp global enable
#
interface M-GigabitEthernet0/0/0
ip address 192.168.0.11 255.255.255.0
#
interface Ten-GigabitEthernet1/0/1
description ToSpine1
undo stp enable
port link-mode bridge
trill enable
trill link-type trunk
#
interface Ten-GigabitEthernet2/0/1
description ToSpine2
undo stp enable
port link-mode bridge
trill enable
trill link-type trunk
#
interface Bridge-Aggregation1
description ToLeaf2
13
Architecture guide | Guidelines for deploying TRILL in an HP data center
14
Architecture guide | Guidelines for deploying TRILL in an HP data center
Additional links
For more information refer to the TRILL configuration guide of the specific product.
HP 12900 configuration guide
HP 11900 configuration guide
HP 5900 configuration guide
Learn more at
hp.com/networking
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 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.