If you have feedback for TechNet Subscriber Support, contact tnmff microsoft. They have been working for many years. Just recently, one of them starts having the problem. No major hardware and software changed except windows update. Whenever we add 2 more sessions in Volume Properties, they stay there for a few seconds and then disappear. SAN also show the new sessions for a few seconds and then disappear. What could be the problem? How are things going on?
For now, I couldn't find more clue about this issue. As suggested, you could contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue. In addition, if the issue has been proved as system flaw, the consulting fee would be refund. You may find phone number for your region accordingly from the link below:. Meanwhile, I'll follow up this thread.
Sorry for the inconvenience and thank you for your understanding and patience. Highly appreciate your successive effort and time. Best regards,. I do see the volume but it is named "production" Tvideo" I assume it is contained within that volume. Is there a way to look into the volume to see its contents? Go to Solution. I have created a new volume on the SAN and configured access control for one initiator IP address only. I removed all settings in the initiator. I copied in the IQN of the server.
The firewall on the server is off for testing. I do not have any targets listed on the Target tab. I have rebooted the server. View solution in original post. There is no need to do that. At that point from that populated list you can login and connect that server to that EQL volume. Here's some Equallogic training videos. You might find some of them helpful.
If in the ISCSI initiator app you see the volume connected, I believe that error message is for a volume that is no longer there. For that volume how is access restricted? It should be set to only allow that server to access that volume. This results in corruption over time. When you reboot then is when you tend to discover the problem as the OS re-reads the partition table and filesystem info. If the access control is a wildcard then that needs to be changed immediately.
Using IQN name from the server is a very common approach. FWIW, this is the same mechanism that is used for multi-pathing. After a SCSI timeout, the system tries to re-connect using an alternative path. So a 15 second delay not an outage a few times a year is not a very big deal.
If you have to, you can schedule it for non-peak hours. Everything will work, applications will stay up and end users will see a short temporary hang — if they see anything at all. Skip to content.
0コメント