1278-Ucs Software Release 1.4

Unified Computing System
Software Release 1.4 (Balboa)
An Overview
UCS Product Management

SAVBU
December 2010
Rel v1.4 (Balboa) © 2010 Cisco Systems, Inc. All rights reserved. Public 1
UCS Software Release 1.4 (Codename: Balboa)
Feature Summary
Compute Authentication & Security

• Support for new UCS B230 Blade Server • Simpler integration with MSFT Active Directory
• UCS C-Series server integration into UCS Manager • Multiple simultaneous authentication systems
• Multi-chassis power capping for UCS B-Series • Multi-user KVM enhancements
Ethernet and Fibre Channel

• Full vNIC failover w/o NIC teaming/bonding with Stateless Computing
FabricFailover/FabricSync • Scheduling of service profile changes
• SPAN support on UCS 6100
• CIMC IP address abstraction
• Higher VLAN scalability 1024
• Service profile “pre-flight” checks
• Higher logical port scalability 8000
• Higher virtual interface Scalability 2000
• PVLAN support
• FC trunking and port channel (in NPV mode) Management & Monitoring
• Direct connect Ethernet Appliance • SNMP GET support for ALL UCS components
• Limited Direct Connect FC Storage • Syslog enhancements
• UCS 6100 licensing enforcement/warnings
• Usability enhancements
UCS
Software Release 1.4

Ethernet Stateless Computing
Fibre Channel Management & Monitoring
UCS Manager 1.4 supports UCS B230 M1
Industry leading compute density in half-blade form factor
 2 Intel Xeon 7500 or 6500

(Nehalem EX)
 32 DIMM Slots; up to 512 GB
OPTIMIZED FOR BENEFITS
Memory
 Single instance  Dual Port Converged I/O  Lower operating and
and transaction— Adapter; 20 MB/s licensing expenses
intensive database  Two Optional SSD  Higher density
 Desktop  Reduced foot-print
virtualization (VDI)
 Financial Services
and SPs
High Density Compute: 16 cores per blade
UCS Manager C-Series Integration
Customer benefits
 Unified Management across entire UCS portfolio
 Advanced capabilities extended to rack servers
UCS
Manager
Feature details UCS

UCS6100
6100 UCS
UCS6100
6100
 C-Series servers connectivity

Management connectivity through FEX to FI Nexus
Nexus2248
2248 Nexus
Nexus2248
2248
Data connectivity directly to Fabric Interconnect
 Stateless computing
Service profiles extended to C-series
Migration among compatible B & C series servers
 All UCSM management services

Automated discovery
Fault and monitoring
Firmware updates
Mgmt Connection
Data Connection
UCSM C-Series Integration in UCS 1.4
Device support and scaling
 Server Support
• C200, C210, C250
• C460 support will follow-on in a later release
 Adapter support
• Cisco UCS P81E Virtual Interface Card
• Emulex OneConnect Universal Converged Network Adapter
• QLogic QLE8152 Dual Port 10 Gb Ethernet to PCIe Converged Network Adapter
• Broadcom NetXtreme II 57711 Dual Port 10 Gb Ethernet PCIe Adapter Card
• Intel 82599 (Niantic) Dual port 10Gb Ethernet Adapter
• Homogenous adapter support only upto 4 adapters; No mix n’ match adapters in this release
• For UCS P81E upto *2* adapters per C-series server with 112* interfaces
(*under verification)
 Number of C-Series servers supported per UCSM:

Upto the maximum number of available server ports in the fabric interconnect
 C-Series only and mixed B- & C-series configuration will be supported

 LOM Ports on the server can be used only as management ports
 PCIe cards other than the ones listed above are not supported
UCS Chassis and Multi-Chassis Power Cap
Customer benefits
 Eliminate power capacity wastage in Data Center Power allocated without power capping
Power
(faceplate)
 Cap multiple chassis from a single interface
Power capacity savings

Feature details with
Chassis Power Capping
 Group Level Power cap Power
Power allocated
allocated with
with power
power capping
capping
• Set a single cap for multiple chassis that share a power feed
• Automatic static distribution of power to chassis in group
 Dynamic Intra-chassis power redistribution

• Blade power allocation based on priority and blade
configuration Actual chassis power draw
• High power blades can borrow power from low power blades
• No performance impact under normal operation
 Service Profile Priorities

