netappamazon-fsx

Getting "There is no connectivity" when trying to manage an FSxN File System within BlueXP


I added a FSxN file system to my BlueXP canvas a few weeks ago and it was working perfectly until yesterday. Now, when I try to "enter it" I am presented with a "There is no connectivity" error page.

enter image description here

I have confirmed that I can access the FSxN from the connector over both ports 22 and 443, so I don't think it is actually a connectivity problem. Regardless. I checked the Security Group and ACL rules and I'm not seeing anything that would hinder traffic flowing between the two systems.

If anyone has any ideas as to what else could be causing the problem, and/or where to look to diagnose the issue, I'd appreciate hearing them.


Solution

  • The problem you are seeing is when BlueXP has bad credentials for the fsxadmin user for the FSxN file system you are trying to manage. The simple fix is to simply remove the FSxN Working Environment from your canvas and add it back. When you do that, BlueXP should prompt you for the current password.

    Unfortunately, there is no way to just set the password for an FSxN file system like you can for a CVO. Well, that isn't entirely true, if you bring up your browser's developer's tools when the BlueXP console is prompting you for the password, after you fill in the password and click on “Submit", you will see what API it uses to set the password.

    Note that the remove and rediscover method only works if the FSxN file system is only in one workspace. If it is in multiple, you will have to either use the undocumented API mentioned above, or remove it from all the workspaces and then add it back.