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.

Figure 2-9. FabricPath Topology<br />

As discussed previously, FabricPath IS-IS can automatically assign a unique switch ID;<br />

however, these values are usually statically assigned via the network administrator. The<br />

switch ID is a 12-bit identifier, giving the administrator 4094 unique switch IDs to cho<strong>os</strong>e<br />

from. The switch ID can be configured, as shown in Example 2-74.<br />

Example 2-74. Configuring the Switch ID<br />

Click here to view code image<br />

! Configure Fabric Path Switch ID on fp-spine-1<br />

fp-spine-1(config)# fabricpath switch-id 1<br />

! Configure Fabric Path Switch ID on fp-spine-1<br />

fp-spine-2(config)# fabricpath switch-id 2<br />

! Configure Fabric Path Switch ID on fp-edge-3<br />

fp-edge-3(config)# fabricpath switch-id 3<br />

! Configure Fabric Path Switch ID on fp-edge-4<br />

fp-edge-4(config)# fabricpath switch-id 4<br />

After defining the switch IDs for the sample topology, you must next define which VLANs<br />

will be transported through the FabricPath network. VLANs must be defined <strong>and</strong> configured<br />

as FabricPath VLANs on each switch. The configuration in Example 2-75 is used to<br />

configure a set of VLANs as a FabricPath VLANs.

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

Saved successfully!

Ooh no, something went wrong!