Nexus 7000/5000/2000/1000v Deployment Case Studies

Transcription

1

2 Nexus 7000/5000/2000/1000v Deployment Case Studies

3 Session Goal Understand how to design a scalable data center based upon customer requirements How to choose different flavor of the designs using Nexus family. Share Cisco Advanced Services team s experiences in real life deployment case studies. 3

4 Recommended Sessions BRKARC-3470: Cisco Nexus 7000 Hardware Architecture BRKARC-3452: Cisco Nexus 5000/5500 and 2000 Switch Architecture BRKARC-3471: Cisco NX-OS Software Architecture BRKVIR-3013: Deploying and Troubleshooting the Nexus 1000v Virtual Switch BRKDCT-2048: Deploying Virtual Port Channel in NX-OS BRKDCT-2049: Overlay Transport Virtualization BRKDCT-2081: Cisco FabricPath Technology and Design BRKDCT-2202: FabricPath Migration Use Case BRKDCT-2121: VDC Design and Implementation Considerations with Nexus 7000 BRKRST-2509: Mastering Data Center QoS BRKDCT-2214: Ultra Low Latency Data Center Design - End-to-end design approach BRKDCT-2218: Data Center Design for the Small and Medium Business 4

5 Session Agenda Nexus Platform Overview Data Center Design and Considerations Case Study #1: Green Field Data Center Design Case Study #2: Data Center Migration Key Takeaways 5

6 Data Center Drivers Business Agility Regulatory Compliance Security Threats Budget Constraints Business Challenges Technology Trends Cloud Big Data Energy Efficiency Proliferation of Devices 6

7 Data Center Architecture Trends Spectrum of Design Evolution blade1 blade2 slot 1 blade3 slot 2 blade4 slot 3 blade5 slot 4 blade6 slot 5 blade7 slot 6 blade8 slot 7 slot 8 blade1 blade2 slot 1 blade3 slot 2 blade4 slot 3 blade5 slot 4 blade6 slot 5 blade7 slot 6 blade8 slot 7 slot 8 blade1 blade2 slot 1 blade3 slot 2 blade4 slot 3 blade5 slot 4 blade6 slot 5 blade7 slot 6 blade8 slot 7 slot 8 blade1 blade2 slot 1 blade3 slot 2 blade4 slot 3 blade5 slot 4 blade6 slot 5 blade7 slot 6 blade8 slot 7 slot 8 blade1 blade2 slot 1 blade3 slot 2 blade4 slot 3 blade5 slot 4 blade6 slot 5 blade7 slot 6 blade8 slot 7 slot 8 blade1 blade2 slot 1 blade3 slot 2 blade4 slot 3 blade5 slot 4 blade6 slot 5 blade7 slot 6 blade8 slot 7 slot 8 blade1 blade2 slot 1 blade3 slot 2 blade4 slot 3 blade5 slot 4 blade6 slot 5 blade7 slot 6 blade8 slot 7 slot 8 blade1 blade2 slot 1 blade3 slot 2 blade4 slot 3 blade5 slot 4 blade6 slot 5 blade7 slot 6 blade8 slot 7 slot 8 blade1 blade2 slot 1 blade3 slot 2 blade4 slot 3 blade5 slot 4 blade6 slot 5 blade7 slot 6 blade8 slot 7 slot 8 Virtualized Data Center blade1 blade2 slot 1 blade3 slot 2 blade4 slot 3 blade5 slot 4 blade6 slot 5 blade7 slot 6 blade8 slot 7 slot 8 blade1 blade2 slot 1 blade3 slot 2 blade4 slot 3 blade5 slot 4 blade6 slot 5 blade7 slot 6 blade8 slot 7 slot 8 blade1 blade2 slot 1 blade3 slot 2 blade4 slot 3 blade5 slot 4 blade6 slot 5 blade7 slot 6 blade8 slot 7 slot 8 SP and Enterprise Hypervisor Virtualization Shared infrastructure Heterogeneous 1G Edge moving to 10G Nexus 1000v, 2000, 5500, 7000 & UCS Warehouse Scale Layer 3 Edge (ibgp, ISIS) 1000 s of racks Homogeneous Environment No Hypervisor virtualization 1G edge moving to 10G Nexus 2000, 3000, 5500, 7000 & UCS HPC/GRID Layer 3 & Layer 2 No Virtualization iwarp & RCoE Nexus 2000, 3000, 5500, 7000 & UCS 10G moving to 40G Ultra Low Latency High Frequency Trading Layer 3 & Multicast No Virtualization Limited Physical Scale Nexus 3000 & UCS 10G edge moving to 40G 7