• Customer control of application performance
• Ensures high priority workloads get more power when Time
group/chassis cap is reached
UCS Software Bundling
Infrastructure & Server Bundles
Customer benefits
Infrastructure Bundle: UCS
 Manager
HW support decoupled from major SW releases • UCSM
• Fabric Interconnect
 Quicker adoption of new server & adapter types (NX-OS)
• Fabric Extender
(IOM) Firmware
Feature details • Chassis Mgmt.
Controller
 Unbundling of UCS software bundles
 Server and adapter packs aimed at new server
and adapter hardware Server Bundle:
• CIMC
 Off-cycle introduction of server and adapter packs • BIOS
in-sync with hardware releases • RAID Controller FW
 Next major software releases will incorporate • Catalog File
previous modular server and adapter packs • UCSM Mgmt Extn.
 Enables faster introduction of new server and

adapters without waiting for next major SW • Adapter FW
release • Catalog File
• UCSM Mgmt Extn.
UCS Software Bundling
What bundles do you need?
 If your environment has

• Fabric Interconnect and B-Series Chassis only:
Infrastructure Bundle
B-Series Blade Server Bundle
• C-Series servers as well:

+ C-Series Rack-Mount Server Bundle
• Off-cycle addition of memory DIMMsor hard drives

+ Capability Catalog
The Capability Catalog will be cumulatively bundled into every Infrastructure
Bundle.
UCS

UCS Manager
Active Directory (LDAP) Groups
Integration
Customer benefits
 Unified user privilege control within AD

 Easier alignment for security and server admin
UCSM
Feature details
Server Network
 AD user groups looked up by UCSM Admin Admin
 UCSM role assignment to AD groups

Roles Privileges
 Users’ role membership based on AD
group membership Active Directory
 Single place control of user privileges by

changing user AD group membership
User
User Groups
UCS Manager
Active Directory (LDAP) Groups Integration
UCS Manager
Multi Scheme Authentication
Customer benefits
 Integration into mixed authentication environs. Radius

Radius
 Support for segmented authentication
Feature details
 Concurrent multi-scheme authentication

• LDAP (Active Directory) LDAP
LDAP
(Active
• TACACS+ UCSM (Active
Directory)
Directory)
• RADIUS
 Authentication with multiple AD domains

• Multiple AD domains segmentation by region,
organization etc. can be input into UCSM
• UCSM communicates with multiple AD domain
controllers to authenticate a user TACACS+
TACACS+
UCS Manager
Multi Auth Domain Setup
UCS Manager
Multi Auth Login Screen & API
UCS Manager
Multi-User KVM Security Enhancements
Customer benefits
 Secure KVM use in multi-user environments

 Granular control of KVM access
Feature details
 First user KVM ownership

• First KVM user gets RW privileges to session
• First user grants permission for other sessions
• Second KVM session is read-only by default
 KVM admin control

• KVM forced termination by UCS admin user
UCS

UCS Manager
Service Profile Deployment Scheduling
Customer benefits
UCS
 Service Profile disruptions in maint. windows Manager
 Plan ahead design changes for service profiles
Service Profile: CRM-App1 App
Design
Feature details Network: Sales-VLAN
OS
Network QoS: High
 Maintenance policies MAC: 08:00:69:02:01:FC-E

WWN: 5080020000075740-3
Firmware
Firmware
BIOS: Version 1.03
New policy contains schedule when SP can be changed Boot Order: SAN, LAN Network
Network
Policy can be mapped to one or more SPs
 Schedule disruptions
 Resource reservation Service Profile: CRM-App1 App
Deploy
SP acquires required resources prior to deployment Network: Sales-VLAN
OS
Network QoS: High
Resources are held until deployment MAC: 08:00:69:02:01:FC-E
Firmware
Firmware
WWN: 5080020000075740-3
Eliminates future resource contention BIOS: Version 1.03
Network
Boot Order: SAN, LAN Network
UCS Manager
Service Profile Deployment Scheduling
Maintenance Policies are part of Service Profiles
UCS Manager
CIMC IP address in Service Profile
Customer benefits
 “Follow the server” KVM access

 10.21.20.21
Fully self contained server identification 10.21.20.21
SP
SPCIMC
CIMCIP
IP11
Feature details Service Profile
 Current IP address assignment continues 10.21.32.44

10.21.32.44
 New , second IP address for CIMC Native

