Note for later – installing ip rules on a brocade SAN switch

Florian — Tue, 20 Jul 2010 13:57:43 +0000

After forgetting what I did previously and I eventually managed to lock myself out of the fabric.

So instead of adding a rule to disable telnet, you will prefer to clone the rule set and modify it.

#ipfilter --clone CurrentSec -from default_ipv4
#ipfilter --show (write down the rule number for Telnet 23)
#ipfilter --delrule CurrentSec -rule 2
#ipfilter --addrule CurrentSec -rule 2 -sip any -dp 23 -proto tcp -act deny
#ipfilter --save CurrentSec
#ipfilter --activate CurrentSec

VMX connection handshake failed for mks

Florian — Mon, 22 Feb 2010 18:21:37 +0000

Today I ran into an interesting error when trying to access one of my VM.

First I could not get into that VM remotely as it appeared as offline. This said, VI showed the VM as healthy and online.

Trying to get to it using the Console from VI showed the following error:

As you can see I was afraid that some of the SAN path were down or some kind of painful problem with the SAN. No, no a quick ssh in showed that the mentioned volumes were online, accessible and all SAN paths were up.

So I do power off and restart the VM: no success. Restart the ESX (after vmotioning all VMs): no success.

Eventually I find that in the settings of the VM, there was a reference of some floppy image pointing to a volume (not even on the same volume). I changed that option to Client Device and voila everything was back to normal.

Looking that information up on the VMware KB or community forum doesn't provide any solution.

a Flo + a Blog = a Flog » san

Note for later – installing ip rules on a brocade SAN switch

VMX connection handshake failed for mks