8 Cisco Nexus Family High availability (ISSU, Modular OS, Non-Stop Forwarding) Integrated virtualization (VDC, VRF, VLAN, VN-link) Fiber Channel over Ethernet(FCOE) and Fiber Channel(FC) Complete data center class switching portfolio and unified management Nexus 1000V Virtual Switch K Cisco Nexus 1000V x86 Nexus 2000 FEX Nexus 3K Nexus 4K Nexus 5K Nexus 7K NX-OS Data Center Operating System Data Center Network Manager 8

9 Nexus 7000 Platform Overview Next Generation Modular Nexus 7000 and NX-OS 9, 10 & 18 Slot Chassis 15+ Terabit System (18 Slot) Unified Fabric Modular NX-OS Device Virtualization Hitless ISSU Highest Availability Ethernet Switch and Director Class SAN Linecard Modules Supervisor 10G Ethernet M Series 32 Port SFP+ 10G - XL 8 Port X2 10G - XL 1G Ethernet M Series 48 Port 10/100/1000 -XL 48 Port 1G - XL 10G Ethernet F Series 32 Port SFP+ 10G (F1) 48 Port SFP+ 10G (F2) Cisco NX-OS Multi-protocol Operating System Data Center Network Manager (DCNM) 9

10 Nexus 5000/5500 and 2000 Architecture Virtualized Data Center Access Nexus Fixed Ports 10G/FCoE/IEEE DCB Line-rate, Non-blocking 10G 1 Expansion Module Slot Redundant Fans & Power Supplies Nexus 2000/2200 Fabric Extender 48 Fixed Ports 100M/1G (1000 BASE-T) 32 Fixed ports 1G/10G/FCoE/IEEE DCB 4-8 Fixed Port 10G Uplink Distributed Virtual Line Card Nexus Fixed Ports 10G/FCoE/IEEE DCB Line-rate, Non-blocking 10G 2 Expansion Module Slots Redundant Fans & Power Supplies Nexus 5548UP 32 Fixed Ports 1/10G Ethernet or 1/2/4/8 FC Line-rate, Non-blocking 10G FCoE/IEEE DCB 1 Expansion Module Slot IEEE 1588, FabricPath & Layer 3 Capable Redundant Fans & Power Supplies Nexus 5596UP 48 Fixed Ports 1/10G Ethernet or 1/2/4/8 FC Line-rate, Non-blocking 10G/FCoE/IEEE DCB 3 Expansion Module Slot IEEE 1588, FabricPath & Layer 3 Capable Redundant Fans & Power Supplies 10

11 Cisco Nexus 1000V Industry s most advanced software switch for VMware vsphere Support MS Hyper-V Built on Cisco NX-OS Compatible with all switches Compatible with all servers on the VMware Hardware Compatibility List 1000V VSM x 1 VSM on Virtual Machine Nexus 1000V VM VM VM Server Physical Switches vsphere 1000V VSM x 4 Cisco Nexus 1010 VM Nexus 1000V VEM VSM: Virtual Supervisor Module VEM: Virtual Ethernet Module VSM on Nexus 1010 VM VM VM Server Physical Switches vsphere 11

12 Session Agenda Nexus Platform Overview Data Center Design and Considerations Case Study #1: Green Field Data Center Design Case Study #2: Data Center Migration Key Takeaways 12

13 Data Center Architecture Building Blocks Allow customization within blocks while maintain overall architecture Blocks aligned to meeting business and technical requirements 13

14 A Cloud Ready Data Center Architecture Cisco Virtualized Multi-Tenant Data Center Validated reference architecture that delivers a highly scalable, available, secure, flexible, and efficient data center infrastructure. Proven layered approach Reduced time to deployment Reduced risk Increased flexibility Improved operational efficiency 14

