BGP on Windows
BGP-ul a fost ceva ce s-a cerut de mult pe Windows. Si uite ca intr-un final, odata cu Windows Server 2012 R2, BGP-ul si-a facut aparitia si pe Windows.
Nu o sa gasiti nimic de configurat in interfata grafica, ci numai prin Powershell. Conditia este ca RRAS sa fie instalat. Documentatia pentru noile comenzi powershell pentru RRAS (si BGP bineinteles) o gasiti aici:
http://technet.microsoft.com/library/hh918399(v=wps.630).aspx
Iar daca sunteti pasionati de subiect va invit sa cititi si articolul urmator:
De unde am extras si urmatoarele specificatii:
Windows Server 2012 R2 – BGP capabilities
The above section gives an overview of the type of deployments supported by Windows BGP Router. These deployments however require the support of various BGP capabilities to work effectively. Following section lists all such capabilities that are presently supported in Windows BGP Router –
Internal BGP / External BGP support – Both iBGP and eBGP peering session supports are available. To configure either, the administrator has to make sure the appropriate AS Numbers have been assigned to the local and remote BGP Routers. Scenarios 1-4 employ the eBGP peering whereas scenario 4 uses iBGP peering as well.
Mixed / Passive Peering – Windows BGP Peering sessions can be configured as mixed or passive, i.e. it can act as either both Initiator and responder or as responder to incoming requests. The recommendation is to use the Mixed mode (default mode) for BGP peering unless it is being used for debugging / diagnostic purposes. All of the scenarios above are supposed to have Mixed mode peering to enable automatic restarts in case of failure events.
IPv4 and IPv6 transport peering support – Windows BGP Router supports both IPv4 and IPv6 peering. However, the BGP Identifier has to be configured as the IPv4 address of the BGP Router. The above scenarios can have any of the two peering types (IPV4 / IPv6).
IPv4 / IPv6 unicast route learning and advertisement capability (Multiprotocol NLRI) – Irrespective of the transport, Windows BGP Router is capable of exchanging IPv4 and IPv6 routes if the appropriate capability is announced while establishing the session. To configure IPv6 routing, parameter IPv6Routing has to be enabled and Local Global IPv6 address has to be configured at the router level.
Transit routing support – Windows BGP Router supports iBGP <-> iBGP and iBGP <-> eBGP transit routing. However, eBGP <-> eBGP transit routing support is not available as of yet. iBGP <-> eBGP transit routing is evident in all of the scenarios discussed in previous section.
Static route configuration support – Custom / static routes or interfaces can be configured on the Windows BGP Router via the available Add-BgpCustomRoute cmdlets. The routes being configured can be the prefixes or the name if the interfaces from which the routes have to be picked. However, only the routes with resolvable next-hops will be plumbed into the BGP routing tables and advertised to peers.
Equal Cost Multi Path Routing support – Windows BGP Router supports ECMP and can have more than one equal cost routes plumbed into the BGP routing table / stack. The decision to select the route for transmitting data packets in such cases is taken randomly in such cases.
Route filtering – Windows BGP router supports filtering ingress or egress route advertisements based on multiple route attributes such as
-
Prefix,
-
ASN-Range,
-
Community,
-
Next-Hop
Route Attribute re-write capability – Following attributes can be added, modified or removed from the ingress / egress route advertisements by using the BGP Routing policies
-
Next-Hop
-
MED
-
Local-Pref
-
Community
HoldTime and IdleHoldTime configuration – Windows BGP Router supports configuration of HoldTimer and IdleHoldTimer values as per the network requirements. It can be dynamically changed to accommodate interoperability with third party devices or to maintain a certain min / max time for reconnect (useful for failovers, route dampening etc.).
Route-Reflector client – Windows BGP Router can act as a Route-Reflector client, however it cannot be used to act as Route-Reflector itself. This is useful in cases where a new BGP Router needs to be introduced in complex topologies using third party BGP Routers deployed in RR mode.
Interoperability with 3rd party solutions – Windows BGP routing solution has been tested for interoperability with most of the major third party BGP routing devices (details in Interoperability with 3rdparty solutions section).
Route-Refresh support – Windows BGP Router supports Route-Refresh and advertises this capability on peering by default. It is capable of sending a fresh set of route updates when requested by a peer via route-refresh message.
BGP Statistics (Message counters, Route counters) – Windows BGP Router supports displaying the message and route statistics, if required, by using the Get-BgpStatistics cmdlet.