Server Blade ASYNC / threshold of passage / hardware verification

Similar Questions

• Reference Dell R310 Server Blade not start CD ROM [FRESH WINDOWS SETUP]

  Hello

  I have a Server Blade Dell R310. I created the virtual disk on a Raid Configuration, also I updated the BIOS boot.

  I PERC S100 when I checked on my configuration tab.

  The scenario is that I want to install a new / new copy of Windows 2008 R2 on this server, I have the dvd bootable. but when I put it on the drive it says "No Bootable Media found" something like that.

  Y at - it all the configurations that I missed? hoping to get answers from here.

  Kind regards!

  OK, let's back up a bit:

  Use the management tools of systems and Documentation (GDPS) instead of SBUU.  If you use SBUU with 2008R2, you should use the Driver Pack too... MUCH easier to use the GDPS, which has everything you need in there:

  FTP (you will need to copy/paste - forums do not like the FTP links):

  FTP://FTP.Dell.com/secure/FOLDER01538030M/1/OM_SMTD_730_A00.ISO

  Yes, you start on GDPS, follow the instructions, and then insert the 2008R2 media when prompted.

• IP address of server blades management

  Hello

  Could someone please help me know which path is followed to reach the ip addresses of the server blade chassis management? To be more precise, to say that I have the management interfaces of interconnections connected to the switch network management of my fabric. When I ping addresses it ip of the blades, that ping through the management interface of the FIs management? Can I assign different subnet IP subnet Management Server as the FI management interfaces?

  Also, could someone share a document illustrating this architecture?

  Thank you

  Quesnel

  Hi Quesnel

  Let's be very clear: IP address management blade = IP address of the MMIC, you can for example. access by the KVM.

  There are 2 modes:

  - out of band which is accessible on port 1 G of the interconnection of fabric management

  - in the band which is accessible via a fabric interconnect 10 G uplink interface

  See the discussion in

  https://supportforums.Cisco.com/discussion/12185011/management-blades-OU...

  Management in-band MMIC

  A determinant to provide access management in-band for integrated management Cisco (CIMC) controller is the desire to separate traffic treated tenant provider cloud for service provider deployments shared, public or private. Out of band (OOB) management traffic is at the fabric of interconnections and cross management via the management port. This has the potential to cause bottlenecks and affect the bandwidth of the processor in the management ports.

  In-band management allows MMIC traffic to take the same path as the data traffic into and out of the fabric of interconnections via the uplink ports. The highest bandwidth available to the uplink ports means that inband access greatly accelerates the management traffic and reduced risk of bottlenecks and the stress of CPU. When out of band (OOB) and inband address pools can be configured for access to the administration in Cisco's UCS Manager. Out-of-band access only supports IPv4 addresses. Access inband supports IPv4 addresses and IPv6, which allows a management single or double stack.

  The two addresses of OOB management interface that can be configured in Cisco UCS Manager blade and rack servers are:

  • An OOB IPv4 address assigned to the physical server via the pool global ext-mgmt
  • An address IPv4 OOB derived from a service associated with the physical server profile

  In addition, up to four inband management interface addresses can be configured:

  • A tape attributed to the physical server IPv4 address
  • An IPv4 address of inband derived from a service associated with the physical server profile
  • An IPv6 address band attributed to the physical server
  • An IPv6 address of inband derived from a service associated with the physical server profile

  Several in-band for each server management IP addresses take additional sessions of CIMC. When you configure the OOB, and strip addresses, users can choose from a list of these addresses in the KVM Console dialog box when they launch KVM from a server, SSH to the ground, a service profile, the KVM Launch Manager or Cisco UCS Manager GUI web URL.

  MMIC inband access supports the following services:

  • KVM console

  • SSH to MMIC for soil

  • vMedia of ISO, virtual CD/DVD, removable disk, floppy drive

  Note	Only Cisco UCS M3 and M4 servers support access in-band MMIC. Access Inband MMIC for Cisco UCS M1 and M2 servers is not supported.

