Adding Static Route to Route Table Not Working

0

We have a BGP peering group setup with AWS and have most routes propagated. The propagated routes work great. However there are some routes that are not on the BGP device. We've added these other routes (separate data center) as static routes but that doesn't seem to be working. When pinging from this separate data center to AWS, there's no "reply" back if that makes sense. Anyone have any ideas as to why this route is not recognized?

質問済み 2ヶ月前474ビュー
2回答
0

Hello.

Is the added static route a CIDR that exists on the on-premises side?
Also, is that route registered in the customer gateway on the on-premises side?
If it is not registered, it may not be possible to route from the customer gateway.
Also, how about using the "tracert" command to check how far communication is reaching from AWS VPC?

profile picture
エキスパート
回答済み 2ヶ月前
profile picture
エキスパート
レビュー済み 2ヶ月前
  • Yes the static route exists on the on-premise side. The route was not explicitly on gateway on the on-premise side. We have since added it as a static route on the on-premise side but it's still not propagating the route to the AWS route table. Should it propagate immediately or does that take time to refresh? A tracert from AWS -> on-premise shows the route going externally and trying to come back in.

0

Direct connect donot support Static Routes. You have to advertise your other DC route from your router to AWS over direct connect using BGP.

Once AWS learn those routes as propagated. Only then it will work

回答済み 2ヶ月前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