I know this is old, but I have been dealing with this recently and thought I would throw something at this. While it is true that a defective device or FW may be at fault, be careful to assume something is defective. I had several M620 blades where the NDC ports on the ethernet pass-through in fabric A were not connected during maintenance and rebuilding. These blades would eventually finish initializing FW, but it took forever compared to the ones that had a connection. As soon as I plugged cables into the appropriate ports, the time to boot went back to normal. I wish there was an easy way to avoid this without having to configure a route through a switch in another fabric or something. Anyone know how to do that btw?
DELL-Chris H
Moderator
•
9.7K Posts
0
August 5th, 2016 07:00
John Bradshaw,
What is the current version for the BIOS and iDrac at on your M620? Also, what devices, do you have attached to the server, if any?
Let me know
bradje1
2 Intern
•
743 Posts
0
August 10th, 2016 16:00
All f/ware is the latest. There are no external devices attached to the servers.
Thx,
JB
Cieginator
1 Rookie
•
8 Posts
0
April 27th, 2018 06:00
I know this is old, but I have been dealing with this recently and thought I would throw something at this. While it is true that a defective device or FW may be at fault, be careful to assume something is defective. I had several M620 blades where the NDC ports on the ethernet pass-through in fabric A were not connected during maintenance and rebuilding. These blades would eventually finish initializing FW, but it took forever compared to the ones that had a connection. As soon as I plugged cables into the appropriate ports, the time to boot went back to normal. I wish there was an easy way to avoid this without having to configure a route through a switch in another fabric or something. Anyone know how to do that btw?