15 What Makes Designing Networks for the Data Center Different? Extremely high density of end nodes and switching Power, cooling, and space management constraints Mobility of servers a requirement, without DHCP The most critical shared end-nodes in the network, high availability required with very small service windows Multiple logical multi-tier application architectures built on top of a common physical topology Server load balancing, firewall, other services required 15

16 Hierarchical Design Network Layers Defining the Terms Data Center Core Routed layer which is distinct from enterprise network core Enterprise Network Provides scalability to build multiple aggregation blocks Aggregation Layer Data Center Core Provides the boundary between layer-3 routing and layer-2 switching Point of connectivity for service devices (firewall, LB, etc.) Access Layer Aggregation Layer 3 Links Layer 2 Trunks Provides point of connectivity for servers and shared resources Typically layer-2 switching Access 16

17 Data Center Core Layer Design Core Layer Function & Key Considerations High speed switching &100% layer 3 Fault domain isolation between Enterprise and DC AS / Area boundary Routing table scale Fast routing convergence Data Center Core Aggregation Enterprise Network Layer 3 Links Layer 2 Trunks Access 17

18 Data Center Core Layer Design Commonly Deployed Platform and Modules Platform: Nexus 7K Modules M1-10G LC F2-Series LC M1: L2/L3/L4 with large forwarding tables and rich feature set F2: Low-cost, high density with high performance, low latency and low power Classic layer 3 Core: M1 or F2 Large routing and ACL tables: M1 High density linerate10g: F2 MPLS: M1 Software 4.0 and later* 6.0(1) and later Fabric Connection 80G 480G* L3 IPv4 Unicast 128K/1M 32K L3 IPv4 Multicast 32K 16K L3 IPv6 Unicast Up to 350K 32K L3 IPv6 Multicast 16K 8K ACL Entries 128K 16K MPLS LISP and OTV 18

19 Data Center Aggregation Layer Design Virtualized Aggregation Layer provides L2 / L3 boundary Access layer connectivity point: STP root, loop-free features Service insertion point Network policy control point: default GW, DHCP Relay, ACLs Data Center Core Aggregation Enterprise Network Access 19

20 Data Center Aggregation Layer Design Commonly Deployed Platform and Modules Platform: N7K/N5K Features(L3, OTV etc.) Scalability (routing/mac table) Performance and port density M1-10G LC F1-Series LC F2-Series LC N5500 with L3 Min. Software 4.0* 5.1(1) 6.0(1) 5.0(3)N1(1) Fabric Connection 80G 230G 480G* - L3 IPv4 Unicast 128K/1M - 32K 8K L3 IPv4 Multicast 32K - 16K 2K MAC Entries 128K 16K (per SOC) 16K (per SOC) 32K FEX Support Yes* No Yes Yes L2 Portchannel 8 active 16 active 16 active 16 active LISP and OTV FabricPath FCOE Support 20

21 Data Center Aggregation Layer Design Key Design Considerations Data Center physical infrastructure POD design & cabling infrastructure Size of the layer 2 domain Oversubscription ratio Traffic flow No. of access layer switches to aggregate Scalability requirement Service insertion Service chassis vs. appliance Firewall deployment model Load balancer deployment model Data Center Core Aggregation Access Enterprise Network 21

22 Data Center Access Layer Design Access Layer & Virtualized Edge Access Layer provides Hosts connectivity point Mapping from virtual to physical L2 Services: LACP, VLAN Trunking Virtualized Edge provides Virtual host connectivity point Virtual extension of access services Network policy enforcement point 22

23 Data Center Access Layer Design Access Layer Key Considerations & Commonly Deployed Platform Physical infrastructure TOR vs. MoR Server Types 1 G vs 10G A/A or A/S NIC Single attached Oversubscription ratio No. of servers and uplinks Virtual Access Requirements Virtual Machine Visibility Virtual Machine Management Boundary N5548/N5596 N5010/N5020 N7 F-Series LC Fabric Throughput 960G/1.92T 520G/1.04T 230G/480G Port Density 48/96 26/52 32/48 per LC No. of Vlans MAC Entries 32K 16K 16K (per SOC) No. of FEXs (F2 only) 1G FEX Ports /48 per LC 10G FEX Ports /48 per LC 8G Native FC Ports 48/96 6/12 - FabricPath 23

