vmware

vSphere: NUMA 706: Can’t boot system as genuine NUMA

Posted on Updated on

If you install vSphere on NON-NUMA hardware the following warning message will be displayed on the Service Console splash screen

cpu0:0)NUMA: 706: Can’t boot system as genuine NUMA. Booting with 1 fake node(s)

To resolve the warning message uncheck the option setting vmkernel.boot.usenumainfo

c7000 – Enclosure Interlink

Posted on Updated on

Today I was able to interlink my 3 HP c7000 blade chassis.  I used the document listed below as guidance and here are some of my brief note/findings around this.

  • Interlinking the HP c7000 blade chassis (BC) is simple as connecting a CAT5e or better network cable to the  UP and DOWN interlinks ports on the back of your C7000.
  • Keep in mind the BC at the top of the link (or last BC pointing down) will become the master. 
  • Per the document link below, HP recommends you interlink BC’s per rack vs. across multiple racks and the max BC’s to be interlinked is 7.  
  • The linked enclosures will enforce a common rack name on all the linked enclosures; however, the enclosure name will remain unique.  
  • Interlinking the c7000 chassis allowed me to have a one-stop web page for the BC’s.  However, the BC’s are still unique in their settings, user accounts, etc.

Note: If you’re using local accounts then the account names and passwords for each BC need to match for single login to work.


Reference Links…

Updated link on 09-20-2017 http://h20565.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=1844065&docId=emr_na-c00698286&docLocale=en_US

 

ESX 4.1 Host Profile Copy

Posted on Updated on

Wouldn’t it be nice be able to make a copy of an existing host profile allowing you to create new profile?

vCenter Server 4.1.0 doesn’t have a copy function but you can export the profile then import it with a different name.

Note – Keep in mind this might not work on your destination hardware, you should use a base profile that is simlar and go fromt there. You also might have to tweek the copied profile for it work properly.

In vCenter Server 4.1.0 go to the Host Profiles area on you vCenter server

Simply right click and choose export profile

Choose ok to this warning…

Choose a good name and click on save

When the creation is complete from the main window Choose “Create a new host profile” > Import Profile >, Browse to the Import location and choose your file > Enter a new Name for the profile > Choose Finish

Once your done you can now edit this profile, updated it, add hosts, etc..

vmworld 2010 – The Schedule

Posted on Updated on

Here is my schedule for vmworld 2010…  This year I plan to hit the self-paced labs in the morning, followed up by super-sessions, performance, and cloud computing throughout the week.   Hopefully I’ll have time for lunch and the vendor area!
EA7850  —  Design, Deploy, and Optimize Microsoft SQL 2008
SS1055  —  Partner Track Super Session
TA8102  —  Tuning Linux for Virtual Machines
EA8210  —  Zimbra and The Future for Mission Critical Apps in the Virtualized Enterprise
ALT3005  —  VMware vCenter™ Orchestrator – Orchestrating the Cloud 
ALT2004  —  Building the VMworld Lab Cloud Infrastructure
EA7829  —  Panel Discussion: Virtualization’s Impact on the Delivery of Healthcare IT Services
TA9420  —  vSphere 4.1 Overview
SP9820  —  Getting the Most Out of Your Storage Infrastructure with Client and Server Virtualization
TA6720  —  Troubleshooting using ESXTOP for Advanced Users
TA8133  —  Best Practices to Increase Availability and Throughput for VMware
SS1011  —  How Cisco, EMC and VMware Are Changing the IT Landscape with Vblock Converged Infrastructure
TA8623  —  Storage Super-Heavyweight Challenge
SP9721  —  How to Use Virtual I/O to Provision and Manage Networks and Storage Resources in a Private Cloud
TA6944  —  PowerCLI Is For Administrators!
TA8051  —  Infrastructure Technologies to Long Distance VMotion – What Is “VM Teleportation”?
TA8101  —  Virtual Storage and VMware vSphere: Best Practices and Design Considerations
TA7994  —  vStorage Update for vSphere 4.1 

ESX – Using USB to IP Adapeters

Posted on Updated on

Here are some IP to USB Adapters that I know have worked with ESX…

Multi VM Use –http://www.lantronix.com/device-networking/external-device-servers/ubox.html

