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 &

Support for new UCS B230 Blade
Server
Security
UCS C-Series server integration  Simpler integration with MSFT Active
into UCS Manager Directory
Multi-chassis power capping for UCS Multiple simultaneous
B-Series authentication systems
 Multi-user KVM enhancements

 Ethernet and Fibre
Channel
 Stateless Computing
 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
SPAN support on UCS 6100

Higher VLAN scalability 1024
Higher logical port scalability  Management &
8000
Higher virtual interface
Monitoring
Scalability 2000 SNMP GET support for ALL UCS
components
PVLAN support
Syslog enhancements
FC trunking and port channel (in
NPV mode) UCS 6100 licensing
enforcement/warnings
Direct connect Ethernet Appliance
Usability enhancements
Limited Direct Connect FC Storage
UCS
Software Release 1.4
Compute Authentication & Security

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 and §Dual Port Converged I/O §Lower operating 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
§ UCS
§Advanced capabilities extended to rack servers
§
Manager
Feature details UCS 6100 UCS 6100
§ C-Series servers connectivity

 Management connectivity through FEX to FI Nexus 2248 Nexus 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 allocated with power capping
 Set a single cap for multiple chassis that share a
power feed
 Automatic static distribution of power to chassis
in group
Actual chassis power draw
§ Dynamic Intra-chassis power redistribution
 Blade power allocation based on priority and
blade configuration
 High power blades can borrow power from low
power blades
 No performance impact under normal operation Time
§ Service Profile Priorities

 Customer control of application performance
 Ensures high priority workloads get more power
UCS Software Bundling
Infrastructure & Server Bundles
Customer benefits
UCS
§HW support decoupled from major SW releases Infrastructure Bundle: Manager
UCSM
§Quicker adoption of new server & adapter types
Fabric Interconnect (NX-OS)
§
Fabric Extender (IOM) Firmware
§
Chassis Mgmt. Controller
Feature details
§ 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 BIOS
packs in-sync with hardware releases RAID Controller FW
Catalog File
§ Next major software releases will incorporate UCSM Mgmt Extn.
previous modular server and adapter packs
§ 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
§
§ AD user groups looked up by UCSM Server Admin Network 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
 TACACS+ UCSM (Active Directory)
