Linksys NSS2000 Cisco NSS2000 Series Network Storage System Administration Gui - Page 163

Free Bound Virtualized Storage when the Master System Fails, All CIFS Connections were Unexpectedly

Get Linksys NSS2000 - Gigabit Storage System Chassis PDF manuals and user guides
UPC - 745883577088
View all Linksys NSS2000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 163 highlights

Troubleshooting Free Bound Virtualized Storage when the Master System Fails A STEP 2 Go through the steps to upgrade the firmware ensuring that the conditions listed previously are met. Free Bound Virtualized Storage when the Master System Fails Problem Scenario: A storage system is bound to a failed storage system and rejects any bind requests from other systems. The steps to recreate this problem are as follows: STEP 1 Export storage from System A. STEP 2 Import storage from System A to System B. STEP 3 System B crashes and cannot be recovered. STEP 4 System A is "bound" to System B and rejects any new bind requests from other systems. Resolution: To resolve the problem: STEP 1 Unexport the bound storage system (in our example, System A). STEP 2 Re-export the storage system. The storage system is now available to be used by another system. All CIFS Connections were Unexpectedly Ended Problem: All current CIFS connections to the NSS were unexpectedly severed. Solution: Check if the hostname set up in the Network Identification page has been changed. Changing the hostname severs any current CIFS connections to the NSS. Cisco Small Business NSS2000 Series Administration Guide 155

  • 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
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
Troubleshooting
Free Bound Virtualized Storage when the Master System Fails
Cisco Small Business NSS2000 Series Administration Guide
155
A
STEP 2
Go through the steps to upgrade the firmware ensuring that the conditions listed
previously are met.
Free Bound Virtualized Storage when the Master System Fails
Problem Scenario:
A storage system is bound to a failed storage system and
rejects any bind requests from other systems. The steps to recreate this problem
are as follows:
STEP 1
Export storage from System A.
STEP 2
Import storage from System A to System B.
STEP 3
System B crashes and cannot be recovered.
STEP 4
System A is "bound" to System B and rejects any new bind requests from other
systems.
Resolution:
To resolve the problem:
STEP 1
Unexport the bound storage system (in our example, System A).
STEP 2
Re-export the storage system.
The storage system is now available to be used by another system.
All CIFS Connections were Unexpectedly Ended
Problem:
All current CIFS connections to the NSS were unexpectedly severed.
Solution:
Check if the hostname set up in the
Network Identification
page has been
changed. Changing the hostname severs any current CIFS connections to the NSS.