Adding Static Route to Route Table Not Working

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?

主题

网络和内容交付

标签

亚马逊 VPC 网络和内容交付

语言

English

theotherPadawan

已提问 2 个月前475 查看次数

2 回答

最新
投票最多
评论最多

这些答案有用吗？为正确答案投票，以帮助社区从您的知识中受益。

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?

专家

Riku_Kobayashi

已回答 2 个月前

专家

Giovanni Lauria

已审核 2 个月前

theotherPadawan
1 个月前
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.

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

Muhammad-Muha

已回答 2 个月前

Adding Static Route to Route Table Not Working

相关内容