2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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?
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
beantwortet vor 2 Monaten
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor einem Jahr
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.