public:iscsi:login
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| public:iscsi:login [2015/06/06 10:15] – wiki.tk | public:iscsi:login [2015/06/12 14:56] (current) – wiki.tk | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ===== First connection to iSCSI targets ===== | ||
| + | The standard program for iSCSI management is the administration tool '' | ||
| + | root@kvm55: | ||
| + | Current active iSCSI sessions: | ||
| + | iscsiadm: No active sessions. | ||
| + | When the service is not active, it will be started: | ||
| + | root@kvm55: | ||
| + | * Starting iSCSI initiator service iscsid | ||
| + | * Setting up iSCSI targets | ||
| + | scsiadm: No records found | ||
| + | As minimum information for a log-in the IP address of the host is needed that exports iSCSI targets. With the help of the IP address the iSCSI targets are searched. When multipath is used, a query of the first IP address normally also finds the iSCSI targets on the second iSCSI path with the other IP address. | ||
| + | root@kvm55: | ||
| + | 10.48.2.10: | ||
| + | 10.48.2.11: | ||
| + | As a result of the query, the directory '/ | ||
| + | Some iSCSI targets already need a CHAP username and a pasword for an iSCSI discovery. In these cases the directory '/ | ||
| + | |||
| + | After successful log-in the login information should be added to the configuration files of the single nodes as described below and should be removed from the standard iSCSI configuration file. Otherwise it will not be possible to carry out an iSCSI discovery for an iSCSI target that possibly expects different login information. | ||
| + | |||
| + | In most cases a CHAP authentication for the iSCSI targets is used, in few cases also an authentication of the iSCSI initiator (so called mutual CHAP) is used. | ||
| + | |||
| + | For a successful log-in to an iSCSI target the configuration file ' | ||
| + | root@kvm55: | ||
| + | -T iqn.2000-05.com.3pardata: | ||
| + | --op=update --name node.session.auth.authmethod --value=CHAP | ||
| + | root@kvm55: | ||
| + | -T iqn.2000-05.com.3pardata: | ||
| + | --op=update --name node.session.auth.authmethod --value=CHAP | ||
| + | root@kvm55: | ||
| + | -T iqn.2000-05.com.3pardata: | ||
| + | --op=update --name node.session.auth.username --value=iscsiuser | ||
| + | root@kvm55: | ||
| + | -T iqn.2000-05.com.3pardata: | ||
| + | --op=update --name node.session.auth.username --value=iscsiuser | ||
| + | root@kvm55: | ||
| + | -T iqn.2000-05.com.3pardata: | ||
| + | --op=update --name name node.session.auth.password --value=password | ||
| + | root@kvm55: | ||
| + | -T iqn.2000-05.com.3pardata: | ||
| + | --op=update --name name node.session.auth.password --value=password | ||
| + | The values ' | ||
| + | |||
| + | Afterwards a log-in to the iSCSI targets is done. A separate log-in to every iSCSI target is possible | ||
| + | root@kvm55: | ||
| + | –T iqn.2000-05.com.3pardata: | ||
| + | … | ||
| + | root@kvm55: | ||
| + | –T iqn.2000-05.com.3pardata: | ||
| + | … | ||
| + | ... as well as a log-on to all targets simultaniously: | ||
| + | root@kvm55: | ||
| + | … | ||
| + | The precise content of the command output depends on the iSCSI target and therefore was not displayed here. In any case the output of every log-in trial has to contain ' | ||
| + | |||
| + | In the end, the success of the connection process is checked by displaying the active iSCSI sessions: | ||
| + | root@kvm55: | ||
| + | tcp: [1] 10.48.2.11: | ||
| + | tcp: [2] 10.48.2.10: | ||
| + | In case the connection has to be carried out at every boot, the configuration files have to be adapted accordingly: | ||
| + | root@kvm55: | ||
| + | | xargs –r0 sed –i ‘s/ | ||
| + | root@kvm55: | ||
| + | | xargs –r0 sed –i ‘s/ | ||
| + | |||
| + | [[public: | ||