AMS and Vmware vSphere virtualization

Hi,
We are now running AMS 5 on Centos and on hardware machine with 2 quad core and 16GB memory.
Does AMS 5 can be install and run on virtual server like Vmware vSphere ?
I'll be appreciate to also get official answer form adobe representative.
Thanks,
Alon

We haven't qualified VDI 3 yet for vSphere. But we try to do this in one of the upcoming patches.
-Dirk

Similar Messages

Sequencing multiple versions of the VMWare vSphere client (and reducing the size of the final sequence)

Application Name: vSphere client
Application Version: 4.1, 5.0, and 5.5 (all in one package)
Company Name: VMWare
Sequencer Version: 5.0 SP1 or SP2
App-V Client Version Tested On: 5.0, 5.0 SP1, 5.0 SP2
Operating System Sequenced On: Windows 7 (64bit)
Pre-requisites: Orca
Client Operating Systems Successfully Deployed To: Windows 7 (64bit), Windows Server 2008 (64bit)
*Posted by non-Microsoft Employee: Cody Lambert (a Fortune 100 company)
If Posted by Microsoft Employee, the Corresponding KB Article Reference:
N/A
Steps to Prepare and Sequence the Application:
Phase 1: Prepare vSphere install to be used in your sequence (to be performed prior to sequencing)
Clear %TEMP% directory on machine you are using to prepare the install
Create a folder that will be referred to as "vSphereInstDir"
that install files are copied to
Download the vSphere 5.5 client from your vSphere management server
Run the installer for the vSphere Client
Once at the Language Selection portion of the installer,
using windows explorer browse to the %temp% directory and copy the files that were just created when the vSphere installer extracted to a directory (name it vSphereInstDir)
Kill the installer
Find VMware-viclient.exe in the files you just copied
and run it
Once at the "Welcome to the installation
wizard" stage of the installer, using windows explorer browse to the %temp% directory and copy the files that were just created into the vSphereInstDir
Kill the installer
Find the VMware vSphere Client 5.5.msi in the vSphereInstDir,
in the second set of files you copied over
Using Orca, open the VMware vSphere Client 5.5.msi
Drop the following rows from the msi (some of the rows may have additional text at the end of the names) (InstallExecuteSequence/VM_InstallHcmon,
InstallExecuteSequence/VM_InstallHcmon_SetData,
InstallExecuteSequence/VM_InstallUSB,
InstallExecuteSequence/VM_InstallUSB_SetData,
InstallExecuteSequence/VM_InstallUSBArbritrator,
InstallExecuteSequence/VM_InstallUSBArbritratorSetData,
InstallExecuteSequence/VM_StartUSBArbSvc)
Save the VMware vSphere 5.5.msi in place
Copy the vSphereInstDir to a network location that
can be used during sequencing on your Sequencer
Phase 2: Sequence the vSphere Client
Pre-requisites: All of the latest available VC++ redist (x64 and x86) are installed on the Sequencer VM
Copy vSphereInstDir to your temporary install directory on your Sequencer (mine is C:\temp)
Start up the Sequencer
Click Create a New Virtual Application Package
Click Next with Create Package (default) selected
Click Next on the Prepare Computer screen, taking
note of any findings
Click Next with Standard Application (default) selected
Choose Perform a custom installation, then click Next
Input the Virtual Application name (vSphere Client
5.5 for example)
Enter the Primary Virtual Application Directory (C:\vSphere55
for example) and click Next
Using Windows Explorer find the Visual J# install (vjredist64.exe) in the vSphereInstDir you copied over. Install using defaults
Using Windows Explorer, find and install the vSphere client using the VMware vSphere Client 5.0.msi located in the vSphereInstDir you copied over.
Change the installation directory to use the Primary Virtual Application Directory you configured above (C:\vSphere55 for example). Install using
defaults
While the sequencer is still monitoring changes connect to the 4.1 environment to get the files needed. To do this, launch the vSphere client and connect
to your 4.1 environment. When prompted, choose RUN to install the files needed for the 4.1 environment.
While the sequencer is still monitoring changes connect to the 5.0 environment to get the files needed. To do this, launch the vSphere client and
connect to your 5.0 environment. When prompted, choose RUN to install the files needed for the 5.0 environment.
With the sequencer still monitoring changes, after the additional environments have been installed, delete all of the language folders from the install locations
that are not required. You will find that there are language folders in each of the different modules that are installed. Make sure look in every folder. This will free up approximately 300mb from the package.
When done, check the box to finish the sequence and continue cleaning up the sequenced application.
Known Issues/Limitations:
Functions that require the USB Arbritration Service will not work
Approximate Sequencing Time:
20 minutes
Descriptive Tags:
App-V, 5.0, VMWare, vSphere, Recipe, Guidance
Credit Due: Thanks to Rorymon and Aaron Parker for accurate information that allowed for me to put together this recipe.

