Table Of Contents
Release Notes for Cisco VFrame Data Center 1.1.4
Contents
Introduction
New Features
Expanded Switch Interoperability
Expanded Fibre Channel Switch Interoperability
Blade Server Integration
Switch Replacement Reconfiguration
Lights Out Management Discovery Enhancements
SNMPv3 Support
System Fault Notification
System Requirements
Client System Requirements
Upgrading Cisco VFrame Data Center from 1.1 to 1.1.4
Upgrading to Cisco VFrame Data Center 1.1.4 on a Standalone Configuration
Upgrading to Cisco VFrame Data Center 1.1.4 on a High-Availability Configuration
Supported Devices
Caveats
Open Caveats
Resolved Caveats
Documentation Updates
Replacing an Ethernet Switch
Replacing a Non-Stackable Ethernet Switch
Replacing a Stackable Ethernet Switch
Related Documentation
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco VFrame Data Center 1.1.4
November 1, 2007
This document describes the new features, system requirements, and caveats for Cisco VFrame Data Center 1.1.4. 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
•System Requirements
•Caveats
•Documentation Updates
•Related Documentation
•Obtaining Documentation, Obtaining Support, and Security Guidelines
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 1.1.4:
•Expanded Switch Interoperability
•Expanded Fibre Channel Switch Interoperability
•Blade Server Integration
•Switch Replacement Reconfiguration
•Lights Out Management Discovery Enhancements
•SNMPv3 Support
Expanded Switch Interoperability
This release now includes Cisco VFrame Data Center interoperability with the following additional Cisco Catalyst switches:
•Cisco Catalyst 4948 Switch
•Cisco Catalyst 4948-10GE Switch
•Cisco Catalyst Blade Switch S3110G-S for IBM
•Cisco Catalyst Blade Switch 3110X-S for IBM
•Cisco Catalyst Blade Switch 3120G-S for HP
•Cisco Catalyst Blade Switch 3120X-S for HP
•Cisco Catalyst 3750G-12S Switch
•Cisco Catalyst 3750G-24T Switch
•Cisco Catalyst 3750G-24WS Switch
•Cisco Catalyst 3750G-24TS Switch
•Cisco Catalyst 3750G-24PS Switch
•Cisco Catalyst 3750G-24TS-1U Switch
•Cisco Catalyst 3750G-48TS Switch
•Cisco Catalyst 3750G-48PS Switch
Expanded Fibre Channel Switch Interoperability
This release now includes Cisco VFrame Data Center interoperability with the following additional Fibre Channel switches:
•HP Cisco MDS Fibre Channel Blade Switch for HP c-Class BladeSystem
•IBM Cisco MDS Fibre Channel Blade Switch
•Cisco MDS 9124 Multilayer Fabric Switch
Blade Server Integration
This release introduces blade server systems integration. The IBM BladeCenter and the HP c-Class BladeSystem blade server systems are now supported in VFrame Data Center as manageable servers.
Switch Replacement Reconfiguration
Cisco VFrame Data Center now allows you to physically replace an Ethernet switch while maintaining its managed status, if it was previously managed. After you replace the switch and then schedule or run a discovery, VFrame detects the new replacement switch and provides you with the option of making it accessible to VFrame.
Lights Out Management Discovery Enhancements
This release introduces the LOM Inventory dialog box, which complements the existing LOM inventory macro, to work with LOM interface information. While the LOM inventory macro can be used when there are a large number of LOM interfaces to inventory, the LOM Inventory dialog box, which allows you to work with one LOM interface at a time, can be used for working with a smaller number of LOM interfaces, or for making incremental changes to a large inventory.
SNMPv3 Support
VFrame now supports SNMPv3 protocols to communicate with Ethernet switches and SAN fabric devices.
System Fault Notification
This release introduces System Fault Notification, which allows you to configure VFrame to send e-mail notifications when system faults occur. When notified of a system fault, you can check the related log file for detailed fault information. For example:
•If you receive a "VFDC service down" e-mail notification, use the show system services command to find out which service is down, then use the debug services service-name command to debug that particular service.
•If you receive a "DB Backup Device Unrechable" e-mail notification, use the debug services sysmnt command to see the detailed fault information.
•If you receive an HA-related e-mail notification, use the debug services hsrp and debug services hdrh commands to see the detailed fault information.
System Requirements
The system requirements are described in the following sections:
•Client System Requirements
•Upgrading Cisco VFrame Data Center from 1.1 to 1.1.4
•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
Upgrading Cisco VFrame Data Center from 1.1 to 1.1.4
The following sections describe how to upgrade Cisco VFrame Data Center from Version 1.1 to Version 1.1.4:
•Upgrading to Cisco VFrame Data Center 1.1.4 on a Standalone Configuration
•Upgrading to Cisco VFrame Data Center 1.1.4 on a High-Availability Configuration
Note In Cisco VFrame Data Center 1.1, all pre-defined LOM templates accept LOM MAC addresses with upper case and lower case hex digits. While this is not a issue by itself, this causes problems in server-to-LOM associations and in other internal queries, when server MAC addresses were persisted in upper case hex digits.
In Cisco VFrame Data Center 1.1.4, the LOM Inventory macro for all pre-defined LOM Templates no longer accepts MAC addresses with lower case digits, and does not perform inventory of such records. To avoid the issues associated with using lower case hex digits after upgrading to Cisco VFrame Data Center 1.1.4, we recommended updating the Validate_macaddrr routine in the LOM Inventory macro for all pre-defined LOM Templates to accept only upper case hex digits.
To update the Validate_macaddrr routine, replace this line:
if (!($byte =~ m/[(\d)|(a-f)|(A-F)]{2}/)) {
with this line:
if (!($byte =~ m/[(\d)|(A-F)]{2}/)) {
Upgrading to Cisco VFrame Data Center 1.1.4 on a Standalone Configuration
Use the following procedure to upgrade the software on a standalone Cisco VFrame Data Center device from Version 1.1 to Version 1.1.4.
Before you begin
You must back up the VFrame Data Center database before starting the software upgrade procedure. If the upgrade fails then all the information in the database may be lost. Enter the following command to back up the database:
db backup scp://hostname:/path/filename
Procedure
Step 1 Using an SSH client, log into the Cisco VFrame Data Center device using the admin username and password.
Step 2 Enter the following command to stage the VFrameUpgrade.zip upgrade patch file to the VFrame Data Center device:
copy url http://hostname/patch/VFrameUpgrade.zip install
The copy command can use HTTP, FTP, or SCP to copy the install patch, and prompts for a username. If the username is not needed, as is the case for http access, then enter a return and you will not be prompted for a password.
Step 3 Enter the following command to start the software upgrade:
install update VFrameUpgrade
This installs the upgrade patch and reboots the system. Do not attempt to reboot the system; the patch can take up to 20 minutes to install before rebooting.
Upgrading to Cisco VFrame Data Center 1.1.4 on a High-Availability Configuration
Use the following procedure to upgrade the software on a pair of Cisco VFrame Data Center devices in the High Availability configuration from Version 1.1 to Version 1.1.4.
Before you begin
You must back up the VFrame Data Center database before starting the software upgrade procedure. If the upgrade fails then all the information in the database may be lost. Enter the following command to back up the database:
db backup scp://hostname:/path/filename
Procedure
Step 1 Perform the following steps to upgrade the software on the secondary Cisco VFrame Data Center device.
a. Using an SSH client, log into the secondary Cisco VFrame Data Center device using the admin username and password.
b. Enter the following command to stage the VFrameUpgrade.zip upgrade patch file to the secondary device:
copy url http://hostname/patch/VFrameUpgrade.zip install
c. Enter the show redundancy status command to verify that you are on the secondary device and that the databases are synchronized. The command must show that the local device is in the STANDBY_READY state and that the databases are in sync. This must be checked to ensure that the current database will be converted without database or configuration loss.
The following example shows that the device you are logged in to (Local) is the secondary device and that the databases are synchronized (in sync):
vframehost# show redundancy status
HA state: STANDBY_READY ACTIVE_READY
DB mode: Secondary Primary
d. Enter the following command to start the software upgrade:
install update VFrameUpgrade
This switches the primary VFrame device to the UPGRADE state. No operations are permitted during upgrade and the GUI is unavailable; however, DHCP and TFTP services remain in operation on the primary VFrame device to allow the reloading of any rebooting deployed servers.
After the software upgrade finishes, the secondary device remains in secondary mode.
e. Enter the exit command to log off the secondary device.
f. Log on to the primary device using the admin username and password.
g. Enter the reboot command to reboot the primary device. The reboot causes the secondary device to become the new primary with the converted database preserved. The original primary device remains in UPGRADE state.
h. Enter the exit command to log off the original primary device.
i. Log on to the new primary (original secondary) device using the admin username and password.
j. Verify that the device upgraded successfully.
k. Enter the exit command to log off the device.
Step 2 Perform the following steps to upgrade the software on the original primary Cisco VFrame Data Center device.
a. Using an SSH client, log into the original primary device using the admin username and password.
b. Enter the following command to stage the VFrameUpgrade.zip upgrade patch file to the original primary device:
copy url http://hostname/patch/VFrameUpgrade.zip install
c. Enter the following command to start the software upgrade:
install update VFrameUpgrade force
After the device reboots, it will start up as the new secondary device.
d. Enter the show redundancy status command to check the redundancy state. Initially, the redundancy state should appear similar to the following example:
vframehost# show redundancy status
HA state: STANDBY_DATA ACTIVE_READY
DB state: IDS_RECOVER IDS_UP
DB mode: Secondary Primary
After the databases synchronize, the redundancy state should match the following example:
HA state: STANDBY_READY ACTIVE_READY
DB mode: Secondary Primary
e. Enter the exit command to log off the new secondary device.
Supported Devices
Table 1 through Table 13 describe the hardware that is supported with Cisco VFrame Data Center:
Table 1 Supported Cisco Catalyst 3750 Ethernet Switches
Models
|
Cisco IOS Releases
|
3750G-12S
3750G-24T
3750G-24WS
3750G-24TS
3750G-24PS
3750G-24TS-1U
3750G-48TS
3750G-48PS
|
12.2(40)SE
|
Table 2 Supported Cisco Catalyst 4900 Series Ethernet Switches
Models
|
Cisco IOS Releases
|
4948
4948-10GE
|
12.2(25)EWA
|
Table 3 Supported 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
6513-E
|
12.2(18)SXF6
12.2(18)SXF7
|
WS-SUP720-3B
|
4.2(1)
4.2(2)
4.2(3a)
|
2.1(2a)
|
3.1(1)
3.1(3)
3.1(4)
|
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 Supported Cisco Catalyst 3100 Series Blade Switches
Models
|
Cisco IOS Releases
|
3110G-S for IBM
3110X-S for IBM
3120G-S for HP
3120X-S for HP
|
12.2(40)EX
|
Table 5 Supported Cisco MDS Storage Switches
Models
|
SanOS Versions
|
Supervisor Modules
|
Fiber Channel Modules
|
Service Modules
|
MDS 9120
MDS 91241
MDS 9140
MDS 9506
MDS 9509
MDS 9513
MDS 9216A
MDS 9216i
|
3.0(1)
3.0(2)
3.0(3)
3.1(3a)
|
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 Supported 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)
|
Table 7 Supported Storage Arrays
Manufacturer
|
Model
|
Operating System
|
Management Software
|
EMC
|
Symmetrix DMX1000S-M2
|
DMX microcode c5671
|
SYMCLI v6.2.0
|
EMC
|
CLARiiON CX700
|
Flare v02.19.700.5.010
|
Navisphere CLI v6.19.0.4.14 for Linux
|
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.
Table 8 Supported Network-Attached Storage
Manufacturer
|
Model
|
Version
|
Network Appliance
|
F820 Filer
|
ONTAP 7.0.4
|
Network Appliance
|
FAS980 Filer
|
ONTAP 7.0.4
|
Network Appliance
|
FAS3020 Filer
|
ONTAP 7.2.1.1
|
Network Appliance
|
V3020 Filer
|
ONTAP 7.1.1.1
|
Table 9 Supported 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 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 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
|
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
|
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 10 Supported Blade Server Systems
Manufacturer
|
Chassis Model
|
Blade Server
|
Management Module
|
HP c-Class BladeSystem
|
c7000 Enclosure
|
Proliant BL685c G1
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 11 Supported 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
|
Table 12 Supported Server Operating Systems
Manufacturer
|
OS Version
|
Microsoft
|
Windows 2003 Enterprise Edition SP1, 32-bit
|
RedHat
|
Enterprise Linux 3, Update 7, 32-bit and 64-bit
|
RedHat
|
Enterprise Linux 4, 32-bit and 64-bit
|
Table 13 Supported 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
|
Emulex
|
LP10000
|
2 Gb
|
1
|
1.90A4
|
1.70A1
|
Emulex
|
LP10000DC
|
2 Gb
|
2
|
1.90A4
|
1.70A1
|
Caveats
The caveats describe unexpected behavior in Cisco VFrame Data Center 1.1.
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 14 describes the open caveats for VFrame Data Center 1.1.4.
Table 14 Open Caveats for Cisco VFrame Data Center 1.1.4
Caveat ID
|
Description
|
CSCsg11489
|
Host route with /32 netmask should be supported in logical server.
|
CSCsg59019
|
Network Map Device Filter does not work as expected.
|
CSCsg83801
|
Incorrect interface, HBA, and NFS trend counters in Windows VHA.
|
CSCsh48535
|
VFrame should not report Null Pointer Exception if NFS Filers are down.
|
CSCsh70465
|
The hbatool command returns slowly during replication.
|
CSCsh81325
|
Macro subroutines not covered in the user documentation.
|
CSCsh82306
|
Distorted Discovery Status GUI when vertically scrolling.
|
CSCsh87224
|
The inquire command returns LUN as invalid.
|
CSCsh94026
|
Set up fails if interfaces are down and NFS is the DB back-up location.
|
CSCsh97117
|
Root LUN multi-pathing not supported.
|
CSCsi07286
|
Verify macro with syntax error still appears to execute successfully.
|
CSCsi12939
|
Resource Pool Utilization per Network reports are inconsistent.
|
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 LN deployment failure.
|
CSCsi59229
|
Able to unmange and manage a VSAN that is in a fault state.
|
CSCsi64027
|
The redundant Fabric does not auto-populate.
|
CSCsi69364
|
Using the LOM Manager to power on discovered Dell servers causes and error.
|
CSCsi73071
|
LOM macro fails if using OpenSSH v4.1 to connect to iLO and iLO2
|
CSCsi73262
|
Macro execution fails while deploying servers.
|
CSCsi82840
|
VFrame should support SVI monitoring.
|
CSCsi84350
|
Basic information is missing from the Windows Model Server properties.
|
CSCsi91542
|
Sysprep Validate button gives OK even when the sysprep file is invalid.
|
CSCsi93780
|
First attempt of SAN Deployment in a Fabric mode with DMX fails.
|
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.
|
CSCsj00861
|
Web cache is not cleared when an old client accesses a new build.
|
CSCsj02427
|
Model server local disk Image is corrupted after a successful deploy.
|
CSCsj03799
|
SAN Mgr Disc Job status is misleading when using a Multi Storage Mgr.
|
CSCsj06483
|
No warning msg when HBA port is connected to undiscovered VSAN.
|
CSCsj06532
|
ProLiant DL360 G5 server failed to form an EtherChannel bonding.
|
CSCsj15365
|
SAN Manager discovery failed with Perl macro exception.
|
CSCsj17261
|
VFrame does not monitor missing LUN in Array Mode.
|
CSCsj20147
|
Acquired FWSM not shown in Service Network Mappings Resource UI
|
CSCsj22240
|
VLAN resource deletion error causes time out.
|
CSCsj29183
|
Must run Verify Network if one same-chassis FWSM/HA member leaves.
|
CSCsj30098
|
With DB Restore, GIs in the GIR are not matched with GIs in DB.
|
CSCsj31330
|
Cross launch should not allow creating the same display name.
|
CSCsj33496
|
Server group wizard allows selecting more than 1 PXE interface per SG.
|
CSCsj33530
|
LOM jobs fail in multi credential scenario.
|
CSCsj35544
|
The vcc_java service does not stop while stopping all the services in setup.
|
CSCsj36872
|
SAN GIR code needs deprecate the use of LUID.
|
CSCsj39570
|
Critical service Java restarting in loop with backup in time-out state.
|
CSCsj88461
|
Seed switch IP address does not update after rediscovery of SAN.
|
CSCsj90673
|
CDP discovery fails with "Discovery completed with errors" message.
|
CSCsk01063
|
SAN replication fails, VFrame using 2 HBA ports to the same fabric.
|
CSCsk09094
|
Error Message when upgrading from v1.1.0.728 (FCS) to v1.1.4.433.
|
CSCsk29716
|
LOM inventory file does not accept capital letters in the MAC address.
|
CSCsk30864
|
Switch discovery through CDP using SNMPv3 credentials causes error msg.
|
CSCsk35765
|
Unable to find a LUN when the mapped LUN number is greater than 255.
|
CSCsk39371
|
Logical network is in deployable state with FWSM in DepoymentBlocked.
|
CSCsk41161
|
Pool View sorting does not work correctly.
|
CSCsk47575
|
Heartbeat received for over 5 mins while logical server in config state.
|
CSCsk60697
|
GUI fails to refresh when the FWSM VC context changes mode.
|
CSCsk62435
|
VHA auto-upgrade fails during server deploy when SELinux is enabled.
|
CSCsk62923
|
VFrame does not validate SNMPv3 write permissions.
|
CSCsk72115
|
Server discovery does not work with ' character in LOM credentials.
|
CSCsk73684
|
GUI lists unofficially-supported devices in the supported devices folder.
|
CSCsk75097
|
Pool selection GUI shows only one managed server.
|
CSCsk87629
|
Certain chars in Hostname for SAN-based nets cause SAN provisioning to fail.
|
CSCsl12700
|
GUI timestamp is not consistent with the log timestamp.
|
Resolved Caveats
Table 15 describes the resolved caveats for VFrame Data Center 1.1.4.
Table 15 Resolved Caveats for Cisco VFrame Data Center 1.1.4
Caveat ID
|
Description
|
CSCsh95854
|
LOM template enhancements based on EFT customer feedback.
|
CSCsi14719
|
Serious error messages not shown to user via GUI or e-mail.
|
CSCsi52610
|
Duplicate LUN entries appear in the GUI.
|
CSCsj06507
|
Ping and Traceroute Utility does not work with Hostname.
|
CSCsj09441
|
ALL CIFS Share option not working in Service Group Config Wizard.
|
CSCsj10568
|
DNS name with domain name not accepted in CDP seed.
|
CSCsj13772
|
The Max. Results value does not update immediately after it is changed.
|
CSCsj13789
|
Show Policy Jobs history filter checkbox not updated.
|
CSCsj15317
|
Incorrect macro target applied for dual EtherChannel.
|
CSCsj18538
|
GUI should display serial number in device properties for server/switch.
|
CSCsj22188
|
Popup for SN Design appears in SN Ops when creating server.
|
CSCsj22810
|
Initiator is discovered as target.
|
CSCsj22878
|
High disk usage occurs during windows snapshot process.
|
CSCsj24974
|
Unable to clear server imaging failed configuration error.
|
CSCsj29212
|
Redundancy coup not rejected when remote DB backup cannot be reached.
|
CSCsj29264
|
CIFS shares randomly go into fault state, causing Window Deploy failure.
|
CSCsj29480
|
The show fault {status | history} command output needs to be changed.
|
CSCsj31780
|
Failed to restore database on first attempt.
|
CSCsj32035
|
CIFS Share drop-down menu shows VFrame-created CIFS Share.
|
CSCsj34950
|
Deploy Server with Emulex HBA unable to boot up from SAN.
|
CSCsj36735
|
Incremental logical network saves cause cleanup-svi failure.
|
CSCsj38360
|
VFrame does not clean up SVI during undeploy after Create SVI failure.
|
CSCsj38386
|
Failed to reinitialize database at first try.
|
CSCsj42362
|
Stopping two SNs with FWSM at same time generates DB exception error.
|
CSCsj42960
|
The df & mount cmd outputs do not show non-root NFS mounted partitions.
|
CSCsj44774
|
Setup run on secondary device fails because of problem in setup_ids.sh.
|
CSCsj46290
|
Unable to replicate servers in imaging failed state after VFrame reboot.
|
CSCsj49581
|
No option to restart backup service.
|
CSCsj50030
|
Resource err on L3 when all IP aliases are set as primary on L3 switch.
|
CSCsj51511
|
Shutting down VFrame interface to filer, switch backup to local fails.
|
CSCsj55739
|
NIC teaming for Dell server with BroadCom NIC does not work.
|
CSCsj59301
|
Error generated during CSM based service network deployment.
|
CSCsj63387
|
IDS will not synch to each other if data VIP is in DNS.
|
CSCsj77199
|
Filer exports not consistently updated with multiple host deploys.
|
CSCsj77259
|
Scheduled jobs not shown when number of jobs is greater than the max.
|
CSCsj88578
|
Storage macros do not handle special chars in usernames/passwords.
|
CSCsj92114
|
When acquiring servers, Windows NIC HA/Switch HA properties ignored.
|
CSCsk81527
|
Creating an IPv4 address range fails when using the /23 subnet mask.
|
Documentation Updates
The "Replacing a Failed Ethernet Switch" section in the Cisco VFrame Data Center 1.1.4 Administration Guide and the online Help has been updated. The updated section is a follows:
Replacing an Ethernet Switch
Depending on whether the Ethernet switch you want to replace is non-stackable or stackable, perform one of the following procedures:
•Replacing a Non-Stackable Ethernet Switch
•Replacing a Stackable Ethernet Switch
Replacing a Non-Stackable Ethernet Switch
You can physically replace an Ethernet switch being managed by Cisco VFrame Data Center while maintaining its managed status. After you replace the switch and then schedule or run a discovery, VFrame detects the new replacement switch and provides you with the option of making it accessible to Cisco VFrame Data Center.
Note We recommend that you replace a switch with a device that is in the same Cisco Ethernet switch family. For example, you can replace a 3-slot Catalyst 6503 with 9-slot Catalyst 6509.
Cisco VFrame Data Center does not enforce OS versions between the previous switch and the replacement switch.
Before You Begin
Record the IP address of the switch being replaced. You will need to configure the replacement switch with the same IP address.
Procedure
Step 1 Replace the switch.
Step 2 Configure the replacement switch with the IP address of the switch being replaced. Ensure that the replacement switch is set up with the same configuration as the switch being replaced.
Step 3 Choose Tools > Discovery.
Step 4 Run a discovery using the IP address of the replacement switch.
You do not need to set a distance for this discovery because you are only interested in discovering the replaced switch. After it is discovered, two warning messages appear in the Jobs Log:
A new device with IP address 209.165.200.225 (identity: MarComm) was not discovered
because a different device (209.165.200.225) with the same IP address already exists.
If you replaced the hardware of the device 209.165.200.225, please use the feature
"Replace Device."
Note The discovery is also marked failed in the top log in the Discovery tab.
Step 5 Choose View > Resources.
Step 6 In the Discovered Devices pane, place your mouse cursor over the switch.
A tool tip appears. In the tool tip, Fault State should read Error.
Step 7 Choose View > Alarms.
The following message appears in the Summary field:
A different device with the same IP address was discovered. If you replaced the hardware
of this switch, please use the feature 'Replace Device.'
Step 8 Choose View > Resources.
Step 9 Perform one of the following:
•In the Discovered Devices pane, right-click the switch.
•Click Actions.
Step 10 Choose Replace Device from the menu.
A pop-up appears with the following message:
A hardware change has been detected. Do you want to rediscover this device without losing
the VFrame Data Center configuration?
Step 11 Click OK.
The replacement operation begins. The replacement operation is essentially a rediscovery of the switch. However, if the previous switch was managed, the replacement switch will be managed.
When the replacement operation begins, a new entry appears in the Logs tab. When the replacement operation finishes and it is successful, the word Success appears in the Status field. The switch is now accessible by VFrame.
Replacing a Stackable Ethernet Switch
In Cisco VFrame Data Center, stackable switches connected together in a stack are displayed and managed as a single switch device with each stackable switch chassis represented as a module. Stackable switch chassis replacement is treated in the same way as a line card replacement.
Use the following procedure to replace a stackable Ethernet switch.
Procedure
Step 1 If the switch is operational and has not failed, place it in maintenance mode. However, if the switch has failed, you do not need to place it in maintenance mode.
Step 2 Replace the failed switch chassis and connect the new switch into the stack (if any).
Step 3 If you are replacing one of the switches in a stack, change the ID of the new switch to the ID of the previous switch.
The following example shows the CLI commands used to change the switch ID:
switch(config)# switch 2 renumber 9
Note We recommend changing the switch ID offline before adding the switch to the stack. If you do not change the switch ID offline, avoid running discovery, otherwise VFrame discovers the new ID and retains old ID, causing the switch replacement to fail.
Step 4 Choose Tools > Discovery.
Step 5 Run a discovery by using either the IP address of the chassis or by rediscovering all managed devices.
Step 6 Choose View > Resources.
Step 7 In the Discovered Devices pane, place your mouse cursor over the switch and choose Properties.
Step 8 Verify that the properties of the switch have been updated.
Step 9 Choose View > Alarms.
Step 10 Verify that the faults for the previous switch are cleared.
Related Documentation
Table 16 describes the documentation available for Cisco VFrame Data Center 1.1.4.
Table 16 Cisco VFrame Data Center Documentation
Document Title
|
Available Formats
|
Cisco VFrame Data Center 1.1.4 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 1.1.4 Administration Guide
|
This guide is available in the following formats:
•On Cisco.com.
•Included in the online help in HTML and PDF formats.
|
Cisco VFrame Data Center 1.1.4 Programmer's Guide
|
This guide is available on Cisco.com
|
Cisco VFrame Data Center 1.1.4 Regulatory Compliance Information
|
Printed document included with the product.
|
Important Safety Information
|
Printed document included with the product.
|
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.
|
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath 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. (0709R)
© 2007 Cisco Systems, Inc. All rights reserved.
