Re: [ovirt-users] iscsi failover MD3820i

[Marcin Kruk]

According to not hosted-engine storage, I found the
"storage_server_connections" and "lun_storage_server_connnection_map"
tables.
Is it possible to insert there rows with info about my extra iSCSI
connections?

2017-03-08 11:45 GMT+01:00 Marcin Kruk :

> I found the configuration file /etc/ovirt-hosted-engine/hosted-engine.conf
> with field sotrage=.
> Is it possible to change the value above to put four IP there (four array
> interfaces IP)?
>
> 2017-03-08 10:58 GMT+01:00 Marcin Kruk :
>
>> How to verify this?
>> In the RHEM GUI storage ->  -> Manage domain  I can see all
>> fourt target names,
>> but mabye there is only present state and I shoud verify something else
>> in the database or wherever?
>>
>> Where is the info about iSCSI hosted-engine storage target IP,
>> about other storages information is in the table
>> engine.storage_server_connections.
>> I presume that information about iSCSI storage target IP can not be in
>> the
>> the database due to "chicken or the egg" dillema.
>>
>> 2017-03-07 22:50 GMT+01:00 Dan Yasny :
>>
>>> "*Important:* If more than one path access is required, ensure to
>>> discover and log in to the target through all the required paths. Modifying
>>> a storage domain to add additional paths is currently not supported."
>>>
>>> This is from the oVirt admin guide, did you discover and login to all
>>> the MD3xxxi controllers/portals when you were setting the storage domain up?
>>>
>>> On Tue, Mar 7, 2017 at 4:43 PM, Marcin Kruk 
>>> wrote:
>>>
 Hello I have got Dell MD3820i and four interfaces which was connected
 to the hostst via switches.

 But there is only one IP which I can set during the configuration of
 iSCSI RHV storage.
 Everything has been fine until I pluged off cable from the storage NIC
 interface with IP configured in the RHV iSCSI section.

 Now VDSMD got problem because it tries to connect via iscsiadm with
 exact IP and does not use the configuration from the /var/lib/iscsi/, where
 are tree extra paths to achive the LUN. In multipath -ll I see an active
 path, of course with the second storage interface IP

 systemctl status vdsmd:
CGroup: /system.slice/vdsmd.service
├─4975 /usr/bin/python /usr/share/vdsm/vdsm
├─5558 /usr/bin/sudo -n /usr/sbin/iscsiadm -m node -T
 iqn.1984-05.com.dell:powervault.md3800i.600a098000ae589c5893ade2
 -I default -p 192...
└─5559 /usr/sbin/iscsiadm -m node -T
 iqn.1984-05.com.dell:powervault.md3800i.600a098000ae589c5893ade2
 -I default -p 192.168.130.101 32...

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] iscsi failover MD3820i

[Marcin Kruk]

I found the configuration file /etc/ovirt-hosted-engine/hosted-engine.conf
with field sotrage=.
Is it possible to change the value above to put four IP there (four array
interfaces IP)?

2017-03-08 10:58 GMT+01:00 Marcin Kruk :

> How to verify this?
> In the RHEM GUI storage ->  -> Manage domain  I can see all
> fourt target names,
> but mabye there is only present state and I shoud verify something else in
> the database or wherever?
>
> Where is the info about iSCSI hosted-engine storage target IP,
> about other storages information is in the table
> engine.storage_server_connections.
> I presume that information about iSCSI storage target IP can not be in the
> the database due to "chicken or the egg" dillema.
>
> 2017-03-07 22:50 GMT+01:00 Dan Yasny :
>
>> "*Important:* If more than one path access is required, ensure to
>> discover and log in to the target through all the required paths. Modifying
>> a storage domain to add additional paths is currently not supported."
>>
>> This is from the oVirt admin guide, did you discover and login to all the
>> MD3xxxi controllers/portals when you were setting the storage domain up?
>>
>> On Tue, Mar 7, 2017 at 4:43 PM, Marcin Kruk 
>> wrote:
>>
>>> Hello I have got Dell MD3820i and four interfaces which was connected to
>>> the hostst via switches.
>>>
>>> But there is only one IP which I can set during the configuration of
>>> iSCSI RHV storage.
>>> Everything has been fine until I pluged off cable from the storage NIC
>>> interface with IP configured in the RHV iSCSI section.
>>>
>>> Now VDSMD got problem because it tries to connect via iscsiadm with
>>> exact IP and does not use the configuration from the /var/lib/iscsi/, where
>>> are tree extra paths to achive the LUN. In multipath -ll I see an active
>>> path, of course with the second storage interface IP
>>>
>>> systemctl status vdsmd:
>>>CGroup: /system.slice/vdsmd.service
>>>├─4975 /usr/bin/python /usr/share/vdsm/vdsm
>>>├─5558 /usr/bin/sudo -n /usr/sbin/iscsiadm -m node -T
>>> iqn.1984-05.com.dell:powervault.md3800i.600a098000ae589c5893ade2
>>> -I default -p 192...
>>>└─5559 /usr/sbin/iscsiadm -m node -T
>>> iqn.1984-05.com.dell:powervault.md3800i.600a098000ae589c5893ade2
>>> -I default -p 192.168.130.101 32...
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] iscsi failover MD3820i