Native CIMC
CIMCIP
IP11
 Second IP address associated with

Physical
Physical Server
Server 11
Service Profile
 Upon SP deployment CIMC can be
accessed through both IP addresses 10.21.32.45
10.21.32.45
Native
Native CIMC
CIMCIP
IP22
 When SP moves, second IP address
moves to new server
Physical
Physical Server
Server 22
Migration Validation for Service Profiles
Customer benefits
 Increased infrastructure availability for OS/app

 Increased utilization due to HW repurposing
Feature details
 “Pre-flight” check on the compatibility of a
Service Profile with a server
 Service Profile migrations more consistent
SP remembers the HW it was associated to
If new HW has meaningful differences  warning
 Differences do exist at OS layer

Service Profile: CRM-App1
Windows, Linux, Vmware behave differently App
Network: Sales-VLAN
OS
Network QoS: High
MAC: 08:00:69:02:01:FC-E
Firmware
Firmware
WWN: 5080020000075740-3
BIOS: Version 1.03
Boot Order: SAN, LAN Network
Network
UCS

UCS Manager
SNMP GET support
Customer benefits
 Easy integration to 3rd party mgmt tools UCS

 SNMP based corelation for trap information Manager
Feature details Fabric

Interconnects
 Release 1.3 provided SNMP trap support earlier
 Access to full information model of UCS: Fabric
Extender
Access same information as XML API
SNMP Traps and GETs

• Fabric interconnects & Fabric extenders
• Chassis Chassis
• Blades (B-Series)
• Rack servers (C-Series)
 58 new MIBs to be posted on Cisco.com
Blade Servers
 Any additions/changes to model, automatically results in
regeneration of MIBs
 SNMP access is read-only, no SNMP SET support planned
Rack Servers
UCS Manager
Licensing Enhancements
Customer benefits
 Licensing now integrated and accessible directly from UCS

Manager
 Easy “check-in/check-out” of licenses (for example, for
device replacement)
Feature details
 UCS Manager integration
• Licenses can now be assigned / revoked from UCS Manager
 Ports are licensed by count
• User does not need to re-assign a port license to use different physical
ports on the UCS 6100 Series fabric interconnects
• Only fixed ports need to be licensed (in other words, expansion module
ports do not require a license)
• Same 8/16 freely-licensed ports included with UCS6120XP / 6140XP
> show license usage
• Ports must be licensed whether configured as 1GE or 10GE Switch A:
Feature Status Expires Count
 Grace period Used Switch File Id
• Each port that is activated but for which there is no available license ETH_PORT_ACTIVATION_PKG ok never
8 8 FLC12110018 20080612113521765 1
count will start on a 120-day grace period
• Status of ports on grace period / days remaining visible in UCS
Manager
• If ports are used in grace period, WARNING level alerts are generated
• Note: Upon expiration, UCS Manager will generate CRITICAL level
alerts but will not shutdown active ports
UCS Manager
Custom Naming
Users will be able to enter custom labels for Service Profiles, Chassis, Servers.
Labels can be free form text and can be displayed, sorted and filtered
Sort
Sort
Display
Display
Filter
Filter
UCS Manager
Firmware Descriptions
Additional information including model name for easier selection of firmware
UCS Manager
Usability – Firmware upload
Support for direct upload from client running UCSM GUI
UCS Manager
Syslog Categorization
New categorization to differentiate components & additional filtering capabilities
UCS Manager Resources
 UCS Manager Product Page on Cisco.com

http://www.cisco.com/en/US/products/ps10281/index.html
 UCS Manager Whitepapers

http://www.cisco.com/en/US/products/ps10281/prod_white_papers_list.html
 Cisco Developer Network for UCS Manager

http://developer.cisco.com/web/cdc/tech/unifiedcomputing
 UCS Platform Emulator (UCSPE) download

http://developer.cisco.com/web/unifiedcomputing/ucsemulatordownload
 UCS Manager Software Downloads

http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=282567938
Q&A
UCS

Feature Summary

• Support for new UCS B230 Blade Server
• Simpler integration with MSFT Active Directory
• UCS C-Series server integration into UCS Manager
• Multi-chassis power capping for UCS B-Series • Multiple simultaneous authentication systems
• Multi-user KVM enhancements