Single VM Use – http://www.digi.com/products/usb/anywhereusb.jsp#overview

I’ve worked with the DIGI models and they have pretty well…

One note – if you are working with a true VM then you need to enable Windows USB features…

Special Steps for VMware ESX Server Virtual Machines
Since ESX Server does not provide direct support for USB, USB drivers are not installed in the
guest operating system by default. The AnywhereUSB device depends on the USB core files to
install properly.
To enable the rest of the installation to proceed normally, copy and rename the required file from the original operating system CD.
• Source: usbd.sy_ in the \I386 directory of the CD
• Destination: usbd.sys in the \system32\drivers directory of the guest operating system
After copying this file, reboot your machine. You can then continue with the normal
AnywhereUSB installation.

VMware KB TV on You Tube

Posted on Updated on

Here is a great source for VMware related information all on YouTube…

http://www.youtube.com/user/VMwareKB

vSphere Hot Memory Add

Posted on Updated on

I was playing around with vSphere Hot memory add with ESX 4 U1 on a Windows 2008 ETP x64 VM.

I was simple to configure and could be a quick upgrade…

  1. In vCenter Server Shutdown the VM
  2. Right Click > Edit Settings > Options > Under Advanced Choose Memory/CPU Hotplug
  3. Enable Memory Hot Add and CPU Hot Plug

  4. Power on your VM, Go to the Consol for this VM, Wait for it to boot, logon
  5. I noticed mine had a pop up that it added a snap-in
  6. In vCenter Server Right click on the VM, Edit Settings, click on Memory and add the memory you wish..

    (Notice you can’t go down only up… You’ll need to power down to do this)

     

     

    Notes…

    I noticed after clicking OK, my vm console screen went blank for about 10 seconds and then it came back.

    When it did I had the upgraded memory and all was well.

     

    Here’s a great post with more information…

    http://www.boche.net/blog/index.php/2009/05/10/vsphere-memory-hot-add-cpu-hot-plug/

     

     

Installing vCenter Server 4 with Windows 2008 64Bit and SQL2008 64Bit

Posted on Updated on

You might be asking yourself what are the benefits of deploying Windows & SQL 2008×64?

So far I have found one… If you want to position your server for x64 and 2008 then this makes sense.

See these articles for more information..

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010401

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1009080&sliceId=2&docTypeID=DT_KB_1_1&dialogID=101033551&stateId=0 0 101037544

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010023

http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=install/c_preparing_the_vmware_infrastructure_databases.html

http://support.microsoft.com/kb/149605

Here are the basic steps to setup vCenter 4 with Windows/SQL 2008 x64

This guide is for reference, like all articles I post up, they are my notes, so use them at your own risk…

SQL2008 Install…

  1. Setup your VM with ample – CPU, RAM, Disk C: for OS and D: SQL Data
  2. In this case drives are 1 x vCPU, 4GB RAM, C: [50GB] D:[150GB]
  3. Install Windows 2008 x64 Standard Setup
  4. Run the setup from the SQL2008 CDROM
  5. Click on Installation > New SQL Servers
  6. Click okay if your “SQL Support Rules” succeed
  7. Click Install to setup the support install files
  8. Validate that all Setup Support Rules status are Passed (if not remediate), click next
  9. Click next to Product Key
  10. Click next to accept the terms
  11. Choose Database Engine Services, All Management Tools – Basic, Click Next
  12. Change the location of the “Instance Root Directory” to your D: drive using the default folder path, Click Next
  13. Confirm Disk Usage Summary, Click Next
  14. Choose “NT Authority\SYSTEM” for the account for SQL Agent & Database Engine, Click Next
  15. Choose Mixed Mode, Enter the “sa” password, Click on Add Current User Or Add your own, Click Next
  16. Click Next to validate install Rules
  17. Remediate issues if necessary, else Click Next
  18. Click install to start installation, Allow to complete the install of SQL 2008
  19. Click Next to complete and close to exit
  20. Validate your install by opening SQL Server Management Studio
  21. Ensure the SQL Server Agent Service is set to Automatic and is started

