Direct Connect interconnect subnet sizes
My customer is a Direct Connect partner that provisioned a Direct Connect service for a customer and tied it into the customer's existing ELAN VPLS WAN. As I write this, I'm not sure what size subnet the customer is using on their WAN, but pretty sure it's shorter than a /30 :) What are the valid subnet sizes that we will accept on a private VIF?
Also, if you have any thoughts on this design, I'd be open to hearing them. Concerns I have: 1/ can the customer assign a subnet shorter than a /30 on the VIF, 2/ any spoke on the WAN can hit the Direct Connect; unsure if customer realizes/wants that.
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
It sounds like you are asking about a larger subnet. Since the BGP session is the only way to route beyond this subnet, The issue would be the VGW would not have the routes to anything other than the BGP peers routes or IPs directly on the subnet used for the WAN link and so it wouldnt have a return route to anything else. If you asking about a /31: I have configured a private VIF with a /31 between a VGW and Customer Router. IE 10.0.0.0/30 with 0. and .1 as the endpoint IPs
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren