- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's because WAN1 is already being referenced in policies, routes etc.
You need to remove all references to WAN1 before you can then add it to the wan LLB.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Greetings, you must deactivate routes, policies and objects that are associated with that interface, so that you can appear in the WLLB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's because WAN1 is already being referenced in policies, routes etc.
You need to remove all references to WAN1 before you can then add it to the wan LLB.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Greetings, you must deactivate routes, policies and objects that are associated with that interface, so that you can appear in the WLLB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One way to preserve the policies, etc. instead of deleting them and starting over is to assign them to an unused interface. So, if they are something like INSIDE > OUTSIDE and going to WAN1, change them to go from INSIDE > internal4 temporariliy.
Then, when WAN1 is where you want it, you can change them back.
Easier to preserve things this way....
