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.

SSL VPN vs IPSec VPN: Understanding the Key Differences

When it comes to securing communication over the internet, Virtual Private Networks (VPNs) are a cornerstone of modern networking. Two popular types of VPNs are SSL VPN and IPSec VPN . While both serve to encrypt and secure data, they differ significantly in terms of technology, use cases, and implementation. This blog post will help you understand these differences and choose the right solution for your needs. What is SSL VPN? An SSL VPN uses the Secure Sockets Layer (SSL) or its successor, Transport Layer Security (TLS) , to create a secure connection. It operates at the Application Layer (Layer 7) of the OSI model and is designed to provide secure access to specific resources over the internet. Key Features of SSL VPN: Ease of Use: Accessible via a standard web browser without the need for dedicated client software. Granular Access Control: Allows users to access specific applications or resources rather than the entire network. Port Usage: Uses TCP port 443, which is rarely...

AS Path Prepending: Controlling Inbound Traffic in BGP

AS Path Prepending is a BGP feature used to make a specific path appear less preferred by artificially lengthening the AS path. This is done by adding your AS number multiple times to the AS path. It is a common method to influence inbound traffic from external networks. Longer AS Path = Less preferred route . Example Scenario : You have two ISPs: ISP1 (through CE1) and ISP2 (through CE2). You want inbound traffic from the internet to prefer ISP1 over ISP2. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP2): 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 CE2 (AS Path Prepending to Make ISP2 Less Preferred) : Create a route map to prepend your AS path multiple times for CE2: route-map PREPEND_AS permit 10 set as-path prepend 65001 65001 65001 Apply this route map to the neighbor in the BGP configuration for CE2: router bgp 65001 neighbor 10.0.2.1 remote-as 65002 neighbor 10.0.2.1 ro...