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

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.

Authoritative DNS Servers Delegation and Internal DNS Explained

DNS (Domain Name System) plays a critical role in how users and systems find resources on the internet or within internal networks. Whether it's managing an internal domain in an enterprise or delegating parts of a domain for traffic distribution, DNS setups vary widely depending on needs. In this blog post, we’ll break down the different types of DNS setups, including authoritative DNS servers, DNS delegation, and how internal DNS functions within organizations. 1. Authoritative DNS Server An Authoritative DNS server is the final source of truth for a specific domain. When someone queries a domain (e.g., example.com ), the authoritative DNS server for that domain holds the DNS records (A records, CNAME, MX, etc.) and responds with the corresponding IP address. Key Points: Who can host it? Authoritative DNS servers are often hosted by domain registrars (e.g., GoDaddy, Namecheap) or cloud DNS providers (e.g., AWS Route 53, Cloudflare). However, organizations can also host their ...

BGP MED: Managing Inbound Traffic with Multi-Exit Discriminator

The Multi-Exit Discriminator (MED) is used in BGP to control inbound traffic into your AS. It tells a neighboring AS which entry point into your network it should prefer when there are multiple links between your AS and the neighboring AS. The lower the MED value , the more preferred the path. MED is only honored between the same neighboring AS . Example Scenario : You are connected to ISP1 via two routers, CE1 and CE2 , and want to control which router ISP1 uses to send traffic into your AS. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP1): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE1 (Lower MED, More Preferred) : Create a route map to set the MED to 50 for CE1: route-map SET_MED permit 10 set metric 50 Apply this route map to the neighbor in the BGP configuration for CE1: router bgp 65001 neighbor 10.0.1.1 remote-as 65000 neighbor 10.0.1.1 route-map SET_MED out Configuratio...