File Storage

Al Hagopian posted 12-17-2018 15:49

Dan BradoSushant SawantVictor Abyad

you'll need to check NAS FW versions in use on the 4040 (and I'll assume for now this is a 2-node cluster).

plus you'll need to verify on the cli of the NAS that you have enabled the REST api (check rest-server-status and associated commands).

Mariusz Rendaszka posted 01-04-2019 10:54

problem solved.

I had to migrate evs-admin from ag1 aggregate to phisical ethernet eth1.

Now is OK.

Thaufik Jonhar posted 04-25-2019 04:18

Hi,

I also have the same problem with adding HNAS probe in HDCA.

login to REST API server validation and I see the error message:

[HNSEF273141C]: Validation failed.

Rest server status is running and enabled.

Node    Rest Server

----    -----------

1       running

2       running

RESTful API server is enabled.

evs-admin using port eth1.

But still failed to add the HNAS probe.

Any idea?

Thanks in advance.

Regards,

Thaufik

Al Hagopian posted 04-25-2019 12:00

Simon CroslandVictor AbyadSushant SawantDan Brado

We can see you are using a very old and outdated "private" management scheme (192.0.2.3) and I wager very little testing has been done using this outdated schema. Could it be a problem? It very well might be that way - also if this is a single node (not 2 node) then HDCA will not work (but that is in the process of being fixed). The private management schema was changed several years ago and you should contact your local team help with changing to a modern topology.

Additionally, please open a software case against HIAA/HDCA with diagnostics captured from probe and server to help facili

Peng Yu posted 08-12-2019 18:59

If the admin evs IP on your ethx is not pingable from probe server, then I think you need a "pingable" IP address to be added on another ethx for admin evs, then HDCA probe can connect to HNAS successful.

Nathan King posted 08-12-2019 19:49

For the REST Server IP Address:

Unified system addresses that work:

pnode addresses on the management network (mgmt1, mgmt2)

Admin EVS via the management network (controller1 or controller2) or an eth-agX port

30x0/4xx0 system addresses that work:

pnode addresses on the management network (eth0, eth1)

Admin EVS via the management network (eth0, eth1) or an eth-agX port

Does not work for any addresses directly on agX ports - including admin and file serving addresses

Only works with IPv4 addresses and not IPv6

Peng Yu posted 08-12-2019 20:05

That is exactly what I figured out. Thanks.