Trunk-120 Course Introduction

Revision 0318 1-1

Trunk-120 Course Introduction

Revision 0318 1-2

Trunk-120 Course Introduction

Revision 0318 1-3

Trunk-120 Course Introduction

Revision 0318 1-4

Trunk-120 Course Introduction

Revision 0318 1-5

Trunk-120 Course Introduction

Revision 0318 1-6

Trunk-120 Course Introduction

Revision 0318 1-7

Trunk-120 Introduction to Brocade Gen6 Hardware

Footnote 1: For a course to be marked as completed all non-optional course elements

must be completed

Revision 0318 1-8

Trunk-120 Course Introduction

Revision 0318 1-9

Trunk-120 Course Introduction

Revision 0318 1 - 10
Trunk-120 Course Introduction

Revision 0318 1 - 11
Trunk-120 Course Introduction

Revision 0318 1 - 12
Trunk-120 Trunking

Revision 0318 2-1

Trunk-120 Trunking

Revision 0318 2-2

Trunk-120 Trunking

Revision 0318 2-3

Trunk-120 Trunking

The routing database determines how frames are routed from input port to output port when
going to the next destination. Fabric Shortest Path First (FSPF) puts available equal cost
routes in the routing data base. One output port in the trunk group is put into the routing
data base. When a communication between two end devices in a fabric is assigned a route
through a trunk, the ASIC of the assigned trunk group port will be the same ASIC as all ports
in the trunk group. This ASIC will multiplex frames across ISLs in the trunk group and
maintain in-order delivery. The ASIC will send a frame down each link to determine the links
latency. These individual link latency calculations will be used to maintain in-order delivery.
If some ports in a trunk group have QoS enabled and some ports have QoS disabled, the
two different trunks are formed: one with QoS enabled and one with QoS disabled.

Revision 0318 2-4

Trunk-120 Trunking

Footnote 1: Automatically creates ISL trunks using from 2 to 8 ISLs when the switches are
connected and all trunking requirements are met.

Revision 0318 2-5

Trunk-120 Trunking

Switches are shipped with Trunking enabled on all ports. To use Trunking, you must first
install the Brocade Trunking license. Trunking is enabled automatically when the Trunking
license is activated and ports are reinitialized. Trunks are easily managed using either
Fabric OS CLI commands or Web Tools.
Trunk port-groups are ASIC specific and are discussed in more detail in subsequent slides.
8, 16 and 32 Gbps port groups include: ports 0-7; 8-15; and so on
• The Condor4 ASIC is the foundation for the Brocade Gen6 32 Gbps Fibre Channel
products, such as the X6-4 and X6-8 directors as well as the G620 switch
• The Condor 3 ASIC is the foundation for the Brocade Gen5 16 Gbps products, such
as the DCX 8510-4 and DCX 8510-8 directors as well as the 6520, 6510 and 6505
switches.
Long distance trunks must be set to the same distance.
See the Brocade Fabric OS Administrators Guide for additional information.

Revision 0318 2-6

Trunk-120 Trunking

With ASIC trunking in effect, 8 ISLs are aggregated into a single logical ISL capable of up to
256 Gbps aggregate bandwidth. Frames entering the logical pipe are allocated to a
predetermined port which happens to be the lowest back ASIC port in the port group. If that
port is busy, they are allocated to another predetermined port. When the bandwidth of the
pipe is fully utilized the frames are evenly distributed. When the aggregate bandwidth of the
logical pipe is not fully utilized and the 1st predetermined port is free, the frames do not
need to be evenly distributed. Calculated time differentials are needed to maintain in-order
delivery of frames.
If traffic patterns involve large sequences of frames and high bandwidth utilization, then the
frame allocation across the ISLs in the trunk begins to evenly distribute frames across the
ISLs.
The predictable way frames are allocated to ASIC trunk groups enables non-disruptive loss
of trunk master behavior which is also referred to as Pseudo-Master Trunking.

Revision 0318 2-7

Trunk-120 Trunking

Dynamic Path Selection (DPS) is exchange-based routing where exchanges or

communications between end devices in a fabric are assigned to egress ports in ratios
proportional to the potential bandwidth of the ISL or trunk group.
When there are multiple routes to a destination, the input traffic will be distributed across the
different routes in proportion to the bandwidth available on each of the routes. This improves
utilization of the available routes, thus reducing possible congestion on the routes. Every
time there is a change in the network (which changes the available routes), the input traffic
can be redistributed across the available routes. This is a very easy and non-disruptive
process when the Exchange-based Routing Policy is engaged.
Exchanges in the example depicted on this slide are allocated based on the primary criteria:
link cost and secondary criteria: potential bandwidth. The potential bandwidth allocation
depicted in this example yields flow allocations of 3:1.

Revision 0318 2-8

Trunk-120 Trunking

The switchshow commands shows trunk groups associated with ports 0 – 5 and 6-7 with
the master port of the individual trunk groups noted. The remaining ports in the trunk groups
are the non-master ports. It should also be noted that only one trunk group represents the
principal ISL path.

Revision 0318 2-9

Trunk-120 Trunking

When the Trunk Master is disabled another pre-determined port takes over the role
without fabric disruption.

Note – Gen6 products use a starting deskew value of 1, Gen5 and older products use a
starting deskew value of 15. Deskew value is discussed on the next slide.