• Direct connect Ethernet Appliance
Stateless Computing
• PVLAN Isolated access support • Scheduling of service profile changes
• Full vNIC failover w/o NIC teaming/bonding with • CIMC IP address abstraction
FabricFailover/FabricSync • Service profile “pre-flight” checks
• Higher virtual interface Scalability 2000 Management & Monitoring
• Fabric Extender Transceiver Support • SNMP GET support for ALL UCS components
• Management Interface monitoring and failover • Syslog enhancements
• FC trunking and port channel (in NPV mode) • UCS 6100 licensing enforcement/warnings
• Limited Direct Connect FC Storage • Usability enhancements
UCS Manager 1.3(1) Release
ExistingConnectivity Types
IP Storage FC Storage
Uplinks FC/Eth
Upstream Links connecting to LAN
LAN SAN and SAN
Server Ports
Eth Uplink FC Uplink Eth Uplink FC Uplink Downstream links connecting to
Server Server servers though IOM
© 2010 Cisco and/or its affiliates. All rights reserved. Public 33

New Connectivity Options
New connectivity choices are Appliance, Monitoring (FC and Eth) and
Storage target ( FC and FCOE )
IP Storage LAN SAN FC/FCOE Storage
Appliance FC Target
Eth Monitor FC Monitor

Appliance Direct Connection “End Host”
UCS simplifies appliance connectivity
In-direct Connection Direct Connection

IP Storage IP Storage
Inter switch bandwidth Simplified connectivity
consumption Optimized uplink bandwidth
Several switches/hops utilization
LAN
End Host Mode
UCS 6100 A UCS 6100 B
UCS 6100 A UCS 6100 B

UCS 6100 Switching Modes
End Host Mode Switch Mode
The external LAN sees the UCS The UCS 6100 acts like a
6100 as an end-host with multiple traditional Ethernet switch with support
adapters. No Spanning Tree protocol on for Spanning Tree protocol on the uplink
uplink ports. ports
Active/Active use of uplinks by Some uplinks connected to the
pinning external switches may be blocked by STP.
All uplink ports should be Only PVST+ is supported
connected to the same Layer 2 network Mac-add learning is enabled on
More scalable than switch mode uplink/server interfaces
since the control plane is not stressed as
an Layer 2 switch.

Appliance Direct Connection “End Host”
Ethernet appliance support enhanced to include “End Host” mode
Today, UCS 1.3 (Aptos+) UCS 1.4 (Balboa)

Ethernet Appliance Ethernet Appliance
Appliance port
Trunk 10,100,101 uplink Port Trunk 10,100 or Access 100
Switch Mode End Host Mode

UCS 6100 UCS 6100
UCS B-Series UCS B-Series

Fabric Interconnect mode - Switch mode Fabric Interconnect mode - End-host mode
Port type – Uplink only Port type - Appliance
Can’t define VLANs on uplink to appliance (VLAN filtering) VLAN filtering available
Advanced feature such as QOS not available Advanced features such as QOS available
UCS 1.4 (Balboa) onwards “End host” mode is recommended

Supported Ports and Configuration
Ethernet Appliance
Any fixed 10G or 1G
Any expansion port Port-Channel Single port
Fixed Ports Expansion

Ports
UCS 6100 UCS 6100
UCS B-Series
Non-vPC port-channel and singe port configurations are supported

NIC teaming or port-channeling is required on the appliance to have resilient
connectivity
UCSM Appliance port - Visual
QOS settings
Specify VLANs
Configure static MAC

Feature Summary

• Multiple simultaneous authentication systems
• Multi-chassis power capping for UCS B-Series

• Direct connect Ethernet Appliance Stateless Computing
• Scheduling of service profile changes
• PVLAN Isolated access support
• Full vNIC failover w/o NIC teaming/bonding with
Management & Monitoring
• Management Interface moniroting and failover • Syslog enhancements

Unified Monitoring
Monitor FC and Ethernet traffic with a single analyzer
Today Unified Monitoring
Eth FC Eth
Analyzer Analyzer Analyzer
LAN SAN
LAN SAN
UCS 6100 UCS 6100
Port 0 Port 0
vNIC
vNIC 1
1 vHBA
vHBA vNIC
vNIC 1
1 vHBA
vHBA
UCS server A UCS server A
Requires a dedicated FC analyzer Ability to monitor FC and Eth traffic using a Eth analyzer
 Need separate analyzers for FC and Eth  Single analyzer to monitor FC and Eth
