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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Interface Allocation: N7K-M132XP-12 <strong>and</strong> L<br />

Interfaces are assigned on a per-VDC basis <strong>and</strong> cannot be shared acr<strong>os</strong>s VDCs. After an<br />

interface has been assigned to a VDC, all subsequent configuration is done from within that<br />

VDC. The N7K-M132XP-12 <strong>and</strong> L require allocation in port groups of four to align ASIC<br />

resources:<br />

• Ports are assigned on a per-VDC basis <strong>and</strong> cannot be shared acr<strong>os</strong>s VDCs.<br />

• After a port has been assigned to a VDC, all subsequent configuration is done from<br />

within that VDC.<br />

• N7K-M132XP-12 <strong>and</strong> L require allocation in port groups of four to align ASIC<br />

resources.<br />

Figure 1-17 shows the interface allocation for the N7K-M132XP-12 <strong>and</strong> L modules.<br />

Figure 1-17. N7K-M132XP-12 <strong>and</strong> L Module Interface Allocation<br />

Interface Allocation: N7K-F132XP-15<br />

Interfaces are assigned on a per-VDC basis <strong>and</strong> cannot be shared acr<strong>os</strong>s VDCs unless using<br />

FCoE. When an interface has been assigned to a VDC, all subsequent configuration is done<br />

from within that VDC. The N7K-F132XP-15 requires allocation in port groups of two to<br />

align ASIC resources:<br />

• Ports are assigned on a per-VDC basis <strong>and</strong> cannot be shared acr<strong>os</strong>s VDCs unless<br />

using FCoE.

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

Saved successfully!

Ooh no, something went wrong!