22.05.2017 Views

nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

Nexus Switching 2nd Edition

Nexus Switching 2nd Edition

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

FabricPath Unicast Route Table for Topology-Default<br />

0/1/0, number of next-hops: 0<br />

via ---- , [60/0], 4 day/s 00:16:21, local<br />

1/2/0, number of next-hops: 1<br />

via Po1, [115/20], 0 day/s 01:11:34,<br />

isis_fabricpath-default<br />

1/3/0, number of next-hops: 1<br />

via Eth2/5, [115/40], 1 day/s 00:41:32,<br />

isis_fabricpath-default<br />

1/4/0, number of next-hops: 1<br />

via Eth2/7, [115/40], 1 day/s 00:41:30,<br />

isis_fabricpath-default<br />

You can see that to reach SID 4, traffic will be sent out Ethernet 2/7. This process would be<br />

repeated on all intermediate FabricPath switches, until the frame arrives at SID 4 or the<br />

TTL in the FabricPath header is decremented to zero.<br />

vPC+<br />

FabricPath is designed to interoperate with other Layer 2 technologies such as vPC. vPC+<br />

provides extensions to vPC for connecting classical Ethernet devices to a FabricPath cloud.<br />

vPC+ enables the entire vPC domain to be seen as one virtual switch by the FabricPath<br />

network. vPC+ enables classical Ethernet devices such as h<strong>os</strong>ts or STP domains to<br />

communicate with each other through the cloud. With vPC+, the FabricPath cloud is seen as<br />

a single L2 bridge for STP purp<strong>os</strong>es.<br />

vPC+ can also enables FabricPath nodes to combine as a single virtual switch for the<br />

purp<strong>os</strong>e of creating active/active First Hop Redundancy Protocols (FHRPs) such as HSRP<br />

<strong>and</strong> GLBP to operate in an active/active fashion. These protocols are discussed in detail in<br />

Chapter 3, “Layer 3 Support <strong>and</strong> Configurations.”<br />

Caution<br />

The following points should be kept in mind as they relate to vPC+:<br />

• The vPC Peer-Link <strong>and</strong> all vPC members must reside on F1, F2, or F2e linecards.<br />

• Peer-Switch is not recommended in a vPC+ domain configuration.<br />

• The vPC+ should be configured with STP priorities low enough to ensure that they<br />

become the root bridge of the connected L2 domain.<br />

Configuring vPC+<br />

Building upon the FabricPath topology <strong>and</strong> configuration used so far, now consider another<br />

device that can connect in via vPC+ configuration, as shown in Figure 2-11.<br />

First, enable the vPC as done earlier in this chapter. The steps that must be completed<br />

follows:

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!