24 Data Center Interconnect Design Data Center Interconnect Drivers DC to DC IP connectivity DC to DC LAN extension Workload scaling with vmotion WAAS Main Data Center L3 L2 IP Routed Service EoMPLS EoMPLSoGRE L2 L3 Backup Data Center WAAS GeoCluster L2 L2 Disaster recovery SAN DWDM/ CWDM SAN Non-disruptive DC migration Storage extension and replication FC FC Storage Storage 24

25 Data Center Interconnect Design DCI LAN Extension Key Considerations STP domain isolation Multihoming and loop avoidance Unknown unicast flooding and broadcast storm control FHRP redundancy and localization Scalability and convergence time Three Nexus based options OTV vpc Fabric Path 25

26 Session Agenda Nexus Platform Overview Data Center Design and Considerations Case Study #1: Green Field Data Center Design Case Study #2: Data Center Migration Key Takeaways 26

27 Case Study #1 Customer Business Challenges A leading online higher education institution More than 500,000 students, 24,000 faculty members Approximately 1200 servers and 600 VMs across 5 data centers Current data centers reach the limit of switching, power, and cooling capacity Business decision made to build two new green field data centers to consolidate and provide DR capability Data Center High Level Requirements x10g based virtualized next generation data center architecture No STP blocking topology Firewall protection for secured servers Support vmotion within and between data centers Network team gains visibility to VM networking 27

28 Virtualized Access Layer Requirements G capable server connections 30 ESX servers with roughly 600 VMs 800 1G connections for standalone servers, and out of band management network Support both active/active and active/standby NIC teaming configuration Network team manages network, Server team manages server/virtual machines Network policies are retained during vmotion 28

29 Data Center Access Layer Design N2K being remote line card to reduce number of devices to manage Migration to ToR for 10GE servers or selective 1GE server racks if required (mix of ToR and EoR) Mixed cabling environment (optimized as required) Flexible support for Future Requirements... Combination of EoR (End of Row) and ToR (Top of Rack) cabling Nexus 5000/2000 Mixed ToR & EoR 29

30 Access Layer Port Counts & Oversubscription For 10G server off the 5596s Total 10G ports = 20*32 = 640 Server NIC utilization = 50% Total uplink BW = 16*10 = 160G Oversubscription ratio = 160/(640*0.5*10) = 1/20 For 1G server off the 5548s Total 1G ports = 20*48 = 960 Server NIC utilization = 50% Total uplinks BW = 8*10 = 80G Oversubscription ratio = 80/(960x0.5) = 1/6 30

31 N1KV Gains Visibility Into VM Environment Cisco Nexus 1000V Software Based Built on Cisco NX-OS Compatible with all switching platforms Maintain vcenter provisioning model unmodified for server administration; allow network administration of virtual network via familiar Cisco NX-OS CLI VM VM VM VM Nexus 1000V vsphere Nexus 1000V Policy-Based VM Connectivity Mobility of Network and Security Properties Non-Disruptive Operational Model 31

32 Nexus 1000V Uplink Options Mac Pinning UCS Blade Server Environment 3 rd party blade server environment in non-mcec topologies Spanning-Tree (Active/Passive) Channel-group auto mode on mac-pinning Port-Channel with single switch Upstream switches do not support MCEC Single Switch Port-Channel Channel-group auto mode [active passive] Port-channel with two switches Any server connected to upstream switches that supports Multi-Chassis EtherChannel (MCEC) Multi-Chassis EtherChannel Channel-group auto mode [active passive] 32

33 Access Layer Design Highlight Requirement Solution Flexible cabling Ease of management N5K/2K provide mixed ToR & EoR Configurations only done on the 5Ks 1G, 10G server connectivity with active/active, active/standby NIC teaming Straight-through FEX supports all the NIC teaming options Note: EVPC provides flexible server/fex topology vmotion within the Data Center N5K operates in layer 2 only to make larger layer 2 adjacency possible Visibility to VMs N1KV provides network visibility to VM Network team manages network, server team manages server Clear management boundary defined by N1KV 33

34 Aggregation Requirements Facility Drop any server anywhere in the data center L2-L3 Layer 2 domain within data center No STP blocking topology Service Layer Secured zone and non-secured zone FW protection between zones, no FW protection within the zone LB service is required for Web server, server needs to track the client IP High performance FW and LB are required NAM and IPS solution are also required 34

