Forum Replies Created

Page 1 of 2
  • Hi,

    This could in theory work, however you’ll most likely need to perform
    a few manual steps in configuring the storage repository. At a bare
    minimum, you’ll need to ensure that:

    1. Both XenServers operate on the same subnet or are at least routable
    to eachother.
    2. The XenServers need to be placed in a pool and must have
    communication with eachother.
    3. Ideally the LUNs presented by the iSCSI storage have the same IDs –
    if not, you’ll need to manually create the PBDs (see
    https://docs.xensource.com/XenServer/5.0.0/1.0/en_gb/reference.html#cl…)
    to reflect the DR SAN’s LUN configuration.

    If this is all too much, there is an alternative which may be of
    interest. This method does not require the XenServer hosts to be in a
    pool, but you’ll need to be sure not to start up VMs up from the DR
    SAN – you will need to investigate what would happen if your DR SAN
    had writes to it from the DR XenServer host. This solution would work
    as follows:

    1. Configure two discrete XenServer hosts (not in a pool) – one for
    primary usage, the other for DR.
    2. Through the XSConsole (run xsconsole if you wish to use this from
    the XenCenter console or SSH), select “Backup, Restore and Update” and
    then schedule regular metadata backups.

    To restore, you would simply create a new SR on your DR XenServer host
    and perform a metadata restore (same procedure as step 2 above, just
    choose “restore”).

    Thanks..

    Edwards

  • Hi, please specify what you want exactly. I am not getting what you waned to know. Server gets hung on disk rescan means what. You are getting error as “A connection to thetarget was lost, but Initiator successfully reconnected to the target”. I don’t think this is a whole error. Just post the question rightly and then you will able to solve your error. Just explain in such a way that reader will able to get what is happening exactly.

  • Edwards Willeam

    November 25, 2009 at 2:23 am in reply to: Server gets hung on disk rescan

    Hi, please specify what you want exactly. I am not getting what you waned to know. Server gets hung on disk rescan means what. You are getting error as “A connection to thetarget was lost, but Initiator successfully reconnected to the target”. I don’t think this is a whole error. Just post the question rightly and then you will able to solve your error. Just explain in such a way that reader will able to get what is happening exactly.

  • Hi,

    Here are some tips.

    Configuring RS-232 Connection via Front Panel

    Take the following steps to change the baud rate using the front
    panel:

    Press ENT for two seconds to enter the Main Menu. Press t or s to
    select “View and Edit Configuration ..”, then press
    ENT.
    Select “Communication Parameters ..”, then press ENT.
    Select “RS-232 Configuration ..”, then press ENT.
    Select “COM1 Configuration ..”, then press ENT.
    Select “Baud-rate 38400 ..”, then press ENT.
    If other baud rate is preferred, press t or s to select the baud
    rate,
    then press ENT for 2 seconds to confirm the selected baud
    rate. Set identical baud rate to your controller and your host
    computer
    Starting RS-232 Terminal Emulation
    The keys used when operating via the terminal are as follows:
    To select options
    [Enter] To go to a submenu or to execute a selected option
    [Esc] To escape and go back to the previous menu
    [Ctrl] [L] The controller will refresh the screen information

    Kind regards,
    Edwards

  • Edwards Willeam

    November 21, 2009 at 1:19 am in reply to: Server gets hung on disk rescan

    1.When something like this happens I have seen it be a hardware issue. It could be due to the frame size mismatch between the root switch and
    the host nic ports. btw, but i think you may not have any changes in
    the network setup recently correct. Check your BIOS settings are correct for ESX as supplied by the vendor. Reseat the riser card as well as look for anything out of the ordinary that may had a busted heat sink in one system.
    Reply With Quote
    2.Update from Support. VMware ESX 3.5, Patch ESX350-200808401-BG: Security and Other Updates to VMkernel, hostd, and Other RPMs. Apparently HP has acknowledged that there is an IRQ conflict between, at least, the DL360 G5 and ESX 3.0.1. HP is working on a firmware update to fix this issue but it is not available yet. More to come as Support enlightens me.

  • You have to make sure the array supports clustering and enable multiple intiatiors on the LUN so they can be arbitrated by a cluster. This is usually a feature that has to be enabled on the array – otherwise only one of the hosts will be able to access the LUN at a time and this no sufficient for clustering.

  • hello,

    To prevent this problem, restart the computer after you modify the
    Microsoft iSCSI Install package. To resolve this problem if you cannot
    start the computer, use Use the Last Known Good Configuration startup
    option.

    regards,
    Edwards

  • Edwards Willeam

    November 13, 2009 at 12:19 am in reply to: Lost connectivity to storage device

    We have stonefly’s opti SAN.Physically verified the all connections.checked the path also all things are perfect.

  • Edwards Willeam

    November 13, 2009 at 12:13 am in reply to: On Areca RAID card Expanding the LUN

    Hi,

    Expanding/Migrating only available while RAID Set/Volume condition is
    normal and host is not access it. Please make sure your RAID Set/
    Volume condition is normal and idle while you are setting. check it.

    Thanks

    Edwards

  • The upgrade process resets the ESX Server firewall to the default settings.
    Hi Irrani,

    To re-enable the software iSCSI port in the ESX Server firewall:

    1. Log in to the ESX host or VirtualCenter using the Virtual Infrastructure Client. If you log in to VirtualCenter, select the ESX host from the Inventory.

    2. Click the Configuration tab.

    3. Click Security Profile.

    4. Click the Properties link.

    5. Select Software iSCSI Client.

    6. Click OK

    kind regards,
    Duf

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy