Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies To: Windows Server 2012 R2
This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the Remote Access Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.
Operating System |
Windows Server 2012 R2 |
Product/Feature |
Remote Access |
Severity |
Warning |
Category |
Configuration |
Issue
Border Gateway Protocol (BGP) peers are configured for manual peering.
Impact
The manual peering mode is meant for troubleshooting purposes. In this mode, unless you manually start the peer, the BGP peer cannot connect or reconnect.
Resolution
Change the peering mode for the BGP peer from Manual to Automatic.
Membership in Administrators, or equivalent, is the minimum required to perform these procedures.
To change a BGP peering mode
Run Windows PowerShell with Administrative privileges.
Change the BGP Peer’s Peering Mode by running the following command.
Set-BgpPeer –Name <Peer Name> -PeeringMode Automatic