Feeds:
Posts
Comments

Archive for April, 2011

Problem

I have installed windows 2008 storage server (64-bit) and after the OS installation I didn’t know how to log in to the server.

Solution

The default user name and password for Windows 2008 Storage Server are:

  • Administrator
  • wSS2008!

Fixed!

Yaron.

Advertisements

Read Full Post »

Problem

We  have cloned a configuration from the library to the workspace , afterwards we try to deploy the configuration and received the following error: “Unable to deploy virtual machines in resource pool”

Due to the fact that the lab manager server does not deploy the configuration equally between the hosts , we manually disabled all hosts except for the one that we wanted to deploy the configuration on, and when we try to deploy the configuration we received that error message.

Solution

  • Stand on the configuration name > Delete Revert point

            

  • Deploy the environment.
  • After deploying the environment, power off the configuration.
  • Take a snapshot for the configuration.
  • Power on the configuration.

Fixed.

Idit & Yaron.

Read Full Post »

In our environment we use promiscuous mode in order to record calls between phones. In order to configure the VOIP you’ll need to follow the following steps:

  • Define a physical switch that will be your VOIP switch. In this switch you’ll need to define one port configured with port mirroring (span port). The span port is a port that all of the telephony traffic will be duplicated to it. In our environment we use CISCO 2960G switch for the VOIP.

             How to Define the “VOIP” Switch?  

                           

  • Connect the phones into the VOIP switch which you defined in the step above.
  • Make sure that in your ESX one physical network adapter is connected to hub while the other physical network adapters connected to your LAN switch.
  • Define a virtual switch with special parameters on each ESX server by using the following link: https://vvirtual.wordpress.com/2011/04/14/how-to-define-span-port-virtual-switch-in-esx-4/
  •  Connect one of your virtual machines into the virtual “VOIP” switch

             How to Connect your Virtual Machine into the Virtual “VOIP” Switch? 

  • Add the virtual machine 1 network adapter that is connected to the LAN
  • And another network adapter that is connected to the Voip.

                          For example:

                         

Below you can find a diagram which demonstrate how we have been implementing VOIP in our environment:

We hope that this article will help you to implement this solution in your environment 🙂 

Yaron & Idit.

Read Full Post »

Span Port Virtual Switch Configuration

  • From the vSphere client stand on one of the ESX servers
  • Go to Configuration > Networking > Add Networking  > Virtual Machine
  • Choose the physical NIC which is dedicated to the VOIP and is connected to the Hub
  • We have renamed the name of the virtual port group into: VoipCapture

             

  • Go to the Virtual Switch Properties
  • Go to vSwitch > Edit

             

  • Move to Security tab and change the Promiscuous Mode into : Accept

            

  • Go back to vSwitch > Edit ,stand on the VoipCapture virtual port Group > Edit
  • Move to Security tab and mark Promiscuous Mode : Accept

              

  • Move to Traffic Shaping tab and mark Status : Disabled

            

  • Move to NIC Teaming tab and mark Network Failover Detection: Link Status Only

              

  • Note:  If you have more than one ESX server, repeat these steps for each ESX server.

 Yaron & Idit.

Read Full Post »

Problem

I tried to revert into a snapshot to a certain configuration in Lab Manager 4 and received the following error: Invalid “.vmx” file containing “config.version” field value of “0”. vCenter Lab Manager only supports virtual machines with “config.version” field value of “8”.

It didn’t happen every time, it happens once in a while.

Solution

  • Try to revert again (Lab Manager might undeploy the environment)
  • In case the environment was undeploy, deploy the environment (without powering on theenvironment)    

            

  • Go to Monitor > Activity Log ,and see if  prior to the unemployment the revert task completed successfully. If the answer is yes, after the deploy there is no need to revert the configuration again.

            

Fixed!

Idit 🙂

Read Full Post »