Unsolved
This post is more than 5 years old
8 Posts
0
2995
November 8th, 2005 15:00
PowerEdge 1855 network and startup issues
We just have a Blade Chassis installed, and trying to start deploying service using PowerEdge 1855 Blades but experiencing the following problems, which we do not see on our any of existing standalone PowerEdge servers ranging from 1650 to 2850. Thus, I am wondering if it's solely related to this Blade technology? and wondering if anyone have experience the same and got a solution.
In our environment, it's running RedHat AS4. We've noted the followings,
1. When the system is bootup, nfs mounting will fail with server not found error. However, I can mount it with a statement on rc.local;
2. DSA cannot detect PERC4 controller when it's bootup, with error of PERC4 controller not found. However, I can stop and start DSA again in rc.local and this time it can detect the PERC4 controller without problem;
3. I have a monitoring system (BigBrother) startup with a su statement on rc.local which seems always hang. However, once everything is started up, I can kill and restart using the same statement and it works;
4. After mounting the nfs volume, it will disappear after running for around half a day. This disappear doesn't generate any error message other than nfs error 512. Everything when this happen, I can still kill the process and remount the volume again and it works. Based on packet trace, it seems that this server suddenly no longer respond to nfs sync ack request.
All of the above do not happen on standalone server. Anyone got an idea on this, and can enlight me on what I can try to fix it?
Thanks,
Bosco
In our environment, it's running RedHat AS4. We've noted the followings,
1. When the system is bootup, nfs mounting will fail with server not found error. However, I can mount it with a statement on rc.local;
2. DSA cannot detect PERC4 controller when it's bootup, with error of PERC4 controller not found. However, I can stop and start DSA again in rc.local and this time it can detect the PERC4 controller without problem;
3. I have a monitoring system (BigBrother) startup with a su statement on rc.local which seems always hang. However, once everything is started up, I can kill and restart using the same statement and it works;
4. After mounting the nfs volume, it will disappear after running for around half a day. This disappear doesn't generate any error message other than nfs error 512. Everything when this happen, I can still kill the process and remount the volume again and it works. Based on packet trace, it seems that this server suddenly no longer respond to nfs sync ack request.
All of the above do not happen on standalone server. Anyone got an idea on this, and can enlight me on what I can try to fix it?
Thanks,
Bosco
No Events found!