Can you double check the that the following were removed from the MSI:
InstallExecuteSequence/VM_InstallHcmon
InstallExecuteSequence/VM_InstallHcmon_SetData
InstallExecuteSequence/VM_InstallUSB
InstallExecuteSequence/VM_InstallUSB_SetData
InstallExecuteSequence/VM_InstallUSBArbritrator
InstallExecuteSequence/VM_InstallUSBArbritratorSetData
InstallExecuteSequence/VM_StartUSBArbSvc

What's the difference between OEM and standart licensing of VMware vSphere for users?

Good day,
Could you please explain me,
What's the difference between OEM and standart licensing of VMware vSphere for users?

The difference is usually the support you get. With OEM versions you'll often get support from the OEM and not from VMware directly.
André

Virtualization, i have windows xp and vmware installed

Virtualization, i have windows xp and vmware installed, as virtual machine i installed in vmware windows server 2008, i want to make the network work between mi real machine the windows xp and the virtual machine windows server 2008.
The thing is i only have 1.5 Gb of Ram at the moment, i just want a minimal networking configuration so as to study networking.
It could be good if someone can tell me how to configure Vmware so as to make the network work, as firewall i only use the windows xp firewall.
Thanks
Mariano Alippi

Can you please tell me what is your goal?? what are you trying to achieve.
Akshay Pate

Cisco WAAS-Global policy for VMware Vsphere and/or 3par replication

So, this is somewhat annoying that VMware Site Recovery Manager 5.0 does not seem to get much replication acceleration, mostly it is just Pass Through. I have read a couple of Cisco marketing powerpoints that say WAAS will accelerate VMware. But there are no Policies to that effect or configuration assistance. So, vmware has a hundred or so connections in passthrough, all using port 44046, this web site here:
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1009562
Shows that this is the port used for Ongoing replication, and port 31031 is used for the initial replication. So, I have two 674-8gb with inline cards. One in main office, one at DR office, both running 5.0.1. The Lan ports on each side point to the LAN and the WAN interfaces on each end point to each other. I have a layer 2 - 90Mbps link between the two locations, so "show cdp neighbor" shows the WAN interface connected.
My question is, is there a policy I should create for this data to be accelerated and stop being "PT Asymmetric"?
Second question, very similar to the first, 3par replication. Same as above, but 3par uses port 5785 and the traffic shows up as "PT In Progress", there are only 6 or so connections in this state, but all are on this port 5785.
If I pull up the pretty graphs on the CM for this device, it shows a well distributed graph, but if I click the check box for "include Pass-Through" it turns all blue and says 100% of traffic is "other-traffic" Since 99% of what goes between these two WAAS devices is VMware site recovery manager 5.0 and 3par replication, I would really like to find a fix for this.

