Unsolved
This post is more than 5 years old
7 Posts
0
20607
May 30th, 2012 09:00
Inconsistent iscsi Connection on OS startup
Equallogic is a PS5000E and it is connected to 2 physical machines that are running SLES 11 Enterprise. There are 3 volumes that the SLES hosts connect to. The "Connected Targets" start-up option is set to "automatic" for both hosts.
The issue is the following:
Upon reboot/shutdown-startup one of the SLES 11 hosts simply will not consistently connect to any of the 3 volumes on boot/reboot. It is quite random and will sometimes connect on 3-4 reboots in a row and then will not connect the next time. I would guess the connection is made maybe 50% of the time.
When the volumes do not connect on OS boot, the Equallogic can be connected to manually. THe volumes are still shown in Discovered Targets.
All settings have been checked and everything appears correct (if they werent I would think it simply would never connect).
Anyone seen this type of issue and have any suggestions to guranttee connection?
0 events found
jwmcf1
7 Posts
0
May 30th, 2012 12:00
Yes, it is only one server that is showing the problem. THe FW or the equallogic is at 5.2.2.
The server ports and equallogic ports all have portfast enabled. PVST is enabled on the switches.
All port settings match between the server that works and the one that does not.
jwmcf1
7 Posts
0
May 30th, 2012 13:00
Yes, it is very strange. I can see nothing obvious in the Linux system logs on the server.
Rebuilding is out of the question at this point. Physical server which is one node in an Oracle RAC system.
jwmcf1
7 Posts
0
May 31st, 2012 08:00
Unfortunately do not have another server to try install on. Was hoping there was maybe a few system settings I could check. Havent talked to the SLES support, but may need to go that route.
thanks
jwmcf1
7 Posts
0
May 31st, 2012 10:00
Just did a little research and see mention of the daemon start/stop scripts. Is it possible that during reboots/shutdowns that the service is not always being stopped correctly and on the next startup some log file from the previous session is preventing the daemon from starting?
jwmcf1
7 Posts
0
May 31st, 2012 10:00
I will look it up, but can you explain what the forked verison is/?