Unsolved
This post is more than 5 years old
12 Posts
0
150582
Problems with my new PowerEdge M620
Hi Everyone:
I recently bought 4 new power edge blade servers m620, and the problem i am facing is this one in particular, i am installing xenserver version 6 in this servers, at the end of the installation, I made some connectivity tests to certify everything it's OK, but only the new 4 servers M620 are able to respond pings between them, when i made a ping to my default gateway, the ping doesn't respond, also when pinging to my other servers "the old ones M610" the same issue happen,ping does not respond. My switches on fabrics A1 and A2 are M6220 and doesn't have any particular configuration, in fact they are with the fabric configuration, i suppose the issue is because the firmware on my M1000e is not the new one. It is possible this is causing the problem, or any one have other suggestion?
Waiting for someone respond this post, i will be eternally grateful
Best Regards
DELL-Chris H
Moderator
Moderator
•
8.8K Posts
0
July 24th, 2012 10:00
JLNA221082,
On the CMC what does the M610 (ones failing ping) show? Are they online and healthy?
Also, if you look at the M620 under the I/O Connectivity, are they showing the same under Fabric B and C as the M610's?
Fabric A is a passthrough so that will be the same.
You may also check that the power cap isn't set to low or that a power supply isn't functioning, causing the blades to not start up.
Lastly see if anything is showing under the CMC log referring to this.
Let me know what you find.
DELL-Chris H
Moderator
Moderator
•
8.8K Posts
0
July 24th, 2012 10:00
It is also a good idea to update everything to current as well. As you were stating.
JLNA221082
12 Posts
0
July 24th, 2012 11:00
Chris:
thanks for your response, let me describe what do i have on the fabrics, on A1 and A2 there is two PowerConnect M6220 connected directly to a Cisco 3560G that I use for LAN connection, on fabbrics B1 and B2 also I have two PowerConnect M6220 used exclusively for SAN connection based on ISCSI, so the issue is, four of the PowerEdge M620 when the OS is already installed "Xen Server 6" they are no able to ping to my oldest blades "model M610" nor even my default gateway or other ip address on my LAN, I suppose the issue is because the firmware of the enclosure is an older one, or may I have to update all the firmwares on my infrastructure.
have you ever heard from someone facing a problem like this?
Best Regards
quantranblog
9 Posts
0
July 25th, 2012 02:00
Hi,
From M610 you can ping gateway or not?
If your can ping gateway from M610 you can try swap M620 to slot of M610 and ping again.
You can try by direct connect your Laptop to M6220 and ping gateway, if can not maybe your network has problem from M6220 to Cisco Switch.
toddpfaff
4 Posts
0
July 27th, 2012 15:00
We are experiencing the same problem with a new Dell PowerEdge M620 blade in an M1000e chassis with a Dell PowerConnect M6220 blade switch on fabric A.
The original passthrough on fabric A has been removed and replaced by this M6220 switch.
We have other M600 and M610 blades in this chassis that are working fine.
Our M620 has the Broadcom 10Gbps NIC (as opposed to the Intel NIC option).
Our M1000e chassis and M620 blade both have latest firmware.
Our M6220 switch currently runs firmware PCM6220v3.1.5.7. The latest M6220 firmware at this time is PCM6220v4.2.2.3a30.
With linux installed on this M620 blade we can see that the NIC is properly detected by the linux broadcom driver, the device is properly configured, the interface comes up, ethtool shows the device as properly detecting link status and speed, and after we attempt some pings from this host we can see packets have been transmitted with ifconfig but no packets have been received.
After some back and forth with Dell support, where they had us send them log dumps and try reseating the NIC, they have now told us to update the M6220 firmware. That was my guess a week ago but, unfortunately, that means network downtime.
I'm reluctant to believe that there is not something that could be configured at either the M620 blade or the M6220 switch port to make this work until such time as we can schedule downtime to update the M6220 switch firmware. What is it about the M6220 firmware update to version 4.x that would make it more compatible with the next generation of Dell blades such as the M620?
toddpfaff
4 Posts
0
July 27th, 2012 15:00
So you did not have to update firmware on either your M1000e chassis or the M6220 switch?
If you don't mind, could you please tell us what firmware versions you are currently running on
these various pieces of hardware?
Thanks!
JLNA221082
12 Posts
0
July 27th, 2012 15:00
the problem was occasioned because xenserver version 6.0.0 does not have the proper drivers for intel and broadcom network cards, we installed the version 6.0.2 with fixes and now my blades are working without problems
JLNA221082
12 Posts
0
July 27th, 2012 16:00
dell technical support, gave me the advice to update the firmware on my enclosure to version 4.11, and my M610 blades to the latest firmware in the IDRAC, PERC and BIOS, but honestly, I never believed that this was the solution, everything was about updating the drivers on the OS
toddpfaff
4 Posts
0
July 27th, 2012 19:00
I'm curious to know what nic driver version you're using now in xenserver 6.0.2.
JLNA221082
12 Posts
0
July 30th, 2012 07:00
sure, here are the links of the drivers i installed, also these are the brands and models of the nics i'm using
NetXtreme II BCM57810S Converged Controller "LOM Fabrics A1 and B2"
http://hcl.vmd.citrix.com/ProductDetails.aspx?ProductType=NIC&ProductName=NetXtreme%20II%20BCM57810S%20Converged%20Controller
Intel® Ethernet Server Adapter I350 "Mezz Fabrics B1 and B2"
http://hcl.vmd.citrix.com/ProductDetails.aspx?ProductType=NIC&ProductName=Intel%C2%AE%20Ethernet%20Server%20Adapter%20I350
i hope works for you
best regards