This could be another easy question regarding VPN setup.
Current situation:
All four networks below have PepVPN enabled using the default L3 bridging.
Network A: B20 (with five PepVPN licences activated)
Network B: B20 (default two PepVPN)
Network C: BR1
Network D: AC-mini
‘B’, ‘C’ and ‘D’ connects to ‘A’ located at the head office. ‘A’ manages three PepVPN profiles in total. ‘B’, ‘C’, and ‘D’ can all access each others via PepVPN, so far so good.
Problem:
‘A’ now becomes a central hub for all the VPN profiles. If ‘A’ is down due to power or broadband outage, then ‘B’, ‘C’ and ‘D’ will no longer be connected.
Question:
How do I configure the PepVPN so that ‘A’ will not be the central hub for all the VPN connections? In case ‘A’ is down, I want ‘B’, ‘C’ and ‘D’ to be able to maintain VPN connectivity.
Hi @sitloongs. I have two questions for you regarding this:
First: So, multiple routes to the same destination won’t’ cause a “spanning tree” type problem?
Second: In looking at the diagram you thoughtfully provided, how will the routes taken by the packets be chosen? Lowest latency, greatest bandwidth? Another way to ask the question: Suppose all links are operational. How will packets travel from A to B? On what basis will the decision be made? (I don’t recall reading anything about this in the PCE materials. )
When two Speedfusion profiles are created to the same endpoint you should set the metric for the 2nd profile at a higher value so that the primary route is preferred. That way all VPN traffic will flow between the BR1 and the B20 (A) unless it is unavailable then traffic will flow via B20 (B).
This i sthe Cost setting in the profile (default cost is 10):
)
