Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
See matching posts in thread - BGP and VRF Export...
See matching posts in thread - default export policy for routi...
See matching posts in thread - RSVP next-hop for BGP VRF?
With multiple BGP policies in an import or export policy chain, it can become troublesome to determine what action will be taken for a particular prefix because the policies will usually not appear in the desired order within the policy-options hierarchy in the configuration
Three are three command-line arguments: neighbor - Specificy which BGP peer to view direction - Choose the import or export direction database - The policies can be viewed from either the committed database (the default), or the candidate database
If the path source is BGP , the route is imported to the VRF table from a BGP peer, either another control-node or an external bgp router such as an MX Series router
The following shows the basic configuration for interfaces, zones, and BGP: interfaces ( ge-0/0/4 ( description Untrust; unit 0 ( family inet ( address 200.200.200.2/30; ) ) ) ge-0/0/8 ( description Trust; unit 0 ( family inet ( address 172.16.0.1/24; ) ) ) ) protocols ( bgp ( group partner ( export conditional route; peer-as 1111; neighbor 200.200.200.1; ) group wan ( peer-as 65100; neighbor 172.16.0.2; ) ) ) routing-options ( autonomous-system 65100; ) security ( zones ( security-zone untrust ( interfaces ( ge-0/0/4.0 ( host-inbound-traffic ( protocols ( bgp; ) ) ) ) ) security-zone trust ( interfaces ( ge-0/0/8.0 ( host-inbound-traffic ( protocols ( bgp; ) ) ) ) ) ) ) The export policy conditional route is as follows: policy-options ( policy-statement conditional route ( term 1 ( from ( route-filter 1.1.1.0/24 exact; condition check route; ) then accept; ) then reject; ) ) The SRX Series device advertises 1.1.1.0/24 based on the condition labeled check route, shown as follows: policy-options ( condition check route ( if-route-exists ( 192.168.1.0/24; table inet.0; ) ) ) You must add 1.1.1.0/24 into the route table
1 Comment - no search term matches found in comments.
See matching posts in thread - Communities: target:100:1 Import Accepted VPN La...
See matching posts in thread - HI Team, i'm running ospf as PE(Juniper)-CE(Cisc...