283
Ignoring the ORIGINATOR_ID attribute
By default, BGP drops incoming route updates whose ORIGINATOR_ID attribute is the same as the
local router ID. Some special networks such as firewall networks require BGP to accept such route
updates. To meet the requirement, you must configure BGP to ignore the ORIGINATOR_ID attribute.
To ignore the ORIGINATOR_ID attribute (IPv4 unicast/multicast address family):
1. Enter system view.
system-view
N/A
2. Enter BGP instance view or
BGP-VPN instance view.
• Enter BGP instance view:
bgp as-number [ instance
instance-name ]
• Enter BGP-VPN instance
view:
a. bgp as-number
[ instance
instance-name ]
b. ip vpn-instance
N/A
3. Ignore the ORIGINATOR_ID
attribute.
peer
{ group-name | ipv4-address
[ mask-length ] }
ignore-originatorid
By default, BGP does not ignore
the ORIGINATOR_ID attribute.
Make sure this command does not
result in a routing loop.
After you execute this command,
BGP also ignores the
CLUSTER_LIST attribute.
To ignore the ORIGINATOR_ID attribute (IPv6 unicast/multicast address family):
1. Enter system view.
system-view
N/A
2. Enter BGP instance view or
BGP-VPN instance view.
• Enter BGP instance view:
bgp as-number [ instance
instance-name ]
• Enter BGP-VPN instance
view:
a. bgp as-number
[ instance
instance-name ]
b. ip vpn-instance
N/A
3. Ignore the ORIGINATOR_ID
attribute.
peer
{ group-name | ipv6-address
[ prefix-length ] }
ignore-originatorid
By default, BGP does not ignore
the ORIGINATOR_ID attribute.
Make sure this command does not
result in a routing loop.
After you execute this command,
BGP also ignores the
CLUSTER_LIST attribute.
Configuring a BGP confederation
BGP confederation provides another way to reduce IBGP connections in an AS.
To Next Page
Loading...
Need help?
General