The Cisco Nexus 1000V has been supported in VMware vSphere hypervisor since 4.0 release (August 2009) up to the current vSphere release 5.5 update 2. We are happy to announce that the Nexus 1000V will continue to be supported in the latest vSphere 6 release which VMware recently announced. Customers who are currently running Nexus 1000V will be able to upgrade to the vSphere 6 release and the new vSphere 6 customers will have the Nexus 1000V as part of their choices for virtual networking.
Cisco is fully committed to support the Nexus 1000V product for our 10,000+ Advanced Edition customers and the thousands more using the Essential Edition software in all future releases of VMware vSphere. Cisco has a significant virtual switching R&D investment with hundreds of engineers dedicated to the Nexus 1000V platform. The Nexus 1000V has been the industry’s leading virtual switching platform with innovations on VXLAN (industry’s first shipping VXLAN platform), and distributed zone firewall (via Virtual Security Gateway released in Jan 2011).
The Nexus 1000V also continues to be the industry’s only multi-hypervisor virtual switching solution that delivers enterprise class functionality and features across vSphere, Hyper-V and KVM.
In the last major release of the Nexus 1000V for vSphere, version 3.1 (August 2014) we added significant scaling and security features and we continue to provide subsequent updates (December 2014) with the next release planned for March 2015. The recently released capabilities include:
- Increased scale per Nexus 1000V:
- 250 hosts
- 10,000 virtual ports
- 1,000 virtual ports per host
- 6,000 VXLAN segments with ability to scale out via BGP
- Increased security and visibility
- Seamless security policy from campus and WAN to datacenter with Cisco TrustSec tagging/enforcement capabilities
- Distributed port-security for scalable anti-spoofing deployment
- Enhanced L2 security and loop prevention with BPDU Guard
- Protection against broadcast storms and or attacks with Storm control
- Scalable flow accounting and statistics with Distributed Netflow
- Ease of management via Virtual Switch Update Manager (VSUM) – a vSphere web-client plug-in
One of the common questions coming from our customers is whether VMware is still re-selling and supporting the Nexus 1000V via VMware support?
VMware has decided to no longer offer Nexus 1000V through VMware sales or sell support for the Nexus 1000V through the VMware support organization as of Feb 2nd 2015. We want to reiterate that this has NO IMPACT on the availability and associated support from Cisco for the Nexus 1000V running in a vSphere environment. Cisco will continue to sell Nexus 1000V and offer support contracts. Cisco encourages customers who are currently using VMware support for the Nexus 1000V to migrate their support contracts to Cisco by contacting their local Cisco Sales team to aide in this transition.
For questions or help, please reach out firstname.lastname@example.org
Tags: ACI, Cisco Nexus, Cisco UCS, Nexus1000V, VMware, VMware vSphere, vsg, vsphere 6, VXLAN
Over the last 12 months I’ve been doing a lot of work that has involved the Cisco Nexus 1000v, and during this time I came to realise that there wasn’t a huge amount of recent information available online about it.
Because of this I’m going to put together a short post covering what the 1000v is, and a few points around it’s deployment.
What is the Nexus 1000v?
The blurb on the VMware website defines the 1000v as “..a software switch implementation that provides an extensible architectural platform for virtual machines and cloud networking.”, and the Cisco website says, “This switch: Extends the network edge to the hypervisor and virtual machines, is built to scale for cloud networks, forms the foundation of virtual network overlays for the Cisco Open Network Environment and Software Defined Networking (SDN)”
So that’s all fine and good, but what does this mean for us? Well, the 1000v is a software only switch that sits inside the ESXi (and KVM or Hyper-V, if they’re your poison) Hypervisor that leverages VMware’s built-in Distributed vSwitch functionality.
Read More »
Tags: #ciscochampion, Cisco Nexus, Nexus 1000v
Today at Microsoft’s Worldwide Partner Conference (WPC 2014) in Washington D.C. we entered into a new phase of our Microsoft relationship. Together Cisco and Microsoft announced a multi-year, worldwide sales and channel program focused on driving infrastructure solutions for Server Migration, Private Cloud, and SQL Server engagements. Based on key technologies such as UCS, Nexus, Hyper-V, and Windows Server 2012 R2 these solutions help to enable I.T. organizations to radically improve their I.T. effectiveness while improving their business outcomes.
At Cisco we believe our foundational technologies – with UCS as the compute platform, Nexus as the switching platform, and with UCS Manager and System Center management integration – provide customers an optimal infrastructure for their Microsoft Windows Server workloads of SQL, SharePoint, Exchange, and Cloud. Our industry leading UCS integrated infrastructure solutions combined with storage from EMC or NetApp, delivers an even more robust end-to-end value proposition via our FlexPod or VSPEX offerings to our customers. These solutions position our customers well on their respective journeys to the cloud. You’ve read my thoughts here; but let’s hear from Microsoft and their comments on Cisco, Microsoft, our partnership, and value to our joint customers:
We have focused heavily on infrastructure solutions for the Microsoft ecosystem over the past ~2 years and now that our UCS integrated infrastructure architectures are proven we will be putting more emphasis on discrete Microsoft workload solutions. Our initial focus will be on Microsoft SQL Server 2014 and how UCS and its differentiated features, such as Service Profiles and Cisco SingleConnect, deliver improved performance, availability, and scalability. Satinder Sethi, Vice President of UCS Engineering, details out the benefits of UCS and SQL Server 2014 in this video:
The solutions we deliver to our customers, whether they be private or hybrid cloud, workload or infrastructure focused, are architected and engineered by Cisco, and certified for the Cisco Validated Design (CVD) program as well as certified for the Microsoft Fast Track program. This delivers more value for customers as the prescriptive guidance in each solution offering enables customers to accelerate their deployments with lower risk.
If you happen to be at WPC 2014, please stop by the Cisco booth #801 to speak with our Experts; see things hands on; and simply learn a bit more. You can also read more about Cisco’s channel programs for the Microsoft ecosystem in Cisco VP Denny Trevett’s blog. Finally, please feel free to visit www.cisco.com/go/microsoft.
Tags: @ciscoDC, Cisco Nexus, Cisco UCS, Cisco UCS Manager, FlexPod, Microsoft, System Center, vspex
Cisco and Microsoft have been working closely to integrate our data center solutions to provide agile, secure and scalable platforms for private cloud, hybrid IT and modern business applications. The Cisco team is looking forward to showcasing these solutions at Microsoft TechEd 2014, May 12-15, in Houston, Texas.
We have a full line-up of demos, sessions and events that will highlight the unique benefits of the Cisco Unified Data Center for Microsoft environments and applications. If you’ll be in Houston for TechEd, drop by the Cisco booth to speak with Cisco experts and learn how you can take advantage of deep integrations between the Cisco Unified Computing System (UCS) and Microsoft Windows Server, Hyper-V and System Center, to deliver Microsoft applications in private or hybrid cloud environments.
Connect with Cisco in Booth 701
Learn about Cisco Data Center products and talk to Cisco solution experts in booth 701. We’ll be conducting live solution demonstrations on:
- 3-D UCS demos featuring FlexPod and VSPEX for Microsoft Private Cloud and Applications
- UCS Management with Microsoft System Center
- Network Visualization with Nexus for Hyper-V
- Cisco InterCloud Fabric
- UCS Invicta Series Solid State Systems
- Application Centric Infrastructure
You’ll come for the demos but you won’t leave empty handed. We’ll have exceptionally cool Cisco hats for visitors to our booth.
Cisco Showcase Sessions
Read More »
Tags: Cisco Nexus, Cisco UCS, cloud, data center, Microsoft, Microsoft Fast Track
Extensive Message Protocol (XMPP) is an open standard protocol based on XML (Extensible Markup Language). XMPP is designed to transport instant messages (IM) between entities and to detect online presence. It supports authentication of IM application and secure transport of messages over SSL/TLS. In XMPP entities can be bots, physical users, servers, devices or components. It’s really a powerful tool that has great potential for system administrators to add to their toolbox because:
- XMPP is powerful
- XMPP with Python is only 12 lines of code – trust me, it’s easy!
- XMPP only requires a single query for multiple nodes
- Status message can be used to track host presence
The Power of XMPP
For those of you that are not familiar with XMPP, it not only supports one-to-one messaging between entities but it also supports multi-party messaging (which enables an entity to join a chat room for the exchange of messages with several participants). The messages can be text messages embedded in XML format but XML can also be used to send control messages between entities as we will see with the presence stanza in a bit.
XMPP is widely used; Google uses it (for its Hangout application – formerly google chat) and so does Yahoo and MSN. At Cisco, we use Cisco Jabber extensively to communicate internally. The XMPP client function is now integrated in the Cisco Nexus 5000 series with the release 5.2(1)N1(7) and the Nexus 6000 series with the release of 7.0(0)N1(1). XMPP is an integral part of the single console access for Dynamic Fabric Automation (DFA) which is a powerful framework described in my previous blog.
The new Data Center Network Manager (DCNM) 7.0(1) is delivered as an OVA file that can be deployed quickly on an existing VMware-enabled server. Although DCNM comes with a lot of features that simplify the deployment of the Data Center fabric, we can pick and choose any service we want to use independently – which is great since DCNM comes with Cisco Jabber XCP and is license free. If you already have a XMPP service installed (like Openfire or ejabberd), it will not be a problem because everything discussed here is valid on any standard XMPP implementation.
On NX-OS devices, the XMPP feature is activated by configuring ‘feature fabric access’ and is part of the Enhanced L2 license (ENHANCED_LAYER2_PKG). Once activated, the switch becomes a XMPP client that needs to be registered on the server. In order to register it, XMPP requires the use of fully qualified domain names (FQDNs) to identify the domain server. If the switch does not have access to a DNS service, I recommend that you use the switch management network for messaging and a static host–to–IP address mapping in the switch configuration.
The switch will use its hostname to login to the XMPP service. If your XMPP server does not support auto-registration, you will need to register the switch and the rooms in the XMPP database beforehand. The DCNM OVA requires users and groups to be created via the CLI, and example of this user and group creation is:
[root@dcnm-ova ~]# appmgr add_user xmpp -u leaf0 -p cisco123
[root@dcnm-ova ~]# appmgr add_user xmpp -u leaf1 -p cisco123
User added. Read More »
Tags: Cisco Data Center Fabric, Cisco Nexus, DCNM, instant messaging (IM), NX-OS, open standard protocol, XML, XMPP, xmpp with python