Hi All, I have recently been looking through our network here, and have found a large number of overruns on various interfaces within our 6513 switch. We only had 12 blades installed, so I have now installed a 13th blade so that I can reduce some of the congestion. As these switch blades work on a line card supporting 8 ports, I have split up the current ports into groups of 8, totalled any overruns and identified the biggest groups of congestion, along with the biggest single offenders etc. Now, the root cause of the overruns appears to be various blade enclosures of ours, so consist of multiple servers which could be creating the load. Unfortunately, whoever did the cabling has not done a good job and large amounts of it appear to be wrong. I was rather hoping I could look at the cables from the blade centres, which state which port they are plugged into, then present that to our server team to show which servers/blades are causing the fault. Due to the labelling though I am not able to do it without individually tracing each and every cable, which would be a mountain if work for me to get through. So my question, Is there a way from the switch to be able to find out which port in the blade centre it is connected too? I know if it was a single server, then I could get the server MAC address, then just check the mac address table to see where it is coming from, however I am not too sure how it works with blade centres, as they have multiple servers. Will all data still come from one shared NIC? ie I will be able to see the same NIC coming in on 8 different ports on the switch, but no way to know which port in the Blade is sending to that switch port? If that makes sense? Is there an easy way to audit this? So that I can find where the problem is without having to trace the mountains of cables?