Skip to main content

Cisco UCS Mini - Add Extender Chassis

If you happen to own a UCS Mini Setup, a 5108 Chassis with two Fi 6324 or similar, and you are looking for documentation on how to add another 5108 Chassis with fabric extenders (2204XP in my case), then Cisco really does not have much out there, nor is there a lot of googlable information either (Everything you find is related to standalone Fabric Interconnects and "standard" UCS). Even after calling TAC, it took a while to get something, and what they told us was not even accurate. So here is how we did it, and it worked, came up without any interruption to current chassis, network, or running profiles.

Equipment

Of course we used our Cisco vendor to spec the equipment, but just for reference here is the list of what we had and what we added:

  • Original Setup
    • 5108 Chassis 
    • Fi 6324 (Qty 2)
    • Ports 1-2 for Fibre Channel, and 3-4 for Ethernet (MMF)
    • Connected to a stack of switches and pair of FC switches/SAN
    • Running UCS version 4.0.1 (Fairly recently upgraded as of May 2019)
  • Added Equipment
    • 5108 Chassis
    • 2204XP (Qty 2) Fabric Extenders
    • QSFP to 4SFP Breakuout cable (Qty 2)
    • Scalability Port Enablement License for existing Fi6324 (Qty 2) (Allows usage of the QSFP)

Procedure

This ended up being quite simple - it was the uncertainty of doing it in a way that would not impact anything that had us fumbling for documentation. In the end it is pretty painless and straight forward:

  1. Obtain the llicense file from Cisco, we had a PAK imported to the Cisco portal, then  generated Lic files with the FI Serial numbers
  2. Apply the licenses in UCS UI. 
    1. Admin, Licensing
    2. Fabric Interconnect A
    3. Click Download License, Choose the Lic file and off you go
    4. Click on Installed Licenses Tab, you should see the "SCAL_ETH_PORT_ACTIVATION_PKG" or similar with expiry Never
    5. Repeat for Fi B
  3. Rack your Chassis, install fabric extenders (And server blades if you have them).
  4. Wire up the extenders
    1. The QSFP (Scalability port 5) in Fabric A on primary chassis, to Port 1/2/3/4 on the extended chassis XP A (Left)
    2. The QSFP (Scalability port 5) in Fabric B on primary chassis, to Port 1/2/3/4 on the extended chassis XP B (Right)
  5. Plug in power to the extender chassis
  6. Bootup will take a while - give it 10 minutes
    1. In UCS UI, go to Equipment, Click on Fabric Interconnect A node
      1. Select the Physical Ports Tab
      2. Expand the Fixed Module and Scalability Port 5
      3. If these ports are showing As up and enabled you can skip the next step
      4. Right click on each of the 4 ports, one at the time, click "Configure as Server Port"
    2. Go to Equipment, Click on Fabric Interconnect B node
      1. Select the Physical Ports Tab
      2. Expand the Fixed Module and Scalability Port 5
      3. If these ports are showing As up and enabled you can skip the next step
      4. Right click on each of the 4 ports, one at the time, click "Configure as Server Port"
    3. If you did not have to manually configure the ports as server ports above, it may be related to the setting in Equipment, Policies, Port Auto-Discovery, Auto Configure Server port being set to enabled. This was not enabled in our system, and we left it as is and just enabled all the ports manually.
    4. As soon as the ports are enabled, Chassis 2 (extended) should start showing up. It may take quite some time before this is all set, as it performs Firmware upgrades on the fabric extenders and takes care of a lot of things, then does discovery - you will see several warnings and issues for a while till it is all done. Let it sit for an hour probably - after that, things should show up and hopefully be all error free.
    5. At the root of Equipment you should now see your second chassis and be good to go
As you can see, it is quite simple - i just posted this to help anyone having a hard time finding information like we did, not sure how many run Mini's, but can't be all that many.
Here is the simple diagram of how the wiring was done with ethe QSFP Breakouts.













Labels:

Comments

Post a Comment

Popular posts from this blog

Removing Domain - Office 365 / Azure AD Tenant

Recently I had an interesting experience and challenge, removing a domain from an Azure AD (Office 365) Tenant which had been around for years, switching all the users to another domain for logins/UPN. A normal procedure for this should be simple: Change UPN for all users and groups Change any associated apps, email, and other resources Remove Domain (This can be done from Azure Portal, or from Office 365 Admin). The issue for me was that there was resources associated with some users, which I could not find what recourses or how to clear it up. In Azure Portal, Azure AD, Custom Domains - it would not let me delete at all, just showed me a link to the list of users in violation. In office 365 Admin, Settings, Domains - I was able to initiate a Delete action, once, with a supposed automatic removal action. After several hours this failed, and it now remained in a failed state that did not let me try again from UI. So I started digging with PowerShell - I found it most usable with the MS
Post a Comment
Read more

Active Directory Account Lockout - Narrowing Down the source

If you are in a all-windows shop where everything is nice and neat, everybody has a proper domain membership and all authentication is SSO or Windows Integrated, then you probably do not have much of a problem with repeated account lockouts. On the other hand, if you are in a mixed environment, lots of :Linux, Mac, and unmanaged Wintendo, then you probably run into some users that manage to Lock themselves out frequently - typically for several days in a row after the account password had been changed. Reasons can be plenty fold - typically saved credentials somewhere, like a git client, sql-server client, email client, rdp-manager, smbfs-automount, or anything that tries a bunch of logins when you start it up, or keeps trying in the background. As a sysadmin, you don't have time to narrow it down for the end user - but they will be adamant it is not their fault, so you probably need to prove that "Yes it is" - so I use powershell to grab 4740 events from Domain Con
Post a Comment
Read more