ANSWER ******* SOLUTION ******* ANSWER
I created 2 - Optimization Policy Rules for "WAAS-GLOBAL"
par3-rcopy, destination ports - 5785, 3491-3492, Application - Replication, TFO with DRE Adaptive and LZ
VMware-Replication, destination ports - 44046, 31031, Application - Replication, TFO with DRE Adaptive and LZ
Then I rebooted both WAAS devices and shut off the link for 20 minutes. When I brought the link back online. 100% of data was accelerated, and 99% of the data was classified as "Replication" data. I now get between 60% and 90% acceleration on this "Replication" traffic. The final 1% is other data, remote desktop, ssl, citrix, sql, web...
Lessons learned: The 3par and VMware keep TCP connections open forever, and once the traffic in that session is classified as something, "other traffic" or "Pass Through" it does not change until you reset the connection. So, if you make any changes, you have to shutdown the link, and clear all TCP connections from the WAAS devices, then it will go to a different optimization rule.
Final thoughts: I am not completely sure that the Optimization policy rule "TFO with DRE Adaptive and LZ" is the BEST possible rule to use for this traffic. If anyone has a better configuration for this traffic, I would really appreciate your input.

Cisco Prime Collaboration Deployment with BE7K and VMWare license

Hello, I am looking for some help trying to figure out if Cisco Prime Collaboration Deployment can be used to upgrade our existing 7.1.5 cluster. From what I have read there is a API problem with the VMWare license that comes with the BE7K. But after reviewing the BOM/quote from my VAR it lists the foundation license which based of the release notes is supported.
UCSS-U-VMW-FND-5-1
UCSS Cisco UC Virt. Foundation Five Year - 1 server
Has anybody out there had expericne with PCD and BE7K'?
This is from release notes of PCD
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/10_5_1/CUCM_BK_P139675A_00_pcd-rns-1051/CUCM_BK_P139675A_00_pcd-rns-1051_chapter_010.html
Search for “Business Edition 7000” and it will state it is not supported with PCD. It is because the licenses that the BE 6k and 7K are shipped with don’t enable certain VMware APIs that PCD needs.
“Virtualization Software License Compatibility
Cisco Prime Collaboration Deployment is not compatible with all license types of VMware vSphere ESXi, as some licenses do not enable required VMware APIs.
The following are compatible with Cisco Prime Collaboration Deployment:
Cisco UC Virtualization Foundation (appears as "Foundation Edition" in vSphere Client)
VMware vSphere Standard Edition, Enterprise Edition, or Enterprise Plus Edition
Evaluation mode license
The following are not compatible with Cisco Prime Collaboration Deployment:
Cisco UC Virtualization Hypervisor (appears as "Hypervisor Edition" in vSphere Client)-preloaded on Cisco Business Edition 6000 and Business Edition 7000
VMware vSphere Hypervisor Edition
Any help would be appreacted.
JP

Thanks Jamie for repsonding, we haven't made any purchase's yet but I wanted to ensure we are purchasing a solution that won't lead to a lot of frustration. We only have 1000 phones so we are pretty small and the BE7K seems to be a good fit and value.
Cheers,

VMware Vsphere 5.0

Hi,
We are looking for suggestions and advice from the users who are running Oracle EBS R12 in VMware Vsphere 5.0 environment.
Thanks & Regards
Chakrapani.S

Helping the little guys think big!
http://www.microage.com/data-center-refresh-and-server-virtualization-provides-big-benefits.html
This topic first appeared in the Spiceworks Community

Vmware vsphere health check report v5.1.0

