Skip to main content

Steps to install RAM and NIC Cisco UCS Server

It is always very easy to install additional hardware components to Cisco UCS blade or Rack servers in non-production environment. If you have to add something to Cisco UCS blade or Rack server in your company’s data center or in customer production environments then you are given a small time window to perform your activity and resume the Server or compute infrastructure in production. In this case you have to put extra efforts and create method of procedure MOP, to avoid any delay and surprises during your Change Request CR window and complete the task before the end of the CR window.
Writing this post to save your time if you are going to install additional hardware components e.g Memory RAM/DIMM, Network interface cards, NICs, or VIC, hard drives etc. You got to plan it well, otherwise you may stuck with troubleshooting and run out of time in CR window time.
Before installing the new hardware components, make sure the new hardware is compatible with your blade/rack server, supported by your current UCS firmware version, and there are no open bugs of that new hardware component in the installed UCS firmware version
After confirming above points, follow below steps to install new hardware.
  1. Dissociate service profile from Server
  2. Decommission the same server
  3. In case of  rack server, remove the power cords from Server and all fibre/copper network connections
  4. Pull out the Server and open the top cover
  5. Install new hardware components
  6. Put back the server in the same slot, if blade.
  7. Re-commission the Server
  8. Associate same Service profile to the server.

Comments

Popular posts from this blog

What is Cisco Supervisor Engine?

Supervisor Engine is a module that is installed in the Cisco Chassis-based Catalyst Switches or Routers. Supervisor engine contains nearly all the same components of a fixed Cisco Switches or Routers. These Supervisor engines come in a variety of different types with different functionalities and are installed in the Switches/Router Chassis as per requirements of the network types.

Benefits of Supervisor Engines
By installing Latest Supervisor Engines in your existing investments (Switches and Routers) you can scale system performance and integrate next-generation services into your Networks.
Within a single multilayer switch chassis, two supervisor modules with integrated route processors can be used to provide hardware redundancy. If an entire supervisor module fails, the other module can pick up the pieces and continue operating the switch.
The supervisor engine contains the following integrated daughter cards that perform forwarding and routing and provide the protocols supported …

GNS3 Docker Error while creating node: Docker has returned an error: Cannot connect to host docker:80

Error while creating node: Docker has returned an error: Cannot connect to host docker:80 ssl:False [No such file or directory]

After adding docker template for Alpine Linux in gns3, you get above mentioned message when you want to use alpine linux in GNS3.

To get rid of this message you have to install Docker by following below link
curl -fsSL https://get.docker.com/ | sh

If you do not have curl installed then instal curl first with below command.apt-get install curl
After installing Docker you need to add your user name in the docker group with the following command. $ sudo usermod -aG docker your_username

Verify if the docker service is started with following command$ service docker status
If docker is not started then start with following command $ sudo service docker start
Logout from GNS3 Virtual Machines and log back. Start gns3 and use alpine linux.

a file I/O error has occurred while accessing vmware converter

While converting physical Windows 7 machine to Virtual machine of infrastructure type, I got this error. The error seems it is unable to read/write source or destination datastore.

I have installed VMware-converter-en-6.2.0-8466193 on Windows 7 physical machine with option locally selected. (not at server/client option)

All of my ESXi servers are connected to the vCenter Server, so I had to use vCenter Server's IP address to send this physical machine to the virtual world.

The issue i found was with the dns resolution to the vCenter Server's hostname. Since I am not using the same dns server on the Windows 7 client machine. So I updated the host entries manually for the vCenter Server's hosname to it IP address.

After adding dns eteries to the hostfile of windows 7, I am not getting this "a file I/O error has occurred while accessing vmware converter" and the migration has started.