rac2節點上配置iscsi 遇到iscsiadm: failing authentication, received incorrect username from target
在rac2節點上配置iscsi 連線共享儲存(使用openfiler做共享儲存)時遇到:
注意:192.168.0.222是openfiler伺服器ip
[root@rac2 nodes]# iscsiadm -m discovery -t st -p 192.168.0.222
iscsiadm: failing authentication, received incorrect username from target
iscsiadm: Login authentication failed with target
iscsiadm: discovery login to 192.168.0.222 failed, giving up
最終發現是/etc/iscsi/iscsid.conf 配置檔案的問題。
[root@rac2 nodes]# cat /etc/iscsi/iscsid.conf
#
# Open-iSCSI default configuration.
# Could be located at /etc/iscsi/iscsid.conf or ~/.iscsid.conf
#
# Note: To set any of these values for a specific node/session run
# the iscsiadm --mode node --op command for the value. See the README
# and man page for iscsiadm for details on the --op command.
#
################
# iSNS settings
################
# Address of iSNS server
#isns.address = 192.168.0.1
#isns.port = 3205
#############################
# NIC/HBA and driver settings
#############################
# open-iscsi can create a session and bind it to a NIC/HBA.
# To set this up see the example iface config file.
#*****************
# Startup settings
#*****************
# To request that the iscsi initd scripts startup a session set to "automatic".
# node.startup = automatic
#
# To manually startup the session set to "manual". The default is automatic.
node.startup = automatic
# *************
# CHAP Settings
# *************
# To enable CHAP authentication set node.session.auth.authmethod
# to CHAP. The default is None.
node.session.auth.authmethod = CHAP
#--以上1行需要
# To set a CHAP username and password for initiator
# authentication by the target(s), uncomment the following lines:
node.session.auth.username = iqn.1994-05.com.redhat:85c7a96862
node.session.auth.password = 85c7a96862
#--以上2行需要
# To set a CHAP username and password for target(s)
# authentication by the initiator, uncomment the following lines:
#node.session.auth.username_in = username_in
#node.session.auth.password_in = password_in
# To enable CHAP authentication for a discovery session to the target
# set discovery.sendtargets.auth.authmethod to CHAP. The default is None.
discovery.sendtargets.auth.authmethod = CHAP
#--以上1行需要
# To set a discovery session CHAP username and password for the initiator
# authentication by the target(s), uncomment the following lines:
discovery.sendtargets.auth.username = iqn.1994-05.com.redhat:85c7a96862
discovery.sendtargets.auth.password = 85c7a96862
#--以上2行需要
# To set a discovery session CHAP username and password for target(s)
# authentication by the initiator, uncomment the following lines:
#discovery.sendtargets.auth.username_in = username_in
#discovery.sendtargets.auth.password_in = password_in
#--請務必將以上兩行註釋掉,註釋掉後,service iscsi restart重啟iscsi服務
# ********
# Timeouts
# ********
#
# See the iSCSI REAME's Advanced Configuration section for tips
# on setting timeouts when using multipath or doing root over iSCSI.
#
# To specify the length of time to wait for session re-establishment
# before failing SCSI commands back to the application when running
# the Linux SCSI Layer error handler, edit the line.
# The value is in seconds and the default is 120 seconds.
node.session.timeo.replacement_timeout = 120
# To specify the time to wait for login to complete, edit the line.
# The value is in seconds and the default is 15 seconds.
node.conn[0].timeo.login_timeout = 15
# To specify the time to wait for logout to complete, edit the line.
# The value is in seconds and the default is 15 seconds.
node.conn[0].timeo.logout_timeout = 15
# Time interval to wait for on connection before sending a ping.
node.conn[0].timeo.noop_out_interval = 5
# To specify the time to wait for a Nop-out response before failing
# the connection, edit this line. Failing the connection will
# cause IO to be failed back to the SCSI layer. If using dm-multipath
# this will cause the IO to be failed to the multipath layer.
node.conn[0].timeo.noop_out_timeout = 5
#******
# Retry
#******
# To speficy the number of times iscsiadm should retry a login
# to the target when we first login, modify the following line.
# The default is 4. Valid values are any integer value. This only
# affects the initial login. Setting it to a high value can slow
# down the iscsi service startup. Setting it to a low value can
# cause a session to not get logged into, if there are distuptions
# during startup or if the network is not ready at that time.
node.session.initial_login_retry_max = 4
################################
# session and device queue depth
################################
# To control how many commands the session will queue set
# node.session.cmds_max to an integer between 2 and 2048 that is also
# a power of 2. The default is 128.
node.session.cmds_max = 128
# To control the device's queue depth set node.session.queue_depth
# to a value between 1 and 128. The default is 32.
node.session.queue_depth = 32
#***************
# iSCSI settings
#***************
# To enable R2T flow control (i.e., the initiator must wait for an R2T
# command before sending any data), uncomment the following line:
#
#node.session.iscsi.InitialR2T = Yes
#
# To disable R2T flow control (i.e., the initiator has an implied
# initial R2T of "FirstBurstLength" at offset 0), uncomment the following line:
#
# The defaults is No.
node.session.iscsi.InitialR2T = No
#
# To disable immediate data (i.e., the initiator does not send
# unsolicited data with the iSCSI command PDU), uncomment the following line:
#
#node.session.iscsi.ImmediateData = No
#
# To enable immediate data (i.e., the initiator sends unsolicited data
# with the iSCSI command packet), uncomment the following line:
#
# The default is Yes
node.session.iscsi.ImmediateData = Yes
# To specify the maximum number of unsolicited data bytes the initiator
# can send in an iSCSI PDU to a target, edit the following line.
#
# The value is the number of bytes in the range of 512 to (2^24-1) and
# the default is 262144
node.session.iscsi.FirstBurstLength = 262144
# To specify the maximum SCSI payload that the initiator will negotiate
# with the target for, edit the following line.
#
# The value is the number of bytes in the range of 512 to (2^24-1) and
# the defauls it 16776192
node.session.iscsi.MaxBurstLength = 16776192
# To specify the maximum number of data bytes the initiator can receive
# in an iSCSI PDU from a target, edit the following line.
#
# The value is the number of bytes in the range of 512 to (2^24-1) and
# the default is 131072
node.conn[0].iscsi.MaxRecvDataSegmentLength = 131072
# To specify the maximum number of data bytes the initiator can receive
# in an iSCSI PDU from a target during a discovery session, edit the
# following line.
#
# The value is the number of bytes in the range of 512 to (2^24-1) and
# the default is 32768
#
discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768
# To allow the targets to control the setting of the digest checking,
# with the initiator requesting a preference of enabling the checking, uncommen
# the following lines (Data digests are not supported and on ppc/ppc64
# both header and data digests are not supported.):
#node.conn[0].iscsi.HeaderDigest = CRC32C,None
#
# To allow the targets to control the setting of the digest checking,
# with the initiator requesting a preference of disabling the checking,
# uncomment the following lines:
#node.conn[0].iscsi.HeaderDigest = None,CRC32C
#
# To enable CRC32C digest checking for the header and/or data part of
# iSCSI PDUs, uncomment the following lines:
#node.conn[0].iscsi.HeaderDigest = CRC32C
#
# To disable digest checking for the header and/or data part of
# iSCSI PDUs, uncomment the following lines:
#node.conn[0].iscsi.HeaderDigest = None
#
# The default is to never use DataDigests and to allow the target to control
# the setting of the HeaderDigest checking with the initiator requesting
# a preference of disabling the checking.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/161195/viewspace-1054703/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Openfiler配置ISCSI Target及FC Target
- Win10系統怎麼連線iscsi target_Win10連線iscsi target的方法Win10
- Incorrect MEMORY_MAX_TARGET (> Available RAM) Can Lead To Database HangsAIDatabase
- LeetCode之All Paths From Source to Target(Kotlin)LeetCodeKotlin
- The last packet successfully received from the server was 2,625 milliseconds ago.ASTServerGo
- MySQL報錯Slave: received end packet from server, apparent master shutdownMySqlServerAPPAST
- SourceTreet提交時顯示remote: Incorrect username or password ( access token )(4種解決辦法)REM
- Linux中,如何配置iSCSI儲存?Linux
- iOS 配置多targetiOS
- You can‘t specify target table ‘Person‘ for update in FROM clause
- Connect SQL Server from Linux Client using Windows Authentication and troubleshoot stepsSQLServerLinuxclientWindows
- 因配置失誤 超1.3萬iSCSI儲存叢集已線上上暴露
- CentOS 7配置iSCSI共享儲存案例CentOS
- 在Linux中,如何配置iSCSI目標?Linux
- mysql中You can’t specify target table for update in FROM clMySql
- Unknown initial character set index ‘255‘ received from server. Initial client character set can beIndexServerclient
- rac新增節點容易遇到的問題
- MGR無法連線主節點Authentication plugin 'caching_sha2_password'Plugin
- iSCSI
- ElasticSearch(單節點)環境配置Elasticsearch
- mongodb主從仲裁節點配置MongoDB
- jenkins 節點配置使用小記Jenkins
- MongoDB修復config配置節點MongoDB
- 11g rac新增節點容易遇到的問題
- rac新增節點容易遇到的問題(11g)
- 節點 B 上的 Windows 防火牆未正確配置為故障轉移群集Windows防火牆
- 007.iSCSI伺服器CHAP雙向認證配置伺服器
- RHEL6 或CentOS 6配置共享儲存--使用iSCSICentOS
- URL username 屬性
- zookeeper單節點和叢集部署與配置
- springboot讀取自定義配置檔案節點Spring Boot
- Kubernetes Node 節點上的映象管理
- 編譯Android14遇到lunch不顯示target的問題編譯Android
- 【Lintcode】1789. Distinguish UsernameNGUI
- Windows 11.2.0.4 RAC安裝配置以及RAC新增節點Windows
- PinPoint單節點部署及客戶端配置方法客戶端
- Kubernetes安裝之九:配置node節點之kubelet
- [BUG反饋]username欄位的長度設定有點小問題。
- 如何確定計算節點能不能檢測到儲存節點上的磁碟