35 Physical Infrastructure and Network Topology Physical to Logical Mapping 35

36 Aggregation Oversubscription Ratio Large layer 2 domain with single pair of 7Ks Worse Case Calculation Assume all the traffic is northsouth bound Assume 100% utilization from the 5Ks All the ports operated in dedicated mode 36

37 Service Integration at Aggregation Layer Service chassis vs. Appliance Virtual Service with Nexus 1000V Virtual/Cloud Data Center APP VDC-1 OS Hypervisor VDC-2 Virtual Service Node (VSN) Virtual appliance form factor Dynamic instantiation/provisioning Service transparent to VM mobility Support scale-out Large scale multitenant operation 37

38 Service Integration-Physical Design High performance solution ASA5585 Firewall and IPS ACE30 module Low TCO 6500 repurpose Most scalable NAM module inside service chassis Available slot for future expansion 38

39 Firewall Logical Deployment Model Bridging Router GW Vlan Vlan 31 Transparent Mode Pros : Easy to implement Cons: 8 bridge-group per context Routing Router GW Router GW Vlan 10 FW Vlan 11 Vlan 40 Vlan Routing Mode Router GW Vlan 10 FW GW Vlan 20 Pros: More scalable GW Cons: Configuration complexity VRF sandwich VDC sandwich Nexus (external VDC) vlan100 FW Vlan 10 GW Nexus (internal VDC) GW Vlan Vlan 11 Nexus (external vlan100 Vrf) FW Vlan 30 Vlan 10 Vlan 40 GW Nexus (internal Vrf) GW GW Vlan Vlan 11 Vlan 41 GW Vlan

40 Load Balancer Logical Deployment Model Transparent Mode Pros: Ease of deployment and multicast support Cons: 8 bridge-group per context Routing Mode Pros: Separate STP domain Cons: No routing protocol support One Arm Mode Pros: Non-LB traffic bypass the LB Cons: SNAT or PBR required Bridging Routing One Arm Vlan 10 Router Router Router Router LB Vlan 201 GW GW GW GW Nexus GW Vlan 30 Vlan Vlan 10 LB Vlan 11 Vlan Vlan Vlan GW Vlan Vlan 11 LB GW GW Vlan 20 GW Vlan

41 Service Integration Logical Design VRF sandwich design Three VRF created on Agg N7K Server default gateway is Agg N7k No VRF route leaking LB in transparent mode Tracking client IP is possible Multicast application behind LB is possible Two ACE contexts plus admin context FW in routing mode FW provides routing between VRFs Two FW contexts plus admin and system context 41

42 Spanning Tree Recommendations N Network port E Edge or portfast port type - Normal port type Data Center Core B R BPDUguard Rootguard Aggregation Primary Root Primary vpc HSRP ACTIVE R R R N - vpc Domain R N R R R Secondary vpc HSRP STANDBY Secondary Root - R L Loopguard Layer 3 Layer 2 (STP + Rootguard) Access L E B E B E B E B E B Layer 2 (STP + BPDUguard) 42

43 vpc Best Practice Features Feature Benefit Overview vpc auto-recovery (reload restore) Increase High-availability allows the one vpc device to assume STP / vpc primary role and bring up all local vpcs in case other vpc peer device is down after DC power outage vpc Peer-Gateway Service continuity Allows a vpc switch to act as the active gateway for packets addressed to the peer router MAC vpc orphan-ports suspend Increase High-availability When vpc peer-links go down, vpc secondary shuts down all the vpc member ports as well as orphan ports. It avoids single attached devices like FW,LB or NIC teamed device get isolated during vpc peer-link failure vpc ARP SYNC Improve Convergence time Improve Convergence for Layer 3 flows after vpc peer-link is UP vpc Peer-Switch Improve Convergence time Virtualize both vpc peer devices so they appear as a unique STP root BRKDCT-2048: Deploying Virtual Port Channel in NX-OS 43