Hi,
I'm currently using the vmware vsphere health check report v5.1.0 script. I switched from another perl script to this and the report provide much more information. There is one thing that don't seem to work properly though..
I currently have a failed disk in my server and the report is showing "unknown" status next to 3 disk / disk day. If I run the other script I have used in the past, I have 3 alerts in red clearly showing that something has failed. Would any of you know why it's showing as unknown instead of critical in the report?
Old Script
o Disk or Disk Bay 15 Drive 15 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 15 Drive 15 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 15 Drive 15 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 15 Drive 15 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 15 Drive 15 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 14 Drive 14 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 14 Drive 14 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 14 Drive 14 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 14 Drive 14 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 14 Drive 14 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 13 Drive 13 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 13 Drive 13 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 13 Drive 13 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 13 Drive 13 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 13 Drive 13 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 12 Drive 12 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 12 Drive 12 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 12 Drive 12 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 12 Drive 12 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 12 Drive 12 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 11 Drive 11 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 11 Drive 11 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 11 Drive 11 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 11 Drive 11 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 11 Drive 11 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 10 Drive 10 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 10 Drive 10 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 10 Drive 10 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 10 Drive 10 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 10 Drive 10 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 9 Drive 9 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 9 Drive 9 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 9 Drive 9 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 9 Drive 9 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 9 Drive 9 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 8 Drive 8 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 8 Drive 8 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 8 Drive 8 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 8 Drive 8 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 8 Drive 8 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 7 Drive 7 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 7 Drive 7 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 7 Drive 7 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 7 Drive 7 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 7 Drive 7 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 6 Drive 6 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 6 Drive 6 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 6 Drive 6 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 6 Drive 6 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 6 Drive 6 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 5 Drive 5 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 5 Drive 5 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 5 Drive 5 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 5 Drive 5 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 5 Drive 5 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 4 Drive 4 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 4 Drive 4 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 4 Drive 4 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 4 Drive 4 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 4 Drive 4 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 3 Drive 3 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 3 Drive 3 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 3 Drive 3 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 3 Drive 3 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 3 Drive 3 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 2 Drive 2 0: Drive Fault - Assert: 0
o Disk or Disk Bay 2 Drive 2 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 2 Drive 2 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 2 Drive 2 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 2 Drive 2 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 1 Drive 1 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 1 Drive 1 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 1 Drive 1 0: In Critical Array - Assert: 0
o Disk or Disk Bay 1 Drive 1 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 1 Drive 1 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 0 Drive 0 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 0 Drive 0 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 0 Drive 0 0: In Critical Array - Assert: 0
o Disk or Disk Bay 0 Drive 0 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 0 Drive 0 0: Rebuild In Progress - Deassert: 0
New Report
BIOS 1 ABR Status 0: Unspecified - Deassert
0
OK
BIOS 1 Firmware Error 0: Unspecified - Deassert
0
OK
BIOS 1 Firmware Error 0: Unspecified - Deassert
0
OK
Cooling Unit 1 Cooling Zone 1 0 - Fully redundant
0
OK
Cooling Unit 2 Cooling Zone 2 0 - Fully redundant
0
OK
Cooling Unit 3 Cooling Zone 3 0 - Fully redundant
0
OK
Disk or Disk Bay 0 Drive 0 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 0 Drive 0 0: In Critical Array - Assert
0
UNKNOWN
Disk or Disk Bay 0 Drive 0 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 0 Drive 0 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 0 Drive 0 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 1 Drive 1 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 1 Drive 1 0: In Critical Array - Assert
0
UNKNOWN
Disk or Disk Bay 1 Drive 1 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 1 Drive 1 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 1 Drive 1 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 10 Drive 10 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 10 Drive 10 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 10 Drive 10 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 10 Drive 10 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 10 Drive 10 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 11 Drive 11 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 11 Drive 11 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 11 Drive 11 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 11 Drive 11 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 11 Drive 11 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 12 Drive 12 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 12 Drive 12 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 12 Drive 12 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 12 Drive 12 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 12 Drive 12 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 13 Drive 13 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 13 Drive 13 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 13 Drive 13 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 13 Drive 13 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 13 Drive 13 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 14 Drive 14 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 14 Drive 14 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 14 Drive 14 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 14 Drive 14 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 14 Drive 14 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 15 Drive 15 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 15 Drive 15 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 15 Drive 15 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 15 Drive 15 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 15 Drive 15 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 2 Drive 2 0: Drive Fault - Assert
0
UNKNOWN
Disk or Disk Bay 2 Drive 2 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 2 Drive 2 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 2 Drive 2 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 2 Drive 2 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 3 Drive 3 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 3 Drive 3 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 3 Drive 3 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 3 Drive 3 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 3 Drive 3 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 4 Drive 4 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 4 Drive 4 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 4 Drive 4 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 4 Drive 4 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 4 Drive 4 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 5 Drive 5 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 5 Drive 5 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 5 Drive 5 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 5 Drive 5 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 5 Drive 5 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 6 Drive 6 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 6 Drive 6 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 6 Drive 6 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 6 Drive 6 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 6 Drive 6 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 7 Drive 7 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 7 Drive 7 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 7 Drive 7 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 7 Drive 7 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 7 Drive 7 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 8 Drive 8 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 8 Drive 8 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 8 Drive 8 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 8 Drive 8 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 8 Drive 8 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 9 Drive 9 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 9 Drive 9 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 9 Drive 9 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 9 Drive 9 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 9 Drive 9 0: Rebuild In Progress - Deassert
0
OK

