- Table of Contents
-
- 05-Network Connectivity Command Reference
- 00-Preface
- 01-MAC address table commands
- 02-Ethernet link aggregation commands
- 03-VLAN commands
- 04-Spanning tree commands
- 05-LLDP commands
- 06-Layer 2 forwarding commands
- 07-PPP commands
- 08-L2TP commands
- 09-ARP commands
- 10-IP addressing commands
- 11-DHCP commands
- 12-DHCPv6 commands
- 13-DNS commands
- 14-NAT commands
- 15-IP performance optimization commands
- 16-IPv6 basics commands
- 17-Tunneling commands
- 18-GRE commands
- 19-ADVPN commands
- 20-Basic IP routing commands
- 21-IP forwarding basics commands
- 22-Static routing commands
- 23-IPv6 static routing commands
- 24-RIP commands
- 25-Policy-based routing commands
- 26-IPv6 policy-based routing commands
- 27-OSPF commands
- 28-RIPng commands
- 29-BGP commands
- 30-IGMP snooping commands
- 31-MLD snooping commands
Title | Size | Download |
---|---|---|
29-BGP commands | 567.63 KB |
bgp update-delay on-startup prefix-list
display bgp routing-table flap-info
display bgp routing-table ipv4 unicast
display bgp routing-table ipv6 unicast
peer as-number (for a BGP peer group)
peer as-number (for a BGP peer)
BGP commands
address-family ipv4
Use address-family ipv4 to create the BGP IPv4 unicast address family and enter its view, or enter the view of the existing address family.
Use undo address-family ipv4 to remove the BGP IPv4 unicast address family and all its configurations.
address-family ipv4 [ unicast ]
undo address-family ipv4 [ unicast ]
No BGP IPv4 unicast address family exists.
network-admin
unicast: Specifies the IPv4 unicast address family. If this command is executed with the unicast keyword in BGP instance view, it places you into BGP IPv4 unicast address family view.
Configurations made in BGP IPv4 unicast address family view apply only to the BGP IPv4 unicast routes and peers of the public network.
By default, the unicast keyword is used if you do not specify the unicast keyword.
# In BGP instance view, create the BGP IPv4 unicast address family and enter its view.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4]
address-family ipv6
Use address-family ipv6 to create the BGP IPv6 unicast address family and enter its view, or enter the view of the existing address family.
Use undo address-family ipv6 to remove the BGP IPv6 unicast address family and all its configurations.
address-family ipv6 [ unicast ]
undo address-family ipv6 [ unicast ]
No BGP IPv6 unicast address family exists.
network-admin
unicast: Specifies the IPv6 unicast address family. If this command is executed with the unicast keyword in BGP instance view, it places you into BGP IPv6 unicast address family view.
Configurations made in BGP IPv6 unicast address family view apply only to the BGP IPv6 unicast routes and peers of the public network.
By default, the unicast keyword is used if the unicast keyword is not specified.
# In BGP instance view, create the BGP IPv6 unicast address family and enter its view.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv6 unicast
[Sysname-bgp-default-ipv6]
advertise-rib-active
Use advertise-rib-active to enable BGP to advertise only the optimal BGP routes in the IP routing table.
Use undo advertise-rib-active to restore the default.
advertise-rib-active
undo advertise-rib-active
In BGP instance view, BGP advertises optimal routes in the BGP routing table, regardless of whether they are optimal in the IP routing table. In other views, the setting is the same as that in BGP instance view.
BGP IPv4 unicast address family view
BGP IPv6 unicast address family view
network-admin
The advertise-rib-active command does not apply to the following routes:
· Routes redistributed by the import-route command.
· Routes advertised by the network command.
· Default routes redistributed by the default-route imported command.
This command takes effect only on the routes generated after you execute this command. To apply this command to existing routes, use the reset bgp command to reset BGP sessions.
The setting in BGP unicast address family view applies when it is different from that in BGP instance view.
# In BGP instance view, enable BGP to advertise optimal routes in the IP routing table.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] advertise-rib-active
aggregate
Use aggregate to create a summary route in the BGP routing table.
Use undo aggregate to remove a summary route.
In BGP IPv4 unicast address family view:
aggregate ipv4-address { mask-length | mask } [ as-set | detail-suppressed ] *
undo aggregate ipv4-address { mask-length | mask }
In BGP IPv6 unicast address family view:
aggregate ipv6-address prefix-length [ as-set | detail-suppressed ] *
undo aggregate ipv6-address prefix-length
No summary routes are configured.
BGP IPv4 unicast address family view
BGP IPv6 unicast address family view
network-admin
ipv4-address: Specifies an IPv4 summary address.
mask-length: Specifies a mask length for the IPv4 summary address, in the range of 0 to 32.
mask: Specifies a mask for the IPv4 summary address, in dotted decimal notation.
ipv6-address: Specifies an IPv6 summary address.
prefix-length: Specifies a prefix length for the IPv6 summary address, in the range of 0 to 128.
as-set: Enables the AS_PATH attribute of the summary route to contain the AS path information for all summarized routes. The AS_PATH attribute is of the AS_SET type that requires no sequence when arranging AS numbers. If you do not specify this keyword, the AS_PATH attribute of the summary route contains only the AS number of the local router.
detail-suppressed: Advertises only the summary route. If you do not specify this keyword, BGP advertises both the summary route and the more specific routes.
This command creates a summary route. If the BGP routing table has routes whose destination addresses fall within the specified network, the summary route is added to the BGP routing table. For example, if two routes 10.1.1.0/24 and 10.1.2.0/24 exist in the BGP routing table, configuring the aggregate 10.1.0.0 16 command creates a summary route 10.1.0.0/16.
If the summarized routes have different ORIGIN attributes, the summary route selects the ORIGIN attribute in the sequence of INCOMPLETE, EGP, and IGP. For example, if the ORIGIN attributes of the summarized routes include INCOMPLETE and IGP, the ORIGIN attribute of the summary route is INCOMPLETE.
The COMMUNITY attribute of the summary route includes all the COMMUNITY (or extended community) attribute values if the routes have the following details:
· Summarized routes have different COMMUNITY (or extended community) attribute values.
· The summary route does not have the ATOMIC_AGGREGATE attribute.
Table 1 Functions of the keywords
Keywords |
Function |
as-set |
Enables the summary route to carry the AS path information for all summarized routes. This feature can help avoid routing loops. However, if many routes are summarized and are changed frequently, do not specify this keyword. This configuration causes the summary route to flap with the more specific routes. |
detail-suppressed |
Disables advertisement of all more specific routes. To disable advertisement of some more specific routes, use the suppress-policy keyword or the peer filter-policy command. |
# In BGP IPv4 unicast address family view, create summary route 1.1.0.0/16 in the BGP routing table.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] aggregate 1.1.0.0 255.255.0.0
display bgp routing-table ipv4 unicast
display bgp routing-table ipv6 unicast
summary automatic
bgp
Use bgp to enable a BGP instance and enter its view.
Use undo bgp to disable a BGP instance.
bgp as-number [ instance instance-name ]
undo bgp [ as-number [ instance instance-name ] ]
BGP is disabled and no BGP instances exist.
network-admin
as-number: Specifies a local AS by its number in the range of 1 to 4294967295.
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command enables the BGP instance default.
A router supports 4-byte AS number.
A BGP router can run multiple BGP processes. Each BGP process corresponds to a BGP instance. BGP maintains an independent routing table for each BGP instance.
# Enable BGP instance default, set the local AS number to 100, and enter BGP instance view.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default]
bgp update-delay on-startup
Use bgp update-delay on-startup to configure BGP to delay sending route updates when it restores after a device reboot.
Use undo bgp update-delay on-startup to restore the default.
bgp update-delay on-startup seconds
undo bgp update-delay on-startup
BGP sends route updates immediately to BGP peers in established state when it restores after a device reboot.
network-admin
seconds: Specifies the delay time in the range of 0 to 3600 seconds. The value of 0 indicates that BGP does not send route updates after the device reboots and the process recovers.
With this command executed, BGP delays sending route updates when it restores after a device reboot. During the delay time, BGP finishes learning all routes from other peers, and then selects the optimal route. After the delay time elapses, BGP will advertise the optimal route. Using this command can reduce traffic loss caused by device reboot.
# In BGP instance view, configure BGP to delay sending route updates when it restores after a device reboot and set the delay time to 100 seconds.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] bgp update-delay on-startup 100
bgp update-delay on-startup prefix-list
bgp update-delay on-startup prefix-list
Use bgp update-delay on-startup prefix-list to configure BGP to immediately send route updates for routes that match a prefix list.
Use undo bgp update-delay on-startup prefix-list to restore the default.
bgp update-delay on-startup prefix-list ipv4-prefix-list-name
undo bgp update-delay on-startup prefix-list
No prefix list is specified to filter routes.
network-admin
ipv4-prefix-list-name: Specifies an IPv4 prefix list by its name, a case-sensitive string of 1 to 63 characters.
After the bgp update-delay on-startup command is configured, BGP delays sending updates for all routes when it restores after a device reboot. For BGP to immediately send updates for the specified routes, execute the bgp update-delay on-startup prefix-list command.
This command is available only to IPv4 prefix lists.
# In BGP instance view, configure BGP to send updates 100 seconds after it restores from a device reboot and immediately send updates for routes that match prefix list aaa.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] bgp update-delay on-startup 100
[Sysname-bgp-default] bgp update-delay on-startup prefix-list aaa
bgp update-delay on-startup
default-route imported
Use default-route imported to enable default route redistribution into the BGP routing table.
Use undo default-route imported to restore the default.
default-route imported
undo default-route imported
Default route redistribution into the BGP routing table is disabled.
BGP IPv4 unicast address family view
BGP IPv6 unicast address family view
network-admin
By default, BGP does not redistribute default IGP routes. To redistribute default IGP routes into the BGP routing table, you must use the default-route imported command together with the import-route command.
# In BGP IPv4 unicast address family view, enable default route redistribution from OSPF process 1 into the BGP routing table.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] default-route imported
[Sysname-bgp-default-ipv4] import-route ospf 1
import-route
display bgp group
Use display bgp group to display BGP peer group information.
display bgp [ instance instance-name ] group ipv4 [ unicast ] [ group-name group-name ]
display bgp [ instance instance-name ] group ipv6 [ unicast ] [ group-name group-name ]
network-admin
network-operator
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays BGP peer group information for the default BGP instance.
ipv4: Displays IPv4 BGP peer group information.
ipv6: Displays IPv6 BGP peer group information.
unicast: Displays BGP unicast peer group information.
group-name group-name: Specifies a BGP peer group by its name, a case-sensitive string of 1 to 47 characters. If you do not specify a group, this command displays brief information about all BGP peer groups for the specified address family.
By default, the unicast keyword is used if the unicast keyword is not specified.
# Display brief information about all BGP IPv4 unicast peer groups.
<Sysname> display bgp group ipv4
BGP peer group: group1
Remote AS: 600
Type: external
Members:
1.1.1.10
Remote AS number: not specified
Type: external
Members:
# Display detailed information about BGP IPv4 unicast peer group group1.
<Sysname> display bgp group ipv4 group-name group1
BGP peer group: group1
Remote AS: 600
Type: external
Maximum number of prefixes allowed: 4294967295
Threshold: 75%
Configured hold time: 180 seconds
Keepalive time: 60 seconds
Minimum time between advertisements: 30 seconds
Peer preferred value: 0
Site-of-Origin: Not specified
Routing policy configured:
No routing policy is configured
Members:
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
1.1.1.10 600 0 0 0 0 00:00:55 Established
# Display detailed information about BGP IPv6 unicast peer group group2.
<Sysname> display bgp group ipv6 group-name group2
BGP peer group: group2
Remote AS: 600
Type: external
Maximum number of prefixes allowed: 4294967295
Threshold: 75%
Configured hold time: 180 seconds
Keepalive time: 60 seconds
Minimum time between advertisements: 30 seconds
Peer preferred value: 0
Site-of-Origin: Not specified
Routing policy configured:
No routing policy is configured
Members:
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
2::2 600 0 0 0 0 00:00:45 Established
3::3 600 0 0 0 0 00:00:40 Established
Table 2 Command output
Field |
Description |
BGP peer group |
Name of the BGP peer group. |
Remote AS |
AS number of the peer group. |
Type |
Type of the peer groups: · external—EBGP peer group. · internal—IBGP peer group. |
Maximum number of prefixes allowed |
Maximum number of routes allowed to learn from the peer. |
Threshold |
Percentage of received routes from the peer to maximum routes allowed to learn from the peer. If the percentage is reached, the system generates a log message. |
Configured hold time |
Configured hold interval in seconds. |
Keepalive time |
Keepalive interval in seconds. |
Minimum time between advertisements |
Minimum route advertisement interval in seconds. |
Peer preferred value |
Preferred value specified for routes from the peer. |
Site-of-Origin |
SoO for the peer group. |
Routing policy configured |
This field is not supported in the current software version. Routing policy configured for the peer group. If you do not specify a routing policy, this field displays No routing policy is configured. |
Members |
Information about peers included in the peer group. |
* - Dynamically created peer |
An asterisk (*) before a peer address indicates that the peer is a dynamic peer. |
Peer |
IPv4 or IPv6 address of the peer. |
AS |
AS number of the peer. |
MsgRcvd |
Number of messages received. |
MsgSent |
Number of messages sent. |
OutQ |
Number of messages to be sent. |
PrefRcv |
For the IPv4 and IPv6 address families, this field displays the number of prefixes received from the peer. |
Up/Down |
Lasting time of the current BGP session state. |
State |
Current state of the BGP session between the local router and the peer. |
display bgp instance-info
Use display bgp instance-info to display information about all BGP instances.
display bgp instance-info
network-admin
network-operator
Examples
# Display information about all BGP instances.
<Sysname> display bgp instance-info
Total BGP instances: 3
BGP instance name AS
BGP1 100
BGP2 200
BGP3 300
Table 3 Command output
Field |
Description |
Total BGP instances |
Number of BGP instances. |
BGP instance name |
BGP instance name. |
AS |
AS number of the BGP instance. |
display bgp network
Use display bgp network to display information about routes advertised by the network command.
display bgp [ instance instance-name ] network { ipv4 | ipv6 } [ unicast ]
network-admin
network-operator
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays information for the default BGP instance.
ipv4: Displays IPv4 address family information.
ipv6: Displays IPv6 address family information.
unicast: Displays BGP unicast address family information.
Usage guidelines
By default, the unicast keyword is used if the unicast keyword is not specified.
# Display information about routes advertised by the network command in the IPv4 unicast address family.
<Sysname> display bgp network ipv4
BGP local router ID: 192.168.1.135
Local AS number: 100
Network Mask Route-policy Short-cut
20.1.1.0 255.255.255.0 No
40.1.1.0 255.255.255.0 abc No
30.1.1.0 255.255.255.0 Yes
# Display information about routes advertised by the network command in the IPv6 unicast address family.
<Sysname> display bgp network ipv6
BGP local router ID: 192.168.1.135
Local AS number: 100
Network PrefixLen Route-policy Short-cut
1:: 24 No
2:: 24 No
3:: 64 policy1 No
2:: 24 Yes
Table 4 Command output
Field |
Description |
Network |
Destination network address of the routes advertised by the network command. |
Mask |
Mask of the destination network address. |
PrefixLen |
Prefix length of the destination network address. |
Route-policy |
Routing policy that is applied to the route. |
Short-cut |
This field is not supported in the current software version. Whether the route is a shortcut route: · Yes. · No. |
display bgp paths
Use display bgp paths to display BGP path attribute information.
display bgp [ instance instance-name ] paths [ as-regular-expression ]
network-admin
network-operator
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays BGP path attribute information for the default BGP instance.
as-regular-expression: Displays information about BGP path attributes whose AS_PATH attribute matches the specified regular expression. The as-regular-expression argument is a string of 1 to 256 characters. If you do not specify this argument, the command displays information about all BGP path attributes.
Examples
# Display information about all BGP path attributes.
<Sysname> display bgp paths
RefCount MED Path/Origin
3 0 ?
2 0 100i
3 0 100i
1 0 ?
1 0 ?
1 0 ?
Table 5 Command output
Field |
Description |
RefCount |
Number of BGP routes with these path attributes. |
MED |
MULTI_EXIT_DISC attribute. |
Path/Origin |
AS_PATH and ORIGIN attributes of the route: · AS_PATH attribute—Records the ASs the route has passed, which avoids routing loops. · ORIGIN attribute—Identifies the origin of the route: ¡ i—Originated in the AS. The origin of routes advertised with the network command is IGP. ¡ e—Learned through EGP. ¡ ?—Unknown origin. The origin of routes redistributed from IGP protocols is INCOMPLETE. |
display bgp peer
Use display bgp peer to display BGP peer or peer group information.
display bgp [ instance instance-name ] peer ipv4 [ unicast ] [ ipv4-address mask-length | { ipv4-address | group-name group-name } log-info | [ ipv4-address ] verbose ]
display bgp [ instance instance-name ] peer ipv6 [ unicast ] [ ipv6-address prefix-length | { ipv6-address | group-name group-name } log-info | [ ipv6-address ] verbose ]
display bgp [ instance instance-name ] peer ipv4 [ unicast ] [ ipv6-address prefix-length | ipv6-address log-info | [ ipv6-address ] verbose ]
network-admin
network-operator
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays BGP peer or peer group information for the default BGP instance.
ipv4: Displays IPv4 BGP peer or peer group information.
ipv6: Displays IPv6 BGP peer or peer group information.
unicast: Displays BGP unicast peer or peer group information.
ipv4-address mask-length: Specifies a subnet. The value range for the mask length is 0 to 32. If you specify a subnet, this command displays information about all dynamic peers in the subnet.
ipv4-address: Specifies a peer by its IPv4 address.
ipv6-address prefix-length: Specifies a subnet. The value range for the prefix length is 0 to 128. If you specify a subnet, this command displays information about all dynamic peers in the subnet.
ipv6-address: Specifies a peer by its IPv6 address.
group-name group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters.
log-info: Displays log information.
verbose: Displays detailed information. If you do not specify this keyword, the command displays brief BGP peer or peer group information.
If you do not specify any parameters, this command displays brief information about all BGP peers for the specified address family.
By default, the unicast keyword is used if the unicast keyword is not specified.
# Display brief information about all BGP IPv4 unicast peers.
<Sysname> display bgp peer ipv4
BGP local router ID: 192.168.100.1
Local AS number: 100
Total number of peers: 1 Peers in established state: 1
* - Dynamically created peer
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
10.2.1.2 200 13 16 0 0 00:10:34 Established
Table 6 Command output
Field |
Description |
* - Dynamically created peer |
An asterisk (*) before a peer address indicates that the peer is a dynamic peer. |
Peer |
IPv4 or IPv6 address of the peer. |
AS |
AS number of the peer. |
MsgRcvd |
Number of messages received. |
MsgSent |
Number of messages sent. |
OutQ |
Number of messages to be sent. |
PrefRcv |
For the IPv4 and IPv6 address families, this field displays the number of prefixes that have been received from the peer and added into the local BGP routing table. |
Up/Down |
Lasting time of the current BGP session state. |
State |
Current state of the BGP session between the local router and the peer. |
# Display brief information about all dynamic peers in network 1.1.1.0/24.
<Sysname> display bgp peer ipv4 1.1.1.0 24
Dynamic address range: 1.1.1.0 24
Configured: Active Hold Time: 3 sec Keepalive Time: 1 sec
Address family IPv4 Unicast: Configured
Address family IPv4 Label: Configured
Address family IPv6 Unicast: Configured
Maximum allowed prefix number: 100
Threshold: 75%
Minimum time between advertisements is 100 seconds
Optional capabilities:
Multi-protocol extended capability has been enabled
Route refresh capability has been enabled
Nexthop self has been configured
Keep-all-routes has been configured
Send community has been configured
Send extend community has been configured
Default route originating has been configured
Multi-hop ebgp has been enabled
Peer preferred value: 100
BFD: Enabled
Site-of-Origin: 1:1
Routing policy configured:
No import as-path-acl list
Export as-path-acl list is: 22
No import prefix list
Export prefix list is: p1
No import route policy
Export route policy is: p1
No import filter-policy
No export filter-policy
Dynamic peers:
# Display brief information about all dynamic peers in network 1::/64.
<Sysname> display bgp peer ipv6 1:: 64
Dynamic address range: 1:: 64
Configured: Active Hold Time: 180 sec Keepalive Time: 60 sec
Address family IPv6 Unicast: Configured
Maximum allowed prefix number: 4294967295
Threshold: 75%
Minimum time between advertisements is 15 seconds
Optional capabilities:
Multi-protocol extended capability has been enabled
Route refresh capability has been enabled
Send community has been configured
Peer preferred value: 0
Site-of-Origin: Not specified
Routing policy configured:
No routing policy is configured
Dynamic peers:
1::1
Table 7 Command output
Field |
Description |
Type |
BGP connection type between the local router and the dynamic peer: · IBGP link—IBGP connection. · EBGP link—EBGP connection. |
Configured |
Timers configured on the local router in seconds, including the hold time (Active Hold Time) and keepalive interval (Keepalive Time). |
Address family IPv4 Unicast |
IPv4 unicast address family capability. |
Address family IPv6 Unicast |
IPv6 unicast address family capability. |
Maximum allowed prefix number |
Maximum number of routes allowed to learn from the peer. |
Threshold |
Percentage of received routes from the peer to maximum routes allowed to learn from the peer. If the percentage is reached, the system generates alarm messages. |
Minimum time between advertisements |
Minimum route advertisement interval in seconds. |
Optional capabilities |
Optional capabilities supported by the local end. |
Peer Preferred Value |
Preferred value specified for the routes from the peer. |
BFD |
Whether BFD is enabled to detect the link to the BGP peers. |
Routing policy configured |
This field is not supported in the current software version. Routing policy configured for the peer. If you do not specify a routing policy, this field displays No routing policy is configured. |
Dynamic peers |
IP addresses of dynamic peers. |
# Display detailed information about BGP IPv4 unicast peer 10.2.1.2.
<Sysname> display bgp peer ipv4 10.2.1.2 verbose
Peer: 10.2.1.2 Local: 192.168.100.1
BGP version 4, remote router ID 192.168.100.2
BGP current state: Established, Up for 00h11m10s
BGP current event: RecvKeepalive
BGP last state: OpenConfirm
Port: Local - 179 Remote - 60672
Configured: Active Hold Time: 180 sec Keepalive Time: 60 sec
Received : Active Hold Time: 180 sec
Negotiated: Active Hold Time: 180 sec Keepalive Time: 60 sec
Peer optional capabilities:
Peer supports BGP multi-protocol extension
Peer supports BGP route refresh capability
Peer supports BGP route AS4 capability
Address family IPv4 Unicast: advertised and received
InQ updates: 0, OutQ updates: 0
NLRI statistics:
Rcvd: UnReach NLRI 0, Reach NLRI 0
Sent: UnReach NLRI 0, Reach NLRI 0
Message statistics:
Msg type Last rcvd time/ Current rcvd count/ History rcvd count/
Last sent time Current sent count History sent count
Open 10:38:50-2013.7.23 1 1
10:38:50-2013.7.23 1 1
Update 10:38:51-2013.7.23 1 1
10:38:51-2013.7.23 1 1
Notification - 0 0
- 0 0
Keepalive 10:38:50-2013.7.23 1 1
10:38:50-2013.7.23 1 1
RouteRefresh - 0 0
- 0 0
Total - 3 3
- 3 3
Maximum allowed prefix number: 4294967295
Threshold: 75%
Minimum time between advertisements is 30 seconds
Optional capabilities:
Multi-protocol extended capability has been enabled
Route refresh capability has been enabled
GTSM has been enabled, and the maximum number of hops is 10
BFD: Enabled
Site-of-Origin: Not specified
Routing policy configured:
No routing policy is configured
# Display detailed information about BGP IPv6 unicast peer 1::2.
<Sysname> display bgp peer ipv6 1::2 verbose
Peer: 1::2 Local: 192.168.1.136
Type: EBGP link
BGP version 4, remote router ID 192.168.1.135
BGP current state: Established, Up for 00h05m48s
BGP current event: RecvKeepalive
BGP last state: OpenConfirm
Port: Local - 13184 Remote - 179
Configured: Active Hold Time: 180 sec Keepalive Time: 60 sec
Received : Active Hold Time: 180 sec
Negotiated: Active Hold Time: 180 sec Keepalive Time: 60 sec
Peer optional capabilities:
Peer supports BGP multi-protocol extension
Peer supports BGP route refresh capability
Peer supports BGP route AS4 capability
Address family IPv6 Unicast: advertised and received
InQ updates: 0, OutQ updates: 0
NLRI statistics:
Rcvd: UnReach NLRI 0, Reach NLRI 0
Sent: UnReach NLRI 0, Reach NLRI 3
Message statistics:
Msg type Last rcvd time/ Current rcvd count/ History rcvd count/
Last sent time Current sent count History sent count
Open 18:59:15-2013.4.24 1 1
18:59:15-2013.4.24 1 2
Update - 0 0
18:59:16-2013.4.24 1 1
Notification - 0 0
18:59:15-2013.4.24 0 1
Keepalive 18:59:15-2013.4.24 1 1
18:59:15-2013.4.24 1 1
RouteRefresh - 0 0
- 0 0
Total - 2 2
- 3 5
Maximum allowed prefix number: 4294967295
Threshold: 75%
Minimum time between advertisements is 30 seconds
Optional capabilities:
Multi-protocol extended capability has been enabled
Route refresh capability has been enabled
GTSM has been enabled, and the maximum number of hops is 10
BFD: Enabled
Site-of-Origin: Not specified
Routing policy configured:
No routing policy is configured
Table 8 Command output
Field |
Description |
|
Peer |
IPv4 or IPv6 address of the peer. |
|
Local |
Local router ID. |
|
Type |
BGP connection type between the local router and the peer: · IBGP link—IBGP connection. · EBGP link—EBGP connection. |
|
remote router ID |
Router ID of the peer. |
|
BGP current state |
Current state of the BGP session between the local router and the peer. |
|
Up for |
Lasting time of the BGP session. |
|
BGP current event |
Current event of the BGP session between the local router and the peer. |
|
BGP last state |
Previous state of the BGP session. |
|
Port |
TCP port numbers of the local router and its peer. |
|
Configured |
Timers configured on the local router in seconds, including the hold time (Active Hold Time) and keepalive interval (Keepalive Time). |
|
Received |
Received timer (configured on the peer) in seconds, including the hold time (Active Hold Time). |
|
Negotiated |
Negotiated timers in seconds, including the hold time (Active Hold Time) and keepalive interval (Keepalive Time). |
|
Peer optional capabilities |
Optional capabilities supported by the peer. |
|
Peer supports BGP route AS4 capability |
The peer supports 4-byte AS number. |
|
Address family IPv4 Unicast |
IPv4 unicast address family capability: routes of the address family can be advertised and received. |
|
Address family IPv6 Unicast |
IPv6 unicast address family capability: routes of the address family can be advertised and received. |
|
InQ updates |
Number of received updates to be processed. |
|
OutQ updates |
Number of updates to be sent to the peer. |
|
NLRI statistics |
Number of the reachable and unreachable routes received from and sent to the peer after the BGP session is established. |
|
Message statistics |
BGP message statistics. |
|
Msg type |
BGP message type. |
|
Last rcvd time/Last sent time |
Time when the most recent BGP message was received from or sent to the peer. |
|
Current rcvd count/Current sent count |
Number of BGP messages received from or sent to the peer on the current BGP session. |
|
History rcvd count/History sent count |
Number of BGP messages received from or sent to the peer since the BGP peer relationship was established. |
|
Total |
Total number of received and sent messages. |
|
Maximum allowed prefix number |
Maximum number of routes allowed to learn from the peer. |
|
Threshold |
Percentage of received routes from the peer to maximum routes allowed to learn from the peer. If the percentage is reached, the system generates alarm messages. |
|
Minimum time between advertisements |
Minimum route advertisement interval in seconds. |
|
Optional capabilities |
Optional capabilities supported by the local end. |
|
Peer Preferred Value |
Preferred value specified for the routes from the peer. |
|
the maximum number of hops |
Maximum number of hops to the specified peer. |
|
BFD |
Whether BFD is enabled to detect the link to the BGP peer. |
|
Routing policy configured |
This field is not supported in the current software version. Routing policy configured for the peer. If you do not specify a routing policy, this field displays No routing policy is configured. |
|
# Display log information for BGP IPv4 unicast peer 1.1.1.1.
<Sysname> display bgp peer ipv4 1.1.1.1 log-info
Date Time State Notification
Error/SubError
06-Feb-2013 22:54:42 Down Send notification with error 6/4
<administrative reset>
Table 9 Command output
Field |
Description |
Peer |
IPv4 or IPv6 address of the peer. |
Date |
Date on which the Notification was sent or received. |
Time |
Time at which the Notification was sent or received. |
State |
BGP session state: · Up—The BGP session is in Established state. · Down—The BGP session is down. |
Notification Error/SubError |
Error code of the Notification, indicating the cause of why the BGP session was down. · Error—Refers to the error code, which identifies the type of the Notification. · SubError—Refers to the error subcode of the Notification, which identifies the specific information about the reported error. |
display bgp routing-table flap-info
Use display bgp routing-table flap-info to display BGP route flap statistics.
display bgp [ instance instance-name ] routing-table flap-info ipv4 [ unicast ] [ ipv4-address [ { mask-length | mask } [ longest-match ] ] | as-path-acl as-path-acl-number ]
display bgp [ instance instance-name ] routing-table flap-info ipv6 [ unicast ] [ ipv6-address prefix-length | as-path-acl as-path-acl-number ]
network-admin
network-operator
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays BGP route flap statistics for the default BGP instance.
ipv4: Displays BGP IPv4 route flap statistics.
ipv6: Displays BGP IPv6 route flap statistics.
unicast: Displays BGP unicast route flap statistics.
ipv4-address: Specifies a destination network address.
mask-length: Specifies a mask length in the range of 0 to 32.
mask: Specifies a network mask in dotted decimal notation.
longest-match: Specifies longest match mode, which selects the longest matching route through the following steps:
1. ANDs the specified network address with the mask of each route.
2. Matches a route if the AND result is the same as the network address of the route and the mask of the route is shorter than or equal to the specified mask.
3. Selects the route with the longest mask among the matching routes.
ipv6-address prefix-length: Displays route flap statistics for BGP IPv6 routes that match the specified network address, and match the prefix length in the range of 0 to 128.
as-path-acl as-path-acl-number: Displays route flap statistics for BGP routes that match the AS path list specified by its number in the range of 1 to 256.
If you specify only the ipv4-address argument, the system ANDs the network address with the mask of a BGP IPv4 unicast route. If the result matches the network address of the route, the command displays flap statistics of the route.
If you specify the ipv4-address mask or ipv4-address mask-length argument, and do not specify the longest-match keyword, the command displays flap statistics of the BGP IPv4 unicast route that matches both the specified destination network address and the mask (or mask length).
By default, the unicast keyword is used.
# Display BGP IPv4 unicast route flap statistics.
<Sysname> display bgp routing-table flap-info ipv4
BGP local router ID is 192.168.1.135
Status codes: * - valid, > - best, d - dampened, h - history
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network From Flaps Duration Reuse Path/Ogn
de 20.1.1.0/24 10.1.1.2 1 00:02:36 00:53:58 100i
# Display BGP IPv6 unicast route flap statistics.
<Sysname> display bgp routing-table flap-info ipv6
BGP local router ID is 192.168.1.135
Status codes: * - valid, > - best, d - dampened, h - history
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
de Network : 2:: PrefixLen : 64
Duration: 00:03:25 Reuse : 00:39:28
Path/Ogn: 100i
de Network : 2:: PrefixLen : 64
Duration: 00:03:25 Reuse : 00:39:28
Path/Ogn: 100i
Table 10 Command output
Field |
Description |
Status codes |
Status codes: · * – valid—Valid route. · > – best—Optimal route. · d – dampened—Dampened route. · h – history—History route. · s – suppressed—Suppressed route. · S – stale—Stale route. · i – internal—Internal route. · e – external—External route. |
Origin |
Origin of the route: · i – IGP—Originated in the AS. The origin of routes advertised with the network command is IGP. · e – EGP—Learned through EGP. · ?– incomplete—Unknown origin. The origin of routes redistributed from IGP protocols is INCOMPLETE. |
Network |
Destination network address. |
From |
Source IP address of the route. |
Flaps |
Number of routing flaps. |
Duration |
Duration time of the flap route. |
Reuse |
Reuse time of the route. |
Path/Ogn |
AS_PATH and ORIGIN attributes of the route: · AS_PATH attribute—Records the ASs the route has passed, which avoids routing loops. · ORIGIN attribute—Identifies the origin of the route. |
dampening
reset bgp flap-info
display bgp routing-table ipv4 unicast
Use display bgp routing-table ipv4 unicast to display BGP IPv4 unicast routing information.
display bgp [ instance instance-name ] routing-table ipv4 [ unicast ] [ ipv4-address [ { mask-length | mask } [ longest-match ] ] | ipv4-address [ mask-length | mask ] advertise-info | peer { ipv4-address | ipv6-address } { advertised-routes | received-routes } [ ipv4-address [ mask-length | mask ] | statistics ] | statistics ]
network-admin
network-operator
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays BGP IPv4 unicast routing information for the default BGP instance.
ipv4-address: Specifies a destination network address.
mask-length: Specifies a mask length in the range of 0 to 32.
mask: Specifies a network mask in dotted decimal notation.
longest-match: Specifies longest match mode, which selects the longest matching route through the following steps:
1. ANDs the specified network address with the mask of each route.
2. Matches a route if the AND result is the same as the network address of the route and the mask of the route is shorter than or equal to the specified mask.
3. Selects the route with the longest mask among the matching routes.
advertise-info: Displays advertisement information for BGP IPv4 unicast routes.
peer { ipv4-address | ipv6-address }: Displays BGP IPv4 unicast routing information advertised to or received from the specified peer.
advertised-routes: Displays routing information advertised to the specified peer.
received-routes: Displays routing information received from the specified peer.
statistics: Displays routing statistics.
If you do not specify any parameters, this command displays brief information about all BGP IPv4 unicast routes.
If you specify only the ipv4-address argument, the system ANDs the network address with the mask of a route. If the result matches the network address of the route, the command displays information about the route.
If you specify the ipv4-address mask or ipv4-address mask-length argument and do not specify the longest-match keyword, this command displays information about the BGP IPv4 unicast route that matches both the specified destination network address and the mask (or mask length).
This command displays BGP IPv4 unicast routing information regardless of whether the unicast keyword is specified.
# Display brief information about all BGP IPv4 unicast routes.
<Sysname> display bgp routing-table ipv4
BGP local router ID is 192.168.100.1
Status codes: * - valid, > - best, d - dampened, h - history
s - suppressed, S - stale, i - internal, e - external
a – additional-path
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* > 10.2.1.0/24 10.2.1.1 0 0 i
e 10.2.1.2 0 0 4294967295
4294967294 4294967293 4294967292 4294967291 4294967290 4294967215 4294967225 4294967235 4294967245 4294967295 4294967294 4294967293 4294967292 4294967291 4294967290 i
* > 192.168.1.0 192.168.1.135 0 0 i
* e 10.2.1.2 0 0 200i
# Display information about BGP IPv4 unicast routes that match AS path list 1.
<Sysname> display bgp routing-table ipv4 as-path-acl 1
BGP local router ID is 2.2.2.2
Status codes: * - valid, > - best, d - dampened, h - history
s - suppressed, S - stale, i - internal, e - external
a – additional-path
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* >e 30.1.1.0/24 20.1.1.1 0 200i
# Display information about all public BGP IPv4 unicast routes advertised to peer 10.2.1.2.
<Sysname> display bgp routing-table ipv4 peer 10.2.1.2 advertised-routes
BGP local router ID is 192.168.100.1
Status codes: * - valid, > - best, d - damped, h - history
s - suppressed, S - Stale, i - internal, e - external
a – additional-path
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* > 10.2.1.0/24 10.2.1.1 0 0 i
* > 192.168.1.0 192.168.1.135 0 0 i
# Display information about all public BGP IPv4 unicast routes received from peer 10.2.1.2.
<Sysname> display bgp routing-table ipv4 peer 10.2.1.2 received-routes
BGP local router ID is 192.168.100.1
Status codes: * - valid, > - best, d - damped, h - history
s - suppressed, S - Stale, i - internal, e - external
a – additional-path
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
e 10.2.1.0/24 10.2.1.2 0 0 200i
* e 192.168.1.0 10.2.1.2 0 0 200i
Field |
Description |
Status codes |
Status codes: · * – valid—Valid route. · > – best—Optimal route. · d – dampened—Dampened route. · h – history—History route. · s – suppressed—Suppressed route. · S – stale—Stale route. · i – internal—Internal route. · e – external—External route. · a – additional-path—Add-Path optimal route. |
Origin |
Origin of the route: · i – IGP—Originated in the AS. The origin of routes advertised with the network command is IGP. · e – EGP—Learned through EGP. · ?– incomplete—Unknown origin. The origin of routes redistributed from IGP protocols is INCOMPLETE. |
Network |
Destination network address. |
NextHop |
Next hop IP address. |
MED |
MULTI_EXIT_DISC attribute. |
LocPrf |
Local preference value. |
PrefVal |
Preferred value of the route. |
Path/Ogn |
AS_PATH and ORIGIN attributes of the route: · AS_PATH—Records the ASs the route has passed, which avoids routing loops. This field can display a maximum of 16 AS numbers. More AS numbers are omitted and can be viewed in the detailed route information. · ORIGIN—Identifies the origin of the route. |
# Display detailed information about BGP IPv4 unicast routes destined to network 10.2.1.0/24.
<Sysname> display bgp routing-table ipv4 10.2.1.0 24
BGP local router ID: 192.168.100.1
Local AS number: 100
BGP routing table information of 10.2.1.0/24:
Imported route.
Original nexthop: 10.2.1.1
OutLabel : NULL
RxPathID : 0x0
TxPathID : 0x0
AS-path : (null)
Origin : igp
Attribute value : MED 0, pref-val 0, pre 0
State : valid, local, best, bgp-rib-only
Originator : 176.1.1.2
Cluster list : 80
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
VPN-Peer UserID : N/A
DSCP : N/A
EXP : N/A
From : 10.2.1.2 (192.168.100.2)
Rely nexthop : not resolved
Original nexthop: 10.2.1.2
OutLabel : NULL
RxPathID : 0x0
TxPathID : 0x0
AS-path : 200
Origin : igp
Attribute value : MED 0, pref-val 0, pre 255
State : external
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
VPN-Peer UserID : N/A
DSCP : N/A
EXP : N/A
# Display detailed information about the BGP IPv4 unicast route destined to address 1.1.1.1/32.
<Sysname> display bgp routing-table ipv4 1.1.1.1 32
BGP local router ID: 192.168.100.1
Local AS number: 100
BGP routing table information of 1.1.1.1/32:
From : 10.2.1.1 (192.168.100.3)
Rely nexthop : 10.2.1.1
Original nexthop: 10.2.1.1
OutLabel : NULL
RxPathID : 0x0
TxPathID : 0x0
AS-path : (null)
Origin : igp
Attribute value : MED 0, pref-val 0, pre 0
State : valid, local, best
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
VPN-Peer UserID : N/A
DSCP : N/A
EXP : N/A
Backup route.
From : 10.2.1.2 (192.168.100.2)
Rely nexthop : 10.2.1.2
Original nexthop: 10.2.1.2
OutLabel : NULL
RxPathID : 0x0
TxPathID : 0x0
AS-path : 200
Origin : igp
Attribute value : MED 0, pref-val 0, pre 255
State : external
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
VPN-Peer UserID : N/A
DSCP : N/A
EXP : N/A
Table 12 Command output
Field |
Description |
Paths |
Number of routes: · available—Number of valid routes. · best—Number of optimal routes. |
Original nexthop |
Original next hop of the route. If the route was obtained from a BGP update message, the original next hop is the next hop IP address in the message. |
OutLabel |
Outgoing label of the route. |
RxPathID |
Add-path ID of received routes. |
TxPathID |
Add-path ID of advertised routes. |
AS-path |
AS_PATH attribute of the route, which records the ASs the route has passed and avoids routing loops. |
Origin |
Origin of the route: · igp—Originated in the AS. The origin of routes advertised with the network command is IGP. · egp—Learned through EGP. · incomplete—Unknown origin. The origin of routes redistributed from IGP protocols is INCOMPLETE. |
Attribute value |
BGP path attributes: · MED—MED value. · localpref—Local preference value. · pref-val—Preferred value. · pre—Route preference. |
State |
Current state of the route: · valid. · internal. · external. · local. · synchronize. · best. |
Originator |
Router ID of the peer that advertised the route to the reflector. |
From |
IP address of the BGP peer that advertised the route. |
Rely Nexthop |
Next hop found by route recursion. If no next hop is found, this field displays not resolved. |
IP precedence |
IP precedence in the range of 0 to 7. N/A indicates that the route does not support this field. |
QoS local ID |
QoS local ID in the range of 1 to 4095. N/A indicates that the route does not support this field. |
Traffic index |
Traffic index in the range of 1 to 64. N/A indicates that the route does not support this field. |
VPN-Peer UserID |
This field is not supported in the current software version. VPN peer ID in the range of 1 to 134217727. N/A indicates that the route does not support this field. |
DSCP |
This field is not supported in the current software version. DSCP value in the range of 0 to 63. N/A indicates that the route does not support this field. |
EXP |
This field is not supported in the current software version. MPLS EXP value of the route. N/A indicates that the route does not support this field. |
Rely Tunnel IDs |
This field is not supported in the current software version. Tunnel index IDs after route recursion. This field displays multiple tunnel index IDs if ECMP tunnels exist and displays N/A if no tunnels are found by route recursion. |
# Display statistics for public BGP IPv4 unicast routes advertised to peer 10.2.1.2.
<Sysname> display bgp routing-table ipv4 peer 10.2.1.2 advertised-routes statistics
# Display statistics for public BGP IPv4 unicast routes received from peer 10.2.1.2.
<Sysname> display bgp routing-table ipv4 peer 10.2.1.2 received-routes statistics
Table 13 Command output
Field |
Description |
Advertised routes total |
Total number of advertised routes. |
Received routes total |
Total number of received routes. |
# Display BGP IPv4 unicast route statistics.
<Sysname> display bgp routing-table ipv4 statistics
Table 14 Command output
Field |
Description |
Total number of routes |
Total number of routes. |
# Display advertisement information for the BGP IPv4 unicast route destined to network 10.2.1.0/24.
<Sysname> display bgp routing-table ipv4 10.2.1.0 24 advertise-info
BGP local router ID: 192.168.100.1
Local AS number: 100
BGP routing table information of 10.2.1.0/24:
Advertised to peers (1 in total):
Table 15 Command output
Field |
Description |
BGP local router ID |
Local BGP router ID. |
Local AS number |
Local AS number. |
Paths |
Number of optimal routes to the destination. |
BGP routing table information of 10.2.1.0/24 |
Advertisement information for network 10.2.1.0/24. |
Advertised to peers (1 in total) |
Peers to which the network has been advertised. |
display bgp routing-table ipv6 unicast
Use display bgp routing-table ipv6 unicast to display BGP IPv6 unicast routing information.
display bgp [ instance instance-name ] routing-table ipv6 [ unicast ] [ ipv6-address prefix-length [ advertise-info ] | peer ipv6-address { advertised-routes | received-routes } [ ipv6-address prefix-length | statistics ] | statistics ]
network-admin
network-operator
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays BGP IPv6 unicast routing information for the default BGP instance.
ipv6-address prefix-length: Specifies the destination network address and prefix length. The value range for the prefix-length argument is 0 to 128. If you do not specify this argument, the command displays brief information about all BGP IPv6 unicast routing information.
advertise-info: Displays advertisement information for BGP IPv6 unicast routes. If you do not specify this keyword, the command displays the BGP IPv6 unicast routing table.
peer: Displays BGP IPv6 unicast routing information advertised to or received from the specified peer.
ipv4-address: Specifies the peer IPv4 address.
ipv6-address: Specifies the peer IPv6 address.
advertised-routes: Displays routing information advertised to the specified peer.
received-routes: Displays routing information received from the specified peer.
statistics: Displays routing statistics.
This command displays BGP IPv6 unicast routing information regardless of whether the unicast keyword is specified.
# Display brief information about all BGP IPv6 unicast routes.
<Sysname> display bgp routing-table ipv6
BGP local router ID is 192.168.1.136
Status codes: * - valid, > - best, d - dampened, h - history
s - suppressed, S - stale, i - internal, e - external
a – additional-path
Origin: i - IGP, e - EGP, ? - incomplete
* >e Network : 3:: PrefixLen : 64
NextHop : 1::2 LocPrf :
PrefVal : 0 OutLabel : NULL
MED :
Path/Ogn: 4294967295 4294967294 4294967293 4294967292 4294967291 4294967290 4294967215 4294967225 4294967235 4294967245 4294967295 4294967294 4294967293 4294967292 4294967291 4294967290 i
# Display information about BGP IPv6 unicast routes that match AS path list 1.
<Sysname> display bgp routing-table ipv6 as-path-acl 1
BGP local router ID is 192.168.1.136
Status codes: * - valid, > - best, d - dampened, h - history
s - suppressed, S - stale, i - internal, e - external
a – additional-path
Origin: i - IGP, e - EGP, ? - incomplete
* >e Network : 2:: PrefixLen : 64
NextHop : 1::2 LocPrf :
PrefVal : 0 OutLabel : NULL
MED :
Path/Ogn: 100i
* >e Network : 3:: PrefixLen : 64
NextHop : 1::2 LocPrf :
PrefVal : 0 OutLabel : NULL
MED :
Path/Ogn: 100i
# Display information about BGP IPv6 unicast routes that match BGP community list 100.
<Sysname> display bgp routing-table ipv6 community-list 100
BGP local router ID is 192.168.1.136
Status codes: * - valid, > - best, d - dampened, h - history
s - suppressed, S - stale, i - internal, e - external
a – additional-path
Origin: i - IGP, e - EGP, ? - incomplete
* >e Network : 2:: PrefixLen : 64
NextHop : 1::2 LocPrf :
PrefVal : 0 OutLabel : NULL
MED :
Path/Ogn: 100i
* >e Network : 3:: PrefixLen : 64
NextHop : 1::2 LocPrf :
PrefVal : 0 OutLabel : NULL
MED :
Path/Ogn: 100i
# Display information about all BGP IPv6 unicast routes advertised to peer 1::1.
<Sysname> display bgp routing-table ipv6 peer 1::1 advertised-routes
BGP local router ID is 192.168.1.136
Status codes: * - valid, > - best, d - dampened, h - history
s - suppressed, S - stale, i - internal, e - external
a – additional-path
Origin: i - IGP, e - EGP, ? - incomplete
* > Network : 2:: PrefixLen : 64
NextHop : :: LocPrf :
MED : 0 OutLabel : NULL
Path/Ogn: i
# Display information about all BGP IPv6 unicast routes received from peer 1::1.
<Sysname> display bgp routing-table ipv6 peer 1::1 received-routes
BGP local router ID is 192.168.1.135
Status codes: * - valid, > - best, d - dampened, h - history
s - suppressed, S - stale, i - internal, e - external
a – additional-path
Origin: i - IGP, e - EGP, ? - incomplete
* >e Network : 2:: PrefixLen : 64
NextHop : ::FFFF:10.1.1.1 LocPrf :
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: 100i
Field |
Description |
Status codes |
Status codes: · * – valid—Valid route. · > – best—Optimal route. · d – dampened—Dampened route. · h – history—History route. · s – suppressed—Suppressed route. · S – stale—Stale route. · i – internal—Internal route. · e – external—External route. · a – additional-path—Add-Path optimal route. |
Origin |
Origin of the route: · i – IGP—Originated in the AS. The origin of routes advertised with the network command is IGP. · e – EGP—Learned through EGP. · ?– incomplete—Unknown origin. The origin of routes redistributed from IGP protocols is INCOMPLETE. |
Network |
Destination network address. |
PrefixLen |
Prefix length of the destination network address. |
NextHop |
Next hop IPv6 address. |
LocPrf |
Local preference value. |
PrefVal |
Preferred value of the route. |
OutLabel |
This field is not supported in the current software version. Outgoing label of the route. |
MED |
MULTI_EXIT_DISC attribute. |
Path/Ogn |
AS_PATH and ORIGIN attributes of the route: · AS_PATH attribute—Records the ASs the route has passed, which avoids routing loops. This field can display a maximum of 16 AS numbers. More AS numbers are omitted and can be viewed in the detailed route information. · ORIGIN attribute—Identifies the origin of the route. |
# Display detailed information about BGP IPv6 unicast routes destined to network 2::/64.
<Sysname> display bgp routing-table ipv6 2:: 64
BGP local router ID: 192.168.1.135
Local AS number: 200
BGP routing table information of 2::/64:
From : 10.1.1.1 (192.168.1.136)
Relay nexthop : ::FFFF:10.1.1.1
Original nexthop: ::FFFF:10.1.1.1
OutLabel : NULL
RxPathID : 0x0
TxPathID : 0x0
AS-path : 100
Origin : igp
Attribute value : MED 0, pref-val 0
State : valid, external, best, bgp-rib-only
Originator : 176.1.1.2
Cluster list : 80
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
EXP : N/A
Backup route.
Relay nexthop : 1::1
Original nexthop: 1::1
OutLabel : NULL
RxPathID : 0x0
TxPathID : 0x0
AS-path : 100
Origin : igp
Attribute value : MED 0, pref-val 0
State : valid, external
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
EXP : N/A
Table 17 Command output
Field |
Description |
Paths |
Number of routes: · available—Number of valid routes. · best—Number of optimal routes. |
Original nexthop |
Original next hop of the route. If the route was obtained from a BGP update message, the original next hop is the next hop IP address in the message. |
OutLabel |
Outgoing label of the route. |
RxPathID |
Add-path ID of received routes. |
TxPathID |
Add-path ID of advertised routes. |
AS-path |
AS_PATH attribute of the route, which records the ASs the route has passed and avoids routing loops. |
Origin |
Origin of the route: · igp—Originated in the AS. The origin of routes advertised with the network command is IGP. · egp—Learned through EGP. · incomplete—Unknown origin. The origin of routes redistributed from IGP protocols is INCOMPLETE. |
Attribute value |
BGP path attributes: · MED—MED value. · localpref—Local preference value. · pref-val—Preferred value. · pre—Route preference. |
State |
Current state of the route: · valid—Valid route. · internal—Internal route. · external—External route. · local—Locally generated route. · best—Optimal route. This field is not supported in the current software version. |
Originator |
Router ID of the peer that advertised the route to the reflector. |
From |
IP address of the BGP peer that advertised the route. |
Relay Nexthop |
Next hop found by route recursion. If no next hop is found, this field displays not resolved. |
IP precedence |
IP precedence in the range of 0 to 7. N/A indicates that the route does not support this field. |
QoS local ID |
QoS local ID in the range of 1 to 4095. N/A indicates that the route does not support this field. |
Traffic index |
Traffic index in the range of 1 to 64. N/A indicates that the route does not support this field. |
Tag |
Route tag. |
VPN-Peer UserID |
This field is not supported in the current software version. VPN peer ID in the range of 1 to 134217727. N/A indicates that the route does not support this field. |
EXP |
This field is not supported in the current software version. MPLS EXP value of the route. N/A indicates that the route does not support this field. |
Tunnel policy |
This field is not supported in the current software version. Tunnel policy that takes effect. NULL indicates that no tunnel policy takes effect. |
Rely Tunnel IDs |
This field is not supported in the current software version. Tunnel index IDs after route recursion. This field displays multiple tunnel index IDs if ECMP tunnels exist and displays N/A if no tunnels are found by route recursion. |
# Display advertisement information for BGP IPv6 unicast routes destined to network 2::/64.
<Sysname> display bgp routing-table ipv6 2:: 64 advertise-info
BGP local router ID: 192.168.1.136
Local AS number: 100
BGP routing table information of 2::/64:
Advertised to peers (2 in total):
10.1.1.2
1::2
Table 18 Command output
Field |
Description |
Paths |
Number of optimal routes destined to the specified network. |
BGP routing table information of 2::/64 |
Advertisement information for BGP routes destined to network 2::/64. |
Advertised to peers (2 in total) |
Peers to which the route has been advertised, and the number of peers. |
# Display statistics for BGP IPv6 unicast routes advertised to peer 1::1.
<Sysname> display bgp routing-table ipv6 peer 1::1 advertised-routes statistics
# Display statistics for BGP IPv6 unicast routes received from peer 1::1.
<Sysname> display bgp routing-table ipv6 peer 1::1 received-routes statistics
Table 19 Command output
Field |
Description |
Advertised routes total |
Total number of advertised routes. |
Received routes total |
Total number of received routes. |
# Display BGP IPv6 unicast route statistics.
<Sysname> display bgp routing-table ipv6 statistics
Table 20 Command output
Field |
Description |
Total number of routes |
Total number of routes. |
display bgp update-group
Use display bgp update-group to display information about BGP update groups.
display bgp [ instance instance-name ] update-group ipv4 [ unicast ] [ ipv4-address ]
display bgp [ instance instance-name ] update-group ipv4 [ unicast ] [ ipv6-address ]
display bgp [ instance instance-name ] update-group ipv6 [ unicast ] [ ipv6-address ]
display bgp [ instance instance-name ] update-group ipv6 [ unicast ] [ ipv4-address ]
network-admin
network-operator
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays BGP update group information for the default BGP instance.
ipv4: Displays BGP update group information for IPv4 address family.
ipv6: Displays BGP update group information for IPv6 address family.
unicast: Displays BGP update group information for unicast address family.
ipv4-address: Displays BGP update group information for the specified BGP peer.
ipv6-address: Displays BGP update group information for the specified IPv6 BGP peer.
The update group feature classifies BGP peers that have the same export policy into an update group. When BGP advertises routes to the peers in the update group, it uses the export policy to filter the routes and generates route updates for all the peers only once.
With this feature, BGP performs one-time policy filtering and encapsulation for a prefix before advertising the prefix to all the peers in the update group. For example, BGP advertises 1000 prefixes to 1000 peers that have the same export policy (in data centers for example). Without the update group feature, BGP matches the export policy 1000 × 1000 times. With the update group feature, BGP matches the export policy only 1000 × 1 times, improving encapsulation efficiency 1000 times.
If you do not specify any parameters, this command displays all update groups for the specified address family on the public network.
By default, the unicast keyword is used if the unicast keyword is not specified.
# Display information about all BGP update groups for the IPv4 unicast address family.
<Sysname> display bgp update-group ipv4
Type: EBGP link
4-byte AS number: Supported
Site-of-Origin: Not specified
Minimum time between advertisements: 30 seconds
OutQ: 0
Members: 1
99.1.1.1
Table 21 Command output
Field |
Description |
Update-group ID |
ID of the update group. |
Type |
BGP link type: · IBGP link. · EBGP link. · Confed IBGP link—Confederation IBGP link. · Confed EBGP link—Confederation EBGP link. |
4-byte AS number: Supported |
4-byte AS number suppression is disabled for the peers in the update group. The peers in the update group support 4-byte AS numbers. |
4-byte AS number: Suppressed |
4-byte AS number suppression is enabled for the peers in the update group. |
Minimum time between advertisements: number seconds |
Minimum time between advertisements. |
Export filter-policy |
ACL used to filter BGP routes advertised to peers in the update group. |
OutQ |
Number of prefixes to be advertised to peers in the update group. |
Members |
Number and IP addresses of peers in the update group. |
filter-policy export
Use filter-policy export to filter advertised BGP routes.
Use undo filter-policy export to remove the route filter.
In BGP IPv4 unicast address family view:
filter-policy { ipv4-acl-number | prefix-list ipv4-prefix-list-name } export [ direct | { isis | ospf | rip } process-id | static ]
undo filter-policy export [ direct | { isis | ospf | rip } process-id | static ]
In BGP IPv6 unicast address family view:
filter-policy { ipv6-acl-number | prefix-list ipv6-prefix-list-name } export [ direct | { isisv6 | ospfv3 | ripng } process-id | static ]
undo filter-policy export [ direct | { isisv6 | ospfv3 | ripng } process-id | static ]
Advertised BGP routes are not filtered.
BGP IPv4 unicast address family view
BGP IPv6 unicast address family view
network-admin
ipv4-acl-number: Specifies an IPv4 ACL by its number in the range of 2000 to 3999, to match routes by destination.
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999, to match routes by destination.
prefix-list ipv4-prefix-list-name: Specifies an IPv4 prefix list by its name, a case-sensitive string of 1 to 63 characters, to match routes by destination.
prefix-list ipv6-prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters, to match routes by destination.
direct: Filters direct routes.
eigrp: Filters EIGRP routes.
isis: Filters IS-IS routes.
isisv6: Filters IPv6 IS-IS routes.
ospf: Filters OSPF routes.
ospfv3: Filters OSPFv3 routes.
rip: Filters RIP routes.
ripng: Filters RIPng routes.
static: Filters static routes.
process-id: Specifies a routing protocol by its ID in the range of 1 to 65535.
If you specify a protocol (such as direct and isis), this command filters only routes redistributed from the specified protocol. If you do not specify a protocol, this command filters all advertised routes, including the following routes:
· Redistributed from IGP.
· Injected by the network command.
· Learned from BGP peers.
If you use a basic ACL (with a number from 2000 to 2999) configured with the rule [ rule-id ] { deny | permit } source source-address source-wildcard command, the command matches routes whose destination network addresses match the source-address source-wildcard argument. However, it does not match the masks of the destination addresses.
To use an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL using one of the following steps:
· To deny or permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny or permit a route with the specified destination and mask, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard destination dest-addr dest-wildcard command.
The source keyword specifies the destination address of a route and the destination keyword specifies the subnet mask of the destination address. For the mask configuration to take effect, specify a contiguous subnet mask.
If the specified ACL does not exist or does not have any rules, all BGP routes can pass the ACL.
Examples
# In BGP IPv4 unicast address family view, use IPv4 basic ACL 2000 to filter advertised BGP IPv4 routes.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] filter-policy 2000 export
filter-policy import
peer filter-policy
filter-policy import
Use filter-policy import to filter received BGP routes.
Use undo filter-policy import to restore the default.
In BGP IPv4 unicast address family view:
filter-policy { ipv4-acl-number | prefix-list ipv4-prefix-list-name } import
undo filter-policy import
In BGP IPv6 unicast address family view:
filter-policy { ipv6-acl-number | prefix-list ipv6-prefix-list-name } import
undo filter-policy import
Received BGP routes are not filtered.
BGP IPv4 unicast address family view
BGP IPv6 unicast address family view
network-admin
ipv4-acl-number: Specifies an IPv4 ACL by its number in the range of 2000 to 3999, to match routes by destination.
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999, to match routes by destination.
prefix-list ipv4-prefix-list-name: Specifies an IPv4 prefix list by its name, a case-sensitive string of 1 to 63 characters, to match routes by destination.
prefix-list ipv6-prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters, to match routes by destination.
If you use a basic ACL (with a number from 2000 to 2999) configured with the rule [ rule-id ] { deny | permit } source source-address source-wildcard command, the command matches routes whose destination network addresses match the source-address source-wildcard argument. However, it does not match the masks of the destination addresses.
To use an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL using one of the following steps:
· To deny or permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny or permit a route with the specified destination and mask, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard destination dest-addr dest-wildcard command.
The source keyword specifies the destination address of a route and the destination keyword specifies the subnet mask of the destination address. For the mask configuration to take effect, specify a contiguous subnet mask.
If the specified ACL does not exist or does not have any rules, all BGP routes can pass the ACL.
Examples
# In BGP IPv4 unicast address family view, use IPv4 basic ACL 2000 to filter received BGP routes.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] filter-policy 2000 import
filter-policy export
peer filter-policy
group
Use group to create a peer group.
Use undo group to delete a peer group.
group group-name [ external | internal ]
undo group group-name
No peer groups exist.
network-admin
group-name: Specifies a name for the peer group, a case-sensitive string of 1 to 47 characters.
external: Creates an EBGP peer group.
internal: Creates an IBGP peer group.
In a large-scale network, many peers can use the same route selection policy. You can configure a peer group and add these peers into this group. In this way, peers can share the same policy as the peer group. When the policy of the group is modified, the modification also applies to peers in it.
If you do not specify the internal or external keyword, this command creates an IBGP peer group.
If you perform configurations on a peer group and peers of the peer group, the most recent configuration takes effect.
After you create a peer group, you must use the peer enable command to enable BGP to exchange routing information with the specified peer group.
# In BGP instance view, create EBGP peer group test with AS number 200, and add EBGP peers 10.1.1.1 and 10.1.2.1 into the group.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] group test external
[Sysname-bgp-default] peer test as-number 200
[Sysname-bgp-default] peer 10.1.1.1 group test
[Sysname-bgp-default] peer 10.1.2.1 group test
display bgp group
peer enable
import-route
Use import-route to enable BGP to redistribute routes from an IGP protocol.
Use undo import-route to disable route redistribution from an IGP protocol.
In BGP IPv4 unicast address family view:
import-route { isis | ospf | rip } [ { process-id | all-processes } [ allow-direct | med med-value ] * ]
import-route { direct | guard | static } [ med med-value ] *
undo import-route { direct | guard | { isis | ospf | rip } [ process-id | all-processes ] | static }
In BGP IPv6 unicast address family view:
import-route { isisv6 | ospfv3 | ripng } [ { process-id | all-processes } [ allow-direct | med med-value ] * ]
import-route { direct | guard | static } [ med med-value ] *
undo import-route { direct | guard | { isisv6 | ospfv3 | ripng } [ process-id | all-processes ] | static }
BGP does not redistribute IGP routes.
BGP IPv4 unicast address family view
BGP IPv6 unicast address family view
network-admin
direct: Redistributes direct routes.
eigrp: Redistributes EIGRP routes.
guard: Redistributes guard routes.
isis: Redistributes IS-IS routes.
isisv6: Redistributes IPv6 IS-IS routes.
ospf: Redistributes OSPF routes.
ospfv3: Redistributes OSPFv3 routes.
rip: Redistributes RIP routes.
ripng: Redistributes RIPng routes.
static: Redistributes static routes.
process-id: Specifies a process by its ID in the range of 1 to 65535.
all-processes: Redistributes routes from all the processes of the specified IGP protocol.
allow-direct: Redistributes the networks of the local interfaces enabled with the specified routing protocol. By default, the networks of the local interfaces are not redistributed.
med med-value: Specifies a MED value for redistributed routes, in the range of 0 to 4294967295. If you do not specify an MED, the metric of a redistributed route is used as its MED.
The import-route command cannot redistribute default IGP routes. To redistribute default IGP routes, use the default-route imported command together with the import-route command.
Only active routes can be redistributed. You can use the display ip routing-table protocol or display ipv6 routing-table protocol command to view route state information.
If you do not specify any parameters when redistributing IS-IS, IPv6 IS-IS, OSPF, OSPFv3, RIP, or RIPng routes, the command redistributes routes from process 1.
The ORIGIN attribute of routes redistributed by the import-route command is INCOMPLETE.
After you redistribute routes from all processes of a routing protocol by using the all-processes keyword, this command does not take effect on any processes of the protocol.
# In BGP IPv4 unicast address family view, redistribute routes from RIP process 1, and set the MED value for redistributed routes to 100.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] import-route rip 1 med 100
import-route-append
import-route-append
Use import-route-append to redistribute routes from an IGP without overwriting the routes redistributed by the import-route command.
Use undo import-route-append to remove the redistributed routes.
Syntax
In BGP IPv4 unicast address family view:
import-route-append { isis | ospf | rip } [ { process-id | all-processes } [ allow-direct | med med-value ] * ]
import-route-append { direct | static } [ med med-value ] *
undo import-route-append { direct | { isis | ospf | rip } [ process-id | all-processes ] | static }
In BGP IPv6 unicast address family view:
import-route-append { isisv6 | ospfv3 | ripng } [ { process-id | all-processes } [ allow-direct | med med-value ] * ]
import-route-append { direct | static } [ med med-value ] *
undo import-route-append { direct | { isisv6 | ospfv3 | ripng } [ process-id | all-processes ] | static }
Default
BGP does not redistribute IGP routes.
Views
BGP IPv4 unicast address family view
BGP IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
direct: Redistributes direct routes.
isis: Redistributes IS-IS routes.
isisv6: Redistributes IPv6 IS-IS routes.
ospf: Redistributes OSPF routes.
ospfv3: Redistributes OSPFv3 routes.
rip: Redistributes RIP routes.
ripng: Redistributes RIPng routes.
static: Redistributes static routes.
process-id: Specifies a process by its number in the range of 1 to 65535.
all-processes: Redistributes routes from all processes of the specified routing protocol.
allow-direct: Redistributes the networks of the local interfaces enabled with the specified routing protocol. By default, the networks of the local interfaces are not redistributed.
med med-value: Specifies a MED value for redistributed routes, in the range of 0 to 4294967295. If you do not specify an MED, the metric of a redistributed route is used as its MED.
Usage guidelines
If you execute the import-route-append command without executing the import-route command, the import-route-append command has the same effect as the import-route command.
If you execute both the import-route and import-route-append commands for an IGP process, the MED value specified by the import-route-append command takes precedence over that specified by the import-route command.
After you redistribute routes from all processes of a routing protocol by using the all-processes keyword, this command does not take effect on any processes of the protocol.
Examples
# In BGP IPv4 unicast address family view, redistribute routes from IS-IS process 1 without overwriting the routes redistributed by the import-route command.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] import-route isis 1
[Sysname-bgp-default-ipv4] import-route-append isis 1
Related commands
display ip routing-table protocol (Network Connectivity Command Reference)
display ipv6 routing-table protocol (Network Connectivity Command Reference)
import-route
log-peer-change
Use log-peer-change to enable logging for BGP session state changes globally.
Use undo log-peer-change to disable logging for BGP session state changes globally.
log-peer-change
undo log-peer-change
Logging for BGP session state changes is enabled globally.
network-admin
After you execute both the log-peer-change and peer log-change commands, BGP logs session establishment and disconnection events for the peer or peer group. To display the log information, use the display bgp peer ipv4 unicast log-info command or the display bgp peer ipv6 unicast log-info command. The logs are sent to the information center of the device. The output rules of the logs (whether to output the logs and where to output) are determined by the information center configuration. For more information about information center configuration, see System Management Configuration Guide.
If you disable logging for BGP session state changes globally or disable logging for a peer or peer group, BGP does not generate logs for session establishments and disconnections.
# Enable logging for session state changes globally.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] log-peer-change
display bgp peer
network
Use network to inject a network to the BGP routing table and configure BGP to advertise the network.
Use undo network to remove a local network.
In BGP IPv4 unicast address family view:
network ipv4-address [ mask-length | mask ]
undo network ipv4-address [ mask-length | mask ]
In BGP IPv6 unicast address family view:
network ipv6-address prefix-length
undo network ipv6-address prefix-length
BGP does not advertise local networks.
BGP IPv4 unicast address family view
BGP IPv6 unicast address family view
network-admin
ipv4-address: Specifies an IPv4 network address. If you do not specify the mask or mask-length argument, natural mask is used.
mask-length: Specifies a mask length in the range of 0 to 32.
mask: Specifies a mask in dotted decimal notation.
ipv6-address: Specifies an IPv6 network address.
prefix-length: Specifies a prefix length in the range of 0 to 128.
The network to be injected must be available and active in the local IP routing table.
The ORIGIN attribute of the route injected with the network command is IGP.
When you execute the undo network command, you must specify the same mask or mask length/prefix length that you specified for the network command. Otherwise, the configuration cannot be removed.
# In BGP IPv4 unicast address family view, inject local network 10.0.0.0/16 to the BGP routing table.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] network 10.0.0.0 255.255.0.0
peer as-number (for a BGP peer group)
Use peer as-number to specify an AS number for a peer group.
Use undo peer as-number to delete the AS number of a peer group.
peer group-name as-number as-number
undo peer group-name as-number
No AS number is specified for a peer group.
network-admin
group-name: Specifies a name for a peer group, a case-sensitive string of 1 to 47 characters. The peer group must have been created.
as-number: Specifies an AS number for a peer group, in the range of 1 to 4294967295.
This command applies only to a peer group with no peers in it.
When you specify an AS number for a peer group and want to add peers to it, make sure the AS number of the peers is the same as the peer group.
If you do not specify an AS number for a peer group, peers added to it can use their own AS numbers.
# In BGP instance view, set the AS number for peer group test to 100.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer test as-number 100
peer as-number (for a BGP peer)
Use peer as-number to create a BGP peer and specify its AS number.
Use undo peer to delete a BGP peer.
peer { ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } as-number as-number
undo peer { ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] }
No BGP peers exist.
network-admin
ipv4-address: Specifies the IPv4 address of a peer.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command enables BGP to establish dynamic peer relationships with all devices in the subnet.
ipv6-address: Specifies the IPv6 address of a peer.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command enables BGP to establish dynamic peer relationships with all devices in the subnet.
as-number: Specifies an AS number for the peer, in the range of 1 to 4294967295. If the AS numbers of the peer and the local router are the same, the peer is an IBGP peer. If they are different, the peer is an EBGP peer.
You can also create a peer and add it to a peer group by using the peer group command.
To modify the AS number of a peer, do not execute the peer as-number command repeatedly. Instead, you must first delete the peer and configure it again.
After you create a peer, you must use the peer enable command to enable BGP to exchange routing information with the specified peer.
For a remote device to establish a peer relationship with the local device, you must specify the IP address of the local device on the remote device.
# In BGP instance view, create BGP peer 1.1.1.1 and set its AS number to 100.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer 1.1.1.1 as-number 100
display bgp peer
peer enable
peer group
peer connect-interface
Use peer connect-interface to specify a source interface (IPv4 address/IPv6 address) for establishing TCP connections to a peer or peer group.
Use undo peer connect-interface to remove the configuration.
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } connect-interface interface-type interface-number
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } connect-interface
BGP uses the primary IPv4 or IPv6 address of the output interface in the optimal route destined for the BGP peer or peer group as the source address.
network-admin
group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must have been created.
ipv4-address: Specifies a peer by its IPv4 address. The peer must have been created.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command specifies a source interface for establishing TCP connections to all dynamic peers in the network.
ipv6-address: Specifies a peer by its IPv6 address. The peer must have been created.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command specifies a source interface for establishing TCP connections to all dynamic peers in the subnet.
interface-type interface-number: Specifies an interface by its type and number.
The peer connect-interface command and the peer source-address command can both change the source address for establishing TCP connections. If you execute both commands, the most recent configuration takes effect.
The peer source-address and peer connect-interface commands are applicable to the following scenarios:
· The peer's IPv4/IPv6 address does not belong to the interface directly connected to the local router. To ensure successful TCP connection establishment, use one of the following methods:
¡ Specify the interface to which the IPv4/IPv6 address belongs as the source interface on the peer.
¡ Specify the IPv4/IPv6 address of the interface directly connected to the local router as the source address on the peer.
· A BGP peer at an IPv6 link-local address must be directly connected to the local router. On the local router, you must use the peer connect-interface command to specify the interface directly connected to the BGP peer as the source interface of TCP connections.
· On a BGP router that has multiple links to a peer, the source interface for TCP connection changes because the primary source interface fails. To avoid this problem, specify a loopback interface as the source interface or specify the IP address of a loopback interface as the source address.
· You want to establish multiple BGP sessions to a router. In this case, BGP might fail to determine the source address for each TCP connection based on the optimal route to the peer. To prevent this problem, use one of the following methods:
¡ If the BGP sessions use IP addresses of different interfaces, specify a source interface or source address for each session.
¡ If the BGP sessions use different IP addresses of the same interface, specify a source address for each session.
The source interfaces on the local router and the peer must be reachable to each other.
To specify an indirectly connected interface on an EBGP peer as the source interface, use the peer ebgp-max-hop command. The command allows the establishment of an EBGP session to the indirectly connected peer.
If an interface has multiple IPv4 addresses, BGP uses the primary IPv4 address to establish TCP connections. If an interface has multiple IPv6 addresses, BGP selects a source IPv6 address. To use an IPv6 address as the source address, specify that IPv6 address by using the peer source-address command.
# In BGP instance view, specify loopback 0 as the source interface for TCP connections to peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer test connect-interface loopback 0
peer ebgp-max-hop
peer source-address
peer default-route-advertise
Use peer default-route-advertise to advertise a default route to a peer or peer group.
Use undo peer default-route-advertise to disable default route advertisement to a peer or peer group.
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } default-route-advertise
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } default-route-advertise
No default route is advertised to any peers or peer groups.
BGP IPv4 unicast address family view
BGP IPv6 unicast address family view
network-admin
group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must have been created.
ipv4-address: Specifies a peer by its IPv4 address. The peer must have been created.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command advertises a default route to all dynamic peers in the subnet.
ipv6-address: Specifies a peer by its IPv6 address. The peer must have been created.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command advertises a default route to all dynamic peers in the subnet.
This command enables the router to send a default route with the next hop being itself to the peer or peer group regardless of whether the default route exists in the routing table.
# In BGP IPv4 unicast address family view, advertise a default route to peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer test default-route-advertise
peer description
Use peer description to configure a description for a peer or peer group.
Use undo peer description to remove the description for a peer or peer group.
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } description text
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } description
No description information is configured for a peer or peer group.
network-admin
group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must have been created.
ipv4-address: Specifies a peer by its IPv4 address. The peer must have been created.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command configures a description for all dynamic peers in the subnet.
ipv6-address: Specifies a peer by its IPv6 address. The peer must have been created.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command configures a description for all dynamic peers in the subnet.
text: Specifies a description for a peer or peer group, a case-sensitive string of 1 to 79 characters.
Examples
# In BGP instance view, set the description for peer group test to ISP1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer test description ISP1
peer enable
Use peer enable to enable BGP to exchange routing information for an address family with a peer or peer group.
Use undo peer enable to disable BGP from exchanging routing information for an address family with a peer or peer group.
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } enable
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } enable
BGP cannot exchange routing information with a peer or peer group.
BGP IPv4 unicast address family view
BGP IPv6 unicast address family view
network-admin
group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must have been created.
ipv4-address: Specifies a peer by its IPv4 address. The peer must have been created.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet in this command, BGP exchanges routing information for an address family with all dynamic peers in the subnet.
ipv6-address: Specifies a peer by its IPv6 address. The peer must have been created.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet in this command, BGP exchanges routing information for an address family with all dynamic peers in the subnet.
Executing the peer enable command in different views enables BGP to exchange routing information for the corresponding address families with the specified peer.
· In BGP IPv4 unicast address family view, the command enables the capability to exchange IPv4 unicast routing information. It also adds the learned routes to the BGP routing table of the public network.
· In BGP IPv6 unicast address family view, the command enables the capability to exchange IPv6 unicast routing information. It also adds the learned routes to the IPv6 BGP routing table of the public network.
· In BGP VPNv4 flowspec address family view, the command enables the capability to exchange VPNv4 flowspec routing information. It also adds the learned routes to the BGP VPNv4 flowspec routing table of the VPN instance.
The undo peer enable command disables BGP to exchange routing information for the corresponding address family with the peer.
# In BGP IPv4 unicast address family view, enable BGP to exchange IPv4 unicast routing information with peer 1.1.1.1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer 1.1.1.1 enable
display bgp peer
peer filter-policy
Use peer filter-policy to filter routes advertised to or received from a peer or peer group by using an ACL.
Use undo peer filter-policy to remove the ACL specified to filter routes advertised to or received from a peer or peer group.
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } filter-policy ipv6-acl-number { export | import }
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } filter-policy { export | import }
No ACL-based filtering is configured.
BGP IPv4 unicast address family view
BGP IPv6 unicast address family view
network-admin
group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must have been created.
ipv4-address: Specifies a peer by its IPv4 address. The peer must have been created.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command filters routes advertised to or received from all dynamic peers in the subnet by using an ACL.
ipv6-address: Specifies a peer by its IPv6 address. The peer must have been created.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command filters routes advertised to or received from all dynamic peers in the subnet by using an ACL.
ipv4-acl-number: Specifies an ACL by its number in the range of 2000 to 3999.
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999.
export: Filters routes advertised to the peer/peer group.
import: Filters routes received from the peer/peer group.
The specified ACL used by the peer filter-policy command must have been created with the acl command in system view. Otherwise, all routes can pass the ACL.
If you use a basic ACL (with a number from 2000 to 2999) configured with the rule [ rule-id ] { deny | permit } source source-address source-wildcard command, the command matches routes whose destination network addresses match the source-address source-wildcard argument without matching the masks of the destination addresses.
To use an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL using one of the following steps:
· To deny or permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny or permit a route with the specified destination and mask, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard destination dest-addr dest-wildcard command.
The source keyword specifies the destination address of a route and the destination keyword specifies the subnet mask of the destination address. For the mask configuration to take effect, specify a contiguous subnet mask.
If the specified ACL does not exist or does not have any rules, all BGP routes can pass the ACL.
Examples
# In BGP IPv4 unicast address family view, apply ACL 2000 to filter routes advertised to peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer test filter-policy 2000 export
acl (Security Command Reference)
filter-policy export
filter-policy import
peer group
Use peer group to add a peer to a peer group.
Use undo peer group to delete a peer from a peer group.
peer { ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } group group-name [ as-number as-number ]
undo peer { ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } group group-name
No peers exist in a peer group.
network-admin
ipv4-address: Specifies a peer by its IPv4 address.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command adds all dynamic peers in the subnet to a peer group.
ipv6-address: Specifies a peer by its IPv6 address.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command adds all dynamic peers in the subnet to a peer group.
group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must have been created.
as-number as-number: Specifies an AS for a peer by its number in the range of 1 to 4294967295.
You can add a peer to a peer group in the following ways:
· Use the peer as-number command to create a peer and specify its AS number, and then use the peer group command to add the peer to the peer group.
¡ You can specify the as-number keyword for the peer group command. The AS number must be the same as the AS number specified in the peer as-number command.
¡ If you have specified the AS number of the peer group with the peer as-number command, the peer to be added must have the same AS number as the peer group.
¡ To add a peer to an IBGP peer group, the peer must be an IBGP peer.
· Use the peer group command to create a peer and add it to the peer group.
¡ If you have specified the AS number of the peer group with the peer as-number command, you do not need to specify the as-number keyword when you execute the peer group command. This is because the AS number of the peer is the same as the peer group. To specify the as-number keyword for the peer group command, make sure the AS number is the same as the peer group.
¡ If no AS number is specified for an EBGP peer group, specify the as-number keyword when you execute the peer group command.
¡ If no AS number is specified for an IBGP peer group, you do not need to specify the as-number keyword when you execute the peer group command. This is because the AS number of the IBGP peer group is the local AS number. To specify the as-number keyword for the peer group command, make sure the AS number is the same as the local AS number.
If you have specified the AS number of a peer group with the peer as-number command, only the peers with the same AS number can be added to the peer group. All peers in the group share the same AS number. If you have not specified the AS number for a peer group, peers added to it can use their own AS numbers.
After you add a peer to a peer group, you must use the peer enable command to enable BGP to exchange routing information with the peer group.
# In BGP instance view, add peer 10.1.1.1 to EBGP peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] group test external
[Sysname-bgp-default] peer 10.1.1.1 group test as-number 2004
group
peer as-number
peer enable
peer log-change
Use peer log-change to enable logging for BGP session state changes for a peer or peer group.
Use undo peer log-change to disable logging for BGP session state changes for a peer or peer group.
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } log-change
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } log-change
Logging for BGP session state changes is enabled for all peers or peer groups.
network-admin
group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must already exist.
ipv4-address: Specifies the IPv4 address of a peer. The peer must already exist.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command enables the logging of BGP session state changes for all dynamic peers in the subnet.
ipv6-address: Specifies the IPv6 address of a peer. The peer must already exist.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command enables the logging of BGP session state changes for all dynamic peers in the subnet.
After you execute both the log-peer-change and peer log-change commands, BGP logs session establishment and disconnection events for the peer or peer group. To view the log information, use the display bgp peer ipv4 unicast log-info command or the display bgp peer ipv6 unicast log-info command. The logs are sent to the information center of the device. The output rules of the logs (whether to output the logs and where to output) are determined by the information center configuration. For more information about information center configuration, see System Management Configuration Guide.
If you disable logging for BGP session state changes globally or disable logging for a peer or peer group, BGP does not generate logs for session establishments and disconnections.
# In BGP instance view, enable logging for BGP session state changes for peer 1.1.1.1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer 1.1.1.1 as-number 200
[Sysname-bgp-default] peer 1.1.1.1 log-change
display bgp peer
log-peer-change
peer route-update-interval
Use peer route-update-interval to specify an interval for sending the same update to a peer or peer group.
Use undo peer route-update-interval to remove the configuration.
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } route-update-interval interval
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } route-update-interval
The interval for sending the same update to an IBGP peer is 15 seconds and the interval for sending the same update to an EBGP peer is 30 seconds.
network-admin
group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must have been created.
ipv4-address: Specifies a peer by its IPv4 address. The peer must have been created.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command specifies an interval for sending the same update to all dynamic peers in the subnet.
ipv6-address: Specifies a peer by its IPv6 address. The peer must have been created.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command specifies an interval for sending the same update to all dynamic peers in the subnet.
interval: Specifies a minimum interval for sending the same update message, in the range of 0 to 600 seconds.
A BGP router sends an update message to its peers when a route is changed. If the route changes frequently, the BGP router sends many updates for the route, resulting in routing flaps. By configuring the interval for sending the same update to a peer or peer group, you can avoid such routing flaps. This command does not take effect on withdrawn routes. For withdrawn routes, BGP sends the withdrawal messages immediately.
# In BGP instance view, set the interval for sending the same update to peer group test to 10 seconds.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer test as-number 100
[Sysname-bgp-default] peer test route-update-interval 10
peer soo
Use peer soo to configure the Site of Origin (SoO) attribute for a BGP peer or peer group.
Use undo peer soo to remove the configuration.
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } soo site-of-origin
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } soo
No SoO attribute is configured for a peer or peer group.
BGP IPv4 unicast address family view
BGP IPv6 unicast address family view
network-admin
group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must have been created.
ipv4-address: Specifies a peer by its IPv4 address. The peer must have been created.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command configures the SoO attribute for all dynamic peers in the subnet.
ipv6-address: Specifies a peer by its IPv6 address. The peer must have been created.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command configures the SoO attribute for all dynamic peers in the subnet.
site-of-origin: Specifies the SoO attribute, a string of 3 to 21 characters. The SoO attribute has the following formats:
· 16-bit AS number:32-bit user-defined number. For example, 100:3.
· 32-bit IP address:16-bit user-defined number. For example, 192.168.122.15:1.
· 32-bit AS number:16-bit user-defined number, where the minimum value of the AS number is 65536. For example, 65536:1.
The SoO attribute specifies the site where the route was originated. It prevents advertising a route back to the originating site. If the AS-path attribute is lost, the router can use the SoO attribute to avoid routing loops.
After you configure the SoO attribute for a BGP peer or peer group, BGP adds the SoO attribute into the route updates received from the BGP peer or peer group. Before advertising route updates to the peer or peer group, BGP checks the SoO attribute of the route update against the configured SoO attribute. If they are the same, BGP does not advertise the route updates to the BGP peer or peer group to avoid loops.
If a PE configured with AS number substitution connects to multiple CEs in the same VPN site through different interfaces, routing loops will occur. To avoid routing loops, configure the same SoO attribute for the CEs on the PE.
# In BGP IPv4 unicast address family view, set the SoO attribute to 100:1 for peer 1.1.1.1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4
[Sysname-bgp-default-ipv4] peer 1.1.1.1 soo 100:1
peer substitute-as
peer source-address
Use peer source-address to specify a source IPv4 or IPv6 address for establishing TCP connections to a peer or peer group.
Use undo peer source-address to remove the configuration.
peer ipv4-address [ mask-length ] source-address source-ipv4-address
peer ipv6-address [ prefix-length ] source-address source-ipv6-address
undo peer { ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } source-address
peer group-name source-address { source-ipv4-address | source-ipv6-address } *
undo peer group-name source-address [ source-ipv4-address | source-ipv6-address ]
BGP uses the primary IPv4 or IPv6 address of the output interface in the optimal route destined for the BGP peer or peer group as the source address for TCP connection establishment.
network-admin
ipv4-address: Specifies a peer by its IPv4 address. The peer must have been created.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command specifies a source IP address for establishing TCP connections to all dynamic peers in the subnet.
source-ipv4-address: Specifies a source IPv4 address.
ipv6-address: Specifies a peer by its IPv6 address. The peer must have been created.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command specifies a source IPv6 address for establishing TCP connections to all dynamic peers in the subnet.
source-ipv6-address: Specifies a source IPv6 address.
group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must have been created.
The peer connect-interface command and the peer source-address command can both change the source address for establishing TCP connections. If you execute both commands, the most recent configuration takes effect.
The peer source-address and peer connect-interface commands are applicable to the following scenarios:
· The peer's IPv4/IPv6 address does not belong to the interface directly connected to the local router. To ensure successful TCP connection establishment, use one of the following methods:
¡ Specify the interface to which the IPv4/IPv6 address belongs as the source interface on the peer.
¡ Specify the IPv4/IPv6 address of the interface directly connected to the local router as the source address on the peer.
· A BGP peer at an IPv6 link-local address must be directly connected to the local router. On the local router, you must use the peer connect-interface command to specify the interface directly connected to the BGP peer as the source interface of TCP connections.
· On a BGP router that has multiple links to a peer, the source interface for TCP connection changes because the primary source interface fails. To avoid this problem, specify a loopback interface as the source interface or specify the IP address of a loopback interface as the source address.
· You want to establish multiple BGP sessions to a router. In this case, BGP might fail to determine the source address for each TCP connection based on the optimal route to the peer. To prevent this problem, use one of the following methods:
¡ If the BGP sessions use IP addresses of different interfaces, specify a source interface or source address for each session.
¡ If the BGP sessions use different IP addresses of the same interface, specify a source address for each session.
The source addresses on the local router and the peer must be reachable to each other.
To specify the address of an indirectly connected interface as the source address, use the peer ebgp-max-hop command. The command allows the establishment of an EBGP session to the indirectly connected peer.
You can specify both a source IPv4 address and a source IPv6 address for a peer group. BGP uses the source IPv4 address to establish TCP connections to IPv4 peers in the group. It also uses the source IPv6 address to establish TCP connections to IPv6 peers in the group.
# In BGP instance view, specify source IPv4 address 1.1.1.1 for peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer test source-address 1.1.1.1
peer connect-interface
peer ebgp-max-hop
peer timer
Use peer timer to set a keepalive interval and hold time for a peer or peer group.
Use undo peer timer to remove the configuration.
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } timer keepalive keepalive hold holdtime
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } timer
The keepalive interval is 60 seconds, and the hold time is 180 seconds.
network-admin
group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must have been created.
ipv4-address: Specifies a peer by its IPv4 address. The peer must have been created.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command configures a keepalive interval and hold time for all dynamic peers in the subnet.
ipv6-address: Specifies a peer by its IPv6 address. The peer must have been created.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command configures a keepalive interval and hold time for all dynamic peers in the subnet.
keepalive keepalive: Sets a keepalive interval in the range of 0 to 21845 seconds.
hold holdtime: Sets a hold time in the range of 3 to 65535 seconds. The hold time must be at least three times the keepalive interval.
After establishing a BGP session, two routers send keepalive messages at the specified keepalive interval to each other to keep the session.
If a router receives no keepalive or update message from the peer within the hold time, it tears down the session.
The timers configured with this command are preferred to the timers configured with the timer command.
If the hold time settings on the local and peer routers are different, the smaller one is used.
If the hold time is set to 0, no keepalive message will be sent to the peer, and the peer session will never time out. If neither the hold time nor the keepalive interval is set to 0, the actual keepalive interval is the smaller one between one third of the hold time and the keepalive interval.
The timers configured with this command do not take effect until a session is re-established (for example, a session is reset).
# In BGP instance view, set the keepalive interval and hold time for peer group test to 60 seconds and 180 seconds, respectively.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer test timer keepalive 60 hold 180
display bgp peer
timer
peer timer connect-retry
Use peer timer connect-retry to set the session retry timer for a peer or peer group.
Use undo peer timer connect-retry to remove the configuration.
Syntax
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } timer connect-retry retry-time
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } timer connect-retry
Default
The session retry timer is 32 seconds a peer or peer group.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must have been created.
ipv4-address: Specifies a peer by its IPv4 address. The peer must have been created.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command sets a connection retry timer for all dynamic peers in the subnet.
ipv6-address: Specifies a peer by its IPv6 address. The peer must have been created.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command sets a connection retry timer for all dynamic peers in the subnet.
retry-time: Specifies a session retry timer in the range of 1 to 65535 seconds.
Usage guidelines
To speed up session establishment to a peer or peer group and route convergence, set a small session retry timer. If the BGP session flaps, you can set a large session retry timer to reduce the impact.
The timer set by the peer timer connect-retry command takes precedence over the timer set by the timer connect-retry command.
Examples
# In BGP instance view, set the session retry timer to 30 seconds for peer 1.1.1.1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer 1.1.1.1 timer connect-retry 30
Related commands
timer connect-retry
refresh bgp
Use refresh bgp to manually soft-reset BGP sessions.
refresh bgp [ instance instance-name ] { ipv4-address [ mask-length ] | all | external | group group-name | internal } { export | import } ipv4 [ unicast ]
refresh bgp [ instance instance-name ] { ipv6-address [ prefix-length ] | all | external | group group-name | internal } { export | import } ipv6 [ unicast ]
refresh bgp [ instance instance-name ] ipv6-address [ prefix-length ] { export | import } ipv4 [ unicast ]
refresh bgp [ instance instance-name ] ipv4-address [ mask-length ] { export | import } ipv6 [ unicast ]
network-admin
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command soft-resets BGP sessions for the default BGP instance.
ipv4-address: Soft-resets the BGP session to a peer specified by its IP address.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command soft-resets BGP sessions to all dynamic peers in the subnet.
ipv6-address: Soft-resets the BGP session to a peer specified by its IPv6 address.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command soft-resets BGP sessions to all dynamic peers in the subnet.
all: Soft-resets all BGP sessions.
external: Soft-resets all EBGP sessions.
group group-name: Soft-resets the BGP sessions to the peers of the specified peer group. The group-name argument refers to the name of a peer group, a case-sensitive string of 1 to 47 characters.
internal: Soft-resets all IBGP sessions.
export: Performs outbound soft-reset (filters routes advertised to the specified peer or peer group by using the new configuration).
import: Performs inbound soft-reset (filters routes received from the specified peer or peer group by using the new configuration).
ipv4: Soft-resets BGP sessions for IPv4 address family.
ipv6: Soft-resets BGP sessions for IPv6 address family.
unicast: Soft-resets BGP sessions for unicast address family.
A soft-reset operation enables the router to apply a new route selection policy without tearing down BGP connections.
To apply a new policy to outbound BGP sessions, execute this command with the export keyword. The router uses the new policy to filter routing information and sends the routing information that passes the filtering to the BGP peers.
To apply a new policy to inbound sessions, execute this command with the import keyword. The router advertises a route-refresh message to the peer and the peer resends its routing information to the router. After receiving the routing information, the router uses the new policy to filter the routing information.
This command requires that both the local router and the peer support route refresh.
By default, the unicast keyword is used if the unicast keyword is not specified.
# Soft-reset all inbound BGP sessions for the IPv4 unicast address family.
<Sysname> refresh bgp all import ipv4
peer capability-advertise route-refresh
peer keep-all-routes
reset bgp
Use reset bgp to reset BGP sessions for the specified address family.
reset bgp [ instance instance-name ] { as-number | ipv4-address [ mask-length ] | all | external | group group-name | internal } ipv4 [ unicast ]
reset bgp [ instance instance-name ] { as-number | ipv6-address [ prefix-length ] | all | external | group group-name | internal } ipv6[ unicast ]
reset bgp [ instance instance-name ] ipv6-address [ prefix-length ] ipv4 [ unicast ]
reset bgp [ instance instance-name ] ipv4-address [ mask-length ] ipv6 [ unicast ]
network-admin
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command resets BGP sessions for the default BGP instance.
as-number: Resets BGP sessions to peers in the AS specified by its number in the range of 1 to 4294967295.
ipv4-address: Resets the BGP session to a peer specified by its IPv4 address.
mask-length: Specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command resets BGP sessions to all dynamic peers in the subnet.
ipv6-address: Resets the BGP session to a peer specified by its IPv6 address.
prefix-length: Specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command resets BGP sessions to all dynamic peers in the subnet.
all: Resets all BGP sessions.
external: Resets all EBGP sessions.
group group-name: Resets the BGP sessions to the peers in the peer group specified by its name, a case-sensitive string of 1 to 47 characters.
internal: Resets all IBGP sessions.
ipv4: Resets BGP sessions for IPv4 address family.
ipv6: Resets BGP sessions for IPv6 address family.
unicast: Resets BGP sessions for unicast address family.
A reset operation enables the router to apply a new route selection policy by re-establishing BGP sessions.
By default, the unicast keyword is used if the unicast keyword is not specified.
# Reset all BGP sessions for the IPv4 unicast address family.
reset bgp all
Use reset bgp all to reset all BGP sessions for all address families.
reset bgp [ instance instance-name ] all
network-admin
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command resets all BGP sessions for all address families of the default BGP instance.
A reset operation enables the router to apply a new route selection policy by re-establishing BGP sessions.
# Reset all BGP sessions.
reset bgp flap-info
Use reset bgp flap-info to clear flap statistics for BGP routes.
reset bgp [ instance instance-name ] flap-info ipv4[ unicast ] [ ipv4-address [ mask-length | mask ] | as-path-acl as-path-acl-number | peer ipv4-address [ mask-length ] ]
reset bgp [ instance instance-name ] flap-info ipv6[ unicast ] [ ipv6-address prefix-length | as-path-acl as-path-acl-number | peer ipv6-address [ prefix-length ] ]
network-admin
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command clears flap statistics for the default BGP instance.
ipv4: Clears flap statistics for BGP IPv4 routes.
ipv6: Clears flap statistics for BGP IPv6 routes.
unicast: Clears flap statistics for BGP unicast routes.
ipv4-address: Specifies an IPv4 destination network address.
mask-length: Specifies a mask length in the range of 0 to 32.
mask: Specifies a network mask in dotted decimal notation.
ipv6-address: Specifies an IPv6 destination network address.
prefix-length: Specifies a prefix length in the range of 0 to 128.
as-path-acl as-path-acl-number: Specifies an AS path list by its number in the range of 1 to 256, to filter BGP route flap statistics.
peer ipv4-address [ mask-length ]: Clears flap statistics for BGP routes learned from the specified IPv4 BGP peer. The mask-length argument specifies a mask length in the range of 0 to 32. You can use the ipv4-address and mask-length arguments together to specify a subnet. If you specify a subnet, this command clears flap statistics for BGP routes learned from all dynamic peers in the subnet.
peer ipv6-address [ prefix-length ]: Clears flap statistics for BGP routes learned from the specified IPv6 BGP peer. The prefix-length argument specifies a prefix length in the range of 0 to 128. You can use the ipv6-address and prefix-length arguments together to specify a subnet. If you specify a subnet, this command clears flap statistics for BGP routes learned from all dynamic peers in the subnet.
When you execute the reset bgp flap-info ipv4 command:
· If you specify only the ipv4-address argument, the system ANDs the IPv4 network address with the mask of a BGP IPv4 unicast route. If the result matches the IPv4 network address of the route, this command clears the flap statistics of the route.
· If you specify the ipv4-address mask or ipv4-address mask-length argument, this command clears the flap statistics of the BGP IPv4 unicast route that matches both the specified IPv4 destination network address and the mask (or mask length).
By default, the unicast keyword is used.
# Clear flap statistics for the BGP IPv4 unicast route to network 20.1.0.0/16.
<Sysname> reset bgp flap-info ipv4 20.1.0.0 16
dampening
display bgp routing-table flap-info
router id
Use router id to configure a global router ID.
Use undo router id to restore the default.
router id router-id
undo router id
No global router ID is configured.
network-admin
router-id: Specifies a router ID in IP address format.
Some routing protocols use a router ID to identify a device. You can configure a global router ID, which is used by routing protocols that have no router ID configured.
If no global router ID is configured, the highest loopback address, if any, is used as the router ID. If no loopback address is available, the highest physical interface IP address is used, regardless of the interface status. If no IP address is configured for any interface, the router ID is 0.0.0.0. BGP cannot use router ID 0.0.0.0 for peer session establishment, because the router ID is invalid.
During an active/standby switchover, the standby main processing unit (MPU) checks the validity of the previous router ID backed up before switchover. If it is not valid, it selects a new router ID.
If the interface IP address that is selected as the router ID is removed or modified, a new router ID is selected. The following events will not trigger a router ID re-selection:
· The interface goes down.
· After a physical interface address is selected as the router ID, an IP address is configured for a loopback interface.
· A higher interface IP address is configured.
After you modify the global router ID and reset BGP sessions, the modification does not take effect for a BGP instance that uses the global router ID. To modify the router ID for the BGP instance, use the router-id command in BGP instance view.
# Configure a global router ID as 1.1.1.1.
<Sysname> system-view
[Sysname] router id 1.1.1.1
router-id (BGP instance view)
router-id (BGP instance view)
Use router-id to configure a router ID for a BGP instance.
Use undo router-id to restore the default.
router-id router-id
undo router-id
No router ID is configured for a BGP instance, and the BGP instance uses the global router ID configured by the router id command in system view.
network-admin
router-id: Specifies a router ID for BGP, in IP address format.
To run BGP, a BGP instance must have a router ID, which is an unsigned 32-bit integer that uniquely identifies the router in the AS.
To modify a non-zero router ID for BGP, execute the router-id command in BGP instance view.
To improve availability, specify the IP address of a loopback interface as the router ID for BGP.
If you execute this command in the same BGP instance view multiple times, the most recent configuration takes effect.
You can configure the same router ID for different BGP instances.
# In BGP instance view, set the router ID for BGP to 1.1.1.1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] router-id 1.1.1.1
router id
snmp context-name
Use snmp context-name to configure an SNMP context for a BGP instance.
Use undo snmp context-name to restore the default.
snmp context-name context-name
undo snmp context-name
No SNMP context is configured for a BGP instance.
network-admin
context-name: Specifies an SNMP context by its name, a case-sensitive string of 1 to 32 characters.
BGP does not know the BGP instance to which a managed MIB node belongs. To resolve this issue, configure different SNMP contexts for different BGP instances.
The device selects a MIB for an SNMP packet according to the context (for SNMPv3) or community name (for SNMPv1/v2c) in the following ways:
· For an SNMPv3 packet:
¡ The device selects the MIB of the BGP instance default if the packet does not carry a context and no SNMP context was configured for the BGP instance default.
¡ The device selects the MIB of a BGP instance if the packet meets the following conditions:
- Carries a context that was configured with the snmp-agent context command in system view.
- Matches the context of the BGP instance.
¡ The device does not process any MIBs in other situations.
· For an SNMPv1/v2c packet:
¡ The device selects the MIB of the BGP instance default if the following conditions are met:
- No SNMP community to SNMP context mapping was configured with the snmp-agent community-map command in system view.
- No SNMP context was configured for the BGP instance default.
¡ The device selects the MIB of a BGP instance if the SNMP community is mapped to an SNMP context and the context matches the context of the BGP instance.
¡ The device does not process any MIBs in other situations.
For more information about SNMP contexts and community names, see Network Management and Monitoring Configuration Guide.
Do not configure the same SNMP context for different BGP instances.
If you execute this command multiple times, the most recent configuration takes effect.
# Configure SNMP context bgp-abc for BGP instance abc.
<Sysname> system-view
[Sysname] bgp 100 instance abc
[Sysname-bgp-abc] snmp context-name bgp-abc
snmp-agent community-map (Network Management and Monitoring Command Reference)
snmp-agent context (Network Management and Monitoring Command Reference)
snmp-agent trap enable bgp
Use snmp-agent trap enable bgp to enable SNMP notifications for BGP.
Use undo snmp-agent trap enable bgp to disable SNMP notifications for BGP.
snmp-agent trap enable bgp [ instance instance-name ]
undo snmp-agent trap enable bgp [ instance instance-name ]
SNMP notifications for BGP are enabled.
network-admin
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command enables SNMP notifications for the default BGP instance.
After you enable SNMP notifications for BGP, the device generates a notification when a BGP neighbor state change occurs. The notification includes the neighbor address, the error code and subcode of the most recent error, and the current neighbor state.
For BGP notifications to be sent correctly, you must also configure SNMP on the device. For more information about SNMP configuration, see the network management and monitoring configuration guide for the device.
# Enable SNMP notifications for BGP.
<Sysname> system-view
[Sysname] snmp-agent trap enable bgp
summary automatic
Use summary automatic to configure automatic route summarization for redistributed IGP subnet routes.
Use undo summary automatic to restore the default.
summary automatic
undo summary automatic
Automatic route summarization is not performed for redistributed IGP subnet routes.
BGP IPv4 unicast address family view
network-admin
After the summary automatic command is configured, BGP summarizes IGP subnets redistributed by the import-route command.
Automatic summary routes can be manually summarized, but cannot be added to the IP routing table.
# In BGP IPv4 unicast address family view, configure automatic route summarization for redistributed IGP subnet routes.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] summary automatic
aggregate
import-route
timer
Use timer to configure a BGP keepalive interval and hold time.
Use undo timer to restore the default.
timer keepalive keepalive hold holdtime
undo timer
The BGP keepalive interval and the hold time are 60 seconds and 180 seconds, respectively.
network-admin
keepalive keepalive: Configures a keepalive interval in the range of 0 to 21845 seconds.
hold holdtime: Configures a hold time in seconds, whose value is 0 or in the range of 3 to 65535. The hold time must be at least three times the keepalive interval.
After establishing a BGP session, two routers send keepalive messages at the specified keepalive interval to each other to keep the session.
If a router receives no keepalive or update message from the peer within the hold time, it tears down the session.
Use the timer command to configure the keepalive interval and hold time for all BGP peers. Use the peer timer command to configure the keepalive interval and hold time for a peer or peer group. If both commands are configured, the intervals configured by the peer timer command have higher priority.
If the hold time settings on the local and peer routers are different, the smaller one is used.
If the hold time is set to 0, no keepalive message will be sent to the peer, and the peer session will never time out. If neither the hold time nor the keepalive interval is set to 0, the actual keepalive interval is the smaller one between one third of the hold time and the keepalive interval.
The timer command affects only new BGP sessions.
After the timer command is executed, no peer session is closed at once. The configured hold time is used for negotiation in session re-establishment (for example, when you reset the BGP session).
# In BGP instance view, set the keepalive interval and hold time to 60 seconds and 180 seconds, respectively.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] timer keepalive 60 hold 180
display bgp peer
peer timer
timer connect-retry
Use timer connect-retry to set the session retry timer for all peers and peer groups.
Use undo timer connect-retry to restore the default.
Syntax
timer connect-retry retry-time
undo timer connect-retry
Default
The session retry timer is 32 seconds for all peers and peer groups.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
retry-time: Specifies a session retry timer in the range of 1 to 65535 seconds.
Usage guidelines
To speed up session establishment to a peer or peer group and route convergence, set a small session retry timer. If the BGP session flaps, you can set a large session retry timer to reduce the impact.
The timer set by the peer timer connect-retry command takes precedence over the timer set by the timer connect-retry command.
Examples
# In BGP instance view, set the session retry timer to 30 seconds for all peers.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] timer connect-retry 30
Related commands
peer timer connect-retry