44 Aggregation Layer Design Highlight Requirement Solution Drop any server anywhere in the DC vmotion within the DC No STP blocking Topology Single pair of 7Ks provide data center wide layer 2 domain Double sided vpc between 7K and 5K eliminating blocking ports Data Center Core Enterprise Network FW protection between secure zone and non-secure zone Web servers require load balancing service FW virtualization and VDC sandwich design to provide logical separation and protection LB in transparent mode provides service per Vlan basis Aggregation Layer 3 Links Layer 2 Trunks High throughput services are required and future scalability Mixed of service chassis and appliance design is able to provide flexible and scalable service choices Access Low subscription ratio (target 15:1) M1 10G line cards configured in dedicated mode to provide lower subscription ratio 44

45 Core Layer Design Nexus 7010 with Redundant M1 line cards 10G layer 3 port channels to Aggregation switches OSPF as IGP Data Center Core Enterprise Network Inject default into data center Fault domain separation via BGP ebgp peering with enterprise network Aggregation Layer 3 Links Layer 2 Trunks ebgp peering with remote data center DC Interconnects are connected onto the Core N7Ks Access 45

46 DCI Requirements and Design Choices Requirements L2 connectivity to provide workload scaling with vmotion OTV VDC OTV VDC IGP + PIM Peering IGMPv3 OTV VDC OTV VDC Data replication between the data centers PIM Interface L3 Join Interface L2 Internal Interface Potential 3 rd data center DCI Design Choices CO RE DC 1 DC 2 Dark Fiber CO RE OTV vpc AG GR AG GR Fabric Path ACC ESS Server Farms Server Farms ACC ESS 46

47 OTV Design Why OTV Native STP and broadcast isolation Easy to add 3 rd site Existing multicast core Design OTV VDC on Aggregation No HSRP localization(phase1) simplify configuration minimal latency via dark fiber Data Center Core Aggregation OTV VDC VPC OTV VDC Dark fiber links OTV VDC VPC Data Center 1 Data Center 2 OTV VDC 47

48 Nexus 1000v Deployment for VM Mobility Both VSM in the same data center Layer 3 control on Nexus 1000V Stretched cluster supports live vmotion (5ms latency) Data Center #1 Data Center #2 VSM (Active) vcenter (Active) VSM (Standby) Layer 2 Extension (OTV) vsphere vsphere Virtualized Workload Mobility vsphere vsphere Nexus 1000V VEM Nexus 1000V VEM Stretched Cluster Nexus 1000V VEM Nexus 1000V VEM vcenter SQL/Oracle Database Dark Fiber Replicated vcenter SQL/Oracle Database 48

49 Traffic Flow for VM Mobility vmotion between Data Centers Virtual machines still use the original ACE and gateway after vmotion Traffic will trombone the DCI link for vmotioned virtual machines No HSRP localization and Source NAT 49

50 Overall Design Highlight Case Study #1 Requirement Solution x10g based virtualized generation data center architecture Nexus 7K,5K,2K provide scalable x10g architecture with end to end virtualization No STP blocking Topology Double sided vpc between 7K and 5K eliminating blocking ports FW protection between secure zone and non-secure zone FW virtualization and VRF sandwich design to provide logical separation and protection Support vmotion within and between data centers L2/L3 boundary is placed at aggregation layer to provide data center wide layer 2 domain OTV provide layer 2 extension between data centers Network team gains visibility to VM networking Nexus 1000v provides clear management boundary between network and server team. Network policy through N1KV is implemented on VMs 50

51 Session Agenda Nexus Platform Overview Data Center Design and Considerations Case Study #1: Green Field Data Center Design Case Study #2: Data Center Migration Key Takeaways 51

52 Case Study #2 Customer Profile A leading financial institution An existing Catalyst based network architecture 300+ standalone servers 20+ ESX servers with 500+ VMs Building a retrofitted data center Migrate existing network and server to the new data center architecture High Level Requirements x10g based virtualized next generation data center architecture No STP blocking topology Support vmotion within the data center Migrate the server per Vlan basis, and servers in the same Vlan may require multiple windows 52

53 Current Environment Catalyst 6500 at Core, Agg and Access ENT Network L2/L3 boundary at Access layer vmotion within Access layer Access layer switches are mainly gigabits, new ESX servers looking to upgrade to 10Gig AGG1 CORE1 CORE2 AGG2 EoR cabling infrastructure not cost effective for upgrade Access1 Access2 Access3 Access4 Access5 Access6 53