Requires specialized in-line TAP, expensive Eliminates expensive FC analyzer

vNIC and vHBA Level Monitoring
vNIC level monitoring and troubleshooting capability
Traditional SPAN vNIC Level Monitoring

Eth Analyzer Needs only vNIC 2 Eth Analyzer
Monitor vNIC 2,
but saw vNIC 1 &
saw only vNIC 2
3
Eth1/1
Nexus 5000 UCS 6100
Port 0
UCS 6100
Port 0
vNIC1 vNIC2 vNIC3
M81KR
VIC
VM VM VM
vNIC1 vNIC2 vNIC3 VM-FEX mode
M81KR
VIC
VM VM VM
 Complex connectivity  Simple connectivity

 Inability to monitor specific VM traffic  Ability to monitor specific VM traffic
 Lack of visibility (bulk capture)  Granular visibility

Summary
A total of 4 local SPAN sessions per UCS system, 2 on each UCS 6100
Un-used licensed port UCS 6100 A UCS 6100 B
Cluster Link
Trouble Eth Network Trouble FibreChannel

shooting Analyzer shooting Analyzer
Tool Tool
Things to remember :
 Configure identical monitoring sessions in both fabrics for failover and load-balanced traffic
flows.
 vHBA is available to be monitored in both FC and Eth monitoring configurations
 Monitoring session of a VM using PTS not persistent after a vMotion (VIF is changed) Future
enhancement.

UCSM Monitoring- Visual
SPAN destination can be any unused licensed port

UCSM Monitoring- Visual
Support for various Eth and FC monitoring sources

Feature Summary



VLAN based Layer-2 separation
VLAN Deployment  L2 separation with VLANs

 A vlan or more per tenant/application/function
 VLAN scalability on various platforms is a
UCS 6100 UCS 6100
deciding factor of NW scale
Port 0 Port 1 Port 0 Port 1
vNIC
vNIC 1
1 vNIC
vNIC 1
1 vNIC
vNIC 2
2
No of VLANs used = 3
Bare metal
VM VM VLAN A
VLAN B
VLAN C
Tenant A Tenant B Tenant C

PVLAN based Layer-2 separation
Single Isolated PVLAN to provide v NIC level layer 2 separation
PVLAN Deployment  L2 Separation with Isolated PVLAN

 Single isolated VLAN for all tenants/apps
 Provides same level of isolation as with VLAN
UCS 6100 UCS 6100
 VLAN limits is no longer scalability limiting
Port 0 Port 1
factor
Port 0 Port 1
 Useful for Bronze tier separation
M81
vNIC
vNIC 1
1 vNIC
vNIC 1
1 vNIC
vNIC 2
2
KR
VIC No of VLANs used = 1
Bare metal
VM VM Isolated VLAN A
Tenant A Tenant B Tenant C

PVLAN on the UCS design consideration
 Only PVLAN Isolated access is supported

 One Isolated per primary
 Can not carry PVLAN and regular VLANs on the same
vNIC
 Community PVLAN is not supported
 Promiscuous port is not supported

PVLAN with Nexus 1000v
Today
Promiscuous on the Nexus 1000v.
Cat6500 – L3
UCS 6100 UCS 6100

No special PVLAN configuration is
required, UCS treats primary VLAN
like any regular VLAN.
Promiscuous Port vNIC vNIC vNICs are promiscuous trunks,

terminate PVLAN on the Nexus
Nexus 1000v 1000v . Only supported config
with UCS
VM1 VM2 VM3
Point to N1kv documentation

UCS 1.4 (Balboa)
Requires minimum of 2 vNICs, one
Promiscuous outside of the Nexus 1000v vNIC for isolated VLAN and one vNIC
for carrying regular VLANs for service
Promiscuous Port
Backup console, vMotion and control.
Cat6500 – L3 Recommendation: Fabric failover is
recomended for HA assuming 2 vNIC
UCS 6100 UCS 6100 configuration
Enable PVLAN Isolated Access
vNIC vNIC
Isolated PVLAN Trunk carrying regular VLANs:
Adapter
Adapter service console, vMotion and
control
Nexus 1000v
VM1 VM2 VM3
For more details check PVLAN tech note -

