If you’re trying to set the time on a brand new out of box Cisco Nexus 5500 and you get the message “Setting clock from CLI is not allowed in this VDC.”, it’s because the clock protocol is set to ntp, even though you didn’t configure NTP. Go into config and type “clock protocol none”, and then it will let you set the time.

Then, when you’ve finished the config, set up NTP!

And while you’re at it, this page from Cisco is awesome for troubleshooting VPC

This week, I went to Las Vegas. For a day. I arrived in at about 9:30PM, and left the next day at the same time. I went along for Chris and Rachel’s wedding.. and their wedding guest, Kim, Penny and Laura. Yay seeing Perth people. I also had a pretty full week at work.. so I’m sitting at home on Friday night thinking back over my week – “san installation, crazydayinvegaswithkimandpenny, san installation, network installation, san installation..”

These days I’m doing a lot of work implementing Datacentre equipment, including SANs, servers and switches. I recently installed some Brocade VDX6720 switches. Pretty cool stuff, especially the way that TRILL and vLAGs work so easily. I had a loaner switch, running Network OS (NOS) 3.0.1aa, while waiting for the final switches to be delivered. When the final switches were delivered, they were running NOS 2.0.1, so I had to upgrade them. That wasn’t the smoothest of experiences.

In Brocade’s defence, I should have read the manual closer, both of these issues are in there, if you read it all.. but time is money!

1 – I couldn’t get it to download new firmware over SCP – it kept reporting file not found, and that’s hard to diagnose. Might not be brocade’s fault, so I went to use the USB method of loading firmware. It took about 15 minutes till I re-read the manual and saw that you can only use the Brocade branded USB key to do that. Yes, there’s a USB port on the thing, but you can only use the ONE USB key it came with to load firmware onto it (or a similar Brocade one, at least they aren’t node locked)

2 – Turns out by “not supported”, they mean that a direct upgrade from 2.0.1 to 3.0.1 will almost brick your switch. You need to upgrade to 3.0.0 first. I missed that bit. One of the switches didn’t have VLAN information on, and came back pretty quickly, while the other, that I had configured VLANs on, would crash at startup.

eAnvil rev B found
Info: panic dump has been initialized!
Exisitng reboot reason fsize = 5 rb=
Global Fan Direction is 0

The file contains no trace dump information.

Network OS ((none))

(none) console login: ********************************************************************************************************
** Crashed in OM/Worker (WaveNs::ClusterLocalObjectManager::boot(WaveNs::WaveAsynchronousContextForBootPhases*))
********************************************************************************************************

WaveNs::ClusterLocalObjectManager::boot(WaveNs::WaveAsynchronousContextForBootPhases*)
WaveNs::WaveObjectManager::bootBootSelfStep(WaveNs::PrismLinearSequencerContext*)
WaveNs::PrismLinearSequencerContext::executeCurrentStep()
WaveNs::PrismLinearSequencerContext::executeNextStep(unsigned int const&)
WaveNs::WaveObjectManager::bootBootWorkersStep(WaveNs::PrismLinearSequencerContext*)
WaveNs::PrismLinearSequencerContext::executeCurrentStep()
WaveNs::PrismLinearSequencerContext::start()
WaveNs::WaveObjectManager::bootHandler(WaveNs::PrismBootObjectManagerMessage*)
WaveNs::WaveObjectManager::PrismOperationMapContext::executeMessageHandler(WaveNs::PrismMessage*&)
WaveNs::WaveObjectManager::handlePrismMessage(WaveNs::PrismMessage*)
WaveNs::PrismThread::start()
WaveNs::PrismPosixThread::pthreadStartMethod(WaveNs::PrismPosixThread*)
/lib/libpthread.so.0 [0xc306e5c]
clone

Thu Jul 11 22:04:07 UTC 2013 :: Confd: Waiting for Dcmd to become ready...

How did I recover? Well, reading scrollback I noticed a “Found 2(threshold 5) abnormal reboots within 3000 seconds window(threshold)” message, and wondered what would happen if I hit 5 abnormal reboots? Well, that gives you an option to “clean databases”, which fixed it good and proper.

3 – Bonus gripe here. As far as I can tell, there’s no way to configure a range of interfaces, like cisco’s “int range” or dell’s “int blah/0 to blah/2”. I’ve seen some people say on forums that they wouldn’t buy Brocade again because of this. A little harsh, but it seems like a pretty trivial feature to add.

After the previously posted of “thieving gits” in 2009, I now encrypt my laptop, and was prepared to take a performance hit for it, and this is just fine.

For the OCZ Agility 4 I just got (AGT4-25SAT3-512G) – this is the “411”, as they say here. Without encrypting, blackmagic speed test was 208MB/sec write, 252MB/sec read. Encrypted with Filevault, it’s 196MB/sec write and 215MB/sec read, which is good enough, especially considering I was getting about 40MB/sec read/write on my encrypted 5200RPM HDD (vs 70MB/sec read/write on my wife’s unencrypted 7200RPM HDD)

One of the pieces of advice I’ve seen about SSDs is to not encrypt them because the extra write cycle will wear them out quicker, incompressible data leads to slower transfer rates, garbage collection/trim will slow them down, etc. Well, that hasn’t been my experience, and these concerns are even addressed specifically for this drive.

I sort of regard replacing hard drives like changing oil in a car – something you need to do to keep things working. It might last, but it probably won’t.

So along those lines, I’ve just replaced the hard drive in my MacBook Pro with a new SSD – my local computer store had two 512GB OCZ Agility 4’s for a very good price – so I got that.

One things I was worried about was how it works with the crazy NVidia MCP79 SATA interface in these.. they are a SATA-II controller, and have a bit of a bug, where if they see a SATA-III device, it goes “wtf is this?” and clocks it down to SATA-I speed, instead of SATA-II. For hard drives, that doesn’t matter – but for SSD’s, it’s going to limit performance. I have an SSD in my work MacBook Pro, of a similar vintage, and it only runs at SATA-I speed, and it’s good enough, but not great.

I did some reading on OCZ’s offerings – for their “3” series of drives, there’s a utility you can download to set them to SATA-II, but no such utility exists for the “4” series. Well, turns out what I had seen suggested is the case – they will detect they’re connected to an MCP79, and automatically claim to be SATA-II. This is the main reason I’m posting this – in case someone else has similar concerns ;) So this SSD is doing 208MB/sec write, 250MB/sec read, which is pretty impressive.

As a side note: I saw a storage company’s SEs who I work quite closely with while I was buying this – and made a joke about how much cheaper they were than their SSD’s ;)

Damn fine bird

Went to Mount Baker today – beautiful place. Also set up theducks.org to only have comments via Facebook. Sorry.

I could write a lot about Steve Job’s death, but a lot of it has been said by others, and said well.

I’ll take the anonymous proverb, sometimes mis-attributed to Dr Seuss – “Don’t cry because it’s over, smile because it happened.”

And what happened was amazing – from the “ignition” (as their press releases say) of the personal computer market, their decline, NeXT’s rise, Apple’s return and to the sheer scale of their success.

But I’m sad because it wasn’t finished. He won’t see the mothership built, or even his new house, or the growth and development of his youngest children, or the evolution of Apple or society.

I’m sorry he didn’t get a dotage – a relaxing retirement. I’m sorry he didn’t get to do more philanthropic work. I’m sorry he wasn’t able to make Apple a good corporate citizen – the ~$80 billion Apple has in the bank is money that has come from consumers and hasn’t “trickled down” back into society – and that’s a big problem.

But, for all these things he wasn’t able to achieve in one lifetime, he still did some truly amazing things.