Unsolved
This post is more than 5 years old
5 Posts
0
2155
June 12th, 2012 22:00
The problem with the initialization of the storage
Good afternoon. Storage CLARiiON ax4-5i.Server 2008 R2. When restart the server connected two of the resource can be seen in the control console supports, but writes, that the devices outside the network. Only helps break the connection through the control panel storage, and mix again. After that require re-initialize the disks, and re-connected via snap isсsi, keeping the data.How to ensure that the wheels were mounted on reboot automatically, which used to avoid this problem?
No Events found!
Anonymous User
457 Posts
0
June 13th, 2012 03:00
Hi,
May I know if this the new array that you are trying to Initialize ..?
Regards,
Suman Pinnamaneni
sawaqa
5 Posts
0
June 13th, 2012 04:00
No, this array has worked for 2 months, but without having to reboot the server when you restart the server hard disk storage as determined by raw-disk until reconnection iscsi made on both sides and switch to dynamic disks.
rupal1
433 Posts
0
June 13th, 2012 05:00
Need to have the physical analysis of the array, please open a SR with the support and get a CE onsite to check your enviorment as from the explianation the issue here is not very clear.
Thanks
Anonymous User
457 Posts
0
June 13th, 2012 06:00
Hi,
You can open Service Request either by contacting EMC CST ( CST contact no: http://india.emc.com/collateral/contact-us/h4165-csc-phonelist-ho.pdf” or you can also open via Powerlink by selecting “Live Chat” ., Please follow the steps to open Service Request using “Live chat”:
Go to https://Powerlink.emc.com
Log in with your Powerlink credentials.
Go to Support > Request Support > Live Chat
To begin your Live Chat session, follow these steps::
Regards,
Suman Pinnamaneni
christopher_ime
6 Operator
•
2K Posts
0
June 16th, 2012 20:00
When configuring iSCSI there are several best practices that you might have overlooked in the MS iSCSI Initiator software:
1) "Automatically restore this connection when the computer starts" (persistent targets)
As you log into each target, you will have the ability to make it a "Favorite Target" so that it is restored (as the lengthy option suggests) upon reboot.
2) "Volumes and Devices" (persistent binding)
On the above mentioned tab, this is how you configure "persistent binding" (the equivalent on a fibre channel HBA) so that the device is restored with the same volume each time upon reboot. Please note though that you first have to configure the target as a "Favorite Target".
3) Application service dependencies (depend on msiscsi)
It is also best practice to that the application relying on the iSCSI LUNs to configure the application service(s) to depend on the iSCSI service (msiscsi) to start first. For instance, using SQL Server as an example:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER\DependOnService
Add the key: "msiscsi"
Each application such as Exchange has a similar registry key (or you can do this also via the MMC: services.msc)