Skip to content

Commit 9e58ad1

Browse files
authored
Update walkthrough-direct-peering-type-conversions.md
1 parent 1b96bb8 commit 9e58ad1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/internet-peering/walkthrough-direct-peering-type-conversions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ Get answers to frequently asked questions.
113113

114114
**Q.** Is there an impact on traffic for the overall conversion?
115115

116-
**A.** The conversion process involves several stages. Not all the stages affect traffic. Tapering the traffic, configuring new policies for the type of peering, and allowing the traffic back happen serially when BGP and BFD are online. Combined these steps usually take approximately two hours if the peering partner completes their end of the configurations promptly.
116+
**A.** The conversion process involves several stages. Not all the stages affect traffic. Tapering the traffic, configuring new policies for the type of peering, and allowing the traffic back when BGP and BFD are online happen serially. Combined these steps usually take approximately two hours if the peering partner completes their end of the configurations promptly.
117117

118118
For voice interconnect conversions, ensure that the BFD setup is done on time to ensure minimal downtime. For conversions that involve a change in IP addresses, there's almost zero downtime because the traffic is seamlessly shifted to the session that has the new addresses. Then, the session that has the old IP addresses is shut down.
119119

0 commit comments

Comments
 (0)