Storage Node og different network segment
I'm trying to set up a storage node on a separate network, but can't get my management server to connect to it properly. I've opened TCP and UDP ports 445,9876,9877 and 25001. A lot more than should be needed, but still I get the same error message when trying to access the vault.
I am able to connect to the storage node and create a managed vault, but if I try to validate it or choose it for a backup plan I get the following error.
Code: 10 092 557(0x9A000D)
LineInfo: 0x9A79F20828BC7F3;
Module: archive_manager_plugin_vs
Message: The vault is unavailable.
Code: 10 092 557(0x9A000D)
LineInfo: 0x90BBCA5EAF5C5C6E;
Module: archive_manager_plugin_vs
Message: The vault is unavailable.
Code: 2 555 963(0x27003B)
LineInfo: 0xAF0695FA9D426DB8;
Module: storage_server_vsa64
Message: Failed to obtain information about vault 'bsp://xxx.xxx.xxx.xxx/ASN'.
Code: 10 092 556(0x9A000C)
LineInfo: 0xAF0695FA9D426C61;
Module: storage_server_vsa64
Message: Invalid URI is specified: 'bsp://xxx.xxx.xxx.xxx/ASN'.
Code: 11 337 731(0xAD0003)
LineInfo: 0x67E2725E54112C8E;
Module: storage_server_vsa64
Module: storage_server_vsa64
Code: 11 337 745(0xAD0011)
LineInfo: 0x1C13ECEB383289A2;
Module: storage_server_vsa64
Message: Failed to connect to service 'ASN'. Destination host 'xxx.xxx.xxx.xxx' is unreachable.
Placing the storage node on the same lan as the management server solves the issue, so in my mind it has to be a communication issue. All sercurity features (firewall, antivirus etc.) are turned off for testing purposes.
The setup has been tried with several storage nodes and management severs, using different firewalls, but the result is always the same.
Are there any other ports that need to be opened? Any other ideas as to what could be the cause of this problem?
Thanks,
Thank you for your answer. Seems I got one step further :)
The obscured address is the public IP of the network where ASN is located. ASN was able to able connect with itself on port 9876 using the internal IP-address, but not the the public one. Added NAT loopback to the firewall and can now connect using the public address as well.
This has caused a new issue. Now the error message is gone, but the process seems to hang when trying to validate or use the vault. If I cancel the task and try to open the vault it just keeps loading forever. Both the ASM service on the Management Server and ANS service on the Storage Node are hung and have to be "killed" before restarting. Restarting them from services leaves them in a stopping state. After doing this I have to disconnect from the Storage Node and re-add it to be able to communicate correctly.
I have tried this scenario on two different Management Servers, using two different Storage Nodes, and the result is the same.
Any other suggestions as to what could be the cause of this problem?
Unfortunately not. If you're going to contact support regarding this issue, I'd suggest to wait for ABR11.5 release, because they will suggest you to update to it anyway if it is released during investigation. And problems with services lockups will take a while.
I've already contacted support and am going through the usual time consuming process of sending them logs, wait for a few days, reinstall and sending them logs again.
I have recreated the scenario on several AMS and ASN's, using the latest 4 builds of the software, and the result is always the same. I don't understand how this can work for anyone :)
If I set up a VPN connection between the two, so I can reach ASN on a local IP, everything works like a charm.
I guess I'll just have to be patient and will post here if I ever find a solution.