Thank you for the follow up. I do understand that a completly unreadable disk might throw an unknown status but the status is different from one report than the other. On one side, it clearly shows in red that the disk has something and on the side, it just throws a "I don't know what's going on with the disk". I ran both report the same day and i'm expecting some red in the report to warn me if a disk fail.
Is there a way to change that behavior from the health check script?

Where i can get a Cisco VMware Vsphere ESXi 4.1 update 1 installable media

Hi All,
can someone from cisco tell me how to get cisco vmware vsphere ESXi 4.1 update 1 that was certified by Cisco ?
because the last release from the vmware website still 4.1 without update 1.
http://downloads.vmware.com/d/details/esxi41_cisco_oem_iso/ZHcqYnRkdHdiZCpwcA==
Thanks.
Berwin H.

Sorry for any spelling errors:
What is working well for us, is to always get the latest ESX(i) release from vmware, apply all patches and then make sure to install the newest drivers for Cisco fnic (hba) and enic (lan) that can be found on the vmware site.
During our first UCS upgrade (we did not have installed the Cisco drivers) we experienced some issues. A lot of our VMs lost connectivity to storage for about 2-3 minutes during the reboot of the primary FI. After opening a support request at vmware and Cisco, vmware sent us a newer fnic driver, as the standard driver included in the ESX iso did not handle hba failover very well.
Since that upgrade we always keep up to date the enic and fnic drivers for Cisco UCS. They can be found on the VMWare ESX download site.
Newer drivers are also available on the Cisco UCS driver CD, but those are not yet signed by vmware, so it may be a better idea to use those tested by vmware.
Since we are handling ESX updates like this, every UCS upgrade and everything else worked like a charm and my pulse during upgrades got divided by 2
BTW: Also with other server manufacturers we could have saved us a lot of trouble if we simply had upgraded adapter drivers earlier.

Cisco LMS 4.2 Appliance on VMware vSphere 4.0

Hi all,
I'm currently trying to install the Cisco LMS 4.2 Appliance on a VMware vSphere 4.0 environment.
I'm following the http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.2/install/guide/instl.html#wp1689675
guide.
I downloaded the Cisco_Prime_LAN_Management_Solution_4_2.iso and I started the server.
I get this screen and I choose option 1:
A Welcome message appears:
Welcome to Cisco Prime LAN Management Solution 4.2
To boot from hard disk, press <Enter>
The following options appears:
•[1] Cisco Prime LAN Management Solution 4.2 Installation
This option allows you to perform installation of LMS 4.2.
•[2] Recover administrator password
This option allows you to recover the administration password. Follow Step 3 to Step 17 of Recovering Admin Password on Soft Appliance Installed on VMware, to recover the administration password.
•<Enter> Boot existing OS from Hard Disk
This allows you to boot up the existing OS available in the hard disk.
However, unlike the installation on my laptop (using VMware Workstation) I cannot get to this part:
Enter the following configuration details of the server:
•Hostname
•IP Address
•Subnetmask
•Gateway
•DNS Domain
et cetera
What follows looks like an installation to me.
When this stops I get a
localhost login:
I cannot enter Setup as I get a password statement afterwards.
Can somebody please help me as I'm having no idea what went wrong..
Many thanks in advance.

