Once the blade server is provisioned using the UCS manager and necessary configurations like service profile creation etc. is done. The next step is to configure and deploy blade server for various applications. Since the blade server is very attractive for virtualization based applications, in this document the VMWare ESXi installation is discussed. The concepts discussed here are also applicable to non-vmware based hypervisor and any other vendor's software application installation as well.
During this setup no physical keyboard, mouse or monitor was attached to the physical KVM port on the blade server. It should be noted that this document only discusses the installation using the UCS manager built-in software KVM switch. Although there could be various other ways to install the software on the blade server (for instance USB DVD based installation on the blade server).
BMC - Baseboad Management Controller
Baseboard Management Controller (BMC), also called as Service processor, resides on each blade for OS independent/pre-OS management. The BMC's focus is to monitor/manage a single blade in the UCS chassis. BMC should be assigned an IP address so that the UCS Manager's software KVM can connect to it using the IP. The UCS manager talks to the BMC and configures the blade. BMC controls things like BIOS (upgrade/downgrade), assigning MAC addresses, assigning WWNs, etc.
Using KVM Connection to Setup the Blade Server
Each physical blade is capable of supporing remote KVM and remote media access. This is made possible by associating IP addresses for the cut-through interfaces that correspond to each blade's BMC. Typically, these addresses are configured on the same subnet as the management IP address of the UCSM. This pool is created from the Admin tab, by selecting "Management IP Pool".
In our example, the ip address 10.194.40.208 is used to connect to the UCS Manager. And 10.194.40.33 is assigned to the " BMC Management IP Pool" so that UCSM can connect to blade server using KVM and will also be used for remtoe media access.
Notice that in our example we have only one IP address because we are configuring only one blade right now. So one ip address is required per blade server.
In the following screen it is shown that chassis-1/blade-1 is assigned the 10.194.40.33 IP address for remote KVM and virtual media access.
Following screen shows the IP address block that is allocated for BMC.
Now connect to blade server's software based KVM Console
This should open a new dialog box that will show the console screen of the blade server.
Now you can launch the virtual media from within the UCS Manager windows and can map vmvisor (ESXi4.0) iso image as virtual CD/DVD.
The macros are available to perform basic tasks as follows
You may also setup the boot oder on the blade server's BIOS
Now the blade should dedect the virtual CD/DVD and will start booting from it.
ESXi 4.0 installation will continue
The installation is done. Now the next step should be to assing a management ip address to the ESXi server itself so that you can access it individually or can add it to your vCenter Setup.
At this point, the VMWare EXSi 4.0 hypervisor (VMware-VMvisor-Installer-4i.0.0-164009.x86_64.iso) is installed on the UCS blade server and you can customize the vmware hypervisor with the IP address related information so you can connect to it using the vCenter and manage it from the vmwar vCenter clinet. Also right now no DataStore is created. So once you login to ESXi server, you can create data store either using iSCSI or SAN based data store or NAS.
So after that part is done, if your VLAN and network connectivity is in place, you should be able to connect/ping the 172.19.246.187.
Notice that there are two different ethernet networks here.
UCS Management Network:
10.194.x.x network (is used here in this setup to connect to UCS Manager and for KVM over IP purposes for the blade.This is out of band network and connect to the management port on the UCS fabric interconnect UCS-6120XP). The UCS Manager is the management application that is embedded inside the UCS-6120XP fabric interconnect switch.
VMWare Management Network:
172.19.246.x network (this is used to connect the vmware hypervisor using the in-band network so that it can be managed by the vCenter. This same network can be used for iSCSI traffic if needed but it is not recommended). So in our setup, the ESXi4 is running on the local hard drive on the blade server (ESXi 4 can also boot from the SAN itself but it is not covered in this document). Logically the vmware management traffic will be going through the UCS Chassis fabric extender to UCS fabric interconnect 6120XP switch. The 6120XP is connected to CAT6K 10GE port in this setup. Although the ethernet uplink could be Nexus 5K or Nexus 7K switch as well.
Unlike EPGs, the ESGs don't seem to respect multi-site contracts. An ESG at site 1 won't talk to an ESG at site 2 even with an allow all filter and contract between them.Has anyone found a way around this, like going through an l2/l3 out to go throu...
Hi all; I have two Cisco MDS-9148 and a lot of servers existing in same zone and not problem.Recently i would like add new zone with new others servers and HPE MSA-1050. Including the news servers in the new zone was successful but i can't still do w...
I have a nexus that when I log into the console it has a completely different hostname than what is set in the config. Where is this configuration stored or modifiable. Initially the prompt says TO-N7K:After I log in it says the actual hostname as th...
We have an ACI(Multipod) & F5 (ACT-STBY) setup in our environment build in Network centric mode. Some strange issue occurred in last migration, when we failover from Active to Standby and again back from Standby to Active F5 , it is seen that traffic ...