Manual:Routing/BGP: Difference between revisions

From MikroTik Wiki
Jump to navigation Jump to search
Newer edit →
New page: <div class=manual> <h2>Summary</h2> <p> RFC 1771 -> RFC 4271<br /> <br /> Standards and Technologies: <ul> <li>RFC 4271 Border Gateway Protocol 4 <li>RFC 4456 BGP Route Reflection <li>RFC...
 
No edit summary
Line 22: Line 22:
<p><b>Sub-menu:</b> <code>/routing bgp instance</code></p>
<p><b>Sub-menu:</b> <code>/routing bgp instance</code></p>
<br />
<br />
<p><var><b>as</b></var> (<em>integer: 0..65535</em>; Default: <b></b>) - BGP autonomous system number</p>
<table class="styled_table">
<p><var><b>client-to-client-reflection</b></var> (<em>yes | no</em>; Default: <b>yes</b>) - in case this instance is a route reflector: whether to redistribute routes learned from one routing reflection client to other clients</p>
<tr>
<p><var><b>cluster-id</b></var> (<em>IP address</em>; Default: <b></b>) - in case this instance is a route reflector: cluster ID of the router reflector cluster this instance belongs to. This attribute helps to recognize routing updates that comes from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; this case 'cluster-id' does not need to be configured and BGP router ID is used instead</p>
  <th width="350">Property</th>
<p><var><b>confederation</b></var> (<em>integer: 0..65535</em>; Default: <b></b>) - in case of BGP confederations: autonomous system number that identifies the [local] confederation as a whole</p>
  <th >Description</th>
<p><var><b>confederation-peers</b></var> (<em>integer: 0..65535</em>; Default: <b></b>) - in case of BGP confederations: list of BGP peers internal to the [local] confederation</p>
</tr>
<p><var><b>ignore-as-path-len</b></var> (<em>yes | no</em>; Default: <b>no</b>) - whether to ignore AS_PATH attribute in BGP route selection algorithm</p>
<tr>
<p><var><b>name</b></var> (<em>string</em>; Default: <b>""</b>) - BGP instance name</p>
    <td><var><b>as</b></var> (<em>integer: 0..65535</em>; Default: <b></b>)</td>
<p><var><b>out-filter</b></var> (<em>string</em>; Default: <b>""</b>) - the output routing filter used by all BGP peers belonging to this instance</p>
    <td> BGP autonomous system number</td>
<p><var><b>redistribute-connected</b></var> (<em>yes | no</em>; Default: <b>no</b>) - if enabled, this BGP instance will redistribute the information about connected routes, i.e., routes to the networks that can be directly reached</p>
</tr>
<p><var><b>redistribute-ospf</b></var> (<em>yes | no</em>; Default: <b>no</b>) - if enabled, this BGP instance will redistribute the information about routes learned by OSPF </p>
<tr>
<p><var><b>redistribute-other-bgp</b></var> (<em>yes | no</em>; Default: <b>no</b>) - if enabled, this BGP instance will redistribute the information about routes learned by other BGP instances</p>
    <td><var><b>client-to-client-reflection</b></var> (<em>yes | no</em>; Default: <b>yes</b>)</td>
<p><var><b>redistribute-rip</b></var> (<em>yes | no</em>; Default: <b>no</b>) - if enabled, this BGP instance will redistribute the information about routes learned by RIP</p>
    <td> in case this instance is a route reflector: whether to redistribute routes learned from one routing reflection client to other clients</td>
<p><var><b>redistribute-static</b></var> (<em>yes | no</em>; Default: <b>no</b>) - if enabled, the router will redistribute the information about static routes added to its routing database, i.e., routes that have been created using the '/ip route add' command on the router</p>
</tr>
<p><var><b>router-id</b></var> (<em>IP address</em>; Default: <b>0.0.0.0</b>) - the BGP Router ID (for this instance). If not specified, BGP will use one of router's IP addresses.</p>
<tr>
    <td><var><b>cluster-id</b></var> (<em>IP address</em>; Default: <b></b>)</td>
    <td> in case this instance is a route reflector: cluster ID of the router reflector cluster this instance belongs to. This attribute helps to recognize routing updates that comes from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; this case 'cluster-id' does not need to be configured and BGP router ID is used instead</td>
</tr>
<tr>
    <td><var><b>confederation</b></var> (<em>integer: 0..65535</em>; Default: <b></b>)</td>
    <td> in case of BGP confederations: autonomous system number that identifies the [local] confederation as a whole</td>
</tr>
<tr>
    <td><var><b>confederation-peers</b></var> (<em>integer: 0..65535</em>; Default: <b></b>)</td>
    <td> in case of BGP confederations: list of BGP peers internal to the [local] confederation</td>
</tr>
<tr>
    <td><var><b>ignore-as-path-len</b></var> (<em>yes | no</em>; Default: <b>no</b>)</td>
    <td> whether to ignore <b>AS_PATH</b> attribute in BGP route selection algorithm</td>
</tr>
<tr>
    <td><var><b>name</b></var> (<em>string</em>; Default: <b>""</b>)</td>
    <td> BGP instance name</td>
</tr>
<tr>
    <td><var><b>out-filter</b></var> (<em>string</em>; Default: <b>""</b>)</td>
    <td> the output routing filter used by all BGP peers belonging to this instance</td>
</tr>
<tr>
    <td><var><b>redistribute-connected</b></var> (<em>yes | no</em>; Default: <b>no</b>)</td>
    <td> if enabled, this BGP instance will redistribute the information about connected routes, i.e., routes to the networks that can be directly reached</td>
