travis' brain dump

Ok, since there really isn’t a very good tutorial out there on this nor are there good resources to find the right links to this stuff, here’s a post for you and for me.

So you need update your Virtual Connect Module, right? Should be just as easy as updating the OA, right? riiiiight. Because HP, that’s why.

Ok, so a few things you’ll need:

1. A current version of the VCSU -> Click Here <-
2. A current version of the VCM firmware. (make sure you get the right firmware for your device type)
a. Flex-10/10D Module
b. FlexFabric 10Gb/24-port Module
c. FlexFabric-20/40 F8 Module
3. You don’t need this, but it’s handy. VCSU Useful Commands.

Now that you’ve made it through all that, the easy part. First we’re going to check the current version of the module, do this by running the vcsu utility with the following:

.\vcsu.exe -a version -i (ip.addr.of.active.oa) -u OA.Admin -p OA,Admin.Pass -vcu VCU.Admin -vcp VCU.Admin.Pass 

(yes, you really want to pass all of those lovely credentials, even if they are the same login/password for both the OA and the VCU)

You should then see some results sort of like this:

Now to update. This is very similar to your version check, except changing version to update and adding the switch and path at the end.

.\vcsu.exe -a update -i (ip.addr.of.active.oa) -u OA.Admin -p OA,Admin.Pass -vcu VCU.Admin -vcp VCU.Admin.Pass -l ‘c:\path\to\firmware.bin’

You should now see something like the following:

At this point you should now be updated.

I’ll try to keep these updated with the most current links as I update my equipment, however, if someone hits it and it’s out of date, please let me know and I’ll go update it.

Little FreeBSD one for this morning… mostly because I’m sure I’ll forget this.

So, here’s the scenario, common mistake… you put a typo in your rc.conf and you get slapped into single user mode. We’ve all been there, on multiple occasions. It’s typically one of those moments you forgot an end quote or something silly like that. No biggie right?

I guess that depends on if you’re a regular user of ZFS or if you’ve been using UFS2 for so long you run commands for that on auto pilot…
In my case this morning, it was just that. “oh yeah, I’m running zfs on this box…” and found myself with half a second of ‘tf?’ when I went to run ‘mount -w /’ and received ‘unknown special file or file system’.

Solution? Just as easy.

# mount -u /
# mount -a -t zfs

Fix issue, reboot. 🙂