Thanks for your help, Marvin.
We went ahead with the .ova file and it worked alright.
We also did a little test and it seems that the .iso file does work on some VMware platforms. Our test environment had a VMware vSphere 4.1. When we started a VM with the same specs and the ISO file mounted, the installation did succeed.

Vmware vsphere update manager client 5.1 update 3 fails to install

Hi guys,
I tried to install VMware vSphere update manager client 5.1 update 3 to upgrade the old client (5.1 update 2) and keep failing without any visible error. I notice that right after start installing sun java runtime environment the installation fail and the rolling back process start and abort the installation. Did any of you have experience this before? if yes what is the solution.
vCenter 5.1 update 3 Build 2306353
ESXi 5.1.0,2191751
Thanks in advance.

Hi,
Had the same problem.
Seems to be no solution apart from uninstalling 5.1 U2, then installing 5.1 U3. (worked for me)
It's the same problem as this KB: KB2092290, which remains unresolved.

VMware vSphere ESXi Lockup

We are running VMware vSphere 4 ESXi on Sun X6450 blades with the Intel six core dunnington processors, boot from Compact Flash, iSCSI storage, 10GbE, and 92GB of RAM. The blades run fine for 10 to 30 days before completely locking up. There is no PSOD. No indication of any log that something has gone wrong. The machine simply stops responding. The issue is intermittant and apparently random. We can't find any correlation to the problem except the hardware. We are running on X6250 blades with similar configuration as well with no problem. Also, we see the problem when there is high load, when there is moderate load, and when there is no load. We have even seen it in blades which have ESXi in maintenance mode.
Has anyone seen a similar problem? If so, what is your config?

Are you using NFS? I suspect I've hit this bug on two separate X6250s while doing some I/O performance testing (Iometer testing disk access to VMDKs on NFS datastore): http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01804949
My stack trace isn't exactly the same, but it's definitely an IP stack deadlock of some sort. At first, I was going to blame hardware failure on one of the newer X6250s, but then I tried another identical unit and it PSODs in just the same fashion. If it's not a "to-be-fixed-in-U5" bug, then it might be the 10Gig Multithreaded adapter driver.
Charles

Bootcamp and VMWare Fusion, possible problem with Bootcamp, cant see USB.

Hey,
Would really appreciate your help. So I have MBP mid 2010 with the latest version of OSX Mountain Lion and decided to install Windows 7 on it. I gave it to the professional IT guy, who installed Windows 7 through the latest version of VMWare Fusion. It is not bad overall, but at times incredible slow (which might be because of my slow processor).
So I decided to install Windows 7 through the BootCamp Assistant - USB way. And did the following steps:
1)Format USB, put Windows 7 .iso image on it
2) Installed the latest Windows software through the Bootcamp (step2 tick). However, it said that the latest version would be installed only after Windows 7 is installed (in step3 tick). I clicked OK and moved to Step 3
3) I started Installing Windows and had a few errors (which were solved by repairing the HDD after rebooting in recovery mode), but all went fine until almost the end. Before the bar almost moved to the end my macbook went to reboot and I though it was all done and ready. I clicked the alt at *ding* sound and no USB was detected.
I checked disk utility and the thing was portioned.
I was thinking that MBP doesn't recognize the second Windows installed, and VMWare Fusion needs to be deleted in order to run Bootcamp. I haven't deleted anything, wanted to ask for advice first.
Any one could think of what's wrong? Thank you.

You can only install Windows from a USB in one of these computers:
- MacBook Pro with Retina display.
- MacBook Air.
- Mac mini (Mid 2010 and newer).
- iMac (Late 2012).
Your Mac doesn't support the Windows installation through a USB drive. However, you have installed Windows through a USB drive. What did you do?
You did an EFI installation (or a native installation). Apple doesn't support this option because of the huge number of problems it gives, and you have probably erased OS X (or you erased the Windows partition that Boot Camp created, both possibilities). The error you mentioned in 3) was probably that the Windows installer detected that you have a MBR disk instead of a GPT one, and you erased everything.
First of all, to make sure that you erased everything, hold the Option (Alt) key while your Mac is starting. If you see the OS X partition, start up from it, and make a complete backup of your files with Time Machine.
Then, what I recommend you is to erase the whole drive by starting in Internet Recovery (hold Command, Option and R keys while your Mac is starting), and use the Time Machine option to restore your files

