Atención :
La publicación que estás redactando aparecerá en un foro Público. Asegúrate de que todo el contenido sea apto para todo Público. Consulta los guidelines para empleados aquí en la comunidad.
I have been dealing with this error for the last 2 weeks. The policy will update just fine with the PBR flexconfig and then the next time a deployment takes place I get this error even if I didn't touch the flexconfig option. I have spent close to 2...
I am having this issue right now and TAC discovered the bug when I upgraded from 2.7 to 3.0.0 with patch 4. I would recommend upgrading to version 2.7 instead of 3.1. The cisco-av-pair worked just fine in 2.7, if I could travel back in time I would ...
When are PBR goes down all the Guest traffic then gets routed through the production network ISP automatically. I am not sure how you have your system setup. I would open a TAC case for assistance if the failover isn't working correctly.
I am assuming you have a HA pair? We use our PBR for out Guest network. We had to setup a second ip address under the monitored interfaces in the HA tab on the devices in FTD. Once we did that we did a failover to the secondary device and then went i...
Wow, 10 minutes, now I don't feel so bad :). I did try the prepend when we working working on the issue last month and the PBR got removed but it didn't get added back in which made it more frustrating. That was with 6.2.1 though so maybe they have f...
I do have it. I can use that as well if I want. Either option will do the same thing. The one difference is if I add the policy-based-routing-clear I will have to deploy 2 times instead of just once. I will have to deploy it to have that clear option...