SQL2008 Prep for vCenter Server

  1. Open SQL Server Configuration Manager, Click on SQL Server Network Configuration, Choose Protocols for MSSQLserver, Right click on named pipes and choose enable, Restart the SQL Services or reboot
  2. Apply any vmware approved SQL Patches (Ensure a snapshot, backup or other has been taken)
  3. Create the user vcdb, Click on security > Logins > Right Click Choose New User
  4. Type in the user vcdb
  5. Choose SQL Server Authentication then enter a password
  6. Uncheck Enforce Password Expiration
  7. On the left, click on Server Roles
  8. Choose sysadmin, then click on OK
  9. Create the Database vcdb, Right Click on Databases > choose New Database
  10. Enter the Name vcdb for the database name
  11. Click on ‘….’ to add the owner, use vcdb as the owner, click OK
  12. On the left, click on Options, choose simple for recovery mode
  13. Choose OK at the bottom
  14. Click on Security > logins > right click on vcdb choose properties
  15. Change default database to vcdb, choose OK
  16. Create the user vmupd, Click on security > Logins > Right Click Choose New User user
  17. Type in vmupd
  18. Choose SQL Server Authentication then enter a password
  19. Uncheck Enforce Password Expiration
  20. On the left, click on Server Roles
  21. Choose sysadmin, then click on OK
  22. Create the database vmupd, Right Click on Databases > choose New Database
  23. Enter the Name vmupd for the database name
  24. Click on ‘….’ to add the owner, use vmupd as the owner, click ok
  25. On the left click on Options, choose simple for recovery mode
  26. Choose OK at the bottom
  27. Click on Security > logins > right click on vmupd choose properties
  28. Change default database to vmupd, choose OK

Setup ODBC Connectors…

  1. Create a link to the 32Bit ODBC Admin tool (C:\Windows\SysWOW64\odbcad32.exe)
  2. Open the 32Bit ODBC Data Source Admin
  3. Create System DSN for vcdb database, Click on System DSN Tab
  4. Click on Add
  5. Choose ‘SQL Native Client 10.0’ (Don’t Choose SQL Native Client only)
  6. Enter the database name of vcdb
  7. For Server Choose the local server name, Click on next
  8. Choose With SQL Server Authentication
  9. Ensure Connect to SQL is checked
  10. Enter Login ID of vcdb and the password Click on Next
  11. Ensure that Change the Default Database to is checked and vcdb appears below it, Click on Next
  12. Choose Finish
  13. Click on Test data source and look for TESTS COMPLETE SUCCESSFULLY!
  14. Click on OK, then OK again
  15. Create System DSN for vmupd database, Click on System DSN Tab
  16. Click on Add
  17. Choose ‘SQL Native Client 10.0’ (Don’t Choose SQL Native Client only)
  18. Enter the database name of vmupd
  19. For Server Choose the local server name
  20. Click on next
  21. Choose With SQL Server Authentication
  22. Ensure Connected to SQL is checked
  23. Enter Login ID of vmupd and the password Click on Next
  24. Ensure that Change the Default Database to is checked and vmupd appears below it, Click on Next
  25. Choose Finish
  26. Click on Test data source and look for TESTS COMPLETE SUCCESSFULLY!
  27. Click on OK, then OK again

     

Install vCenter Server 4

  1. Open the vCenter Installer
  2. Choose vCenter Server from the Installer screen
  3. Choose Ok for English
  4. If prompted Choose Yes to continue to possible IIS port issues
  5. Click Next on the Welcome Screen
  6. Choose I agree to the terms, click next
  7. Enter your User and Organization Names, Enter your license Key, Click Next
  8. Choose Use an existing supported database
  9. Choose the DSN name of vcdb, click next
  10. Enter the password for vcdb, click next
  11. Ensure Use System Account is checked, click next
  12. Click Next for the Default folder name
  13. Choose create a standalone VMware vCenter Server Instance
  14. Ensure all the TCP Ports are okay, Adjust as needed (MS KB149605), Click next
  15. Click on Install

Install vCenter Update Manager

  1. Open the vCenter Installer
  2. Choose vCenter Update Manager from the Installer screen
  3. Choose OK for English
  4. Click Next on the Welcome Screen
  5. Choose I agree to the terms, click next
  6. Enter the user name and password for the vCenter Server system.
  7. Choose Use and existing support database, Choose vmupd for the DSN, click next
  8. Enter the password for vmupd, click next
  9. Leave defaults for Update Manger Ports, If needed choose Yes to Proxy Settings, else Click next
  10. Click next for default Directories (Ensure more the 20GB for Location for Downloading Patches)
  11. Click Install to complete