[Marcin Kruk]

How to verify this?
In the RHEM GUI storage ->  -> Manage domain  I can see all
fourt target names,
but mabye there is only present state and I shoud verify something else in
the database or wherever?

Where is the info about iSCSI hosted-engine storage target IP,
about other storages information is in the table engine.storage_server_
connections.
I presume that information about iSCSI storage target IP can not be in the
the database due to "chicken or the egg" dillema.

2017-03-07 22:50 GMT+01:00 Dan Yasny :

> "*Important:* If more than one path access is required, ensure to
> discover and log in to the target through all the required paths. Modifying
> a storage domain to add additional paths is currently not supported."
>
> This is from the oVirt admin guide, did you discover and login to all the
> MD3xxxi controllers/portals when you were setting the storage domain up?
>
> On Tue, Mar 7, 2017 at 4:43 PM, Marcin Kruk 
> wrote:
>
>> Hello I have got Dell MD3820i and four interfaces which was connected to
>> the hostst via switches.
>>
>> But there is only one IP which I can set during the configuration of
>> iSCSI RHV storage.
>> Everything has been fine until I pluged off cable from the storage NIC
>> interface with IP configured in the RHV iSCSI section.
>>
>> Now VDSMD got problem because it tries to connect via iscsiadm with exact
>> IP and does not use the configuration from the /var/lib/iscsi/, where are
>> tree extra paths to achive the LUN. In multipath -ll I see an active path,
>> of course with the second storage interface IP
>>
>> systemctl status vdsmd:
>>CGroup: /system.slice/vdsmd.service
>>├─4975 /usr/bin/python /usr/share/vdsm/vdsm
>>├─5558 /usr/bin/sudo -n /usr/sbin/iscsiadm -m node -T
>> iqn.1984-05.com.dell:powervault.md3800i.600a098000ae589c5893ade2
>> -I default -p 192...
>>└─5559 /usr/sbin/iscsiadm -m node -T
>> iqn.1984-05.com.dell:powervault.md3800i.600a098000ae589c5893ade2
>> -I default -p 192.168.130.101 32...
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] iscsi failover MD3820i

[Dan Yasny]

"*Important:* If more than one path access is required, ensure to discover
and log in to the target through all the required paths. Modifying a
storage domain to add additional paths is currently not supported."

This is from the oVirt admin guide, did you discover and login to all the
MD3xxxi controllers/portals when you were setting the storage domain up?

On Tue, Mar 7, 2017 at 4:43 PM, Marcin Kruk  wrote:

> Hello I have got Dell MD3820i and four interfaces which was connected to
> the hostst via switches.
>
> But there is only one IP which I can set during the configuration of iSCSI
> RHV storage.
> Everything has been fine until I pluged off cable from the storage NIC
> interface with IP configured in the RHV iSCSI section.
>
> Now VDSMD got problem because it tries to connect via iscsiadm with exact
> IP and does not use the configuration from the /var/lib/iscsi/, where are
> tree extra paths to achive the LUN. In multipath -ll I see an active path,
> of course with the second storage interface IP
>
> systemctl status vdsmd:
>CGroup: /system.slice/vdsmd.service
>├─4975 /usr/bin/python /usr/share/vdsm/vdsm
>├─5558 /usr/bin/sudo -n /usr/sbin/iscsiadm -m node -T
> iqn.1984-05.com.dell:powervault.md3800i.600a098000ae589c5893ade2
> -I default -p 192...
>└─5559 /usr/sbin/iscsiadm -m node -T iqn.1984-05.com.dell:
> powervault.md3800i.600a098000ae589c5893ade2 -I default -p
> 192.168.130.101 32...
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] iscsi failover MD3820i

[Marcin Kruk]

Hello I have got Dell MD3820i and four interfaces which was connected to
the hostst via switches.

But there is only one IP which I can set during the configuration of iSCSI
RHV storage.
Everything has been fine until I pluged off cable from the storage NIC
interface with IP configured in the RHV iSCSI section.

Now VDSMD got problem because it tries to connect via iscsiadm with exact
IP and does not use the configuration from the /var/lib/iscsi/, where are
tree extra paths to achive the LUN. In multipath -ll I see an active path,
of course with the second storage interface IP

systemctl status vdsmd:
   CGroup: /system.slice/vdsmd.service
   ├─4975 /usr/bin/python /usr/share/vdsm/vdsm
   ├─5558 /usr/bin/sudo -n /usr/sbin/iscsiadm -m node -T
iqn.1984-05.com.dell:powervault.md3800i.600a098000ae589c5893ade2 -I
default -p 192...
   └─5559 /usr/sbin/iscsiadm -m node -T
iqn.1984-05.com.dell:powervault.md3800i.600a098000ae589c5893ade2 -I
default -p 192.168.130.101 32...
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users