9.12.2014

UCS Central Upgrade: 1.2(1a)

After downloading the appropriate .iso file for your UCS Central upgrade (the most current version is 1.2(1a)), map it to your server, and reboot.


Some details you need to consider from the Upgrade Guide:
-You can only upgrade to 1.2(1a) from either 1.1(1b) or 1.1(2a)
--Clear the browser cache after logging into the UCS Central web interface
-You must upgrade from 1.1 to 1.2 versions in standalone mode (cluster mode can be enabled from the loca-mgmt CLI level)
-You can only use the ISO image upgrade (Provider Bundle is not longer in use)
-UCS Central 1.2 supports UCSM 2.1(x), 2.2(x) and 3.0.  Upgrade UCSM BEFORE UCS Central, or deal with mismatched version faults and missed updates on UCSM side
-Be aware that once you upgrade, you cannot downgrade :]


Source: http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-central/install-upgrade/1-2/b_UCSC_Install_and_Upgrade_Guide_1-2/b_UCSC_Install_and_Upgrade_Guide_1-2_chapter_0110.html#concept_B130CCED6E5F400A872CA19557D8A2CF

Again we are presented with the option to install or upgrade, as was seen in the Installation post.  This time we are going to elect to "Upgrade existing Cisco UCS Central".



Let's move on to configuring this bad boy...

UCS Central Installation: 1.1(2a)

Documenting the UCS Central installation of 1.1(2a) (so I can afterwards document the upgrade procedure to 1.2(1a)).  I elected to install UCS Central via the .iso onto a standalone rackmount server.  The installation guide suggests installing UCS Central on a VM, but I have a spare server that I can dedicate for this purpose.




Whoops... I had not logged into the server in some time, so ensure that you have the appropriate drive configuration set up.  Go ahead and take a look at the installation prerequisites before you begin:
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-central/install-upgrade/1-1/b_UCSC_Installation_and_Upgrade_Guide_11/b_UCSC_Installation_and_Upgrade_Guide_11_chapter_010.html



Let's try this again.



Better. :]


...And that's pretty much it :]  You can check out the first boot up below:



I am going to setup a new standalone configuration as this is a new UCS Central server in my environment.  The installer walks you through some of your basic "new server" questions - IP, mask, gateway, hostname, DNS, passwords.  You can also elect to enable Statistics Collection.  According to the User Manual: "Cisco UCS Central collects and aggregates statistics data on Network, Temperature, Cooling and Power from the registered Cisco UCS domains."



Nonetheless, after you make it through the install, the UCS Central server reboots to apply the configuration that was specified.  You can then either log in from the CLI, or browse to the IP that was specified and check out the web interface (the login screen is very similar to the C-Series CIMC interface).



Before I do any further configuration/UCSM integration/posts on cool things you can do with UCS Central, I am going to document the upgrade procedure to 1.2(1a).


9.18.2013

VCE VBlock Visio Stencils

Looking for some way to showcase your VBlock in your existing Visio diagrams?  Look no further.  I have put together some stencils of VCE Vblock environments that you can simply import to Visio and drag into your existing network diagrams.

Here are some examples of what you will find:

VBlock100 BX-4P:


VBlock300 FX Base:


VBlock700:


VBlock 100: https://sites.google.com/site/vcevblockvisiostencils/VBlock100.vss?attredirects=0&d=1
VBlock 700MX: https://sites.google.com/site/vcevblockvisiostencils/VBlock700MX.vss?attredirects=0&d=1

**Note: I am trying to shrink down the size of the VBlock 300 files so that they can be posted within sizing limits.  Stay tuned.



7.25.2013

C-Series Rack Mount Integration with UCSM

Few things to keep in mind when integrating a rack mount server with UCSM:

-CIMC settings must be reset to factory defaults
-As long as you configure the cable management per the Cisco documentation, the server will automatically be discovered by UCSM (just as if you inserted a new blade)
-If you need to decommission a rack mount server for any reason and what to again integrate it with UCSM, don't forget to recommission it from the decommissioned tab
-The VIC card needs to be P81E or 1225 (NOT 1225T)
 -SFPs should be the same on FEX and server side (I used Twinax cables in my environment, which are also supported)
-C-series server needs to be running firmware version 1.4(6) or later.


Will add more tips to this post as I run into them.

7.22.2013

Belkin KVM Switch

More so for my own knowledge...

In order to switch between the hosts connected to a Belkin KVM switch: SCROLL LOCK, SCROLL LOCK, up arrow/down arrow.
Alternatively, if you want direct access to a specific server you can do so with: SCROLL LOCK, SCROLL LOCK, 0 + server number.  (i.e. If trying to view the console of server 2: SCROLL LOCK, SCROLL LOCK, 0, 2)

7.17.2013

UCS Core File Exporter

Bet you didn't know about this...

UCS has a feature built-in that will allow for the export of core files off of the system as soon as they occur to a specified TFTP server.  In order to configure this feature, known as the Core File Exporter, you will need to navigate in UCSM to the Admin tab -> Faults, Events and Audit Log -> Settings.  On the right hand pane, you will see a Core File Exporter tab, which will need to be enabled.






One the feature is enabled, you will be able to enter the TFTP server hostname/IP and remote path.





Whenever a core file is written to the UCS system, it will be automatically be sent to the configured TFTP server.
This feature can also be enabled via the CLI: http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/cli/config/guide/1.3.1/CLI_Config_Guide_1_3_1_chapter40.html#task_00981534E203404D9D4B547FF17D8FDB


Great feature for system monitoring and automatic export of core files to be included in TAC cases!

7.01.2013

Rehost Nexus 1000v Licenses in Minutes

We have all been there.  Nexus 1000v license re-hosting because something happened to our VSM and we needed to re-install... the LUN got corrupted... the host-ID magically changed somehow... etc, + hours on the phone trying to accomplish this task.  Instead of opening up a Licensing case, you can actually complete the re-host via Cisco's License Administration Portal in under 5 minutes!

You can access the portal via the following link: https://tools.cisco.com/SWIFT/LicensingUI/lookupLicenseForRehost

Once you log in, the link will take you directly to the 'Initiate a Rehost' option.  There are few other options available from the menus atop the page.  You will need to check the box next to the license file you would like to transfer/rehost (you can differentiate by Host ID in the case of a 1000v license).


After you click next, you will be prompted to enter the new Host ID of your VSM:

The final page is a review of the changes you submitted.  Ensure that the Target Host ID is accurate.  You will need to view and agree to Cisco's Software License Agreement.  At that point you can click Submit and you will receive a confirmation pop-up.  Your new license file will be emailed to the address associated with your cisco.com account, and you can go ahead and upload the new license file(s) to the VSM.  

This procedure will greatly expedite the time it takes to rehost the 1000v licenses!