Jose Martinez is an escalation engineer for server virtualization products in the RTP Technical Assistance Center. Jose joined Cisco in 1995 and has worked in multiple pre- and post-sales groups supporting different technologies, including Layer 2/Layer 3 switches, voice gateways, unified communications (Cisco CallManager), and most recently data center technologies (including Cisco UCS, Cisco Nexus 5000, and Cisco Nexus100v). He has presented in multiple Cisco Live events as well as traveled around the United States providing seminars and tech talks. Jose holds CCIE certification (number 1690) in Routing and Switching.
Matthew Wronkowski is an escalation engineer for server virtualization products in the RTP Technical Assistance Center. Matthew joined Cisco in 2001 and has worked in multiple pre- and post-sales groups, including the Cisco IOS Technology Center, researching and developing home gateway products. He joined the Cisco Technical Assistance Center in 2004 supporting large service provider voice networks. In mid-2010 he moved to the Unified Computing and Virtualization team, where he became a focal point for Cisco Nexus 1000v and Cisco UCS products. Matthew holds CCIE certification (number 21202) in Voice. He holds a master of science degree in bioinformatics from the Rochester Institute of Technology.
The following experts were helping Jose and Matthew to answer few of the questions asked during the session: Dave McFarland and Mike Timm. Dave and Mike are top UCS experts and have vast knowledge in related topics.
A. No, it does not disables vmotion. You can do direct I/O and still vmotion will work.
A. The VM still sits on the host and connects to the hypervisor. The system after some seconds of traffic, if it has the right components, switches modes and it takes the VM off the hypervisor. Once there it keeps switching traffic that way unless vmotion is needed.
A. VM-FEX is a distributed switch, which is managed from Unified Computing System Manager (UCSM). It has fewer features than Nexus 1000v.
A. Yes it is supported. Cisco Fabric Extender Transceiver (FET) SFP are listed in the matrix.
A. The VIC 1280 is an alternative choice to M81KR allowing increased blade bandwidth. M81KR is still available for purchase.
A. It is suggested to look at the compatibility matrix at www.cisco.com for confirmation.
A. Yes, it is still needed since multi-hop FCoE is not currently supported on the Fabric Interconnects. Multi-hop is on the roadmap for the next major release.
A. Yes, Nexus 4000 is available.
A. Probably at the end of February; however reach out to local accounts team for more information.
A. For login security UCS supports certificates, trustpoint, CA, LDAP, TACACS, and RADIUS. Also multiple authentication methods are possible. UCS also has Role Based Access Control (RBAC), which allows you to control what a person can change or do on the system. Version 2.0 allows creation of VLAN to create a separate path for traffic, so that you can have links going only to DMZ and links going only to rest of the network. For physical security UCS has many options in BIOS to protect from people reloading and booting a separate OS.
A. Multi hop FCoE is available in hardware although not available in software. The target date for multi hop FCoE support is the next major UCS software release.
A. UC on UCS still requires hypervisor installed locally or on fibre channel.
A. The vNIC has the QoS policy that can be applied to using the service profile for that particular SCSI booting.
A. Yes. This would be the best configuration option as bandwidth utilization is better allocated and improves redundancy capabilities.
A. For FI to IOM it is source-dest-mac. It is not configurable and is done by the system automatically. For 1280 to the IOM, it has more options up to the Layer 4.
A. You can enable QoS for a particular vnic using the GUI for a particular Service-profile.
A. If you are talking about firmware update of the IOM remember that the system allows you to update one side at a time. This means that complete loss of communication does not happen. Only one path is down at a time.
A. Release schedules for future releases are rather fluid but the current target is sometime in March. This can obviously change.
A. Yes, the eye "i" versions only of 5.0, 4.1u1 and 4.1u2. Only those versions support iBFT, which is what is used to configure the OS during install.
A. ESXi iSCSI boot is supported per the latest support matrix.