Category Archives: General

Intel c2000 Cisco Clock Signal Replacement

So, you thought you’d buy into the next generation of firewall technology early? #FAIL

After ongoing reporting from The Register, Cisco have finally admitted some of their products are affected by the intel C2000 series chip problem. This affects most (all?) ASA5506’s, 5508’s, and 5516’s, along with some other equipment, for a full list – look at Cisco’s product notices here.

The solution – fill out their spreadsheet with your devices details and get it sent over to Cisco, they promise to replace the equipment as soon as possible. I will keep this topic updated with my experience, but so far the only replies I’ve had to my email with the sheet was a mailbox full message (!) and a confirmation saying that I should get a response within the next two to three weeks, so don’t wait to get your request in.

This problem is not isolated to Cisco equipment, with Synology, Netgear, HP, Dell and Supermicro also having products affected by the faulty chip. For more information head over to The Register for the latest.

So Far the list of chips suspected to be vulnerable to sudden death are the C2308, C2338, C2350, C2358, C2508, C2518, C2530, C2538, C2550, C2558, C2718, C2730, C2738, C2750, and C2758. Although it seems vendors are reluctant to admit to problems being caused by the processors it seems that the writing is on the wall, go out and check what your new network device is actually running, and contact your vendor to make sure they have a plan to get you back up and running when it fails!


IP Office VM Pro Installation Error 1327

When installing Avaya IP Office Voicemail Pro 9.13.0, I came across this error, 1327 Invalid Drive:<driver letter of problem drive> and was unable to install voicemail pro.

Searching google suggested that a change is made to the registry to resolve this issue for office installs, and some suggested disconnecting the drive and disabling automatic reconnect.

There is, however, an easier solution:

Step 1: Create the local voicemail user

Step 2:  Log in as that user,

Step 3: Run your installation application again. It should now complete without error. If you are asked to restart the machine, you must log in using the local account to continue installation.

Step 4: Once the install is completed, you can continue to use your domain credentials.

I hope this saves you some time.

This problem is not really Avaya related, but an issue with Microsoft Windows, so this procedure may or may not work for you if you are trying to install some other application, but it’s worth a shot. Let me know if it worked for you…

Welcome to WeAreNothing

Welcome to, the new home of this blog. I don’t know why I just said new home, because it’s not.. it never existed before so I can hardly call it the new home, so maybe, the first home of my WeAreNothing blog.

Firstly, thanks for visiting, I intend to update this blog regularly (how many times have you heard that before?) so that I can share my personal view on the convergence industry, and by that I mean pretty much anything IT related.

For those of you that have never met me, I am a voice and data engineer from Northern England, I install and maintain Mitel and Avaya phone systems and the systems required for their operation. This means I am frequently required to work with other tech, such as Cisco remote access and site to site VPNs, and VMware. Whilst not my primary focus, it does still interest me, so from time to time you may see me post about these things. I will probably also post about common problems I have seen, these may sometimes seem a little off topic, but this is industry we are in, nobody will have the same problems all the time, and sometimes you will be asked to investigate a problems slightly outside your comfort zone. I hope you may find the answer to some problem you may have on this site at some point.