Awesome.
Thanks again. I went ahead and ran the below and it removed the deactivate
command and no impact 😊
"delete routing-options forwarding-table export exp-to-fwd"
show | compare
- inactive: forwarding-table {
- export exp-to-fwd;
- }
________________________________
From: juniper-nsp <[email protected]> on behalf of Eric Van
Tol <[email protected]>
Sent: Thursday, September 28, 2017 5:11 PM
To: [email protected]
Subject: Re: [j-nsp] deactivate routing-options forwarding-table
> I do see where it looks like an export policy was applied but there is
> nothing in it
>
> "set routing-options forwarding-table export exp-to-fwd"
>
> show configuration policy-options policy-statement exp-to-fwd (no output)
>
>
> show configuration | display set | match exp-to-fwd (only thing found)
> set routing-options forwarding-table export exp-to-fwd
My guess is that someone deleted the exp-to-fwd policy, tried to commit, and
saw it was being called from within the forwarding table. Rather than delete
that line, they deactivated it, perhaps with a reason, but there should be no
issues just removing that line altogether. The 'deactivate' just ignores the
configuration altogether, essentially the same as not having any explicit
forwarding-table configuration.
-evt
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
juniper-nsp Info Page -
puck.nether.net<https://puck.nether.net/mailman/listinfo/juniper-nsp>
puck.nether.net
To see the collection of prior postings to the list, visit the juniper-nsp
Archives. Using juniper-nsp: To post a message to all the list members ...
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