UCS 1.4 (Balboa)
Isolated PVLAN shared between Nexus 1000v and Bare metal
Promiscuous Port
Backup
Cat6500 – L3 trunk
switchport mode trunk
switchport trunk allowed vlan 100,101
UCS 6100 UCS 6100 Uplink port
All vlans are allowed
vNIC vNIC Choose a vNIC for isolated pvlan on Bare metal

vNIC Adapter
Adapter vNIC and Nexus 1000v
Assign VLAN 101
Adapter
Adapter Nexus 1000v Adapter
Adapter Isolated VLAN 101
Bare metal Bare metal

VM1 VM2 VM3

PVLAN on theUCS summary
 One Isolated PVLAN is supported with Menlo

adapter
 VIC (PALO) is recommended for traffic load-sharing
and HA
 VMware DVS does not support native VLAN on the
trunk hence Isolated PVLAN on the UCS does not
work with VmwareDVS.

PVLAN using the UCSM - Visual
Primary and Secondary VLANs and their mapping using UCSM
Private VLAN on The UCS
Configuration and Management

Feature Summary



UCS Manager 1.3(1) Release or earlier
Fabric based NIC teaming
FabricFailover
 Chassis backplane (or Fabric) provides

redundant path for each vNIC
 HW based active/standby failover
mechanism for Eth traffic
 Host OS un-aware of failure and recovery
 Unlike OS NIC Teaming, redundancy
provided with single interface
 After failover:
 Transmit GARP
 Multicast Group reRegistration
Enable fabric failover in vNIC creation

UCS Manager 1.3(1) Release or earlier Animated Slide
FabricFailoveron UCS
Return traffic for MAC

FabricFailover
MAC C MAC C
Ten 1/1 Ten 1/2
 Fabric failover load-balances traffic on
per vNIC basis Ten 1/1
Ten 1/2
 Palo provides up to 58 vNICs gARP

 Each vNIC maps to one of the fabric for MAC C
active data path

 When active path fails, failover to UCS 6100 UCS 6100
standby fabric.
 6100 updates path changes to MAC A MAC B
upstream switches via gARP of vNIC Eth 0 Eth 1
MAC upon active link failure
MAC C
UCS Server

UCS Manager 1.4(1) Release Animated Slide
FabricFailoverand Sync on UCS
Return traffic for MAC NEW
FabricSync
MAC C MAC C
Ten 1/1 Ten 1/2
Keeps mac address table synchronized
between FI’s Ten 1/1
Ten 1/2
6100 updates path changes to upstream gARP

MAC D
switches via gARP not only vNICMACs
but also VMMACs behind a vSwitchupon
active link failure UCS 6100 UCS 6100
Always enabled
MAC A MAC B
Eth 0 Eth 1
MAC C
UCS Server
VM
MAC D

Hyper-V Network Link Redundancy
No redundancy for Hyper-V Link
Switch 1  Can only connect a single NIC to a virtual switch in
Hyper-V
 Single point of failure
Hyper V
vSwitch
Server
VM

Hyper-V Network Link Redundancy
Hyper-V Link redundancy with NIC teaming
Switch 1 Switch 2  Hyper-V does not support NIC teaming or bonding
 Requires 3rd party intermediate NIC teaming driver
software to provide network link HA
LAN Primary NIC LAN Secondary NIC  Officially not supported by Microsoft technical
Virtual Machines LAN NIC team adapter
support
Hyper V
vSwitch
Server
VM Server
– Source Microsoft support website http://support.microsoft.com/kb/968703 date 09/22/10

“Since Network Adapter Teaming is only provided by Hardware Vendors, Microsoft does not provide any support for this
technology thru Microsoft Product Support Services. As a result, Microsoft may ask that you temporarily disable or remove
Network Adapter Teaming software when troubleshooting issues where the teaming software is suspect.”


EnhancedHyper-V Network Link Redundancy
FabricFailover with FabricSync enhances Hyper-V Link redundancy
 Fabric failover provides hardware based
redundancy and failover
UCS 6100 UCS 6100
 Microsoft fully supports fabric failover based
configuration
Eth 0 Eth 1
 Eliminates need for un-supported software
Redundant
path
teaming drivers
Hyper V
vSwitch  Predictable and faster failover (confirm)
VM UCS Server

Feature Summary


• Management Interface monitoring and failover • Syslog enhancements

