Harihara Sudhan Posted February 1, 2023 Share Posted February 1, 2023 After modifying the default route pointing to client interface, on every reboot it gets reverted back to management interface on AWS. How to overcome this? Link to comment Share on other sites More sharing options...
Guest Farhan Ali Posted February 9, 2023 Share Posted February 9, 2023 This is expected behavior of Netscaler on AWS. As it needs to do some api and metadata calls from NSIP and need internet access. A default route will be pointing to management interface 0/1 and it will be auto applied on reboot. You should design your topology in such a way that your backend servers are properly segregated with subnetting . Mac based forwarding is enabled on Netscaler which takes care of the return traffic.An enhancement is raised and in upcoming releases we will have the flexibility of modifying the default route to different interface. Will update further once the feature is ready Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now