2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hi,
From looking at your stackoverflow post, I suspect the issue might be that you don't have the File System security group configured properly. Take a look at the link below for additional inbound rules to add:
https://docs.aws.amazon.com/fsx/latest/OpenZFSGuide/limit-access-security-groups.html
con risposta 2 anni fa
0
I am facing the same problem. I have the same VPC, same Availability Zone, and the communication within the VPC is fully permitted (0.0.0.0.0/0 all communication) by ACL. I applied a Security Group with full permission (0.0.0.0.0/0 all communication) to the EIP attached to FSx OpenZFS just to be sure, but I cannot communicate with both ping and nfs(2049).
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
Thanks Tom, I have just followed the link you were shared to create security group for Open ZFS file system. I added inbound rules custom TCP and UDP with port numbers : 111, 2049, 20001-20003 and added outbound rules to all. However, still I'm facing mount timed out error.
Any update on this? I have tried multiple time with Security group (Any where) for both EC2 and ZFS security group. However, no luck. Can any please help on this?
Hi Latchu, Happy new year! Have you tried running Reachability Analyzer, it can look at the path between your instance and the OpenZFS ENI, to determine if it is accessible based on your configuration. More details here: https://docs.aws.amazon.com/vpc/latest/reachability/getting-started.html
HI Tom, Yes i have checked with Reachability Analyzer for both TCP and RDP. Both are accessible. Where I'm wrong? I don't why connection timed-out even all ports are opened to anywhere in both EC2 and OpenZFS security group.