Management Interface Failover
MGMT
6100-A Primary 6100-B Secondary
Cluster Link
1.3(1) or earlier :
VIP does not failover to UCS 6100 secondary
Recover access by manual failover using CLI of the UCS 6100
secondary
KVM/IPMI/SSH IP does not failover

MGMT
6100-A Primary 6100-B Secondary
Cluster Link
1.4(1) :
VIP failover to UCS 6100 secondary upon active MGMT port failure
KVM/IPMI/SSH IP fails over to the available fabric
 Failover delay is 90 sec to limit CPU churn due to continues interface flaps
Managing instance is not state full. Re-login is required for VIP and
KVM/IPMI/SSH IP.


Feature Summary



Increased Scalability
UCS 1.4 Software (Balboa) Increases overall scalability of the UCS
system, following table provides comparison between UCS 1.3 and
UCS 1.4 Software
UCS 1.3 (Aptos+)
Feature Name June 2010 UCS 1.4 (Balboa)
VLANs per FI 512 1024
STP logical ports 3800 6000
VIFs 1000 2000
Number of Chassis 14 20

Increasing Chassis support
UCS 1.3 Software UCS 1.4 Software

14 Chassis 20 Chassis

Summary
 Fabric Extender Transceiver (FET) is supported in

UCS 1.4. Software Working with TMG group to offer in
UCS SKU.
 Support PVLAN Isolated access only, understand the
customer requirements as some customer currently may
be using community for cluster traffic and VMware VDS
 Recommend VIC (PALO) for scalable PVLAN
implementation
 Recommend FabricFailover for Hyper-V based
deployments.

UCS Networking Resources
 PVLAN Tech note

http://developer.cisco.com/web/cdc/tech/unifiedcomputing
 SPAN Tech note

http://developer.cisco.com/web/unifiedcomputing/ucsemulatordownload

Q&A

UCS

Agenda
 Storage Connectivity for UCS Today
 Limitations
 New Topologies and Features in UCS 1.4 Software

(Balboa)
 Use cases for Direct Connect Storage

Storage Connectivity with UCS 1.3(1)
LAN
NAS
NAS STORAGE
STORAGE CLOUD
LAN
CLOUD
FC
FC STORAGE
STORAGE
LAN Switch SAN Switch
LAN Switch SAN Switch
End NPV/End
NPV/End Host
Host Mode
Mode
End Host
Host Mode
Mode
Switch
Switch Mode
Mode
NAS
NAS STORAGE
STORAGE

Limitations with UCS Release 1.3(1)
 FC Storage
No storage connectivity directly to Fabric Interconnects
Need upstream SAN switches
No FC Port Channels
No VSANTrunking
 NAS Storage
Direct connection of NAS appliance requires Fabric Interconnects
to be in switch mode (STP)

Exec Summary: UCS 1.4 Storage Features
 New Direct Connect Topologies introduced
Both FC and NAS
Allows lower cost point for small UCS Pod like
deployments
 FC Port Channeling and VSAN Trunking

More flexibility in engineering FC traffic

Enable Direct Connection of FC Storage
Customer benefits FCoE Storage FC Storage
 Support to connect FC and FCoE storage to

6100
 Fewer hops and reduced latency to access
the storage
 End to end FCoE topologies possible
Feature details FC Target Ports
 Support for NetApp and EMC direct connect

UCS 6100 UCS 6100
storage
 Zoning configuration not supported, but zoning
may be inherited from upstream switch
 LUN security through LUN masking in the
array
 Ethernet and FC switching modes are
independent
UCS B-Series

Hybrid Topology with direct-attach and SAN
SAN Fabric Storage Arrays
Fibre Channel
Fabric A Fabric B
Ethernet
Core
Direct Attach Unified I/O
FCoE
FC Storage
FCoE Storage
SAN A SAN B
UCS 6100 UCS 6100
Security via zoneset merge

and/orLUN Masking on the Array
Controller
UCS B-Series

Enable Direct Connection of NAS Appliances
NAS Appliance
Customer benefits
UCS 1.4
 NAS appliance connected to Fabric Appliance Port
Interconnects in “END HOST” Mode
End Host
 Eliminates additional access-layer switches
Feature details
 Support for NAS (Ethernet appliance) in End
Host (general best practice) without putting
6100 in switch mode UCS B-Series
NAS Appliance
 New NAS port type to support this functionality
Current
 Support for advanced features like VLAN Uplink Port
