Quickly Check Interface Status on Multiple Cisco Blade Switches in an HP C7000 Chassis

The HP blade server ecosystem is very flexible, especially when it comes to I/O connectivity modules, and one popular choice for Ethernet is the Cisco 3020 Blade Switch.  While the HP C7000 does help reduce the nest of physical cables found in a typical server rack, vSphere administrators are on their own when it comes to managing the individual blade switches — nothing new here, just another bespoke Cisco-powered network handcrafted by skilled artisans. It’s not uncommon to have four separate blade switch modules in a chassis, each corresponding to one Ethernet interface on an HP blade server.

Wouldn’t it be nice to have an easy way to quickly view the status of of all four interfaces connected to an individual blade server without having to telnet into four different blade switches and run IOS commands?  Enter clogin, a command-line utility that comes with the Really Awesome New Cisco config Differ (RANCID) tool suite, and should be packaged for most Linux distributions.

If you’re using Mac OS X, good news: RANCID is available through Homebrew.

Once the package is installed, create a .cloginrc file (with 600 permissions) in your home directory with at least the following line to enable seamless authentication to the switches:

Now test a simple command to see if things are working:

if that is successful, you can create a simple shell script to automate logging into all four blade switches to get stats for a particular blade server.  For example:

Run the script and pass the blade number (typically from 1-16 on a C7000) for a quick glance at the status of all ports as well as the VLAN info:

It’s not exactly software defined networking, but sure comes in handy when troubleshooting connectivity issues with blades.

Tags: , , ,

1 comment

  1. spayce’s avatar

    Anything like this in RANCID for virtual connect modules

Comments are now closed.