Ping from on-premise to all my EC2 instance has packet loss

0

I need to monitor all my EC2 instance using Nagios from on-premise using Ping but when It's shows packet loss nearly 30% many time. I checked my hardware performance include CPU or RAM it is okay. PS: I also monitor using Nagios with service Ping to other EC2 instance on my other account but it's working just fine.

2개 답변
0

I would start by investigating the connection from on-prem to AWS. Below are two guides that can help to troubleshoot the packet loss. How do I troubleshoot packet loss on my VPN connection? https://repost.aws/knowledge-center/troubleshoot-vpn-packet-loss How can I troubleshoot packet loss for my Direct Connect connection? https://repost.aws/knowledge-center/direct-connect-packet-loss

profile pictureAWS
Matt_E
답변함 일 년 전
  • Thanks, but I didn't use VPN connection nor Direct Connect connection because I ping to my EC2 instance Public IP

0

Hi, this very probably comes from the fact that your different EC2 instances are protected by different security groups: one allowing ICMP (ping) and the other not. So, please, identify those 2 sec groups and align them for ICMP.

See details to allow ping (specifically): https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/security-group-rules-reference.html#sg-rules-ping.

If groups are same, the second possible cause is absence of public IP for the failing one. See https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html#concepts-public-addresses to check if you have one for your instance and how to add it if not.

profile pictureAWS
전문가
답변함 일 년 전
profile picture
전문가
검토됨 일 년 전
  • Thanks, but my security group is okay because I can ping normally but I just concern because there is a packet loss sometime not 100% packet loss nor Request time out.

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