Install vCenter Converter

  1. Open the vCenter Installer
  2. Choose vCenter Converter from the Installer screen
  3. Choose OK for English
  4. Click Next on the Welcome Screen
  5. Choose I agree to the terms, click next
  6. Choose Typical, click next
  7. Enter username and password for vCenter Server connection, click next
  8. Click next for default ports
  9. Click next for default server ID
  10. Click Install

Install the vCenter Client

  1. Open the vCenter Installer
  2. Choose vCenter Client from the Installer screen
  3. Choose OK for English
  4. Click Next on the Welcome Screen
  5. Choose I agree to the terms, click next
  6. Enter your User and Organization Names, Enter your license Key, Click Next
  7. Click next on the Custom Setup windows, Choose install vsphere update utility if needed
  8. Click next for the default install folders
  9. Click install to finish

Well that’s it… I’m so glad I decided not to post up screen shots!

From here you should be able to bring up vCenter Server via the client, and with some minor configuration pull down updates too..

Good luck…

Introduction to vSphere 4 Link

Posted on Updated on

This link is well worth bookmarking and has been a great reference for me…

http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=welcome/welcome.html

Installing ESX 4.0 and vCenter 4.0 best practices

Posted on Updated on

This is one of my favorite references… I seem to need it from time to time… 

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009080

Installing ESX 4.0 and vCenter 4.0 best practices

Purpose

This article provides quick reference to the information needed for a trouble free installation of vSphere ESX 4.0 and vCenter Server 4.0.

Note: Because each environment is different, many installation decisions require knowledge and understanding beyond the scope of this article, consult the vSphere 4.0 document set for more detailed information regarding your installation at http://www.vmware.com/support/pubs/vs_pubs.html.

Resolution

Note: Read the VMware vSphere 4.0 Release Notes for known installation issues.

On the vCenter Server

1.Make sure your hardware and operating system requirements are compliant:

Note: For more information, see ESX and vCenter Server Installation Guide and VMware Infrastructure Compatibility Guide.

•Processor – 2 CPUs 2.0GHz or higher Intel or AMD x86 processors. Processor may be higher if the database runs on the same machine.

•Memory – 3GB RAM. RAM requirements may be higher if your database runs on the same machine.

•Disk storage – 2GB. Disk requirements may be higher if your database runs on the same machine.

•Microsoft SQL Server 2005 Express disk requirements. The bundled database requires up to 2GB free disk space to decompress the installation archive.

•Networking – 1Gbit recommended.

2.Make sure your database requirements and patch levels are compliant:

Note: For more information, see VMware Infrastructure Compatibility Guide and vCenter Server Database Patch and Configuration Requirements.

•Microsoft SQL server Database Support:

•Microsoft SQL Server 2005 Express

Note: Microsoft SQL Server 2005 Express is intended to be used for small deployments of up to 5 hosts and/or 50 virtual machines.

•Microsoft SQL Server 2005 Standard edition (SP1, SP2, SP3)

•Microsoft SQL Server 2005 Standard edition (SP2, SP3) 64bit

•Microsoft SQL Server 2005 Enterprise edition (SP1, SP2, SP3)

•Microsoft SQL Server 2005 Enterprise edition (SP2, SP3) 64bit

•Microsoft SQL Server 2008 Standard Edition

•Microsoft SQL Server 2008 Standard Edition 64bit

•Microsoft SQL Server 2008 Enterprise Edition

•Microsoft SQL Server 2008 Enterprise Edition 64bit

•Oracle Database Support:

•Oracle 10g Standard edition (Release 1 [10.1.0.3.0])

•Oracle 10g Enterprise edition (Release 1 [10.1.0.3.0])

•Oracle 10g Standard edition (Release 2 [10.2.0.1.0])

•Oracle 10g Enterprise edition (Release 2 [10.2.0.1.0])

•Oracle 10g Enterprise edition (Release 2 [10.2.0.1.0]) 64bit