ISight in not working in Photo Booth, iChat, and VMWare with Snow Leopard

System Info
Model Name: iMac
Model Identifier: iMac8,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.8 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 4 GB
Bus Speed: 1.07 GHz
Boot ROM Version: IM81.00C1.B00
SMC Version (system): 1.30f1
OS Version 10.6.1
Symptoms
iSight is not working, a blank screen is shown in the following Apps / VM
1. Photo Booth
2. iChat
Visible to VM app, but unable to connect in Windows XP running on VMWare
It is however viewable in Skype preference Video tab
Visible in System Profiler under USB
Following actions taken for troubleshooting
SMC reset - by unplugging all cables over couples minutes, as well as CommandOption+PR key at boot time
Repairing Permission on the Macintosh HD drive, rebooted after and didn't work
Not user account specific, tried different account and the same problem persists

Welcome to Discussions, Stanley Chung
Sorry you are still having problems even after trying the good suggestions from Ralph and Boomer.
I did not see specifically from your posts that your iSight worked before upgrading to Snow Leopard, but I am inferring from your topic's title that it did. If your iMac came with Snow Leopard installed, please post and tell us whether you erased the disk and reinstalled all your iMac's software before you started using it. If you upgraded your iMac to Snow Leopard, consider the following.
(1) Until you get iSight working, do all your testing while no peripherals other than keyboard/mouse are attached to your iMac. To eliminate all possibility of any conflict external to your Mac, be sure you also disconnect any wireless devices (iPod, printer, etc) connected to your system.
(2) If you still have problems with all you have tried, it seems to me that you must have a software issue. You might try uninstalling Skype and VMWare and testing again to see if those installations are causing a conflict.
(3) Check the support sites for all of your third party software to be sure there are no known Snow Leopard issues and that you are using the latest compatible versions.
(4) If the problem still exists and you have not already tried this, reinstall Snow Leopard, repairing permissions immediately before and after the reinstall.
(5) If your problem remains and System Profiler still shows your inbuilt iSight as a USB device, I suggest you backup all important files, erase your disk, reinstall all Apple software, and test to see if iSight works properly. Once it does, you can install any necessary peripherals and third-party apps one-at-a-time, testing after each addition to see if one of them is causing problems.
EZ Jim
MacBook Pro (13 inch, Mid 2009) 2.26GHz w/Mac OS X (10.6.1) G5 DP 1.8GHz w/Mac OS X (10.5.8)
G4 PowerBook 1.67GHz (10.4.11) iBookSE 366MHz (10.3.9) LED Cinema Display External iSight

Solaris 10 Update 10 (8/11) panics on boot under virtualbox and vmware

I am trying to install S10 U10 in a VM and have downloaded the DVD ISO image. I verified the MD5 checksum then tried to boot the installation from the DVD image but it panics on boot under both Virtualbox (latest version) and VMware workstation (latest version). How can I get this working?
Thanks
Andrew.
Edited by: 884653 on 19-Sep-2011 13:18

I had no problems installing Solaris 10 U9 x86 from an ISO download. The ISO download of Solaris 10 U10 x86 I got recently is another matter. When I try to install U10 with VMware Player or Virtualbox on a Dell PC with Windows 7 the install process hangs. I can't tell if this behavior is a panic or not, but it is a problem. On both VMware Player and Virtualbox the install process gets to the following screen and never does anything else:
SunOS Release 5.10 Version Generic_147441-01 64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
Any ideas? Thanks.

AMS and Vmware vSphere virtualization

Similar Messages

Maybe you are looking for