Citrix NetScaler EE, Руководство по установке и настройке

Страница: 333 / 1026

© 1999-2017 Citrix Systems, Inc. All rights reserved. p.333 https://docs.citrix.com
In the above illustration:
OSPF is configured between ME-BR1_Router and ME-DC_Router in area 0.
OSPF is configured between
ME-DC_Router
and
DC
in area 0.
Recommended Configurat ion: Recommended Configurat ion:
a. DC VW and ME-DC_Router on area0
b. ME-BR1_Router and ME-DC_Router on area0
c. BR1 VW and ME-BR1_Router on area0
On the ME-DC _Ro uter: On the ME-DC _Ro uter:
a.
Add, static route for 172.58.3.10/32(Virtual IP of BR1 for MPLS Link) through 172.58.6.1
b. Add, static route for 172.58.4.10/32(Virtual IP of BR1 for INET) through 172.58.5.1
Adding static routes prevents loop formation between the ME-DC_Router and DC SD-WAN appliance. If you do not add
static routes, the MCN forwards traffic to the ME-DC Router, and back from router to the MCN and this creates a loop
continuously.
The static routes which are not PBR routes but the destination Host IP based routes will traverse towards the right link to
be chosen from the DC side based on the path chosen and the encapsulation performed thereafter. Therefore, with these
static routes configured, the encapsulated packets with any destination Virtual IP of BR1 SD-WAN appliance would use
these links as per the best path selected by the DC MCN.
Add ACL to avoid loop formation when IPHOST routes are installed (if no static Virtual IPs configured):
a. If the IPHOST routes advertised by BR1 SD-WAN appliance are installed by the MCN router ME-DC_Router and not
added as static routes as mentioned above, there is a possibility of loop formation if the OSPF participating interface
(172.58.6.x) between ME-BR1_Router and ME-DC_Router goes down.