•Oracle 11g Standard edition

•Oracle 11g Enterprise edition

3.Download and fill out the vCenter Server Installation Worksheet.

Note: For more information about the fields in this form, see the Required Data for Installing vCenter Server section of the ESX and vCenter Server Installation Guide.

4.The vCenter Server install wizard gives you the option to use the Windows system account or a user-specified account for the purpose of running vCenter Server.

The primary reason to use a user-specified account is to enable the use of Windows authentication for SQL Server.

If you choose this option:

•The user-specified account must be an Administrator on the local machine and act as part of the operating system and login as a service rights.

•You must specify the account name as DomainName\Username in the vCenter Server install wizard.

•You must configure the SQL Server database to allow the domain account access to SQL Server.

5.Make sure your system has all the software prerequisites for vCenter Server:

Note: For more information, see the vCenter Server Prerequisites section of the ESX and vCenter Server Installation Guide.

•Make sure your operating system meets the requirements:

Note: For more information, see the Operating System Compatibility for vSphere Client, vCenter Server, and VMware vCenter Update Manager section of the VMware Infrastructure Compatibility Guide.

•Windows XP Pro SP2 (SP2 required)

•Windows Server 2003, SP1 and SP2 32bit and 64bit all editions

•Windows Server 2003, R2 and SP2 32bit and 64bit all editions

•Windows Server 2008 32bit all editions

•Windows Server 2008 64bit Standard and Enterprise editions

•Make sure that the system you use for your vCenter Server installation belongs to a domain, rather than a workgroup.

•It is critical that you have reliable DNS and Time services.

•During the installation, the connection between the machine and the domain controller must be working.

•Log into the system using an account with local administrator rights. If joining another vCenter Server in Linked Mode, the account must be a local Administrator on both systems.

•The computer name cannot be more than 15 characters.

•Assign a static IP address and host name to the Windows server that will host the vCenter Server system. This IP address must have a valid (internal) DNS registration that resolves properly from all managed ESX hosts.

6.Configure your database prior to the vCenter install, unless you are using default Microsoft 2005 Express:

Note: Schema creation scripts mentioned in the documentation for both Microsoft SQL and Oracle are optional and intended for experienced Database Administrators. The vCenter Server installer performs the schema creation automatically if one does not already exist.

•Microsoft SQL Database:

•As the Database Administrator, use a script to create a local or remote Microsoft SQL Server Database.

Optionally, the database can be created as it was in vCenter 2.5 by using SQL Server Management Studio.

•Configure a SQL Server ODBC Connection

When you install the vCenter Server system, you can establish a connection with a SQL Server database.

•Configure Microsoft SQL Server TCP/IP for JDBC

If the Microsoft SQL Server database has TCP/IP disabled and the dynamic ports are not set, the JDBC connection remains closed. This causes the vCenter Server statistics to malfunction.

•Oracle Database:

•As the Database Administrator, use a script to create a local or remote Oracle database.

•Configure an Oracle Database User

If you plan to use an Oracle database when you install vCenter Server, you must configure the database user.

•Configure an Oracle Connection for Local Access or Configure an Oracle Connection for Remote Access depending on where the database is located.

•Connect to an Oracle Database Locally

7.VMware recommends using a separate database for vCenter Server and vCenter Update Manager.

8.Run the vCenter Server installer using the vCenter Server Installation Worksheet filled out in step 3.

On the ESX Server

1.Make sure your hardware is compliant on the Hardware Compatibility Guide.

This includes:

•System compatibility

•I/O compatibility (Network and HBA cards)

•Storage compatibility

•Backup software compatibility

2.VMware ESX 4.0 only installs and runs on servers with 64bit x86 CPUs. 32bit systems are no longer supported.

3.Make sure Intel VT is enabled in the host’s BIOS.

4.If you are installing to the local disks and SAN is connected to the ESX host, detach the fiber before continuing with the installation.

Note: Do not disable HBA cards in the BIOS.

5.The /, swap, and all the optional partitions are stored on a virtual disk called esxconsole-.vmdk. Set a size minimum of 8GB for this virtual disk.

Note: For /var/log, VMware recommends a separate partition to prevent unexpected disk space constraints due to extensive logging.