Thanks to everyone who offered advice - turns out the IBM server connect module in bay 2 of the chassis was the issue. Removing it from the chassis resolved all problems. It had nothing connected to it and all ports were disabled so I can only guess that its faulty. Thanks again, Andrew From: Andrew McBeath Sent: Tuesday, 8 September 2015 9:53 p.m. To: 'nznog(a)list.waikato.ac.nz' Subject: Appeal to bigger brains I'm throwing this out there because I'm at a loss to figure out whats happening in our lab. I realise it's a bit outside the scope of this forum but as the subject line says I'm looking for some bigger brains - Beers are involved. We have an IBM blade chassis - only 4 blades at present - with a management VLAN 50 (192.168.10.0/24) and a data vlan 100 (10.10.10.10.0/24) hooked up to our prod network (10.10.1.0 and 11.11.1.0 -Yes I know this is BAD but I inherited the network and haven't been able to change it as yet) via a juniper SRX. Blades are running VMware 5.5 - no nic teaming as yet. All blades and AMM module (all on 192.168.10 addresses) can get to all parts of the network VMWare machine (Only one so far - on 10.10.10.0 network - can ping host, can ping external firewall, CAN ONLY PING ODD OR EVEN NUMBERED IP's DEPENDING ON WETHER IT HAS AN ODD\EVEN IP) ie if its forth octet is .125 it can ping .1, .3, .5 but if I change it to .126 it can only ping .2, .4, .6 Everything I've found online points to NIC teams in certain situations but none apply as the blades only have a single NIC enabled and the VM only has one NIC assigned. Appreciate any feedback Cheers, Andrew McBeath