Cisco Cisco Nexus 2224TP GE Fabric Extender Weißbuch
© 2014 Cisco | IBM. All rights reserved.
Page 7
Fabric Connectivity Options
The Cisco Nexus B22 for IBM creates a distributed, modular chassis with the Cisco Nexus parent switch after a
fabric connection has been made over standard 10-Gbps cabling. This connection can be accomplished using
any of the following types of interconnects:
fabric connection has been made over standard 10-Gbps cabling. This connection can be accomplished using
any of the following types of interconnects:
Cisco passive direct-attach cables (1m, 3m, or 5m)
Cisco active direct-attach cables (7m or 10m)
Cisco standard Enhanced Small Form-Factor Pluggable (SFP+) optics (SR, LR, and ER)
Cisco Fabric Extender Transceivers (FET modules)
After the fabric links have been physically established, the logical configuration of the links must be established.
The fabric links to the Cisco Nexus B22 for IBM can use either of two connection methods:
The fabric links to the Cisco Nexus B22 for IBM can use either of two connection methods:
Statically pinned fabric interface connection
Port Channel fabric interface connection
Statically Pinned Fabric Interface Connection
Static pinning is the default method of connection between the fabric extender and the Cisco Nexus parent switch.
In this mode of operation, a deterministic relationship exists between the host interfaces and the upstream parent;
up to eight fabric interfaces can be connected. These fabric interfaces are equally divided among the 16 server-
side host ports. If fewer fabric ports are allocated, more server ports are assigned to a single fabric link. The
advantage of this configuration is that the traffic path and the amount of allocated bandwidth are always known for
a particular set of servers.
In this mode of operation, a deterministic relationship exists between the host interfaces and the upstream parent;
up to eight fabric interfaces can be connected. These fabric interfaces are equally divided among the 16 server-
side host ports. If fewer fabric ports are allocated, more server ports are assigned to a single fabric link. The
advantage of this configuration is that the traffic path and the amount of allocated bandwidth are always known for
a particular set of servers.
Since static pinning will group host-side ports into individual fabric links, you should understand how ports are
grouped. The size of the port groups is determined by the number of host ports divided by the max link
parameter value. For example, if the max link parameter is set to 2, eight host ports would be assigned to each
link. The interfaces will be grouped in ascending order starting from interface 1. Thus, interfaces 1 to 8 will be
pinned to one fabric link, and interfaces 9 to 16 will be pinned to a different interface (Table 5).
grouped. The size of the port groups is determined by the number of host ports divided by the max link
parameter value. For example, if the max link parameter is set to 2, eight host ports would be assigned to each
link. The interfaces will be grouped in ascending order starting from interface 1. Thus, interfaces 1 to 8 will be
pinned to one fabric link, and interfaces 9 to 16 will be pinned to a different interface (Table 5).
Table 5
Interface Assignment with Two Fabric Links
Interface
Fabric Link
1, 2, 3, 4, 5, 6, and 7
Fabric link 1
8, 9, 10, 11, 12, 13, and 14
Fabric link 2