(Active 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
MAC: 08:00:69:02:01:FC-E
§ Maintenance policies WWN: 5080020000075740-3
BIOS: Version 1.03
Firmware
Boot Order: SAN, LAN Network

 New policy contains schedule when SP can be
changed
 Policy can be mapped to one or more SPs
§ Schedule disruptions
Deploy
§ Resource reservation Network: Sales-VLAN OS
Network QoS: High
 SP acquires required resources prior to deployment MAC: 08:00:69:02:01:FC-E
WWN: 5080020000075740-3 Firmware
BIOS: Version 1.03
 Resources are held until deployment Boot Order: SAN, LAN Network
 Eliminates future resource contention

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
§ SP CIMC IP 1
§
Feature details Service Profile
§
§ Current IP address assignment continues 10.21.32.44
Native CIMC IP 1
§ New , second IP address for CIMC
§ Second IP address associated with
Physical Server 1
Service Profile
§ Upon SP deployment CIMC can be
10.21.32.45
accessed through both IP addresses Native CIMC IP 2
§ When SP moves, second IP address

moves to new server Physical Server 2
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

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

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

§ Manager
§SNMP based corelation for trap information
Feature details Fabric

Interconnects
§ Release 1.3 provided SNMP trap support earlier
Fabric
§ Access to full information model of UCS: 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
icensing 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 > show license usage
UCS6120XP / 6140XP Switch A:
Feature Status Expires Count
 Ports must be licensed whether configured as 1GE or Used Switch File Id
10GE ETH_PORT_ACTIVATION_PKG ok never
§ Grace period 8 8 FLC1211001820080612113521765 1
 Each port that is activated but for which there is no

available license 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
Rel v1.4 (Balboa) portsInc. All rights reserved.
© 2010 Cisco Systems, Public 24
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
So
rt
Displa
y
Filt
er
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

Fibre Channel Management &
Monitoring
Feature Summary

Support for new UCS B230 Blade Server
UCS C-Series server integration into
Security
UCS Manager  Simpler integration with MSFT Active
Multi-chassis power capping for UCS B- Directory
Series Multiple simultaneous
 authentication systems
Multi-user KVM enhancements
 Ethernet and Fibre 
Channel  Stateless Computing
Direct connect Ethernet
Appliance  Scheduling of service profile changes
SPAN support on UCS 6100  CIMC IP address abstraction
PVLAN Isolated access Service profile “pre-flight” checks
support 
Full vNIC failover w / o NIC
teaming / bonding with  Management &
FabricFailover / FabricSync Monitoring
Higher VLAN scalability 1024 SNMP GET support for ALL UCS
Higher logical port components
scalability 6000 Syslog enhancements
Higher virtual interface UCS 6100 licensing
Scalability 2000 enforcement/warnings
Fabric Extender Transceiver Usability enhancements
Support
Rel v1.4 (Balboa)
Management InterfacePublic
© 2010 Cisco Systems, Inc. All rights reserved. 32
UCS Manager 1 . 3 ( 1 ) Release
ExistingConnectivity Types
IP Storage FC Storage
Uplinks FC / Eth
Upstream Links connecting to
LAN and SAN
LAN SAN
Server Ports
Downstream links connecting
Eth Uplink FC Uplink Eth Uplink FC Uplink
to servers though IOM
Server Server
© 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
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 §The UCS 6100 acts like a
UCS6100 as an end-host with traditional Ethernet switch with
multiple adapters. No Spanning support for Spanning Tree
Tree protocol on uplink ports. protocol on the uplink ports
§Active/Active use of uplinks §Some uplinks connected to
by pinning the external switches may be
§All uplink ports should be blocked by STP.
connected to the same Layer 2 §Only PVST+ is supported
network §Mac-add learning is enabled
§More scalable than switch on uplink/server interfaces
mode 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 UCS 1 . 4

( Aptos +) ( Balboa )
Ethernet Appliance Ethernet Appliance
Appliance
Trunk 10,100,101 uplink Port Trunk 10,100 or Access 100
port
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 VLANson uplink to appliance (VLAN §VLAN filtering available
filtering) §Advanced features such as QOS available
§Advanced feature such as QOS not available §
§ §
§ UCS 1.4 (Balboa) onwards “End host
§ ” mode is
§ recommended
Appliance port
What is Ethernet Appliance
A specialized device for use on a

Ethernet network, for example Network
Attached Storage , iSCSI, security
appliances, Nexus 1010…
What qualifies to be a appliance

Appliance is specialized external
host, does not run STP
Purpose of Appliance Port

Connect Ethernet appliances only
! Not to use this port type for switch connectivity to

avoid traffic loops

Supported Ports and Configuration
Ethernet
§Any fixed 10G or Appliance
1G §Any expansion Port-Channel Single port
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

Security
UCS C-Series server integration into UCS
Manager Simpler integration with MSFT Active
Directory
Multi-chassis power capping for UCS B-
Channel
Appliance
Scheduling of service profile changes
CIMC IP address abstraction
PVLAN Isolated access support
teaming / bonding with 
FabricFailover / FabricSync  Management &
Higher VLAN scalability 1024 Monitoring
Higher logical port SNMP GET support for ALL UCS
scalability 6000 components
Higher virtual interface Syslog enhancements
Scalability 2000
UCS 6100 licensing
Fabric Extender Transceiver enforcement/warnings
Support
Management
© 2010 Cisco Interface
and/or its affiliates. All rights reserved. Public 41
Unified Monitoring
Monitor FC and Ethernet traffic with a single analyzer
Today Unified
Eth FC Monitoring
Eth
Analyzer Analyzer Analyzer
UCS 6100 UCS 6100
Port 0 Port 0
vNIC vHB vNIC vHB

1 A 1 A
UCS server A UCS server A

§Requi res a dedi cated FC analyzer §Ability to monitor FC and Eth traffic usin
§Need separate a nalyzers for FC and Eth§Single analyzer to monitor FC and Eth
§Requi res specia lized 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 Eth Analyzer
Needs only vNIC 2 but saw vNIC 1 & 3 Monitor vNIC 2 , saw only vNIC 2
Et h 1 / 1
Nexus 5000 UCS 6100
Port 0
UCS 6100
Port 0
vNIC vNIC vNIC
1 2 3
M81KR
VIC
VM VM VM
vNIC
1
vNIC
2
vNIC
3 VM-FEX mode
M81KR
VIC
VM VM VM
§Complex connectivity §Simple connectivity

§Inability to monitor specific VM §Ability to monitor specific VM traffic
traffic §Granular visibility
§Lack of visibility ( bulk capture ) §
§
Summary
A total of 4 local SPAN sessions per UCS system , 2 on each
UCS 6100
Un - used licensed UCS 6100 A UCS 6100 B
port
Cluster Link
Trouble Eth Network Trouble FibreChannel

shooting Analyzer shooting Analyzer
Tool Tool
§Things to
remember identical
§Configure : 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
( VIFis changed ) Future enhancement .

UCSM Monitoring - Visual
estination can be any unused licensed port

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

Feature Summary

Security
Directory
Channel
Appliance
Scalability 2000
Support
Management
VLAN based Layer - 2 separation
§L2 separation with VLANs

VLAN Deployment
§A vlan or more per
tenant/application/function
§VLAN scalability on various
UCS 6100 UCS 6100
platforms is a deciding factor of

Port 0 Port 1
NW scale
Port 0 Port 1
§
No of VLANs used =
3
vNIC 1 vNIC 1 vNIC 2
Bare metal
VM VM VLAN A
VLAN B
VLAN C
Tenant A Tenant B Tenant C

PVLAN based Layer - 2 separation
Single Isolated PVLANto provide v NIC level layer 2
separation
§L2 Separation with Isolated PVLAN
PVLAN Deployment
§Single isolated VLAN for all
tenants/apps
§Provides same level of isolation
UCS 6100 UCS 6100
as with VLAN
§VLAN limits is no longer
Port 0 Port 1 Port 0 Port 1
scalability limiting factor
§Useful for Bronze tier separation
M81
KR §No of VLANs used =
VIC
1
vNIC 1 vNIC 1 vNIC 2
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.
Cat 6 5 0 0 – L 3
UCS 6 1 0 0 UCS 6100

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

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

UCS 1 . 4 ( Balboa )
Requires minimum of 2 vNICs,
Promiscuous outside of the Nexus 1000v one vNIC for isolated VLAN and
one vNIC for carrying regular
Promiscuous
VLANs for service console,
Port Backup vMotion and control.
Cat6500 – L3 Recommendation: Fabric
failover is recomended for HA
assuming 2 vNIC configuration
UCS 6100 UCS 6100
Enable PVLAN Isolated Access
vNIC vNIC
Isolated Trunk carrying regular VLANs:
PVLAN service console, vMotion and
Adapter 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

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

Adapter 1000v Adapter
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 VLANsand their mapping using UCSM
Private VLAN on The UCS
Configuration and Management

Feature Summary

Security
Directory
Channel
Appliance
Scalability 2000
Support
Management
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 Enable fabric failover in vNIC
creation
§Multicast Group
reRegistration

UCS Manager 1 . 3 ( 1 ) Release orAnimated Slide
earlier
FabricFailover on UCS
Return traffic for MAC

FabricFailover
MAC C MAC C
§Fabric failover load-balances Ten 1/1 Ten 1/2
traffic on per vNIC basis

§Palo provides up to 58 vNICs
Ten 1/2
Ten 1/1
§Each vNIC maps to one of the gARP

MAC C
fabric for active data path
§When active path fails,
failover to standby fabric. UCS 6100 UCS 6100
§6100 updates path changes to
upstream switches via
gARP of vNIC MAC upon MAC A MAC B
active link failure

Eth 0 Eth 1
§
§
§ MAC C UCS Server
§
§
§

Animated Slide
FabricFailover and Sync on UCS
Return traffic for MAC
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 gARP

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

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

earlier
Hyper - V Network Link Redundancy
Hyper - V Link redundancy with NIC teaming
§Hyper-V does not support NIC teaming or
Switch 1 Switch 2
bonding
§Requires 3rd party intermediate NIC
teaming driver software to provide
LAN Primary NIC LAN Secondary NIC network link HA
Virtual Machines LAN NIC team adapter §Officially not supported by Microsoft
technical 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.”

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

Animated Slide
Silent VM
MAC A Ten1/1
§Silent VM describes a VM receiving but not

sending traffic (one way communication)
Ten1/1
Ten1/2
§Rare in production networks
§Fabric failover enables standby path upon
active path failure
§Does not provide path update for VM’s
behind the hypervisor
Traffic §Upstream switch continues to use old path
black
hole
until VM starts talking
Eth 0 Eth 1
vSwitch
MAC A
VM
UCS Server
Silent VM

UCS Manager 1 . 3 ( 1 ) Release or Animated Slide
earlier
Silent VM Available in UCS 1.4 (Balboa)
FabricFailover with FabricSync resolves Silent VM
issue §FabricSync along with Fabric failover
solves silent VM issues
MAC A Ten1/2
§FabricSync tracks the remote mac-

gARPVM addresses
Ten1/1
Ten1/2
MAC A triggers gARPs upon their active path
failure
§Path changes are updated immediately,
Mac - sync
provides faster recovery
Eth 0 Eth 1 §
vSwitch
MAC A
VM UCS Server
Silent VM © 2010 Cisco and/or its affiliates. All rights reserved. Public 64
Feature Summary

Security
Directory
Channel
Appliance
Scalability 2000
Support
Management
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/SSHIP.


Feature Summary

Security
Directory
Channel
Appliance
Scalability 2000
Support
Management
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
Feature Name UCS 1.3 (Aptos+) UCS 1.4 (Balboa)
June 2010
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

Increasing VLAN support
Need for increasing VLAN support …
§VLAN every ware/larger Layer 2 domains
§Hosting providers implementing VLAN= a customer
Feature Name UCS 1.3 (Aptos+) UCS 1.4 (Balboa)

June 2010
VLANs supported 512 1024
VLANs available 498 948
76 VLANs reserved (948 available)

§12 Reserved including UCS default VLAN and VSAN
§32 Reserved for VSANs within UCSM
§32 Reserved for FCoEVLANs (to map to VSANs)

UCS Virtual Ports
Virtual Ports are representations for a Physical Interface’s aggregate VLAN
Membership. These are represented to the system as a particular {Port, VLAN}
instance. In simplest terms, for a given Physical Interface, each VLAN
represents a separate Vlan-Port.
Logical Ports = Sum of All VLANs on all trunks

Of every port in the System + access ports
VLAN10
VLAN20
VLAN30
VLAN40
VLAN50
Vlan-port maintains various L2 interface

state/information. Vlan-port scalability limitation
is still applied even if STP is disabled or UCS 6100
is running in EHM.

Virtual Interfaces in UCS
§Interface Descriptor on Fabric

Interconnect
VNIC VNIC §
§Maps through VN-Link to vNIC on a IOM,
Server, or VM itself
§
§End-Point of the VNtag
§
§Finite Number Supported
VETH VETH §Memory for interface structure
just like a physical adapter on
any Cisco Switch

Virtual Interface Count
Virtual InterfacesCount UCS 1.3 (Aptos+) UCS 1.4 (Balboa)

June 2010
6100 1000 2000
Oplin 2 2
Menlo 2 2
Emulex/Q-logic Gen 2 2 2
Cisco VIC 58 (56 usable) 58(56 usable)

Scalability in UCS Software Release 1.3
3 chassis with VN - link in
4 Links each hardware
to Fixed FI
VIC Ports §Assumptions
§VLAN per tenant (498 tenants)
§General compute VMs(4 VMs per core)
§1 VIC per VM
§1 VIC per service
console,MGMT,vMotion and vHBA
§VMs per blade 32
§No of VMs = 32 * 24 = 768
§No of VLANs = 498
§No of tenants = 498
§No of virtual interfaces = 768 +
( 24 * 4 ) = 864 < 1000
§No of logical ports =
( 2 * 498 )+( 24 * 32 )= 1764 < 3000
§vMotion every ware is okay

Scalability with UCS Software Release 1.4
5 chassis with VN - link in
4 Links each hardware
to Fixed FI
VIC Ports §Assumptions
§VLAN per tenant
§General compute VMs(4 VMs per core)
§1 VIC per VM
§1 VIC per service
§VMs per blade 32
§No of VMs= 32 * 40 = 1280
§No of VLANs = 948
( 40 * 4 ) = 1440 < 2000
§No of logical
ports =( 2 * 948 )+( 32 * 40 )= 3176
§vMotion every ware is okay

Mix of Menlo and PALO with UCS SW 1.4
2 Chassis with Menlo / Nexus
4 Links each 1000v
to Fixed FI 4 chassis with VN - link in
§Assumptions
Ports
hardware
§VLAN per tenant 150 in Menlo sub-
group
798 in VIC sub-group. No VMotion
between 2 sub-groups, but within is OK
§General compute VMs
Menlo/N1k §1 VIC per VM
§1 VIC per service
§VMs per blade 32
§No of VMs = 32 * 32 = 1536
§No of VLANs = 948
( 32 * 4 )+( 2 * 16 ) = 1184 < 2000
§No of logical
ports =( 2 * 798 )+( 32 * 32 )+( 300 * 16 * 2 )= 7420
VIC

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)
NAS STORAGE
FC STORAGE
LAN SAN
Switch Switch
End Host Mode NPV/End Host Mode
Switch Mode
NAS 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
§
FC Target Ports
Feature details
tApp and EMC direct connect storage
UCS 6100 UCS 6100
uration not supported, but zoning may be inherited from upstream switch
through LUN masking in the array
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
S appliance connected to Fabric Interconnects in “END HOST” Mode Appliance Port
minates additional access-layer switches End Host
Feature details
ernet appliance) in End Host (general best practice) without putting 6100 in switch mode
UCS B-Series
support this functionality
NAS Appliance
features like VLAN Filtering and QoS Current

Uplink Port
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
gregate and maximize available bandwidth while maintaining isolation
eases 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 A VSAN C
§ VSAN trunking and port channel supported for VSAN B VSAN D
both NPV and switch mode FI operation
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_refere

 © 2010 Cisco and/or its affiliates. All rights reserved. Public 93

Q&A


Язык

Добро пожаловать в Scribd!

1278-Ucs Software Release 1.4

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Описание:

Авторское право:

Доступные форматы

1278-Ucs Software Release 1.4

Загружено:

Описание:

Авторское право:

Доступные форматы

Похожие издания

Unified Computing System

Software Release 1.4 (Balboa)

UCS Product Management

 Compute  Authentication &

Compute Authentication & Security

§2 Intel Xeon 7500 or 6500

High Density Compute: 16 cores per blade

Feature details UCS 6100 UCS 6100

§ C-Series servers connectivity

 Data connectivity directly to Fabric Interconnect

§ 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

§ Service Profile Priorities

§ If your environment has

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

§ Authentication with multiple AD domains

§Secure KVM use in multi-user environments

§ KVM admin control

Compute Authentication & Security

Boot Order: SAN, LAN Network

§“Follow the server” KVM access

§ When SP moves, second IP address

§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

icensing now integrated and accessible directly from UCS Manager

 Each port that is activated but for which there is no

§ 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 &

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

New connectivity choices are Appliance , Monitoring ( FC and

Eth Monitor FC Monitor

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

In - direct Connection Direct Connection

End Host Mode

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 UCS 1 . 4

UCS B - Series UCS B - Series

What is Ethernet Appliance

A specialized device for use on a

What qualifies to be a appliance

Purpose of Appliance Port

! Not to use this port type for switch connectivity to