public:iscsi:fixes
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| public:iscsi:fixes [2015/06/06 10:18] – added footer wiki.tk | public:iscsi:fixes [2015/10/29 12:42] (current) – [Checking the iSCSI configuration] wiki.tk | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ===== Fix iSCSI login errors ===== | ||
| + | A few solutions for iSCSI log-in errors are known. They are described in the next sections. | ||
| + | ==== Checking the iSCSI configuration ==== | ||
| + | If the iSCSI login was possible before and the configuration was not changed manually, a misconfiguration will not be very likely - especially when the configuration is distributed by Puppet.\\ | ||
| + | If Puppet is used and if in doubt, the configuration can be updated like so: | ||
| + | root@kvm55: | ||
| + | If a backup of the host was created with the help of rsnapshot, the iSCSI configuration can be compared to older configurations in order to find possible configuration errors. | ||
| + | In such a situation a detection of the configuration with the help of the command | ||
| + | root@kvm55: | ||
| + | has to be prevented, because the execution of the command will certainly overwrite the current configuration files thus possibly overwriting passwords stored in the configuration files ultimately. | ||
| + | |||
| + | If in doubt, compare the passwords contained in die iSCSI configuration with those (hopefully) stored in the password databse: | ||
| + | root@kvm55: | ||
| + | node.session.auth.username_in = hp3par30 | ||
| + | node.session.auth.password_in = OngunajG8thi7i | ||
| + | node.session.auth.username = Company_kvm55 | ||
| + | node.session.auth.password = aer2Do8faithiV | ||
| + | node.session.auth.username_in = hp3par30 | ||
| + | node.session.auth.password_in = OngunajG8thi7i | ||
| + | node.session.auth.username = Company_kvm55 | ||
| + | node.session.auth.password = aer2Do8faithiV | ||
| + | If the iSCSI configuration has to be adapted and Puppet is in use for the distribution of the configuration, | ||
| + | ==== Restart the iSCSI interfaces ==== | ||
| + | A complete restart of all iSCSI connections is possible like so: | ||
| + | root@kvm55: | ||
| + | root@kvm55: | ||
| + | root@kvm55: | ||
| + | If the iSCSI sessions don't get connected by '' | ||
| + | ==== Wait before another log-in trial ==== | ||
| + | Sometimes it is helpful to wait for 10 to 15 minutes before the next log-in trial. In some cases log-in was possible again after some waiting time. The reason for the time-out is unknown - maybe switches discard the MAC addresses after some time or the account will be locked temporarily after failed login attemtps. | ||
| + | ==== When all log-in trials fail ==== | ||
| + | In such a case it should be checked whether the log-in ever succeeded before. If this is not the case then maybe a wrong username or a wrong password was transferred to the user. If all else fails, ask the administrator to reset the password on the iSCSI device. Do not forget to update the configuration and the password in the password database afterwards! | ||
| + | ==== Assignment between iscsi LUNs and SCSI devices ==== | ||
| + | For further debugging it might be helpful to know the assignment between iSCSI LUNs and physical disks. The assignment can be displayed with the command | ||
| + | root@kvm55: | ||
| + | A display of the SCSI devices can look like so: | ||
| + | root@kvm55: | ||
| + | [4: | ||
| + | [5: | ||
| + | [5: | ||
| + | [5: | ||
| + | [6: | ||
| + | [6: | ||
| + | [6: | ||
| + | In the code above the device '/ | ||
| + | |||
| + | |||
| + | [[public: | ||