• Physically, move a server blade in a different location - best practices?

  Hello

  Is there a best practice to move a physical blade to another location?  I can't find a document about it.

  We want to move a slide to another location due to keep grouped similar environments but do not want to disassociate the profile.

  Can we just unassign, and then take it out and put in another location and let it automatically reactivate.  The profile will remain with the server?

  You say - associate profile and then re - associate profile again?

  Thank you

  A

  Hi Adrien,.

  Thank you for poining, I guess I wrote too soon.

  Yes it takes the decomission.

  Here are the steps to update:

  (1) shut down the operating system on the blade,

  (2) Disassocite the service profile, wait dissociate it in full (check the status on the WSF of the blade tab)

  (3) Decomission the blade of the UCSM (check the status on the tab of the WSF for the process)

  (4) to remove the blade from the current location,

  (5) move the blade into the slot again.

  (6) wait for blade to discover fully (even once, check the condition of the WSF of the blade tab), you may be required to validate / recognize the slot to accept the blade and trigger the discovery.

  7) once discovered associated with the profile back

  (8) start the dos operating system.

  I would check the documents and let you know.

  . / Afonso

• Server Blade B200M2 showing an amber light

  Hello

  I am faceing question in one of our Cisco UCS B200 M2 Blade Server, is to show the orange light.

  We have a chassis with 4 servers B200 M2 all other servers are working properly, but the server which is present in 3 Bay gives seeing orange.

  Until now, we bypass them and made the firmware updated, tested with the service profile, work tryied in the Bay of different, changed map of CNA.

  But no results, after that we are thinging of the motherboard number the server is 2 months and under no mandate. waiting for the solution

  Thanks in advance

  Thank you

  Sunil

  Sunil,

  The fluctuation of power may be due to a defective mother board and voltage sensor.  I suggest you open the TAC proof and they may decide to replace the blade (mainboard only) for you.

  Connect to the UCSM CLI using telnet or SSH and enable logging with your SSH client to capture output following

  (Where X = chassis # and Y = blade #)

  UCS-250-A # login local-mgmt

  UCS-A(local-Mgmt) # show the chassis support Mmic X Y

  Output UCS-A(local-Mgmt) #.

  UCS-250-A # connect Mmic X / Y

  [help] # sensors power

  Fix spacewalks on the TAC case when you open for a quicker resolution.

  Kind regards

  Robert

• Manually add a new vLan to the server blade in Cisco UCS 5108

  Hello

  I tried to add a new vLan to my chassie of server and then add the manulay on the blad server. The problem is that I can´t to connect to the network, what I introduced it in fabric switch? Anyone got a tip where to start troubleshooting?

  / T

  Hello

  You need SSH interconnection fabric (FI) and then change in context nxos

  Padma

• SERVER BLADE with 96 GB of RAM

  I have a server balde with 2 processors and 96 GB of physical RAM installed.

  Having the license for "VMware vSphere 5 Standard for 1 processor (with 32 GB vRAM) right by processor"

  According to my understanding vSphere 5, there is no limitation on phyiscal RAM and processor.

  limitation to a virtual machine is the maximum that we can assign 32GB vRAM.

  Please confirm if this is correct.

  Read the white paper of the licenses at http://www.vmware.com/files/pdf/vsphere_pricing.pdf

  manu101914 wrote:

  I have a server balde with 2 processors and 96 GB of physical RAM installed.

  Having the license for "VMware vSphere 5 Standard for 1 processor (with 32 GB vRAM) right by processor"

  According to my understanding vSphere 5, there is no limitation on phyiscal RAM & CPU.

  The license is per-SOCKET on the blade, but not on CARROTS by socket which is now unlimited.  Since you have 2 jacks, you will need a minimum of 2 licenses.  With your evidence of 32 GB per socket, you can be powered with a total of 64 GB memory configured, regardless of the amount of memory they use in fact virtual machines.

  You can either purchase a 3rd license then you can connect virtual machines with a total of 96 GB of memory configured, or you can update your licenses to the company that will give you a total allocation of 128 GB.  Note that this is the CONFIGURED memory, not the USED memory, so it is very likely that you will need licenses that go beyond the 96 GB.

  Also note that the memory is pooled - if you have several other servers also running vSphere 5 Standard, then he the the sum of all virtual machines running on all hosts in the operating mode that count.

• I'm not sure how to make it work. 2 guests, 2 virtual machines, trying to keep the traffic on the Server Blade.

  I have two blades on the same chassis running ESXi 4.1, each has an Exchange Server on it. Im trying to keep the traffic between the two Exchange boxes contained between the two. I thought that I could put in the same vSwtich, but looks like I need vDS for this. I don't have this license level.

  Now, I found myself with two separate vSwitches with the same label. network, it shows them on the same vSwitch so they don't transmit traffic. because they are separate switches... my vSphere networking missing a bit... need to study more.

  Since you have virtual machines on different blades that the traffic between the two will have to cross a physical network card.   If you need to segment this traffic, you can configure a VLAN in your network, add a new group of port on each host to ESXi virtual machine and then set up a NIC in the virtual machines to use this group of VIRTUAL LAN port.

  Though the virtual machines on the same host (always) you can configure a single vSwitch.   In this case the traffic between virtual machines would not hit the physical network and you wouldn't need even a physical NETWORK adapter, attached to the vSwitch.

  Dave
  VMware communities user moderator

  ESXi Essentials free training / eBook offer

  Now available - VMware ESXi: planning, implementation, and security

  Also available - vSphere Quick Start Guide

• GUI for OEL6 Server Blade

  Hello
  
  I installed OEL6 on VM to the blade server. We use Citrix for virtualization. Problem is that since the installation is done on the server without any VGA monitor card attached so Linux got installed without GUI. Now I need to install the Oracle database on this virtual machine. I believe that X-Window is necessary at least. I installed X Windows System and the Gnome desktop environment. Now when I run gdmsetup it does not work. I installed tigervnc on the server and updated the iptables for also made of changes in the gdm configuration file, but when I try to connect from my computer Windows XP using Tightvncviewer error, it throws firewall rules. "Unable to RRs data socket. My windows Firewall is disabled. I disabled the firewall and SELinux on the server, but that did not help either.
  
  I just need to be able to access the linux VM since my machine windows in graphical mode. I, therefore, ask you to help me set up.
  
  Note: The startx command server throws this error.
  

  Build Date: 07 March 2012  04:10:46PM
  Build ID: xorg-x11-server 1.10.4-6.el6_2.3 
  Current version of pixman: 0.18.4
  Before reporting problems, check https://www.redhat.com/apps/support/
  to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jun  1 23:42:07 2012
  (==) Using default built-in configuration (21 lines)
  (EE) open /dev/fb0: No such device
  (EE) No devices detected.
  
  Fatal server error:
  no screens found
  
  Please consult the Red Hat, Inc. support 
   at https://www.redhat.com/apps/support/
   for help. 
  Please also check the log file at "/var/log/Xorg.0.log" for additional information.
  
  giving up.
  xinit:  No such file or directory (errno 2):  unable to connect to X server
  xinit:  No such process (errno 3):  Server error.

  Xorg.0.log file contains the following information
  

  [ 33282.906]
  X.Org X Server 1.10.4
  Release Date: 2011-08-19
  [ 33282.906] X Protocol Version 11, Revision 0
  [ 33282.907] Build Operating System: ca-build44 2.6.31.5-127.fc12.x86_64
  [ 33282.907] Current Operating System: Linux aud-devdbs-01.adcci.gov.ae 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64
  [ 33282.907] Kernel command line: ro root=/dev/mapper/VolGroup-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD console=hvc0  KEYTABLE=us rd_LVM_LV=VolGroup/lv_swap SYSFONT=latarcyrheb-sun16 rhgb crashkernel=129M@0M quiet rd_LVM_LV=VolGroup/lv_root rd_NO_DM  graphical utf8
  [ 33282.907] Build Date: 07 March 2012  04:10:46PM
  [ 33282.907] Build ID: xorg-x11-server 1.10.4-6.el6_2.3
  [ 33282.907] Current version of pixman: 0.18.4
  [ 33282.907]    Before reporting problems, check https://www.redhat.com/apps/support/
   to make sure that you have the latest version.
  [ 33282.907] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [ 33282.908] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jun  1 23:42:07 2012
  [ 33282.908] (II) Loader magic: 0x7d6d20
  "Xorg.0.log" 146L, 7594C
  [ 33282.908] (II) Loader magic: 0x7d6d20
  [ 33282.908] (II) Module ABI versions:
  [ 33282.908]    X.Org ANSI C Emulation: 0.4
  [ 33282.908]    X.Org Video Driver: 10.0
  [ 33282.908]    X.Org XInput driver : 12.2
  [ 33282.908]    X.Org Server Extension : 5.0
  [ 33282.909] (==) Using default built-in configuration (21 lines)
  [ 33282.909] (==) --- Start of built-in configuration ---
  [ 33282.909]    Section "Device"
  [ 33282.909] Identifier      "Builtin Default vesa Device 0"
  [ 33282.909] Driver  "vesa"
  [ 33282.909]    EndSection
  [ 33282.909]    Section "Screen"
  [ 33282.909] Identifier      "Builtin Default vesa Screen 0"
  [ 33282.909] Device  "Builtin Default vesa Device 0"
  [ 33282.909]    EndSection
  [ 33282.909]    Section "Device"
  [ 33282.909] Identifier      "Builtin Default fbdev Device 0"
  [ 33282.909] Driver  "fbdev"
  [ 33282.909]    EndSection
  [ 33282.909]    Section "Screen"
  [ 33282.909] Identifier      "Builtin Default fbdev Screen 0"
  [ 33282.909] Device  "Builtin Default fbdev Device 0"
  [ 33282.909] Device  "Builtin Default fbdev Device 0"
  [ 33282.909]    EndSection
  [ 33282.909]    Section "ServerLayout"
  [ 33282.909] Identifier      "Builtin Default Layout"
  [ 33282.910] Screen  "Builtin Default vesa Screen 0"
  [ 33282.910] Screen  "Builtin Default fbdev Screen 0"
  [ 33282.910]    EndSection
  [ 33282.910] (==) --- End of built-in configuration ---
  [ 33282.910] (==) ServerLayout "Builtin Default Layout"
  [ 33282.910] (**) |-->Screen "Builtin Default vesa Screen 0" (0)
  [ 33282.910] (**) |   |-->Monitor "<default monitor>"
  [ 33282.910] (**) |   |-->Device "Builtin Default vesa Device 0"
  [ 33282.910] (==) No monitor specified for screen "Builtin Default vesa Screen 0".
   Using a default monitor configuration.
  [ 33282.911] (**) |-->Screen "Builtin Default fbdev Screen 0" (1)
  [ 33282.911] (**) |   |-->Monitor "<default monitor>"
  [ 33282.911] (**) |   |-->Device "Builtin Default fbdev Device 0"
  [ 33282.911] (==) No monitor specified for screen "Builtin Default fbdev Screen 0".
   Using a default monitor configuration.
  [ 33282.911] (==) Automatically adding devices
  [ 33282.911] (==) Automatically enabling devices
  [ 33282.911] (==) FontPath set to:
   catalogue:/etc/X11/fontpath.d,
   built-ins
  [ 33282.911] (==) ModulePath set to "/usr/lib64/xorg/modules"
  [ 33282.911] (II) The server relies on HAL to provide the list of input devices.
   If no devices become available, reconfigure HAL or disable AutoAddDevices.
  [ 33282.911] (II) LoadModule: "extmod"
  [ 33282.912] (II) Loading /usr/lib64/xorg/modules/extensions/libextmod.so
  [ 33282.914] (II) Module extmod: vendor="X.Org Foundation"
  [ 33282.914]    compiled for 1.10.4, module version = 1.0.0
  [ 33282.914]    Module class: X.Org Server Extension
  [ 33282.914]    ABI class: X.Org Server Extension, version 5.0
  [ 33282.914] (II) Loading extension SELinux
  [ 33282.914] (II) Loading extension MIT-SCREEN-SAVER
  [ 33282.914] (II) Loading extension XFree86-VidModeExtension
  [ 33282.914] (II) Loading extension XFree86-DGA
  [ 33282.914] (II) Loading extension DPMS
  [ 33282.914] (II) Loading extension XVideo
  [ 33282.914] (II) Loading extension XVideo-MotionCompensation
  [ 33282.914] (II) Loading extension X-Resource
  [ 33282.914] (II) LoadModule: "dbe"
  [ 33282.915] (II) Loading /usr/lib64/xorg/modules/extensions/libdbe.so
  [ 33282.915] (II) Module dbe: vendor="X.Org Foundation"
  [ 33282.915]    compiled for 1.10.4, module version = 1.0.0
  [ 33282.915]    Module class: X.Org Server Extension
  [ 33282.915]    ABI class: X.Org Server Extension, version 5.0
  [ 33282.915] (II) Loading extension DOUBLE-BUFFER
  [ 33282.915] (II) LoadModule: "glx"
  [ 33282.915] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
  [ 33282.916] (II) Module glx: vendor="X.Org Foundation"
  [ 33282.916]    compiled for 1.10.4, module version = 1.0.0
  [ 33282.916]    ABI class: X.Org Server Extension, version 5.0
  [ 33282.916] (==) AIGLX enabled
  [ 33282.916] (II) Loading extension GLX
  [ 33282.916] (II) LoadModule: "record"
  [ 33282.917] (II) Loading /usr/lib64/xorg/modules/extensions/librecord.so
  [ 33282.917] (II) Module record: vendor="X.Org Foundation"
  [ 33282.917]    compiled for 1.10.4, module version = 1.13.0
  [ 33282.917]    Module class: X.Org Server Extension
  [ 33282.917]    ABI class: X.Org Server Extension, version 5.0
  [ 33282.917] (II) Loading extension RECORD
  [ 33282.917] (II) LoadModule: "dri"
  [ 33282.918] (II) Loading /usr/lib64/xorg/modules/extensions/libdri.so
  [ 33282.918] (II) Module dri: vendor="X.Org Foundation"
  [ 33282.919]    compiled for 1.10.4, module version = 1.0.0
  [ 33282.919]    ABI class: X.Org Server Extension, version 5.0
  [ 33282.919] (II) Loading extension XFree86-DRI
  [ 33282.919] (II) LoadModule: "dri2"
  [ 33282.919] (II) Loading /usr/lib64/xorg/modules/extensions/libdri2.so
  [ 33282.919] (II) Module dri2: vendor="X.Org Foundation"
  [ 33282.919]    compiled for 1.10.4, module version = 1.2.0
  [ 33282.919]    ABI class: X.Org Server Extension, version 5.0
  [ 33282.920] (II) Loading extension DRI2
  [ 33282.920] (II) LoadModule: "vesa"
  [ 33282.920] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
  [ 33282.921] (II) Module vesa: vendor="X.Org Foundation"
  [ 33282.921]    compiled for 1.10.4, module version = 2.3.0
  [ 33282.921]    Module class: X.Org Video Driver
  [ 33282.921]    ABI class: X.Org Video Driver, version 10.0
  [ 33282.921] (II) LoadModule: "fbdev"
  [ 33282.922] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
  [ 33282.922] (II) Module fbdev: vendor="X.Org Foundation"
  [ 33282.922]    compiled for 1.10.4, module version = 0.4.2
  [ 33282.922]    ABI class: X.Org Video Driver, version 10.0
  [ 33282.922] (II) VESA: driver for VESA chipsets: vesa
  [ 33282.922] (II) FBDEV: driver for framebuffer: fbdev
  [ 33282.922] (--) using VT number 7
  
  [ 33282.923] (WW) Falling back to old probe method for vesa
  [ 33282.923] (WW) Falling back to old probe method for fbdev
  [ 33282.923] (II) Loading sub module "fbdevhw"
  [ 33282.924] (II) LoadModule: "fbdevhw"
  [ 33282.925] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
  [ 33282.925] (II) Module fbdevhw: vendor="X.Org Foundation"
  [ 33282.925]    compiled for 1.10.4, module version = 0.0.2
  [ 33282.925]    ABI class: X.Org Video Driver, version 10.0
  [ 33282.932] (EE) open /dev/fb0: No such device
  [ 33282.932] (EE) No devices detected.
  [ 33282.932]
  Fatal server error:
  [ 33282.932] no screens found
  [ 33282.932]
  Please consult the Red Hat, Inc. support
   at https://www.redhat.com/apps/support/
   for help.
  [ 33282.932] Please also check the log file at "/var/log/Xorg.0.log" for additional information.

  I'm sorry if you find my silly post since I'm new to Linux and still learning.
  
  Published by: 938187 on June 1, 2012 12:49
  
  Published by: 938187 on June 1, 2012 12:56

  Maybe you try more. What happens if you use ' xclock - norender "?

• M1000e inadmissible after update BIOS of Server Blade M630

  Nice day

  I'm in a bit of a pickle. I recently downloaded BIOS and updated Power Edge M630 and realized that I did not follow the recommended order of updates. The M1000e should be updated 1. Now, the CMC is inadmissible.

  Any ideas where I should start troubleshooting. Can delete the update of the BIOS?

  Can you pull the blade, the CMC update and then reinsert the blade? You can save the BIOS flash, but it's something we want to try to avoid.

• Hard to reformat the disks on the Server Blade

  We just installed a blade with 4 servers M620 m1000E chassis.  I'm looking at a variety of new Virtualization options.  One product claims a previous installation has failed and the obvious solution is to format the drive (mirrored 136 15K SAS) and reinstall.  The problem is, I have not met this before, and I am really uncertain how can I achieve this.  The installer doesn't have an option to reformat before you install it.

  If anyone has a suggestion, or can point me in a direction I would be very happy.

  Darwin

  56Nine,

  What you would do is access to the controller on the M620 via the Control Panel, and then select device settings, then the Raid Controller in question. From there select Virtual Disk Mgmt and virtual disk operations. You will see the choice between fast, slow to boot initialization and check the consistency. Select the fast initialization and start again. Now a reminder, this will delete all data on the disks, so if these data are necessary Please save the first.

  Let me know how it goes.

• Assign the profile to a server blade using script

  I had a UCS workshop this morning with one of my clients, and he asked me if there is a way to develop a script to remove the profle of one of the blades and re - assign a different profile for the same lame.

  Thanks for your input in advance!

  Should be possible.

  Take a look at some of the scripts available on the Cisco Developer Network site, using the API of the UCS:

  Examples (logon may be required to download):

  UCS (goUCS) automation tool

  Cisco UCS PowerTool for UCSM

  Thank you

  Michael

• Run OEM Windows Server on hypervisor on the same hardware?

  (1) get physical server which includes licensed OEM for Windows Server.

  (2) wipe the drive and install a hypervisor, such as the independent (free) version of Hyper-V

  (3) install copy OEM of Windows Server on the virtual machine running on the hypervisor

  Is this legal, in what concerns MS licenses, and there will be problems with activation? I have scoured the internet looking for the answer and have determined that it is absolutely not possible. And I also determined that it is absolutely possible. In fact, nobody seems to know for sure. Everyone here knows for sure?

  Yes, you can, and Dell tells you how (licenses are different for 2003, so this applies to the 2008 and subsequent versions).  You can even install OEM 2008 on the physical server, and then install it as a virtual server, as long as the physical instance is only used to manage the virtual instance (Hyper-V), the Hyper-V hypervisor or other free/independent is not necessary.  Each edition (Standard, Enterprise, etc.) is a license for a different number of virtual instances.

  content.dell.com/.../Documents~virtual-machines-oem-media.pdf.aspx

  www.dell.com/.../WS08_Media_VM_Final.pdf

  www.Microsoft.com/.../confirmation.aspx

• Server Blade asking reboot or insertion of media.

  We have suffered the loss of power and are now problems bringing our servers online. What is the best path to take when the server asks me to restart or insert media? Thanks for any help!

  Hello

  It seems that you start from the SAN and your coming UCS before storage or SAN. Just restart the servers still once, after you make sure that your storage and san work well.

  If anything I have said not to make sense to you, please check your configuration of startup strategy.

  http://www.Cisco.com/en/us/docs/unified_computing/UCS/SW/GUI/config/Guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_011101.html#task_1F7624A2A07B48459AB57B9593D98E84

  Richard

• Can the ESXI 5.0 and Vmware View coexist on the same server blade

  Hi team, sorry for the basic question, but can I install the ESXI and Vmware View on the same server?

  Kind regards

  Ismail

  VMware view installs inside a server operating system and he can definitley be installed inside a server running on top of vSphere.