</tr>
<tr>
    <td><var><b>redistribute-ospf</b></var> (<em>yes | no</em>; Default: <b>no</b>)</td>
    <td> if enabled, this BGP instance will redistribute the information about routes learned by OSPF </td>
</tr>
<tr>
    <td><var><b>redistribute-other-bgp</b></var> (<em>yes | no</em>; Default: <b>no</b>)</td>
    <td> if enabled, this BGP instance will redistribute the information about routes learned by other BGP instances</td>
</tr>
<tr>
    <td><var><b>redistribute-rip</b></var> (<em>yes | no</em>; Default: <b>no</b>)</td>
    <td> if enabled, this BGP instance will redistribute the information about routes learned by RIP</td>
</tr>
<tr>
    <td><var><b>redistribute-static</b></var> (<em>yes | no</em>; Default: <b>no</b>)</td>
    <td> if enabled, the router will redistribute the information about static routes added to its routing database, i.e., routes that have been created using the '/ip route add' command on the router</td>
</tr>
<tr>
    <td><var><b>router-id</b></var> (<em>IP address</em>; Default: <b>0.0.0.0</b>)</td>
    <td> the BGP Router ID (for this instance). If not specified, BGP will use one of router's IP addresses.</td>
</tr>
</table>
 
<br />


<h2>Peer</h2>
<h2>Peer</h2>
<p><b>Sub-menu:</b> <code>/routing bgp peer</code></p>
<p><b>Sub-menu:</b> <code>/routing bgp peer</code></p>
<br />
<br />


<h2>Advertisements</h2>
<h2>Advertisements</h2>
<p><b>Sub-menu:</b> <code>/routing bgp advertisements</code></p>
<p><b>Sub-menu:</b> <code>/routing bgp advertisements</code></p>
<br />
<br />


<h2>Network</h2>
<h2>Network</h2>
<p><b>Sub-menu:</b> <code>/routing bgp network</code></p>
<p><b>Sub-menu:</b> <code>/routing bgp network</code></p>
<br />
<br />


<h2>Aggregate</h2>
<h2>Aggregate</h2>
<p><b>Sub-menu:</b> <code>/routing bgp aggregate</code></p>
<p><b>Sub-menu:</b> <code>/routing bgp aggregate</code></p>
<br />
<br />


<h2>Vpnv4 route</h2>
<h2>Vpnv4 route</h2>
<p><b>Sub-menu:</b> <code>/routing bgp vpnv4-route</code></p>
<p><b>Sub-menu:</b> <code>/routing bgp vpnv4-route</code></p>
<br />
<br />


</div>
</div>

Revision as of 13:40, 12 November 2008

Summary

RFC 1771 -> RFC 4271

Standards and Technologies:

  • RFC 4271 Border Gateway Protocol 4
  • RFC 4456 BGP Route Reflection
  • RFC 1965 Autonomous System Confederations for BGP
  • RFC 1997 BGP Communities Attribute
  • RFC 2385 TCP MD5 Authentication for BGPv4
  • RFC 3392 Capabilities Advertisement with BGP-4
  • RFC 2918 Route Refresh Capability
  • RFC 2858 Multiprotocol Extensions for BGP-4
  • RFC 2545 Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing


Instance

Sub-menu: /routing bgp instance


Property Description
as (integer: 0..65535; Default: ) BGP autonomous system number
client-to-client-reflection (yes | no; Default: yes) in case this instance is a route reflector: whether to redistribute routes learned from one routing reflection client to other clients
cluster-id (IP address; Default: ) in case this instance is a route reflector: cluster ID of the router reflector cluster this instance belongs to. This attribute helps to recognize routing updates that comes from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; this case 'cluster-id' does not need to be configured and BGP router ID is used instead
confederation (integer: 0..65535; Default: ) in case of BGP confederations: autonomous system number that identifies the [local] confederation as a whole
confederation-peers (integer: 0..65535; Default: ) in case of BGP confederations: list of BGP peers internal to the [local] confederation
ignore-as-path-len (yes | no; Default: no) whether to ignore AS_PATH attribute in BGP route selection algorithm
name (string; Default: "") BGP instance name
out-filter (string; Default: "") the output routing filter used by all BGP peers belonging to this instance
redistribute-connected (yes | no; Default: no) if enabled, this BGP instance will redistribute the information about connected routes, i.e., routes to the networks that can be directly reached
redistribute-ospf (yes | no; Default: no) if enabled, this BGP instance will redistribute the information about routes learned by OSPF
redistribute-other-bgp (yes | no; Default: no) if enabled, this BGP instance will redistribute the information about routes learned by other BGP instances
redistribute-rip (yes | no; Default: no) if enabled, this BGP instance will redistribute the information about routes learned by RIP
redistribute-static (yes | no; Default: no) if enabled, the router will redistribute the information about static routes added to its routing database, i.e., routes that have been created using the '/ip route add' command on the router
router-id (IP address; Default: 0.0.0.0) the BGP Router ID (for this instance). If not specified, BGP will use one of router's IP addresses.


Peer

Sub-menu: /routing bgp peer



Advertisements

Sub-menu: /routing bgp advertisements



Network

Sub-menu: /routing bgp network



Aggregate

Sub-menu: /routing bgp aggregate



Vpnv4 route

Sub-menu: /routing bgp vpnv4-route



Retrieved from "https://wiki.mikrotik.com/index.php?title=Manual:Routing/BGP&oldid=9430"