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.

egular monthly basis as it could in years past. Downtime windows are becoming<br />

shorter <strong>and</strong> further between. The next-generation infrastructure must provide high<br />

availability through network design <strong>and</strong> product selection. The next-generation design<br />

must also be incrementally deployable so that long maintenance windows are not<br />

required to migrate services to the new design.<br />

• Flexibility: Currently, Acme, Inc., has faced several challenges related to the capacity<br />

of its data center; many of the regions are at full capacity with space <strong>and</strong> power<br />

consumption at nearing 100 percent. Clustering applications require L2 adjacencies<br />

that cannot be accomplished unless the servers physically reside in the same region of<br />

the data center. In addition, recent efforts to optimize data center operations <strong>and</strong> lower<br />

c<strong>os</strong>ts have resulted in large-scale server virtualization efforts. These virtualization<br />

efforts have led to challenges associated with the L2 adjacency requirements of its<br />

virtualization solution. Acme, Inc., would like the future design to provide the ability<br />

to extend VLANs between regions of the data center <strong>and</strong> provide future abilities of<br />

extending VLANs to its disaster recovery data center. Fibre Channel over Ethernet<br />

(FCoE) is also something that Acme will be evaluating over the next several months,<br />

<strong>and</strong> it would like the new solution to provide this functionality.<br />

The Design<br />

To accomplish the design goals, Acme, Inc., has ch<strong>os</strong>en the Cisco Nexus lines of switches<br />

because of the alignment that exists between Acme’s design goals <strong>and</strong> the Nexus product<br />

family.<br />

The existing Core Layer will remain intact because it currently meets all the Campus<br />

connectivity requirements. New linecards will be installed to connect to the aggregation<br />

switches at 10 Gbps.<br />

The aggregation layer will receive the m<strong>os</strong>t dramatic change; the Catalyst 6500s will be<br />

replaced with Nexus 7010 switches based on the current <strong>and</strong> future capacity dem<strong>and</strong>s of<br />

Acme, Inc. vPC technology will be leveraged to enable an active/active topology <strong>and</strong><br />

eliminate any Spanning Tree Protocol (STP) blocked links.<br />

The existing access switches will stay in place until they are fully depreciated <strong>and</strong> all of the<br />

h<strong>os</strong>ts have been migrated off of them. New access layer 5596UPs have been ch<strong>os</strong>en to<br />

provide next-generation server connectivity. Each region switch pair within the data center<br />

will be replaced with a pair of Nexus 5596UPs <strong>and</strong> will aggregate Nexus 2248 <strong>and</strong> 2232<br />

Fabric Extenders that are placed strategically in the top of various racks within the data<br />

center.<br />

Migration Plan<br />

Acme’s business is such that it cannot afford extended outage windows for the migration to<br />

occur <strong>and</strong> therefore has approved several smaller outage windows of approximately 1 hour<br />

each. The IT management team would like to see the actual impact of the changes to be made<br />

to be considerably less than 1 hour but are preparing for worst-case scenari<strong>os</strong>. There also<br />

must be an easy back-out strategy with each change made to the environment to eliminate as<br />

much risk as p<strong>os</strong>sible. This project has high visibility within the entire organization <strong>and</strong>

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

Saved successfully!

Ooh no, something went wrong!