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.
Labels:

Comments

Post a Comment

Popular posts from this blog

Basic MPLS BGP and L3VPN Lab Setup

In this lab, we’ve set up a basic MPLS, BGP, and L3VPN environment, which is a great foundation for understanding how service providers build scalable networks. The lab uses the EVE-NG simulator along with Router IOS C7200-ADVENTERPRISEK9-M, Version 15.2(4)M8 to emulate a realistic MPLS environment. Below is a summary of the key components and roles of each router in the lab. MPLS Core Routers : The MPLS core consists of the routers responsible for label switching and forwarding customer traffic through the network: PE1 (Provider Edge 1) : Connects customer networks to the MPLS core and handles both MPLS and BGP routing. It also hosts VRF (Virtual Routing and Forwarding) instances for customers. PE2 (Provider Edge 2) : Functions similarly to PE1, connecting another customer network to the MPLS core. P1 (Core Router 1) and P2 (Core Router 2) : These routers serve as MPLS core routers and handle label switching but do not store or process customer routes directly. They simply f
Post a Comment
Read more

OSPF Adjacency Stuck in EXSTART on Cisco IOS XR – Issue and Solution

In a recent lab setup using Cisco IOS XR on EVE-NG, I faced a common but frustrating issue with OSPF adjacencies getting stuck in the EXSTART state. After spending considerable time troubleshooting interface MTUs and configurations, I discovered that the root cause was related to the virtual network interface type being used. This post outlines the issue, troubleshooting steps, and the eventual solution that got everything working. Issue: While configuring OSPF between two routers running Cisco IOS XR in my lab, OSPF adjacencies were getting stuck in the EXSTART state. I verified that interface configurations, MTU settings, and OSPF parameters were correct, but the problem persisted. I tried adjusting the MTU size, using the mtu-ignore command, and even checked for ACLs, but nothing seemed to resolve the issue. Troubleshooting Steps: MTU Settings: I started by verifying that both sides of the OSPF adjacency had matching MTUs. I used the default MTU and even tried different values wit
Post a Comment
Read more

How to Properly Clone an EVE-NG Lab with Configurations

Cloning labs in EVE-NG is a great way to duplicate setups and expand or experiment on a new copy without affecting the original lab. However, if not done correctly, the cloned lab may only copy the topology without configurations. In this guide, I’ll show you how to properly clone a lab in EVE-NG with all configurations using the EVE-NG GUI . Follow these steps to ensure that both the topology and router configurations are retained when cloning your lab. Steps to Clone an EVE-NG Lab with Configurations Save Running Configuration on All Devices In your original lab, make sure all devices have their configurations saved to NVRAM. Go into the CLI of each router and run the command: copy running-config startup-config Export All Configurations (CFGs) On the left sidebar in the EVE-NG Web UI , click on the "More Actions" option. Then select "Export all CFGs" . This step exports the configurations of all devices in the lab. Shutdown All Devices After exporting the confi
Post a Comment
Read more