ES1640dc v2 and high availability

[camillo777]

Hi all,

QNAP ES1640dc v2
Firmware 2.0.0.0279

Anyone tested successfully high availability?

The appliance has 2 controllers SCA SCB.
Every controller has its own IP address to a 10Gb SFP+ fiber switches, say .9 (SCA) and .10 (SCB) .

I tried to copy via samba and ftp on the qnap via .9 ip, then removed the .9 network cable, I was expecting the copy to go on, but it stopped waiting and after some minutes went timeout; same on samba and ftp.

I started then the same copy but this time I rebooted the controller SCA and the same thing happened (copy failed).

While the controller SCA was rebooting I tried to connect to both .9 and .10 and to restart the copies, but sometimes it started, then stopped then permission error.... I had to wait both the 2 controllers were up and running again... means to me no high availability at all.

Did anyone make some good test?
How did you configure the HA options?

Thank you
Camillo

[storageman]

What is the HA page showing?
Does it say active/active? Post a screenshot.
What controller has control of the pool?

[camillo777]

What is the HA page showing?
Does it say active/active? Post a screenshot.
What controller has control of the pool?

Hi @storageman,
I tried to upload some screenshots here:

https://drive.google.com/drive/folders/ ... sp=sharing

Storage pool and shares are in charge of controller SCA.
Configuration seems active-active.
Both controller OK, SCA says Primary.

Thank you
Camillo

[storageman]

I can't see anything wrong in your settings, it should work as you have "Failover when network fails" ticked.
You could try disabling and enabling this option!?!?

When failover occurs .109 should transfer to SCB and continue.
Can you "ping xxx.xxx.xxx.109 -t" then pull the cable and see if the ping recovers as a test?

Sorry, I would raise ticket with Qnap.

[camillo777]

I can't see anything wrong in your settings, it should work as you have "Failover when network fails" ticked.
When failover occurs .109 should transfer to SCB and continue.
Can you "ping xxx.xxx.xxx.109 -t" then pull the cable and see if the ping recovers as a test?

Sorry, I would raise ticket with Qnap.

Hi @storageman,
the "ping" thing seemed to work ok, but on FTP and Samba I have got some issues: like timeout and permission denied....

And the storage pool is still in charge of SCA even if network is disconnected.
I added a new screenshot of HA:

https://drive.google.com/file/d/1hPhmLL ... sp=sharing

64 bytes from 10.102.35.109: icmp_seq=140 ttl=59 time=2.487 ms
64 bytes from 10.102.35.109: icmp_seq=141 ttl=59 time=2.118 ms
64 bytes from 10.102.35.109: icmp_seq=142 ttl=59 time=1.964 ms
Request timeout for icmp_seq 143
Request timeout for icmp_seq 144
Request timeout for icmp_seq 145
Request timeout for icmp_seq 146
Request timeout for icmp_seq 147
Request timeout for icmp_seq 148
Request timeout for icmp_seq 149
Request timeout for icmp_seq 150
Request timeout for icmp_seq 151
Request timeout for icmp_seq 152
Request timeout for icmp_seq 153
Request timeout for icmp_seq 154
Request timeout for icmp_seq 155
Request timeout for icmp_seq 156
Request timeout for icmp_seq 157
Request timeout for icmp_seq 158
Request timeout for icmp_seq 159
Request timeout for icmp_seq 160
Request timeout for icmp_seq 161
Request timeout for icmp_seq 162
Request timeout for icmp_seq 163
Request timeout for icmp_seq 164
Request timeout for icmp_seq 165
Request timeout for icmp_seq 166
Request timeout for icmp_seq 167
Request timeout for icmp_seq 168
Request timeout for icmp_seq 169
Request timeout for icmp_seq 170
Request timeout for icmp_seq 171
Request timeout for icmp_seq 172
Request timeout for icmp_seq 173
Request timeout for icmp_seq 174
Request timeout for icmp_seq 175
Request timeout for icmp_seq 176
Request timeout for icmp_seq 177
Request timeout for icmp_seq 178
Request timeout for icmp_seq 179
Request timeout for icmp_seq 180
Request timeout for icmp_seq 181
Request timeout for icmp_seq 182
Request timeout for icmp_seq 183
Request timeout for icmp_seq 184
Request timeout for icmp_seq 185
Request timeout for icmp_seq 186
Request timeout for icmp_seq 187
Request timeout for icmp_seq 188
Request timeout for icmp_seq 189
Request timeout for icmp_seq 190
Request timeout for icmp_seq 191
Request timeout for icmp_seq 192
Request timeout for icmp_seq 193
Request timeout for icmp_seq 194
Request timeout for icmp_seq 195
Request timeout for icmp_seq 196
Request timeout for icmp_seq 197
Request timeout for icmp_seq 198
Request timeout for icmp_seq 199
64 bytes from 10.102.35.109: icmp_seq=200 ttl=59 time=7.584 ms
64 bytes from 10.102.35.109: icmp_seq=201 ttl=59 time=128.103 ms
64 bytes from 10.102.35.109: icmp_seq=202 ttl=59 time=1.505 ms
64 bytes from 10.102.35.109: icmp_seq=203 ttl=59 time=2.094 ms
64 bytes from 10.102.35.109: icmp_seq=204 ttl=59 time=2.309 ms

[storageman]

I see "SCB takeover"
Looks like it's working to me. That's a pretty fast failover.
Not sure why you get other errors.