This document discusses the Cisco Nexus 1000V virtual switch, which provides virtual machine-level network visibility and policy enforcement within VMware vSphere environments. The Nexus 1000V replaces the hypervisor virtual switch with Cisco's modular software switch. It extends the network to each virtual machine and allows consistent network and security policies to follow VMs during live migration. The Nexus 1000V integrates tightly with VMware vCenter and leverages Cisco's NX-OS operating system, providing familiar CLI management of the virtual switch.
Nexus 1000V Support for VMWare vSphere 6Tony Antony
The document discusses Cisco Nexus 1000V virtual networking software. It provides details on:
1. Nexus 1000V now supports VMware vSphere 6.0 and has increased scalability, security, and simplified installation/upgrade/monitoring features in version 3.1.
2. Version 3.1 provides micro-segmentation using the Virtual Security Gateway for distributed firewall capabilities. It also simplifies management using the Cisco Virtual Switch Update Manager plug-in for vSphere.
3. Cisco is committed to supporting Nexus 1000V across multiple hypervisors including VMware vSphere, Microsoft Hyper-V, and Red Hat/Canonical KVM.
ASBIS: Virtualization Aware Networking - Cisco Nexus 1000VASBIS SK
The document discusses the Cisco Nexus 1000V virtual switch and Nexus 1010 appliance. It provides an overview of key issues with server virtualization and networking, and how the Nexus 1000V addresses these issues with policy-based VM connectivity, mobility of network properties during VMotion, and a non-disruptive operational model. It also compares features of the Nexus 1000V to VMware vSphere standard and distributed virtual switches.
The document discusses Cisco Nexus 1000V and the Nexus 1010 appliance. It provides an overview of the Nexus 1000V architecture, comparing it to a physical modular switch. It describes how the Nexus 1000V uses Virtual Supervisor Modules (VSMs) and Virtual Ethernet Modules (VEMs) to replace the functionality of physical linecards and supervisors. It also discusses how the Nexus 1010 appliance allows hosting of VSMs on a physical device for improved performance and redundancy.
Ronnie Scott
Consulting CSE
Presented at the Cybera/CANARIE National Summit 2009, as part of the session "What's Next: Key Areas of Emerging Cyberinfrastructure."
This session explored some of the up-and-coming areas of cyberinfrastructure and why they are increasingly being considered as essential elements to innovative research and development.
The document discusses NSX design and deployment considerations including:
1. Physical and logical infrastructure requirements for NSX including IP connectivity and MTU size.
2. Edge cluster design with options for collapsed or separated edge and infrastructure racks.
3. NSX manager and controller placement and sizing within management clusters.
4. Transport zone, VTEP, and VXLAN switching concepts which are fundamental to the NSX overlay architecture.
The document provides information about the Cisco Nexus 7009 switch, including:
- It is a modular network switch with up to 9 slots that can support 336 10GbE or 1GbE ports.
- It uses up to 5 Crossbar Fabric Modules and 2 power supplies.
- The Nexus 7009 specifications section provides additional details about its hardware capabilities and supported interface speeds.
Nexus 1000V Support for VMWare vSphere 6Tony Antony
The document discusses Cisco Nexus 1000V virtual networking software. It provides details on:
1. Nexus 1000V now supports VMware vSphere 6.0 and has increased scalability, security, and simplified installation/upgrade/monitoring features in version 3.1.
2. Version 3.1 provides micro-segmentation using the Virtual Security Gateway for distributed firewall capabilities. It also simplifies management using the Cisco Virtual Switch Update Manager plug-in for vSphere.
3. Cisco is committed to supporting Nexus 1000V across multiple hypervisors including VMware vSphere, Microsoft Hyper-V, and Red Hat/Canonical KVM.
ASBIS: Virtualization Aware Networking - Cisco Nexus 1000VASBIS SK
The document discusses the Cisco Nexus 1000V virtual switch and Nexus 1010 appliance. It provides an overview of key issues with server virtualization and networking, and how the Nexus 1000V addresses these issues with policy-based VM connectivity, mobility of network properties during VMotion, and a non-disruptive operational model. It also compares features of the Nexus 1000V to VMware vSphere standard and distributed virtual switches.
The document discusses Cisco Nexus 1000V and the Nexus 1010 appliance. It provides an overview of the Nexus 1000V architecture, comparing it to a physical modular switch. It describes how the Nexus 1000V uses Virtual Supervisor Modules (VSMs) and Virtual Ethernet Modules (VEMs) to replace the functionality of physical linecards and supervisors. It also discusses how the Nexus 1010 appliance allows hosting of VSMs on a physical device for improved performance and redundancy.
Ronnie Scott
Consulting CSE
Presented at the Cybera/CANARIE National Summit 2009, as part of the session "What's Next: Key Areas of Emerging Cyberinfrastructure."
This session explored some of the up-and-coming areas of cyberinfrastructure and why they are increasingly being considered as essential elements to innovative research and development.
The document discusses NSX design and deployment considerations including:
1. Physical and logical infrastructure requirements for NSX including IP connectivity and MTU size.
2. Edge cluster design with options for collapsed or separated edge and infrastructure racks.
3. NSX manager and controller placement and sizing within management clusters.
4. Transport zone, VTEP, and VXLAN switching concepts which are fundamental to the NSX overlay architecture.
The document provides information about the Cisco Nexus 7009 switch, including:
- It is a modular network switch with up to 9 slots that can support 336 10GbE or 1GbE ports.
- It uses up to 5 Crossbar Fabric Modules and 2 power supplies.
- The Nexus 7009 specifications section provides additional details about its hardware capabilities and supported interface speeds.
This document provides an overview of Cisco's NX-OS operating system and Nexus platforms. It discusses the case for 10GbE connectivity to servers, how NX-OS is purpose-built for the data center, and how it provides increased efficiency and simpler operations through a unified fabric. It then reviews the Nexus 7000, 5000, 2000 and hardware and software versions. Key NX-OS features like Layer 2/3, routing protocols, VRFs, FabricPath, VDCs, FCoE, vPCs and OTV are summarized.
VMworld 2013: Designing Network Virtualization for Data-Centers: Greenfield D...VMworld
VMworld 2013
Ben Basler, VMware
Roberto Mari, VMware
Learn more about VMworld and register at http://www.vmworld.com/index.jspa?src=socmed-vmworld-slideshare
VXLAN with NSX -MH describes VXLAN and how it is implemented with NSX Micro Segmentation. It discusses VXLAN basics like encapsulation and VTEPs. It then covers the NSX control plane and data plane views including logical network view with logical switches/ports and physical transport node view. It provides examples of VXLAN L2 and L3 gateways for inter and intra-subnet communication deployed on NSX managed switches or physical gateways.
vVMworld 2013: Deploying, Troubleshooting, and Monitoring VMware NSX Distribu...VMworld
VMworld 2013
Srinivas Nimmagadda, VMware
Shadab Shah, VMware
Learn more about VMworld and register at http://www.vmworld.com/index.jspa?src=socmed-vmworld-slideshare
VMware NSX - Lessons Learned from real projectDavid Pasek
This document provides an overview and agenda for a presentation on implementing end-to-end quality of service (QoS) for VMware vSphere with NSX on Cisco UCS. It discusses the project requirements of guaranteeing network traffic for FCoE storage, vSphere management, vMotion and VM backups. It then presents three design options for implementing QoS by marking and prioritizing different classes of service on the virtual network interface cards, VMware distributed virtual switch port groups, Cisco UCS fabric interconnects and Nexus switches. The optimal solution must meet requirements within the constraints of the Cisco and VMware infrastructure components.
This document describes EYWA, a virtual network architecture for IaaS that provides elastic load balancing, high availability, and scalability. It addresses problems with conventional architectures like single points of failure, limited resources and poor connectivity. EYWA uses technologies like MVRRP and VxLAN to create highly available virtual routers that provide load balancing and isolation across large layer 2 networks. The key components are virtual routers, a guest virtual network that isolates traffic, and a controller that monitors network state and proxies ARP requests.
Cisco Evolving virtual switching to applications & cloudsolarisyougood
This document discusses evolving virtual switching technologies and Cisco's solutions. It introduces the Cisco Virtual Application Containers Service (VACS) which uses Cisco UCS Director to automate and accelerate application deployment through container provisioning. Key points include:
- VACS allows applications to be deployed from weeks to minutes through automated self-service provisioning of containers.
- Cisco UCS Director provides a single interface to build, deploy, and manage containers across physical, virtual, and cloud infrastructures for consistency and reduced risk.
- The Nexus 1000V virtual switch extends consistent Cisco switching capabilities to virtual and cloud workloads through features like intra-tenant security, application acceleration, and routing/gateways.
Customers are using NSX to drive business benefits as show in the figure below. The main themes for NSX deployments are Security, IT automation and Application Continuity.
Figure 3: NSX Use Cases
• Security:
NSX can be used to create a secure infrastructure, which can create a zero-trust security model. Every virtualized workload can be protected with a full stateful firewall engine at a very granular level. Security can be based on constructs such as MAC, IP, ports, vCenter objects and tags, active directory groups, etc. Intelligent dynamic security grouping can drive the security posture within the infrastructure.
NSX can be used in conjunction with 3rd party security vendors such as Palo Alto Networks, Checkpoint, Fortinet, or McAffee to provide a complete DMZ like security solution within a cloud infrastructure.
NSX has been deployed widely to secure virtual desktops to secure some of the most vulnerable workloads, which reside in the data center to prohibit desktop-to-desktop hacking.
• Automation:
VMware NSX provides a full RESTful API to consume networking, security and services, which can be used to drive automation within the infrastructure. IT admins can reduce the tasks and cycles required to provision workloads within the datacenter using NSX.
NSX is integrated out of the box with automation tools such as vRealize automation, which can provide customers with a one-click deployment option for an entire application, which includes the compute, storage, network, security and L4-L7 services.
6
Developers can use NSX with the OpenStack platform. NSX provides a neutron plugin that can be used to deploy applications and topologies via OpenStack
• Application Continuity:
NSX provides a way to easily extend networking and security up to eight vCenters either within or across data center In conjunction with vSphere 6.0 customers can easily vMotion a virtual machine across long distances and NSX will ensure that the network is consistent across the sites and ensure that the firewall rules are consistent. This essentially maintains the same view across sites.
NSX Cross vCenter Networking can help build active – active data centers. Customers are using NSX today with VMware Site Recovery Manager to provide disaster recovery solutions. NSX can extend the network across data centers and even to the cloud to enable seamless networking and security.
Cisco nexus 7000, nexus 5000 and 2000 fa qsIT Tech
The document discusses Cisco Nexus networking switches, including differences between line cards, fabric modules, and virtual device contexts (VDCs) on Nexus 7000, 5000, and 2000 series switches. It answers several questions about the hardware and software capabilities of these switches. Key points include that M series line cards support layer 3 functions while F series support layer 2, fabric modules provide redundancy but no ports, and Nexus 2000 switches have no operating system and download one from a connected Nexus 5000 or 7000.
VMworld 2013: Troubleshooting VXLAN and Network Services in a Virtualized Env...VMworld
This document discusses troubleshooting VXLAN and network services in a virtualized environment using VMware NSX. It covers VXLAN packet flow, NSX enhancements to the data and control planes, configuration and consumption demos, packet walks in unicast mode, troubleshooting demos using NSX Manager tools, dynamic routing details and demos, and network virtualization operations. The key takeaways are that multicast is not required in the physical network for VXLAN, NSX provides tools to troubleshoot networks and services, and NSX integrates with operations tools for analysis and alerting.
VMware NSX + Cumulus Networks: Software Defined NetworkingCumulus Networks
Witness the enablement of a true integration of a virtual network platform and an underlay physical network for a scalable data center orchestration, automation and multi-tenancy solution over high-capacity IP fabrics. With the integration of VMware NSX Layer 2 gateway services on networking hardware running Cumulus Linux, customers can now connect virtual workloads to physical workloads with no performance impact.
The Vision for the Future of Network Virtualization with VMware NSXScott Lowe
This presentation recaps some announcements and demonstrations made at VMworld 2015 regarding new features and new functionality tentatively anticipated for future versions of VMware NSX.
This document discusses VMware NSX architecture and design. It provides an overview of NSX components like the NSX manager, controllers, distributed logical routing, and NSX edge services gateway. It also covers NSX design considerations such as transport zones, VTEPs, logical networks, and VDS configuration. The document emphasizes that NSX is agnostic to underlying network topology and flexible in its deployment.
Software Defined Networking is seeing a lot of momentum these days. With server virtualization solving the virtual machines problem, and large scale object storage solving the distributed storage challenge, SDN is seen as key in virtual networking.
In this talk we don't try to define SDN but rather dive straight into what in our opinion is the core enabled of SDN: the virtual switch OVS.
OVS can help manage VLAN for guest network isolation, it can re-route any traffic at L2-L4 by keeping forwarding tables controlled by a remote controller (Openfow controller). We show these few OVS capabilities and highlight how they are used in CloudStack and Xen.
Xen Summit presentation of CloudStack and Software Defined Networks. OpenVswitch is the default bridge in Xen and supported in XenServer and Xen Cloud Platform
Medtronic had challenges virtualizing large workloads over 1Gb connections with vMotion failures in ESX 4.1. Upgrading to ESX 5.0 enabled features like multiple-NIC vMotion and Stun During Page-Send (SDPS) to improve performance for migrating large VMs. Using multiple 10Gb NICs for vMotion provided more bandwidth and reduced migration times. Quality of service (QoS) was important to prioritize traffic and avoid overwhelming switch interconnects when not using dedicated vMotion switches. Medtronic deployed a solution with UCS servers, Nexus 1000v switches, and four 10Gb FCoE NICs per host, achieving a 157:1 consolidation ratio while successfully
VMworld 2013: vSphere Distributed Switch – Design and Best Practices VMworld
VMworld 2013
Vyenkatesh (Venky) Deshpande, VMware
Marcos Hernandez, VMware
Learn more about VMworld and register at http://www.vmworld.com/index.jspa?src=socmed-vmworld-slideshare
The document discusses virtual networking solutions from Cisco and VMware that aim to provide transparency and mobility of network and security policies as virtual machines move around in a datacenter. It introduces Cisco's VN-Link technology which extends the network into the virtualization layer by integrating with VMware's hypervisor management. Key components of VN-Link include the Nexus 1000V virtual switch, port profiles to apply network policies to VMs, and visibility of individual VMs. The document also compares VMware's virtual switch and Cisco's Nexus 1000V, and discusses how VN-Link can be implemented in software with Nexus 1000V or in hardware with Cisco UCS adapters.
The document provides an overview of the Cisco Nexus 1000V virtual switch, including:
1) The Nexus 1000V uses Virtual Ethernet Modules (VEMs) that replace the VMware vSwitch on each hypervisor and a Virtual Supervisor Module (VSM) that controls the VEMs and provides a unified NX-OS CLI.
2) Port profiles allow common configurations to be defined once and applied to multiple virtual Ethernet ports, simplifying management of virtual networking resources.
3) The distributed data plane means each VEM switches independently without synchronization, and the VSM is not in the data path between VEMs.
The document provides an overview of network virtualization and Quantum, an OpenStack module that provides network as a service. It discusses how Quantum uses plug-ins and extensions to provide layer 2 isolation using mechanisms like VLANs and tunnels. It also describes Quantum's layer 3 networking extension which allows creation of routers to connect different networks, and how security groups can specify ingress/egress traffic rules for ports.
This document provides an overview of Cisco's NX-OS operating system and Nexus platforms. It discusses the case for 10GbE connectivity to servers, how NX-OS is purpose-built for the data center, and how it provides increased efficiency and simpler operations through a unified fabric. It then reviews the Nexus 7000, 5000, 2000 and hardware and software versions. Key NX-OS features like Layer 2/3, routing protocols, VRFs, FabricPath, VDCs, FCoE, vPCs and OTV are summarized.
VMworld 2013: Designing Network Virtualization for Data-Centers: Greenfield D...VMworld
VMworld 2013
Ben Basler, VMware
Roberto Mari, VMware
Learn more about VMworld and register at http://www.vmworld.com/index.jspa?src=socmed-vmworld-slideshare
VXLAN with NSX -MH describes VXLAN and how it is implemented with NSX Micro Segmentation. It discusses VXLAN basics like encapsulation and VTEPs. It then covers the NSX control plane and data plane views including logical network view with logical switches/ports and physical transport node view. It provides examples of VXLAN L2 and L3 gateways for inter and intra-subnet communication deployed on NSX managed switches or physical gateways.
vVMworld 2013: Deploying, Troubleshooting, and Monitoring VMware NSX Distribu...VMworld
VMworld 2013
Srinivas Nimmagadda, VMware
Shadab Shah, VMware
Learn more about VMworld and register at http://www.vmworld.com/index.jspa?src=socmed-vmworld-slideshare
VMware NSX - Lessons Learned from real projectDavid Pasek
This document provides an overview and agenda for a presentation on implementing end-to-end quality of service (QoS) for VMware vSphere with NSX on Cisco UCS. It discusses the project requirements of guaranteeing network traffic for FCoE storage, vSphere management, vMotion and VM backups. It then presents three design options for implementing QoS by marking and prioritizing different classes of service on the virtual network interface cards, VMware distributed virtual switch port groups, Cisco UCS fabric interconnects and Nexus switches. The optimal solution must meet requirements within the constraints of the Cisco and VMware infrastructure components.
This document describes EYWA, a virtual network architecture for IaaS that provides elastic load balancing, high availability, and scalability. It addresses problems with conventional architectures like single points of failure, limited resources and poor connectivity. EYWA uses technologies like MVRRP and VxLAN to create highly available virtual routers that provide load balancing and isolation across large layer 2 networks. The key components are virtual routers, a guest virtual network that isolates traffic, and a controller that monitors network state and proxies ARP requests.
Cisco Evolving virtual switching to applications & cloudsolarisyougood
This document discusses evolving virtual switching technologies and Cisco's solutions. It introduces the Cisco Virtual Application Containers Service (VACS) which uses Cisco UCS Director to automate and accelerate application deployment through container provisioning. Key points include:
- VACS allows applications to be deployed from weeks to minutes through automated self-service provisioning of containers.
- Cisco UCS Director provides a single interface to build, deploy, and manage containers across physical, virtual, and cloud infrastructures for consistency and reduced risk.
- The Nexus 1000V virtual switch extends consistent Cisco switching capabilities to virtual and cloud workloads through features like intra-tenant security, application acceleration, and routing/gateways.
Customers are using NSX to drive business benefits as show in the figure below. The main themes for NSX deployments are Security, IT automation and Application Continuity.
Figure 3: NSX Use Cases
• Security:
NSX can be used to create a secure infrastructure, which can create a zero-trust security model. Every virtualized workload can be protected with a full stateful firewall engine at a very granular level. Security can be based on constructs such as MAC, IP, ports, vCenter objects and tags, active directory groups, etc. Intelligent dynamic security grouping can drive the security posture within the infrastructure.
NSX can be used in conjunction with 3rd party security vendors such as Palo Alto Networks, Checkpoint, Fortinet, or McAffee to provide a complete DMZ like security solution within a cloud infrastructure.
NSX has been deployed widely to secure virtual desktops to secure some of the most vulnerable workloads, which reside in the data center to prohibit desktop-to-desktop hacking.
• Automation:
VMware NSX provides a full RESTful API to consume networking, security and services, which can be used to drive automation within the infrastructure. IT admins can reduce the tasks and cycles required to provision workloads within the datacenter using NSX.
NSX is integrated out of the box with automation tools such as vRealize automation, which can provide customers with a one-click deployment option for an entire application, which includes the compute, storage, network, security and L4-L7 services.
6
Developers can use NSX with the OpenStack platform. NSX provides a neutron plugin that can be used to deploy applications and topologies via OpenStack
• Application Continuity:
NSX provides a way to easily extend networking and security up to eight vCenters either within or across data center In conjunction with vSphere 6.0 customers can easily vMotion a virtual machine across long distances and NSX will ensure that the network is consistent across the sites and ensure that the firewall rules are consistent. This essentially maintains the same view across sites.
NSX Cross vCenter Networking can help build active – active data centers. Customers are using NSX today with VMware Site Recovery Manager to provide disaster recovery solutions. NSX can extend the network across data centers and even to the cloud to enable seamless networking and security.
Cisco nexus 7000, nexus 5000 and 2000 fa qsIT Tech
The document discusses Cisco Nexus networking switches, including differences between line cards, fabric modules, and virtual device contexts (VDCs) on Nexus 7000, 5000, and 2000 series switches. It answers several questions about the hardware and software capabilities of these switches. Key points include that M series line cards support layer 3 functions while F series support layer 2, fabric modules provide redundancy but no ports, and Nexus 2000 switches have no operating system and download one from a connected Nexus 5000 or 7000.
VMworld 2013: Troubleshooting VXLAN and Network Services in a Virtualized Env...VMworld
This document discusses troubleshooting VXLAN and network services in a virtualized environment using VMware NSX. It covers VXLAN packet flow, NSX enhancements to the data and control planes, configuration and consumption demos, packet walks in unicast mode, troubleshooting demos using NSX Manager tools, dynamic routing details and demos, and network virtualization operations. The key takeaways are that multicast is not required in the physical network for VXLAN, NSX provides tools to troubleshoot networks and services, and NSX integrates with operations tools for analysis and alerting.
VMware NSX + Cumulus Networks: Software Defined NetworkingCumulus Networks
Witness the enablement of a true integration of a virtual network platform and an underlay physical network for a scalable data center orchestration, automation and multi-tenancy solution over high-capacity IP fabrics. With the integration of VMware NSX Layer 2 gateway services on networking hardware running Cumulus Linux, customers can now connect virtual workloads to physical workloads with no performance impact.
The Vision for the Future of Network Virtualization with VMware NSXScott Lowe
This presentation recaps some announcements and demonstrations made at VMworld 2015 regarding new features and new functionality tentatively anticipated for future versions of VMware NSX.
This document discusses VMware NSX architecture and design. It provides an overview of NSX components like the NSX manager, controllers, distributed logical routing, and NSX edge services gateway. It also covers NSX design considerations such as transport zones, VTEPs, logical networks, and VDS configuration. The document emphasizes that NSX is agnostic to underlying network topology and flexible in its deployment.
Software Defined Networking is seeing a lot of momentum these days. With server virtualization solving the virtual machines problem, and large scale object storage solving the distributed storage challenge, SDN is seen as key in virtual networking.
In this talk we don't try to define SDN but rather dive straight into what in our opinion is the core enabled of SDN: the virtual switch OVS.
OVS can help manage VLAN for guest network isolation, it can re-route any traffic at L2-L4 by keeping forwarding tables controlled by a remote controller (Openfow controller). We show these few OVS capabilities and highlight how they are used in CloudStack and Xen.
Xen Summit presentation of CloudStack and Software Defined Networks. OpenVswitch is the default bridge in Xen and supported in XenServer and Xen Cloud Platform
Medtronic had challenges virtualizing large workloads over 1Gb connections with vMotion failures in ESX 4.1. Upgrading to ESX 5.0 enabled features like multiple-NIC vMotion and Stun During Page-Send (SDPS) to improve performance for migrating large VMs. Using multiple 10Gb NICs for vMotion provided more bandwidth and reduced migration times. Quality of service (QoS) was important to prioritize traffic and avoid overwhelming switch interconnects when not using dedicated vMotion switches. Medtronic deployed a solution with UCS servers, Nexus 1000v switches, and four 10Gb FCoE NICs per host, achieving a 157:1 consolidation ratio while successfully
VMworld 2013: vSphere Distributed Switch – Design and Best Practices VMworld
VMworld 2013
Vyenkatesh (Venky) Deshpande, VMware
Marcos Hernandez, VMware
Learn more about VMworld and register at http://www.vmworld.com/index.jspa?src=socmed-vmworld-slideshare
The document discusses virtual networking solutions from Cisco and VMware that aim to provide transparency and mobility of network and security policies as virtual machines move around in a datacenter. It introduces Cisco's VN-Link technology which extends the network into the virtualization layer by integrating with VMware's hypervisor management. Key components of VN-Link include the Nexus 1000V virtual switch, port profiles to apply network policies to VMs, and visibility of individual VMs. The document also compares VMware's virtual switch and Cisco's Nexus 1000V, and discusses how VN-Link can be implemented in software with Nexus 1000V or in hardware with Cisco UCS adapters.
The document provides an overview of the Cisco Nexus 1000V virtual switch, including:
1) The Nexus 1000V uses Virtual Ethernet Modules (VEMs) that replace the VMware vSwitch on each hypervisor and a Virtual Supervisor Module (VSM) that controls the VEMs and provides a unified NX-OS CLI.
2) Port profiles allow common configurations to be defined once and applied to multiple virtual Ethernet ports, simplifying management of virtual networking resources.
3) The distributed data plane means each VEM switches independently without synchronization, and the VSM is not in the data path between VEMs.
The document provides an overview of network virtualization and Quantum, an OpenStack module that provides network as a service. It discusses how Quantum uses plug-ins and extensions to provide layer 2 isolation using mechanisms like VLANs and tunnels. It also describes Quantum's layer 3 networking extension which allows creation of routers to connect different networks, and how security groups can specify ingress/egress traffic rules for ports.
Cisco VSG_Конкурс продуктов портала VirtualizationSecurityGroup.RuVirtSGR
Cisco Virtual Security Gateway (VSG) provides security policies and controls for virtual machine to virtual machine traffic. It analyzes VM attributes and context to dynamically apply access controls. VSG inserts transparently without relying on VLANs to protect intra-segment communication. It also supports multi-tenant environments through security domain separation and granular policy assignment.
Managing The Impact Of Virtualization Technology On Your NetworkSolarWinds
This document provides an overview of managing the impact of virtualization technology on networks. It discusses how virtualization can impact network policies and visibility. The Cisco Nexus 1000V is introduced as a solution to these issues by providing policy-based VM connectivity, mobility of network properties, and a non-disruptive operational model. It maintains the vCenter provisioning model while allowing network administration via Cisco NX-OS CLI. The document then discusses how SolarWinds Orion can help manage and monitor the Nexus 1000V and virtualized infrastructure through discovery, monitoring, and notifications. It notes that Orion is the only management tool offered in a bundle with vSphere and Nexus
The document discusses network virtualization technologies used in contemporary virtualized data centers. It describes how software-defined networking (SDN), network function virtualization (NFV), and network virtualization (NV) can alleviate increased network demands from server, storage, and network virtualization. Specifically, it outlines virtual extensible local area network (VXLAN) as a common network overlay technique, how it encapsulates and transports virtualized layer 2 frames over layer 3 networks using VXLAN tunnel end points (VTEPs) and a VXLAN network identifier (VNI). VXLAN aims to solve limitations of spanning trees, VLAN ranges, and switch table sizes in multi-tenant environments.
OVHcloud Hosted Private Cloud Platform Network use cases with VMware NSXOVHcloud
In this workshop VMware will provide a quick reminder of the main contributions of the NSX network virtualization platform: consistent network and security management, increased application resiliency, rapid migration of workloads to and from the cloud.
VMware and OVH will then move on to practical cases with implementation of micro-segmentation, dynamic routing, automatic deployment of an application, load balancing in the OVH Hosted Private Cloud. This workshop is aimed at a technical audience.
Data Center Convergentes - Carlos Spera - 20 de octubre - UYLogicalis Latam
The document provides an overview of cloud computing, data center technologies, and Cisco solutions. It defines cloud computing, discusses concepts like SaaS, PaaS, and IaaS, and examines trends driving data center evolution such as server virtualization and automation. It also introduces Cisco's Nexus switching portfolio including the Nexus 1000V virtual switch, Nexus 5000 series, and Nexus 2000 fabric extenders for scalable server access.
Network virtualization with open stack quantumMiguel Lavalle
Network virtualization with OpenStack Quantum allows tenants to create their own virtual networks that map to underlying physical network technologies. The Quantum plugin architecture supports different virtual networking backends. Quantum provides an API for tenants to dynamically create networks and attach virtual machine ports, implementing advanced networking features through extensions.
The document discusses network function virtualization and how 6WIND's Virtual Accelerator solution addresses performance bottlenecks in virtualized network environments. It provides high-speed networking and packet processing capabilities independent of the underlying Linux kernel. This improves throughput for east-west traffic between virtual network functions and north-south traffic, allowing for higher VM and VNF densities. It also enables appliance-based network functions to be virtualized without performance limitations.
VMware vSphere 6.0 - Troubleshooting Training - Day 3 Sanjeev Kumar
The document discusses vSphere networking and distributed switches. It describes the benefits of distributed switches over standard switches, such as simplifying administration and enabling features like private VLANs and port mirroring. It explains how to create and manage distributed switches and port groups, assign physical NICs and virtual machines, and configure properties and advanced features. Troubleshooting tips are provided for issues with virtual machine communication across distributed switch ports.
The document provides an introduction to VMware vSphere distributed switches. It lists the benefits of distributed switches over standard switches, describes the distributed switch architecture, and discusses how to create, manage, and configure distributed switches and their properties. It also covers topics like distributed port groups, VMkernel networking, NetFlow, private VLANs, and troubleshooting distributed switch issues.
Azure Networking: Innovative Features and Multi-VNet TopologiesMarius Zaharia
Are you looking to deploy a more complex structure of resources in Azure, all secured and segregated by precise boundaries while closely communicating with each other? Following the arrival of the advanced IaaS networking features in Azure (network security groups, routing, multi-NIC, …) and their maturation in the last months, here is the moment for you to find a modern architectural vision of networking in Azure, with focus on multi-VNET / VPN topologies, and based on ARM deployment model.
The document discusses VMware's product direction and focus on the future. It outlines VMware's vision of a "Virtual Datacenter OS" that will deliver an internal cloud through technologies like vCompute, vStorage, vNetwork and management solutions. It also discusses initiatives around vCloud to federate internal and external clouds, and addressing the "desktop dilemma" through solutions like VMware View that deliver virtual desktops to follow the user across devices.
VMM provides several options for connecting virtual machines to a physical network including VLAN-based configuration, no isolation configuration, and network virtualization. It uses logical networks, logical switches, and VM networks to abstract the physical network and provide isolated virtual networks for tenants. Extensibility options allow connecting to external management consoles and using extensions to configure networking features.
Contrail provides software defined networking and virtual network capabilities for OpenStack clouds. Key components of Contrail include the Contrail controller, vRouters running on hypervisors, and integration with OpenStack using Neutron and Nova. Virtual networks in Contrail can be created which provide isolation between groups of virtual machines and connectivity to physical networks.
VMworld 2013: vSphere Networking and vCloud Networking Suite Best Practices a...VMworld
VMworld 2013
Richard Cockett, VMware
Umesh Goyal, VMware Software India Pvt ltd
Learn more about VMworld and register at http://www.vmworld.com/index.jspa?src=socmed-vmworld-slideshare
MidoNet 101: Face to Face with the Distributed SDNMidoNet
Midokura has made the source code for MidoNet freely available at www.midonet.org, delivering the truly open, vendor-agnostic network virtualization solution available for the OpenStack and the Docker community.
About MidoNet
Taking an overlay-based approach to network virtualization, MidoNet sits on top of any IP-connected network, and pushes the network intelligence to the edge of the network, in software. MidoNet makes it possible to build an IaaS cloud with fully virtualized and distributed scale-out L2-L4 networking.
FOSDEM 2015
Presenters: Antonio Sagliocco, Alex Bikfalvi in Midokura Engineering
This document proposes EYWA, a virtual network architecture for cloud environments that aims to overcome scalability limitations of conventional architectures. EYWA uses virtual routers distributed across hypervisor hosts to provide high availability and load balancing for public networks without bottlenecks. It employs VxLAN to provide large private IP subnets for tenants by eliminating issues like VLAN limits and MAC flooding. Key to EYWA is an agent on each hypervisor that monitors virtual routers, caches ARP entries, and controls ARP packets according to rules to enable multiple virtual routers per tenant with a single IP address.
F1 is a distributed SQL database developed by Google to support its ad business. It combines the scalability of Bigtable with the functionality of SQL. Key features include automatic data sharding across servers, synchronous replication for high availability and consistency, and hiding high commit latencies. Google migrated from a sharded MySQL system to F1 to gain better scalability, availability, and query capabilities while maintaining application performance. F1 uses hierarchical schemas, protocol buffer column types, and optimized client coding to cope with its higher latency compared to MySQL.
The document discusses a proposed proof by Vinay Deolalikar that P ≠ NP, the famous open problem in computer science. The proof strategy involved showing that satisfiability problems like random k-SAT would have "simple structure" if in P, but some instances do not. However, the proof was found to have flaws, as the "simple structure" property still holds even for problems in P. Multiple objections and counterexamples were found within a week through open online discussion, suggesting the proof is likely unsalvageable. The rapid online peer review process provided both benefits and costs to rigorously evaluating the proposed proof.
- MapReduce is a programming model for processing large datasets in a distributed manner across clusters of machines. It handles parallelization, load balancing, and hardware failures automatically.
- In MapReduce, the input data is mapped to intermediate key-value pairs, shuffled and sorted by the keys, then reduced to produce the final output. This pattern applies to many large-scale computing problems.
- Google uses MapReduce for tasks like generating map tiles, processing web search indexes, and mining log data. It hides the complex distributed systems details from programmers and provides robustness and performance improvements when run on large clusters.
This document introduces the Open Virtualization Format (OVF), a standard for packaging and distributing virtual appliances. OVF aims to provide a hypervisor-neutral format to allow virtual machines and their applications to be easily transferred between virtualization platforms. It addresses the need for a multi-tier packaging model to support modern applications. OVF provides features for virtual hardware description, deployment customization, internationalization, and extensibility. The goal is for OVF to facilitate automated and secure management of virtual appliances.
The document provides an introduction and overview of the vCloud API. It discusses key concepts such as the API being standardized, platform independent, and focused on resource semantics rather than physical infrastructure. It also covers the API features such as interface for providing and consuming cloud resources, deployment and management of virtual workloads, and migration of workloads between clouds. Examples of API operations like powering on a vApp, looking at vApp details, and instantiating a vApp template are also provided at a high level.
The document provides an overview of the Open Virtualization Format Specification, which defines an open standard format for packaging and distributing virtual machines and their associated metadata. The format supports both single and multiple virtual machine configurations, is optimized for distribution and an automated user experience, and is extensible, vendor-independent, and localizable. Key elements of the format include the OVF package structure, OVF descriptor file, virtual hardware description, and core metadata sections.
2. Transparency in the Eye of the Beholder
With virtualization,
VMs have a
transparent view of
their resources…
3. Transparency in the Eye of the Beholder
…but its difficult to
correlate network and
storage back to virtual
machines
4. Transparency in the Eye of the Beholder
Scaling globally depends
on maintaining
transparency while also
providing operational
consistency
5. Networking Challenges to Scaling Server Virtualization
Security and Policy Operations and Organizational
Enforcement Management Structure
Applied at physical Lack of VM visibility, Muddled ownership
server—not the accountability, and as server admin
individual VM consistency must configure
virtual network
Impossible to enforce Inefficient
policy for VMs in management model Organizational
motion and inability to redundancy creates
effectively compliance
troubleshoot challenges
6. Why the Network is Changing…
Desire for VM-level access-layer policy & monitoring
Virtualization is driving higher link utilization
More demanding role of network (i.e. DRS, vMotion)
Current approaches lead to inconsistent network policies
7. Cisco Virtual Network Link – VN-Link
Virtual Network Link (VN-Link) is about:
– VM-level network granularity
– Mobility of network and security properties
(follow the VM)
VNIC
– Policy-based configuration of VM interfaces VNIC
Hypervisor
(Port Profiles)
– Non-disruptive operational model
VN-Link refers to a literal link
VN-Link with Nexus 1000V VETH VETH
– Replaces Hypervisor switch with Cisco modular
switch (software)
8. VN-Link Brings VM Level Granularity
Problems:
VMotion
VMotion may move VMs across
physical ports—policy must follow
Impossible to view or apply policy to
locally switched traffic
Cannot correlate traffic on physical
links—from multiple VMs
VLAN
101
VN-Link:
Extends network to the VM
Consistent services
Coordinated, coherent management
9. VN-Link With the Cisco Nexus 1000V
Cisco Nexus 1000V
Software Based
Server
Industry’s first 3rd-party vNetwork VM VM VM VM
#1 #2 #3 #4
Distributed switch for ESX
Built on Cisco NX-OS
Nexus 1000V
Compatible with all switching platforms VMW ESX
Maintain vCenter provisioning model NIC NIC
unmodified for server administration;
allow network administration of Nexus Nexus
1000V
1000V via familiar Cisco NX-OS CLI
LAN
Policy-Based Mobility of Network Non-Disruptive
VM Connectivity & Security Properties Operational Model
10. vNetwork – 3rd Party Virtual Switches
Enterprise networking vendors can
provide their own implementations
CURRENT
of the virtual switch leveraging the
vSwitch
vSwitch vSwitch vNetwork switch API interfaces
Enables support for 3rd party
networking capabilities, including
monitoring and management of the
virtual network
vNetwork
vNetwork Distributed Switch Third Party Switch Products
vNetwork Platform vNetwork Platform
11. VI Virtual Networking - 3rd Party Virtual Switch Style
Host1 Host2 Host3 Host4
W2003EE-32-A W2003EE-32-B W2003EE-32-A2 W2003EE-32-B2 W2003EE-32-A3 W2003EE-32-B3 W2003EE-32-A4 W2003EE-32-B4
Single
Distributed
Port
Group
3rd Party Distributed vSwitch Machine Network
Virtual Single
Distributed
vNetwork Platform Switch
3rd Party Distributed
Switch Spanning
Host1, Host2,
Host3, Host4
12. Cisco Nexus 1000V Architecture
Server 1 Server 2 Server 3
VM VM VM VM VM VM VM VM VM VM VM VM
#1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12
VEM
VMware vSwitch VEM
VMware vSwitch VMware vSwitch
VEM
VMW ESX VMW ESX VMW ESX
Virtual Supervisor Module (VSM)
Virtual or Physical appliance running
Virtual Ethernet Module (VEM)
Cisco OS (supports HA)
Enables advanced networking
Cisco Nexus 1000V Installation:&
Performs management, monitoring,
capability on the hypervisor vCenter
configuration
ESX & ESXi
Provides each VM with dedicated
Tight integrationInstallation
“switch Manual with VMware
VUM & port” Nexus 1000V
vCenter
VEM is installed/upgraded like an
Collection of VEMs = 1 Distributed
ESX patch
Switch
VSM
13. VSM to vCenter Communication
Nexus 1000V
vCenter VSM
Two-way API between the VSM and vCenter
Certificate (Cisco self signed or customer supplied) ensures secure
communications
Connection is setup on the VSM
n1000v# show svs connections
connection vc:
ip address: 10.95.5.227
protocol: vmware-vim https
datacenter name: Nexus1K-RC1
DVS uuid: 58 ae 0f 50 c4 f9 af 4d-47 df c7 a8 f5 72 f5 64
config status: Enabled
operational status: Connected
14. Deploying the Cisco Nexus 1000V
Collaborative Deployment Model
1. VMW vCenter & Cisco
Nexus 1000V Server 1
relationship established
2. Network Admin
configures Nexus 1000V
Nexus 1000V—VEM
to support new ESX
hosts VMW ESX
3. Server Admin plugs new
ESX host into network & 3.
adds host to Cisco 2.
switch in vCenter
Nexus 1000V
vCenter 1. VSM
15. Deploying the Cisco Nexus 1000V
Collaborative Deployment Model
1. VMW vCenter & Cisco
Nexus 1000V Server N Server 1
relationship established
2. Network Admin
configures Nexus 1000V
to support new ESX Nexus 1000V—VEM Nexus 1000V 1000V—VEM
Nexus
hosts VMW ESX VMW ESX
3. Server Admin plugs new
ESX host into network &
adds host to Cisco
4.
switch in vCenter
Nexus 1000V
4. Repeat step three to
add another host and
extend the switch
vCenter
configuration VSM
16. Cisco Nexus 1000V Architecture – Network View
nexus1000v01# show module
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
1 1 Virtual Supervisor Module Nexus1000V active * VSM
3 48 Virtual Ethernet Module ok
4 48 Virtual Ethernet Module ok
VEM
Mod Sw Hw World-Wide-Name(s) (WWN)
--- -------------- ------ --------------------------------------------------
1 4.1(1a)S1(0.14 0.0 --
3 NA 0.0 --
4 NA 0.0 --
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
1 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
3 02-00-0c-00-07-00 to 02-00-0c-00-07-80 NA
4 02-00-0c-00-08-00 to 02-00-0c-00-08-80 NA
Mod Server-IP Server-UUID Server-Name
--- --------------- ------------------------------------ --------------------
ESX
1 192.168.32.31
3 192.168.32.101 48c8d12a-1e15-00db-5efe-001e0bcae426 esx01a.cisco.com Details
4 192.168.32.102 48c8da10-e70b-aa66-3089-001e0bcab2e4 esx02b.cisco.com
18. Cisco Nexus 1000V - Faster VM Deployment
Virtualizing the Network Domain
Policy-Based Mobility of Network Non-Disruptive
VM Connectivity & Security Properties Operational Model
Server Server
VM VM VM VM VM VM VM VM
#1 #2 #3 #4 #5 #6 #7 #8
Cisco Nexus 1000V
Defined Policies VMW ESX VMW ESX
WEB Apps
HR
VM Connection Policy
Defined in the network
DB
Applied in vCenter
Compliance Linked to VM UUID
vCenter
19. Policy Based VM Connectivity
Enabling Policy
1. Nexus 1000V automatically
enables port groups in vCenter Server 1
2. Server Admin uses vCenter to VM VM VM VM
#1 #2 #3 #4
assign vnic policy from available
port groups
3. Nexus 1000V automatically 2. Nexus 1000V - VEM
enables VM connectivity at VM VMW ESX
power-on
3.
WEB Apps:
PVLAN 108, Isolated 1. Nexus 1000V
Security Policy = Port 80 and 443 Available Port Groups
Rate Limit = 100 Mbps
WEB Apps HR
QoS Priority = Medium vCenter
Remote Port Mirror = Yes DB Compliance VSM
20. Policy Definition with NX-OS Port Profiles
Port Profiles (aka Port Groups) defined in the Nexus 1000V VSM
Port profiles are pushed to vCenter via API
Upon connection/reconnection with vCenter the VSM re-verifies the
correct port profile configuration exists within vCenter
Port profile ‘state’ and ‘type’ must be set for propagation to occur
– N1K-CP(config-port-prof) state enable
– N1K-CP(config-port-prof) vmware port-group
(optional name)
21. Port Profile – Network View
n1000v-RC# show port-profile
port-profile web-server-dmz-2
description: Web Server – DMZ-2
status: enabled
capability uplink: no
system vlans: none
port-group: Web Server – DMZ-2
max-ports: 32 Port Group
inherit: Name
config attibutes:
switchport mode access
switchport acess vlan 5
ip port access-group web-secure in ACL
ip flow monitor output
no shutdown
evaluated config attibutes:
switchport mode access
switchport acess vlan 5
ip port access-group web-secure in
ip flow monitor output
no shutdown
assigned interfaces:
Vethernet10 Interfaces
22. Port Groups - VI Admin View
Consistent Workflow: VI admin
selects Port Groups when
configuring a VM in VMware
Virtual Infrastructure Client
23. Policy Based VM Connectivity
Virtualization Admin Benefits
Accelerate & Simplify deployment of new ESX hosts
– Network Admin provisions physical switch trunks & ESX host PNICs in a
uniform and consistent way (takes care of both sides of physical connection)
– Virtualization Admin 1) plugs in a new ESX host, 2) assigns PNICs to Cisco
vNetwork Distributed Switch in vCenter, 3) ESX PNIC configuration (including
vMotion & Console) automatically assigned and enabled, 4) ESX host ready
for VMs
Ensure proper connectivity & networking safeguards are in place
– Virtualization Admin leverages existing workflow (vCenter & Port Groups) to
assign VNIC policy.
– Network Admin responsible for ensuring Port Groups provide proper VLAN
access & DC network security policy
– Cisco Nexus 1000V extends VM networking to include IP/Port security rules,
multi-host PVLAN, Flow Statistics, Quality of Service.
24. Cisco Nexus 1000V
Richer Network Services
Virtualizing the Network Domain
Policy-Based Mobility of Network Non-Disruptive
VM Connectivity & Security Properties Operational Model
Server
VM VM VM VM
VM VM VM VM VM #1 VM#2 VM #3 VM #4
#1 #2 #3 #4 #5 #6 #7 #8
Cisco Nexus 1000V
VMW ESX VMW ESX
VMs Need to Move
VMotion VN-Link Property Mobility
DRS VMotion for the network
SW Upgrade/Patch Ensures VM security
Hardware Failure Maintains connection state
vCenter
25. Mobility of Security & Network Properties
Following Your VMs Around
1. vCenter kicks off a Server 1 Server 2
VMotion (manual/DRS) VM VM VM VM VM VM VM VM
and notifies Nexus #1 #2 #3 #4 #5 #6 #7 #8
1000V
2. During VM replication, Nexus
Nexus 1000V—VEM 1000V
Nexus 1000 -—VEM
Nexus 1000V copies VM VMW ESX VMW ESX
port state to new host
Mobile Properties Include: 2.
Port policy 1.
Interface state and
counters Nexus 1000V
Flow statistics Network Persistence
VMotion Notification
Current: VM1 onstate 1
VM port config, Server
Remote port mirror vCenter New: VM1 on Server 2
VM monitoring statistics
session VSM
26. Mobility of Security & Network Properties
Following Your VMs Around
1. vCenter kicks off a Server 1 Server 2
VMotion VM VM VM VM VMVM VM VM VM
(manual/DRS) & #1 #2 #3 #4 #1
#5 #6 #7 #8
notifies Nexus 1000V
2. During VM replication, Nexus
Nexus 1000V—VEM 1000V
Nexus 1000 -—VEM
Nexus 1000V copies VMW ESX VMW ESX
VM port state to new
host
3. Once VMotion 3.
completes, port on
new ESX host is
brought up & VM’s Nexus 1000V
MAC address is Network Update
ARP for VM1 sent
announced to the to network
vCenter
network Flows to VM1 MAC
redirected to Server 2 VSM
27. Mobility of Network & Security Properties
Virtualization Admin Benefits
Prevent ESX host/network config discrepancies from impacting
VMotion
– VMotion domains can be configured once and the vSwitch parameters across
the cluster will always be consistent with the physical network
Gain consistent visibility into VM-level I/O
– Virtual applications can be diagnosed using the same tools and method NOCs
currently use in the physical environment. 1 consistent operations model
provides faster MTTR of virtual applications
Secure I/O to VMs located in the DMZ
– The use of IP/Port security rules (also know as Access Control Lists) can lock
down traffic to/from a particular VM. For instance, a Web server in a DMZ can
have traffic limited only to Port 80 to support a Web Server. This rule set is
applied to the VM VNIC and moves with the VM during VMotion
28. Cisco Nexus 1000V
Increase Operational Efficiency
Virtualizing the Network Domain
Policy-Based Mobility of Network Non-Disruptive
VM Connectivity & Security Properties Operational Model
Server Server
VM VM VM VM VM VM VM VM
#1 #2 #3 #4 #5 #6 #7 #8
Cisco Nexus 1000V
Server Benefits VMW ESX
Network Benefits
VMW ESX
Unifies network mgmt and ops
Maintains existing VM mgmt
Reduces deployment time Improves operational security
Improves scalability Enhances VM network features
Reduces operational workload Ensures policy persistence
Enables VM-level visibility Enables VM-level visibility
vCenter
29. Non-Disruptive Operational Model
Virtualization Admin Benefits
VM workflow doesn’t change
– Virtualization administrator continues to leverage vCenter for VM creation,
maintenance, monitoring
ESX vSwitch configuration & management responsibility offloaded
– vSwitch and Port Groups now provisioned along with the physical network
infrastructure ensuring consistency, virtualization administrator subscribes
VMs to available Port Groups and vSwitch is dynamically provisioned
Equip Data Center operations teams to respond to applications
issues
– By extending the data center network operations model and troubleshooting
toolkit down to the virtualization infrastructure, customers can leverage
physical world tools and diagnostic procedures for their VM-based
applications – 1 consistent model for the whole data center
32. Cisco Nexus 1000V
Three New Features that Make a Difference
Encapsulated Remote NetFlow v.9 Private VLANs
SPAN (ERSPAN) with Data Export (PVLANs)
Mirror VM interface View flow-based stats Great for mixed use
traffic to a remote sniffer for individual VMs ESX clusters
Identify root cause for Captures multi-tiered Segment VMs w/o
connectivity issues app traffic inside a burning IP addresses
No host-based sniffer single ESX host
Supports isolated,
virtual appliance to Export aggregate stats community and
maintain to dedicated collector promiscuous trunk ports
Follows your VM with Follows your VM with Follows your VM with
VMotion or DRS VMotion or DRS VMotion or DRS
33. Nexus 1000V Deployment Scenarios
Pick Your Flavor
Rack Optimized
1. Works with all servers on Servers
the VMW Hardware Blade Servers
Compatibility List
2. Requires next version of
VMW ESX or ESXi
(1H 2009)
3. Works with ANY
upstream switch (Blade,
Top or Rack, Modular)
4. Works at any speed
(1G or 10G) Nexus 1000V
5. Nexus 1000V VSM can
be deployed as a VM or a
physical appliance
VSM
vCenter
35. SETAO Background
Responsible for urban transportation for metropolitan
area of Orleans
100,000 riders each day
24km MAN Metropolitan Area Network
High availability is critical
36. SETAO Design
Primary Data
Center VMotion
19 km
Backup Data
Center
DCI
VSS
SRM
37. Evaluation of Nexus 1000V beta
NX-OS consistent with rest of IOS-based network
– Provides visibility to each VM
Great for troubleshooting
– Tools to monitor and diagnose individual VM traffic
– Example: Use Cisco Discovery Protocol to isolate configuration errors
in physical network that cause VMotion problems
Very good integration with Virtual Center
– Example: Port Profiles automatically become Port Groups
Conclusion: Will deploy Nexus 1000V in production
– Already tested the migration in SEATO’s complex environment
38. Accelerate Server Virtualization
Enable, Simplify, Scale
Security and Policy Operation & Organizational
Enforcement Management Structure
Simplify Enable flexible
Enable VM-level management and collaboration with
security and policy troubleshooting with individual team
VM-level visibility autonomy
Scale the use of Scale with Simplify and
VMotion and DRS automated server & maintain existing
network VM mgmt model
provisioning
39. More Information…
VMWorld Europe 2009 Events
– TP34 – Designing the Next Generation Data Center – Ed Bugnion
– Nexus 1000V Demonstration – Cisco Booth
– VMware Nexus 1000V Hands-On LAB
On the Web
– http://www.cisco.com/go/1000v
40.
41. Thank you for coming.
Rate your session and
watch for the highest scores!