UCS – VIF Hold Down

November 22nd, 2011 | by | sysadmin

Nov
22

Last night I had a maintenance that went fine, but had a little hiccup that I wanted to write about. The maintenance was to simply add another block of WWN Initiators to our configuration and everything ran smooth.

Now, the reason for adding this new block is simply that we were out of WWNs and needed to turn up 4 new UCS B-200 blades. Well, since I have the new WWNs, might as well use them right? This is where the error came up that raised a bunch of alarms for our networking team which in turn, gave me a bit of ass-ache.

The fault code that was raised was Fault Code:F0283 and had a message in this format.

[transport] VIF [chassisId] / [slotId] [switchId]-[id] down, reason: [stateQual][transport] VIF [chassisId] / [id] [switchId]-[id] down, reason: [stateQual]

We ran into the stateQual being VIF Hold Down.

While looking for this error, I found the Cisco UCS Faults and Error Messages Reference which basically explained that “Endpoint(switch/fabric interconnect) reports the connectivity state on virtual interface as one of: a.down, b.errored, c.unavailable.”

Since this was a brand spanking new install and no zoning was present, all things are pointing a bit to the ports not being fully initialized since nothing has loaded a driver or attempted to make them active. Once we have a good first boot, these errors should clear themselves up as our Firmware has the appropriate bootcode for the HBAs, its just a bit of a chicken and egg issue. To test this theory, I simply loaded the ESXi boot CD with the Cisco boot drivers on it and lo and behold, the errors went away.

The confusing part is that this “looks” like an ethernet error when really it should be an HBA error. Someone on the support forum had a similiar issue as well. Also, UCS throws a major link down alarm when the link was never really up to begin with as this is a new install. A warning indication and a clearer error code on where the error actually is would make this error a lot easier to debug.

So, it appears to be harmless in our use case, but wanted to make a note of it here and maybe help out some other bastard with the same issue.

Comments Closed

New content coming

November 8th, 2011 | by | site news

Nov
08

Sure sure, we all say it, and some even believe it. I’m going to write more…promise!!!

I’ve been pretty swamped at work and side things that I have been neglecting the old blog here for a bit. But I should be posting some new content here over the next few weeks of some stuff that I have been working on and a certification that I’m picking up.

Good stuff to come…check back soon.

Comments Closed

VMworld 2011 – Lessons Learned

October 11th, 2011 | by | vmware

Oct
11

VMworld 2011 Las Vegas was my first ever VMworld, and hopefully it will be one of many! Before I left, I got some advice from a co-worker who was an alumni as well as reading various articles including David Marshall’s 10 tips for VMworld 2011 newbies.

Now that I’m been there and back and with VMworld Copenhagen just around the corner, I figured it would be a good time to recap David’s rules as I thought they were a pretty good blue print for first timers.

VMworld tip No. 1: Make time on your schedule for the Solutions Exchange

This is a chance to meet a lot of vendors and talk shop. Sure they are going to scan your badge and maybe all you wanted was that cool t-shirt that they were handing out. But there are a lot of great vendors there that we’re talking to today to answer some of our needs. I specifically was looking for capacity planning software and we found at least 3 vendors that we’re comparing currently. One tip that I would recommend, before you go next year, register with an alias of some sort so you can simply setup a rule for all the spam that will eventually come your way. Its been a huge time saver for me.

VMworld tip No. 2: Network, network, network.

There were a few people that completed every lab that was there. Its time consuming with the lines and the length of the lab itself. But there is a prize, the person that does the most labs gets a free ticket to the conference next year. But I believe that there is a higher cost to this than what these guys realize. I met a TON of people. And not sure average joes like you and me. I met some of the VMware rock stars. The guys that are writing the books that we’re buying and absorbing. If you’re not reaching out and talking to other guys at the show, you’re doing it wrong.

VMworld tip No. 3: Breakout sessions.

I highly recommend attending some sessions. I attended a lot and will fully admit, too many. The second time around, I think I’d attend the sessions that I really want to see in person and possibly ask a question in. They’re recorded so you can watch them later. Now, what I would probably skip next time around would be the group discussions. Of the 3 I attended, only one was really worth while and I think I could have gotten that answer if I would have networked a little more strategically.

VMworld tip No. 4: Remember, most breakout sessions are being recorded

See above!

VMworld tip No. 5: If there are any must-see sessions, be sure to sign up for them quickly so that they don’t fill up and lock you out.

Holy craps yeah. I signed up for a few sessions that I knew would fill up fast early on. You’ll know which ones these are but thankfully the popular ones they’ll typically put on a few times and if they don’t and it becomes popular unexpectedly, well, they still try and sneak in another session on the last day.

VMworld tip No. 6: Be careful about scheduling back-to-back sessions.

I was lucky enough that this only bit me once and it was at my last session of the conference. The conference area was big and 4 floors in size. Mix in 20,000 of your closest friends and well, you get the picture. You’re not moving anywhere fast.

VMworld tip No. 7: Try your hand at a VMworld lab session.

This is the one area where I wish I had spent more time. I think I got through 4 or 5 labs. But I wish that number was 9-10. The labs were awesome. Sure there were a few hiccups in a few due to the hyper virutalization of everything. But overall, it was pretty smooth sailing as the ops guys worked out the kinks in the system. Its hard work doing that many labs constantly. Hats off to the crew that made the labs happen!

VMworld tip No. 8: Don’t count on the Wi-Fi connection.

Yeah…Wifi was pretty spotty at time. But overall not too bad. I would recommend not even trying during the large keynotes. It will just drain your battery.

VMworld tip No. 9: The dress is business casual

Jeans and collared shirts worked for me. Some people may sport slacks, but that’s not the norm. Dress casual but professional.

VMworld tip No. 10: Enjoy the parties!

Oh yeah, can’t recommend this one enough. Talk to the vendors as well and get an invite to their parties. Almost all of them were throwing one or at least planning a dinner to wine and dine people.

And since I work with one of the organizers, keep your eyes and ears open for VMunderground. Tickets go fast but the party is a hell of a lot of fun. Free drinks and great give aways. Awesome networking happening here!

Comments Closed