#juniper so you bought a juniper episode #2

So, we also have three EX 4200 series junipers. First things first lets stack these suckers.

So, actually before you stack them you need to initialize them. So I followed this ezsetup procedure.

Found this guide that basically says cable all the interconnect cables but only power on the first switch

Run the ezsetup and it will copy the configuration down to the other switches. What it won’t do is assign a vlan to the ports on the other switches though.

After reading that, It looks like I should hard code who is master / backup etc… will do that later

So, to squash one alert I will run

set chassis alarm management-ethernet link-down ignore



One thing you must must do with your ‘virtual chassis’ is to configure

Graceful Routing Engine Switchover (GRES) is not enabled by default, and it is strongly recommended to be enabled on a EX Virtual Chassis (VC).  This article includes a FAQ on the why, what, and how of enabling GRES on a VC.

It takes a failover from dropping say 30 pings, to only dropping 2 pings.

My latest annoyance though is this message: THIS DEVICE HAS BOOTED FROM THE BACKUP JUNOS IMAGE

I have tried using these steps

But if I reboot using the request system reboot slice alternate media internal, then host 0 will boot from the backup and 1 and 2 will be fine, if I do it again then 0 becomes fine 1,2 are screwed up…. such is the life



#EqualLogic time to rebuild RAID 50 two PS6000 ~ 5 hours

The two PS6000’s are in a group with capacity of 9.41 TB, 3.58 was reserved for volumes

Had to pull out a drive, took about five hours to rebuild.

#Juniper so you just bought a juniper episode 1

So, we have been going through all sorts of Juniper stuff these days. We went to a juniper boot camp or two. The first was on switching where we used a remote lab to practice (remote labs suck) and the second was on wireless AP where they had gear and it was a much nicer experience.

So I have a EX2200-C and I was trying to configure it, sweet look there is a mini usb port on the front labeled CON (for console hopefully) I russle up a mini usb plug it in install the drivers fire up putty and…..


So hit the google, of course the mini-usb isn’t enabled (I guess you only get one, serial or mini-usb) to enable:

  1. Connect the host machine to the switch using the management console port
  2. Configure the port type:
    user@switch# set system ports auxiliary port-type type

    For example, to activate the Mini USB Type-B console port:

    user@switch# set system ports auxiliary port-type mini-usb
  1. Commit the configuration and Exit.
  2. Reboot the switch. The control and the boot log will appear on the activated console.

hmmmm It would sure be nice if there was a way this could be activated right out of the box….

On replacing failed drives #EqualLogic

#EqualLogic has drives with mismatched RPM which may prevent all drives from performing at rated specifications. Mismatched drives should be replaced with matching RPM specifications

has drives with mismatched RPM which may prevent all drives from performing at rated specifications.  Mismatched drives should be replaced with matching RPM specifications

After support reviewed the logs they said a drive failure was eminent, so replaced the drive.

#Equallogic I wish I could, blink a single drive

Wouldn’t it be nice to be able to blink a single drive to identify it?

The Performance Overview tab fails to display with the error: Navigation to the webpage was cancelled

So went round and round with this one, and finally found the answer on expertsexchange (no thanks to a couple of vmware KB articles)

The answer is a crypic change of server.xml


For 64 bit machines there is a Windows update and for Windows XP 32 bit there is a bit of a hack to perform. 


(Windows XP 64 bit and Windows 2003 -

I would recommend that you back up the server.xml file that is edited for this

Windows XP 32 bit hack - I would recommend to stop the VC service first

1) on the vCenter Server machine go to %PROGRAM_FILES%\VMware\Infrastructure\tomcat\conf
2) open the "server.xml" file
3) Look for the following XML element:
<Connector port="8443"...></Connector>
4) Modify the 'ciphers' attribute to the following value:


5) Restart the vCenter server service