Filtering and QoS
Switch Mode
UCS B-Series
FC Port Trunking
Customer benefits
 Provide isolation to SAN traffic over the same
physical FC link
 Help consolidate FC infrastructure
Feature details
 fNICs (of vHBAs) can be on different VSANs
 All VSANs will be trunked on every uplink FC

port
 Scalability: Max of 32 VSANs per UCS system SAN A SAN B
VSAN A VSAN C
 FC trunking supported in FC end host and
VSAN B VSAN D
switch mode

FC Port Channels
Customer benefits
 Aggregate and maximize available bandwidth
while maintaining isolation
 Increases resiliency and guard against port
failures
Feature details
vFCs
 Up to 16 FC ports can be aggregated together for
a single port channel
ISL / Port
Channel
 Different combination of FC ports from different
expansion modules on the FI can be placed on
the same port channel
 VSANs can be trunked over the port channel SAN A SAN B
 VSAN trunking and port channel supported for VSAN A VSAN C

both NPV and switch mode FI operation VSAN B VSAN D

Direct Connect Storage - Use Cases
 Commercial segment
 Test/dev environments
 Flat scale-out architectures for cloud-type deployments
 Architectures migrating from FC to FCoE storage

Storage Vendor Support
 UCS 1.4 Direct Connect will be EMC and NetApp only for
all topologies (FC, FCoE, NAS)
 Support for more vendors based on business cases
 Please consult the URLs below early in the sales cycle

Palo and Storage Current State of Qualification
http://www.cisco.com/en/US/prod/ps10265/at_work_promo.html#~si
,
General HCL for UCS
http://www.cisco.com/en/US/products/ps10477/prod_technical_refer
ence_list.html

Q&A


1278-Ucs Software Release 1.4

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1278-Ucs Software Release 1.4

Uploaded by

Copyright:

Available Formats

Unified Computing System

Software Release 1.4 (Balboa)

UCS Product Management

Compute Authentication & Security

Ethernet and Fibre Channel

Compute Authentication & Security

 2 Intel Xeon 7500 or 6500

High Density Compute: 16 cores per blade

Feature details UCS

 C-Series servers connectivity

 All UCSM management services

 Number of C-Series servers supported per UCSM:

 C-Series only and mixed B- & C-series configuration will be supported

Power capacity savings

 Dynamic Intra-chassis power redistribution

 Service Profile Priorities

 Enables faster introduction of new server and

 If your environment has

• C-Series servers as well:

• Off-cycle addition of memory DIMMsor hard drives

Compute Authentication & Security

 Unified user privilege control within AD

 UCSM role assignment to AD groups

 Single place control of user privileges by

 Integration into mixed authentication environs. Radius

 Concurrent multi-scheme authentication

 Authentication with multiple AD domains

 Secure KVM use in multi-user environments

 First user KVM ownership

 KVM admin control

Compute Authentication & Security

 Maintenance policies MAC: 08:00:69:02:01:FC-E

Policy can be mapped to one or more SPs

 “Follow the server” KVM access

Feature details Service Profile

 Current IP address assignment continues 10.21.32.44

 New , second IP address for CIMC Native

 Second IP address associated with

 Increased infrastructure availability for OS/app

 Differences do exist at OS layer

Compute Authentication & Security

 Easy integration to 3rd party mgmt tools UCS

Feature details Fabric

SNMP Traps and GETs

 Licensing now integrated and accessible directly from UCS

 UCS Manager Product Page on Cisco.com

 UCS Manager Whitepapers

 Cisco Developer Network for UCS Manager

 UCS Platform Emulator (UCSPE) download

 UCS Manager Software Downloads

Compute Authentication & Security

Compute Authentication & Security

Ethernet and Fibre Channel

© 2010 Cisco and/or its affiliates. All rights reserved. Public 33

IP Storage LAN SAN FC/FCOE Storage

Eth Monitor FC Monitor

© 2010 Cisco and/or its affiliates. All rights reserved. Public 34

In-direct Connection Direct Connection

UCS 6100 A UCS 6100 B

© 2010 Cisco and/or its affiliates. All rights reserved. Public 35

© 2010 Cisco and/or its affiliates. All rights reserved. Public 36

Today, UCS 1.3 (Aptos+) UCS 1.4 (Balboa)

Switch Mode End Host Mode