![]() ![]() In terms of LAN BGP peering only default policy is applied which accept all received prefixes and advertise everything towards LAN segment. ![]() For the incoming updated from the MPLS router default policy is used which accept all prefixes. If you look closer at MPLS peer configuration, local DC prefix 172.16.1.0/24 is allow to be advertised to the peer and everything else is deny. You can match routes based on different BGP attributes. The default policy is to accept all routes. You can specify the direction to indicate if this policy is applied for incoming or outgoing routes. Policy is similar to creating a route map and ACL to match certain routes and configuring BGP attributes for that neighbor. In addition, policy for MPLS and Internet BGP peer was configured. In this example I have three BGP peering for each link configured on the appliance MPLS, LAN and Internet respectively. Next step is to configure BGP peers Configuration->Connections->BGP -Neighbors. Make sure that Advertise Citrix SD-WAN Routes option is tick, otherwise routes which are learned on the Citrix appliance won’t be advertised to other BGP peers. To configure dynamic BGP peering go to Configuration->Connections->BGP enable BGP process, provide BGP router-id and AS number. Let’s configure BGP at DC site first, for Branch side process will be exactly the same. I am going to use below topology to setup BGP for SD-WAN in in-line deployment and test some its functionalities. ![]() ![]() Also I am going to show how to create custom rule to match specific flow and steer such traffic over virtual path In this blog I will describe how to setup and configure BGP between Citrix SD-WAN appliance and rest of the network infrastructure when deploying Citrix SD-WAN in gateway deployment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |