Setting the local as number, Changing the maximum number of shared bgp4 paths, Treating missing meds as the worst meds – Brocade BigIron RX Series Configuration Guide User Manual

Page 923

Advertising
background image

BigIron RX Series Configuration Guide

845

53-1002484-04

Setting the local AS number

27

Setting the local AS number

The local AS number identifies the AS the Brocade BGP4 router is in.

To set the local AS number, enter commands such as the following.

BigIron RX(config)# router bgp

BGP4: Please configure 'local-as' parameter in order to enable BGP4.

BigIron RX(config-bgp)# local-as 10

BigIron RX(config-bgp)# write memory

Syntax: [no] local-as <num>

The <num> parameter specifies the local AS number 1 – 65535. There is no default. AS numbers
64512 – 65535 are the well-known private BGP4 AS numbers and are not advertised to the
Internet community.

Changing the maximum number of shared BGP4 paths

When IP load sharing is enabled, BGP4 can balance traffic to a specific destination across up to
eight equal paths. You can set the maximum number of paths to a value from 1 – 8. The default is
1.

NOTE

The maximum number of BGP4 load sharing paths cannot be greater than the maximum number of
IP load sharing paths. To increase the maximum number of IP load sharing paths, use the ip load
sharing <num> command at the global CONFIG level of the CLI or use the # of Paths field next to
Load Sharing on the IP configuration panel of the Web management interface.

To change the maximum number of shared paths, enter commands such as the following.

BigIron RX(config)# router bgp

BigIron RX(config-bgp)# maximum-paths 4

BigIron RX(config-bgp)# write memory

Syntax: [no] maximum-paths <number>

The <num> parameter specifies the maximum number of paths across which the BigIron RX can
balance traffic to a given BGP4 destination. You can change the maximum number of paths to a
value from 2 – 8. The default is 1.

Treating missing MEDs as the worst MEDs

By default, the BigIron RX favors a lower MED over a higher MED during MED comparison. Since the
device assigns the value 0 to a route path’s MED if the MED value is missing, the default MED
comparison results in the device favoring the route paths that are missing their MEDs.

To change this behavior so that the device favors a route that has a MED over a route that is
missing its MED, enter the following command at the BGP4 configuration level of the CLI.

BigIron RX(config-bgp)# med-missing-as-worst

Syntax: [no] med-missing-as-worst

Advertising