Local Networks No Longer Being Propagated to AWS VPC Route Table

Updated this morning to 9.508-10 and have the same issue all our site-to-site links are broken

Is there is a workaround to this issue till Sophos figures this out?

Our entire operations are on a standstill since morning and I am going bonkers!!!

 https://community.sophos.com/kb/en-us/131832

Per support.. Try turning off all the BGP neighbors and turning them back on..

They said it will be fixed in next firmware

I also downloaded my AWS vpn configuration and it had new neighbor IPs in it..

I am still testing doesn't seem 100% yet. Also if you turn the site-to-site connection on and off it seems like you have to back to bgp and turn them off and on again.

On a side note I just noticed that connecting to multiple regions on AWS They give you different ASN numbers so I had to enable multiple ASN under advanced settings under BGP

Finally our network is up and running again. Thanks a ton Joseph! Your help is very much appreciated.

Thanks!

Hi, Could you guide me through those steps a little bit more. Where do I have to change the settings? 

I have the latest Config from AWS which has been readded to the Sophos but still no change.

BGP routes have been checked and look good. State is still idle and up/down shows never in BGB Global overview.

I have set it to Multi ASN.

Final edit to get it running - the default ASN for the gateway wasnt set to the same as in the config. Manually changed it to the one from the AWS Config and restarted both, VPC and BGP - all working now

Glad you got it up in running we really rely on these site to site things..

One thing I have noticed using multiple ASN.  

--If you have the same local networks on multiple ASN -- It will only propogate those routes to the first ASN. 

So I am connecting to east coast and west coast and my BGP routes are only showing up in one region. other region shows 0..

Not sure if that is just a bug in my config but doesn't seem right.

Using static routes in that region instead.

Hi All, 

I just had this fixed by getting a patch from support to 9.508-10 for my AWS UTM9. 

Kind Regards,

Rick 

Hi Rick and welcome to the UTM Community!

Thanks for sharing - that's helpful to me on a project I'm starting on next week.

Cheers - Bob