Table Of Contents
Release Notes for Cisco VFrame Data Center, Version 1.2
Contents
Introduction
New Features
Golden Image Repository Back Up and Restore
Golden Image Versioning
VMware ESX
Template Design Enhancements
Expanded Fibre Channel Switch Interoperability
Virtual Machine File System Datastores
Improved User Interface
Dynamic Changes to Operating Service Networks
HBA ID Virtualization
Automatic LOM Discovery
Deprecated Features
Prerequisites
System Requirements
Client System Requirements
Supported Devices
Restoring the VFrame Data Center Database
Restoring the Database on a Standalone VFrame Configuration
Restoring the Database on a High-Availability VFrame Configuration
Caveats
Open Caveats
Resolved Caveats
Related Documentation
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco VFrame Data Center, Version 1.2
October 21, 2008
This document describes the new features, system requirements, and caveats for Cisco VFrame Data Center, Version 1.2. Use this document in conjunction with the documents listed in the "Related Documentation" section.
Note 
We sometimes update the documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.
Contents
This document includes the following sections:
•Introduction
•New Features
•Deprecated Features
•Prerequisites
•System Requirements
•Restoring the VFrame Data Center Database
•Caveats
•Related Documentation
•Obtaining Documentation and Submitting a Service Request
Introduction
VFrame Data Center is an appliance-based service orchestration solution for the data center. With VFrame, customers can define end-to-end virtualized application services. VFrame can discover physical resources within the data center. Based on requirements defined for the application infrastructure resources, VFrame can allocate appropriate physical or virtual resources and power the application service network.
New Features
The following new features are available in Cisco VFrame Data Center, Version 1.2:
•Golden Image Repository Back Up and Restore
•Golden Image Versioning
•VMware ESX
•Template Design Enhancements
•Expanded Fibre Channel Switch Interoperability
•Virtual Machine File System Datastores
•Improved User Interface
•Dynamic Changes to Operating Service Networks
•HBA ID Virtualization
•Automatic LOM Discovery
Golden Image Repository Back Up and Restore
The following two new CLI commands have been added:
•gir backup—Backs up the Golden Image Repository (GIR) to a remote storage device.
•gir restore—Restores the GIR from a previous back up.
When you backup the database and if the images have changed since the last backup, we recommend that you also backup the GIR so that the golden images on the GIR file system can be restored along with the database restore. This ensures that the images in the repository match what is in the database.
Golden Image Versioning
VFrame now supports golden image versions organized in a version hierarchy. With multiple golden image versions, you can dynamically change the golden being used by a running server group from one version to another.
VMware ESX
VFrame Data Center now supports server virtualization environments with VMware ESX Hypervisor and Virtual Center. VFrame DC 1.2 remote boots the ESX Hypervisor from Fibre Channel SANs with automated network and storage access provisioning. This configuration includes, VLAN, trunking, SAN zoning, VSAN memberships, LUN masking and additional access port configurations. VFrame DC also has an API that talks to VMware Virtual Center for ESX server cluster registrations and extended discovery. Both first time ESX provisioning and runtime incremental changes to network and storage access configurations are supported.
Template Design Enhancements
The following enhancements are now available when designing VFrame templates:
•A new Storage logical element has been added. This element can be configured to represent either server-attached NAS storage or SAN/SAN Fabric storage. New storage system actions support the new Storage logical element.
•A new ESX feature has been added to the VLAN logical element. The element can now be configured to represent an access link or an 802.1q trunk. An access link provides a single VLAN connection, while the 802.1q trunk provides multiple VLAN connections.
•A new expansion feature has been added to the ServerGroup logical element. You can now expand the element to view virtual switches, port groups, and the connection paths between VLANs, virtual switches, and port groups in the server group.
Expanded Fibre Channel Switch Interoperability
This release now includes Cisco VFrame Data Center interoperability with the following Fibre Channel SAN switches:
•Cisco MDS 9124e Blade Switches
•Brocade 48000 Director
•Brocade 5000
For more information, see Table 7.
Virtual Machine File System Datastores
VMware Virtual Machine File System (VMFS) datastores can be used by VMware ESX to store virtual machine disk images, including snapshots. VMFS allows multiple servers to simultaneously use (read to and write from) the same datastore while ensuring that the same virtual machine is not powered on by multiple servers at the same time. New VMFS datastores can be created using one or more shared LUNs, and existing datastores can be extended with additional shared LUNs.
Improved User Interface
The VFrame Data Center user interface has been restructured to increase its usability and to enhance the user experience.
Dynamic Changes to Operating Service Networks
The following elements can now be dynamically added to or removed from a service network that is deployed and operating:
•NAS and SAN LUNs can be dynamically added or removed.
•ESX port groups can be dynamically added or removed.
•VLANs can be dynamically added or removed on server access ports configured in 802.1q trunk mode.
•Qtrees (for Linux and ESX servers) and CIFS shares (for Windows servers) can be dynamically added or removed.
HBA ID Virtualization
You can now virtualize the identity of the Host Bus Adapter (HBA) World Wide Names (WWN) using a pool of user-defined WWN ranges. Virtualizing HBA WWNs provides key mobility advantages and implicit support for any SAN fabric.
Automatic LOM Discovery
VFrame can now automatically discover the following lights-out management (LOM) modules:
•HP iLO-1 and iLO-2
•IBM RSA II
•Dell DRAC4
Deprecated Features
The following features have been deprecated from Cisco VFrame Data Center, Version 1.2:
•SAN fabric based LUN zoning is not supported.
•SAN Boot is not supported for file-based images (no PXE SAN support).
Prerequisites
VFrame Data Center requires your data center to comply with the following conditions:
•Servers must be remote booted.
•Only x86 architecture is used.
•Windows and ESX require SAN remote boot.
•Windows logical servers can only be moved between physical servers with identical hardware compatibility lists.
•Only a single L2 access domain for Ethernet is used.
•A single SAN fabric (or single set of dual SAN fabrics) is used.
•Out-of-band server power management is required.
System Requirements
The system requirements are described in the following sections:
•Client System Requirements
•Supported Devices
Client System Requirements
The Cisco VFrame Data Center client must meet or exceed the following minimum system requirements:
•Intel Pentium III, 1.1 GHz
•512 MB to 1 GB RAM
•100 MB hard drive space
•Any of the following operating systems:
–Microsoft Windows XP, Service Pack 1
–Microsoft Windows 2000, Service Pack 3
–Microsoft Windows Server 2003
•Either of the following web browsers:
–Microsoft Internet Explorer 6.0
–Mozilla Firefox 1.0
•Java Runtime Environment JRE1.5.0_11 or JRE1.5.0_08
•High-resolution monitor, 1024 by 768 pixels, 256 colors
Supported Devices
VFrame supports the following devices:
•x86 servers with lights out management
•Catalyst 6000 series, Catalyst 4000 series, and Catalyst 3000 series switches
•Cisco Load Balancing and Firewall Service Modules
•Network Appliance Filers
•Major Fibre Channel switches and storage arrays
Table 1 through Table 15 describe the hardware that has been tested for interoperability with VFrame:
Table 1 Tested Cisco Catalyst 4500 Series Ethernet Switches
Models
|
Cisco IOS Releases
|
4503
4507R
|
12.2(25)SG
12.2(25)SG2
|
Table 2 Tested Cisco Catalyst 4900 Series Ethernet Switches
Models
|
Cisco IOS Releases
|
Line Cards
|
4948
4948-10GE
4900M
|
12.2(25)EWA
12.2(40)XO47
12.2(44)SG
|
WS-X4904-10GE
WS-X4920-GB-RJ45
|
Table 3 Tested Cisco Catalyst 6500 Series Ethernet Switches
Models
|
Cisco IOS Releases
|
Supervisor Card
|
CSM Versions
|
CSM-S Versions
|
FWSM Versions
|
Line Cards
|
6503-E
6504-E
6506-E
6509-E
6509-V-E
6513-E
|
12.2(18)SXF6
12.2(18)SXF7
12.2(18)SXF10a
12.2(33)SXH
|
WS-SUP720-3B
VS-SUP720-10G
|
4.2(1)
4.2(2)
4.2(3a)
|
2.1(2a)
|
3.1(1)
3.1(3)
3.1(4)
3.1(8)
3.2(1)
|
WS-X6548-GE-TX
WS-X6548V-GE-TX
WS-X6748-GE-TX
WS-X6316-GE-TX
WS-X6408A-GBIC
WS-X6416-GBIC
WS-X6416-GE-MT
WS-X6502-10GE
WS-X6516-GBIC
WS-X6516A-GBIC
WS-X6516-GE-TX
WS-X6704-10GE
WS-X6724-SFP
WS-X6816-GBIC
WS-X6148-RJ-45
WS-X6148V-GE-TX
WS-X6148-GE-TX
WS-6748-SFP
WS-6708-10GE
|
Table 4 Tested Cisco Catalyst 3100 Series Blade Switches
Models
|
Cisco IOS Releases
|
3110G-S for IBM
3110X-S for IBM
3020 for HP
3120G-S for HP
3120X-S for HP
|
12.2(40)EX
12.2(40)SE1
|
Table 5 Tested Cisco MDS Storage Switches
Models
|
SanOS Versions
|
Supervisor Modules
|
Fiber Channel Modules
|
Service Modules
|
MDS 9120
MDS 91241
MDS 9124e
MDS 91341
MDS 9140
MDS 9506
MDS 9509
MDS 9513
MDS 9216A
MDS 9216i
|
3.0(1)
3.0(2)
3.0(3)
3.1(3a)
3.2(1)
3.2(1a)
3.2(3)
3.2(3a)
3.3(1a)
|
Supervisor-1
Supervisor-2
|
1/2/4 Gb
1/2 Gb
|
DS-X9304-SMIP 4-Port 1 Gb IP Storage Service Module
DS-X9308-SMIP 8-Port 1 Gb IP Storage Service Module
|
Table 6 Tested Cisco MDS Storage Blade Switches
Models
|
SanOS Version
|
HP Cisco MDS Fibre Channel Blade Switch for HP c-Class BladeSystem1
IBM Cisco MDS Fibre Channel Blade Switch1
|
3.0(1)
3.0(2)
3.0(3)
3.1(3a)
3.2(1)
3.2(1a)
3.2(3)
3.2(3a)
3.3(1a)
|
Table 7 Other Tested Storage Switches
Models
|
Fabric OS Version
|
Brocade 48000 Director
Brocade 5000 Switch
|
5.2.1 or later
|
Table 8 Tested Storage Arrays
Manufacturer
|
Model
|
Operating System
|
Management Software
|
EMC
|
Symmetrix DMX1000S-M2
|
DMX microcode c5671
|
SYMCLI v6.2.0
|
EMC
|
CLARiiON CX700
CLARiiON CX3
|
Flare v02.19.700.5.010
|
Navisphere CLI v6.19.0.4.14 for Linux
|
EMC
|
CLARiiON CX310c
|
Flare 03.24.010.5.016
|
Navisphere CLI v6.26.0.2.24
|
HDS
|
Thunder 9585V
|
Microprogram v1659AZ
|
Disk Array Management Program Version 10.30
Storage Navigator Modular Version 7.30
|
NetApp
|
FAS3020
|
Data ONTAP 7.1.0.1
NetApp Release 7.2.1.1
|
|
Note Storage Array support is provided through a modular interface. The support matrix is constantly expanding. Please check with your account team about support for specific devices in your environment.
Other example storage array macros are available for the IBM DS4000 Series disk storage systems, IBM SAN Volume Controller, and JBODs.
Table 9 Tested Network-Attached Storage
Manufacturer
|
Model
|
Version
|
NetApp
|
F820 Filer
|
ONTAP 7.0.4
|
NetApp
|
FAS Series Filers
|
ONTAP 7.0 or later
|
NetApp
|
V3020 Filer
|
ONTAP 7.1.1.1
|
Table 10 Tested Servers
Manufacturer
|
Model
|
Processor Speed
|
Memory
|
LOM Types and Firmware Versions
|
BIOS Version
|
|
Fiber Channel HBA and Driver 2
|
Internal SCSI Controller
|
Dell
|
PowerEdge 1950 Server
|
Dual Core 3.0 GHz
|
2.0 GB
|
DRAC v1.27
|
1.2.0
|
Broadcom NetXtreme
|
Qlogic v1.12
|
LSI Logic v5.0.1
|
Dell
|
PowerEdge 2950 Server
|
Quad Core 2.0 GHz
|
4.0 GB
|
DRAC v1.27
|
1.2.0
|
Broadcom NetXtreme
|
Qlogic v1.08
|
LSI Logic v5.0.1
|
HP
|
ProLiant DL320 G5 Server
|
Dual Core Xeon 2.13 GHz
|
2.0 GB
|
iLO-2 v1.29
|
W04
|
Broadcom NetXtreme
|
Qlogic, Emulex
|
HP Embedded SATA RAID v4.7-6 B2067
|
HP
|
ProLiant DL360 G4 Server
|
3.0 GHz
|
1.0 GB
|
iLO-1 v1.89
|
P52
|
Broadcom NetXtreme
|
Qlogic QLA2340 v1.34
|
N/A
|
HP
|
ProLiant DL360 G4p Server
|
3.0 GHz
|
1.0 GB
|
iLO-1 v1.89
|
A05
|
Broadcom NetXtreme
|
Qlogic QLA2340 v1.43
|
N/A
|
HP
|
ProLiant DL360 G5 Server
|
Dual Core Xeon 1.6 GHz
|
1.0 GB
|
iLO-2 v1.3
|
P58
|
Broadcom NetXtreme
|
None
|
None
|
HP
|
ProLiant DL365 G1 Server
|
Dual Core 1.8 GHz
|
1.0 GB
|
iLO-2 v1.3
|
A10
|
Broadcom NetXtreme
|
None
|
None
|
HP
|
ProLiant DL380 G4 Server
|
Intel Xeon 3.4 GHz to 3.6 GHz
|
1.0 GB
|
iLo-1 v1.89
|
P51
|
HP Integrated NC7782 Dual Port LOM
|
None
|
HP Smart Array 6i Controller
HP Smart Array P600 SAS RAID Controller
|
HP
|
ProLiant DL380 G5 Server
|
Dual Core Intel Xeon Processor 2.33 GHz, 4MB L2
|
4.0 GB
|
iLo-2 v1.29
|
P56
|
HP NC373i Multifunction Gigabit Adaptor
|
HPAE311Av1.09
|
HP Smart Array P400 Controller
|
HP
|
ProLiant DL385 G1 Server
|
Quad Core Dual Processor 2.6 GHz
|
8.0 GB
|
iLo-1 v1.89
|
A05
|
Broadcom NetXtreme
|
Qlogic v1.47
|
HP Smart Array 6i Controller
|
HP
|
ProLiant DL585 G1 Server
|
AMD 875 Dual-core Opteron 2.2 GHz
|
2.0 GB
|
iLO-2 v1.3
|
A01
|
HP Integrated NC7782 Dual Port LOM
|
None
|
HP Smart Array 5i+ Controller
|
HP
|
ProLiant DL585 G2 Server
|
AMD 875 Dual-core Opteron 2.2 GHz
|
2.0 GB
|
iLO-2 v1.3
|
A01
|
HP Integrated NC7782 Dual Port LOM
|
None
|
HP Smart Array 5i+ Controller
|
IBM
|
xSeries 3950 Server
|
Dual Core Xeon 2.5 GHz
|
2.0 GB
|
RSA II v1.14
|
3.08
|
Broadcom NetXtreme
|
Qlogic v1.12
|
Adaptec RAID v5.2-0
|
IBM
|
xSeries 346 Server
|
Intel Xeon 3.0 GHz
|
1.0 GB
|
RSA II v1.08
|
1.16
|
Broadcom NetXtreme
|
Qlogic v1.47
|
Adaptec RAID v4.30.11
|
NEC
|
Express5800 120Rj-2 Server
Express5800 120Rh-1 Server
|
Intel Quad Core 2GHz to 3.16GHz
Intel Dual Core 1.86GHz to 3.33GHz
|
2GB up to 48GB
|
Server Engines™ 2nd Gen Server Management Controller v00.04
|
2S
|
Intel 6321ESB
Intel 82563EB
|
Emulex LPe1150-F4
Emulex LPe11002-M4
|
None
|
Note Server support is provided through a modular interface. The support matrix is constantly expanding. Please check with your account team about support for specific servers in your environment.
Table 11 Tested Blade Server Systems
Manufacturer
|
Chassis Model
|
Blade Server
|
Management Module
|
HP c-Class BladeSystem
|
c7000 Enclosure
|
Proliant BL685c G1
Proliant BL680c G5
Proliant BL480c G1
Proliant BL465c G1
Proliant BL460c G1
|
c7000 Onboard Administrator Tray
Firmware: v1.30
|
IBM BladeCenter
|
H Chassis
|
BladeCenter HS21 Type 7971
|
Advanced Management Module
Build ID: BPET30L, Rev. 30
|
Table 12 Tested Ethernet Network Interface Cards
Manufacturer
|
Model
|
Driver Version
|
Broadcom
|
NetXtreme Gigabit Ethernet
(5703, 5704, 5714 chipsets)
|
3u7-v3.43-rh for Linux
4u2-v3.27-rh for Linux
9.52.0.0 for Windows
|
HP
|
Integrated NC7782 Dual Port LOM
|
bcm5700
|
Intel
|
Pro/1000
|
e1000
|
Intel
|
6321ESB
|
9.9.13.0
|
Intel
|
82563EB
|
9.9.13.0
|
NetXen
|
NXB-10GXSR
|
ESX3.5
nx_nic 3.4.336 for RHEL5U1
|
Table 13 Tested Server Operating Systems
Manufacturer
|
OS Version
|
Microsoft
|
Windows 2003 Enterprise Edition SP1, 32-bit
|
RedHat
|
Enterprise Linux 3, Updates 7 and 8, 32-bit and 64-bit
|
RedHat
|
Enterprise Linux 4, Updates 2, 4, 5 and 6, 32-bit and 64-bit
|
RedHat
|
Enterprise Linux 5, 32-bit and 64-bit
|
Novell
|
SUSE Linux Enterprise Server 9 Service Pack 3, 32-bit and 64-bit
|
Novell
|
SUSE Linux Enterprise Server 10, 32-bit and 64-bit
|
Table 14 Tested VMware Products
Product
|
Version
|
VMware ESX
|
3.0.1
3.0.2
3.51
3.5 Update 1
|
VMware VirtualCenter
|
2.0
2.52
2.5 Update 1
|
Table 15 Tested Host Bus Adapters
Manufacturer
|
Model
|
Speed
|
Ports
|
Firmware Version
|
BIOS Version
|
Qlogic
|
SANblade QLA2340
|
2 Gb
|
1
|
3.02.28
3.03.08
3.03.11
3.03.23
|
1.43
1.47
1.5
0.54
|
Qlogic
|
SANblade QLA2344
|
2 Gb
|
4
|
3.03.11
|
1.47
0.54
|
Qlogic
|
SANblade QLA2460 S
|
4 Gb
|
1
|
4.00.13
|
1.04
|
Qlogic
|
QLE2460
|
4 Gb
|
1
|
4.00.22
|
1.18
|
Qlogic
|
QMH2462 for HP C-class Blades
|
4 Gb
|
2
|
4.00.90
|
1.26
|
Qlogic
|
HPAE311A
|
4 Gb
|
2
|
4.0.70
|
1.09
|
Emulex
|
LP10000
|
2 Gb
|
1
|
1.90A4
|
1.70A1
|
Emulex
|
LP10000DC
|
2 Gb
|
2
|
1.90A4
|
1.70A1
|
Emulex
|
LPe1105-HP for HP C-Class Blades
|
4 Gb
|
2
|
ZS2.70A5
|
ZB3.00a4
|
Emulex
|
LPe11002-M4
|
4 Gb
|
2
|
2.50A4
|
1.71A0
|
Emulex
|
LPe1150-F4
|
4 Gb
|
1
|
2.50A4
|
1.70A3
|
Restoring the VFrame Data Center Database
When the VFrame database becomes corrupted, you must restore it from a backup file. Depending on your VFrame configuration, you can use one of the following procedures to restore the database from a backup file without shutting down the running servers:
•Restoring the Database on a Standalone VFrame Configuration
•Restoring the Database on a Standalone VFrame Configuration
Restoring the Database on a Standalone VFrame Configuration
Use the following procedure to restore the database on a standalone VFrame configuration without shutting down the running servers.
Before You Begin
Ensure that you have an available full database backup file from which to restore the database.
Procedure
Step 1 Open the config.text file that was saved with the backup file and verify that the database backup was taken from the current VFrame by checking the following information:
•Line 1—the specified hostname should match the current VFrame hostname.
•Line 3—the specified IP address should match the current VFrame management interface IP address.
•Line 6—the specified IP address should match the current VFrame server communication interface IP address.
•Line 13—should specify a standalone configuration.
If any of the information is not correct, do not restore the database from the associated backup file.
Step 2 From current VFrame command-line interface, enter the db restore command.
Step 3 Wait until the services are up.
Restoring the Database on a High-Availability VFrame Configuration
Use the following procedure to restore the database on a high-availability VFrame configuration without shutting down the running servers.
Before You Begin
Ensure that you have an available full database backup file from which to restore the database.
Procedure
Step 1 Disable high availability on the Secondary VFrame.
Step 2 Wait until the services are up.
Step 3 Open the config.text file that was saved with the backup file and verify that the database backup was taken from the current VFrame by checking the following information:
•Line 1—the specified hostname should match the current Primary VFrame hostname.
•Line 3—the specified IP address should match the current Primary VFrame management interface IP address.
•Line 4—the specified virtual IP address should match the current Primary VFrame management interface virtual IP address.
•Line 6—the specified IP address should match the current Primary VFrame server communication interface IP address.
•Line 7—the specified virtual IP address should match the current Primary VFrame server communication interface virtual IP address.
•Line 13—should specify a pair configuration.
If any of the information is not correct, do not restore the database from the associated backup file.
Step 4 From current Primary VFrame command-line interface, enter the db restore command.
Step 5 Wait until the services are up.
Step 6 Enable high availability on the Standalone VFrame.
Caveats
The caveats describe unexpected behavior in Cisco VFrame Data Center.
You can use Cisco's Bug Toolkit to access detailed information about the caveats listed in this section. For your convenience in locating caveats in Cisco's Bug Toolkit, the caveat titles listed in this section are drawn directly from the Bug Toolkit database. These caveat titles are not intended to be read as complete sentences because the title field length is limited. In the caveat titles, some truncation of wording or punctuation may be necessary to provide the most complete and concise description. The only modifications made to these titles are as follows:
•Commands are in boldface type.
•Product names and acronyms may be standardized.
•Spelling errors and typos may be corrected.
Note If you are a registered cisco.com user, access Cisco's Bug Toolkit at http://www.cisco.com/support/bugtools. (You will be prompted to log into Cisco.com.)
To become a registered cisco.com user, go to the following website:
http://tools.cisco.com/RPF/register/register.do
Open Caveats
Table 16 describes the open caveats for VFrame Data Center, Version 1.2.
Table 16 Open Caveats for Cisco VFrame Data Center, Version 1.2
Caveat ID
|
Description
|
CSCsu90575
|
VFrame 1.2 doesn't support JRE 1.5 update 16.
|
CSCsg59019
|
Device status filter for network map does not work as expected.
|
CSCsh48535
|
VFrame should not report Null Pointer Exception if NFS Filers are down.
|
CSCsh70465
|
The hbatool command returns slowly during replication.
|
CSCsh97117
|
Root LUN multi-pathing not supported.
|
CSCsi12939
|
Resource Pool Utilization per Network reports are inconsistent.
|
CSCsi59229
|
Able to unmange and manage a VSAN that is in a fault state.
|
CSCsi82840
|
VFrame should support SVI monitoring.
|
CSCsi84350
|
Basic information is missing from the Windows Model Server properties.
|
CSCsj00861
|
Web cache is not cleared when an old client accesses a new build.
|
CSCsj06532
|
ProLiant DL360 G5 server failed to form an EtherChannel bonding.
|
CSCsj08455
|
VFrame should automatically fix LUN masking error during verification.
|
CSCsj17261
|
VFrame does not monitor missing LUN in Array Mode.
|
CSCsj29183
|
Must run Verify Network if one same-chassis FWSM/HA member leaves.
|
CSCsj31330
|
Cross launch should not allow creating the same display name.
|
CSCsj33496
|
Server group wizard allows selecting more than one PXE interface per SG.
|
CSCsj33530
|
LOM jobs fail in multi-credential scenario.
|
CSCsk35765
|
Unable to find a LUN when the mapped LUN number is greater than 255.
|
CSCsk62435
|
VHA auto-upgrade fails during server deploy when SELinux is enabled.
|
CSCsl18023
|
NFS server deploy boot timeouts on HP DL385G2/585G2 with NIC teaming.
|
CSCsl80415
|
Missing FWSM HA member should leave the HA group.
|
CSCsm11779
|
Timeout occurs while performing LOM power off operation.
|
CSCsm13463
|
VFrame sometimes fails to discover cat6k with 12.2(18)SXF[9|10a|12].
|
CSCsm72797
|
Same shared LUN across server groups is assigned different LUN number.
|
CSCsm90506
|
Managed LUN can be used as remote GIR.
|
CSCsm95671
|
Error loading operating system (snapshot from HP Blades local disk).
|
CSCso01200
|
Unable to support CSM direct server return mode.
|
CSCso07510
|
Wrong resource pool display for FWSM HA when one member has left.
|
CSCso49152
|
Validation should fail if 2 VMkernel PG IP addr are in the same subnet.
|
CSCsq01820
|
Storage element changes to Running state when provisioning fails.
|
CSCsq10301
|
Storage Manager dialog box requires path even when one is not needed.
|
CSCsq33318
|
ESX VMFS rescan fails on a LUN in ReadyToApply state.
|
CSCsq39465
|
HBA/VMFS rescan socket timeout when undeploy LUNs, ESX not responding.
|
CSCsq41564
|
Wrong user ID or pwd during GIR setup leaves system in bad state.
|
CSCsq48866
|
Rediscovery of HDS fails.
|
CSCsq56433
|
Trend report response too slow when opening the report for 100 servers.
|
CSCsq57698
|
LUN state is changed to Running while LS state is Server Start Failed.
|
CSCsq64690
|
Save button is disabled when switching between golden images.
|
CSCsq71455
|
Service network design is not being saved with default variable values.
|
CSCsq74336
|
Trunk port is still in Running state after undeployment.
|
CSCsq77395
|
Alarms in AdminContext can be acknowledged from all Virtual Contexts.
|
CSCsq83018
|
WinVHA does not work correctly if LANG env is not C or en_US.UTF-8.
|
CSCsq85234
|
Server misses HB if system clock is adjusted too far forward.
|
CSCsq85317
|
GUI refresh problem causes inconsistent service network states.
|
CSCsq89423
|
Waiting for LUN path while an array port is in fault.
|
CSCsq93206
|
Service network deployment fails when using GI label from deleted GI.
|
CSCsq97577
|
Missing information in Deploy Properties for running logical servers.
|
CSCsq97788
|
Switch management fails when enable pwd is not req'd to enter exec mode.
|
CSCsq98056
|
Server state should change to failed when Root Qtree is removed.
|
CSCsr01943
|
Zoning verification error in MDS fabric triggers server remap.
|
CSCsr04692
|
StateChangeException error and failure to update status for the LNE.
|
CSCsr05521
|
Standby VFDC fails to become the secondary peer.
|
CSCsr05675
|
Unmasked/unmapped LUN shows as running with alarm status as OK.
|
CSCsr05686
|
Duplicate entries are created after cloning template.
|
CSCsr05718
|
Undeploying partition fails because the host is not in VIM inventory.
|
CSCsr05722
|
Failed partition cannot be removed because delete option is grayed out.
|
CSCsr05734
|
No fault is raised when a GIR mount fails on Active VFrame.
|
CSCsr05737
|
GIR fails to mount on new active VFrame.
|
CSCsr06055
|
Unable to SSH deployed SUSE file based servers.
|
CSCsr06188
|
GUI Refresh issue causes problem canceling scheduled SN jobs.
|
Resolved Caveats
Table 17 describes the resolved caveats for VFrame Data Center, Version 1.2.
Table 17 Resolved Caveats for Cisco VFrame Data Center, Version 1.2
Caveat ID
|
Description
|
CSCsg11489
|
Logical Servers should allow host routes with /32 netmask to be added.
|
CSCsg77293
|
Discovery of same model server fails with different OS.
|
CSCsg83801
|
Incorrect interface, HBA, and NFS trend counters in Windows VHA.
|
CSCsh81325
|
Macro subroutines not covered in the user documentation.
|
CSCsh92486
|
VFDC should use devlabel (UUID) names in fstab to handle m-pathed disks.
|
CSCsh94026
|
Set up fails if interfaces are down and NFS is the DB back-up location.
|
CSCsi07286
|
Verify macro with syntax error still appears to execute successfully.
|
CSCsi09233
|
Simplify the LUN and Path interface for SAN deployed servers.
|
CSCsi26271
|
Server request time out for RMI request: getLOMStationElemntDetails LOM.
|
CSCsi31460
|
Database session commit failed while updating power status.
|
CSCsi43042
|
Config macro run failure causes SN deployment failure.
|
CSCsi63972
|
Need to allow scp/sftp import of SN templates, similar to image import.
|
CSCsi64027
|
The redundant fabric does not auto-populate.
|
CSCsi69364
|
Using LOM Manager to power on discovered Dell servers causes an error.
|
CSCsi73071
|
LOM macro fails if using OpenSSH v4.1 to connect to iLO and iLO2.
|
CSCsi73262
|
Macro execution fails while deploying servers.
|
CSCsi91542
|
Sysprep Validate button gives OK even when the sysprep file is invalid.
|
CSCsi97096
|
Bulk managing multiple switches fails and generates database errors.
|
CSCsi98839
|
Server re-inventory fails after moving HBA from one server to another.
|
CSCsi99034
|
LUN 0 from CLARiiON array can be selected for additional LUN.
|
CSCsj00725
|
Opening the LUN path selection dialog box is slow.
|
CSCsj03799
|
SAN Mgr Disc Job status is misleading when using a Multi Storage Mgr.
|
CSCsj06483
|
No warning message when HBA port is connected to undiscovered VSAN.
|
CSCsj15365
|
SAN Manager discovery fails with Perl macro exception.
|
CSCsj22240
|
VLAN resource deletion error causes time out.
|
CSCsj30098
|
With DB Restore, GIs in the GIR are not matched with GIs in DB.
|
CSCsj35544
|
The vcc_java service does not stop when stopping all services in setup.
|
CSCsj39570
|
Critical service Java in restart loop with backup in time-out state.
|
CSCsj72746
|
Logical server imaging fails, but status says server is imaged.
|
CSCsj88461
|
Seed switch IP address does not update after rediscovery of SAN.
|
CSCsj93662
|
User should be allowed to change default root bridge settings
|
CSCsk01540
|
Non-visibility of SN/Template causing confusion in AC got created in VC.
|
CSCsk09094
|
Error message when upgrading from v1.1.0.728 (FCS) to v1.1.4.433.
|
CSCsk29716
|
LOM inventory file does not accept lower case letters in MAC address.
|
CSCsk30864
|
Switch discovery through CDP using SNMPv3 credentials causes error msg.
|
CSCsk39371
|
Logical network is in deployable state with FWSM in DepoymentBlocked.
|
CSCsk41161
|
Pool view sorting does not work properly.
|
CSCsk60697
|
GUI fails to refresh when the FWSM VC context changes mode.
|
CSCsk62923
|
VFrame does not validate SNMPv3 write permissions.
|
CSCsk72115
|
Server discovery does not work with apostrophe (') in LOM credentials.
|
CSCsk73684
|
GUI lists unofficially-supported devices in the supported devices folder.
|
CSCsk75097
|
Pool selection GUI shows only one managed server.
|
CSCsk87629
|
Some chars in hostname for SAN-based nets cause SAN provisioning failure.
|
CSCsl10478
|
SpaceReserved volume attribute not updated properly.
|
CSCsl12700
|
GUI timestamp is not consistent with the log timestamp.
|
CSCsl73354
|
Error not reported when enable password is wrong.
|
CSCsl83231
|
The show fault status CLI command displays wrong status for HA peer.
|
CSCsl94630
|
Server inventory fails to discover Dell 2950 server.
|
CSCsm03724
|
FSM is not defined for virtual machine managers.
|
CSCsm09204
|
LUN information is empty in logical server.
|
CSCsm11543
|
VFrame fails to configure 2nd service console port group.
|
CSCsm27109
|
Windows server deployment fails due to missing WinUpdates.exe file.
|
CSCsm51241
|
ESX verification failure (VMK gateway).
|
CSCsm54449
|
SuSE Linux deployment fails.
|
CSCsm63391
|
RHEL 5 deployment fails due to missing ext3 module in initrd-vfdc.
|
CSCsm88808
|
Storage discovery fails when station SSH is 2.0 or above
|
CSCsm88893
|
Storage discovery NPE after creating SAN GIR for CLARiiON array.
|
CSCso02711
|
Acquired FWSM not shown in service network mappings resource GUI.
|
CSCso04828
|
Creating shared partitions before creating servers causes NPE.
|
CSCso15300
|
Fix for the file content parsing case where the sysprep is not imported.
|
CSCso43585
|
When HA is turned off, VFrame fails to unmount remote /gir from filer.
|
CSCso69311
|
Changes in Ethernet interface names not checked on Linux server reboot.
|
CSCso75034
|
The service console default gateway does not configure properly.
|
CSCso98649
|
Discovery/verification fails after VirtualCenter Server Service restart.
|
Related Documentation
Table 18 describes the documentation available for Cisco VFrame Data Center.
Table 18 Cisco VFrame Data Center Documentation
Document Title
|
Available Formats
|
Cisco VFrame Data Center
Documentation Roadmap
|
This guide is available in the following formats:
•Printed document included with the product.
•On the product recovery CD-ROM.
•On Cisco.com.
|
Cisco VFrame Data Center
Installation and Configuration Guide
|
This guide is available in the following formats:
•On the product recovery CD-ROM.
•On Cisco.com.
|
Cisco VFrame Data Center
Administration Guide
|
This guide is available in the following formats:
•On the product recovery CD-ROM.
•On Cisco.com.
•Included in the online help in HTML and PDF formats.
|
Context-sensitive online help
|
To access online help, perform any of the following tasks:
•Choose Help > Contents to open the help system.
•Choose Help > For This Page to obtain help on the page currently in the window.
•Click the Help button in a dialog box.
|
Cisco VFrame Data Center
Programmer's Guide
|
This guide is available in the following formats:
•On the product recovery CD-ROM.
•On Cisco.com.
|
Cisco VFrame Data Center
Regulatory Compliance Information
|
This guide is available in the following formats:
•Printed document included with the product.
•On the product recovery CD-ROM.
•On Cisco.com.
|
Cisco VFrame Data Center
Open Source Licenses
|
This guide is available in the following formats:
•On the product recovery CD-ROM.
•On Cisco.com.
|
Important Safety Information
|
Printed document included with the product.
|
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)
Release Notes for Cisco VFrame Data Center, Version 1.2
© 2008 Cisco Systems, Inc. All rights reserved.