Example from 6510 Gen5 switch:

6510_Edge:FID128:admin> trunkshow
1: 9-> 9 10:00:c4:f5:7c:0e:c0:7c 2 deskew 15 MASTER
8-> 8 10:00:c4:f5:7c:0e:c0:7c 2 deskew 16

Revision 0318 2 - 10
Trunk-120 Trunking

Footnote 1: Gen6 products use 1 as the minimum deskew value, Gen5 and older products
use 15. The difference in latency (typically due to cable length) between the ISLs in a trunk
determines the deskew value. This is needed for timing purposes so that delivery of frames
across the trunk can be ensured. The shortest ISL is selected as the base and is assigned a
deskew value of 10 nanoseconds (ns) for Gen6 products and 150ns for Gen5 and older
products. The deskew values are expressed (shown in all command displays) by dividing
the time value by 10. Example: A deskew value of 10ns is shows as 1 (10/10) and a deskew
value of 150ns is shown as 15 (150/10).

The first ISL in the trunk to initialize is selected as the trunk master. The length of the cable
is not a consideration when selecting the master. The deskew values for the other ISLs in
the trunk will be calculated from the base ISL and may have a higher value. Each switch
connected by the ISL will have a deskew value since each has a separate transmit line to
the other. Due to the signal quality/optical media, cables that are identified as the same
length may have a different deskew value. For example, one cable may have a deskew
value of 1 and a cable of the same length may calculate to be 3. This is not a problem since
deskew is a true measurement of its transmission capabilities.

Revision 0318 2 - 11
Trunk-120 Trunking

Footnote 1: Light in a vacuum travels much faster, but in optical cable the rate is about 5
ns/meter. 5ns/meter multiplied by 30 meters is 150 ns.

A two meter difference is approximately equal to one (10ns) deskew unit.

Differences greater than 30 meters could introduce performance degradation
For Gen5 and older products, since the shortest ISL is set to a deskew of 15 (150ns), an ISL
with a difference of 30 meters has a deskew of approximately 30
A 400 meter difference would yield a deskew value of 215.

Revision 0318 2 - 12
Trunk-120 Trunking

trunkshow
• Displays each trunk group
• Displays which local port is connected to which remote port
• Displays WWN of the other switch
• Displays deskew values and identifies the trunk master port
switchshow
• Displays the master port (trunk master) and each non-master port
• Displays the WWN of connected switch to trunked ports
islshow
• Displays bandwidth information associated with each trunk group
switchcfgtrunk
• Used to configure trunking to be ON or OFF on all ports on switch
portcfgtrunkport
• Used to configure trunking per port as either ON or OFF, default is ON
portcfgshow
• Displays port configuration information including trunk ON/OFF status

Revision 0318 2 - 13
Trunk-120 Trunking

trunkdebug port1 port2

• Tests specified ports in trunk group and reports trunking status. Possible trunkdebug
outputs include:
• Switch does not support trunking
• Trunking license required
• port port_id is not E_Port
• port port_id trunking disabled
• port port_id speed is not 2G, 4G, 8G, 10G, or 16G
• port port_id and port port_id are not in same port group
• port port_id and port port_id connect to different switches
• port port_id and port port_id connect to the switch WWN
• port port_id is not a trunking port due to: E_Port being disabled, or trunking might be
disabled at remote port
• port port_id and port port_id cannot trunk, please check link length to make sure
difference is less than 400 m

Revision 0318 2 - 14
Trunk-120 Trunking

Trunk master selection is not related to deskew.

Trunk master selection is based on the ASICs internal port values, it is predictable. It is
dependent on distance and quality of the link and its associated connection points.
The switches in this example have multiple trunk groups between them. Notice that the
trunk master is not always the lowest port number in the group nor is it related to the
deskew value.

Revision 0318 2 - 15
Trunk-120 Trunking

Revision 0318 2 - 16
Trunk-120 Trunking

The portcfgtrunkport command is used to turn on or off trunking on one port, specified
by port number. The last parameter indicates on or off (1 for on and 0 for off).
Usage: portCfgTrunkPort [SlotNumber/]PortNumber Mode
Mode: 1 - Configure port to be Trunking capable
0 - Configure port to be Trunking incapable

The switchcfgtrunk command is used to turn on or off trunking capability for the whole
switch:
Usage: switchCfgTrunk Mode
Mode: 0 - Configure ports to be Trunking incapable
1 - Configure ports to be Trunking capable

Revision 0318 2 - 17
Trunk-120 Trunking

This command has the following operands:

port1 Specify the port index number of port 1. Use the switchshow command to view the
index numbers for a port. This operand is required.
port2 Specify the port index number of port 2. Use the switchshow command to view the
index numbers for a port. This operand is required.

Example of debugging a trunk connection:

switch:admin> trunkdebug 43 44
Switch does not support trunking
switch:admin> trunkdebug 62 63
port 62 and 63 are trunked together

Director command syntax:

trunkdebug: area_number1 area_number2

Revision 0318 2 - 18
Trunk-120 Trunking

Revision 0318 2 - 19
Trunk-120 Trunking

Revision 0318 2 - 20
Trunk-120 Trunking

Revision 0318 2 - 21
Trunk-120 Trunking

This page left intentionally blank

Revision 0318 2 - 22