54 New Nexus Based Architecture Catalyst 6500 at Core, N7K Agg and N5K/2K Access L2/L3 boundary at N7K Agg switches vmotion within entire data center 10Gig based architecture ToR cabling infrastructure 54

55 High Level Migration Strategy Building the new Nexus Environment Connect the new environment with the existing environment Layer 2 extension via migration VDC Layer 2 fault domain separation via non-stp blocking topology Server migration per vlan basis Default-gateway migration per vlan basis 55

56 Step 1: Building the New Environment in Parallel Conduct Network Ready For Use testing for Nexus 7K/5K/2K 56

57 Step 2: Creating Migration VDC BPDU Filter BPDU Filter BPDU Filter SVI down HSRP LP BPDU Filter SVI down HSRP LP Test layer 2 connectivity between migration VDC and new environment Shut down all the server SVIs; Lower the HSRP priority 57

58 Step 3: Connect the N7K Agg to the Existing Core SVI down HSRP LP SVI down HSRP LP Test routing connectivity between N7K and the rest of network 58

59 Step 4: Add Layer 2 Links STP leaf STP leaf SVI down HSRP LP SVI down HSRP LP Test layer 2 connectivity between 6500 access and new environment 59

60 Step 5: Server Migration SVI down SVI down Gateway HSRP A Gateway HSRP S 60

61 Step 6a: Default Gateway Migration SVI up HSRP L SVI up HSRP L Gateway HSRP A Gateway HSRP S Bring up the SVIs on the Nexus; Asymmetric routing may exist 61

62 Step 6b: Default Gateway Migration-cont d Gateway HSRP A Gateway HSRP S Gateway HSRP L Gateway HSRP L Raise HSRP priority on N7K, make N7K the active default gateway Note: Asymmetric routing may exist. Very minimal traffic disruption may occur 62

63 Step 6c: Default Gateway Migration-cont d Gateway HSRP A Gateway HSRP S Gateway HSRP L Gateway HSRP L Shutdown the SVIs on 6500 Note: this step may also have traffic interruption due to asymmetric routing 63

64 Step 7: Migrate All The Servers For All The Vlans Gateway HSRP A Gateway HSRP S Gateway HSRP L Gateway HSRP L Repeat step 5 & 6 64

65 Step 8: Clean Up Disconnect Aggregation 6500 from Core Decommission Aggregation and Access 6500 and migration VDC 65

66 Case Study #2: Migration Summary Migration Highlight Using VDC to extent the existing and new environment Leveraging vpc non-stp blocking topology to isolate the STP domain via BPDU filter Using HSRP preemption to migrate the default gateway smoothly Default gateway migration Other Considerations Identify the steps where downtime are required Avoid asymmetric routing if stateful device involved Tuning routing metric maybe required STP root placement & migration Different behavior between NX-OS, IOS QoS, NTP 66

67 Key Takeaways Nexus family and NX-OS are designed for modern data center architecture 3 tier design model (Core, Aggregation, Access) ensure high availability & scalability Nexus 5K/2K offer flexible cabling solution at Access Nexus 7K/5K double sided vpc supports non-blocking topology and larger layer 2 domain. Fabric path is the new trend Nexus 7K virtualization provides flexible service insertion at Aggregation OTV/FabricPath/vPC simplify DCI and migration solution Nexus 1000v provides network policy control & visibility into VM, and offers integrated virtual services (VSG, vwaas, NAM, ASA) at VM level. 67

68 Complete Your Online Session Evaluation Give us your feedback and you could win fabulous prizes. Winners announced daily. Receive 20 Passport points for each session evaluation you complete. Complete your session evaluation online now (open a browser through our wireless network to access our portal) or visit one of the Internet stations throughout the Convention Center. Don t forget to activate your Cisco Live Virtual account for access to all session material, communities, and on-demand and live activities throughout the year. Activate your account at the Cisco booth in the World of Solutions or visit 68

69 Final Thoughts Get hands-on experience with the Walk-in Labs located in World of Solutions, booth 1042 Come see demos of many key solutions and products in the main Cisco booth 2924 Visit after the event for updated PDFs, ondemand session videos, networking, and more! Follow Cisco Live! using social media: Facebook: Twitter: LinkedIn Group: 69

70 Presentation_ID