Forum Discussion
NimbostratusF5 AWS no internet access
Hello, I just deployed BYOL f5 in AWS, I managed to license it etc. I was following the guide available from f5, and everything was fine until I tried to ping 8.8.8.8 from f5 after the deployment. I have EIP attached to the secondary IP address on the external interface, but I can't ping anything outside of my network... I'm suspecting this has something to do with default GW, but I have it all setup correctly in aws, just not sure where to set it up in f5?
9 Replies
Lukasz_01_15307ok.. it looks like f5 thinks that default GW is through the management interface (eth0) and not the external one (eth1), how can i change that?
Karol_Biernack4Hey Lukasz, check in config if You have management-route somewhere
tmsh list /sys management-routeAnd then use this command to delete it
tmsh delete /sys management-route- Lukasz_01_15307
Hi Karol,
Now I'm getting network is unreachable instead of time out... please help
- Karol_Biernack4
Did you configure new route?
- Lukasz_01_15307
yes i did and it's working now... thanks, I was hoping aws will handle this automagically with subnet routes...
- Karol_Biernack4
Good to hear that :) Automagically - i like this word
Have a good day
- Lukasz_01_15307
Thanks! you too :)
It looks like now I can't access resources within my VPC... I have internal F5 interface and a veb server in dmz subnet and I can't ping the server from f5 or f5 from the server... what am I missing with f5, routing and AWS? I added one route to network -> Routes and it's dest 0.0.0.0 netmask 0.0.0.0 GW address going to IP address of 172.17.0.1... in "normal" environment and in my lab this works fine...
- Karol_Biernack4
Sadly i am not able to tell anything about AWS. (didn't played with it yet)
I think that this one should help you.
- Lukasz_01_15307
Thanks! :) I will have a look
