Share via


RRAS: The total number of prefixes learned is in proximity of the Maximum Allowed Prefixes

 

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

Information

Category

Configuration

Issue

The threshold for the maximum allowed prefixes is about to be reached for the Border Gateway Protocol (BGP) Peer.

Impact

BGP Peering will be restarted and purge all of the previously learned routes.

Resolution

Reset or update the total number of MaxAllowedPrefix for the peer.

Membership in Administrators, or equivalent, is the minimum required to perform these procedures.

To reset the MaxAllowedPrefix value for a peer

  1. Run Windows PowerShell with Administrative privileges.

  2. You can use one of the following commands to either update the number of prefixes that can be learned from a peer or to remove the set limit on the number of prefixes that are learned.

    • Use this command to update the maximum number of prefixes that can be learned from a peer.

      Set-BgpPeer –Name <PeerName> -MaxAllowedPrefix <new count>
      
    • Use this command to remove the set limit of the number of prefixes that are learned.

      Set-BgpPeer –Name <PeerName> -ClearPrefixLimit