HP AM866A Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53-1000853-01, - Page 104

Authentication

Get HP AM866A - StorageWorks 8/8 Base SAN Switch PDF manuals and user guides
UPC - 884420064602
View all HP AM866A manuals
Add to My Manuals
Save this manual to your list of manuals

Page 104 highlights

11 Authentication Symptom Changes made to the iSCSI database do not appear on iSCSI hosts. Probable cause and recommended action The DDSet has not been enabled or the database has not been committed. Check the currently enabled DD Set using: iscsiCfg - -show ddset Make sure it is reported as enabled and committed. Enable an appropriate DDSet using: iscsiCfg - -enable ddset Check for open transactions using: iscsiCfg - -show transaction Commit any open transactions using: iscsicfg - -commit all -f Authentication Symptom Symptom Symptom Cannot set up mutual CHAP. Probable cause and recommended action A CHAP name that matches the IQN of an iSCSI initiator is treated differently in the CHAP database. When a CHAP name is set to the IQN of an iSCSI initiator, it will be used for initiator CHAP during mutual CHAP login. After an iSCSI host logs out of a target, it cannot log in to that target again. Probable cause and recommended action There is an inconsistency in the iSCSI database. Check using: iscsiCfg - -show fabric Make sure the aggregated state is in sync. If it is not in sync, fix the inconsistency and perform a commit using: iscsiCfg - -commit all iSCSI host can discover targets, but cannot log in to them. Probable cause and recommended action Zoning is enabled, but iSCSI virtual initiators are not in the same zone as the targets. Check zoning using cfgShow. Make sure iSCSI virtual initiators are in the same zone as the targets. Display the port WWN of the iSCSI virtual initiators using nsShow. 90 Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
90
Fabric OS Troubleshooting and Diagnostics Guide
53-1000853-01
Authentication
11
Symptom
Changes made to the iSCSI database do not appear on iSCSI hosts.
Probable cause and recommended action
The DDSet has not been enabled or the database has not been committed.
Check the currently enabled DD Set using:
iscsiCfg - -show ddset
Make sure it is reported as enabled and committed.
Enable an appropriate DDSet using:
iscsiCfg - -enable ddset
Check for open transactions using:
iscsiCfg - -show transaction
Commit any open transactions using:
iscsicfg - -commit all -f
Authentication
Symptom
Cannot set up mutual CHAP.
Probable cause and recommended action
A CHAP name that matches the IQN of an iSCSI initiator is treated differently in the CHAP database.
When a CHAP name is set to the IQN of an iSCSI initiator, it will be used for initiator CHAP during
mutual CHAP login.
Symptom
After an iSCSI host logs out of a target, it cannot log in to that target again.
Probable cause and recommended action
There is an inconsistency in the iSCSI database.
Check using:
iscsiCfg - -show fabric
Make sure the aggregated state is in sync.
If it is not in sync, fix the inconsistency and perform a commit using:
iscsiCfg - -commit all
Symptom
iSCSI host can discover targets, but cannot log in to them.
Probable cause and recommended action
Zoning is enabled, but iSCSI virtual initiators are not in the same zone as the targets.
Check zoning using
cfgShow
.
Make sure iSCSI virtual initiators are in the same zone as the targets. Display the port WWN of the
iSCSI virtual initiators using
nsShow
.