Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 01-Text | 3.36 MB |
display ip routing-table ip-address
display ip routing-table prefix-list
display ip routing-table protocol
display ip routing-table statistics
display ip routing-table summary
display ipv6 rib graceful-restart
display ipv6 routing-table acl
display ipv6 routing-table ipv6-address
display ipv6 routing-table prefix-list
display ipv6 routing-table protocol
display ipv6 routing-table statistics
display ipv6 routing-table summary
reset ip routing-table statistics protocol
reset ipv6 routing-table statistics protocol
display route-static routing-table
ip route-static default-preference
ip route-static fast-reroute auto
ip route-static primary-path-detect bfd echo
bandwidth-reference (OSPF view)
database-filter peer (OSPF view)
default-route-advertise (OSPF view)
description (OSPF/OSPF area view)
display ospf fast-reroute lfa-candidate
display ospf non-stop-routing status
enable out-of-band-resynchronization
filter-policy export (OSPF view)
filter-policy import (OSPF view)
graceful-restart helper enable
graceful-restart helper strict-lsa-checking
graceful-restart interval (OSPF view)
maximum load-balancing (OSPF view)
display isis graceful-restart event-log
display isis graceful-restart status
display isis non-stop-routing event-log
display isis non-stop-routing status
domain-authentication send-only
import-route isis level-1 into level-2
import-route isis level-2 into level-1
isis fast-reroute lfa-backup exclude
reset isis graceful-restart event-log
reset isis non-stop-routing event-log
bgp update-delay on-startup prefix-list
display bgp dampening parameter
display bgp non-stop-routing status
display bgp routing-table dampened
display bgp routing-table flap-info
display bgp routing-table ipv4 multicast
display bgp routing-table ipv4 rtfilter
display bgp routing-table ipv4 unicast
display bgp routing-table ipv6 multicast
display bgp routing-table ipv6 unicast
display bgp routing-table ipv6 unicast inlabel
display bgp routing-table ipv6 unicast outlabel
graceful-restart timer purge-time
graceful-restart timer restart
graceful-restart timer wait-for-rib
ip vpn-instance (BGP instance view)
peer advertise-policy exist-policy
peer advertise-policy non-exist-policy
peer as-number (for a BGP peer group)
peer as-number (for a BGP peer)
peer capability-advertise conventional
peer capability-advertise route-refresh
peer capability-advertise suppress-4-byte-as
router-id (BGP-VPN instance view)
apply default-output-interface
display ip policy-based-route interface
display ip policy-based-route local
display ip policy-based-route setup
reset ip policy-based-route statistics
display ipv6 route-static routing-table
ipv6 route-static default-preference
display ripng graceful-restart
display ripng non-stop-routing
ripng primary-path-detect bfd echo
abr-summary (OSPFv3 area view)
default-cost (OSPFv3 area view)
default-route-advertise (OSPFv3 view)
display ospfv3 graceful-restart
display ospfv3 non-stop-routing
filter-policy export (OSPFv3 view)
filter-policy import (OSPFv3 view)
graceful-restart helper enable
graceful-restart helper strict-lsa-checking
maximum load-balancing (OSPFv3 view)
ospfv3 fast-reroute lfa-backup exclude
ospfv3 primary-path-detect bfd
display isis redistribute ipv6
import-route isisv6 level-1 into level-2
import-route isisv6 level-2 into level-1
isis ipv6 fast-reroute lfa-backup exclude
isis ipv6 primary-path-detect bfd
IPv6 policy-based routing commands
apply default-output-interface
display ipv6 policy-based-route
display ipv6 policy-based-route interface
display ipv6 policy-based-route local
display ipv6 policy-based-route setup
ipv6 policy-based-route (interface view)
ipv6 policy-based-route (system view)
reset ipv6 policy-based-route statistics
Common routing policy commands
Basic IP routing commands
IPv6-related parameters are not supported on the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS.
· MSR3600-28-SI/3600-51-SI.
The topology parameter is not supported on the MSR810-LMS and MSR810-LUS routers.
address-family ipv4
Use address-family ipv4 to create a RIB IPv4 address family and enter its view, or enter the view of the existing RIB IPv4 address family.
Use undo address-family ipv4 to delete the RIB IPv4 address family and all configurations in the view.
Syntax
address-family ipv4
undo address-family ipv4
Default
No RIB IPv4 address family exists.
Views
RIB view
Predefined user roles
network-admin
Examples
# Create a RIB IPv4 address family and enter its view.
<Sysname> system-view
[Sysname] rib
[Sysname-rib] address-family ipv4
[Sysname-rib-ipv4]
address-family ipv6
Use address-family ipv6 to create a RIB IPv6 address family and enter its view, enter the view of the existing RIB IPv6 address family.
Use undo address-family ipv6 to delete the RIB IPv6 address family and all configurations in the view.
Syntax
address-family ipv6
undo address-family ipv6
Default
No RIB IPv6 address family exists.
Views
RIB view
Predefined user roles
network-admin
Examples
# Create a RIB IPv6 address family and enter its view.
<Sysname> system-view
[Sysname] rib
[Sysname-rib] address-family ipv6
[Sysname-rib-ipv6]
display ip routing-table
Use display ip routing-table to display routing table information.
Syntax
display ip routing-table [ topology topo-name | vpn-instance vpn-instance-name ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing table information for the public network.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing table information for the public network.
verbose: Displays detailed routing table information, including information about both active and inactive routes. If you do not specify this keyword, the command displays only brief information about active routes.
Examples
# Display brief information about active routes in the routing table.
<Sysname> display ip routing-table
Destinations : 10 Routes : 10
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
1.1.1.0/24 Static 60 0 192.168.47.4 GE1/0/1
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0
192.168.1.40/32 Direct 0 0 127.0.0.1 InLoop0
224.0.0.0/4 Direct 0 0 0.0.0.0 NULL0
224.0.0.0/24 Direct 0 0 0.0.0.0 NULL0
255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0
|
Field |
Description |
|
Destinations |
Number of destination addresses. |
|
Routes |
Number of routes. |
|
Destination/Mask |
Destination address/mask length. |
|
Proto |
Protocol that installed the route. |
|
Pre |
Preference of the route. |
|
Cost |
Cost of the route. |
|
NextHop |
Next hop address of the route. |
|
Interface |
Output interface for packets to be forwarded along the route. |
|
Summary count |
Number of routes. |
# Display detailed information about all routes in the routing table.
<Sysname> display ip routing-table verbose
Destinations : 13 Routes : 13
Destination: 0.0.0.0/32
Protocol: Direct
Process ID: 0
SubProtID: 0x0 Age: 08h34m37s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active NoAdv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x10000000 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1000c OrigNextHop: 127.0.0.1
Label: NULL RealNextHop: 127.0.0.1
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: InLoopBack0
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: 1.1.1.0/24
Protocol: Static
Process ID: 0
SubProtID: 0x0 Age: 04h20m37s
Cost: 0 Preference: 60
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x10000003 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1008c OrigNextHop: 192.168.47.4
Label: NULL RealNextHop: 192.168.47.4
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: GigabitEthernet1/0/1
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: 1.2.3.4/32
Protocol: BGP instance default
Process ID: 0
SubProtID: 0x1 Age: 02h38m34s
Cost: 0 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 200
NibID: 0x16000000 LastAs: 200
AttrID: 0x2 Neighbor: 2.2.3.4
Flags: 0x10060 OrigNextHop: 2.2.3.4
Label: NULL RealNextHop: 2.2.3.4
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: GigabitEthernet1/0/3
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
...
|
Field |
Description |
|
Destinations |
Number of destination addresses. |
|
Routes |
Number of routes. |
|
Destination |
Destination address/mask length. |
|
Protocol |
Protocol that installed the route. |
|
SubProtID |
ID of the subprotocol for routing. |
|
Age |
Time for which the route has been in the routing table. |
|
Cost |
Cost of the route. |
|
Preference |
Preference of the route. |
|
IpPre |
IP precedence. |
|
QosLocalID |
Local QoS ID. |
|
Tag |
Route tag. |
|
State |
Route status: · Active—Active unicast route. · Adv—Route that can be advertised. · Inactive—Inactive route. · NoAdv—Route that the router must not advertise. · Vrrp—Routes generated by VRRP. · Nat—Routes generated by NAT. · TunE—Tunnel. |
|
OrigTblID |
Original routing table ID. |
|
OrigVrf |
Original VPN instance to which the route belongs. This field displays default-vrf if the route is on the IPv4 public network. |
|
TableID |
ID of the routing table. |
|
OrigAs |
Original AS number. |
|
NibID |
ID of the next hop. |
|
LastAs |
Last AS number. |
|
AttrID |
Attribute ID. |
|
Neighbor |
Address of the neighbor determined by the routing protocol. |
|
Flags |
Flags of the route. |
|
OrigNextHop |
Next hop address of the route. |
|
RealNextHop |
Real next hop of the route. |
|
BkLabel |
Backup label. |
|
BkNexthop |
Backup next hop. |
|
Interface |
Output interface for packets to be forwarded along the route. |
|
BkTunnel ID |
Backup tunnel ID. |
|
BkInterface |
Backup output interface. |
|
FtnIndex |
Index of the FTN entry. |
|
Traffic index in the range of 1 to 64. This field displays N/A when the value is invalid. |
|
|
BGP connector attribute exchanged between BGP peers along with a VPN IPv4 route. The value of the attribute is the IP address of the remote PE device. The BGP connector attribute is used for MD VPN. This field displays N/A if the attribute is not configured. |
|
|
VpnPeerId |
ID of the VPN peer to which the route belongs, in the range of 1 to 134217727. This field displays N/A when the value is invalid. |
|
Dscp |
DSCP value of the route, in the range of 0 to 63. This field displays N/A when the value is invalid. |
|
Summary count |
Number of routes. |
display ip routing-table acl
Use display ip routing-table acl to display information about routes permitted by a basic ACL.
Syntax
display ip routing-table [ topology topo-name | vpn-instance vpn-instance-name ] acl ipv4-acl-number [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing information for the public network.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing information for the public network.
ipv4-acl-number: Specifies a basic ACL by its number in the range of 2000 to 2999.
verbose: Displays detailed information about all routes permitted by the basic ACL. If you do not specify this keyword, the command displays only brief information about active routes permitted by the basic ACL.
Usage guidelines
If the specified ACL does not exist or has no rules configured, the command displays information about all routes.
Examples
# Define basic ACL 2000 and set the route filtering rules.
<Sysname> system-view
[Sysname] acl basic 2000
[Sysname-acl-ipv4-basic-2000] rule permit source 192.168.1.0 0.0.0.255
[Sysname-acl-ipv4-basic-2000] rule deny source any
# Display brief information about active routes permitted by basic ACL 2000.
[Sysname-acl-ipv4-basic-2000] display ip routing-table acl 2000
Summary count : 4
Destination/Mask Proto Pre Cost NextHop Interface
192.168.1.0/24 Direct 0 0 192.168.1.111 GE1/0/1
192.168.1.0/32 Direct 0 0 192.168.1.111 GE1/0/1
192.168.1.111/32 Direct 0 0 127.0.0.1 InLoop0
192.168.1.255/32 Direct 0 0 192.168.1.111 GE1/0/1
For command output, see Table 1.
# Display detailed information about all routes permitted by basic ACL 2000.
<Sysname> display ip routing-table acl 2000 verbose
Summary count : 4
Destination: 192.168.1.0/24
Protocol: Direct
Process ID: 0
SubProtID: 0x1 Age: 04h20m37s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x10000003 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x10080 OrigNextHop: 192.168.1.111
Label: NULL RealNextHop: 192.168.1.111
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: GigabitEthernet1/0/1
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: 192.168.1.0/32
Protocol: Direct
Process ID: 0
SubProtID: 0x0 Age: 04h20m37s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active NoAdv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x10000003 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1008c OrigNextHop: 192.168.1.111
Label: NULL RealNextHop: 192.168.1.111
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: GigabitEthernet1/0/1
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: 192.168.1.111/32
Protocol: Direct
Process ID: 0
SubProtID: 0x1 Age: 04h20m37s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active NoAdv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x10000000 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x10004 OrigNextHop: 127.0.0.1
Label: NULL RealNextHop: 127.0.0.1
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: InLoopBack0
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: 192.168.1.255/32
Protocol: Direct
Process ID: 0
SubProtID: 0x0 Age: 04h20m37s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active NoAdv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x10000003 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1008c OrigNextHop: 192.168.1.111
Label: NULL RealNextHop: 192.168.1.111
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: GigabitEthernet1/0/1
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
For command output, see Table 2.
display ip routing-table ip-address
Use display ip routing-table ip-address to display information about routes to a specific destination address.
Use display ip routing-table ip-address1 to ip-address2 to display information about routes to a range of destination addresses.
Syntax
display ip routing-table [ topology topo-name | vpn-instance vpn-instance-name ] ip-address [ mask | mask-length ] [ longer-match ] [ verbose ]
display ip routing-table [ topology topo-name | vpn-instance vpn-instance-name ] ip-address1 to ip-address2 [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing information for the public network.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing information for the public network.
ip-address: Specifies a destination IP address in dotted decimal notation.
mask: Specifies the IP address mask in dotted decimal notation.
mask-length: Specifies the mask length, an integer in the range of 0 to 32.
longer-match: Displays the route entry with the longest mask.
ip-address1 to ip-address2: Specifies a destination IP address range.
verbose: Displays detailed routing table information, including information about both active and inactive routes. If you do not specify this keyword, the command displays brief information about active routes.
Usage guidelines
Executing the command with different parameters yields different outputs.
· display ip routing-table ip-address
¡ The system ANDs the entered destination IP address with the subnet mask in each active route entry.
¡ The system ANDs the destination IP address in each active route entry with its own subnet mask.
If the two operations yield the same result for an entry, the entry is displayed.
· display ip routing-table ip-address mask
¡ The system ANDs the entered destination IP address with the entered subnet mask.
¡ The system ANDs the destination IP address in each active route entry with the entered subnet mask.
If the two operations yield the same result for an entry with a subnet mask not greater than the entered subnet mask, the entry is displayed.
· display ip routing-table ip-address longer-match
¡ The system ANDs the entered destination IP address with the subnet mask in each active route entry.
¡ The system ANDs the destination IP address in each active route entry with its own subnet mask.
If the two operations yield the same result for multiple entries, the entry with the longest mask length is displayed.
· display ip routing-table ip-address mask longer-match
¡ The system ANDs the entered destination IP address with the entered subnet mask.
¡ The system ANDs the destination IP address in each active route entry with the entered subnet mask.
If the two operations yield the same result for multiple entries with a mask not greater than the entered subnet mask, the entry with the longest mask length is displayed.
· display ip routing-table ip-address1 to ip-address2
The system displays active route entries with destinations in the range of ip-address1/32 to ip-address2/32.
Examples
# Display brief information about the routes to the destination IP address 11.0.0.1.
<Sysname> display ip routing-table 11.0.0.1
Summary count : 3
Destination/Mask Proto Pre Cost NextHop Interface
11.0.0.0/8 Static 60 0 0.0.0.0 NULL0
11.0.0.0/16 Static 60 0 0.0.0.0 NULL0
11.0.0.0/24 Static 60 0 0.0.0.0 NULL0
# Display brief information about the routes to the destination IP address 11.0.0.1 and mask length 20.
<Sysname> display ip routing-table 11.0.0.1 20
Summary count : 2
Destination/Mask Proto Pre Cost NextHop Interface
11.0.0.0/8 Static 60 0 0.0.0.0 NULL0
11.0.0.0/16 Static 60 0 0.0.0.0 NULL0
# Display brief information about the most specific route to the destination address 11.0.0.1.
<Sysname> display ip routing-table 11.0.0.1 longer-match
Summary count : 1
Destination/Mask Proto Pre Cost NextHop Interface
11.0.0.0/24 Static 60 0 0.0.0.0 NULL0
# Display brief information about the most specific route to the destination IP address 11.0.0.1 and mask length 20.
<Sysname> display ip routing-table 11.0.0.1 20 longer-match
Summary count : 1
Destination/Mask Proto Pre Cost NextHop Interface
11.0.0.0/16 Static 60 0 0.0.0.0 NULL0
# Display brief information about the routes to destination addresses in the range of 1.1.1.0 to 5.5.5.0.
<Sysname> display ip routing-table 1.1.1.0 to 5.5.5.0
Summary count : 5
Destination/Mask Proto Pre Cost NextHop Interface
1.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0
3.3.3.0/24 Direct 0 0 3.3.3.1 GE1/0/2
3.3.3.1/32 Direct 0 0 127.0.0.1 InLoop0
4.4.4.0/24 Direct 0 0 4.4.4.1 GE1/0/1
4.4.4.1/32 Direct 0 0 127.0.0.1 InLoop0
# Display detailed information about the routes to the destination IP address 1.2.3.4.
<Sysname> display ip routing-table 1.2.3.4 verbose
Summary count : 1
Destination: 1.2.3.4/32
Protocol: BGP instance test
Process ID: 0
SubProtID: 0x1 Age: 00h00m37s
Cost: 0 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 200
NibID: 0x15000000 LastAs: 200
AttrID: 0x0 Neighbor: 192.168.47.2
Flags: 0x10060 OrigNextHop: 192.168.47.2
Label: NULL RealNextHop: 192.168.47.2
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: GigabitEthernet1/0/1
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
For command output, see Table 1.
display ip routing-table prefix-list
Use display ip routing-table prefix-list to display routes permitted by an IP prefix list.
Syntax
display ip routing-table [ topology topo-name | vpn-instance vpn-instance-name ] prefix-list prefix-list-name [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing information for the public network.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing information for the public network.
prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters.
verbose: Displays detailed information about all routes permitted by the IP prefix list. If you do not specify this keyword, the command displays brief information about active routes permitted by the IP prefix list.
Usage guidelines
If the specified IP prefix list does not exist, the command displays information about all routes.
Examples
# Create an IP prefix list named test to permit the route 1.1.1.0/24.
<Sysname> system-view
[Sysname] ip prefix-list test permit 1.1.1.0 24
# Display brief information about the active route permitted by the IP prefix list.
[Sysname] display ip routing-table prefix-list test
Summary count : 1
Destination/Mask Proto Pre Cost NextHop Interface
1.1.1.0/24 Direct 0 0 1.1.1.2 GE1/0/2
For command output, see Table 1.
# Display detailed information about all routes permitted by the IP prefix list.
[Sysname] display ip routing-table prefix-list test verbose
Summary count : 1
Destination: 1.1.1.0/24
Protocol: Direct
Process ID: 0
SubProtID: 0x1 Age: 04h20m37s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x10000003 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1008c OrigNextHop: 1.1.1.2
Label: NULL RealNextHop: 1.1.1.2
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: GigabitEthernet1/0/2
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
For command output, see Table 2.
display ip routing-table protocol
Use display ip routing-table protocol to display information about routes installed by a protocol.
Syntax
display ip routing-table [ topology topo-name | vpn-instance vpn-instance-name ] protocol protocol [ inactive | verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing information for the public network.
vpn-instance vpn-instance-name: Specifies MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing information for the public network.
protocol: Specifies a routing protocol.
inactive: Displays information about inactive routes. If you do not specify this keyword, the command displays information about both active and inactive routes.
verbose: Displays detailed routing table information. If you do not specify this keyword, the command displays brief routing information.
Examples
# Display brief information about direct routes.
<Sysname> display ip routing-table protocol direct
Summary count : 9
Direct Routing Table Status : <Active>
Summary count : 9
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0
192.168.80.0/24 Direct 0 0 192.168.80.10 GE1/0/1
192.168.80.0/32 Direct 0 0 192.168.80.10 GE1/0/1
192.168.80.10/32 Direct 0 0 127.0.0.1 InLoop0
192.168.80.255/32 Direct 0 0 192.168.80.10 GE1/0/1
Direct Routing Table Status : <Inactive>
Summary count : 0
# Display brief information about static routes.
<Sysname> display ip routing-table protocol static
Summary count : 1
Static Routing Table Status : <Active>
Summary count : 0
Static Routing Table Status : <Inactive>
Summary count : 1
Destination/Mask Proto Pre Cost NextHop Interface
3.0.0.0/8 Static 60 0 2.2.2.2 GE1/0/1
# Display detailed information about BGP routes.
<Sysname> display ip routing-table protocol bgp verbose
Summary count : 1
Destination: 1.1.1.2/32
Protocol: BGP instance default
Process ID: 0
SubProtID: 0x6 Age: 00h03m54s
Cost: 0 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 200
NibID: 0x16000000 LastAs: 200
AttrID: 0x0 Neighbor: 192.168.47.2
Flags: 0x10060 OrigNextHop: 192.168.47.2
Label: NULL RealNextHop: 192.168.47.2
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: GigabitEthernet1/0/1
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
For command output, see Table 1.
display ip routing-table statistics
Use display ip routing-table statistics to display IPv4 route statistics, including numbers of total routes, routes installed by the protocol, routes marked as deleted, and active routes.
Syntax
display ip routing-table [ topology topo-name | vpn-instance vpn-instance-name ] statistics
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays IPv4 route statistics for the public network.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays IPv4 route statistics for the public network.
Examples
# Display IPv4 route statistics for the public network.
<Sysname> display ip routing-table statistics
Total prefixes: 15 Active prefixes: 15
Proto route active added deleted
DIRECT 12 12 30 18
STATIC 3 3 5 2
RIP 0 0 0 0
OSPF 0 0 0 0
IS-IS 0 0 0 0
LISP 0 0 0 0
BGP 0 0 0 0
Total 15 15 35 20
Table 3 Command output
|
Field |
Description |
|
Proto |
Protocol that installed the route. |
|
route |
Number of routes installed by the protocol. |
|
active |
Number of active routes. |
|
added |
Number of routes added to the routing table after the router started up or the routing table was cleared most recently. |
|
deleted |
Number of routes marked as deleted, which will be cleared after a period. |
|
Total |
Total number of routes. |
display ip routing-table summary
Use display ip routing-table summary to display brief routing table information, including maximum number of ECMP routes, maximum number of active routes, and number of remaining active routes.
Syntax
display ip routing-table [ topology topo-name | vpn-instance vpn-instance-name ] summary
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. The name base indicates the base topology. If you do not specify a topology, this command displays brief routing table information for the public network.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify an MPLS L3VPN instance, this command displays brief routing table information for the public network.
Examples
# Display brief routing table information for the public network.
<Sysname> display ip routing-table summary
Max ECMP: 32
Max Active Route: 262144
Remain Active Route: 262126
# Display brief routing table information for the MPLS L3VPN instance vpn1.
<Sysname> display ip routing-table vpn-instance vpn1 summary
Max ECMP: 32
Max Active Route: 262144
Remain Active Route: 262134
Threshold value of active routes alert: 65100
|
Field |
Description |
|
Max ECMP |
Maximum number of ECMP routes supported by the system. |
|
Max Active Route |
Maximum number of supported routes. |
|
Remain Active Route |
Number of the remaining inactive routes. |
|
Threshold value of active routes alert |
Alarm threshold of active routes specified by using the routing-table limit command in a VPN instance: · Threshold value of active routes alert—This field is displayed when the alarm threshold is specified by using the routing-table limit number simply-alert command. When the number of active routes exceeds the alarm threshold, the system logs the event and sends traps but still accepts active routes. · Threshold value percentage of max active routes—This field is displayed when the alarm threshold is specified by using the routing-table limit number warn-threshold command, in the range of 1 to 100 in percentage. When the percentage of active routes exceeds the alarm threshold, the system logs the event and sends traps but still accepts active routes. If the number of active routes reaches the maximum number, no more routes can be added. The percentage of active routes equals the number of active routes divided by the maximum number of active routes supported in a VPN instance, and multiplied by 100. |
display ipv6 rib attribute
Use display ipv6 rib attribute to display route attribute information in the IPv6 RIB.
Syntax
display ipv6 rib attribute [ attribute-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
attribute-id: Specifies a route attribute by its ID, a hexadecimal number in the range of 0 to ffffffff.
Examples
# Display route attribute information in the IPv6 RIB.
<Sysname> display ipv6 rib attribute
Total number of attribute(s): 1
Detailed information of attribute 0x9:
Flag: 0x0
Protocol: BGP4+ instance default
Address family: IPv6
Reference count: 0
Local preference: 0
Ext-communities number: 0
Ext-communities value: N/A
Communities number: 0
Communities value: N/A
AS-path number: 0
AS-path value: N/A
For command output, see Table 10.
display ipv6 rib graceful-restart
Use display ipv6 rib graceful-restart to display IPv6 RIB GR state information.
Syntax
display ipv6 rib graceful-restart
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display IPv6 RIB GR state information.
<Sysname> display ipv6 rib graceful-restart
RIB GR state : Phase2-calculation end
RCOM GR state : Flush end
Protocol GR state:
No. Protocol Lifetime FD State Start/End
--------------------------------------------------
1 DIRECT6 480 29 End No/No
2 STATIC6 480 32 End No/No
3 ISISV6 480 30 End No/No
4 BGP4+ instance default
480 31 End No/No
5 BGP4+ instance ebcdefg
480 32 End No/No
For command output, see Table 11.
display ipv6 rib nib
Use display ipv6 rib nib to display next hop information in the IPv6 RIB.
Syntax
display ipv6 rib nib [ self-originated ] [ nib-id ] [ verbose ]
display ipv6 rib nib protocol protocol [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
self-originated: Displays information about next hops of self-originated routes in the IPv6 RIB.
nib-id: Specifies a NIB by its ID, a hexadecimal number in the range of 1 to ffffffff.
verbose: Displays detailed next hop information in the IPv6 RIB. If you do not specify this keyword, the command displays brief next hop information in the IPv6 RIB.
protocol protocol: Specifies a protocol by its name.
Examples
# Display brief next hop information in the IPv6 RIB.
<Sysname> display ipv6 rib nib
Total number of nexthop(s): 151
NibID: 0x20000000 Sequence: 0
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: ::
IFIndex: 0x111 LocalAddr: ::
TopoNthp: Invalid
NibID: 0x20000001 Sequence: 1
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: ::1
IFIndex: 0x112 LocalAddr: ::1
TopoNthp: Invalid
...
# Display detailed next hop information in the IPv6 RIB.
<Sysname> display ipv6 rib nib verbose
Total number of nexthop(s): 151
NibID: 0x20000000 Sequence: 0
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: ::
IFIndex: 0x111 LocalAddr: ::
TopoNthp: Invalid
RefCnt: 4 FlushRefCnt: 1
Flag: 0x84 Version: 1
1 nexthop(s):
PrefixIndex: 0 OrigNexthop: ::
RelyDepth: 0 RealNexthop: ::
Interface: NULL0 LocalAddr: ::
TunnelCnt: 0 Vrf: default-vrf
TunnelID: N/A Topology:
Weight: 0
NibID: 0x20000001 Sequence: 1
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: ::1
IFIndex: 0x112 LocalAddr: ::1
TopoNthp: Invalid
RefCnt: 4 FlushRefCnt: 1
Flag: 0x84 Version: 1
1 nexthop(s):
PrefixIndex: 0 OrigNexthop: ::1
RelyDepth: 0 RealNexthop: ::1
Interface: InLoop0 LocalAddr: ::1
TunnelCnt: 0 Vrf: default-vrf
TunnelID: N/A Topology:
Weight: 0
NibID: 0x26000001 Sequence: 1
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 121::2
IFIndex: 0x112 LocalAddr: ::
TopoNthp: Invalid
Instance: default
NibID: 0x26000002 Sequence: 1
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 122::2
IFIndex: 0x112 LocalAddr: ::
TopoNthp: Invalid
Instance: abc
...
For command output, see Table 12 and Table 13.
display ipv6 route-direct nib
Use display ipv6 route-direct nib to display next hop information for IPv6 direct routes.
Syntax
display ipv6 route-direct nib [ nib-id ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
nib-id: Specifies a NIB by its ID, a hexadecimal number in the range of 1 to ffffffff.
verbose: Displays detailed next hop information for IPv6 direct routes. If you do not specify this keyword, the command displays brief next hop information for IPv6 direct routes.
Examples
# Display brief next hop information for IPv6 direct routes.
<Sysname> display ipv6 route-direct nib
Total number of nexthop(s): 115
NibID: 0x20000000 Sequence: 0
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: ::
IFIndex: 0x111 LocalAddr: ::
TopoNthp: Invalid
NibID: 0x20000001 Sequence: 1
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: ::1
IFIndex: 0x112 LocalAddr: ::1
TopoNthp: Invalid
...
Table 5 Command output
|
Field |
Description |
|
NibID |
ID of the NIB. |
|
Sequence |
Sequence number of the NIB. |
|
Type |
Type of the NIB. |
|
Flushed |
Indicates whether the route with the NIB has been flushed to the FIB. |
|
UserKey0 |
Reserved data 1. |
|
UserKey1 |
Reserved data 2. |
|
VrfNthp |
Index of the VPN instance to which the next hop belongs. This field displays 0 if the next hop is on an IPv6 network. |
|
Nexthop |
Next hop address. |
|
IFIndex |
Interface index. |
|
LocalAddr |
Local interface address. |
|
Index of the topology that contains the next hop. This field displays Invalid if the next hop is on an IPv6 network, because the router does not support multiple IPv6 topologies. |
# Display detailed next hop information for IPv6 direct routes.
<Sysname> display ipv6 route-direct nib verbose
Total number of nexthop(s): 115
NibID: 0x20000000 Sequence: 0
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: ::
IFIndex: 0x111 LocalAddr: ::
RefCnt: 1 FlushRefCnt: 0
Flag: 0x2 Version: 1
1 nexthop(s):
PrefixIndex: 0 OrigNexthop: ::
RelyDepth: 0 RealNexthop: ::
Interface: NULL0 LocalAddr: ::
TunnelCnt: 0 Vrf: default-vrf
TunnelID: N/A Topology:
Weight: 0
NibID: 0x20000001 Sequence: 1
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: ::1
IFIndex: 0x112 LocalAddr: ::1
RefCnt: 1 FlushRefCnt: 0
Flag: 0x2 Version: 1
1 nexthop(s):
PrefixIndex: 0 OrigNexthop: ::1
RelyDepth: 0 RealNexthop: ::1
Interface: InLoop0 LocalAddr: ::1
TunnelCnt: 0 Vrf: default-vrf
TunnelID: N/A Topology:
Weight: 0
...
Table 6 Command output
|
Field |
Description |
|
x nexthop(s) |
Number of next hops. |
|
Tnl-Policy |
Tunnel policy. |
|
PrefixIndex |
Prefix index of the next hop for an ECMP route. |
|
Vrf |
VPN instance name. For an IPv6 network, this field displays default-vrf. |
|
OrigNexthop |
Original next hop. |
|
RealNexthop |
Real next hop. |
|
Interface |
Output interface. |
|
localAddr |
Local interface address. |
|
RelyDepth |
Recursion depth. |
|
TunnelCnt |
Number of tunnels after route recursion. |
|
TunnelID |
ID of the tunnel after route recursion. |
|
Topology name. This field is blank for IPv6, because IPv6 does not support multiple topologies. |
|
|
Weight |
ECMP route weight. This field displays 0 for non-ECMP routes. |
|
RefCnt |
Reference count of the next hop. |
|
FlushRefCnt |
Reference count of the next hop that is flushed to the FIB. |
|
Flag |
Flag of the next hop. |
|
Version |
Version of the next hop. |
display ipv6 routing-table
Use display ipv6 routing-table to display IPv6 routing table information.
Syntax
display ipv6 routing-table [ vpn-instance vpn-instance-name ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing information for the public network.
verbose: Displays detailed routing table information, including information about both active and inactive routes. If you do not specify this keyword, the command displays only brief information about active routes.
Examples
# Display brief information about active routes in the IPv6 routing table.
<Sysname> display ipv6 routing-table
Destinations : 3 Routes : 3
Destination: ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: FE80::/10 Protocol : Direct
NextHop : :: Preference: 0
Interface : InLoop0 Cost : 0
Destination: FF00::/8 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
|
Field |
Description |
|
Destinations |
Number of destination addresses. |
|
Routes |
Number of routes. |
|
Destination |
IPv6 address and prefix of the destination network or host. |
|
NextHop |
Next hop address of the route. |
|
Preference |
Preference of the route. |
|
Interface |
Output interface for packets to be forwarded along the route. |
|
Protocol |
Protocol that installed the route. |
|
Cost |
Cost of the route. |
|
Summary count |
Number of routes. |
# Display detailed information about all routes in the routing table.
<Sysname> display ipv6 routing-table verbose
Destinations : 6 Routes : 6
Destination: ::1/128
Protocol: Direct
Process ID: 0
SubProtID: 0x0 Age: 19h23m02s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active NoAdv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x20000000 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10004 OrigNextHop: ::1
Label: NULL RealNextHop: ::1
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: InLoopBack0
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: 12::/96
Protocol: Direct
Process ID: 0
SubProtID: 0x0 Age: 00h01m47s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x20000003 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10080 OrigNextHop: ::
Label: NULL RealNextHop: ::
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: GigabitEthernet2/0/2
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: 12::1/128
Protocol: Direct
Process ID: 0
SubProtID: 0x0 Age: 00h01m45s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active NoAdv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x20000000 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10004 OrigNextHop: ::1
Label: NULL RealNextHop: ::1
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: InLoopBack0
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: FF::11/128
Protocol: BGP4+ instance default
Process ID: 0
SubProtID: 0x6 Age: 00h00m33s
Cost: 0 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 200
NibID: 0x26000000 LastAs: 200
AttrID: 0x1 Neighbor: 12::2
Flags: 0x10060 OrigNextHop: 12::2
Label: NULL RealNextHop: 12::2
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: GigabitEthernet2/0/2
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: FE80::/10
Protocol: Direct
Process ID: 0
SubProtID: 0x0 Age: 19h23m02s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active NoAdv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x20000002 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10084 OrigNextHop: ::
Label: NULL RealNextHop: ::
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: InLoopBack0
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: FF00::/8
Protocol: Direct
Process ID: 0
SubProtID: 0x0 Age: 19h23m02s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active NoAdv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x20000001 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10014 OrigNextHop: ::
Label: NULL RealNextHop: ::
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: NULL0
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
|
Field |
Description |
|
Destination |
IPv6 address and prefix of the destination network or host. |
|
Protocol |
Protocol that installed the route. |
|
SubProtID |
ID of the subprotocol for routing. |
|
Age |
Time for which the route has been in the routing table. |
|
Cost |
Cost of the route. |
|
Preference |
Preference of the route. |
|
IP precedence. |
|
|
Local QoS ID. |
|
|
Tag |
Tag of the route. |
|
State |
Route status: · Active—Active unicast route. · Adv—Route that can be advertised. · Inactive—Inactive route. · NoAdv—Route that the router must not advertise. · Vrrp—Routes generated by VRRP. · Nat—Routes generated by NAT. · TunE—Tunnel. |
|
OrigTblID |
Original routing table ID. |
|
OrigVrf |
Original VPN instance to which the route belongs. This field displays default-vrf if the route is on an IPv6 network. |
|
TableID |
ID of the routing table. |
|
OrigAs |
Original AS number. |
|
NibID |
ID of the next hop. |
|
LastAs |
Last AS number. |
|
AttrID |
Attribute ID. |
|
Neighbor |
Address of the neighbor determined by the routing protocol. |
|
Flags |
Flags of the route. |
|
OrigNextHop |
Next hop address of the route. |
|
RealNextHop |
Real next hop of the route. |
|
BkLabel |
Backup label. |
|
BkNexthop |
Backup next hop. |
|
Interface |
Output interface for packets to be forwarded along the route. |
|
BkTunnel ID |
Backup tunnel ID. |
|
BkInterface |
Backup output interface. |
|
Index of the FTN entry. |
|
|
TrafficIndex |
Traffic index in the range of 1 to 64. This field displays N/A when the value is invalid. |
|
Connector |
BGP connector attribute exchanged between BGP peers along with a VPN IPv4 route. The value of the attribute is the IP address of the remote PE device. The BGP connector attribute is used for MD VPN. This field displays N/A if the attribute is not configured. |
|
VpnPeerId |
ID of the VPN peer to which the route belongs, in the range of 1 to 134217727. This field displays N/A when the value is invalid. |
|
Dscp |
DSCP value of the route, in the range of 0 to 63. This field displays N/A when the value is invalid. |
|
Summary count |
Number of routes. |
display ipv6 routing-table acl
Use display ipv6 routing-table acl to display routing information permitted by an IPv6 basic ACL.
Syntax
display ipv6 routing-table [ vpn-instance vpn-instance-name ] acl ipv6-acl-number [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing information for the public network.
ipv6-acl-number: Specifies a basic IPv6 ACL by its number in the range of 2000 to 2999.
verbose: Displays detailed information about all routes permitted by the basic IPv6 ACL. If you do not specify this keyword, the command displays only brief information about active routes permitted by the basic IPv6 ACL.
Usage guidelines
If the specified IPv6 ACL does not exist or has no rules configured, the command displays information about all IPv6 routes.
Examples
# Display brief information about active routes permitted by IPv6 ACL 2000.
<Sysname> display ipv6 routing-table acl 2000
Summary count : 6
Destination : ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 12::/96 Protocol : Direct
NextHop : :: Preference: 0
Interface : GE2/0/2 Cost : 0
Destination: 12::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: FF::11/128 Protocol : BGP4+
NextHop : 12::2 Preference: 255
Interface : GE2/0/2 Cost : 0
Destination: FE80::/10 Protocol : Direct
NextHop : :: Preference: 0
Interface : InLoop0 Cost : 0
Destination: FF00::/8 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
For command output, see Table 7.
# Display detailed information about all routes permitted by IPv6 ACL 2000.
<Sysname> display ipv6 routing-table acl 2000 verbose
Summary count : 6
Destination: ::1/128
Protocol: Direct
Process ID: 0
SubProtID: 0x0 Age: 19h29m12s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active NoAdv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x20000000 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10004 OrigNextHop: ::1
Label: NULL RealNextHop: ::1
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: InLoopBack0
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: 12::/96
Protocol: Direct
Process ID: 0
SubProtID: 0x0 Age: 00h07m57s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x20000003 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10080 OrigNextHop: ::
Label: NULL RealNextHop: ::
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: GigabitEthernet2/0/2
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: 12::1/128
Protocol: Direct
Process ID: 0
SubProtID: 0x0 Age: 00h07m55s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active NoAdv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x20000000 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10004 OrigNextHop: ::1
Label: NULL RealNextHop: ::1
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: InLoopBack0
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: FF::11/128
Protocol: BGP4+ instance default
Process ID: 0
SubProtID: 0x6 Age: 00h06m43s
Cost: 0 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 200
NibID: 0x26000000 LastAs: 200
AttrID: 0x1 Neighbor: 12::2
Flags: 0x10060 OrigNextHop: 12::2
Label: NULL RealNextHop: 12::2
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: GigabitEthernet2/0/2
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: FE80::/10
Protocol: Direct
Process ID: 0
SubProtID: 0x0 Age: 19h29m12s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active NoAdv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x20000002 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10084 OrigNextHop: ::
Label: NULL RealNextHop: ::
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: InLoopBack0
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
Destination: FF00::/8
Protocol: Direct
Process ID: 0
SubProtID: 0x0 Age: 19h29m12s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active NoAdv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x20000001 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10014 OrigNextHop: ::
Label: NULL RealNextHop: ::
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: NULL0
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A VpnPeerId:
N/A
Dscp: N/A
For command output, see Table 8.
display ipv6 routing-table ipv6-address
Use display ipv6 routing-table ipv6-address to display information about routes to an IPv6 destination address.
Use display ipv6 routing-table ipv6-address1 to ipv6-address2 to display information about routes to a range of IPv6 destination addresses.
Syntax
display ipv6 routing-table [ vpn-instance vpn-instance-name ] ipv6-address [ prefix-length ] [ longer-match ] [ verbose ]
display ipv6 routing-table [ vpn-instance vpn-instance-name ] ipv6-address1 to ipv6-address2 [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing information for the public network.
ipv6-address: Specifies a destination IPv6 address.
prefix-length: Specifies the prefix length in the range of 0 to 128.
longer-match: Displays the route entry with the longest prefix.
ipv6-address1 to ipv6-address2: Specifies a destination IPv6 address range.
verbose: Displays detailed routing table information, including information about both active and inactive routes. If you do not specify this keyword, the command displays only brief information about active routes.
Usage guidelines
Executing the command with different parameters yields different output.
· display ipv6 routing-table ipv6-address
¡ The system ANDs the entered destination IPv6 address with the prefix length in each active route entry.
¡ The system ANDs the destination IPv6 address in each active route entry with the prefix length in the entry.
If the two operations yield the same result for an entry, the entry is displayed.
· display ipv6 routing-table ipv6-address prefix-length
¡ The system ANDs the entered destination IPv6 address with the entered prefix length.
¡ The system ANDs the destination IPv6 address in each active route entry with the entered prefix length.
If the two operations yield the same result for an entry with a prefix length not greater than the entered prefix length, the entry is displayed.
· display ipv6 routing-table ipv6-address longer-match
¡ The system ANDs the entered destination IPv6 address with the prefix length in each active route entry.
¡ The system ANDs the destination IPv6 address in each active route entry with the prefix length in the entry.
If the two operations yield the same result for multiple entries, the entry with the longest prefix length is displayed.
· display ipv6 routing-table ipv6-address prefix-length longer-match
¡ The system ANDs the entered destination IPv6 address with the entered prefix length.
¡ The system ANDs the destination IPv6 address in each active route entry with the entered prefix length.
If the two operations yield the same result for multiple entries with a prefix length not greater than the entered prefix length, the entry with the longest prefix length is displayed.
· display ipv6 routing-table ipv6-address1 to ipv6-address2
The system displays route entries with destinations in the range of ipv6-address1/128 to ipv6-address2/128.
Examples
# Display brief information about the routes to the destination IPv6 address 10::1 127.
<Sysname> display ipv6 routing-table 10::1 127
Summary count: 3
Destination: 10::/64 Protocol : Static
NextHop : :: Preference: 60
Interface : NULL0 Cost : 0
Destination: 10::/68 Protocol : Static
NextHop : :: Preference: 60
Interface : NULL0 Cost : 0
Destination: 10::/120 Protocol : Static
NextHop : :: Preference: 60
Interface : NULL0 Cost : 0
# Display brief information about the most specific route to the destination IPv6 address 10::1 and prefix length 127.
<Sysname> display ipv6 routing-table 10::1 127 longer-match
Summary count : 1
Destination: 10::/120 Protocol : Static
NextHop : :: Preference: 60
Interface : NULL0 Cost : 0
# Display brief information about the routes to destination addresses in the range of 100:: to 300::.
<Sysname> display ipv6 routing-table 100:: to 300::
Summary count : 3
Destination: 100::/64 Protocol : Static
NextHop : :: Preference: 60
Interface : NULL0 Cost : 0
Destination: 200::/64 Protocol : Static
NextHop : :: Preference: 60
Interface : NULL0 Cost : 0
Destination: 300::/64 Protocol : Static
NextHop : :: Preference: 60
Interface : NULL0 Cost : 0
# Display detailed information about the routes to destination IPv6 addresses 1:2::3:4/128.
<Sysname> display ipv6 routing-table 1:2::3:4 128 verbose
Summary count : 1
Destination: 1:2::3:4/128
Protocol: BGP4+ instance abc
Process ID: 0
SubProtID: 0x1 Age: 00h01m14s
Cost: 0 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x1 OrigAs: 200
NibID: 0x26000000 LastAs: 200
AttrID: 0x0 Neighbor: 2:2::3:4
Flags: 0x10060 OrigNextHop: 2:2::3:4
Label: NULL RealNextHop: 2:2::3:4
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: GigabitEthernet1/0/1
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
For command output, see Table 7.
display ipv6 routing-table prefix-list
Use display ipv6 routing-table prefix-list to display information about IPv6 routes permitted by an IPv6 prefix list.
Syntax
display ipv6 routing-table [ vpn-instance vpn-instance-name ] prefix-list prefix-list-name [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing information for the public network.
prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters.
verbose: Displays detailed information about all IPv6 routes permitted by the IPv6 prefix list. If you do not specify this keyword, the command displays brief information about active IPv6 routes permitted by the IPv6 prefix list.
Usage guidelines
If the specified IPv6 prefix list does not exist, the command displays information about all routes.
Examples
# Create an IPv6 prefix list named test to permit the prefix ::1/128.
<Sysname> system-view
[Sysname] ipv6 prefix-list test permit ::1 128
# Display brief information about the active IPv6 route permitted by the IPv6 prefix list.
[Sysname] display ipv6 routing-table prefix-list test
Summary count : 1
Destination: ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
For command output, see Table 7.
# Display detailed information about all routes permitted by the IPv6 prefix list.
[Sysname] display ipv6 routing-table prefix-list test verbose
Summary count : 1
Destination: ::1/128
Protocol: Direct
Process ID: 0
SubProtID: 0x0 Age: 08h57m19s
Cost: 0 Preference: 0
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active NoAdv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x20000000 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10004 OrigNextHop: ::1
Label: NULL RealNextHop: ::1
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: InLoopBack0
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
For command output, see Table 8.
display ipv6 routing-table protocol
Use display ipv6 routing-table protocol to display information about IPv6 routes installed by a protocol.
Syntax
display ipv6 routing-table [ vpn-instance vpn-instance-name ] protocol protocol [ inactive | verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays routing information for the public network.
protocol: Specifies a routing protocol.
inactive: Displays information about inactive routes. If you do not specify this keyword, the command displays information about both active and inactive routes.
verbose: Displays detailed routing table information. If you do not specify this keyword, the command displays brief routing information.
Examples
# Display brief information about IPv6 direct routes.
<Sysname> display ipv6 routing-table protocol direct
Summary count : 3
Direct Routing Table Status : <Active>
Summary count : 3
Destination: ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: FE80::/10 Protocol : Direct
NextHop : :: Preference: 0
Interface : InLoop0 Cost : 0
Destination: FF00::/8 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
Direct Routing Table Status : <Inactive>
Summary count : 0
# Display brief information about IPv6 static routes.
<Sysname> display ipv6 routing-table protocol static
Summary count : 3
Static Routing table Status : <Active>
Summary count : 3
Destination: 2::2/128 Protocol : Static
NextHop : fe80::2 Preference: 60
Interface : GE1/0/2 Cost : 0
Destination: 2::2/128 Protocol : Static
NextHop : fe80::3 Preference: 60
Interface : GE1/0/2 Cost : 0
Destination: 3::3/128 Protocol : Static
NextHop : 2::2 Preference: 60
Interface : GE1/0/2 Cost : 0
Static Routing table Status : <Inactive>
Summary count : 0
# Display detailed information about IPv6 BGP routes.
<Sysname> display ipv6 routing-table protocol bgp4+ verbose
Summary count : 1
Destination: 22::22/128
Protocol: BGP4+ instance abc
Process ID: 0
SubProtID: 0x6 Age: 00h04m15s
Cost: 0 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 200
NibID: 0x25000001 LastAs: 200
AttrID: 0x3 Neighbor: 121::2
Flags: 0x10060 OrigNextHop: 121::2
Label: NULL RealNextHop: 121::2
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: GigabitEthernet1/0/5
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
For command output, see Table 7.
display ipv6 routing-table statistics
Use display ipv6 routing-table statistics to display IPv6 route statistics, including numbers of total routes, routes installed and deleted by the protocol, and active routes.
Syntax
display ipv6 routing-table [ vpn-instance vpn-instance-name ] statistics
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays route statistics for the public network.
Examples
# Display IPv6 route statistics for the public network.
<Sysname> display ipv6 routing-table statistics
Total prefixes: 8 Active prefixes: 8
Proto route active added deleted
DIRECT 5 5 5 0
STATIC 3 3 3 0
RIPng 0 0 0 0
OSPFv3 0 0 0 0
IS-ISv6 0 0 0 0
LISP 0 0 0 0
BGP4+ 0 0 0 0
Total 8 8 8 0
Table 9 Command output
|
Field |
Description |
|
Proto |
Protocol that installed the route. |
|
route |
Number of routes installed by the protocol. |
|
active |
Number of active routes. |
|
added |
Number of routes added to the routing table after the router started up or the routing table was cleared most recently. |
|
deleted |
Number of routes marked as deleted, which will be cleared after a period. |
|
Total |
Total number of routes. |
display ipv6 routing-table summary
Use display ipv6 routing-table summary to display brief IPv6 routing table information, including maximum number of ECMP routes, maximum number of active routes, and number of remaining active routes.
Syntax
display ipv6 routing-table [ vpn-instance vpn-instance-name ] summary
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify an MPLS L3VPN instance, this command displays brief IPv6 routing table information for the public network.
Examples
# Display brief IPv6 routing table information for the public network.
<Sysname> display ipv6 routing-table summary
Max ECMP: 32
Max Active Route: 262144
Remain Active Route: 262126
# Display brief IPv6 routing table information for the MPLS L3VPN instance vpn1.
<Sysname> display ipv6 routing-table vpn-instance vpn1 summary
Max ECMP: 32
Max Active Route: 262144
Remain Active Route: 262134
Threshold value of active routes alert: 65100
For command output, see Table 4.
display rib attribute
Use display rib attribute to display route attribute information in the RIB.
Syntax
display rib attribute [ attribute-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
attribute-id: Specifies a route attribute by its ID, a hexadecimal number in the range of 0 to ffffffff.
Examples
# Display route attribute information in the RIB.
<Sysname> display rib attribute
Total number of attribute(s): 10
Detailed information of attribute 0x0:
Flag: 0x0
Protocol: BGP instance default
Address family: IPv4
Reference count: 0
Local preference: 0
Ext-communities number: 26
Ext-communities value: <RT: 1:1> <RT: 2:2> <RT: 3:3> <RT: 123.123.123.123:65535
> <RT: 1234567890:65535> <RT: 123.123.123.123:65534> <RT
: 4:4> <RT: 5:5> <RT: 6:6> <RT: 7:7> <RT: 8:8> <RT: 9:9>
<RT: 10:10> <RT: 10:1> <RT: 10:11> <RT: 10:12> <RT: 10:
13> <RT: 10:14> <RT: 10:15> <RT: 10:16> ...
Communities number: 0
Communities value: N/A
AS-path number: 0
AS-path value: N/A
Detailed information of attribute 0x1:
Flag: 0x0
Protocol: BGP
Address family: IPv4
Reference count: 0
Local preference: 0
Ext-communities number: 1
Ext-communities value: <RT: 1:2>
Communities number: 0
Communities value: N/A
AS-path number: 0
AS-path value: N/A
|
Field |
Description |
|
Protocol |
Protocol that generates the attribute. |
|
Ext-communities number |
Number of the extended community attribute values. |
|
Ext-communities value |
Values of the extended community attribute. This field displays N/A when no values exist, and it can display a maximum of 20 values. |
|
Communities number |
Number of the COMMUNITY attribute values. |
|
Communities value |
Values of the COMMUNITY attribute. This field displays N/A when no values exist, and it can display a maximum of 20 values. |
|
AS-path number |
Number of ASs in the AS_PATH attribute. |
|
AS-path value |
Values of the AS_PATH attribute, including AS_SET, AS_SEQUENCE, confederation AS_SET, and confederation AS_SEQUENCE. This field displays N/A when no values exist, and it can display a maximum of 20 values. |
display rib graceful-restart
Use display rib graceful-restart to display RIB GR state information.
Syntax
display rib graceful-restart
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display RIB GR state information.
<Sysname> display rib graceful-restart
RIB GR state : Phase2-calculation end
RCOM GR state : Flush end
Protocol GR state:
No. Protocol Lifetime FD State Start/End
--------------------------------------------------
1 DIRECT 100 30 End No/No
2 STATIC 480 34 End No/No
3 OSPF 480 36 End No/No
4 ISIS 480 32 End No/No
5 BGP instance abc
480 22 End No/No
6 BGP instance default
480 25 End No/No
7 LDP 480 35 End No/No
8 SLSP 480 29 End No/No
|
Field |
Description |
|
RIB GR state |
RIB GR status: · Start—GR starts. · IGP end—All IGP protocols complete GR. · VPN-triggering end—Optimal route selection triggered by VPN routes completes. · VPN-calculation end—Optimal VPN route selection completes. · Routing protocol end—All routing protocols complete GR. · NSR-calculation unfinished—NSR has not finished optimal route selection. · Triggering start—All triggered optimal route selection starts. · Triggering end—All triggered optimal route selection completes. · Phase1-calculation end—Optimal route selection phase 1 completes. · All end—All protocols complete GR. · Phase2-calculation end—Optimal route selection phase 2 completes. |
|
RCOM GR state |
RCOM GR status: · Start—GR starts. · VPN-calculation end—Optimal VPN route selection completes. · VPN-notification end—VPN routes have been delivered to the route management module. · Routing protocol end—All routing protocols complete GR. · NSR-calculation unfinished—NSR has not finished optimal route selection. · Phase1-calculation end—Optimal route selection phase 1 completes. · Notification end—All routes have been delivered to the route management module. · Phase2-calculation end—Optimal route selection phase 2 completes. · Flush start—Starts to flush routes to the FIB. · Flush end—Completes flushing routes to the FIB. |
|
No. |
Protocol number. |
|
Lifetime |
Lifetime (in seconds) of routes/labels in the RIB during GR. |
|
FD |
Handle between the protocol and the RIB. |
|
State |
Protocol GR state: · Init—Initialization state. · Listen—Listening state. · Idle. · Active. · Start—GR starts. · End—GR completes. |
|
Start/End |
Message sending state: · No—The message has not been sent. · Yes—The message has been sent. |
display rib nib
Use display rib nib to display next hop information in the RIB.
Syntax
display rib nib [ self-originated ] [ nib-id ] [ verbose ]
display rib nib protocol protocol [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
self-originated: Displays information about next hops of self-originated routes in the RIB.
nib-id: Specifies a NIB by its ID, a hexadecimal number in the range of 1 to ffffffff.
verbose: Displays detailed next hop information in the RIB. If you do not specify this keyword, the command displays brief next hop information in the RIB.
protocol protocol: Specifies a protocol by its name.
Examples
# Display brief next hop information in the RIB.
<Sysname> display rib nib
Total number of nexthop(s): 176
NibID: 0x10000000 Sequence: 0
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 0.0.0.0
IFIndex: 0x111 LocalAddr: 0.0.0.0
TopoNthp: 0
NibID: 0x10000001 Sequence: 1
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 127.0.0.1
IFIndex: 0x112 LocalAddr: 127.0.0.1
TopoNthp: 0
NibID: 0x10000002 Sequence: 2
Type: 0x5 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 127.0.0.1
IFIndex: 0x112 LocalAddr: 127.0.0.1
TopoNthp: 0
NibID: 0x16000000 Sequence: 3
Type: 0x21 Flushed: No
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 12.1.1.2
IFIndex: 0x0 LocalAddr: 0.0.0.0
TopoNthp: 0
Instance: abc
|
Field |
Description |
|
NibID |
ID of the next hop. |
|
Sequence |
Sequence number of the next hop. |
|
Type |
Type of the next hop. |
|
Flushed |
Indicates whether the route with the next hop has been flushed to the FIB. |
|
UserKey0 |
Reserved data 1. |
|
UserKey1 |
Reserved data 2. |
|
VrfNthp |
Index of the VPN instance to which the next hop belongs. This field displays 0 if the next hop is on the IPv4 public network or an IPv6 network. |
|
Nexthop |
Next hop address. |
|
IFIndex |
Interface index. |
|
LocalAddr |
Local interface address. |
|
Index of the topology that contains the next hop. This field displays 0 if the next hop is on the IPv4 public network. This field displays Invalid if the next hop is on an IPv6 network, because the router does not support multiple IPv6 topologies. |
|
|
Instance |
BGP instance name. |
|
SubNibID |
ID of the sub-next hop. |
|
SubSeq |
Sequence number of the sub-next hop. |
|
NthpCnt |
Number of sub-next hops. |
|
Samed |
Number of the same sub-next hops. |
|
NthpType |
Type of the sub-next hop: · IP—IP forwarding. · MPLS—MPLS forwarding. |
# Display detailed next hop information in the RIB.
<Sysname> display rib nib verbose
Total number of nexthop(s): 176
NibID: 0x10000000 Sequence: 0
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 0.0.0.0
IFIndex: 0x111 LocalAddr: 0.0.0.0
TopoNthp: 0
RefCnt: 6 FlushRefCnt: 2
Flag: 0x84 Version: 1
1 nexthop(s):
PrefixIndex: 0 OrigNexthop: 0.0.0.0
RelyDepth: 0 RealNexthop: 0.0.0.0
Interface: NULL0 LocalAddr: 0.0.0.0
TunnelCnt: 0 Vrf: default-vrf
TunnelID: N/A Topology: base
Weight: 0
NibID: 0x10000001 Sequence: 1
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 127.0.0.1
IFIndex: 0x112 LocalAddr: 127.0.0.1
TopoNthp: 0
RefCnt: 13 FlushRefCnt: 5
Flag: 0x84 Version: 1
1 nexthop(s):
PrefixIndex: 0 OrigNexthop: 127.0.0.1
RelyDepth: 0 RealNexthop: 127.0.0.1
Interface: InLoop0 LocalAddr: 127.0.0.1
TunnelCnt: 0 Vrf: default-vrf
TunnelID: N/A Topology: base
Weight: 0
NibID: 0x15000003 Sequence: 3
Type: 0x43 Flushed: Yes
UserKey0: 0x100010000 VrfNthp: 0
UserKey1: 0x0 Nexthop: 22.22.22.22
IFIndex: 0x0 LocalAddr: 0.0.0.0
TopoNthp: 0
Instance: default
RefCnt: 9 FlushRefCnt: 3
Flag: 0x84 Version: 1
Policy: tnl-policy1
1 nexthop(s):
PrefixIndex: 0 OrigNexthop: 22.22.22.22
RelyDepth: 1 RealNexthop: 13.1.1.2
Interface: GE0/1/3 LocalAddr: 13.1.1.1
TunnelCnt: 1 Vrf: default-vrf
TunnelID: 1025 Topology: base
Weight: 0
|
Field |
Description |
|
Policy |
Tunnel policy name. |
|
x nexthop (s) |
Number of next hops. |
|
PrefixIndex |
Prefix index of the next hop for an ECMP route. |
|
Vrf |
VPN instance name. For the IPv4 public network or an IPv6 network, this field displays default-vrf. |
|
OrigNexthop |
Original next hop. |
|
RealNexthop |
Real next hop. |
|
Interface |
Output interface. |
|
LocalAddr |
Local interface address. |
|
RelyDepth |
Recursion depth. |
|
TunnelCnt |
Number of tunnels after route recursion. |
|
TunnelID |
ID of the tunnel after route recursion. |
|
Topology name. The topology name for the IPv4 public network is base. This field is blank for IPv6, because IPv6 does not support multiple topologies. |
|
|
Weight |
ECMP route weight. This field displays 0 for non-ECMP routes. |
|
Instance |
BGP instance name. |
|
RefCnt |
Reference count of the next hop. |
|
FlushRefCnt |
Reference count of the next hop that is flushed to the FIB. |
|
Flag |
Flag of the next hop. |
|
Version |
Version of the next hop. |
display route-direct nib
Use display route-direct nib to display next hop information for direct routes.
Syntax
display route-direct nib [ nib-id ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
nib-id: Specifies a NIB by its ID, a hexadecimal number in the range of 1 to ffffffff.
verbose: Displays detailed next hop information for direct routes. If you do not specify this keyword, the command displays brief next hop information for direct routes.
Examples
# Display brief next hop information for direct routes.
<Sysname> display route-direct nib
Total number of nexthop(s): 116
NibID: 0x10000000 Sequence: 0
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 0.0.0.0
IFIndex: 0x111 LocalAddr: 0.0.0.0
TopoNthp: 0
NibID: 0x10000001 Sequence: 1
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 127.0.0.1
IFIndex: 0x112 LocalAddr: 127.0.0.1
TopoNthp: 0
...
Table 14 Command output
|
Field |
Description |
|
NibID |
ID of the NIB. |
|
Sequence |
Sequence number of the NIB. |
|
Type |
Type of the NIB. |
|
Flushed |
Indicates whether the route with the NIB has been flushed to the FIB. |
|
UserKey0 |
Reserved data 1. |
|
UserKey1 |
Reserved data 2. |
|
VrfNthp |
Index of the VPN instance to which the next hop belongs. This field displays 0 if the next hop is on the IPv4 public network. |
|
Nexthop |
Next hop address. |
|
IFIndex |
Interface index. |
|
Local interface IP address. |
|
|
Index of the topology that contains the next hop. This field displays 0 if the next hop is on the IPv4 public network. |
# Display detailed next hop information for direct routes.
<Sysname> display route-direct nib verbose
Total number of nexthop(s): 116
NibID: 0x10000000 Sequence: 0
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 0.0.0.0
IFIndex: 0x111 LocalAddr: 0.0.0.0
RefCnt: 2 FlushRefCnt: 0
Flag: 0x2 Version: 1
1 nexthop(s):
PrefixIndex: 0 OrigNexthop: 0.0.0.0
RelyDepth: 0 RealNexthop: 0.0.0.0
Interface: NULL0 LocalAddr: 0.0.0.0
TunnelCnt: 0 Vrf: default-vrf
TunnelID: N/A Topology: base
Weight: 0
NibID: 0x10000001 Sequence: 1
Type: 0x1 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 127.0.0.1
IFIndex: 0x112 LocalAddr: 127.0.0.1
RefCnt: 5 FlushRefCnt: 0
Flag: 0x2 Version: 1
1 nexthop(s):
PrefixIndex: 0 OrigNexthop: 127.0.0.1
RelyDepth: 0 RealNexthop: 127.0.0.1
Interface: InLoop0 LocalAddr: 127.0.0.1
TunnelCnt: 0 Vrf: default-vrf
TunnelID: N/A Topology: base
Weight: 0
...
Table 15 Command output
|
Field |
Description |
|
x nexthop(s) |
Number of next hops. |
|
PrefixIndex |
Prefix index of the next hop for an ECMP route. |
|
Vrf |
VPN instance name. For the IPv4 public network, this field displays default-vrf. |
|
OrigNexthop |
Original next hop. |
|
RealNexthop |
Real next hop. |
|
Interface |
Output interface. |
|
localAddr |
Local interface address. |
|
RelyDepth |
Recursion depth. |
|
TunnelCnt |
Number of tunnels after route recursion. |
|
TunnelID |
ID of the tunnel after route recursion. |
|
Topology |
Topology name. The topology name for the IPv4 public network is base. |
|
Weight |
ECMP route weight. This field displays 0 for non-ECMP routes. |
|
RefCnt |
Reference count of the next hop. |
|
FlushRefCnt |
Reference count of the next hop that is flushed to the FIB. |
|
Flag |
Flag of the next hop. |
|
Version |
Version of the next hop. |
fib lifetime
Use fib lifetime to set the maximum lifetime for IPv4 or IPv6 routes in the FIB.
Use undo fib lifetime to restore the default.
Syntax
fib lifetime seconds
undo fib lifetime
Default
The maximum lifetime for IPv4 or IPv6 routes in the FIB is 600 seconds.
Views
RIB IPv4 address family view
RIB IPv6 address family view
Predefined user roles
network-admin
Parameters
seconds: Specifies the maximum lifetime for routes in the FIB, in the range of 0 to 6000 seconds. When this argument is set to 0, FIB entries immediately age out after a protocol or RIB process switchover.
Usage guidelines
When a protocol or RIB process switchover occurs and GR or NSR is not configured, FIB entries age out after the time specified in this command.
Examples
# Set the maximum lifetime for IPv4 routes in the FIB to 60 seconds.
[Sysname] rib
[Sysname-rib] address-family ipv4
[Sysname-rib-ipv4] fib lifetime 60
inter-protocol fast-reroute
Use inter-protocol fast-reroute to enable IPv4 or IPv6 RIB inter-protocol FRR.
Use undo inter-protocol fast-reroute to disable IPv4 or IPv6 RIB inter-protocol FRR.
Syntax
inter-protocol fast-reroute [ vpn-instance vpn-instance-name ]
undo inter-protocol fast-reroute [ vpn-instance vpn-instance-name ]
Default
Inter-protocol FRR is disabled.
Views
RIB IPv4 address family view
RIB IPv6 address family view
Predefined user roles
network-admin
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify an MPLS L3VPN instance, this command enables IPv4 or IPv6 RIB inter-protocol FRR for the public network.
Usage guidelines
This command allows a device to perform fast rerouting between routes of different protocols. A backup next hop is automatically selected to reduce the service interruption time caused by unreachable next hops. When the next hop of the primary link fails, the traffic is redirected to the backup next hop.
This command uses the next hop of a route from a different protocol as the backup next hop for the faulty route, which might cause loops.
Inter-protocol FRR cannot select a backup next hop from routes in the RIB that have the same next hop, output interface, and destination as those of the faulty route.
Examples
# Enable IPv4 RIB inter-protocol FRR for the public network.
[Sysname] rib
[Sysname-rib] address-family ipv4
[Sysname-rib-ipv4] inter-protocol fast-reroute
# Enable IPv4 RIB inter-protocol FRR for the MPLS L3VPN instance VPN1.
[Sysname] rib
[Sysname-rib] address-family ipv4
[Sysname-rib-ipv4] inter-protocol fast-reroute vpn-instance VPN1
non-stop-routing
Use non-stop-routing to enable RIB NSR.
Use undo non-stop-routing to disable RIB NSR.
Syntax
non-stop-routing
undo non-stop-routing
Default
RIB NSR is disabled.
Views
RIB IPv4 address family view
RIB IPv6 address family view
Predefined user roles
network-admin
Usage guidelines
The following matrix shows the command and hardware compatibility:
|
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
Yes |
|
MSR3600-28/3600-51 |
No |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
No |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Command compatibility |
|
MSR810-LM-GL |
No |
|
MSR810-W-LM-GL |
No |
|
MSR830-6EI-GL |
No |
|
MSR830-10EI-GL |
No |
|
MSR830-6HI-GL |
No |
|
MSR830-10HI-GL |
No |
|
MSR2600-6-X1-GL |
No |
|
MSR3600-28-SI-GL |
No |
Examples
# Enable NSR for the RIB IPv4 address family.
<Sysname> system-view
[Sysname] rib
[Sysname-rib] address-family ipv4
[Sysname-rib-ipv4] non-stop-routing
protocol lifetime
Use protocol lifetime to set the maximum lifetime for IPv4 or IPv6 routes and labels in the RIB.
Use undo protocol lifetime to restore the default.
Syntax
protocol protocol [ instance instance-name ] lifetime seconds
undo protocol protocol [ instance instance-name ] lifetime
Default
The maximum lifetime for IPv4 or IPv6 routes and labels in the RIB is 480 seconds.
Views
RIB IPv4 address family view
RIB IPv6 address family view
Predefined user roles
network-admin
Parameters
protocol: Specifies a routing protocol.
seconds: Specifies the maximum lifetime for routes and labels in the RIB, in the range of 1 to 6000 seconds.
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. This argument applies only to the BGP protocol. If you do not specify a BGP instance, this command sets the maximum lifetime for all BGP routes and labels in the RIB.
Usage guidelines
When GR is enabled, make sure the protocol can complete GR and install all route entries to the RIB within the lifetime configured in this command.
Examples
# Set the maximum lifetime for OSPF routes and labels in the RIB to 60 seconds.
[Sysname] rib
[Sysname-rib] address-family ipv4
[Sysname-rib-ipv4] protocol ospf lifetime 60
# Set the maximum lifetime for all BGP routes and labels in the RIB to 60 seconds.
[Sysname-rib] address-family ipv4
[Sysname-rib-ipv4] protocol bgp lifetime 60
# Set the maximum lifetime for BGP routes and labels in BGP instance abc to 60 seconds.
[Sysname-rib] address-family ipv4
[Sysname-rib-ipv4] protocol bgp instance abc lifetime 60
reset ip routing-table statistics protocol
Use reset ip routing-table statistics protocol to clear IPv4 route statistics.
Syntax
reset ip routing-table statistics protocol [ topology topo-name | vpn-instance vpn-instance-name ] { protocol | all }
Views
User view
Predefined user roles
network-admin
Parameters
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command clears IPv4 route statistics for the public network.
vpn-instance vpn-instance-name: Clears the IPv4 route statistics for an MPLS L3VPN instance specified by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command clears IPv4 route statistics for the public network.
protocol: Clears route statistics for a routing protocol.
all: Clears route statistics for all IPv4 routing protocols.
Examples
# Clear all IPv4 route statistics for the public network.
<Sysname> reset ip routing-table statistics protocol all
reset ipv6 routing-table statistics protocol
Use reset ipv6 routing-table statistics protocol to clear IPv6 route statistics.
Syntax
reset ipv6 routing-table statistics protocol [ vpn-instance vpn-instance-name ] { protocol | all }
Views
User view
Predefined user roles
network-admin
Parameters
vpn-instance vpn-instance-name: Clears route statistics for an MPLS L3VPN instance specified by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command clears the IPv6 route statistics for the public network.
protocol: Clears route statistics for an IPv6 routing protocol.
all: Clears route statistics for all IPv6 routing protocols.
Examples
# Clear all IPv6 route statistics for the public network.
<Sysname> reset ipv6 routing-table statistics protocol all
rib
Use rib to enter RIB view.
Use undo rib to remove all configurations in RIB view.
Syntax
rib
undo rib
Views
System view
Predefined user roles
network-admin
Examples
# Enter RIB view.
<Sysname> system-view
[Sysname] rib
[Sysname-rib]
Static routing commands
The topology parameter is not supported on the MSR810-LMS and MSR810-LUS routers.
delete static-routes all
Use delete static-routes all to delete all static routes.
Syntax
delete [ topology topo-name | vpn-instance vpn-instance-name ] static-routes all
Views
System view
Predefined user roles
network-admin
Parameters
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a topology, the command deletes all static routes for the public network.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify an MPLS L3VPN instance, the command deletes all static routes for the public network.
Usage guidelines
When you use this command, the system will prompt you to confirm the operation before deleting all the static routes.
To delete one static route, use the undo ip route-static command. To delete all static routes, including the default route, use the delete static-routes all command.
Examples
# Delete all static routes.
<Sysname> system-view
[Sysname] delete static-routes all
This will erase all IPv4 static routes and their configurations, you must reconfigure all static routes.
Are you sure?[Y/N]:y
Related commands
ip route-static
display route-static nib
Use display route-static nib to display static route next hop information.
Syntax
display route-static nib [ nib-id ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
nib-id: Specifies a NIB by its ID in the range of 1 to FFFFFFFF.
verbose: Displays detailed static route next hop information. If you do not specify this keyword, the command displays brief static route next hop information.
Examples
# Displays brief static route next hop information.
<Sysname> display route-static nib
Total number of nexthop(s): 44
NibID: 0x11000000 Sequence: 0
Type: 0x21 Flushed: Yes
UserKey0: 0x111 VrfNthp: 0
UserKey1: 0x0 Nexthop: 0.0.0.0
IFIndex: 0x111 LocalAddr: 0.0.0.0
TopoNthp: 0
NibID: 0x11000001 Sequence: 1
Type: 0x41 Flushed: Yes
UserKey0: 0x0 VrfNthp: 5
UserKey1: 0x0 Nexthop: 2.2.2.2
IFIndex: 0x0 LocalAddr: 0.0.0.0
TopoNthp: 0
Table 16 Command output
|
Field |
Description |
|
NibID |
ID of the NIB. |
|
NibSeq |
Sequence number of the NIB. |
|
Type |
Type of the NIB. |
|
Flushed |
Indicates whether the route with the NIB has been flushed to the FIB. |
|
UserKey0 |
Reserved data 1. |
|
UserKey1 |
Reserved data 2. |
|
VrfNthp |
Index of the VPN instance to which the next hop belongs. This field displays 0 if the next hop is on the IPv4 public network. |
|
Nexthop |
Next hop address. |
|
IFIndex |
Interface index |
|
LocalAddr |
Local interface address. |
|
TopoNthp |
Index of the topology that contains the next hop. This field displays 0 if the next hop is on the IPv4 public network. |
# Displays detailed static route next hop information.
<Sysname> display route-static nib verbose
Total number of nexthop(s): 44
NibID: 0x11000000 Sequence: 0
Type: 0x21 Flushed: Yes
UserKey0: 0x111 VrfNthp: 0
UserKey1: 0x0 Nexthop: 0.0.0.0
IFIndex: 0x111 LocalAddr: 0.0.0.0
TopoNthp: 0
RefCnt: 2 FlushRefCnt: 0
Flag: 0x2 Version: 1
1 nexthop(s):
PrefixIndex: 0 OrigNexthop: 0.0.0.0
RelyDepth: 0 RealNexthop: 0.0.0.0
Interface: NULL0 LocalAddr: 0.0.0.0
TunnelCnt: 0 Vrf: default-vrf
TunnelID: N/A Topology: base
Weight: 1000000
NibID: 0x11000001 Sequence: 1
Type: 0x41 Flushed: Yes
UserKey0: 0x0 VrfNthp: 5
UserKey1: 0x0 Nexthop: 2.2.2.2
IFIndex: 0x0 LocalAddr: 0.0.0.0
TopoNthp: 0
RefCnt: 1 FlushRefCnt: 0
Flag: 0x12 Version: 1
2 nexthop(s):
PrefixIndex: 0 OrigNexthop: 2.2.2.2
RelyDepth: 7 RealNexthop: 8.8.8.8
Interface: GE1/0/1 LocalAddr: 12.12.12.12
TunnelCnt: 0 Vrf: default-vrf
TunnelID: N/A Topology: base
Weight: 1000000
PrefixIndex: 0 OrigNexthop: 2.2.2.2
RelyDepth: 9 RealNexthop: 0.0.0.0
Interface: NULL0 LocalAddr: 0.0.0.0
TunnelCnt: 0 Vrf: default-vrf
TunnelID: N/A Topology: base
Weight: 1000000
...
Table 17 Command output
|
Field |
Description |
|
x nexthop(s) |
Number of next hops. |
|
PrefixIndex |
Prefix index of the next hop for an ECMP route. |
|
OrigNexthop |
Original next hop. |
|
RelyDepth |
Recursion depth. |
|
RealNexthop |
Real next hop. |
|
Interface |
Output interface. |
|
localAddr |
Local interface address. |
|
TunnelCnt |
Number of tunnels after route recursion. |
|
Vrf |
VPN instance name. For the IPv4 public network, this field displays default-vrf. |
|
TunnelID |
ID of the tunnel after route recursion. |
|
Topology |
Topology name. The topology name for the IPv4 public network is base. |
|
Weight |
Weight of the ECMP route. The route is not an ECMP route if its weight is 0. |
|
RefCnt |
Reference count of the next hop. |
|
FlushRefCnt |
Reference count of the next hop that is flushed to the FIB. |
|
Flag |
Flag of the next hop. |
|
Version |
Version of the next hop. |
display route-static routing-table
Use display route-static routing-table to display static routing table information.
Syntax
display route-static routing-table [ topology topo-name | vpn-instance vpn-instance-name ] [ ip-address { mask-length | mask } ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a topology, the command displays all static routes for the public network.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify an MPLS L3VPN instance, the command displays static routing table information for the public network.
ip-address: Specifies the destination IP address in dotted decimal notation.
mask-length: Specifies the mask length, an integer in the range of 0 to 32.
mask: Specifies the subnet mask in dotted decimal notation.
Examples
# Display static routing table information.
<Sysname> display route-static routing-table
Total number of routes: 24
Status: * - valid
*Destination: 0.0.0.0/0
NibID: 0x1100000a NextHop: 2.2.2.10
MainNibID: N/A BkNextHop: N/A
BkNibID: N/A Interface: GigabitEthernet1/0/1
TableID: 0x2 BkInterface: GigabitEthernet1/0/2
Flag: 0x82d01 BfdSrcIp: N/A
DbIndex: 0xd BfdIfIndex: 0x0
Type: Normal BfdVrfIndex: 0
TrackIndex: 0xffffffff Label: NULL
Preference: 60 vrfIndexDst: 0
BfdMode: N/A vrfIndexNH: 0
Permanent: 0 Tag: 0
Destination: 0.0.0.0/0
NibID: 0x1100000b NextHop: 2.2.2.11
MainNibID: N/A BkNextHop: N/A
BkNibID: N/A Interface: GigabitEthernet1/0/3
TableID: 0x2 BkInterface: GigabitEthernet1/0/4
Flag: 0x82d01 BfdSrcIp: N/A
DbIndex: 0xd BfdIfIndex: 0x0
Type: Normal BfdVrfIndex: 0
TrackIndex: 0xffffffff Label: NULL
Preference: 60 vrfIndexDst: 0
BfdMode: N/A vrfIndexNH: 0
Permanent: 0 Tag: 0
...
Table 18 Command output
|
Field |
Description |
|
destination |
Destination address/prefix. |
|
NibID |
ID of the NIB. |
|
MainNibID |
ID of the primary next hop for static route FRR. |
|
BkNibID |
ID of the backup next hop for static route FRR. |
|
NextHop |
Next hop address. |
|
BkNextHop |
Backup next hop address. |
|
Interface |
Output interface of the route. |
|
BkInterface |
Backup output interface. |
|
TableID |
ID of the table to which the route belongs. |
|
Flag |
Flag of the route. |
|
DbIndex |
Index of the database to which the route belongs. |
|
Type |
Route type: · Normal. · DHCP. · NAT. · IPsec. |
|
BfdSrcIp |
Source IP address of the indirect BFD session. |
|
BfdIfIndex |
Index of the interface where BFD is enabled. |
|
BfdVrfIndex |
Index of the VPN instance where BFD is enabled. This field displays 0 if BFD is enabled for the IPv4 public network. |
|
BfdMode |
BFD session mode: · N/A—No BFD session is configured. · Ctrl—Control packet mode · Echo—Echo packet mode. |
|
TrackIndex |
NQA Track index. |
|
vrfIndexDst |
Index of VPN instance to which the destination belongs. For the IPv4 public network, this field displays 0. |
|
vrfIndexNH |
Index of the VPN instance to which the next hop belongs. For the IPv4 public network, this field displays 0. |
|
Permanent |
Permanent static route flag. 1 indicates a permanent static route. |
ip route-static
Use ip route-static to configure a static route.
Use undo ip route-static to delete a static route.
Syntax
ip route-static { dest-address { mask-length | mask } | group group-name } { interface-type interface-number [ next-hop-address ] [ backup-interface interface-type interface-number [ backup-nexthop backup-nexthop-address ] [ permanent ] | bfd { control-packet | echo-packet } | permanent | track track-entry-number ] | next-hop-address [ bfd control-packet bfd-source ip-address | permanent | track track-entry-number ] | vpn-instance d-vpn-instance-name next-hop-address [ bfd control-packet bfd-source ip-address | permanent | track track-entry-number ] } [ preference preference ] [ tag tag-value ] [ description text ]
undo ip route-static { dest-address { mask-length | mask } | group group-name } [ interface-type interface-number [ next-hop-address ] | next-hop-address | vpn-instance d-vpn-instance-name next-hop-address ] [ preference preference ]
ip route-static vpn-instance s-vpn-instance-name { dest-address { mask-length | mask } | group group-name } { interface-type interface-number [ next-hop-address ] [ backup-interface interface-type interface-number [ backup-nexthop backup-nexthop-address ] [ permanent ] | bfd { control-packet | echo-packet } | permanent | track track-entry-number ] | next-hop-address [ public ] [ bfd control-packet bfd-source ip-address | permanent | track track-entry-number ] | vpn-instance d-vpn-instance-name next-hop-address [ bfd control-packet bfd-source ip-address | permanent | track track-entry-number ] } [ preference preference ] [ tag tag-value ] [ description text ]
undo ip route-static vpn-instance s-vpn-instance-name { dest-address { mask-length | mask } | group group-name } [ interface-type interface-number [ next-hop-address ] | next-hop-address [ public ] | vpn-instance d-vpn-instance-name next-hop-address ] [ preference preference ]
ip route-static topology topo-name { dest-address { mask | mask-length } | group group-name } { next-hop-address | interface-type interface-number [ next-hop-address [ backup-interface interface-type interface-number backup-nexthop backup-nexthop-address ] ] } [ preference preference ] [ tag tag-value ] [ description text ]
undo ip route-static topology topo-name { dest-address { mask | mask-length } | group group-name } [ next-hop-address | interface-type interface-number [ next-hop-address ] ] [ preference preference ]
Default
No static route is configured.
Views
System view
Predefined user roles
network-admin
Parameters
vpn-instance s-vpn-instance-name: Specifies a source MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. Each VPN has its own routing table, and the configured static route is installed in the routing tables of the specified VPNs.
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. The topology named base represents the base topology. Each topology has its own routing table, and the configured static route is installed in the routing tables of the specified topologies.
dest-address: Specifies the destination IP address of the static route, in dotted decimal notation.
mask-length: Specifies the mask length, an integer in the range of 0 to 32.
mask: Specifies the subnet mask in dotted decimal notation.
group group-name: Specifies a static route group by its name, a case-sensitive string of 1 to 31 characters.
vpn-instance d-vpn-instance-name: Specifies a destination MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If a destination VPN is specified, packets will search for the output interface in the destination VPN based on the configured next hop address.
interface-type interface-number: Specifies an output interface by its type and number. For more information, see Layer 3—IP Routing Configuration Guide.
next-hop-address: Specifies the IP address of the next hop, in dotted decimal notation. For more information, see Layer 3—IP Routing Configuration Guide.
backup-interface interface-type interface-number: Specifies a backup output interface by its type and number. If the backup output interface is an NBMA interface or broadcast interface and not a P2P interface, you must specify the backup next hop address.
backup-nexthop backup-nexthop-address: Specifies a backup next hop address.
bfd: Enables BFD to detect reachability of the static route's next hop. When the next hop is unreachable, the system immediately switches to the backup route.
control-packet: Specifies the BFD control mode.
bfd-source ip-address: Specifies the source IP address of BFD packets. As a best practice, specify the loopback interface address.
permanent: Specifies the route as a permanent static route. If the output interface is down, the permanent static route is still active.
track track-entry-number: Associates the static route with a track entry specified by its number in the range of 1 to 1024. For more information about Track, see High Availability Configuration Guide.
echo-packet: Specifies the BFD echo mode.
public: Indicates that the specified next hop address is on the public network.
preference preference: Specifies a preference for the static route, in the range of 1 to 255. The default is 60.
tag tag-value: Sets a tag value for marking the static route, in the range of 1 to 4294967295. The default is 0. Tags of routes are used for route control in routing policies. For more information about routing policies, see Layer 3—IP Routing Configuration Guide.
description text: Configures a description of 1 to 60 characters for the static route. The description can include special characters, such as the space, except the question mark (?).
Usage guidelines
If the destination IP address and the mask are both 0.0.0.0 (or 0), the configured route is a default route. The default route is used for forwarding a packet matching no entry in the routing table.
Implement different routing policies to configure different route preferences. For example, to enable load sharing for multiple routes to the same destination, assign the same preference to the routes. To enable the routes to back up one another, assign different preferences to them.
Follow these guidelines when you specify the output interface or the next hop address of the static route:
· If the output interface is a Null 0 interface, no next hop address is required.
· If the output interface is a point-to-point interface, you can specify only the output interface. You do not need to change the configuration of the route even if the peer address is changed.
· NBMA or P2MP interfaces need IP address-to-link layer address mappings for successful packet delivery. If the output interface is an NBMA or P2MP interface, specify the next hop address for the route at the same time as a best practice.
· If the output interface is a broadcast interface that might have multiple next hops, you must specify the next hop address at the same time.
Follow these guidelines when you configure a static route:
· Enabling BFD for a flapping route could worsen the route flapping situation. Therefore, use it with caution. For more information about BFD, see High Availability Configuration Guide.
· For static routing-Track-NQA collaboration, you must configure the same VPN instance ID for the next hop to be detected and the NQA operation.
· If a static route needs route recursion, the associated track entry must monitor the next hop of the recursive route instead of that of the static route. Otherwise, a valid route might be mistakenly considered invalid.
· Do not specify the permanent keyword together with the bfd or track keyword.
If you specify a static route group, all prefixes in the static route group will be assigned the next hop and output interface specified by using this command.
Examples
# Configure a static route, whose destination address is 1.1.1.1/24, next hop address is 2.2.2.2, tag value is 45, and description information is for internet.
<Sysname> system-view
[Sysname] ip route-static 1.1.1.1 24 2.2.2.2 tag 45 description for internet
Related commands
display ip routing-table protocol
ip route-static-group
prefix
ip route-static default-preference
Use ip route-static default-preference to configure a default preference for static routes.
Use undo ip route-static default-preference to restore the default.
Syntax
ip route-static default-preference default-preference
undo ip route-static default-preference
Default
The default preference of static routes is 60.
Views
System view
Predefined user roles
network-admin
Parameters
default-preference: Specifies a default preference for static routes, in the range of 1 to 255.
Usage guidelines
If no preference is specified for a static route, the default preference applies.
When the default preference is reconfigured, it applies only to newly added static routes.
Examples
# Set a default preference of 120 for static routes.
<Sysname> system-view
[Sysname] ip route-static default-preference 120
Related commands
display ip routing-table protocol
ip route-static fast-reroute auto
Use ip route-static fast-reroute auto to configure static route FRR to automatically select a backup next hop.
Use undo ip route-static fast-reroute auto to disable static route FRR from automatically selecting a backup next hop.
Syntax
ip route-static fast-reroute auto
undo ip route-static fast-reroute auto
Default
Static route FRR is disabled from automatically selecting a backup next hop.
Views
System view
Predefined user roles
network-admin
Examples
# Configure static route FRR to automatically select a backup next hop.
<Sysname> system-view
[Sysname] ip route-static fast-reroute auto
ip route-static primary-path-detect bfd echo
Use ip route-static primary-path-detect bfd echo to enable BFD echo packet mode for static route FRR.
Use undo ip route-static primary-path-detect bfd to disable BFD echo packet mode for static route FRR.
Syntax
ip route-static primary-path-detect bfd echo
undo ip route-static primary-path-detect bfd
Default
BFD echo packet mode for static route FRR is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This command enables static route FRR to use BFD echo packet mode for fast failure detection on the primary link.
Examples
# Enable BFD echo packet mode for static route FRR.
<Sysname> system-view
[Sysname] ip route-static 1.1.1.1 32 gigabitethernet 1/0/1 2.2.2.2 backup-interface gigabitethernet 1/0/2 backup-nexthop 3.3.3.3
[Sysname] ip route-static primary-path-detect bfd echo
ip route-static-group
Use ip route-static-group to create a static route group and enter its view, or enter the view of an existing static route group.
Use undo ip route-static-group to delete a static route group.
Syntax
ip route-static-group group-name
undo ip route-static-group group-name
Default
No static route groups exist.
Views
System view
Predefined user roles
network-admin
Parameters
group-name: Specifies the static route group name, a case-sensitive string of 1 to 31 characters.
Parameters
Execute the ip route-static command to configure static routes in batches after you create a static route group with static route prefixes.
Examples
# Create the static route group test and enter its view.
<Sysname> system-view
[Sysname] ip route-static-group test
[Sysname-route-static-group-test]
Related commands
ip route-static
prefix
prefix
Use prefix to configure a static route prefix.
Use undo prefix to delete a static route prefix.
Syntax
prefix dest-address { mask-length | mask }
undo prefix dest-address { mask-length | mask }
Default
No static route prefix is configured.
Views
Static route group view
Predefined user roles
network-admin
Parameters
dest-address: Specifies the destination IP address of the static route, in dotted decimal notation.
mask-length: Specifies the mask length, an integer in the range of 0 to 32.
mask: Specifies the subnet mask in dotted decimal notation.
Usage guidelines
Execute the prefix command repeatedly to add multiple static route prefixes to a static route group.
After you create a static route group with static route prefixes, execute the ip route-static command to configure static routes with the prefixes. To configure more static routes, you only need to add new static route prefixes to the group.
Examples
# Configure the static route prefix 1.1.1.1/32 for the static route group test.
<Sysname> system-view
[Sysname] ip route-static-group test
[Sysname-route-static-group-test] prefix 1.1.1.1 32
Related commands
ip route-static
ip route-static-group
RIP commands
bfd all-interfaces enable
Use bfd all-interfaces enable to enable BFD on all interfaces of a RIP process.
Use undo bfd all-interfaces enable to restore the default.
Syntax
bfd all-interfaces enable [ ctrl ]
undo bfd all-interfaces enable
Default
BFD is disabled on the interfaces of a RIP process.
Views
RIP view
Predefined user roles
network-admin
Parameters
ctrl: Enables BFD bidirectional control detection for both directly and indirectly connected neighbors. If you do not specify this keyword, RIP uses BFD single-hop echo detection for a directly connected neighbor and BFD bidirectional control detection for an indirectly connected neighbor.
Usage guidelines
RIP supports the following BFD detection modes:
· Single-hop echo detection—Detection mode for a directly connected neighbor. In this mode, a BFD session is established only when the directly connected neighbor has route information to send.
· Single-hop echo detection for a specific destination—Detection mode for a directly connected neighbor. In this mode, a BFD session is established to the specified RIP neighbor when RIP is enabled on the local interface.
· Bidirectional control detection—Detection mode for both directly and indirectly connected neighbors. In this mode, a BFD session is established only when both ends have routes to send and BFD is enabled on the receiving interface.
Bidirectional control detection must be configured on both ends of the link to take effect.
The BFD setting configured in interface view takes precedence over the BFD setting configured in RIP view.
Using the undo peer command cannot delete the neighbor relationship immediately to bring down the BFD session.
Examples
# Enable BFD on all interfaces of RIP process 1.
<Sysname> system-view
[Sysname] rip 1
[Sysname-rip-1] bfd all-interfaces enable
Related commands
rip bfd
checkzero
Use checkzero to enable zero field check on RIPv1 messages.
Use undo checkzero to disable zero field check.
Syntax
checkzero
undo checkzero
Default
The zero field check feature is enabled.
Views
RIP view
Predefined user roles
network-admin
Usage guidelines
When the zero field check is enabled, the router discards RIPv1 messages in which zero fields contain non-zero values. If all messages are trustworthy, disable this feature to reduce the workload of the CPU.
Examples
# Disable zero field check on RIPv1 messages for RIP process 1.
<Sysname> system-view
[Sysname] rip
[Sysname-rip-1] undo checkzero
default cost
Use default cost to configure a default metric for redistributed routes.
Use undo default cost to restore the default.
Syntax
default cost cost-value
undo default cost
Default
The default metric of redistributed routes is 0.
Views
RIP view
Predefined user roles
network-admin
Parameters
cost-value: Specifies a default metric for redistributed routes, in the range of 0 to 16.
Usage guidelines
When you use the import-route command to redistribute routes from another routing protocol without specifying a metric, the metric specified by the default cost command applies.
Examples
# Configure a default metric of 3 for redistributed routes.
<Sysname> system-view
[Sysname] rip 1
[Sysname-rip-1] default cost 3
Related commands
import-route
default-route
Use default-route to configure all interfaces running a RIP process to advertise a default route with a specified metric to RIP neighbors.
Use undo default-route to restore the default.
Syntax
default-route { only | originate } [ cost cost-value | route-policy route-policy-name ] *
undo default-route
Default
No default route is sent to RIP neighbors.
Views
RIP view
Predefined user roles
network-admin
Parameters
only: Advertises only a default route.
originate: Advertises both a default route and other routes.
cost-value: Specifies a cost for the default route, in the range of 1 to 15. The default is 1.
route-policy route-policy-name: Specifies a routing policy by its name, a case sensitive string of 1 to 63 characters. If you specify this option, the command advertises a default route only when a route in the routing table matches the routing policy.
Usage guidelines
A RIP router configured with this feature does not receive any default route from RIP neighbors.
Examples
# Configure all interfaces running RIP process 100 to send only a default route with a metric of 2 to RIP neighbors.
<Sysname> system-view
[Sysname] rip 100
[Sysname-rip-100] default-route only cost 2
Related commands
rip default-route
display rip
Use display rip to display state and configuration information for a RIP process.
Syntax
display rip [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535. If no process is specified, the command displays state and configuration information for all RIP processes.
Examples
# Display current state and configuration information for all RIP processes.
<Sysname> display rip
Public VPN-instance name:
RIP process: 1
RIP version: 1
Preference: 100
Routing policy: abc
Fast-reroute:
Routing policy: frr
Checkzero: Enabled
Default cost: 0
Summary: Enabled
Host routes: Enabled
Maximum number of load balanced routes: 8
Update time : 30 secs Timeout time : 180 secs
Suppress time : 120 secs Garbage-collect time : 120 secs
Update output delay: 20(ms) Output count: 3
TRIP retransmit time: 5(s) Retransmit count: 36
Graceful-restart interval: 60 secs
Triggered Interval : 5 50 200
BFD: Enabled (ctrl)
Silent interfaces: None
Default routes: Originate Default routes cost: 3
Verify-source: Enabled
Networks:
1.0.0.0
Configured peers:
197.168.6.2
Triggered updates sent: 0
Number of routes changes: 1
Number of replies to queries: 0
Table 19 Command output
|
Field |
Description |
|
Public VPN-instance name/Private VPN-instance name |
Public network or VPN where the RIP process runs. |
|
RIP process |
RIP process ID. |
|
RIP version |
RIP version 1 or 2. |
|
Preference |
RIP preference. |
|
Checkzero |
Indicates whether the zero field check is enabled for RIPv1 messages: Enabled or Disabled. |
|
Default cost |
Default cost of redistributed routes. |
|
Summary |
Indicates whether route summarization is enabled: Enabled or Disabled. |
|
Host routes |
Indicates whether to receive host routes: Enabled or Disabled. |
|
Update time |
RIP update interval, in seconds. |
|
Timeout time |
RIP timeout time, in seconds. |
|
Suppress time |
RIP suppress interval, in seconds. |
|
Garbage-collect time |
RIP garbage-collection interval, in seconds. |
|
Update output delay |
RIP packet sending interval, in seconds. |
|
Output count |
Maximum number of RIP packets sent at each interval. |
|
TRIP retransmit time |
TRIP message retransmission interval, in seconds. |
|
Retransmit count |
Retransmission times of TRIP messages. |
|
Graceful-restart interval |
GR interval, in seconds. |
|
Triggered Interval |
Triggered update sending interval. |
|
BFD |
Whether BFD is enabled: · Disabled—Disabled in RIP view. · Enabled—Enabled in RIP view. RIP uses BFD single-hop echo detection for a directly connected neighbor and BFD bidirectional control detection for an indirectly connected neighbor. · Enabled (ctrl)—Enabled in RIP view. RIP uses BFD bidirectional control detection for both directly and indirectly connected neighbors. |
|
Silent interfaces |
Silent interfaces, which do not periodically send updates. |
|
Default routes |
Indicates whether a default route is sent to RIP neighbors. · only—Only a default route is advertised. · originate—A default route is advertised along with other routes. · disable—No default route is advertised. |
|
Default routes cost |
Metric for a default route. |
|
Verify-source |
Indicates whether the source IP address is checked for received RIP routing updates: Enabled or Disabled. |
|
Networks |
Networks enabled with RIP. |
|
Configured peers |
Configured neighbors. |
|
Triggered updates sent |
Number of triggered updates sent. |
|
Number of routes changes |
Number of route changes. |
|
Number of replies to queries |
Number of RIP responses. |
display rip database
Use display rip database to display active routes for a RIP process. RIP advertises active routes in RIP routing updates.
Syntax
display rip process-id database [ ip-address { mask-length | mask } ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
ip-address { mask-length | mask }: Displays active routes for the specified IP address. If you do not specify this argument, the command displays all actives routes for a RIP process.
Examples
# Display active routes for RIP process 100.
<Sysname> display rip 100 database
1.0.0.0/8, auto-summary
1.1.1.0/24, cost 16, interface summary
1.1.1.0/24, cost 0, nexthop 1.1.1.1, RIP-interface
1.1.2.0/24, cost 0, imported
2.0.0.0/8, auto-summary
2.0.0.0/8, cost 1, nexthop 1.1.1.2
# Display active routes with destination IP address 1.1.1.0 and mask length 24 for RIP process 100.
<Sysname> display rip 100 database 1.1.1.0 24
1.1.1.0/24, cost 16, interface summary
1.1.1.0/24, cost 0, nexthop 1.1.1.1, RIP-interface
Table 20 Command output
|
Field |
Description |
|
cost |
Cost of the route. |
|
auto-summary |
Indicates that the route is a RIP automatic summary route. |
|
interface summary |
Indicates that the route is a RIP interface summary route. |
|
nexthop |
Address of the next hop. |
|
RIP-interface |
Direct route on a RIP-enabled interface. |
|
imported |
Indicates that the route is redistributed from another routing protocol. |
display rip graceful-restart
Use display rip graceful-restart to display the GR status for a RIP process.
Syntax
display rip [ process-id ] graceful-restart
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays the GR status for all RIP processes.
Examples
# Display the GR status for RIP process 1.
<Sysname> display rip 1 graceful-restart
RIP process: 1
Graceful Restart capability : Enabled
Current GR state : Normal
Graceful Restart period : 60 seconds
Graceful Restart remaining time : 0 seconds
Table 21 Command output
|
Field |
Description |
|
Indicates whether GR is enabled: Enabled or Disabled. |
|
|
GR state: · Under GR—GR is in progress. · Normal—No GR is in progress or GR has completed. |
|
|
GR interval. |
display rip interface
Use display rip interface to display RIP interface information for a RIP process.
Syntax
display rip process-id interface [ interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
interface-type interface-number: Specifies an interface by its type and number. If no interface is specified, the command displays information about all RIP interfaces for the RIP process.
Examples
# Display information about all interfaces for RIP process 1.
<Sysname> display rip 1 interface
Total: 1
Interface: GigabitEthernet1/0/2
Address/Mask: 1.1.1.1/24 Version: RIPv1
MetricIn: 0 MetricIn route policy: Not designated
MetricOut: 1 MetricOut route policy: Not designated
Split-horizon/Poison-reverse: On/Off Input/Output: On/On
Default route: Off
Update output delay: 20(ms) Output count: 3
BFD: Enabled (ctrl), inherited
Current number of packets/Maximum number of packets: 0/2000
Table 22 Command output
|
Field |
Description |
|
Total |
Number of interfaces running RIP. |
|
Interface |
Name of an interface running RIP. |
|
Address/Mask |
IP address and mask of the interface. |
|
Version |
RIP version running on the interface. |
|
MetricIn |
Additional metric added to incoming routes. |
|
MetricIn route policy |
Name of the routing policy used to add an additional metric for incoming routes. If no routing policy is used, the field displays Not designated. |
|
MetricOut |
Additional metric added to outgoing routes. |
|
MetricOut route policy |
Name of the routing policy used to add an additional routing metric for outgoing routes. If no routing policy is used, the field displays Not designated. |
|
Split-horizon |
Indicates whether split horizon is enabled: · on—Enabled. · off—Disabled. |
|
Poison-reverse |
Indicates whether poison reverse is enabled: · on—Enabled. · off—Disabled. |
|
Input/Output |
Indicates whether the interface is enabled to receive and send RIP messages: · on—Enabled. · off—Disabled. |
|
Default route |
Indicates whether to send a default route to RIP neighbors: · Only—Advertises only a default route. · Originate—Advertises both a default route and other routes. · No-originate—Advertises only non-default routes. · Off—Advertises no default route. |
|
Default route cost |
Metric for a default route. |
|
Update output delay |
RIP packet sending interval. |
|
Output count |
Maximum number of RIP packets that can be sent at each interval. |
|
BFD |
Whether BFD for RIP is enabled: · Disabled—Disabled in interface view and RIP view. · Enabled—Enabled on the RIP interface. The interface uses BFD single-hop echo detection for a directly connected neighbor and BFD bidirectional control detection for an indirectly connected neighbor. · Enabled (ctrl)—Enabled on the RIP interface. The interface uses BFD bidirectional control detection for both directly and indirectly connected neighbors. · Enabled, inherited—Enabled in RIP view. RIP uses BFD single-hop echo detection for a directly connected neighbor and BFD bidirectional control detection for an indirectly connected neighbor. The RIP interface uses the BFD setting configured in RIP view. · Enabled (ctrl), inherited—Enabled in RIP view. RIP uses BFD bidirectional control detection for both directly and indirectly connected neighbors. The RIP interface uses the BFD setting configured in RIP view. · Enabled (destination)—Enabled on the RIP interface. The interface uses BFD single-hop echo detection for a specific destination. |
|
Current number of packets /Maximum number of packets |
Number of RIP packets to be sent/maximum number of RIP packets that can be sent within a certain interval. |
display rip neighbor
Use display rip neighbor to display neighbor information for a RIP process.
Syntax
display rip process-id neighbor [ interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
interface-type interface-number: Specifies an interface by its type and number. If you do not specify this argument, the command displays all neighbor information for the RIP process.
Examples
# Display neighbor information for RIP process 1.
<Sysname> display rip 1 neighbor
Neighbor address: 197.168.2.3
Interface : GigabitEthernet1/0/2
Version : RIPv2 Last update: 00h00m02s
Relay nbr : N/A BFD session: N/A
Bad packets: 0 Bad routes : 0
Table 23 Command output
|
Field |
Description |
|
Interface |
Output interface that is connected to the neighbor. |
|
Version |
Version of RIP that the neighbor runs. |
|
Last update |
Time elapsed since the most recent update. |
|
Relay nbr |
Relay neighbor type. |
|
BFD session type. |
|
|
Number of received bad packets. |
|
|
Number of received bad routes. |
|
|
TRIP neighbor. |
display rip non-stop-routing
Use display rip non-stop-routing to display the NSR status for a RIP process.
Syntax
display rip [ process-id ] non-stop-routing
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays the NSR status for all RIP processes.
Usage guidelines
The following matrix shows the command and hardware compatibility:
|
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
Yes |
|
MSR3600-28/3600-51 |
Yes |
|
MSR3600-28-SI/3600-51-SI |
Yes |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Command compatibility |
|
MSR810-LM-GL |
No |
|
MSR810-W-LM-GL |
No |
|
MSR830-6EI-GL |
No |
|
MSR830-10EI-GL |
No |
|
MSR830-6HI-GL |
No |
|
MSR830-10HI-GL |
No |
|
MSR2600-6-X1-GL |
No |
|
MSR3600-28-SI-GL |
No |
Examples
# Display the NSR status for RIP process 1.
<Sysname> display rip 1 non-stop-routing
RIP process: 1
Nonstop Routing capability: Enabled
Current NSR state : Finish
Table 24 Command output
|
Field |
Description |
|
Nonstop Routing capability |
Indicates whether NSR is enabled: Enabled or Disabled. |
|
Current NSR state |
NSR state: · Initialization. · Smooth—Upgrading data. · Advertising—Advertising routes. · Redistribution—Redistributing routes. · Finish. |
display rip route
Use display rip route to display routing information for a RIP process.
Syntax
display rip process-id route [ ip-address { mask-length | mask } [ verbose ] | peer ip-address | statistics ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
ip-address { mask-length | mask }: Displays route information for the specified IP address.
verbose: Displays all routing information for the specified destination IP address. If you do not specify this keyword, the command displays only information about optimal routes with the specified destination IP address.
peer ip-address: Displays route information learned from the specified neighbor.
statistics: Displays route statistics, including the total number of routes and number of routes from each neighbor.
Usage guidelines
If no optional parameters are specified, the display rip process-id route command displays all routing information for a RIP process.
Examples
# Display all routing information for RIP process 1.
<Sysname> display rip 1 route
Route Flags: R - RIP, T - TRIP
P - Permanent, A - Aging, S - Suppressed, G - Garbage-collect
D - Direct, O - Optimal, F - Flush to RIB
----------------------------------------------------------------------------
Peer 1.1.1.1 on GigabitEthernet1/0/2
Destination/Mask Nexthop Cost Tag Flags Sec
3.0.0.0/8 1.1.1.1 1 0 RAOF 24
Local route
Destination/Mask Nexthop Cost Tag Flags Sec
4.4.4.4/32 0.0.0.0 0 0 RDOF -
1.1.1.0/24 0.0.0.0 0 0 RDOF -
# Display specified routing information for RIP process 1.
<Sysname> display rip 1 route 3.0.0.0 8 verbose
Route Flags: R - RIP, T - TRIP
P - Permanent, A - Aging, S - Suppressed, G - Garbage-collect
D - Direct, O - Optimal, F - Flush to RIB
----------------------------------------------------------------------------
Peer 1.1.1.1 on GigabitEthernet1/0/2
Destination/Mask OrigNexthop/RealNexthop Cost Tag Flags Sec
3.0.0.0/8 1.1.1.1/1.1.1.1 1 0 RAOF 16
Table 25 Command output
|
Field |
Description |
|
Route Flags |
· R—RIP route. · T—TRIP route. · P—The route never ages out. · A—The route is aging. · S—The route is suppressed. · G—The route is in Garbage-collect state. · D—The route is a direct route. · O—The route is an optimal route. · F—The route has been flushed to the RIB. |
|
Peer X.X.X.X on interface-type interface-number |
Routing information learned from a neighbor on a RIP interface. |
|
Local route |
Locally generated direct routes. |
|
Destination/Mask |
Destination IP address and subnet mask. |
|
Nexthop |
Next hop of the route. |
|
OrigNexthop/RealNexthop |
If the route is from a directly connected neighbor, the original next hop is the real next hop. If the route is from an indirectly connected neighbor, the RealNexthop field displays the recursive next hop for the route. Otherwise, the field is blank. |
|
Cost |
Cost of the route. |
|
Tag |
Route tag. |
|
Flags |
Route state. |
|
Sec |
Remaining time of the timer corresponding to the route state. |
# Display routing statistics for RIP process 1.
<Sysname> display rip 1 route statistics
Peer Optimal/Aging Optimal/Permanent Garbage
1.1.1.1 1/1 0/0 0
Local 2/0 0/0 0
Total 3/1 0/0 0
Table 26 Command output
|
Field |
Description |
|
Peer |
IP address of a neighbor. |
|
Optimal |
Total number of optimal routes. |
|
Aging |
Total number of aging routes. |
|
Permanent |
Total number of routes that never age out. |
|
Garbage |
Total number of routes in the Garbage-collection state. |
|
Local |
Total number of locally generated direct routes. |
|
Total |
Total number of routes learned from all RIP neighbors. |
fast-reroute
Use fast-reroute to configure RIP FRR.
Use undo fast-reroute to disable RIP FRR.
Syntax
fast-reroute route-policy route-policy-name
undo fast-reroute
Default
RIP FRR is disabled.
Views
RIP view
Predefined user roles
network-admin
Parameters
route-policy route-policy-name: Specifies a routing policy by its name, a case sensitive string of 1 to 63 characters. If you specify this option, the command designates a backup next hop for the routes that match the routing policy.
Usage guidelines
RIP FRR is available only when the state of primary link (with Layer 3 interfaces staying up) changes from bidirectional to unidirectional or down. A unidirectional link refers to the link through which packets are forwarded only from one end to the other.
RIP FRR is only effective for RIP routes that are learned from directly connected neighbors.
Equal-cost routes do not support RIP FRR.
Examples
# Enable RIP FRR and use routing policy frr to specify a backup next hop.
<Sysname> system-view
[Sysname] ip prefix-list abc index 10 permit 100.1.1.0 24
[Sysname] route-policy frr permit node 10
[Sysname-route-policy-frr-10] if-match ip address prefix-list abc
[Sysname-route-policy-frr-10] apply fast-reroute backup-interface gigabitethernet 1/0/1 backup-nexthop 193.1.1.8
[Sysname-route-policy-frr-10] quit
[Sysname] rip 100
[Sysname-rip-100] fast-reroute route-policy frr
filter-policy export
Use filter-policy export to configure RIP to filter redistributed routes.
Use undo filter-policy export to remove the filtering.
Syntax
filter-policy { ipv4-acl-number | prefix-list prefix-list-name } export [ interface-type interface-number | bgp | direct | eigrp [ eigrp-as ] | { isis | ospf | rip } [ process-id ] | static ]
undo filter-policy export [ interface-type interface-number | bgp | direct | eigrp [ eigrp-as ] | { isis | ospf | rip } [ process-id ] | static ]
Default
RIP does not filter redistributed routes.
Views
RIP view
Predefined user roles
network-admin
Parameters
ipv4-acl-number: Specifies an IPv4 ACL by its number in the range of 2000 to 3999 to filter redistributed routes.
prefix-list prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter redistributed routes.
interface-type interface-number: Specifies an interface by its type and number.
bgp: Filters routes redistributed from BGP.
direct: Filters direct routes.
eigrp: Filters routes redistributed from EIGRP.
isis: Filters routes redistributed from IS-IS.
ospf: Filters routes redistributed from OSPF.
rip: Filters routes redistributed from RIP.
eigrp-as: Specifies an EIGRP process by its ID in the range of 1 to 65535. The default value is 1.
process-id: Specifies a process ID of IS-IS, OSPF, or RIP, in the range of 1 to 65535. The default value is 1.
Usage guidelines
You can configure only one filtering policy to filter routes redistributed from a routing protocol or an interface. Without any protocol or interface specified, the filtering policy applies globally. If you execute this command multiple times, the most recent configuration takes effect.
To remove the filtering policy configured for a protocol or an interface, use the undo filter-policy export command with the protocol or interface specified.
To reference an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL using one of the following methods:
· To deny/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny/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 route. The specified subnet mask must be contiguous. Otherwise, the mask configuration does not take effect.
Examples
# Use basic ACL 2000 to filter redistributed routes.
<Sysname> system-view
[Sysname] acl basic 2000
[Sysname-acl-ipv4-basic-2000] rule deny source 192.168.10.0 0.0.0.255
[Sysname-acl-ipv4-basic-2000] quit
[Sysname] rip 1
[Sysname-rip-1] filter-policy 2000 export
# Use IP prefix list abc to filter redistributed routes.
<Sysname> system-view
[Sysname] ip prefix-list abc index 10 permit 11.0.0.0 8
[Sysname] rip 1
[Sysname-rip-1] filter-policy prefix-list abc export
# Configure advanced ACL 3000 to permit only route 113.0.0.0/16 to pass. Use ACL 3000 to filter redistributed routes.
<Sysname> system-view
[Sysname] acl advanced 3000
[Sysname-acl-ipv4-adv-3000] rule 10 permit ip source 113.0.0.0 0 destination 255.255.0.0 0
[Sysname-acl-ipv4-adv-3000] rule 100 deny ip
[Sysname-acl-ipv4-adv-3000] quit
[Sysname] rip 1
[Sysname-rip-1] filter-policy 3000 export
acl (ACL and QoS Command Reference)
import-route
ip prefix-list
filter-policy import
Use filter-policy import to configure RIP to filter received routes.
Use undo filter-policy import to remove the filtering.
Syntax
filter-policy { ipv4-acl-number | gateway prefix-list-name | prefix-list prefix-list-name [ gateway prefix-list-name ] } import [ interface-type interface-number ]
undo filter-policy import [ interface-type interface-number ]
Default
RIP does not filter received routes.
Views
RIP view
Predefined user roles
network-admin
Parameters
ipv4-acl-number: Specifies an IPv4 ACL by its number in the range of 2000 to 3999 to filter received routes.
prefix-list prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter received routes.
gateway prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter routes based on their next hops.
interface-type interface-number: Specifies an interface by its type and number.
Usage guidelines
You can configure only one filtering policy to filter routes received on an interface. Without any interface specified, the filtering policy applies globally. If you execute this command multiple times, the most recent configuration takes effect.
To remove the filtering policy configured for an interface, use the undo filter-policy import command with the interface specified.
To reference an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL using one of the following methods:
· To deny/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command
· To deny/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 route. The subnet mask must be contiguous. Otherwise, the mask configuration does not take effect.
Examples
# Use basic ACL 2000 to filter received RIP routes.
<Sysname> system-view
[Sysname] acl basic 2000
[Sysname-acl-ipv4-basic-2000] rule deny source 192.168.10.0 0.0.0.255
[Sysname-acl-ipv4-basic-2000] quit
[Sysname] rip 1
[Sysname-rip-1] filter-policy 2000 import
# Use IP prefix list abc to filter received RIP routes.
<Sysname> system-view
[Sysname] ip prefix-list abc index 10 permit 11.0.0.0 8
[Sysname] rip 1
[Sysname-rip-1] filter-policy prefix-list abc import
# Configure advanced ACL 3000 to permit only route 113.0.0.0/16 to pass. Use ACL 3000 to filter received routes.
<Sysname> system-view
[Sysname] acl advanced 3000
[Sysname-acl-ipv4-adv-3000] rule 10 permit ip source 113.0.0.0 0 destination 255.255.0.0 0
[Sysname-acl-ipv4-adv-3000] rule 100 deny ip
[Sysname-acl-ipv4-adv-3000] quit
[Sysname] rip 1
[Sysname-rip-1] filter-policy 3000 import
Related commands
acl (ACL and QoS Command Reference)
ip prefix-list
graceful-restart
Use graceful-restart to enable RIP GR.
Use undo graceful-restart to disable RIP GR.
Syntax
graceful-restart
undo graceful-restart
Default
RIP GR is disabled.
Views
RIP view
Predefined user roles
network-admin
Usage guidelines
The graceful-restart command and the non-stop-routing command are mutually exclusive.
Examples
# Enable GR for RIP process 1.
<Sysname> system-view
[Sysname] rip 1
[Sysname-rip-1] graceful-restart
graceful-restart interval
Use graceful-restart interval to set the GR interval.
Use undo graceful-restart interval to restore the default.
Syntax
graceful-restart interval interval
undo graceful-restart interval
Default
The GR interval is 60 seconds.
Views
RIP view
Predefined user roles
network-admin
Parameters
interval: Specifies the GR interval in the range of 5 to 360 seconds.
Examples
# Set the GR interval to 200 seconds for RIP process 1.
[Sysname] rip 1
[Sysname-rip-1] graceful-restart interval 200
host-route
Use host-route to enable host route reception.
Use undo host-route to disable host route reception.
Syntax
host-route
undo host-route
Default
RIP receives host routes.
Views
RIP view
Predefined user roles
network-admin
Usage guidelines
A router might receive many host routes from the same subnet. These routes are not helpful for routing and occupy a large number of resources. To solve this problem, use the undo host-route command to disable RIP from receiving host routes.
This command takes effect only for RIPv2 routes.
Examples
# Disable RIP from receiving host routes.
<Sysname> system-view
[Sysname] rip 1
[Sysname-rip-1] undo host-route
import-route
Use import-route to enable route redistribution.
Use undo import-route to disable route redistribution.
Syntax
import-route bgp [ as-number ] [ allow-ibgp ] [ cost cost-value | route-policy route-policy-name | tag tag ] *
import-route { direct | static } [ cost cost-value | route-policy route-policy-name | tag tag ] *
import-route eigrp [ eigrp-as | all-as ] [ allow-direct | cost cost-value | route-policy route-policy-name | tag tag ] *
import-route { isis | ospf | rip } [ process-id | all-processes ] [ allow-direct | cost cost-value | route-policy route-policy-name | tag tag ] *
undo import-route { bgp | direct | eigrp [ eigrp-as | all-as ] | { isis | ospf | rip } [ process-id | all-processes ] | static }
Default
RIP does not redistribute routes.
Views
RIP view
Predefined user roles
network-admin
Parameters
bgp: Redistributes BGP routes.
direct: Redistributes direct routes.
eigrp: Redistributes EIGRP routes.
isis: Redistributes IS-IS routes.
ospf: Redistributes OSPF routes.
rip: Redistributes RIP routes.
static: Redistributes static routes.
as-number: Specifies an AS by its number in the range of 1 to 4294967295. If you do not specify the as-number argument, this command redistributes all IPv4 EBGP routes. As a best practice, specify the AS number to avoid redistributing excessive IPv4 EBGP routes.
eigrp-as: Specifies an EIGRP process by its ID in the range of 1 to 65535. The default value is 1.
all-as: Specifies all EIGRP processes.
process-id: Specifies a process ID of IS-IS, OSPF, or RIP, in the range of 1 to 65535. The default is 1.
all-processes: Specifies all processes of IS-IS, OSPF, or RIP.
allow-ibgp: Allows redistribution of IBGP routes.
allow-direct: Redistributes the networks of the local interfaces enabled with the specified routing protocol. If you do not specify this keyword, the networks of the local interfaces are not redistributed. If you specify both the allow-direct keyword and the route-policy route-policy-name option, make sure the if-match rule defined in the routing policy does not conflict with the allow-direct keyword. For example, if you specify the allow-direct keyword, do not configure the if-match route-type rule for the routing policy. Otherwise, the allow-direct keyword does not take effect.
cost cost-value: Specifies a cost for redistributed routes, in the range of 0 to 16. The default cost is 0.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
tag tag: Specifies a tag for marking redistributed routes, in the range of 0 to 65535. The default is 0.
Usage guidelines
This command redistributes only active routes. To view route state information, use the display ip routing-table protocol command.
The import-route bgp command redistributes only EBGP routes if you do not specify the allow-ibgp keyword. To redistribute IBGP routes in addition to EBGP routes, specify the allow-ibgp keyword.
|
|
IMPORTANT: Improper redistribution of IBGP routes might cause routing loops. When you use the allow-ibgp keyword, make sure you understand its impact on the network. |
When you execute the undo form of the command, per-process setting has higher priority than the all-processes setting.
· The undo import-route { isis | ospf | rip } all-processes command cannot remove the setting configured for a process by using the import-route { isis | ospf | rip } process-id command. To remove the setting for that process, you must specify the process ID in the undo form of the command.
· The undo import-route eigrp all-as command cannot remove the setting configured for an EIGRP process by using the import-route eigrp eigrp-as command. To remove the setting for that process, you must specify the process number in the undo form of the command.
Examples
# Redistribute static routes into RIP, and set the cost for redistributed routes to 4.
<Sysname> system-view
[Sysname] rip 1
[Sysname-rip-1] import-route static cost 4
Related commands
default cost
maximum load-balancing
Use maximum load-balancing to set the maximum number of equal-cost multi-path (ECMP) routes for load balancing.
Use undo maximum load-balancing to restore the default.
Syntax
maximum load-balancing number
undo maximum load-balancing
Default
The maximum number of RIP ECMP routes is 32.
Views
RIP view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of ECMP routes, in the range of 1 to 32.
Examples
# Set the maximum number of ECMP routes to 2.
<Sysname> system-view
[Sysname] rip
[Sysname-rip-1] maximum load-balancing 2
network
Use network to enable RIP on an interface attached to a specified network.
Use undo network to disable RIP on an interface attached to a specified network.
Syntax
network network-address [ wildcard-mask ]
undo network network-address
Default
RIP is disabled on an interface.
Views
RIP view
Predefined user roles
network-admin
Parameters
network-address: Specifies a subnet address where an interface resides.
wildcard-mask: Specifies an IP address wildcard mask. A wildcard mask can be thought of as a subnet mask, with 1s and 0s inverted. For example, a wildcard mask of 255.255.255.0 corresponds to a subnet mask of 0.0.0.255. If you do not specify this argument, the command uses the natural mask.
Usage guidelines
RIP runs only on an interface attached to the specified network, which can be configured with a wildcard mask. An interface not on the specified network does not receive or send RIP routes, or advertise its direct routes.
For a single RIP process, the network 0.0.0.0 command can enable RIP on all interfaces. If multiple RIP processes exist, the command is not applicable.
If a physical interface is attached to multiple networks, you cannot advertise these networks in different RIP processes.
Examples
# Enable RIP process 100 on the interface attached to the network 129.102.0.0.
<Sysname> system-view
[Sysname] rip 100
[Sysname-rip-100] network 129.102.0.0
Related commands
rip enable
non-stop-routing
Use non-stop-routing to enable RIP NSR.
Use undo non-stop-routing to disable RIP NSR.
Syntax
Default
RIP NSR is disabled.
Views
RIP view
Predefined user roles
network-admin
Usage guidelines
The following matrix shows the command and hardware compatibility:
|
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/ 810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
Yes |
|
MSR3600-28/3600-51 |
Yes |
|
MSR3600-28-SI/3600-51-SI |
Yes |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Command compatibility |
|
MSR810-LM-GL |
No |
|
MSR810-W-LM-GL |
No |
|
MSR830-6EI-GL |
No |
|
MSR830-10EI-GL |
No |
|
MSR830-6HI-GL |
No |
|
MSR830-10HI-GL |
No |
|
MSR2600-6-X1-GL |
No |
|
MSR3600-28-SI-GL |
No |
RIP NSR enabled for a RIP process takes effect only on that process. As a best practice, enable RIP NSR for each process if multiple RIP processes exist.
The non-stop-routing command and the graceful-restart command are mutually exclusive.
Examples
# Enable NSR for RIP process 1.
[Sysname] rip 1
[Sysname-rip-1] non-stop-routing
output-delay
Use output-delay to set the rate at which an interface sends RIP packets.
Use undo output-delay to restore the default.
Syntax
output-delay time count count
undo output-delay
Default
An interface sends up to three RIP packets every 20 milliseconds.
Views
RIP view
Predefined user roles
network-admin
Parameters
time: Specifies the sending interval in the range of 10 to 100 milliseconds.
count: Specifies the maximum number of RIP packets sent at each interval, in the range of 1 to 30.
Examples
# Configure all interfaces running RIP process 1 to send up to 10 RIP packets every 60 milliseconds.
<Sysname> system-view
[Sysname] rip 1
[Sysname-rip-1] output-delay 60 count 10
peer
Use peer to specify a RIP neighbor in the NBMA network, where routing updates destined for the neighbor are only unicasts and not multicast or broadcast.
Use undo peer to remove a RIP neighbor.
Syntax
peer ip-address
undo peer ip-address
Default
RIP does not unicast updates to any neighbor.
Views
RIP view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the IP address of a RIP neighbor, in dotted decimal notation.
Usage guidelines
Do not use the peer ip-address command when the neighbor is directly connected. Otherwise, the neighbor might receive both unicast and multicast (or broadcast) messages with the same routing information.
This command must be executed together with the undo validate-source-address command, which disables source IP address check on inbound RIP routing updates.
Examples
# Configure RIP to unicast updates to peer 202.38.165.1.
<Sysname> system-view
[Sysname] rip 1
[Sysname-rip-1] peer 202.38.165.1
Related commands
validate-source-address
preference
Use preference to specify a preference for RIP routes.
Use undo preference to restore the default.
Syntax
preference { preference | route-policy route-policy-name } *
undo preference
Default
The preference of RIP routes is 100.
Views
RIP view
Predefined user roles
network-admin
Parameters
preference: Specifies a preference for RIP routes, in the range of 1 to 255. The smaller the value, the higher the preference.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
You can specify a routing policy by using the keyword route-policy to set a preference for matching RIP routes.
· The preference set by the routing policy applies to all matching RIP routes. The preference of other routes is set by the preference command.
· If no preference is set by the routing policy, the preference of all RIP routes is set by the preference command.
Examples
# Set a preference of 120 for RIP routes.
<Sysname> system-view
[Sysname] rip 1
[Sysname-rip-1] preference 120
reset rip process
Use reset rip process to reset a RIP process.
Syntax
reset rip process-id process
Views
User view
Predefined user roles
network-admin
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
Usage guidelines
After executing the command, you are prompted to confirm the operation.
Examples
# Reset RIP process 100.
<Sysname> reset rip 100 process
Reset RIP process? [Y/N]:y
reset rip statistics
Use reset rip statistics to clear statistics for a RIP process.
Syntax
reset rip process-id statistics
Views
User view
Predefined user roles
network-admin
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
Examples
# Clear statistics for RIP process 100.
<Sysname> reset rip 100 statistics
rip
Use rip to enable RIP and enter RIP view.
Use undo rip to disable RIP.
Syntax
rip [ process-id ] [ vpn-instance vpn-instance-name ]
undo rip [ process-id ]
Default
RIP is disabled.
Views
System view
Predefined user roles
network-admin
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535. The default is 1.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If no VPN is specified, the RIP process runs on the public network.
Usage guidelines
You must enable a RIP process before configuring global parameters for it. This restriction does not apply to configuring interface parameters.
If you disable a RIP process, the configured interface parameters become invalid.
Examples
# Enable RIP process 1 and enter RIP view.
<Sysname> system-view
[Sysname] rip
[Sysname-rip-1]
rip authentication-mode
Use rip authentication-mode to configure RIPv2 authentication.
Use undo rip authentication-mode to restore the default.
Syntax
rip authentication-mode { md5 { rfc2082 { cipher | plain } string key-id | rfc2453 { cipher | plain } string } | simple { cipher | plain } string }
undo rip authentication-mode
Default
RIPv2 authentication is not configured.
Views
Interface view
Predefined user roles
network-admin
Parameters
md5: Specifies the MD5 authentication.
rfc2082: Uses the message format defined in RFC 2082.
cipher: Specifies a password in encrypted form.
plain: Specifies a password in plaintext form. For security purposes, the password specified in plaintext form will be stored in encrypted form.
string: Specifies the password. Its plaintext form is a case-sensitive string of 1 to 16 characters. Its encrypted form is a case-sensitive string of 33 to 53 characters.
key-id: Specifies the key ID in the range of 1 to 255.
rfc2453: Uses the message format defined in RFC 2453 (IETF standard).
simple: Specifies the simple authentication mode.
Usage guidelines
A newly configured key overwrites the old one, if any.
Although you can specify an authentication mode for RIPv1 in interface view, the configuration does not take effect because RIPv1 does not support authentication.
Examples
# Configure MD5 authentication on GigabitEthernet 1/0/1, and specify a plaintext key rose in the format defined in RFC 2453.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip version 2
[Sysname-GigabitEthernet1/0/1] rip authentication-mode md5 rfc2453 plain rose
Related commands
rip version
rip bfd
Use rip bfd to enable or disable BFD for RIP on an interface.
Use undo rip bfd to remove the configuration.
Syntax
rip bfd { disable | enable [ ctrl | destination ip-address ] }
undo rip bfd
Default
BFD for RIP is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
disable: Disables BFD for RIP on an interface.
enable: Enables BFD for RIP on an interface.
ctrl: Enables BFD bidirectional control detection for both directly and indirectly connected neighbors. If you do not specify this keyword, the interface uses BFD single-hop echo detection for a directly connected neighbor and BFD bidirectional control detection for an indirectly connected neighbor.
destination ip-address: Specifies a destination to which the interface establishes a BFD session. If you do not specify this option, the interface establishes a BFD session to its RIP neighbor.
Usage guidelines
RIP supports the following BFD detection modes:
· Single-hop echo detection—Detection mode for a directly connected neighbor. In this mode, a BFD session is established only when the directly connected neighbor has route information to send.
· Single-hop echo detection for a specific destination—Detection mode for a directly connected neighbor. In this mode, a BFD session is established to the specified RIP neighbor when RIP is enabled on the local interface.
· Bidirectional control detection—Detection mode for both directly and indirectly connected neighbors. In this mode, a BFD session is established only when both ends have routes to send and BFD is enabled on the receiving interface.
If you specify the destination ip-address option, the interface uses BFD single-hop echo detection to detect failures on the link to the specified destination. If a failure is detected on the link, the interface does not send or receive RIP packets anymore.
The bfd all-interfaces enable command enables BFD for RIP on all interfaces of a RIP process. If the link to one of the interfaces becomes unstable, the BFD session might flap on the interface. This will affect the stability of the network. To resolve this problem, use the rip bfd disable command to disable BFD on that interface.
Bidirectional control detection must be configured on both ends of the link to take effect.
Using the undo peer command cannot delete the neighbor relationship immediately to bring down the BFD session.
Examples
# Enable BFD for RIP on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip bfd enable
rip bfd enable destination
Use rip bfd enable destination to enable BFD single-hop echo detection for a specific destination.
Use undo rip bfd enable to disable BFD single-hop echo detection for RIP.
Syntax
rip bfd enable destination ip-address
undo rip bfd enable
Default
BFD single-hop echo detection for a specific destination is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
The rip bfd enable destination command applies only to BFD echo-mode detection.
The rip bfd enable destination command and the rip bfd enable command are mutually exclusive and cannot be configured on a device at the same time.
When a link failure occurs between the local device and the specified neighbor, BFD can detect the failure. The local device will not receive or send any RIP packets through the interface connected to the neighbor.
Examples
# Enable BFD on GigabitEthernet 1/0/1 for a specific destination 202.38.165.1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip bfd enable destination 202.38.165.1
rip default-route
Use rip default-route to configure a RIP interface to advertise a default route with a specified metric.
Use undo rip default-route to disable a RIP interface from sending a default route.
Syntax
rip default-route { { only | originate } [ cost cost-value | route-policy route-policy-name ] * | no-originate }
undo rip default-route
Default
A RIP interface advertises a default route if the RIP process that the interface runs is enabled to advertise a default route.
Views
Interface view
Predefined user roles
network-admin
Parameters
only: Advertises only a default route.
originate: Advertises both a default route and other routes.
cost-value: Specifies a cost for the default route, in the range of 1 to 15. The default is 1.
route-policy route-policy-name: Specifies a routing policy by its name, a case sensitive string of 1 to 63 characters. If you specify this option, the command advertises a default route only when a route in the routing table matches the routing policy.
no-originate: Advertises only non-default routes.
Usage guidelines
An interface that is enabled to advertise a default route does not receive any default route from RIP neighbors.
Examples
# Configure GigabitEthernet 1/0/1 to advertise only a default route with a metric of 2.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip default-route only cost 2
# Configure GigabitEthernet 1/0/1 to advertise a default route with a metric of 4 and other routes.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip default-route originate cost 4
Related commands
default-route
rip enable
Use rip enable to enable RIP on an interface.
Use undo rip enable to disable RIP on an interface.
Syntax
rip process-id enable [ exclude-subip ]
undo rip enable
Default
RIP is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
exclude-subip: Excludes secondary IP addresses from being enabled with RIP. If you do not specify this keyword, RIP is also enabled on secondary IP addresses of a RIP-enabled interface.
Usage guidelines
The rip enable command has a higher priority than the network command.
Examples
# Enable RIP process 100 on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip 100 enable
Related commands
network
rip input
Use rip input to enable an interface to receive RIP messages.
Use undo rip input to disable an interface from receiving RIP messages.
Syntax
rip input
undo rip input
Default
An interface is enabled to receive RIP messages.
Views
Interface view
Predefined user roles
network-admin
Examples
# Disable GigabitEthernet 1/0/1 from receiving RIP messages.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] undo rip input
rip max-packet-length
Use rip max-packet-length to set the maximum length of RIP packets.
Use undo rip max-packet-length to restore the default.
Syntax
rip max-packet-length value
undo rip max-packet-length
Default
The maximum length of RIP packets is 512 bytes.
Views
Interface view
Predefined user roles
network-admin
Parameters
value: Specifies the maximum length of RIP packets, in the range of 32 to 65535 bytes.
Usage guidelines
If the configured value in the rip max-packet-length command is greater than the MTU of an interface, the interface MTU value is used as the maximum length of RIP packets.
The supported maximum length of RIP packets varies by vendor. Use this feature with caution to avoid compatibility issues.
When authentication is enabled, follow these guidelines to ensure packet forwarding:
· For simple authentication, the maximum length of RIP packets must be no less than 52 bytes.
· For MD5 authentication (with packet format defined in RFC 2453), the maximum length of RIP packets must be no less than 56 bytes.
· For MD5 authentication (with packet format defined in RFC 2082), the maximum length of RIP packets must be no less than 72 bytes.
Examples
# Set the maximum length of RIP packets on GigabitEthernet 1/0/1 to 1024 bytes.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip max-packet-length 1024
rip metricin
Use rip metricin to configure an interface to add a metric to inbound routes.
Use undo rip metricin to restore the default.
Syntax
rip metricin [ route-policy route-policy-name ] value
undo rip metricin
Default
The additional metric of an inbound route is 0.
Views
Interface view
Predefined user roles
network-admin
Parameters
route-policy route-policy-name: Specifies a routing policy by its name, a case sensitive string of 1 to 63 characters. If you specify this option, the command adds an additional metric for the routes that match the routing policy.
value: Adds an additional metric to inbound routes, in the range of 0 to 16.
Usage guidelines
When a valid RIP route is received, the system adds a metric to it and then installs it into the routing table. The metric of the route received on the configured interface is then increased. If the sum of the additional metric and the original metric is greater than 16, the metric of the route will be 16.
If a routing policy is referenced with the route-policy keyword, the following operations can be performed:
· Routes matching the policy are added with the metric specified in the apply cost command configured in the policy. Routes not matching it are added with the metric specified in the rip metricin command. The rip metricin command does not support specifying the + or – keyword in the apply cost command to add or reduce a metric.
· If the apply cost command is not configured in the policy, all the inbound routes are added with the metric specified in the rip metricin command.
Examples
# Configure GigabitEthernet 1/0/1 to add a metric of 6 to the inbound route 1.0.0.0/8 and to add a metric of 2 to other inbound routes.
<Sysname> system-view
[Sysname] ip prefix-list 123 permit 1.0.0.0 8
[Sysname] route-policy abc permit node 10
[Sysname-route-policy-abc-10] if-match ip address prefix-list 123
[Sysname-route-policy-abc-10] apply cost 6
[Sysname-route-policy-abc-10] quit
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip metricin route-policy abc 2
Related commands
apply cost
rip metricout
Use rip metricout to configure an interface to add a metric to outbound routes.
Use undo rip metricout to restore the default.
Syntax
rip metricout [ route-policy route-policy-name ] value
undo rip metricout
Default
The additional metric for outbound routes is 1.
Views
Interface view
Predefined user roles
network-admin
Parameters
route-policy route-policy-name: Specifies a routing policy by its name, a case sensitive string of 1 to 63 characters. If you specify this option, the command adds an additional metric for the routes that match the routing policy.
value: Adds an additional metric to outbound routes, in the range of 1 to 16.
Usage guidelines
With the command configured on an interface, the metric of RIP routes sent on the interface will be increased.
If a routing policy is referenced with the route-policy keyword, the following operations can be performed:
· Routes matching the policy is added with the metric specified in the apply cost command configured in the policy. Routes not matching it are added with the metric specified in the rip metricout command. The rip metricout command does not support specifying the + or – keyword in the apply cost command to add or reduce a metric.
· If the apply cost command is not configured in the policy, all the outbound routes are added with the metric specified in the rip metricout command.
Examples
# Configure GigabitEthernet 1/0/1 to add a metric of 6 to the outbound route 1.0.0.0/8 and to add a metric of 2 to other outbound routes.
<Sysname> system-view
[Sysname] ip prefix-list 123 permit 1.0.0.0 8
[Sysname] route-policy abc permit node 10
[Sysname-route-policy-abc-10] if-match ip address prefix-list 123
[Sysname-route-policy-abc-10] apply cost 6
[Sysname-route-policy-abc-10] quit
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip metricout route-policy abc 2
Related commands
apply cost
rip mib-binding
Use rip mib-binding to bind a RIP process to MIB.
Use undo rip mib-binding to restore the default.
Syntax
rip mib-binding process-id
undo rip mib-binding
Default
MIB is bound to the RIP process with the smallest process ID.
Views
System view
Predefined user roles
network-admin
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
Usage guidelines
If the specified process ID does not exist, the MIB binding configuration does not take effect.
Deleting a RIP process bound to MIB deletes the MIB binding configuration. After the RIP process is deleted, MIB is bound to the RIP process with the smallest process ID.
Examples
# Bind RIP process 100 to MIB.
<Sysname> system-view
[Sysname] rip mib-binding 100
rip output
Use rip output to enable an interface to send RIP messages.
Use undo rip output to disable an interface from sending RIP messages.
Syntax
rip output
undo rip output
Default
An interface sends RIP messages.
Views
Interface view
Predefined user roles
network-admin
Examples
# Disable GigabitEthernet 1/0/1 from sending RIP messages.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] undo rip output
rip output-delay
Use rip output-delay to set the RIP packet sending interval for an interface and the maximum number of RIP packets that can be sent at each interval.
Use undo rip output-delay to restore the default.
Syntax
rip output-delay time count count
Default
An interface uses the RIP packet sending rate set for the RIP process that the interface runs.
Views
Interface view
Predefined user roles
network-admin
Parameters
Time: Specifies the RIP packet sending interval in the range of 10 to 100 milliseconds.
count: Specifies the maximum number of RIP packets sent at each interval, in the range of 1 to 30.
Examples
# Configure GigabitEthernet 1/0/1 to send a maximum of six RIP packets every 30 milliseconds.
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip output-delay 30 count 6
Related commands
output-delay
rip poison-reverse
Use rip poison-reverse to enable the poison reverse feature.
Use undo rip poison-reverse to disable the poison reverse feature.
Syntax
rip poison-reverse
undo rip poison-reverse
Default
The poison reverse feature is disabled.
Views
Interface view
Predefined user roles
network-admin
Examples
# Enable the poison reverse feature on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip poison-reverse
rip primary-path-detect bfd
Use rip primary-path-detect bfd to enable BFD for RIP FRR.
Use undo rip primary-path-detect bfd to disable BFD for RIP FRR.
Syntax
rip primary-path-detect bfd { ctrl | echo }
undo rip primary-path-detect bfd
Default
BFD for RIP FRR is disabled.
Views
Interface view
Predefined user roles
network-admin
Parameters
ctrl: Enables BFD bidirectional control detection for RIP FRR to detect primary link failures.
echo: Enables BFD single-hop echo detection for RIP FRR to detect primary link failures.
Usage guidelines
For quicker RIP FRR, use BFD on the primary link of redundant links to detect link failure.
Bidirectional control detection must be configured on both ends of the link to take effect.
Examples
# Enable BFD single-hop echo detection for RIP FRR on GigabitEthernet 1/0/1 to detect primary link failures.
<Sysname> system-view
[Sysname] rip 1
[Sysname-rip-1] fast-reroute route-policy frr
[Sysname-rip-1] quit
[Sysname] bfd echo-source-ip 1.1.1.1
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip primary-path-detect bfd echo
rip split-horizon
Use rip split-horizon to enable the split horizon feature.
Use undo rip split-horizon to disable the split horizon feature.
Syntax
rip split-horizon
undo rip split-horizon
Default
The split horizon feature is enabled.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
· The split horizon feature prevents routing loops. If you want to disable the feature, make sure the operation is necessary.
· On NBMA networks, such as FR where multiple VCs are configured on the primary and secondary interfaces, disable split horizon to ensure correct route advertisement. For more information about FR, see frame relay configuration in Layer 2—WAN Configuration Guide.
· If both split horizon and poison reverse are enabled, only the poison reverse feature takes effect.
Examples
# Enable the split horizon feature on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip split-horizon
rip summary-address
Use rip summary-address to configure a summary route on an interface.
Use undo rip summary-address to remove a summary route on an interface.
Syntax
rip summary-address ip-address { mask-length | mask }
undo rip summary-address ip-address { mask-length | mask }
Default
No summary route is configured on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the destination IP address of the summary route.
mask-length: Specifies the subnet mask length of the summary route, in the range of 0 to 32.
mask: Specifies the subnet mask of the summary route, in dotted decimal notation.
Usage guidelines
This command takes effect only when automatic route summarization is disabled.
Examples
# Configure a summary route on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip summary-address 10.0.0.0 255.255.255.0
Related commands
summary
rip triggered
Use rip triggered to enable TRIP.
Use undo rip triggered to disable TRIP.
Syntax
Default
TRIP is disabled.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
TRIP runs only on link layer protocols: PPP and frame relay.
Examples
# Enable TRIP.
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] rip triggered
rip version
Use rip version to specify a RIP version on an interface.
Use undo rip version to restore the default.
Syntax
rip version { 1 | 2 [ broadcast | multicast ] }
undo rip version
Default
No RIP version is configured on an interface. The interface can send RIPv1 broadcasts, and receive RIPv1 broadcasts and unicasts, and RIPv2 broadcasts, multicasts, and unicasts.
Views
Interface view
Predefined user roles
network-admin
Parameters
1: Specifies the RIP version as RIPv1.
2: Specifies the RIP version as RIPv2.
[ broadcast | multicast ]: Sends RIPv2 messages in broadcast mode or multicast mode (default).
Usage guidelines
If an interface has no RIP version configured, it uses the global RIP version. Otherwise, it uses the RIP version configured on it.
An interface running RIPv1 can perform the following operations:
· Sends RIPv1 broadcast messages.
· Receives RIPv1 broadcast and unicast messages.
An interface running RIPv2 in broadcast mode can perform the following operations:
· Sends RIPv2 broadcast messages.
· Receives RIPv1 broadcast and unicast messages, and RIPv2 broadcast, multicast, and unicast messages.
An interface running RIPv2 in multicast mode can perform the following operations:
· Sends RIPv2 multicast messages.
· Receives RIPv2 broadcast, multicast, and unicast messages.
Examples
# Configure RIPv2 in broadcast mode on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rip version 2 broadcast
version
silent-interface
Use silent-interface to disable interfaces from sending RIP messages. The interfaces can still receive RIP messages.
Use undo silent-interface to enable interfaces to send RIP messages.
Syntax
silent-interface { interface-type interface-number | all }
undo silent-interface { interface-type interface-number | all }
Default
All RIP interfaces can send RIP messages.
Views
RIP view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Disables a specified interface from sending RIP messages.
all: Disables all interfaces from sending RIP messages.
Examples
# Disable all interfaces from sending RIP messages except GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] rip 100
[Sysname-rip-100] silent-interface all
[Sysname-rip-100] undo silent-interface gigabitethernet 1/0/1
[Sysname-rip-100] network 131.108.0.0
summary
Use summary to enable automatic RIPv2 route summarization. Natural masks are used to advertise summary routes to reduce the size of routing tables.
Use undo summary to disable automatic RIPv2 route summarization to advertise all subnet routes.
Syntax
summary
undo summary
Default
Automatic RIPv2 route summarization is enabled.
Views
RIP view
Predefined user roles
network-admin
Usage guidelines
Automatic RIPv2 route summarization can reduce the routing table size to enhance the scalability and efficiency for large networks.
Examples
# Disable automatic RIPv2 route summarization.
<Sysname> system-view
[Sysname] rip
[Sysname-rip-1] undo summary
Related commands
rip summary-address
rip version
timer triggered
Use timer triggered to set the interval for sending triggered updates.
Use undo timer triggered to restore the default.
Syntax
timer triggered maximum-interval [ minimum-interval [ incremental-interval ] ]
Default
The maximum interval is 5 seconds, the minimum interval is 50 milliseconds, and the incremental interval is 200 milliseconds.
Views
RIP view
Predefined user roles
network-admin
Parameters
maximum-interval: Specifies the maximum interval in the range of 1 to 5 seconds.
minimum-interval: Specifies the minimum interval in the range of 10 to 5000 milliseconds.
incremental-interval: Specifies the incremental interval in the range of 100 to 1000 milliseconds.
Usage guidelines
The minimum-interval and incremental-interval cannot be greater than the maximum-interval.
For a stable network, the minimum-interval setting is used. If network changes become frequent, the triggered update sending interval is incremented by incremental-interval × 2n-2 for each triggered update until the maximum-interval is reached. The value n is the number of triggered update times.
Examples
# For RIP process 1, set the maximum interval, minimum interval, and incremental interval to 2 seconds, 100 milliseconds, and 100 milliseconds, respectively.
[Sysname] rip 1
[Sysname-rip-1] timer triggered 2 100 100
timers
Use timers to set RIP timers.
Use undo timers to restore the default.
Syntax
timers { garbage-collect garbage-collect-value | suppress suppress-value | timeout timeout-value | update update-value } *
undo timers { garbage-collect | suppress | timeout | update } *
Default
The garbage-collect timer is 120 seconds, the suppress timer is 120 seconds, the timeout timer is 180 seconds, and the update timer is 30 seconds.
Views
RIP view
Predefined user roles
network-admin
Parameters
garbage-collect-value: Specifies the garbage-collect timer in the range of 1 to 3600 seconds.
suppress-value: Specifies the suppress timer in the range of 0 to 3600 seconds.
timeout-value: Specifies the timeout timer in the range of 1 to 3600 seconds.
update-value: Specifies the update timer in the range of 1 to 3600 seconds.
Usage guidelines
RIP uses the following timers:
· Update timer—Specifies the interval between routing updates.
· Timeout timer—Specifies the route aging time. If no update for a route is received before the timer expires, RIP sets the metric of the route to 16.
· Suppress timer—Specifies how long a RIP route stays in suppressed state. When the metric of a route becomes 16, the route enters the suppressed state. If RIP receives an update for the route with a metric less than 16 from the same neighbor, RIP uses this route to replace the suppressed route.
· Garbage-collect timer—Specifies the interval from when the metric of a route becomes 16 to when it is deleted from the routing table. During the garbage-collect timer length, RIP advertises the route with a metric of 16. If no update is announced for that route before the garbage-collect timer expires, RIP deletes the route from the routing table.
As a best practice, do not change the default values of these timers.
The timer lengths must be consistent on all routers on the network.
The timeout timer must be greater than the update timer.
Examples
# Set the update, timeout, suppress, and garbage-collect timers to 5, 15, 15, and 30 seconds.
<Sysname> system-view
[Sysname] rip 100
[Sysname-rip-100] timers update 5 timeout 15 suppress 15 garbage-collect 30
trip retransmit count
Use trip retransmit count to set the maximum retransmission times of TRIP update responses.
Use undo trip retransmit count to restore the default.
Syntax
trip retransmit count retransmit-count-value
Default
The maximum times for retransmitting a TRIP update response is 36.
Views
RIP view
Predefined user roles
network-admin
Parameters
retransmit-count-value: Specifies the maximum retransmission times of update responses, in the range of 1 to 3600.
Examples
# Set the maximum retransmission times of update responses to 20 for RIP process 1.
[Sysname] rip 1
[Sysname-rip-1] trip retransmit count 20
trip retransmit timer
Use trip retransmit timer to set the interval for retransmitting a TRIP Update Request or Update Response.
Use undo trip retransmit timer to restore the default.
Syntax
trip retransmit timer retransmit-time-value
Default
The interval for retransmitting a TRIP Update Request or Update Response is 5 seconds.
Views
RIP view
Predefined user roles
network-admin
Parameters
retransmit-time-value: Specifies the TRIP Update Request or Update Response retransmission interval in the range of 1 to 3600 seconds.
Examples
# Set the TRIP Update Request or Update Response retransmission interval to 80 seconds for RIP process 1.
[Sysname] rip 1
[Sysname-rip-1] trip retransmit timer 80
validate-source-address
Use validate-source-address to enable source IP address check on inbound RIP routing updates.
Use undo validate-source-address to disable source IP address check on inbound RIP routing updates.
Syntax
validate-source-address
undo validate-source-address
Default
Source IP address check on inbound RIP routing updates is enabled.
Views
RIP view
Predefined user roles
network-admin
Examples
# Disable source IP address check on inbound RIP routing updates.
<Sysname> system-view
[Sysname-rip] rip 100
[Sysname-rip-100] undo validate-source-address
version
Use version to specify a global RIP version.
Use undo version to restore the default.
Syntax
version { 1 | 2 }
undo version
Default
No global RIP version is configured. An RIP interface can send RIPv1 broadcasts and receive RIPv1 broadcasts and unicasts, and RIPv2 broadcasts, multicasts, and unicasts.
Views
RIP view
Predefined user roles
network-admin
Parameters
1: Specifies the RIP version as RIPv1.
2: Specifies the RIP version as RIPv2. RIPv2 messages are multicast.
Usage guidelines
An interface prefers the RIP version configured on it over the global RIP version.
If no RIP version is specified for the interface and the global version is RIPv1, the interface uses RIPv1 and can perform the following operations:
· Send RIPv1 broadcasts.
· Receive RIPv1 broadcasts and unicasts.
If no RIP version is specified for the interface and the global version is RIPv2, the interface uses RIPv2 multicast mode and can perform the following operations:
· Send RIPv2 multicasts.
· Receive RIPv2 broadcasts, multicasts, and unicasts.
Examples
# Specify the global RIP version as RIPv2.
<Sysname> system-view
[Sysname] rip 100
[Sysname-rip-100] version 2
Related commands
rip version
OSPF commands
abr-summary (OSPF area view)
Use abr-summary to configure route summarization on an ABR.
Use undo abr-summary to remove the configuration.
Syntax
abr-summary ip-address { mask-length | mask } [ advertise | not-advertise ] [ cost cost-value ]
undo abr-summary ip-address { mask-length | mask }
Default
Route summarization is not configured on an ABR.
Views
OSPF area view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the destination IP address of the summary route in dotted decimal notation.
mask-length: Specifies the mask length in the range of 0 to 32.
mask: Specifies the mask of the IP address, in dotted decimal notation.
advertise | not-advertise: Advertises the summary route or not. By default, the command advertises the summary route.
cost cost-value: Specifies the cost of the summary route, in the range of 1 to 16777215. The default cost is the largest cost value among routes that are summarized.
Usage guidelines
This command applies only to an ABR to summarize multiple contiguous networks into one network.
To enable ABR to advertise specific routes that have been summarized, use the undo abr-summary command.
Examples
# Summarize networks 36.42.10.0/24 and 36.42.110.0/24 in Area 1 into 36.42.0.0/16.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] area 1
[Sysname-ospf-100-area-0.0.0.1] network 36.42.10.0 0.0.0.255
[Sysname-ospf-100-area-0.0.0.1] network 36.42.110.0 0.0.0.255
[Sysname-ospf-100-area-0.0.0.1] abr-summary 36.42.0.0 255.255.0.0
area (OSPF view)
Use area to create an area and enter area view.
Use undo area to remove an area.
Syntax
area area-id
undo area area-id
Default
No OSPF areas exist.
Views
OSPF view
Predefined user roles
network-admin
Parameters
area-id: Specifies an area by its ID, an IP address or a decimal integer in the range of 0 to 4294967295 that is translated into the IP address format.
Examples
# Create Area 0 and enter Area 0 view.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] area 0
[Sysname-ospf-100-area-0.0.0.0]
asbr-summary
Use asbr-summary to configure route summarization on an ASBR.
Use undo asbr-summary to remove the configuration.
Syntax
asbr-summary ip-address { mask-length | mask } [ cost cost-value | not-advertise | nssa-only | tag tag ] *
undo asbr-summary ip-address { mask-length | mask }
Default
Route summarization is not configured on an ASBR.
Views
OSPF view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the destination IP address of the summary route.
mask-length: Specifies the mask length in the range of 0 to 32.
mask: Specifies the mask in dotted decimal notation.
cost cost-value: Specifies the cost of the summary route, in the range of 1 to 16777214. If you do not specify this option, the largest cost among the summarized routes applies. If the routes in Type-5 LSAs translated from Type-7 LSAs are Type-2 external routes, the largest cost among the summarized routes plus 1 applies.
not-advertise: Disables advertising the summary route. If you do not specify this keyword, the command advertises the route.
nssa-only: Limits the route advertisement to the NSSA area by setting the P-bit of Type-7 LSAs to 0. By default, the P-bit of Type-7 LSAs is set to 1. If the ASBR is also an ABR and FULL state neighbors exist in the backbone area, the P-bit of Type-7 LSAs originated by the ASBR is set to 0. This keyword applies to the NSSA ASBR.
tag tag: Specifies a tag for the summary route, in the range of 0 to 4294967295. The default is 1. The tag can be used by a routing policy to control summary route advertisement.
Usage guidelines
An ASBR can summarize routes in the following LSAs:
· Type-5 LSAs.
· Type-7 LSAs in an NSSA area.
· Type-5 LSAs translated by the ASBR (also an ABR) from Type-7 LSAs in an NSSA area.
If the ASBR (ABR) is not a translator, it cannot summarize routes in Type-5 LSAs translated from Type-7 LSAs.
To enable ASBR to advertise specific routes that have been summarized, use the undo asbr-summary command.
Examples
# Summarize redistributed static routes into a single route, and specify a tag value of 2 and a cost of 100 for the summary route.
<Sysname> system-view
[Sysname] ip route-static 10.2.1.0 24 null 0
[Sysname] ip route-static 10.2.2.0 24 null 0
[Sysname] ospf 100
[Sysname-ospf-100] import-route static
[Sysname-ospf-100] asbr-summary 10.2.0.0 255.255.0.0 tag 2 cost 100
authentication-mode
Use authentication-mode to specify an authentication mode for an OSPF area.
Use undo authentication-mode to remove the configuration.
Syntax
For MD5/HMAC-MD5 authentication:
authentication-mode { hmac-md5 | md5 } key-id { cipher | plain } string
undo authentication-mode [ { hmac-md5 | md5 } key-id ]
For simple authentication:
authentication-mode simple { cipher | plain } string
undo authentication-mode
Default
No authentication is performed for an area.
Views
OSPF area view
Predefined user roles
network-admin
Parameters
hmac-md5: Specifies the HMAC-MD5 authentication mode.
md5: Specifies the MD5 authentication mode.
simple: Specifies the simple authentication mode.
key-id: Specifies a key by its ID in the range of 0 to 255.
cipher: Specifies a key in encrypted form.
plain: Specifies a key in plaintext form. For security purposes, the key specified in plaintext form will be stored in encrypted form.
string: Specifies the key. This argument is case sensitive.
· In simple authentication mode, the plaintext form of the key is a string of 1 to 8 characters. The encrypted form of the key is a string of 33 to 41 characters.
· In MD5/HMAC-MD5 authentication mode, the plaintext form of the key is a string of 1 to 16 characters. The encrypted form of the key is a string of 33 to 53 characters.
Usage guidelines
To establish or maintain adjacencies, routers in the same area must have the same authentication mode and key.
If MD5 or HMAC-MD5 authentication is configured, you can configure multiple keys, each having a unique key ID and key string. As a best practice to minimize the risk of key comprise, use only one key for an area and delete the old key after key replacement.
To replace the key used for MD5 or HMAC-MD5 authentication in an area, you must configure the new key before removing the old key from each router. OSPF uses the key rollover mechanism to ensure that the routers can pass authentication before the replacement is complete across the area. After you configure a new key on a router, the router sends copies of the same packet, each authenticated by a different key, including the new key and the keys in use. This practice continues until the router detects that all its neighbors have the new key.
Examples
# Configure OSPF Area 0 to use the MD5 authentication mode, and set the key ID to 15 and the key to abc in plaintext form.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] area 0
[Sysname-ospf-100-area-0.0.0.0] authentication-mode md5 15 plain abc
ospf authentication-mode
bandwidth-reference (OSPF view)
Use bandwidth-reference to set a reference bandwidth value for link cost calculation.
Use undo bandwidth-reference to restore the default value.
Syntax
bandwidth-reference value
undo bandwidth-reference
Default
The reference bandwidth value is 100 Mbps for link cost calculation.
Views
OSPF view
Predefined user roles
network-admin
Parameters
value: Specifies the reference bandwidth value for link cost calculation, in the range of 1 to 4294967 Mbps.
Usage guidelines
If no cost values are configured for links, OSPF calculates their cost values by using the following formula: Cost = Reference bandwidth value / Expected interface bandwidth. The expected bandwidth of an interface is configured with the bandwidth command (see Interface Command Reference). If the calculated cost is greater than 65535, the value of 65535 is used. If the calculated cost is less than 1, the value of 1 is used.
Examples
# Set the reference bandwidth value to 1000 Mbps.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] bandwidth-reference 1000
Related commands
ospf cost
database-filter peer (OSPF view)
Use database-filter peer to filter LSAs for the specified P2MP neighbor.
Use undo database-filter peer to restore the default.
Syntax
database-filter peer ip-address { all | { ase [ acl ipv4-acl-number ] | nssa [ acl ipv4-acl-number ] | summary [ acl ipv4-acl-number ] } * }
undo database-filter peer ip-address
Default
The LSAs for the specified P2MP neighbor are not filtered.
Views
OSPF view
Predefined user roles
network-admin
Parameters
ip-address: Specifies a P2MP neighbor by its IP address.
all: Filters all LSAs except the Grace LSAs.
ase: Filters Type-5 LSAs.
nssa: Filters Type-7 LSAs.
summary: Filters Type-3 LSAs.
acl ipv4-acl-number: Specifies an IPv4 ACL by its number in the range of 2000 to 3999.
Usage guidelines
To use an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL using one of the following methods:
· To deny/permit LSAs with the specified link state ID, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny/permit LSAs with the specified link state ID 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 link state ID of an LSA and the destination keyword specifies the subnet mask of the LSA. The specified subnet mask must be contiguous.
On an P2MP network, a router might have multiple OSPF neighbors with the P2MP type. Use this command to prevent the router from sending LSAs to the specified neighbor.
If the specified neighbor has already received an LSA, the LSA still exists in the LSDB of the neighbor after you execute the command.
Examples
# Filter all LSAs (except the Grace LSAs) for the P2MP neighbor with the IP address 121.20.20.121.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] database-filter peer 121.20.20.121 all
# Configure advanced ACL 3000 to filter Type-3 LSAs for the P2MP neighbor with the IP address 121.20.20.121.
<Sysname> system-view
[Sysname] acl advanced 3000
[Sysname-acl-ipv4-adv-3000] rule 10 deny ip source 121.20.0.0 0 destination 255.255.0.0 0
[Sysname-acl-ipv4-adv-3000] rule 100 permit ip
[Sysname-acl-ipv4-adv-3000] quit
[Sysname] ospf 1
[Sysname-ospf-1] database-filter peer 121.20.20.121 summary acl 3000
Related commands
ospf database-filter
default
Use default to configure default parameters for redistributed routes.
Use undo default to remove the configuration.
Syntax
default { cost cost-value | tag tag | type type } *
undo default { cost | tag | type } *
Default
The cost is 1, the tag is 1, and the route type is 2.
Views
OSPF view
Predefined user roles
network-admin
Parameters
cost cost-value: Specifies a default cost for redistributed routes, in the range of 0 to 16777214.
tag tag: Specifies a tag for redistributed routes, in the range of 0 to 4294967295.
type type: Specifies a type for redistributed routes: 1 or 2.
Examples
# Set the default cost, tag, and type to 10, 100, and 2 for redistributed external routes.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] default cost 10 tag 100 type 2
Related commands
import-route
default-cost (OSPF area view)
Use default-cost to set a cost for the default route advertised to the stub or NSSA area.
Use undo default-cost to restore the default value.
Syntax
default-cost cost-value
undo default-cost
Default
The cost is 1.
Views
OSPF area view
Predefined user roles
network-admin
Parameters
cost-value: Specifies a cost for the default route advertised to the Stub or NSSA area, in the range of 0 to 16777214.
Usage guidelines
This command takes effect only on the ABR of a stub area or the ABR or ASBR of an NSSA area.
Examples
# Configure Area 1 as a stub area, and set the cost of the default route advertised to the stub area to 20.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] area 1
[Sysname-ospf-100-area-0.0.0.1] stub
[Sysname-ospf-100-area-0.0.0.1] default-cost 20
nssa
stub
default-route-advertise (OSPF view)
Use default-route-advertise to redistribute a default route into the OSPF routing domain.
Use undo default-route-advertise to restore the default.
Syntax
default-route-advertise [ [ [ always | permit-calculate-other ] | cost cost-value | route-policy route-policy-name | type type ] * | summary cost cost-value ]
undo default-route-advertise
Default
No default route is redistributed into the OSPF routing domain.
Views
OSPF view
Predefined user roles
network-admin
Parameters
always: Redistributes a default route in a Type-5 LSA into the OSPF routing domain regardless of whether a default route exists in the routing table. If you do not specify this keyword, the router redistributes a default route only when an active default route that does not belong to the current OSPF process exists in the IP routing table.
permit-calculate-other: Enables OSPF to calculate default routes received from other routers. If you do not specify this keyword, OSPF does not calculate default routes from other routers. If the router does not redistribute any default route in a Type-5 LSA into the OSPF routing domain, the router calculates default routes from other routers. It calculates these routes regardless of whether this keyword is specified.
cost cost-value: Specifies a cost for the default route, in the range of 0 to 16777214. If you do not specify this option, the default cost specified by the default-cost command applies.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters. When the routing policy is matched and one of the following conditions is met, the command redistributes a default route in a Type-5 LSA into the OSPF routing domain:
· A default route exists in the routing table.
· The always keyword is specified.
The routing policy modifies values in the Type-5 LSA.
type type: Specifies a type for the Type-5 LSA: 1 or 2. If you do not specify this option, the default type for the Type-5 LSA specified by the default type command applies.
summary: Advertises the specified default route in a Type-3 LSA. This keyword is available only for VPNs.
Usage guidelines
This command redistributes a default route in a Type-5 LSA, which cannot be redistributed with the import-route command. If the local routing table has no default route, you must specify the always keyword for the command.
The default-route-advertise summary cost command is applicable only to VPNs. It enables a PE router to redistribute a default external route in a Type-3 LSA to CE routers.
Examples
# Redistribute a default route into the OSPF routing domain, regardless of whether the default route exists in the local routing table.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] default-route-advertise always
default
import-route
discard-route
Use discard-route to configure discard routes for summary networks.
Use undo discard-route to restore the default.
Syntax
discard-route { external { preference | suppression } | internal { preference | suppression } } *
undo discard-route [ external | internal ] *
Default
A device generates discard routes with preference 255 for summary networks.
Views
OSPF view
Predefined user roles
network-admin
Parameters
external: Specifies discard routes for redistributed summary networks on the ASBR. These discard routes are external discard routes.
preference: Specifies a preference for external discard routes, in the range of 1 to 255.
suppression: Disables the ASBR from generating external discard routes for summary networks.
internal: Specifies discard routes for summary networks on the ABR. These discard routes are internal discard routes.
preference: Specifies a preference for internal discard routes, in the range of 1 to 255.
suppression: Disables the ABR from generating internal discard routes for summary networks.
Examples
# Generate external and internal discard routes with preference 100 and 200, respectively.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] discard-route external 100 internal 200
description (OSPF/OSPF area view)
Use description to configure a description for an OSPF process or area.
Use undo description to restore the default.
Syntax
description text
undo description
Default
No description is configured for an OSPF process or area.
Views
OSPF view
OSPF area view
Predefined user roles
network-admin
Parameters
text: Specifies a description, a case-sensitive string of 1 to 80 characters.
Usage guidelines
The description specified by this command is used to identify an OSPF process or area.
Examples
# Describe OSPF process 100 as abc.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] description abc
# Describe OSPF Area 0 as bone area.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] area 0
[Sysname-ospf-100-area-0.0.0.0] description bone area
display ospf
Use display ospf to display OSPF process information.
Syntax
display ospf [ process-id ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays information about all OSPF processes.
verbose: Displays detailed OSPF process information. If you do not specify this keyword, the command displays brief OSPF process information.
Examples
# Display detailed OSPF process information.
<Sysname> display ospf verbose
OSPF Process 1 with Router ID 192.168.1.2
OSPF Protocol Information
RouterID: 192.168.1.2 Router type: NSSA
Route tag: 0
Multi-VPN-Instance is not enabled
Ext-community type: Domain ID 0x5, Route Type 0x306, Router ID 0x107
Domain ID: 0.0.0.0:23
Opaque capable
Originating router-LSAs with maximum metric
Condition: On startup for 100 seconds, State: Inactive
Advertise stub links with maximum metric in router-LSAs
Advertise summary-LSAs with metric 16711680
Advertise external-LSAs with metric 16711680
ISPF is enabled
SPF-schedule-interval: 50 (in milliseconds)
LSA generation interval: 5
LSA arrival interval: 1000
Transmit pacing: Interval: 20 Count: 3
Default ASE parameters: Metric: 1 Tag: 1 Type: 2
Route preference: 10
ASE route preference: 150
SPF calculation count: 10
RFC 1583 compatible
Graceful restart interval: 120
SNMP trap rate limit interval: 2 Count: 300
This process is currently bound to MIB
Area count: 1 NSSA area count: 1
Normal areas with up interfaces: 0
NSSA areas with up interfaces: 1
Up interfaces: 1
ExChange/Loading neighbors: 0
Full neighbors:3
Calculation trigger type: Full
Current calculation type: SPF calculation
Current calculation phase: Calculation area topology
Process reset state: N/A
Current reset type: N/A
Next reset type: N/A
Reset prepare message replied: -/-/-/-
Reset process message replied: -/-/-/-
Reset phase of module:
M-N/A, P-N/A, L-N/A, C-N/A, R-N/A
Area: 0.0.0.1 (MPLS TE not enabled)
Authtype: None Area flag: NSSA
7/5 translator state: Disabled
7/5 translate stability timer interval: 0
SPF scheduled count: 5
ExChange/Loading neighbors: 0
Up interfaces: 1
Interface: 192.168.1.2 (GigabitEthernet1/0/1)
Cost: 1 State: DR Type: Broadcast MTU: 1500
Priority: 1
Designated router: 192.168.1.2
Backup designated router: 192.168.1.1
Timers: Hello 10 , Dead 40 , Poll 40 , Retransmit 5 , Transmit Delay 1
FRR backup: Enabled
Enabled by network configuration
Table 27 Command output
|
Field |
Description |
|
OSPF Process 1 with Router ID 192.168.1.2 |
OSPF process ID and OSPF router ID. |
|
RouterID |
Router ID. |
|
Router type |
Router type: · ABR. · ASBR. · NSSA. · Null. |
|
Route tag |
Tag of redistributed routes. |
|
Multi-VPN-Instance is not enabled |
The OSPF process does not support multi-VPN-instance. |
|
Ext-community type |
OSPF extended community attribute type codes: · domain ID—Domain ID code. · router type—Router type code. · router ID—Router ID code. |
|
Domain ID |
OSPF domain ID (primary ID). |
|
Opaque capable |
Opaque LSA advertisement and reception capability is enabled. |
|
Originating router-LSAs with maximum metric |
The maximum cost value for router LSAs (excluding stub links) is used. |
|
Condition |
Status of the stub router: · Always. · On startup while BGP is converging. · On startup while BGP is converging for xxx seconds, where xxx is specified by the user. · On startup for xxx seconds, where xxx is specified by the user. |
|
State |
Whether the stub router is active. |
|
SPF-schedule-interval |
Interval for SPF calculations. If the SPF calculation interval is fixed, this field also displays in milliseconds enclosed with brackets. |
|
LSA generation interval |
LSA generation interval. |
|
LSA arrival interval |
LSA arrival interval. |
|
Transmit pacing |
LSU packet transmit rate of the interface: · Interval—LSU transmit interval of the interface. · Count—Maximum number of LSU packets sent at each interval. |
|
Default ASE parameters |
Default ASE parameters: Metric, Tag, and Type. |
|
Route preference |
Internal route preference. |
|
ASE route preference |
External route preference. |
|
SPF calculation count |
SPF calculation count of the OSPF process. |
|
RFC1583 compatible |
Compatible with RFC 1583. |
|
SNMP trap rate limit interval |
SNMP notification sending interval. |
|
Count |
Number of sent SNMP notifications. |
|
ExChange/Loading neighbors |
Neighbors in ExChange/Loading state. |
|
Full neighbors |
Neighbors in Full state. |
|
Calculation trigger type |
Route calculation trigger type: · Full—Calculation of all routes is triggered. · Area topology change—Topology change in an area. · Intra router change—Incremental intra-area route change. · ASBR change—Incremental ASBR route change. · 7to5 translator—Type-7-to-Type-5 LSA translator role change. · Full IP prefix—Calculation of all IP prefixes is triggered. · Full intra AS—Calculation of all intra-AS prefixes is triggered. · Inc intra AS—Calculation of incremental intra-AS prefixes is triggered. · Full inter AS—Calculation of all AS-external prefixes is triggered. · Inc inter AS—Calculation of incremental AS-external prefixes is triggered. · N/A—Route calculation is not triggered. |
|
Current calculation type |
Current route calculation type: · SPF calculation. · Intra router calculation—Intra-area route calculation. · ASBR calculation—Inter-area ASBR route calculation. · Inc intra router—Incremental intra-area route calculation. · Inc ASBR calculation—Incremental inter-area ASBR route calculation. · 7to5 translator—Type-7-to-Type-5 LSA calculation. · Full intra AS—Calculation of all intra-AS prefixes. · Inc intra AS—Calculation of incremental intra-AS prefixes. · Full inter AS—Calculation of all AS-external prefixes. · Inc inter AS—Calculation of incremental AS-external prefixes. · Forward address—Forwarding address calculation. · N/A—Route calculation is not triggered. |
|
Current calculation phase |
Current route calculation phase: · Calculation area topology—Calculating area topology. · Calculation router—Calculating routes on routers. · Calculation intra AS—Calculating intra-AS routes. · 7to5 translator—Calculating Type-7-to-Type-5 LSAs. · Forward address—Calculating forwarding addresses. · Calculation inter AS—Calculating AS-external routes. · Calculation end—Ending phase of calculation. · N/A—Route calculation is not triggered. |
|
Process reset state |
Process reset state: · N/A—The process is not reset. · Under reset—The process is in the reset progress. · Under RIB smooth—The process is synchronizing the RIB. |
|
Current reset type |
Current process reset type: · N/A—The process is not reset. · Normal—Normal reset. · GR quit—Normal reset when GR quits abnormally. · Delete—Delete OSPF process. · VPN delete—Delete VPN. |
|
Next reset type |
Next process reset type: · N/A—The process is not reset. · Normal—Normal reset. · GR quit—Normal reset when GR quits abnormally. · Delete—Delete OSPF process. · VPN delete—Delete VPN. |
|
Reset prepare message replied |
Modules that reply reset prepare messages: · P—Neighbor maintenance module. · L—LSDB synchronization module. · C—Route calculation module. · R—Route redistribution module. |
|
Reset process message replied |
Modules that reply reset process messages: · P—Neighbor maintenance module. · L—LSDB synchronization module. · C—Route calculation module. · R—Route redistribution module. |
|
Reset phase of module |
Reset phase of each module: · Main control module: ¡ N/A—Not reset. ¡ Delete area. ¡ Delete process. · Neighbor maintenance (P) module: ¡ N/A—Not reset. ¡ Delete neighbor. ¡ Delete interface. ¡ Delete vlink—Delete virtual link. ¡ Delete shamlink—Delete sham link. · LSDB synchronization (L) module: ¡ N/A—Not reset. ¡ Stop timer. ¡ Delete ASE—Delete all ASE LSAs. ¡ Delete ASE maps—Delete ASE LSA maps. ¡ Clear process data. ¡ Delete area LSA—Delete LSAs and maps from an area. ¡ Delete area interface—Delete interfaces from an area. ¡ Delete process—Delete process-related resources. ¡ Restart—Restart process-related resources. · Route calculation (C) module: ¡ N/A—Not reset. ¡ Delete topology—Delete area topology. ¡ Delete router—Delete routes of routers. ¡ Delete intra AS—Delete intra-AS routes ¡ Delete inter AS—Delete AS-external routes. ¡ Delete forward address—Delete forwarding address list. ¡ Delete advertise—Delete advertising router list. · Route redistribution (R) module: ¡ N/A—Not reset. ¡ Delete ABR summary—Delete summary routes of the ABR. ¡ Delete ASBR summary—Delete summary routes of the ASBR. ¡ Delete import—Delete redistributed routes. |
|
Area |
Area ID in the IP address format. |
|
Authtype |
Authentication type of the area: · None—No authentication. · Simple—Simple authentication. · MD5—MD5 authentication. |
|
Area flag |
Type of the area: · Normal. · Stub. · StubNoSummary (totally stub area). · NSSA. · NSSANoSummary (totally NSSA area). |
|
7/5 translator state |
State of the translator that translates Type-7 LSAs to Type-5 LSAs: · Enabled—The translator is specified through commands. · Elected—The translator is designated through election. · Disabled—The device is not a translator. |
|
7/5 translate stability timer interval |
Stability interval for Type-7 LSA-to-Type-5 LSA translation. |
|
SPF scheduled Count |
SPF calculation count in the OSPF area. |
|
Interface |
Interface in the area. |
|
Cost |
Interface cost. |
|
State |
Interface state. |
|
Type |
Interface network type. |
|
MTU |
Interface MTU. |
|
Priority |
Router priority. |
|
Timers |
OSPF timers: · Hello—Interval for sending hello packets. · Dead—Interval within which the neighbor is down. · Poll—Interval for sending hello packets. · Retransmit—Interval for retransmitting LSAs. |
|
FRR backup |
Whether Loop Free Alternate (LFA) calculation is enabled on an interface. |
display ospf abr-asbr
Use display ospf abr-asbr to display routes to the ABR or ASBR.
Syntax
display ospf [ process-id ] abr-asbr [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays routes to the ABR and ASBR for all OSPF processes.
verbose: Displays detailed information. If you do not specify this keyword, the command displays brief information.
Usage guidelines
If you use this command on routers in a stub area, the commands displays no ASBR information.
Examples
# Display brief information about routes to the ABR or ASBR.
<Sysname> display ospf abr-asbr
OSPF Process 1 with Router ID 192.168.1.2
Routing Table to ABR and ASBR
Type Destination Area Cost Nexthop RtType
Inter 3.3.3.3 0.0.0.0 3124 10.1.1.2 ASBR
Intra 2.2.2.2 0.0.0.0 1562 10.1.1.2 ABR
# Display detailed information about routes to the ABR or ASBR.
<Sysname> display ospf abr-asbr verbose
OSPF Process 10 with Router ID 101.1.1.11
Routing Table to ABR and ASBR
Destination: 1.1.1.1 RtType : ASBR
Area : 0.0.0.1 Type : Intra
Nexthop : 150.0.1.12 BkNexthop : 0.0.0.0
Interface : GE1/0/1 BkInterface: N/A
Cost : 1000
Table 28 Command output
|
Field |
Description |
|
Type |
Type of the route to the ABR or ASBR: · Intra—Intra-area route. · Inter—Inter-area route. |
|
Destination |
Router ID of an ABR or ASBR. |
|
Area |
ID of the area of the next hop. |
|
Cost |
Cost from the router to the ABR or ASBR. |
|
Nexthop |
Next hop address. |
|
BkNexthop |
Backup next hop address. |
|
RtType |
Router type: ABR or ASBR. |
|
Interface |
Output interface. |
|
BkInterface |
Backup output interface. |
display ospf abr-summary
Use display ospf abr-summary to display ABR summary route information.
Syntax
display ospf [ process-id ] [ area area-id ] abr-summary [ ip-address { mask-length | mask } ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays information about ABR summary routes for all OSPF processes.
area area-id: Specifies an OSPF area by its ID. The area ID is an IP address or a decimal integer in the range of 0 to 4294967295 that is translated into the IP address format. If you do not specify this option, the command displays information about ABR summary routes for all OSPF areas.
ip-address: Specifies a summary route by its IP address.
mask-length: Specifies the mask length in the range of 0 to 32.
mask: Specifies the mask in dotted decimal notation.
verbose: Displays detailed ABR summary route information. If you do not specify this keyword, the command displays brief ABR summary route information.
Usage guidelines
If you do not specify an IP address, this command displays information about all summary routes on the ABR.
Examples
# Display brief information about summary routes on the ABR.
<Sysname> display ospf abr-summary
OSPF Process 1 with Router ID 2.2.2.2
ABR Summary Addresses
Area: 0.0.0.1
Total summary addresses: 1
Net Mask Status Count Cost
100.0.0.0 255.0.0.0 Advertise 1 (Not Configured)
Table 29 Command output
|
Field |
Description |
|
Area |
Area to which the summary routes belong. |
|
Total summary addresses |
Total number of summary routes. |
|
Net |
Address of the summary route. |
|
Mask |
Mask of the summary route address. |
|
Status |
Advertisement status of the summary route: Advertise or Non-Advertise. |
|
Count |
Number of summarized routes. |
|
Cost |
Cost of the summary route. |
# Display detailed information about summary routes on the ABR.
<Sysname> display ospf abr-summary verbose
OSPF Process 1 with Router ID 2.2.2.2
ABR Summary Addresses
Total summary address count: 1
Area: 0.0.0.1
Total summary addresses: 1
Net : 100.0.0.0
Mask : 255.0.0.0
Status : Advertise
Cost : (Not Configured)
Routes count: 1
Destination NetMask Metric
100.1.1.0 255.255.255.0 1000
Table 30 Command output
|
Field |
Description |
|
Destination |
Destination address of a summarized route. |
|
NetMask |
Network mask of a summarized route. |
|
Metric |
Metric of a summarized route. |
display ospf asbr-summary
Use display ospf asbr-summary to display ASBR summary route information.
Syntax
display ospf [ process-id ] asbr-summary [ ip-address { mask-length | mask } ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays information about ASBR summary routes for all OSPF processes.
ip-address: Specifies an IP address in dotted decimal notation.
mask-length: Specifies the mask length in the range of 0 to 32.
mask: Specifies the mask in dotted decimal notation.
Usage guidelines
If you do not specify an IP address, this command displays information about all ASBR summary routes.
Examples
# Display ASBR summary route information in OSPF process 1.
<Sysname> display ospf 1 asbr-summary
OSPF Process 1 with Router ID 2.2.2.2
Summary Addresses
Total Summary Address Count: 1
Summary Address
Net : 30.1.0.0
Mask : 255.255.0.0
Tag : 20
Status : Advertise
Cost : 10 (Configured)
The Count of Route is : 2
Destination Net Mask Proto Process Type Metric
30.1.2.0 255.255.255.0 OSPF 2 2 1
30.1.1.0 255.255.255.0 OSPF 2 2 1
Table 31 Command output
|
Field |
Description |
|
Total Summary Address Count |
Total number of summary routes. |
|
Net |
Address of the summary route. |
|
Mask |
Mask of the summary route address. |
|
Tag |
Tag of the summary route. |
|
Status |
Advertisement status of the summary route. |
|
Cost |
Cost of the summary route. |
|
The Count of Route |
Number of summarized routes. |
|
Destination |
Destination address of a summarized route. |
|
Net Mask |
Network mask of a summarized route. |
|
Proto |
Routing protocol from which the route was redistributed. |
|
Process |
Process ID of the routing protocol from which the route was redistributed. |
|
Type |
Type of a summarized route. |
|
Metric |
Metric of a summarized route. |
display ospf event-log
Use display ospf event-log to display OSPF log information.
Syntax
display ospf [ process-id ] event-log { lsa-flush | peer | spf }
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays OSPF log information for all processes.
lsa-flush: Specifies LSA aging log information.
peer: Specifies neighbor log information.
spf: Specifies route calculation log information.
Usage guidelines
Route calculation logs show the number of routes newly installed in the IP routing table.
Neighbor logs include information about the following events:
· The OSPF neighbor state goes down.
· The OSPF neighbor state goes backward because the local end receives BadLSReq, SeqNumberMismatch, and 1-Way events.
Examples
# Display OSPF LSA aging log information for all processes.
<Sysname> display ospf event-log lsa-flush
OSPF Process 1 with Router ID 1.1.1.1
LSA Flush Log
Date: 2013-09-22 Time: 14:47:33 Received MaxAge LSA from 10.1.1.1
Type: 1 LS ID: 2.2.2.2 AdvRtr: 2.2.2.2 Seq#: 80000001
Date: 2013-09-22 Time: 14:47:33 Flushed MaxAge LSA by the self
Type: 1 LS ID: 1.1.1.1 AdvRtr: 1.1.1.1 Seq#: 80000001
Date: 2013-09-22 Time: 14:47:33 Received MaxAge LSA from 10.1.2.2
Type: 1 LS ID: 2.2.2.2 AdvRtr: 2.2.2.2 Seq#: 80000001
Date: 2013-09-22 Time: 14:47:33 Flushed MaxAge LSA by the self
Type: 1 LS ID: 1.1.1.1 AdvRtr: 1.1.1.1 Seq#: 80000001
Table 32 Command output
|
Field |
Description |
|
Date/Time |
Time when the device receives an LSA that has reached the maximum age. |
|
Received MaxAge LSA from X.X.X.X |
The device received an LSA that has reached the maximum age from X.X.X.X. |
|
Flushed MaxAge LSA by the self |
The device flushed the LSA that has reached the maximum age. |
|
Type |
LSA type. |
|
LS ID |
LSA link state ID. |
|
AdvRtr |
Advertising router. |
|
Seq# |
LSA sequence number. |
# Display OSPF route calculation log information for all processes.
<Sysname> display ospf event-log spf
OSPF Process 1 with Router ID 1.1.1.2
SPF Log
Date Time Duration Intra Inter External Reason
2012-06-27 15:28:26 0.95 1 1 10000 Intra-area LSA
2012-06-27 15:28:23 0.2 0 0 0 Area 0 full neighbor
2012-06-27 15:28:19 0 0 0 0 Intra-area LSA
2012-06-27 15:28:19 0 0 0 0 external LSA
2012-06-27 15:28:19 0.3 0 0 0 Intra-area LSA
2012-06-27 15:28:12 0 1 0 0 Intra-area LSA
2012-06-27 15:28:11 0 0 0 0 Routing policy
2012-06-27 15:28:11 0 0 0 0 Intra-area LSA
Table 33 Command output
|
Field |
Description |
|
Date/Time |
Time when the route calculation starts. |
|
Duration |
Duration of the route calculation, in seconds. |
|
Intra |
Number of intra-area routes newly installed in the IP routing table. |
|
Inter |
Number of inter-area routes newly installed in the IP routing table. |
|
External |
Number of external routes newly installed in the IP routing table. |
|
Reason |
Reasons why the route calculation is performed: · Intra-area LSA—Intra-area LSA changes. · Inter-area LSA—Inter-area LSA changes. · External LSA—External LSA changes. · Configuration—Configuration changes. · Area 0 full neighbor—Number of FULL-state neighbors in Area 0 changes. · Area 0 up interface—Number of interfaces in up state in Area 0 changes. · LSDB overflow state—Overflow status changes. · AS number—AS number changes. · ABR summarization—ABR summarization changes. · GR end—GR ends. · Routing policy—Routing policy changes. · Intra-area tunnel—Intra-area tunnel changes. · Others—Other reasons. |
# Display OSPF neighbor log information for OSPF process 1.
<Sysname> display ospf 1 event-log peer
OSPF Process 1 with Router ID 1.1.1.1
Neighbors Log
Date Time Local Address Remote Address Router ID Reason
2012-12-31 12:35:45 197.168.1.1 197.168.1.2 2.2.2.2 IntPhyChange
2012-12-31 12:35:19 197.168.1.1 197.168.1.2 2.2.2.2 ConfNssaArea
2012-12-31 12:34:59 197.168.1.1 197.168.1.2 2.2.2.2 SilentInt
Table 34 Command output
|
Field |
Description |
|
Date/Time |
Time when the neighbor state changes. |
|
Local Address |
Local address of the neighbor relationship. |
|
Remote Address |
Peer address of the neighbor relationship. |
|
Router ID |
Neighbor router ID. |
|
Reason |
Reasons for neighbor state changes: · ResetConnect—The connection is lost due to insufficient memory. · IntChange—The interface parameter has changed. · VlinkChange—The virtual link parameter has changed. · ShamlinkChange—The sham link parameter has changed. · ResetOspf—The OSPF process is reset. · UndoOspf—The OSPF process is deleted. · UndoArea—The OSPF area is deleted. · UndoNetwork—The interface is disabled. · SilentInt—The interface is configured as a silent interface. · IntLogChange—The logical attribute of the interface has changed. · IntPhyChange—The physical attribute of the interface has changed. · IntVliChange—The virtual link attribute of the interface has changed. · VlinkDown—The virtual link goes down. · ShamlinkDown—The sham link goes down. · DeadExpired—The dead timer expires. · ConfStubArea—The interface is configured with stub area parameters. · ConfNssaArea—The interface is configured with NSSA area parameters. · AuthChange—The authentication type has changed. · OpaqueChange—The Opaque capability has changed. · Retrans—Excessive retransmissions. · LLSChange—The LLS capability has changed. · OOBChange—The OOB capability has changed. · GRChange—The GR capability has changed. · BFDDown—The interface is shut down by BFD. · BadLSReq—The interface receives BadLSReq events. · SeqMismatch—The interface receives SeqNumberMismatch events. · 1-Way—The interface receives 1-Way events. |
Related commands
reset ospf event-log
display ospf fast-reroute lfa-candidate
Use display ospf fast-reroute lfa-candidate to display OSPF FRR backup next hop information.
Syntax
display ospf [ process-id ] [ area area-id ] fast-reroute lfa-candidate
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays FRR backup next hop information for all processes.
area area-id: Specifies an OSPF area by its ID. The area ID is an IP address or a decimal integer in the range of 0 to 4294967295 that is translated into the IP address format. If you do not specify this option, the command displays FRR backup next hop information for all OSPF areas.
Examples
# Display OSPF FRR backup next hop information.
<Sysname> display ospf 1 area 0 fast-reroute lfa-candidate
OSPF Process 1 with Router ID 2.2.2.2
LFA Candidate List
Area: 0.0.0.0
Candidate nexthop count: 2
NextHop IntIP Interface
10.0.1.1 10.0.1.2 GE1/0/2
10.0.11.1 10.0.11.2 GE1/0/3
Table 35 Command output
|
Field |
Description |
|
Area |
Area to which the backup next hops belong. |
|
Candidate nexthop count |
Number of backup next hops. |
|
NextHop |
Backup next hop address. |
|
IntIP |
IP address of the output interface. |
|
Interface |
Output interface. |
display ospf graceful-restart
Use display ospf graceful-restart to display GR information.
Syntax
display ospf [ process-id ] graceful-restart [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays GR information for all processes.
verbose: Displays detailed GR information. If you do not specify this keyword, the command displays brief GR information.
Examples
# Display detailed GR information.
<Sysname> display ospf graceful-restart verbose
OSPF Process 1 with Router ID 1.1.1.1
Graceful Restart information
Graceful Restart capability : Enable(IETF)
Graceful Restart support : Planned and un-planned,Partial
Helper capability : Enable(IETF)
Helper support : Planned and un-planned(IETF),Strict LSA check
Current GR state : Normal
Graceful Restart period : 40 seconds
Number of neighbors under Helper: 0
Number of restarting neighbors : 0
Last exit reason:
Restarter : None
Helper : None
Area: 0.0.0.0
Authtype: None Area flag: Normal
Area up Interface count: 2
Interface: 40.4.0.1 (GigabitEthernet1/0/2))
Restarter state: Normal State: P-2-P Type: PTP
Last exit reason:
Restarter : None
Helper : None
Neighbor count of this interface: 1
Number of neighbors under Helper: 0
Neighbor IP address GR state Last Helper exit reason
3.3.3.3 40.4.0.3 Normal None
Virtual-link Neighbor-ID -> 4.4.4.4, Neighbor-State: Full
Restarter state: Normal
Interface: 20.2.0.1 (Vlink)
Transit Area: 0.0.0.1
Last exit reason:
Restarter : None
Helper : None
Neighbor IP address GR state Last Helper exit reason
4.4.4.4 20.2.0.4 Normal Reset neighbor
Table 36 Command output
|
Field |
Description |
|
OSPF Process 1 with Router ID 1.1.1.1 Graceful Restart information |
GR information for OSPF process 1 with router ID 1.1.1.1. |
|
Graceful Restart capability |
Whether GR is enabled: · Enable(IETF)—IETF GR is enabled. · Enable(Nonstandard)—Non-IETF GR is enabled. · Disable—GR is disabled. |
|
Graceful Restart support |
GR modes that the process supports (displayed only when GR is enabled): · Planned and un-planned—Supports both planned and unplanned GR. · Planned only—Supports only planned GR. · Partial—Supports partial GR. · Global—Supports global GR. |
|
Helper capability |
Helper capability that the process supports: · Enable (IETF)—Supports IETF GR helper capability. · Enable (Nonstandard)—Supports non-IETF GR helper capability. · Enable (IETF and nonstandard)—Supports both IETF GR helper capability and non-IETF GR helper capability. · Disable—Does not support GR helper capability. |
|
Helper support |
Policies that the helper supports (displayed only when GR helper is enabled): · Strict lsa check—The helper supports strict LSA checking. · Planned and un-planned—The helper supports planned and unplanned GR. · Planned only—The helper supports only planned GR. |
|
Current GR state |
GR state: · Normal—GR is not in progress or has completed. · Under GR—GR is in process. · Under Helper—The process is acting as GR helper. |
|
Last exit reason |
Last exit reason: · Restarter—Reason that the restarter exited most recently. · Helper—Reason that the helper exited most recently. |
|
Area |
Area ID in IP address format. |
|
Authtype |
Authentication type of the area: · None—No authentication. · Simple—Simple authentication. · MD5—MD5 authentication. |
|
Area flag |
Type of the area: · Normal. · Stub. · StubNoSummary (totally stub area). · NSSA. · NSSANoSummary (totally NSSA area). |
|
Area up Interface count |
Number of up interfaces in the area. |
|
Interface |
Interface in the area. |
|
Restarter state |
Restarter state on the interface. |
|
State |
Interface state. |
|
Type |
Interface network type. |
|
Neighbor count of this interface |
Neighbors of an interface. |
|
Neighbor |
Neighbor router ID. |
|
IP address |
Neighbor IP address. |
|
GR state |
Neighbor GR state: · Normal—GR is not in progress or has completed. · Under GR—GR is in process. · Under Helper—The process is acting as GR helper. |
|
Last Helper exit reason |
Reason that the helper exited most recently. |
|
Virtual-link Neighbor-ID |
Router ID of the virtual link's neighbor. |
|
Neighbor-State |
Neighbor state: Down, Init, 2-Way, ExStart, Exchange, Loading, and Full. |
|
Interface |
Output interface of the virtual link. |
display ospf hostname-table
Use display ospf hostname-table to display the router ID-to-host name mapping table.
Syntax
display ospf [ process-id ] hostname-table
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify an OSPF process, this command displays the router ID-to-host name mapping tables for all OSPF processes.
Examples
# Display the router ID-to-host name mapping tables for all OSPF processes.
<RouterA> display ospf hostname-table
OSPF Process 1 with Router ID 192.168.56.21
Hostname Table Information
Area: 0.0.0.1
Router ID Hostname
192.168.56.21 RouterA
display ospf interface
Use display ospf interface to display OSPF interface information.
Syntax
display ospf [ process-id ] interface [ interface-type interface-number | verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process ID in the range of 1 to 65535. If you do not specify this argument, the command displays the OSPF interface information for all OSPF processes.
interface-type interface-number: Specifies an interface by its type and number.
verbose: Displays detailed OSPF information for all interfaces.
Usage guidelines
If you do not specify the interface-type interface-number argument or the verbose keyword, this command displays OSPF brief information for all interfaces.
Examples
# Display all OSPF interface brief information.
<Sysname> display ospf interface
OSPF Process 1 with Router ID 192.168.1.1
Interfaces
Area: 0.0.0.0
IP Address Type State Cost Pri DR BDR
192.168.1.1 PTP P-2-P 1562 1 0.0.0.0 0.0.0.0
Area: 0.0.0.1
IP Address Type State Cost Pri DR BDR
172.16.0.1 Broadcast DR 1 1 172.16.0.1 0.0.0.0
Table 37 Command output
|
Field |
Description |
|
Area |
Area ID of the interface. |
|
IP Address |
Interface IP address (regardless of whether TE is enabled or not). |
|
Type |
Interface network type: PTP (P2P), PTMP (P2MP), Broadcast, or NBMA. |
|
State |
Interface state: · DOWN—No protocol traffic can be sent or received on the interface. · Loopback—The interface is in loopback state and it cannot forward traffic. · Waiting—The interface starts sending and receiving Hello packets. The router is trying to determine the identity of the (Backup) designated router for the network. · P-2-P—The interface will send Hello packets at the interval of HelloInterval, and try to establish an adjacency with the neighbor. · DR—The router is the designated router on the network. · BDR—The router is the backup designated router on the network. · DROther—The router is a DR Other router on the attached network. |
|
Cost |
Interface cost. |
|
Pri |
Router priority. |
|
DR |
DR on the interface's network segment. |
|
BDR |
BDR on the interface's network segment. |
# Display detailed information about GigabitEthernet 1/0/1.
<Sysname> display ospf interface gigabitethernet 1/0/1
OSPF Process 1 with Router ID 192.168.1.1
Interfaces
Interface: 172.16.0.1 (GigabitEthernet1/0/1)
Cost: 1 State: DR Type: Broadcast MTU: 1500
Priority: 1
Designated router: 172.16.0.1
Backup designated router: 0.0.0.0
Timers: Hello 10, Dead 40, Poll 40, Retransmit 5, Transmit Delay 1
FRR backup: Enabled
Primary path detection mode: BFD ctrl
Enabled by interface configuration (including secondary IP addresses)
MD5 authentication enabled.
The last key is 3.
The rollover is in progress, 2 neighbor(s) left.
LDP state: No-LDP
LDP sync state: Achieved
Table 38 Command output
|
Field |
Description |
|
Interface |
Information about the interface, such as the IP address. |
|
Timers |
OSPF timers (in seconds): Hello, Dead, Poll, and Retransmit. |
|
Transmit Delay |
LSA transmission delay on the interface, in seconds. |
|
FRR backup |
Whether LFA calculation is enabled on an interface. |
|
Primary path detection mode |
Primary link detection mode: · BFD ctrl—BFD control packet mode. · BFD echo—BFD echo packet mode. |
|
Enabled by interface configuration (including secondary IP addresses) |
OSPF is enabled on the interface (including secondary IP addresses). |
|
MD5 authentication enabled |
Authentication mode. |
|
The last key |
Most recent MD5 authentication key ID. |
|
neighbor(s) |
Number of neighbors that have not completed key rollover. |
|
LDP state |
LDP state: · Init—Initialization state. LDP has not been delivered. · No-LDP—LDP is not configured. · Not ready—LDP sessions have not been established. · Ready—LDP sessions have been established. |
|
LDP sync state |
LDP IGP synchronization state: · Init—Initialization state. · Achieved—LDP has been synchronized. · Max cost—OSPF advertises the maximum cost in LSAs. |
display ospf lsdb
Use display ospf lsdb to display OSPF LSDB information.
Syntax
display ospf [ process-id ] lsdb [ brief | originate-router advertising-router-id | self-originate ] [ age { max-value max-age-value | min-value min-age-value } * ] [ resolve-hostname ]
display ospf [ process-id ] lsdb hostname host-name [ age { max-value max-age-value | min-value min-age-value } * ]
display ospf [ process-id ] lsdb { opaque-as | ase } [ link-state-id ] [ originate-router advertising-router-id | self-originate ] [ age { max-value max-age-value | min-value min-age-value } * ] [ resolve-hostname ]
display ospf [ process-id ] lsdb { opaque-as | ase } [ link-state-id ] hostname host-name [ age { max-value max-age-value | min-value min-age-value } * ]
display ospf [ process-id ] [ area area-id ] lsdb { asbr | network | nssa | opaque-area | opaque-link | router | summary } [ link-state-id ] [ originate-router advertising-router-id | self-originate ] [ age { max-value max-age-value | min-value min-age-value } * ] [ resolve-hostname ]
display ospf [ process-id ] [ area area-id ] lsdb { asbr | network | nssa | opaque-area | opaque-link | router | summary } [ link-state-id ] hostname host-name [ age { max-value max-age-value | min-value min-age-value } * ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays LSDB information for all OSPF processes.
age: Displays LSAs whose ages are in the specified range. If you do not specify this keyword, the command displays all LSAs in the LSDB.
max-value max-age-value: Specifies the maximum age of LSAs, in the range of 0 to 3600 seconds. The default value is 3600.
min-value min-age-value: Specifies the minimum age of LSAs, in the range of 0 to 3600 seconds. The default value is 0. The min-age-value cannot be greater than the max-age-value.
area area-id: Specifies an OSPF area by its ID. The area ID is an IP address or a decimal integer in the range of 0 to 4294967295 that is translated into the IP address format. If you do not specify this option, the command displays LSDB information for all OSPF areas.
brief: Displays brief LSDB information.
asbr: Displays Type-4 LSA (ASBR Summary LSA) information in the LSDB.
ase: Displays Type-5 LSA (AS External LSA) information in the LSDB.
network: Displays Type-2 LSA (Network LSA) information in the LSDB.
nssa: Displays Type-7 LSA (NSSA External LSA) information in the LSDB.
opaque-area: Displays Type-10 LSA (Opaque-area LSA) information in the LSDB.
opaque-as: Displays Type-11 LSA (Opaque-AS LSA) information in the LSDB.
opaque-link: Displays Type-9 LSA (Opaque-link LSA) information in the LSDB.
router: Displays Type-1 LSA (Router LSA) information in the LSDB.
summary: Displays Type-3 LSA (Network Summary LSA) information in the LSDB.
link-state-id: Specifies a link state ID in the IP address format.
originate-router advertising-router-id: Specifies an advertising router by its ID.
self-originate: Displays information about self-originated LSAs.
hostname host-name: Displays LSAs advertised by the router with the specified host name. If you do not specify this option, the command displays all LSAs in the OSPF LSDB.
resolve-hostname: Displays host names in OSPF LSDB information. If you do not specify this keyword, the OSPF LSDB information does not include host names.
Examples
# Display OSPF LSDB information.
<Sysname> display ospf lsdb
OSPF Process 1 with Router ID 192.168.0.1
Link State Database
Area: 0.0.0.0
Type LinkState ID AdvRouter Age Len Sequence Metric
Router 192.168.0.2 192.168.0.2 474 36 80000004 0
Router 192.168.0.1 192.168.0.1 21 36 80000009 0
Network 192.168.0.1 192.168.0.1 321 32 80000003 0
Sum-Net 192.168.1.0 192.168.0.1 321 28 80000002 1
Sum-Net 192.168.2.0 192.168.0.2 474 28 80000002 1
Area: 0.0.0.1
Type LinkState ID AdvRouter Age Len Sequence Metric
Router 192.168.0.1 192.168.0.1 21 36 80000005 0
Sum-Net 192.168.2.0 192.168.0.1 321 28 80000002 2
Sum-Net 192.168.0.0 192.168.0.1 321 28 80000002 1
Type 9 Opaque (Link-Local Scope) Database
Flags: * -Vlink interface LSA
Type LinkState ID AdvRouter Age Len Sequence Interfaces
*Opq-Link 3.0.0.0 7.2.2.1 8 14 80000001 10.1.1.2
*Opq-Link 3.0.0.0 7.2.2.2 8 14 80000001 20.1.1.2
# Display OSPF LSDB information, including the host names of the advertising routers.
<Sysname> display ospf lsdb resolve-hostname
OSPF Process 1 with Router ID 2.2.2.2
Link State Database
Area: 0.0.0.0
Type LinkState ID AdvRouter Age Len Sequence Metric
Router 1.1.1.1 1.1.1.1 1419 36 80000004 0
Router 2.2.2.2 RouterB 1420 36 80000004 0
Network 192.168.12.2 RouterB 1420 32 80000001 0
Sum-Net 192.168.13.0 1.1.1.1 1456 28 80000001 1
Area: 0.0.0.1
Type LinkState ID AdvRouter Age Len Sequence Metric
Router 3.3.3.3 3.3.3.3 1416 36 80000003 0
Router 1.1.1.1 1.1.1.1 1415 36 80000003 0
Network 192.168.13.2 3.3.3.3 1416 32 80000001 0
Sum-Net 192.168.12.0 1.1.1.1 1456 28 80000001 1
Type 10 Opaque (Area-Local Scope) Database
Type LinkState ID AdvRouter Age Len Sequence Area
Opq-Area 4.0.0.0 RouterB 470 32 80000001 0.0.0.0
Table 39 Command output
|
Field |
Description |
|
Area |
LSDB information for the area. |
|
Type |
LSA type. |
|
LinkState ID |
Link state ID. |
|
AdvRouter |
Advertising router. |
|
Age |
Age of the LSA. |
|
Len |
Length of the LSA. |
|
Sequence |
Sequence number of the LSA. |
|
Metric |
Cost of the LSA. |
|
*Opq-Link |
Opaque LSA generated by a virtual link. |
|
Opq-Area |
Received Type-10 LSA. |
# Display Type-2 LSA (Network LSA) information in the LSDB.
<Sysname> display ospf 1 lsdb network
OSPF Process 1 with Router ID 192.168.1.1
Area: 0.0.0.0
Link State Database
Type : Network
LS ID : 192.168.0.2
Adv Rtr : 192.168.2.1
LS Age : 922
Len : 32
Options : E
Seq# : 80000003
Checksum : 0x8d1b
Net Mask : 255.255.255.0
Attached Router 192.168.1.1
Attached Router 192.168.2.1
Area: 0.0.0.1
Link State Database
Type : Network
LS ID : 192.168.1.2
Adv Rtr : 192.168.1.2
LS Age : 782
Len : 32
Options : NP
Seq# : 80000003
Checksum : 0x2a77
Net Mask : 255.255.255.0
Attached Router 192.168.1.1
Attached Router 192.168.1.2
# Display Type-2 LSA (Network LSA) information in the LSDB, including the host names of the advertising routers.
<Sysname> display ospf 1 lsdb network resolve-hostname
OSPF Process 1 with Router ID 2.2.2.2
Area: 0.0.0.0
Link State Database
Type : Network
LS ID : 192.168.12.2
Adv Rtr : 2.2.2.2
Hostname : RouterB
LS age : 1552
Len : 32
Options : O E
Seq# : 80000001
Checksum : 0xbdd0
Net mask : 255.255.255.0
Attached router 1.1.1.1
Attached router 2.2.2.2
Area: 0.0.0.1
Link State Database
Type : Network
LS ID : 192.168.13.2
Adv Rtr : 3.3.3.3
LS age : 1548
Len : 32
Options : O E
Seq# : 80000001
Checksum : 0xc6be
Net mask : 255.255.255.0
Attached router 1.1.1.1
Attached router 3.3.3.3
Table 40 Command output
|
Field |
Description |
|
Type |
LSA type. |
|
LS ID |
DR IP address. |
|
Adv Rtr |
Router that advertised the LSA. |
|
Hostname |
Host name of the advertising router. |
|
LS Age |
LSA age time. |
|
Len |
LSA length. |
|
Options |
LSA options: · O—Opaque LSA advertisement capability. · E—AS External LSA reception capability. · EA—External extended LSA reception capability. · DC—On-demand link support. · N—NSSA external LSA support. · P—Capability of an NSSA ABR to translate Type-7 LSAs into Type-5 LSAs. |
|
Seq# |
LSA sequence number. |
|
Checksum |
LSA checksum. |
|
Net Mask |
Network mask. |
|
Attached Router |
ID of the router that established adjacency with the DR, and ID of the DR itself. |
display ospf nexthop
Use display ospf nexthop to display OSPF next hop information.
Syntax
display ospf [ process-id ] nexthop
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays next hop information for all OSPF processes.
Examples
# Display OSPF next hop information.
<Sysname> display ospf nexthop
OSPF Process 1 with Router ID 1.1.1.2
Neighbor Nexthop Information
NbrID Nexthop Interface RefCount Status
192.168.12.1 0.0.0.0 GE1/0/2 4 Valid
192.168.12.2 192.168.12.2 GE1/0/2 3 Valid
192.168.12.1 0.0.0.0 Loop100 1 Valid
Table 41 Command output
|
Field |
Description |
|
NbrID |
Neighbor router ID. |
|
Nexthop |
Next hop address. |
|
Interface |
Output interface. |
|
RefCount |
Reference count (routes that use the next hop). |
|
Status |
Next hop status: valid or invalid. |
display ospf non-stop-routing status
Use display ospf non-stop-routing status to display OSPF NSR information.
Syntax
display ospf [ process-id ] non-stop-routing status
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays OSPF NSR information for all OSPF processes.
Usage guidelines
The following matrix shows the command and hardware compatibility:
|
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28/3600-51 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
· In standalone mode: No · In IRF mode: Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Command compatibility |
|
MSR810-LM-GL |
No |
|
MSR810-W-LM-GL |
No |
|
MSR830-6EI-GL |
No |
|
MSR830-10EI-GL |
No |
|
MSR830-6HI-GL |
No |
|
MSR830-10HI-GL |
No |
|
MSR2600-6-X1-GL |
No |
|
MSR3600-28-SI-GL |
No |
Examples
# Display OSPF NSR information.
<Sysname> display ospf non-stop-routing status
OSPF Process 1 with Router ID 192.168.33.12
Non Stop Routing information
-----------------------------------------
Non Stop Routing capability : Enabled
Upgrade phase : Normal
Table 42 Command output
|
Field |
Description |
|
Non Stop Routing capability |
NSR status: enabled or disabled. |
|
Upgrade phase |
Upgrade phase: · Prepare—Upgrade preparation phase. · Restore Smooth—Upgrade phase. · Preroute—Route pre-calculation phase. · Calculating—Route calculation phase. · Redisting—Route redistribution phase. · Original and age—LSA generation and aging phase. · Normal—Normal status. |
display ospf peer
Use display ospf peer to display information about OSPF neighbors.
Syntax
display ospf [ process-id ] peer [ verbose ] [ interface-type interface-number ] [ neighbor-id ] [ resolve-hostname ] | hostname host-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by ID in the range of 1 to 65535. If you do not specify this argument, the command displays OSPF neighbor information for all OSPF processes.
verbose: Displays detailed neighbor information. If you do not specify this keyword, the command displays brief OSPF neighbor information.
interface-type interface-number: Specifies an interface by its type and number. If you do not specify this argument, the command displays neighbor information for all interfaces.
neighbor-id: Specifies a neighbor router ID. If you do not specify this argument, the command displays all neighbor information.
resolve-hostname: Resolves the host names of the neighbor routers. If you do not specify this keyword, the command does not resolve the host names of the neighbor routers.
hostname host-name: Specifies a neighbor router by its host name, a case-sensitive string of 1 to 255 characters. If you do not specify this option, the command displays information for all neighbors.
Examples
# Display detailed OSPF neighbor information.
<Sysname> display ospf peer verbose
OSPF Process 1 with Router ID 1.1.1.1
Neighbors
Area 0.0.0.0 interface 1.1.1.1(GigabitEthernet1/0/1)'s neighbors
Router ID: 1.1.1.2 Address: 1.1.1.2 GR state: Normal
State: Full Mode: Nbr is master Priority: 1
DR: 1.1.1.2 BDR: 1.1.1.1 MTU: 0
Options is 0x02 (-|-|-|-|-|-|E|-)
Dead timer due in 33 sec
Neighbor is up for 02:03:35
Authentication Sequence: [ 0 ]
Neighbor state change count: 6
BFD status: Disabled
Last Neighbor Down Event:
Router ID: 22.22.22.22
Local Address: 11.11.11.11
Remote Address: 22.22.22.22
Time: Apr 9 03:18:19 2014
Reason: Ospf_ifachange
# Display detailed OSPF neighbor information and resolve the host names of the neighbor routers.
<Sysname> display ospf peer verbose resolve-hostname
Area 0.0.0.1 interface 1.1.1.2(GigabitEthernet1/0/1)'s neighbors
Router ID: 3.3.3.3 Address: 13.1.1.2 GR state: Normal
Hostname: RouterA
State: Full Mode: Nbr is slave Priority: 1
DR: 13.1.1.2 BDR: 13.1.1.1 MTU: 0
Options is 0x42 (-|O|-|-|-|-|E|-)
Dead timer due in 31 sec
Neighbor is up for 00:04:42
Authentication sequence: [ 0 ]
Neighbor state change count: 5
BFD status: Disabled
Last Neighbor Down Event:
Router ID: 3.3.3.3
Local Address: 13.1.1.1
Remote Address: 13.1.1.2
Time: Jun 15 16:13:29 2016
Reason: Reset ospf command was performed
Table 43 Command output
|
Field |
Description |
|
Area areaID interface IPAddress(InterfaceName)'s neighbors |
Neighbor information for the interface in the specified area: · areaID—Area to which the neighbor belongs. · IPAddress—Interface IP address. · InterfaceName—Interface name. |
|
Router ID |
Neighbor router ID. |
|
Address |
Neighbor router address. |
|
GR State |
GR state: · Normal. · Restarter. · Complete. · Helper. |
|
Hostname |
Host name of the neighbor router. |
|
State |
Neighbor state: · Down—Initial state of a neighbor conversation. · Init—The router has received a Hello packet from the neighbor. However, the router has not established bidirectional communication with the neighbor. The router did not appear in the neighbor's hello packet. · Attempt—Available only in an NBMA network. In this state, the OSPF router has not received any information from a neighbor for a period. The router can send Hello packets at a longer interval to keep the neighbor relationship. · 2-Way—Communication between the two routers is bidirectional. The local router appears in the neighbor's Hello packet. · Exstart—The goal of this state is to decide which router is the master, and to decide upon the initial Database Description (DD) sequence number. · Exchange—The router is sending DD packets to the neighbor, describing its entire link-state database. · Loading—The router sends LSRs packets to the neighbor, requesting more recent LSAs. · Full—The neighboring routers are fully adjacent. |
|
Mode |
Neighbor mode for LSDB synchronization. |
|
Priority |
Neighboring router priority. |
|
DR |
DR on the interface's network segment. |
|
BDR |
BDR on the interface's network segment. |
|
MTU |
Interface MTU. |
|
Options |
LSA options: · O—Opaque LSA advertisement capability. · E—AS External LSA reception capability. · EA—External extended LSA reception capability. · DC—On-demand link support. · N—NSSA external LSA support. · P—Capability of an NSSA ABR to translate Type-7 LSAs into Type-5 LSAs. |
|
Dead timer due in 33 sec |
This dead timer will expire in 33 seconds. |
|
Neighbor is up for 02:03:35 |
The neighbor has been up for 02:03:35. |
|
Authentication Sequence |
Authentication sequence number. |
|
Neighbor state change count |
Count of neighbor state changes. |
|
BFD status |
BFD status: · Disabled. · Enabled (Control mode). · Enabled (Echo mode). |
|
Last Neighbor Down Event |
The most recent neighbor down event. |
|
Time |
Time when the neighbor went down. |
|
Reason |
Reason for the neighbor down event. |
# Display brief OSPF neighbor information.
<Sysname> display ospf peer
OSPF Process 1 with Router ID 1.1.1.1
Neighbor Brief Information
Area: 0.0.0.0
Router ID Address Pri Dead-Time State Interface
1.1.1.2 1.1.1.2 1 40 Full/DR GE1/0/1
Sham link: 11.11.11.11 -> 22.22.22.22
Router ID Address Pri Dead-Time State
22.22.22.22 22.22.22.22 1 36 Full
# Display brief OSPF neighbor information and resolve the host names of the neighbor routers.
<Sysname> display ospf peer resolve-hostname
OSPF Process 1 with Router ID 1.1.1.1
Neighbor Brief Information
Area: 0.0.0.0
Router ID Address Pri Dead-Time State Interface
RouterA 1.1.1.2 1 34 Full/DR GE1/0/1
Sham link: 11.11.11.11 -> 22.22.22.22
Router ID Address Pri Dead-Time State
22.22.22.22 22.22.22.22 1 36 Full
Table 44 Command output
|
Field |
Description |
|
Area |
Neighbor area. |
|
Router ID |
ID or host name of the neighbor router. |
|
Address |
Neighbor interface address. |
|
Pri |
Neighboring router priority. |
|
Dead-Time |
Dead interval remained. |
|
Interface |
Interface connected to the neighbor. |
|
State |
Neighbor state: Down, Init, Attempt, 2-Way, Exstart, Exchange, Loading, or Full. |
|
Sham link 11.11.11.11 -> 22.22.22.22 |
Sham link from 11.11.11.11 to 22.22.22.22. |
display ospf peer statistics
Use display ospf peer statistics to display OSPF neighbor statistics.
Syntax
display ospf [ process-id ] peer statistics
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays OSPF neighbor statistics for all OSPF processes.
Examples
# Display OSPF neighbor statistics.
<Sysname> display ospf peer statistics
OSPF Process 1 with Router ID 10.3.1.1
Neighbor Statistics
Area ID Down Attempt Init 2-Way ExStart Exchange Loading Full Total
0.0.0.0 0 0 0 0 0 0 0 1 1
0.0.0.2 0 0 0 0 0 0 0 1 1
Total 0 0 0 0 0 0 0 2 2
Sham links' neighbors (Total: 1):
Down: 0, Init: 0, 2-Way: 0, ExStart: 0, Exchange: 0, Loading: 0, Full: 1
Table 45 Command output
|
Field |
Description |
|
Area ID |
The state statistics for all the routers in the area to which the router belongs is displayed. |
|
Down |
Number of neighboring routers in Down state in the same area. |
|
Attempt |
Number of neighboring routers in Attempt state in the same area. |
|
Init |
Number of neighboring routers in Init state in the same area. |
|
2-Way |
Number of neighboring routers in 2-Way state in the same area. |
|
ExStart |
Number of neighboring routers in ExStart state in the same area. |
|
Exchange |
Number of neighboring routers in Exchange state in the same area. |
|
Loading |
Number of neighboring routers in Loading state in the same area. |
|
Full |
Number of neighboring routers in Full state in the same area. |
|
Total |
Total number of neighbors in the same state: Down, Attempt, Init, 2-Way, ExStart, Exchange, Loading, or Full. |
|
Sham links' neighbors |
Statistics about sham links' neighbors. |
display ospf request-queue
Use display ospf request-queue to display OSPF request queue information.
Syntax
display ospf [ process-id ] request-queue [ interface-type interface-number ] [ neighbor-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays the OSPF request queue information for all OSPF processes.
interface-type interface-number: Specifies an interface by its type and number. If you do not specify this argument, the command displays the OSPF request queue information for all interfaces.
neighbor-id: Specifies a neighbor's router ID. If you do not specify this argument, the command displays the OSPF request queue information for all OSPF neighbors.
Examples
# Display OSPF request queue information.
<Sysname> display ospf request-queue
OSPF Process 100 with Router ID 192.168.1.59
Link State Request List
The Router's Neighbor is Router ID 2.2.2.2 Address 10.1.1.2
Interface 10.1.1.1 Area 0.0.0.0
Request list:
Type LinkState ID AdvRouter Sequence Age
Router 2.2.2.2 1.1.1.1 80000004 1
Network 192.168.0.1 1.1.1.1 80000003 1
Sum-Net 192.168.1.0 1.1.1.1 80000002 2
Table 46 Command output
|
Field |
Description |
|
The Router's Neighbor is Router ID |
Neighbor router ID. |
|
Address |
Neighbor interface IP address. |
|
Interface |
Local interface IP address. |
|
Area |
Area ID. |
|
Request list |
Request list information. |
|
Type |
LSA type. |
|
LinkState ID |
Link state ID. |
|
AdvRouter |
Advertising router. |
|
Sequence |
LSA sequence number. |
|
Age |
LSA age. |
display ospf retrans-queue
Use display ospf retrans-queue to display retransmission queue information.
Syntax
display ospf [ process-id ] retrans-queue [ interface-type interface-number ] [ neighbor-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays retransmission queue information for all OSPF processes.
interface-type interface-number: Specifies an interface by its type and number. If you do not specify this argument, the command displays retransmission queue information for all interfaces.
neighbor-id: Specifies a neighbor's router ID. If you do not specify this argument, the command displays retransmission queue information for all neighbors.
Examples
# Display OSPF retransmission queue information.
<Sysname> display ospf retrans-queue
OSPF Process 100 with Router ID 192.168.1.59
Link State Retransmission List
The Router's Neighbor is Router ID 2.2.2.2 Address 10.1.1.2
Interface 10.1.1.1 Area 0.0.0.0
Retransmit list:
Type LinkState ID AdvRouter Sequence Age
Router 2.2.2.2 2.2.2.2 80000004 1
Network 12.18.0.1 2.2.2.2 80000003 1
Sum-Net 12.18.1.0 2.2.2.2 80000002 2
Table 47 Command output
|
Field |
Description |
|
The Router's Neighbor is Router ID |
Neighbor router ID. |
|
Address |
Neighbor interface IP address. |
|
Interface |
Interface address of the router. |
|
Area |
Area ID. |
|
Retrans List |
Retransmission list. |
|
Type |
LSA type. |
|
LinkState ID |
Link state ID. |
|
AdvRouter |
Advertising router. |
|
Sequence |
LSA sequence number. |
|
Age |
LSA age. |
display ospf routing
Use display ospf routing to display OSPF routing information.
Syntax
display ospf [ process-id ] routing [ ip-address { mask-length | mask } ] [ interface interface-type interface-number ] [ nexthop nexthop-address ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays the routing information for all OSPF processes.
ip-address: Specifies a destination IP address.
mask-length: Specifies mask length in the range of 0 to 32.
mask: Specifies the mask in dotted decimal notation.
interface interface-type interface-number: Displays routes passing the specified output interface. If you do not specify this option, the command displays OSPF routing information for all interfaces.
nexthop nexthop-address: Displays routes passing the specified next hop. If you do not specify this option, the command displays all OSPF routing information.
verbose: Displays detailed OSPF routing information. If you do not specify this keyword, the command displays brief OSPF routing information.
Examples
# Display OSPF routing information.
<Sysname> display ospf routing
OSPF Process 1 with Router ID 192.168.1.2
Routing Table
Routing for network
Destination Cost Type NextHop AdvRouter Area
192.168.1.0/24 1562 Stub 192.168.1.2 192.168.1.2 0.0.0.0
172.16.0.0/16 1563 Inter 192.168.1.1 192.168.1.1 0.0.0.0
Total nets: 2
Intra area: 1 Inter area: 1 ASE: 0 NSSA: 0
Table 48 Command output
|
Field |
Description |
|
Destination |
Destination network. |
|
Cost |
Cost to destination. |
|
Type |
Route type: intra-area, transit, stub, inter-area, Type-1 external, and Type-2 external. |
|
NextHop |
Next hop address. |
|
AdvRouter |
Advertising router. |
|
Area |
Area ID. |
|
Total nets |
Total networks. |
|
Intra area |
Total intra-area routes. |
|
Inter area |
Total inter-area routes. |
|
ASE |
Total ASE routes. |
|
NSSA |
Total NSSA routes. |
# Display detailed OSPF routing information.
<Sysname> display ospf routing verbose
OSPF Process 2 with Router ID 192.168.1.112
Routing Table
Routing for network
Destination: 192.168.1.0/24
Priority: Low Type: Stub
AdvRouter: 192.168.1.2 Area: 0.0.0.0
SubProtoID: 0x1 Preference: 10
NextHop: 192.168.1.2 BkNextHop: N/A
IfType: Broadcast BkIfType: N/A
Interface: GE1/0/2 BkInterface: N/A
NibID: 0x1300000c Status: Normal
Cost: 1562
Destination: 172.16.0.0/16
Priority: Low Type: Inter
AdvRouter: 192.168.1.1 Area: 0.0.0.0
SubProtoID: 0x1 Preference: 10
NextHop: 192.168.1.1 BkNextHop: N/A
IfType: Broadcast BkIfType: N/A
Interface: GE1/0/3 BkInterface: N/A
NibID: 0x1300000c Status: Normal
Cost: 1563 SpfCost: 65535
Total nets: 2
Intra area: 2 Inter area: 0 ASE: 0 NSSA: 0
Table 49 Command output
|
Field |
Description |
|
Priority |
Prefix priority: critical, high, medium, and low. |
|
Type |
Route type: intra-area, transit, stub, inter-area, Type-1 external, and Type-2 external. |
|
AdvRouter |
Advertising router. |
|
Area |
Area ID. |
|
SubProtoID |
Sub protocol ID. |
|
Preference |
OSPF route preference. |
|
NextHop |
Primary next hop IP address. |
|
BkNextHop |
Backup next hop IP address. |
|
IfType |
Type of the network to which the primary next hop belongs. |
|
BkIfType |
Type of the network to which the backup next hop belongs. |
|
Interface |
Output interface. |
|
BkInterface |
Backup output interface. |
|
NibID |
Next hop ID. |
|
Status |
Route status: · Local—The route is on the local end and is not sent to the route management module. · Invalid—The next hop is invalid. · Stale—The next hop is stale. · Normal—The route is available. · Delete—The route is deleted. · Host-Adv—The route is a host route. · Rely—The route is a recursive route. |
|
Cost |
Cost to destination. |
|
SpfCost |
SPF cost. |
display ospf spf-tree
Use display ospf spf-tree to display OSPF topology information.
Syntax
display ospf [ process-id ] [ area area-id ] spf-tree [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays topology information for all OSPF processes.
area area-id: Specifies an OSPF area by its ID. The area ID is an IP address or a decimal integer in the range of 0 to 4294967295 that is translated into the IP address format. If you do not specify this option, the command displays topology information for all OSPF areas.
verbose: Displays detailed OSPF topology information. If you do not specify this keyword, the command displays brief OSPF topology information.
Examples
# Display brief topology information for Area 0 in OSPF process 1.
<Sysname> display ospf 1 area 0 spf-tree
OSPF Process 1 with Router ID 100.0.0.4
Flags: S-Node is on SPF tree R-Node is directly reachable
I-Node or Link is init D-Node or Link is to be deleted
P-Neighbor is parent A-Node is in candidate list
C-Neighbor is child T-Node is tunnel destination
H-Nexthop changed N-Link is a new path
V-Link is involved G-Link is in change list
Area: 0.0.0.0 Shortest Path Tree
SpfNode Type Flag SpfLink Type Cost Flag
>1.1.1.1 Router S
-->12.1.1.2 RT2NET 1 C
>2.2.2.2 Router S
-->12.1.1.2 RT2NET 1 P
-->3.3.3.3 RT2RT 1 C
>3.3.3.3 Router S
-->2.2.2.2 RT2RT 1 P
>12.1.1.2 Network S R
-->1.1.1.1 NET2RT 0 P
-->2.2.2.2 NET2RT 0 C
Table 50 Command output
|
Field |
Description |
|
SpfNode |
SPF node, represented by a router ID when the node type is Router, or the IP address of the DR when the node type is Network. Node flag: · I—The node is in initialization state. · A—The node is on the candidate list. · S—The node is on the SPF tree. · R—The node is directly connected to the root node. · D—The node is to be deleted. · T—The node is the tunnel destination. |
|
SpfLink |
SPF link, representing the peer node. Link type: · RT2RT—Router to router. · NET2RT—Network to router. · RT2NET—Router to network. Link flag: · I—The link is in initialization state. · P—The peer is the parent node. · C—The peer is the child node. · D—The link is to be deleted. · H—The next hop is changed. · V—When the peer node is deleted or added, the peer node is not on the SPF tree or is deleted. · N—The link is newly added, and both end nodes are on the SPF tree. · G—The link is on the area change list. |
# Display detailed topology information for Area 0 in OSPF process 1.
<Sysname> display ospf 1 area 0 spf-tree verbose
OSPF Process 1 with Router ID 100.0.0.4
Flags: S-Node is on SPF tree R-Node is directly reachable
I-Node or Link is init D-Node or Link is to be deleted
P-Neighbor is parent A-Node is in candidate list
C-Neighbor is child T-Node is tunnel destination
H-Nexthop changed N-Link is a new path
V-Link is involved G-Link is in change list
Area: 0.0.0.0 Shortest Path Tree
>LsId(192.168.119.130)
AdvId : 100.0.0.4 NodeType : Network
Mask : 255.255.255.0 SPFLinkCnt : 2
Distance : 10
VlinkData: 0.0.0.0 ParentLinkCnt: 1 NodeFlag: S R
NextHop : 1
192.168.119.130 Interface: GE1/0/2
BkNextHop: 1
0.0.0.0 Interface: GE1/0/2
-->LinkId(114.114.114.111)
AdvId : 100.0.0.4 LinkType : NET2RT
LsId : 192.168.119.130 LinkCost : 0 NextHopCnt: 1
LinkData: 0.0.0.0 LinkNewCost: 0 LinkFlag : C
-->LinkId(100.0.0.4)
AdvId : 100.0.0.4 LinkType : NET2RT
LsId : 192.168.119.130 LinkCost : 0 NextHopCnt: 1
LinkData: 0.0.0.0 LinkNewCost: 0 LinkFlag : P
Table 51 Command output
|
Field |
Description |
|
LsId |
Link state ID. |
|
AdvId |
ID of the advertising router. |
|
NodeType |
Node type: · Network—Network node. · Router—Router node. |
|
Mask |
Network mask. Its value is 0 for a router node. |
|
SPFLinkCnt |
Number of SPF links. |
|
Distance |
Cost to the root node. |
|
VlinkData |
Destination address of virtual link packets. |
|
ParentLinkCnt |
Number of parent links. |
|
NodeFlag |
Node flag: · I—The node is in initialization state. · A—The node is on the candidate list. · S—The node is on the SPF tree. · R—The node is directly connected to the root node. · D—The node is to be deleted. · T—The node is the tunnel destination. |
|
NextHop |
Next hop. |
|
Interface |
Output interface. |
|
BkNextHop |
Backup next hop. |
|
LinkId |
Link ID. |
|
LinkType |
Link type: · RT2RT—Router to router. · NET2RT—Network to router. · RT2NET—Router to network. |
|
LinkCost |
Link cost. |
|
NextHopCnt |
Number of next hops. |
|
LinkData |
Link data. |
|
LinkNewCost |
New link cost. |
|
LinkFlag |
Link flag: · I—The link is in initialization state. · P—The peer is the parent node. · C—The peer is the child node. · D—The link is to be deleted. · H—The next hop is changed. · V—When the peer node is deleted or added, the peer node is not on the SPF tree or is deleted. · N—The link is newly added, and both end nodes are on the SPF tree. · G—The link is on the area change list. |
display ospf statistics
Use display ospf statistics to display OSPF statistics.
Syntax
display ospf [ process-id ] statistics [ error | packet [ interface-type interface-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays OSPF statistics for all OSPF processes.
error: Displays error statistics. If you do not specify this keyword, the command displays OSPF packet, LSA, and route statistics.
packet: Displays OSPF packet statistics.
interface-type interface-number: Specifies an interface by its type and number. If you do not specify this argument, the command displays statistics for all interfaces.
Examples
# Display OSPF statistics.
<Sysname> display ospf statistics
OSPF Process 1 with Router ID 2.2.2.2
Statistics
I/O statistics
Type Input Output
Hello 61 122
DB Description 2 3
Link-State Req 1 1
Link-State Update 3 3
Link-State Ack 3 2
LSAs originated by this router
Router : 4
Network : 0
Sum-Net : 0
Sum-Asbr: 0
External: 0
NSSA : 0
Opq-Link: 0
Opq-Area: 0
Opq-As : 0
LSAs originated: 4 LSAs received: 7
Routing table:
Intra area: 2 Inter area: 3 ASE/NSSA: 0
Table 52 Command output
|
Field |
Description |
|
I/O statistics |
Statistics about input/output packets and LSAs. |
|
Type |
OSPF packet type. |
|
Input |
Packets received. |
|
Output |
Packets sent. |
|
Hello |
Hell packet. |
|
DB Description |
Database Description packet. |
|
Link-State Req |
Link-State Request packet. |
|
Link-State Update |
Link-State Update packet. |
|
Link-State Ack |
Link-State Acknowledge packet. |
|
LSAs originated by this router |
LSAs originated by this router. |
|
Router |
Number of Type-1 LSAs originated. |
|
Network |
Number of Type-2 LSAs originated. |
|
Sum-Net |
Number of Type-3 LSAs originated. |
|
Sum-Asbr |
Number of Type-4 LSAs originated. |
|
External |
Number of Type-5 LSAs originated. |
|
NSSA |
Number of Type-7 LSAs originated. |
|
Opq-Link |
Number of Type-9 LSAs originated. |
|
Opq-Area |
Number of Type-10 LSAs originated. |
|
Opq-As |
Number of Type-11 LSAs originated. |
|
LSA originated |
Number of LSAs originated. |
|
LSA received |
Number of LSAs received. |
|
Routing table |
Routing table information. |
|
Intra area |
Number of intra-area routes. |
|
Inter area |
Number of inter-area routes. |
|
ASE |
Number of ASE routes. |
# Display OSPF error statistics.
<Sysname> display ospf statistics error
OSPF Process 1 with Router ID 192.168.1.112
OSPF Packet Error Statistics
0 : Router ID confusion 0 : Bad packet
0 : Bad version 0 : Bad checksum
0 : Bad area ID 0 : Drop on unnumbered link
0 : Bad virtual link 0 : Bad authentication type
0 : Bad authentication key 0 : Packet too small
0 : Neighbor state low 0 : Transmit error
0 : Interface down 0 : Unknown neighbor
0 : HELLO: Netmask mismatch 0 : HELLO: Hello-time mismatch
0 : HELLO: Dead-time mismatch 0 : HELLO: Ebit option mismatch
0 : DD: MTU option mismatch 0 : DD: Unknown LSA type
0 : DD: Ebit option mismatch 0 : ACK: Bad ack
0 : ACK: Unknown LSA type 0 : REQ: Empty request
0 : REQ: Bad request 0 : UPD: LSA checksum bad
0 : UPD: Unknown LSA type 0 : UPD: Less recent LSA
Table 53 Command output
|
Field |
Description |
|
Router ID confusion |
Packets with duplicate router ID. |
|
Bad packet |
Packets illegal. |
|
Bad version |
Packets with wrong version. |
|
Bad checksum |
Packets with wrong checksum. |
|
Bad area ID |
Packets with invalid area ID. |
|
Drop on unnumbered link |
Packets dropped on the unnumbered interface. |
|
Bad virtual link |
Packets on wrong virtual links. |
|
Bad authentication type |
Packets with invalid authentication type. |
|
Bad authentication key |
Packets with invalid authentication key. |
|
Packet too small |
Packets too small in length. |
|
Neighbor state low |
Packets received in low neighbor state. |
|
Transmit error |
Packets with error when being transmitted. |
|
Interface down |
Shutdown times of the interface. |
|
Unknown neighbor |
Packets received from unknown neighbors. |
|
HELLO: Netmask mismatch |
Hello packets with mismatched mask. |
|
HELLO: Hello-time mismatch |
Hello packets with mismatched hello timer. |
|
HELLO: Dead-time mismatch |
Hello packets with mismatched dead timer. |
|
HELLO: Ebit option mismatch |
Hello packets with mismatched E-bit in the option field. |
|
DD: MTU option mismatch |
DD packets with mismatched MTU. |
|
DD: Unknown LSA type |
DD packets with unknown LSA type. |
|
DD: Ebit option mismatch |
DD packets with mismatched E-bit in the option field. |
|
ACK: Bad ack |
Bad LSAck packets for LSU packets. |
|
ACK: Unknown LSA type |
LSAck packets with unknown LSA type. |
|
REQ: Empty request |
LSR packets with no request information. |
|
REQ: Bad request |
Bad LSR packets. |
|
UPD: LSA checksum bad |
LSU packets with wrong LSA checksum. |
|
UPD: Unknown LSA type |
LSU packets with unknown LSA type. |
|
UPD: Less recent LSA |
LSU packets without the most recent LSA. |
# Display OSPF packet statistics for all processes and interfaces.
<Sysname> display ospf statistics packet
OSPF Process 100 with Router ID 192.168.1.59
Packet Statistics
Waiting to send packet count: 0
Hello DD LSR LSU ACK Total
Input : 489 6 2 44 40 581
Output: 492 8 2 45 40 587
Area: 0.0.0.1
Interface: 20.1.1.1 (GigabitEthernet1/0/1)
DD LSR LSU ACK Total
Input : 0 0 0 0 0
Output: 0 0 0 0 0
Interface: 100.1.1.1 (GigabitEthernet1/0/9)
DD LSR LSU ACK Total
Input : 3 1 22 16 42
Output: 2 1 19 20 42
Table 54 Command output
|
Field |
Description |
|
Waiting to send packet count |
Number of packets waiting to be sent. |
|
Total |
Total number of packets. |
|
Input |
Number of received packets. |
|
Output |
Number of sent packets. |
|
Area |
Area ID. |
|
Interface |
Interface address and interface name. |
Related commands
reset ospf statistics
display ospf vlink
Use display ospf vlink to display OSPF virtual link information.
Syntax
display ospf [ process-id ] vlink
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays the OSPF virtual link information for all OSPF processes.
Examples
# Display OSPF virtual link information.
<Sysname> display ospf vlink
OSPF Process 1 with Router ID 3.3.3.3
Virtual Links
Virtual-link Neighbor-ID -> 2.2.2.2, Neighbor-State: Full
Interface: 10.1.2.1 (GigabitEthernet1/0/1)
Cost: 1562 State: P-2-P Type: Virtual
Transit Area: 0.0.0.1
Timers: Hello 10 , Dead 40 , Retransmit 5 , Transmit Delay 1
MD5 authentication enabled.
The last key is 3.
The rollover is in progress, 2 neighbor(s) left.
Table 55 Command output
|
Field |
Description |
|
Virtual-link Neighbor-ID |
ID of the neighbor on the virtual link. |
|
Neighbor-State |
Neighbor state: Down, Init, 2-Way, ExStart, Exchange, Loading, Full. |
|
Interface |
IP address and name of the local interface on the virtual link. |
|
Cost |
Interface route cost. |
|
State |
Interface state. |
|
Type |
Virtual link. |
|
Transit Area |
Transit area ID. |
|
Timers |
Values of timers (in seconds): Hello, Dead, and Retransmit. |
|
Transmit Delay |
LSA transmission delay on the interface, in seconds. |
|
MD5 authentication enabled |
Authentication mode. |
|
The last key |
Most recent MD5 authentication key ID. |
|
neighbor(s) |
Number of neighbors that have not completed key rollover. |
display router id
Use display router id to display the global router ID.
Syntax
display router id
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display the global router ID.
<Sysname> display router id
Configured router ID is 1.1.1.1
distribute bgp-ls
Use distribute bgp-ls to advertise OSPF link state information to BGP.
Use undo distribute bgp-ls to restore the default.
Syntax
distribute bgp-ls [ instance-id id ] [ strict-link-checking ]
undo distribute bgp-ls
Default
OSPF link state information cannot be advertised to BGP.
Views
OSPF view
Predefined user roles
network-admin
Parameters
instance-id id: Specifies an instance by its ID in the range of 0 to 65535. If you do not specify an instance, this command advertises OSPF link state information of instance 0 to BGP.
strict-link-checking: Enables strict checking on link state information advertised to BGP. If you specify this keyword, the IP addresses of the local and remote ends of a link must be in the same subnet. If you do not specify this keyword, the IP addresses of both ends can be in different subnets. This feature applies only to P2P links.
Usage guidelines
After the device advertises OSPF link state information to BGP, BGP can advertise the information for intended applications.
For multiple OSPF processes with the same link state information and instance ID, only the link state information of the OSPF process with the smallest process ID is advertised.
To advertise the same link state information of different OSPF processes to BGP, specify a different instance ID for each OSPF process.
With this feature enabled, error link state information is not advertised to BGP when the equal-cost links flap.
Strict link state information checking and prefix suppression are mutually exclusive. Before you enable strict link state information checking, make sure prefix suppression is disabled.
Strict link state information checking does not take effect when MPLS TE is enabled. For more information about MPLS TE, see MPLS TE configuration in MPLS Configuration Guide.
Examples
# Advertise link state information of OSPF process 1 to BGP.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] distribute bgp-ls
dscp
Use dscp to set a DSCP value for outgoing OSPF packets.
Use undo dscp to restore the default.
Syntax
dscp dscp-value
undo dscp
Default
The DSCP value for outgoing OSPF packets is 48.
Views
OSPF view
Predefined user roles
network-admin
Parameters
dscp-value: Specifies a DSCP value in the range of 0 to 63 for outgoing OSPF packets.
Examples
# Set the DSCP value for outgoing OSPF packets to 63 in OSPF process 1.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] dscp 63
enable link-local-signaling
Use enable link-local-signaling to enable the OSPF link-local signaling (LLS) capability.
Use undo enable link-local-signaling to disable the OSPF LLS capability.
Syntax
enable link-local-signaling
undo enable link-local-signaling
Default
OSPF link-local signaling capability is disabled.
Views
OSPF view
Predefined user roles
network-admin
Examples
# Enable link-local signaling for OSPF process 1.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] enable link-local-signaling
enable out-of-band-resynchronization
Use enable out-of-band-resynchronization to enable the OSPF out-of-band resynchronization (OOB-Resynch) capability.
Use undo enable out-of-band-resynchronization to disable the OSPF out-of-band resynchronization capability.
Syntax
enable out-of-band-resynchronization
undo enable out-of-band-resynchronization
Default
The OSPF out-of-band resynchronization capability is disabled.
Views
OSPF view
Predefined user roles
network-admin
Usage guidelines
Before you configure this command, enable the link-local signaling capability.
Examples
# Enable the out-of-band resynchronization capability for OSPF process 1.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] enable link-local-signaling
[Sysname-ospf-1] enable out-of-band-resynchronization
Related commands
enable link-local-signaling
event-log
Use event-log to set the number of OSPF logs.
Use undo event-log to remove the configuration.
Syntax
event-log { lsa-flush | peer | spf } size count
undo event-log { lsa-flush | peer | spf } size
Default
The number of LSA aging logs, route calculation logs, or neighbor logs is 10.
Views
OSPF view
Predefined user roles
network-admin
Parameters
lsa-flush: Specifies the number of LSA aging logs.
peer: Specifies the number of neighbor logs.
spf: Specifies the number of route calculation logs.
size count: Specifies the number of OSPF logs, in the range of 0 to 65535.
Examples
# Set the number of route calculation logs to 50 in OSPF process 100.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] event-log spf size 50
fast-reroute (OSPF view)
Use fast-reroute to configure OSPF FRR.
Use undo fast-reroute to restore the default.
Syntax
fast-reroute { lfa [ abr-only ] | route-policy route-policy-name }
undo fast-reroute
Default
OSPF FRR is disabled.
Views
OSPF view
Predefined user roles
network-admin
Parameters
lfa: Uses the LFA algorithm to calculate a backup next hop for all routes.
abr-only: Uses the next hop of the route to the ABR as the backup next hop.
route-policy route-policy-name: Uses a routing policy to designate a backup next hop. The route-policy-name argument is a case-sensitive string of 1 to 63 characters.
Usage guidelines
Do not use the fast-reroute lfa command together with the vlink-peer command.
When both OSPF FRR and PIC are configured, OSPF FRR takes effect.
Examples
# Enable FRR to calculate a backup next hop for all routes by using LFA algorithm in OSPF process 1.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] fast-reroute lfa
filter (OSPF area view)
Use filter to configure OSPF to filter inbound/outbound Type-3 LSAs on an ABR.
Use undo filter to disable Type-3 LSA filtering.
Syntax
filter { ipv4-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } { export | import }
undo filter { export | import }
Default
Type-3 LSAs are not filtered.
Views
OSPF area view
Predefined user roles
network-admin
Parameters
ipv4-acl-number: Specifies an IPv4 ACL by its number in the range of 2000 to 3999 to filter inbound/outbound Type-3 LSAs.
prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter inbound/outbound Type-3 LSAs.
route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter inbound/outbound Type-3 LSAs.
export: Filters Type-3 LSAs advertised to other areas.
import: Filters Type-3 LSAs advertised into the local area.
Usage guidelines
This command applies only to an ABR.
Examples
# Use IP prefix list my-prefix-list to filter inbound Type-3 LSAs. Use basic ACL 2000 to filter outbound Type-3 LSAs in OSPF Area 1.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] area 1
[Sysname-ospf-100-area-0.0.0.1] filter prefix-list my-prefix-list import
[Sysname-ospf-100-area-0.0.0.1] filter 2000 export
filter-policy export (OSPF view)
Use filter-policy export to configure OSPF to filter redistributed routes.
Use undo filter-policy export to remove the configuration.
Syntax
filter-policy { ipv4-acl-number | prefix-list prefix-list-name } export [ bgp | direct | eigrp [ eigrp-as ] | { isis | ospf | rip } [ process-id ] | static ]
undo filter-policy export [ bgp | direct | eigrp [ eigrp-as ] | { isis | ospf | rip } [ process-id ] | static ]
Default
OSPF does not filter redistributed routes.
Views
OSPF view
Predefined user roles
network-admin
Parameters
ipv4-acl-number: Specifies an IPv4 ACL by its number in the range of 2000 to 3999 to filter redistributed routes by destination address.
prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter redistributed routes by destination address.
bgp: Filters routes redistributed from BGP.
direct: Filters direct routes.
eigrp: Filters routes redistributed from EIGRP.
eigrp-as: Specifies an EIGRP process by its ID in the range of 1 to 65535. The default value is 1.
isis: Filters routes redistributed from IS-IS.
ospf: Filters routes redistributed from OSPF.
rip: Filters routes redistributed from RIP.
process-id: Specifies a process by its ID in the range of 1 to 65535. The default value is 1.
Usage guidelines
If you do not specify any parameters, the command filters all redistributed routes.
To use an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL using one of the following methods:
· To deny/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny/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 route. For the mask configuration to take effect, the specified subnet mask must be contiguous.
Examples
# Configure OSPF process 100 to filter redistributed routes by using basic ACL 2000.
<Sysname> system-view
[Sysname] acl basic 2000
[Sysname-acl-ipv4-basic-2000] rule deny source 192.168.10.0 0.0.0.255
[Sysname-acl-ipv4-basic-2000] quit
[Sysname] ospf 100
[Sysname-ospf-100] filter-policy 2000 export
# Configure advanced ACL 3000 to permit only route 113.0.0.0/16. Configure OSPF process 100 to filter redistributed routes by using advanced ACL 3000.
<Sysname> system-view
[Sysname] acl advanced 3000
[Sysname-acl-ipv4-adv-3000] rule 10 permit ip source 113.0.0.0 0 destination 255.255.0.0 0
[Sysname-acl-ipv4-adv-3000] rule 100 deny ip
[Sysname-acl-ipv4-adv-3000] quit
[Sysname] ospf 100
[Sysname-ospf-100] filter-policy 3000 export
Related commands
import-route
filter-policy import (OSPF view)
Use filter-policy import to configure OSPF to filter routes calculated using received LSAs.
Use undo filter-policy import to restore the default.
Syntax
filter-policy { ipv4-acl-number [ gateway prefix-list-name ] | gateway prefix-list-name | prefix-list prefix-list-name [ gateway prefix-list-name ] | route-policy route-policy-name } import
undo filter-policy import
Default
OSPF does not filter routes calculated using received LSAs.
Views
OSPF view
Predefined user roles
network-admin
Parameters
ipv4-acl-number: Specifies an IPv4 ACL by its number in the range of 2000 to 3999 to filter received routes by destination.
gateway prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter received routes by next hop.
prefix-list prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter received routes by destination.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter received routes.
Usage guidelines
To use an advanced ACL (with a number from 3000 to 3999) in the command or in the specified routing policy, configure the ACL in one of the following ways:
· To deny/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny/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, the specified subnet mask must be contiguous.
Examples
# Use basic ACL 2000 to filter received routes.
<Sysname> system-view
[Sysname] acl basic 2000
[Sysname-acl-ipv4-basic-2000] rule deny source 192.168.10.0 0.0.0.255
[Sysname-acl-ipv4-basic-2000] quit
[Sysname] ospf 100
[Sysname-ospf-100] filter-policy 2000 import
# Configure advanced ACL 3000 to permit only route 113.0.0.0/16. Use ACL 3000 to filter received routes.
<Sysname> system-view
[Sysname] acl advanced 3000
[Sysname-acl-ipv4-adv-3000] rule 10 permit ip source 113.0.0.0 0 destination 255.255.0.0 0
[Sysname-acl-ipv4-adv-3000] rule 100 deny ip
[Sysname-acl-ipv4-adv-3000] quit
[Sysname] ospf 100
[Sysname-ospf-100] filter-policy 3000 import
graceful-restart (OSPF view)
Use graceful-restart to enable OSPF GR.
Use undo graceful-restart to disable OSPF GR.
Syntax
graceful-restart [ ietf | nonstandard ] [ global | planned-only ] *
undo graceful-restart
Default
OSPF GR is disabled.
Views
OSPF view
Predefined user roles
network-admin
Parameters
ietf: Enables IETF GR.
nonstandard: Enables non-IETF GR.
global: Enables global GR. In global GR mode, a GR process can be completed only when all GR helpers exist. A GR process fails if a GR helper fails (for example, the interface connected to the GR helper goes down). If you do not specify this keyword, the command enables partial GR. In partial GR mode, a GR process can be completed if a GR helper exists.
planned-only: Enables only planned GR. If you do not specify this keyword, the command enables both planned GR and unplanned GR.
Usage guidelines
GR includes planned GR and unplanned GR.
· Planned GR—Manually restarts OSPF or performs an active/standby switchover. Before OSPF restart or active/standby switchover, the GR restarter sends Grace-LSAs to GR helpers.
· Unplanned GR—OSPF restarts or an active/standby switchover occurs because of device failure. Before OSPF restart or active/standby switchover, the GR restarter does not send Grace-LSAs to GR helpers.
Before enabling IETF GR for OSPF, enable Opaque LSA advertisement and reception with the opaque-capability enable command.
Before enabling non-IETF GR for OSPF, enable OSPF LLS with the enable link-local-signaling command and OOB-Resynch with the enable out-of-band-resynchronization command.
If you do not specify the nonstandard or ietf keyword, this command enables non-IETF GR for OSPF.
OSPF GR and OSPF NSR are mutually exclusive. Do not configure the graceful-restart command and the non-stop-routing command at the same time.
Examples
# Enable IETF GR for OSPF process 1.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] opaque-capability enable
[Sysname-ospf-1] graceful-restart ietf
# Enable non-IETF GR for OSPF process 1.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] enable link-local-signaling
[Sysname-ospf-1] enable out-of-band-resynchronization
[Sysname-ospf-1] graceful-restart nonstandard
Related commands
enable link-local-signaling
enable out-of-band-resynchronization
opaque-capability enable
graceful-restart helper enable
Use graceful-restart helper enable to enable OSPF GR helper capability.
Use undo graceful-restart helper enable to disable OSPF GR helper capability.
Syntax
graceful-restart helper enable [ planned-only ]
undo graceful-restart helper enable
Default
OSPF GR helper capability is enabled.
Views
OSPF view
Predefined user roles
network-admin
Parameters
planned-only: Enables only planned GR for the GR helper. If you do not specify this keyword, the command enables both planned GR and unplanned GR for the GR helper.
Usage guidelines
The planned-only keyword is available only for the IETF GR helper.
Examples
# Enable GR helper capability for OSPF process 1.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] graceful-restart helper enable
graceful-restart helper strict-lsa-checking
Use graceful-restart helper strict-lsa-checking to enable strict LSA checking capability for GR helper.
Use undo graceful-restart helper strict-lsa-checking to disable strict LSA checking capability for GR helper.
Syntax
graceful-restart helper strict-lsa-checking
undo graceful-restart helper strict-lsa-checking
Default
Strict LSA checking capability for GR helper is disabled.
Views
OSPF view
Predefined user roles
network-admin
Usage guidelines
When an LSA change on the GR helper is detected, the GR helper device exits the GR helper mode.
Examples
# Enable strict LSA checking capability for GR helper in OSPF process 1.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] graceful-restart helper strict-lsa-checking
graceful-restart interval (OSPF view)
Use graceful-restart interval to set the GR interval.
Use undo graceful-restart interval to restore the default.
Syntax
graceful-restart interval interval
undo graceful-restart interval
Default
The GR interval is 120 seconds.
Views
OSPF view
Predefined user roles
network-admin
Parameters
interval: Specifies the GR interval in the range of 40 to 1800 seconds.
Usage guidelines
For GR restart to succeed, the value of the GR restart interval cannot be smaller than the maximum OSPF neighbor dead time of all the OSPF interfaces.
Examples
# Set the GR interval for OSPF process 1 to 100 seconds.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] graceful-restart interval 100
Related commands
ospf timer dead
host-advertise
Use host-advertise to advertise a host route.
Use undo host-advertise to remove a host route.
Syntax
host-advertise ip-address cost-value
undo host-advertise ip-address
Default
No host route is advertised.
Views
OSPF area view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the IP address of a host.
cost-value: Specifies a cost for the route, in the range of 1 to 65535.
Examples
# Advertise host route 1.1.1.1 with a cost of 100.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] area 0
[Sysname-ospf-100-area-0.0.0.0] host-advertise 1.1.1.1 100
hostname
Use hostname to enable the OSPF dynamic host name mapping feature.
Use undo hostname disable the OSPF dynamic host name mapping feature.
Syntax
hostname [ host-name ]
undo hostname
Default
The OSPF dynamic host name mapping feature is disabled.
Views
OSPF view
Predefined user roles
network-admin
Parameters
host-name: Specifies the host name mapped to the router ID of the OSPF process, a case-sensitive string of 1 to 255 characters. If you do not specify this argument, the device name is mapped to the router ID of the OSPF process.
Usage guidelines
OSPF uses Type-10 LSAs and Type-11 LSAs to carry information about the dynamic host name attribute. Therefore, make sure the opaque LSA reception and advertisement capability is enabled.
Examples
# Enable the dynamic host name mapping feature for OSPF process 1, and specify the host name mapped to the router ID as red.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] hostname red
Related commands
display ospf hostname-table
opaque-capability enable
import-route (OSPF view)
Use import-route to configure OSPF to redistribute routes.
Use undo import-route to disable route redistribution.
Syntax
import-route bgp [ as-number ] [ allow-ibgp ] [ cost cost-value | nssa-only | route-policy route-policy-name | tag tag | type type ] *
import-route { direct | static } [ cost cost-value | nssa-only | route-policy route-policy-name | tag tag | type type ] *
import-route eigrp [ eigrp-as | all-as ] [ allow-direct | cost cost-value | nssa-only | route-policy route-policy-name | tag tag | type type ] *
import-route { isis | ospf | rip } [ process-id | all-processes ] [ allow-direct | cost cost-value | nssa-only | route-policy route-policy-name | tag tag | type type ] *
undo import-route { bgp | direct | eigrp [ eigrp-as | all-as ] | { isis | ospf | rip } [ process-id | all-processes ] | static }
Default
OSPF does not redistribute routes.
Views
OSPF view
Predefined user roles
network-admin
Parameters
bgp: Redistributes BGP routes.
direct: Redistributes direct routes.
eigrp: Redistributes EIGRP routes.
isis: Redistributes IS-IS routes.
ospf: Redistributes OSPF routes.
rip: Redistributes RIP routes.
static: Redistributes static routes.
as-number: Redistributes routes in an AS specified by its number in the range of 1 to 4294967295. If you do not specify this argument, this command redistributes all IPv4 EBGP routes. As a best practice, specify an AS number to prevent the system from redistributing excessive IPv4 EBGP routes.
eigrp-as: Specifies an EIGRP process by its ID in the range of 1 to 65535. The default value is 1.
all-as: Specifies all EIGRP processes.
process-id: Specifies a process by its ID for IS-IS, OSPF, or RIP, in the range of 1 to 65535. The default value is 1.
all-processes: Redistributes routes from all the processes of IS-IS, OSPF, or RIP.
allow-ibgp: Redistributes IBGP routes.The import-route bgp command redistributes only EBGP routes. Because the import-route bgp allow-ibgp command redistributes both EBGP and IBGP routes and might cause routing loops, use it with caution.
allow-direct: Redistributes the networks of the local interfaces enabled with the specified routing protocol. If you do not specify this keyword, the networks of the local interfaces are not redistributed. If you specify both the allow-direct keyword and the route-policy route-policy-name option, make sure the if-match rule defined in the routing policy does not conflict with the allow-direct keyword. For example, if you specify the allow-direct keyword, do not configure the if-match route-type rule for the routing policy. Otherwise, the allow-direct keyword does not take effect.
cost cost-value: Specifies a route cost in the range of 0 to 16777214. The default is 1.
nssa-only: Limits the route advertisement to the NSSA area by setting the P-bit of Type-7 LSAs to 0. If you do not specify this keyword, the P-bit of Type-7 LSAs is set to 1. If the router acts as both an ASBR and an ABR and FULL state neighbors exist in the backbone area, the P-bit is set to 0. This keyword applies to NSSA routers.
route-policy route-policy-name: Specifies a routing policy to filter redistributed routes. The route-policy-name argument is a case-sensitive string of 1 to 63 characters.
tag tag: Specifies a tag for external LSAs, in the range of 0 to 4294967295. The default is 1.
type type: Specifies a cost type, 1 or 2. The default is 2.
Usage guidelines
This command redistributes routes destined for other ASs from another protocol. AS external routes include the following types:
· Type-1 external routes—Have high credibility. The cost of Type-1 external routes is comparable with the cost of OSPF internal routes. The cost of a Type-1 external route equals the cost from the router to the ASBR plus the cost from the ASBR to the external route's destination.
· Type-2 external routes—Have low credibility. OSPF considers the cost from the ASBR to the destination of a Type-2 external route is much bigger than the cost from the ASBR to an OSPF internal router. The cost of a Type-2 external route equals the cost from the ASBR to the Type-2 external route's destination.
The import-route command cannot redistribute default external routes.
Only active routes can be redistributed. To view information about active routes, use the display ip routing-table protocol command.
The undo import-route eigrp all-as command removes only the configuration made by the import-route eigrp all-as command. It does not remove the configuration made by the import-route eigrp eigrp-as command.
The undo import-route protocol all-processes command removes only the configuration made by the import-route protocol all-processes command, instead of the configuration made by the import-route protocol process-id command.
The import-route nssa-only command redistributes AS-external routes in Type-7 LSAs only into the NSSA area.
Examples
# Redistribute routes from RIP process 40 and specify the type, tag, and cost as 2, 33, and 50 for redistributed routes.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] import-route rip 40 type 2 tag 33 cost 50
default-route-advertise (OSPF view)
ispf enable
Use ispf enable to enable OSPF incremental SPF (ISPF).
Use undo ispf enable to disable OSPF ISPF.
Syntax
ispf enable
undo ispf enable
Default
OSPF ISPF is enabled.
Views
OSPF view
Predefined user roles
network-admin
Usage guidelines
Upon topology changes, ISPF recomputes only the affected part of the SPT, instead of the entire SPT.
Examples
# Disable ISPF for OSPF process 100.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] undo ispf enable
log-peer-change
Use log-peer-change to enable logging for OSPF neighbor state changes.
Use undo log-peer-change to disable logging for OSPF neighbor state changes.
Syntax
log-peer-change
undo log-peer-change
Default
Logging for OSPF neighbor state changes is enabled.
Views
OSPF view
Predefined user roles
network-admin
Usage guidelines
This command enables output of OSPF neighbor state changes to the information center. The information center processes the logs according to user-defined output rules (whether and where to output logs). For more information about the information center, see Network Management and Monitoring Configuration Guide.
Examples
# Disable logging for neighbor state changes for OSPF process 100.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] undo log-peer-change
lsa-arrival-interval
Use lsa-arrival-interval to set the LSA arrival interval.
Use undo lsa-arrival-interval to restore the default.
Syntax
lsa-arrival-interval interval
undo lsa-arrival-interval
Default
The LSA arrival interval is 1000 milliseconds.
Views
OSPF view
Predefined user roles
network-admin
Parameters
interval: Specifies the LSA arrival interval in the range of 0 to 60000 milliseconds.
Usage guidelines
If an LSA that has the same LSA type, LS ID, originating router ID as the previous LSA is received within the interval, OSPF discards the LSA. This feature helps protect resources from being over consumed due to frequent network changes.
As a best practice, set the interval with the lsa-arrival-interval command to be smaller than or equal to the minimum interval set with the lsa-generation-interval command.
Examples
# Set the LSA arrival interval to 200 milliseconds.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] lsa-arrival-interval 200
lsa-generation-interval
lsa-generation-interval
Use lsa-generation-interval to set the OSPF LSA generation interval.
Use undo lsa-generation-interval to restore the default.
Syntax
lsa-generation-interval maximum-interval [ minimum-interval [ incremental-interval ] ]
undo lsa-generation-interval
Default
The maximum interval is 5 seconds, the minimum interval is 50 milliseconds, and the incremental interval is 200 milliseconds.
Views
OSPF view
Predefined user roles
network-admin
Parameters
maximum-interval: Specifies the maximum LSA generation interval in the range of 1 to 60 seconds.
minimum-interval: Specifies the minimum LSA generation interval in the range of 10 to 60000 milliseconds.
incremental-interval: Specifies the LSA generation incremental interval in the range of 10 to 60000 milliseconds.
Usage guidelines
When network changes are infrequent, LSAs are generated at the minimum interval. If network changes become frequent, the LSA generation interval is incremented by the incremental interval × 2n-2 for each generation until the maximum interval is reached. The value n is the number of generation times.
The minimum interval and the incremental interval cannot be greater than the maximum interval.
Examples
# Set the maximum LSA generation interval to 2 seconds, minimum interval to 100 milliseconds, and incremental interval to 100 milliseconds.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] lsa-generation-interval 2 100 100
Related commands
lsa-arrival-interval
lsdb-overflow-interval
Use lsdb-overflow-interval to set the interval that OSPF exits overflow state.
Use undo lsdb-overflow-interval to restore the default.
Syntax
lsdb-overflow-interval interval
undo lsdb-overflow-interval
Default
The OSPF exit overflow interval is 300 seconds.
Views
OSPF view
Predefined user roles
network-admin
Parameters
interval: Specifies the interval that OSPF exits overflow state, in the range of 0 to 2147483647 seconds.
Usage guidelines
When the number of LSAs in the LSDB exceeds the upper limit, the LSDB is in an overflow state. In this state, OSPF does not receive any external LSAs and deletes the external LSAs generated by itself to save system resources.
You can configure the interval that OSPF exits overflow state. An interval of 0 indicates that the timer is not started and OSPF does not exit overflow state.
Examples
# Set the OSPF exit overflow interval to 10 seconds.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] lsdb-overflow-interval 10
lsdb-overflow-limit
Use lsdb-overflow-limit to set the upper limit of external LSAs in the LSDB.
Use undo lsdb-overflow-limit to restore the default.
Syntax
lsdb-overflow-limit number
undo lsdb-overflow-limit
Default
The number of external LSAs is not limited.
Views
OSPF view
Predefined user roles
network-admin
Parameters
number: Specifies the upper limit of external LSAs in the LSDB, in the range of 1 to 1000000.
Examples
# Set the upper limit of external LSAs to 400000.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] lsdb-overflow-limit 400000
maximum load-balancing (OSPF view)
Use maximum load-balancing to set the maximum number of equal-cost multi-path (ECMP) routes for load balancing.
Use undo maximum load-balancing to restore the default.
Syntax
maximum load-balancing number
undo maximum load-balancing
Default
The maximum number of OSPF ECMP routes equals the maximum number of ECMP routes supported by the system.
Views
OSPF view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of ECMP routes. No ECMP load balancing is available when the number is set to 1.
Examples
# Set the maximum number of ECMP routes to 2.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] maximum load-balancing 2
network (OSPF area view)
Use network to enable OSPF on the interface attached to the specified network in the area.
Use undo network to disable OSPF for the interface attached to the specified network in the area.
Syntax
network ip-address wildcard-mask
undo network ip-address wildcard-mask
Default
OSPF is not enabled for any interface.
Views
OSPF area view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the IP address of a network.
wildcard-mask: Specifies the wildcard mask of the IP address. For example, the wildcard mask of mask 255.0.0.0 is 0.255.255.255.
Usage guidelines
This command enables OSPF on the interface attached to the specified network. The interface's primary IP address must be in the specified network. If only the interface's secondary IP address is in the network, the interface cannot run OSPF.
Examples
# Specify the interface whose primary IP address is on network 131.108.20.0/24 to run OSPF in Area 2.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] area 2
[Sysname-ospf-100-area-0.0.0.2] network 131.108.20.0 0.0.0.255
ospf
non-stop-routing
Use non-stop-routing to enable OSPF NSR.
Use undo non-stop-routing to disable OSPF NSR.
Syntax
non-stop-routing
undo non-stop-routing
Default
OSPF NSR is disabled.
Views
OSPF view
Predefined user roles
network-admin
Usage guidelines
The following matrix shows the command and hardware compatibility:
|
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28/3600-51 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
· In standalone mode: No · In IRF mode: Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Command compatibility |
|
MSR810-LM-GL |
No |
|
MSR810-W-LM-GL |
No |
|
MSR830-6EI-GL |
No |
|
MSR830-10EI-GL |
No |
|
MSR830-6HI-GL |
No |
|
MSR830-10HI-GL |
No |
|
MSR2600-6-X1-GL |
No |
|
MSR3600-28-SI-GL |
No |
This command takes effect only for the current process. As a best practice, enable OSPF NSR for each process if multiple OSPF processes exist.
OSPF NSR and OSPF GR are mutually exclusive. Do not configure the non-stop-routing command and the graceful-restart command at the same time.
Examples
# Enable NSR for OSPF process 100.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] non-stop-routing
nssa
Use nssa to configure an area as an NSSA area.
Use undo nssa to restore the default.
Syntax
nssa [ default-route-advertise [ cost cost-value | nssa-only | route-policy route-policy-name | type type ] * | no-import-route | no-summary | suppress-fa | [ [ [ translate-always ] [ translate-ignore-checking-backbone ] ] | translate-never ] | translator-stability-interval value ] *
undo nssa
Default
No area is configured as an NSSA area.
Views
OSPF area view
Predefined user roles
network-admin
Parameters
default-route-advertise: Used on an NSSA ABR or an ASBR only. With this keyword, an NSSA ABR redistributes a default route in a Type-7 LSA into the NSSA area. The ABR redistributes a default route regardless of whether a default route exists in the routing table. With this keyword, an ASBR redistributes a default route in a Type-7 LSA only when the default route exists in the routing table.
cost cost-value: Specifies a cost for the default route, in the range of 0 to 16777214. If you do not specify this option, the default cost specified by the default-cost command applies.
nssa-only: Limits the default route advertisement to the NSSA area by setting the P-bit of Type-7 LSAs to 0. By default, the P-bit of Type-7 LSAs is set to 1. If the router acts as both an ASBR and an ABR and FULL state neighbors exist in the backbone area, the P-bit is set to 0.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters. When a default route exists in the routing table and the routing policy is matched, the command redistributes a default route in a Type-7 LSA into the OSPF routing domain. The routing policy modifies values in the Type-7 LSA.
type type: Specifies a type for the Type-7 LSA, 1 or 2. If you do not specify this option, the default type specified by the default type command applies.
no-import-route: Used on an NSSA ABR to control the import-route command to not redistribute routes into the NSSA area.
no-summary: Used only on an ABR to advertise a default route in a Type-3 summary LSA into the NSSA area and to not advertise other summary LSAs into the area. The area is a totally NSSA area.
suppress-fa: Suppresses the forwarding address in the Type-7 LSAs from being placed in the Type-5 LSAs.
translate-always: Always translates Type-7 LSAs to Type-5 LSAs. This keyword takes effect only on an NSSA ABR.
translate-ignore-checking-backbone: Ignores checking for FULL state neighbors in the backbone area during the translator election in the NSSA area.
translate-never: Never translates Type-7 LSAs to Type-5 LSAs. This keyword takes effect only on an NSSA ABR.
translator-stability-interval value: Specifies the stability interval of the translator. During the interval, the translator can maintain its translating capability after another device becomes the new translator. The value argument is the stability interval in the range of 0 to 900 seconds and defaults to 0. A value of 0 means the translator does not maintain its translating capability when a new translator arises.
Usage guidelines
All routers attached to an NSSA area must be configured with the nssa command in area view.
If you specify the translate-ignore-checking-backbone keyword for an ABR, you must also specify the keyword for other ABRs in the NSSA area. This ensures that a translator can be elected among the ABRs.
Examples
# Configure Area 1 as an NSSA area.
[Sysname] ospf 100
[Sysname-ospf-100] area 1
[Sysname-ospf-100-area-0.0.0.1] nssa
default-cost (OSPF area view)
opaque-capability enable
Use opaque-capability enable to enable opaque LSA advertisement and reception.
Use undo opaque-capability to disable opaque LSA advertisement and reception.
Syntax
opaque-capability enable
undo opaque-capability
Default
The feature is enabled.
Views
OSPF view
Predefined user roles
network-admin
Usage guidelines
After the opaque LSA advertisement and reception capability is enabled, OSPF can receive and advertise Type-9, Type-10, and Type-11 opaque LSAs.
Examples
# Disable opaque LSA advertisement and reception.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] undo opaque-capability
ospf
Use ospf to enable OSPF and enter OSPF view.
Use undo ospf to disable OSPF.
Syntax
ospf [ process-id | router-id { auto-select | router-id } | vpn-instance vpn-instance-name ] *
undo ospf [ process-id ] [ router-id ]
Default
OSPF is disabled.
Views
System view
Predefined user roles
network-admin
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535.
router-id: Specifies an OSPF router ID. If you do not specify an OSPF router ID, the global router ID is used.
auto-select: Automatically obtains an OSPF router ID.
router-id: Manually specifies an OSPF router ID in dotted decimal notation. The value range is from 0.0.0.1 to 255.255.255.255.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the OSPF process runs on the public network.
Usage guidelines
You can enable multiple OSPF processes on a router and specify different router IDs for them.
Enable an OSPF process before performing other tasks.
If you specify the auto-select keyword, the OSPF process obtains a router ID in the following ways:
· During the startup of the OSPF process, the primary IPv4 address of the first interface that runs the process is specified as the router ID.
· During the reboot of the router, the primary IPv4 address of the first interface that runs the process is specified as the router ID.
· During the restart of the OSPF process, the highest primary IPv4 address of the loopback interface that runs the process is specified as the router ID. If no loopback address is available, the highest primary IPv4 address of the interface that runs the process is used, regardless of the interface state (up or down).
If you do not specify the router-id keyword, the undo ospf command shuts down an OSPF process. If you specify the router-id keyword, the undo ospf command specifies the global router ID as the router ID. The setting takes effect after the OSPF process restarts.
Examples
# Enable OSPF process 100 and specify router ID 10.10.10.1.
<Sysname> system-view
[Sysname] ospf 100 router-id 10.10.10.1
[Sysname-ospf-100]
ospf area
Use ospf area to enable OSPF on an interface.
Use undo ospf area to disable OSPF on an interface.
Syntax
ospf process-id area area-id [ exclude-subip ]
undo ospf process-id area [ exclude-subip ]
Default
OSPF is not enabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535.
area-id: Specifies an area by its ID, an IP address or a decimal integer in the range of 0 to 4294967295 that is translated into the IP address format.
exclude-subip: Excludes secondary IP addresses. If you do not specify this keyword, the command enables OSPF also on secondary IP addresses.
Usage guidelines
The ospf area command has a higher priority than the network command.
If the specified process and area do not exist, the command creates the process and area. Disabling an OSPF process on an interface does not delete the OSPF process or the area.
Examples
# Enable OSPF process 1 on GigabitEthernet 1/0/2 that is in Area 2 and exclude secondary IP addresses.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/2
[Sysname-GigabitEthernet1/0/2] ospf 1 area 2 exclude-subip
Related commands
network
ospf authentication-mode
Use ospf authentication-mode to set the authentication mode and key on an interface.
Use undo ospf authentication-mode to remove specified configuration.
Syntax
For MD5/HMAC-MD5 authentication:
ospf authentication-mode { hmac-md5 | md5 } key-id { cipher | plain } string
undo ospf authentication-mode { hmac-md5 | md5 } key-id
For simple authentication:
ospf authentication-mode simple { cipher | plain } string
undo ospf authentication-mode simple
For keychain authentication:
ospf authentication-mode keychain keychain-name
undo ospf authentication-mode keychain
Default
No authentication is performed.
Views
Interface view
Predefined user roles
network-admin
Parameters
hmac-md5: Specifies HMAC-MD5 authentication.
md5: Specifies MD5 authentication.
simple: Specifies simple authentication.
key-id: Specifies a key by its ID in the range of 1 to 255.
cipher: Specifies a key in encrypted form.
plain: Specifies a key in plaintext form. For security purposes, the key specified in plaintext form will be stored in encrypted form.
string: Specifies the key. This argument is case sensitive.
· In simple authentication mode, the plaintext form of the key is a string of 1 to 8 characters. The encrypted form of the key is a string of 33 to 41 characters.
· In MD5/HMAC-MD5 authentication mode, the plaintext form of the key is a string of 1 to 16 characters. The encrypted form of the key is a string of 33 to 53 characters.
keychain: Specifies keychain authentication.
keychain-name: Specifies a keychain by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
To establish or maintain adjacencies, interfaces attached to the same network segment must have the same authentication mode and key.
If MD5 or HMAC-MD5 authentication is configured, you can configure multiple keys, each having a unique key ID and key string. To minimize the risk of key comprise, use only one key for an interface and delete the old key after key replacement.
To replace the key used for MD5 or HMAC-MD5 authentication on an interface, you must configure the new key before removing the old key from each router. OSPF uses the key rollover mechanism to ensure that the routers can pass authentication before the replacement is complete on the interface. After you configure a new key on a router, the router sends copies of the same packet, each authenticated by a different key, including the new key and the keys in use. This practice continues until the router detects that all its neighbors have the new key.
If keychain authentication is configured, the keys on the keychain must be the same on the interface, including the key ID, key string, and valid period of time. In addition, the authentication method can only be MD5 or HMAC-MD5, and the key ID cannot be greater than 255.
Examples
# On GigabitEthernet 1/0/1, enable MD5 authentication, and set the interface key ID to 15 and the key to 123456 in plaintext form.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf authentication-mode md5 15 plain 123456
# On GigabitEthernet 1/0/1, enable simple authentication, and set the key to 123456 in plaintext form.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf authentication-mode simple plain 123456
authentication-mode
ospf bfd enable
Use ospf bfd enable to enable BFD on an OSPF interface.
Use undo ospf bfd enable to disable BFD on an OSPF interface.
Syntax
ospf bfd enable [ echo ]
undo ospf bfd enable
Default
BFD for OSPF is disabled.
Views
Interface view
Predefined user roles
network-admin
Parameters
echo: Enables BFD single-hop echo detection. If you do not specify this keyword, the command enables BFD bidirectional control detection.
Examples
# Enable BFD for OSPF on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] ospf
[Sysname-ospf-1] area 0
[Sysname-ospf-1-area-0.0.0.0] network 192.168.0.0 0.0.255.255
[Sysname-ospf-1-area-0.0.0.0] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf bfd enable
ospf cost
Use ospf cost to set an OSPF cost for an interface.
Use undo ospf cost to restore the default.
Syntax
ospf cost cost-value
undo ospf cost
Default
An interface computes its OSPF cost according to the interface bandwidth. For a loopback interface, the cost is 0.
Views
Interface view
Predefined user roles
network-admin
Parameters
cost-value: Specifies an OSPF cost in the range of 0 to 65535 for a loopback interface, and in the range of 1 to 65535 for other interfaces.
Usage guidelines
If you do not execute this command, the interface automatically computes its OSPF cost.
Examples
# Set the OSPF cost on GigabitEthernet 1/0/1 to 65.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf cost 65
Related commands
bandwidth-reference
ospf database-filter
Use ospf database-filter to filter outbound LSAs on an interface.
Use undo ospf database-filter to restore the default.
Syntax
ospf database-filter { all | { ase [ acl ipv4-acl-number ] | nssa [ acl ipv4-acl-number ] | summary [ acl ipv4-acl-number ] } * }
undo ospf database-filter
Default
The outbound LSAs are not filtered on the interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
all: Filters all outbound LSAs except the Grace LSAs.
ase: Filters outbound Type-5 LSAs.
nssa: Filters outbound Type-7 LSAs.
summary: Filters outbound Type-3 LSAs.
acl ipv4-acl-number: Specifies an IPv4 ACL by its number in the range of 2000 to 3999.
Usage guidelines
To use an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL using one of the following methods:
· To deny/permit LSAs with the specified link state ID, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny/permit LSAs with the specified link state ID 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 link state ID of an LSA and the destination keyword specifies the subnet mask of the LSA. The specified subnet mask must be contiguous. Otherwise, the mask configuration does not take effect.
If the neighbor has already received an LSA to be filtered, the LSA still exists in the LSDB of the neighbor after you execute the command.
Examples
# Filter all outbound LSAs (except the Grace LSAs) on the interface GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf database-filter all
# On the interface GigabitEthernet 1/0/2, configure ACL 2000, 2100, and 2200 to filter outbound Type-5, Type-7, and Type-3 LSAs, respectively.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/2
[Sysname-GigabitEthernet1/0/2] ospf database-filter ase acl 2000 nssa acl 2100 summary acl 2200
Related commands
database-filter peer (OSPF view)
ospf dr-priority
Use ospf dr-priority to set the router priority for DR/BDR election on an interface.
Use undo ospf dr-priority to restore the default value.
Syntax
ospf dr-priority priority
undo ospf dr-priority
Default
The router priority is 1.
Views
Interface view
Predefined user roles
network-admin
Parameters
priority: Specifies the router priority for the interface, in the range of 0 to 255.
Usage guidelines
The greater the value, the higher the priority for DR/BDR election. If a device has a priority of 0, it will not be elected as a DR or BDR.
Examples
# Set the router priority on GigabitEthernet 1/0/1 to 8.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf dr-priority 8
ospf fast-reroute lfa-backup
Use ospf fast-reroute lfa-backup to enable LFA on an interface.
Use undo ospf fast-reroute lfa-backup to disable LFA on an interface.
Syntax
ospf fast-reroute lfa-backup
undo ospf fast-reroute lfa-backup
Default
LFA is enabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
An interface enabled with LFA can be selected as a backup interface. After you disable LFA on the interface, it cannot be selected as a backup interface.
Examples
# Disable GigabitEthernet 1/0/1 from calculating a backup next hop by using the LFA algorithm.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] undo ospf fast-reroute lfa-backup
ospf mib-binding
Use ospf mib-binding to bind an OSPF process to MIB.
Use undo ospf mib-binding to restore the default.
Syntax
ospf mib-binding process-id
undo ospf mib-binding
Default
MIB is bound to the OSPF process with the smallest process ID.
Views
System view
Predefined user roles
network-admin
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535.
Usage guidelines
To access information or data about an OSPF process in RFC4750-OSPF.MIB, use this command. To access information or data about an OSPF process in a Comware MIB for the device, you do not need to use this command. You can access information or data about all OSPF processes in the Comware MIBs.
If the specified process ID does not exist, a notification is displayed to report that the MIB binding configuration has failed.
Deleting an OSPF process that has been bound to MIB unbinds the OSPF process from MIB, and re-binds MIB to the OSPF process with the smallest process ID.
Examples
# Bind OSPF process 100 to MIB.
<Sysname> system-view
[Sysname] ospf mib-binding 100
ospf mtu-enable
Use ospf mtu-enable to enable an interface to add the interface MTU into DD packets.
Use undo ospf mtu-enable to restore the default.
Syntax
ospf mtu-enable
undo ospf mtu-enable
Default
The MTU in DD packets is 0.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
After a virtual link is established through a Virtual-Template or Tunnel, two devices on the link from different vendors might have different MTU values. To make them consistent, restore the interfaces' MTU to the default value 0.
After you configure this command, the interface checks whether the MTU in a received DD packet is greater than its own MTU. If yes, the interface discards the packet.
Examples
# Enable interface GigabitEthernet 1/0/1 to add the interface MTU value into DD packets.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf mtu-enable
ospf network-type
Use ospf network-type to specify the network type for an interface.
Use undo ospf network-type to restore the default.
Syntax
ospf network-type { broadcast | nbma | p2mp [ unicast ] | p2p [ peer-address-check ] }
undo ospf network-type
Default
By default, the network type of an interface depends on its link layer protocol:
· For Ethernet and FDDI, the network type is broadcast.
· For ATM, FR, and X.25, the network type is NBMA.
· For PPP, LAPB, HDLC, and POS, the network type is P2P.
Views
Interface view
Predefined user roles
network-admin
Parameters
broadcast: Specifies the network type as broadcast.
nbma: Specifies the network type as NBMA.
p2mp: Specifies the network type as P2MP.
unicast: Specifies the P2MP interface to unicast OSPF packets. By default, a P2MP interface multicasts OSPF packets.
p2p: Specifies the network type as P2P.
peer-address-check: Checks whether the peer interface and the local interface are on the same network segment. Two P2P interfaces can establish a neighbor relationship only when they are on the same network segment.
Usage guidelines
If a router on a broadcast network does not support multicast, configure the network type for the connected interfaces as NBMA.
If any two routers on an NBMA network are directly connected through a virtual link, the network is fully meshed. You can configure the network type for the connected interfaces as NBMA. If two routers are not directly connected, configure the P2MP network type so that the two routers can exchange routing information through another router.
When the network type of an interface is NBMA or P2MP unicast, you must use the peer command to specify the neighbor.
If only two routers run OSPF on a network, you can configure the network type for the connected interfaces as P2P.
When the network type of an interface is P2MP unicast, all OSPF packets are unicast by the interface.
Examples
# Specify the OSPF network type for GigabitEthernet 1/0/1 as NBMA.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf network-type nbma
ospf dr-priority
ospf prefix-suppression
Use ospf prefix-suppression to disable an OSPF interface from advertising all its IP prefixes, except for the prefixes of secondary IP addresses.
Use undo ospf prefix-suppression to restore the default.
Syntax
ospf prefix-suppression [ disable ]
undo ospf prefix-suppression
Default
Prefix suppression is disabled.
Views
Interface view
Predefined user roles
network-admin
Parameters
disable: Disables prefix suppression for an interface.
Usage guidelines
To disable prefix suppression for an interface associated with an OSPF process that has been enabled with prefix suppression, use the ospf prefix-suppression disable command on that interface.
Examples
# Enable prefix suppression for GigabitEthernet 1/0/2.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/2
[Sysname-GigabitEthernet1/0/2] ospf prefix-suppression
Related commands
prefix-suppression
ospf primary-path-detect bfd
Use ospf primary-path-detect bfd to enable BFD for OSPF FRR or OSPF PIC.
Use undo ospf primary-path-detect bfd to disable BFD for OSPF FRR or OSPF PIC.
Syntax
ospf primary-path-detect bfd { ctrl | echo }
undo ospf primary-path-detect bfd
Default
BFD is disabled for OSPF FRR or OSPF PIC.
Views
Interface view
Predefined user roles
network-admin
Parameters
ctrl: Enables BFD control packet mode.
echo: Enables BFD echo packet mode.
Usage guidelines
This command enables OSPF PIC or OSPF FRR to use BFD to detect primary link failures.
Examples
# On GigabitEthernet 1/0/1, enable BFD control packet mode for OSPF FRR.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] fast-reroute lfa
[Sysname-ospf-1] quit
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf primary-path-detect bfd ctrl
# On GigabitEthernet 1/0/2, enable BFD echo packet mode for OSPF PIC.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] pic additional-path-always
[Sysname-ospf-1] quit
[Sysname] bfd echo-source-ip 1.1.1.1
[Sysname] interface gigabitethernet 1/0/2
[Sysname-GigabitEthernet1/0/2] ospf primary-path-detect bfd echo
ospf timer dead
Use ospf timer dead to set the neighbor dead interval.
Use undo ospf timer dead to restore the default.
Syntax
ospf timer dead seconds
undo ospf timer dead
Default
The dead interval is 40 seconds for broadcast and P2P interfaces. The dead interval is 120 seconds for P2MP and NBMA interfaces.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the dead interval in the range of 1 to 2147483647 seconds.
Usage guidelines
If an interface receives no hello packet from a neighbor within the dead interval, the interface considers the neighbor down.
The dead interval on an interface is a minimum of four times the hello interval. Routers attached to the same segment must have the same dead interval.
Examples
# Set the dead interval for GigabitEthernet 1/0/1 to 60 seconds.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf timer dead 60
ospf timer hello
ospf timer hello
Use ospf timer hello to set the hello interval on an interface.
Use undo ospf timer hello to restore the default.
Syntax
ospf timer hello seconds
undo ospf timer hello
Default
The hello interval is 10 seconds for P2P and broadcast interfaces, and is 30 seconds for P2MP and NBMA interfaces.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the hello interval in the range of 1 to 65535 seconds.
Usage guidelines
The shorter the hello interval, the faster the topology converges, and the more resources are consumed. Make sure the hello interval on two neighboring interfaces is the same.
Examples
# Set the hello interval on GigabitEthernet 1/0/1 to 20 seconds.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf timer hello 20
ospf timer dead
ospf timer poll
Use ospf timer poll to set the poll interval on an NBMA interface.
Use undo ospf timer poll to restore the default.
Syntax
ospf timer poll seconds
undo ospf timer poll
Default
The poll interval is 120 seconds on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the poll interval in the range of 1 to 2147483647 seconds.
Usage guidelines
When an NBMA interface finds its neighbor is down, it sends hello packets at the poll interval.
The poll interval must be a minimum of four times the hello interval.
Examples
# Set the poll timer interval on GigabitEthernet 1/0/1 to 130 seconds.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf timer poll 130
ospf timer hello
ospf timer retransmit
Use ospf timer retransmit to set the LSA retransmission interval on an interface.
Use undo ospf timer retransmit to restore the default.
Syntax
ospf timer retransmit seconds
undo ospf timer retransmit
Default
The LSA retransmission interval is 5 seconds on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the LSA retransmission interval in the range of 1 to 3600 seconds.
Usage guidelines
After sending an LSA, an interface waits for an acknowledgment packet. If the interface receives no acknowledgment within the retransmission interval, it retransmits the LSA.
To avoid unnecessary retransmissions, set an appropriate retransmission interval. For example, you can set a large retransmission interval value on a low-speed link.
Examples
# Set the LSA retransmission interval to 8 seconds on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf timer retransmit 8
ospf trans-delay
Use ospf trans-delay to set the LSA transmission delay on an interface.
Use undo ospf trans-delay to restore the default.
Syntax
ospf trans-delay seconds
undo ospf trans-delay
Default
The LSA transmission delay is 1 second.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the LSA transmission delay in the range of 1 to 3600 seconds.
Usage guidelines
Each LSA in the LSDB has an age that is incremented by 1 every second, but the age does not change during transmission. Adding a transmission delay into the age time is important in low speed networks.
Examples
# Set the LSA transmission delay to 3 seconds on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf trans-delay 3
ospf ttl-security
Use ospf ttl-security to enable OSPF GTSM for an interface.
Use undo ospf ttl-security to disable OSPF GTSM for an interface.
Syntax
ospf ttl-security [ hops hop-count | disable ]
undo ospf ttl-security
Default
OSPF GTSM is disabled for an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
hops hop-count: Specifies the hop limit for checking OSPF packets, in the range of 1 to 254. The default hop limit is 1 for packets from common neighbors, and is 255 for packets from virtual link neighbors and sham link neighbors.
disable: Disables OSPF GTSM for the interface.
Usage guidelines
GTSM checks OSPF packets from common neighbors and virtual link neighbors. It does not check OSPF packets from sham link neighbors.
GTSM protects the device by comparing the TTL value in the IP header of incoming OSPF packets against a valid TTL range. If the TTL value is within the valid TTL range, the packet is accepted. If not, the packet is discarded.
The valid TTL range is from 255 – the configured hop count + 1 to 255.
When GTSM is configured, the OSPF packets sent by the device have a TTL of 255. To use GTSM, you must configure GTSM on both the local and peer devices. You can specify different hop-count values for them.
The hops keyword configured in interface view takes precedence over the hops keyword configured in OSPF area view.
If the ttl-security command is not configured, the undo ospf ttl-security command disables GTSM for an interface.
If the ttl-security command is configured, the undo ospf ttl-security command removes the GTSM configuration for an interface. At the same time, the GTSM configuration for the area applies to the interface. The ospf ttl-security disable command disables GTSM for an interface.
If a virtual link exists in an area, you can enable GTSM for the interfaces on the virtual link. If you do not know the interfaces on the virtual link, enable GTSM in area view to prevent packet loss.
Examples
# Enable OSPF GTSM for the interface GigabitEthernet 1/0/1 and set the hop limit to 254.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf ttl-security hops 254
# Enable GTSM in OSPF area view and disable OSPF GTSM for the interface GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] area 1
[Sysname-ospf-100-area-0.0.0.1] ttl-security
[Sysname-ospf-100-area-0.0.0.1] quit
[Sysname-ospf-100] quit
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospf ttl-security disable
Related commands
ttl-security (OSPF area view)
peer
Use peer to specify a neighbor in an NBMA or P2MP network.
Use undo peer to remove a neighbor in an NBMA or P2MP network.
Syntax
peer ip-address [ cost cost-value | dr-priority priority ]
undo peer ip-address
Default
No neighbor is specified.
Views
OSPF view
Predefined user roles
network-admin
Parameters
ip-address: Specifies a neighbor by its IP address.
cost cost-value: Specifies the cost to reach the neighbor, in the range of 1 to 65535.
dr-priority priority: Specifies the DR priority for the neighbor, in the range of 0 to 255. The default neighbor DR priority is 1.
Usage guidelines
In an NBMA or P2MP network, OSPF packets are sent in unicast, so you must use this command to specify neighbors.
The cost set with the peer command applies only to P2MP neighbors. If no cost is specified, the cost to the neighbor equals the local interface's cost.
A router uses the priority set with the peer command to determine whether to send a hello packet to the neighbor rather than for DR election. The DR priority set with the ospf dr-priority command is used for DR election.
Examples
# Specify the neighbor 1.1.1.1.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] peer 1.1.1.1
ospf dr-priority
pic
Use pic to enable OSPF PIC.
Use undo pic to disable OSPF PIC.
Syntax
pic [ additional-path-always ]
undo pic
Default
OSPF PIC is enabled.
Views
OSPF view
Predefined user roles
network-admin
Parameters
additional-path-always: Allows the indirect suboptimal route as the backup route.
Usage guidelines
Prefix Independent Convergence (PIC) enables the device to speed up network convergence by ignoring the number of prefixes. PIC applies only to inter-area routes and external routes.
When both OSPF PIC and OSPF FRR are configured, OSPF FRR takes effect.
Examples
# Configure OSPF PIC to support the suboptimal route as the backup route.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] pic additional-path-always
preference
Use preference to set a preference for OSPF.
Use undo preference to remove the configuration.
Syntax
preference [ ase ] { preference | route-policy route-policy-name } *
undo preference [ ase ]
Default
The preference is 10 for OSPF internal routes and 150 for OSPF external routes (ASE routes).
Views
OSPF view
Predefined user roles
network-admin
Parameters
ase: Specifies a preference for OSPF external routes. If you do not specify this keyword, the command sets a preference for OSPF internal routes.
preference: Specifies the preference value in the range of 1 to 255. A smaller value represents a higher preference.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to set a preference for the specified routes.
Usage guidelines
When the route-policy route-policy-name option is specified, the following preferences take effect:
· For routes matching the routing policy, the preference set in the routing policy takes effect.
· For other routes, the preference set with the preference command takes effect.
If multiple routing protocols find routes to the same destination, the router uses the route found by the protocol with the highest preference.
Examples
# Set a preference of 200 for OSPF external routes.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] preference ase 200
# Set a preference of 100 for OSPF internal routes matching the specified routing policy, and set a preference of 150 for other routes.
<Sysname> system-view
[Sysname] ip prefix-list test index 10 permit 100.1.1.0 24
[Sysname] route-policy pre permit node 10
[Sysname-route-policy-pre-10] if-match ip address prefix-list test
[Sysname-route-policy-pre-10] apply preference 100
[Sysname-route-policy-pre-10] quit
[Sysname] ospf 100
[Sysname-ospf-100] preference route-policy pre 150
prefix-priority
Use prefix-priority to enable prefix prioritization.
Use undo prefix-priority to disable prefix prioritization.
Syntax
prefix-priority route-policy route-policy-name
undo prefix-priority
Default
Prefix prioritization is disabled.
Views
OSPF view
Predefined user roles
network-admin
Parameters
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to set a priority for the specified route prefixes.
Usage guidelines
Prefix prioritization enables the device to install prefixes in descending priority order: critical, high, medium, and low. The prefix priorities are assigned through routing policies. When a route is assigned multiple prefix priorities, it uses the highest priority.
By default, the 32-bit OSPF host routes have a medium priority and other routes have a low priority.
Examples
# Use a routing policy to assign the medium priority to the specified route prefixes.
<Sysname> system-view
[Sysname] ip prefix-list test index 10 permit 100.1.1.0 24
[Sysname] route-policy pre permit node 10
[Sysname-route-policy-pre-10] if-match ip address prefix-list test
[Sysname-route-policy-pre-10] apply prefix-priority medium
[Sysname-route-policy-pre-10] quit
[Sysname] ospf 100
[Sysname-ospf-100] prefix-priority route-policy pre
prefix-suppression
Use prefix-suppression to disable an OSPF process from advertising all IP prefixes except for the prefixes of loopback interfaces, secondary IP addresses, and passive interfaces.
Use undo prefix-suppression to restore the default.
Syntax
prefix-suppression
undo prefix-suppression
Default
An OSPF process advertises all prefixes.
Views
OSPF view
Predefined user roles
network-admin
Usage guidelines
As a best practice, configure prefix suppression on all OSPF routers if you want to use prefix suppression.
To disable an OSPF process from advertising the prefixes of loopback and passive interfaces, configure prefix suppression on the interfaces by using the ospf prefix-suppression command.
By default, an OSPF interface advertises all of its prefixes in LSAs. To speed up OSPF convergence, you can suppress interfaces from advertising all their prefixes. This feature helps improve network security by preventing IP routing to the suppressed networks.
When prefix suppression is enabled:
· On P2P and P2MP networks, OSPF does not advertise Type-3 links in Type-1 LSAs. Other routing information can still be advertised to ensure traffic forwarding.
· On broadcast and NBMA networks, the DR generates Type-2 LSAs with a mask length of 32 to suppress network routes. Other routing information can still be advertised to ensure traffic forwarding. If no neighbors exist, the DR also does not advertise the primary IP addresses of interfaces in Type-1 LSAs.
Examples
# Enable prefix suppression for OSPF process 1.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] prefix-suppression
Related commands
ospf prefix-suppression
reset ospf event-log
Use reset ospf event-log to clear OSPF log information.
Syntax
reset ospf [ process-id ] event-log [ lsa-flush | peer | spf ]
Views
User view
Predefined user roles
network-admin
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify this argument, the command clears OSPF log information for all OSPF processes.
lsa-flush: Clears LSA aging log information.
peer: Clears neighbor log information.
spf: Clears route calculation log information.
Usage guidelines
If you do not specify a log type, this command clears all log information.
Examples
# Clear OSPF route calculation log information for all OSPF processes.
<Sysname> reset ospf event-log spf
Related commands
display ospf event-log
reset ospf process
Use reset ospf process to restart all OSPF processes or a specified process.
Syntax
reset ospf [ process-id ] process [ graceful-restart ]
Views
User view
Predefined user roles
network-admin
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify a process, this command restarts all OSPF processes.
graceful-restart: Resets the OSPF process by using GR.
Usage guidelines
The reset ospf process command performs the following actions:
· Clears all invalid LSAs without waiting for their timeouts.
· Makes a newly configured router ID take effect.
· Starts a new DR/BDR election.
· Keeps previous OSPF configurations.
The system prompts you to select whether to restart OSPF process upon execution of this command.
Examples
# Restart all OSPF processes.
<Sysname> reset ospf process
Reset OSPF process? [Y/N]:y
reset ospf redistribution
Use reset ospf redistribution to restart route redistribution.
Syntax
reset ospf [ process-id ] redistribution
Views
User view
Predefined user roles
network-admin
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535. If you do not specify a process, this command restarts route redistribution for all OSPF processes.
Examples
# Restart route redistribution.
<Sysname> reset ospf redistribution
reset ospf statistics
Use reset ospf statistics to clear OSPF statistics.
Syntax
reset ospf [ process-id ] statistics
Views
User view
Predefined user roles
network-admin
Parameters
process-id: Clears the statistics for an OSPF process specified by its ID in the range of 1 to 65535.
Examples
# Clear OSPF statistics for all processes.
<Sysname> reset ospf statistics
Related commands
display ospf statistics
rfc1583 compatible
Use rfc1583 compatible to enable compatibility with RFC 1583.
Use undo rfc1583 compatible to disable compatibility with RFC 1583.
Syntax
rfc1583 compatible
undo rfc1583 compatible
Default
Compatibility with RFC 1583 is enabled.
Views
OSPF view
Predefined user roles
network-admin
Usage guidelines
RFC 1583 specifies a different method than RFC 2328 for selecting the optimal route to a destination in another AS. When multiple routes are available to the ASBR, OSPF selects the optimal route by using the following procedure:
1. Selects the route with the highest preference.
¡ If RFC 2328 is compatible with RFC 1583, all these routes have equal preference.
¡ If RFC 2328 is not compatible with RFC 1583, the intra-area route in a non-backbone area is preferred to reduce the burden of the backbone area. The inter-area route and intra-area route in the backbone area have equal preference.
2. Selects the route with lower cost if two routes have equal preference.
3. Selects the route with larger originating area ID if two routes have equal cost.
To avoid routing loops, set identical RFC 1583-compatibility on all routers in a routing domain.
Examples
# Disable compatibility with RFC 1583.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] undo rfc1583 compatible
router id
Use router id to configure a global router ID.
Use undo router id to restore the default.
Syntax
router id router-id
undo router id
Default
No global router ID is configured.
Views
System view
Predefined user roles
network-admin
Parameters
router-id: Specifies the router ID, in the format of an IPv4 address.
Usage guidelines
OSPF uses a router ID to identify a device. If no router ID is specified, the global router ID is used.
If no global router ID is configured, the highest loopback interface IP address is used as the router ID. If no loopback interface IP address is available, the highest physical interface IP address is used, regardless of the interface status (up or down).
During an active/standby switchover, the new active main processing unit (MPU) checks whether the previously backed up router ID is valid. If not, it selects a new router ID.
A new router ID is selected only when the interface IP address used as the router ID is removed or changed. Other events will not trigger a router ID re-selection. For example, router ID re-selection is not triggered in the following situations:
· The interface goes down.
· You change the router ID to the address of a loopback interface after a physical interface address is selected as the router ID.
· A higher interface IP address is configured as the router ID.
After a router ID is changed, you must use the reset command to enable it.
Examples
# Configure a global router ID as 1.1.1.1.
<Sysname> system-view
[Sysname] router id 1.1.1.1
silent-interface (OSPF view)
Use silent-interface to disable an interface or all interfaces from receiving and sending OSPF packets.
Use undo silent-interface to remove the configuration.
Syntax
silent-interface { interface-type interface-number | all }
undo silent-interface { interface-type interface-number | all }
Default
An interface can receive and send OSPF packets.
Views
OSPF view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
all: Specifies all interfaces.
Usage guidelines
To disable a network from receiving and sending OSPF routes, use the command on the interface connected to the network.
Examples
# Disable interface GigabitEthernet 1/0/1 from receiving and sending OSPF packets.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] silent-interface gigabitethernet 1/0/1
snmp trap rate-limit
Use snmp trap rate-limit to set the SNMP notification output interval and the maximum number of SNMP notifications that can be output at each interval.
Use undo snmp trap rate-limit to restore the default.
Syntax
snmp trap rate-limit interval trap-interval count trap-number
undo snmp trap rate-limit
Default
OSPF outputs a maximum of seven SNMP notifications within 10 seconds.
Views
OSPF view
Predefined user roles
network-admin
Parameters
interval trap-interval: Specifies the SNMP notification output interval in the range of 2 to 60 seconds.
count trap-number: Specifies the number of SNMP notifications output by OSPF at each interval, in the range of 0 to 300.
Examples
# Configure OSPF to output a maximum of 10 SNMP notifications within 5 seconds.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] snmp trap rate-limit interval 5 count 10
snmp-agent trap enable ospf
Use snmp-agent trap enable ospf to enable SNMP notifications for OSPF.
Use undo snmp-agent trap enable ospf to disable SNMP notifications for OSPF.
Syntax
snmp-agent trap enable ospf [ authentication-failure | bad-packet | config-error | grhelper-status-change | grrestarter-status-change | if-state-change | lsa-maxage | lsa-originate | lsdb-approaching-overflow | lsdb-overflow | neighbor-state-change | nssatranslator-status-change | retransmit | virt-authentication-failure | virt-bad-packet | virt-config-error | virt-retransmit | virtgrhelper-status-change | virtif-state-change | virtneighbor-state-change ] *
undo snmp-agent trap enable ospf [ authentication-failure | bad-packet | config-error | grhelper-status-change | grrestarter-status-change | if-state-change | lsa-maxage | lsa-originate | lsdb-approaching-overflow | lsdb-overflow | neighbor-state-change | nssatranslator-status-change | retransmit | virt-authentication-failure | virt-bad-packet | virt-config-error | virt-retransmit | virtgrhelper-status-change | virtif-state-change | virtneighbor-state-change ] *
Default
SNMP notifications for OSPF are enabled.
Views
System view
Predefined user roles
network-admin
Parameters
authentication-failure: Specifies notifications about authentication failures on an interface.
bad-packet: Specifies notifications about error messages received on an interface.
config-error: Specifies notifications about error configuration of an interface.
grhelper-status-change: Specifies notifications about GR helper state change.
grrestarter-status-change: Specifies notifications about GR restarter state change.
if-state-change: Specifies notifications about interface state change.
lsa-maxage: Specifies LSA max age notifications.
lsa-originate: Specifies notifications about locally generated LSAs.
lsdb-approaching-overflow: Specifies notifications about approaching LSDB overflows.
lsdb-overflow: Specifies LSDB overflow notifications.
neighbor-state-change: Specifies notifications about neighbor state change.
nssatranslator-status-change: Specifies notifications about NSSA translator state change.
retransmit: Specifies notifications about packets that are received and forwarded on an interface.
virt-authentication-failure: Specifies notifications about authentication failures on a virtual interface.
virt-bad-packet: Specifies notifications about error messages received on a virtual interface.
virt-config-error: Specifies notifications about error configuration of a virtual interface.
virt-retransmit: Specifies notifications about packets that are received and forwarded on a virtual interface.
virtgrhelper-status-change: Specifies notifications about neighbor GR helper state changes of a virtual interface.
virtif-state-change: Specifies notifications about virtual interface state change.
virtneighbor-state-change: Specifies notifications about the neighbor state change of a virtual interface.
Examples
# Disable SNMP notifications for OSPF.
<Sysname> system-view
[Sysname] undo snmp-agent trap enable ospf
spf-schedule-interval
Use spf-schedule-interval to set the OSPF SPF calculation interval.
Use undo spf-schedule-interval to restore the default.
Syntax
spf-schedule-interval { maximum-interval [ minimum-interval [ incremental-interval ] ] | millisecond interval }
undo spf-schedule-interval
Default
The maximum calculation interval is 5 seconds, the minimum interval is 50 milliseconds, and the incremental interval is 200 milliseconds.
Views
OSPF view
Predefined user roles
network-admin
Parameters
maximum-interval: Specifies the maximum OSPF SPF calculation interval in the range of 1 to 60 seconds.
minimum-interval: Specifies the minimum OSPF SPF calculation interval in the range of 10 to 60000 milliseconds.
incremental-interval: Specifies the incremental OSPF SPF calculation interval in the range of 10 to 60000 milliseconds.
millisecond interval: Specifies the fixed OSPF SPF calculation interval in the range of 0 to 10000 milliseconds.
Usage guidelines
Based on the LSDB, an OSPF router uses SPF to calculate a shortest path tree with itself as the root. OSPF uses the shortest path tree to determine the next hop to a destination. By adjusting the SPF calculation interval, you can prevent overconsumption of bandwidth and router resources due to frequent topology changes.
For a stable network, use the minimum interval set by the spf-schedule-interval maximum-interval [ minimum-interval [ incremental-interval ] ] command. If network changes become frequent, the SPF calculation interval is incremented by the incremental interval × 2n-2 for each calculation until the maximum interval is reached. The value n is the number of calculation times. The minimum interval and the incremental interval cannot be greater than the maximum interval.
For a network that requires fast route convergence, use the spf-schedule-interval millisecond interval command to set a short SPF calculation interval.
Examples
# Set the maximum SPF calculation interval to 10 seconds, minimum interval to 500 milliseconds, and incremental interval to 300 milliseconds.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] spf-schedule-interval 10 500 300
stub (OSPF area view)
Use stub to configure an area as a stub area.
Use undo stub to restore the default.
Syntax
stub [ default-route-advertise-always | no-summary ] *
undo stub
Default
No area is a stub area.
Views
OSPF area view
Predefined user roles
network-admin
Parameters
default-route-advertise-always: Enables the ABR to advertise a default route in a Type-3 LSA into the stub area regardless of whether FULL-state neighbors exist in the backbone area. If you do not specify this keyword, the ABR advertises a default route in a Type-3 LSA into the stub area only when a minimum of one FULL-state neighbor exists in the backbone area.
no-summary: Enables the ABR to advertise only a default route in a Type-3 LSA into the stub area without advertising any other Type-3 LSAs. The area is a totally stub area.
Usage guidelines
If you execute this command multiple times, the most recent configuration takes effect.
To configure an area as a stub area, use the stub command on all routers attached to the area.
Examples
# Configure Area 1 as a stub area.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] area 1
[Sysname-ospf-100-area-0.0.0.1] stub
default-cost (OSPF area view)
stub-router
Use stub-router to configure a router as a stub router.
Use undo stub-router to restore the default.
Syntax
stub-router [ external-lsa [ max-metric-value ] | include-stub | on-startup { seconds | wait-for-bgp [ seconds ] } | summary-lsa [ max-metric-value ] ] *
undo stub-router
Default
The router is not configured as a stub router.
Views
OSPF view
Predefined user roles
network-admin
Parameters
external-lsa max-metric-value: Specifies a cost for the external LSAs, in the range of 1 to 16777215. The default is 16711680.
include-stub: Specifies the cost of the stub links (link type 3) in Router LSAs to the maximum value 65535.
on-startup seconds: Specifies the router as a stub router during reboot, and specifies the timeout time in the range of 5 to 86400 seconds.
wait-for-bgp seconds: Specifies the router as a stub router during BGP route convergence after reboot, and specifies the timeout time in the range of 5 to 86400 seconds. The default timeout time is 600 seconds.
summary-lsa max-metric-value: Specifies a cost for the Type-3 LSAs, in the range of 1 to 16777215. The default cost value is 16711680.
Usage guidelines
The router LSAs sent by the stub router over different links contain different link type values. A value of 3 represents a link to a stub network, and the cost of the link is not changed. A value of 1, 2, or 4 represents a point-to-point link, a link to a transit network, or a virtual link. The cost of these links is set to 65535. Neighbors on such links will not send packets to the stub router as long as they have a route with a smaller cost.
Examples
# Configure a stub router.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] stub-router
transmit-pacing
Use transmit-pacing to set the LSU transmission interval and the maximum number of LSU packets that can be sent at each interval.
Use undo transmit-pacing to restore the default.
Syntax
transmit-pacing interval interval count count
undo transmit-pacing
Default
An OSPF interface sends a maximum of three LSU packets every 20 milliseconds.
Views
OSPF view
Predefined user roles
network-admin
Parameters
interval interval: Specifies an interval at which an interface sends LSU packets, in the range of 0 to 1000 milliseconds. If the router has multiple OSPF interfaces, increase this interval to reduce the total number of LSU packets sent by the router every second. As a best practice to maintain network stability, do not set the interval to 0 millseconds when the OSPF LSDB is large or network changes are frequent.
count count: Specifies the maximum number of LSU packets sent by an interface at each interval, in the range of 1 to 200. If the router has multiple OSPF interfaces, decrease the maximum number to reduce the total number of LSU packets sent by the router every second.
Examples
# Configure all the interfaces running OSPF process 1 to send a maximum of 10 LSU packets every 30 milliseconds.
<Sysname> system-view
[Sysname] ospf 1
[Sysname-ospf-1] transmit-pacing interval 30 count 10
ttl-security
Use ttl-security to enable OSPF GTSM for an area.
Use undo ttl-security to disable OSPF GTSM for an area.
Syntax
ttl-security [ hops hop-count ]
undo ttl-security
Default
OSPF GTSM is disabled for an OSPF area.
Views
OSPF area view
Predefined user roles
network-admin
Parameters
hops hop-count: Specifies the hop limit for checking OSPF packets, in the range of 1 to 254. The default hop limit is 1 for packets from common neighbors, and is 255 for packets from virtual link neighbors and sham link neighbors.
Usage guidelines
The GTSM configuration in OSPF area view applies to all OSPF interfaces in the area. GTSM checks OSPF packets from common neighbors and virtual link neighbors. It does not check OSPF packets from sham link neighbors.
GTSM protects the device by comparing the TTL value in the IP header of incoming OSPF packets against a valid TTL range. If the TTL value is within the valid TTL range, the packet is accepted. If not, the packet is discarded.
The valid TTL range is from 255 – the configured hop count + 1 to 255.
When GTSM is configured, the OSPF packets sent by the device have a TTL of 255. To use GTSM, you must configure GTSM on both the local and peer devices. You can specify different hop-count values for them.
The hops keyword configured in interface view takes precedence over the hops keyword configured in OSPF area view.
As a best practice, set the hop limit if a virtual link exists in an area. You can enable GTSM for the interfaces on the virtual link. If you do not know the interfaces on the virtual link, enable GTSM in area view to prevent packet loss.
Examples
# Enable OSPF GTSM for OSPF area 1.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] area 1
[Sysname-ospf-100-area-0.0.0.1] ttl-security
Related commands
ospf ttl-security
vlink-peer (OSPF area view)
Use vlink-peer to configure a virtual link.
Use undo vlink-peer to remove a virtual link.
Syntax
vlink-peer router-id [ dead seconds | hello seconds | { { hmac-md5 | md5 } key-id { cipher | plain } string | simple { cipher | plain } string } | retransmit seconds | trans-delay seconds ] *
undo vlink-peer router-id [ dead | hello | { hmac-md5 | md5 } key-id | retransmit | simple | trans-delay ] *
Default
No virtual links exist.
Views
OSPF area view
Predefined user roles
network-admin
Parameters
router-id: Specifies the router ID of the neighbor on the virtual link.
dead seconds: Specifies the dead interval in the range of 1 to 32768 seconds. The default is 40. The dead interval must be identical with that on the virtual link neighbor, and a minimum of four times the hello interval.
hello seconds: Specifies the hello interval in the range of 1 to 8192 seconds. The default is 10. It must be identical with the hello interval on the virtual link neighbor.
hmac-md5: Specifies the HMAC-MD5 authentication mode.
md5: Specifies the MD5 authentication mode.
simple: Specifies the simple authentication mode.
key-id: Specifies the key ID for MD5 or HMAC-MD5 authentication, in the range of 1 to 255.
cipher: Specifies a key in encrypted form.
plain: Specifies a key in plaintext form. For security purposes, the key specified in plaintext form will be stored in encrypted form.
string: Specifies the key. This argument is case sensitive.
· In simple authentication mode, the plaintext form of the key is a string of 1 to 8 characters. The encrypted form of the key is a string of 33 to 41 characters.
· In MD5/HMAC-MD5 authentication mode, the plaintext form of the key is a string of 1 to 16 characters. The encrypted form of the key is a string of 33 to 53 characters.
retransmit seconds: Specifies the retransmission interval in the range of 1 to 3600 seconds. The default is 5.
trans-delay seconds: Specifies the transmission delay interval in the range of 1 to 3600 seconds. The default is 1.
Usage guidelines
As defined in RFC 2328, all non-backbone areas must maintain connectivity to the backbone. You can use the vlink-peer command to configure a virtual link to connect an area to the backbone.
When you configure this command, follow these guidelines:
· The smaller the hello interval is, the faster the network converges, and the more network resources are consumed.
· A retransmission interval that is too small can cause unnecessary retransmissions. A large value is appropriate for a low speed link.
· Specify an appropriate transmission delay with the trans-delay keyword.
You can specify either MD5/HMAC-MD5 authentication or simple authentication for a virtual link. For MD5/HMAC-MD5 authentication, you can configure multiple keys by executing this command multiple times, and each command must have a unique key ID and key string.
To modify the key of a virtual link, perform the following key rollover configurations:
1. Configure a new MD5/HMAC-MD5 authentication key for the virtual link on the local device. If the new key is not configured on the neighbor device, MD5/HMAC-MD5 authentication key rollover is triggered. During key rollover, OSPF sends multiple packets that contain both the new and old MD5/HMAC-MD5 authentication keys to ensure that the neighbor device can pass the authentication.
2. Configure the new MD5/HMAC-MD5 authentication key on the neighbor device. When the local device receives packets with the new key from the neighbor device, it exits MD5 key rollover.
3. Delete the old MD5/HMAC-MD5 authentication key from the local device and the neighbor. This step helps prevent attacks from devices that use the old key for communication and reduces system resources and bandwidth consumption caused by key rollover.
Examples
# Configure a virtual link to the neighbor with router ID 1.1.1.1.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] area 2
[Sysname-ospf-100-area-0.0.0.2] vlink-peer 1.1.1.1
Related commands
authentication-mode
display ospf vlink
IS-IS commands
Commands and descriptions for centralized devices apply to the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS.
· MSR2600-6-X1/2600-10-X1.
· MSR 2630.
· MSR3600-28/3600-51.
· MSR3600-28-SI/3600-51-SI.
· MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC.
· MSR 3610/3620/3620-DP/3640/3660.
· MSR810-LM-GL/810-W-LM-GL/830-6EI-GL/830-10EI-GL/830-6HI-GL/830-10HI-GL/2600-6-X1-GL/3600-28-SI-GL.
Commands and descriptions for distributed devices apply to the following routers:
· MSR5620.
· MSR 5660.
· MSR 5680.
MTR is not supported on the 810-LMS/810-LUS routers.
address-family ipv4
Use address-family ipv4 to create the IS-IS IPv4 address family and enter its view.
Use undo address-family ipv4 to delete the IS-IS IPv4 address family and all configurations in the view.
Syntax
address-family ipv4 [ unicast ]
undo address-family ipv4 [ unicast ]
Default
No IS-IS IPv4 address family exists.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
unicast: Specifies the unicast address family (the default).
Examples
# Create the IS-IS IPv4 address family and enter its view.
<Sysname> system-view
[Sysname] isis 100
[Sysname-isis-100] address-family ipv4
[Sysname-isis-100-ipv4]
area-authentication send-only
Use area-authentication send-only to configure IS-IS not to check the authentication information in the received Level-1 packets, including LSPs, CSNPs, and PSNPs.
Use undo area-authentication send-only to restore the default.
Syntax
area-authentication send-only
undo area-authentication send-only
Default
When area authentication mode and key are configured, a Level-1 or Level-1-2 router checks the authentication information in the received packets.
Views
IS-IS view
Predefined user roles
network-admin
Usage guidelines
When area authentication mode and key are configured, a Level-1 or Level-1-2 router adds the key in the specified mode into transmitted Level-1 packets (including LSPs, CSNPs, and PSNPs). It also checks the key in the received Level-1 packets.
To prevent packet exchange failure in case of an authentication key change, configure IS-IS not to check the authentication information in the received packets.
Examples
# Configure IS-IS not to check the authentication information in the received packets.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] area-authentication send-only
Related commands
area-authentication-mode
domain-authentication send-only
isis authentication send-only
area-authentication-mode
Use area-authentication-mode to specify an area authentication mode and a key.
Use undo area-authentication-mode to restore the default.
Syntax
area-authentication-mode { { gca key-id { hmac-sha-1 | hmac-sha-224 | hmac-sha-256 | hmac-sha-384 | hmac-sha-512 } [ nonstandard ] | md5 | simple } { cipher | plain } string } | keychain keychain-name } [ ip | osi ]
undo area-authentication-mode
Default
No area authentication mode or key is configured.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
gca: Specifies the Generic Cryptographic Authentication (GCA) mode.
key-id: Uniquely identifies an SA in the range of 1 to 65535. The sender inserts the Key ID into the authentication TLV, and the receiver authenticates the packet by using the SA that is selected based on the Key ID.
hmac-sha-1: Specifies the HMAC-SHA-1 algorithm.
hmac-sha-224: Specifies the HMAC-SHA-224 algorithm.
hmac-sha-256: Specifies the HMAC-SHA-256 algorithm.
hmac-sha-384: Specifies the HMAC-SHA-384 algorithm.
hmac-sha-512: Specifies the HMAC-SHA-512 algorithm.
nonstandard: Specifies the nonstandard GCA mode.
md5: Specifies the MD5 authentication mode.
simple: Specifies the simple authentication mode.
cipher: Specifies a key in encrypted form.
plain: Specifies a key in plaintext form. For security purposes, the key specified in plaintext form will be stored in encrypted form.
string: Specifies the key. Its plaintext form is a case-sensitive string of 1 to 16 characters. Its encrypted form is a case-sensitive string of 33 to 53 characters.
keychain: Specifies the keychain authentication mode.
keychain-name: Specifies a keychain by its name, a case-sensitive string of 1 to 63 characters.
ip: Checks IP-related fields in LSPs.
osi: Checks OSI-related fields in LSPs.
The key in the specified mode is inserted into all outbound Level-1 packets (LSP, CSNP, and PSNP) and is used to authenticate inbound Level-1 packets.
IS-IS keychain authentication can operate correctly only when the keys in the keychain use the HMAC-MD5 authentication algorithm.
· Before IS-IS sends a Level-1 packet, it uses the valid send key obtained from the keychain to authenticate the packet. If no valid send key exists or the valid send key does not use the HMAC-MD5 algorithm, the authentication fails and the packet does not contain authentication information.
· After IS-IS receives a Level-1 packet, it uses a valid accept key obtained from the keychain to authenticate the packet. If no valid accept key exists or all valid accept keys fail to authenticate the packet, the authentication fails and the packet is discarded.
Area authentication enables IS-IS to discard routes from untrusted routers.
Routers in an area must have the same authentication mode and key.
If neither ip nor osi is specified, OSI-related fields are checked.
When you specify the GCA mode, follow these guidelines:
· If you do not specify the nonstandard keyword, the device can communicate only with devices that use the GCA mode.
· If you specify the nonstandard keyword, the device can communicate only with devices that use the nonstandard GCA mode.
Examples
# Set the area authentication mode to simple, and set the plaintext key to 123456.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] area-authentication-mode simple plain 123456
Related commands
area-authentication send-only
domain-authentication-mode
isis authentication-mode
auto-cost enable
Use auto-cost enable to enable automatic link cost calculation.
Use undo auto-cost enable to disable automatic link cost calculation.
Syntax
auto-cost enable
undo auto-cost enable
Default
Automatic link cost calculation is disabled.
Views
IS-IS view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Usage guidelines
After automatic link cost calculation is enabled, the link cost is automatically calculated based on the bandwidth reference value of an interface. When the cost-style is wide or wide-compatible, the cost value of an interface is calculated by using the following formula: Cost = (Reference bandwidth value / Link bandwidth) × 10. For other cost styles, Table 56 applies.
Table 56 Automatic cost calculation scheme for cost styles other than wide and wide-compatible
|
Interface bandwidth |
Cost |
|
≤10 Mbps |
60 |
|
≤100 Mbps |
50 |
|
≤155 Mbps |
40 |
|
≤622 Mbps |
30 |
|
≤2500 Mbps |
20 |
|
>2500 Mbps |
10 |
Examples
# Enable automatic link cost calculation for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] auto-cost enable
Related commands
bandwidth-reference
cost-style
isis cost
bandwidth-reference
Use bandwidth-reference to set the bandwidth reference value for automatic link cost calculation.
Use undo bandwidth-reference to restore the default.
Syntax
bandwidth-reference value
undo bandwidth-reference
Default
The bandwidth reference value is 100 Mbps.
Views
IS-IS view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
value: Specifies the bandwidth reference value in the range of 1 to 2147483648 Mbps.
Examples
# Set the bandwidth reference of IS-IS process 1 to 200 Mbps.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] bandwidth-reference 200
Related commands
auto-cost enable
isis cost
circuit-cost
Use circuit-cost to set a global IS-IS link cost.
Use undo circuit-cost to remove the configuration.
Syntax
circuit-cost cost-value [ level-1 | level-2 ]
undo circuit-cost [ level-1 | level-2 ]
Default
No global link cost is configured.
Views
IS-IS view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
cost-value: Specifies the link cost value. The value range varies by cost style.
· For styles narrow, narrow-compatible, and compatible, the cost value is in the range of 0 to 63.
· For styles wide and wide-compatible, the cost value is in the range of 0 to 16777215.
level-1: Applies the link cost to Level-1.
level-2: Applies the link cost to Level-2.
Usage guidelines
If no level is specified, the specified cost applies to both Level-1 and Level-2.
Examples
# Set the global Level-1 link cost to 11 for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] circuit-cost 11 level-1
Related commands
cost-style
isis cost
cost-style
Use cost-style to set a cost style.
Use undo cost-style to restore the default.
Syntax
cost-style { narrow | wide | wide-compatible | { compatible | narrow-compatible } [ relax-spf-limit ] }
undo cost-style
Default
The IS-IS cost style is narrow.
Views
Predefined user roles
network-admin
Parameters
narrow: Receives and sends only narrow cost style packets. The narrow cost is in the range of 0 to 63.
wide: Receives and sends only wide cost style packets. The wide cost is in the range of 0 to 16777215.
compatible: Receives and sends both wide and narrow cost style packets.
narrow-compatible: Receives both narrow and wide cost style packets, but sends only narrow cost style packets.
wide-compatible: Receives both narrow and wide cost style packets, but sends only wide cost style packets.
relax-spf-limit: Allows receiving routes with a cost greater than 1023. If you do not specify this keyword, routes with a cost bigger than 1023 will be discarded. This keyword is available only when compatible or narrow-compatible is used.
Examples
# Configure the router to send only narrow cost style packets, but receive both narrow and wide cost style packets.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] cost-style narrow-compatible
Related commands
circuit-cost
isis cost
default-route-advertise
Use default-route-advertise to advertise a default route of 0.0.0.0/0.
Use undo default-route-advertise to restore the default.
Syntax
default-route-advertise [ avoid-learning | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
undo default-route-advertise
Default
Default route advertisement is disabled.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
avoid-learning: Avoids learning the default route received in LSPs or generated by using the ATT bit to avoid routing loops.
level-1: Advertises a Level-1 default route.
level-1-2: Advertises both Level-1 and Level-2 default routes.
level-2: Advertises a Level-2 default route.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
tag tag: Specifies the tag value for the default route, in the range of 1 to 4294967295.
Usage guidelines
If no level is specified, a Level-2 default route is advertised.
The Level-1 default route is advertised to other routers in the same area, and the Level-2 default route is advertised to all the Level-2 and Level-1-2 routers.
You can use a routing policy to specify a level for the default route. The apply isis level-1 command in routing policy view can generate a Level-1 default route. The apply isis level-2 command in routing policy view can generate a Level-2 default route. The apply isis level-1-2 command in routing policy view can generate both a Level-1 default route and Level-2 default route.
The tag value specified in the routing policy takes precedence over the tag value specified in this command.
Examples
# Configure IS-IS process 1 to advertise a Level-2 default route.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] default-route-advertise
display isis
Use display isis to display configuration information for an IS-IS process.
Syntax
display isis [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays configuration information for all IS-IS processes.
Examples
# Display IS-IS configuration information.
<Sysname> display isis
IS-IS(1) Protocol Information
Network entity : 10.0000.0000.0001.00
IS level : level-1-2
Cost style : Wide
Fast reroute : Disabled
Preference : 15
LSP length receive : 1497
LSP length originate
level-1 : 1497
level-2 : 1497
Maximum imported routes : 1000
Timers
LSP-max-age : 1200
LSP-refresh : 900
SPF intervals : 5 50 200
IPv6 enabled
Multi-topology : Standard
Fast reroute : LFA
Preference : 15
Maximum imported routes : 1000
SPF intervals : 5 50 200
IPv4-Unicast
Topology red
Topology ID : 6
Preference : 15
Maximum imported routes : 1000000
SPF intervals : 5 50 200
Overload status : Overloaded manually
Table 57 Command output
|
Field |
Description |
|
Network entity |
Network entity name. |
|
IS level |
IS-IS routing level. |
|
Cost style |
Cost style. |
|
Fast-reroute |
IS-IS FRR status: · Disabled—IS-IS FRR is disabled. · LFA—IS-IS FRR automatically calculates a backup next hop. · Route-policy—IS-IS FRR specifies a backup next hop by using a routing policy. |
|
Preference |
IS-IS route preference. |
|
LSP length receive |
Maximum LSP that can be received. |
|
LSP length originate |
Maximum LSP that can be generated. |
|
Maximum imported routes |
Maximum number of redistributed Level-1/Level-2 IPv4/IPv6 routes. |
|
Timers |
Timers: · LSP-max-age—Maximum life period of LSPs. · LSP-refresh—Refresh interval of LSPs. · SPF intervals—Interval between SPF calculations. |
|
IPv6 enabled |
IPv6 is enabled. |
|
Multi-topology |
IPv6 unicast topology mode: · Standard—IPv6 unicast topology standard mode. · Compatible—IPv6 unicast topology compatible mode. |
display isis graceful-restart event-log
Use display isis graceful-restart event-log to display IS-IS GR log information.
Syntax
Centralized devices in standalone mode:
display isis graceful-restart event-log
Distributed devices in standalone mode/centralized devices in IRF mode:
display isis graceful-restart event-log slot slot-number
Distributed devices in IRF mode:
display isis graceful-restart event-log chassis chassis-number slot slot-number
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its ID. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument specifies the ID of the IRF member device. The slot-number argument specifies the slot number of the card. (Distributed devices in IRF mode.)
Examples
# Display IS-IS GR log information about card 0.
<Sysname> display isis graceful-restart event-log slot 1
IS-IS loginfo :
Sep 18 08:48:24 2015 slot 1 Process 1 enter GR restarting phase(Initialization).
Sep 18 08:48:24 2015 slot 1 Process 1 enter GR phase (LSDB synchronization).
Sep 18 08:48:24 2015 slot 1 Process 1 enter GR phase (TE tunnel prepare).
Sep 18 08:48:24 2015 slot 1 Process 1 enter GR phase (First SPF computation).
Sep 18 08:48:25 2015 slot 1 Process 1 enter GR phase (Redistribution).
Sep 18 08:48:25 2015 slot 1 Process 1 enter GR phase (Second SPF computation).
Sep 18 08:48:25 2015 slot 1 Process 1 enter GR phase (LSP stability).
Sep 18 08:48:25 2015 slot 1 Process 1 enter GR phase (LSP generation).
Sep 18 08:48:25 2015 slot 1 Process 1 enter GR phase (Finish).
Sep 18 08:48:25 2015 slot 1 Process 1 GR complete.
Table 58 Command output
|
Field |
Description |
|
GR phase |
GR phase: · Initialization. · LSDB synchronization. · TE tunnel prepare—Preparing for TE tunnel computation. · First SPF computation. · Redistribution. · Second SPF computation. · LSP stability—Ready to generate LSPs. · LSP generation. · Finish. |
display isis graceful-restart status
Use display isis graceful-restart status to display IS-IS GR state.
Syntax
display isis graceful-restart status [ level-1 | level-2 ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
level-1: Displays the IS-IS Level-1 GR state.
level-2: Displays the IS-IS Level-2 GR state.
process-id: Specifies a process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays GR state of all IS-IS processes.
Examples
# Display IS-IS GR state.
<Sysname> display isis graceful-restart status
Restart information for IS-IS(1)
--------------------------------
Restart status: COMPLETE
Restart phase: Finish
Restart t1: 3, count 10; Restart t2: 60; Restart t3: 300
SA Bit: supported
Level-1 restart information
---------------------------
Total number of interfaces: 1
Number of waiting LSPs: 0
Level-2 restart information
---------------------------
Total number of interfaces: 1
Number of waiting LSPs: 0
Table 59 Command output
|
Field |
Description |
|
Restart status |
Current GR state: · RESTARTING—In this state, forwarding can be ensured. · STARTING—In this state, forwarding cannot be ensured. · COMPLETE—GR is completed. |
|
Restart phase |
Current Restart phase: · Initialization. · LSDB synchronization. · First SPF computation. · Redistribution. · Second SPF computation. · LSP stability—Ready to generate LSPs. · LSP generation. · Finish. |
|
Restart t1 |
T1 timer, in seconds. |
|
count |
Number of T1 timer expirations. |
|
Restart t2 |
T2 timer, in seconds. |
|
Restart t3 |
T3 timer, in seconds. |
|
SA Bit |
Whether SA is supported. |
|
Total number of interfaces |
Total number of IS-IS interfaces. |
|
Number of waiting LSPs |
Number of LSPs not obtained by the GR restarter from GR helpers during LSDB synchronization. |
display isis interface
Use display isis interface to display IS-IS interface information.
Syntax
display isis interface [ [ interface-type interface-number ] [ verbose ] | statistics ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type interface-number: Displays information for a specified IS-IS interface. If you do not specify this argument, the command displays information about all interfaces.
verbose: Displays detailed information about an interface. If you do not specify this keyword, the command displays brief information about an interface.
statistics: Displays IS-IS interface statistics.
process-id: Displays IS-IS interface information for an IS-IS process specified by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays interface information for all IS-IS processes.
Examples
# Display brief IS-IS interface information.
<Sysname> display isis interface
Interface information for IS-IS(1)
----------------------------------
Interface: GigabitEthernet1/0/2
Index IPv4 state IPv6 state CircuitID MTU Type DIS
00001 Up Down 1 1497 L1/L2 No/No
# Display detailed IS-IS interface information.
<Sysname> display isis interface verbose
Interface information for IS-IS(1)
----------------------------------
Interface: GigabitEthernet1/0/2
Index IPv4 state IPv6 state CircuitID MTU Type DIS
00001 Up Down 1 1497 L1/L2 No/No
SNPA address : 000c-29e8-1bd5
IP address : 192.168.220.10
Secondary IP address(es) :
IPv6 link-local address :
Extended circuit ID : 1
CSNP timer value : L1 10 L2 10
Hello timer value : L1 10.00 L2 10.00
Hello multiplier value : L1 3 L2 3
LSP timer value : L12 33
LSP transmit-throttle count : L12 5
Cost : L1 100 L2 100
IPv6 cost : L1 10 L2 10
Priority : L1 64 L2 64
Retransmit timer value : L12 5
LDP state : L1 Init L2 No-LDP
LDP sync state : L1 Init L2 Achieved
MPLS TE status : L1 Disabled L2 Disabled
IPv4 BFD : Disabled
IPv6 BFD : Disabled
IPv4 FRR LFA backup : Enabled
IPv6 FRR LFA backup : Enabled
FRR LFA backup : Enabled
IPv4 prefix-suppression : Disabled
IPv6 prefix-suppression : Disabled
IPv4 tag : 1
IPv6 tag : 4294967295
IPv4 primary path detection mode: BFD ctrl
IPv6 primary path detection mode: BFD ctrl
IPv4-Unicast :
Topology ipv4_unicast_multopo
Topology ID : 6
Cost : L1 444 L2 444
FRR LFA backup : Disabled
Prefix-suppression : Enabled
Tag : 44444444
Table 60 Command output
|
Field |
Description |
|
Interface |
Interface type and number. |
|
Index |
Interface index. |
|
IPv4 state |
IPv4 state. |
|
IPv6 state |
IPv6 state. |
|
CircuitID |
Circuit ID. |
|
MTU |
Interface MTU. |
|
Type |
Interface link adjacency type. |
|
DIS |
Indicates whether the interface is elected as the Level-1/Level-2 DIS. In a P2P network, this field displays a hyphen (-) because DIS election is not performed. |
|
SNPA address |
Subnet access point address. |
|
IP address |
Primary IP address. |
|
Secondary IP address(es) |
Secondary IP addresses. |
|
IPv6 link-local address |
IPv6 link local address. |
|
Extended circuit ID |
Extended circuit ID for a P2P link. |
|
CSNP timer value |
Interval for sending CSNP packets. |
|
Hello timer value |
Interval for sending Hello packets. |
|
Hello multiplier value |
Number of invalid Hello packets. |
|
LSP timer value |
Minimum interval for sending LSP packets. |
|
LSP transmit-throttle count |
Number of LSP packets sent each time. |
|
Cost |
Cost of the interface. |
|
IPv6 cost |
IPv6 link cost of the interface. |
|
Priority |
DIS priority. |
|
Retransmit timer value |
Retransmission interval for LSPs on a P2P link. |
|
MPLS TE status |
MPLS TE status: Enabled or Disabled. |
|
LDP state |
LDP state: · Init—LDP is not reported. · No-LDP—LDP is not configured. · Not ready—LDP session is not established. · Ready—LDP session is established. |
|
LDP sync state |
LDP synchronization state: · Init—Initialized. · Achieved—Synchronized. · Max cost—Maintain the maximum cost. |
|
IPv4 BFD |
Whether BFD for IS-IS is enabled: · Disabled. · Enabled. |
|
IPv6 BFD |
Whether BFD for IPv6 IS-IS is enabled: · Disabled. · Enabled. |
|
IPv4 FRR LFA backup |
Whether LFA calculation is enabled for IPv4 FRR: · Disabled. · Enabled. |
|
IPv6 FRR LFA backup |
Whether LFA calculation is enabled for IPv6 FRR: · Disabled. · Enabled. |
|
IPv4 prefix-suppression |
Whether IPv4 IS-IS prefix suppression is enabled: · Disabled. · Enabled. |
|
IPv6 prefix-suppression |
Whether IPv6 IS-IS prefix suppression is enabled: · Disabled. · Enabled. |
|
IPv4 tag |
IPv4 tag value of the interface. |
|
IPv6 tag |
IPv6 tag value of the interface. |
|
IPv4 primary path detection mode |
IPv4 primary path detection mode: · BFD ctrl—BFD control packet mode. · BFD echo—BFD echo packet mode. |
|
IPv6 primary path detection mode |
IPv6 primary path detection mode: · BFD ctrl—BFD control packet mode. · BFD echo—BFD echo packet mode. |
|
IPv4-Unicast |
IPv4 unicast topology supported by the interface. |
|
Topology |
IPv4 unicast topology name. |
|
Topology ID |
IPv4 unicast topology ID. |
# Display IS-IS interface statistics.
<Sysname> display isis interface statistics
Interface statistics information for IS-IS(1)
--------------------------------------------
Type IPv4 up/down IPv6 up/down
LAN 1/0 0/0
P2P 0/0 0/0
Table 61 Command output
|
Field |
Description |
|
Type |
Network type of the interface: · LAN—Broadcast network. · P2P—Point-to-point network. |
|
IPv4 up |
Number of IS-IS interfaces in up state. |
|
IPv4 down |
Number of IS-IS interfaces in down state. |
|
IPv6 up |
Number of IS-ISv6 interfaces in up state. |
|
IPv6 down |
Number of IS-ISv6 interfaces in down state. |
display isis lsdb
Use display isis lsdb to display IS-IS LSDB information.
Syntax
display isis lsdb [ [ level-1 | level-2 ] | local | [ lsp-id lspid | lsp-name lspname ] | verbose ] * [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
level-1: Displays the level-1 LSDB.
level-2: Displays the level-2 LSDB.
local: Displays LSP information generated locally.
lsp-id lspid: Specifies an LSP ID, in the form of sysID. Pseudo ID-fragment num, where sysID represents the originating node or pseudo node. Pseudo ID is separated by a dot from sysID and by a hyphen from fragment num.
lsp-name lspname: Specifies the LSP name, in the form of Symbolic name.Pseudo ID-fragment num, where Pseudo ID is separated by a dot from Symbolic name and by a hyphen from fragment num. If the Pseudo ID is 0, specify the LSP name in the form Symbolic name-fragment num.
verbose: Displays LSDB detailed information. If you do not specify this keyword, the command displays brief information about LSDB.
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays LSDBs for all IS-IS processes.
Usage guidelines
If no level is specified, the command displays both Level-1 and Level-2 LSDB information.
Examples
# Display brief Level-1 LSDB information.
<Sysname> display isis lsdb level-1
Database information for IS-IS(1)
--------------------------------
Level-1 Link State Database
---------------------------
LSPID Seq Num Checksum Holdtime Length ATT/P/OL
-------------------------------------------------------------------------------
0000.0000.0001.00-00* 0x00000087 0xf846 1152 183 0/0/0
0000.0000.0003.00-00 0x00000005 0x4bee 520 177 0/0/0
0000.0000.0003.00-01 0x00000004 0x7245 520 45 0/0/0
0000.0000.0011.00-00 0x0000000b 0xcdf6 815 183 0/0/0
*-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload
# Display detailed Level-1 LSDB information.
<Sysname> display isis lsdb level-1 verbose
Database information for IS-IS(1)
--------------------------------
Level-1 Link State Database
---------------------------
LSPID Seq Num Checksum Holdtime Length ATT/P/OL
-------------------------------------------------------------------------------
0000.0000.0001.00-00* 0x00000080 0x73f 1185 183 0/0/0
Source 0000.0000.0001.00
NLPID IPv4
Area address 10
IPv4 address 192.168.220.10
MT ID 0000 (-/-)
MT ID 0002 (-/-)
MT ID 0006 (-/-)
+NBR ID
0000.0000.0011.00 Cost: 100
Admin group: 0x00000000
Physical bandwidth: 12500000 bytes/sec
Reservable bandwidth: 0 bytes/sec
Unreserved bandwidth for each TE class:
TE class 0: 0 bytes/sec TE class 1: 0 bytes/sec
TE class 2: 0 bytes/sec TE class 3: 0 bytes/sec
TE class 4: 0 bytes/sec TE class 5: 0 bytes/sec
TE class 6: 0 bytes/sec TE class 7: 0 bytes/sec
TE class 8: 0 bytes/sec TE class 9: 0 bytes/sec
TE class 10: 0 bytes/sec TE class 11: 0 bytes/sec
TE class 12: 0 bytes/sec TE class 13: 0 bytes/sec
TE class 14: 0 bytes/sec TE class 15: 0 bytes/sec
TE cost: 10
Bandwidth constraint model: Prestandard DS-TE RDM
Bandwidth constraints:
BC[0] : 0 bytes/sec BC[1] : 0 bytes/sec
Neighbor IP address: 192.168.220.30
Interface IP address: 192.168.220.10
IPv6 unicast NBR ID
6464.6464.6464.01 Cost: 10 MT ID: 2
MT NBR ID
6464.6464.6464.01 Cost: 10 MT ID: 6
+IP-Extended
192.168.220.0 255.255.255.0 Cost: 100
IPv4 unicast
1.1.1.1 255.255.255.255 Cost: 0 MT ID: 6
IPv4 unicast
10.10.10.0 255.255.255.0 Cost: 10 MT ID: 6
IPv6 unicast
1:1:1::1/128 Cost: 0 MT ID: 2
IPv6 unicast
10:10:10::/64 Cost: 10 MT ID: 2
Router ID 1.1.1.1
0000.0000.0003.00-00 0x00000005 0x4bee 887 177 0/0/0
Source 0000.0000.0003.00
NLPID IPv4
Area address 10
IPv4 address 10.10.10.10
IPv4 address 192.168.220.20
+NBR ID
0000.0000.0001.00 Cost: 10
Admin group: 0x00000000
Physical bandwidth: 12500000 bytes/sec
Reservable bandwidth: 0 bytes/sec
Unreserved bandwidth for each TE class:
TE class 0: 0 bytes/sec TE class 1: 0 bytes/sec
TE class 2: 0 bytes/sec TE class 3: 0 bytes/sec
TE class 4: 0 bytes/sec TE class 5: 0 bytes/sec
TE class 6: 0 bytes/sec TE class 7: 0 bytes/sec
TE class 8: 0 bytes/sec TE class 9: 0 bytes/sec
TE class 10: 0 bytes/sec TE class 11: 0 bytes/sec
TE class 12: 0 bytes/sec TE class 13: 0 bytes/sec
TE class 14: 0 bytes/sec TE class 15: 0 bytes/sec
TE cost: 10
Bandwidth constraint model: Prestandard DS-TE RDM
Bandwidth constraints:
BC[0]: 0 bytes/sec BC[1]: 0 bytes/sec
Interface IP address: 192.168.220.20
Neighbor IP address: 192.168.220.10
Router ID 3.3.3.3
0000.0000.0003.00-01 0x00000004 0x7245 887 45 0/0/0
Source 0000.0000.0003.00
+IP-Extended
10.10.10.0 255.255.255.0 Cost: 10
+IP-Extended
192.168.220.0 255.255.255.0 Cost: 10
*-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload
Table 62 Command output
|
Field |
Description |
|
LSPID |
LSP ID. |
|
Seq Num |
LSP sequence number. |
|
Checksum |
LSP checksum. |
|
Holdtime |
LSP lifetime, which decreases as time elapses. |
|
Length |
LSP length. |
|
ATT/P/OL |
· ATT—Attach bit. · P—Partition bit. · OL—Overload bit. 1 means the LSP bit is set and 0 means the LSP bit is not set. |
|
Source |
System ID of the originating router. |
|
HOST NAME |
Dynamic host name of the originating router. |
|
ORG ID |
Original system ID of the virtual system of the originating router. |
|
NLPID |
Network layer protocol the originating router runs. |
|
Area address |
Area address of the originating router. |
|
IPv4 address |
IP address of the originating router's IS-IS interface. |
|
IPv6 address |
IPv6 address of the originating router's IS-ISv6 interface. |
|
MT ID 0000 (-/-) MT ID 0002 (-/-) MT ID 0006 (-/-) |
Topology supported by the originating router (0/0/0 indicates ATT/P/OL): · 0000—Base topology. · 0002—IPv6 unicast topology. · 0006—IPv4 unicast topology. · (-/-)—Attach bit/overload bit. |
|
NBR ID |
Neighbor ID of the originating router. |
|
MT NBR ID |
IPv4 unicast topology neighbor information about the originating router. |
|
IPv6 unicast NBR ID |
IPv6 unicast neighbor information about the originating router. |
|
Admin group |
Link management group attribute. |
|
Interface IP address |
IP address of the interface connected to the remote end. |
|
Neighbor IP address |
Neighbor interface IP address. |
|
Physical bandwidth |
Physical bandwidth. |
|
Reservable bandwidth |
Reserved bandwidth. |
|
Unreserved bandwidth for each TE class |
Available bandwidth reserved for each TE class. |
|
TE class |
Available bandwidth for each of the 8 or 16 TE classes. |
|
TE cost |
TE cost. |
|
Bandwidth constraint model |
Bandwidth constraint model: · Prestandard DS-TE RDM. · IETF DS-TE RDM. · IETF DS-TE MAM. |
|
BC |
Bandwidth constraint value. The Prestandard model supports 2 BCs, and the IETF modes support a maximum of 8 BCs. |
|
Router ID |
Router ID. |
|
IP-Internal |
Internal IP address and mask of the originating router. |
|
IP-External |
External IP address and mask of the originating router. |
|
IP-Extended |
Extended IP address and mask of the originating router. |
|
Cost |
Cost. |
|
Auth |
Authentication information of the originating router. |
|
IPV6 |
Internal IPv6 address and prefix of the originating router. |
|
IPV6-Ext |
External IPv6 address and prefix of the originating router. |
|
IPv4 unicast |
IPv4 unicast reachability information about the originating router. |
|
IPv6 unicast |
Internal IPv6 unicast reachability information about the originating router. |
|
IPv6 unicast-ext |
External IPv6 unicast reachability information about the originating router. |
display isis mesh-group
Use display isis mesh-group to display IS-IS mesh group configuration information.
Syntax
display isis mesh-group [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Displays IS-IS mesh-group configuration for an IS-IS process specified by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays IS-IS mesh group configuration information for all IS-IS processes.
Examples
# Add Serial 2/1/0 and Serial 2/1/1 to mesh group 100.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] isis mesh-group 100
[Sysname-Serial2/1/0] quit
[Sysname] interface serial 2/1/1
[Sysname-Serial2/1/1] isis mesh-group 100
# Display IS-IS mesh-group configuration information.
[Sysname-Serial2/1/1] display isis mesh-group
Mesh Group information for IS-IS(1)
----------------------------------------------------------------------
Interface Status
Serial2/1/0 Blocked
Serial2/1/1 100
Table 63 Command output
|
Field |
Description |
|
Interface |
Interface name. |
|
Status |
Mesh group the interface belongs to/whether a blocked interface is configured. |
display isis name-table
Use display isis name-table to display the host name-to-system ID mapping table.
Syntax
display isis name-table [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Displays the host name to system ID mapping table for an IS-IS process specified by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays the host name to system ID mapping table for all IS-IS processes.
Examples
# Display the IS-IS host name to system ID mapping table.
<Sysname> display isis name-table
Name table information for IS-IS(1)
-----------------------------------
System ID Hostname Type Level
6789.0000.0001 RUTA DYNAMIC Level-1
6789.0000.0001 RUTA DYNAMIC Level-2
0000.0000.0041 RUTB STATIC Level-1
0000.0000.0041 RUTB STATIC Level-2
6789.0000.0001.01 DIS-A DYNAMIC Level-1
0000.0000.0041.01 DIS-B DYNAMIC Level-2
Table 64 Command output
|
Field |
Description |
|
System ID |
System ID. |
|
Hostname |
Host name. |
|
Type |
Mapping type: · STATIC. · DYNAMIC. |
|
Level |
Level on which the system ID-to-host name mapping takes effect: Level-1 or Level-2. |
display isis non-stop-routing event-log
Use display isis non-stop-routing event-log to display IS-IS NSR log information.
Syntax
Distributed devices in standalone mode/centralized devices in IRF mode:
display isis non-stop-routing event-log slot slot-number
Distributed devices in IRF mode:
display isis non-stop-routing event-log chassis chassis-number slot slot-number
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its ID. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument specifies the ID of the IRF member device. The slot-number argument specifies the slot number of the card. (Distributed devices in IRF mode.)
Usage guidelines
The following matrix shows the command and hardware compatibility:
|
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28/3600-51 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28-SI/3600-51-SI |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
· In standalone mode: No · In IRF mode: Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Command compatibility |
|
MSR810-LM-GL |
No |
|
MSR810-W-LM-GL |
No |
|
MSR830-6EI-GL |
No |
|
MSR830-10EI-GL |
No |
|
MSR830-6HI-GL |
No |
|
MSR830-10HI-GL |
No |
|
MSR2600-6-X1-GL |
No |
|
MSR3600-28-SI-GL |
No |
Examples
# Display IS-IS NSR log information.
<Sysname> display isis non-stop-routing event-log slot 1
IS-IS loginfo :
Sep 18 10:20:44 2015 slot 1 Enter HA Block status
Sep 18 10:20:44 2015 slot 1 Exit HA Block status
Sep 18 10:24:00 2015 slot 1 Process 100 enter NSR phase (Initialization).
Sep 18 10:24:00 2015 slot 1 Process 100 enter NSR phase (Smooth).
Sep 18 10:24:00 2015 slot 1 Process 100 enter NSR phase (TE tunnel prepare).
Sep 18 10:24:00 2015 slot 1 Process 100 enter NSR phase (First SPF computation).
Sep 18 10:24:00 2015 slot 1 Process 100 enter NSR phase (Redistribution).
Sep 18 10:24:00 2015 slot 1 Process 100 enter NSR phase (Second SPF computation).
Sep 18 10:24:00 2015 slot 1 Process 100 enter NSR phase (LSP stability).
Sep 18 10:24:00 2015 slot 1 Process 100 enter NSR phase (LSP generation).
Sep 18 10:24:00 2015 slot 1 Process 100 enter NSR phase (Finish).
Sep 18 10:24:00 2015 slot 1 Process 100 NSR complete.
Table 65 Command output
|
Field |
Description |
|
NSR phase |
NSR phase: · Initialization. · Smooth. · TE tunnel prepare—Preparing for TE tunnel computation. · First SPF computation. · Redistribution. · Second SPF computation. · LSP stability—Ready to generate LSPs. · LSP generation. · Finish. |
display isis non-stop-routing status
Use display isis non-stop-routing status to display IS-IS NSR status.
Syntax
display isis non-stop-routing status
Views
Any view
Predefined user roles
network-admin
network-operator
Usage guidelines
The following matrix shows the command and hardware compatibility:
|
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28/3600-51 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28-SI/3600-51-SI |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
· In standalone mode: No · In IRF mode: Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Command compatibility |
|
MSR810-LM-GL |
No |
|
MSR810-W-LM-GL |
No |
|
MSR830-6EI-GL |
No |
|
MSR830-10EI-GL |
No |
|
MSR830-6HI-GL |
No |
|
MSR830-10HI-GL |
No |
|
MSR2600-6-X1-GL |
No |
|
MSR3600-28-SI-GL |
No |
Examples
# Display IS-IS NSR status.
<Sysname> display isis non-stop-routing status
Nonstop Routing information for IS-IS(1)
----------------------------------------
NSR phase: Finish
Table 66 Command output
|
Field |
Description |
|
NSR phase |
NSR phase: · Initialization. · Smooth. · First SPF computation. · Redistribution. · Second SPF computation. · LSP stability—Ready to generate LSPs. · LSP generation. · Finish. |
display isis peer
Use display isis peer to display IS-IS neighbor information.
Syntax
display isis peer [ statistics | verbose ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
statistics: Displays IS-IS neighbor statistics.
verbose: Displays detailed IS-IS neighbor information. If you do not specify this keyword, the command displays brief IS-IS neighbor information.
process-id: Displays IS-IS neighbor information for an IS-IS process specified by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays neighbor information for all IS-IS processes.
Examples
# Display brief IS-IS neighbor information.
<Sysname> display isis peer
Peer information for IS-IS(1)
-----------------------------
System ID: 0000.0000.0001
Interface: GE1/0/2 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 27s Type: L1(L1L2) PRI: 64
System ID: 0000.0000.0001
Interface: GE1/0/2 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 27s Type: L2(L1L2) PRI: 64
# Display detailed IS-IS neighbor information.
<Sysname> display isis peer verbose
Peer information for IS-IS(1)
----------------------------
System ID: 0000.1111.2222
Interface: GE1/0/2 Circuit Id: 0000.1111.2222.01
State: Up Holdtime: 6s Type: L1(L1L2) PRI: 64
Area address(es): 49
Peer IP address(es): 12.0.0.2
Peer local circuit ID: 1
Peer circuit SNPA address: 000c-293b-c4be
Uptime: 00:05:07
Adj protocol: IPv4
Adj P2P three-way handshake: No
Graceful Restart capable
Restarting signal: No
Suppress adjacency advertisement: No
Local topology:
0 2
Remote topology:
0 2
System ID: 0000.0000.0002
Interface: GE1/0/3 Circuit Id: 001
State: Up HoldTime: 27s Type: L1L2 PRI: --
Area address(es): 49
Peer IP address(es): 192.168.220.30
Peer local circuit ID: 1
Peer circuit SNPA address: 000c-29fd-ed69
Uptime: 00:05:07
Adj protocol: IPv4
Adj P2P three-way handshake: Yes
Peer extended circuit ID: 2
Graceful Restart capable
Restarting signal: No
Suppress adjacency advertisement: No
Table 67 Command output
|
Field |
Description |
|
System Id |
System ID of the neighbor. |
|
Interface |
Interface connecting to the neighbor. |
|
Circuit Id |
Circuit ID. |
|
State |
Circuit state. |
|
HoldTime |
Within the holdtime, if no hellos are received from the neighbor, the neighbor is considered down. If a hello is received, the holdtime is reset to the initial value. |
|
Type |
Circuit type: · L1—Means the circuit type is Level-1 and the neighbor is a Level-1 router. · L2—Means the circuit type is Level-2 and the neighbor is a Level-2 router. · L1(L1L2)—Means the circuit type is Level-1 and the neighbor is a Level-1-2 router. · L2(L1L2)—Means the circuit type is Level-2 and the neighbor is a Level-1-2 router. |
|
PRI |
DIS priority of the neighbor. |
|
Area address(es) |
Area address of the neighbor. |
|
Peer IP address(es) |
IP address of the neighbor. |
|
Peer IPv6 address(es) |
IPv6 address of the neighbor. |
|
Uptime |
Time elapsed since the neighbor relationship was formed. |
|
Adj Protocol |
Adjacency protocol. |
|
Peer local circuit ID |
Circuit ID of the neighbor. |
|
Peer circuit SNPA address |
SNPA address of the neighbor. |
|
Adj P2P three-way handshake |
Indicates whether the neighbor supports P2P three-way handshake. |
|
Peer extended circuit ID |
Extended circuit ID of the neighbor interface. This field is available when the neighbor supports three-way handshake. |
|
Graceful Restart capable |
The neighbor has the GR helper capability. |
|
Restarting signal |
RR flag. |
|
Suppress adjacency advertisement |
SA flag. |
|
Local topology |
List of topologies supported by the local interface. |
|
Remote topology |
List of topologies supported by the neighbor interface. |
# Display IS-IS neighbor statistics.
<Sysname> display isis peer statistics
Peer Statistics information for IS-IS(1)
---------------------------------------
Type IPv4 Up/Init IPv6 Up/Init
LAN Level-1 1/0 0/0
LAN Level-2 1/0 0/0
P2P 0/0 0/0
Table 68 Command output
|
Field |
Description |
|
Type |
Neighbor type: · LAN Level-1—Number of Level-1 neighbors whose network type is broadcast. · LAN Level-2—Number of Level-2 neighbors whose network type is broadcast. · P2P—Number of neighbors whose network type is P2P. |
|
IPv4 Up |
Number of IPv4 neighbors in up state. |
|
IPv4 Init |
Number of IPv4 neighbors in init state. |
|
IPv6 Up |
Number of IPv6 neighbors in up state. |
|
IPv6 Init |
Number of IPv6 neighbors in init state. |
display isis redistribute
Use display isis redistribute to display the redistributed IS-IS routing information.
Syntax
display isis redistribute [ ipv4 [ topology topo-name ] [ ip-address mask-length ] ] [ level-1 | level-2 ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv4: Displays the redistributed IPv4 routing information (the default).
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays redistributed IS-IS routing information for the public network.
ip-address mask-length: Specifies the destination IP address and mask length.
process-id: Specifies the IS-IS process by its ID in the range of 1 to 65535.
level-1: Displays the IS-IS Level-1 routing information.
level-2: Displays the IS-IS Level-2 routing information.
Usage guidelines
If you do not specify an IS-IS level, this command displays both Level-1 and Level-2 routing information.
Examples
# Display redistributed IPv4 routing information.
<Sysname> display isis redistribute 1
Route information for IS-IS(1)
------------------------------
Level-1 IPv4 Redistribute Table
--------------------------------
Type IPv4 Destination IntCost ExtCost Tag State
--------------------------------------------------------------------------------
D 192.168.30.0/24 0 0 Active
D 11.11.11.11/32 0 0
D 10.10.10.0/24 0 0
Type: D -Direct, I -ISIS, S -Static, O -OSPF, B -BGP, R –RIP, E -EIGRP
Table 69 Command output
|
Field |
Description |
|
Route information for IS-IS(1) |
IS-IS process of the redistributed routing information. |
|
Level-1 IPv4 Redistribute Table |
Redistributed IPv4 routing information of IS-IS Level-1. |
|
Level-2 IPv4 Redistribute Table |
Redistributed IPv4 routing information of IS-IS Level-2. |
|
Type |
Redistributed route type: · Direct. · IS-IS. · Static. · OSPF. · BGP. · RIP. · EIGRP. |
|
IPV4 Destination |
IPv4 destination address. |
|
IntCost |
Internal cost of the route. |
|
ExtCost |
External cost of the route. |
|
Tag |
Tag value. |
|
State |
Indicates whether the route is valid. |
display isis route
Use display isis route to display IS-IS IPv4 routing information.
Syntax
display isis route [ ipv4 [ topology topo-name ] [ ip-address mask-length ] ] [ [ level-1 | level-2 ] | verbose ] * [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv4: Displays IS-IS IPv4 routing information (the default).
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays IS-IS IPv4 routing information for the public network.
ip-address mask-length: Displays IS-IS IPv4 routing information for the specified IP address. The mask-length argument is in the range of 0 to 32.
verbose: Displays detailed IS-IS IPv4 routing information. If you do not specify this keyword, the command displays brief IS-IS IPv4 routing information
process-id: Displays IS-IS IPv4 routing information for an IS-IS process specified by its ID in the range of 1 to 65535.
level-1: Displays Level-1 IS-IS routes.
level-2: Displays Level-2 IS-IS routes.
Usage guidelines
If you do not specify a level, this command displays both Level-1 and Level-2 routing information.
If you do not specify an IS-IS process ID, this command displays routing information for all IS-IS process IDs.
Examples
# Display brief IS-IS IPv4 routing information.
<Sysname> display isis route
Route information for IS-IS(1)
-----------------------------
Level-1 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
8.8.8.0/24 10 NULL GE1/0/2 Direct D/L/-
9.9.9.0/24 20 NULL GE1/0/2 8.8.8.5 R/L/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Level-2 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
8.8.8.0/24 10 NULL D/L/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Table 70 Command output
|
Field |
Description |
|
Route information for IS-IS(1) |
Route information for IS-IS process 1. |
|
Level-1 IPv4 Forwarding Table |
IS-IS IPv4 routing information for Level-1. |
|
Level-2 IPv4 Forwarding Table |
IS-IS IPv4 routing information for Level-2. |
|
IPv4 Destination |
IPv4 destination address. |
|
IntCost |
Internal cost. |
|
ExtCost |
External cost. |
|
ExitInterface |
Output interface. |
|
NextHop |
Next hop. |
|
Flags |
Routing state flag: · D—Direct route. · R—The route has been added into the routing table. · L—The route has been advertised in an LSP. · U—Penetration flag. Setting it to UP can prevent an LSP sent from L2 to L1 from being sent back to L2. |
# Display detailed IS-IS IPv4 routing information.
<Sysname> display isis route verbose
Route information for IS-IS(1)
-----------------------------
Level-1 IPv4 Forwarding Table
-----------------------------
IPV4 Dest : 8.8.8.0/24 Int. Cost : 10 Ext. Cost : NULL
Admin Tag : - Src Count : 2 Flag : D/L/-
NextHop : Interface : ExitIndex :
Direct GE1/0/2 0x00000000
Nib ID : 0x0
IPV4 Dest : 9.9.9.0/24 Int. Cost : 20 Ext. Cost : NULL
Admin Tag : - Src Count : 1 Flag : R/L/-
NextHop : Interface : ExitIndex :
8.8.8.5 GE1/0/2 0x00000003
Nib ID : 0x0
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Level-2 IPv4 Forwarding Table
-----------------------------
IPV4 Dest : 8.8.8.0/24 Int. Cost : 10 Ext. Cost : NULL
Admin Tag : - Src Count : 2 Flag : D/L/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Table 71 Command output
|
Field |
Description |
|
Route information for IS-IS(1) |
Route information for IS-IS process 1. |
|
Level-1 IPv4 Forwarding Table |
IS-IS IPv4 routing information for Level-1. |
|
Level-2 IPv4 Forwarding Table |
IS-IS IPv4 routing information for Level-2. |
|
IPV4 Dest |
IPv4 destination. |
|
Int. Cost |
Internal cost. |
|
Ext. Cost |
External cost. |
|
Admin Tag |
Tag. |
|
Src Count |
Count of advertising sources. |
|
Flag |
Route state flag: · R—The route has been installed into the routing table. · L—The route has been flooded in an LSP. · U—Route leaking flag. Setting it to UP can prevent an LSP sent from L2 to L1 from being sent back to L2. |
|
Next Hop |
Next hop. |
|
Interface |
Output interface. |
|
ExitIndex |
Index of the output interface. |
|
Nib ID |
ID assigned by the routing management module (next hop index). |
display isis spf-tree
Use display isis spf-tree to display IS-IS IPv4 topology information.
Syntax
display isis spf-tree [ ipv4 [ topology topo-name ] ] [ [ level-1 | level-2 ] | verbose ] * [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv4: Displays IS-IS IPv4 topology information. If you do not specify this keyword, the command displays IS-IS IPv4 topology information.
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays IS-IS IPv4 topology information for the public network.
level-1: Displays Level-1 IS-IS topology information. If you do not specify a level, the command displays both Level-1 and Level 2 topology information.
level-2: Displays Level-2 IS-IS topology information. If you do not specify a level, the command displays both Level-1 and Level 2 topology information.
verbose: Displays detailed IS-IS topology information. If you do not specify this keyword, the command displays brief topology information.
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays topology information for all IS-IS processes.
Examples
# Display brief IS-IS IPv4 topology information.
<Sysname> display isis spf-tree
Shortest Path Tree for IS-IS(1)
-------------------------------
Flags: S-Node is on SPF tree T-Node is on tent list
O-Node is overload R-Node is directly reachable
I-Node or Link is isolated D-Node or Link is to be deleted
C-Neighbor is child P-Neighbor is parent
V-Link is involved N-Link is a new path
L-Link is on change list U-Protocol usage is changed
H-Nexthop is changed
Level-1 Shortest Path Tree
--------------------------
SpfNode NodeFlag SpfLink LinkCost LinkFlag
-------------------------------------------------------------------------------
0000.0000.0032.00 S/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/C/-/-/-/-/-/-
-->0000.0000.0064.00 10 -/-/C/-/-/-/-/-/-
0000.0000.0032.01 S/-/-/R/-/-
-->0000.0000.0064.00 0 -/-/C/-/-/-/-/-/-
-->0000.0000.0032.00 0 -/-/-/P/-/-/-/-/-
0000.0000.0064.00 S/-/-/R/-/-
-->0000.0000.0032.00 10 -/-/-/P/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/-/P/-/-/-/-/-
Level-2 Shortest Path Tree
--------------------------
SpfNode NodeFlag SpfLink LinkCost LinkFlag
-------------------------------------------------------------------------------
0000.0000.0032.00 S/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/C/-/-/-/-/-/-
-->0000.0000.0064.00 10 -/-/C/-/-/-/-/-/-
0000.0000.0032.01 S/-/-/R/-/-
-->0000.0000.0064.00 0 -/-/C/-/-/-/-/-/-
-->0000.0000.0032.00 0 -/-/-/P/-/-/-/-/-
0000.0000.0064.00 S/-/-/R/-/-
-->0000.0000.0032.00 10 -/-/-/P/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/-/P/-/-/-/-/-
# Display detailed IS-IS IPv4 topology information.
<Sysname> display isis spf-tree verbose
Shortest Path Tree for IS-IS(1)
-------------------------------
Flags: S-Node is on SPF tree T-Node is on tent list
O-Node is overload R-Node is directly reachable
I-Node or Link is isolated D-Node or Link is to be deleted
C-Neighbor is child P-Neighbor is parent
V-Link is involved N-Link is a new path
L-Link is on change list U-Protocol usage is changed
H-Nexthop is changed
Level-1 Shortest Path Tree
--------------------------
SpfNode : 0000.0000.0001.00
Distance : 0
TE distance : 0
NodeFlag : S/-/-/-/-/-
RelayNibID : 0x0
TE tunnel count: 0
Nexthop count : 0
SpfLink count : 1
-->0000.0000.0004.04
LinkCost : 10
LinkNewCost : 10
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type: Adjacent Interface: N/A
Cost: 10 Nexthop : N/A
SpfNode : 0000.0000.0004.00
Distance : 10
Te Distance : 10
NodeFlag : S/-/-/-/-/-
RelayNibID : 0x14000000
TE tunnel count: 1
Destination: 4.4.4.4 Interface : Tun0
TE cost : 10 Final cost : 10
Add nexthop: YES Add TLV : YES
Nexthop count : 2
Neighbor : 0000.0000.0004.00 Interface : Tun0
Nexthop : 4.4.4.4
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
Neighbor : 0000.0000.0004.00 Interface : GE1/0/1
Nexthop : 1.1.1.3
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
SpfLink count : 1
-->0000.0000.0004.04
LinkCost : 10
LinkNewCost : 10
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type: Remote Interface: N/A
Cost: 10 Nexthop : N/A
AdvMtID: 0
SpfNode : 0000.0000.0004.04
Distance : 10
TE distance : 10
NodeFlag : S/-/-/R/-/-
RelayNibID : 0x14000001
TE tunnel count: 0
Nexthop count : 0
SpfLink count : 2
-->0000.0000.0001.00
LinkCost : 0
LinkNewCost : 0
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type: Remote Interface: N/A
Cost: 0 Nexthop : N/A
-->0000.0000.0004.00
LinkCost : 0
LinkNewCost : 0
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type: Remote Interface: GE1/0/1
Cost: 0 Nexthop : 1.1.1.3
Level-2 Shortest Path Tree
--------------------------
SpfNode : 0000.0000.0001.00
Distance : 0
TE distance : 0
NodeFlag : S/-/-/-/-/-
RelayNibID : 0x0
TE tunnel count: 0
Nexthop count : 0
SpfLink count : 1
-->0000.0000.0004.04
LinkCost : 10
LinkNewCost : 10
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type: Adjacent Interface: N/A
Cost: 10 Nexthop : N/A
SpfNode : 0000.0000.0004.00
Distance : 10
TE distance : 10
NodeFlag : S/-/-/-/-/-
RelayNibID : 0x0
TE tunnel count: 1
Destination: 4.4.4.4 Interface : Tun0
TE cost : 10 Final cost : 10
Add nexthop: YES Add TLV : YES
Nexthop count : 2
Neighbor : 0000.0000.0004.00 Interface : Tun0
Nexthop : 4.4.4.4
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
Neighbor : 0000.0000.0004.00 Interface : GE1/0/1
Nexthop : 1.1.1.3
BkNeighbor : N/A BkInterface: N/A
BkNexthop : N/A
SpfLink count : 1
-->0000.0000.0004.04
LinkCost : 10
LinkNewCost : 10
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type: Remote Interface: N/A
Cost: 10 Nexthop : N/A
AdvMtID: 0
SpfNode : 0000.0000.0004.04
Distance : 10
TE distance : 10
NodeFlag : S/-/-/R/-/-
RelayNibID : 0x0
TE tunnel count: 0
Nexthop count : 0
SpfLink count : 2
-->0000.0000.0001.00
LinkCost : 0
LinkNewCost : 0
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type: Remote Interface: N/A
Cost: 0 Nexthop : N/A
-->0000.0000.0004.00
LinkCost : 0
LinkNewCost : 0
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type: Remote Interface: GE1/0/1
Cost: 0 Nexthop : 1.1.1.3
Table 72 Command output
|
Field |
Description |
|
SpfNode |
ID of the topology node. |
|
Distance |
Shortest distance from the root node to the local node. |
|
TE distance |
Shortest distance from the root node to the local node (including tunnel links). If tunnel is not configured, TE distance equals to Distance. |
|
NodeFlag |
Node flag: · S—The node is on the SPF tree. · T—The node is on the tent list. · O—The node is overloaded. · R—The node is directly connected. · I—The node is isolated. · D—The node is to be deleted. |
|
RelayNibID |
Next hop ID of the node after route recursion. |
|
TE tunnel count |
Number of tunnels destined to this node. |
|
Destination |
Destination router. |
|
TE cost |
IGP cost of the TE tunnel. |
|
Final cost |
Final cost of the TE tunnel. |
|
Nexthop count |
Next hop count. |
|
Nexthop |
Primary next hop of the node or the link advertising source. |
|
AdvMtID |
Topology from which the routing information is learned: · 0—Base topology. · 6-4094—Other topologies. |
|
Interface |
Primary output interface of the node or the link advertising source. |
|
BkNexthop |
Backup next hop. |
|
BkInterface |
Backup output interface. |
|
Neighbor |
ID of the primary next hop neighbor. |
|
BkNeighbor |
ID of the backup next hop neighbor. |
|
SpfLink |
Topology link. |
|
SpfLink count |
Number of topology links. |
|
LinkCost |
Link cost. |
|
LinkNewCost |
New link cost. |
|
LinkFlag |
Link flag: · I—The link is isolated. · D—The link is to be deleted. · C—The neighbor is a child node. · P—The neighbor is the parent node. · V—The link is involved. · N—The link is a new path. · L—The link is on the change list. · U—The protocol usage of the link is changed. · H—The next hop of the link is changed. |
|
LinkSrcCnt |
Number of link advertising sources. |
|
Type |
Type of the link advertising source: · Adjacent—The link advertising source is a local neighbor. · Remote—The link advertising source is advertised by a remote node in an LSP. |
|
Cost |
Cost of the link advertising source. |
display isis statistics
Use display isis statistics to display IS-IS statistics.
Syntax
display isis statistics [ ipv4 [ topology topo-name ] ] [ level-1 | level-1-2 | level-2 ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv4: Displays IS-IS IPv4 statistics. If you do not specify this option, the command displays both IPv4 and IPv6 statistics.
topology topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays IS-IS statistics for the public network.
level-1: Displays IS-IS Level-1 statistics.
level-1-2: Displays IS-IS Level-1-2 statistics.
level-2: Displays IS-IS Level-2 statistics.
process-id: Displays statistics for an IS-IS process specified by its ID in the range of 1 to 65535.
Usage guidelines
If you do not specify a level, this command displays both Level-1 and Level-2 routing information.
If you do not specify an IS-IS process ID, this command displays the statistics for all IS-IS processes.
Examples
# Display IS-IS statistics.
<Sysname> display isis statistics
Statistics information for IS-IS(1)
----------------------------------
Level-1 Statistics
------------------
MTR(base)
Learnt routes information:
Total IPv4 Learnt Routes in IPv4 Routing Table: 1
Imported routes information:
IPv4 Imported Routes:
Static: 0 Direct: 0
ISIS: 0 BGP: 0
RIP: 0 OSPF: 0
EIGRP: 0
Total Number: 0
MTR(base)
Learnt routes information:
Total IPv6 Learnt Routes in IPv6 Routing Table: 0
Imported routes information:
IPv6 Imported Routes:
Static: 0 Direct: 0
ISISv6: 0 BGP4+: 0
RIPng: 0 OSPFv3: 0
Total Number: 0
Lsp information:
LSP Source ID: No. of used LSPs
7777.8888.1111 001
Level-2 Statistics
------------------
MTR(base)
Learnt routes information:
Total IPv4 Learnt Routes in IPv4 Routing Table: 0
Imported routes information:
IPv4 Imported Routes:
Static: 0 Direct: 0
ISIS: 0 BGP: 0
RIP: 0 OSPF: 0
EIGRP: 0
Total Number: 0
MTR(base)
Learnt routes information:
Total IPv6 Learnt Routes in IPv6 Routing Table: 0
Imported routes information:
IPv6 Imported Routes:
Static: 0 Direct: 0
ISISv6: 0 BGP4+: 0
RIPng: 0 OSPFv3: 0
Total Number: 0
Lsp information:
LSP Source ID: No. of used LSPs
7777.8888.1111 001
Table 73 Command output
|
Field |
Description |
|
Statistics information for IS-IS(processid) |
Statistics for the IS-IS process. |
|
Level-1 Statistics |
Level-1 statistics. |
|
Level-2 Statistics |
Level-2 statistics. |
|
MTR(topo-name) |
MTR topology. base represents the base topology. |
|
Learnt routes information |
· Total IPv4 Learnt Routes in IPv4 Routing Table—Number of learned IPv4 routes. · Total IPv6 Learnt Routes in IPv6 Routing Table—Number of learned IPv6 routes. |
|
Imported routes information |
· IPv4 Imported Routes—Numbers of different types of redistributed IPv4 routes, including static, direct, IS-IS, BGP, RIP, OSPF, and EIGRP routes. · IPv6 Imported Routes—Numbers of different types of redistributed IPv6 routes, including static, direct, IS-ISv6, BGP4+, RIPng, and OSPFv3 routes. |
|
Lsp information |
LSP information: · LSP Source ID—ID of the source system. · No. of used LSPs—Number of used LSPs. |
display osi
Use display osi to display OSI connection information, including the socket status, options, input interfaces, and matched multicast MAC addresses.
Syntax
Centralized devices in standalone mode:
display osi
Distributed devices in standalone mode/centralized devices in IRF mode:
display osi [ slot slot-number ]
Distributed devices in IRF mode:
display osi [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays OSI connection information for all cards. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays OSI connection information for all member devices. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays OSI connection information for all cards on all IRF member devices.
Examples
# Display OSI connection information.
<Sysname> display osi
Total OSI socket number: 2
Location: chassis 1 slot 0
Creator: isisd[1539]
State: N/A
Options: SO_FILTER
Error: 0
Receiving buffer(cc/hiwat/lowat/drop/state): 0 / 1048576 / 1 / 0 / N/A
Sending buffer(cc/hiwat/lowat/state): 0 / 262144 / 512 / N/A
Type: 2
Enabled interfaces:
GigabitEthernet0/0
MAC address: 0180-c200-0014
Location: chassis 1 slot 0
Creator: isisd[1539]
State: N/A
Options: SO_FILTER
Error: 0
Receiving buffer(cc/hiwat/lowat/drop/state): 0 / 1048576 / 1 / 0 / N/A
Sending buffer(cc/hiwat/lowat/state): 0 / 262144 / 512 / N/A
Type: 2
Enabled interfaces:
GigabitEthernet0/0
MAC address: 0180-c200-0014
Table 74 Command output
|
Field |
Description |
|
Total OSI socket number |
Total number of OSI sockets. |
|
Chassis |
ID of the IRF member device. |
|
Slot |
Slot number of the card. |
|
Creator |
Name of the socket creator. The process ID of the creator is displayed in the square brackets. |
|
State |
This field always displays N/A. |
|
Options |
Socket options: · SO_FILTER—Filter option is configured. · N/A—No option is configured. |
|
Error |
Number of errors that affect the socket session. |
|
Receiving buffer(cc/hiwat/lowat/drop/state) |
Receiving buffer information, including the current used space, maximum space, minimum space, termination, and status. |
|
Sending buffer(cc/hiwat/lowat/state) |
Sending buffer information, including the current used space, maximum space, minimum space, and status. |
|
Type |
Type 2 socket, corresponding to unreliable connectionless-oriented transport layer protocols. |
|
Enabled interfaces |
Input interfaces and matched multicast MAC addresses. Only packets received from Ethernet link-layer interfaces need to match the multicast MAC addresses. |
display osi statistics
Use display osi statistics to display OSI packet statistics, including received packets, relayed packets, discarded packets, and sent packets.
Syntax
Centralized devices in standalone mode:
display osi statistics
Distributed devices in standalone mode/centralized devices in IRF mode:
display osi statistics [ slot slot-number ]
Distributed devices in IRF mode:
display osi statistics [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays OSI packet statistics for all cards. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays OSI packet statistics for all member devices. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays OSI packet statistics for all cards on all IRF member devices.
Examples
# Display OSI packet statistics.
<Sysname> display osi statistics
Received packets:
Total: 35
Relay received: 35
Relay forwarded: 35
Invalid service slot: 0
No matched socket: 0
Not delivered, input socket full: 0
Sent packets:
Total: 19
Relay forwarded: 19
Relay received: 19
Failed: 0
Table 75 Command output
|
Field |
Description |
|
|
Received packets |
Total |
Total number of received link layer packets. |
|
Relay received |
Number of inbound packets on LPUs relayed from other cards. This count is not included in the total count of received packets. |
|
|
Relay forwarded |
Number of inbound packets relayed to LPUs. |
|
|
Invalid service slot |
Number of discarded packets due to unavailable LPUs. |
|
|
No matched socket |
Number of discarded packets due to mismatches in input interfaces, MAC addresses, or connection filter criteria. |
|
|
Not delivered, input socket full |
Number of undelivered packets due to a socket receiving buffer overflow. |
|
|
Sent packets |
Total |
Total number of packets that IS-IS sent over OSI connections. |
|
Relay forwarded |
Number of outbound packets relayed to the cards that hosts the output interfaces. This count is not included in the total count of sent packets. |
|
|
Relay received |
Number of outbound packets on the cards that hosts the output interfaces. These packets are relayed from other cards. |
|
|
Failed |
Number of packets failed to be sent. |
|
Related commands
distribute bgp-ls
Use distribute bgp-ls to advertise IS-IS link state information to BGP.
Use undo distribute bgp-ls to restore the default.
Syntax
distribute bgp-ls [ instance-id id ] [ level-1 | level-2 ]
undo distribute bgp-ls [ level-1 | level-2 ]
Default
The device does not advertise IS-IS link state information to BGP.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
instance-id id: Specifies an instance by its ID in the range of 0 to 65535. If you do not specify this option, the command advertises IS-IS link state information of instance 0 to BGP.
level-1: Advertises the Level-1 IS-IS link state information to BGP.
level-2: Advertises the Level-2 IS-IS link state information to BGP.
Usage guidelines
After the device advertises IS-IS link state information to BGP, BGP can advertise the information for intended applications.
If multiple IS-IS processes have the same instance ID and link state information, only the link state information of the IS-IS process with the smallest process ID is advertised.
To advertise the same link state information of different IS-IS processes to BGP, specify different instance IDs for the IS-IS processes.
If you do not specify a level for the distribute bgp-ls command, both Level-1 and Level-2 IS-IS link state information are advertised to BGP.
If you do not specify a level for the undo distribute bgp-ls command, neither Level-1 nor Level-2 IS-IS link state information can be advertised to BGP.
Examples
# Advertise link state information of IS-IS process 1 to BGP.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] distribute bgp-ls
domain-authentication send-only
Use domain-authentication send-only to configure IS-IS not to check the authentication information in the received Level-2 packets, including LSPs, CSNPs, and PSNPs.
Use undo domain-authentication send-only to restore the default.
Syntax
domain-authentication send-only
undo domain-authentication send-only
Default
When domain authentication mode and key are configured, a Level-2 or Level-1-2 router checks the authentication information in the received packets.
Views
IS-IS view
Predefined user roles
network-admin
Usage guidelines
When domain authentication mode and key are configured, a Level-2 or Level-1-2 router adds the key in the specified mode into transmitted Level-2 packets (including LSPs, CSNPs, and PSNPs). It also checks the key in the received Level-2 packets.
To prevent packet exchange failure in case of an authentication key change, configure IS-IS not to check the authentication information in the received packets.
Examples
# Configure IS-IS not to check the authentication information in the received packets.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] domain-authentication send-only
Related commands
area-authentication send-only
domain-authentication-mode
isis authentication send-only
domain-authentication-mode
Use domain-authentication-mode to specify the routing domain authentication mode and a key.
Use undo domain-authentication-mode to restore the default.
Syntax
domain-authentication-mode { { gca key-id { hmac-sha-1 | hmac-sha-224 | hmac-sha-256 | hmac-sha-384 | hmac-sha-512 } [ nonstandard ] | md5 | simple } { cipher | plain } string } | keychain keychain-name } [ ip | osi ]
undo domain-authentication-mode
Default
No routing domain authentication mode or key is configured.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
gca: Specifies the GCA mode.
key-id: Uniquely identifies an SA in the range of 1 to 65535. The sender inserts the Key ID into the authentication TLV, and the receiver authenticates the packet by using the SA that is selected based on the Key ID.
hmac-sha-1: Specifies the HMAC-SHA-1 algorithm.
hmac-sha-224: Specifies the HMAC-SHA-224 algorithm.
hmac-sha-256: Specifies the HMAC-SHA-256 algorithm.
hmac-sha-384: Specifies the HMAC-SHA-384 algorithm.
hmac-sha-512: Specifies the HMAC-SHA-512 algorithm.
nonstandard: Specifies the nonstandard GCA mode.
md5: Specifies the MD5 authentication mode.
simple: Specifies the simple authentication mode.
cipher: Specifies a key in encrypted form.
plain: Specifies a key in plaintext form. For security purposes, the key specified in plaintext form will be stored in encrypted form.
string: Specifies the key. Its plaintext form is a case-sensitive string of 1 to 16 characters. Its encrypted form is a case-sensitive string of 33 to 53 characters.
keychain: Specifies the keychain authentication mode.
keychain-name: Specifies a keychain by its name, a case-sensitive string of 1 to 63 characters.
ip: Checks IP-related fields in LSPs.
osi: Checks OSI-related fields in LSPs.
Usage guidelines
The configured key in the specified mode is inserted into all outgoing Level-2 packets (LSP, CSNP, and PSNP) and is used for authenticating the incoming Level-2 packets.
IS-IS keychain authentication can operate correctly only when the keys in the keychain use the HMAC-MD5 authentication algorithm.
· Before IS-IS sends a Level-2 packet, it uses the valid send key obtained from the keychain to authenticate the packet. If no valid send key exists or the valid send key does not use the HMAC-MD5 algorithm, the authentication fails and the packet does not contain the authentication information.
· After IS-IS receives a Level-2 packet, it uses a valid accept key obtained from the keychain to authenticate the packet. If no valid accept key exists or all valid accept keys fail to authenticate the packet, the authentication fails and the packet is discarded.
All the backbone routers must have the same authentication mode and key.
If neither ip nor osi is specified, the OSI-related fields in LSPs are checked.
When you specify the GCA mode, follow these guidelines:
· If you do not specify the nonstandard keyword, the device can communicate only with devices that use the GCA mode.
· If you specify the nonstandard keyword, the device can communicate only with devices that use the nonstandard GCA mode.
Examples
# Set the routing domain authentication mode to simple, and set the plaintext key to 123456.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] domain-authentication-mode plain 123456
Related commands
area-authentication-mode
domain-authentication send-only
isis authentication-mode
fast-reroute
Use fast-reroute to configure IS-IS FRR.
Use undo fast-reroute to disable IS-IS FRR.
Syntax
fast-reroute { lfa | route-policy route-policy-name }
undo fast-reroute
Default
IS-IS FRR is disabled.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
lfa: Calculates a backup next hop through Loop Free Alternate (LFA) calculation for all routes.
route-policy route-policy-name: Uses the specified routing policy to designate a backup next hop. The route-policy-name argument is a case-sensitive string of 1 to 63 characters.
Usage guidelines
The LFA calculation of FRR and IS-IS TE are mutually exclusive.
Example
# Enable FRR for IS-IS process 1 and configure IS-IS FRR to calculate a backup next hop through LFA calculation for all routes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] fast-reroute lfa
filter-policy export
Use filter-policy export to configure IS-IS to filter redistributed routes.
Use undo filter-policy export to remove the configuration.
Syntax
filter-policy { ipv4-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } export [ bgp | direct | eigrp [ eigrp-as ] | { isis | ospf | rip } [ process-id ] | static ]
undo filter-policy export [ bgp | direct | eigrp [ eigrp-as ] | { isis | ospf | rip } [ process-id ] | static ]
Default
IS-IS does not filter redistributed routes.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
ipv4-acl-number: Specifies an ACL by its number in the range of 2000 to 3999 to filter redistributed routes.
prefix-list prefix-list-name: Specifies an IPv4 prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter redistributed routes by destination address.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter redistributed routes.
bgp: Filters routes redistributed from BGP.
direct: Filters direct routes.
eigrp: Filters routes redistributed from EIGRP.
eigrp-as: Specifies an EIGRP process by its ID in the range of 1 to 65535. The default value is 1.
isis: Filters routes redistributed from IS-IS.
ospf: Filters routes redistributed from OSPF.
rip: Filters routes redistributed from RIP.
process-id: Specifies a process by its ID in the range of 1 to 65535. The default process ID is 1.
Usage guidelines
If you do not specify any parameters, the command filters all redistributed routes.
To use an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL using one of the following methods:
· To deny/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny/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 route. The specified subnet mask must be contiguous. Otherwise, the configuration does not take effect.
Examples
# Use basic ACL 2000 to filter redistributed routes.
<Sysname> system-view
[Sysname] acl basic 2000
[Sysname-acl-ipv4-basic-2000] rule deny source 192.168.10.0 0.0.0.255
[Sysname-acl-ipv4-basic-2000] quit
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] filter-policy 2000 export
# Configure advanced ACL 3000 to permit only route 113.0.0.0/16 to pass. Use advanced ACL 3000 to filter redistributed routes.
[Sysname] acl advanced 3000
[Sysname-acl-ipv4-adv-3000] rule 10 permit ip source 113.0.0.0 0 destination 255.255.0.0 0
[Sysname-acl-ipv4-adv-3000] rule 100 deny ip
[Sysname-acl-ipv4-adv-3000] quit
[Sysname] isis 1
[Sysname-isis 1] address-family ipv4
[Sysname-isis-1-ipv4] filter-policy 3000 export
Related commands
display isis route
filter-policy import
Use filter-policy import to configure IS-IS to filter routes calculated using received LSPs.
Use undo filter-policy import to restore the default.
Syntax
filter-policy { ipv4-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } import
undo filter-policy import
Default
IS-IS does not filter routes calculated using received LSPs.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
ipv4-acl-number: Specifies an ACL by its number in the range of 2000 to 3999 to filter routes calculated using received LSPs.
prefix-list prefix-list-name: Specifies an IPv4 prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter routes calculated using received LSPs by destination address.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter received routes.
Usage guidelines
To use an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL using one of the following methods:
· To deny/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny/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 route. The subnet mask must be contiguous. Otherwise, the configuration does not take effect.
Examples
# Use basic ACL 2000 to filter routes calculated using received LSPs.
<Sysname> system-view
[Sysname] acl basic 2000
[Sysname-acl-ipv4-basic-2000] rule deny source 192.168.10.0 0.0.0.255
[Sysname-acl-ipv4-basic-2000] quit
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] filter-policy 2000 import
# Use advanced ACL 3000 to filter routes calculated using received LSPs and install only route 113.0.0.0/16 to the IP routing table.
<Sysname> system-view
[Sysname] acl number 3000
[Sysname-acl-ipv4-adv-3000] rule 10 permit ip source 113.0.0.0 0 destination 255.255.0.0 0
[Sysname-acl-ipv4-adv-3000] rule 100 deny ip
[Sysname-acl-ipv4-adv-3000] quit
[Sysname] isis 1
[Sysname-isis 1] address-family ipv4
[Sysname-isis-1-ipv4] filter-policy 3000 import
Related commands
display ip routing-table
flash-flood
Use flash-flood to enable IS-IS LSP flash flooding.
Use undo flash-flood to disable IS-IS LSP flash flooding.
Syntax
flash-flood [ flood-count flooding-count | max-timer-interval flooding-interval | [ level-1 | level-2 ] ] *
undo flash-flood [ level-1 | level-2 ]
Default
IS-IS LSP flash flooding is disabled.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
flood-count flooding-count: Specifies the maximum number of LSPs to be flooded before the next SPF calculation, in the range of 1 to 15. The default is 5.
max-timer-interval flooding-interval: Specifies the delay of the flash flooding, in the range of 10 to 50000 milliseconds. The default is 10.
level-1: Enables flash flooding for level-1.
level-2: Enables flash flooding for level-2.
Usage guidelines
If no level is specified, the command enables IS-IS LSP flash flooding for both Level-1 and Level-2.
Examples
# Enable fast flooding, and set the maximum LSPs to be sent to 10 and the delay time to 100 milliseconds.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] flash-flood flood-count 10 max-timer-interval 100
graceful-restart
Use graceful-restart to enable IS-IS GR.
Use undo graceful-restart to disable IS-IS GR.
Syntax
graceful-restart
undo graceful-restart
Default
IS-IS GR is disabled.
Views
IS-IS view
Predefined user roles
network-admin
Usage guidelines
IS-IS GR and IS-IS NSR are mutually exclusive. Therefore, do not configure the graceful-restart command and the non-stop-routing command at the same time.
Examples
# Enable GR for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] graceful-restart
Related commands
graceful-restart suppress-sa
graceful-restart suppress-sa
Use graceful-restart suppress-sa to suppress the Suppress-Advertisement (SA) bit during restart.
Use undo graceful-restart suppress-sa to restore the default.
Syntax
graceful-restart suppress-sa
undo graceful-restart suppress-sa
Default
The SA bit is set during restart.
Views
IS-IS view
Predefined user roles
network-admin
Usage guidelines
Suppressing the SA bit is mainly for avoiding black hole route. If a router starts or reboots without keeping the local forwarding table, sending packets to the router might result in severe packet loss. To avoid this, you can set the SA bit of the hello packet sent by the GR restarter to 1. Upon receiving such hello packets, the GR helpers will not advertise the GR restarter through LSP.
Examples
# Suppress the SA bit during graceful restart.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] graceful-restart suppress-sa
Related commands
graceful-restart
graceful-restart t1
Use graceful-restart t1 to set the T1 timer.
Use undo graceful-restart t1 to restore the default.
Syntax
graceful-restart t1 seconds count count
undo graceful-restart t1
Default
The T1 timer is 3 seconds and can expire 10 times.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
seconds: Specifies the T1 timer in the range of 3 to 10 seconds.
count: Specifies the number of times that the T1 timer can expire, in the range of 1 to 20.
Usage guidelines
The T1 timer specifies the number of times that GR restarter can send a Restart TLV with the RR bit set. After restart, the GR restarter sends a Restart TLV with the RR bit set to its neighbor. If the restarting router receives a Restart TLV with the RA set from its neighbor before the T1 timer expires, the GR process starts. Otherwise, the GR process fails.
Examples
# Set the T1 timer of IS-IS process 1 to 5 seconds, and the expiration times to 5.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] graceful-restart t1 5 count 5
Related commands
graceful-restart
graceful-restart t2
graceful-restart t3
graceful-restart t2
Use graceful-restart t2 to set the T2 timer.
Use undo graceful-restart t2 to restore the default.
Syntax
graceful-restart t2 seconds
undo graceful-restart t2
Default
The T2 timer is 60 seconds.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
seconds: Specifies the T2 timer in the range of 30 to 65535 seconds.
Usage guidelines
The T2 timer specifies the LSDB synchronization interval. Each LSDB has a T2 timer. The Level-1-2 router has two T2 timers: a Level-1 timer and a Level-2 timer. If the LSDBs have not achieved synchronization before the two timers expire, the GR process fails.
Examples
# Set the T2 timer of IS-IS process 1 to 50 seconds.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] graceful-restart t2 50
Related commands
graceful-restart
graceful-restart t1
graceful-restart t3
graceful-restart t3
Use graceful-restart t3 to set the T3 timer.
Use undo graceful-restart t3 to restore the default.
Syntax
graceful-restart t3 seconds
undo graceful-restart t3
Default
The T3 timer is 300 seconds.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
seconds: Specifies the T3 timer in the range of 300 to 65535 seconds.
Usage guidelines
The T3 timer specifies the GR interval. The GR interval is set as the holdtime in hello PDUs. Within the interval, the neighbors maintain their adjacency with the GR restarter. If the GR process has not completed within the holdtime, the neighbors tear down the neighbor relationship and the GR process fails.
Examples
# Set the T3 timer of IS-IS process 1 to 500 seconds.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] graceful-restart t3 500
Related commands
graceful-restart
graceful-restart t1
graceful-restart t2
ignore-att
Use ignore-att to configure IS-IS not to calculate the default route through the ATT bit.
Use undo ignore-att to restore the default.
Syntax
ignore-att
undo ignore-att
Default
IS-IS calculates the default route through the ATT bit.
Views
IS-IS view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Examples
# Configure IS-IS not to calculate the default route through the ATT bit.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] ignore-att
import-route
Use import-route to configure IS-IS to redistribute external routes.
Use undo import-route to remove the redistribution.
Syntax
import-route bgp [ as-number ] [ allow-ibgp ] [ cost cost-value | cost-type { external | internal } | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
import-route { direct | static } [ cost cost-value | cost-type { external | internal } | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
import-route eigrp [ eigrp-as | all-as ] [ allow-direct | cost cost-value | cost-type { external | internal } | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
import-route { isis | ospf | rip } [ process-id | all-processes ] [ allow-direct | cost cost-value | cost-type { external | internal } | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
undo import-route { bgp | direct | eigrp [ eigrp-as | all-as ] | { isis | ospf | rip } [ process-id | all-processes ] | static }
Default
IS-IS does not redistribute routes.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
bgp: Redistributes BGP routes.
as-number: Specifies an AS by its number in the range of 1 to 4294967295. If you do not specify this argument, the command redistributes all IPv4 EBGP routes. As a best practice, specify an AS to prevent the system from redistributing excessive routes.
direct: Redistributes direct routes.
eigrp: Redistributes EIGRP routes.
eigrp-as: Specifies an EIGRP process by its ID in the range of 1 to 65535. The default value is 1.
isis: Redistributes IS-IS routes.
ospf: Redistributes OSPF routes.
rip: Redistributes RIP routes.
static: Redistributes static routes.
process-id: Specifies a process by its ID in the range of 1 to 65535. The default value is 1.
all-processes: Redistributes routes from all the processes of IS-IS, OSPF, or RIP.
allow-ibgp: Allows redistribution of IBGP routes. The import-route bgp command redistributes only EBGP routes. The import-route bgp allow-ibgp command redistributes both EBGP and IBGP routes. Because this command might cause routing loops, use it with caution.
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. If you specify both the allow-direct keyword and the route-policy route-policy-name option, make sure the if-match rule defined in the routing policy does not conflict with the allow-direct keyword. For example, if you specify the allow-direct keyword, do not configure the if-match route-type rule for the routing policy. Otherwise, the allow-direct keyword does not take effect.
cost cost-value: Specifies a cost for redistributed routes, which is in the range of 0 to 4261412864.
· For the styles of narrow, narrow-compatible, and compatible, the cost is in the range of 0 to 63.
· For the styles of wide and wide-compatible, the cost is in the range of 0 to 4261412864.
cost-type { external | internal }: Specifies the cost type. The internal type indicates internal routes, and the external type indicates external routes. If external is specified, the cost of a redistributed route is added by 64 to make internal routes take priority over external routes. The type is external by default. The keywords are available only when the cost type is narrow, narrow-compatible, or compatible.
level-1: Redistributes routes into the Level-1 routing table.
level-1-2: Redistributes routes into both Level-1 and Level-2 routing tables.
level-2: Redistributes routes into the Level-2 routing table. If no level is specified, the routes are redistributed into the Level-2 routing table by default.
route-policy route-policy-name: Redistributes only routes matching the specified routing policy. The route-policy-name argument is a case-sensitive string of 1 to 63 characters.
tag tag: Specifies a tag value for marking redistributed routes, in the range of 1 to 4294967295.
Usage guidelines
IS-IS takes all the redistributed routes as external routes to destinations outside the IS-IS routing domain.
The effective cost varies by cost style. For the styles of narrow, narrow-compatible, and compatible, the cost is in the range of 0 to 63. If the cost is more than 63, 63 is used. For the style of wide or wide-compatible, the configured value is the effective value.
This import-route command cannot redistribute default routes. The command redistributes only active routes. To display route state information, use the display ip routing-table protocol command.
The undo import-route eigrp all-as command removes only the configuration made by the import-route eigrp all-as command. It does not remove the configuration made by the import-route eigrp eigrp-as command.
The undo import-route protocol all-processes command removes only the configuration made by the import-route protocol all-processes command, instead of the configuration made by the import-route protocol process-id command.
Examples
# Redistribute static routes into IS-IS, and set the cost for redistributed routes to 15.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] import-route static cost 15
Related commands
import-route limit
import-route isis level-1 into level-2
Use import-route isis level-1 into level-2 to enable route advertisement from Level-1 to Level-2.
Use undo import-route isis level-1 into level-2 to disable route advertisement from Level-1 to Level-2.
Syntax
import-route isis level-1 into level-2 [ filter-policy { ipv4-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } | tag tag ] *
undo import-route isis level-1 into level-2
Default
Route advertisement from Level-1 to Level-2 is enabled.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
filter-policy: Specifies a filtering policy.
ipv4-acl-number: Specifies an ACL by its number in the range of 2000 to 3999 to filter routes from Level-1 to Level-2.
prefix-list prefix-list-name: Specifies an IPv4 prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter routes from Level-1 to Level-2 by destination address.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter routes from Level-1 to Level-2.
tag tag: Specifies a tag for marking redistributed routes, in the range of 1 to 4294967295.
Usage guidelines
If a routing policy is used, the routing policy must be specified in the import-route isis level-1 into level-2 command to filter routes from Level-1 to Level-2. Other routing policies specified for route reception and redistribution do not affect the route leaking.
If a filtering policy is configured, only Level-1 routes not filtered out can be advertised into the Level-2 area.
Examples
# Enable route advertisement from Level-1 to Level-2.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] import-route isis level-1 into level-2
Related commands
import-route
import-route isis level-1 into level-2
import-route isis level-2 into level-1
Use import-route isis level-2 into level-1 to enable route advertisement from Level-2 to Level-1.
Use undo import-route isis level-2 into level-1 to restore the default.
Syntax
import-route isis level-2 into level-1 [ filter-policy { ipv4-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } | tag tag ] *
undo import-route isis level-2 into level-1
Default
Route advertisement from Level-2 to Level-1 is disabled.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
filter-policy: Specifies a filtering policy.
ipv4-acl-number: Specifies an ACL by its number in the range of 2000 to 3999 to filter routes from Level-2 to Level-1.
prefix-list prefix-list-name: Specifies an IPv4 prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter routes from Level-2 to Level-1 by destination address.
route-policy route-policy-name: Uses the specified routing policy to filter routes from Level-2 to Level-1. The route-policy-name argument is a case-sensitive string of 1 to 63 characters.
tag tag: Specifies a tag for marking redistributed routes, in the range of 1 to 4294967295.
Usage guidelines
If a routing policy is used, the routing policy must be specified in the import-route isis level-2 into level-1 command to filter routes from Level-2 to Level-1. Other routing policies specified for route reception and redistribution does not affect the route leaking.
If a filtering policy is configured, only Level-2 routes not filtered out can be advertised into the Level-1 area.
Examples
# Enable route advertisement from Level-2 to Level-1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] import-route isis level-2 into level-1
Related commands
import-route
import-route isis level-1 into level-2
import-route limit
Use import-route limit to configure the maximum number of redistributed Level 1/Level 2 IPv4 routes.
Use undo import-route limit to restore the default.
Syntax
import-route limit number
undo import-route limit
Default
The following matrix shows the default maximum number of redistributed Level 1/Level 2 IPv4 routes:
|
Hardware |
Default value |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
201024 |
|
MSR2600-6-X1/2600-10-X1 |
301024 |
|
MSR 2630 |
301024 |
|
MSR3600-28/3600-51 |
301024 |
|
MSR3600-28-SI/3600-51-SI |
201024 |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
501024 |
|
MSR 3610 |
201024 |
|
MSR 3620/3620-DP/3640/3660 |
501024 |
|
MSR5620/5660/5680 |
1001024 |
|
Hardware |
Default value |
|
MSR810-LM-GL |
201024 |
|
MSR810-W-LM-GL |
201024 |
|
MSR830-6EI-GL |
201024 |
|
MSR830-10EI-GL |
201024 |
|
MSR830-6HI-GL |
201024 |
|
MSR830-10HI-GL |
201024 |
|
MSR2600-6-X1-GL |
301024 |
|
MSR3600-28-SI-GL |
201024 |
Views
IS-IS IPv4 unicast address family view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of redistributed Level 1/Level 2 IPv4 routes.
The following matrix shows the value ranges for the number argument:
|
Hardware |
Value range |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
1 to 201024 |
|
MSR2600-6-X1/2600-10-X1 |
1 to 301024 |
|
MSR 2630 |
1 to 301024 |
|
MSR3600-28/3600-51 |
1 to 301024 |
|
MSR3600-28-SI/3600-51-SI |
1 to 201024 |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
1 to 501024 |
|
MSR 3610 |
1 to 201024 |
|
MSR 3620/3620-DP/3640/3660 |
1 to 501024 |
|
MSR5620/5660/5680 |
1 to 1001024 |
Examples
# Configure IS-IS process 1 to redistribute up to 1000 Level 1/Level 2 IPv4 routes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] import-route limit 1000
Related commands
import-route
isis
Use isis to enable IS-IS and enter IS-IS view.
Use undo isis to disable IS-IS.
Syntax
isis [ process-id ] [ vpn-instance vpn-instance-name ]
undo isis [ process-id ]
Default
IS-IS is disabled.
Views
System view
Predefined user roles
network-admin
Parameters
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535. The default is 1.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If no VPN is specified, the IS-IS process runs on the public network.
Examples
# Enable IS-IS process 1 and set the system ID to 0000.0000.0002 and area ID to 01.0001.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] network-entity 01.0001.0000.0000.0002.00
Related commands
isis enable
isis authentication send-only
Use isis authentication send-only to configure an IS-IS interface not to check the authentication information in the received hello packets.
Use undo isis authentication send-only to remove the configuration.
Syntax
isis authentication send-only [ level-1 | level-2 ]
undo isis authentication send-only [ level-1 | level-2 ]
Default
When interface authentication mode and key are configured, an IS-IS interface checks the authentication information in the received packets.
Views
Interface view
Predefined user roles
network-admin
Parameters
level-1: Configures IS-IS not to check the authentication information in the received Level-1 hello packets.
level-2: Configures IS-IS not to check the authentication information in the received Level-2 hello packets.
Usage guidelines
When peer authentication mode and key are configured, an IS-IS interface adds the key in the specified mode into transmitted hello packets. It also checks the key in the received hello packets.
To prevent packet exchange failure in case of an authentication key change, configure the IS-IS interface not to check the authentication information in the received packets.
Examples
# Configure interface GigabitEthernet1/0/1 not to check the authentication information in the received Level-1 hello packets.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis authentication send-only level-1
Related commands
area-authentication send-only
domain-authentication send-only
isis authentication-mode
isis authentication-mode
Use isis authentication-mode to specify the neighbor relationship authentication mode and a key.
Use undo isis authentication-mode to remove the configuration.
Syntax
isis authentication-mode { { gca key-id { hmac-sha-1 | hmac-sha-224 | hmac-sha-256 | hmac-sha-384 | hmac-sha-512 } [ nonstandard ] | md5 | simple } { cipher | plain } string } | keychain keychain-name } [ level-1 | level-2 ] [ ip | osi ]
undo isis authentication-mode [ level-1 | level-2 ]
Default
No neighbor relationship authentication mode or key is configured.
Views
Interface view
Predefined user roles
network-admin
Parameters
gca: Specifies the GCA mode.
key-id: Uniquely identifies an SA in the range of 1 to 65535. The sender inserts the Key ID into the authentication TLV, and the receiver authenticates the packet by using the SA that is selected based on the Key ID.
hmac-sha-1: Specifies the HMAC-SHA-1 algorithm.
hmac-sha-224: Specifies the HMAC-SHA-224 algorithm.
hmac-sha-256: Specifies the HMAC-SHA-256 algorithm.
hmac-sha-384: Specifies the HMAC-SHA-384 algorithm.
hmac-sha-512: Specifies the HMAC-SHA-512 algorithm.
nonstandard: Specifies the nonstandard GCA mode.
md5: Specifies the MD5 authentication mode.
simple: Specifies the simple authentication mode.
cipher: Specifies a key in encrypted form.
plain: Specifies a key in plaintext form. For security purposes, the key specified in plaintext form will be stored in encrypted form.
string: Specifies the key. Its plaintext form is a case-sensitive string of 1 to 16 characters. Its encrypted form is a case-sensitive string of 33 to 53 characters.
keychain: Specifies the keychain authentication mode.
keychain-name: Specifies a keychain by its name, a case-sensitive string of 1 to 63 characters.
level-1: Configures the key for Level-1.
level-2: Configures the key for Level-2.
ip: Checks IP-related fields in LSPs and SNPs.
osi: Checks OSI-related fields in LSPs and SNPs.
Usage guidelines
The key in the specified mode is inserted into all outbound hello packets and is used for authenticating inbound hello packets. Only if the authentication succeeds can the neighbor relationship be formed.
IS-IS keychain authentication can operate correctly only when the keys in the keychain use the HMAC-MD5 authentication algorithm.
· Before IS-IS sends a Hello packet, it uses the valid send key obtained from the keychain to authenticate the packet. If no valid send key exists or the valid send key does not use the HMAC-MD5 algorithm, the authentication fails and the packet does not contain the authentication information.
· After IS-IS receives a Hello packet, it uses a valid accept key obtained from the keychain to authenticate the packet. If no valid accept key exists or all valid accept keys fail to authenticate the packet, the authentication fails and the packet is discarded.
For two routers to become neighbors, the authentication mode and key at both ends must be identical.
The level-1 and level-2 keywords are configurable on an interface that has had IS-IS enabled with the isis enable command.
If you configure a key without specifying a level, the key applies to both Level-1 and Level-2.
If neither ip nor osi is specified, the OSI-related fields in LSPs are checked.
When you specify the GCA mode, follow these guidelines:
· If you do not specify the nonstandard keyword, the device can communicate only with devices that use the GCA mode.
· If you specify the nonstandard keyword, the device can communicate only with devices that use the nonstandard GCA mode.
Examples
# On GigabitEthernet 1/0/1, set the authentication mode to simple, and set the plaintext key to 123456.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis authentication-mode simple plain 123456
Related commands
area-authentication-mode
domain authentication-mode
isis authentication send-only
isis bfd enable
Use isis bfd enable to enable BFD.
Use undo isis bfd enable to disable BFD.
Syntax
isis bfd enable
undo isis bfd enable
Default
IS-IS BFD is disabled.
Views
Interface view
Predefined user roles
network-admin
Examples
# Enable BFD for IS-IS on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis enable
[Sysname-GigabitEthernet1/0/1] isis bfd enable
isis circuit-level
Use isis circuit-level to set the circuit level for the interface.
Use undo isis circuit-level to restore the default.
Syntax
isis circuit-level [ level-1 | level-1-2 | level-2 ]
undo isis circuit-level
Default
An interface can establish either the Level-1 or Level-2 adjacency.
Views
Interface view
Predefined user roles
network-admin
Parameters
level-1: Sets the circuit level to Level-1.
level-1-2: Sets the circuit level to Level-1-2.
level-2: Sets the circuit level to Level-2.
Usage guidelines
For a Level-1 (Level-2) router, the circuit level can only be Level-1 (Level-2). For a Level-1-2 router, you must specify a circuit level for a specific interface to form only the specified level neighbor relationship.
Examples
# GigabitEthernet 1/0/1 is connected to a non-backbone router in the same area. Set the circuit level of Ethernet 1/1 to Level-1 to prevent sending and receiving Level-2 Hello packets.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis enable
[Sysname-GigabitEthernet1/0/1] isis circuit-level level-1
Related commands
is-level
isis circuit-type p2p
Use isis circuit-type p2p to set the network type of an interface to P2P.
Use undo isis circuit-type to restore the default.
Syntax
isis circuit-type p2p
undo isis circuit-type
Default
The network type of an interface varies by physical media. (The network type of a VLAN interface is broadcast.)
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
This command is applicable only to a broadcast network with only two attached routers.
Interfaces with different network types operate differently. For example, broadcast interfaces must elect a DIS and flood CSNP packets to synchronize the LSDBs. P2P interfaces do not need to elect a DIS, and use a different LSDB synchronization mechanism.
If only two routers exist on a broadcast network, set the network type of attached interfaces to P2P to avoid DIS election and CSNP flooding. This saves network bandwidth and speeds up network convergence.
Examples
# Set the network type of GigabitEthernet 1/0/1 to P2P.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis enable
[Sysname-GigabitEthernet1/0/1] isis circuit-type p2p
isis cost
Use isis cost to set the IS-IS cost for an interface.
Use undo isis cost to remove the configuration.
Syntax
isis cost cost-value [ level-1 | level-2 ]
undo isis cost [ level-1 | level-2 ]
Default
No IS-IS cost is configured for an interface.
Views
Interface view
IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
cost-value: Specifies an IS-IS cost in the range of 1 to 16777215.
level-1: Applies the cost to Level-1.
level-2: Applies the cost to Level-2.
Usage guidelines
If neither level-1 nor level-2 is included, the cost applies to both level-1 and level-2.
Examples
# Set the Level-2 IS-IS cost to 5 for GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis cost 5 level-2
Related commands
auto-cost enable
bandwidth-reference
isis dis-name
Use isis dis-name to configure a name for a DIS to represent the pseudo node on a broadcast network.
Use undo isis dis-name to restore the default.
Syntax
isis dis-name symbolic-name
undo isis dis-name
Default
No name is configured for the DIS.
Views
Interface view
Predefined user roles
network-admin
Parameters
symbolic-name: Specifies a DIS name, a case-insensitive string of 1 to 64 characters.
Usage guidelines
This command takes effect only on routers that have dynamic system ID to host name mapping enabled. This command does not take effect on Point-to-Point interfaces.
Examples
# Set the DIS name to LOCALAREA.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis dis-name LOCALAREA
Related commands
display isis name-table
is-name
isis dis-priority
Use isis dis-priority to specify a DIS priority at a specified level for an interface.
Use undo isis dis-priority to remove the configuration.
Syntax
isis dis-priority priority [ level-1 | level-2 ]
undo isis dis-priority [ level-1 | level-2 ]
Default
The priority of Level-1 and Level-2 is 64.
Views
Interface view
Predefined user roles
network-admin
Parameters
priority: Specifies a DIS priority in the range of 0 to 127.
level-1: Applies the DIS priority to Level-1.
level-2: Applies the DIS priority to Level-2.
Usage guidelines
If neither level-1 nor level-2 is specified, the DIS priority applies to both Level-1 and Level-2.
On an IS-IS broadcast network, a router must be elected as the DIS at each routing level. Specify a DIS priority at a level for an interface. The greater the interface's priority is, the more likelihood it becomes the DIS. If multiple routers in the broadcast network have the same highest DIS priority, the router with the highest Subnetwork Point of Attachment (SNPA) address becomes the DIS. SNPA addresses are MAC addresses on a broadcast network.
IS-IS has no backup DIS. The router with a priority of 0 can also participate in DIS election.
Examples
# Set the Level-2 DIS priority to 127 for GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis dis-priority 127 level-2
isis enable
Use isis enable to enable an IS-IS process on an interface.
Use undo isis enable to disable IS-IS.
Syntax
isis enable [ process-id ]
undo isis enable
Default
No IS-IS process is enabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535. The default is 1.
Examples
# Enable IS-IS process 1 globally and enable it on the GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] network-entity 10.0001.1010.1020.1030.00
[Sysname-isis-1] quit
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis enable 1
Related commands
isis
isis fast-reroute lfa-backup exclude
Use isis fast-reroute lfa-backup exclude to disable LFA calculation on an interface.
Use undo isis fast-reroute lfa-backup exclude to restore the default.
Syntax
isis fast-reroute lfa-backup exclude
undo isis fast-reroute lfa-backup exclude
Default
LFA calculation is enabled on an interface, and the interface can be elected as a backup interface.
Views
Interface view
IPv4 unicast topology view of the interface
Predefined user roles
network-admin
Usage guidelines
When this command is configured, the interface does not participate in the LFA calculation, and cannot be elected as a backup interface.
Examples
# Disable LFA calculation on the interface GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] network-entity 10.0001.1010.1020.1030.00
[Sysname-isis-1] quit
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis enable 1
[Sysname-GigabitEthernet1/0/1] isis fast-reroute lfa-backup exclude
Related commands
fast-reroute
isis mesh-group
Use isis mesh-group to add an interface into a mesh group or block the interface.
Use undo isis mesh-group to restore the default.
Syntax
isis mesh-group { mesh-group-number | mesh-blocked }
undo isis mesh-group
Default
An interface does not belong to any mesh group and is not blocked.
Views
Interface view
Predefined user roles
network-admin
Parameters
mesh-group-number: Specifies a mesh group by its number in the range of 1 to 4294967295.
mesh-blocked: Configures the interface to send LSPs only after receiving LSP requests.
Usage guidelines
An interface not in a mesh group floods received LSPs to other interfaces. For an NBMA network with multiple point-to-point links, this mechanism causes repeated LSP flooding and bandwidth waste.
To solve this problem, use this command to add relevant interfaces to a mesh group. An interface in a mesh group only floods a received LSP to interfaces not in the same mesh group.
You can also use this command to block an interface. A blocked interface sends LSPs only after receiving LSP requests.
The mesh-group feature takes effect only on point-to-point links.
Examples
# Add the frame relay subinterface Serial2/1/1.1 to mesh-group 3.
<Sysname> system-view
[Sysname] interface serial 2/1/1
[Sysname-Serial2/1/1] link-protocol fr
[Sysname-Serial2/1/1] quit
[Sysname] interface serial 2/1/1.1
[Sysname-Serial2/1/1.1] isis mesh-group 3
isis mib-binding
Use isis mib-binding to bind an IS-IS process to MIB.
Use undo isis mib-binding to restore the default.
Syntax
isis mib-binding process-id
undo isis mib-binding
Default
MIB operation is bound to the IS-IS process with the smallest process ID.
Views
System view
Predefined user roles
network-admin
Parameters
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535.
Usage guidelines
If the specified the process ID does not exist, the MIB binding configuration fails.
Deleting an IS-IS process bound to MIB operation deletes the MIB binding configuration. MIB operation is bound to the IS-IS process with the smallest process ID.
Examples
# Bind IS-IS process 100 to MIB.
<Sysname> system-view
[Sysname] isis mib-binding 100
isis peer-ip-check
Use isis peer-ip-check to enable source address check for hello packets on an IS-IS PPP interface.
Use undo isis peer-ip-check to restore the default.
Syntax
isis peer-ip-check
undo isis peer-ip-check
Default
An IS-IS PPP interface can have a peer on a different network.
Interface view
Predefined user roles
network-admin
Usage guidelines
When the isis peer-ip-check command is configured, an IS-IS PPP interface can establish a neighbor relationship only with a peer on the same network.
Examples
# Enable source address check for hello packets on interface Serial 2/1/0.
<Sysname> system-view
[Sysname] interface serial 2/1/0
[Sysname-Serial2/1/0] isis peer-ip-check
isis prefix-suppression
Use isis prefix-suppression to enable prefix suppression on an interface.
Use undo isis prefix-suppression to disable prefix suppression on an interface.
Syntax
isis prefix-suppression
undo isis prefix-suppression
Default
Prefix suppression is disabled on an interface.
Views
Interface view
IPv4 unicast topology view of the interface
Predefined user roles
network-admin
Usage guidelines
Use this command to disable an interface from advertising its prefix in LSPs. This enhances network security by preventing IP routing to the interval nodes and speeds up network convergence.
This command is also applicable to the secondary IP address of the interface.
Examples
# Enable prefix suppression on the interface GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis prefix-suppression
isis primary-path-detect bfd
Use isis primary-path-detect bfd echo to enable BFD for IS-IS FRR or IS-IS PIC.
Use undo isis primary-path-detect bfd to disable BFD for IS-IS FRR or IS-IS PIC.
Syntax
isis primary-path-detect bfd { ctrl | echo }
undo isis primary-path-detect bfd
Default
BFD is disabled for IS-IS FRR or IS-IS PIC.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
This command enables IS-IS FRR or IS-IS PIC to use BFD to detect primary link failures.
Examples
# Enable BFD control packet mode for IS-IS FRR on the interface GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] fast-reroute lfa
[Sysname-isis-1-ipv4] quit
[Sysname-isis-1] quit
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis primary-path-detect bfd ctrl
# Enable BFD echo packet mode for IS-IS PIC on the interface GigabitEthernet 1/0/2.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] pic additional-path-always
[Sysname-isis-1] quit
[Sysname] bfd echo-source-ip 1.1.1.1
[Sysname] interface gigabitethernet 1/0/2
[Sysname-GigabitEthernet1/0/2] isis primary-path-detect bfd echo
isis silent
Use isis silent to disable the interface from sending and receiving IS-IS packets.
Use undo isis silent to restore the default.
Syntax
isis silent
undo isis silent
Default
An interface can send and receive IS-IS packets.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
This command is not available in loopback interface view.
Examples
# Disable GigabitEthernet 1/0/1 from sending and receiving IS-IS packets.
<<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis silent
isis small-hello
Use isis small-hello to configure the interface to send small hello packets without CLVs.
Use undo isis small-hello to restore the default.
Syntax
isis small-hello
undo isis small-hello
Default
An interface sends standard hello packets.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
This command is not available in loopback interface view.
Examples
# Configure GigabitEthernet 1/0/1 to send small Hello packets.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis small-hello
isis tag
Use isis tag to configure the tag value for an interface.
Use undo isis tag to restore the default.
Syntax
isis tag tag
undo isis tag
Default
The interface is not configured with a tag value.
Views
Interface view
IPv4 unicast topology view of the interface
Predefined user roles
network-admin
Parameters
tag: Specifies the tag value in the range of 1 to 4294967295.
Usage guidelines
When the link cost style is wide, wide-compatible, or compatible, IS-IS adds the tag of a prefix to the IP reachability information TLV of the prefix.
Examples
# Configure the tag value for the interface GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis tag 4294967295
isis timer csnp
Use isis timer csnp to set on the DIS of a broadcast network the interval for sending CSNP packets.
Use undo isis timer csnp to remove the configuration.
Syntax
isis timer csnp seconds [ level-1 | level-2 ]
undo isis timer csnp [ level-1 | level-2 ]
Default
The default CSNP interval is 10 seconds.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies on the DIS of a broadcast network the interval for sending CSNP packets. The value range is 1 to 600 seconds.
level-1: Applies the interval to Level-1.
level-2: Applies the interval to Level-2.
Usage guidelines
If no level is specified, the CSNP interval applies to both Level-1 and Level-2.
On a broadcast network, this command only applies to the DIS because the DIS sends CSNP packets periodically for LSDB synchronization.
Examples
# Configure Level-2 CSNP packets to be sent every 15 seconds over GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis timer csnp 15 level-2
isis timer hello
Use isis timer hello to set the interval for sending hello packets.
Use undo isis timer hello to remove the configuration.
Syntax
isis timer hello seconds [ level-1 | level-2 ]
undo isis timer hello [ level-1 | level-2 ]
Default
The hello interval is 10 seconds.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the interval for sending hello packets, in the range of 1 to 255 seconds.
level-1: Specifies the interval for sending Level-1 hello packets.
level-2: Specifies the interval for sending Level-2 hello packets.
Usage guidelines
If a neighbor does not receive any hello packets from the router within the advertised hold time, it considers the router down and recalculates the routes. The hold time is the hello multiplier multiplied by the hello interval.
Level-1 and Level-2 hello packets are sent independently on a broadcast network, so you need to specify an interval for each level. On a P2P link, Level-1 and Level-2 packets are both sent in P2P hello packets, and you need not specify an interval for each level.
You can configure the level-1 and level-2 keywords only on broadcast interfaces. Before you configure the level-1 or level-2 keyword, enable IS-IS on the interface.
The shorter the interval, the more system resources will be occupied. Configure an appropriate interval as needed.
If no level is specified, the hello interval applies to both Level-1 and Level-2.
Examples
# Configure Level-2 hello packets to be sent every 20 seconds over GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis timer hello 20 level-2
Related commands
isis timer holding-multiplier
isis timer holding-multiplier
Use isis timer holding-multiplier to set the IS-IS hello multiplier.
Use undo isis timer holding-multiplier to remove the configuration.
Syntax
isis timer holding-multiplier value [ level-1 | level-2 ]
undo isis timer holding-multiplier [ level-1 | level-2 ]
Default
The default IS-IS hello multiplier is 3.
Views
Interface view
Predefined user roles
network-admin
Parameters
value: Specifies the number of hello intervals, in the range of 3 to 1000.
level-1: Applies the number to the Level-1 IS-IS neighbor.
level-2: Applies the number to the Level-2 IS-IS neighbor.
Usage guidelines
The hello multiplier is the number of hello packets a neighbor must miss before declaring the router is down.
If a neighbor does not receive any hello packets from the router within the advertised hold time, it considers the router down and recalculates the routes. The hold time is the hello multiplier multiplied by the hello interval.
Level-1 and Level-2 hello packets are sent independently on a broadcast network, so you need to specify a hello multiplier for each level. On a P2P link, Level-1 and Level-2 packets are both sent in P2P hello packets, and you need not specify Level-1 or Level-2.
You can configure the level-1 and level-2 keywords only on broadcast interfaces. Before you configure the level-1 or level-2 keyword, enable IS-IS on the interface.
If no level is specified, the hello multiplier applies to both Level-1 and Level-2.
The value of hello multiplier multiplied by hello interval cannot be more than 65535.
Examples
# Set the hello multiplier to 6 for GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis timer holding-multiplier 6 level-2
Related commands
isis timer hello
isis timer lsp
Use isis timer lsp to configure the minimum interval for sending LSPs on the interface and specify the maximum number of LSPs that can be sent per time.
Use undo isis timer lsp to restore the default.
Syntax
isis timer lsp time [ count count ]
undo isis timer lsp
Default
The minimum interval for sending LSPs on the interface is 33 milliseconds, and the maximum number of LSPs that can be sent at a time is 5.
Views
Interface view
Predefined user roles
network-admin
Parameters
time: Specifies the minimum interval for sending link-state packets, in the range of 1 to 1000 milliseconds.
count: Specifies the maximum number of link-state packets to be sent at one time, in the range of 1 to 1000.
Usage guidelines
If a change occurs in the LSDB, IS-IS advertises the changed LSP to neighbors. You can specify the minimum interval for sending these LSPs.
Configure an appropriate LSP retransmission interval to avoid unnecessary retransmissions.
Examples
# Set the interval to 500 milliseconds for sending LSPs on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis timer lsp 500
Related commands
isis timer retransmit
isis timer retransmit
Use isis timer retransmit to configure the interval for retransmitting LSP packets over a point-to-point link.
Use undo isis timer retransmit to restore the default.
Syntax
isis timer retransmit seconds
undo isis timer retransmit
Default
The retransmission interval on a P2P link is 5 seconds.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the interval for retransmitting LSP packets, in the range of 1 to 300 seconds.
Usage guidelines
On a P2P link, IS-IS requires an advertised LSP be acknowledged. If no acknowledgment is received within a configurable interval, IS-IS will retransmit the LSP.
You do not need to use this command over a broadcast link where CSNPs are periodically broadcast to implement LSDB synchronization.
Examples
# Set the LSP retransmission interval on a P2P link to 50 seconds for Serial 2/1/1.
<Sysname> system-view
[Sysname] interface serial 2/1/1
[Sysname-Serial2/1/1] isis timer retransmit 50
Related commands
isis circuit-type p2p
isis timer lsp
isis topology enable
Use isis topology enable to enable IS-IS for the specified topology.
Use undo isis topology enable to disable IS-IS for the specified topology.
Syntax
isis topology enable
undo isis topology enable
Default
IS-IS is disabled for the topology.
Views
IPv4 unicast topology view
Predefined user roles
network-admin
Usage guidelines
To configure this command, you must complete the following tasks:
· Enable IS-IS on the interface.
· Create an IS-IS IPv4 unicast topology.
Examples
# Enable IS-IS for IPv4 unicast topology voice on the interface Gigabitethernet1/0/1.
<Sysname> system-view
[Sysname] isis 100
[Sysname-isis-100] address-family ipv4
[Sysname-isis-100-ipv4] topology voice tid 4000
[Sysname-isis-100-ipv4-topo-voice] quit
[Sysname-isis-100-ipv4] quit
[Sysname-isis-100] quit
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis enable 100
[Sysname-GigabitEthernet1/0/1] topology ipv4 voice
[Sysname-GigabitEthernet1/0/1-topo-voice] isis topology enable
is-level
Use is-level to specify the IS level.
Use undo is-level to restore the default.
Syntax
is-level { level-1 | level-1-2 | level-2 }
undo is-level
Default
The IS level is level-1-2.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
level-1: Specifies Level-1, which means IS-IS only calculates intra-area routes and maintains the Level-1 LSDB.
level-1-2: Specifies Level-1-2, which means IS-IS calculates routes and maintains the LSDBs for both Level-1 and Level-2.
level-2: Specifies Level-2, which means IS-IS calculates routes and maintains the LSDB for Level-2 only.
Usage guidelines
If the only area is an IP network, configure all the routers as Level-2 for scalability.
Examples
# Set the IS level to Level-1 for the IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] is-level level-1
is-name
Use is-name to specify a host name for the IS and enable dynamic system ID to hostname mapping.
Use undo is-name to disable dynamic system ID to hostname mapping.
Syntax
is-name sys-name
undo is-name
Default
Dynamic system ID to hostname mapping is disabled, and no host name is configured for the IS.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
sys-name: Specifies a host name for the local IS, a case-insensitive string of 1 to 64 characters.
Usage guidelines
To display the host name rather than the system ID of an IS by using the display isis lsdb command, first enable dynamic system ID to hostname mapping.
Examples
# Configure a host name for the local IS.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] is-name RUTA
Related commands
display isis name-table
is-name map
Use is-name map to configure a system ID to host name mapping for a remote IS.
Use undo is-name map to remove the mapping.
Syntax
is-name map sys-id map-sys-name
undo is-name map sys-id
Default
No system ID to host name mapping is configured for a remote IS.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
sys-id: Specifies the system ID or pseudonode ID of a remote IS.
map-sys-name: Specifies a host name for the remote IS, a case-insensitive string of 1 to 64 characters.
Usage guidelines
Each remote IS system ID corresponds to only one name.
Examples
# Map the host name RUTB to the system ID 0000.0000.0041 of the remote IS.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] is-name map 0000.0000.0041 RUTB
Related commands
display isis name-table
ispf enable
Use ispf enable to enable IS-IS incremental SPF (ISPF).
Use undo ispf enable to disable IS-IS ISPF.
Syntax
ispf enable
undo ispf enable
Default
IS-IS ISPF is enabled.
Views
IS-IS view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Usage guidelines
When a network topology is changed, ISPF recomputes only the affected part of the SPT, instead of the entire SPT.
Examples
# Enable IS-IS ISPF.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] ispf enable
log-peer-change
Use log-peer-change to enable the logging of neighbor state changes.
Use undo log-peer-change to disable the logging.
Syntax
log-peer-change
undo log-peer-change
Default
The logging of IS-IS neighbor state changes is enabled.
Views
IS-IS view
Predefined user roles
network-admin
Usage guidelines
This command enables sending logs about IS-IS neighbor state changes to the information center. For IS-IS neighbor state change logs to be sent correctly, you must also configure the information center parameters on the device. For more information about information center, see the network management and monitoring configuration guide for the device.
Examples
# Disable the logging of IS-IS neighbor state changes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] undo log-peer-change
lsp-fragments-extend
Use lsp-fragments–extend to enable LSP fragment extension for a level.
Use undo lsp-fragments–extend to restore the default.
Syntax
lsp-fragments-extend [ level-1 | level-1-2 | level-2 ]
undo lsp-fragments-extend
Default
LSP fragment extension is disabled.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
level-1: Applies the fragment extension to Level-1 LSPs.
level-1-2: Applies the fragment extension to both Level-1 and Level-2 LSPs.
level-2: Applies the fragment extension to Level-2 LSPs.
Usage guidelines
If no level is specified, the command enables LSP fragment extension for both Level-1 and Level-2.
Examples
# Enable LSP fragment extension for Level-2.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] lsp-fragments-extend level-2
lsp-length originate
Use lsp-length originate to configure the maximum size of generated Level-1 or Level-2 LSPs.
Use undo lsp-length originate to remove the configuration.
Syntax
lsp-length originate size [ level-1 | level-2 ]
undo lsp-length originate [ level-1 | level-2 ]
Default
The maximum size of generated Level-1 and Level-2 LSPs is 1497 bytes.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
size: Specifies the maximum size of LSP packets, in the range of 512 to 16384 bytes.
level-1: Applies the size to Level-1 LSP packets.
level-2: Applies the size to Level-2 LSP packets.
Usage guidelines
If neither Level-1 nor Level-2 is specified in the command, the configured maximum size applies to the current IS-IS level.
Examples
# Set the maximum size of the generated Level-2 LSPs to 1024 bytes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] lsp-length originate 1024 level-2
lsp-length receive
Use lsp-length receive to configure the maximum size of received LSPs.
Use undo lsp-length receive to restore the default.
Syntax
lsp-length receive size
undo lsp-length receive
Default
The maximum size of received LSPs is 1497 bytes.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
size: Specifies the maximum size of received LSPs, in the range of 512 to 16384 bytes.
Examples
# Configure the maximum size of received LSPs to 1024 bytes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] lsp-length receive 1024
maximum load-balancing
Use maximum load-balancing to configure the maximum number of ECMP routes for load balancing.
Use undo maximum load-balancing to restore the default.
Syntax
maximum load-balancing number
undo maximum load-balancing
Default
The maximum number of IS-IS ECMP routes is 32.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of ECMP routes, in the range of 1 to 32.
Examples
# Set the maximum number of ECMP routes to 2.
<Sysname> system-view
[Sysname] isis 100
[Sysname-isis-100] address-family ipv4
[Sysname-isis-100-ipv4] maximum load-balancing 2
network-entity
Use network-entity to configure the Network Entity Title (NET) for an IS-IS process.
Use undo network-entity to delete a NET.
Syntax
network-entity net
undo network-entity net
Default
No NET is configured.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
Usage guidelines
A NET is a special NSAP address with the SEL being 0. The length of the NET is in the range of 8 to 20 bytes.
A NET comprises the following parts:
· Area ID—With a length of 1 to 13 bytes.
· System ID—A system ID uniquely identifies a host or router in the area and has a fixed 6-byte length.
· SEL—It has a value of 0 and a fixed 1-byte length.
For example, a NET of ab.cdef.1234.5678.9abc.00 specifies the area ID ab.cdef, the system ID 1234.5678.9abc, and the SEL 00.
If you want to execute the cost-style, is-level, and network-entity commands for the same IS-IS process, execute the network-entity command after the other two commands to avoid data loss.
Examples
# Set the NET to 10.0001.1010.1020.1030.00, of which 10.0001 is the area ID and 1010.1020.1030 is the system ID.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] network-entity 10.0001.1010.1020.1030.00
Related commands
cost-style
isis
isis enable
is-level
non-stop-routing
Use non-stop-routing to enable IS-IS NSR.
Use undo non-stop-routing to disable IS-IS NSR.
Syntax
non-stop-routing
undo non-stop-routing
Default
IS-IS NSR is disabled.
Views
IS-IS view
Predefined user roles
network-admin
Usage guidelines
The following matrix shows the command and hardware compatibility:
|
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28/3600-51 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28-SI/3600-51-SI |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
· In standalone mode: No · In IRF mode: Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Command compatibility |
|
MSR810-LM-GL |
No |
|
MSR810-W-LM-GL |
No |
|
MSR830-6EI-GL |
No |
|
MSR830-10EI-GL |
No |
|
MSR830-6HI-GL |
No |
|
MSR830-10HI-GL |
No |
|
MSR2600-6-X1-GL |
No |
|
MSR3600-28-SI-GL |
No |
IS-IS NSR and IS-IS GR are mutually exclusive. Therefore, do not configure the non-stop-routing command and the graceful-restart command at the same time.
IS-IS NSR takes effect on a per-process basis. As a best practice, enable NSR for each IS-IS process.
Examples
# Enable NSR for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] non-stop-routing
pic
Use pic to enable IS-IS PIC.
Use undo pic to disable IS-IS PIC.
Syntax
pic [ additional-path-always ]
undo pic
Default
IS-IS PIC is enabled.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
additional-path-always: Allows the indirect suboptimal route as the backup route.
Usage guidelines
Prefix Independent Convergence (PIC) enables the device to speed up network convergence by ignoring the number of prefixes.
When both IS-IS PIC and IS-IS FRR are configured, only IS-IS FRR takes effect.
Examples
# Configure IS-IS PIC to support the indirect suboptimal route as the backup route.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] pic additional-path-always
preference
Use preference to configure the preference for IS-IS.
Use undo preference to restore the default.
Syntax
preference { preference | route-policy route-policy-name } *
undo preference
Default
IS-IS preference is 15.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
preference: Specifies an IS-IS protocol preference in the range of 1 to 255.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to assign a priority to the matching routes.
Usage guidelines
If a routing policy is specified in this command, the preference set by the routing policy applies to the matching routes. Other routes use the preference set by the preference command.
If multiple routing protocols find routes to the same destination, the route found by the routing protocol with the highest preference is selected as the optimal route.
Examples
# Set the preference for IS-IS to 25.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] preference 25
prefix-priority
Use prefix-priority to assign convergence priorities to specific IS-IS routes.
Use undo prefix-priority to remove the configuration.
Syntax
prefix-priority { critical | high | medium } { prefix-list prefix-list-name | tag tag-value }
prefix-priority route-policy route-policy-name
undo prefix-priority { critical | high | medium } [ prefix-list | tag ]
undo prefix-priority route-policy
Default
IS-IS routes have the lowest convergence priority.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
critical: Specifies the highest convergence priority.
high: Specifies the high convergence priority.
medium: Specifies the medium convergence priority.
prefix-list prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters.
tag tag-value: Specifies a tag value in the range of 1 to 4294967295.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
The higher the convergence priority, the faster the convergence speed.
IS-IS host routes have a medium convergence priority.
Examples
# Assign the high convergence priority to IS-IS routes permitted by IP prefix list standtest.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] prefix-priority high prefix-list standtest
reset isis all
Use reset isis all to clear all IS-IS data structure information.
Syntax
reset isis all [ process-id ] [ graceful-restart ]
Views
User view
Predefined user roles
network-admin
Parameters
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535 to clear the data structure information for an IS-IS process.
graceful-restart: Recovers the data through graceful restart after the data is cleared.
Usage guidelines
Use this command when LSPs must be updated immediately.
Examples
# Clear all IS-IS data structure information.
<Sysname> reset isis all
reset isis graceful-restart event-log
Use reset isis graceful-restart event-log to clear IS-IS GR log information.
Syntax
Centralized devices in standalone mode:
reset isis graceful-restart event-log
Distributed devices in standalone mode/centralized devices in IRF mode:
reset isis graceful-restart event-log slot slot-number
Distributed devices in IRF mode:
reset isis graceful-restart event-log chassis chassis-number slot slot-number
Views
User view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its ID. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument specifies the ID of the IRF member device. The slot-number argument specifies the slot number of the card. (Distributed devices in IRF mode.)
Examples
# Clear IS-IS GR log information about card 1.
<Sysname> reset isis graceful-restart event-log slot 1
reset isis non-stop-routing event-log
Use reset isis non-stop-routing event-log to clear IS-IS NSR log information.
Syntax
Distributed devices in standalone mode/centralized devices in IRF mode:
reset isis non-stop-routing event-log slot slot-number
Distributed devices in IRF mode:
reset isis non-stop-routing event-log chassis chassis-number slot slot-number
Views
User view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its ID. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument specifies the ID of the IRF member device. The slot-number argument specifies the slot number of the card. (Distributed devices in IRF mode.)
Usage guidelines
The following matrix shows the command and hardware compatibility:
|
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28/3600-51 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28-SI/3600-51-SI |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
· In standalone mode: No · In IRF mode: Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Command compatibility |
|
MSR810-LM-GL |
No |
|
MSR810-W-LM-GL |
No |
|
MSR830-6EI-GL |
No |
|
MSR830-10EI-GL |
No |
|
MSR830-6HI-GL |
No |
|
MSR830-10HI-GL |
No |
|
MSR2600-6-X1-GL |
No |
|
MSR3600-28-SI-GL |
No |
Examples
# Clear IS-IS NSR log information on card 1.
<Sysname> reset isis non-stop-routing event-log slot 1
reset isis peer
Use reset isis peer to clear data structure information for a specified IS-IS neighbor.
Syntax
reset isis peer system-id [ process-id ]
Views
User view
Predefined user roles
network-admin
Parameters
system-id: Specifies an IS-IS neighbor by its system ID.
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535 to clear data structure information for the neighbor in the specified IS-IS process.
Usage guidelines
Use this command when you re-establish an IS-IS neighbor relationship.
Examples
# Clear the data structure information of the neighbor with the system ID 0000.0c11.1111.
<Sysname> reset isis peer 0000.0c11.1111
reset osi statistics
Use reset osi statistics to clear OSI packet statistics.
Syntax
reset osi statistics
Views
User view
Predefined user roles
network-admin
Usage guidelines
To obtain OSI packet statistics from the specified time point, first clear the existing statistics.
Examples
# Clear OSI packet statistics.
<Sysname> reset osi statistics
Related commands
display osi statistics
set-att
Use set-att to set the ATT bit of Level-1 LSPs.
Use undo set-att to restore the default.
Syntax
set-att { always | never }
undo set-att
Default
The ATT bit is not set for Level-1 LSPs.
Views
IS-IS view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
always: Sets the ATT bit of Level-1 LSPs.
never: Keeps the ATT bit of Level-1 LSPs not set.
Examples
# Set the ATT bit of Level-1 LSPs.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] set-att always
set-overload
Use set-overload to set the overload bit.
Use undo set-overload to restore the default.
Syntax
set-overload [ on-startup [ [ start-from-nbr system-id [ timeout1 [ nbr-timeout ] ] ] | timeout2 | wait-for-bgp [ timeout3 ] ] ] [ allow { external | interlevel } * ]
undo set-overload
Default
The overload bit is not set.
Views
IS-IS view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
on-startup: Sets the overload bit upon system startup.
start-from-nbr system-id [ timeout1 [ nbr-timeout ] ]: Starts the nbr-timeout timer when the router begins to establish the neighbor relationship with the neighbor after system startup. If the neighbor relationship is formed within the nbr-timeout interval, IS-IS keeps the overload bit set. If not, the bit is cleared. IS-IS keeps the overload bit set within the timeout1 interval after the neighbor relationship is formed within the nbr-timeout interval.
· system-id—Specifies the neighbor.
· timeout1—The timeout1 interval is in the range of 5 to 86400 seconds, and the default is 600 seconds.
· nbr-timeout—The timer has an interval from 5 to 86400 seconds. The default is 1200 seconds.
timeout2: Sets the overload bit within the timeout2 interval after system startup. The interval is in the range of 5 to 86400 seconds, and the default is 600 seconds.
wait-for-bgp [ timeout3 ]: Starts the timeout3 timer for BGP convergence after system startup. If BGP is not converged within the timeout3 interval, IS-IS clears the overload bit. The value range for the timeout3 argument is 5 to 86400 seconds, and the default is 600 seconds.
allow: Allows advertising address prefixes. By default, no address prefixes are allowed to be advertised when the overload bit is set.
external: Allows advertising IP address prefixes redistributed from other routing protocols with the allow keyword specified.
interlevel: Allows advertising IP address prefixes learned from different IS-IS levels with the allow keyword specified.
Usage guidelines
If the on-startup keyword is specified, IS-IS sets the overload bit upon system startup and keeps it set within the timeout2 interval.
Examples
# Set overload flag on the current router.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] set-overload
snmp context-name
Use snmp context-name to set the context name for the SNMP object for managing IS-IS.
Use undo snmp context-name to restore the default.
Syntax
snmp context-name context-name
undo snmp context-name
Default
No context name is set for the SNMP object for managing IS-IS.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
context-name: Specifies a context name, a case-sensitive string of 1 to 32 characters.
Usage guidelines
TRILL shares the standard IS-IS MIB with IS-IS. The standard IS-IS MIB provides only single-instance MIB objects. For SNMP to correctly identify TRILL's management information in the standard IS-IS MIB, you must configure a unique context for TRILL.
Context is a method introduced to SNMPv3 for multiple-instance management. For SNMPv1/v2c, you must specify a community name as a context name for protocol identification.
Examples
# Configure the context name as isis for the SNMP object for managing IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] snmp context-name isis
snmp-agent trap enable isis
Use snmp-agent trap enable isis to enable IS-IS SNMP notifications.
Use undo snmp-agent trap enable isis to disable IS-IS SNMP notifications.
Syntax
snmp-agent trap enable isis [ adjacency-state-change | area-mismatch | authentication | authentication-type | buffsize-mismatch | id-length-mismatch | lsdboverload-state-change | lsp-corrupt | lsp-parse-error | lsp-size-exceeded | manual-address-drop | max-seq-exceeded | maxarea-mismatch | own-lsp-purge | protocol-support | rejected-adjacency | skip-sequence-number | version-skew ] *
undo snmp-agent trap enable isis [ adjacency-state-change | area-mismatch | authentication | authentication-type | buffsize-mismatch | id-length-mismatch | lsdboverload-state-change | lsp-corrupt | lsp-parse-error | lsp-size-exceeded | manual-address-drop | max-seq-exceeded | maxarea-mismatch | own-lsp-purge | protocol-support | rejected-adjacency | skip-sequence-number | version-skew ] *
Default
IS-IS SNMP notifications are enabled.
Views
System view
Predefined user roles
network-admin
Parameters
adjacency-state-change: Specifies notifications about IS-IS adjacency status changes.
area-mismatch: Specifies notifications about area address mismatches between hello packets.
authentication: Specifies notifications about authentication failures of IS-IS packets.
authentication-type: Specifies notifications about authentication type errors of IS-IS packets.
buffsize-mismatch: Specifies notifications about buffer size mismatches for LSPs.
id-length-mismatch: Specifies notifications about system ID length mismatches of IS-IS packets.
lsdboverload-state-change: Specifies notifications about LSDB overload state changes.
lsp-corrupt: Specifies notifications about LSP checksum errors in the LSDB.
lsp-parse-error: Specifies notifications about LSP packet parse failures.
lsp-size-exceeded: Specifies notifications about propagation failures caused by oversized LSPs.
manual-address-drop: Specifies notifications about manually configured area addresses that have been dropped.
max-seq-exceeded: Specifies notifications about attempts to exceed the maximum LSP sequence number.
maxarea-mismatch: Specifies notifications about maximum area address mismatches of hello packets.
own-lsp-purge: Specifies notifications about attempts to remove the local LSP.
protocol-support: Specifies notifications about supported-protocol mismatches.
rejected-adjacency: Specifies notifications about adjacency creation failures.
skip-sequence-number: Specifies notifications about LSP sequence number duplications.
version-skew: Specifies notifications about hello packet version mismatches.
Usage guidelines
If you do not specify a notification, this command enables all IS-IS SNMP notifications.
If no IS-IS process exists, the configuration is not allowed.
This function does not take effect if all configured IS-IS processes are deleted.
Examples
# Disable IS-IS SNMP notifications.
<Sysname> system-view
[Sysname] undo snmp-agent trap enable isis
summary
Use summary to configure a summary route.
Use undo summary to remove a summary route.
Syntax
summary ip-address { mask-length | mask } [ avoid-feedback | generate_null0_route | [ level-1 | level-1-2 | level-2 ] | tag tag ] *
undo summary ip-address { mask-length | mask } [ level-1 | level-1-2 | level-2 ]
Default
No summary route is configured.
Views
IS-IS IPv4 unicast address family view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the destination IP address of the summary route.
mask-length: Specifies the mask length of the summary route, in the range of 0 to 32.
mask: Specifies the mask of the destination IP address, in dotted decimal notation.
avoid-feedback: Avoids learning summary routes by route calculation.
generate_null0_route: Generates the Null 0 route to avoid routing loops.
level-1: Summarizes only the routes redistributed to Level-1.
level-1-2: Summarizes the routes redistributed to both Level-1 and Level-2.
level-2: Summarizes only the routes redistributed to Level-2.
tag tag: Specifies a management tag in the range of 1 to 4294967295.
Usage guidelines
If no level is specified, only level-2 routes are summarized.
If no topology is specified, routes for the base topology are summarized.
To reduce the size of the routing table, as well as the size of LSP and LSDB generated by the router, summarize multiple contiguous networks into a single network. You can summarize native IS-IS routes and redistributed routes. After summarization, the cost of the summary route is the smallest cost of the summarized routes.
The router summarizes only routes generated from local LSPs.
Examples
# Configure a summary route of 202.0.0.0/8.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv4
[Sysname-isis-1-ipv4] summary 202.0.0.0 255.0.0.0
timer lsp-generation
Use timer lsp-generation to set the LSP generation interval.
Use undo timer lsp-generation to remove the configuration.
Syntax
timer lsp-generation maximum-interval [ minimum-interval [ incremental-interval ] ] [ level-1 | level-2 ]
undo timer lsp-generation [ level-1 | level-2 ]
Default
The maximum interval is 5 seconds, the minimum interval is 50 milliseconds, and the incremental interval is 200 milliseconds.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
maximum-interval: Specifies the maximum interval in the range of 1 to 120 seconds.
minimum-interval: Specifies the minimum interval in the range of 10 to 60000 milliseconds.
incremental-interval: Specifies the incremental interval in the range of 10 to 60000 milliseconds.
level-1: Applies the intervals to Level-1.
level-2: Applies the intervals to Level-2. If no level is specified, the specified intervals apply to both Level-1 and Level-2.
Usage guidelines
By adjusting the LSP generation interval, you can prevent bandwidth and router resources from being over consumed due to frequent topology changes.
When network changes are not frequent, the minimum-interval is adopted. If network changes become frequent, the LSP generation interval increases by the incremental-interval each time a generation occurs until the maximum-interval is reached.
The minimum interval and the incremental interval cannot be greater than the maximum interval.
Examples
# Set the maximum interval, minimum interval, and incremental interval to 10 seconds, 100 milliseconds, and 200 milliseconds, respectively.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1]timer lsp-generation 10 100 200
timer lsp-max-age
Use timer lsp-max-age to set the LSP maximum age in the LSDB.
Use undo timer lsp-max-age to restore the default.
Syntax
timer lsp-max-age seconds
undo timer lsp-max-age
Default
The LSP maximum age is 1200 seconds.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
seconds: Specifies the LSP maximum aging time in the range of 1 to 65535 seconds.
Usage guidelines
Each LSP has an age that decreases in the LSDB. Any LSP with an age of 0 is deleted from the LSDB. You can adjust the age value based on the scale of a network.
Examples
# Set the maximum LSP age to 1500 seconds.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] timer lsp-max-age 1500
Related commands
timer lsp-refresh
timer lsp-refresh
Use timer lsp-refresh to set the LSP refresh interval.
Use undo timer lsp-refresh to restore the default.
Syntax
timer lsp-refresh seconds
undo timer lsp-refresh
Default
The default LSP refresh interval is 900 seconds.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
seconds: Specifies the LSP refresh interval in the range of 1 to 65534 seconds.
Usage guidelines
Each router refreshes its LSPs at a configurable interval and sends them to other routers to achieve the following purposes:
· Prevent valid routes from aging out.
· Synchronize LSPs in the network.
A smaller refresh interval speeds up network convergence but consumes more bandwidth.
To refresh LSPs before they are aged out, the interval configured by the timer lsp-refresh command must be smaller than that configured by the timer lsp-max-age command.
Examples
# Set the LSP refresh interval to 1500 seconds.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] timer lsp-refresh 1500
Related commands
timer lsp-max-age
timer spf
Use timer spf to set the SPF calculation interval.
Use undo timer spf to restore the default.
Syntax
timer spf maximum-interval [ minimum-interval [ incremental-interval ] ]
undo timer spf
Default
The maximum interval is 5 seconds, the minimum interval is 50 milliseconds, and the incremental interval is 200 milliseconds.
Views
IS-IS view
IS-IS IPv4 unicast topology view
Predefined user roles
network-admin
Parameters
maximum-interval: Specifies the maximum SPF calculation interval in the range of 1 to 120 seconds.
minimum-interval: Specifies the minimum SPF calculation interval in the range of 10 to 60000 milliseconds.
incremental-interval: Specifies the incremental SPF calculation interval in the range of 10 to 60000 milliseconds.
Usage guidelines
Based on the LSDB, an IS-IS router uses the SPF algorithm to calculate a shortest path tree with itself being the root, and uses the shortest path tree to determine the next hop to a destination network. By adjusting the SPF calculation interval, you can prevent bandwidth and router resources from being overused due to frequent topology changes.
When network changes are not frequent, the minimum-interval is adopted. If network changes become frequent, the SPF calculation interval increases by the incremental-interval each time a generation happens until the maximum-interval is reached.
The minimum interval and the incremental interval cannot be greater than the maximum interval.
Examples
# Set the maximum interval to 10 seconds, the minimum interval to 100 milliseconds, and the incremental interval to 300 milliseconds, respectively.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] timer spf 10 100 300
topology
Use topology to create an IS-IS IPv4 unicast topology and enter its view.
Use undo topology to remove the IS-IS IPv4 unicast topology and all configurations in the view.
Syntax
topology topo-name [ tid tid ]
undo topology topo-name
Default
No IS-IS IPv4 unicast topologies exist.
Views
IS-IS IPv4 unicast address family view
Predefined user roles
network-admin
Parameters
topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters.
tid: Specifies the topology number in the range of 6 to 4095.
Usage guidelines
The name base is reserved for the base topology.
This command takes effect after the related IPv4 subtopology is configured.
This command can be configured only when the link cost style is wide, compatible, or wide-compatible.
Examples
# Create IS-IS IPv4 unicast topology voice (4000) and enter its view.
<Sysname> system-view
[Sysname] isis 100
[Sysname-isis-100] address-family ipv4
[Sysname-isis-100-ipv4] topology voice tid 4000
[Sysname-isis-100-ipv4-topo-voice]
Related commands
cost-style
virtual-system
Use virtual-system to configure a virtual system ID for the IS-IS process.
Use undo virtual-system to remove a virtual system ID.
Syntax
virtual-system virtual-system-id
undo virtual-system virtual-system-id
Default
No virtual system ID is configured.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
virtual-system-id: Specifies a virtual system ID for the IS-IS process.
Examples
# Set a virtual system ID of 2222.2222.2222 for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] virtual-system 2222.2222.2222
BGP commands
IPv6-related parameters are not supported on the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS.
· MSR3600-28-SI/3600-51-SI.
· MSR3600-28-SI-GL.
L2VPN and multicast are not supported on the 810-LMS/810-LUS/MSR3600-28-SI/3600-51-SI routers.
NSR is not supported on the 810-LMS/810-LUS routers.
address-family ipv4
Use address-family ipv4 to create the BGP IPv4 unicast address family, BGP-VPN IPv4 unicast address family, BGP IPv4 multicast address family, or BGP IPv4 RT filter 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, BGP-VPN IPv4 unicast address family, BGP IPv4 multicast address family, or BGP IPv4 RT filter address family and all its configurations.
Syntax
In BGP instance view:
address-family ipv4 [ multicast | rtfilter | unicast ]
undo address-family ipv4 [ multicast | rtfilter | unicast ]
In BGP-VPN instance view:
address-family ipv4 [ unicast ]
undo address-family ipv4 [ unicast ]
Default
No BGP IPv4 unicast address family, BGP-VPN IPv4 unicast address family, BGP IPv4 multicast address family, or BGP IPv4 RT filter address family exists.
Views
BGP instance view
BGP-VPN instance view
Predefined user roles
network-admin
Parameters
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. If this command is executed with the unicast keyword in BGP-VPN instance view, it places you into BGP-VPN IPv4 unicast address family view.
multicast: Specifies the IPv4 multicast address family.
rtfilter: Specifies the IPv4 RT filter address family.
Usage guidelines
Configurations made in BGP IPv4 unicast address family view apply only to the BGP IPv4 unicast routes and peers of the public network.
Configurations made in BGP-VPN IPv4 unicast address family view apply only to the BGP IPv4 unicast routes and peers of the specified VPN instance.
Configurations made in BGP IPv4 multicast address family view apply only to the BGP IPv4 multicast routes and peers.
Configurations made in BGP IPv4 RT filter address family view apply only to the BGP IPv4 RT filter routes and peers.
By default, the unicast keyword is used if you do not specify the multicast, rtfilter, or unicast keyword.
Examples
# In BGP instance view of BGP instance default, 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, BGP-VPN IPv6 unicast address family, or BGP IPv6 multicast 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, BGP-VPN IPv6 unicast address family, or BGP IPv6 multicast address family, and all its configurations.
Syntax
In BGP instance view:
address-family ipv6 [ multicast | unicast ]
undo address-family ipv6 [ multicast | unicast ]
In BGP-VPN instance view:
address-family ipv6 [ unicast ]
undo address-family ipv6 [ unicast ]
Default
No BGP IPv6 unicast address family, BGP-VPN IPv6 unicast address family, or BGP IPv6 multicast address family exists.
Views
BGP instance view
BGP-VPN instance view
Predefined user roles
network-admin
Parameters
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. If this command is executed with the unicast keyword in BGP-VPN instance view, it places you into BGP-VPN IPv6 unicast address family view.
multicast: Specifies the IPv6 multicast address family.
Usage guidelines
Configurations made in BGP IPv6 unicast address family view apply only to the BGP IPv6 unicast routes and peers of the public network.
Configurations made in BGP-VPN IPv6 unicast address family view apply only to the BGP IPv6 unicast routes and peers of the specified VPN instance.
Configurations made in BGP IPv6 multicast address family view apply only to the BGP IPv6 multicast routes and peers.
By default, the unicast keyword is used if neither the multicast keyword nor the unicast keyword is specified.
Examples
# In BGP instance view of BGP instance default, create the BGP IPv6 unicast address family and enter its view.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv6 unicast
address-family link-state
Use address-family link-state to create the BGP LS address family and enter its view, or enter the view of the existing address family.
Use undo address-family link-state to remove the BGP LS address family and all its configurations.
Syntax
address-family link-state
undo address-family link-state
Default
No BGP LS address family exists.
Views
BGP instance view
Predefined user roles
network-admin
Usage guidelines
Configurations made in BGP LS address family view apply only to the BGP LS routes and peers of the public network.
Examples
# In BGP instance view, create the BGP LS address family and enter its view.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family link-state
[Sysname-bgp-default-ls]
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.
Syntax
advertise-rib-active
undo advertise-rib-active
Default
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.
Views
BGP instance view
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
Predefined user roles
network-admin
Usage guidelines
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.
· VPNv4 routes.
· VPNv6 routes.
· IPv4 multicast routes.
· IPv6 multicast routes.
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.
Examples
# In BGP instance view of BGP instance default, 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.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP IPv4 multicast address family view:
aggregate ipv4-address { mask | mask-length } [ as-set | attribute-policy route-policy-name | detail-suppressed | origin-policy route-policy-name | suppress-policy route-policy-name ] *
undo aggregate ipv4-address { mask | mask-length }
In BGP IPv6 unicast address family view/BGP IPv6 multicast address family view:
aggregate ipv6-address prefix-length [ as-set | attribute-policy route-policy-name | detail-suppressed | origin-policy route-policy-name | suppress-policy route-policy-name ] *
undo aggregate ipv6-address prefix-length
No summary routes are configured.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
Predefined user roles
network-admin
Parameters
ipv4-address: Specifies an IPv4 summary address.
mask: Specifies a mask for the IPv4 summary address, in dotted decimal notation.
mask-length: Specifies a mask length for the IPv4 summary address, in the range of 0 to 32.
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.
attribute-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to set attributes for the summary route.
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.
origin-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to select routes to be summarized.
suppress-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter more specific routes to be advertised. Routes permitted by the specified routing policy are not advertised. Routes denied by the specified routing policy are advertised.
Usage guidelines
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 76 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. |
|
attribute-policy |
Sets attributes except the AS-PATH attribute for the summary route. The peer route-policy command can achieve the same purpose. |
|
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. |
|
origin-policy |
Summarizes only routes matching a routing policy. If the destination address of a route falls within the summary network but does not match the routing policy, the route is not summarized. It is not controlled by the detail-suppressed and suppress-policy keywords. There is no need to configure apply clauses for the routing policy applied by the origin-policy keyword because they do not take effect. |
|
suppress-policy |
Disables advertisement of some more specific routes filtered by a routing policy. The routing policy uses if-match clauses to filter routes. There is no need to configure apply clauses for the routing policy applied by the suppress-policy keyword because they do not take effect. |
Examples
# In BGP IPv4 unicast address family view of BGP instance default, create a 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
<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 as-set detail-suppressed
# In BGP IPv4 unicast address family view of BGP instance default, create a summary route 1.1.0.0/16 in the BGP routing table, and set the COMMUNITY attribute of the summary route to INTERNET.
<Sysname> system-view
[Sysname] route-policy commu permit node 0
[Sysname-route-policy-commu-0] apply community internet
[Sysname-route-policy-commu-0] quit
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] aggregate 1.1.0.0 255.255.0.0 attribute-policy commu
# In BGP IPv4 unicast address family view of BGP instance default, create a summary route 1.1.0.0/16 in the BGP routing table, and configure BGP to not summarize route 1.1.1.0/24.
<Sysname> system-view
[Sysname] ip prefix-list spert deny 1.1.1.0 24
[Sysname] ip prefix-list spert permit 0.0.0.0 0 less-equal 32
[Sysname] route-policy srcrt permit node 0
[Sysname-route-policy-srcrt-0] if-match ip address prefix-list spert
[Sysname-route-policy-srcrt-0] quit
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] aggregate 1.1.0.0 255.255.0.0 origin-policy srcrt
# In BGP IPv4 unicast address family view of BGP instance default, create a summary route 1.1.0.0/16 in the BGP routing table, and disable BGP to advertise the specific route 1.1.1.0/24.
<Sysname> system-view
[Sysname] ip prefix-list spert permit 1.1.1.0 24
[Sysname] ip prefix-list spert deny 0.0.0.0 0 less-equal 32
[Sysname] route-policy suprt permit node 0
[Sysname-route-policy-suprt-0] if-match ip address prefix-list spert
[Sysname-route-policy-suprt-0] quit
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] aggregate 1.1.0.0 255.255.0.0 suppress-policy suprt
Related commands
display bgp routing-table ipv4 multicast
display bgp routing-table ipv4 unicast
display bgp routing-table ipv6 multicast
display bgp routing-table ipv6 unicast
summary automatic
balance
Use balance to enable load balancing and set the maximum number of BGP ECMP routes for load balancing.
Use undo balance to disable load balancing.
Syntax
balance [ ebgp | eibgp | ibgp ] number
undo balance [ ebgp | eibgp | ibgp ]
Default
Load balancing is disabled.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
Predefined user roles
network-admin
Parameters
ebgp: Enables load balancing over EBGP routes.
eibgp: Enables load balancing between EBGP and IBGP routes.
ibgp: Enables load balancing over IBGP routes.
number: Specifies the maximum number of BGP ECMP routes for load balancing, in the range of 1 to 32. When it is set to 1, load balancing is disabled.
Usage guidelines
Unlike IGP, BGP has no explicit metric for making load balancing decision. Instead, it implements load balancing by modifying route selection rules.
If multiple BGP routes destined for a network meet the following conditions, the device selects the specified number of routes for load balancing:
· The routes have the same ORIGIN, LOCAL_PREF, and MED attributes. If the balance as-path-neglect command is not configured, the routes must also have the same AS_PATH attribute.
· The routes have the same MPLS label assignment status (labeled or not labeled).
If you do not specify the ibgp, eibgp, or ebgp keyword, this command enables load balancing over EBGP routes and IBGP routes, but not between EBGP and IBGP routes.
After you execute the balance eibgp number command, the balance [ ebgp | ibgp ] number and undo balance [ ebgp | ibgp ] commands cannot be executed; and vice versa.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, enable load balancing and set the maximum number of BGP ECMP routes used for load balancing to 2.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] balance 2
Related commands
balance as-path-neglect
balance as-path-neglect
Use balance as-path-neglect to enable BGP to ignore the AS_PATH attribute when it implements load balancing.
Use undo balance as-path-neglect to restore the default.
Syntax
balance as-path-neglect
undo balance as-path-neglect
Default
BGP does not ignore the AS_PATH attribute when it implements load balancing.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
Predefined user roles
network-admin
Usage guidelines
For BGP to implement load balancing over routes with different AS_PATH attributes, you must use this command together with the balance command.
After this command is executed, BGP ignores the AS_PATH attributes in the routes for load balancing and changes the attributes of the advertised routes to those of the optimal route. The operations might cause routing loops. In addition, this command might also affect the NetStream data. Therefore, use this command with caution.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, enable BGP to ignore the AS_PATH attribute when it implements load balancing.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] balance as-path-neglect
Related commands
balance
balance as-path-relax
Use balance as-path-relax to enable load balancing for routes that have different AS_PATH attributes of the same length.
Use undo balance as-path-relax to restore the default.
Syntax
balance as-path-relax
undo balance as-path-relax
Default
BGP cannot perform load balancing for routes that have different AS_PATH attributes of the same length.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
Predefined user roles
network-admin
Usage guidelines
For BGP to perform load balancing for routes with different AS_PATH attributes of the same length, you must use this command together with the balance command.
If you configure both the balance as-path-relax and balance as-path-neglect commands, the balance as-path-neglect command takes effect.
After this command is executed, BGP ignores the AS_PATH attributes in the routes for load balancing and changes the attributes of the advertised routes to those of the optimal route. This might cause routing loops and affect NetStream statistics. Therefore, use this command with caution.
Examples
# In BGP IPv4 unicast address family view, enable load balancing for routes that have different AS_PATH attributes of the same length.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] balance as-path-relax
bestroute as-path-neglect
Use bestroute as-path-neglect to configure BGP to ignore the AS_PATH attribute during optimal route selection.
Use undo bestroute as-path-neglect to restore the default.
Syntax
bestroute as-path-neglect
undo bestroute as-path-neglect
Default
BGP considers the AS_PATH attribute during optimal route selection.
Views
BGP instance view
BGP-VPN instance view
Predefined user roles
network-admin
Examples
# In BGP instance view of BGP instance default, ignore AS_PATH during optimal route selection.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] bestroute as-path-neglect
bestroute compare-med
Use bestroute compare-med to enable MED comparison for routes on a per-AS basis.
Use undo bestroute compare-med to restore the default.
Syntax
bestroute compare-med
undo bestroute compare-med
Default
MED comparison for routes on a per-AS basis is disabled.
Views
BGP instance view
BGP-VPN instance view
Predefined user roles
network-admin
Usage guidelines
By default, BGP does not compare MEDs for routes from the same AS. When a router learns a new route, it compares the route with the optimal route in its BGP routing table. If the new route is more optimal, it becomes the optimal route in the BGP routing table. In this way, route learning sequence might affect optimal route selection.
To solve the selection problem, the router puts routes received from the same AS into a group when the bestroute compare-med command is configured. The router then selects the route with the lowest MED from the same group, and compares routes from different groups.
Examples
# In BGP instance view of BGP instance default, enable MED comparison for routes on a per-AS basis.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] bestroute compare-med
bestroute igp-metric-ignore
Use bestroute igp-metric-ignore to configure BGP to ignore IGP metrics during optimal route selection.
Use undo bestroute igp-metric-ignore to restore the default.
Syntax
bestroute igp-metric-ignore
undo bestroute igp-metric-ignore
Default
BGP considers IGP metrics during optimal route selection. If multiple routes to the same destination are available, BGP selects the route with the smallest IGP metric as the optimal route.
Views
BGP instance view
BGP-VPN instance view
Predefined user roles
network-admin
Examples
# In BGP instance view of BGP instance default, ignore IGP metrics during optimal route selection.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] bestroute igp-metric-ignore
bestroute med-confederation
Use bestroute med-confederation to enable MED comparison for routes received from confederation peers.
Use undo bestroute med-confederation to restore the default.
Syntax
bestroute med-confederation
undo bestroute med-confederation
Default
MED comparison is disabled for routes received from confederation peers.
Views
BGP instance view
BGP-VPN instance view
Predefined user roles
network-admin
Usage guidelines
This command enables BGP to compare the MEDs of routes received from confederation peers. However, if a route from a confederation peer has an AS number that does not belong to the confederation, BGP does not compare the route with other routes. For example, a confederation has three AS numbers 65006, 65007, and 65009. BGP receives three routes from different confederation peers. The AS_PATH attributes of these routes are 65006 65009, 65007 65009, and 65008 65009, and the MED values of them are 2, 3, and 1. Because the third route's AS_PATH attribute contains AS number 65008, which does not belong to the confederation, BGP does not compare it with other routes. As a result, the first route becomes the optimal route.
Examples
# In BGP instance view of BGP instance default, enable MED comparison for routes received from confederation peers.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] bestroute med-confederation
bgp
Use bgp to enable a BGP instance and enter its view.
Use undo bgp to disable a BGP instance.
Syntax
bgp as-number [ instance instance-name ]
undo bgp [ as-number [ instance instance-name ] ]
Default
BGP is disabled and no BGP instances exist.
Views
System view
Predefined user roles
network-admin
Parameters
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 BGP instance default.
Usage guidelines
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.
You can create multiple public address families for a BGP instance. However, each public address family (except for public VPNv4 and VPNv6 address families) can belong to only one BGP instance.
You can create multiple VPN instances for a BGP instance, and each VPN instance can have multiple address families. A VPN instance can belong to only one BGP instance.
You cannot specify the same peer in the same address family of different BGP instances.
The IPv4 and IPv6 multicast address families must belong to the same BGP instance.
Different BGP instances can have the same AS number but cannot have the same name.
Examples
# 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 on reboot.
Use undo bgp update-delay on-startup to restore the default.
Syntax
bgp update-delay on-startup seconds
undo bgp update-delay on-startup
Default
BGP immediately sends route updates on reboot.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
seconds: Specifies the delay time in the range of 1 to 3600 seconds.
Usage guidelines
After you configure this command, BGP redistributes all routes from other neighbors on reboot, selects the optimal route, and then advertises it. Using this command can reduce traffic loss caused by reboot.
Examples
# In BGP instance view of BGP instance default, configure BGP to delay sending route updates on reboot and set the delay time to 100 seconds.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] bgp update-delay on-startup 100
Related commands
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.
Syntax
bgp update-delay on-startup prefix-list prefix-list-name
undo bgp update-delay on-startup prefix-list
Default
No prefix list is specified to filter routes.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
prefix-list-name: Specifies an IPv4 prefix list by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
After the bgp update-delay on-startup command is configured, BGP delays sending updates for all routes on 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.
Examples
# In BGP instance view of BGP instance default, configure BGP to send updates 100 seconds after reboot and immediately send updates for routes that match the 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
Related commands
bgp update-delay on-startup
bgp-policy accounting
Use bgp-policy accounting to enable BGP policy accounting on an interface.
Use undo bgp-policy accounting to disable BGP policy accounting on an interface.
Syntax
bgp-policy accounting { input | output } * [ source ]
undo bgp-policy accounting { input | output } * [ source ]
Default
BGP policy accounting is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
input: Enables BGP policy accounting for incoming traffic.
output: Enables BGP policy accounting for outgoing traffic.
source: Classifies IP traffic based on the source IP address. If you do not specify this keyword, the command classifies IP traffic based on the destination IP address.
Usage guidelines
BGP policy accounting provides the following functionalities:
· Classifies IP traffic by BGP path attributes such as NEXT HOP, COMMUNITY, and AS_PATH.
· Assigns an index to each class of traffic.
· Collects statistics based on indexes.
BGP policy accounting supports the following traffic classification policies:
· Source IP address-based policy—Used to collect statistics for traffic from a specific source.
BGP searches routes to the source address, obtains the traffic index for the routes, and collects statistics for the traffic identified by the index.
· Destination IP address-based policy—Used to collect statistics for traffic destined to a specific address.
BGP searches routes to the destination address, obtains the traffic index for the routes, and collects statistics for the traffic identified by the index.
Examples
# Enable BGP policy accounting based on source IP address for traffic on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] bgp-policy accounting input output source
Related commands
aggregate
apply traffic-index
import-route
network
peer default-route-advertise
peer route-policy
compare-different-as-med
Use compare-different-as-med to enable MED comparison for routes from peers in different ASs.
Use undo compare-different-as-med to restore the default.
Syntax
compare-different-as-med
undo compare-different-as-med
Default
MED comparison is disabled for routes from peers in different ASs.
Views
BGP instance view
BGP-VPN instance view
Predefined user roles
network-admin
Usage guidelines
If multiple routes to a destination exist, the route with the smallest MED is selected.
Do not use this command unless relevant ASs adopt the same IGP protocol and routing selection method.
Examples
# In BGP instance view of BGP instance default, enable MED comparison for routes from peers in different ASs.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] compare-different-as-med
confederation id
Use confederation id to configure a confederation ID.
Use undo confederation id to restore the default.
Syntax
confederation id as-number
undo confederation id
Default
No confederation ID is configured.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
as-number: Specifies an AS number that identifies the confederation, in the range of 1 to 4294967295.
Usage guidelines
You can split an AS into several sub-ASs, and each sub-AS remains fully meshed. These sub-ASs form a confederation. Key path attributes of a route, such as the Next_HOP, MED, and LOCAL_PREF, are not discarded when crossing each sub-AS. The sub-ASs still look like one AS from the perspective of other ASs. The AS number is the confederation ID.
Confederation can ensure the integrity of the former AS, and solve the problem of too many IBGP connections in the AS.
Configure the same confederation ID for all routers in one confederation.
For a non-confederation BGP router that establishes a BGP connection to a router in a confederation, the confederation ID is the AS number of the router.
Examples
# Confederation 9 of BGP instance default consists of four sub-ASs numbered 38, 39, 40 and 41. The peer 10.1.1.1 is a member of sub-AS 38. The peer 200.1.1.1 is a member outside of confederation 9, which belongs to AS 98. Confederation 9 looks like one AS (with AS number 9) from the perspective of the peer 200.1.1.1. This example uses a router in sub-AS 41.
<Sysname> system-view
[Sysname] bgp 41
[Sysname-bgp-default] confederation id 9
[Sysname-bgp-default] confederation peer-as 38 39 40
[Sysname-bgp-default] group Confed38 external
[Sysname-bgp-default] peer Confed38 as-number 38
[Sysname-bgp-default] peer 10.1.1.1 group Confed38
[Sysname-bgp-default] group Remote98 external
[Sysname-bgp-default] peer Remote98 as-number 98
[Sysname-bgp-default] peer 200.1.1.1 group Remote98
Related commands
confederation nonstandard
confederation nonstandard
Use confederation nonstandard to enable compatibility with routers not compliant with RFC 3065 in the confederation.
Use undo confederation nonstandard to restore the default.
Syntax
confederation nonstandard
undo confederation nonstandard
Default
The device is compatible with only routers compliant with RFC 3065 in the confederation.
Views
BGP instance view
Predefined user roles
network-admin
Usage guidelines
Configure this command on all routers compliant with RFC 3065 to interact with those routers not compliant with RFC 3065 in the confederation.
Examples
# Confederation 100 of BGP instance default consists of two sub-ASs, 64000 and 65000, and contains routers not compliant with RFC 3065. Enable compatibility with routers not compliant with RFC 3065 in the confederation.
<Sysname> system-view
[Sysname] bgp 64000
[Sysname-bgp-default] confederation id 100
[Sysname-bgp-default] confederation peer-as 65000
[Sysname-bgp-default] confederation nonstandard
Related commands
confederation id
confederation peer-as
confederation peer-as
Use confederation peer-as to specify confederation peer sub-ASs.
Use undo confederation peer-as to remove the specified confederation peer sub-ASs.
Syntax
confederation peer-as as-number-list
undo confederation peer-as [ as-number-list ]
Default
No confederation peer sub-ASs are specified.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
as-number-list: Specifies a sub-AS number list. A maximum of 32 sub-ASs can be configured in one command line. The expression is as-number-list = as-number &<1-32>. The as-number argument specifies a sub-AS number in the range of 1 to 4294967295, and &<1-32> indicates that a maximum of 32 numbers can be specified.
Usage guidelines
Before this configuration, use the confederation id command to specify the confederation for the sub-ASs.
If the undo confederation peer-as command is executed without the as-number-list argument, all confederation peer sub-ASs are removed.
Examples
# In BGP instance view of BGP instance default, specify confederation peer sub-ASs 2000 and 2001.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] confederation id 10
[Sysname-bgp-default] confederation peer-as 2000 2001
confederation id
confederation nonstandard
dampening
Use dampening to enable BGP route dampening.
Use undo dampening to restore the default.
Syntax
dampening [ half-life-reachable half-life-unreachable reuse suppress ceiling | route-policy route-policy-name ] *
undo dampening
Default
Route dampening is disabled.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
Predefined user roles
network-admin
Parameters
half-life-reachable: Specifies a half-life for active routes, in the range of 1 to 45 minutes. By default, the value is 15 minutes.
half-life-unreachable: Specifies a half-life for suppressed routes, in the range of 1 to 45 minutes. By default, the value is 15 minutes.
reuse: Specifies a reuse threshold value for suppressed routes, in the range of 1 to 20000. A suppressed route whose penalty value decreases under the value is reused. By default, the reuse value is 750. The reuse threshold must be less than the suppression threshold.
suppress: Specifies a suppression threshold in the range of 1 to 20000. The route with a penalty value greater than the threshold is suppressed. The default value is 2000.
ceiling: Specifies a ceiling penalty value in the range of 1001 to 20000. The value must be greater than the suppress value. By default, the value is 16000.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
This command dampens only EBGP routes.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, configure BGP route dampening. Set the half-life for both active and suppressed routes to 10 minutes, the reuse threshold to 1000, the suppression threshold to 2000, and the ceiling penalty to 10000.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] dampening 10 10 1000 2000 10000
Related commands
display bgp dampening parameter
default local-preference
Use default local-preference to configure a default local preference.
Use undo default local-preference to restore the default.
Syntax
default local-preference value
undo default local-preference
Default
The default local preference is 100.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
Predefined user roles
network-admin
Parameters
value: Specifies a default local preference in the range of 0 to 4294967295. A larger value represents a higher preference.
Usage guidelines
You can also use the apply local-preference command in a routing policy to configure the local preference for BGP routes. If no routing policy is configured, all BGP routes use the local preference set by the default local-preference command. If a routing policy is configured, BGP routes matching the routing policy use the local preference set by the apply local-preference command. Other BGP routes use the local preference set by the default local-preference command.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, set the default local preference to 180.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] default local-preference 180
apply local-preference
route-policy
default med
Use default med to specify a default MED value.
Use undo default med to restore the default.
Syntax
default med med-value
undo default med
Default
The default MED value is 0.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
Predefined user roles
network-admin
Parameters
med-value: Specifies the default MED value in the range of 0 to 4294967295.
Usage guidelines
BGP selects a MED value in the following order:
1. MED set by the apply cost command.
2. MED set by the med keyword in the import-route command.
3. MED set by the default med command.
4. Original MED of a BGP route, or MED changed from the metric of a redistributed IGP route.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, set the default MED to 25.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] default med 25
Related commands
apply cost
import-route
route-policy
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.
Syntax
default-route imported
undo default-route imported
Default
Default route redistribution into the BGP routing table is disabled.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
Predefined user roles
network-admin
Usage guidelines
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.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, 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 dampening parameter
Use display bgp dampening parameter to display BGP route dampening parameters.
Syntax
display bgp [ instance instance-name ] dampening parameter { ipv4 | ipv6 } { multicast | [ unicast ] [ vpn-instance vpn-instance-name ] }
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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 dampening parameters for the default BGP instance.
ipv4: Displays BGP IPv4 route dampening parameters.
ipv6: Displays BGP IPv6 route dampening parameters.
multicast: Displays BGP multicast route dampening parameters.
unicast: Displays BGP unicast route dampening parameters.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command displays BGP route dampening parameters for the public network.
Usage guidelines
By default, the unicast keyword is used if neither the multicast keyword nor the unicast keyword is specified.
Examples
# Display public BGP IPv4 unicast route dampening parameters for the default BGP instance.
<Sysname> display bgp dampening parameter ipv4
Maximum suppression time (in seconds) : 3973
Ceiling value : 16000
Reuse value : 750
Half-life time for reachable routes (in seconds) : 900
Half-life time for unreachable routes (in seconds) : 900
Suppression threshold : 2000
Table 77 Command output
|
Field |
Description |
|
Maximum suppression time |
Maximum time (in seconds) for the penalty value to decrease from the ceiling value to the reuse value. |
|
Ceiling value |
Penalty ceiling value. |
|
Reuse value |
Reuse threshold. |
Related commands
dampening
display bgp group
Use display bgp group to display BGP peer group information.
Syntax
display bgp [ instance instance-name ] group ipv4 { mdt | multicast | rtfilter | [ unicast ] [ vpn-instance vpn-instance-name ] } [ group-name group-name ]
display bgp [ instance instance-name ] group ipv6 { multicast | [ unicast ] [ vpn-instance vpn-instance-name ] } [ group-name group-name ]
display bgp [ instance instance-name ] group link-state [ group-name group-name ]
display bgp [ instance instance-name ] group vpnv4 [ vpn-instance vpn-instance-name ] [ group-name group-name ]
display bgp [ instance instance-name ] group { l2vpn | vpnv6 } [ group-name group-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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.
link-state: Displays BGP LS peer group information.
mdt: Displays BGP MDT peer group information.
multicast: Displays BGP multicast peer group information.
rtfilter: Displays BGP IPv4 RT filter peer group information.
unicast: Displays BGP unicast peer group information.
vpnv4: Displays BGP VPNv4 peer group information.
l2vpn: Displays BGP L2VPN peer group information.
vpnv6: Displays BGP VPNv6 peer group information.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command displays BGP peer group information for the public network.
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.
Usage guidelines
By default, the unicast keyword is used if none of the unicast, rtfilter, multicast, and mdt keywords is specified.
Examples
# Display brief information about all public BGP IPv4 unicast peer groups in the default BGP instance.
BGP peer group: group1
Remote AS: 600
Type: external
Members:
1.1.1.10
BGP peer group: group2
Remote AS number: not specified
Type: external
Members:
2.2.2.2
# Display detailed information about public BGP IPv4 unicast peer group group1 in the default BGP instance.
<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:
* - Dynamically created peer
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 public BGP IPv6 unicast peer group group2 in the default BGP instance.
<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
IPsec profile name: profile001
Site-of-Origin: Not specified
Routing policy configured:
No routing policy is configured
Members:
* - Dynamically created peer
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 78 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. This field does not apply to BGP L2VPN. |
|
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. This field does not apply to BGP L2VPN. |
|
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. This field does not apply to BGP L2VPN. |
|
Site-of-Origin |
SoO for the peer group. |
|
Routing policy configured |
Routing policy configured for the peer group. If you do not specify a routing policy, this field displays No routing policy is configured. This field does not apply to BGP L2VPN. |
|
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, IPv6, VPNv4, and VPNv6 address families, this field displays the number of prefixes received from the peer. For MPLS L2VPN, this field displays the number of label blocks received from the peer. For VPLS, this field displays the total number of label blocks and VPLS PEs discovered by BGP. For the IPv4 MDT address family, this field displays the number of MDT messages 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.
Syntax
display bgp instance-info
Views
Any view
Predefined user roles
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 79 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 link-state
Use display bgp link-state to display BGP LS information.
Syntax
display bgp [ instance instance-name ] link-state [ ls-prefix | peer { ipv4-address | ipv6-address } { advertised | received } [ statistics ] | statistics ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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 LS information for the default BGP instance.
ls-prefix: Specifies an LS prefix. If you do not specify this argument, the command displays all BGP LS information.
ipv4-address: Specifies a peer by its IPv4 address.
ipv6-address: Specifies a peer by its IPv6 address.
advertised: Displays advertised LS information.
received: Displays received LS information.
statistics: Displays statistics about LS messages.
Usage guidelines
If you do not specify any parameters, this command displays brief BGP LS information.
Examples
# Display brief BGP LS information for the public network.
<Sysname> display bgp link-state
Total number of routes: 2
BGP local router ID is 1.1.2.1
Status codes: * - valid, > - best, d – dampened, h – history,
s – suppressed, S – stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Prefix codes: E link, V node, T IP reachable route, u/U unknown,
I Identifier, N local node, R remote node, L link, P prefix,
L1/L2 ISIS level-1/level-2, O OSPF, D direct, S static,
a area-ID, , l link-ID, t topology-ID, s ISO-ID,
c confed-ID/ASN, b bgp-identifier, r router-ID,
i if-address, n nbr-address, o OSPF Route-type, p IP-prefix
d designated router address
* >e Network : [V][O][I0x0][N[c20][b1.1.1.2][a0.0.0.0][r1.1.1.2]]/376
NextHop : 1.1.1.2 LocPrf :
PrefVal : 0 OutLabel : NULL
MED :
Path/Ogn: 20i
* >e Network : [T][O][I0x0][N[c20][b1.1.1.2][a0.0.0.0][r1.1.1.2]][P[o0x1][p1.1.1.0/24]]/480
NextHop : 1.1.1.2 LocPrf :
PrefVal : 0 OutLabel : NULL
MED :
Path/Ogn: 20i
Table 80 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. |
|
Prefix codes |
Route status codes: · E – link. · V – node. · T – IP reachable route. · u/U – unknown. · I – Identifier. · N – local node. · R – remote node. · L – link. · P – prefix. · L1/L2 – ISIS level-1/level-2. · O – OSPF. · D – direct. · S – static. · a – area-ID. · l – link-ID. · t – topology-ID. · s – ISO-ID. · c – confed-ID/ASN. · b – bgp-identifier. · r – router-ID. · i – if-address. · n – peer-address. · o – OSPF Route-type. · p – IP-prefix. · d – designated router address. |
|
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 |
NLRI for the LS. |
|
NextHop |
Next hop IP address. |
|
LocPrf |
Local preference. |
|
OutLabel |
Outgoing label of the route. |
|
MED |
MED attribute. |
|
Path/Ogn |
AS_PATH and ORIGIN attributes of the route: · AS_PATH—Records the ASs the route has passed, which avoids routing loops. · ORIGIN—Identifies the origin of the route. |
# Display detailed BGP LS information with the specified LS prefix.
<Sysname> display bgp link-state [V][O][I0x0][N[c20][b1.1.1.2][a0.0.0.0][r1.1.1.2]]/376
BGP local router ID: 1.1.1.2
Local AS number: 20
Paths: 1 available, 1 best
BGP LS information of [V][O][I0x0][N[c20][b1.1.1.2][a0.0.0.0][r1.1.1.2]]/376:
Imported route.
Original nexthop: 0.0.0.0
OutLabel : NULL
LS : Node flag bits: 30[EA]
AS-path : (null)
Origin : igp
Attribute value : pref-val 32768
State : valid, local, best
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
Table 81 Command output
|
Field |
Description |
|
Paths |
Number of routes: · available—Number of valid routes. · best—Number of optimal routes. |
|
BGP LS information of |
NLRI prefix. |
|
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. |
|
LS |
LS attribute: · Node flag bits—Node attribute in hexadecimal format: ¡ 10[A]—OSPF ABR bit. ¡ 30[E]—OSPF External bit. · Metric—Link or prefix cost. |
|
AS-path |
AS_PATH attribute of the route, which records the ASs the route has passed and avoids routing loops. |
|
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. |
|
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. |
display bgp network
Use display bgp network to display information about routes advertised by the network command and shortcut routes configured by the network short-cut command.
Syntax
display bgp [ instance instance-name ] network { ipv4 | ipv6 } { multicast | [ unicast ] [ vpn-instance vpn-instance-name ] }
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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.
multicast: Displays BGP multicast address family information.
unicast: Displays BGP unicast address family information.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command displays routing information for the public network.
Usage guidelines
By default, the unicast keyword is used if neither the multicast keyword nor the unicast keyword is specified.
Examples
# Display information about routes advertised by the network command and shortcut routes configured by the network short-cut command in the public IPv4 unicast address family of the default BGP instance.
<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 and shortcut routes configured by the network short-cut command in the public IPv6 unicast address family of the default BGP instance.
<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
# Display information about routes advertised by the network command and shortcut routes configured by the network short-cut command in the public IPv4 unicast address family in VPN instance vpn1 of the default BGP instance.
<Sysname> display bgp network ipv4 vpn-instance vpn1
BGP local router ID: 192.168.1.135
Local AS number: 100
Network Mask Route-policy Short-cut
50.1.1.0 255.255.255.0 No
40.1.1.0 255.255.255.0 Yes
Table 82 Command output
|
Field |
Description |
|
Network |
Destination network address of the routes advertised by the network command and the shortcut routes. |
|
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 |
Whether the route is a shortcut route: · Yes. · No. |
display bgp non-stop-routing status
Use display bgp non-stop-routing status to display BGP NSR status information.
Syntax
display bgp [ instance instance-name ] non-stop-routing status
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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 NSR status information for the default BGP instance.
Usage guidelines
The following matrix shows the command and hardware compatibility:
|
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/MSR810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28/3600-51 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28-SI/3600-51-SI |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
· In standalone mode: No · In IRF mode: Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Command compatibility |
|
MSR810-LM-GL |
No |
|
MSR810-W-LM-GL |
No |
|
MSR830-6EI-GL |
No |
|
MSR830-10EI-GL |
No |
|
MSR830-6HI-GL |
No |
|
MSR830-10HI-GL |
No |
|
MSR2600-6-X1-GL |
No |
|
MSR3600-28-SI-GL |
No |
Examples
# Display BGP NSR status information for the default BGP instance.
<Sysname> display bgp non-stop-routing status
BGP NSR status: Ready
Location of preferred standby process: Chassis 0 slot 1
TCP NSR status: Ready
Table 83 Command output
|
Field |
Description |
|
BGP NSR status |
BGP NSR status: · Ready—BGP NSR has backed up BGP neighbor and routing information from the active process to the standby process. In this state, BGP NSR can ensure continuous routing when an active/standby process switchover occurs. · Not ready—BGP NSR is backing up BGP neighbor and routing information from the active process to the standby process. If an active/standby process switchover occurs in this state, traffic is interrupted and the BGP session will be re-established. · Not configured—BGP NSR is disabled. |
|
Location of preferred standby process |
ID of the slot where the preferred standby process resides (distributed devices in standalone mode). ID of the IRF member device where the preferred standby process resides (centralized devices in IRF mode). Chassis ID and slot ID where the preferred standby process resides (distributed devices in IRF mode). |
|
TCP NSR status |
TCP NSR status: · Ready—TCP NSR has backed up TCP connection information from the active process to the standby process. · Not ready—TCP NSR is backing up TCP connection information from the active process to the standby process. |
display bgp paths
Use display bgp paths to display BGP path attribute information.
Syntax
display bgp [ instance instance-name ] paths [ as-regular-expression ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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 for the default BGP instance.
<Sysname> display bgp paths
RefCount MED Path/Origin
3 0 ?
2 0 100i
3 0 100i
1 0 ?
1 0 ?
1 0 ?
Table 84 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.
Syntax
display bgp [ instance instance-name ] peer ipv4 { mdt | multicast | rtfilter | [ unicast ] [ vpn-instance vpn-instance-name ] } [ ipv4-address mask-length | { ipv4-address | group-name group-name } log-info | [ ipv4-address ] verbose ]
display bgp [ instance instance-name ] peer ipv6 { multicast | [ unicast ] [ vpn-instance vpn-instance-name ] } [ ipv6-address prefix-length | { ipv6-address | group-name group-name } log-info | [ ipv6-address ] verbose ]
display bgp [ instance instance-name ] peer ipv6 [ unicast ] [ ipv4-address mask-length | ipv4-address log-info | [ ipv4-address ] verbose ]
display bgp [ instance instance-name ] peer link-state [ ipv4-address mask-length | ipv6-address prefix-length | { ipv4-address | ipv6-address | group-name group-name } log-info | [ ipv4-address | ipv6-address ] verbose ]
display bgp [ instance instance-name ] peer vpnv4 [ vpn-instance vpn-instance-name ] [ ipv4-address mask-length | { ipv4-address | group-name group-name } log-info | [ ipv4-address ] verbose ]
display bgp [ instance instance-name ] peer { l2vpn | vpnv6 } [ ipv4-address mask-length | { ipv4-address | group-name group-name } log-info | [ ipv4-address ] verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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.
link-state: Displays BGP LS peer or peer group information.
vpnv4: Displays BGP VPNv4 peer or peer group information.
l2vpn: Displays BGP L2VPN peer or peer group information.
vpnv6: Displays BGP VPNv6 peer or peer group information.
mdt: Displays BGP MDT peer or peer group information.
multicast: Displays BGP multicast peer or peer group information.
rtfilter: Displays BGP IPv4 RT filter peer or peer group information.
unicast: Displays BGP unicast peer or peer group information.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command displays BGP peer or peer group information for the public network.
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.
Usage guidelines
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 none of the unicast, multicast, rtfilter, and mdt keywords is specified.
Examples
# Display brief information about all public BGP IPv4 unicast peers in the default BGP instance.
<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 85 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, IPv6, VPNv4, and VPNv6 address families, this field displays the number of prefixes that have been received from the peer and added into the local BGP routing table. For MPLS L2VPN, this field displays the number of label blocks received from the peer. For VPLS, this field displays the total number of label blocks and VPLS PEs discovered by BGP. For the IPv4 MDT address family, this field displays the number of MDT messages received from the peer. For the IPv4 RT filter address family, this field displays the number of RT messages 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 brief information about all dynamic peers in network 1.1.1.0/24 in the default BGP instance.
<Sysname> display bgp peer ipv4 1.1.1.0 24
Type: EBGP link
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 Multicast: Configured
Address family IPv4 Label: Configured
Address family VPNv4: Configured
Address family IPv4 RT-Filter: Configured
Address family IPv6 Unicast: Configured
Address family VPNv6: 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:
1.1.1.3
# Display brief information about all dynamic peers in network 1::/64 in the default BGP instance.
<Sysname> display bgp peer ipv6 1:: 64
Type: IBGP link
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 86 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. |
|
Address family IPv4 Multicast |
IPv4 multicast address family capability. |
|
Address family IPv6 Multicast |
IPv6 multicast address family capability. |
|
Address family link-state |
LS address family capability. |
|
Address family MDT |
IPv4 MDT address family capability. |
|
Address family L2VPN |
L2VPN address family capability. |
|
Address family L2VPN VPWS (Draft) |
L2VPN VPWS address family capability. |
|
Address family IPv4 RT-Filter |
IPv4 RT filter address family capability. |
|
Maximum allowed prefix number |
Maximum number of routes allowed to learn from the peer. This field does not apply to BGP L2VPN. |
|
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. This field does not apply to BGP L2VPN. |
|
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. This field does not apply to BGP L2VPN. |
|
BFD |
Whether BFD is enabled to detect the link to the BGP peers. |
|
IPsec profile name |
IPsec profile applied to the IPv6 BGP peer. This field is available only for the IPv6 unicast and IPv6 multicast address families. |
|
Routing policy configured |
Routing policy configured for the peer. If you do not specify a routing policy, this field displays No routing policy is configured. This field does not apply to BGP L2VPN. |
|
Dynamic peers |
IP addresses of dynamic peers. |
# Display detailed information about the public BGP IPv4 unicast peer 10.2.1.2 in the default BGP instance.
<Sysname> display bgp peer ipv4 10.2.1.2 verbose
Peer: 10.2.1.2 Local: 192.168.100.1
Type: EBGP link
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 support BGP multi-protocol extended
Peer support BGP route refresh capability
Peer support 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
Peer Preferred Value: 0
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 the public BGP IPv6 unicast peer 1::2 in the default BGP instance.
<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 support BGP multi-protocol extended
Peer support BGP route refresh capability
Peer support 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
Peer preferred value: 0
GTSM has been enabled, and the maximum number of hops is 10
BFD: Enabled
IPsec profile name: profile001
Site-of-Origin: Not specified
Routing policy configured:
No routing policy is configured
# Display detailed information about BGP L2VPN peer 10.1.1.1 in the default BGP instance.
<Sysname> display bgp peer l2vpn 10.1.1.1 verbose
Peer: 10.1.1.1 Local: 192.168.1.136
Type: EBGP link
BGP version 4, remote router ID 192.168.1.135
BGP current state: Established, Up for 00h01m25s
BGP current event: KATimerExpired
BGP last state: OpenConfirm
Port: Local - 179 Remote - 1049
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 support BGP multi-protocol extended
Peer support BGP route refresh capability
Peer support BGP route AS4 capability
Address family IPv4 Unicast: advertised and received
Address family L2VPN: advertised
Address family L2VPN VPWS (Draft): 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
Peer Preferred Value: 0
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 87 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 support 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. |
||
|
Address family IPv4 Multicast |
IPv4 multicast address family capability: routes of the address family can be advertised and received. |
||
|
Address family IPv6 Multicast |
IPv6 multicast address family capability: routes of the address family can be advertised and received. |
||
|
Address family LS |
LS address family capability: routes of the address family can be advertised and received. |
||
|
Address family MDT |
IPv4 MDT address family capability: routes of the address family can be advertised and received. |
||
|
Address family L2VPN |
L2VPN address family capability: routes of the address family can be advertised and received. |
||
|
Address family L2VPN VPWS (Draft) |
L2VPN VPWS address family capability (draft-kompella-ppvpn-l2vpn-03): routes of the address family can be advertised and received. |
||
|
Address family IPv4 RT-Filter |
IPv4 RT filter 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. This field does not apply to BGP L2VPN. |
||
|
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. This field does not apply to BGP L2VPN. |
||
|
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. This field does not apply to BGP L2VPN. |
||
|
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. |
||
|
IPsec profile name |
IPsec profile applied to the IPv6 BGP peer. This field is available only for the IPv6 unicast and IPv6 multicast address families. |
||
|
Routing policy configured |
Routing policy configured for the peer. If you do not specify a routing policy, this field displays No routing policy is configured. This field does not apply to BGP L2VPN. |
||
# Display log information for the public BGP IPv4 unicast peer 1.1.1.1 in the default BGP instance.
<Sysname> display bgp peer ipv4 1.1.1.1 log-info
Peer : 1.1.1.1
Date Time State Notification
Error/SubError
06-Feb-2013 22:54:42 Down Send notification with error 6/4
Cease/Administrative Reset
<administrative reset>
Table 88 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 dampened
Use display bgp routing-table dampened to display dampened BGP routes.
Syntax
display bgp [ instance instance-name ] routing-table dampened { ipv4 | ipv6 } { multicast | [ unicast ] [ vpn-instance vpn-instance-name ] }
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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 dampened BGP routes for the default BGP instance.
ipv4: Displays dampened BGP IPv4 routes.
ipv6: Displays dampened BGP IPv6 routes.
multicast: Displays dampened BGP multicast routes.
unicast: Displays dampened BGP unicast routes.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command displays dampened BGP routes for the public network.
Usage guidelines
By default, the unicast keyword is used if neither the multicast keyword nor the unicast keyword is specified.
Examples
# Display dampened BGP IPv4 unicast routes in the default BGP instance.
<Sysname> display bgp routing-table dampened ipv4
Total number of routes: 1
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 Reuse Path/Ogn
de 20.1.1.0/24 10.1.1.2 00:56:27 100i
# Display dampened BGP IPv6 unicast routes in the default BGP instance.
<Sysname> display bgp routing-table dampened ipv6
Total number of routes: 2
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
From : 10.1.1.1 Reuse : 00:39:49
Path/Ogn: 100i
de Network : 2:: PrefixLen : 64
From : 1::1 Reuse : 00:39:49
Path/Ogn: 100i
Table 89 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 |
IP address from which the route was received. |
|
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. |
Related commands
dampening
reset bgp dampening
display bgp routing-table flap-info
Use display bgp routing-table flap-info to display BGP route flap statistics.
Syntax
display bgp [ instance instance-name ] routing-table flap-info ipv4 { multicast | [ unicast ] [ vpn-instance vpn-instance-name ] } [ ipv4-address [ { mask | mask-length } [ longest-match ] ] | as-path-acl as-path-acl-number ]
display bgp [ instance instance-name ] routing-table flap-info ipv6 { multicast | [ unicast ] [ vpn-instance vpn-instance-name ] } [ ipv6-address prefix-length | as-path-acl as-path-acl-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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.
multicast: Displays BGP multicast route flap statistics.
unicast: Displays BGP unicast route flap statistics.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command displays BGP route flap statistics for the public network.
ipv4-address: Specifies a destination network address.
mask: Specifies a network mask, in dotted decimal notation.
mask-length: Specifies a mask length in the range of 0 to 32.
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.
Usage guidelines
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 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 or multicast route that matches both the specified destination network address and the mask (or mask length).
By default, the unicast keyword is used if neither the multicast keyword nor the unicast keyword is specified.
Examples
# Display public BGP IPv4 unicast route flap statistics for the default BGP instance.
<Sysname> display bgp routing-table flap-info ipv4
Total number of routes: 1
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 public BGP IPv6 unicast route flap statistics for the default BGP instance.
<Sysname> display bgp routing-table flap-info ipv6
Total number of routes: 2
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
From : 10.1.1.1 Flaps : 5
Duration: 00:03:25 Reuse : 00:39:28
Path/Ogn: 100i
de Network : 2:: PrefixLen : 64
From : 1::1 Flaps : 5
Duration: 00:03:25 Reuse : 00:39:28
Path/Ogn: 100i
Table 90 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. |
Related commands
dampening
reset bgp flap-info
display bgp routing-table ipv4 multicast
Use display bgp routing-table ipv4 multicast to display BGP IPv4 multicast routing information.
Syntax
display bgp [ instance instance-name ] routing-table ipv4 multicast [ ipv4-address [ { mask | mask-length } [ longest-match ] ] | ipv4-address [ mask | mask-length ] advertise-info | as-path-acl as-path-acl-number | community-list { { basic-community-list-number | comm-list-name } [ whole-match ] | adv-community-list-number } | peer ipv4-address { advertised-routes | received-routes } [ ipv4-address [ mask | mask-length ] | statistics ] | statistics ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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 multicast routing information for the default BGP instance.
ipv4-address: Specifies a destination network address.
mask: Specifies a network mask, in dotted decimal notation.
mask-length: Specifies a mask length in the range of 0 to 32.
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 multicast routes.
as-path-acl as-path-acl-number: Displays BGP IPv4 multicast routes that match the AS path list specified by its number in the range of 1 to 256.
community-list: Displays BGP IPv4 multicast routes that match a community list.
basic-community-list-number: Specifies a basic community list by its number in the range of 1 to 99.
comm-list-name: Specifies a community list by its name, a case-sensitive string of 1 to 63 characters.
whole-match: Displays BGP IPv4 multicast routes exactly matching the specified community list. If you do not specify this keyword, the command displays BGP IPv4 multicast routes whose COMMUNITY attributes include the specified community list.
adv-community-list-number: Specifies an advanced community list by its number in the range of 100 to 199.
peer ipv4-address: Displays BGP IPv4 multicast routing information advertised to or received from the specified peer.
advertised-routes: Displays BGP IPv4 multicast routing information advertised to the specified peer.
received-routes: Displays BGP IPv4 multicast routing information received from the specified peer.
statistics: Displays routing statistics.
Usage guidelines
If you do not specify any parameters, this command displays brief information about all BGP IPv4 multicast 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 multicast route that matches both the specified destination network address and the mask (or mask length).
Examples
# Display brief information about all public BGP IPv4 multicast routes in the default BGP instance.
<Sysname> display bgp routing-table ipv4 multicast
Total number of routes: 3
BGP local router ID is 192.168.1.62
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* > 5.5.5.5/32 127.0.0.1 0 32768 ?
* > 192.168.1.0 192.168.1.62 0 32768 ?
* > 192.168.1.62/32 127.0.0.1 0 32768 ?
# Display information about BGP IPv4 multicast routes that match AS path list 20 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 multicast as-path-acl 20
Total number of routes: 3
BGP local router ID is 192.168.1.62
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* > 5.5.5.5/32 127.0.0.1 0 32768 ?
* > 192.168.1.0 192.168.1.62 0 32768 ?
* > 192.168.1.62/32 127.0.0.1 0 32768 ?
# Display information about BGP IPv4 multicast routes that match BGP community list 100 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 multicast community-list 100
Total number of routes: 3
BGP local router ID is 192.168.1.62
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* > 5.5.5.5/32 127.0.0.1 0 32768 ?
* > 192.168.1.0 192.168.1.62 0 32768 ?
* > 192.168.1.62/32 127.0.0.1 0 32768 ?
# Display information about all BGP IPv4 multicast routes advertised to peer 192.168.1.139 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 multicast peer 192.168.1.139 advertised-routes
Total number of routes: 2
BGP local router ID is 192.168.1.62
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf Path/Ogn
* > 5.5.5.5/32 127.0.0.1 0 100 ?
* > 192.168.1.0 192.168.1.62 0 100 ?
# Display information about all BGP IPv4 multicast routes received from peer 192.168.1.139 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 multicast peer 192.168.1.139 received-routes
Total number of routes: 2
BGP local router ID is 192.168.1.62
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* >i 8.8.8.8/32 192.168.1.139 0 100 0 ?
* i 192.168.1.0 192.168.1.139 0 100 0 ?
Table 91 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. |
|
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. · ORIGIN—Identifies the origin of the route. |
# Display detailed information about public BGP IPv4 multicast routes destined to network 5.5.5.5/32 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 multicast 5.5.5.5 32
BGP local router ID: 192.168.1.139
Local AS number: 100
Paths: 1 available, 1 best
BGP routing table information of 5.5.5.5/32:
From : 192.168.1.62 (192.168.1.62)
Rely nexthop : 192.168.1.62
Original nexthop: 192.168.1.62
OutLabel : NULL
AS-path : (null)
Origin : incomplete
Attribute value : MED 0, localpref 100, pref-val 0
State : valid, internal, best
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
Table 92 Command output
|
Field |
Description |
|
Paths |
Number of routes: · available—Number of valid routes. · best—Number of optimal routes. |
|
From |
IP address of 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. |
|
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. |
|
AS-path |
AS_PATH attribute of the route. |
|
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. |
|
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. |
# Display statistics for BGP IPv4 multicast routes advertised to peer 192.168.1.62 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 multicast peer 192.168.1.62 advertised-routes statistics
Advertised routes total: 2
# Display statistics for BGP IPv4 multicast routes received from peer 192.168.1.62 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 multicast peer 192.168.1.62 received-routes statistics
Received routes total: 2
Table 93 Command output
|
Field |
Description |
|
Advertised routes total |
Total number of advertised routes. |
|
Received routes total |
Total number of received routes. |
# Display BGP IPv4 multicast route statistics for the default BGP instance.
<Sysname> display bgp routing-table ipv4 multicast statistics
Total number of routes: 5
Table 94 Command output
|
Field |
Description |
|
Total number of routes |
Total number of routes. |
# Display advertisement information for the public BGP IPv4 multicast route destined to network 8.8.8.8/32 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 multicast 8.8.8.8 32 advertise-info
BGP local router ID: 192.168.1.139
Local AS number: 100
Paths: 1 best
BGP routing table information of 8.8.8.8/32:
Advertised to peers (1 in total):
192.168.1.62
Table 95 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 8.8.8.8/32 |
Advertisement information for network 8.8.8.8/32. |
|
Advertised to peers (1 in total) |
Peers to which the network has been advertised. |
Related commands
ip as-path
ip community-list
display bgp routing-table ipv4 rtfilter
Use display bgp routing-table ipv4 rtfilter to display BGP IPv4 RT filter routing information.
Syntax
Views
Any view
Predefined user roles
Parameters
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 RT filter routing information for the default BGP instance.
default-rt: Displays BGP IPv4 RT filter routing information for an all-zero RT.
origin-as as-number: Specifies an origin AS by its number.
route-target: Specifies an RT, a string of 3 to 21 characters.
An RT has the following formats:
· 16-bit AS number:32-bit user-defined number. For example, 101: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.
advertise-info: Displays advertisement information for BGP IPv4 RT filter routes.
peer ip-address: Displays BGP IPv4 RT filter routing information advertised to or received from the specified peer.
advertised-routes: Displays BGP IPv4 RT filter routing information advertised to the specified peer.
received-routes: Displays BGP IPv4 RT filter routing information received from the specified peer.
statistics: Displays routing statistics.
Usage guidelines
If you do not specify any parameters, this command displays brief information about all BGP IPv4 RT filter routes.
Examples
# Display brief information about all public BGP IPv4 RT filter routes for the default BGP instance.
<Sysname> display bgp routing-table ipv4 rtfilter
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
Origin: i - IGP, e - EGP, ? - incomplete
Total number of routes from all PEs: 2
Origin AS: 100
Total number of routes: 2
* >e Network : <100:1> PrefixLen : 96
NextHop : 1.1.1.2 LocPrf :
PrefVal : 0
MED :
Path/Ogn: 100i
* >e Network : <1.1.1.1:1> PrefixLen : 96
NextHop : 1.1.1.2 LocPrf :
PrefVal : 0
MED :
Path/Ogn: 100i
# Display information about BGP IPv4 RT filter routes that match origin AS 100 for the default BGP instance.
<Sysname> display bgp routing-table ipv4 rtfilter origin-as 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
Origin: i - IGP, e - EGP, ? - incomplete
Origin AS: 100
Total number of routes: 2
* >e Network : <100:1> PrefixLen : 96
NextHop : 1.1.1.2 LocPrf :
PrefVal : 0
MED :
Path/Ogn: 100i
* >e Network : <1.1.1.1:1> PrefixLen : 96
NextHop : 1.1.1.2 LocPrf :
PrefVal : 0
MED :
Path/Ogn: 100i
# Display information about all public BGP IPv4 RT filter routes advertised to peer 10.2.1.2 for the default BGP instance.
<Sysname> display bgp routing-table ipv4 rtfilter peer 10.2.1.2 advertised-routes
Total number of routes: 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
Origin: i - IGP, e - EGP, ? - incomplete
Origin AS: 100
Total number of routes: 1
* > Network : <100:1> PrefixLen : 96
NextHop : 1.1.1.2 LocPrf :
MED : 0
Path/Ogn: i
# Display information about all public BGP IPv4 RT filter routes received from peer 10.2.1.2 for the default BGP instance.
<Sysname> display bgp routing-table ipv4 rtfilter peer 10.2.1.2 received-routes
Total number of routes: 1
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
Origin AS: 100
Total number of routes: 1
* >e Network : <100:1> PrefixLen : 96
NextHop : 10.1.1.1 LocPrf :
PrefVal : 0
MED : 0
Path/Ogn: 100i
Table 96 Command output
|
Field |
Description |
|
Origin AS |
Origin AS of the RT filter routes. |
|
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. · e – EGP—Learned through EGP. · ?– incomplete—Unknown origin. |
|
Network |
RT value. |
|
PrefixLen |
Length of the RT plus the 4-byte AS number, which equals 96. If the RT is default-rt, this field displays 0. |
|
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. · ORIGIN—Identifies the origin of the route. |
# Display detailed information about BGP IPv4 RT filter route 100:1 for the default BGP instance.
<Sysname> display bgp routing-table ipv4 rtfilter 100:1
BGP local router ID: 192.168.100.1
Local AS number: 100
Origin AS: 100
Total number of routes: 1
Paths: 1 available, 1 best
BGP routing table information of <100:1>/96:
Imported route.
Original nexthop: 10.2.1.1
OutLabel : NULL
AS-path : (null)
Origin : igp
Attribute value : MED 0, pref-val 32768, 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
# Display detailed information about BGP IPv4 RT filter route 1.1.1.1:1 for the default BGP instance.
<Sysname> display bgp routing-table ipv4 rtfilter 1.1.1.1:1
BGP local router ID: 192.168.100.1
Local AS number: 100
Origin AS: 100
Total number of routes: 1
Paths: 1 available, 1 best
BGP routing table information of <1.1.1.1:1>/96:
From : 10.2.1.1 (192.168.100.3)
Rely nexthop : 10.2.1.1
Original nexthop: 10.2.1.1
OutLabel : NULL
AS-path : (null)
Origin : igp
Attribute value : MED 0, pref-val 32768, 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
Table 97 Command output
|
Field |
Description |
|
Paths |
Number of routes: · available—Number of valid routes. · best—Number of optimal routes. |
|
Imported route |
The BGP RT filter route is locally generated. |
|
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. |
|
AS-path |
AS_PATH attribute of the route. |
|
Origin |
Origin of the route: · igp—Originated in the AS. · egp—Learned through EGP. · incomplete—Unknown origin. |
|
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. |
|
From |
IP address of 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 |
VPN peer ID in the range of 1 to 134217727. N/A indicates that the route does not support this field. |
|
DSCP |
DSCP value in the range of 0 to 63. N/A indicates that the route does not support this field. |
|
Backup route |
The route is a backup route. |
# Display statistics for BGP IPv4 RT filter routes advertised to peer 10.2.1.2 for the default BGP instance.
<Sysname> display bgp routing-table ipv4 rtfilter peer 10.2.1.2 advertised-routes statistics
Advertised routes total: 2
# Display statistics for BGP IPv4 RT filter routes received from peer 10.2.1.2 for the default BGP instance.
<Sysname> display bgp routing-table ipv4 rtfilter peer 10.2.1.2 received-routes statistics
Received routes total: 2
Table 98 Command output
|
Field |
Description |
|
Advertised routes total |
Total number of advertised routes. |
|
Received routes total |
Total number of received routes. |
# Display BGP IPv4 RT filter route statistics for the default BGP instance.
<Sysname> display bgp routing-table ipv4 rtfilter statistics
Total number of routes from all PEs: 6
Origin AS: 100
Total number of routes: 2
Origin AS: 200
Total number of routes: 4
# Display advertisement information for the BGP IPv4 RT filter route 1.1.1.1:1/96 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 rtfilter 1.1.1.1:1 advertise-info
BGP local router ID: 192.168.100.1
Local AS number: 100
Paths: 1 best
Origin AS: 100
Total number of routes: 1
Paths: 1 best
BGP route-target filter information of <1.1.1.1:1>/96:
Advertised to VPN peers (1 in total):
1.1.1.2
Origin AS: 200
Total number of routes: 1
Paths: 1 best
BGP route-target filter information of <1.1.1.1:1>/96:
Advertised to VPN peers (1 in total):
1.1.1.2
Table 99 Command output
|
Field |
Description |
|
Paths |
Number of optimal routes to the destination. |
|
BGP route-target filter information of <1.1.1.1:1>/96 |
Information about BGP IPv4 RT filter route 1.1.1.1:1/96. |
|
Advertised to VPN peers (1 in total) |
Peers to which the network has been advertised. |
display bgp routing-table ipv4 unicast
Use display bgp routing-table ipv4 unicast to display BGP IPv4 unicast routing information.
Syntax
display bgp [ instance instance-name ] routing-table ipv4 [ unicast ] [ vpn-instance vpn-instance-name ] [ ipv4-address [ { mask | mask-length } [ longest-match ] ] | ipv4-address [ mask | mask-length ] advertise-info | as-path-acl as-path-acl-number | community-list { { basic-community-list-number | comm-list-name } [ whole-match ] | adv-community-list-number } | peer ipv4-address { advertised-routes | received-routes } [ ipv4-address [ mask | mask-length ] | statistics ] | statistics ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command displays the BGP IPv4 unicast routing information for the public network.
ipv4-address: Specifies a destination network address.
mask: Specifies a network mask, in dotted decimal notation.
mask-length: Specifies a mask length in the range of 0 to 32.
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.
as-path-acl as-path-acl-number: Displays BGP IPv4 unicast routes that match the AS path list specified by its number in the range of 1 to 256.
community-list: Displays BGP IPv4 unicast routes that match a community list.
basic-community-list-number: Specifies a basic community list by its number in the range of 1 to 99.
comm-list-name: Specifies a community list by its name, a case-sensitive string of 1 to 63 characters.
whole-match: Displays routes exactly matching the specified community list. If you do not specify this keyword, the command displays routes whose COMMUNITY attributes include the specified community list.
adv-community-list-number: Specifies an advanced community list by its number in the range of 100 to 199.
peer ipv4-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.
Usage guidelines
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.
Examples
# Display brief information about all public BGP IPv4 unicast routes in the default BGP instance.
<Sysname> display bgp routing-table ipv4
Total number of routes: 4
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
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 200i
* > 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 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 as-path-acl 1
Total number of routes: 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
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 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 peer 10.2.1.2 advertised-routes
Total number of routes: 2
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
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 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 peer 10.2.1.2 received-routes
Total number of routes: 2
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
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. |
|
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. · ORIGIN—Identifies the origin of the route. |
# Display detailed information about public BGP IPv4 unicast routes destined to network 10.2.1.0/24 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 10.2.1.0 24
BGP local router ID: 192.168.100.1
Local AS number: 100
Paths: 2 available, 1 best
BGP routing table information of 10.2.1.0/24:
Imported route.
Original nexthop: 10.2.1.1
OutLabel : NULL
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
From : 10.2.1.2 (192.168.100.2)
Rely nexthop : not resolved
Original nexthop: 10.2.1.2
OutLabel : NULL
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
# Display detailed information about the public BGP IPv4 unicast route destined to address 1.1.1.1/32 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 1.1.1.1 32
BGP local router ID: 192.168.100.1
Local AS number: 100
Paths: 2 available, 1 best
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
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
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
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
Table 101 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. |
|
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. |
|
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. |
# Display statistics for public BGP IPv4 unicast routes advertised to peer 10.2.1.2 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 peer 10.2.1.2 advertised-routes statistics
Advertised routes total: 2
# Display statistics for public BGP IPv4 unicast routes received from peer 10.2.1.2 in the default BGP instance.
<Sysname> display bgp routing-table ipv4 peer 10.2.1.2 received-routes statistics
Received routes total: 2
Table 102 Command output
|
Field |
Description |
|
Advertised routes total |
Total number of advertised routes. |
|
Received routes total |
Total number of received routes. |
# Display public BGP IPv4 unicast route statistics for the default BGP instance.
<Sysname> display bgp routing-table ipv4 statistics
Total number of routes: 4
Table 103 Command output
|
Field |
Description |
|
Total number of routes |
Total number of routes. |
# Display advertisement information for the public BGP IPv4 unicast route destined to network 10.2.1.0/24 in the default BGP instance.
<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
Paths: 1 best
BGP routing table information of 10.2.1.0/24:
Advertised to peers (1 in total):
10.2.1.2
Table 104 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. |
Related commands
ip as-path
ip community-list
display bgp routing-table ipv6 multicast
Use display bgp routing-table ipv6 multicast to display BGP IPv6 multicast routing information.
Syntax
display bgp [ instance instance-name ] routing-table ipv6 multicast [ ipv6-address prefix-length [ advertise-info ] | as-path-acl as-path-acl-number | community-list { { basic-community-list-number | comm-list-name } [ whole-match ] | adv-community-list-number } | peer ipv6-address { advertised-routes | received-routes } [ ipv6-address prefix-length | statistics ] | statistics ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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 multicast 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 multicast routing information.
advertise-info: Displays advertisement information for BGP IPv6 multicast routes. If you do not specify this keyword, the command displays the BGP IPv6 multicast routing table.
as-path-acl as-path-acl-number: Displays BGP IPv6 multicast routes that match the AS path list specified by its number in the range of 1 to 256.
community-list: Displays BGP IPv6 multicast routes that match a community list.
basic-community-list-number: Specifies a basic community list by its number in the range of 1 to 99.
comm-list-name: Specifies a community list by its name, a case-sensitive string of 1 to 63 characters.
whole-match: Displays BGP IPv6 multicast routes exactly matching the specified community list. If you do not specify this keyword, the command displays BGP IPv6 multicast routes whose COMMUNITY attributes include the specified community list.
adv-community-list-number: Specifies an advanced community list by its number in the range of 100 to 199.
peer: Displays BGP IPv6 multicast routing information advertised to or received from the specified peer.
ipv6-address: Specifies the peer IPv6 address.
advertised-routes: Displays BGP IPv6 multicast routing information advertised to the specified peer.
received-routes: Displays BGP IPv6 multicast routing information received from the specified peer.
statistics: Displays routing statistics.
Examples
# Display brief information about all BGP IPv6 multicast routes in the default BGP instance.
<Sysname> display bgp routing-table ipv6 multicast
Total number of routes: 5
BGP local router ID is 192.168.1.139
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
* > Network : 1:: PrefixLen : 64
NextHop : :: LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: ?
* i Network : 1:: PrefixLen : 64
NextHop : 1::1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: ?
* > Network : 1::2 PrefixLen : 128
NextHop : ::1 LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: ?
* > Network : 2::2 PrefixLen : 128
NextHop : ::1 LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: ?
* >i Network : 5::5 PrefixLen : 128
NextHop : 1::1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: ?
# Display information about BGP IPv6 multicast routes that match AS path list 1 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 multicast as-path-acl 1
Total number of routes: 5
BGP local router ID is 192.168.1.139
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
* > Network : 1:: PrefixLen : 64
NextHop : :: LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: ?
* i Network : 1:: PrefixLen : 64
NextHop : 1::1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: ?
* > Network : 1::2 PrefixLen : 128
NextHop : ::1 LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: ?
* > Network : 2::2 PrefixLen : 128
NextHop : ::1 LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: ?
* >i Network : 5::5 PrefixLen : 128
NextHop : 1::1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: ?
# Display information about BGP IPv6 multicast routes that match BGP community list 100 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 multicast community-list 100
Total number of routes: 5
BGP local router ID is 192.168.1.139
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
* > Network : 1:: PrefixLen : 64
NextHop : :: LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: ?
* i Network : 1:: PrefixLen : 64
NextHop : 1::1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: ?
* > Network : 1::2 PrefixLen : 128
NextHop : ::1 LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: ?
* > Network : 2::2 PrefixLen : 128
NextHop : ::1 LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: ?
* >i Network : 5::5 PrefixLen : 128
NextHop : 1::1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: ?
# Display information about all BGP IPv6 multicast routes advertised to peer 1::1 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 multicast peer 1::1 advertised-routes
Total number of routes: 2
BGP local router ID is 192.168.1.139
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
* > Network : 1:: PrefixLen : 64
NextHop : :: LocPrf : 100
MED : 0 OutLabel : NULL
Path/Ogn: ?
* > Network : 2::2 PrefixLen : 128
NextHop : ::1 LocPrf : 100
MED : 0 OutLabel : NULL
Path/Ogn: ?
# Display information about all BGP IPv6 multicast routes received from peer 1::1 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 multicast peer 1::1 received-routes
Total number of routes: 2
BGP local router ID is 192.168.1.139
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
* i Network : 1:: PrefixLen : 64
NextHop : 1::1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: ?
* >i Network : 5::5 PrefixLen : 128
NextHop : 1::1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: ?
Table 105 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. |
|
PrefixLen |
Prefix length of the destination network address. |
|
NextHop |
Next hop IP address. |
|
LocPrf |
Local preference value. |
|
PrefVal |
Preferred value of the route. |
|
OutLabel |
Outgoing label of the route. |
|
MED |
MULTI_EXIT_DISC attribute. |
|
Path/Ogn |
AS_PATH and ORIGIN attributes of the route: · AS_PATH—Records the ASs the route has passed, which avoids routing loops. · ORIGIN—Identifies the origin of the route. |
# Display detailed information about the BGP IPv6 multicast routes destined to network 2::2/128 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 multicast 2::2 128
BGP local router ID: 192.168.1.139
Local AS number: 100
Paths: 1 available, 1 best
BGP routing table information of 2::2/128:
Imported route.
Original nexthop: ::1
OutLabel : NULL
AS-path : (null)
Origin : incomplete
Attribute value : MED 0, pref-val 32768
State : valid, local, best
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
Table 106 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. |
|
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. |
|
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. |
# Display advertisement information for the BGP IPv6 multicast routes destined to network 2::2/128 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 multicast 2::2 128 advertise-info
BGP local router ID: 192.168.1.139
Local AS number: 100
Paths: 1 best
BGP routing table information of 2::2/128:
Advertised to peers (1 in total):
1::1
Table 107 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 2::2/128 |
Advertisement information for network 2::2/128. |
|
Advertised to peers (1 in total) |
Peers to which the network has been advertised. |
# Display statistics for BGP IPv6 multicast routes advertised to peer 1::1 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 multicast peer 1::1 advertised-routes statistics
Advertised routes total: 2
# Display statistics for BGP IPv6 multicast routes received from peer 1::1 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 multicast peer 1::1 received-routes statistics
Received routes total: 2
Table 108 Command output
|
Field |
Description |
|
Advertised routes total |
Total number of advertised routes. |
|
Received routes total |
Total number of received routes. |
# Display BGP IPv6 multicast route statistics for the default BGP instance.
<Sysname> display bgp routing-table ipv6 multicast statistics
Total number of routes: 5
Table 109 Command output
|
Field |
Description |
|
Total number of routes |
Total number of routes. |
Related commands
ip as-path
ip community-list
display bgp routing-table ipv6 unicast
Use display bgp routing-table ipv6 unicast to display BGP IPv6 unicast routing information.
Syntax
display bgp [ instance instance-name ] routing-table ipv6 [ unicast ] [ vpn-instance vpn-instance-name ] [ ipv6-address prefix-length [ advertise-info ] | as-path-acl as-path-acl-number | community-list { { basic-community-list-number | comm-list-name } [ whole-match ] | adv-community-list-number } | peer ipv6-address { advertised-routes | received-routes } [ ipv6-address prefix-length | statistics ] | statistics ]
display bgp [ instance instance-name ] routing-table ipv6 [ unicast ] peer ipv4-address { advertised-routes | received-routes } [ ipv6-address prefix-length | statistics ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command displays the BGP IPv6 unicast routing information for the public network.
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.
as-path-acl as-path-acl-number: Displays BGP IPv6 unicast routes that match the AS path list specified by its number in the range of 1 to 256.
community-list: Displays BGP IPv6 unicast routes that match a community list.
basic-community-list-number: Specifies a basic community list by its number in the range of 1 to 99.
comm-list-name: Specifies a community list by its name, a case-sensitive string of 1 to 63 characters.
whole-match: Displays routes exactly matching the specified community list. If you do not specify this keyword, the command displays routes whose COMMUNITY attributes include the specified community list.
adv-community-list-number: Specifies an advanced community list by its number in the range of 100 to 199.
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.
Usage guidelines
This command displays BGP IPv6 unicast routing information regardless of whether the unicast keyword is specified.
Examples
# Display brief information about all public BGP IPv6 unicast routes in the default BGP instance.
<Sysname> display bgp routing-table ipv6
Total number of routes: 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
Origin: i - IGP, e - EGP, ? - incomplete
* >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 AS path list 1 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 as-path-acl 1
Total number of routes: 2
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
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 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 community-list 100
Total number of routes: 2
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
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 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 peer 1::1 advertised-routes
Total number of routes: 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
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 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 peer 1::1 received-routes
Total number of routes: 1
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
* >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. |
|
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 |
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. · ORIGIN attribute—Identifies the origin of the route. |
# Display detailed information about BGP IPv6 unicast routes destined to network 2::/64 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 2:: 64
BGP local router ID: 192.168.1.135
Local AS number: 200
Paths: 2 available, 1 best
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
AS-path : 100
Origin : igp
Attribute value : MED 0, pref-val 0
State : valid, external, best
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
From : 1::1 (192.168.1.136)
Relay nexthop : 1::1
Original nexthop: 1::1
OutLabel : NULL
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
Table 111 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. |
|
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. · best. |
|
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. |
# Display advertisement information for the public BGP IPv6 unicast routes destined to network 2::/64 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 2:: 64 advertise-info
BGP local router ID: 192.168.1.136
Local AS number: 100
Paths: 1 best
BGP routing table information of 2::/64:
Advertised to peers (2 in total):
10.1.1.2
1::2
Table 112 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 the BGP IPv6 unicast routes advertised to peer 1::1 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 peer 1::1 advertised-routes statistics
Advertised routes total: 1
# Display statistics for the BGP IPv6 unicast routes received from peer 1::1 in the default BGP instance.
<Sysname> display bgp routing-table ipv6 peer 1::1 received-routes statistics
Received routes total: 1
Table 113 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 for the default BGP instance.
<Sysname> display bgp routing-table ipv6 statistics
Total number of routes: 4
Table 114 Command output
|
Field |
Description |
|
Total number of routes |
Total number of routes. |
Related commands
ip as-path
ip community-list
display bgp routing-table ipv6 unicast inlabel
Use display bgp routing-table ipv6 unicast inlabel to display incoming labels for BGP IPv6 unicast routes.
Syntax
display bgp [ instance instance-name ] routing-table ipv6 [ unicast ] inlabel
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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 incoming labels of BGP IPv6 unicast routes in the default BGP instance.
Usage guidelines
This command displays incoming labels for BGP IPv6 unicast routes regardless of whether the unicast keyword is specified.
Examples
# Display incoming labels for all BGP IPv6 unicast routes for the default BGP instance.
<Sysname> display bgp routing-table ipv6 inlabel
Total number of routes: 2
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
Origin: i - IGP, e - EGP, ? - incomplete
* > Network : 1::1 PrefixLen : 128
NextHop : 10::1 OutLabel : NULL
InLabel : 1279
* > Network : 10:: PrefixLen : 64
NextHop : :: OutLabel : NULL
InLabel : 1278
Table 115 Command output
|
Field |
Description |
|
Status codes |
Status codes. For more information, see Table 110. |
|
Origin |
Origin of the route. For more information, see Table 110. |
|
Network |
Destination network address. |
|
PrefixLen |
Prefix length of the destination network address. |
|
NextHop |
Next hop IPv6 address. |
|
OutLabel |
Outgoing label of the IPv6 unicast route, which is assigned by the peer 6PE device. |
|
InLabel |
Incoming label of the IPv6 unicast route, which is assigned by the local 6PE device. |
display bgp routing-table ipv6 unicast outlabel
Use display bgp routing-table ipv6 unicast outlabel to display outgoing labels for BGP IPv6 unicast routes.
Syntax
display bgp [ instance instance-name ] routing-table ipv6 [ unicast ] outlabel
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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 display outgoing labels of BGP IPv6 unicast routes in the default BGP instance.
Usage guidelines
This command displays outgoing labels for BGP IPv6 unicast routes regardless of whether the unicast keyword is specified.
Examples
# Display outgoing labels for all public BGP IPv6 unicast routes for the default BGP instance.
<Sysname> display bgp routing-table ipv6 outlabel
Total number of routes: 2
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
Origin: i - IGP, e - EGP, ? - incomplete
* >i Network : 4::4 PrefixLen : 128
NextHop : ::FFFF:3.3.3.3 OutLabel : 1279
* >i Network : 20:: PrefixLen : 64
NextHop : ::FFFF:3.3.3.3 OutLabel : 1278
Table 116 Command output
|
Field |
Description |
|
Status codes |
Status codes. For more information, see Table 110. |
|
Origin |
Origin of the route. For more information, see Table 110. |
|
Network |
Destination network address. |
|
PrefixLen |
Prefix length of the destination network address. |
|
NextHop |
Next hop IPv6 address. |
|
OutLabel |
Outgoing label of the IPv6 unicast route, which is assigned by the peer 6PE device. |
display bgp update-group
Use display bgp update-group to display information about BGP update groups.
Syntax
display bgp [ instance instance-name ] update-group ipv4 { mdt | multicast | rtfilter | [ unicast ] [ vpn-instance vpn-instance-name ] } [ ipv4-address ]
display bgp [ instance instance-name ] update-group ipv6 { multicast | [ unicast ] [ vpn-instance vpn-instance-name ] } [ ipv6-address ]
display bgp [ instance instance-name ] update-group ipv6 [ unicast ] [ ipv4-address ]
display bgp [ instance instance-name ] update-group link-state [ ipv4-address | ipv6-address ]
display bgp [ instance instance-name ] update-group vpnv4 [ vpn-instance vpn-instance-name ] [ ipv4-address ]
display bgp [ instance instance-name ] update-group { l2vpn | vpnv6 } [ ipv4-address ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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.
link-state: Displays BGP update group information for LS address family.
vpnv4: Displays BGP update group information for VPNv4 address family.
l2vpn: Displays BGP update group information for L2VPN address family.
vpnv6: Displays BGP update group information for VPNv6 address family.
mdt: Displays BGP update group information for MDT address family.
multicast: Displays BGP update group information for multicast address family.
rtfilter: Displays BGP update group information for IPv4 RT filter address family.
unicast: Displays BGP update group information for unicast address family.
vpn-instance vpn-instance-name: Displays BGP update group information for the MPLS L3VPN instance specified by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command displays update group information for the public network.
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.
Usage guidelines
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 none of the multicast, mdt, rtfilter, and unicast keywords is specified.
Examples
# Display information about all public BGP update groups for IPv4 unicast address family of the default BGP instance.
<Sysname> display bgp update-group ipv4
Update-group ID: 0
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
# Display update group information for the public BGP IPv4 unicast peer 1.1.1.2 in the default BGP instance.
<Sysname> display bgp update-group ipv4 1.1.1.2
Update-group ID: 0
Type: EBGP link
4-byte AS number: Supported
Site-of-Origin: Not specified
Minimum time between advertisements: 30 seconds
OutQ: 0
Members: 2
1.1.1.2
1.1.1.3
# Display information about all public BGP update groups for IPv6 multicast address family of the default BGP instance.
<Sysname> display bgp update-group ipv6 multicast
Update-group ID: 0
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
# Display update group information for the public BGP IPv6 multicast peer 1::2 in the default BGP instance.
<Sysname> display bgp update-group ipv6 multicast 1::2
Update-group ID: 0
Type: EBGP link
4-byte AS number: Supported
Site-of-Origin: Not specified
Minimum time between advertisements: 30 seconds
OutQ: 0
Members: 2
1::2
1::3
# Display update group information for the BGP VPNv4 peer 1.1.1.2 in VPN instance vpn1 of the default BGP instance.
<Sysname> display bgp update-group vpnv4 vpn-instance vpn1 1.1.1.2
Update-group ID: 0
Type: EBGP link
4-byte AS number: Supported
Site-of-Origin: Not specified
Nesting VPN: vpn1
Minimum time between advertisements: 30 seconds
OutQ: 0
Members: 2
1.1.1.2
1.1.1.3
# Display all update group information for the BGP L2VPN address family of the default BGP instance.
<Sysname> display bgp update-group l2vpn
Update-group ID: 0
Type: IBGP link
4-byte AS number: Supported
Site-of-Origin: Not specified
L2VPN signaling (VPLS): Supported
L2VPN signaling (VPWS): RFC mode
L2VPN auto-discovery: RFC mode
Minimum time between advertisements: 15 seconds
OutQ: 0
Members: 2
2.2.2.9
3.3.3.9
# Display update group information for the BGP L2VPN peer 1.1.1.3 in the default BGP instance.
<Sysname> display bgp update-group l2vpn 1.1.1.3
Update-group ID: 0
Type: IBGP link
4-byte AS number: Supported
Site-of-Origin: Not specified
L2VPN signaling (VPLS): Supported
L2VPN signaling (VPWS): Draft mode
Minimum time between advertisements: 15 seconds
OutQ: 0
Members: 1
1.1.1.3
# Display update group information for the BGP L2VPN peer 1.1.1.4 in the default BGP instance.
<Sysname> display bgp update-group l2vpn 1.1.1.4
Update-group ID: 0
Type: EBGP link
4-byte AS number: Supported
Site-of-Origin: Not specified
L2VPN signaling (VPLS): Supported
L2VPN signaling (VPWS): RFC mode
L2VPN auto-discovery: Non-standard mode
Minimum time between advertisements: 30 seconds
OutQ: 0
Members: 1
1.1.1.4
Table 117 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. |
|
Label capability: Supported |
The peers in the update group support labeled routes. |
|
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. |
|
Fake AS |
A fake local AS number is configured for the peers in the update group. |
|
Public-AS-Only: Yes |
BGP route updates advertised to the peers in the update group only carry the public AS number without the private AS number. · Yes—If a peer uses a private AS number, the AS number is used as an update group classification criterion. If a peer uses a public AS number, the AS number is not used as an update group classification criterion. · No—The AS number is not used as an update group classification criterion. |
|
Substitute-AS: Yes |
AS number substitution is enabled. |
|
Minimum time between advertisements: number seconds |
Minimum time between advertisements. |
|
Advertising community: Yes |
Community advertisement to peers in the update group is enabled. |
|
Route-reflect client: Yes |
The peer is a client of the route reflector. |
|
Advertising extended community: Yes |
Extended community advertisement to peers in the update group is enabled. |
|
Export AS-path-ACL |
AS path ACL used to filter BGP routes advertised to peers in the update group. |
|
Export prefix list |
Prefix list used to filter BGP routes advertised to peers in the update group. |
|
Export route policy |
Routing policy used to filter BGP routes advertised to peers in the update group. |
|
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. |
|
L2VPN signaling (VPLS): Supported |
Peers in the update group support using NLRI defined in RFC 4761 to advertise VPLS label blocks. |
|
L2VPN signaling (VPWS): RFC mode |
Peers in the update group support using NLRI defined in RFC 4761 to advertise MPLS L2VPN label blocks. |
|
L2VPN signaling (VPWS): Draft mode |
Peers in the update group support using NLRI defined in the draft draft-kompella-ppvpn-l2vpn-03 to advertise MPLS L2VPN label blocks. |
|
L2VPN auto-discovery: RFC mode |
Peers in the update group support using NLRI defined in RFC 6074 to exchange VPLS PE information. |
|
L2VPN auto-discovery: Non-standard mode |
Peers in the update group support using non-standard NLRI to exchange VPLS PE information. |
display bgp-policy statistics
Use display bgp-policy statistics to display BGP policy accounting information.
Syntax
display bgp-policy { ip | ipv6 } statistics { input | output } [ interface interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ip: Displays BGP policy accounting information for IPv4 traffic.
ipv6: Displays BGP policy accounting information for IPv6 traffic.
input: Displays BGP policy accounting information for incoming traffic.
output: Displays BGP policy accounting information for outgoing traffic.
interface interface-type interface-number: Displays BGP policy accounting information on an interface specified by the interface type and number. If you do not specify an interface, this command displays global BGP policy accounting information.
Examples
# Display global BGP policy accounting information for incoming IPv4 traffic.
<Sysname> display bgp-policy ip statistics input
Statistics for the inbound direction:
Traffic index Packets Bytes
1 0 0
2 0 0
3 0 0
4 0 0
5 0 0
6 0 0
7 0 0
8 0 0
9 0 0
10 0 0
# Display global BGP policy accounting information for incoming IPv6 traffic.
<Sysname> display bgp-policy ipv6 statistics input
Statistics for the inbound direction:
Traffic index Packets Bytes
1 0 0
2 0 0
3 0 0
4 0 0
5 0 0
6 0 0
7 0 0
8 0 0
9 0 0
10 0 0
# Display BGP policy accounting information for outgoing IPv4 traffic on GigabitEthernet 1/0/1.
<Sysname> display bgp-policy ip statistics output interface gigabitethernet 1/0/1
Statistics for GigabitEthernet1/0/1 in the outbound direction:
Traffic index Packets Bytes
1 0 0
2 0 0
3 0 0
4 0 0
5 0 0
6 0 0
7 0 0
8 0 0
9 0 0
10 0 0
# Display BGP policy accounting information for outgoing IPv6 traffic on GigabitEthernet 1/0/1.
<Sysname> display bgp-policy ipv6 statistics output interface gigabitethernet 1/0/1
Statistics for GigabitEthernet1/0/1 in the outbound direction:
Traffic index Packets Bytes
1 0 0
2 0 0
3 0 0
4 0 0
5 0 0
6 0 0
7 0 0
8 0 0
9 0 0
10 0 0
Table 118 Command output
|
Field |
Description |
|
Packets |
Number of packets for traffic with an index. |
|
Bytes |
Number of bytes for traffic with an index. |
Related commands
domain-distinguisher
Use domain-distinguisher to specify an AS number and a router ID for BGP LS messages.
Use undo domain-distinguisher to restore the default.
Syntax
domain-distinguisher as-number:router-id
undo domain-distinguisher
Default
The AS number and router ID of the current BGP process are used.
Views
BGP LS address family view
Predefined user roles
network-admin
Parameters
as-number:router-id: Specifies the AS number and router ID. The value range for the as-number argument is 1 to 4294967295, and the router ID is in IP address format.
Examples
# Set the AS number and router ID for BGP LS messages to 65009 and 1.1.1.1, respectively.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family link-state
[Sysname-bgp-default-ls] domain-distinguisher 65009:1.1.1.1
ebgp-interface-sensitive
Use ebgp-interface-sensitive to enable immediate re-establishment of direct EBGP sessions.
Use undo ebgp-interface-sensitive to disable immediate re-establishment of direct EBGP sessions.
Syntax
ebgp-interface-sensitive
undo ebgp-interface-sensitive
Default
Immediate re-establishment of direct EBGP sessions is enabled.
Views
BGP instance view
Predefined user roles
network-admin
Usage guidelines
When a direct link to an EBGP peer fails, BGP tears down the session and re-establishes a session to the peer immediately. If the feature is not enabled, the router does not tear down the session until the hold time expires. However, disabling this feature can prevent routing flaps from affecting EBGP session state.
This command applies only to direct EBGP sessions.
Examples
# Enable immediate re-establishment of direct EBGP sessions for BGP instance default.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] ebgp-interface-sensitive
fast-reroute route-policy
Use fast-reroute route-policy to apply a routing policy to fast reroute (FRR) for a BGP address family.
Use undo fast-reroute route-policy to restore the default.
Syntax
fast-reroute route-policy route-policy-name
undo fast-reroute route-policy
Default
No routing policy is applied to FRR.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
You can use the following methods to configure BGP FRR:
· Method 1—Execute the pic command in BGP address family view. BGP calculates a backup next hop for a BGP route in the address family if there are two or more unequal-cost routes to reach the destination.
· Method 2—Execute the fast-reroute route-policy command to use a routing policy in which a backup next hop is specified by using the command apply [ ipv6 ] fast-reroute backup-nexthop. For BGP to generate a backup next hop for the primary route, the backup next hop calculated by BGP must be the same as the specified backup next hop. You can also configure if-match clauses in the routing policy to identify the routes protected by FRR.
If both methods are configured, Method 2 takes precedence over Method 1.
Examples
# Apply the routing policy frr-policy to FRR in BGP IPv4 unicast address family view of BGP instance default.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4
[Sysname-bgp-default-ipv4] fast-reroute route-policy frr-policy
# Apply the routing policy frr-policy to FRR in BGP IPv4 unicast address family view of BGP instance abc.
<Sysname> system-view
[Sysname] bgp 100 instance abc
[Sysname-bgp-abc] address-family ipv4
[Sysname-bgp-abc-ipv4] fast-reroute route-policy frr-policy
Related commands
apply fast-reroute
apply ipv6 fast-reroute
pic
route-policy
filter-policy export
Use filter-policy export to filter advertised BGP routes.
Use undo filter-policy export to remove the route filter.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP IPv4 multicast address family view:
filter-policy { ipv4-acl-number | prefix-list prefix-list-name } export [ direct | eigrp eigrp-as | [ isis | ospf | rip ] process-id | static ]
undo filter-policy export [ direct | eigrp eigrp-as | [ isis | ospf | rip ] process-id | static ]
In BGP IPv6 unicast address family view/BGP-VPN IPv6 unicast address family view/BGP VPNv6 address family view/BGP IPv6 multicast address family view:
filter-policy { ipv6-acl-number | prefix-list ipv6-prefix-name } export [ direct | [ isisv6 | ospfv3 | ripng ] process-id | static ]
undo filter-policy export [ direct | [ isisv6 | ospfv3 | ripng ] process-id | static ]
Default
Advertised BGP routes are not filtered.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP VPNv4 address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP VPNv6 address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
Predefined user roles
network-admin
Parameters
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 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-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters, to match routes by destination.
direct: Specifies direct routes.
eigrp: Specifies EIGRP routes.
isis: Specifies IS-IS routes.
isisv6: Specifies IPv6 IS-IS routes.
ospf: Specifies OSPF routes.
ospfv3: Specifies OSPFv3 routes.
rip: Specifies RIP routes.
ripng: Specifies RIPng routes.
static: Specifies static routes.
eigrp-as: Specifies an EIGRP process by its ID in the range of 1 to 65535.
process-id: Specifies a routing protocol by its ID in the range of 1 to 65535.
Usage guidelines
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/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny/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. The subnet mask must be contiguous. Otherwise, the configuration does not take effect.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, use IPv4 basic ACL 2000 to filter advertised BGP IPv4 routes.
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] filter-policy 2000 export
filter-policy import
peer as-path-acl
peer filter-policy
peer prefix-list
peer route-policy
filter-policy import
Use filter-policy import to filter received BGP routes.
Use undo filter-policy import to restore the default.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP IPv4 multicast address family view:
filter-policy { ipv4-acl-number | prefix-list prefix-list-name } import
undo filter-policy import
In BGP IPv6 unicast address family view/BGP-VPN IPv6 unicast address family view/BGP VPNv6 address family view/BGP IPv6 multicast address family view:
filter-policy { ipv6-acl-number | prefix-list ipv6-prefix-name } import
undo filter-policy import
Default
Received BGP routes are not filtered.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP VPNv4 address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP VPNv6 address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
Predefined user roles
network-admin
Parameters
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 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-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters, to match routes by destination.
Usage guidelines
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/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny/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. The subnet mask must be contiguous. Otherwise, the configuration does not take effect.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, 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
Related commands
filter-policy export
peer as-path-acl
peer filter-policy
peer prefix-list
peer route-policy
flush suboptimal-route
Use flush suboptimal-route to enable BGP to flush the suboptimal BGP route to the RIB.
Use undo flush suboptimal-route to disable BGP from flushing the suboptimal BGP route to the RIB.
Syntax
flush suboptimal-route
undo flush suboptimal-route
Default
BGP is disabled from flushing the suboptimal BGP route to the RIB. Only the optimal route is flushed to the RIB.
Views
BGP instance view
Predefined user roles
network-admin
Usage guidelines
This command flushes the suboptimal BGP route to the RIB when the following conditions are met:
· The optimal route is generated by the network command or is redistributed by the import-route command.
· The suboptimal route is received from a BGP peer.
After the suboptimal route is flushed to the RIB on a network, BGP immediately switches traffic to the suboptimal route when the optimal route fails.
For example, the device has a static route to the subnet 1.1.1.0/24 that has a higher priority than a BGP route. BGP redistributes the static route and receives a route to 1.1.1.0/24 from a peer. After the flush suboptimal-route command is executed, BGP flushes the received BGP route to the RIB as the suboptimal route. When the static route fails, BGP immediately switches traffic to the suboptimal route if inter-protocol FRR is enabled. For more information about inter-protocol FRR, see Layer 3—IP Routing Configuration Guide.
Examples
# Enable BGP to flush the suboptimal BGP route to the RIB for BGP instance default.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] flush suboptimal-route
graceful-restart
Use graceful-restart to enable BGP Graceful Restart (GR) capability.
Use undo graceful-restart to disable BGP GR capability.
Syntax
graceful-restart
undo graceful-restart
Default
BGP GR capability is disabled.
Views
BGP instance view
Predefined user roles
network-admin
Usage guidelines
GR ensures continuous forwarding when BGP restarts or an active/standby switchover occurs.
BGP peers exchange Open messages containing GR information. If both parties have GR capability, they establish a GR-capable session.
After you execute this command, the device re-establishes BGP sessions.
Examples
# Enable GR capability for BGP process 100 of BGP instance default.
[Sysname] bgp 100
[Sysname-bgp-default] graceful-restart
Related commands
graceful-restart timer purge-time
graceful-restart timer restart
graceful-restart timer wait-for-rib
graceful-restart timer purge-time
Use graceful-restart timer purge-time to set the Routing Information Base (RIB) purge timer.
Use undo graceful-restart timer purge-time to restore the default.
Syntax
graceful-restart timer purge-time timer
undo graceful-restart timer purge-time
Default
The RIB purge timer is 480 seconds.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
timer: Sets the RIB purge timer in the range of 1 to 6000 seconds.
Usage guidelines
BGP starts the RIB purge timer when an active/standby switchover occurs or BGP restarts. If BGP route exchange is not completed within the RIB purge timer, the GR restarter quits the GR process. It updates the RIB with the BGP routes already learned, and removes the stale routes from RIB.
Enable BGP GR before you execute this command.
Set the RIB purge timer to be long enough to complete GR, especially when large numbers of BGP routes exist.
As a best practice, set the RIB purge timer greater than the timer set by the graceful-restart timer wait-for-rib command and less than the timer set by the protocol lifetime command.
Examples
# Set the RIB purge timer to 300 seconds for BGP instance default.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] graceful-restart
[Sysname-bgp-default] graceful-restart timer purge-time 300
Related commands
graceful-restart
graceful-restart timer restart
graceful-restart timer wait-for-rib
protocol lifetime (Layer 3—IP Routing Command Reference)
graceful-restart timer restart
Use graceful-restart timer restart to configure the GR timer.
Use undo graceful-restart timer restart to restore the default.
Syntax
graceful-restart timer restart timer
undo graceful-restart timer restart
Default
The GR timer is 150 seconds.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
timer: Specifies the GR timer in the range of 3 to 600 seconds.
Usage guidelines
The GR restarter sends the GR timer to the GR helper in an Open message. When the GR helper detects that an active/standby switchover or a BGP restart occurred on the GR restarter, the GR helper performs the following actions:
1. Marks all routes learned from the GR restarter as stale.
2. Starts the GR timer.
3. If no BGP session is established before the GR timer expires, the GR helper removes the stale routes.
Before you configure this command, enable the BGP GR capability.
To apply a new GR timer, you must re-establish BGP sessions.
Examples
# Set the GR timer to 300 seconds for BGP instance default.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] graceful-restart
[Sysname-bgp-default] graceful-restart timer restart 300
Related commands
graceful-restart timer purge-time
graceful-restart timer wait-for-rib
graceful-restart timer wait-for-rib
Use graceful-restart timer wait-for-rib to configure the time to wait for the End-of-RIB marker.
Use undo graceful-restart timer wait-for-rib to restore the default.
Syntax
graceful-restart timer wait-for-rib timer
undo graceful-restart timer wait-for-rib
Default
The time to wait for the End-of-RIB marker is 180 seconds.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
timer: Specifies the time to wait for the End-of-RIB marker, in the range of 3 to 3600 seconds.
Usage guidelines
BGP uses this timer to control the time to receive updates from the peer. The timer is not advertised to the peer.
After the GR restarter and GR helper re-establish a BGP session, they start this timer. If they do not complete route exchange within the timer, the GR restarter does not receive new routes. It updates its routing table and forwarding table with learned BGP routes, and the GR helper removes the stale routes.
This command controls the routing convergence speed. A smaller timer value means faster routing convergence but possibly results in incomplete routing information.
Before configuring this command, you must enable the BGP GR capability.
Examples
# Set the time to wait for the End-of-RIB marker on the local end to 100 seconds for BGP instance default.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] graceful-restart
[Sysname-bgp-default] graceful-restart timer wait-for-rib 100
Related commands
graceful-restart
graceful-restart timer purge-time
graceful-restart timer restart
group
Use group to create a peer group.
Use undo group to delete a peer group.
Syntax
group group-name [ external | internal ]
undo group group-name
Default
No peer groups exist.
Views
BGP instance view
BGP-VPN instance view
Predefined user roles
network-admin
Parameters
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.
Usage guidelines
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.
Examples
# In BGP instance view of BGP instance default, create an 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
ignore-first-as
Use ignore-first-as to configure BGP to ignore the first AS number of EBGP route updates.
Use undo ignore-first-as to restore the default.
Syntax
ignore-first-as
undo ignore-first-as
Default
BGP checks the first AS number of a received EBGP route update. If the first AS number is neither that of the BGP peer nor a private AS number, the BGP router disconnects the BGP session to the peer.
Views
BGP instance view
Predefined user roles
network-admin
Examples
# Configure BGP to ignore the first AS number of EBGP route updates for BGP instance default.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] ignore-first-as
import-route
Use import-route to enable BGP to redistribute routes.
Use undo import-route to disable route redistribution.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP IPv4 multicast address family view:
import-route { isis | ospf | rip } [ { process-id | all-processes } [ allow-direct | med med-value | route-policy route-policy-name ] * ]
import-route { direct | static } [ med med-value | route-policy route-policy-name ]
import-route eigrp [ eigrp-as | all-as ] [ allow-direct | med med-value | route-policy route-policy-name ] * ]
undo import-route { direct | eigrp [ eigrp-as | all-as ] | { isis | ospf | rip } [ process-id | all-processes ] | static }
In BGP IPv6 unicast address family view/BGP-VPN IPv6 unicast address family view/BGP IPv6 multicast address family view:
import-route { isisv6 | ospfv3 | ripng } [ { process-id | all-processes } [ allow-direct | med med-value | route-policy route-policy-name ] * ]
import-route { direct | static } [ med med-value | route-policy route-policy-name ]
undo import-route { direct | { isisv6 | ospfv3 | ripng } [ process-id | all-processes ] | static }
Default
BGP does not redistribute IGP routes.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
Predefined user roles
network-admin
Parameters
direct: Redistributes direct routes.
eigrp: Redistributes EIGRP 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.
eigrp-as: Specifies an EIGRP process by its ID in the range of 1 to 65535.
all-as: Redistributes routes from all the processes of EIGRP.
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. If you specify both the allow-direct keyword and the route-policy route-policy-name option, make sure the if-match rule defined in the routing policy does not conflict with the allow-direct keyword. For example, if you specify the allow-direct keyword, do not configure the if-match route-type rule for the routing policy. Otherwise, the allow-direct keyword does not take effect.
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.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter redistributed routes or set route attributes for redistributed routes.
Usage guidelines
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 EIGRP routes, the command redistributes EIGRP routes from process 1. If you do not specify any parameters when redistributing IS-IS, IPv6 IS-IS, OSPF, OSPFv3, RIP, or RIPng routes, the command redistributes the routes from process 1.
The undo import-route eigrp all-as command removes the configuration made by the import-route eigrp all-as command. It does not remove the configuration made by the import-route eigrp eigrp-as command.
The ORIGIN attribute of routes redistributed by the import-route command is INCOMPLETE.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, 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
display ip routing-table protocol
display ipv6 routing-table protocol
ip vpn-instance (BGP instance view)
Use ip vpn-instance to create a BGP-VPN instance and enter its view, or enter the view of an existing BGP-VPN instance.
Use undo ip vpn-instance to remove a BGP-VPN instance and all its configurations.
Syntax
ip vpn-instance vpn-instance-name
undo ip vpn-instance vpn-instance-name
Default
No BGP-VPN instances exist.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
vpn-instance-name: Specifies a VPN instance by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
After you create a BGP peer in BGP-VPN instance view, the BGP routes learned from the peer are added into the routing table of the specified VPN instance.
This command and all commands in BGP-VPN instance view are typically executed on provider edge (PE) or Multi-VPN-Instance CE (MCE) devices. The commands add routes learned from different sites into different VPN instances.
Before you execute this command, you must perform the following tasks:
· Use the ip vpn-instance command to create the VPN instance in system view.
· Use the route-distinguisher command to configure a route distinguisher (RD) for the VPN instance.
Examples
# Create a BGP-VPN instance for BGP instance default and enter its view.
<Sysname> system-view
[Sysname] ip vpn-instance vpn1
[Sysname-vpn-instance-vpn1] route-distinguisher 100:1
[Sysname-vpn-instance-vpn1] quit
[Sysname] bgp 100
[Sysname-bgp-default] ip vpn-instance vpn1
[Sysname-bgp-default-vpn1]
Related commands
ip vpn-instance (system view) (MPLS Command Reference)
route-distinguisher (MPLS Command Reference)
label-allocation-mode
Use label-allocation-mode to specify a label allocation mode.
Use undo label-allocation-mode to restore the default.
Syntax
label-allocation-mode { per-prefix | per-vrf }
undo label-allocation-mode
Default
BGP allocates labels on a per-next-hop basis.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
per-prefix: Allocates a label to each route prefix.
per-vrf: Allocates a label to each VPN instance.
Usage guidelines
BGP supports the following label allocation modes:
· Per-prefix—Allocates a label to each route prefix.
· Per-next-hop—Allocates a label to each next hop. This mode is applicable when the number of labels required by the per-prefix mode exceeds the maximum number of labels supported by the device.
· Per-VPN-instance—Allocates a label to each VPN instance. This mode is applicable when the number of labels required by the per-next-hop mode exceeds the maximum number of labels supported by the device.
When you specify the per-prefix or per-next-hop label allocation mode, you can execute the vpn popgo command to specify the POPGO forwarding mode on an egress PE. The egress PE will pop the label for each packet and forward the packet out of the interface corresponding to the label.
When you specify the per-VPN instance label allocation mode, do not execute the vpn popgo command because it is mutually exclusive with the label-allocation-mode per-vrf command. The egress PE will pop the label for each packet and forward the packet through the FIB table.
A change to the label allocation mode enables BGP to re-advertise all routes, which will cause service interruption. Use this command with caution.
Examples
# Specify the per-prefix label allocation mode.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] label-allocation-mode per-prefix
Related commands
vpn popgo (MPLS Command Reference)
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.
Syntax
log-peer-change
undo log-peer-change
Default
Logging for BGP session state changes is enabled globally.
Views
BGP instance view
Predefined user roles
network-admin
Usage guidelines
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 Network Management and Monitoring Configuration Guide.
If you disable the logging of BGP session state changes globally or disable the logging for a peer or peer group, BGP does not generate logs for session establishments and disconnections.
Examples
# Enable the logging of session state changes globally for BGP instance default.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] log-peer-change
Related commands
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.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP IPv4 multicast address family view:
network ipv4-address [ mask | mask-length ] [ route-policy route-policy-name ]
undo network ipv4-address [ mask | mask-length ]
In BGP IPv6 unicast address family view/BGP-VPN IPv6 unicast address family view/BGP IPv6 multicast address family view:
network ipv6-address prefix-length [ route-policy route-policy-name ]
undo network ipv6-address prefix-length
Default
BGP does not advertise local networks.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
Predefined user roles
network-admin
Parameters
ipv4-address: Specifies an IPv4 network address. If you do not specify the mask or mask-length, natural mask is used.
mask: Specifies a mask in dotted decimal notation.
mask-length: Specifies a mask length in the range of 0 to 32.
ipv6-address: Specifies an IPv6 network address.
prefix-length: Specifies a prefix length in the range of 0 to 128.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter routes or set the route attributes.
Usage guidelines
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.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, 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
network short-cut
Use network short-cut to increase the preference for a received EBGP route. This EBGP route is called a shortcut route.
Use undo network short-cut to remove the configuration.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP IPv4 multicast address family view:
network ipv4-address [ mask | mask-length ] short-cut
undo network ipv4-address [ mask | mask-length ] short-cut
In BGP IPv6 unicast address family view/BGP-VPN IPv6 unicast address family view/BGP IPv6 multicast address family view:
network ipv6-address prefix-length short-cut
undo network ipv6-address prefix-length short-cut
Default
A received EBGP route has a preference of 255.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
Predefined user roles
network-admin
Parameters
ipv4-address: Specifies an IPv4 network address. If you do not specify the mask or mask-length, natural mask is used.
mask: Specifies a mask of the network address in dotted decimal notation.
mask-length: Specifies a mask length in the range of 0 to 32.
ipv6-address: Specifies an IPv6 network address.
prefix-length: Specifies a prefix length in the range of 0 to 128.
Usage guidelines
Different routing protocols might find different routes to the same destination. However, not all of those routes are optimal. For route selection, routing protocols, direct routes, and static routes are assigned different preferences. The route with the highest preference is preferred.
By default, the preference of an EBGP route is lower than a local route. If a device has an EBGP route and a local route to reach the same destination, the device does not select the EBGP route. You can use the network shortcut command to configure the EBGP route to have the same preference as the local route so the EBGP route is more likely to become the optimal route.
You can use the preference command to modify the preferences for external and local BGP routes.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, increase the preference of EBGP route 10.0.0.0/16.
<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 short-cut
Related commands
preference
non-stop-routing
Use non-stop-routing to enable BGP nonstop routing (NSR).
Use undo non-stop-routing to disable BGP NSR.
Syntax
non-stop-routing
undo non-stop-routing
Default
BGP NSR is disabled.
Views
BGP instance view
Predefined user roles
network-admin
Usage guidelines
The following matrix shows the command and hardware compatibility:
|
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/MSR810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28/3600-51 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28-SI/3600-51-SI |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
· In standalone mode: No · In IRF mode: Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Command compatibility |
|
MSR810-LM-GL |
No |
|
MSR810-W-LM-GL |
No |
|
MSR830-6EI-GL |
No |
|
MSR830-10EI-GL |
No |
|
MSR830-6HI-GL |
No |
|
MSR830-10HI-GL |
No |
|
MSR2600-6-X1-GL |
No |
|
MSR3600-28-SI-GL |
No |
BGP NSR ensures continuous routing by synchronizing BGP state and data information from the active BGP process to the standby BGP process. The standby BGP process can seamlessly take over all services when the active process fails.
Examples
# Enable BGP NSR for BGP instance default.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] non-stop-routing
Related commands
display bgp non-stop-routing status
peer advertise-community
Use peer advertise-community to advertise the COMMUNITY attribute to a peer or peer group.
Use undo peer advertise-community to disable the COMMUNITY attribute advertisement to a peer or peer group.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP-VPN IPv6 unicast address family view/BGP VPNv6 address family view/BGP EVPN address family view/BGP IPv4 multicast address family view:
peer { group-name | ipv4-address [ mask-length ] } advertise-community
undo peer { group-name | ipv4-address [ mask-length ] } advertise-community
In BGP IPv6 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } advertise-community
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } advertise-community
In BGP IPv6 multicast address family view/BGP-VPN IPv6 unicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } advertise-community
undo peer { group-name | ipv6-address [ prefix-length ] } advertise-community
Default
No COMMUNITY attribute is advertised to any peers or peer groups.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP VPNv4 address family view
BGP-VPN IPv6 unicast address family view
BGP VPNv6 address family view
BGP IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
BGP EVPN address family 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 advertises the COMMUNITY attribute 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 the COMMUNITY attribute to all dynamic peers in the subnet.
Usage guidelines
The COMMUNITY attribute is a group of specific data carried in update messages. A route can carry one or more COMMUNITY attribute values (each is represented by a 4-byte integer). The receiving router processes the route (for example, determining whether to advertise the route and the scope for advertising the route) based on the COMMUNITY attribute values.
After you execute the peer advertise-community command, routing updates advertised to the peer carry the COMMUNITY attribute.
After you execute the undo peer advertise-community command, BGP, upon receiving a route with the COMMUNITY attribute, removes the COMMUNITY attribute before sending the route to the peer or peer group.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, advertise the COMMUNITY attribute to peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer test advertise-community
Related commands
apply community
if-match community
ip community-list
peer advertise-ext-community
Use peer advertise-ext-community to advertise the extended community attribute to a peer or peer group.
Use undo peer advertise-ext-community to disable the extended community attribute advertisement to a peer or peer group.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP IPv4 multicast address family view:
peer { group-name | ipv4-address [ mask-length ] } advertise-ext-community
undo peer { group-name | ipv4-address [ mask-length ] } advertise-ext-community
In BGP IPv6 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } advertise-ext-community
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } advertise-ext-community
In BGP IPv6 multicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } advertise-ext-community
undo peer { group-name | ipv6-address [ prefix-length ] } advertise-ext-community
Default
No extended community attribute is advertised to any peers or peer groups.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family 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 advertises the extended community attribute 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 the extended community attribute to all dynamic peers in the subnet.
Usage guidelines
To meet increasing user demands, BGP defines a new attribute—extended community attribute. The extended community attribute has the following advantages over the COMMUNITY attribute:
· The extended community attribute has an 8-byte length.
· The extended community attribute supports various types. You can select an extended community attribute type as needed to implement route filtering and control. This simplifies configuration and management.
After you execute the peer advertise-ext-community command, route updates sent to the peer or peer group carry the extended community attribute.
After you execute the undo peer advertise-ext-community command, BGP, upon receiving a route with the extended community attribute, removes the extended community attribute before sending the route to the peer or peer group.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, advertise the extended community attribute to peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer test advertise-ext-community
apply extcommunity
if-match extcommunity
ip extcommunity-list
peer advertise-policy exist-policy
Use peer advertise-policy exist-policy to specify an existent policy to control route advertisement.
Use undo peer advertise-policy exist-policy to remove the configuration.
Syntax
In BGP IPv4 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] } advertise-policy advertise-policy-name exist-policy exist-policy-name
undo peer { group-name | ipv4-address [ mask-length ] } advertise-policy exist-policy
In BGP IPv6 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } advertise-policy advertise-policy-name exist-policy exist-policy-name
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } advertise-policy exist-policy
Default
No existent policy is specified to control route advertisement.
Views
BGP IPv4 unicast address family view
BGP IPv6 unicast address family 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 specifies 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 all dynamic peers in the subnet.
advertise-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters. The routing policy is used as the route advertisement policy.
exist-policy exist-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters. The routing policy is used as the existent policy.
Usage guidelines
After you configure this command, routes that match the route advertisement policy can be advertised only when the BGP routing table contains prefixes that match the existent policy.
The existent policy does not apply to routes that do not match the route advertisement policy.
Examples
# In BGP IPv4 unicast address family view, configure BGP to advertise routes matching routing policy adv-policy to peer 1.1.1.1 only when the BGP routing table contains prefixes matching routing policy ex-policy.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer 1.1.1.1 advertise-policy adv-policy exist-policy ex-policy
Related commands
filter-policy export
filter-policy import
peer as-path-acl
peer filter-policy
peer prefix-list
peer route-policy
peer advertise-policy non-exist-policy
route-policy
peer advertise-policy non-exist-policy
Use peer advertise-policy non-exist-policy to specify a nonexistent policy to control route advertisement.
Use undo peer advertise-policy non-exist-policy to remove the configuration.
Syntax
In BGP IPv4 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] } advertise-policy advertise-policy-name non-exist-policy non-exist-policy-name
undo peer { group-name | ipv4-address [ mask-length ] } advertise-policy non-exist-policy
In BGP IPv6 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } advertise-policy advertise-policy-name non-exist-policy non-exist-policy-name
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } advertise-policy non-exist-policy
Default
No nonexistent policy is specified to control route advertisement.
Views
BGP IPv4 unicast address family view
BGP IPv6 unicast address family 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 specifies 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 all dynamic peers in the subnet.
advertise-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters. The routing policy is used as the route advertisement policy.
non-exist-policy non-exist-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters. The routing policy is used as the nonexistent policy.
Usage guidelines
After you configure this command, routes that match the route advertisement policy can be advertised only when the BGP routing table does not contain any prefixes that match the nonexistent policy.
The nonexistent policy does not apply to routes that do not match the route advertisement policy.
Examples
# In BGP IPv4 unicast address family view, configure BGP to advertise routes matching routing policy adv-policy to peer 1.1.1.1 only when the BGP routing table does not contain any prefixes matching routing policy n-ex-policy.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer 1.1.1.1 advertise-policy adv-policy non-exist-policy n-ex-policy
Related commands
filter-policy export
filter-policy import
peer as-path-acl
peer filter-policy
peer prefix-list
peer route-policy
peer advertise-policy exist-policy
route-policy
peer allow-as-loop
Use peer allow-as-loop to allow a local AS number to exist in the AS_PATH attribute of routes from a peer or peer group, and to set the number of times the local AS number can appear.
Use undo peer allow-as-loop to remove the configuration.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP L2VPN address family view/BGP IPv4 multicast address family view/BGP EVPN address family view:
peer { group-name | ipv4-address [ mask-length ] } allow-as-loop [ number ]
undo peer { group-name | ipv4-address [ mask-length ] } allow-as-loop
In BGP IPv6 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } allow-as-loop [ number ]
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } allow-as-loop
In BGP VPN IPv6 unicast address family view/BGP IPv6 multicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } allow-as-loop [ number ]
undo peer { group-name | ipv6-address [ prefix-length ] } allow-as-loop
Default
The local AS number is not allowed to exist in the AS_PATH attribute of routes from a peer or peer group.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP-VPNv4 address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP L2VPN address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
BGP EVPN address family 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 in this command, BGP allows a local AS number to exist in the AS_PATH attribute of routes from 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 allows a local AS number to exist in the AS_PATH attribute of routes from all dynamic peers in the subnet.
number: Specifies the number of times for which the local AS number can appear, in the range of 1 to 10. The default number is 1. If the number of times for which the local AS number appears in a route is more than the specified number, BGP considers that a routing loop occurs and discards the route.
Usage guidelines
By default, BGP does not receive routes that contain the local AS number in the AS_PATH attribute to avoid routing loops. However, in some network environments, the AS_PATH attribute of a route from a peer must be allowed to contain the local AS number (for example, a Hub&Spoke network in MPLS L3VPN). Otherwise, the route cannot be advertised correctly.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, set the number of times the local AS number can appear in AS_PATH attribute of routes from peer group test to 2.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer test allow-as-loop 2
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.
Syntax
peer group-name as-number as-number
undo peer group-name as-number
Default
No AS number is specified for a peer group.
Views
BGP instance view
BGP-VPN instance view
Predefined user roles
network-admin
Parameters
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.
Usage guidelines
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.
Examples
# In BGP instance view of BGP instance default, 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.
Syntax
peer { ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } as-number as-number
undo peer { ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] }
Default
No BGP peers exist.
Views
BGP instance view
BGP-VPN instance view
Predefined user roles
network-admin
Parameters
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.
Usage guidelines
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.
Examples
# In BGP instance view of BGP instance default, 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
Related commands
display bgp peer
peer enable
peer group
peer as-path-acl
Use peer as-path-acl to specify an AS path list to filter routes incoming from or outgoing to a peer or peer group.
Use undo peer as-path-acl to delete the AS path list specified to filter routes incoming from or outgoing to a peer or peer group.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP IPv4 multicast address family view:
peer { group-name | ipv4-address [ mask-length ] } as-path-acl as-path-acl-number { export | import }
undo peer { group-name | ipv4-address [ mask-length ] } as-path-acl { export | import }
In BGP IPv6 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } as-path-acl as-path-acl-number { export | import }
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } as-path-acl { export | import }
In BGP IPv6 multicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } as-path-acl as-path-acl-number { export | import }
undo peer { group-name | ipv6-address [ prefix-length ] } as-path-acl { export | import }
Default
No AS path list is specified for filtering.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP-VPNv4 address family view
BGP IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family 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 specifies an AS path list to filter routes incoming from or outgoing 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 AS path list to filter routes incoming from or outgoing to all dynamic peers in the subnet.
as-path-acl-number: Specifies an AS path list by its number in the range of 1 to 256.
export: Filters outgoing routes.
import: Filters incoming routes.
Usage guidelines
The specified AS path list must have been created with the ip as-path command in system view. If you specify a nonexistent AS path list, all routes can pass the AS path list.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, specify the AS path list 1 to filter routes outgoing to the peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer test as-path-acl 1 export
Related commands
filter-policy export
filter-policy import
ip as-path
peer filter-policy
peer prefix-list
peer route-policy
peer bfd
Use peer bfd to enable BFD for the link to a BGP peer or peer group.
Use undo peer bfd to remove the configuration.
Syntax
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } bfd [ multi-hop | single-hop ]
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } bfd
Default
BFD is disabled for the link to a BGP peer or peer group.
Views
BGP instance view
BGP-VPN 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 enables BFD for links 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 enables BFD for links to all dynamic peers in the subnet.
multi-hop: Enables multi-hop BFD.
single-hop: Enables single-hop BFD.
Usage guidelines
When you do not specify the multi-hop keyword or the single-hop keyword:
· If an IBGP peer or peer group is specified, this command enables multi-hop BFD for the IBGP peer or peer group.
· If a directly connected EBGP peer or peer group is specified and the peer ebgp-max-hop command is not configured, this command enables single-hop BFD for the EBGP peer or peer group. If the EBGP peer or peer group is not directly connected or the peer ebgp-max-hop command is configured, this command enables multi-hop BFD for the EBGP peer or peer group.
For more information about multi-hop and single-hop BFD, see High Availability Configuration Guide.
BFD helps speed up BGP routing convergence upon link failures. However, if you have enabled GR, use BFD with caution. BFD might detect a failure before the system performs GR, resulting in GR failure. If you have enabled both BFD and GR for BGP, do not disable BFD during a GR process to avoid GR failure.
To establish a BFD session to a BGP peer, you must configure the same BFD detection mode (multi-hop or single-hop) on the local router and the BGP peer.
Examples
# In BGP instance view of BGP instance default, enable BFD for the link to BGP peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer test bfd
display bfd session (High Availability Command Reference)
display bgp peer
peer capability-advertise conventional
Use peer capability-advertise conventional to disable the BGP multi-protocol extension, route refresh, and 4-byte AS number features for a peer or peer group.
Use undo peer capability-advertise conventional to enable the BGP multi-protocol extension, route refresh, and 4-byte AS number features for a peer or peer group.
Syntax
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } capability-advertise conventional
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } capability-advertise conventional
Default
The BGP multi-protocol extension, route refresh, and 4-byte AS number features are enabled.
Views
BGP instance view
BGP-VPN 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 disables BGP multi-protocol extension and route refresh 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 disables BGP multi-protocol extension and route refresh for all dynamic peers in the subnet.
Usage guidelines
The route refresh feature enables BGP to send and receive Route-refresh messages and implement BGP session soft-reset.
The multi-protocol extension feature enables BGP to advertise and receive routing information for various protocols (for example, IPv6 routing information).
The 4-byte AS number feature enables BGP to use 4-byte AS numbers in the range of 1 to 4294967295.
If both the peer capability-advertise conventional and peer capability-advertise route-refresh commands are executed, the most recent configuration takes effect.
Examples
# In BGP instance view of BGP instance default, disable the multi-protocol extension, route refresh, and 4-byte AS number features for peer 1.1.1.1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer 1.1.1.1 as-number 100
[Sysname-bgp-default] peer 1.1.1.1 capability-advertise conventional
display bgp peer
peer capability-advertise route-refresh
peer capability-advertise route-refresh
Use peer capability-advertise route-refresh to enable BGP route refresh for a peer or peer group.
Use undo peer capability-advertise route-refresh to disable BGP route refresh for a peer or peer group.
Syntax
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } capability-advertise route-refresh
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } capability-advertise route-refresh
Default
BGP route refresh is enabled.
Views
BGP instance view
BGP-VPN 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 enables BGP route refresh 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 enables BGP route refresh for all dynamic peers in the subnet.
Usage guidelines
The route refresh feature enables BGP to send and receive Route-refresh messages.
BGP uses the route refresh feature to implement BGP session soft-reset. After a policy is modified, the router advertises a Route-refresh message to the peers. The peers resend their routing information to the router. After receiving the routing information, the router filters the routing information by using the new policy. This method allows you to refresh the BGP routing table and apply the new route selection policy without tearing down BGP sessions.
BGP route refresh requires that both the local router and the peer support route refresh.
If both the peer capability-advertise route-refresh and peer capability-advertise conventional commands are executed, the most recent configuration takes effect.
Examples
# In BGP instance view of BGP instance default, enable BGP route refresh for peer 1.1.1.1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer 1.1.1.1 as-number 100
[Sysname-bgp-default] peer 1.1.1.1 capability-advertise route-refresh
Related commands
display bgp peer
peer capability-advertise conventional
peer keep-all-routes
refresh bgp
peer capability-advertise suppress-4-byte-as
Use peer capability-advertise suppress-4-byte-as to enable 4-byte AS number suppression.
Use undo peer capability-advertise suppress-4-byte-as to disable 4-byte AS number suppression.
Syntax
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } capability-advertise suppress-4-byte-as
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } capability-advertise suppress-4-byte-as
Default
The 4-byte AS number suppression feature is disabled.
Views
BGP instance view
BGP-VPN 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 enables 4-byte AS number suppression 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 enables 4-byte AS number suppression for all dynamic peers in the subnet.
Usage guidelines
BGP supports 4-byte AS numbers. The 4-byte AS number occupies four bytes, in the range of 1 to 4294967295. By default, a device sends an Open message to the peer device for session establishment. The Open message indicates that the device supports 4-byte AS numbers. If the peer device supports 2-byte AS numbers instead of 4-byte AS numbers, the session cannot be established. To resolve this issue, enable the 4-byte AS number suppression feature. The device then sends an Open message to inform the peer that it does not support 4-byte AS numbers, so the BGP session can be established.
If the peer device supports 4-byte AS numbers, do not enable the 4-byte AS number suppression feature. If this feature is enabled, the BGP session cannot be established.
Examples
# In BGP instance view of BGP instance default, enable 4-byte AS number suppression for peer 1.1.1.1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer 1.1.1.1 as-number 100
[Sysname-bgp-default] peer 1.1.1.1 capability-advertise suppress-4-byte-as
Related commands
display bgp peer
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.
Syntax
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
Default
BGP uses the primary IPv4 or IPv6 address of the egress interface in the optimal route destined for the BGP peer or peer group as the source address.
Views
BGP instance view
BGP-VPN 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 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.
Usage guidelines
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.
You can change the source address in 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.
· On a BGP router that has multiple links to a peer, if the source interface fails, BGP must re-establish TCP connections. To avoid this problem, use a loopback interface as the source interface or use the IP address of a loopback interface as the source address.
· To establish multiple BGP sessions to a router, specify a source address or source interface for each peer if the BGP sessions use the IP addresses of different interfaces. Specify a source address for each peer if the BGP sessions use the different addresses of the same interface. Otherwise, the local BGP router might fail to establish a TCP connection to a peer when it uses the optimal route to determine the source address.
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.
You cannot specify a virtual template (VT) interface as the source interface for establishing TCP connections because a VT interface cannot process services.
Examples
# In BGP instance view of BGP instance default, specify loopback 0 as the source interface for TCP connections to the 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.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP IPv4 multicast address family view:
peer { group-name | ipv4-address [ mask-length ] } default-route-advertise [ route-policy route-policy-name ]
undo peer { group-name | ipv4-address [ mask-length ] } default-route-advertise
In BGP VPNv4 address family view:
peer { group-name | ipv4-address [ mask-length ] } default-route-advertise vpn-instance vpn-instance-name
undo peer { group-name | ipv4-address } default-route-advertise vpn-instance vpn-instance-name
In BGP IPv6 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } default-route-advertise [ route-policy route-policy-name ]
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } default-route-advertise
In BGP-VPN IPv6 unicast address family view/BGP IPv6 multicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } default-route-advertise [ route-policy route-policy-name ]
undo peer { group-name | ipv6-address [ prefix-length ] } default-route-advertise
In BGP IPv4 RT filter address family view:
peer { group-name | ip-address [ mask-length ] } default-route-advertise [ route-policy route-policy-name ]
undo peer { group-name | ip-address [ mask-length ] } default-route-advertise
Default
No default route is advertised to any peers or peer groups.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP VPNv4 address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
BGP IPv4 RT filter address family 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 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.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to modify the route attribute.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
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.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, 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.
Syntax
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
Default
No description information is configured for a peer or peer group.
Views
BGP instance view
BGP-VPN 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 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 of BGP instance default, configure a description for the peer group test as ISP1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer test description ISP1
peer ebgp-max-hop
Use peer ebgp-max-hop to enable BGP to establish an EBGP session to an indirectly connected peer or peer group and specify the maximum hop count.
Use undo peer ebgp-max-hop to disable BGP to establish an EBGP session to an indirectly connected peer or peer group.
Syntax
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } ebgp-max-hop [ hop-count ]
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } ebgp-max-hop
Default
BGP does not establish an EBGP session to an indirectly connected peer or peer group.
Views
BGP instance view
BGP-VPN 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 in this command, BGP establishes EBGP sessions to all indirectly connected 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 establishes EBGP sessions to all indirectly connected dynamic peers in the subnet.
hop-count: Specifies the maximum number of hop counts, in the range of 1 to 255. The default is 64.
Usage guidelines
To become EBGP peers, two routers must be directly connected and use directly connected interfaces to establish an EBGP session. If they are not directly connected, use the peer ebgp-max-hop command to establish an EBGP session over multiple hops between two peers.
This command takes effect only on the routes generated after you execute this command. To apply this command to existing routes, use the refresh bgp command to refresh BGP routes.
When the BGP GTSM feature is enabled, two peers can establish an EBGP session after passing GTSM check, regardless of whether the maximum number of hops is reached.
Examples
# In BGP instance view of BGP instance default, enable BGP to establish EBGP sessions to an indirectly connected EBGP peer group test, and set the maximum hop count to 64 (default).
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer test ebgp-max-hop
peer ttl-security
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.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP-VPN VPNv4 address family view/BGP VPNv6 address family view/BGP L2VPN address family view/BGP IPv4 multicast address family view/BGP IPv4 MDT address family view/BGP IPv4 RT filter address family view:
peer { group-name | ipv4-address [ mask-length ] } enable
undo peer { group-name | ipv4-address [ mask-length ] } enable
In BGP IPv6 unicast address family view:
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
In BGP LS address family view:
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
In BGP-VPN IPv6 unicast address family view/BGP IPv6 multicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } enable
undo peer { group-name | ipv6-address [ prefix-length ] } enable
Default
BGP cannot exchange routing information with a peer or peer group.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP-VPNv4 address family view
BGP-VPN VPNv4 address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP LS address family view
BGP-VPNv6 address family view
BGP L2VPN address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
BGP IPv4 MDT address family view
BGP IPv4 RT filter address family 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 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.
Usage guidelines
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-VPN 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 specified VPN instance.
· In BGP VPNv4 address family view, the command enables the capability to exchange VPNv4 routing information. In an MPLS L3VPN network, execute the command on PE devices in BGP VPNv4 address family view.
· In BGP-VPN VPNv4 address family view, the command enables the capability to exchange VPNv4 routing information. In a nested VPN network, execute this command on ISP PE devices in BGP-VPN VPNv4 address family view to do the following:
¡ Enable the PE devices to exchange BGP VPNv4 routing information with ISP CEs.
¡ Add the VPNv4 routes learned by the PE devices to the routing table of the specified VPN instance.
· 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-VPN 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 specified VPN instance.
· In BGP VPNv6 address family view, the command enables the capability to exchange VPNv6 routing information. In an IPv6 MPLS L3VPN network, execute the command on PE devices in BGP VPNv6 address family view.
· In BGP L2VPN address family view, the command enables the capability to exchange L2VPN information. In an MPLS L2VPN or a VPLS network, execute the command on PE devices in BGP L2VPN address family view.
· In BGP IPv4 multicast address family view, the command enables the capability to exchange IPv4 unicast routes used for RPF check. For information about RPF check, see IP Multicast Configuration Guide.
· In BGP IPv6 multicast address family view, the command enables the capability to exchange IPv6 unicast routes used for RPF check. For information about RPF check, see IP Multicast Configuration Guide.
· In BGP IPv4 MDT address family view, the command enables the capability to exchange MDT information. For multicast VPN, you must configure this command in BGP IPv4 MDT address family view on PEs.
· In BGP IPv4 RT filter address family view, the command enables the capability to exchange IPv4 RT filter routing information. In an MPLS L3VPN network, execute the command on PE devices in BGP IPv4 RT filter address family view.
The undo peer enable command disables BGP to exchange routing information for the corresponding address family with the peer.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, 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
Related commands
display bgp peer
peer fake-as
Use peer fake-as to advertise a fake AS number to a peer or peer group.
Use undo peer fake-as to remove the fake AS number advertised to a peer or peer group.
Syntax
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } fake-as as-number
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } fake-as
Default
No fake local AS number is advertised to a peer or peer group.
Views
BGP instance view
BGP-VPN 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 advertises a fake AS number 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 fake AS number to all dynamic peers in the subnet.
as-number: Specifies a fake AS number in the range of 1 to 4294967295.
Usage guidelines
After you move a BGP router from an AS to another AS (from AS 2 to AS 3 for example), you have to modify the AS number of the router on all its EBGP peers. To avoid such modifications, you can configure the router to advertise a fake AS number 2 to its EBGP peers so that the EBGP peers still think that Router A is in AS 2.
The peer fake-as command is applicable only to EBGP peers or peer groups.
If you execute the peer fake-as command on the local router, specify the local router's AS number on the peer as the fake local AS number specified in the command.
Examples
# In BGP instance view of BGP instance default, advertise a fake AS number of 200 to the peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer test fake-as 200
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.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP IPv4 multicast address family view:
peer { group-name | ipv4-address [ mask-length ] } filter-policy acl-number { export | import }
undo peer { group-name | ipv4-address [ mask-length ] } filter-policy { export | import }
In BGP IPv6 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } filter-policy acl6-number { export | import }
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } filter-policy { export | import }
In BGP-VPN IPv6 unicast address family view/BGP IPv6 multicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } filter-policy acl6-number { export | import }
undo peer { group-name | ipv6-address [ prefix-length ] } filter-policy { export | import }
In BGP VPNv6 address family view:
peer { group-name | ipv4-address [ mask-length ] } filter-policy acl6-number { export | import }
undo peer { group-name | ipv4-address [ mask-length ] } filter-policy { export | import }
Default
No ACL-based filtering is configured.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP VPNv4 address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP VPNv6 address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family 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 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.
acl-number: Specifies an ACL by its number in the range of 2000 to 3999.
acl6-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.
Usage guidelines
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/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ip source sour-addr sour-wildcard command.
· To deny/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. The subnet mask must be contiguous. Otherwise, the configuration does not take effect.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, apply ACL 2000 to filter routes advertised to the 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
Related commands
acl (ACL and QoS Command Reference)
filter-policy export
filter-policy import
peer as-path-acl
peer prefix-list
peer route-policy
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.
Syntax
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
Default
No peers exist in a peer group.
Views
BGP instance view
BGP-VPN instance view
Predefined user roles
network-admin
Parameters
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.
Usage guidelines
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.
Examples
# In BGP instance view of BGP instance default, add peer 10.1.1.1 to the 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 ignore
Use peer ignore to disable BGP session establishment with a peer or peer group.
Use undo peer ignore to enable BGP session establishment with a peer or peer group.
Syntax
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } ignore
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } ignore
Default
BGP can establish a session to a peer or peer group.
Views
BGP instance view
BGP-VPN 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 in this command, BGP tears down sessions 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 in this command, BGP tears down sessions to all dynamic peers in the subnet.
Usage guidelines
This command enables you to temporarily tear down the BGP session to a peer or peer group. Then you can perform network upgrade and maintenance without needing to delete and reconfigure the peer or peer group. To recover the session, execute the undo peer ignore command.
If a session has been established to a peer, executing the peer ignore command for the peer tears down the session and clears all related routing information.
If sessions have been established to a peer group, executing the peer ignore command for the peer group disables the sessions to all peers in the group and clears all related routing information.
Examples
# In BGP instance view of BGP instance default, disable session establishment with peer 1.1.1.1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer 1.1.1.1 ignore
peer ignore-originatorid
Use peer ignore-originatorid to configure BGP to ignore the ORIGINATOR_ID attribute in BGP route updates.
Use undo peer ignore-originatorid to remove the configuration.
Syntax
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } ignore-originatorid
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } ignore-originatorid
Default
BGP does not ignore the ORIGINATOR_ID attribute in BGP route updates.
Views
BGP instance view
BGP-VPN 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.
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 ignores the ORIGINATOR_ID attribute in BGP route updates from all dynamic peers in the subnet.
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 in this command, BGP ignores the ORIGINATOR_ID attribute in BGP route updates from all dynamic peers in the subnet.
Usage guidelines
|
|
IMPORTANT: Before using this command, make sure it does not cause any routing loops to the network. |
By default, BGP drops incoming route updates whose ORIGINATOR_ID attribute is the same as the local router ID. Some networks such as firewall networks require BGP to accept such route updates. To meet the requirement, you must configure BGP to ignore the ORIGINATOR_ID attribute.
After you execute this command, BGP also ignores the CLUSTER_LIST attribute.
Examples
# In BGP instance view of BGP instance default, configure BGP to ignore the ORIGINATOR_ID attribute in BGP route updates from the peer 1.1.1.1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer 1.1.1.1 ignore-originatorid
peer ipsec-profile
Use peer ipsec-profile to apply an IPsec profile to an IPv6 BGP peer or peer group.
Use undo peer ipsec-profile to remove the profile from an IPv6 BGP peer or peer group.
Syntax
peer { group-name | ipv6-address [ prefix-length ] } ipsec-profile profile-name
undo peer { group-name | ipv6-address [ prefix-length ] } ipsec-profile
Default
No IPsec profile is configured for any IPv6 BGP peers or peer groups.
Views
BGP instance view
BGP-VPN 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.
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 applies an IPsec profile to all dynamic peers in the subnet.
profile-name: Specifies an IPsec profile by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
IPsec can protect IPv6 BGP packets from data eavesdropping, tampering, and attacks caused by forged IPv6 BGP packets.
When two IPv6 BGP neighbor devices, for example Device A and Device B, are configured with IPsec, Device A encapsulates an IPv6 BGP packet with IPsec before sending it to Device B. If Device B successfully receives and decapsulates the packet, it establishes an IPv6 BGP peer relationship with Device A or learns IPv6 BGP routes to Device A. If Device B receives but fails to decapsulate the packet, or receives a packet not protected by IPsec, it discards the packet.
Configure IPsec to protect IPv6 BGP packets through the following steps:
1. Configure an IPsec transform set.
2. Configure a manual IPsec profile.
3. Execute this command to apply the IPsec profile to an IPv6 BGP peer or peer group.
For more information about IPsec transform sets and IPsec profiles, see Security Configuration Guide.
This command supports only IPsec profiles in manual mode.
If you configure IPsec on a device, you must configure IPsec on its IPv6 BGP peer. Otherwise, IPv6 BGP packets cannot be received.
Examples
# In BGP instance view of BGP instance default, apply IPsec profile profile001 to peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer test ipsec-profile profile001
Related commands
display bgp group
display bgp peer
peer keep-all-routes
Use peer keep-all-routes to save all route updates from a peer or peer group, regardless of whether the routes have passed the configured routing policy.
Use undo peer keep-all-routes to remove the configuration.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP IPv4 multicast address family view:
peer { group-name | ipv4-address [ mask-length ] } keep-all-routes
undo peer { group-name | ipv4-address [ mask-length ] } keep-all-routes
In BGP IPv6 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } keep-all-routes
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } keep-all-routes
In BGP-VPN IPv6 unicast address family view/BGP IPv6 multicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } keep-all-routes
undo peer { group-name | ipv6-address [ prefix-length ] } keep-all-routes
Default
Route updates from a peer or peer group are not saved.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP VPNv4 address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family 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 saves all route updates from all dynamic peers in the subnet, regardless of whether the routes have passed the configured routing policy.
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 saves all route updates from all dynamic peers in the subnet, regardless of whether the routes have passed the configured routing policy.
Usage guidelines
To implement BGP session soft-reset when the local router and a peer or peer group do not support the route refresh feature, use the peer keep-all-routes command. The command saves all route updates received from the peer or peer group. After modifying the route selection policy, filter all saved routes with the new policy to refresh the routing table. This method avoids tearing down BGP sessions.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, save all route updates from 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 keep-all-routes
Related commands
peer capability-advertise route-refresh
refresh bgp
peer label-route-capability
Use peer label-route-capability to enable BGP to exchange labeled routes with a peer or peer group.
Use undo peer label-route-capability to disable BGP from exchanging labeled routes with a peer or peer group.
Syntax
peer { group-name | ipv4-address [ mask-length ] } label-route-capability
undo peer { group-name | ipv4-address [ mask-length ] } label-route-capability
Default
BGP cannot exchange labeled routes with a peer or peer group.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family 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 in this command, BGP exchanges labeled routes with all dynamic peers in the subnet.
Usage guidelines
On an inter-AS option C network, use this command in BGP IPv4 unicast or BGP-VPN IPv4 unicast address family view to exchange labeled IPv4 unicast routes for inter-AS public LSP establishment.
On a 6PE network, use this command in BGP IPv6 unicast address family view to exchange labeled IPv6 unicast routes for forwarding IPv6 packets over an IPv4 network.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, enable BGP to exchange labeled IPv4 routes with peer 2.2.2.2.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4
[Sysname-bgp-default-ipv4] peer 2.2.2.2 label-route-capability
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.
Syntax
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
Default
Logging for BGP session state changes is enabled for all peers or peer groups.
Views
BGP instance view
BGP-VPN 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 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.
Usage guidelines
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 Network Management and Monitoring 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.
Examples
# In BGP instance view of BGP instance default, 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
Related commands
display bgp peer
log-peer-change
peer low-memory-exempt
Use peer low-memory-exempt to configure BGP to protect EBGP peers or peer groups when the memory usage reaches level 2 threshold.
Use undo peer low-memory-exempt to remove the configuration.
Syntax
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } low-memory-exempt
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } low-memory-exempt
Default
When the memory usage reaches level 2 threshold, BGP tears down an EBGP session to release memory resources periodically.
Views
BGP instance view
BGP-VPN 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 in this command, BGP protects all dynamic peers in the subnet when the memory usage reaches level 2 threshold.
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 protects all dynamic peers in the subnet when the memory usage reaches level 2 threshold.
Usage guidelines
Memory usage includes the following levels of thresholds: normal, level 1, level 2, and level 3. When level 2 threshold is reached, BGP tears down an EBGP session to release memory resources periodically until the memory usage is exempt from level 2 threshold. You can use this command to avoid tearing down the BGP session to an EBGP peer when memory usage reaches level 2 threshold.
For more information about thresholds, see Fundamentals Configuration Guide.
Examples
# In BGP instance view of BGP instance default, configure BGP to protect EBGP peer 1.1.1.1 when the memory usage reaches level 2 threshold.
<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 low-memory-exempt
peer next-hop-local
Use peer next-hop-local to set the local router as the next hop for routes sent to a peer or peer group.
Use undo peer next-hop-local to remove the configuration.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/ BGP IPv4 multicast address family view/BGP EVPN address family view:
peer { group-name | ipv4-address [ mask-length ] } next-hop-local
undo peer { group-name | ipv4-address [ mask-length ] } next-hop-local
In BGP IPv6 unicast address family view/BGP IPv6 multicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } next-hop-local
undo peer { group-name | ipv6-address [ prefix-length ] } next-hop-local
Default
BGP sets the local router as the next hop for all routes sent to an EBGP peer or peer group.
BGP sets the local router as the next hop for EBGP routes sent to an IBGP peer or peer group for BGP VPNv4 address family. It does not set the local router as the next hop for EBGP routes sent to an IBGP peer or peer group for other address families.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP VPNv4 address family view
BGP IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
BGP EVPN address family 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 the local router as the next hop for routes sent 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 sets the local router as the next hop for routes sent to all dynamic peers in the subnet.
Usage guidelines
By default, BGP does not set the local router as the next hop for EBGP routes sent to an IBGP peer or peer group. To ensure that an IBGP peer can find the next hop, you can use this command to specify the router as the next hop for routes sent to the IBGP peer.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, specify the router as the next hop for routes sent to peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer test next-hop-local
peer password
Use peer password to enable MD5 authentication for a BGP peer or peer group.
Use undo peer password to remove MD5 authentication for a BGP peer or peer group.
Syntax
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } password { cipher | simple } password
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } password
Default
MD5 authentication is disabled.
Views
BGP instance view
BGP-VPN 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 enables MD5 authentication 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 enables MD5 authentication for all dynamic peers in the subnet.
cipher: Specifies a password in encrypted form.
simple: Specifies a password in plaintext form. For security purposes, the password specified in plaintext form will be stored in encrypted form.
password: Specifies the password. Its encrypted form is a case-sensitive string of 33 to 137 characters. Its plaintext form is a case-sensitive string of 1 to 80 characters.
Usage guidelines
You can enable MD5 authentication to enhance security using the following methods:
· Perform MD5 authentication when establishing TCP connections. Only the two parties that have the same password configured can establish TCP connections.
· Perform MD5 calculation on TCP segments to avoid modification to the encapsulated BGP packets.
Examples
# In BGP instance view of BGP instance default, perform MD5 authentication on the TCP connection between the local router 10.1.100.1 and the peer router 10.1.100.2. Set the authentication password to aabbcc in plaintext form.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer 10.1.100.2 password simple aabbcc
peer preferred-value
Use peer preferred-value to set a preferred value for routes received from a peer or peer group.
Use undo peer preferred-value to remove the configuration.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP VPNv6 address family view/BGP IPv4 multicast address family view:
peer { group-name | ipv4-address [ mask-length ] } preferred-value value
undo peer { group-name | ipv4-address [ mask-length ] } preferred-value
In BGP IPv6 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } preferred-value value
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } preferred-value
In BGP-VPN IPv6 unicast address family view/BGP IPv6 multicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } preferred-value value
undo peer { group-name | ipv6-address [ prefix-length ] } preferred-value
Default
The preferred value is 0 for routes received from a peer or peer group.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP-VPNv4 address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP-VPNv6 address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family 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 specifies a preferred value for routes received from 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 a preferred value for routes received from all dynamic peers in the subnet.
value: Specifies a preferred value in the range of 0 to 65535.
Usage guidelines
If multiple routes that have the same destination are learned from different peers, you can specify different preferred values for the routes as needed to control BGP path selection. The one with the greatest preferred value is selected as the optimal route to the destination.
The preferred value is used for route selection on the local router and is not advertised to the peer. It has only local significance.
You can also use the apply preferred-value command in a routing policy to configure the preferred value for BGP routes. If both the peer preferred-value and apply preferred-value commands are configured, the apply preferred-value command applies. If the preferred value is not set in the routing policy or no routing policy is configured, the peer preferred-value command applies.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, set the preferred value to 50 for routes from 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 preferred-value 50
apply preferred-value
route-policy
peer prefix-list
Use peer prefix-list to specify a prefix list to filter routes received from or advertised to a peer or peer group.
Use undo peer prefix-list to remove the prefix list specified to filter routes received from or advertised to a peer or peer group.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP IPv4 multicast address family view:
peer { group-name | ipv4-address [ mask-length ] } prefix-list prefix-list-name { export | import }
undo peer { group-name | ipv4-address [ mask-length ] } prefix-list { export | import }
In BGP IPv6 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } prefix-list ipv6-prefix-name { export | import }
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } prefix-list { export | import }
In BGP-VPN IPv6 unicast address family view/BGP IPv6 multicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } prefix-list ipv6-prefix-name { export | import }
undo peer { group-name | ipv6-address [ prefix-length ] } prefix-list { export | import }
In BGP VPNv6 address family view:
peer { group-name | ipv4-address [ mask-length ] } prefix-list ipv6-prefix-name { export | import }
undo peer { group-name | ipv4-address [ mask-length ] } prefix-list { export | import }
Default
No prefix list based filtering is configured.
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP VPNv4 address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP VPNv6 address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family 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 uses a prefix list to filter routes received from or advertised 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 uses a prefix list to filter routes received from or advertised to all dynamic peers in the subnet.
prefix-list-name: Specifies an IPv4 prefix list by its name, a case-sensitive string of 1 to 63 characters.
export: Applies the filter to routes advertised to the specified peer/peer group.
import: Applies the filter to routes received from the specified peer/peer group.
Usage guidelines
The specified IPv4 prefix list or IPv6 prefix list must have been created with the ip prefix-list or ipv6 prefix-list command in system view. If you specify a nonexistent IPv4/IPv6 prefix list, all routes can pass the prefix list.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, use the IPv4 prefix list list1 to filter routes advertised to the peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer test prefix-list list1 export
Related commands
filter-policy export
filter-policy import
ip prefix-list
ipv6 prefix-list
peer as-path-acl
peer filter-policy
peer route-policy
peer public-as-only
Use peer public-as-only to remove private AS numbers in BGP updates sent to an EBGP peer or peer group.
Use undo peer public-as-only to remove the configuration.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP VPNv6 address family view/BGP IPv4 multicast address family view:
peer { group-name | ipv4-address [ mask-length ] } public-as-only
undo peer { group-name | ipv4-address [ mask-length ] } public-as-only
In BGP IPv6 unicast address family view/BGP IPv6 multicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } public-as-only
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } public-as-only
In BGP-VPN IPv6 unicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } public-as-only
undo peer { group-name | ipv6-address [ prefix-length ] } public-as-only
Default
BGP updates sent to an EBGP peer or peer group can carry both public and private AS numbers.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP VPNv4 address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP VPNv6 address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family 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 removes private AS numbers in BGP updates sent 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 removes private AS numbers in BGP updates sent to all dynamic peers in the subnet.
Usage guidelines
Private AS numbers are typically used in test networks, and need not be transmitted in public networks. The range of private AS numbers is from 64512 to 65535.
After you execute the command, you can get the following results:
· If the AS_PATH attribute of a BGP update carries only private AS numbers, the device removes the AS numbers before sending the update to the EBGP peer or peer group.
· If the AS_PATH attribute carries both public and private AS numbers, the command does not take effect. The device sends the BGP update to the EBGP peer or peer group without removing the private AS numbers.
· If the AS_PATH attribute carries AS numbers of the peer or peer group, the command does not take effect. The device sends the BGP update to the peer or peer group without removing the private AS numbers.
This command is applicable only to EBGP peers and peer groups.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, remove private AS numbers in BGP updates sent to EBGP peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer test public-as-only
peer reflect-client
Use peer reflect-client to configure the device as a route reflector and specify a peer or peer group as a client.
Use undo peer reflect-client to remove the configuration.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP VPNv6 address family view/BGP L2VPN address family view/BGP EVPN address family view/BGP IPv4 multicast address family view/BGP IPv4 MDT address family view/BGP IPv4 RT filter address family view:
peer { group-name | ipv4-address [ mask-length ] } reflect-client
undo peer { group-name | ipv4-address [ mask-length ] } reflect-client
In BGP IPv6 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } reflect-client
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } reflect-client
In BGP LS address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } reflect-client
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } reflect-client
In BGP IPv6 multicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } reflect-client
undo peer { group-name | ipv6-address [ prefix-length ] } reflect-client
Default
Neither the route reflector nor the client is configured.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP LS address family view
BGP VPNv4 address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP VPNv6 address family view
BGP L2VPN address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
BGP IPv4 MDT address family view
BGP EVPN address family view
BGP IPv4 RT filter address family 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 configures the device as a route reflector and specifies all dynamic peers in the subnet as clients.
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 device as a route reflector and specifies all dynamic peers in the subnet as clients.
Usage guidelines
Using route reflectors can solve the issue brought by too many IBGP connections. In an AS, a router acts as a route reflector, and other routers act as clients connecting to the route reflector. The route reflector forwards the routing information received from a client to other clients. In this way, all clients can receive routing information from one another without establishing BGP sessions.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, configure the local device as a route reflector and specify the IBGP peer group test as a client.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer test reflect-client
Related commands
reflect between-clients
reflector cluster-id
peer route-limit
Use peer route-limit to set the maximum number of routes that can be received from a peer or peer group.
Use undo peer route-limit to remove the configuration.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP VPNv6 address family view/BGP IPv4 multicast address family view:
peer { group-name | ipv4-address [ mask-length ] } route-limit prefix-number [ { alert-only | discard | reconnect reconnect-time } | percentage-value ] *
undo peer { group-name | ipv4-address [ mask-length ] } route-limit
In BGP IPv6 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } route-limit prefix-number [ { alert-only | discard | reconnect reconnect-time } | percentage-value ] *
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } route-limit
In BGP IPv6 multicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } route-limit prefix-number [ { alert-only | discard | reconnect reconnect-time } | percentage-value ] *
undo peer { group-name | ipv6-address [ prefix-length ] } route-limit
Default
The number of routes that can be received from a peer or peer group is not limited.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP VPNv4 address family view
BGP IPv6 unicast address family view
BGP VPNv6 address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family 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 specifies the maximum number of routes that can be received from 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 the maximum number of routes that can be received from all dynamic peers in the subnet.
prefix-number: Specifies the number of routes that can be received from the peer or peer group. The value range is 1 to 4294967295. The router will tear down the session to the peer or peer group if the following conditions exist:
· The alert-only, discard, and reconnect keywords are not specified.
· The number of routes received from the peer or peer group reaches the prefix-number.
The router will not attempt to re-establish the session to a dynamic BGP peer until the router receives a connection request from the peer. For other peers, you can use the reset bgp command to re-establish the sessions.
alert-only: If the number of routes received from the peer or peer group reaches the prefix-number, the router generates a log message instead of tearing down the session to the peer or peer group. The router can continue to receive routes from the peer or peer group.
discard: If the number of routes received from the peer or peer group reaches the prefix-number, the router retains the session to the peer or peer group. However, it discards excess routes and generates a log message. After the number of routes received from the peer or peer group falls below the prefix-number, the router can continue to receive routes from the peer or peer group. To restore the discarded routes, use the refresh bgp import command to request the peer or peer group to resend the routes.
reconnect reconnect-time: Specifies a reconnect time. After the specified time is reached, the router re-establishes a session to the peer or peer group when the number of routes received from the peer or peer group reaches the prefix-number. The value range for the reconnect-time argument is 1 to 65535 seconds. This option is not available for dynamic BGP peers.
percentage-value: Specifies the threshold value for the router to generate a log message (the router generates a log message when the ratio of the number of received routes to the prefix-number exceeds the percentage value). The value range of this argument is 1 to 100, and the default is 75.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, set the maximum number of routes that can be received from peer 1.1.1.1 to 10000. Configure the router to tear down the session to the peer if the number is exceeded.
<Sysname> system-view
[Sysname] bgp 109
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer 1.1.1.1 route-limit 10000
peer route-policy
Use peer route-policy to apply a routing policy to routes incoming from or outgoing to a peer or peer group.
Use undo peer route-policy to remove the configuration.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP VPNv6 address family view/BGP IPv4 multicast address family view/BGP EVPN address family view:
peer { group-name | ipv4-address [ mask-length ] } route-policy route-policy-name { export | import }
undo peer { group-name | ipv4-address [ mask-length ] } route-policy { export | import }
In BGP-VPN VPNv4 address family view:
peer { group-name | ipv4-address [ mask-length ] } route-policy route-policy-name import
undo peer { group-name | ipv4-address [ mask-length ] } route-policy import
In BGP IPv6 unicast address family view:
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } route-policy route-policy-name { export | import }
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } route-policy { export | import }
In BGP-VPN IPv6 unicast address family view/BGP IPv6 multicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } route-policy route-policy-name { export | import }
undo peer { group-name | ipv6-address [ prefix-length ] } route-policy { export | import }
Default
No routing policy is applied to routes incoming from or outgoing to a peer or peer group.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP VPNv4 address family view
BGP-VPN VPNv4 address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP VPNv6 address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
BGP EVPN address family 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 applies a routing policy to routes incoming from or outgoing 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 applies a routing policy to routes incoming from or outgoing to all dynamic peers in the subnet.
route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
export: Applies the routing policy to routes outgoing to the peer or peer group.
import: Applies the routing policy to routes incoming from the peer or peer group.
Usage guidelines
The specified routing policy must have been configured with the route-policy command in system view. If you specify a nonexistent routing policy, all routes can pass the routing policy.
The if-match interface command, if configured for the applied routing policy, does not take effect on routes.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, apply routing policy test-policy to routes outgoing to the peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] peer test route-policy test-policy export
Related commands
filter-policy export
filter-policy import
peer as-path-acl
peer filter-policy
peer prefix-list
route-policy
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.
Syntax
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
Default
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.
Views
BGP instance view
BGP-VPN 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 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.
Usage guidelines
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.
Examples
# In BGP instance view of BGP instance default, 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.
Syntax
In BGP IPv4 unicast address family view/BGP-VPN IPv4 unicast address family view/BGP VPNv4 address family view/BGP-VPN VPNv4 address family view/BGP VPNv6 address family view/BGP IPv4 multicast address family view:
peer { group-name | ipv4-address [ mask-length ] } soo site-of-origin
undo peer { group-name | ipv4-address [ mask-length ] } soo
In BGP IPv6 unicast address family view:
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
In BGP-VPN IPv6 unicast address family view/BGP IPv6 multicast address family view:
peer { group-name | ipv6-address [ prefix-length ] } soo site-of-origin
undo peer { group-name | ipv6-address [ prefix-length ] } soo
Default
No SoO attribute is configured for a peer or peer group.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP VPNv4 address family view
BGP-VPN VPNv4 address family view
BGP VPNv6 address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family 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 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.
Usage guidelines
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.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, set the SoO attribute to 100:1 for the 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
Related commands
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.
Syntax
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 ]
Default
BGP uses the primary IPv4 or IPv6 address of the egress interface in the optimal route destined for the BGP peer or peer group as the source address for establishing a TCP connection to the peer or peer group.
Views
BGP instance view
BGP-VPN instance view
Predefined user roles
network-admin
Parameters
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.
Usage guidelines
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.
You can change the source address in 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.
· If the source interface fails on a BGP router that has multiple links to a peer, BGP has to re-establish TCP connections. To avoid this problem, use a loopback interface as the source interface or use the IP address of a loopback interface as the source address.
· If the BGP sessions use the IP addresses of different interfaces, specify a source address or source interface for each peer to establish multiple BGP sessions to a router. Specify a source address for each peer if the BGP sessions use the different addresses of the same interface. Otherwise, the local BGP router might fail to establish a TCP connection to a peer when it uses the optimal route to determine the source address.
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.
Examples
# In BGP instance view of BGP instance default, specify the source IPv4 and IPv6 addresses 1.1.1.1 and 1::1 for the peer group test.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer test source-address 1.1.1.1 1::1
Related commands
peer connect-interface
peer ebgp-max-hop
peer substitute-as
Use undo peer substitute-as to remove the configuration.
Syntax
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } substitute-as
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } substitute-as
Default
The AS number of a peer or peer group in the AS_PATH attribute is not replaced.
Views
BGP instance view
BGP-VPN 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 replaces the AS number of all dynamic peers in the subnet in the AS_PATH attribute with the local AS number.
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 replaces the AS number of all dynamic peers in the subnet in the AS_PATH attribute with the local AS number.
Usage guidelines
In MPLS L3VPN, if EBGP is used between PE and CE, sites in different geographical areas must have different AS numbers assigned to ensure correct route advertisement.
If different CEs use the same AS number, you must configure the relevant PE to replace the AS number of the CE as its own AS number. This ensures correct advertisement of private network routes.
Examples
# In BGP instance view of BGP instance default, substitute the local AS number for the AS number of peer 1.1.1.1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer 1.1.1.1 substitute-as
peer soo
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.
Syntax
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
Default
The keepalive interval is 60 seconds, and the hold time is 180 seconds.
Views
BGP instance view
BGP-VPN 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 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.
Usage guidelines
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).
Examples
# In BGP instance view of BGP instance default, 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
BGP-VPN 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
peer ttl-security
Use peer ttl-security to configure Generalized TTL Security Mechanism (GTSM) for a BGP peer or peer group.
Use undo peer ttl-security to disable BGP GTSM for a peer or peer group.
Syntax
peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } ttl-security hops hop-count
undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } ttl-security hops
Default
GTSM is disabled for BGP.
Views
BGP instance view
BGP-VPN 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 configures GTSM 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 GTSM for all dynamic peers in the subnet.
hops hop-count: Specifies the maximum number of hops to the specified peer, in the range of 1 to 254.
Usage guidelines
GTSM protects a BGP session by comparing the TTL value of an incoming IP packet against the valid TTL range. If the TTL value is within the valid TTL range, the packet is accepted. If not, the packet is discarded.
The valid TTL range is from 255 – the configured hop count + 1 to 255.
When GTSM is configured, the BGP packets sent by the device have a TTL of 255.
When GTSM is configured, the local device can establish an EBGP session to the peer after they pass GTSM check, regardless of whether the maximum number of hops is reached.
To use GTSM, you must configure GTSM on both the local and peer devices. You can specify different hop-count values for them.
Examples
# In BGP instance view of BGP instance default, enable GTSM for BGP peer group test and set the maximum number of hops to the specified peer in the peer group to 1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] peer test ttl-security hops 1
Related commands
peer ebgp-max-hop
pic
Use pic to enable BGP FRR for a BGP address family.
Use undo pic to disable BGP FRR for a BGP address family.
Syntax
pic
undo pic
Default
BGP FRR is disabled.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
Predefined user roles
network-admin
Usage guidelines
FRR is used in a dual-homing network to protect a primary route with a backup route. It uses ARP (for IPv4), echo-mode BFD (for IPv4), or ND (for IPv6) to detect the connectivity of the primary route. When the primary route fails, BGP directs packets to the backup route.
After you enable FRR, BGP calculates a backup route for each BGP route in the address family if there are two or more unequal-cost routes to reach the destination.
You can also configure BGP FRR by using the fast-reroute route-policy command, which takes precedence over the pic command. For more information about routing policies, see Layer 3—IP Routing Configuration Guide.
Use the pic command with caution because it might cause routing loops in specific scenarios.
Examples
# Enable BGP FRR in BGP IPv4 unicast address family view of BGP instance default.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] pic
Related commands
preference
Use preference to configure preferences for BGP routes.
Use undo preference to restore the default.
Syntax
preference { external-preference internal-preference local-preference | route-policy route-policy-name }
undo preference
Default
The preferences of external, internal, and local BGP routes are 255, 255, and 130, respectively.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv6 unicast address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
Predefined user roles
network-admin
Parameters
external-preference: Specifies a preference for EBGP routes, in the range of 1 to 255.
internal-preference: Specifies a preference for IBGP routes, in the range of 1 to 255.
local-preference: Specifies a preference for local routes, in the range of 1 to 255.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to set the route preference for matching routes. Routes not matching the routing policy use the default preference.
Usage guidelines
Different routing protocols might find different routes to the same destination. However, not all of those routes are optimal. For route selection, routing protocols, direct routes, and static routes are assigned different preferences. The route with the highest preference is preferred.
Configuring the preferences for BGP routes changes the possibility for the routes to become the optimal route.
To use a routing policy to set the preference, you must configure the preference with the apply preference command in the routing policy in advance. Otherwise, all matching routes use the default preference.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, set preferences for EBGP, IBGP, and local routes to 20, 20, and 200, respectively.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] preference 20 20 200
primary-path-detect bfd
Use primary-path-detect bfd to configure BGP FRR to use BFD to detect next hop connectivity for the primary route.
Use undo primary-path-detect bfd to restore the default.
Syntax
primary-path-detect bfd echo
undo primary-path-detect bfd
Default
BGP FRR uses ARP to detect the connectivity to the next hop of the primary route.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
echo: Uses echo-mode BFD to detect the connectivity to the next hop of the primary route.
Examples
# In BGP instance view of BGP instance default, configure BGP FRR to use echo-mode BFD to detect next hop connectivity for the primary route.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] primary-path-detect bfd echo
Related commands
fast-reroute route-policy
pic
reflect between-clients
Use reflect between-clients to enable route reflection between clients.
Use undo reflect between-clients to disable route reflection between clients.
Syntax
reflect between-clients
undo reflect between-clients
Default
Route reflection between clients is enabled.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP LS address family view
BGP VPNv4 address family view
BGP IPv6 unicast address family view
BGP VPNv6 address family view
BGP L2VPN address family view
BGP EVPN address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
BGP IPv4 MDT address family view
BGP IPv4 RT filter address family view
Predefined user roles
network-admin
Usage guidelines
When a route reflector is configured, and the clients of a route reflector are fully meshed, route reflection is unnecessary because it consumes more bandwidth resources. You can use the undo reflect between-clients command to disable route reflection instead of modifying network configuration or changing network topology.
After route reflection is disabled between clients, routes can still be reflected between a client and a non-client.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, disable route reflection between clients.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] undo reflect between-clients
Related commands
peer reflect-client
reflector cluster-id
Use reflector cluster-id to configure the cluster ID for a route reflector.
Use undo reflector cluster-id to restore the default.
Syntax
reflector cluster-id { cluster-id | ipv4-address }
undo reflector cluster-id
Default
A route reflector uses its router ID as the cluster ID.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP LS address family view
BGP VPNv4 address family view
BGP IPv6 unicast address family view
BGP VPNv6 address family view
BGP L2VPN address family view
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
BGP IPv4 MDT address family view
BGP IPv4 RT filter address family view
Predefined user roles
network-admin
Parameters
cluster-id: Specifies the cluster ID in the format of an integer, in the range of 1 to 4294967295.
ipv4-address: Specifies the cluster ID in the format of an IPv4 address in dotted decimal notation.
Usage guidelines
The route reflector and clients form a cluster. Typically a cluster has one route reflector. The ID of the route reflector is the cluster ID.
You can configure more than one route reflector in a cluster to improve network reliability and prevent a single point of failure. Use this command to configure the same cluster ID for all route reflectors in the cluster to avoid routing loops.
Do not configure the router ID of a client as the cluster ID.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, set the cluster ID on the local router (a reflector in the cluster) to 80.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] reflector cluster-id 80
Related commands
peer reflect-client
reflect between-clients
refresh bgp
Use refresh bgp to manually soft-reset BGP sessions.
Syntax
refresh bgp [ instance instance-name ] { ipv4-address [ mask-length ] | all | external | group group-name | internal } { export | import } ipv4 { multicast | rtfilter | [ unicast ] [ vpn-instance vpn-instance-name ] }
refresh bgp [ instance instance-name ] { ipv6-address [ prefix-length ] | all | external | group group-name | internal } { export | import } ipv6 { multicast | [ unicast ] [ vpn-instance vpn-instance-name ] }
refresh bgp [ instance instance-name ] ipv4-address [ mask-length ] { export | import } ipv6 [ unicast ]
refresh bgp [ instance instance-name ] { ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] | all | external | group group-name | internal } { export | import } link-state
refresh bgp [ instance instance-name ] { ipv4-address [ mask-length ] | all | external | group group-name | internal } { export | import } vpnv4 [ vpn-instance vpn-instance-name ]
refresh bgp [ instance instance-name ] { ipv4-address [ mask-length ] | all | external | group group-name | internal } { export | import } vpnv6
refresh bgp [ instance instance-name ] { ipv4-address [ mask-length ] | all | external | group group-name | internal } { export | import } l2vpn [ evpn ]
Views
User view
Predefined user roles
network-admin
Parameters
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.
multicast: Soft-resets BGP sessions for multicast address family.
rtfilter: Soft-resets BGP sessions for IPv4 RT filter address family.
unicast: Soft-resets BGP sessions for unicast address family.
link-state: Soft-resets BGP sessions for LS address family.
vpnv4: Soft-resets BGP sessions for VPNv4 address family.
vpnv6: Soft-resets BGP sessions for VPNv6 address family.
l2vpn: Soft-resets BGP sessions for L2VPN address family.
evpn: Soft-resets BGP sessions for EVPN address family.
The following matrix shows the evpn keyword and hardware compatibility:
|
Hardware |
Keyword compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK |
Yes |
|
MSR810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28/3600-51 |
Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Keyword compatibility |
|
MSR810-LM-GL |
Yes |
|
MSR810-W-LM-GL |
Yes |
|
MSR830-6EI-GL |
Yes |
|
MSR830-10EI-GL |
Yes |
|
MSR830-6HI-GL |
Yes |
|
MSR830-10HI-GL |
Yes |
|
MSR2600-6-X1-GL |
Yes |
|
MSR3600-28-SI-GL |
No |
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command soft-resets BGP sessions for the specified address family on the public network.
Usage guidelines
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.
If the peer keep-all-routes command is configured, the refresh bgp import command does not take effect.
By default, the unicast keyword is used if you do not specify the multicast, unicast, or rtfilter keyword.
Examples
# Soft-reset all inbound BGP sessions for the IPv4 unicast address family of BGP instance default.
<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.
Syntax
reset bgp [ instance instance-name ] { as-number | ipv4-address [ mask-length ] | all | external | group group-name | internal } ipv4 { mdt | multicast | rtfilter | [ unicast ] [ vpn-instance vpn-instance-name ] }
reset bgp [ instance instance-name ] { as-number | ipv6-address [ prefix-length ] | all | external | group group-name | internal } ipv6 { multicast | [ unicast ] [ vpn-instance vpn-instance-name ] }
reset bgp [ instance instance-name ] ipv4-address [ mask-length ] ipv6 [ unicast ]
reset bgp [ instance instance-name ] { as-number | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] | all | external | group group-name | internal } link-state
reset bgp [ instance instance-name ] { as-number | ipv4-address [ mask-length ] | all | external | group group-name | internal } vpnv4 [ vpn-instance vpn-instance-name ]
reset bgp [ instance instance-name ] { as-number | ipv4-address [ mask-length ] | all | external | group group-name | internal } vpnv6
reset bgp [ instance instance-name ] { as-number | ipv4-address [ mask-length ] | all | external | group group-name | internal } l2vpn [ evpn ]
Views
User view
Predefined user roles
network-admin
Parameters
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.
mdt: Resets BGP sessions for MDT address family.
multicast: Resets BGP sessions for multicast address family.
rtfilter: Resets BGP sessions for IPv4 RT filter address family.
unicast: Resets BGP sessions for unicast address family.
link-state: Resets BGP sessions for LS address family.
vpnv4: Resets BGP sessions for VPNv4 address family.
vpnv6: Resets BGP sessions for VPNv6 address family.
l2vpn: Resets BGP sessions for L2VPN address family.
evpn: Resets BGP sessions for EVPN address family.
The following matrix shows the evpn keyword and hardware compatibility:
|
Hardware |
Keyword compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK |
Yes |
|
MSR810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28/3600-51 |
Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Keyword compatibility |
|
MSR810-LM-GL |
Yes |
|
MSR810-W-LM-GL |
Yes |
|
MSR830-6EI-GL |
Yes |
|
MSR830-10EI-GL |
Yes |
|
MSR830-6HI-GL |
Yes |
|
MSR830-10HI-GL |
Yes |
|
MSR2600-6-X1-GL |
Yes |
|
MSR3600-28-SI-GL |
No |
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command resets BGP sessions for the specified address family on the public network.
Usage guidelines
A reset operation enables the router to apply a new route selection policy by re-establishing BGP sessions. This operation breaks down BGP sessions for a short period of time.
By default, the unicast keyword is used if you do not specify the unicast, mdt, multicast, or rtfilter keyword.
Examples
# Reset all BGP sessions for the IPv4 unicast address family of BGP instance default.
<Sysname> reset bgp all ipv4
reset bgp all
Use reset bgp all to reset all BGP sessions for all address families.
Syntax
reset bgp [ instance instance-name ] all
Views
User view
Predefined user roles
network-admin
Parameters
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.
Usage guidelines
A reset operation enables the router to apply a new route selection policy by re-establishing BGP sessions. This operation breaks down BGP sessions for a short while.
Examples
# Reset all BGP sessions for BGP instance default.
<Sysname> reset bgp all
reset bgp dampening
Use reset bgp dampening to clear BGP route dampening information and release suppressed BGP routes.
Syntax
reset bgp [ instance instance-name ] dampening ipv4 { multicast | [ unicast ] [ vpn-instance vpn-instance-name ] } [ ipv4-address [ mask | mask-length ] ]
reset bgp [ instance instance-name ] dampening ipv6 { multicast | [ unicast ] [ vpn-instance vpn-instance-name ] } [ ipv6-address prefix-length ]
Views
User view
Predefined user roles
network-admin
Parameters
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 BGP route dampening information and releases suppressed BGP routes for the default BGP instance.
ipv4: Clears BGP IPv4 route dampening information and release suppressed BGP IPv4 routes.
ipv6: Clears BGP IPv6 route dampening information and release suppressed BGP IPv6 routes.
multicast: Clears BGP multicast route dampening information and release suppressed BGP multicast routes.
unicast: Clears BGP unicast route dampening information and release suppressed BGP unicast routes.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command clears BGP route dampening information for the public network, and releases suppressed BGP routes.
ipv4-address: Specifies an IPv4 destination network address. If you do not specify a network address, this command clears all BGP route dampening information, and releases all suppressed BGP routes.
mask: Specifies a network mask, in dotted decimal notation.
mask-length: Specifies a mask length in the range of 0 to 32.
ipv6-address: Specifies an IPv6 destination network address. If you do not specify a network address, this command clears all BGP route dampening information, and releases all suppressed BGP routes.
prefix-length: Specifies a prefix length in the range of 0 to 128.
Usage guidelines
When you execute the reset bgp dampening ipv4 command:
· 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 clears dampening information for the route, and releases the suppressed route.
· If you specify the ipv4-address mask or ipv4-address mask-length argument, this command does the following:
¡ Clears dampening information for the route that matches both the specified destination network address and the mask (or mask length).
¡ Releases the suppressed route.
By default, the unicast keyword is used if neither the unicast keyword nor the multicast keyword is specified.
Examples
# Clear dampening information for the public BGP IPv4 unicast route to network 20.1.0.0/16 and release the suppressed route for BGP instance default.
<Sysname> reset bgp dampening ipv4 20.1.0.0 255.255.0.0
Related commands
dampening
display bgp routing-table dampened
reset bgp flap-info
Use reset bgp flap-info to clear flap statistics for BGP routes.
Syntax
reset bgp [ instance instance-name ] flap-info ipv4 { multicast | [ unicast ] [ vpn-instance vpn-instance-name ] } [ ipv4-address [ mask | mask-length ] | as-path-acl as-path-acl-number | peer ipv4-address [ mask-length ] ]
reset bgp [ instance instance-name ] flap-info ipv6 { multicast | [ unicast ] [ vpn-instance vpn-instance-name ] } [ ipv6-address prefix-length | as-path-acl as-path-acl-number | peer ipv6-address [ prefix-length ] ]
Views
User view
Predefined user roles
network-admin
Parameters
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.
multicast: Clears flap statistics for BGP multicast routes.
unicast: Clears flap statistics for BGP unicast routes.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command clears flap statistics for public BGP routes.
ipv4-address: Specifies an IPv4 destination network address.
mask: Specifies a network mask, in dotted decimal notation.
mask-length: Specifies a mask length in the range of 0 to 32.
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.
Usage guidelines
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 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 route that matches both the specified IPv4 destination network address and the mask (or mask length).
By default, the unicast keyword is used if neither the unicast keyword nor the multicast keyword is specified.
Examples
# Clear flap statistics for the public BGP IPv4 unicast route to network 20.1.0.0/16 for BGP instance default.
<Sysname> reset bgp flap-info ipv4 20.1.0.0 16
Related commands
dampening
display bgp routing-table flap-info
retain local-label
Use retain local-label to set an update delay for local MPLS labels.
Use undo retain local-label to restore the default.
Syntax
retain local-label retain-time
undo retain local-label
Default
The update delay is 60 seconds.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
retain-time: Specifies the update delay in the range of 1 to 21845 seconds.
Usage guidelines
BGP includes local MPLS labels in advertised VPNv4 routes, VPNv6 routes, labeled IPv4 unicast routes, and labeled IPv6 unicast routes.
When a local label is changed, BGP removes the old label and advertises the new label. Traffic interruption occurs if BGP peers use the old label to forward packets before they learn the new label. To resolve this issue, configure an update delay for local MPLS labels. BGP does not remove the old label before the update delay timer expires.
Examples
# Set the update delay for local MPLS labels to 100 seconds for BGP instance default.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] retain local-label 100
router id (system view)
Use router id to configure a global router ID.
Use undo router id to restore the default.
Syntax
router id router-id
undo router id
Default
No global router ID is configured.
Views
System view
Predefined user roles
network-admin
Parameters
router-id: Specifies a router ID in IP address format.
Usage guidelines
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.
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 a router ID is changed, use the reset command to make it effective.
Examples
# Configure a global router ID as 1.1.1.1.
<Sysname> system-view
[Sysname] router id 1.1.1.1
Related commands
router-id
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.
Syntax
router-id router-id
undo router-id
Default
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.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
router-id: Specifies a router ID for BGP, in IP address format.
Usage guidelines
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.
Examples
# In BGP instance view of BGP instance default, 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
Related commands
router-id (BGP-VPN instance view)
router id (system view)
router-id (BGP-VPN instance view)
Use router-id to configure a router ID for a BGP VPN instance.
Use undo router-id to restore the default.
Syntax
router-id { router-id | auto-select }
undo router-id
Default
No router ID is configured for a BGP VPN instance, and the BGP VPN instance uses the router ID configured in BGP instance view. If no router ID is configured in BGP instance view, the BGP VPN instance uses the global router ID configured in system view.
Views
BGP-VPN instance view
Predefined user roles
network-admin
Parameters
router-id: Specifies a router ID in IP address format.
auto-select: Automatically selects a router ID for the BGP VPN instance.
Usage guidelines
To run BGP, a VPN instance of a BGP instance must have a router ID, which is an unsigned 32-bit integer that uniquely identifies the BGP VPN router in the AS.
If the auto-select keyword is specified, the system selects a router ID for the BGP VPN instance in the following order:
1. The highest loopback address in the BGP VPN instance as the router ID.
2. The highest physical interface address in the BGP VPN instance as the router ID, regardless of the interface status.
3. 0.0.0.0 as the router ID.
If a non-zero router ID is selected for the BGP VPN instance, the router ID will not change when a more preferable router ID is available in the BGP VPN instance.
To improve availability, specify the IP address of a loopback interface as the router ID.
You can specify a different router ID for each VPN instance on a device.
If you execute this command in the same BGP-VPN instance view multiple times, the most recent configuration takes effect.
Examples
# In BGP-VPN instance view of BGP instance default, set the router ID to 1.1.1.1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] ip vpn-instance vpn1
[Sysname-bgp-default-vpn1] router-id 1.1.1.1
Related commands
router-id (BGP instance view)
router-id (system view)
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.
Syntax
snmp context-name context-name
undo snmp context-name
Default
No SNMP context is configured for a BGP instance.
Views
BGP instance view
Predefined user roles
network-admin
Parameters
context-name: Specifies an SNMP context by its name, a case-sensitive string of 1 to 32 characters.
Usage guidelines
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 BGP instance default if the packet does not carry a context and no SNMP context was configured for 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 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 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.
Examples
# 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
Related commands
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.
Syntax
snmp-agent trap enable bgp [ instance instance-name ]
undo snmp-agent trap enable bgp [ instance instance-name ]
Default
SNMP notifications for BGP are enabled.
Views
System view
Predefined user roles
network-admin
Parameters
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.
Usage guidelines
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.
Examples
# Enable SNMP notifications for BGP instance default.
<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.
Syntax
summary automatic
undo summary automatic
Default
Automatic route summarization is not performed for redistributed IGP subnet routes.
Views
BGP IPv4 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP IPv4 multicast address family view
Predefined user roles
network-admin
Usage guidelines
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.
Examples
# In BGP IPv4 unicast address family view of BGP instance default, 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
Related commands
aggregate
import-route
timer
Use timer to configure a BGP keepalive interval and hold time.
Use undo timer to restore the default.
Syntax
timer keepalive keepalive hold holdtime
undo timer
Default
The BGP keepalive interval and the hold time are 60 seconds and 180 seconds, respectively.
Views
BGP instance view
BGP-VPN instance view
Predefined user roles
network-admin
Parameters
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.
Usage guidelines
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).
Examples
# In BGP instance view of BGP instance default, 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
BGP-VPN 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
Policy-based routing commands
Commands and descriptions for centralized devices apply to the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/ 810-LMS/810-LUS.
· MSR2600-6-X1/2600-10-X1.
· MSR 2630.
· MSR3600-28/3600-51.
· MSR3600-28-SI/3600-51-SI.
· MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC.
· MSR 3610/3620/3620-DP/3640/3660.
· MSR810-LM-GL/810-W-LM-GL/830-6EI-GL/830-10EI-GL/830-6HI-GL/830-10HI-GL/2600-6-X1-GL/3600-28-SI-GL.
Commands and descriptions for distributed devices apply to the following routers:
· MSR5620.
· MSR 5660.
· MSR 5680.
apply access-vpn vpn-instance
Use apply access-vpn vpn-instance to set VPN instances.
Use undo apply access-vpn vpn-instance to remove VPN instances.
Syntax
apply access-vpn vpn-instance vpn-instance-name&<1-n>
undo apply access-vpn vpn-instance [ vpn-instance-name&<1-n> ]
Default
No VPN instance is specified for a node.
Views
Policy node view
Predefined user roles
network-admin
Parameters
vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. The specified VPN must already exist.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify a maximum of n VPN instances for a node. The matching packets are forwarded according to the forwarding table of the first available VPN instance.
With a VPN instance specified, the undo apply access-vpn vpn-instance command removes the VPN instance.
Without any VPN instance specified, the undo apply access-vpn vpn-instance command removes all VPN instances.
Examples
# Set VPN 1 and VPN 2 for node 10. (VPN 1 and VPN 2 already exist.)
<Sysname> system-view
[Sysname] policy-based-route policy1 permit node 10
[Sysname-pbr-policy1-10] apply access-vpn vpn-instance vpn1 vpn2
Related commands
apply remark-vpn
apply continue
Use apply continue to compare packets with the next policy node upon failure on the current node.
Use undo apply continue to restore the default.
Syntax
apply continue
undo apply continue
Default
PBR does not compare packets with the next policy node upon failure on the current node.
Views
Policy node view
Predefined user roles
network-admin
Usage guidelines
This command takes effect only when the match mode of the node is permit.
This command applies when the following clauses are not configured or become invalid:
· apply access-vpn vpn-instance
· apply next-hop
· apply output-interface
· apply default-next-hop
· apply default-output-interface
For example, the command applies when the specified next hop is unreachable, the specified output interface is down, or the packets cannot be forwarded in the specified VPN instance.
Examples
# Compare with the next policy node upon failure on the current node.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply continue
apply default-next-hop
Use apply default-next-hop to set default next hops.
Use undo apply default-next-hop to remove default next hops.
Syntax
apply default-next-hop [ vpn-instance vpn-instance-name | inbound-vpn ] { ip-address [ direct ] [ track track-entry-number ] }&<1-n>
undo apply default-next-hop [ [ vpn-instance vpn-instance-name | inbound-vpn ] ip-address&<1-n> ]
Default
No default next hop is set.
Views
Policy node view
Predefined user roles
network-admin
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. The specified VPN must already exist.
inbound-vpn: Specifies the VPN instance where the inbound interface belongs.
ip-address: Specifies the IP address of the default next hop. If you do not specify the vpn-instance vpn-instance-name option or the inbound-vpn keyword, the default next hop belongs to the public network.
direct: Specifies a directly connected default next hop.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify multiple default next hops for backup or load sharing in one command line or by executing this command multiple times.
With a default next hop specified, the undo apply default-next-hop command removes the default next hop.
Without any default next hop specified, the undo apply default-next-hop command removes all default next hops.
Examples
# Set a directly-connected default next hop of 1.1.1.1.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply default-next-hop 1.1.1.1 direct
Related commands
apply loadshare
apply default-output-interface
Use apply default-output-interface to set default output interfaces.
Use undo apply default-output-interface to remove default output interfaces.
Syntax
apply default-output-interface { interface-type interface-number [ track track-entry-number ] }&<1-n>
undo apply default-output-interface [ { interface-type interface-number }&<1-n> ]
Default
No default output interface is set.
Views
Policy node view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify multiple default output interfaces for backup or load sharing in one command line or by executing this command multiple times.
The default output interface must be P2P type. Using a non-P2P default output interface can result in forwarding failures when the interface has multiple next hops. Non-P2P interfaces include broadcast and non-broadcast multi-access (NBMA) interfaces such as Ethernet and virtual-template interfaces. In NBMA networks, packets are sent in unicast.
With a default output interface specified, the undo apply default-output-interface command removes the default output interface.
Without any default output interface specified, the undo apply default-output-interface command removes all default output interfaces.
Examples
# Specify GigabitEthernet 1/0/1 as the default output interface for IP packets.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply default-output-interface gigabitethernet 1/0/1
Related commands
apply loadshare
apply ip-df
Use apply ip-df to set the Don't Fragment (DF) bit in the IP header of matching packets.
Use undo apply ip-df to restore the default.
Syntax
apply ip-df df-value
undo apply ip-df
Default
The DF bit is not set.
Views
Policy node view
Predefined user roles
network-admin
Parameters
df-value: Sets the DF bit in the IP header of matching packets. The value can be 0 or 1.
Usage guidelines
Setting the DF bit to 0 allows packet fragmentation.
Setting the DF bit to 1 prohibits packet fragmentation.
Examples
# Set the DF bit in the IP header of matching packets to 0.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply ip-df 0
apply loadshare
Use apply loadshare to enable load sharing among multiple next hops, output interfaces, default next hops, or default output interfaces.
Use undo apply loadshare to restore the default.
Syntax
apply loadshare { default-next-hop | default-output-interface | next-hop | output-interface }
undo apply loadshare { default-next-hop | default-output-interface | next-hop | output-interface }
Default
Multiple next hops, output interfaces, default next hops, or default output interfaces operate in primary/backup mode.
Views
Policy node view
Predefined user roles
network-admin
Parameters
default-next-hop: Enables load sharing among multiple default next hops.
default-output-interface: Enables load sharing among multiple default output interfaces.
next-hop: Enables load sharing among multiple next hops.
output-interface: Enables load sharing among multiple output interfaces.
Usage guidelines
Multiple next hops, output interfaces, default next hops, or default output interfaces operate in either primary/backup or load sharing mode. For example:
· Primary/backup mode—The first configured output interface is used. When the primary output interface fails, the first configured backup output interface takes over.
· Load sharing mode—Multiple output interfaces load share traffic on a per-packet basis in turn, according to the configuration order.
|
|
NOTE: Multiple next hops load share traffic according to their weights. By default, all next hops have the same weight and traffic is load balanced among them. |
Examples
# Enable load sharing among multiple next hops.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply next-hop 1.1.1.1 2.2.2.2
[Sysname-pbr-aa-11] apply loadshare next-hop
# Enable load sharing among multiple output interfaces.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply output-interface gigabitethernet 1/0/1 gigabitethernet 1/0/2
[Sysname-pbr-aa-11] apply loadshare output-interface
# Enable load sharing among multiple default next hops.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply default-next-hop 1.1.1.1 2.2.2.2
[Sysname-pbr-aa-11] apply loadshare default-next-hop
# Enable load sharing among multiple default output interfaces.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply default-output-interface gigabitethernet 1/0/1 gigabitethernet 1/0/2
[Sysname-pbr-aa-11] apply loadshare default-output-interface
Related commands
apply default-next-hop
apply default-output-interface
apply next-hop
apply output-interface
apply next-hop
Use apply next-hop to set next hops.
Use undo apply next-hop to remove next hops.
Syntax
apply next-hop [ vpn-instance vpn-instance-name| inbound-vpn ] { ip-address [ direct ] [ track track-entry-number ] [ weight weight-value ] }&<1-n>
undo apply next-hop [ [ vpn-instance vpn-instance-name | inbound-vpn ] ip-address&<1-n> ]
Default
No next hop is set.
Views
Policy node view
Predefined user roles
network-admin
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. The specified VPN must already exist.
inbound-vpn: Specifies the VPN instance where the inbound interface belongs.
ip-address: Specifies the IP address of the next hop. If you do not specify the vpn-instance vpn-instance-name option or the inbound-vpn keyword, the next hop belongs to the public network.
direct: Specifies that the next hop must be directly connected to take effect.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
weight weight-value: Specifies a load sharing weight for the next hop, in the range of 1 to 100. The default is 10. If you specify weights 1, 1, and 2 for three next hops, they share 1/4, 1/4, and 1/2 of the whole traffic, respectively.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify multiple next hops for backup or load sharing in one command line or by executing this command multiple times.
With a next hop specified, the undo apply next-hop command removes the next hop.
Without any next hop specified, the undo apply next-hop command removes all next hops.
Examples
# Set a directly-connected next hop of 1.1.1.1.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply next-hop 1.1.1.1 direct
apply loadshare
apply output-interface
Use apply output-interface to set output interfaces.
Use undo apply output-interface to remove output interfaces.
Syntax
apply output-interface { interface-type interface-number [ track track-entry-number ] }&<1-n>
undo apply output-interface [ { interface-type interface-number }&<1-n> ]
Default
No output interface is set.
Views
Policy node view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify multiple output interfaces for backup or load sharing in one command line or by executing this command multiple times.
The output interface must be P2P type. Using a non-P2P output interface can result in forwarding failures when the interface has multiple next hops. Non-P2P interfaces include broadcast and NBMA interfaces such as Ethernet and virtual-template interfaces.
With an output interface specified, the undo apply output-interface command removes the output interface.
Without any output interface specified, the undo apply output-interface command removes all output interfaces.
Examples
# Specify GigabitEthernet 1/0/1 as the output interface for IP packets.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply output-interface gigabitethernet 1/0/1
Related commands
apply loadshare
apply precedence
Use apply precedence to set a precedence for IP packets.
Use undo apply precedence to restore the default.
Syntax
apply precedence { type | value }
undo apply precedence
Default
No precedence is set for IP packets.
Views
Policy node view
Predefined user roles
network-admin
Parameters
type: Specifies the precedence type for IP packets.
value: Specifies the precedence for IP packets. Eight precedence values (0 to 7) are available. Each precedence value corresponds to a precedence type, as shown in Table 119. You can set either a precedence value or a precedence type for IP packets.
Table 119 IP precedences and corresponding types
|
Precedence value |
Precedence type |
|
0 |
routine |
|
1 |
priority |
|
2 |
immediate |
|
3 |
flash |
|
4 |
flash-override |
|
5 |
critical |
|
6 |
internet |
|
7 |
network |
Examples
# Set the precedence to 5 (critical) for IP packets.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply precedence critical
apply remark-vpn
Use apply remark-vpn to mark the VPN instance for matching packets.
Use undo apply remark-vpn to restore the default.
Syntax
apply remark-vpn
undo apply remark-vpn
Default
The VPN instance is not marked for matching packets.
Views
Policy node view
Predefined user roles
network-admin
Usage guidelines
The apply access-vpn vpn-instance command is used to forward matching packets in a specified VPN instance. To make the VPN instance known to the service modules, use the apply remark-vpn command to mark the VPN instance in the packets.
This command must be used together with the apply access-vpn vpn-instance command.
This command marks a VPN instance in a packet only when the packet is forwarded in the VPN instance specified by the apply access-vpn vpn-instance command.
Examples
# Mark VPN instance vpn1 for packets that match ACL 3000.
<Sysname> system-view
[Sysname] policy-based-route aaa permit node 10
[Sysname-pbr-aaa-10] if-match acl 3000
[Sysname-pbr-aaa-10] apply access-vpn vpn-instance vpn1
[Sysname-pbr-aaa-10] apply remark-vpn
Related commands
apply access-vpn vpn-instance
display ip policy-based-route
Use display ip policy-based-route to display PBR policy information.
Syntax
display ip policy-based-route [ policy policy-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
policy policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. If you do not specify a policy, this command displays information for all PBR policies.
Examples
# Display all policy information.
<Sysname> display ip policy-based-route
Policy name: aaa
node 1 permit:
if-match acl 2000
apply next-hop 1.1.1.1
Table 120 Command output
|
Field |
Description |
|
node 1 permit |
The match mode of Node 1 is permit. |
|
if-match acl |
Compares packets with the ACL. |
|
apply next-hop |
Specifies a next hop for permitted packets. |
Related commands
policy-based-route
display ip policy-based-route interface
Use display ip policy-based-route interface to display interface PBR configuration and statistics.
Syntax
Centralized devices in standalone mode:
display ip policy-based-route interface interface-type interface-number
Distributed devices in standalone mode/centralized devices in IRF mode:
display ip policy-based-route interface interface-type interface-number [ slot slot-number ]
Distributed devices in IRF mode:
display ip policy-based-route interface interface-type interface-number [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays interface PBR configuration and statistics for the active MPU. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays interface PBR configuration and statistics for the master device. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays interface PBR configuration and statistics for the global active MPU. (Distributed devices in IRF mode.)
Examples
# Display PBR configuration and statistics on GigabitEthernet 1/0/1.
<Sysname> display ip policy-based-route interface gigabitethernet 1/0/1
Policy based routing information for interface GigabitEthernet1/0/1(failed):
Policy name: aaa
node 0 deny:
Matched: 0
node 1 permit:
if-match acl 3999
Matched: 0
node 2 permit:
if-match acl 2000
apply next-hop 2.2.2.2
Matched: 0
node 5 permit:
if-match acl 3101
apply next-hop 1.1.1.1
apply output-interface GigabitEthernet1/0/2 track 1 (down)
apply output-interface GigabitEthernet1/0/3 track 2 (inactive)
Matched: 0
Total matched: 0
<Sysname> display ip policy-based-route interface gigabitethernet 1/0/1
Policy based routing information for interface GigabitEthernet1/0/1:
Policy name: aaa
node 0 deny(not support):
Matched: 0
node 1 permit:
if-match acl 3999
Matched: 0
node 2 permit(no resource):
if-match acl 2000
apply next-hop 2.2.2.2
apply output-interface GigabitEthernet1/0/2 track 1 (down)
apply output-interface GigabitEthernet1/0/3 track 2 (inactive)
Matched: 0
node 5 permit:
if-match acl 3101
apply next-hop 1.1.1.1
Matched: 0 (no statistics resource)
Total matched: 0
Table 121 Command output
|
Field |
Description |
|
Policy based routing information for interface GigabitEthernet1/0/1(failed) |
PBR configuration and statistics on GigabitEthernet 1/0/1. This field displays failed in brackets if none of the nodes in the policy has been successfully issued to the driver. NOTE: The failed status is available on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command. · For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces. · For a physical interface, specify its slot number. |
|
node 0 deny(not support) node 2 permit(no resource) |
Match mode of the node, permit or deny. If a node fails to be issued to the driver, the command displays the cause in brackets, which include: · not support—The device does not support the match criteria configured on the node. · no resource—No sufficient resources (for example, ACLs) are available for the node. NOTE: The cause is available only on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command. · For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces. · For a physical interface, specify its slot number. |
|
if-match acl |
Compares packets with the ACL. |
|
apply next-hop |
Specifies a next hop for permitted packets. |
|
apply output-interface GigabitEthernet1/0/2 track 1 (down) |
Specifies an output interface for permitted packets. The interface status includes the following: · up—The interface is up. · down—The interface is down at network layer. · inactive—The card that hosts the interface is not in position. |
|
Matched: 0 (no statistics resource) |
Number of successful matches on the node. If the device does not have sufficient resources to count matches, this field displays no statistics resource in brackets. NOTE: The statistics collection failure cause is available only on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command. · For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces. · For a physical interface, specify its slot number. |
|
Total matched |
Total number of successful matches on all nodes. |
Related commands
reset ip policy-based-route statistics
display ip policy-based-route local
Use display ip policy-based-route local to display local PBR configuration and statistics.
Syntax
Centralized devices in standalone mode:
display ip policy-based-route local
Distributed devices in standalone mode/centralized devices in IRF mode:
display ip policy-based-route local [ slot slot-number ]
Distributed devices in IRF mode:
display ip policy-based-route local [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays local PBR configuration and statistics for the active MPU. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays local PBR configuration and statistics for the master device. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays local PBR configuration and statistics for the global active MPU. (Distributed devices in IRF mode.)
Examples
# Display local PBR configuration and statistics.
<Sysname> display ip policy-based-route local
Policy based routing information for local:
Policy name: aaa
node 0 deny:
Matched: 0
node 1 permit:
if-match acl 3999
Matched: 0
node 2 permit:
if-match acl 2000
apply next-hop 2.2.2.2
Matched: 0
node 5 permit:
if-match acl 3101
apply next-hop 1.1.1.1
Matched: 0
Total matched: 0
Table 122 Command output
|
Field |
Description |
|
Policy based routing information for local |
Local PBR configuration and statistics. |
|
node 0 deny/node 2 permit |
Match mode of the node: permit or deny. |
|
if-match acl |
Compares packets with the ACL. |
|
apply next-hop |
Specifies a next hop for permitted packets. |
|
Matched: 0 |
Number of successful matches on the node. |
|
Total matched |
Total number of successful matches on all nodes. |
Related commands
reset ip policy-based-route statistics
display ip policy-based-route setup
Use display ip policy-based-route setup to display PBR configuration.
Syntax
display ip policy-based-route setup
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display PBR configuration.
<Sysname> display ip policy-based-route setup
Policy Name Interface Name
pr01 GigabitEthernet 1/0/1
Table 123 Command output
|
Field |
Description |
|
Interface Name |
Interface where the policy is applied. |
Related commands
ip policy-based-route
if-match acl
Use if-match acl to set an ACL match criterion.
Use undo if-match acl to restore the default.
Syntax
if-match acl { acl-number | name acl-name }
undo if-match acl
Default
No ACL match criterion is set.
Views
Policy node view
Predefined user roles
network-admin
Parameters
acl-number: Specifies an ACL by its number in the range of 2000 to 2999 for a basic ACL, and in the range of 3000 to 3999 for an advanced ACL.
name acl-name: Specifies a basic or advanced ACL by its name, a case-insensitive string of 1 to 63 characters starting with letter a to z or A to Z. The ACL name cannot be all.
Examples
# Configure Node 11 of policy aa to permit the packets matching ACL 2011.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] if-match acl 2011
# Configure Node 11 of policy aa to permit the packets matching ACL aaa.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] if-match acl name aaa
if-match app-group
Use if-match app-group to set application group match criteria.
Use undo if-match app-group to delete application group match criteria.
Syntax
if-match app-group app-group-name&<1-n>
undo if-match app-group [ app-group-name&<1-n> ]
Default
No application group match criterion is set.
Views
Policy node view
Predefined user roles
network-admin
Parameters
app-group-name: Specifies an application group by its name, a case-insensitive string of 1 to 63 characters. The group name can include letters, digits, underscores (_), and hyphens (-). The application group name cannot be Invalid, other, or any application group name predefined by the system.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 6.
Usage guidelines
Application group match criteria apply only to interface PBR.
If you specify an application group, the undo if-match app-group command deletes the application group match criterion.
If you do not specify an application group, the undo if-match app-group command deletes all application group match criteria.
Examples
# Specify the application group test as a match criterion.
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] if-match app-group test
if-match object-group
Use if-match object-group to set service object group match criteria.
Use undo if-match object-group to delete service object group match criteria.
Syntax
if-match object-group service object-group-name&<1-n>
undo if-match object-group service [ object-group-name&<1-n> ]
Default
No service object group match criterion is set.
Views
Policy node view
Predefined user roles
network-admin
Parameters
service object-group-name: Specifies a service object group by its name, a case-insensitive string of 1 to 31 characters. The group name can include letters, digits, underscores (_), and hyphens (-).
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 6.
Usage guidelines
If you specify a service object group, the undo if-match object-group command deletes the service object group match criterion.
If you do not specify a service object group, the undo if-match object-group command deletes all service object group match criteria.
Examples
# Specify the service object group test as a match criterion.
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] if-match object-group service test
if-match packet-length
Use if-match packet-length to set a packet length match criterion.
Use undo if-match packet-length to delete the match criterion.
Syntax
if-match packet-length min-len max-len
undo if-match packet-length
Default
No packet length match criterion is set.
Views
Policy node view
Predefined user roles
network-admin
Parameters
min-len: Specifies the minimum IP packet length in the range of 1 to 65535 bytes.
max-len: Specifies the maximum IP packet length in the range of 1 to 65535 bytes. The maximum length must be no less than the minimum length.
Usage guidelines
Use this command to set a criterion to match the total length of data packets.
The packet length range includes boundary values. For example, if you set the min-len and max-len arguments to 100 and 200, respectively, packets with lengths of 100 bytes and 200 bytes are also matched.
Examples
# Match packets with a length from 100 to 200 bytes.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] if-match packet-length 100 200
ip local policy-based-route
Use ip local policy-based-route to configure local PBR based on a policy.
Use undo ip local policy-based-route to restore the default.
Syntax
ip local policy-based-route policy-name
undo ip local policy-based-route
Default
No policy is referenced for local PBR.
Views
System view
Predefined user roles
network-admin
Parameters
policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. The specified policy must already exist.
Usage guidelines
You can apply only one policy locally. Before you apply a new policy, you must first remove the current policy.
Local PBR is used to route locally generated packets except the packets destined for the sender. This feature might affect local services. Do not configure local PBR unless doing so is required.
Examples
# Configure local PBR based on policy aaa.
<Sysname> system-view
[Sysname] ip local policy-based-route aaa
Related commands
display ip policy-based-route setup
policy-based-route
ip policy-based-route
Use ip policy-based-route to configure interface PBR by applying a policy to an interface.
Use undo ip policy-based-route to restore the default.
Syntax
ip policy-based-route policy-name
undo ip policy-based-route
Default
No policy is applied to an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. The specified policy must already exist.
Usage guidelines
You can apply only one policy to an interface. Before you apply a new policy, you must first remove the current policy from the interface.
Examples
# Apply policy aaa to GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ip policy-based-route aaa
Related commands
display ip policy-based-route setup
policy-based-route
policy-based-route
Use policy-based-route to create a policy node and enter its view, or enter the view of an existing policy node.
Use undo policy-based-route to delete a policy or policy node.
Syntax
policy-based-route policy-name [ deny | permit ] node node-number
undo policy-based-route policy-name [ deny | node node-number | permit ]
Default
No policy nodes exist.
Views
System view
Predefined user roles
network-admin
Parameters
policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters.
deny: Specifies the match mode for the policy node as deny.
permit: Specifies the match mode for the policy node as permit (default mode).
node node-number: Specifies a policy node by its number. A smaller number has a higher priority. The value range for the node-number argument is 0 to 65535.
Usage guidelines
A policy that has been applied to an interface or locally cannot be deleted. To delete it, you must first cancel the application.
· If a policy node is specified, the undo policy-based-route command deletes the specified policy node.
· If a match mode is specified, the command deletes all nodes configured with the match mode.
· If no policy node or match mode is specified, the command deletes the whole policy.
Examples
# Create permit-mode of Node 10 for policy policy1 and enter its view.
<Sysname> system-view
[Sysname] policy-based-route policy1 permit node 10
[Sysname-pbr-policy1-10]
Related commands
display ip policy-based-route
reset ip policy-based-route statistics
Use reset ip policy-based-route statistics to clear PBR statistics.
Syntax
reset ip policy-based-route statistics [ policy policy-name ]
Views
User view
Predefined user roles
network-admin
Parameters
policy policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. If you do not specify a policy, this command clears PBR statistics for all policies.
Examples
# Clear all PBR statistics.
<Sysname> reset ip policy-based-route statistics
Related commands
display ip policy-based-route interface
display ip policy-based-route local
IPv6 static routing commands
delete ipv6 static-routes all
Use delete ipv6 static-routes all to delete all IPv6 static routes.
Syntax
delete ipv6 [ vpn-instance vpn-instance-name ] static-routes all
Views
System view
Predefined user roles
network-admin
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command deletes all IPv6 static routes for the public network.
Usage guidelines
When you use this command, the system will prompt you to confirm the operation before deleting all the IPv6 static routes.
Examples
# Delete all IPv6 static routes.
<Sysname> system-view
[Sysname] delete ipv6 static-routes all
This will erase all IPv6 static routes and their configurations, you must reconfigure all static routes.
Are you sure?[Y/N]:y
Related commands
ipv6 route-static
display ipv6 route-static nib
Use display ipv6 route-static nib to display IPv6 static route next hop information.
Syntax
display ipv6 route-static nib [ nib-id ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
nib-id: Specifies a NIB by its ID, a hexadecimal string in the range of 1 to ffffffff.
verbose: Displays detailed IPv6 static route next hop information. If you do not specify this keyword, the command displays brief IPv6 static route next hop information.
Examples
# Display brief IPv6 static route next hop information.
<Sysname> display ipv6 route-static nib
Total number of nexthop(s): 35
NibID: 0x21000000 Sequence: 0
Type: 0x41 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 2::3
IFIndex: 0x0 LocalAddr: ::
TopoNthp: Invalid
NibID: 0x21000001 Sequence: 1
Type: 0x41 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 3::4
IFIndex: 0x0 LocalAddr: ::
TopoNthp: Invalid
...
Table 124 Command output
|
Field |
Description |
|
NibID |
ID of the NIB. |
|
Sequence |
Sequence number of the NIB. |
|
Type |
Type of the NIB. |
|
Flushed |
Indicates whether the route with the NIB has been flushed to the FIB. |
|
UserKey0 |
Reserved data 1. |
|
UserKey1 |
Reserved data 2. |
|
VrfNthp |
Index of the VPN instance to which the next hop belongs. This field displays 0 if the next hop is on an IPv6 network. |
|
Nexthop |
Next hop address. |
|
IFIndex |
Interface index |
|
LocalAddr |
Local interface address. |
|
Index of the topology that contains the next hop. This field displays Invalid if the next hop is on an IPv6 network, because the router does not support multiple topologies. |
# Display detailed IPv6 static route next hop information.
<Sysname> display ipv6 route-static nib verbose
Total number of nexthop(s): 35
NibID: 0x21000000 Sequence: 0
Type: 0x41 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 2::3
IFIndex: 0x0 LocalAddr: ::
TopoNthp: Invalid
RefCnt: 1 FlushRefCnt: 0
Flag: 0x12 Version: 1
1 nexthop(s):
PrefixIndex: 0 OrigNexthop: 2::3
RelyDepth: 2 RealNexthop: ::
Interface: NULL0 LocalAddr: ::
TunnelCnt: 0 Vrf: default-vrf
TunnelID: N/A Topology:
Weight: 0
NibID: 0x21000001 Sequence: 1
Type: 0x41 Flushed: Yes
UserKey0: 0x0 VrfNthp: 0
UserKey1: 0x0 Nexthop: 3::4
IFIndex: 0x0 LocalAddr: ::
TopoNthp: Invalid
RefCnt: 1 FlushRefCnt: 0
Flag: 0x12 Version: 1
1 nexthop(s):
PrefixIndex: 0 OrigNexthop: 3::4
RelyDepth: 1 RealNexthop: ::
Interface: GE1/0/1 LocalAddr: ::
TunnelCnt: 0 Vrf: default-vrf
TunnelID: N/A Topology:
Weight: 0
...
Table 125 Command output
|
Field |
Description |
|
x nexthop(s) |
Number of next hops. |
|
Tnl-Policy |
Tunnel policy. |
|
PrefixIndex |
Prefix index of the next hop for an ECMP route. |
|
Vrf |
VPN instance name. For an IPv6 network, this field displays default-vrf. |
|
OrigNexthop |
Original next hop. |
|
RealNexthop |
Real next hop. |
|
Interface |
Output interface. |
|
localAddr |
Local interface address. |
|
RelyDepth |
Recursion depth. |
|
TunnelCnt |
Number of tunnels after route recursion. |
|
TunnelID |
ID of the tunnel after route recursion. |
|
Topology name. This field is blank for IPv6, because IPv6 does not support multiple topologies. |
|
|
Weight |
Weight of the ECMP route. The route is not an ECMP route if its weight is 0. |
|
RefCnt |
Reference count of the next hop. |
|
FlushRefCnt |
Reference count of the next hop that is flushed to the FIB. |
|
Flag |
Flag of the next hop. |
|
Version |
Version of the next hop. |
display ipv6 route-static routing-table
Use display ipv6 route-static routing-table to display IPv6 static routing table information.
Syntax
display ipv6 route-static routing-table [ vpn-instance vpn-instance-name ] [ ipv6-address prefix-length ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays IPv6 static routing table information for the public network.
ipv6-address: Specifies the destination IPv6 address.
prefix-length: Specifies the prefix length in the range of 0 to 128.
Examples
# Display IPv6 static routing table information.
<Sysname> display ipv6 route-static routing-table
Total number of routes: 5
Status: * - valid
*Destination: 1::1/128
NibID: 0x21000000 NextHop: 2::2
MainNibID: N/A BkNextHop: N/A
BkNibID: N/A Interface: GigabitEthernet1/0/1
TableID: 0xa BkInterface: N/A
Flag: 0x80d0a BfdSrcIp: N/A
DbIndex: 0x3 BfdIfIndex: 0x0
Type: Normal BfdVrfIndex: 0
TrackIndex: 0xffffffff Label: NULL
Preference: 60 vrfIndexDst: 0
BfdMode: N/A vrfIndexNH: 0
Permanent: 0 Tag: 0
*Destination: 1::1234/128
NibID: 0x21000000 NextHop: 2::2
MainNibID: N/A BkNextHop: N/A
BkNibID: N/A Interface: NULL0
TableID: 0xa BkInterface: N/A
Flag: 0x80d0a BfdSrcIp: N/A
DbIndex: 0x1 BfdIfIndex: 0x0
Type: Normal BfdVrfIndex: 0
TrackIndex: 0xffffffff Label: NULL
Preference: 60 vrfIndexDst: 0
BfdMode: N/A vrfIndexNH: 0
Permanent: 0 Tag: 0
...
Table 126 Command output
|
Field |
Description |
|
Destination |
Destination address/prefix. |
|
NibID |
ID of the NIB. |
|
MainNibID |
ID of the primary next hop for static route FRR. |
|
BkNibID |
ID of the backup next hop for static route FRR. |
|
NextHop |
Next hop address. |
|
BkNextHop |
Backup next hop address. |
|
Interface |
Output interface of the route. |
|
BkInterface |
Backup output interface. |
|
TableID |
ID of the table to which the route belongs. |
|
DbIndex |
Index of the database to which the route belongs. |
|
Type |
Route type: · Normal. · DHCP. · NAT. |
|
BfdSrcIp |
Source IPv6 address of the indirect BFD session. |
|
BfdIfIndex |
Index of the interface where BFD is enabled. |
|
BfdVrfIndex |
Index of the VPN instance where BFD is enabled. This field displays 0 if BFD is enabled for an IPv6 network. |
|
BfdMode |
BFD session mode: · N/A—No BFD session is configured. · Ctrl—Control packet mode. · Echo—Echo packet mode. |
|
TrackIndex |
NQA Track index. |
|
vrfIndexDst |
Index of the VPN instance to which the destination belongs. For an IPv6 network, this field displays 0. |
|
vrfIndexNH |
Index of the VPN instance to which the next hop belongs. For an IPv6 network, this field displays 0. |
|
Permanent |
Permanent static route flag. 1 indicates a permanent static route. |
ipv6 route-static
Use ipv6 route-static to configure an IPv6 static route.
Use undo ipv6 route-static to remove an IPv6 static route.
Syntax
ipv6 route-static ipv6-address prefix-length { interface-type interface-number [ next-hop-address ] [ bfd { control-packet | echo-packet } [ bfd-source ipv6-address ] | permanent ] | [ vpn-instance d-vpn-instance-name ] next-hop-address [ bfd control-packet bfd-source ipv6-address | permanent ] } [ preference preference ] [ tag tag-value ] [ description text ]
undo ipv6 route-static ipv6-address prefix-length [ interface-type interface-number [ next-hop-address ] [ vpn-instance d-vpn-instance-name ] next-hop-address ] [ preference preference ]
ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length { interface-type interface-number [ next-hop-address ] [ bfd { control-packet | echo-packet } [ bfd-source ipv6-address ] | permanent ] | next-hop-address [ public ] [ bfd control-packet bfd-source ipv6-address | permanent ] | vpn-instance d-vpn-instance-name next-hop-address [ bfd control-packet bfd-source ipv6-address | permanent ] } [ preference preference ] [ tag tag-value ] [ description text ]
undo ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length [ interface-type interface-number [ next-hop-address ] | next-hop-address [ public ] | vpn-instance d-vpn-instance-name next-hop-address ] [ preference preference ]
Default
No IPv6 static route is configured.
Views
System view
Predefined user roles
network-admin
Parameters
ipv6-address prefix-length: Specifies the IPv6 address and prefix length.
interface-type interface-number: Specifies an output interface by its type and number. If the output interface is an NBMA interface or broadcast interface and not a point-to-point (P2P) interface, the next hop address must be specified.
next-hop-address: Specifies the next hop IPv6 address.
bfd: Enables BFD to detect reachability of the static route's next hop.
control-packet: Specifies the BFD control mode.
bfd-source ipv6-address: Specifies the source IPv6 address of BFD packets.
echo-packet: Specifies the BFD echo mode.
permanent: Specifies the IPv6 route as a permanent IPv6 static route. If the output interface is down, the permanent IPv6 static route is still active.
public: Indicates the next hop is on the public network.
vpn-instance d-vpn-instance-name: Specifies a destination MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If a destination VPN is specified, packets will search for the output interface based on the specified next hop (IPv6 address) for the static route.
preference preference: Specifies a preference for IPv6 static routes, in the range of 1 to 255. The default is 60.
tag tag-value: Sets a tag for marking the static route, in the range of 1 to 4294967295. The default is 0. Tags of routes are used for route control in routing policies. For more information about routing policies, see Layer 3—IP Routing Configuration Guide.
description text: Configures a description for the IPv6 static route, which consists of 1 to 60 characters, including special characters such as the space, but excluding the question mark (?).
vpn-instance s-vpn-instance-name: Specifies a source MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. Each VPN has its own routing table, and the configured static route is installed in the routing tables of the specified VPNs.
Usage guidelines
An IPv6 static route that has the destination address configured as ::/0 (a prefix length of 0) is the default IPv6 route. If the destination address of an IPv6 packet does not match any entry in the routing table, this default route is used to forward the packet.
Follow these guidelines to configure the output interface, next hop address, or both for a static route:
· If the output interface is a broadcast interface or an NBMA interface, the next hop address must be specified.
· If the output interface is a P2P interface, you can specify only the output interface. You do not need to change the configuration of the route even if the peer address is changed.
Follow these guidelines when you configure BFD for IPv6 static routes:
· If you specify the source IPv6 address of BFD packets, you must specify the IPv6 address as the next hop IPv6 address on the peer device.
· If you specify a non-P2P output interface and a direct next hop, specify the bfd-source ipv6-address option as a best practice. Make sure the source IPv6 address of BFD packets meets the following requirements:
¡ The address is the same as the IPv6 address of the output interface.
¡ The address is on the same network segment as the next hop IPv6 address of the same type.
For example, if the next hop IPv6 address is a link-local address, the source IPv6 address of BFD packets must also be a link-local address.
Follow these guidelines when you configure a static route:
· Enabling BFD for a flapping route could worsen the route flapping situation. Therefore, use it with caution. For more information about BFD, see High Availability Configuration Guide.
· The next hop IPv6 address of echo packets must be a global unicast address.
· Do not specify the permanent keyword together with the bfd or track keyword.
Examples
# Configure an IPv6 static route, with the destination address 1:1:2::/64 and next hop 1:1:3::1.
<Sysname> system-view
[Sysname] ipv6 route-static 1:1:2:: 64 1:1:3::1
Related commands
display ipv6 routing-table protocol
ipv6 route-static default-preference
Use ipv6 route-static default-preference to set a default preference for IPv6 static routes.
Use undo ipv6 route-static default-preference to restore the default.
Syntax
ipv6 route-static default-preference default-preference
undo ipv6 route-static default-preference
Default
The default preference of IPv6 static routes is 60.
Views
System view
Predefined user roles
network-admin
Parameters
default-preference: Specifies a default preference for IPv6 static routes, in the range of 1 to 255.
Usage guidelines
If no preference is specified for an IPv6 static route, the default preference applies.
When the default preference is reconfigured, it applies only to newly added IPv6 static routes.
Examples
# Set a default preference of 120 for IPv6 static routes.
[Sysname] ipv6 route-static default-preference 120
Related commands
display ipv6 routing-table protocol
RIPng commands
checkzero
Use checkzero to enable zero field check on RIPng packets.
Use undo checkzero to disable zero field check.
Syntax
checkzero
undo checkzero
Default
Zero field check is enabled.
Views
RIPng view
Predefined user roles
network-admin
Usage guidelines
Some fields in RIPng packet headers must be zero. These fields are called zero fields. You can enable zero field check on incoming RIPng packets. If a zero field of a packet contains a non-zero value, RIPng discards the packet.
Examples
# Disable zero field check on RIPng packets for RIPng 100.
<Sysname> system-view
[Sysname] ripng 100
[Sysname-ripng-100] undo checkzero
default cost
Use default cost to configure a default metric for redistributed routes.
Use undo default cost to restore the default.
Syntax
default cost cost-value
undo default cost
Default
The default metric of redistributed routes is 0.
Views
RIPng view
Predefined user roles
network-admin
Parameters
cost-value: Specifies a default metric for redistributed routes, in the range of 0 to 16.
Usage guidelines
When you use the import-route command to redistribute routes from another routing protocol without specifying a metric, the metric specified by the default cost command applies.
Examples
# Configure a default metric of 2 for redistributed routes.
<Sysname> system-view
[Sysname] ripng 100
[Sysname-ripng-100] default cost 2
Related commands
import-route
display ripng
Use display ripng to display state and configuration information for a RIPng process.
Syntax
display ripng [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIPng process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays information about all RIPng processes.
Examples
# Display state and configuration information for all configured RIPng processes.
<Sysname> display ripng
Public VPN-instance name:
RIPng process: 1
Preference: 100
Routing policy: abc
Fast-reroute:
Routing policy: abc
Checkzero: Enabled
Default cost: 0
Maximum number of load balanced routes: 6
Update time : 30 secs Timeout time : 180 secs
Suppress time : 120 secs Garbage-collect time : 120 secs
Number of periodic updates sent: 256
Number of trigger updates sent: 1
Table 127 Command output
|
Field |
Description |
|
Public VPN-instance name/Private VPN-instance name |
Public network or VPN where the RIPng process runs. |
|
RIPng process |
RIPng process ID. |
|
Preference |
RIPng preference. |
|
Checkzero |
Indicates whether zero field check for RIPng packet headers is enabled: Enabled or Disabled. |
|
Default Cost |
Default metric of redistributed routes. |
|
Fast-reroute |
RIPng FRR. |
|
Maximum number of balanced paths |
Maximum number of load-balanced routes. |
|
Update time |
RIPng update interval, in seconds. |
|
Timeout time |
RIPng timeout interval, in seconds. |
|
Suppress time |
RIPng suppress interval, in seconds. |
|
Garbage-Collect time |
RIPng garbage collection interval, in seconds. |
display ripng database
Use display ripng database to display all active routes in the advertising database for a RIPng process. RIPng advertises active routes in RIPng routing updates.
Syntax
display ripng process-id database [ ipv6-address prefix-length ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIPng process by its ID in the range of 1 to 65535.
ipv6-address prefix-length: Specifies an IPv6 address. The ipv6-address argument specifies an IPv6 address. The prefix-length argument specifies a prefix length in the range of 0 to 128.
Examples
# Display active routes for RIPng process 1.
<Sysname> display ripng 1 database
1::/64,
cost 0, RIPng-interface
10::/32,
cost 0, imported
2::2/128,
via FE80::20C:29FF:FE7A:E3E4, cost 1
Table 128 Command output
|
Field |
Description |
|
cost |
Route metric value. |
|
imported |
Indicates the route is redistributed from another routing protocol. |
|
RIPng-interface |
Route learned from the interface. |
|
via |
Next hop IPv6 address. |
display ripng graceful-restart
Use display ripng graceful-restart to display GR information.
Syntax
display ripng [ process-id ] graceful-restart
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIPng process by its ID in the range of 1 to 65535.
Examples
# Display GR information for RIPng process 1.
<Sysname> display ripng 1 graceful-restart
RIPng process: 1
Graceful Restart capability : Enabled
Current GR state : Normal
Graceful Restart period : 60 seconds
Graceful Restart remaining time: 0 seconds
Table 129 Command output
|
Field |
Description |
|
Indicates whether GR is enabled: Enabled or Disabled. |
|
|
Current GR state |
GR state: · Under GR—GR is in process. · Normal—GR is not in progress or has completed. |
display ripng interface
Use display ripng interface to display interface information for a RIPng process.
Syntax
display ripng process-id interface [ interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIPng process by its ID in the range of 1 to 65535.
interface-type interface-number: Specifies an interface by its type and number. If you do not specify this argument, the command displays information about all interfaces for the RIPng process.
Examples
# Display interface information for RIPng process 1.
<Sysname> display ripng 1 interface
Total: 1
Interface: GigabitEthernet1/0/2
Link-local address: FE80::20C:29FF:FEC8:B4DD
Split-horizon: On Poison-reverse: Off
MetricIn: 0 MetricOut: 1
Default route: Off
Primary path detection mode: BFD echo
Summary address:
1::/16
Table 130 Command output
|
Field |
Description |
|
Total |
Number of interfaces running RIPng. |
|
Interface |
Name of an interface running RIPng. |
|
Link Local Address |
Link-local address of an interface running RIPng. |
|
Split-horizon |
Indicates whether split horizon is enabled: · On—Enabled. · Off—Disabled. |
|
Poison-reverse |
Indicates whether poison reverse is enabled: · On—Enabled. · Off—Disabled. |
|
MetricIn/MetricOut |
Additional metric to incoming and outgoing routes. |
|
Default route |
· Only—The interface advertises only a default route. · Originate—The interface advertises a default route and other RIPng routes. · Off—In this state, the interface does not advertise a default route. · In garbage-collection status—In this state, the interface advertises a default route with a metric of 16. |
|
Default route cost |
Cost of the default route. |
display ripng neighbor
Use display ripng neighbor to display neighbor information for a RIPng process.
Syntax
display ripng process-id neighbor [ interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIPng process by its ID in the range of 1 to 65535.
interface-type interface-number: Specifies an interface by its type and number. If you do not specify this argument, the command displays information about all neighbors for the RIPng process.
Examples
# Display neighbor information for RIPng process 1.
<Sysname> display ripng 1 neighbor
Neighbor Address: FE80::230:FF:FE00:0
Interface : GigabitEthernet1/0/1
Version : RIPng version 1 Last update: 00h00m27s
Bad packets: 0 Bad routes : 0
Table 131 Command output
|
Field |
Description |
|
Neighbor Address |
Link-local address of a neighbor interface. |
|
Interface |
Name of a neighbor interface. |
|
Version of RIPng that the neighbor runs. |
|
|
Time elapsed since the most recent update. |
display ripng non-stop-routing
Use display ripng non-stop-routing to display RIPng NSR information.
Syntax
display ripng [ process-id ] non-stop-routing
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIPng process by its ID in the range of 1 to 65535.
Examples
# Display NSR information for RIPng process 1.
<Sysname> display ripng 1 non-stop-routing
RIPng process: 1
Nonstop Routing capability: Enabled
Current NSR state : Finish
Table 132 Command output
|
Field |
Description |
|
Indicates whether NSR is enabled: Enabled or Disabled. |
|
|
NSR state: · Initialization—Initialization state. · Smooth—Upgrading data. · Advertising—Advertising routes. · Redistribution—Redistributing routes. · Finish—Finished. |
display ripng route
Use display ripng route to display all RIPng routes for a RIPng process.
Syntax
display ripng process-id route [ ipv6-address prefix-length [ verbose ] | peer ipv6-address | statistics ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIPng process by its ID in the range of 1 to 65535.
ipv6-address prefix-length: Specifies an IPv6 address. The ipv6-address argument specifies an IPv6 address. The prefix-length argument specifies a prefix length in the range of 0 to 128.
verbose: Displays all routing information for the specified destination IPv6 address. If you do not specify this keyword, the command displays only optimal RIPng routes with the specified destination IPv6 address.
peer ipv6-address: Specifies a neighbor by its IPv6 address.
statistics: Displays routing information statistics, including total number of routes and the number of routes learned from each neighbor.
Examples
# Display routing information for RIPng process 1.
<Sysname> display ripng 1 route
Route Flags: A - Aging, S - Suppressed, G - Garbage-collect, D – Direct
O - Optimal, F - Flush to RIB
----------------------------------------------------------------
Peer FE80::20C:29FF:FED4:7171 on GigabitEthernet1/0/2
Destination 4::4/128,
via FE80::20C:29FF:FED4:7171, cost 1, tag 0, AOF, 5 secs
Local route
Destination 3::3/128,
via ::, cost 0, tag 0, DOF
Destination 6::/64,
via ::, cost 0, tag 0, DOF
Table 133 Command output
|
Field |
Description |
|
A–Aging |
The route is in aging state. |
|
S–Suppressed |
The route is in suppressed state. |
|
G–Garbage-collect |
The route is in Garbage-collect state. |
|
D–Direct |
The route is a direct route. |
|
Local route |
The route is a locally generated direct route. |
|
O - Optimal |
The route is an optimal route. |
|
F - Flush to RIB |
The route has been flushed to the RIB. |
|
Peer |
Neighbor connected to the interface. |
|
Destination |
IPv6 destination address. |
|
via |
Next hop IPv6 address. |
|
cost |
Routing metric value. |
|
tag |
Route tag. |
|
secs |
Time a route entry has stayed in the current state. |
# Display routing information statistics for RIPng process 1.
<Sysname> display ripng 1 route statistics
Peer Optimal/Aging Garbage
FE80::20C:29FF:FED4:7171 1/2 0
Local 2/0 0
total 3/2 0
Table 134 Command output
|
Field |
Description |
|
Peer |
IPv6 address of the neighbor. |
|
Optimal |
Number of optimal routes. |
|
Aging |
Number of routes in aging state. |
|
Garbage |
Number of routes in Garbage-collection state. |
|
Local |
Total number of locally generated direct route. |
|
total |
Total number of routes learned from RIPng neighbors. |
enable ipsec-profile
Use enable ipsec-profile to apply an IPsec profile to a RIPng process.
Use undo enable ipsec-profile to remove the IPsec profile from the RIPng process.
Syntax
enable ipsec-profile profile-name
undo enable ipsec-profile
Default
No IPsec profile is applied to a RIPng process.
Views
RIPng view
Predefined user roles
network-admin
Parameters
profile-name: Specifies an IPsec profile by its name, a case-insensitive string of 1 to 63 characters.
Usage guidelines
To configure an IPsec profile, see IPsec in Security Configuration Guide.
Examples
# Apply IPsec profile profile001 to RIPng process 1.
<Sysname> system-view
[Sysname] ripng 1
[Sysname-ripng-1] enable ipsec-profile profile001
fast-reroute
Use fast-reroute to configure RIPng FRR.
Use undo fast-reroute to disable RIPng FRR.
Syntax
fast-reroute route-policy route-policy-name
undo fast-reroute
Default
RIPng FRR is disabled.
Views
RIPng view
Predefined user roles
network-admin
Parameters
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
RIPng FRR is available only when the state of primary link (with Layer 3 interfaces in up state) changes from bidirectional to unidirectional or down.
RIPng FRR is effective only for RIPng routes that are learned from directly connected neighbors.
Equal-cost routes do not support RIPng FRR.
Examples
# Enable RIPng FRR and use routing policy frr to specify a backup next hop.
<Sysname> system-view
[Sysname] ipv6 prefix-list abc index 10 permit 100:: 64
[Sysname] route-policy frr permit node 10
[Sysname-route-policy-frr-10] if-match ipv6 address prefix-list abc
[Sysname-route-policy-frr-10] apply ipv6 fast-reroute backup-interface gigabitethernet 1/0/1 backup-nexthop FE80::8
[Sysname-route-policy-frr-10] quit
[Sysname] ripng 100
[Sysname-ripng-100] fast-reroute route-policy frr
filter-policy export
Use filter-policy export to configure RIPng to filter redistributed routes.
Use undo filter-policy export to remove the filtering.
Syntax
filter-policy { ipv6-acl-number | prefix-list prefix-list-name } export [ protocol [ process-id ] ]
undo filter-policy export [ protocol [ process-id ] ]
Default
RIPng does not filter redistributed routes.
Views
RIPng view
Predefined user roles
network-admin
Parameters
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999 to filter redistributed routes.
prefix-list prefix-list-name: Specifies an IPv6 prefix list by its name, a string of 1 to 63 characters, to filter redistributed routes.
protocol: Filters routes redistributed from a routing protocol.
process-id: Specifies the process ID of the specified routing protocol, in the range of 1 to 65535. This argument is available only when the routing protocol is ripng, ospfv3, or isisv6. The default is 1.
Usage guidelines
If the protocol argument is specified, RIPng filters only routes redistributed from the specified routing protocol. Otherwise, RIPng filters all redistributed routes.
To use an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL in one of the following ways:
· To deny/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ipv6 source sour sour-prefix command.
· To deny/permit a route with the specified destination and prefix, use the rule [ rule-id ] { deny | permit } ipv6 source sour sour-prefix destination dest dest-prefix command.
The source keyword specifies the destination address of a route and the destination keyword specifies the prefix of the route. The specified prefix must be contiguous. Otherwise, the prefix configuration does not take effect.
Examples
# Use IPv6 prefix list to filter redistributed RIPng updates.
<Sysname> system-view
[Sysname] ipv6 prefix-list abc index 10 permit 100:1:: 32
[Sysname] ripng 100
[Sysname-ripng-100] filter-policy prefix-list abc export
# Configure advanced IPv6 ACL 3000 to permit only route 2001::1/128 to pass. Use advanced IPv6 ACL 3000 to filter redistributed routes.
<Sysname> system-view
[Sysname] acl ipv6 advanced 3000
[Sysname-acl-ipv6-adv-3000] rule 10 permit ipv6 source 2001::1 128 destination ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff 128
[Sysname-acl-ipv6-adv-3000] rule 100 deny ipv6
[Sysname-acl-ipv6-adv-3000] quit
[Sysname] ripng 100
[Sysname-ripng-100] filter-policy 3000 export
filter-policy import
Use filter-policy import to configure RIPng to filter received routes.
Use undo filter-policy import to restore the default.
Syntax
filter-policy { ipv6-acl-number | prefix-list prefix-list-name } import
undo filter-policy import
Default
RIPng does not filter received routes.
Views
RIPng view
Predefined user roles
network-admin
Parameters
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999 to filter received routes.
prefix-list prefix-list-name: Specifies an IPv6 prefix list by its name, a string of 1 to 63 characters, to filter received routes.
Usage guidelines
To use an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL in one of the following ways:
· To deny/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ipv6 source sour sour-prefix command.
· To deny/permit a route with the specified destination and prefix, use the rule [ rule-id ] { deny | permit } ipv6 source sour sour-prefix destination dest dest-prefix command.
The source keyword specifies the destination address of a route and the destination keyword specifies the prefix of the route. The prefix must be contiguous. Otherwise, the configuration does not take effect.
Examples
# Use the IPv6 prefix list abc to filter received RIPng updates.
<Sysname> system-view
[Sysname] ipv6 prefix-list abc index 10 permit 100:1:: 32
[Sysname] ripng 100
[Sysname-ripng-100] filter-policy prefix-list abc import
# Configure advanced IPv6 ACL 3000 to permit only route 2001::1/128 to pass. Use advanced IPv6 ACL 3000 to filter received routes.
<Sysname> system-view
[Sysname] acl ipv6 advanced 3000
[Sysname-acl-ipv6-adv-3000] rule 10 permit ipv6 source 2001::1 128 destination ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff 128
[Sysname-acl-ipv6-adv-3000] rule 100 deny ipv6
[Sysname-acl-ipv6-adv-3000] quit
[Sysname] ripng 100
[Sysname-ripng-100] filter-policy 3000 import
graceful-restart
Use graceful-restart to enable Graceful Restart (GR) for RIPng.
Use undo graceful-restart to disable RIPng GR.
Syntax
graceful-restart
undo graceful-restart
Default
RIPng GR is disabled.
Views
RIPng view
Predefined user roles
network-admin
Usage guidelines
RIPng GR and RIPng NSR are mutually exclusive. Do not configure the graceful-restart command and the non-stop-routing command at the same time.
Examples
# Enable GR for RIPng process 1.
<Sysname> system-view
[Sysname] ripng 1
[Sysname-ripng-1] graceful-restart
graceful-restart interval
Use graceful-restart interval to set the GR interval.
Use undo graceful-restart interval to restore the default.
Syntax
graceful-restart interval interval
undo graceful-restart interval
Default
The GR interval is 60 seconds.
Views
RIPng view
Predefined user roles
network-admin
Parameters
interval: Specifies the GR interval in the range of 5 to 360 seconds.
Examples
# Set the GR interval to 200 seconds for RIPng process 1.
[Sysname] ripng 1
[Sysname-ripng-1] graceful-restart interval 200
import-route
Use import-route to redistribute routes from another routing protocol.
Use undo import-route to disable route redistribution.
Syntax
import-route protocol [ as-number | process-id ] [ allow-ibgp ] [ allow-direct | cost cost-value | route-policy route-policy-name ] *
undo import-route protocol [ process-id ]
Default
RIPng does not redistribute routes from another routing protocol.
Views
RIPng view
Predefined user roles
network-admin
Parameters
protocol: Specifies a routing protocol from which RIPng redistributes routes.
as-number: Specifies an AS by its number in the range of 1 to 4294967295. This argument applies only to the bgp4+ protocol. If you do not specify the as-number argument, this command redistributes all IPv6 EBGP routes. As a best practice, specify the AS number to avoid redistributing excessive IPv6 EBGP routes.
process-id: Specifies a process by its ID in the range of 1 to 65535. The default is 1. This argument is available only when the protocol is isisv6, ospfv3, or ripng.
allow-ibgp: Allows redistribution of IBGP routes. This keyword is available when the protocol argument is set to bgp4+.
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. If you specify both the allow-direct keyword and the route-policy route-policy-name option, make sure the if-match rule defined in the routing policy does not conflict with the allow-direct keyword. For example, if you specify the allow-direct keyword, do not configure the if-match route-type rule for the routing policy. Otherwise, the allow-direct keyword does not take effect.
cost cost-value: Specifies a metric for redistributed routes, in the range of 0 to 16. The default metric is 0.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
The import-route bgp4+ command redistributes only EBGP routes. The import-route bgp4+ allow-ibgp command redistributes both EBGP and IBGP routes.
Examples
# Redistribute routes from IPv6 IS-IS process 7 into RIPng and set the metric for redistributed routes to 7.
<Sysname> system-view
[Sysname] ripng 100
[Sysname-ripng-100] import-route isisv6 7 cost 7
maximum load-balancing
Use maximum load-balancing to set the maximum number of equal-cost multi-path (ECMP) routes for load balancing.
Use undo maximum load-balancing to restore the default.
Syntax
maximum load-balancing number
undo maximum load-balancing
Default
The maximum number of RIPng ECMP routes is 32.
Views
RIPng view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of ECMP routes. When this argument takes a value of 1, RIPng does not perform load balancing. The value range for this argument is 1 to 32.
Examples
# Set the maximum number of ECMP routes to 2.
<Sysname> system-view
[Sysname] ripng 100
[Sysname-ripng-100] maximum load-balancing 2
non-stop-routing
Use non-stop-routing to enable RIPng NSR.
Use undo non-stop-routing to disable RIPng NSR.
Syntax
non-stop-routing
undo non-stop-routing
Default
RIPng NSR is disabled.
Views
RIPng view
Predefined user roles
network-admin
Usage guidelines
The following matrix shows the command and hardware compatibility:
|
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28/3600-51 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
· In standalone mode: No · In IRF mode: Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Command compatibility |
|
MSR810-LM-GL |
No |
|
MSR810-W-LM-GL |
No |
|
MSR830-6EI-GL |
No |
|
MSR830-10EI-GL |
No |
|
MSR830-6HI-GL |
No |
|
MSR830-10HI-GL |
No |
|
MSR2600-6-X1-GL |
No |
|
MSR3600-28-SI-GL |
No |
RIPng NSR enabled for a RIPng process takes effect only on that process. As a best practice, enable RIPng NSR for each process if multiple RIPng processes exist.
RIPng NSR and RIPng GR are mutually exclusive. Do not configure the non-stop-routing command and the graceful-restart command at the same time.
Examples
# Enable NSR for RIPng process 1.
[Sysname] ripng 1
[Sysname-ripng-1] non-stop-routing
output-delay
Use output-delay to set the RIPng packet sending interval and the maximum number of RIPng packets that can be sent at each interval.
Use undo output-delay to restore the default.
Syntax
Default
A RIPng process sends a maximum of three RIPng packets every 20 milliseconds.
Views
RIPng view
Predefined user roles
network-admin
Parameters
time: Specifies the RIPng packet sending interval in the range of 10 to 100 milliseconds.
count: Specifies the maximum number of RIPng packets sent by a RIPng process at each interval, in the range of 1 to 30.
Usage guidelines
If you configure the RIPng packet sending rate for both a RIPng process and an interface running the RIPng process, the configuration on the interface takes effect.
Examples
# Configure RIPng process 1 to send a maximum of 10 RIPng packets every 60 milliseconds.
[Sysname] ripng 1
[Sysname-ripng-1] output-delay 60 count 10
Related commands
preference
Use preference to set the preference for RIPng routes.
Use undo preference to restore the default.
Syntax
preference { preference | route-policy route-policy-name } *
undo preference
Default
The preference of RIPng routes is 100.
Views
RIPng view
Predefined user roles
network-admin
Parameters
preference: Specifies the preference for RIPng routes, in the range of 1 to 255. The smaller the value, the higher the preference.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
You can specify a routing policy to set a preference for the matching RIPng routes.
· The preference set by the routing policy applies to all matching RIPng routes. The preference of other routes is set by the preference command.
· If no preference is set by the routing policy, the preference of all RIPng routes is set by the preference command.
Examples
# Set the preference for RIPng routes to 120.
<Sysname> system-view
[Sysname] ripng 100
[Sysname-ripng-100] preference 120
reset ripng process
Use reset ripng process to restart a RIPng process.
Syntax
reset ripng process-id process
Views
User view
Predefined user roles
network-admin
Parameters
process-id: Specifies a RIPng process by its ID in the range of 1 to 65535.
Usage guidelines
After executing the command, you are prompted to confirm the operation.
Examples
# Restart RIPng process 100.
<Sysname> reset ripng 100 process
Reset RIPng process? [Y/N]:y
reset ripng statistics
Use reset ripng statistics to clear statistics for a RIPng process.
Syntax
reset ripng process-id statistics
Views
User view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies a RIPng process by its ID in the range of 1 to 65535.
Examples
# Clear statistics for RIPng process 100.
<Sysname> reset ripng 100 statistics
ripng
Use ripng to enable RIPng and enter RIPng view.
Use undo ripng to disable RIPng.
Syntax
ripng [ process-id ] [ vpn-instance vpn-instance-name ]
undo ripng [ process-id ]
Default
RIPng is disabled.
Views
System view
Predefined user roles
network-admin
Parameters
process-id: Specifies a RIPng process by its ID in the range of 1 to 65535. The default value is 1.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the RIPng process runs on the public network.
Usage guidelines
Before you configure global RIPng parameters, you must create a RIPng process. This restriction does not apply to configuring interface RIPng parameters.
If you disable a RIPng process, the configured RIPng parameters become invalid.
Examples
# Create RIPng process 100 and enter its view.
<Sysname> system-view
[Sysname] ripng 100
[Sysname-ripng-100]
ripng default-route
Use ripng default-route to configure a RIPng interface to advertise a default route with a specified metric.
Use undo ripng default-route to disable a RIPng interface from sending a default route.
Syntax
ripng default-route { only | originate } [ cost cost-value | route-policy route-policy-name ] *
undo ripng default-route
Default
A RIPng process does not advertise a default route.
Views
Interface view
Predefined user roles
network-admin
Parameters
only: Advertises only an IPv6 default route (::/0).
originate: Advertises an IPv6 default route (::/0) and other routes.
cost-value: Specifies a cost for the default route, in the range of 1 to 15. The default is 1.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters. The command advertises a default route only when a route in the routing table matches the routing policy.
Usage guidelines
This command enables the interface to advertise a RIPng default route in a route update regardless of whether the default route exists in the local IPv6 routing table.
A RIPng interface configured to advertise a default route does not receive any default routes from its neighbors.
Examples
# Configure RIPng on GigabitEthernet 1/0/1 to advertise only a default route.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ripng default-route only
# Configure RIPng on GigabitEthernet 1/0/1 to advertise a default route and other routes.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ripng default-route originate
ripng enable
Use ripng enable to enable RIPng on an interface.
Use undo ripng enable to disable RIPng on an interface.
Syntax
ripng process-id enable
undo ripng enable
Default
RIPng is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
process-id: Specifies a RIPng process by its ID in the range of 1 to 65535.
Examples
# Enable RIPng 100 on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ripng 100 enable
ripng ipsec-profile
Use ripng ipsec-profile to apply an IPsec profile to a RIPng interface.
Use undo ripng ipsec-profile to restore the default.
Syntax
ripng ipsec-profile profile-name
undo ripng ipsec-profile
Default
No IPsec profile is applied to a RIPng interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
profile-name: Specifies an IPsec profile by its name, a case-insensitive string of 1 to 63 characters.
Usage guidelines
To configure an IPsec profile, see IPsec in Security Configuration Guide.
Examples
# Apply IPsec profile profile001 to GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ripng ipsec-profile profile001
ripng metricin
Use ripng metricin to configure an interface to add a metric to inbound RIPng routes.
Use undo ripng metricin to restore the default.
Syntax
ripng metricin value
undo ripng metricin
Default
The additional metric of an inbound route is 0.
Views
Interface view
Predefined user roles
network-admin
Parameters
value: Adds an additional metric to inbound routes, in the range of 0 to 16.
Examples
# Configure GigabitEthernet 1/0/1 to add a metric of 12 to inbound RIPng routes.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ripng metricin 12
ripng metricout
Use ripng metricout to configure an interface to add a metric to outbound RIPng routes.
Use undo ripng metricout to restore the default.
Syntax
ripng metricout value
undo ripng metricout
Default
The additional metric of outbound RIPng routes is 1.
Views
Interface view
Predefined user roles
network-admin
Parameters
value: Adds an additional metric to outbound routes, in the range of 1 to 16.
Examples
# Configure RIPng on GigabitEthernet 1/0/1 to add a metric of 12 to outbound RIPng routes.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ripng metricout 12
ripng output-delay
Use ripng output-delay to set the RIPng packet sending interval and the maximum number of RIPng packets that can be sent by an interface at each interval.
Use undo ripng output-delay to restore the default.
Syntax
ripng output-delay time count count
Default
An interface uses the RIPng packet sending rate set for the RIPng process that the interface runs.
Views
Interface view
Predefined user roles
network-admin
Parameters
time: Specifies the RIPng packet sending interval in the range of 10 to 100 milliseconds.
count: Specifies the maximum number of RIPng packets sent at each interval, in the range of 1 to 30.
Usage guidelines
If you set the RIPng packet sending rate for both a RIPng process and an interface running the RIPng process, the configuration on the interface takes effect.
Examples
# Configure GigabitEthernet 1/0/1 to send a maximum of six RIPng packets every 30 milliseconds.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ripng output-delay 30 count 6
Related commands
output-delay
ripng poison-reverse
Use ripng poison-reverse to enable poison reverse.
Use undo ripng poison-reverse to disable poison reverse.
Syntax
ripng poison-reverse
undo ripng poison-reverse
Default
Poison reverse is disabled.
Views
Interface view
Predefined user roles
network-admin
Examples
# Enable poison reverse for RIPng update messages on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ripng poison-reverse
ripng primary-path-detect bfd echo
Use ripng primary-path-detect bfd echo to enable BFD single-hop echo detection for RIPng FRR.
Use undo ripng primary-path-detect bfd to disable BFD single-hop echo detection for RIPng FRR.
Syntax
ripng primary-path-detect bfd echo
undo ripng primary-path-detect bfd
Default
BFD single-hop echo detection is disabled for RIPng FRR.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
For quicker RIPng FRR, use BFD single-hop echo detection on the primary link of redundant links to detect link failure.
Examples
# Enable BFD single-hop echo detection for RIPng FRR on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] ripng 1
[Sysname-ripng-1] fast-reroute route-policy frr
[Sysname-ripng-1] quit
[Sysname] bfd echo-source-ipv6 1::1
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ripng primary-path-detect bfd echo
ripng split-horizon
Use ripng split-horizon to enable split horizon.
Use undo ripng split-horizon to disable split horizon.
Syntax
ripng split-horizon
undo ripng split-horizon
Default
Split horizon is enabled.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
Split horizon prevents routing loops. If you want to disable this feature, make sure the operation is indispensable.
If both poison reverse and split horizon are enabled, only poison reverse takes effect.
On NBMA networks, such as FR where multiple VCs are configured on the primary and secondary interfaces, disable split horizon to ensure correct route advertisement. For more information, see frame relay configuration in Layer 2—WAN Configuration Guide.
Examples
# Enable split horizon on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ripng split-horizon
ripng summary-address
Use ripng summary-address to configure a summary network to be advertised through an interface.
Use undo ripng summary-address to remove a summary network.
Syntax
ripng summary-address ipv6-address prefix-length
undo ripng summary-address ipv6-address prefix-length
Default
No summary network is configured to be advertised through an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
ipv6-address: Specifies the destination IPv6 address of the summary route.
prefix-length: Specifies the prefix length of the destination IPv6 address of the summary route, in the range of 0 to 128. It indicates the number of consecutive 1s of the prefix, which defines the network ID.
Usage guidelines
Networks on the summary network will not be advertised. The cost of the summary route is the lowest cost among summarized routes.
Examples
# Assign an IPv6 address with the 64-bit prefix to GigabitEthernet 1/0/1 and configure a summary with the 35-bit prefix.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ipv6 address 2001:200::3EFF:FE11:6770/64
[Sysname-GigabitEthernet1/0/1] ripng summary-address 2001:200:: 35
timer triggered
Use timer triggered to set the interval for sending triggered updates.
Use undo timer triggered to restore the default.
Syntax
timer triggered maximum-interval [ minimum-interval [ incremental-interval ] ]
Default
The maximum, minimum, and incremental intervals for sending triggered updates are 5 seconds, 50 milliseconds, and 200 milliseconds, respectively.
Views
RIPng view
Predefines user roles
network-admin
Parameters
maximum-interval: Specifies the maximum interval for sending triggered updates, in the range of 1 to 5 seconds.
minimum-interval: Specifies the minimum interval for sending triggered updates, in the range of 10 to 5000 milliseconds.
incremental-interval: Specifies the incremental interval for sending triggered updates, in the range of 100 to 1000 milliseconds.
Usage guidelines
The minimum interval and the incremental interval cannot be greater than the maximum interval.
For a stable network, the minimum interval is used. If network changes become frequent, the incremental interval incremental-interval is used to increase the triggered update sending interval until the maximum-interval is reached.
Examples
# Set the maximum, minimum, and incremental intervals for sending triggered updates to 2 seconds, 100 milliseconds, and 100 milliseconds, respectively.
[Sysname] ripng 100
[Sysname-ripng-100] timer triggered 2 100 100
timers
Use timers to set RIPng timers.
Use undo timers to restore the default.
Syntax
timers { garbage-collect garbage-collect-value | suppress suppress-value | timeout timeout-value | update update-value } *
undo timers { garbage-collect | suppress | timeout | update } *
Default
The garbage-collect timer is 120 seconds, the suppress timer is 120 seconds, the timeout timer is 180 seconds, and the update timer is 30 seconds.
Views
RIPng view
Predefines user roles
network-admin
Parameters
garbage-collect-value: Sets the garbage-collect timer in the range of 1 to 86400 seconds.
suppress-value: Sets the suppress timer in the range of 0 to 86400 seconds.
timeout-value: Sets the timeout timer in the range of 1 to 86400 seconds.
update-value: Sets the update timer in the range of 1 to 86400 seconds.
Usage guidelines
RIPng has the following timers:
· Update timer—Interval between update messages.
· Timeout timer—Route aging time. If no update for a route is received before the timer expires, RIPng sets the metric of the route to 16.
· Suppress timer—How long a RIPng route stays in suppressed state. When the metric of a route becomes 16, the route enters the suppressed state. If RIPng receives an update for the route from the same neighbor and the route in the update has a metric less than 16, RIPng uses the route to replace the suppressed route.
· Garbage-collect timer—Interval from when the metric of a route becomes 16 to when it is deleted from the routing table. During the garbage-collect timer length, RIPng advertises the route with a metric of 16. If no update is announced for that route before the garbage-collect timer expires, RIPng deletes the route from the routing table.
As a best practice, do not change the default values of these timers.
The timer lengths must be kept consistent on all routers in the network.
Examples
# Set the update, timeout, suppress, and garbage-collect timers to 5 seconds, 15 seconds, 15 seconds, and 30 seconds.
<Sysname> system-view
[Sysname] ripng 1
[Sysname-ripng-1] timers update 5 timeout 15 suppress 15 garbage-collect 30
OSPFv3 commands
abr-summary (OSPFv3 area view)
Use abr-summary to configure route summarization on an ABR.
Use undo abr-summary to remove the configuration.
Syntax
abr-summary ipv6-address prefix-length [ not-advertise ] [ cost cost-value ]
undo abr-summary ipv6-address prefix-length
Default
Route summarization is not configured on an ABR.
Views
OSPFv3 area view
Predefined user roles
network-admin
Parameters
ipv6-address: Specifies the destination IPv6 address of the summary route.
prefix-length: Specifies the prefix length of the destination IPv6 address, in the range of 0 to 128. This argument specifies the number of consecutive 1s of the prefix, which defines the network ID.
not-advertise: Specifies not to advertise the summary IPv6 route. If you do not specify this keyword, the command advertises the IPv6 summary route.
cost cost-value: Specifies the cost of the summary route, in the range of 1 to 16777215. The default cost is the largest cost value among routes that are summarized.
Usage guidelines
This command applies only to an ABR to summarize multiple contiguous networks into one network.
To enable ABR to advertise specific routes that have been summarized, use the undo abr-summary command.
Examples
# Summarize networks 2000:1:1:1::/64 and 2000:1:1:2::/64 in Area 1 into 2000:1:1::/48.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] area 1
[Sysname-ospfv3-1-area-0.0.0.1] abr-summary 2000:1:1:: 48
area
Use area to create an OSPFv3 area and enter OSPFv3 area view.
Use undo area to remove an OSPFv3 area.
Syntax
area area-id
undo area area-id
Default
No OSPFv3 areas exist.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
area-id: Specifies an area by its ID, an IPv4 address or a decimal integer in the range of 0 to 4294967295 that is translated into the IPv4 address format.
Examples
# Create OSPFv3 Area 0 and enter its view.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] area 0
[Sysname-ospfv3-1-area-0.0.0.0]
asbr-summary (OSPFv3 view)
Use asbr-summary to configure route summarization on an ASBR.
Use undo asbr-summary to remove the configuration.
Syntax
asbr-summary ipv6-address prefix-length [ cost cost-value | not-advertise | nssa-only | tag tag ] *
undo asbr-summary ipv6-address prefix-length
Default
Route summarization is not configured on an ASBR.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
ipv6-address: Specifies the destination IPv6 address of the summary route.
prefix-length: Specifies the prefix length in the range of 0 to 128.
cost cost-value: Specifies the cost of the summary route, in the range of 1 to 16777214. If you do not specify this option, the largest cost among the summarized routes applies. If the routes in Type-5 LSAs translated from Type-7 LSAs are Type-2 external routes, the largest cost among the summarized routes plus 1 applies.
not-advertise: Disables advertising the summary route. If you do not specify this keyword, the command advertises the route.
nssa-only: Limits the route advertisement to the NSSA area by setting the P-bit of Type-7 LSAs to 0. By default, the P-bit of Type-7 LSAs is set to 1. If the ASBR is also an ABR and FULL state neighbors exist in the backbone area, the P-bit of Type-7 LSAs originated by the ASBR is set to 0. This keyword applies to the NSSA ASBR.
tag tag: Specifies a tag for the summary route, in the range of 0 to 4294967295.
Usage guidelines
An ASBR can summarize routes in the following LSAs:
· Type-5 LSAs.
· Type-7 LSAs in an NSSA area.
· Type-5 LSAs translated by the ASBR (also an ABR) from Type-7 LSAs in an NSSA area.
If the ASBR (ABR) is not a translator, it cannot summarize routes in Type-5 LSAs translated from Type-7 LSAs.
To enable ASBR to advertise specific routes that have been summarized, use the undo asbr-summary command.
Examples
# Configure a summary route 2000::/16, and specify a cost of 100 and a tag value of 2 for the summary route.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] asbr-summary 2000:: 16 cost 100 tag 2
bandwidth-reference
Use bandwidth-reference to set a reference bandwidth value for link cost calculation.
Use undo bandwidth-reference to restore the default.
Syntax
bandwidth-reference value
undo bandwidth-reference
Default
The reference bandwidth value is 100 Mbps for link cost calculation.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
value: Specifies the reference bandwidth value for link cost calculation, in the range of 1 to 4294967 Mbps.
Usage guidelines
You can configure an OSPFv3 cost for an interface with one of the following methods:
· Configure the cost value in interface view.
· Configure a bandwidth reference value. OSPFv3 computes the cost automatically based on the bandwidth reference value by using the following formula: Interface OSPFv3 cost = Bandwidth reference value / Interface bandwidth.
¡ If the calculated cost is greater than 65535, the value of 65535 is used.
¡ If the calculated cost is smaller than 1, the value of 1 is used.
If no cost value is configured for an interface, OSPFv3 computes the interface cost value automatically.
Examples
# Set the reference bandwidth value to 1000 Mbps.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] bandwidth-reference 1000
default tag
Use default tag to set a tag for redistributed routes.
Use undo default tag to restore the default.
Syntax
default tag tag
undo default tag
Default
The tag of redistributed routes is 1.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
tag: Specifies a tag for redistributed routes, in the range of 0 to 4294967295.
Usage guidelines
If you do not set a tag for redistributed routes by using the default-route-advertise, import-route, or route-tag command, the tag specified by the default tag command applies.
Examples
# Set the tag for redistributed routes to 2.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] default tag 2
Related commands
default-route-advertise (OSPFv3 view)
import-route
route-tag (MPLS Command Reference)
default-cost (OSPFv3 area view)
Use default-cost to set a cost for the default route advertised to the stub area or NSSA area.
Use undo default-cost to restore the default.
Syntax
default-cost cost
undo default-cost
Default
The cost is 1.
Views
OSPFv3 area view
Predefined user roles
network-admin
Parameters
value: Specifies a cost for the default route advertised to the stub area or NSSA area, in the range of 0 to 16777214.
Usage guidelines
This command takes effect only on the ABR of a stub area or the ABR or ASBR of an NSSA area.
Examples
# Configure Area 1 as a stub area, and set the cost of the default route advertised to the stub area to 60.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] area 1
[Sysname-ospfv3-1-area-0.0.0.1] stub
[Sysname-ospfv3-1-area-0.0.0.1] default-cost 60
Related commands
nssa (OSPFv3 area view)
stub (OSPFv3 area view)
default-route-advertise (OSPFv3 view)
Use default-route-advertise to redistribute a default route into the OSPFv3 routing domain.
Use undo default-route-advertise to restore the default.
Syntax
default-route-advertise [ [ always | permit-calculate-other ] | cost cost-value | route-policy route-policy-name | tag tag | type type ] *
undo default-route-advertise
Default
No default route is redistributed into the OSPFv3 routing domain.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
always: Redistributes a default route in an AS-external-LSA into the OSPFv3 routing domain regardless of whether a default route exists in the routing table. If you do not specify this keyword, the router redistributes a default route in an AS-external-LSA into the OSPFv3 routing domain only when the default route exists in the routing table.
permit-calculate-other: Enables OSPFv3 to calculate default routes received from other routers. If you do not specify this keyword, OSPFv3 does not calculate default routes from other routers. If the router does not redistribute any default route in an AS-external-LSA into the OSPFv3 routing domain, the router calculates default routes from other routers. It calculates these routes regardless of whether this keyword is specified.
cost cost-value: Specifies a cost for the default route, in the range of 0 to 16777214. The default is 1.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters. When the routing policy is matched and one of the following conditions is met, the command redistributes a default route in an AS-external-LSA into the OSPFv3 routing domain:
· A default route exists in the routing table.
· The always keyword is specified.
The routing policy modifies values in the AS-external-LSA.
tag tag: Specifies a tag for the default route, in the range of 0 to 4294967295. If you do not specify this option, the tag specified by the default tag command applies.
type type: Specifies a type for the AS-external-LSA, 1 or 2. The default is 2.
Usage guidelines
This command redistributes a default route in an AS-external-LSA, which cannot be redistributed with the import-route command. If the local routing table has no default route, you must provide the always keyword for the command.
Examples
# Redistribute a default route into the OSPFv3 routing domain. (The default route does not exist in the local router.)
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] default-route-advertise always
Related commands
import-route (OSPFv3 view)
display ospfv3
Use display ospfv3 to display OSPFv3 process information.
Syntax
display ospfv3 [ process-id ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays information about all OSPFv3 processes.
verbose: Displays detailed OSPFv3 process information. If you do not specify this keyword, the command displays brief OSPFv3 process information.
Examples
# Display detailed information about all OSPFv3 processes.
<Sysname> display ospfv3 verbose
OSPFv3 Process 1 with Router ID 1.1.1.1
RouterID: 1.1.1.1 Router type: ABR ASBR NSSA
Route tag: 0
Route tag check: Disabled
Multi-VPN-Instance: Disabled
Type value of extended community attributes:
Domain ID : 0x0005
Route type: 0x0306
Router ID : 0x0107
Domain-id: 0.0.0.0
DN-bit check: Enabled
DN-bit set: Enabled
Originating router-LSAs with maximum metric
Condition: On startup while BGP is converging for 600 seconds, State: Inactive
Advertise summary-LSAs with metric 16711680
Advertise external-LSAs with metric 16711680
Advertise intra-area-prefix-LSAs with maximum metric
SPF-schedule-interval: 5 50 200
LSA generation interval: 5
LSA arrival interval: 1000
Transmit pacing: Interval: 20 Count: 3
Default ASE parameters: Tag: 1
Route preference: 10
ASE route preference: 150
FRR backup mode: LFA
SPF calculation count: 0
External LSA count: 0
LSA originated count: 0
LSA received count: 0
Area count: 2 Stub area Count: 0 NSSA area Count: 1
ExChange/Loading neighbors: 0
Max equal cost paths: 32
Up interfaces: 1
Full neighbors: 1
Normal areas with up interfaces: 1
Calculation trigger type: Full
Current calculation type: SPF calculation
Current calculation phase: Calculation area topology
Redistribute timer: Off
Redistribute schedule type: RIB
Redistribute route count: 0
Process reset state: N/A
Current reset type: N/A
Next reset type: N/A
Reset prepare message replied: -/-/-/-
Reset process message replied: -/-/-/-
Reset phase of module:
M-N/A, P-N/A, S-N/A, C-N/A, R-N/A
Area: 0.0.0.0
Area flag: Normal
SPF scheduled count: 0
ExChange/Loading neighbors: 0
LSA count: 0
IPsec profile name: Profile000
Up interfaces: 0
MTU: 1440
Default cost: 1
Created by Vlink
Process reset state: N/A
Current reset type: N/A
Reset prepare message replied: -/-/-/-
Reset process message replied: -/-/-/-
Reset phase of module:
M-N/A, P-N/A, S-N/A, C-N/A, R-N/A
Area: 0.0.0.2
Area flag: Normal
SPF scheduled count: 0
ExChange/Loading neighbors: 0
LSA count: 0
Up interfaces: 1
MTU: 1500
Default cost: 1
Process reset state: N/A
Current reset type: N/A
Reset prepare message replied: -/-/-/-
Reset process message replied: -/-/-/-
Reset phase of module:
M-N/A, P-N/A, S-N/A, C-N/A, R-N/A
Area: 0.0.0.3
Area flag: NSSA
7/5 translator state: Disabled
7/5 translate stability timer interval: 0
SPF Scheduled Count: 0
ExChange/Loading neighbors: 0
LSA Count: 0
Up interfaces: 0
MTU: 1440
Default cost: 1
Process reset flag: N/A
Current reset type: N/A
Reset prepare message replied: -/-/-/-
Reset process message replied: -/-/-/-
Reset phase of module:
M-N/A, P-N/A, S-N/A, C-N/A, R-N/A
Table 135 Command output
|
Field |
Description |
|
OSPFv3 Process 1 with Router ID 1.1.1.1 |
OSPFv3 process is 1, and router ID is 1.1.1.1. |
|
Router type |
Router type: · ABR. · ASBR. · NSSA. · Null. |
|
Route tag |
Tag of the routes redistributed into the OSPFv3 process. |
|
Route tag check |
Whether the check is enabled for the route tag in OSPFv3 LSAs of the OSPFv3 process. |
|
Multi-VPN-Instance |
Whether the OSPFv3 process supports PE or multiple VPN instances: · Multi-VPN-Instance: Disabled—The process does not support multiple VPN instances. · Multi-VPN-Instance: Enabled—The process supports multiple VPN instances. · PE Router, Multi-VPN-Instance: Enabled—The local device is a PE. |
|
DN-bit check |
Whether the check is enabled for the DN bit in OSPFv3 LSAs of the OSPFv3 process. |
|
DN-bit set |
Whether the DN bit is set for OSPFv3 LSAs in the OSPFv3 process. |
|
Condition |
Time when the router acts as a stub router: · Always. · On startup while BGP is converging for xxx seconds, where xxx is specified by the user. · On startup for xxx seconds, where xxx is specified by the user. |
|
State |
State of the stub router: · Active. · Inactive. |
|
SPF-schedule-interval |
Interval for SPF calculations. |
|
Transmit pacing |
LSU advertisement rate: · Interval—Specifies the interval for sending LSUs. · Count—Specifies the maximum number of LSUs sent at each interval. |
|
Default ASE parameters |
Default parameters of redistributed routes. Tag represents the route tag of the redistributed routes. |
|
Route preference |
Internal route preference. |
|
ASE route preference |
AS-external route preference. |
|
FRR backup mode |
FRR backup mode: · LFA—Uses the LFA algorithm to calculate a backup next hop for all routes. LFA ABR-only indicates that only the next hop of the route to the ABR can be used as the backup next hop. · route-policy route-policy-name—Specifies a backup next hop by using a routing policy. |
|
LSA originated count |
Number of originated LSAs. |
|
LSA received count |
Number of received LSAs. |
|
Area count |
Total number of areas. |
|
Stub area Count |
Number of stub areas. |
|
NSSA area Count |
Number of NSSA areas. |
|
ExChange/Loading neighbors |
Neighbors in ExChange/Loading state. |
|
Calculation trigger type |
Route calculation trigger type: · Full—Calculation of all routes is triggered. · Area topology change—Topology change in an area. · Intra router change—Incremental intra-area route change. · ASBR change—Incremental ASBR route change. · Full IP prefix—Calculation of all IP prefixes is triggered. · Full intra AS—Calculation of all intra-AS prefixes is triggered. · Inc intra AS—Calculation of incremental intra-AS prefixes is triggered. · Full inter AS—Calculation of all AS-external prefixes is triggered. · Inc inter AS—Calculation of incremental AS-external prefixes is triggered. · Nexthop calculation—Calculation of next hops is triggered. · N/A—Route calculation is not triggered. |
|
Current calculation type |
Current route calculation type: · SPF calculation. · Intra router calculation—Intra-area route calculation. · ASBR calculation—Inter-area ASBR route calculation. · Inc intra router—Incremental intra-area route calculation. · Inc ASBR calculation—Incremental inter-area ASBR route calculation. · Full intra AS—Calculation of all intra-AS prefixes. · Inc intra AS—Calculation of incremental intra-AS prefixes. · Full inter AS—Calculation of all AS-external prefixes. · Inc inter AS—Calculation of incremental AS-external prefixes. · N/A—Route calculation is not triggered. |
|
Current calculation phase |
Current route calculation phase: · Calculation area topology—Calculating area topology. · Calculation router—Calculating routes on routers. · Calculation intra AS—Calculating intra-AS routes. · Calculation ASBR—Calculating routes on ASBRs. · Calculation inter AS—Calculating AS-external routes. · Calculation end—Ending phase of calculation. · N/A—Route calculation is not triggered. |
|
Redistribute timer |
Route redistribution timer status: on or off. |
|
Redistribute schedule type |
Route redistribution scheduling type: · RIB—Redistribute routes through the RIB table. · Self—Redistribute routes through the routing table. · N/A—Route redistribution is not triggered. |
|
Redistribute route count |
Number of redistributed routes. |
|
Process reset state |
Process reset state: · N/A—The process is not reset. · Under reset—The process is in the reset progress. · Under RIB smooth—The process is synchronizing RIB routes. |
|
Current reset type |
Current process reset type: · N/A—The process is not reset. · GR quit—Normal reset when GR quits abnormally. · Delete—Delete OSPFv3 process. · Undo router-id—Delete router ID. · Set router-id—Set router ID. |
|
Next reset type |
Next process reset type: · N/A—The process is not reset. · GR quit—Normal reset when GR quits abnormally. · Delete—Delete OSPFv3 process. · Undo router-id—Delete router ID. · Set router-id—Set router ID. |
|
Reset prepare message replied |
Modules that reply reset prepare messages: · P—Neighbor maintenance module. · S—LSDB synchronization module. · C—Route calculation module. · R—Route redistribution module. |
|
Reset process message replied |
Modules that reply reset process messages: · P—Neighbor maintenance module. · S—LSDB synchronization module. · C—Route calculation module. · R—Route redistribution module. |
|
Reset phase of module |
Reset phase of each module: · LSDB synchronization (S) module: ¡ N/A—Not reset. ¡ Delete ASE—Delete all ASE LSAs. ¡ Delete area LSA—Delete LSAs from an area. ¡ Delete area IF—Delete interfaces from an area. · Route calculation (C) module: ¡ N/A—Not reset. ¡ Delete topology—Delete area topology. ¡ Delete router—Delete routes of routers. ¡ Delete intra AS—Delete intra-AS routes ¡ Delete inter AS—Delete AS-external routes. ¡ Delete ASBR—Delete ASBR routes. · Route redistribution (R) module: ¡ N/A—Not reset. ¡ Delete import—Delete redistributed routes. |
|
IPsec profile name |
IPsec profile applied to the interface. |
|
Created by Vlink |
The area is created through virtual link. |
|
7/5 translator state |
State of the translator that translates Type-7 LSAs to Type-5 LSAs: · Enabled—The translator is specified through commands. · Elected—The translator is designated through election. · Disabled—The device is not a translator. |
|
7/5 translate stability timer interval |
Stability interval (in seconds) for Type-7 LSA-to-Type-5 LSA translation. |
display ospfv3 abr-asbr
Use display ospfv3 abr-asbr to display information about the routes to OSPFv3 ABR and ASBR.
Syntax
display ospfv3 [ process-id ] abr-asbr
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays information about all the routes to the OSPFv3 ABR and ASBR.
Examples
# Display information about all the routes to the OSPFv3 ABR and ASBR.
<Sysname> display ospfv3 abr-asbr
OSPFv3 Process 1 with Router ID 1.1.1.1
Destination : 1.1.1.2 Rtr Type : ABR
Area : 0.0.0.0 Path Type: Intra
Interface : GE2/0/2 BkInterface: GE2/0/1
NextHop : FE80:1:1::1
BkNexthop : FE80:1:2::2
Cost : 1
Destination : 1.1.1.3 Rtr Type : ASBR
Area : 0.0.0.0 Path Type: Intra
Interface : GE2/0/3 BkInterface: GE2/0/4
BkNexthop : FE80:1:2::4
NextHop : FE80:2:1::1
Cost : 1
Table 136 Command output
|
Field |
Description |
|
OSPFv3 Process 1 with Router ID 1.1.1.1 |
OSPFv3 process is 1, and router ID is 1.1.1.1. |
|
Destination |
Router ID of an ABR or ASBR. |
|
Rtr Type |
Router type: ABR, or ASBR. |
|
Area |
Area ID of the next hop. |
|
Path Type |
Type of the route to the ABR or ASBR: · Intra—Intra-area route. · Inter—Inter-area route. |
|
Interface |
Output interface. |
|
BkInterface |
Backup output interface. |
|
NextHop |
Next hop address. |
|
BkNexthop |
Backup next hop address. |
|
Cost |
Cost from the router to the ABR or ASBR. |
display ospfv3 abr-summary
Use display ospfv3 abr-summary to display ABR summary route information.
Syntax
display ospfv3 [ process-id ] [ area area-id ] abr-summary [ ipv6-address prefix-length ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays information about ABR summary routes for all OSPFv3 processes.
area area-id: Specifies an OSPFv3 area by its ID. The area ID is an IP address or a decimal integer in the range of 0 to 4294967295 that is translated into the IP address format. If you do not specify this option, the command displays information about ABR summary routes for all OSPFv3 areas.
ipv6-address prefix-length: Specifies an IPv6 address. The ipv6-address argument specifies an IPv6 prefix. The prefix-length argument specifies a prefix length in the range of 0 to 128. If you do not specify this argument, the command displays information about all summary routes on the ABR.
verbose: Displays detailed ABR summary route information. If you do not specify this keyword, the command displays brief ABR summary route information.
Examples
# Display brief ABR summary route information in OSPFv3 process 1.
<Sysname> display ospfv3 1 abr-summary
OSPFv3 Process 1 with Router ID 2.2.2.2
Area: 1.1.1.1
Total summary addresses: 1
Prefix : 1000:4::/32
Status : Advertise
NULL0 : Active
Cost : 1 (Configured)
Routes count: 2
Table 137 Command output
|
Field |
Description |
|
Area |
Area to which the summary routes belong. |
|
Total summary addresses |
Total number of summary routes. |
|
Prefix |
Prefix of the summary route. |
|
Status |
Advertisement status of the summary route. |
|
NULL0 |
Null 0 route. |
|
Cost |
Cost of the summary route. |
|
Routes count |
Number of summarized routes. |
# Display detailed ABR summary route information in OSPFv3 process 1.
<Sysname> display ospfv3 1 abr-summary verbose
OSPFv3 Process 1 with Router ID 2.2.2.2
Area: 1.1.1.1
Total summary addresses: 1
Prefix : 1000:4::/32
Status : Advertise
NULL0 : Active
Cost : 1 (Configured)
Routes count: 2
Destination Metric
1000:4:10:3::/96 1
1000:4:11:3::/96 1
Table 138 Command output
|
Field |
Description |
|
Destination |
Destination address of a summarized route. |
|
Metric |
Metric of a summarized route. |
display ospfv3 asbr-summary
Use display ospfv3 asbr-summary to display ASBR summary route information.
Syntax
display ospfv3 [ process-id ] asbr-summary [ ipv6-address prefix-length ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays information about ASBR summary routes for all OSPFv3 processes.
ipv6-address prefix-length: Specifies an IPv6 address. The ipv6-address argument specifies an IPv6 prefix. The prefix-length argument specifies a prefix length in the range of 0 to 128. If you do not specify this argument, the command displays information about all ASBR summary routes.
verbose: Displays detailed ASBR summary route information. If you do not specify this keyword, the command displays brief ASBR summary route information.
Examples
# Display brief ASBR summary route information in OSPFv3 process 1.
<Sysname> display ospfv3 1 asbr-summary
OSPFv3 Process 1 with Router ID 2.2.2.2
Total summary addresses: 1
Prefix : 1000:4::/32
Status : Advertise
NULL0 : Active
Cost : 1 (Configured)
Tag : (Not configured)
Nssa-only : (Not configured)
Routes count: 2
Table 139 Command output
|
Field |
Description |
|
Total summary addresses |
Total number of summary routes. |
|
Prefix |
Prefix and prefix length of the summary route. |
|
Status |
Advertisement status of the summary route: · Advertise—The summary route has been advertised. · Not-advertise—The summary route has not been advertised. |
|
NULL0 |
Status of the Null 0 route: · Active. · Inactive. |
|
Cost |
Cost of the summary route: · Configured. · Not configured. |
|
Tag |
Tag of the summary route: · Configured. · Not configured. |
|
Nssa-only |
Whether the nssa-only attribute is configured: · Configured. · Not configured. |
|
Routes count |
Number of summarized routes. |
# Display detailed ASBR summary route information in OSPFv3 process 1.
<Sysname> display ospfv3 1 asbr-summary verbose
OSPFv3 Process 1 with Router ID 2.2.2.2
Total summary addresses: 1
Prefix : 1000:4::/32
Status : Advertise
NULL0 : Active
Cost : 1 (Configured)
Tag : (Not configured)
Nssa-only : (Not configured)
Routes count: 2
Destination Protocol Process Type Metric
1000:4:10:3::/96 Static 0 2 1
1000:4:11:3::/96 Static 0 2 1
Table 140 Command output
|
Field |
Description |
|
Destination |
Prefix and prefix length of the summarized route. |
|
Protocol |
Routing protocol from which the route was redistributed. |
|
Process |
Process of the routing protocol from which the route was redistributed. |
|
Type |
Type of the summarized route. |
|
Metric |
Metric of the summarized route. |
display ospfv3 event-log
Use display ospfv3 event-log to display OSPFv3 log information.
Syntax
display ospfv3 [ process-id ] event-log { lsa-flush | peer | spf }
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays OSPFv3 log information for all processes.
lsa-flush: Specifies LSA aging log information.
peer: Specifies neighbor log information.
spf: Specifies route calculation log information.
Usage guidelines
Route calculation logs show the number of routes newly installed in the IPv6 routing table.
Neighbor logs include information about the following events:
· The OSPFv3 neighbor state goes down.
· The OSPFv3 neighbor state goes backward because the local end receives BadLSReq, SeqNumberMismatch, and 1-Way events.
Examples
# Display OSPFv3 LSA aging log information for OSPFv3 process 1.
<Sysname>display ospfv3 1 event-log lsa-flush
OSPFv3 Process 1 with Router ID 1.3.3.3
2014-09-02 07:55:25 Received MaxAge LSA from 1.1.1.1
Type: 3 LS ID: 0.0.0.2 AdvRtr: 1.1.1.1 Seq#: 80000001
2014-09-02 07:55:22 Flushed MaxAge LSA by itself
Type: 3 LS ID: 0.0.0.2 AdvRtr: 1.3.3.3 Seq#: 80000001
2014-09-02 07:55:07 Flushed MaxAge LSA by itself
Type: 3 LS ID: 0.0.0.40 AdvRtr: 1.3.3.3 Seq#: 80000001
2014-09-02 07:55:07 Flushed MaxAge LSA by itself
Type: 3 LS ID: 0.0.0.39 AdvRtr: 1.3.3.3 Seq#: 80000001
Table 141 Command output
|
Field |
Description |
|
Received MaxAge LSA from X.X.X.X |
The device received an LSA that has reached the maximum age from X.X.X.X. |
|
Flushed MaxAge LSA by itself |
The device flushed the LSA that has reached the maximum age. |
|
Type |
LSA type. |
|
LS ID |
LSA link state ID. |
|
AdvRtr |
Advertising router. |
|
Seg# |
LSA sequence number. |
# Display OSPFv3 route calculation log information for OSPFv3 process 1.
<Sysname>display ospfv3 1 event-log spf
OSPFv3 Process 1 with Router ID 1.3.3.3
Date Time Duration Intra Inter External Reason
2014-09-02 07:55:30 0.258827 0 0 0 Intra-area LSA
2014-09-02 07:55:30 0.679 0 0 0 Intra-area LSA
2014-09-02 07:55:30 0.51576 0 0 0 Intra-area LSA
2014-09-02 07:55:30 0.372 0 0 0 Intra-area LSA
2014-09-02 07:55:25 4.948353 0 0 0 Intra-area LSA
2014-09-02 07:55:25 0.5288 0 0 0 Area 0 full neighbor
2014-09-02 07:55:21 1.66013 0 0 0 Intra-area LSA
2014-09-02 07:55:20 0.450905 0 0 0 Intra-area LSA
2014-09-02 07:55:15 0.253688 0 0 0 Interface state change
2014-09-02 07:55:15 0.5693 0 0 0 Intra-area LSA
Table 142 Command output
|
Field |
Description |
|
Date/Time |
Time when the route calculation starts. |
|
Duration |
Duration of the route calculation, in seconds. |
|
Intra |
Number of intra-area routes newly installed in the IPv6 routing table. |
|
Inter |
Number of inter-area routes newly installed in the IPv6 routing table. |
|
External |
Number of external routes newly installed in the IPv6 routing table. |
|
Reason |
Reasons why the route calculation is performed: · Intra-area LSA—Intra-area LSA changes. · Inter-area LSA—Inter-area LSA changes. · External LSA—External LSA changes. · Configuration—Configuration changes. · Area 0 full neighbor—Number of FULL-state neighbors in Area 0 changes. · Area 0 up interface—Number of interfaces in up state in Area 0 changes. · AS number—AS number changes. · ABR summarization—ABR summarization changes. · GR end—GR ends. · Routing policy—Routing policy changes. · Intra-area tunnel—Intra-area tunnel changes. · Others—Other reasons. |
# Display OSPFv3 neighbor log information for OSPFv3 process 1.
<Sysname> display ospfv3 1 event-log peer
OSPFv3 Process 1 with Router ID 1.1.1.1
Date Time Router ID Reason Instance ID Interface
2014-09-02 16:39:13 1.3.3.3 IntPhyChange 0 GE1/0/1
2014-09-02 16:36:46 1.3.3.3 IntPhyChange 0 GE1/0/1
2014-09-02 16:34:49 1.3.3.3 BFDDown 0 GE1/0/1
2014-09-02 10:08:45 1.3.3.3 DeadExpired 0 GE1/0/2
2014-09-02 10:08:39 1.3.3.3 DeadExpired 0 VLINK1
2014-09-02 10:08:08 1.3.3.3 BFDDown 0 GE1/0/1
Table 143 Command output
|
Field |
Description |
|
Date &Time |
Time when the neighbor state changes. |
|
Router ID |
Neighbor router ID. |
|
Reason |
Reasons for neighbor state changes: · ResetConnect—The connection is lost due to insufficient memory. · IntChange—The interface parameter has changed. · ResetOspfv3—The OSPFv3 process is reset. · UndoOspfv3—The OSPFv3 process is deleted. · UndoArea—The OSPFv3 area is deleted. · UndoInt—The interface is disabled. · IntLogChange—The logical attribute of the interface has changed. · IntPhyChange—The physical attribute of the interface has changed. · DeadExpired—The dead timer expires. · Retrans—Excessive retransmissions. · BFDDown—The interface is shut down by BFD. · SilentInt—The interface is configured as a silent interface. · ConfStubArea—The interface is configured with stub area parameters. · ConfNssaArea—The interface is configured with NSSA area parameters. · VlinkDown—The virtual link goes down. · ShamlinkDown—The sham link goes down. · BadLSReq—The interface receives BadLSReq events. · SeqMismatch—The interface receives SeqNumberMismatch events. · Way—The interface receives 1-Way events. |
|
Instance ID |
Instance ID for an interface. |
|
Interface |
Interface name. |
display ospfv3 graceful-restart
Use display ospfv3 graceful-restart to display GR information.
Syntax
display ospfv3 [ process-id ] graceful-restart [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays GR information for all processes.
verbose: Displays detailed GR information. If you do not specify this keyword, the command displays brief GR information.
Examples
# Display brief GR information for all OSPFv3 processes (GR restarter).
<Sysname> display ospfv3 graceful-restart
OSPFv3 Process 1 with Router ID 3.3.3.3
Graceful-restart capability : Enable
Graceful-restart support : Planned and un-planned, Partial
Helper capability : Enable
Helper support : Planned and un-planned
Current GR state : Normal
Graceful-restart period : 120 seconds
Number of neighbors under helper: 0
Number of restarting neighbors : 0
Last exit reason:
Restarter: None
Helper : None
Table 144 Command output
|
Field |
Description |
|
OSPFv3 Process 1 with Router ID 3.3.3.3 |
The GR status of OSPFv3 process 1 with router ID 3.3.3.3 is displayed. |
|
Graceful-restart capability |
Whether OSPFv3 GR is enabled: · Enabled. · Disabled. |
|
Graceful-restart support |
GR modes that the process supports (displayed only when GR is enabled): · Planned and un-planned—Supports both planned and unplanned GR. · Planned only—Supports only planned GR. · Partial—Supports partial GR. · Global—Supports global GR. |
|
Helper capability |
Whether OSPFv3 GR helper is enabled: · Enabled. · Disabled. |
|
Helper support |
Policies and GR modes that the GR helper supports (displayed only when GR helper is enabled): · Strict LSA check—The GR helper supports strict LSA checking. · Planned and un-planned—The GR helper supports both planned and unplanned GR. · Planned only—The GR helper supports only planned GR. |
|
Current GR state |
GR status: · Normal—GR is not in progress or has completed. · Under GR—GR is in progress. · Under Helper—The process is acting as GR helper. |
|
Graceful-restart period |
GR restart interval. |
|
Number of neighbors under helper |
Number of neighbors in GR helper status. |
|
Number of restarting neighbors |
Number of neighbors in GR restarter status. |
|
Last exit reason |
Last exit reason: · Restarter—Reason that the restarter exited most recently: ¡ None. ¡ Completed—GR is completed. ¡ Interval timer is fired—The GR timer expires. ¡ Interface state change—An interface state change occurs. ¡ Received 1-way hello—The device receives 1-way hello packets from the neighbor. ¡ Reset neighbor—The neighbor is reset. ¡ DR or BDR change—The DR or BDR changes. · Helper—Reason that the helper exited most recently: ¡ None. ¡ Completed—GR is completed. ¡ Received 1-way hello—The device receives 1-way hello packets from the neighbor. ¡ Grace Period timer is fired—The GR timer expires. ¡ Lsa check failed—An LSA change on the GR helper is detected. ¡ Reset neighbor—The neighbor is reset. ¡ Received MAXAGE gracelsa but neighbor is not full—The device receives Grace-LSAs that reached the maximum age, but the neighbor is not in Full state. |
# Display detailed GR information for all OSPFv3 processes (GR restarter).
<Sysname> display ospfv3 graceful-restart verbose
OSPFv3 Process 1 with Router ID 3.3.3.3
Graceful-restart capability : Enable
Graceful-restart support : Planned and un-planned, Partial
Helper capability : Enable
Helper support : Planned and un-planned
Current GR state : Normal
Graceful-restart period : 120 seconds
Number of neighbors under helper: 0
Number of restarting neighbors : 0
Last exit reason:
Restarter: None
Helper : None
Area: 0.0.0.0
Area flag: Normal
Area up interface count: 1
Virtual-link Neighbor-ID: 100.1.1.1, Neighbor-state: Full
Restarter state: Normal State: P-2-P Type: Virtual
Interface: 6696 (GigabitEthernet1/0/2), Instance-ID: 0
Local IPv6 address: 200:1:FFFF::1
Remote IPv6 address: 201:FFFF::2
Transit area: 0.0.0.1
Last exit reason:
Restarter: None
Helper : None
Neighbor GR state Last helper exit reason
100.1.1.1 Normal None
Area: 0.0.0.1
Area flag: Transit
Area up interface count: 3
Interface: 5506 (GigabitEthernet1/0/3), Instance-ID: 0
Restarter state: Normal State: DR Type: Broadcast
Last exit reason:
Restarter: None
Helper : None
Neighbor count of this interface: 0
Number of neighbors under helper: 0
Interface: 6696 (GigabitEthernet1/0/2), Instance-ID: 0
Restarter state: Normal State: DR Type: Broadcast
Last exit reason:
Restarter: None
Helper : None
Neighbor count of this interface: 1
Number of neighbors under helper: 0
Neighbor GR state Last helper exit reason
100.1.1.1 Normal None
Sham-link Neighbor-ID: 100.1.1.1, Neighbor-state: Full
Restarter state: Normal State: P-2-P Type: Sham
Interface-ID: 2147483649, Instance-ID: 0
Source : 8000:88::FFFF
Destination : 7000:77::FFFF
Last exit reason:
Restarter: None
Helper : None
Neighbor GR state Last helper exit reason
100.1.1.1 Normal None
Area: 0.0.0.5
Area flag: NSSANoSummaryNoImportRoute
7/5 translator state: Disabled
7/5 translate stability timer interval: 0
Area up interface count: 0
Table 145 Command output
|
Field |
Description |
|
Area |
Area ID. |
|
Area flag |
Type of the area: · Normal. · Transit. · Stub. · StubNoSummary—Totally stub area. · NSSA. · NSSANoSummary—Totally NSSA area. · NSSANoSummaryNoImportRoute—Totally NSSA area with the no-import-route keyword configured. |
|
7/5 translator state |
State of the translator that translates Type-7 LSAs to Type-5 LSAs: · Enabled—The translator is specified through commands. · Elected—The translator is designated through election. · Disabled—The device is not a translator. |
|
7/5 translate stability timer interval |
Stability interval (in seconds) for Type-7 LSA-to-Type-5 LSA translation. |
|
Area up interface count |
Number of up interfaces in the area. |
|
Interface |
Interface in the area, or the output interface of the virtual link. |
|
Restarter state |
Restarter state on the interface. |
|
State |
Interface state. |
|
Type |
Interface network type. |
|
Neighbor count of this interface |
Number of neighbors on the interface. |
|
Neighbor |
Neighbor router ID. |
|
GR state |
Neighbor GR state: · Normal—GR is not in progress or has completed. · Under GR—GR is in process. · Under Helper—The process is acting as GR helper. |
|
Last helper exit reason |
Reason that the helper exited most recently. |
|
Virtual-link Neighbor-ID |
Router ID of the virtual link's neighbor. |
|
Neighbor-State |
Neighbor or virtual link state: Down, Init, 2-Way, ExStart, Exchange, Loading, and Full. |
|
Local IPv6 address |
Local IPv6 address of the neighbor relationship. |
|
Remote IPv6 address |
Peer IPv6 address of the neighbor relationship. |
|
Transit area |
Transit area ID. |
|
Sham-link Neighbor-ID |
Router ID of the sham link's neighbor. |
|
Source |
Source address of the sham link. |
|
Destination |
Destination address of the sham link. |
display ospfv3 interface
Use display ospfv3 interface to display OSPFv3 interface information.
Syntax
display ospfv3 [ process-id ] interface [ interface-type interface-number | verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535.
interface-type interface-number: Specifies an interface by its type and number.
verbose: Displays detailed information about all OSPFv3 interfaces.
Usage guidelines
If you do not specify a process, this command displays brief OSPFv3 interface information for all processes.
If you do not specify the interface-type interface-number argument or the verbose keyword, this command displays brief information about all OSPFv3 interfaces.
Examples
# Display OSPFv3 information about GigabitEthernet 1/0/1.
<Sysname> display ospfv3 interface gigabitethernet 1/0/1
OSPFv3 Process 1 with Router ID 1.1.1.1
Area: 0.0.0.0
-------------------------------------------------------------------------
GigabitEthernet1/0/1 is up, line protocol is up
Interface ID 3 Instance ID 0
IPv6 prefixes
fe80::200:12ff:fe34:1 (Link-Local address)
2001::1
Cost: 1 State: BDR Type: Broadcast MTU: 1500
Priority: 1
Designated router: 2.2.2.2
Backup designated router: 1.1.1.1
Timers: Hello 10, Dead 40, Poll 40, Retransmit 5, Transmit delay 1
FRR backup: Enabled
Neighbor count is 1, Adjacent neighbor count is 1
Primary path detection mode: BFD echo
IPsec profile name: profile001
Exchanging/Loading neighbors: 0
Wait timer: Off, LsAck timer: Off
Prefix-suppression is enabled
Table 146 Command output
|
Field |
Description |
|
Area |
Area ID that the interface belongs to. |
|
Interface ID |
Interface ID. |
|
Instance ID |
Instance ID. |
|
IPv6 prefixes |
IPv6 prefix. |
|
Cost |
Cost value of the interface. |
|
State |
Interface state: · DOWN—No protocol traffic can be sent or received on the interface. · Waiting—The interface starts sending and receiving Hello packets. The router is trying to determine the identity of the (Backup) designated router for the network. · P-2-P—The interface will send Hello packets at the interval of HelloInterval, and try to establish an adjacency with the neighbor. · DR—The router is the designated router on the network. · BDR—The router is the backup designated router on the network. · DROther—The router is a DR Other router on the attached network. |
|
Type |
Network type of the interface: PTP (P2P), PTMP (P2MP), Broadcast, or NBMA. |
|
MTU |
MTU value of the interface. |
|
Priority |
DR priority of the interface. |
|
Designated router |
DR on this link. |
|
Backup designated router |
BDR on this link. |
|
Timers |
Time intervals in seconds configured on the interface: · Hello—Hello interval. · Dead—Dead interval. · Poll—Polling interval on an NBMA network. · Retransmit—LSA retransmission interval. |
|
Transmit Delay |
LSA transmission delay on the interface, in seconds. |
|
FRR backup |
Whether LFA calculation is enabled on an interface: · Enabled. · Disabled. |
|
Neighbor count |
Number of neighbors on the interface. |
|
Primary path detection mode |
Primary link detection mode: · BFD ctrl—BFD control packet mode. · BFD echo—BFD echo packet mode. |
|
Adjacent neighbor count |
Number of adjacencies on the interface. |
|
IPsec profile name |
IPsec profile applied to the interface. |
display ospfv3 lsdb
Use display ospfv3 lsdb to display OSPFv3 LSDB information.
Syntax
display ospfv3 [ process-id ] lsdb [ { external | grace | inter-prefix | inter-router | intra-prefix | link | network | nssa | router | unknown [ type ] } [ link-state-id ] [ originate-router router-id | self-originate ] | statistics | total | verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays LSDB information for all processes.
external: Displays AS external LSAs (Type-5 LSAs).
grace: Displays Grace-LSAs (Type-11 LSAs).
inter-prefix: Displays Inter-area-prefix LSAs (Type-3 LSAs).
inter-router: Displays Inter-area-router LSAs (Type-4 LSAs).
intra-prefix: Displays Intra-area-prefix LSAs (Type-9 LSAs).
link: Displays Link-LSAs (Type-8 LSAs).
network: Displays Network-LSAs (Type-2 LSAs).
nssa: Displays NSSA LSAs (Type-7 LSAs).
router: Displays Router-LSAs (Type-1 LSAs).
unknown: Displays unknown LSAs.
type: Specifies an LSA type, a hexadecimal string of 0 to FFFF. If you do not specify this argument, the command displays all unknown LSAs.
link-state-id: Specifies a link state ID in IPv4 address format.
originate-router router-id: Specifies an advertising router by its ID.
self-originate: Displays locally originated LSAs.
statistics: Displays LSA statistics.
total: Displays the total number of LSAs in the LSDB.
verbose: Displays detailed information. If you do not specify this keyword, the command displays brief information.
Examples
# Display OSPFv3 LSDB information.
<Sysname> display ospfv3 lsdb
OSPFv3 Process 1 with Router ID 1.1.1.1
Link-LSA (Interface GigabitEthernet0/1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum Prefix
0.0.0.2 1.1.1.1 0345 0x80000001 0x4ad7 1
0.0.0.2 2.2.2.2 0241 0x80000001 0xc49f 1
Link-LSA (Interface GigabitEthernet0/0)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum Prefix
0.0.0.1 1.1.1.1 0376 0x80000001 0x829f 1
Router-LSA (Area 0.0.0.1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum Link
0.0.0.0 1.1.1.1 0236 0x80000002 0xd839 1
0.0.0.0 2.2.2.2 0237 0x80000002 0xbd4f 1
Network-LSA (Area 0.0.0.1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum
0.0.0.2 1.1.1.1 0236 0x80000001 0x8492
Inter-Area-Prefix-LSA (Area 0.0.0.1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum
0.0.0.1 2.2.2.2 0162 0x80000001 0xc8ff
0.0.0.0 2.2.2.2 0241 0x80000001 0xb01c
Intra-Area-Prefix-LSA (Area 0.0.0.1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum Prefix Reference
0.0.0.1 1.1.1.1 0231 0x80000002 0x9007 1 Network-LSA
0.0.0.0 1.1.1.1 0236 0x80000003 0xbcda 1 Router-LSA
Table 147 Command output
|
Field |
Description |
|
Origin Router |
Originating router. |
|
Age |
Age of LSAs. |
|
SeqNumber |
LSA sequence number. |
|
Checksum |
LSA checksum. |
|
Prefix |
Number of prefixes. |
|
Link |
Number of links. |
|
Reference |
Type of referenced LSA. |
# Display Link LSA information in the LSDB.
<Sysname> display ospfv3 lsdb
OSPFv3 Process 1 with Router ID 1.1.1.1
Link-LSA (Interface GigabitEthernet0/1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum Prefix
0.0.0.2 1.1.1.1 0345 0x80000001 0x4ad7 1
0.0.0.2 2.2.2.2 0241 0x80000001 0xc49f 1
Link-LSA (Interface GigabitEthernet0/0)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum Prefix
0.0.0.1 1.1.1.1 0376 0x80000001 0x829f 1
Router-LSA (Area 0.0.0.1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum Link
0.0.0.0 1.1.1.1 0236 0x80000002 0xd839 1
0.0.0.0 2.2.2.2 0237 0x80000002 0xbd4f 1
Network-LSA (Area 0.0.0.1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum
0.0.0.2 1.1.1.1 0236 0x80000001 0x8492
Inter-Area-Prefix-LSA (Area 0.0.0.1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum
0.0.0.1 2.2.2.2 0162 0x80000001 0xc8ff
0.0.0.0 2.2.2.2 0241 0x80000001 0xb01c
Intra-Area-Prefix-LSA (Area 0.0.0.1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum Prefix Reference
0.0.0.1 1.1.1.1 0231 0x80000002 0x9007 1 Network-LSA
0.0.0.0 1.1.1.1 0236 0x80000003 0xbcda 1 Router-LSA
<Sysname>display ospfv3 lsdb link
OSPFv3 Process 1 with Router ID 1.1.1.1
Link-LSA (Interface GigabitEthernet0/1)
-------------------------------------------------------------------------
LS age : 1026
LS type : Link-LSA
Link state ID : 0.0.0.2
Originating router : 1.1.1.1
LS seq number : 0x80000001
Checksum : 0x4AD7
Length : 56
Priority : 1
Options : 0x000013 (-|R|-|x|E|V6)
Link-Local address : FE80::42EA:AAFF:FE3F:306
Number of prefixes : 1
Prefix : 2001:1::/64
Prefix options : 0 (-|-|x|-|-)
LS age : 922
LS type : Link-LSA
Link state ID : 0.0.0.2
Originating router : 2.2.2.2
LS seq number : 0x80000001
Checksum : 0xC49F
Length : 56
Priority : 1
Options : 0x000013 (-|R|-|x|E|V6)
Link-Local address : FE80::42EA:A2FF:FE03:106
Number of prefixes : 1
Prefix : 2001:1::/64
Prefix options : 0 (-|-|x|-|-)
Link-LSA (Interface GigabitEthernet0/0)
-------------------------------------------------------------------------
LS age : 1057
LS type : Link-LSA
Link state ID : 0.0.0.1
Originating router : 1.1.1.1
LS seq number : 0x80000001
Checksum : 0x829F
Length : 56
Priority : 1
Options : 0x000013 (-|R|-|x|E|V6)
Link-Local address : FE80::42EA:AAFF:FE3F:305
Number of prefixes : 1
Prefix : 2001:3::/64
Prefix options : 0 (-|-|x|-|-)
Table 148 Command output
|
Field |
Description |
|
LS age |
Age of LSA. |
|
LS type |
Type of LSA. |
|
Link state ID |
Link state ID. |
|
Originating router |
Originating router. |
|
LS seq number |
LSA sequence number. |
|
Checksum |
LSA checksum. |
|
Length |
LSA length. |
|
Priority |
Router priority. |
|
Options |
Options. |
|
Link-Local address |
Link-local address. |
|
Number of prefixes |
Number of prefixes. |
|
Prefix |
Address prefix. |
|
Prefix options |
Prefix options. |
# Display LSA statistics.
<System> display ospfv3 lsdb statistics
OSPFv3 Process 1 with Router ID 1.1.1.1
-------------------------------------------------------------------------
Area ID Router Network IntePre InteRou IntraPre NSSA
0.0.0.1 2 0 0 0 2 0
0.0.0.3 1 0 0 0 1 1
Total 3 0 0 0 3 1
-------------------------------------------------------------------------
Link Grace ASE
Total 4 0 0
Table 149 Command output
|
Field |
Description |
|
Area ID |
Area ID. |
|
Router |
Number of Type-1 LSAs. |
|
Network |
Number of Type-2 LSAs. |
|
IntePre |
Number of Type-3 LSAs. |
|
InteRou |
Number of Type-4 LSAs. |
|
IntraPre |
Number of Type-9 LSAs. |
|
NSSA |
Number of Type-7 LSAs. |
|
Link |
Total number of Type-8 LSAs. |
|
Grace |
Number of Type-11 LSAs. |
|
ASE |
Total number of Type-5 LSAs. |
# Display detailed OSPFv3 LSDB information.
<Sysname> display ospfv3 lsdb verbose
OSPFv3 Process 1 with Router ID 1.1.1.1
Link-LSA (Interface GigabitEthernet0/1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum Prefix
0.0.0.2 1.1.1.1 0380 0x80000003 0x46d9 1
SendCnt: 0 RxmtCnt: 0 Status: Normal
0.0.0.2 2.2.2.2 0448 0x80000003 0xc0a1 1
SendCnt: 0 RxmtCnt: 0 Status: Normal
Link-LSA (Interface GigabitEthernet0/0)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum Prefix
0.0.0.1 1.1.1.1 0415 0x80000003 0x7ea1 1
SendCnt: 0 RxmtCnt: 0 Status: Normal
Router-LSA (Area 0.0.0.1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum Link
0.0.0.0 1.1.1.1 0275 0x80000004 0xd43b 1
SendCnt: 0 RxmtCnt: 0 Status: Normal
0.0.0.0 2.2.2.2 0446 0x80000004 0xb951 1
SendCnt: 0 RxmtCnt: 0 Status: Normal
Network-LSA (Area 0.0.0.1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum
0.0.0.2 1.1.1.1 0275 0x80000003 0x8094
SendCnt: 0 RxmtCnt: 0 Status: Normal
Inter-Area-Prefix-LSA (Area 0.0.0.1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum
0.0.0.1 2.2.2.2 0370 0x80000003 0xc402
SendCnt: 0 RxmtCnt: 0 Status: Normal
0.0.0.0 2.2.2.2 0450 0x80000003 0xac1e
SendCnt: 0 RxmtCnt: 0 Status: Normal
Intra-Area-Prefix-LSA (Area 0.0.0.1)
-------------------------------------------------------------------------
Link state ID Origin router Age SeqNumber Checksum Prefix Reference
0.0.0.1 1.1.1.1 0269 0x80000004 0x8c09 1 Network-LSA
SendCnt: 0 RxmtCnt: 0 Status: Normal
0.0.0.0 1.1.1.1 0275 0x80000005 0xb8dc 1 Router-LSA
SendCnt: 0 RxmtCnt: 0 Status: Normal
Table 150 Command output
|
Field |
Description |
|
SendCnt |
Number of interfaces to send the LSA. |
|
RxmtCnt |
Number of LSAs in the link state retransmission list. |
|
Status |
LSA status: · Normal. · Delayed. · Maxage routed—The LSA has reached its maximum age. · Self originated. · Stale—A self-originated LSA is received during the GR process. |
display ospfv3 nexthop
Use display ospfv3 nexthop to display OSPFv3 next hop information.
Syntax
display ospfv3 [ process-id ] nexthop
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays next hop information for all OSPFv3 processes.
Examples
# Display next hop information for OSPFv3 process 1.
<Sysname> display ospfv3 1 nexthop
OSPFv3 Process 1 with Router ID 1.1.1.1
Nexthop : FE80::20C:29FF:FED7:F308 Interface: GE1/0/2
RefCount: 4 Status : Valid
NbrID : 1.1.1.1 NbrIntID : 21
Nexthop : FE80::20C:29FF:FED7:F312 Interface: GE1/0/3
RefCount: 3 Status : Valid
NbrID : 1.1.1.1 NbrIntID : 38
Table 151 Command output
|
Field |
Description |
|
Nexthop |
Next hop address. |
|
Interface |
Output interface. |
|
RefCount |
Reference count (routes that use the next hop). |
|
Status |
Next hop status: valid or invalid. |
|
NbrId |
Neighbor router ID. |
|
NbrIntID |
Neighbor interface ID. |
display ospfv3 non-stop-routing
Use display ospfv3 non-stop-routing to display OSPFv3 NSR information.
Syntax
display ospfv3 [ process-id ] non-stop-routing
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays OSPFv3 NSR information for all OSPFv3 processes.
Usage guidelines
The following matrix shows the command and hardware compatibility:
|
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28/3600-51 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
· In standalone mode: No · In IRF mode: Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Command compatibility |
|
MSR810-LM-GL |
No |
|
MSR810-W-LM-GL |
No |
|
MSR830-6EI-GL |
No |
|
MSR830-10EI-GL |
No |
|
MSR830-6HI-GL |
No |
|
MSR830-10HI-GL |
No |
|
MSR2600-6-X1-GL |
No |
|
MSR3600-28-SI-GL |
No |
Examples
# Display OSPFv3 NSR information.
<Sysname> display ospfv3 non-stop-routing
OSPFv3 Process 1 with Router ID 3.3.3.3
Nonstop Routing capability: Enabled
Upgrade phase : Normal
Table 152 Command output
|
Field |
Description |
|
Nonstop Routing capability |
NSR status: enabled or disabled. |
|
Upgrade phase |
NSR phase: · Normal—Normal status. · Preparation—Upgrade preparation phase. · Smooth—Upgrade phase. · Precalculation—Route pre-calculation phase. · Calculation—Route calculation phase. · Redistribution—Route redistribution phase. |
display ospfv3 peer
Use display ospfv3 peer to display information about OSPFv3 neighbors.
Syntax
display ospfv3 [ process-id ] [ area area-id ] peer [ [ interface-type interface-number ] [ verbose ] | peer-router-id | statistics ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify a process, this command displays neighbor information for all processes.
area area-id: Specifies an area by its ID, an IPv4 address or a decimal integer in the range of 0 to 4294967295 that is translated into the IPv4 address format. If you do not specify an area, this command displays neighbor information for all areas.
interface-type interface-number: Specifies an interface by its type and number.
verbose: Displays detailed neighbor information.
peer-router-id: Specifies a neighbor.
statistics: Displays OSPFv3 neighbor statistics.
Usage guidelines
If you do not specify an interface and a neighbor, this command displays neighbor information for all interfaces.
Examples
# Display neighbor information for OSPFv3 process 1 on an interface.
<Sysname> display ospfv3 1 peer gigabitethernet 1/0/1
OSPFv3 Process 1 with Router ID 1.1.1.1
Area: 0.0.0.1
-------------------------------------------------------------------------
Router ID Pri State Dead-Time InstID Interface
2.2.2.2 1 Full/DR 00:00:33 0 GE1/0/1
Table 153 Command output
|
Field |
Description |
|
Router ID |
Neighbor router ID. |
|
Pri |
Neighboring router priority. |
|
State |
Neighbor state. |
|
Dead-Time |
Dead time remained. |
|
Inst ID |
Instance ID. |
|
Interface |
Interface connected to the neighbor. |
# Display detailed neighbor information for OSPFv3 process 1 on an interface.
<Sysname> display ospfv3 1 peer gigabitethernet 1/0/2 verbose
OSPFv3 Process 1 with Router ID 1.1.1.1
Area 0.0.0.1 interface GE1/0/2's neighbors
Router ID: 2.2.2.2 Address: fe80::200:5eff:fe00:100
State: Full Mode: Nbr is master Priority: 1
DR: 2.2.2.2 BDR: None MTU: 1500
Options is 0x000013 (-|R|-|x|E|V6)
Dead timer due in 00:00:38
Neighbor is up for 00:19:07
Neighbor state change count: 120
Database Summary List 0
Link State Request List 0
Link State Retransmission List 3
Neighbor interface ID: 8037
GR state: Normal
Grace period: 0 Grace period timer: Off
DD Rxmt Timer: Off LS Rxmt Timer: On
Table 154 Command output
|
Description |
|
|
Router ID |
Neighbor router ID. |
|
Address |
Link-local address of the interface. |
|
State |
Neighbor state. |
|
Mode |
Neighbor mode for LSDB synchronization. |
|
Priority |
Neighboring router priority. |
|
DR |
DR on the interface's network segment. |
|
BDR |
BDR on the interface's network segment. |
|
MTU |
Interface MTU. |
|
Options |
LSA options: · DC—The originating router supports OSPFv3 over on-demand circuits. · R—Whether the originating router is an active router. · N—Whether the originating router supports NSSA LSAs. · x—Reserved. · E—Whether the originating router can receive AS External LSAs. · V6—Whether the originating router takes part in IPv6 route calculation. |
|
Dead timer due in 33 sec |
This dead timer will expire in 33 seconds. |
|
Neighbor is up for 00:24:19 |
The neighbor has been up for 00:24:19. |
|
Neighbor state change count |
Count of neighbor state changes. |
|
Database Summary List |
Number of LSAs sent in DD packet. |
|
Link State Request List |
Number of LSAs in the link state request list. |
|
Link State Retransmission List |
Number of LSAs in the link state retransmission list. |
|
Neighbor interface ID |
Interface ID of the neighbor. |
|
GR state |
GR state: · Normal—GR is not in progress. · Doing GR—Acting as the GR restarter. · Complete GR. · Helper—Acting as the GR helper. |
|
Grace period |
Grace-LSA sending interval. |
|
Grace period timer |
Grace-LSA sending interval timer. |
|
DD Rxmt Timer |
DD packet retransmission timer. |
|
LS Rxmt Timer |
LSU retransmission timer. |
# Display OSPFv3 neighbor statistics.
<Sysname> display ospfv3 peer statistics
OSPFv3 Process 1 with Router ID 1.1.1.1
-------------------------------------------------------------------------
Area ID Down Attempt Init 2-Way ExStart Exchange Loading Full Total
0.0.0.0 0 0 0 0 0 0 0 1 1
Total 0 0 0 0 0 0 0 1 1
Table 155 Command output
|
Field |
Description |
|
Area ID |
Area ID. |
|
Down |
In this state, neighbor initial state, the router has not received any information from a neighboring router for a period of time. |
|
Attempt |
This state is available only in an NBMA network. In this state, the OSPFv3 router has not received any information from a neighbor for a period. The router can send Hello packets at a longer interval to keep the neighbor relationship. |
|
Init |
In this state, the device received a Hello packet from the neighbor but the packet contains no router ID of the neighbor. Mutual communication is not setup. |
|
2-Way |
Mutual communication between the router and its neighbor is available. DR/BDR election is finished under this state (or higher). |
|
ExStart |
In this state, the router decides on the initial DD sequence number and active/standby relationship of the two parties. |
|
Exchange |
In this state, the router exchanges DD packets with the neighbor. |
|
Loading |
In this state, the router sends LSRs to request the neighbor for needed LSAs. |
|
Full |
LSDB synchronization has been accomplished between neighbors. |
|
Total |
Total number of neighbors under the same state. |
display ospfv3 request-queue
Use display ospfv3 request-queue to display OSPFv3 request list information.
Syntax
display ospfv3 [ process-id ] [ area area-id ] request-queue [ interface-type interface-number ] [ neighbor-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify an OSPFv3 process, this command displays OSPFv3 request list information for all OSPFv3 processes.
area area-id: Specifies an area by its ID, an IPv4 address or a decimal integer in the range of 0 to 4294967295 that is translated into the IPv4 address format. If you do not specify an OSPFv3 area, this command displays OSPFv3 request list information for all areas.
interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays OSPFv3 request list information for all interfaces.
neighbor-id: Specifies a neighbor's router ID. If you do not specify a neighbor, this command displays OSPFv3 request list information for all OSPFv3 neighbors.
Examples
# Display OSPFv3 request list information.
<Sysname> display ospfv3 request-queue
OSPFv3 Process 1 with Router ID 1.1.1.1
Area: 0.0.0.0
Interface GigabitEthernet1/0/1
-------------------------------------------------------------------------
Nbr-ID 1.3.3.3 Request List
Type LinkState ID AdvRouter SeqNum Age CkSum
0x4005 0.0.34.127 1.3.3.3 0x80000001 0027 0x274d
0x4005 0.0.34.128 1.3.3.3 0x80000001 0027 0x2d45
0x4005 0.0.34.129 1.3.3.3 0x80000001 0027 0x333d
0x4005 0.0.34.130 1.3.3.3 0x80000001 0027 0x3935
Table 156 Command output
|
Field |
Description |
|
Area |
Area ID. |
|
Interface |
Interface type and sequence number. |
|
Nbr-ID |
Neighbor ID. |
|
Request list |
Request list information. |
|
Type |
LSA type. |
|
LinkState ID |
Link state ID. |
|
AdvRouter |
Advertising router. |
|
SeqNum |
LSA sequence number. |
|
Age |
LSA age. |
|
CkSum |
Checksum. |
display ospfv3 retrans-queue
Use display ospfv3 retrans-queue to display retransmission list information.
Syntax
display ospfv3 [ process-id ] [ area area-id ] retrans-queue [ interface-type interface-number ] [ neighbor-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify an OSPFv3 process, this command displays retransmission list information for all OSPFv3 processes.
area area-id: Specifies an area by its ID, an IPv4 address or a decimal integer in the range of 0 to 4294967295 that is translated into the IPv4 address format. If you do not specify an OSPFv3 area, this command displays retransmission list information for all OSPFv3 areas.
interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays retransmission list information for all interfaces.
neighbor-id: Specifies a neighbor's router ID. If you do not specify a neighbor, this command displays retransmission list information for all neighbors.
Examples
# Display OSPFv3 retransmission list information.
<Sysname> display ospfv3 retrans-queue
OSPFv3 Process 1 with Router ID 1.1.1.1
Area: 0.0.0.0
Interface GigabitEthernet1/0/1
-------------------------------------------------------------------------
Nbr-ID 1.2.2.2 Retransmit List
Type LinkState ID AdvRouter SeqNum Age CkSum
0x2009 0.0.0.0 1.3.3.3 0x80000001 3600 0x49fb
Table 157 Command output
|
Field |
Description |
|
Area |
Area ID. |
|
Interface |
Interface type and sequence number. |
|
Nbr-ID |
Neighbor ID. |
|
Retransmit List |
Retransmission list information. |
|
Type |
LSA type. |
|
LinkState ID |
Link state ID. |
|
AdvRouter |
Advertising router. |
|
SeqNum |
LSA sequence number. |
|
Age |
LSA age. |
|
CkSum |
Checksum. |
display ospfv3 routing
Use display ospfv3 routing to display OSPFv3 route information.
Syntax
display ospfv3 [ process-id ] routing [ ipv6-address prefix-length ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays the OSPFv3 route information for all processes.
ipv6-address prefix-length: Specifies an IPv6 address. The ipv6-address argument specifies an IPv6 prefix. The prefix-length argument specifies a prefix length in the range of 0 to 128.
Examples
# Display OSPFv3 routing information.
<Sysname> display ospfv3 routing
OSPFv3 Process 1 with Router ID 9.9.9.9
-------------------------------------------------------------------------
I - Intra area route, E1 - Type 1 external route, N1 - Type 1 NSSA route
IA - Inter area route, E2 - Type 2 external route, N2 - Type 2 NSSA route
* - Selected route
*Destination: 3::3/128
Type : I Area : 0.0.0.1
AdvRouter : 1.1.1.1 Preference : 0
NibID : 0x130000001 Cost : 10
Interface : GE1/0/1 BkInterface: GE1/0/2
Nexthop : FE80::20C:29FF:FED4:7171
BkNexthop : FE80:1:1:1
*Destination: 3::4/128
Type : I Area : 0.0.0.1
AdvRouter : 1.1.1.1 Preference : 0
NibID : 0x130000001 Cost : 10
Interface : GE1/0/1 BkInterface: GE1/0/2
Nexthop : FE80::10C:29AF:FE97:1210
BkNexthop : FE80:1:1:1
*Destination: 3::5/128
Type : I Area : 0.0.0.1
AdvRouter : 1.1.1.1 Preference : 0
NibID : 0x130000001 Cost : 10
Interface : GE1/0/1 BkInterface: GE1/0/2
Nexthop : FE80::10BC:28AF:FE97:1008
BkNexthop : FE80:1:1:1
Total: 3
Intra area: 3 Inter area: 0 ASE: 0 NSSA: 0
Table 158 Command output
|
Field |
Description |
|
Destination |
Destination network segment. |
|
Type |
Route type. |
|
Area |
Area ID. |
|
AdvRouter |
Advertising router. |
|
Preference |
OSPFv3 route preference. |
|
NibID |
Next hop ID. |
|
Cost |
Route cost value. |
|
Interface |
Output interface. |
|
BkInterface |
Backup output interface. |
|
Nexthop |
Primary next hop IP address. |
|
BkNexthop |
Backup next hop IP address. |
|
Nexthop |
Next hop address. |
|
Interface |
Output interface. |
|
AdvRouter |
Advertising router. |
|
Area |
Area ID. |
|
Tag |
Tag of external routes. |
|
Preference |
Route preference. |
|
Total |
Total number of routes. |
|
Intra area |
Number of intra-area routes. |
|
Inter area |
Number of inter-area routes. |
|
ASE |
Number of Type-5 external routes. |
|
NSSA |
Number of Type-7 external routes. |
display ospfv3 spf-tree
Use display ospfv3 spf-tree to display OSPFv3 topology information.
Syntax
display ospfv3 [ process-id ] [ area area-id ] spf-tree [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays topology information for all OSPFv3 processes.
area area-id: Specifies an OSPFv3 area by its ID. The area ID is an IP address or a decimal integer in the range of 0 to 4294967295 that is translated into the IP address format. If you do not specify this option, the command displays topology information for all OSPFv3 areas.
verbose: Displays detailed OSPFv3 topology information. If you do not specify this keyword, the command displays brief OSPFv3 topology information.
Examples
# Display brief topology information for Area 0 in OSPFv3 process 1.
<Sysname> display ospfv3 1 area 0 spf-tree
OSPFv3 Process 1 with Router ID 1.1.1.1
Flags: S-Node is on SPF tree R-Node is directly reachable
I-Node or Link is init D-Node or Link is to be deleted
P-Neighbor is parent A-Node is in candidate list
C-Neighbor is child H-Nexthop changed
N-Link is a new path V-Link is involved
Area: 0.0.0.0 Shortest Path Tree
SPFNode Type Flag SPFLink Type Cost Flag
>1.1.1.1 Router S R
-->2.2.2.2 RT2RT 1 C
-->2.2.2.2 RT2RT 1 P
Table 159 Command output
|
Field |
Description |
|
SPFNode |
SPF node, represented by the advertising router ID. Node type: · Network—Network node. · Router—Router node. Node flag: · I—The node is in initialization state. · A—The node is on the candidate list. · S—The node is on the SPF tree. · R—The node is directly connected to the root node. · D—The node is to be deleted. |
|
SPFLink |
SPF link, representing the advertising router ID. Link type: · RT2RT—Router to router. · NET2RT—Network to router. · RT2NET—Router to network. Link flag: · I—The link is in initialization state. · P—The peer is the parent node. · C—The peer is the child node. · D—The link is to be deleted. · H—The next hop is changed. · V—When the peer node is deleted or added, the peer node is not on the SPF tree or is deleted. · N—The link is newly added, and both end nodes are on the SPF tree. · L—The link is on the area change list. |
# Display detailed topology information for Area 0 in OSPFv3 process 1.
<Sysname> display ospfv3 1 area 0 spf-tree verbose
OSPFv3 Process 1 with Router ID 1.1.1.1
Flags: S-Node is on SPF tree R-Node is directly reachable
I-Node or Link is init D-Node or Link is to be deleted
P-Neighbor is parent A-Node is in candidate list
C-Neighbor is child H-Nexthop changed
N-Link is a new path V-Link is involved
Area: 0.0.0.0 Shortest Path Tree
>SPFNode[0]
AdvID : 1.1.1.1 LsID : 0.0.0.0
NodeType : Router Distance : 1
NodeFlag : S R
Nexthop count: 1
-->NbrID : 1.1.1.1 NbrIntID : 21
Interface : GE1/0/2 NhFlag : Valid
BkInterface: GE1/0/3 RefCount : 4
Nexthop : FE80::20C:29FF:FED7:F308
BkNexthop : FE80::4
SPFLink count: 1
-->AdvID : 1.1.1.1 LsID : 0.0.0.0
IntID : 232 NbrIntID : 465
NbrID : 2.2.2.2 LinkType : RT2RT
LinkCost : 1 LinkNewCost: 1
LinkFlag : C NexthopCnt : 0
ParentLink count: 1
-->AdvID : 1.1.1.1 LsID : 0.0.0.0
IntID : 215 NbrIntID : 466
NbrID : 2.2.2.2 LinkType : RT2RT
LinkCost : 1 LinkNewCost: 1
LinkFlag : P NexthopCnt : 0
Table 160 Command output
|
Field |
Description |
|
SPFNode |
SPF node. |
|
AdvID |
ID of the advertising router. |
|
LsID |
Link state ID. |
|
NodeType |
Node type. |
|
Distance |
Cost to the root node. |
|
NodeFlag |
Node flag. |
|
Nexthop count |
Number of next hops. |
|
NbrID |
Neighbor router ID. |
|
NbrIntID |
Neighbor interface ID. |
|
Interface |
Output interface. |
|
NhFlag |
Next hop flag: valid or invalid. |
|
BkInterface |
Backup output interface. |
|
RefCount |
Reference count (routes that use the backup next hop). |
|
Nexthop |
Next hop. |
|
BkNexthop |
Backup next hop. |
|
SPFLink count |
Number of SPF links. |
|
IntID |
Interface ID. |
|
LinkType |
Link type: · RT2RT—Router to router. · NET2RT—Network to router. · RT2NET—Router to network. |
|
LinkCost |
Link cost. |
|
LinkNewCost |
New link cost. |
|
LinkFlag |
Link flag: · I—The link is in initialization state. · P—The peer is the parent node. · C—The peer is the child node. · D—The link is to be deleted. · H—The next hop is changed. · V—When the peer node is deleted or added, the peer node is not on the SPF tree or is deleted. · N—The link is newly added, and both end nodes are on the SPF tree. · L—The link is on the area change list. |
|
NexthopCnt |
Number of next hops. |
|
ParentLinkCnt |
Number of parent links. |
display ospfv3 statistics
Use display ospfv3 statistics to display OSPFv3 statistics.
Syntax
display ospfv3 [ process-id ] statistics [ error | packet [ interface-type interface-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays OSPFv3 statistics for all processes.
error: Displays error statistics. If you do not specify this keyword, the command displays OSPFv3 packet, LSA, and route statistics.
packet: Displays packet statistics.
interface-type interface-number: Specifies an interface by its type and number. If you do not specify this argument, the command displays statistics for all interfaces.
Examples
# Display OSPFv3 statistics.
<Sysname> display ospfv3 statistics
OSPFv3 Process 1 with Router ID 1.1.1.1
Packet Statistics
----------------------------------------------------------
Type Recv Send
Hello 1746 1284
DB Description 505 941
Ls Req 252 136
Ls Upd 851 1553
Ls Ack 416 450
Local Originated LSAs Statistics
----------------------------------------------------------
Type Count
Router-LSA 192
Network-LSA 0
Inter-Area-Prefix-LSA 0
Inter-Area-Router-LSA 0
AS-external-LSA 0
NSSA-LSA 0
Link-LSA 10
Intra-Area-Prefix-LSA 112
Grace-LSA 0
Unknown-LSA 0
Total 314
Routes Statistics
----------------------------------------------------------
Type Count
Intra Area 0
Inter Area 0
ASE 0
NSSA 0
Table 161 Command output
|
Field |
Description |
|
Packet Statistics |
Statistics about inbound and outbound packets. |
|
Hello |
Hello packet. |
|
DB Description |
DB description packet. |
|
Ls Req |
Link state request packet. |
|
Ls Upd |
Link state update packet. |
|
Ls Ack |
Link state acknowledgment packet. |
|
Local Originated LSAs Statistics |
Statistics about generated LSAs. |
|
Router-LSA |
Number of Type-1 LSAs. |
|
Network-LSA |
Number of Type-2 LSAs. |
|
Inter-Area-Prefix-LSA |
Number of Type-3 LSAs. |
|
Inter-Area-Router-LSA |
Number of Type-4 LSAs. |
|
AS-external-LSA |
Number of Type-5 LSAs. |
|
NSSA-LSA |
Number of Type-7 LSAs. |
|
Link-LSA |
Number of Type-8 LSAs. |
|
Intra-Area-Prefix-LSA |
Number of Type-9 LSAs. |
|
Grace-LSA |
Number of Type-11 LSAs. |
|
Unknown-LSA |
Number of Unknown-LSAs. |
|
Total |
Total number. |
|
Routes Statistics |
Number of routes. |
|
Intra Area |
Intra-area routes. |
|
Inter Area |
Inter-area routes. |
|
ASE |
Type-5 external routes. |
|
NSSA |
Type-7 external routes. |
# Display OSPFv3 error statistics.
<Sysname> display ospfv3 statistics error
OSPFv3 Process 1 with Router ID 1.1.1.1
0 : Transmit error 0 : Neighbor state low
0 : Packet too small 0 : Bad version
0 : Bad checksum 0 : Unknown neighbor
0 : Bad area ID 0 : Bad packet
0 : Packet dest error 0 : Inactive area packet
0 : Router ID confusion 0 : Bad virtual link
0 : HELLO: Hello-time mismatch 0 : HELLO: Dead-time mismatch
0 : HELLO: Ebit option mismatch 0 : DD: Ebit option mismatch
0 : DD: Unknown LSA type 0 : DD: MTU option mismatch
0 : REQ: Empty request 0 : REQ: Bad request
0 : UPD: LSA checksum bad 0 : UPD: Unknown LSA type
0 : UPD: Less recent LSA 0 : UPD: LSA length bad
0 : UPD: LSA AdvRtr id bad 0 : ACK: Bad ack packet
0 : ACK: Invalid ack 0 : Interface down
0 : Multicast incapable
Table 162 Command output
|
Field |
Description |
|
Transmit error |
Packets with error when being transmitted. |
|
Neighbor state low |
Packets received in low neighbor state. |
|
Packet too small |
Packets too small in length. |
|
Bad version |
Packets with wrong version. |
|
Bad checksum |
Packets with wrong checksum. |
|
Unknown neighbor |
Packets received from unknown neighbors. |
|
Bad area ID |
Packets with invalid area ID. |
|
Bad packet |
Packets illegal. |
|
Packet dest error |
Packets with wrong destination addresses. |
|
Inactive area packet |
Packets received in inactive areas. |
|
Router ID confusion |
Packets with duplicate router ID. |
|
Bad virtual link |
Packets on wrong virtual links. |
|
HELLO: Hello-time mismatch |
Hello packets with mismatched hello timer. |
|
HELLO: Dead-time mismatch |
Hello packets with mismatched dead timer. |
|
HELLO: Ebit option mismatch |
Hello packets with mismatched E-bit in the option field. |
|
DD: Ebit option mismatch |
DD packets with mismatched E-bit in the option field. |
|
DD: Unknown LSA type |
DD packets with unknown LSA type. |
|
DD: MTU option mismatch |
DD packets with mismatched MTU. |
|
REQ: Empty request |
LSR packets with no request information. |
|
REQ: Bad request |
Bad LSR packets. |
|
UPD: LSA checksum bad |
LSU packets with wrong LSA checksum. |
|
UPD: Unknown LSA type |
LSU packets with unknown LSA type. |
|
UPD: Less recent LSA |
LSU packets without the most recent LSA. |
|
UPD: LSA length bad |
LSU packets with wrong LSA length. |
|
UPD: LSA AdvRtr id bad |
LSU packets with wrong LSA advertising router. |
|
ACK: Bad ack packet |
Bad LSAck packets for LSU packets. |
|
ACK: Invalid ack |
Invalid LSAck packets. |
|
Interface down |
Shutdown times of the interface. |
|
Multicast incapable |
Failures to join the multicast group. |
# Display OSPFv3 packet statistics for all processes and interfaces.
<Sysname> display ospfv3 statistics packet
OSPFv3 Process 1 with Router ID 1.1.1.1
Hello DD LSR LSU ACK Total
Input : 8727 128 28 1584 929 11396
Output: 8757 159 86 987 1513 11502
Area: 0.0.0.0
Area: 0.0.0.1
Interface: GigabitEthernet1/0/1
DD LSR LSU ACK Total
Input : 16 0 45 7 68
Output: 17 1 7 44 69
Interface: GigabitEthernet1/0/2
DD LSR LSU ACK Total
Input : 41 13 720 719 1493
Output: 54 41 750 713 1558
Table 163 Command output
|
Field |
Description |
|
Total |
Total number of packets. |
|
Input |
Number of received packets. |
|
Output |
Number of sent packets. |
|
Area |
Area ID. |
|
Interface |
Interface name. |
display ospfv3 vlink
Use display ospfv3 vlink to display OSPFv3 virtual link information.
Syntax
display ospfv3 [ process-id ] vlink
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays the OSPFv3 virtual link information for all OSPFv3 processes.
Examples
# Display OSPFv3 virtual link information.
<Sysname> display ospfv3 vlink
OSPFv3 Process 1 with Router ID 1.1.1.1
Virtual-link Neighbor-id: 12.2.2.2, Neighbor-state: Full
Interface: 2348 (GigabitEthernet1/0/2), Instance-ID: 0
Local IPv6 address: 3:3333::12
Remote IPv6 address: 2:2222::12
Cost: 1 State: P-2-P Type: Virtual
Transit area: 0.0.0.1
Timers: Hello 10, Dead 40, Retransmit 5, Transmit Delay 1
IPsec profile name: profile001
Table 164 Command output
|
Field |
Description |
|
Virtual-link Neighbor-ID |
ID of the neighbor on the virtual link. |
|
Neighbor-State |
Neighbor state: Down, Init, 2-Way, ExStart, Exchange, Loading, or Full. |
|
Interface |
Number and name of the local interface on the virtual link. |
|
Cost |
Interface route cost. |
|
State |
Interface state. |
|
Type |
Virtual link. |
|
Transit Area |
Transit area ID. This field is displayed when a virtual link is present on the interface. |
|
Timers |
Values of OSPFv3 timers (in seconds): Hello, Dead, and Retransmit. |
|
Transmit Delay |
LSA transmission delay on the interface, in seconds. |
|
IPsec profile name |
IPsec profile applied to the virtual link. |
enable ipsec-profile
Use enable ipsec-profile to apply an IPsec profile to an OSPFv3 area.
Use undo enable ipsec-profile to remove the IPsec profile from the OSPFv3 area.
Syntax
enable ipsec-profile profile-name
undo enable ipsec-profile
Default
No IPsec profile is applied to an area.
Views
OSPFv3 area view
Predefined user roles
network-admin
Parameters
profile-name: Specifies an IPsec profile by its name, a case-insensitive string of 1 to 63 characters.
Usage guidelines
To protect routing information and prevent attacks, OSPFv3 can authenticate protocol packets by using an IPsec profile. For more information about IPsec profiles, see Security Configuration Guide.
Examples
# Apply IPsec profile profile001 to Area 0 in OSPFv3 process 1.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] area 0
[Sysname-ospfv3-1-area-0.0.0.0] enable ipsec-profile profile001
event-log
Use event-log to set the number of OSPFv3 logs.
Use undo event-log to remove the configuration.
Syntax
event-log { lsa-flush | peer | spf } size count
undo event-log { lsa-flush | peer | spf } size
Default
The number of LSA aging logs, neighbor logs, or route calculation logs is 10.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
lsa-flush: Specifies the number of LSA aging logs.
peer: Specifies the number of neighbor logs.
spf: Specifies the number of route calculation logs.
size count: Specifies the number of OSPFv3 logs, in the range of 0 to 65535.
Examples
# Set the number of route calculation logs to 50 in OSPFv3 process 100.
<Sysname> system-view
[Sysname] ospfv3 100
[Sysname-ospfv3-100] event-log spf size 50
fast-reroute (OSPFv3 view)
Use fast-reroute to configure OSPFv3 FRR.
Use undo fast-reroute to restore the default.
Syntax
fast-reroute { lfa [ abr-only ] | route-policy route-policy-name }
undo fast-reroute
Default
OSPFv3 FRR is disabled.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
lfa: Uses the LFA algorithm to calculate a backup next hop for all routes.
abr-only: Uses the next hop of the route to the ABR as the backup next hop.
route-policy route-policy-name: Uses a routing policy to designate a backup next hop. The route-policy-name argument is a case-sensitive string of 1 to 63 characters.
Usage guidelines
Do not use the fast-reroute lfa command together with the vlink-peer command.
Examples
# Enable FRR to calculate a backup next hop for all routes by using LFA algorithm in OSPFv3 process 1.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] fast-reroute lfa
filter (OSPFv3 area view)
Use filter to configure inbound/outbound Inter-Area-Prefix-LSA filtering on an ABR.
Use undo filter to remove the configuration.
Syntax
filter { ipv6-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } { export | import }
undo filter { export | import }
Default
Inter-Area-Prefix-LSAs are not filtered.
Views
OSPFv3 area view
Predefined user roles
network-admin
Parameters
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999 to filter inbound/outbound Inter-Area-Prefix-LSAs.
prefix-list prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter inbound/outbound Inter-Area-Prefix-LSAs.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter inbound/outbound Inter-Area-Prefix-LSAs.
export: Filters Inter-Area-Prefix-LSAs advertised to other areas.
import: Filters Inter-Area-Prefix-LSAs advertised into the local area.
Usage guidelines
This command applies only to an ABR.
Examples
# Use IPv6 prefix list my-prefix-list to filter inbound Inter-Area-Prefix-LSAs. Use IPv6 basic ACL 2000 to filter outbound Inter-Area-Prefix-LSAs in OSPFv3 Area 1.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] area 1
[Sysname-ospfv3-1-area-0.0.0.1] filter prefix-list my-prefix-list import
[Sysname-ospfv3-1-area-0.0.0.1] filter 2000 export
filter-policy export (OSPFv3 view)
Use filter-policy export to configure OSPFv3 to filter redistributed routes.
Use undo filter-policy export to remove the configuration.
Syntax
filter-policy { ipv6-acl-number | prefix-list prefix-list-name } export [ protocol [ process-id ] ]
undo filter-policy export [ protocol [ process-id ] ]
Default
Redistributed routes are not filtered.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999 to filter redistributed routes by destination address.
prefix-list prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter redistributed routes by destination address.
protocol: Filters routes redistributed from the specified routing protocol. If you do not specify this argument, the command filters all redistributed routes.
process-id: Specifies a process by its ID in the range of 1 to 65535. This argument is available only when the protocol argument is ripng, ospfv3, or isisv6.
Usage guidelines
To use an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL in one of the following ways:
· To deny/permit a route with the specified destination, use rule [ rule-id ] { deny | permit } ipv6 source sour sour-prefix.
· To deny/permit a route with the specified destination and prefix, use rule [ rule-id ] { deny | permit } ipv6 source sour sour-prefix destination dest dest-prefix.
The source keyword specifies the destination address of a route, and the destination keyword specifies the prefix of the route. The prefix must be contiguous. Otherwise, the configuration does not take effect.
Using the filter-policy export command filters only routes redistributed by the import-route command. If the import-route command is not configured to redistribute routes from other protocols and other OSPFv3 processes, the filter-policy export command does not take effect.
Examples
# Use IPv6 prefix list abc to filter redistributed routes.
<Sysname> system-view
[Sysname] ipv6 prefix-list abc permit 2002:1:: 64
[Sysname] ospfv3
[Sysname-ospfv3-1] filter-policy prefix-list abc export
# Configure IPv6 advanced ACL 3000 to permit only route 2001::1/128. Use ACL 3000 to filter redistributed routes.
<Sysname> system-view
[Sysname] acl ipv6 advanced 3000
[Sysname-acl-ipv6-adv-3000] rule 10 permit ipv6 source 2001::1 128 destination ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff 128
[Sysname-acl-ipv6-adv-3000] rule 100 deny ipv6
[Sysname-acl-ipv6-adv-3000] quit
[Sysname] ospfv3
[Sysname-ospfv3-1] filter-policy 3000 export
filter-policy import (OSPFv3 view)
Use filter-policy import to configure OSPFv3 to filter routes calculated using received LSAs.
Use undo filter-policy import to remove the configuration.
Syntax
filter-policy { ipv6-acl-number [ gateway prefix-list-name ] | prefix-list prefix-list-name [ gateway prefix-list-name ] | gateway prefix-list-name | route-policy route-policy-name } import
undo filter-policy import
Default
Routes calculated using received LSAs are not filtered.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999 to filter routes by destination.
gateway prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter routes by next hop. If you do not specify this option, the command does not filter routes by next hop.
prefix-list prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter routes by destination.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter received routes.
Usage guidelines
To use an advanced ACL (with a number from 3000 to 3999) in the command, configure the ACL in one of the following ways:
· To deny/permit a route with the specified destination, use rule [ rule-id ] { deny | permit } ipv6 source sour sour-prefix.
· To deny/permit a route with the specified destination and prefix, use rule [ rule-id ] { deny | permit } ipv6 source sour sour-prefix destination dest dest-prefix.
The source keyword specifies the destination address of a route, and the destination keyword specifies the prefix of the route. The prefix must be contiguous. Otherwise, the configuration does not take effect.
Using the filter-policy import command filters only routes computed by OSPFv3. Routes that fail to pass the filter are not added to the routing table.
Examples
# Use IPv6 prefix list abc to filter received routes.
<Sysname> system-view
[Sysname] ipv6 prefix-list abc permit 2002:1:: 64
[Sysname] ospfv3
[Sysname-ospfv3-1] filter-policy prefix-list abc import
# Configure IPv6 advanced ACL 3000 to permit only route 2001::1/128 to pass. Use ACL 3000 to filter received routes.
<Sysname> system-view
[Sysname] acl ipv6 advanced 3000
[Sysname-acl-ipv6-adv-3000] rule 10 permit ipv6 source 2001::1 128 destination ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff 128
[Sysname-acl-ipv6-adv-3000] rule 100 deny ipv6
[Sysname-acl-ipv6-adv-3000] quit
[Sysname] ospfv3
[Sysname-ospfv3-1] filter-policy 3000 import
graceful-restart enable
Use graceful-restart enable to enable the GR capability for OSPFv3.
Use undo graceful-restart enable to disable the GR capability for OSPFv3.
Syntax
graceful-restart enable [ global | planned-only ] *
undo graceful-restart enable
Default
The GR capability for OSPFv3 is disabled.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
global: Enables global GR. In global GR mode, a GR process can be completed only when all GR helpers exist. A GR process fails if a GR helper fails (for example, the interface connected to the GR helper goes down). If you do not specify this keyword, the command enables partial GR. In partial GR mode, a GR process can be completed as long as one GR helper exists.
planned-only: Enables planned GR only. If you do not specify this keyword, the command enables both planned GR and unplanned GR.
Usage guidelines
GR includes planned GR and unplanned GR.
· Planned GR—Manually restarts OSPFv3 or performs an active/standby switchover. Before OSPFv3 restart or active/standby switchover, the GR restarter sends Grace-LSAs to GR helpers.
· Unplanned GR—OSPFv3 restarts or an active/standby switchover occurs because of device failure. Before OSPFv3 restart or active/standby switchover, the GR restarter does not send Grace-LSAs to GR helpers.
OSPFv3 GR and OSPFv3 NSR are mutually exclusive. Do not configure the graceful-restart enable command and the non-stop-routing command at the same time.
To prevent service interruption after a master/backup switchover, a GR restarter running OSPFv3 must perform the following tasks:
· Keep the GR restarter forwarding entries stable during reboot.
· Establish all adjacencies and obtain complete topology information after reboot.
Examples
# Enable the GR capability for OSPFv3 process 1.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] graceful-restart enable
Related commands
graceful-restart helper enable
graceful-restart helper enable
Use graceful-restart helper enable to enable the GR helper capability for OSPFv3.
Use undo graceful-restart helper enable to disable the GR helper capability for OSPFv3.
Syntax
graceful-restart helper enable [ planned-only ]
undo graceful-restart helper enable
Default
The GR helper capability for OSPFv3 is enabled.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
planned-only: Enables only planned GR for the GR helper. If you do not specify this keyword, the command enables both planned GR and unplanned GR for the GR helper.
Usage guidelines
Upon receiving the Grace-LSA, the neighbors with the GR helper capability enter the helper mode (and are called GR helpers). Then, the GR restarter retrieves its adjacencies and LSDB with the help of the GR helpers.
Examples
# Enable the GR helper capability for OSPFv3 process 1.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] graceful-restart helper enable
Related commands
graceful-restart enable
graceful-restart helper strict-lsa-checking
Use graceful-restart helper strict-lsa-checking to enable strict LSA checking for the GR helper.
Use undo graceful-restart helper strict-lsa-checking to disable strict LSA checking for the GR helper.
Syntax
graceful-restart helper strict-lsa-checking
undo graceful-restart helper strict-lsa-checking
Default
Strict LSA checking for the GR helper is disabled.
Views
OSPFv3 view
Predefined user roles
network-admin
Usage guidelines
With GR helper enabled, when an LSA change on the GR helper is detected, the GR helper device exits the GR helper mode.
Examples
# Enable strict LSA checking for the GR helper in OSPFv3 process 1.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] graceful-restart helper strict-lsa-checking
Related commands
graceful-restart helper enable
graceful-restart interval
Use graceful-restart interval to set the GR restart interval.
Use undo graceful-restart interval to restore the default.
Syntax
graceful-restart interval interval
undo graceful-restart interval
Default
The GR restart interval is 120 seconds.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
interval: Specifies GR restart interval in the range of 40 to 1800 seconds.
Usage guidelines
For GR restart to succeed, the value of the GR restart interval cannot be smaller than the maximum OSPFv3 neighbor dead time of all the OSPFv3 interfaces.
Examples
# Set the GR restart interval for OSPFv3 process 1 to 100 seconds.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] graceful-restart interval 100
Related commands
ospfv3 timer dead
import-route (OSPFv3 view)
Use import-route to redistribute routes.
Use undo import-route to disable route redistribution.
Syntax
import-route protocol [ as-number ] [ process-id | all-processes | allow-ibgp ] [ allow-direct | cost cost-value | nssa-only | route-policy route-policy-name | tag tag | type type ] *
undo import-route protocol [ process-id | all-processes ]
Default
OSPFv3 route redistribution is disabled.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
protocol: Redistributes routes from the specified routing protocol.
as-number: Redistributes routes from an AS specified by its number in the range of 1 to 4294967295. This argument applies only to the bgp4+ protocol. If you do not specify this argument, this command redistributes all IPv6 EBGP routes. As a best practice, specify an AS number to prevent the system from redistributing excessive IPv6 EBGP routes.
process-id: Specifies the process ID of a routing protocol, in the range of 1 to 65536. The default is 1. This argument takes effect only when the protocol argument is isisv6, ospfv3, or ripng.
all-processes: Redistributes routes from all the processes of the specified routing protocol. This keyword takes effect only when the protocol argument is ripng, ospfv3, or isisv6.
allow-ibgp: Redistributes IBGP routes. It is available only when the protocol argument is bgp4+.
allow-direct: Redistributes the networks of the local interfaces enabled with the specified routing protocol. If you do not specify this keyword, the networks of the local interfaces are not redistributed. If you specify both the allow-direct keyword and the route-policy route-policy-name option, make sure the if-match rule defined in the routing policy does not conflict with the allow-direct keyword. For example, if you specify the allow-direct keyword, do not configure the if-match route-type rule for the routing policy. Otherwise, the allow-direct keyword does not take effect.
cost cost-value: Specifies a cost for redistributed routes, in the range of 1 to 16777214. The default is 1.
nssa-only: Limits the route advertisement to the NSSA area by setting the P-bit of Type-7 LSAs to 0. If you do not specify this keyword, the P-bit of Type-7 LSAs is set to 1. If the router acts as both an ASBR and an ABR and FULL state neighbors exist in the backbone area, the P-bit of Type-7 LSAs originated by the router is set to 0. This keyword applies to NSSA routers.
route-policy route-policy-name: Specifies a routing policy to filter redistributed routes. The route-policy-name argument is a case-sensitive string of 1 to 63 characters.
tag tag: Specifies a tag for external LSAs, in the range of 0 to 4294967295. If you do not specify this option, the tag specified by the default tag command applies.
type type: Specifies the type for redistributed routes, 1 or 2. The default is 2.
Usage guidelines
An external route is a route to a destination outside the OSPFv3 AS. External routes include the following types:
· Type-1 external routes—Have high credibility. The cost of Type-1 external routes is comparable with the cost of OSPFv3 internal routes. The cost of a Type-1 external route equals the cost from the router to the ASBR plus the cost from the ASBR to the external route's destination.
· Type-2 external routes—Have low credibility. OSPFv3 considers the cost from the ASBR to a Type-2 external route is much bigger than the cost from the ASBR to an OSPFv3 internal router. The cost of a Type-2 external route equals the cost from the ASBR to the Type-2 external route's destination.
The import-route command cannot redistribute default routes.
The import-route bgp4+ command redistributes only EBGP routes. The import-route bgp4+ allow-ibgp command redistributes both EBGP and IBGP routes, and might cause routing loops. Therefore, use it with caution.
The import-route nssa-only command redistributes AS-external routes in Type-7 LSAs only into the NSSA area.
Examples
# Configure OSPFv3 process 1 to redistribute routes from RIPng and specify the type as type 2 and cost as 50.
<Sysname> system-view
[Sysname] ospfv3
[Sysname-ospfv3-1] import-route ripng 10 type 2 cost 50
# Configure OSPFv3 process 100 to redistribute the routes discovered by OSPFv3 process 160.
<Sysname> system-view
[Sysname] ospfv3 100
[Sysname-ospfv3-100] import-route ospfv3 160
Related commands
default-route-advertise (OSPFv3 view)
log-peer-change
Use log-peer-change to enable logging for neighbor state changes.
Use undo log-peer-change to disable logging for neighbor state changes.
Syntax
log-peer-change
undo log-peer-change
Default
Logging for neighbor state changes is enabled.
Views
OSPFv3 view
Predefined user roles
network-admin
Usage guidelines
This feature enables the device to deliver logs about neighbor state changes to its information center. The information center processes logs according to user-defined output rules (whether and where to output logs). For more information about the information center, see Network Management and Monitoring Configuration Guide.
Examples
# Disable logging for neighbor state changes for OSPFv3 process 100.
<Sysname> system-view
[Sysname] ospfv3 100
[Sysname-ospfv3-100] undo log-peer-change
lsa-generation-interval
Use lsa-generation-interval to set the OSPFv3 LSA generation interval.
Use undo lsa-generation-interval to restore the default.
Syntax
lsa-generation-interval maximum-interval [ minimum-interval [ incremental-interval ] ]
undo lsa-generation-interval
Default
The maximum interval is 5 seconds, the minimum interval is 0 milliseconds, and the incremental interval is 0 milliseconds.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
maximum-interval: Specifies the maximum OSPFv3 LSA generation interval in the range of 1 to 60 seconds.
minimum-interval: Specifies the minimum OSPFv3 LSA generation interval in the range of 10 to 60000 milliseconds. The default is 0, which indicates that the minimum interval can be any value.
incremental-interval: Specifies the OSPFv3 LSA generation incremental interval in the range of 10 to 60000 milliseconds.
Usage guidelines
When network changes are infrequent, LSAs are generated at the minimum interval. If network changes become frequent, the LSA generation interval is incremented by the incremental interval × 2n-2 for each generation until the maximum interval is reached. The value n is the number of generation times.
The minimum interval and the incremental interval cannot be greater than the maximum interval.
Examples
# Set the maximum LSA generation interval to 2 seconds, minimum interval to 100 milliseconds, and incremental interval to 100 milliseconds.
<Sysname> system-view
[Sysname] ospfv3 100
[Sysname-ospfv3-100] lsa-generation-interval 2 100 100
Related commands
lsa-arrival-interval
maximum load-balancing (OSPFv3 view)
Use maximum load-balancing to set the maximum number of equal-cost multi-path (ECMP) routes.
Use undo maximum load-balancing to restore the default.
Syntax
maximum load-balancing number
undo maximum load-balancing
Default
The maximum number of OSPFv3 ECMP routes is 32.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of ECMP routes, in the range of 1 to 32. When the maximum number is 1, OSPFv3 does not perform load balancing.
Examples
# Set the maximum number of ECMP routes to 2.
<Sysname> system-view
[Sysname] ospfv3 100
[Sysname-ospfv3-100] maximum load-balancing 2
non-stop-routing
Use non-stop-routing to enable OSPFv3 NSR.
Use undo non-stop-routing to disable OSPFv3 NSR.
Syntax
non-stop-routing
undo non-stop-routing
Default
OSPFv3 NSR is disabled.
Views
OSPFv3 view
Predefined user roles
network-admin
Usage guidelines
The following matrix shows the command and hardware compatibility:
|
Hardware |
Command compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
No |
|
MSR 2630 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28/3600-51 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
· In standalone mode: No · In IRF mode: Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
· In standalone mode: No · In IRF mode: Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
Command compatibility |
|
MSR810-LM-GL |
No |
|
MSR810-W-LM-GL |
No |
|
MSR830-6EI-GL |
No |
|
MSR830-10EI-GL |
No |
|
MSR830-6HI-GL |
No |
|
MSR830-10HI-GL |
No |
|
MSR2600-6-X1-GL |
No |
|
MSR3600-28-SI-GL |
No |
This command takes effect only for the current process. As a best practice, enable OSPFv3 NSR for each process if multiple OSPFv3 processes exist.
OSPFv3 NSR and OSPFv3 GR are mutually exclusive. Do not configure the non-stop-routing command and the graceful-restart enable command at the same time.
Examples
# Enable NSR for OSPFv3 process 100.
<Sysname> system-view
[Sysname] ospfv3 100
[Sysname-ospfv3-100] non-stop-routing
nssa
Use nssa to configure an area as an NSSA area.
Use undo nssa to restore the default.
Syntax
nssa [ default-route-advertise [ cost cost-value | nssa-only | route-policy route-policy-name | tag tag | type type ] * | no-import-route | no-summary | [ translate-always | translate-never ] | suppress-fa | translator-stability-interval value ] *
undo nssa
Default
No area is configured as an NSSA area.
Views
OSPFv3 area view
Predefined user roles
network-admin
Parameters
default-route-advertise: Used on an NSSA ABR or an ASBR only. If it is configured on an NSSA ABR, the ABR redistributes a default route in a Type-7 LSA into the NSSA area. It redistributes a default route regardless of whether a default route exists in the routing table. If it is configured on an ASBR, the ASBR redistributes a default route in a Type-7 LSA only when the default route exists in the routing table.
cost cost-value: Specifies a cost for the default route, in the range of 0 to 16777214. If you do not specify this option, the default cost specified by the default-cost command applies.
nssa-only: Limits the default route advertisement to the NSSA area by setting the P-bit of Type-7 LSAs to 0. If you do not specify this keyword, the P-bit of Type-7 LSAs is set to 1. If the router acts as both an ASBR and an ABR and FULL state neighbors exist in the backbone area, the P-bit is set to 0.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters. When the specified routing policy is matched, the command redistributes a default route in a Type-7 LSA into the OSPFv3 routing domain. The routing policy modifies values in the Type-7 LSA.
tag tag: Specifies a tag for the default route, in the range of 0 to 4294967295.
type type: Specifies a type for the Type-7 LSA, 1 or 2. The default is 2.
no-import-route: Used on an NSSA ABR to control the import-route command to not redistribute routes into the NSSA area.
no-summary: Used only on an ABR to advertise a default route in a Type-3 summary LSA into the NSSA area and to not advertise other summary LSAs into the area. The area is a totally NSSA area.
translate-always: Always translates Type-7 LSAs to Type-5 LSAs. This keyword takes effect only on an NSSA ABR.
translate-never: Never translates Type-7 LSAs to Type-5 LSAs. This keyword takes effect only on an NSSA ABR.
suppress-fa: Suppresses the forwarding address in the Type-7 LSAs from being placed in the Type-5 LSAs.
translator-stability-interval value: Specifies the stability interval of the translator. During the interval, the translator can maintain its translating capability after another device becomes the new translator. The value argument is the stability interval in the range of 0 to 900 seconds. The default interval is 0. A value of 0 means the translator does not maintain its translating capability when a new translator arises.
Usage guidelines
All routers attached to an NSSA area must be configured with the nssa command in area view.
Examples
# Configure Area 1 as an NSSA area.
<Sysname> system-view
[Sysname] ospfv3 120
[Sysname-ospfv3-120] area 1
[Sysname-ospfv3-120-area-0.0.0.1] nssa
Related commands
default-cost (OSPFv3 area view)
ospfv3
Use ospfv3 to enable an OSPFv3 process and enter OSPFv3 view.
Use undo ospfv3 to disable an OSPFv3 process.
Syntax
ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
undo ospfv3 [ process-id ]
Default
No OSPFv3 process is enabled.
Views
System view
Predefined user roles
network-admin
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. The default process ID is 1.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the OSPFv3 process runs on the public network.
Usage guidelines
Specify a router ID for the OSPFv3 process. Otherwise, the OSPFv3 process cannot generate LSAs.
Examples
# Enable OSPFv3 process 120 and set the router ID to 1.1.1.1.
<Sysname> system-view
[Sysname] ospfv3 120
[Sysname-ospfv3-120] router-id 1.1.1.1
ospfv3 area
Use ospfv3 area to enable an OSPFv3 process on an interface and specify an area for the interface.
Use undo ospfv3 area to disable an OSPFv3 process on an interface.
Syntax
ospfv3 process-id area area-id [ instance instance-id ]
undo ospfv3 process-id area area-id [ instance instance-id ]
Default
No OSPFv3 processes are enabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535.
area-id: Specifies an area by its ID, an IPv4 address or a decimal integer in the range of 0 to 4294967295 that is translated into the IPv4 address format.
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Examples
# Configure GigabitEthernet 1/0/1 to run instance 1 of OSPFv3 process 1 in Area 1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 1 area 1 instance 1
ospfv3 bfd enable
Use ospfv3 bfd enable to enable BFD on an OSPFv3 interface.
Use undo ospfv3 bfd enable to disable BFD on an OSPFv3 interface.
Syntax
ospfv3 bfd enable [ instance instance-id ]
undo ospfv3 bfd enable [ instance instance-id ]
Default
BFD is disabled on an OSPFv3 interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Usage guidelines
BFD provides a mechanism to quickly detect the connectivity of links between OSPFv3 neighbors, improving the convergence speed of OSPFv3.
OSPFv3 uses BFD to implement bidirectional control detection.
Examples
# Enable BFD on GigabitEthernet 1/0/1 in instance 1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 bfd enable instance 1
ospfv3 cost
Use ospfv3 cost to set an OSPFv3 cost for an interface in an instance.
Use undo ospfv3 cost to remove the configuration.
Syntax
ospfv3 cost cost-value [ instance instance-id ]
undo ospfv3 cost [ instance instance-id ]
Default
The cost is 1 for a VLAN interface, is 0 for a loopback interface, and is computed according to the interface bandwidth for other interfaces.
Views
Interface view
Predefined user roles
network-admin
Parameters
cost-value: Specifies an OSPFv3 cost in the range of 0 to 65535 for a loopback interface, and in the range of 1 to 65535 for other interfaces.
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Examples
# Set the OSPFv3 cost to 33 for GigabitEthernet 1/0/1 in instance 1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 cost 33 instance 1
ospfv3 dr-priority
Use ospfv3 dr-priority to set the router priority for an interface in an instance.
Use undo ospfv3 dr-priority to remove the configuration.
Syntax
ospfv3 dr-priority priority [ instance instance-id ]
undo ospfv3 dr-priority [ instance instance-id ]
Default
An interface has a router ID of 1.
Views
Interface view
Predefined user roles
network-admin
Parameters
priority: Specifies a router priority in the range of 0 to 255.
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Usage guidelines
An interface's router priority determines its privilege in DR/BDR selection.
Examples
# Set the router priority for GigabitEthernet 1/0/1 in instance 1 to 8.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 dr-priority 8 instance 1
ospfv3 fast-reroute lfa-backup exclude
Use ospfv3 fast-reroute lfa-backup exclude to disable LFA on an interface.
Use undo ospfv3 fast-reroute lfa-backup exclude to remove the configuration.
Syntax
ospfv3 fast-reroute lfa-backup exclude [ instance instance-id ]
undo ospfv3 fast-reroute lfa-backup exclude [ instance instance-id ]
Default
LFA is enabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Usage guidelines
An interface enabled with LFA can be selected as a backup interface. After you disable LFA on the interface, it cannot be selected as a backup interface.
Examples
# Disable GigabitEthernet 1/0/1 from calculating a backup next hop by using the LFA algorithm.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 fast-reroute lfa-backup exclude
ospfv3 ipsec-profile
Use ospfv3 ipsec-profile to apply an IPsec profile to an OSPFv3 interface.
Use undo ospfv3 ipsec-profile to remove the IPsec profile from the OSPFv3 interface.
Syntax
ospfv3 ipsec-profile profile-name [ instance instance-id ]
undo ospfv3 ipsec-profile [ instance instance-id ]
Default
No IPsec profile is applied to an OSPFv3 interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
profile-name: Specifies an IPsec profile by its name, a case-insensitive string of 1 to 63 characters.
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Usage guidelines
An IPsec profile must be specified in this command. For more information about IPsec profiles, see Security Configuration Guide.
Examples
# Apply IPsec profile profile001 to OSPFv3 interface GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 ipsec-profile profile001
ospfv3 mib-binding
Use ospfv3 mib-binding to bind an OSPFv3 process to MIB.
Use undo ospfv3 mib-binding to restore the default.
Syntax
ospfv3 mib-binding process-id
undo ospfv3 mib-binding
Default
MIB is bound to the OSPFv3 process with the smallest process ID.
Views
System view
Predefined user roles
network-admin
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535.
Usage guidelines
If the specified process ID does not exist, the MIB binding configuration fails.
Deleting an OSPFv3 process that has been bound to MIB unbinds the OSPFv3 process from MIB, and re-binds MIB to the OSPFv3 process with the smallest process ID.
Examples
# Bind OSPFv3 process 100 to MIB.
<Sysname> system-view
[Sysname] ospfv3 mib-binding 100
ospfv3 mtu-ignore
Use ospfv3 mtu-ignore to configure an interface to ignore MTU check during DD packet exchange.
Use undo ospfv3 mtu-ignore to remove the configuration.
Syntax
ospfv3 mtu-ignore [ instance instance-id ]
undo ospfv3 mtu-ignore [ instance instance-id ]
Default
An interface performs MTU check during DD packet exchange.
Views
Interface view
Predefined user roles
network-admin
Parameters
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Usage guidelines
A neighbor relationship can be established only if the interface's MTU is the same as that of the peer.
Examples
# Configure GigabitEthernet 1/0/1 that belongs to instance 1 to ignore MTU check during DD packet exchange.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 mtu-ignore instance 1
ospfv3 network-type
Use ospfv3 network-type to specify the network type for an OSPFv3 interface.
Use undo ospfv3 network-type to remove the configuration.
Syntax
ospfv3 network-type { broadcast | nbma | p2mp [ unicast ] | p2p } [ instance instance-id ]
undo ospfv3 network-type [ instance instance-id ]
Default
The network type of an OSPFv3 interface depends on its link layer protocol.
· For Ethernet and FDDI, the default network type is broadcast.
· For ATM, FR, and X.25, the default network type is NBMA.
· For PPP, LAPB, HDLC, and POS, the default network type is P2P.
Views
Interface view
Predefined user roles
network-admin
Parameters
broadcast: Specifies the network type as broadcast.
nbma: Specifies the network type as NBMA.
p2mp: Specifies the network type as P2MP.
unicast: Specifies the P2MP interface to unicast OSPFv3 packets. By default, a P2MP interface multicasts OSPFv3 packets.
p2p: Specifies the network type as P2P.
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Usage guidelines
If a router on a broadcast network does not support multicast, configure the network type for the connected interfaces as NBMA.
If any two routers on an NBMA network are directly connected through a virtual link, the network is fully meshed. You can configure the network type for the connected interfaces as NBMA. If two routers are not directly connected, configure the P2MP network type so that the two routers can exchange routing information through another router.
When the network type of an interface is NBMA or P2MP unicast, you must use the peer command to specify the neighbor.
When the network type of an interface is P2MP unicast, all OSPFv3 packets are unicast by the interface.
Examples
# Specify the OSPFv3 network type for GigabitEthernet 1/0/1 as NBMA.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 network-type nbma
Related commands
ospfv3 dr-priority
ospfv3 peer
Use ospfv3 peer to specify a neighbor and the DR priority of the neighbor.
Use undo ospfv3 peer to remove the configuration.
Syntax
ospfv3 peer ipv6-address [ cost cost-value | dr-priority priority ] [ instance instance-id ]
undo ospfv3 peer ipv6-address [ instance instance-id ]
Default
No link-local address is specified for the neighbor interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
ipv6-address: Specifies the link-local IPv6 address of the neighbor.
cost cost-value: Specifies the cost of the neighbor, in the range of 1 to 65535.
dr-priority priority: Specifies the DR priority of the neighbor, in the range of 0 to 255. The default is 1.
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Usage guidelines
For NBMA and P2MP interfaces (only when in unicast mode), you must specify the link-local IPv6 addresses of their neighbors because these interfaces cannot find neighbors through broadcasting hello packets. For NBMA interfaces, you can also specify DR priorities for their neighbors.
Examples
# On GigabitEthernet 1/0/1, specify the link-local address of its neighbor as FE80::1111.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 peer fe80::1111
ospfv3 prefix-suppression
Use ospfv3 prefix-suppression to disable an OSPFv3 interface from advertising all its prefixes.
Use undo ospfv3 prefix-suppression to remove the configuration.
Syntax
ospfv3 prefix-suppression [ disable ] [ instance instance-id ]
undo ospfv3 prefix-suppression [ instance instance-id ]
Default
Prefix suppression is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
disable: Disables prefix suppression for an interface.
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Usage guidelines
To disable prefix suppression for an interface associated with an OSPFv3 process that has been enabled with prefix suppression, use the ospfv3 prefix-suppression disable command on that interface.
Examples
# Enable prefix suppression for GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 prefix-suppression
Related commands
prefix-suppression
ospfv3 primary-path-detect bfd
Use ospfv3 primary-path-detect bfd to enable BFD for OSPFv3 FRR.
Use undo ospfv3 primary-path-detect bfd to disable BFD for OSPFv3 FRR.
Syntax
ospfv3 primary-path-detect bfd { ctrl | echo } [ instance instance-id ]
undo ospfv3 primary-path-detect bfd [ instance instance-id ]
Default
BFD is disabled for OSPFv3 FRR.
Views
Interface view
Predefined user roles
network-admin
Parameters
ctrl: Enables BFD control packet mode.
echo: Enables BFD echo packet mode.
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Usage guidelines
This command enables OSPFv3 FRR to use BFD to detect primary link failures.
Examples
# On GigabitEthernet 1/0/1, enable BFD echo packet mode for OSPFv3 FRR.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] fast-reroute lfa
[Sysname-ospfv3-1] quit
[Sysname] bfd echo-source-ipv6 1::1
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 primary-path-detect bfd echo
ospfv3 timer dead
Use ospfv3 timer dead to set the OSPFv3 neighbor dead time.
Use undo ospfv3 timer dead to remove the configuration.
Syntax
ospfv3 timer dead seconds [ instance instance-id ]
undo ospfv3 timer dead [ instance instance-id ]
Default
The OSPFv3 neighbor dead time is 40 seconds for P2P and broadcast interfaces, and is 120 seconds for P2MP and NBMA interfaces.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the dead time in the range of 1 to 65535 seconds.
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Usage guidelines
If an interface receives no hello packet from a neighbor within the dead time, the interface determines that the neighbor is down.
The dead time must be a minimum of four times the hello time and must be identical on interfaces attached to the same network segment.
Examples
# Set the OSPFv3 neighbor dead time to 60 seconds for GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 timer dead 60
Related commands
ospfv3 timer hello
ospfv3 timer hello
Use ospfv3 timer hello to set the hello interval for an interface.
Use undo ospfv3 timer hello to remove the configuration.
Syntax
ospfv3 timer hello seconds [ instance instance-id ]
undo ospfv3 timer hello [ instance instance-id ]
Default
The hello interval is 10 seconds for P2P and broadcast interfaces, and is 30 seconds for P2MP or NBMA interfaces.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the hello interval in the range of 1 to 65535 seconds.
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Usage guidelines
The shorter the hello interval is, the faster the topology converges and the more resources are consumed. Make sure the hello interval on two neighboring interfaces is the same.
Examples
# Set the hello interval to 20 seconds for GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 timer hello 20
Related commands
ospfv3 timer dead
ospfv3 timer poll
Use ospfv3 timer poll to set the poll interval on an NBMA interface.
Use undo ospfv3 timer poll to remove the configuration.
Syntax
ospfv3 timer poll seconds [ instance instance-id ]
undo ospfv3 timer poll [ instance instance-id ]
Default
The poll interval is 120 seconds on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the poll interval in the range of 1 to 65535 seconds.
instance instance-id: Specifies an interface instance by its ID in the range of 0 to 255. The default is 0.
Usage guidelines
When an NBMA interface finds its neighbor is down, it sends hello packets at the poll interval.
The poll interval must be a minimum of four times the hello interval.
Examples
# Set the poll interval on GigabitEthernet 1/0/1 to 120 seconds.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 timer poll 120
Related commands
ospfv3 timer hello
ospfv3 timer retransmit
Use ospfv3 timer retransmit to set the LSA retransmission interval for an interface.
Use undo ospfv3 timer retransmit to remove the configuration.
Syntax
ospfv3 timer retransmit seconds [ instance instance-id ]
undo ospfv3 timer retransmit [ instance instance-id ]
Default
The interval is 5 seconds.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the LSA retransmission interval in the range of 1 to 3600 seconds.
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Usage guidelines
After the device sends an LSA to its neighbor, it waits for an acknowledgment. If the device receives no acknowledgment after the LSA retransmission interval elapses, it will retransmit the LSA.
To avoid unnecessary retransmissions, set an appropriate retransmission interval. For example, you can set a large retransmission interval value on a low-speed link.
Examples
# Set the LSA retransmission interval to 12 seconds on GigabitEthernet 1/0/1 in instance 1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 timer retransmit 12 instance 1
ospfv3 trans-delay
Use ospfv3 trans-delay to set the transmission delay for an interface.
Use undo ospfv3 trans-delay to remove the configuration.
Syntax
ospfv3 trans-delay seconds [ instance instance-id ]
undo ospfv3 trans-delay [ instance instance-id ]
Default
The transmission delay is 1 second.
Views
Interface view
Predefined user roles
network-admin
Parameters
seconds: Specifies the transmission delay in the range of 1 to 3600 seconds.
instance instance-id: Specifies an instance by its ID in the range of 0 to 255. The default is 0.
Usage guidelines
Each LSA in the LSDB has an age that is incremented by 1 every second, but the age does not change during transmission. Adding a transmission delay into the age time is important in low speed networks.
Examples
# Set the transmission delay to 3 seconds for GigabitEthernet 1/0/1 in instance 1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ospfv3 trans-delay 3 instance 1
preference
Use preference to set a preference for OSPFv3 routes.
Use undo preference to remove the configuration.
Syntax
preference [ ase ] { preference | route-policy route-policy-name } *
undo preference [ ase ]
Default
The preference is 10 for OSPFv3 internal routes and 150 for OSPFv3 external routes.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
ase: Specifies a preference for OSPFv3 external routes. If you do not specify this keyword, the command sets a preference for OSPFv3 internal routes.
preference: Specifies the preference value in the range of 1 to 255. A smaller value represents a higher preference.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to set a preference for matching routes.
Usage guidelines
If multiple routing protocols find multiple routes to the same destination, the router uses the route found by the protocol with the highest preference.
Examples
# Set a preference of 150 for OSPFv3 routes.
<Sysname> system-view
[Sysname] OSPFv3
[Sysname-OSPFv3-1] preference 150
prefix-suppression
Use prefix-suppression to disable an OSPFv3 process from advertising all prefixes except for the prefixes of loopback interfaces and passive interfaces.
Use undo prefix-suppression to restore the default.
Syntax
prefix-suppression
undo prefix-suppression
Default
An OSPFv3 process advertises all prefixes.
Views
OSPFv3 view
Predefined user roles
network-admin
Usage guidelines
By default, an OSPFv3 interface advertises all of its prefixes in LSAs. To speed up OSPFv3 convergence, you can suppress interfaces from advertising all of their prefixes. This feature helps improve network security by preventing IP routing to the suppressed networks.
To disable an OSPFv3 process from advertising the prefixes of loopback and passive interfaces, configure prefix suppression on the interfaces by using the ospfv3 prefix-suppression command.
When prefix suppression is enabled:
· OSPFv3 does not advertise the prefixes of suppressed interfaces in Type-8 LSAs.
· On broadcast and NBMA networks, the DR does not advertise the prefixes of suppressed interfaces in Type-9 LSAs that reference Type-2 LSAs.
· On P2P and P2MP networks, OSPFv3 does not advertise the prefixes of suppressed interfaces in Type-9 LSAs that reference Type-1 LSAs.
Examples
# Enable prefix suppression for OSPFv3 process 100.
<Sysname> system-view
[Sysname] ospfv3 100
[Sysname-ospfv3-100] prefix-suppression
Related commands
ospfv3 prefix-suppression
reset ospfv3 event-log
Use reset ospfv3 event-log to clear OSPFv3 log information.
Syntax
reset ospfv3 [ process-id ] event-log [ lsa-flush | peer | spf ]
Views
User view
Predefined user roles
network-admin
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command clears OSPFv3 log information for all OSPFv3 processes.
lsa-flush: Clears LSA aging log information.
peer: Clears neighbor log information.
spf: Clears route calculation log information.
Usage guidelines
If you do not specify a log type, this command clears all log information.
Examples
# Clear OSPFv3 route calculation log information for all OSPFv3 processes.
<Sysname> reset ospfv3 event-log spf
Related commands
display ospfv3 event-log
reset ospfv3 process
Use reset ospfv3 process to restart OSPFv3 processes.
Syntax
reset ospfv3 [ process-id ] process [ graceful-restart ]
Views
User view
Predefined user roles
network-admin
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command restarts all OSPFv3 processes.
graceful-restart: Restarts the OSPFv3 process by using GR.
Usage guidelines
The reset ospfv3 process command performs the following actions:
· Clears all invalid LSAs without waiting for their timeouts.
· Starts a new DR/BDR election.
· Keeps previous OSPFv3 configurations.
The system prompts you to select whether to restart OSPFv3 process upon execution of this command.
Examples
# Restart all OSPFv3 processes.
<Sysname> reset ospfv3 process
Reset OSPFv3 process? [Y/N]:y
reset ospfv3 redistribution
Use reset ospfv3 redistribution to restart route redistribution.
Syntax
reset ospfv3 [ process-id ] redistribution
Views
User view
Predefined user roles
network-admin
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command restarts route redistribution for all OSPFv3 processes.
Examples
# Restart route redistribution.
<Sysname> reset ospfv3 redistribution
reset ospfv3 statistics
Use reset ospfv3 statistics to clear OSPFv3 statistics.
Syntax
reset ospfv3 [ process-id ] statistics
Views
User view
Predefined user roles
network-admin
Parameters
process-id: Specifies an OSPFv3 process by its ID in the range of 1 to 65535. If you do not specify this argument, the command clears statistics for all OSPFv3 processes.
Examples
# Clear statistics for all OSPFv3 processes.
<Sysname> reset ospfv3 statistics
router-id
Use router-id to configure a router ID.
Use undo router-id to restore the default.
Syntax
router-id router-id
undo router-id
Default
No router ID is configured.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
router-id: Specifies a router ID in IPv4 address format.
Usage guidelines
The router ID is the unique identifier for the device to run OSPFv3 in the AS. An OSPFv3 process cannot run without a router ID.
Different processes must have different router IDs.
Examples
# Configure the router ID 10.1.1.3 for OSPFv3 process 1.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] router-id 10.1.1.3
Related commands
ospfv3
silent-interface(OSPFv3 view)
Use silent-interface to disable the specified interface from receiving and sending OSPFv3 packets.
Use undo silent-interface to remove the configuration.
Syntax
silent-interface { interface-type interface-number | all }
undo silent-interface { interface-type interface-number | all }
Default
An interface can receive and send OSPFv3 packets.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
all: Specifies all interfaces.
Usage guidelines
Multiple processes can disable the same interface from receiving and sending OSPFv3 packets. However, the silent-interface command takes effect only on interfaces enabled with the current process.
Examples
# Disable GigabitEthernet 1/0/1 from receiving and sending OSPFv3 packets in OSPFv3 processes 100 and 200.
[Sysname] ospfv3 100
[Sysname-ospfv3-100] router-id 10.100.1.9
[Sysname-ospfv3-100] silent-interface gigabitethernet 1/0/1
[Sysname-ospfv3-100] quit
[Sysname] ospfv3 200
[Sysname-ospfv3-200] router-id 20.100.1.9
[Sysname-ospfv3-200] silent-interface gigabitethernet 1/0/1
snmp-agent trap enable ospfv3
Use snmp-agent trap enable ospfv3 to enable SNMP notifications for OSPFv3.
Use undo snmp-agent trap enable ospfv3 to disable SNMP notifications for OSPFv3.
Syntax
snmp-agent trap enable ospfv3 [ grrestarter-status-change | grhelper-status-change | if-state-change | if-cfg-error | if-bad-pkt | neighbor-state-change | nssatranslator-status-change | virtif-bad-pkt | virtif-cfg-error | virtif-state-change | virtgrhelper-status-change | virtneighbor-state-change ] *
undo snmp-agent trap enable ospfv3 [ grrestarter-status-change | grhelper-status-change | if-state-change | if-cfg-error | if-bad-pkt | neighbor-state-change | nssatranslator-status-change | virtif-bad-pkt | virtif-cfg-error | virtif-state-change | virtgrhelper-status-change | virtneighbor-state-change ] *
Default
SNMP notifications for OSPFv3 are enabled.
Views
System view
Predefined user roles
network-admin
Parameters
grrestarter-status-change: Specifies notifications about GR restarter state changes.
grhelper-status-change: Specifies notifications about GR helper state changes.
if-state-change: Specifies notifications about interface state changes.
if-cfg-error: Specifies notifications about error configuration of an interface.
if-bad-pkt: Specifies notifications about error messages received on an interface.
neighbor-state-change: Specifies notifications about neighbor state changes.
nssatranslator-status-change: Specifies notifications about NSSA translator state changes.
virtif-bad-pkt: Specifies notifications about error messages received on a virtual interface.
virtif-cfg-error: Specifies notifications about error configuration of a virtual interface.
virtif-state-change: Specifies notifications about virtual interface state changes.
virtgrhelper-status-change: Specifies notifications about neighbor GR helper state changes of a virtual interface.
virtneighbor-state-change: Specifies notifications about the neighbor state changes of a virtual interface.
Examples
# Disable SNMP notifications for OSPFv3.
<Sysname> system-view
[Sysname] undo snmp-agent trap enable ospfv3
snmp context-name
Use snmp context-name to configure an SNMP context for OSPFv3.
Use undo snmp context-name to restore the default.
Syntax
snmp context-name context-name
undo snmp context-name
Default
No SNMP contexts exist for OSPFv3.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
context-name: Specifies a context name, a case-sensitive string of 1 to 32 characters.
Usage guidelines
The standard OSPFv3 MIB provides only single-instance MIB objects. For SNMP to correctly identify OSPFv3 management information in the standard OSPFv3 MIB, you must configure a unique context name for OSPFv3. If multiple OSPFv3 processes exist, you must assign a unique context to each process.
Context is a method introduced to SNMPv3 for multiple-instance management. For SNMPv1/v2c, you must specify a community name as a context name for protocol identification.
Examples
# Configure the SNMP context name as mib for OSPFv3 process 1.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] snmp context-name mib
snmp trap rate-limit
Use snmp trap rate-limit to set the SNMP notification output interval and the maximum number of SNMP notifications that can be output at each interval.
Use undo snmp trap rate-limit to restore the default.
Syntax
snmp trap rate-limit interval trap-interval count trap-number
undo snmp trap rate-limit
Default
OSPFv3 outputs a maximum of seven SNMP notifications within 10 seconds.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
interval trap-interval: Specifies the SNMP notification output interval in the range of 2 to 60 seconds.
count trap-number: Specifies the number of SNMP notifications output by OSPFv3 at each interval, in the range of 0 to 300. The value of 0 indicates that OSPFv3 does not output SNMP notifications.
Examples
# Configure OSPFv3 to output a maximum of 10 SNMP notifications within 5 seconds.
<Sysname> system-view
[Sysname] ospfv3 100
[Sysname-ospfv3-100] snmp trap rate-limit interval 5 count 10
spf-schedule-interval
Use spf-schedule-interval to set the OSPFv3 SPF calculation interval.
Use undo spf-schedule-interval to restore the default.
Syntax
spf-schedule-interval maximum-interval [ minimum-interval [ incremental-interval ] ]
undo spf-schedule-interval
Default
The maximum SPF calculation interval is 5 seconds, the minimum interval is 50 milliseconds, and the incremental interval is 200 milliseconds.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
maximum-interval: Specifies the maximum OSPFv3 route calculation interval in the range of 1 to 60 seconds.
minimum-interval: Specifies the minimum OSPFv3 route calculation interval in the range of 10 to 60000 milliseconds.
incremental-interval: Specifies the incremental OSPFv3 route calculation interval in the range of 10 to 60000 milliseconds.
Usage guidelines
Based on the LSDB, an OSPFv3 router uses SPF to calculate a shortest path tree with itself being the root. OSPFv3 uses the shortest path tree to determine the next hop to a destination. By adjusting the SPF calculation interval, you can prevent overconsumption of bandwidth and router resources due to frequent topology changes.
For a stable network, the minimum interval is used. If network changes become frequent, the SPF calculation interval is incremented by the incremental interval × 2n-2 for each calculation until the maximum interval is reached. The value n is the number of calculation times.
The minimum interval and the incremental interval cannot be greater than the maximum interval.
Examples
# Set the maximum SPF calculation interval to 10 seconds, minimum interval to 500 milliseconds, and incremental interval to 300 milliseconds.
<Sysname> system-view
[Sysname] ospfv3 100
[Sysname-ospfv3-100] spf-schedule-interval 10 500 300
stub (OSPFv3 area view)
Use stub to configure an area as a stub area.
Use undo stub to restore the default.
Syntax
stub [ default-route-advertise-always | no-summary ] *
undo stub
Default
No area is configured as a stub area.
Views
OSPFv3 area view
Predefined user roles
network-admin
Parameters
default-route-advertise-always: Enables the ABR to always advertise a default route into the stub area.
no-summary: Enables the ABR to advertise only a default route in an Inter-Area-Prefix-LSA into the stub area. No AS-external-LSA, Inter-Area-Prefix-LSA, or other Inter-Area-Router-LSA is advertised in the area. The area is a totally stub area.
Usage guidelines
To remove the no-summary configuration on an ABR, execute the stub command again to overwrite it.
To configure an area as a stub area, execute the stub command on all routers attached to the area.
Examples
# Configure OSPFv3 area 1 as a stub area.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] area 1
[Sysname-ospfv3-1-area-0.0.0.1] stub
Related commands
default-cost (OSPFv3 area view)
stub-router
Use stub-router to configure a router as a stub router.
Use undo stub-router to restore the default.
Syntax
stub-router r-bit [ include-stub | on-startup { seconds | wait-for-bgp [ seconds ] } ] *
stub-router max-metric [ external-lsa [ max-metric-value ] | summary-lsa [ max-metric-value ] | include-stub | on-startup { seconds | wait-for-bgp [ seconds ] } ] *
undo stub-router
Default
The router is not configured as a stub router.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
r-bit: Clears the R-bit of the Option field in Type-1 LSAs.
max-metric: Advertises the locally generated Type-1 LSAs with the maximum cost of 65535.
external-lsa max-metric-value: Specifies a cost for external LSAs, in the range of 1 to 16777215. The default is 16711680.
summary-lsa max-metric-value: Specifies a cost for Type-3 and Type-4 LSAs, in the range of 1 to 16777215. The default is 16711680.
include-stub: Specifies the cost for Type-9 LSAs that reference Type-1 LSAs to the maximum value 65535.
on-startup seconds: Specifies the router as a stub router during reboot, and specifies the timeout time in the range of 5 to 86400 seconds.
wait-for-bgp seconds: Specifies the router as a stub router during BGP route convergence after reboot, and specifies the timeout time in the range of 5 to 86400 seconds. The default timeout time is 600 seconds.
Usage guidelines
You can use the stub-router r-bit command or stub-router max-metric command to configure a router as a stub router.
· The stub-router r-bit command clears the R-bit of the Option field in Type-1 LSAs. When the R-bit is clear, the OSPFv3 router can participate in OSPFv3 topology distribution without forwarding traffic.
· The stub-router max-metric command specifies the OSPFv3 max-metric router LSA feature. This feature enables OSPFv3 to advertise its locally generated Type-1 LSAs with a maximum cost of 65535. Neighbors do not send packets to the stub router as long as they have a route with a smaller cost.
Examples
# Configure a stub router.
<Sysname> system-view
[Sysname] ospfv3 100
[Sysname-ospfv3-100] stub-router r-bit
transmit-pacing
Use transmit-pacing to set the LSU transmission interval and the maximum number of LSU packets that can be sent at each interval.
Use undo transmit-pacing to restore the default.
Syntax
transmit-pacing interval interval count count
undo transmit-pacing
Default
An OSPFv3 interface sends a maximum of three LSU packets every 20 milliseconds.
Views
OSPFv3 view
Predefined user roles
network-admin
Parameters
interval interval: Specifies an interval at which an interface sends LSU packets, in the range of 10 to 1000 milliseconds. If the router has multiple OSPFv3 interfaces, increase the interval to reduce the total number of LSU packets sent by the router every second.
count count: Specifies the maximum number of LSU packets sent by an interface at each interval, in the range of 1 to 200. If the router has multiple OSPFv3 interfaces, decrease the maximum number to reduce the total number of LSU packets sent by the router every second.
Examples
# Configure all the interfaces running OSPFv3 process 1 to send a maximum of 10 LSU packets every 30 milliseconds.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] transmit-pacing interval 30 count 10
vlink-peer (OSPFv3 area view)
Use vlink-peer to configure a virtual link.
Use undo vlink-peer to remove a virtual link.
Syntax
vlink-peer router-id [ dead seconds | hello seconds | instance instance-id | ipsec-profile profile-name | retransmit seconds | trans-delay seconds ] *
undo vlink-peer router-id [ dead | hello | ipsec-profile | retransmit | trans-delay ] *
Default
No virtual links exist.
Views
OSPFv3 area view
Predefined user roles
network-admin
Parameters
router-id: Specifies the router ID of the neighbor on the virtual link.
dead seconds: Specifies the dead interval in the range of 1 to 32768 seconds. The default is 40. The dead interval must be identical with that on the virtual link neighbor, and must be a minimum of four times the hello interval.
hello seconds: Specifies the hello interval in the range of 1 to 8192 seconds. The default is 10. It must be identical with the hello interval on the virtual link neighbor.
instance instance-id: Specifies the instance ID of a virtual link, in the range of 0 to 255. The default is 0.
ipsec-profile profile-name: Specifies an IPsec profile by its name, a case-insensitive string of 1 to 63 characters. For more information about IPsec profiles, see Security Configuration Guide.
retransmit seconds: Specifies the retransmission interval in the range of 1 to 3600 seconds. The default is 5.
trans-delay seconds: Specifies the transmission delay interval in the range of 1 to 3600 seconds. The default is 1.
Usage guidelines
You can configure a virtual link to maintain connectivity between a non-backbone area and the backbone, or maintain connectivity within the backbone. A virtual link is similar to an interface with OSPFv3 enabled. You can configure parameters such as hello, dead, retransmit and trans-delay for the virtual link.
Both ends of a virtual link must be ABRs that are configured with the vlink-peer command.
The following guidelines apply to parameters:
· The smaller the hello interval is, the faster the network converges, and the more network resources are consumed.
· For a low speed link, set a large retransmission interval to avoid unnecessary retransmissions.
· Specify a transmission delay with the trans-delay keyword depending on the interface delay.
Examples
# Configure a virtual link to 10.10.0.3.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] area 1
[Sysname-ospfv3-1-area-0.0.0.1] vlink-peer 10.10.0.3
Related commands
display ospfv3 vlink
IPv6 IS-IS commands
IPv6 IS-IS supports all the features of IPv4 IS-IS except that it advertises IPv6 routing information. This chapter describes only IPv6 IS-IS exclusive commands. For other IS-IS configuration commands, see "IS-IS commands."
address-family ipv6
Use address-family ipv6 to create the IS-IS IPv6 address family and enter its view.
Use undo address-family ipv6 to remove the IS-IS IPv6 address family and all configurations in the view.
Syntax
address-family ipv6 [ unicast ]
undo address-family ipv6 [ unicast ]
Default
No IS-IS IPv6 address family exists.
Views
IS-IS view
Predefined user roles
network-admin
Parameters
unicast: Specifies the unicast address family (the default).
Usage guidelines
This command enables IPv6 for an IS-IS process.
Examples
# Create the IS-IS IPv6 address family and enter its view.
<Sysname> system-view
[Sysname] isis 100
[Sysname-isis-100] address-family ipv6
[Sysname-isis-100-ipv6]
auto-cost enable
Use auto-cost enable to enable automatic link cost calculation.
Use undo auto-cost enable to disable automatic link cost calculation.
Syntax
auto-cost enable
undo auto-cost enable
Default
Automatic link cost calculation is disabled.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Usage guidelines
After automatic link cost calculation is enabled, the link cost is automatically calculated based on the bandwidth reference value of an interface. When the cost-style is wide or wide-compatible, the cost value of an interface is calculated by using the following formula: Cost = (Reference bandwidth value / Link bandwidth) × 10. For other cost styles, Table 165 applies.
Table 165 Automatic cost calculation scheme for cost styles other than wide and wide-compatible
|
Interface bandwidth |
Cost |
|
≤10 Mbps |
60 |
|
≤100 Mbps |
50 |
|
≤155 Mbps |
40 |
|
≤622 Mbps |
30 |
|
≤2500 Mbps |
20 |
|
>2500 Mbps |
10 |
Examples
# Enable automatic link cost calculation for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] auto-cost enable
Related commands
bandwidth-reference
cost-style
isis ipv6 cost
bandwidth-reference
Use bandwidth-reference to set the bandwidth reference value for automatic link cost calculation.
Use undo bandwidth-reference to restore the default.
Syntax
bandwidth-reference value
undo bandwidth-reference
Default
The bandwidth reference value is 100 Mbps.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
value: Specifies the bandwidth reference value in the range of 1 to 2147483648 Mbps.
Examples
# Set the IPv6 bandwidth reference to 200 Mbps for IS-IS process 1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] bandwidth-reference 200
Related commands
auto-cost enable
isis cost
circuit-cost
Use circuit-cost to set a global IPv6 IS-IS link cost.
Use undo circuit-cost to remove the configuration.
Syntax
circuit-cost value [ level-1 | level-2 ]
undo circuit-cost [ level-1 | level-2 ]
Default
No global link cost is configured.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
value: Specifies the link cost value. The value range varies by cost style.
· For styles narrow, narrow-compatible, and compatible, the cost value is in the range of 0 to 63.
· For styles wide and wide-compatible, the cost value is in the range of 0 to 16777215.
level-1: Applies the link cost to Level-1.
level-2: Applies the link cost to Level-2.
Usage guidelines
If no level is specified, the specified cost applies to both Level-1 and Level-2.
Examples
# Set the global Level-1 IPv6 link cost of IS-IS process 1 to 11.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] circuit-cost 11 level-1
Related commands
cost-style
isis cost
default-route-advertise
Use default-route-advertise to configure IPv6 IS-IS to advertise a Level-1 or Level-2 default route.
Use undo default-route-advertise to restore the default.
Syntax
default-route-advertise [ avoid-learning | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
undo default-route-advertise
Default
IPv6 IS-IS does not advertise Level-1 and Level-2 default routes.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
avoid-learning: Avoids learning the default route received in LSPs or generated by using the ATT bit to prevent routing loops.
level-1: Advertises a Level-1 default route.
level-1-2: Advertises a Level-1-2 default route.
level-2: Advertises a Level-2 default route.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
tag tag: Specifies a tag value for the default route, in the range of 1 to 4294967295.
Usage guidelines
If no level is specified, this command advertises a Level-2 default route.
A Level-1 default route is advertised to the routers of the local area. A Level-2 route is advertised to all Level-2 and Level-1-2 routers.
You can use a routing policy to specify a level for the default route. The default route can be generated only when a route entry in the routing table matches the routing policy. Use the following commands in routing policy node view to specify different default route levels:
· Use the apply isis level-1 command to specify Level-1.
· Use the apply isis level-2 command to specify Level-2.
· Use the apply isis level-1-2 command to specify both Level-1 and Level-2.
The tag value specified in the routing policy takes precedence over the tag value specified in this command.
Examples
# Configure IS-IS process 1 to advertise a Level-2 IPv6 default route.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] default-route-advertise
Related commands
apply isis
display isis redistribute ipv6
Use display isis redistribute ipv6 to display information about redistributed IPv6 IS-IS routes.
Syntax
display isis redistribute ipv6 [ ipv6-address mask-length ] [ level-1 | level-2 ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv6-address mask-length: Displays redistributed routes for the specified IPv6 address and mask length.
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535.
level-1: Displays IPv6 IS-IS Level-1 route information.
level-2: Displays IPv6 IS-IS Level-2 route information.
Usage guidelines
If no IPv6 IS-IS level is specified, this command displays both Level-1 and Level-2 route information.
Examples
# Display information about redistributed IPv6 IS-IS routes.
<Sysname> display isis redistribute ipv6 1
Route information for IS-IS(1)
------------------------------
Level-1 IPv6 Redistribute Table
--------------------------------
Type : direct Destination: 12:1::/64
IntCost : 0 Tag :
State : Active
Level-2 IPv6 Redistribute Table
--------------------------------
Type : direct Destination: 12:1::/64
IntCost : 0 Tag :
State : Active
Table 166 Command output
|
Field |
Description |
|
Route information for IS-IS(1) |
Redistributed route information for IS-IS process 1. |
|
Level-1 IPv6 Redistribute Table |
Redistributed route information of IS-IS Level-1. |
|
Level-2 IPv6 Redistribute Table |
Redistributed route information of IS-IS Level-2. |
|
Type |
Redistributed route types: · Direct. · IS-ISv6. · Static. · OSPFv3. · BGP4+. · RIPng. |
|
Destination |
IPv6 destination address. |
|
IntCost |
Internal route cost. |
|
Tag |
Tag value. |
|
State |
Indicates whether the redistributed route is valid. |
display isis route ipv6
Use display isis route ipv6 to display IPv6 IS-IS route information.
Syntax
display isis route ipv6 [ ipv6-address ] [ [ level-1 | level-2 ] | verbose ] * [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv6-address: Displays IPv6 IS-IS route information with the specified IPv6 destination address.
level-1: Displays Level-1 IPv6 IS-IS route information.
level-2: Displays Level-2 IPv6 IS-IS route information.
verbose: Displays detailed IPv6 IS-IS routing information.
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535.
Usage guidelines
If no level is specified, this command displays both Level-1 and Level-2 route information.
Examples
# Display IPv6 IS-IS route information.
<Sysname> display isis route ipv6
Route information for IS-IS(1)
------------------------------
Level-1 IPv6 forwarding table
-----------------------------
Destination: 2001:1:: PrefixLen: 64
Flag : R/L/- Cost : 20
Next hop : FE80::200:5EFF:FE64:8905 Interface: GE1/0/1
Destination: 2001:2:: PrefixLen: 64
Flag : D/L/- Cost : 10
Next hop : Direct Interface: GE1/0/1
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down bit set
Level-2 IPv6 forwarding table
-----------------------------
Destination: 2001:1:: PrefixLen: 64
Flag : -/-/- Cost : 20
Destination: 2001:2:: PrefixLen: 64
Flag : D/L/- Cost : 10
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down bit set
Table 167 Command output
|
Field |
Description |
|
Destination |
IPv6 destination prefix. |
|
PrefixLen |
Length of the prefix. |
|
Flag/Flags |
Route flag: · D—This is a direct route. · R—The route has been added into the routing table. · L—The route has been advertised in an LSP. · U—Route leaking flag, indicating that the Level-1 route is from Level-2. U means the route will not be returned to Level-2. |
|
Cost |
Route cost. |
|
Next hop |
Next hop. |
|
Interface |
Output interface. |
# Display detailed IPv6 IS-IS routing information.
<Sysname> display isis route ipv6 verbose
Route information for IS-IS(1)
------------------------------
Level-1 IPv6 forwarding table
-----------------------------
IPv6 dest : 2001:1::/64
Flag : D/L/- Cost : 10
Admin tag : - Src count : 2
Nexthop : Direct
Interface : GE1/0/1
Nib ID : 0x0
IPv6 dest : 2001:2::/64
Flag : R/-/- Cost : 20
Admin tag : - Src count : 2
Nexthop : FE80::200:5EFF:FE64:8905
Interface : GE1/0/1
BkNexthop : FE80::200:5EFF:FE64:8905
BkInterface : GE1/0/1
Nib ID : 0x24000002
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down bit set
Level-2 IPv6 Forwarding Table
-----------------------------
IPv6 dest : 2001:1::/64
Flag : D/L/- Cost : 10
Admin tag : - Src count : 2
Nexthop : -
Interface : -
Nib ID : -
IPv6 dest : 2001:2::/64
Flag : D/L/- Cost : 10
Admin tag : - Src count : 2
Nexthop : -
Interface : -
Nib ID : -
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Table 168 Command output
|
Field |
Description |
|
IPv6 dest |
IPv6 destination address and prefix. |
|
Flag/Flags |
Route flag: · D—This is a direct route. · R—The route has been added into the routing table. · L—The route has been advertised in an LSP. · U—Route leaking flag, indicating the Level-1 route is from Level-2. U means the route will not be returned to Level-2. |
|
Cost |
Route cost. |
|
Admin tag |
Administrative tag. |
|
Src count |
Number of advertisement sources. |
|
Nexthop |
Next hop. |
|
Interface |
Output interface. |
|
BkNexthop |
Backup next hop. |
|
BkInterface |
Backup output interface. |
|
Nib ID |
Next hop index assigned by the routing management module. |
display isis spf-tree ipv6
Use display isis spf-tree ipv6 to display IPv6 IS-IS topology information.
Syntax
display isis spf-tree ipv6 [ [ level-1 | level-2 ] | verbose ] * [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
level-1: Displays Level-1 IPv6 IS-IS topology information. If you do not specify this keyword, the command displays both Level-1 and Level-2 topology information.
level-2: Displays Level-2 IPv6 IS-IS topology information. If you do not specify this keyword, the command displays both Level-1 and Level-2 topology information.
verbose: Displays detailed IPv6 IS-IS topology information. If you do not specify this keyword, the command displays brief IPv6 IS-IS topology information.
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535. If you do not specify this argument, the command displays IPv6 topology information about all IS-IS processes.
Examples
# Display brief IPv6 IS-IS topology information.
<Sysname> display isis spf-tree ipv6
Shortest Path Tree for IS-IS(1)
-------------------------------
Flags: S-Node is on SPF tree T-Node is on tent list
O-Node is overload R-Node is directly reachable
I-Node or Link is isolated D-Node or Link is to be deleted
C-Neighbor is child P-Neighbor is parent
V-Link is involved N-Link is a new path
L-Link is on change list U-Protocol usage is changed
H-Nexthop is changed
Level-1 Shortest Path Tree
----------------------------------
SpfNode NodeFlag SpfLink LinkCost LinkFlag
-------------------------------------------------------------------------------
0000.0000.0032.00 S/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/C/-/-/-/-/-/-
-->0000.0000.0064.00 10 -/-/C/-/-/-/-/-/-
0000.0000.0032.01 S/-/-/R/-/-
-->0000.0000.0064.00 0 -/-/C/-/-/-/-/-/-
-->0000.0000.0032.00 0 -/-/-/P/-/-/-/-/-
0000.0000.0064.00 S/-/-/R/-/-
-->0000.0000.0032.00 10 -/-/-/P/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/-/P/-/-/-/-/-
Level-2 Shortest Path Tree
----------------------------------
SpfNode NodeFlag SpfLink LinkCost LinkFlag
-------------------------------------------------------------------------------
0000.0000.0032.00 S/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/C/-/-/-/-/-/-
-->0000.0000.0064.00 10 -/-/C/-/-/-/-/-/-
0000.0000.0032.01 S/-/-/R/-/-
-->0000.0000.0064.00 0 -/-/C/-/-/-/-/-/-
-->0000.0000.0032.00 0 -/-/-/P/-/-/-/-/-
0000.0000.0064.00 S/-/-/R/-/-
-->0000.0000.0032.00 10 -/-/-/P/-/-/-/-/-
-->0000.0000.0032.01 10 -/-/-/P/-/-/-/-/-
# Display detailed Level-1 IPv6 IS-IS topology information.
<Sysname> display isis spf-tree ipv6 level-1 verbose
Shortest Path Tree for IS-IS(1)
-------------------------------
Flags: S-Node is on SPF tree T-Node is on tent list
O-Node is overload R-Node is directly reachable
I-Node or Link is isolated D-Node or Link is to be deleted
C-Neighbor is child P-Neighbor is parent
V-Link is involved N-Link is a new path
L-Link is on change list U-Protocol usage is changed
H-Nexthop is changed
Level-1 Shortest Path Tree
--------------------------
SpfNode : 0000.0000.0032.00
Distance : 0
TE distance : 0
NodeFlag : S/-/-/-/-/-
RelayNibID : 0x0
TE tunnel count: 0
Nexthop count : 0
SpfLink count : 2
-->0000.0000.0032.01
LinkCost : 10
LinkNewCost : 10
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface: N/A
Cost : 10 Nexthop : N/A
-->0000.0000.0064.00
LinkCost : 10
LinkNewCost : 10
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface: Tun1
Cost : 10 Nexthop : FE80::A0A:A40
SpfNode : 0000.0000.0032.01
Distance : 10
TE distance : 10
NodeFlag : S/-/-/R/-/-
RelayNibID : 0x0
TE tunnel count: 0
Nexthop count : 0
SpfLink count : 2
-->0000.0000.0064.00
LinkCost : 0
LinkNewCost : 0
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface: GE1/0/2
Cost : 10 Nexthop : FE80::200:12FF:FE34:1
-->0000.0000.0032.00
LinkCost : 0
LinkNewCost : 0
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type : Adjacent Interface: N/A
Cost : 0 Nexthop : N/A
SpfNode : 0000.0000.0064.00
Distance : 10
TE distance : 10
NodeFlag : S/-/-/R/-/-
RelayNibID : 0x0
TE tunnel count: 0
Nexthop count : 2
Neighbor : 0000.0000.0064.00 Interface : GE1/0/2
NextHop : FE80::200:12FF:FE34:1
BkNeighbor: N/A BkInterface: N/A
BkNextHop : N/A
Neighbor : 0000.0000.0064.00 Interface : Tun1
NextHop : FE80::A0A:A40
BkNeighbor: N/A BkInterface: N/A
BkNextHop : N/A
SpfLink count : 2
-->0000.0000.0032.00
LinkCost : 10
LinkNewCost : 10
LinkFlag : -/-/-/P/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface: N/A
Cost : 10 Nexthop : N/A
AdvMtID : 0
-->0000.0000.0064.00
LinkCost : 10
LinkNewCost : 10
LinkFlag : -/-/C/-/-/-/-/-/-
LinkSrcCnt : 1
Type : Remote Interface: Tun1
Cost : 10 Nexthop : FE80::A0A:A40
AdvMtID : 0
Table 169 Command output
|
Field |
Description |
|
SpfNode |
ID of the topology node. |
|
Distance |
Shortest distance from the root node to the current node. |
|
TE distance |
Shortest distance from the root node to the current node (including tunnel links). If no tunnels are configured, TE distance equals Distance. |
|
NodeFlag |
Node flag: · S—The node is on the SPF tree. · T—The node is on the tent list. · O—The node is overloaded. · R—The node is directly connected. · I—The node is isolated. · D—The node is to be deleted. |
|
TE tunnel count |
Number of tunnels destined for this node. |
|
Nexthop count |
Number of next hops. |
|
NextHop |
Primary next hop of the node or the link advertising source. |
|
AdvMtID |
Topology from which the routing information is learned: · 0—Base topology. · 6-4094—Other topologies. |
|
Interface |
Primary output interface of the node or the link advertising source. |
|
BkNextHop |
Backup next hop. |
|
BkInterface |
Backup output interface. |
|
Neighbor |
ID of the primary next hop neighbor. |
|
BkNeighbor |
ID of the backup next hop neighbor. |
|
SpfLink |
Topology link. |
|
SpfLink count |
Number of topology links. |
|
LinkCost |
Link cost. |
|
LinkNewCost |
New link cost. |
|
LinkFlag |
Link flag: · I—The link is isolated. · D—The link is to be deleted. · C—The neighbor is a child node. · P—The neighbor is the parent node. · V—The link is involved. · N—The link is a new path. · L—The link is on the change list. · U—The protocol of the link is changed. · H—The next hop of the link is changed. |
|
LinkSrcCnt |
Number of link advertising sources. |
|
Type |
Type of the link advertising source: · Adjacent—The link advertising source is a local neighbor. · Remote—The link advertising source is advertised by a remote node in an LSP. |
|
Cost |
Cost of the link advertising source. |
display isis statistics ipv6
Use display isis statistics ipv6 to display IPv6 IS-IS statistics.
Syntax
display isis statistics ipv6 [ level-1 | level-1-2 | level-2 ] [ process-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
level-1: Displays IPv6 IS-IS Level-1 statistics.
level-1-2: Displays IPv6 IS-IS Level-1-2 statistics.
level-2: Displays IPv6 IS-IS Level-2 statistics.
process-id: Displays statistics for an IS-IS process specified by its ID in the range of 1 to 65535. If you do not specify an IS-IS process, this command displays the statistics for all IS-IS processes.
Usage guidelines
If you do not specify a level, this command displays both Level-1 and Level-2 statistics.
Examples
# Display IPv6 IS-IS statistics.
<Sysname> display isis statistics ipv6
Statistics information for IS-IS(1)
-----------------------------------
Level-1 Statistics
------------------
MTR(base)
Learnt routes information:
Total IPv6 Learnt Routes in IPv6 Routing Table: 0
Imported routes information:
IPv6 Imported Routes:
Static: 0 Direct: 0
ISISv6: 0 BGP4+: 0
RIPng: 0 OSPFv3: 0
Total Number: 0
Level-2 Statistics
------------------
MTR(base)
Learnt routes information:
Total IPv6 Learnt Routes in IPv6 Routing Table: 0
Imported routes information:
IPv6 Imported Routes:
Static: 0 Direct: 0
ISISv6: 0 BGP4+: 0
RIPng: 0 OSPFv3: 0
Total Number: 0
Table 170 Command output
|
Field |
Description |
|
Statistics information for IS-IS(processid) |
Statistics for the IPv6 IS-IS process. |
|
MTR(topo-name) |
MTR topology. base represents the base topology. |
|
Learnt routes information |
Total IPv6 Learnt Routes in IPv6 Routing Table means the number of learned IPv6 routes. |
|
IPv6 Imported Routes |
Numbers of different types of redistributed IPv6 routes, including static, direct, IS-ISv6, BGP4+, RIPng, and OSPFv3 routes. |
|
Lsp information |
LSP information: · LSP Source ID—ID of the source system. · No. of used LSPs—Number of used LSPs. |
fast-reroute
Use fast-reroute to configure IPv6 IS-IS FRR.
Use undo fast-reroute to disable IPv6 IS-IS FRR.
Syntax
fast-reroute { lfa | route-policy route-policy-name }
undo fast-reroute
Default
IPv6 IS-IS FRR is disabled.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
lfa: Calculates a backup next hop through Loop Free Alternate (LFA) calculation for all routes.
route-policy route-policy-name: Uses the specified routing policy to designate a backup next hop. The route-policy-name argument is a case-sensitive string of 1 to 63 characters.
Usage guidelines
ECMP routes do not support FRR.
Examples
# Enable IPv6 IS-IS FRR to calculate a backup next hop through LFA calculation for all routes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] fast-reroute lfa
Related commands
display isis route ipv6
filter-policy export
Use filter-policy export to configure IPv6 IS-IS to filter redistributed routes.
Use undo filter-policy export to remove the configuration.
Syntax
filter-policy { ipv6-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } export [ protocol [ process-id ] ]
undo filter-policy export [ protocol [ process-id ] ]
Default
IPv6 IS-IS does not filter redistributed routes.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999 to filter redistributed routes.
prefix-list prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter the redistributed routes.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter redistributed routes.
protocol: Filters routes redistributed from the specified routing protocol. If you do not specify this argument, the command filters routes redistributed from all routing protocols.
process-id: Specifies a process by its ID in the range of 1 to 65535. This argument is available only when the protocol is isisv6, ospfv3, or ripng.
Usage guidelines
This command filters routes redistributed by the import-route command. Only routes that have not been filtered can be advertised.
To reference an advanced ACL (with a number from 3000 to 3999) in the command or in the routing policy, configure the ACL using one of the following methods:
· To deny/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ipv6 source sour sour-prefix command.
· To deny/permit a route with the specified destination and prefix, use the rule [ rule-id ] { deny | permit } ipv6 source sour sour-prefix destination dest dest-prefix command.
The source keyword specifies the destination address of a route and the destination keyword specifies the prefix of the route. The specified prefix must be valid. Otherwise, the configuration does not take effect.
Examples
# Use IPv6 basic ACL 2006 to filter redistributed routes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] filter-policy 2006 export
# Configure IPv6 advanced ACL 3000 to permit only route 2001::1/128 to pass. Use the ACL to filter redistributed routes.
<Sysname> system-view
[Sysname] acl ipv6 advanced 3000
[Sysname-acl-ipv6-adv-3000] rule 10 permit ipv6 source 2001::1 128 destination ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff 128
[Sysname-acl-ipv6-adv-3000] rule 100 deny ipv6
[Sysname-acl-ipv6-adv-3000] quit
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] filter-policy 3000 export
Related commands
filter-policy import
filter-policy import
Use filter-policy import to configure IPv6 IS-IS to filter received routes.
Use undo filter-policy import to restore the default.
Syntax
filter-policy { ipv6-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } import
undo filter-policy import
Default
IPv6 IS-IS does not filter received routes.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999 to filter received routes.
prefix-list ipv6-prefix-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters, to filter received routes.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter received routes.
Usage guidelines
This command filters received routes. Only routes that have not been filtered can be added into the routing table.
To reference an advanced ACL (with a number from 3000 to 3999) in the command or in the routing policy, configure the ACL using one of the following methods:
· To deny/permit a route with the specified destination, use the rule [ rule-id ] { deny | permit } ipv6 source sour sour-prefix command.
· To deny/permit a route with the specified destination and prefix, use the rule [ rule-id ] { deny | permit } ipv6 source sour sour-prefix destination dest dest-prefix command.
The source keyword specifies the destination address of a route and the destination keyword specifies the prefix of the route. The specified prefix must be valid. Otherwise, the configuration does not take effect.
Examples
# Use IPv6 basic ACL 2003 to filter received routes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] filter-policy 2003 import
# Configure IPv6 advanced ACL 3000 to permit only route 2001::1/128 to pass. Use the ACL to filter received routes.
<Sysname> system-view
[Sysname] acl ipv6 advanced 3000
[Sysname-acl-ipv6-adv-3000] rule 10 permit ipv6 source 2001::1 128 destination ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff 128
[Sysname-acl-ipv6-adv-3000] rule 100 deny ipv6
[Sysname-acl-ipv6-adv-3000] quit
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] filter-policy 3000 import
Related commands
filter-policy export
import-route
Use import-route to enable IPv6 IS-IS to redistribute routes from another routing protocol.
Use undo import-route to remove the configuration.
Syntax
import-route protocol [ as-number | process-id ] [ allow-ibgp ] [ allow-direct | cost cost-value | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name| tag tag ] *
undo import-route protocol [ process-id ]
Default
IPv6 does not redistribute routes from any other routing protocol.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
protocol: Redistributes routes from the specified routing protocol.
as-number: Specifies an AS by its number in the range of 1 to 4294967295. This argument applies only to the bgp4+ protocol. If you do not specify this argument, the command redistributes all IPv6 EBGP routes. As a best practice, specify an AS to prevent the system from redistributing excessive routes.
process-id: Specifies a process by its ID in the range of 1 to 65535. The default value is 1. This argument is available only when the protocol is ripng, isisv6, or ospfv3.
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. If you specify both the allow-direct keyword and the route-policy route-policy-name option, make sure the if-match rule defined in the routing policy does not conflict with the allow-direct keyword. For example, if you specify the allow-direct keyword, do not configure the if-match route-type rule for the routing policy. Otherwise, the allow-direct keyword does not take effect.
cost cost-value: Specifies a cost for redistributed routes, in the range of 0 to 4261412864.
level-1: Redistributes routes into the Level-1 routing table.
level-1-2: Redistributes routes into Level-1 and Level-2 routing tables.
level-2: Redistributes routes into the Level-2 routing table. If you do not specify a level, the routes are redistributed into the Level-2 routing table.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters, to filter redistributed routes.
tag tag: Specifies an administrative tag for marking redistributed routes, in the range of 1 to 4294967295.
allow-ibgp: Allows redistribution of IBGP routes. This keyword is available only when the protocol is bgp4+.
Usage guidelines
IPv6 IS-IS considers redistributed routes as AS-external routes.
You can specify a cost and a level for redistributed routes.
The import-route bgp4+ command redistributes only EBGP routes. The import-route bgp4+ allow-ibgp command redistributes both EBGP and IBGP routes, and might cause routing loops. Therefore, use it with caution.
Examples
# Configure IPv6 IS-IS to redistribute static routes and set the cost for redistributed routes to 15.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] import-route static cost 15
import-route isisv6 level-1 into level-2
Use import-route isisv6 level-1 into level-2 to enable route advertisement from Level-1 to Level-2.
Use undo import-route isisv6 level-1 into level-2 to disable route advertisement from Level-1 to Level-2.
Syntax
import-route isisv6 level-1 into level-2 [ filter-policy { ipv6-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } | tag tag ] *
undo import-route isisv6 level-1 into level-2
Default
Route advertisement from Level-1 to Level-2 is enabled.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
filter-policy: Specifies a filtering policy.
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999.
prefix-list prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
tag tag: Specifies an administrative tag for marking redistributed routes, in the range of 1 to 4294967295.
Usage guidelines
This command enables a Level-1-2 router to redistribute Level-1 routes to Level-2 routers and Level-1-2 routers in the local area.
Examples
# Enable route advertisement from Level-1 to Level-2.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] import-route isisv6 level-1 into level-2
import-route isisv6 level-2 into level-1
Use import-route isisv6 level-2 into level-1 to enable IPv6 IS-IS route advertisement from Level-2 to Level-1.
Use undo import-route isisv6 level-2 into level-1 to restore the default.
Syntax
import-route isisv6 level-2 into level-1 [ filter-policy { ipv6-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } | tag tag ] *
undo import-route isisv6 level-2 into level-1
Default
Route advertisement from Level-2 to Level-1 is disabled.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
filter-policy: Specifies a filtering policy.
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999.
prefix-list prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
tag: Specifies an administrative tag for marking redistributed routes, in the range of 1 to 4294967295.
Usage guidelines
This command enables a Level-1-2 router to redistribute Level-2 routes to the Level-1 and Level-1-2 routers in the local area.
Examples
# Enable IPv6 IS-IS route advertisement from Level-2 to Level-1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] import-route isisv6 level-2 into level-1
import-route limit
Use import-route limit to configure the maximum number of redistributed Level-1/Level-2 IPv6 routes.
Use undo import-route limit to restore the default.
Syntax
import-route limit number
undo import-route limit
Default
The following matrix shows the default maximum number of redistributed Level-1/Level-2 IPv6 routes:
|
Hardware |
Default state |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
201024 |
|
MSR2600-6-X1/2600-10-X1 |
301024 |
|
MSR 2630 |
301024 |
|
MSR3600-28/3600-51 |
301024 |
|
MSR3600-28-SI/3600-51-SI |
201024 |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
501024 |
|
MSR 3610 |
201024 |
|
MSR 3620/3620-DP/3640/3660 |
501024 |
|
MSR5620/5660/5680 |
1001024 |
|
Hardware |
Default value |
|
MSR810-LM-GL |
201024 |
|
MSR810-W-LM-GL |
201024 |
|
MSR830-6EI-GL |
201024 |
|
MSR830-10EI-GL |
201024 |
|
MSR830-6HI-GL |
201024 |
|
MSR830-10HI-GL |
201024 |
|
MSR2600-6-X1-GL |
301024 |
|
MSR3600-28-SI-GL |
201024 |
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of redistributed Level-1/Level-2 IPv6 routes.
The following matrix shows the value ranges for the number argument:
|
Hardware |
Value range |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS |
1 to 201024 |
|
MSR2600-6-X1/2600-10-X1 |
1 to 301024 |
|
MSR 2630 |
1 to 301024 |
|
MSR3600-28/3600-51 |
1 to 301024 |
|
MSR3600-28-SI/3600-51-SI |
1 to 201024 |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
1 to 501024 |
|
MSR 3610 |
1 to 201024 |
|
MSR 3620/3620-DP/3640/3660 |
1 to 501024 |
|
MSR5620/5660/5680 |
1 to 1001024 |
Examples
# Configure IS-IS process 1 to redistribute a maximum of 1000 Level-1/Level-2 IPv6 routes.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] import-route limit 1000
isis ipv6 bfd enable
Use isis ipv6 bfd enable to enable BFD for IPv6 IS-IS.
Use undo isis ipv6 bfd enable to disable BFD for IPv6 IS-IS.
Syntax
isis ipv6 bfd enable
undo isis ipv6 bfd enable
Default
BFD for IPv6 IS-IS is disabled.
Views
Interface view
Predefined user roles
network-admin
Examples
# Enable BFD for IPv6 IS-IS on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis ipv6 bfd enable
isis ipv6 cost
Use isis ipv6 cost to set the IPv6 IS-IS cost for an interface.
Use undo isis ipv6 cost to remove the configuration.
Syntax
isis ipv6 cost cost-value [ level-1 | level-2 ]
undo isis ipv6 cost [ level-1 | level-2 ]
Default
No IPv6 IS-IS cost is configured for an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
cost-value: Specifies an IPv6 IS-IS cost in the range of 1 to 16777215.
level-1: Applies the cost to Level-1 routes.
level-2: Applies the cost to Level-2 routes.
Usage guidelines
This command applies to interfaces that are enabled with IPv6 IS-IS.
This command takes effect only when the standard MTR mode is enabled.
Examples
# Set the IPv6 IS-IS cost to 10 for GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] isis 100
[Sysname-isis-100] address-family ipv6 unicast
[Sysname-isis-100-ipv6] quit
[Sysname-isis-100] quit
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis ipv6 enable 100
[Sysname-GigabitEthernet1/0/1] isis ipv6 cost 10
isis ipv6 enable
Use isis ipv6 enable to enable IPv6 for IS-IS on an interface.
Use undo isis ipv6 enable to disable IPv6 for IS-IS on an interface.
Syntax
isis ipv6 enable [ process-id ]
undo isis ipv6 enable
Default
IPv6 is disabled for IS-IS on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
process-id: Specifies an IS-IS process by its ID in the range of 1 to 65535. The default is 1.
Examples
# Enable IPv6 for IS-IS on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] network-entity 10.0001.1010.1020.1030.00
[Sysname-isis-1] address-family ipv6 unicast
[Sysname-isis-1-ipv6] quit
[Sysname-isis-1] quit
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ipv6 address 2002::1/64
[Sysname-GigabitEthernet1/0/1] isis ipv6 enable 1
isis ipv6 fast-reroute lfa-backup exclude
Use isis ipv6 fast-reroute lfa-backup exclude to disable LFA calculation on an interface.
Use undo isis ipv6 fast-reroute lfa-backup exclude to restore the default.
Syntax
isis ipv6 fast-reroute lfa-backup exclude
undo isis ipv6 fast-reroute lfa-backup exclude
Default
LFA calculation is enabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Examples
# Disable LFA calculation on the interface GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] network-entity 10.0001.1010.1020.1030.00
[Sysname-isis-1] quit
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis ipv6 enable 1
[Sysname-GigabitEthernet1/0/1] isis ipv6 fast-reroute lfa-backup exclude
Related commands
fast-reroute
isis ipv6 prefix-suppression
Use isis ipv6 prefix-suppression to enable prefix suppression on an interface.
Use undo isis ipv6 prefix-suppression to disable prefix suppression on an interface.
Syntax
isis ipv6 prefix-suppression
undo isis ipv6 prefix-suppression
Default
Prefix suppression is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
By default, IS-IS interfaces advertise their IPv6 prefixes in LSPs. Use this command to disable an interface from advertising its IPv6 prefix in LSPs. This enhances network security by preventing IP routing to the internal nodes and speeds up network convergence.
Examples
# Enable prefix suppression on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis ipv6 prefix-suppression
isis ipv6 primary-path-detect bfd
Use isis ipv6 primary-path-detect bfd to enable BFD for IPv6 IS-IS.
Use undo isis ipv6 primary-path-detect bfd to disable BFD for IPv6 IS-IS.
Syntax
isis ipv6 primary-path-detect bfd { ctrl | echo }
undo isis ipv6 primary-path-detect bfd
Default
BFD is disabled for IPv6 IS-IS.
Views
Interface view
Predefined user roles
network-admin
Parameters
ctrl: Enables BFD control packet mode.
echo: Enables BFD echo packet mode.
Usage guidelines
This command enables IPv6 IS-IS FRR or IPv6 IS-IS PIC to use BFD to detect primary link failures.
Examples
# Enable BFD control packet mode for IPv6 IS-IS FRR on the interface GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] fast-reroute lfa
[Sysname-isis-1-ipv6] quit
[Sysname-isis-1] quit
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis ipv6 primary-path-detect bfd ctrl
# Enable BFD echo packet mode for IPv6 IS-IS PIC on the interface GigabitEthernet 1/0/2.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] pic additional-path-always
[Sysname-isis-1] quit
[Sysname] bfd echo-source-ipv6 1::1
[Sysname] interface gigabitethernet 1/0/2
[Sysname-GigabitEthernet1/0/2] isis ipv6 primary-path-detect bfd echo
isis ipv6 tag
Use isis ipv6 tag to configure the tag value on an interface.
Use undo isis ipv6 tag to restore the default.
Syntax
isis ipv6 tag tag
undo isis ipv6 tag
Default
No tag value is configured on an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
tag: Specifies a tag value in the range of 1 to 4294967295.
Usage guidelines
When IS-IS advertises an IPv6 prefix with a tag value, it adds the tag to the IPv6 reachability information TLV, regardless of the link cost style.
Examples
# Set the tag value on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] isis ipv6 tag 4294967295
ispf enable
Use ispf enable to enable IPv6 IS-IS incremental SPF (ISPF).
Use undo ispf enable to disable IPv6 IS-IS ISPF.
Syntax
ispf enable
undo ispf enable
Default
IPv6 IS-IS ISPF is enabled.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Usage guidelines
ISPF recomputes only the affected part of the shortest path tree (SPT) instead of the entire SPT when a network topology is changed.
Examples
# Enable IPv6 IS-IS ISPF.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] ispf enable
maximum load-balancing
Use maximum load-balancing to configure the maximum number of equal-cost multi-path (ECMP) routes for load balancing.
Use undo maximum load-balancing to restore the default.
Syntax
maximum load-balancing number
undo maximum load-balancing
Default
The maximum number of IPv6 IS-IS ECMP routes is 32.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of ECMP routes, in the range of 1 to 32.
Examples
# Set the maximum number of ECMP routes to 2.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] maximum load-balancing 2
multi-topology
Use multi-topology to enable IPv6 IS-IS MTR.
Use undo multiple-topology to disable IPv6 IS-IS MTR.
Syntax
multi-topology [ compatible ]
undo multi-topology
Default
IPv6 IS-IS MTR is disabled.
Views
IS-IS IPv6 address family view
Predefined user roles
network-admin
Parameters
compatible: Specifies the compatible mode to advertise IPv6 prefixes to both IPv4 and IPv6 topologies. If you do not specify this keyword, the command advertises IPv6 prefixes only to the IPv6 topology.
Usage guidelines
This command enables separate route calculation in IPv4 and IPv6 topologies.
This command is available when the link cost style is wide, compatible, or wide-compatible.
Examples
# Enable IPv6 IS-IS MTR.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] multi-topology
Related commands
cost-style
preference
Use preference to configure the preference for IPv6 IS-IS.
Use undo preference to restore the default.
Syntax
preference { preference | route-policy route-policy-name } *
undo preference
Default
The preference for IPv6 IS-IS is 15.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
preference: Specifies a preference for IPv6 IS-IS, in the range of 1 to 255.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
If multiple dynamic routing protocols find routes to the same destination, the route found by the protocol with the highest preference is selected as the optimal route.
Examples
# Set the preference for IPv6 IS-IS to 20.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] preference 20
prefix-priority
Use prefix-priority to assign a convergence priority to the specified IPv6 IS-IS routes.
Use undo prefix-priority to remove the configuration.
Syntax
prefix-priority { critical | high | medium } { prefix-list prefix-list-name | tag tag-value }
prefix-priority route-policy route-policy-name
undo prefix-priority { critical | high | medium } [ prefix-list | tag ]
undo prefix-priority route-policy
Default
IPv6 IS-IS routes have the low convergence priority.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
critical: Specifies the highest convergence priority.
high: Specifies the high convergence priority.
medium: Specifies the medium convergence priority.
route-policy route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
prefix-list prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters.
tag tag-value: Specifies a tag value in the range of 1 to 4294967295.
Usage guidelines
The higher the convergence priority, the faster the convergence speed.
IPv6 IS-IS host routes have a medium convergence priority.
Examples
# Assign the high convergence priority to IS-IS routes permitted by IPv6 prefix list standtest.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] prefix-priority high prefix-list standtest
set-overload
Use set-overload to set the overload bit.
Use undo set-overload to restore the default.
Syntax
set-overload [ on-startup [ [ start-from-nbr system-id [ timeout1 [ nbr-timeout ] ] ] | timeout2 | wait-for-bgp4+ [ timeout3 ] ] ] [ allow { external | interlevel } * ]
undo set-overload
Default
The overload bit is not set.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
on-startup: Sets the overload bit upon system startup.
start-from-nbr system-id [ timeout1 [ nbr-timeout ] ]: Starts the nbr-timeout timer when the router begins to establish the neighbor relationship with the neighbor after system startup. If the neighbor relationship is formed within the nbr-timeout interval, IS-IS keeps the overload bit set. If not, the bit is cleared. IS-IS keeps the overload bit set within the timeout1 interval after the neighbor relationship is formed within the nbr-timeout interval.
· system-id—Specifies the neighbor.
· timeout1—The value range for the timeout1 interval is 5 to 86400 seconds, and the default is 600 seconds.
· nbr-timeout—The timer has an interval from 5 to 86400 seconds. The default is 1200 seconds.
timeout2: Sets the overload bit within the timeout2 interval after system startup. The value range for the interval is 5 to 86400 seconds, and the default is 600 seconds.
wait-for-bgp4+ [ timeout3 ]: Starts the timeout3 timer for IPv6 BGP convergence after system startup. If IPv6 BGP is not converged within the timeout3 interval, IPv6 IS-IS clears the overload bit. The value range for the timeout3 argument is 5 to 86400 seconds, and the default is 600 seconds.
allow: Allows advertising address prefixes. By default, no address prefixes are allowed to be advertised when the overload bit is set.
external: Allows advertising IP address prefixes redistributed from other routing protocols with the allow keyword specified.
interlevel: Allows advertising IP address prefixes learned from different IS-IS levels with the allow keyword specified.
Usage guidelines
If the on-startup keyword is not specified, the command sets the overload bit immediately until the undo set-overload command is executed.
If the on-startup keyword is specified, IS-IS sets the overload bit upon system startup and keeps it set within the timeout2 interval.
Examples
# Set the overload bit on the current router.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] set-overload
summary
Use summary to configure an IPv6 IS-IS summary route.
Use undo summary to remove an IPv6 IS-IS summary route.
Syntax
summary ipv6-prefix prefix-length [ avoid-feedback | generate_null0_route | [ level-1 | level-1-2 | level-2 ] | tag tag ] *
undo summary ipv6-prefix prefix-length [ level-1 | level-1-2 | level-2 ]
Default
No summary route is configured.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
ipv6-prefix: Specifies an IPv6 prefix for the summary route.
prefix-length: Specifies the length of the IPv6 prefix, in the range of 0 to 128.
avoid-feedback: Avoids learning the summary route by route calculation.
generate_null0_route: Generates a NULL 0 route to avoid routing loops.
level-1: Summarizes only the routes redistributed to Level-1.
level-1-2: Summarizes all the routes redistributed to both Level-1 and Level-2.
level-2: Summarize only the routes redistributed to Level-2.
tag: Specifies an administrative tag in the range of 1 to 4294967295.
Usage guidelines
If no level is specified, the command applies to Level-2.
You can summarize routes with the same next hop into a single route to reduce the size of the routing table, as well as the size of the LSDB. This command can summarize both learned and redistributed IPv6 IS-IS routes. The cost of the summary route is the smallest cost of the summarized routes.
Examples
# Configure a summary route 2002::/32.
<Sysname> system-view
[Sysname] isis
[Sysname-isis-1] address-family ipv6
[Sysname-isis-1-ipv6] summary 2002:: 32
timer spf
Use timer spf to set the SPF calculation interval.
Use undo timer spf to restore the default.
Syntax
timer spf maximum-interval [ minimum-interval [ incremental-interval ] ]
undo timer spf
Default
The maximum interval is 5 seconds, the minimum interval is 50 milliseconds, and the incremental interval is 200 milliseconds.
Views
IS-IS IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
maximum-interval: Specifies the maximum SPF calculation interval in the range of 1 to 120 seconds.
minimum-interval: Specifies the minimum SPF calculation interval in the range of 10 to 60000 milliseconds.
incremental-interval: Specifies the incremental SPF calculation interval in the range of 10 to 60000 milliseconds.
Usage guidelines
Based on the LSDB, an IS-IS router uses the SPF algorithm to calculate an SPT with itself being the root. The router uses the SPT to determine the next hop to a destination network. By adjusting the SPF calculation interval, you can prevent bandwidth and router resources from being overused due to frequent topology changes.
For a stable network, the minimum interval is used. If network changes become frequent, the SPF calculation interval is incremented by the incremental interval for each calculation until the maximum interval is reached.
The minimum interval and the incremental interval cannot be greater than the maximum interval.
Examples
# Set the maximum, minimum, and incremental SPF calculation interval to 10 seconds, 100 milliseconds, and 300 milliseconds, respectively.
<Sysname> system-view
[Sysname] isis 1
[Sysname-isis-1] address-family ipv6
IPv6 policy-based routing commands
Commands and descriptions for centralized devices apply to the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/ 810-LMS/810-LUS.
· MSR2600-6-X1/2600-10-X1.
· MSR 2630.
· MSR3600-28/3600-51.
· MSR3600-28-SI/3600-51-SI.
· MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC.
· MSR 3610/3620/3620-DP/3640/3660.
· MSR810-LM-GL/810-W-LM-GL/830-6EI-GL/830-10EI-GL/830-6HI-GL/830-10HI-GL/2600-6-X1-GL/3600-28-SI-GL.
Commands and descriptions for distributed devices apply to the following routers:
· MSR5620.
· MSR 5660.
· MSR 5680.
apply access-vpn vpn-instance
Use apply access-vpn vpn-instance to set VPN instances.
Use undo apply access-vpn vpn-instance to remove VPN instances.
Syntax
apply access-vpn vpn-instance vpn-instance-name&<1-n>
undo apply access-vpn vpn-instance [ vpn-instance-name&<1-n> ]
Default
No VPN instance is specified for a node.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. The specified VPN must already exist.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify a maximum of n VPN instances for a node. The matching packets are forwarded according to the forwarding table of the first available VPN instance.
With a VPN instance specified, the undo apply access-vpn vpn-instance command removes the VPN instance.
Without any VPN instance specified, the undo apply access-vpn vpn-instance command removes all VPN instances.
Examples
# Set VPN 1 and VPN 2 for node 10. (VPN 1 and VPN 2 already exist.)
<Sysname> system-view
[Sysname] ipv6 policy-based-route policy1 permit node 10
[Sysname-pbr6-policy1-10] apply access-vpn vpn-instance vpn1 vpn2
Related commands
apply remark-vpn
apply continue
Use apply continue to compare packets with the next policy node upon failure on the current node.
Use undo apply continue to restore the default.
Syntax
apply continue
undo apply continue
Default
IPv6 PBR does not compare packets with the next policy node upon failure on the current node.
Views
IPv6 policy node view
Predefined user roles
network-admin
Usage guidelines
This command takes effect only when the mode of the node is permit.
This command applies when the following clauses are not configured or become invalid:
· apply access-vpn vpn-instance
· apply next-hop
· apply output-interface
· apply default-next-hop
· apply default-output-interface
For example, the command applies when the specified next hop is unreachable, the specified output interface is down, or the packets cannot be forwarded in the specified VPN instance.
Examples
# Compare with the next policy node upon failure on the current node.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply continue
apply default-next-hop
Use apply default-next-hop to set default next hops.
Use undo apply default-next-hop to remove default next hops.
Syntax
apply default-next-hop [ vpn-instance vpn-instance-name | inbound-vpn ] { ipv6-address [ direct ] [ track track-entry-number ] }&<1-n>
undo apply default-next-hop [ [ vpn-instance vpn-instance-name | inbound-vpn ] ipv6-address&<1-n> ]
Default
No default next hop is set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. The specified VPN must already exist.
inbound-vpn: Specifies the VPN instance where the inbound interface belongs.
ipv6-address: Specifies the IPv6 address of the default next hop. If you do not specify the vpn-instance vpn-instance-name option or the inbound-vpn keyword, the default next hop belongs to the public network.
direct: Specifies a directly connected default next hop.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify multiple default next hops for backup or load sharing in one command line or by executing this command multiple times.
With a default next hop specified, the undo apply default-next-hop command removes the default next hop.
Without any default next hop specified, the undo apply default-next-hop command removes all default next hops.
Examples
# Set a directly-connected default next hop of 1:1::1:1.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply default-next-hop 1:1::1:1 direct
Related commands
apply loadshare
apply default-output-interface
Use apply default-output-interface to set default output interfaces.
Use undo apply default-output-interface to remove default output interfaces.
Syntax
apply default-output-interface { interface-type interface-number [ track track-entry-number ] }&<1-n>
undo apply default-output-interface [ { interface-type interface-number }&<1-n> ]
Default
No default output interface is set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify multiple default output interfaces for backup or load sharing in one command line or by executing this command multiple times.
The default output interface must be P2P type. Using a non-P2P default output interface can result in forwarding failures when the interface has multiple next hops. Non-P2P interfaces include broadcast and non-broadcast multi-access (NBMA) interfaces such as Ethernet and virtual-template interfaces. In NBMA networks, packets are sent in unicast.
With a default output interface specified, the undo apply default-output-interface command removes the default output interface.
Without any default output interface specified, the undo apply default-output-interface command removes all default output interfaces.
Examples
# Specify GigabitEthernet 1/0/1 as the default output interface for IPv6 packets.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply default-output-interface gigabitethernet 1/0/1
Related commands
apply loadshare
apply loadshare
Use apply loadshare to enable load sharing among multiple next hops, output interfaces, default next hops, or default output interfaces.
Use undo apply loadshare to restore the default.
Syntax
apply loadshare { default-next-hop | default-output-interface | next-hop | output-interface }
undo apply loadshare { default-next-hop | default-output-interface | next-hop | output-interface }
Default
Multiple next hops, output interfaces, default next hops, or default output interfaces operate in primary/backup mode.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
default-next-hop: Enables load sharing among multiple default next hops.
default-output-interface: Enables load sharing among multiple default output interfaces.
next-hop: Enables load sharing among multiple next hops.
output-interface: Enables load sharing among multiple output interfaces.
Usage guidelines
Multiple next hops, output interfaces, default next hops, or default output interfaces operate in either primary/backup or load sharing mode. For example:
· Primary/backup mode—The first configured output interface is used. When the primary output interface fails, the first configured backup output interface takes over.
· Load sharing mode—Multiple output interfaces load share traffic on a per-packet basis in turn, according to the configuration order.
|
|
NOTE: Multiple next hops load share traffic according to their weights. By default, all next hops have the same weight and traffic is load balanced among them. |
Examples
# Enable load sharing among multiple next hops.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply next-hop 1::1 2::2
[Sysname-pbr6-aa-11] apply loadshare next-hop
# Enable load sharing among multiple output interfaces.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply output-interface gigabitethernet 1/0/1 gigabitethernet 1/0/2
[Sysname-pbr6-aa-11] apply loadshare output-interface
# Enable load sharing among multiple default next hops.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply default-next-hop 1::1 2::2
[Sysname-pbr6-aa-11] apply loadshare default-next-hop
# Enable load sharing among multiple default output interfaces.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply default-output-interface gigabitethernet 1/0/1 gigabitethernet 1/0/2
[Sysname-pbr6-aa-11] apply loadshare default-output-interface
Related commands
apply default-next-hop
apply default-output-interface
apply next-hop
apply output-interface
apply next-hop
Use apply next-hop to set next hops.
Use undo apply next-hop to remove next hops.
Syntax
apply next-hop [ vpn-instance vpn-instance-name | inbound-vpn ] { ipv6-address [ direct ] [ track track-entry-number ] [ weight weight-value ] } &<1-n>
undo apply next-hop [ [ vpn-instance vpn-instance-name | inbound-vpn ] ipv6-address&<1-n> ]
Default
No next hop is set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. The specified VPN must already exist.
inbound-vpn: Specifies the VPN instance where the inbound interface belongs.
ipv6-address: Specifies the IPv6 address of the next hop. If you do not specify the vpn-instance vpn-instance-name option or the inbound-vpn keyword, the next hop belongs to the public network.
direct: Specifies that the next hop must be directly connected to take effect.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
weight weight-value: Specifies a load sharing weight for the next hop, in the range of 1 to 100. The default is 10. If you specify weights 1, 1, and 2 for three next hops, they share 1/4, 1/4, and 1/2 of the whole traffic, respectively.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify multiple next hops for backup or load sharing in one command line or by executing this command multiple times.
With a next hop specified, the undo apply next-hop command removes the next hop.
Without any next hop specified, the undo apply next-hop command removes all next hops.
Examples
# Set a directly-connected next hop of 1::1.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply next-hop 1::1
Related commands
apply loadshare
apply output-interface
Use apply output-interface to set output interfaces.
Use undo apply output-interface to remove output interfaces.
Syntax
apply output-interface { interface-type interface-number [ track track-entry-number ] }&<1-n>
undo apply output-interface [ { interface-type interface-number }&<1-n> ]
Default
No output interface is set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify multiple output interfaces for backup or load sharing in one command line or by executing this command multiple times.
The output interface must be P2P type. Using a non-P2P output interface can result in forwarding failures when the interface has multiple next hops. Non-P2P interfaces include broadcast and NBMA interfaces such as Ethernet and virtual-template interfaces.
With an output interface specified, the undo apply output-interface command removes the output interface.
Without any output interface specified, the undo apply output-interface command removes all output interfaces.
Examples
# Specify GigabitEthernet 1/0/1 as the output interface for IPv6 packets.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply output-interface gigabitethernet 1/0/1
Related commands
apply loadshare
apply precedence
Use apply precedence to set a precedence for IPv6 packets.
Use undo apply precedence to restore the default.
Syntax
apply precedence { type | value }
undo apply precedence
Default
No precedence is set for IPv6 packets.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
type: Specifies the precedence type for IPv6 packets.
value: Specifies the precedence for IPv6 packets. Eight precedence values (0 to 7) are available. Each precedence value corresponds to a precedence type, as shown in Table 171. You can set either a precedence value or a precedence type for IPv6 packets.
Table 171 IP precedences and the corresponding types
|
Precedence value |
Precedence type |
|
0 |
routine |
|
1 |
priority |
|
2 |
immediate |
|
3 |
flash |
|
4 |
flash-override |
|
5 |
critical |
|
6 |
internet |
|
7 |
network |
Examples
# Set the precedence to 5 (critical) for IPv6 packets.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply precedence critical
apply remark-vpn
Use apply remark-vpn to mark the VPN instance for matching packets.
Use undo apply remark-vpn to restore the default.
Syntax
apply remark-vpn
undo apply remark-vpn
Default
The VPN instance is not marked for matching packets.
Views
IPv6 policy node view
Predefined user roles
network-admin
Usage guidelines
The apply access-vpn vpn-instance command is used to forward matching packets in a specified VPN instance. To make the VPN instance known to the service modules, use the apply remark-vpn command to mark the VPN instance in the packets.
This command must be used together with the apply access-vpn vpn-instance command.
This command marks a VPN instance in a packet only when the packet is forwarded in the VPN instance specified by the apply access-vpn vpn-instance command.
Examples
# Mark VPN instance vpn1 for packets that match ACL 3000.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aaa permit node 10
[Sysname-pbr6-aaa-10] if-match acl 3000
[Sysname-pbr6-aaa-10] apply access-vpn vpn-instance vpn1
[Sysname-pbr6-aaa-10] apply remark-vpn
Related commands
apply access-vpn vpn-instance
display ipv6 policy-based-route
Use display ipv6 policy-based-route to display IPv6 PBR policy information.
Syntax
display ipv6 policy-based-route [ policy policy-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
policy policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. If you do not specify a policy, this command displays information for all IPv6 PBR policies.
Examples
# Display all IPv6 policy information.
<Sysname> display ipv6 policy-based-route
Policy name: aaa
node 1 permit:
if-match acl 2000
apply next-hop 1000::1
Table 172 Command output
|
Field |
Description |
|
node 1 permit |
The match mode of Node 1 is permit. |
|
if-match acl |
Compares IPv6 packets with IPv6 ACL. |
|
apply next-hop |
Specifies a next hop for permitted IPv6 packets. |
Related commands
ipv6 policy-based-route (system view)
display ipv6 policy-based-route interface
Use display ipv6 policy-based-route interface to display IPv6 interface PBR configuration and statistics.
Syntax
Centralized devices in standalone mode:
display ipv6 policy-based-route interface interface-type interface-number
Distributed devices in standalone mode/centralized devices in IRF mode:
display ipv6 policy-based-route interface interface-type interface-number [ slot slot-number ]
Distributed devices in IRF mode:
display ipv6 policy-based-route interface interface-type interface-number [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays IPv6 interface PBR configuration and statistics for the active MPU. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays IPv6 interface PBR configuration and statistics for the master device. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays IPv6 interface PBR configuration and statistics for the global active MPU. (Distributed devices in IRF mode.)
Examples
# Display IPv6 PBR configuration and statistics on GigabitEthernet 1/0/1.
<Sysname> display ipv6 policy-based-route interface gigabitethernet 1/0/1
Policy based routing information for interface GigabitEthernet1/0/1(failed):
Policy name: aaa
node 0 deny:
Matched: 0
node 1 permit:
if-match acl 3999
Matched: 0
node 2 permit:
if-match acl 2000
apply next-hop 1000::1
apply output-interface GigabitEthernet1/0/2 track 1 (down)
apply output-interface GigabitEthernet1/0/3 track 2 (inactive)
Matched: 0
node 5 permit:
if-match acl 3101
apply next-hop 1000::1
Matched: 0
Total matched: 0
<Sysname> display ipv6 policy-based-route interface gigabitethernet 1/0/1
Policy based routing information for interface GigabitEthernet1/0/1:
Policy name: aaa
node 0 deny(not support):
Matched: 0
node 1 permit:
if-match acl 3999
Matched: 0
node 2 permit(no resource):
if-match acl 2000
apply next-hop 1000::1
apply output-interface GigabitEthernet1/0/2 track 1 (down)
apply output-interface GigabitEthernet1/0/3 track 2 (inactive)
Matched: 0
node 5 permit:
if-match acl 3101
apply next-hop 1000::1
Matched: 0 (no statistics resource)
Total matched: 0
Table 173 Command output
|
Field |
Description |
|
Policy based routing information for interface GigabitEthernet1/0/1(failed) |
IPv6 PBR configuration and statistics on GigabitEthernet 1/0/1. This field displays failed in brackets if none of the nodes in the policy has been successfully issued to the driver. NOTE: The failed status is available on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command. · For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces. · For a physical interface, specify its slot number. |
|
node 0 deny(not support) node 2 permit(no resource) |
Match mode of the node, permit or deny. If a node fails to be issued to the driver, the command displays the cause in brackets, which include: · not support—The device does not support the match criteria configured on the node. · no resource—No sufficient resources (for example, ACLs) are available for the node. NOTE: The cause is available only on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command. · For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces. · For a physical interface, specify its slot number. |
|
if-match acl |
Compares IPv6 packets with the IPv6 ACL. |
|
apply next-hop |
Specifies a next hop for permitted IPv6 packets. |
|
apply output-interface GigabitEthernet1/0/2 track 1 (down) |
Specifies an output interface for permitted packets. The interface status includes the following: · up—The interface is up. · down—The interface is down at network layer. · inactive—The interface is not in position. |
|
Matched: 0 (no statistics resource) |
Number of successful matches on the node. If the device does not have sufficient resources to count matches, this field displays no statistics resource in brackets. NOTE: The statistics collection failure cause is available only on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command. · For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces. · For a physical interface, specify its slot number. |
|
Total matched |
Total number of successful matches on all nodes. |
Related commands
reset ipv6 policy-based-route statistics
display ipv6 policy-based-route local
Use display ipv6 policy-based-route local to display IPv6 local PBR configuration and statistics.
Syntax
Centralized devices in standalone mode:
display ipv6 policy-based-route local
Distributed devices in standalone mode/centralized devices in IRF mode:
display ipv6 policy-based-route local [ slot slot-number ]
Distributed devices in IRF mode:
display ipv6 policy-based-route local [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays IPv6 local PBR configuration and statistics for the active MPU. (Distributed devices in standalone mode.)
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays IPv6 local PBR configuration and statistics for the master device. (Centralized devices in IRF mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays IPv6 local PBR configuration and statistics for the global active MPU. (Distributed devices in IRF mode.)
Examples
# Display IPv6 local PBR configuration and statistics.
<Sysname> display ipv6 policy-based-route local
Policy based routing information for local:
Policy name: aaa
node 0 deny:
Matched: 0
node 1 permit:
if-match acl 3999
Matched: 0
node 2 permit:
if-match acl 2000
apply next-hop 1::1
Matched: 0
node 5 permit:
if-match acl 3101
apply next-hop 2::2
Matched: 0
Total matched: 0
Table 174 Command output
|
Field |
Description |
|
Policy based routing information for local |
IPv6 local PBR configuration and statistics. |
|
node 0 deny/node 2 permit |
Match mode of the node, permit or deny. |
|
if-match acl |
Compares packets with the ACL. |
|
apply next-hop |
Specifies a next hop for permitted packets. |
|
Matched: 0 |
Number of successful matches on the node. |
|
Total matched |
Total number of successful matches on all nodes. |
Related commands
reset ipv6 policy-based-route statistics
display ipv6 policy-based-route setup
Use display ipv6 policy-based-route setup to display IPv6 PBR configuration.
Syntax
display ipv6 policy-based-route setup
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display IPv6 PBR configuration.
<Sysname> display ipv6 policy-based-route setup
Policy Name Interface Name
pr01 GigabitEthernet 1/0/1
Table 175 Command output
|
Field |
Description |
|
policy Name |
Policy name. |
|
Interface Name |
Interface where the policy is applied. |
Related commands
ipv6 policy-based-route (interface view)
if-match acl
Use if-match acl to set an ACL match criterion.
Use undo if-match acl to restore the default.
Syntax
if-match acl { ipv6-acl-number | name ipv6-acl-name }
undo if-match acl
Default
No ACL match criterion is set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999. The value range of a basic ACL is 2000 to 2999 and that of an advanced ACL is 3000 to 3999.
name ipv6-acl-name: Specifies an IPv6 basic or advanced ACL by its name, a case-insensitive string of 1 to 63 characters starting with letter a to z or A to Z. The ACL name cannot be all.
Examples
# Configure Node 10 of policy aa to permit the packets matching ACL 2000.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 10
[Sysname-pbr6-aa-10] if-match acl 2000
# Configure Node 10 of policy aa to permit the packets matching ACL aaa.
[Sysname] ipv6 policy-based-route aa permit node 10
[Sysname-pbr6-aa-10] if-match acl name aaa
if-match packet-length
Use if-match packet-length to set an IPv6 packet length match criterion.
Use undo if-match packet-length to delete the match criterion.
Syntax
if-match packet-length min-len max-len
undo if-match packet-length
Default
No packet length match criterion is set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
min-len: Specifies the minimum IPv6 packet length in the range of 1 to 65535 bytes.
max-len: Specifies the maximum IP packet length in the range of 1 to 65535 bytes. The maximum length must be no less than the minimum length.
Usage guidelines
The packet length range includes boundary values. For example, if you set the min-len and max-len arguments to 100 and 200, respectively, packets with lengths of 100 bytes and 200 bytes are also matched.
Examples
# Match packets with a length from 100 to 200 bytes.
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] if-match packet-length 100 200
ipv6 local policy-based-route
Use ipv6 local policy-based-route to configure IPv6 local PBR based on a specified policy.
Use undo ipv6 local policy-based-route to delete the configuration.
Syntax
ipv6 local policy-based-route policy-name
undo ipv6 local policy-based-route
Default
No policy is referenced for IPv6 local PBR.
Views
System view
Predefined user roles
network-admin
Parameters
policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. The specified IPv6 policy must already exist.
Usage guidelines
You can apply only one policy locally. Before you apply a new policy, you must first remove the current policy.
IPv6 local PBR is used to route locally generated packets except the packets destined for the sender. This feature might affect local services. Do not configure IPv6 local PBR unless doing so is required.
Examples
# Configure IPv6 local PBR based on policy aaa.
<Sysname> system-view
[Sysname] ipv6 local policy-based-route aaa
Related commands
display ipv6 policy-based-route setup
ipv6 policy-based-route (system view)
ipv6 policy-based-route (interface view)
Use ipv6 policy-based-route to configure IPv6 interface PBR by applying an IPv6 policy to an interface.
Use undo ipv6 policy-based-route to delete the configuration.
Syntax
ipv6 policy-based-route policy-name
undo ipv6 policy-based-route
Default
No IPv6 is applied to an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. The specified policy must already exist.
Usage guidelines
You can apply only one policy to an interface. Before you apply a new policy, remove the current policy from the interface.
Examples
# Apply policy aaa to GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ipv6 policy-based-route aaa
Related commands
display ipv6 policy-based-route setup
ipv6 policy-based-route (system view)
ipv6 policy-based-route (system view)
Use ipv6 policy-based-route to create an IPv6 policy node and enter its view, or enter the view of an existing IPv6 policy node.
Use undo ipv6 policy-based-route to delete an IPv6 policy or IPv6 policy node.
Syntax
ipv6 policy-based-route policy-name [ deny | permit ] node node-number
undo ipv6 policy-based-route policy-name [ deny | node node-number | permit ]
Default
No IPv6 policy nodes exist.
Views
System view
Predefined user roles
network-admin
Parameters
policy-name: Specifies a policy name, a case-sensitive string of 1 to 19 characters.
deny: Specifies the match mode for the policy node as deny.
permit: Specifies the match mode for the policy node as permit (default mode).
node node-number: Specifies the number of the IPv6 policy node. A smaller number has a higher priority. The value range for the node-number argument is 0 to 65535.
Usage guidelines
To delete an IPv6 policy that has already applied to an interface, you must delete the policy from the interface first.
If a policy node is specified, the undo ipv6 policy-based-route command deletes the specified policy node. If a match mode is specified, the command deletes all nodes configured with the match mode. If no node is specified, the command deletes the whole policy.
Examples
# Create permit-mode Node 10 for IPv6 policy aaa and enter its view.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aaa permit node 10
[Sysname-pbr6-aaa-10]
Related commands
display ipv6 policy-based-route
reset ipv6 policy-based-route statistics
Use reset ipv6 policy-based-route statistics to clear IPv6 PBR statistics.
Syntax
reset ipv6 policy-based-route statistics [ policy policy-name ]
Views
User view
Predefined user roles
network-admin
Parameters
policy policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. If you do not specify a policy, this command clears IPv6 PBR statistics for all policies.
Examples
# Clear all IPv6 PBR statistics.
<Sysname> reset ipv6 policy-based-route statistics
Related commands
display ipv6 policy-based-route interface
display ipv6 policy-based-route local
Routing policy commands
IPv6-related parameters are not supported on the following routers:
· MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-LMS/810-LUS.
· MSR3600-28-SI/3600-51-SI.
Common routing policy commands
apply as-path
Use apply as-path to set the AS_PATH attribute for BGP routes.
Use undo apply as-path to restore the default.
Syntax
apply as-path as-number&<1-32> [ replace ]
undo apply as-path
Default
No AS_PATH attribute is set.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
as-number&<1-32>: Specifies an AS by its number in the range of 1 to 4294967295. &<1-32> indicates that the argument before it can be entered up to 32 times.
replace: Replaces the original AS numbers. If you do not specify this keyword, the command adds the specified AS numbers before the original AS_PATH attribute.
Examples
# Configure node 10 in permit mode for routing policy policy1 to add AS number 200 before the original AS_PATH attribute of BGP routes matching AS path list 1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 1
[Sysname-route-policy-policy1-10] apply as-path 200
Related commands
display ip as-path
if-match as-path
ip as-path
apply comm-list delete
Use apply comm-list delete to delete the COMMUNITY attributes from BGP routes.
Use undo apply comm-list to restore the default.
Syntax
apply comm-list { comm-list-number | comm-list-name } delete
undo apply comm-list
Default
No COMMUNITY attributes are deleted from BGP routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
comm-list-number: Specifies a basic community list by its number in the range of 1 to 99 or an advanced community list by its number in the range of 100 to 199.
comm-list-name: Specifies a community list by its name, a case-sensitive string of 1 to 63 characters that cannot contain only numbers.
Examples
# Configure node 10 in permit mode for routing policy policy1 to delete the COMMUNITY attributes specified in community list 1 from BGP routes.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] apply comm-list 1 delete
Related commands
ip community-list
apply community
Use apply community to set a COMMUNITY attribute for BGP routes.
Use undo apply community to remove the specified COMMUNITY attribute for BGP routes.
Syntax
apply community { none | additive | { community-number&<1-32> | aa:nn&<1-32> | internet | no-advertise | no-export | no-export-subconfed } * [ additive ] }
undo apply community [ none | additive | { community-number&<1-32> | aa:nn&<1-32> | internet | no-advertise | no-export | no-export-subconfed } * [ additive ] ]
Default
No COMMUNITY attribute is set for BGP routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
none: Removes the COMMUNITY attributes of BGP routes.
community-number&<1-32>: Specifies a community sequence number in the range of 1 to 4294967295. &<1-32> indicates that the argument before it can be entered up to 32 times.
aa:nn&<1-32>: Specifies a community number. Both aa and nn are in the range of 0 to 65535. &<1-32> indicates that the argument before it can be entered up to 32 times.
internet: Sets the INTERNET community attribute for BGP routes. Routes with this attribute can be advertised to all BGP peers. By default, all routes have this attribute.
no-advertise: Sets the NO_ADVERTISE community attribute for BGP routes. Routes with this attribute cannot be advertised to any peers.
no-export: Sets the NO_EXPORT community attribute for BGP routes. Routes with this attribute cannot be advertised out of the AS or confederation, but can be advertised to other sub-ASs in the confederation.
no-export-subconfed: Sets the NO_EXPORT_SUBCONFED community attribute for BGP routes. Routes with this attribute cannot be advertised out of the local AS or to other sub-ASs in the confederation.
additive: Adds the specified COMMUNITY attribute to the original COMMUNITY attribute of BGP routes.
Examples
# Configure node 16 in permit mode for routing policy setcommunity to set the NO_EXPORT community attribute for BGP routes.
<Sysname> system-view
[Sysname] route-policy setcommunity permit node 16
[Sysname-route-policy-setcommunity-16] apply community no-export
Related commands
if-match community
ip community-list
apply cost
Use apply cost to set a cost for routes.
Use undo apply cost to restore the default.
Syntax
apply cost [ + | - ] cost-value
undo apply cost
Default
No cost is set for routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
+: Increases a cost value.
-: Decreases a cost value.
cost-value: Specifies a cost in the range of 0 to 4294967295.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set a cost of 120 for OSPF external routes.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match route-type external-type1or2
[Sysname-route-policy-policy1-10] apply cost 120
apply cost-type
Use apply cost-type to set a cost type for routes.
Use undo apply cost-type to restore the default.
Syntax
apply cost-type { external | internal | type-1 | type-2 }
undo apply cost-type
Default
No cost type is set for routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
external: Sets the cost type to IS-IS external route.
internal: Sets the cost type to IS-IS internal route, or sets the MED value for a matching BGP route to the IGP metric of the route's next hop.
type-1: Sets the cost type to OSPF Type-1 external route.
type-2: Sets the cost type to OSPF Type-2 external route.
Usage guidelines
For IS-IS, the apply cost-type internal command sets the cost type for a matching IS-IS route to IS-IS internal route.
For BGP, the apply cost-type internal command sets the MED for a matching BGP route learned from an IBGP peer to the IGP metric of the route's next hop. The MED is modified before BGP advertises the route to an EBGP peer.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set the cost type for routes that have a tag of 8 to IS-IS internal route.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match tag 8
[Sysname-route-policy-policy1-10] apply cost-type internal
apply extcommunity
Use apply extcommunity to apply the specified extended community attribute.
Use undo apply extcommunity to restore the default.
Syntax
apply extcommunity { rt route-target }&<1-32> [ additive ]
undo apply extcommunity
Default
No extended community attribute is set for BGP routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
{ rt route-target }&<1-32>: Sets the RT extended community attribute, a string of 3 to 21 characters. &<1-32> indicates that the argument before it can be entered up to 32 times.
An RT attribute has the following forms:
· 16-bit AS number:32-bit self-defined number. For example, 101:3. The AS number is in the range of 0 to 65535, and the self-defined number is in the range of 0 to 4294967295.
· 32-bit IP address:16-bit self-defined number. For example, 192.168.122.15:1. The self-defined number is in the range of 0 to 65535.
· 32-bit AS number:16-bit self-defined number. For example, 70000:3. The AS number is in the range of 65536 to 4294967295, and the self-defined number is in the range of 0 to 65535.
additive: Adds the specified attribute to the original extended community attribute.
Examples
# Configure node 10 in permit mode for routing policy policy1 to add the RT extended community attribute 100:2 to BGP routes matching AS path list 1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 1
[Sysname-route-policy-policy1-10] apply extcommunity rt 100:2 additive
apply ip-precedence
Use apply ip-precedence to set an IP precedence for matching routes.
Use undo apply ip-precedence to restore the default.
Syntax
apply ip-precedence { value | clear }
undo apply ip-precedence
Default
No IP precedence is set.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
value: Specifies an IP precedence in the range of 0 to 7.
clear: Clears the IP precedence of matching routes.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set an IP precedence of 3 for BGP routes matching extended community list 100.
<Sysname> system-view
[Sysname] ip extcommunity-list 100 permit rt 100:100
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match extcommunity 100
[Sysname-route-policy-policy1-10] apply ip-precedence 3
apply isis
Use apply isis to redistribute routes into the specified IS-IS level.
Use undo apply isis to restore the default.
Syntax
apply isis { level-1 | level-1-2 | level-2 }
undo apply isis
Default
No IS-IS level is set.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
level-1: Redistributes routes into IS-IS Level-1.
level-1-2: Redistributes routes into both IS-IS Level-1 and Level-2.
level-2: Redistributes routes into IS-IS Level-2.
Examples
# Configure node 10 in permit mode for routing policy policy1 to redistribute routes that have a tag of 8 to IS-IS level-2.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match tag 8
[Sysname-route-policy-policy1-10] apply isis level-2
apply local-preference
Use apply local-preference to set a local preference for BGP routes.
Use undo apply local-preference to restore the default.
Syntax
apply local-preference preference
undo apply local-preference
Default
No local preference is set for BGP routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
preference: Specifies a local preference in the range of 0 to 4294967295.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set a local preference of 130 for routes matching AS path list 1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 1
[Sysname-route-policy-policy1-10] apply local-preference 130
apply mpls-label
Use apply mpls-label to set MPLS labels for routes.
Use undo apply mpls-label to restore the default.
Syntax
apply mpls-label
undo apply mpls-label
Default
No MPLS label is set for routes.
Views
Routing policy node view
Predefined user roles
network-admin
Usage guidelines
If this command fails to assign an MPLS label to a route, the route will not be advertised.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set MPLS labels for routes.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] apply mpls-label
apply origin
Use apply origin to set an ORIGIN attribute for BGP routes.
Use undo apply origin to restore the default.
Syntax
apply origin { egp as-number | igp | incomplete }
undo apply origin
Default
No ORIGIN attribute is set for BGP routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
egp as-number: Sets the ORIGIN attribute to EGP. The as-number argument specifies an AS number in the range 1 to 4294967295 for EGP routes.
igp: Sets the ORIGIN attribute to IGP.
incomplete: Sets the ORIGIN attribute to UNKNOWN.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set the ORIGIN attribute to IGP for routes matching AS path list 1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 1
[Sysname-route-policy-policy1-10] apply origin igp
apply preference
Use apply preference to set a preference for a routing protocol.
Use undo apply preference to restore the default.
Syntax
apply preference preference
undo apply preference
Default
No preference is set for a routing protocol.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
preference: Specifies a preference in the range of 1 to 255.
Usage guidelines
If you have set preferences for routing protocols with the preference command, the apply preference command sets a new preference for the matching routing protocol. Unmatched routing protocols still use the preferences set by the preference command.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set the preference for OSPF external routes to 90.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match route-type external-type1or2
[Sysname-route-policy-policy1-10] apply preference 90
apply preferred-value
Use apply preferred-value to set a preferred value for BGP routes.
Use undo apply preferred-value to restore the default.
Syntax
apply preferred-value preferred-value
undo apply preferred-value
Default
No preferred value is set for BGP routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
preferred-value: Specifies a preferred value in the range of 0 to 65535.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set a preferred value of 66 for BGP routes matching AS path list 1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 1
[Sysname-route-policy-policy1-10] apply preferred-value 66
apply prefix-priority
Use apply prefix-priority to set a prefix priority for routes.
Use undo apply prefix-priority to restore the default.
Syntax
apply prefix-priority { critical | high | medium }
undo apply prefix-priority
Default
No prefix priority is set, which means the prefix priority is low.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
critical: Sets the critical prefix priority for routes.
high: Sets the high prefix priority for routes.
medium: Sets the medium prefix priority for routes.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set prefix priority critical for routes matching prefix list abc.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match ip address prefix-list abc
[Sysname-route-policy-policy1-10] apply prefix-priority critical
apply qos-local-id
Use apply qos-local-id to set a local QoS ID for matching routes.
Use undo apply qos-local-id to restore the default.
Syntax
apply qos-local-id { local-id-value | clear }
undo apply qos-local-id
Default
No local QoS ID is set.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
local-id-value: Specifies a local QoS ID in the range of 1 to 4095.
clear: Clears the local QoS ID of matching routes.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set a local QoS ID of 100 for BGP routes matching extended community list 100.
<Sysname> system-view
[Sysname] ip extcommunity-list 100 permit rt 100:100
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match extcommunity 100
[Sysname-route-policy-policy1-10] apply qos-local-id 100
apply tag
Use apply tag to set a tag for IGP routes.
Use undo apply tag to restore the default.
Syntax
apply tag tag-value
undo apply tag
Default
No routing tag is set for IGP routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
tag-value: Specifies the tag value in the range of 0 to 4294967295.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set a tag of 100.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] apply tag 100
apply traffic-index
Use apply traffic-index to set a traffic index for BGP routes.
Use undo apply traffic-index to restore the default.
Syntax
apply traffic-index { value | clear }
Default
No traffic index is set for BGP routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
value: Specifies the traffic index in the range of 1 to 64.
clear: Clear the traffic index of BGP routes.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set a traffic index of 6 for BGP routes matching extended community list 100.
[Sysname] ip extcommunity-list 100 permit rt 100:100
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match extcommunity 100
[Sysname-route-policy-policy1-10] apply traffic-index 6
continue
Use continue to specify the next node to be matched.
Use undo continue to restore the default.
Syntax
continue [ node-number ]
undo continue
Default
No next node is specified.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
node-number: Specifies the routing policy node number in the range of 0 to 65535.
Usage guidelines
The specified next node must have a larger number than the current node.
Example
# Specify the next node 20 for node 10 of routing policy policy1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] continue 20
display ip as-path
Use display ip as-path to display BGP AS path list information.
Syntax
display ip as-path [ as-path-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
as-path-number: Specifies an AS path list by its number in the range of 1 to 256. If you do not specify this argument, the command displays information about all BGP AS path lists.
Examples
# Display information about BGP AS path list 1.
<Sysname> display ip as-path 1
ListID Mode Expression
1 Permit 2
Table 176 Command output
|
Field |
Description |
|
ListID |
AS path list ID. |
|
Mode |
Match mode: · Permit. · Deny. |
|
Expression |
Regular expression used to match routes. |
display ip community-list
Use display ip community-list to display BGP community list information.
Syntax
display ip community-list [ basic-community-list-number | adv-community-list-number | name comm-list-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
basic-community-list-number: Specifies a basic community list by its number in the range of 1 to 99.
adv-community-list-number: Specifies an advanced community list by its number in the range of 100 to 199.
name comm-list-name: Specifies a community list by its name, a case-sensitive string of 1 to 63 characters that cannot contain only numbers.
Usage guidelines
If no community list is specified, this command displays information about all BGP community lists.
Examples
# Display information about all BGP community lists.
<Sysname> display ip community-list
Community List Basic aaa
Permit
Community List Advanced bbb
Permit 3333
Table 177 Command output
|
Field |
Description |
|
Community List Basic |
Basic community list. |
|
Community List Advanced |
Advanced community list. |
|
permit |
Match mode: · Permit. · Deny. |
display ip extcommunity-list
Use display ip extcommunity-list to display BGP extended community list information.
Syntax
display ip extcommunity-list [ ext-comm-list-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ext-comm-list-number: Specifies an extended community list by its number in the range of 1 to 65535. If you do not specify this argument, the command displays information about all BGP extended community lists.
Examples
# Display information about BGP extended community list 1.
<Sysname> display ip extcommunity-list 1
Extended Community List Number 1
Index: 1 Mode: Permit SoO: 100:1 RT: 300:400 SoO: 400:1
Index: 2 Mode: Permit SoO: 100:100 RT: 300:400 SoO: 400:500
Index: 3 Mode: Permit SoO: 200:200 RT: 200:300 SoO: 300:500
Index: 4 Mode: Permit RT: 100:100 SoO: 300:400 SoO: 400:500
Table 178 Command output
|
Field |
Description |
|
Extended Community List Number |
Extended community list. |
|
Index |
Index of the extended community list entry. |
|
Mode |
Match mode: · Permit. · Deny. |
|
Rt |
Route Target (RT) extended community attribute. |
|
Soo |
Site of Origin (SoO) extended community attribute. |
display mac-list
Use display mac-list to display MAC list statistics.
Syntax
display mac-list [ name mac-list-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name mac-list-name: Specifies a MAC list by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the command displays statistics for all MAC lists.
Examples
# Display the statistics for MAC list abc.
<Sysname> display mac-list name abc
MAC address list: abc
Permitted 0
Denied 0
Index: 1 Permit: 001b-2188-946c/48
Table 179 Command output
|
Field |
Description |
|
MAC address list |
Name of the MAC list. |
|
Permitted |
Number of packets matching the criterion. |
|
Denied 0 |
Number of packets not matching the criterion. |
|
Index |
Index of an item. |
|
Permit |
Match mode: · Permit. · Deny. |
display route-policy
Use display route-policy to display routing policy information.
Syntax
display route-policy [ name route-policy-name ]
Views
Predefined user roles
network-admin
network-operator
Parameters
name route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the command displays information about all routing policies.
Examples
# Display information about routing policy 1.
<Sysname> display route-policy name policy1
Route-policy: policy1
Permit : 1
if-match cost 10
continue: next node 11
apply comm-list a delete
Table 180 Command output
|
Field |
Description |
|
Route-policy |
Routing policy name. |
|
permit |
Match mode: · Permit. · Deny. |
|
if-match |
Match criterion. |
|
continue |
Specify the next node to be matched. |
|
apply |
Action. |
if-match as-path
Use if-match as-path to match BGP routes whose AS_PATH attribute matches a specified AS path list.
Use undo if-match as-path to remove the specified AS path list.
Syntax
if-match as-path as-path-number&<1-32>
undo if-match as-path [ as-path-number&<1-32> ]
Default
No AS path list match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
as-path-number&<1-32>: Specifies an AS path list by its number in the range of 1 to 256. &<1-32> indicates that the argument before it can be entered up to 32 times.
Examples
# Configure AS path list 2 to permit BGP routes containing AS number 200 or 300 to pass. Configure node 10 in permit mode for routing policy test to match AS path list 2.
<Sysname> system-view
[Sysname] ip as-path 2 permit _*200.*300
[Sysname] route-policy test permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 2
Related commands
apply as-path
ip as-path
if-match community
Use if-match community to match BGP routes whose COMMUNITY attribute matches a specified community list.
Use undo if-match community to remove the specified community list.
Syntax
if-match community { { basic-community-list-number | name comm-list-name } [ whole-match ] | adv-community-list-number }&<1-32>
undo if-match community [ { basic-community-list-number | name comm-list-name } [ whole-match ] | adv-community-list-number ]&<1-32>
Default
No community list match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
basic-community-list-number: Specifies a basic community list by its number in the range of 1 to 99.
adv-community-list-number: Specifies an advanced community list by its number in the range of 100 to 199.
comm-list-name: Specifies a community list by its name, a case-sensitive string of 1 to 63 characters that cannot contain only numbers.
whole-match: Exactly matches the specified community list.
&<1-32>: Indicates that the argument before it can be entered up to 32 times.
Examples
# Configure community list 1 to permit BGP routes with community number 100 or 200. Then configure node 10 in permit mode for routing policy test to use community list 1 to match BGP routes.
[Sysname] ip community-list 1 permit 100 200
[Sysname] route-policy test permit node 10
[Sysname-route-policy-test-10] if-match community 1
Related commands
apply community
ip community-list
if-match cost
Use if-match cost to match routes having the specified cost.
Use undo if-match cost to restore the default.
Syntax
if-match cost cost-value
undo if-match cost
Default
No cost match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
cost-value: Specifies a cost in the range of 0 to 4294967295.
Examples
# Configure node 10 in permit mode for routing policy policy1 to permit routes with a cost of 8.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match cost 8
if-match extcommunity
Use if-match extcommunity to match BGP routes whose extended community attribute matches a specified extended community list.
Use undo if-match extcommunity to remove the specified extended community list.
Syntax
if-match extcommunity ext-comm-list-number&<1-32>
undo if-match extcommunity [ ext-comm-list-number&<1-32> ]
Default
No extended community list match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
ext-comm-list-number&<1-32>: Specifies an extended community list by its number in the range of 1 to 199. &<1-32> indicates that the argument before it can be entered up to 32 times.
Examples
# Configure node 10 in permit mode for routing policy policy1 to match BGP routes whose extended community attribute matches extended community lists 100 and 150.
<Sysname> system-view
[Sysname] ip extcommunity-list 100 permit rt 100:100
[Sysname] ip extcommunity-list 150 permit rt 150:150
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match extcommunity 100 150
Related commands
apply extcommunity
ip extcommunity-list
if-match interface
Use if-match interface to match routes having the specified output interface.
Use undo if-match interface to remove the specified output interface.
Syntax
if-match interface { interface-type interface-number }&<1-16>
undo if-match interface [ interface-type interface-number ]&<1-16>
Default
No output interface match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
&<1-16>: Indicates that the argument before it can be entered up to 16 times.
Usage guidelines
BGP does not support criteria for matching the output interface of routes.
Examples
# Configure node 10 in permit mode for routing policy policy1 to permit routes with the output interface GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match interface gigabitethernet 1/0/1
if-match local-preference
Use if-match local-preference to match BGP routes having the specified local preference.
Use undo if-match local-preference to restore the default.
Syntax
if-match local-preference preference
undo if-match local-preference
Default
No local preference match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
preference: Specifies a local preference in the range of 0 to 4294967295.
Examples
# Create node 10 in permit mode for routing policy policy1 to match BGP routes having a local preference of 2.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match local-preference 2
if-match mac-list
Use if-match mac-list to match MAC addresses that are contained in EVI IS-IS packets.
Use undo if-match mac-list to remove the specified MAC list.
Syntax
if-match mac-list mac-list-name
undo if-match mac-list mac-list-name
Default
No MAC list match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
mac-list-name: Specifies a MAC list by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
A MAC list can contain multiple items that specify MAC address ranges. Each MAC address entry in an EVI IS-IS packet is compared with these items in ascending order of their index numbers. A MAC address entry matches the MAC list if it matches one item in the list.
Examples
# Configure a routing policy to match the MAC addresses in EVI IS-IS packets with the MAC list p1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match mac-list p1
Related commands
mac-list
if-match mpls-label
Use if-match mpls-label to set the MPLS label match criterion.
Use undo if-match mpls-label to restore the default.
Syntax
if-match mpls-label
undo if-match mpls-label
Default
No MPLS label match criterion is set.
Views
Routing policy node view
Predefined user roles
network-admin
Examples
# Configure node 10 in permit mode for routing policy policy1 to match routes having MPLS labels.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match mpls-label
if-match route-type
Use if-match route-type to set a route-type match criterion.
Use undo if-match route-type to remove the specified route-type match criterion.
Syntax
if-match route-type { bgp-evpn-imet | bgp-evpn-ip-prefix | bgp-evpn-mac-ip | eigrp-external | eigrp-internal | external-type1 | external-type1or2 | external-type2 | internal | is-is-level-1 | is-is-level-2 | nssa-external-type1 | nssa-external-type1or2 | nssa-external-type2 } *
undo if-match route-type [ bgp-evpn-imet | bgp-evpn-ip-prefix | bgp-evpn-mac-ip | eigrp-external | eigrp-internal | external-type1 | external-type1or2 | external-type2 | internal | is-is-level-1 | is-is-level-2 | nssa-external-type1 | nssa-external-type1or2 | nssa-external-type2 ] *
Default
No route-type match criterion is set.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
bgp-evpn-imet: Matches BGP EVPN IMET routes.
bgp-evpn-ip-prefix: Matches BGP EVPN IP prefix advertisement routes.
bgp-evpn-mac-ip: Matches BGP EVPN MAC/IP advertisement routes.
eigrp-external: Matches EIGRP external routes.
eigrp-internal: Matches EIGRP internal routes.
external-type1: Matches OSPF Type 1 external routes.
external-type1or2: Matches OSPF Type 1 and Type 2 external routes.
external-type2: Matches OSPF Type 2 external routes.
internal: Matches OSPF internal routes (including OSPF intra-area and inter-area routes).
is-is-level-1: Matches IS-IS Level-1 routes.
is-is-level-2: Matches IS-IS Level-2 routes.
nssa-external-type1: Matches OSPF NSSA Type 1 external routes.
nssa-external-type1or2: Matches OSPF NSSA Type 1 and 2 external routes.
nssa-external-type2: Matches OSPF NSSA Type 2 external routes.
Examples
# Configure node 10 in permit mode for routing policy policy1 to match OSPF internal routes.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match route-type internal
if-match tag
Use if-match tag to match IGP routes having the specified tag.
Use undo if-match tag to restore the default.
Syntax
if-match tag tag-value
undo if-match tag
Default
No tag match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
tag-value: Specifies a tag in the range of 0 to 4294967295.
Examples
# Configure node 10 in permit mode for routing policy policy1 to match IGP routes having a tag of 8.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match tag 8
if-match vlan
Use if-match vlan to match VLANs in EVI IS-IS packets.
Use undo if-match vlan to remove the specified VLANs.
Syntax
if-match vlan vlan-list
undo if-match vlan vlan-list
Default
No VLAN match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
vlan-list: Specifies a space-separated list of up to 16 VLAN items. Each VLAN item specifies a VLAN ID or a range of VLAN IDs in the form of start-vlan-id to end-vlan-id, where the end VLAN ID must be greater than the start VLAN ID. Valid VLAN IDs are from 1 to 4094.
Examples
# Configure a routing policy to match VLAN 10 and VLANs in the range of 100 to 200.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match vlan 10 100 to 200
ip as-path
Use ip as-path to configure an AS path list.
Use undo ip as-path to remove an AS path list.
Syntax
ip as-path as-path-number { deny | permit } regular-expression
undo ip as-path as-path-number [ regular-expression | deny | permit ]
Default
No AS path lists exist.
Views
System view
Predefined user roles
network-admin
Parameters
as-path-number: Specifies a number for the AS path list, in the range of 1 to 256.
deny: Specifies the match mode for the AS path list as deny.
permit: Specifies the match mode for the AS path list as permit.
regular-expression: Specifies an AS path regular expression, a string of 1 to 63 characters.
Usage guidelines
BGP routing updates contain an AS_PATH attribute field that identifies the ASs through which the routes have passed. An AS path regular expression, for example, ^200.*100$, matches the AS_PATH attribute that starts with AS 200 and ends with AS 100. For more information about regular expressions, see Fundamentals Configuration Guide.
Examples
# Configure AS path list 1 to permit routes whose AS_PATH attribute starts with 10.
<Sysname> system-view
[Sysname] ip as-path 1 permit ^10
Related commands
apply as-path
display ip as-path
if-match as-path
ip community-list
Use ip community-list to configure a community list.
Use undo ip community-list to remove a community list.
Syntax
ip community-list { basic-comm-list-num | basic basic-comm-list-name } { deny | permit } [ community-number&<1-32> | aa:nn&<1-32> ] [ internet | no-advertise | no-export | no-export-subconfed ] *
undo ip community-list { basic-comm-list-num | basic basic-comm-list-name } [ deny | permit ] [ community-number&<1-32> | aa:nn&<1-32> ] [ internet | no-advertise | no-export | no-export-subconfed ] *
ip community-list { adv-comm-list-num | advanced adv-comm-list-name } { deny | permit } regular-expression
undo ip community-list { adv-comm-list-num | advanced adv-comm-list-name } [ deny | permit ] [ regular-expression ]
Default
No community lists exist.
Views
System view
Predefined user roles
network-admin
Parameters
basic-comm-list-num: Specifies a number for the basic community list, in the range of 1 to 99.
basic: Specifies a name for the basic community list.
advanced: Specifies a name for the advanced community list.
basic-comm-list-name: Specifies the basic community list name, a case-sensitive string of 1 to 63 characters that cannot contain only letters.
adv-comm-list-name: Specifies the advanced community list name, a case-sensitive string of 1 to 63 characters that cannot contain only letters.
adv-comm-list-num: Specifies the advanced community list number in the range of 100 to 199.
regular-expression: Specifies a regular expression for the advanced community list, a string of 1 to 63 characters. For more information about regular expressions, see Fundamentals Configuration Guide.
deny: Specifies the match mode for the community list as deny.
permit: Specifies the match mode for the community list as permit.
community-number&<1-32>: Specifies a community sequence number in the range of 1 to 4294967295. &<1-32> indicates that the argument before it can be entered up to 32 times.
aa:nn&<1-32>: Specifies a community number. Both aa and nn are in the range of 0 to 65535. &<1-32> indicates that the argument before it can be entered up to 32 times.
internet: Specifies the INTERNET community attribute. Routes with this attribute can be advertised to all BGP peers. By default, all routes have this attribute.
no-advertise: Specifies the NO_ADVERTISE community attribute. Routes with this attribute cannot be advertised to other BGP peers.
no-export: Specifies the NO_EXPORT community attribute. Routes with this attribute cannot be advertised out of the local AS or the local confederation but can be advertised to other ASs in the confederation.
no-export-subconfed: Specifies the NO_EXPORT_SUBCONFED community attribute. Routes with this attribute cannot be advertised out of the local AS, or to other sub-ASs in the local confederation.
Examples
# Configure basic community list 1 to permit routes with the INTERNET community attribute.
<Sysname> system-view
[Sysname] ip community-list 1 permit internet
# Configure advanced community list 100 to permit routes with the COMMUNITY attribute starting with 10.
<Sysname> system-view
[Sysname] ip community-list 100 permit ^10
Related commands
apply comm-list delete
apply community
display ip community-list
if-match community
ip extcommunity-list
Use ip extcommunity-list to configure an extended community list.
Use undo ip extcommunity-list to remove an extended community list or list entry.
Syntax
ip extcommunity-list ext-comm-list-number [ index index-number ] { deny | permit } { rt route-target | soo site-of-origin }&<1-32>
undo ip extcommunity-list ext-comm-list-number [ index index-number | { deny | permit } [ rt route-target | soo site-of-origin ]&<1-32> ]
Default
No extended community lists exist.
Views
System view
Predefined user roles
network-admin
Parameters
ext-comm-list-number: Specifies a number for the extended community list, in the range of 1 to 65535.
index index-number: Specifies an index for the extended community list entry, in the range of 1 to 4294967295. An extended community list entry with a smaller index number is matched first. If you do not specify this option, the index number starts from 1 and increments by 1 for each of the consecutive extended community list entries.
deny: Specifies the match mode for the extended community list as deny.
permit: Specifies the match mode for the extended community list as permit.
rt route-target: Specifies a space-separated list of up to 32 RT extended community attribute items. Each item is a string of 3 to 21 characters.
soo site-of-origin: Specifies a space-separated list of up to 32 SoO extended community attribute items. Each item is a string of 3 to 21 characters.
An RT or SoO attribute has the following forms:
· 16-bit AS number:32-bit self-defined number. For example, 101:3. The AS number is in the range of 0 to 65535, and the self-defined number is in the range of 0 to 4294967295.
· 32-bit IP address:16-bit self-defined number. For example, 192.168.122.15:1. The self-defined number is in the range of 0 to 65535.
· 32-bit AS number:16-bit self-defined number. For example, 70000:3. The AS number is in the range of 65536 to 4294967295, and the self-defined number is in the range of 0 to 65535.
Usage guidelines
If you execute this command multiple times for an extended community list entry, the most recent configuration takes effect.
Examples
# Configure extended community list 1 and create extended community list entry 10 to permit routes with RT 200:200 to pass.
<Sysname> system-view
[Sysname] ip extcommunity-list 1 index 10 permit rt 200:200
# Configure extended community list 1 and create extended community list entry 30 to permit routes with SoO 100:100 to pass.
<Sysname> system-view
[Sysname] ip extcommunity-list 2 index 30 permit soo 100:100
apply extcommunity
display ip extcommunity-list
if-match extcommunity
mac-list
Use mac-list to configure a MAC list for filtering MAC entries advertised by EVI IS-IS.
Use undo mac-list to delete a MAC list or an item in the list.
Syntax
mac-list mac-list-name [ index index-number ] { deny | permit } mac-address [ mask-length ]
undo mac-list mac-list-name [ index index-number ]
Default
No MAC lists exist.
Views
System view
Predefined user roles
network-admin
Parameters
mac-list-name: Specifies a MAC list by its name, a case-sensitive string of 1 to 63 characters. The MAC list name must be unique.
index-number: Specifies a MAC list item by its index number in the range of 1 to 65535. An item with a smaller number is matched first.
deny: Specifies the match mode for the MAC list as deny. EVI IS-IS does not advertise MAC entries that match a deny-mode item.
permit: Specifies the match mode for the MAC list as permit. EVI IS-IS can advertise MAC entries that match a permit-mode item.
mac-address mask-length: Specifies a MAC address prefix and mask length. The value range for the mask-length argument is 0 to 48.
Examples
# Configure a MAC list to permit MAC address entries in the range of 001b-2188-0000 to 001b-2188-ffff.
<Sysname> system-view
[Sysname] mac-list abc permit 001b-2188-946c 32
Related commands
if-match mac-list
reset mac-list
Use reset mac-list to clear MAC list statistics.
Syntax
reset mac-list [ mac-list-name ]
Views
User view
Predefined user roles
network-admin
Parameters
mac-list-name: Specifies a MAC list by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this argument, the command clears statistics for all MAC lists.
Examples
# Clear the statistics for MAC list abc.
<Sysname> reset mac-list abc
route-policy
Use route-policy to create a routing policy and a node and enter routing policy node view, or enter the view of an existing routing policy node.
Use undo route-policy to remove a routing policy or a node of it.
Syntax
route-policy route-policy-name { deny | permit } node node-number
undo route-policy route-policy-name [ deny | permit ] [ node node-number ]
Default
No routing policies exist.
Views
System view
Predefined user roles
network-admin
Parameters
route-policy-name: Specifies a name for the routing policy, a case-sensitive string of 1 to 63 characters.
deny: Specifies the deny match mode for the routing policy node. If a route matches all the if-match clauses of the node, it is denied without being compared with the next node. If not, the route is compared with the next node.
permit: Specifies the permit match mode for the routing policy node. If a route matches all the if-match clauses of the node, it is handled by the apply clauses of the node. If not, the route is compared with the next node.
node node-number: Specifies a number for the node, in the range of 0 to 65535. A node with a smaller number is matched first.
Usage guidelines
Use a routing policy to filter routing information. A routing policy can contain several nodes and each node contains a set of if-match and apply clauses. The if-match clauses define the match criteria of the node and the apply clauses define the actions to be taken on packets matching the criteria. The relation between the if-match clauses of a node is logical AND. All the if-match clauses must be met. The relation between nodes is logical OR. A packet passing a node passes the routing policy.
Examples
# Create node 10 in permit mode for routing policy policy1 and enter routing policy node view.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10]
Related commands
display route-policy
IPv4 routing policy commands
apply fast-reroute
Use apply fast-reroute to set a backup link for fast route (FRR).
Use undo apply fast-reroute to restore the default.
Syntax
apply fast-reroute { backup-interface interface-type interface-number [ backup-nexthop ip-address ] | backup-nexthop ip-address }
undo apply fast-reroute
Default
No backup link for FRR is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
backup-interface interface-type interface-number: Specifies a backup output interface. If the specified interface is a non-P2P interface, you must also specify a backup next hop. Non-P2P interfaces include NBMA and broadcast interfaces.
backup-nexthop ip-address: Specifies a backup next hop.
Usage guidelines
This command sets a backup link in the routing policy for FRR.
Using the routing policy, a routing protocol can designate a backup link for specific routes to implement FRR. When the primary link fails, FRR immediately directs packets to the backup link to minimize interruption time.
Examples
# Configure node 10 of routing policy policy1 to set the backup output interface GigabitEthernet 1/0/1 and backup next hop 193.1.1.8 for the route destined for 100.1.1.0/24.
<Sysname> system-view
[Sysname] ip prefix-list abc index 10 permit 100.1.1.0 24
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match ip address prefix-list abc
[Sysname-route-policy-policy1-10] apply fast-reroute backup-interface gigabitethernet 1/0/1 backup-nexthop 193.1.1.8
apply ip-address next-hop
Use apply ip-address next-hop to set a next hop for IPv4 routes.
Use undo apply ip-address next-hop to restore the default.
Syntax
apply ip-address next-hop ip-address [ public | vpn-instance vpn-instance-name ]
undo apply ip-address next-hop
Default
No next hop is set for IPv4 routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the next hop IP address.
public: Specifies the public network.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
This command cannot set a next hop for redistributed routes.
If you do not provide the public keyword or vpn-instance vpn-instance-name option for this command, the next hop belongs to the public network.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set next hop 193.1.1.8 for routes matching AS path list 1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 1
[Sysname-route-policy-policy1-10] apply ip-address next-hop 193.1.1.8
display ip prefix-list
Use display ip prefix-list to display IPv4 prefix list statistics.
Syntax
display ip prefix-list [ name prefix-list-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the command displays statistics for all IPv4 prefix lists.
Examples
# Display the statistics for IPv4 prefix list abc.
<Sysname> display ip prefix-list name abc
Prefix-list: abc
Permitted 0
Denied 0
index: 10 Deny 6.6.6.0/24 ge 26 le 28
Table 181 Command output
|
Field |
Description |
|
Prefix-list |
Name of the IPv4 prefix list. |
|
Permitted |
Number of routes matching the criterion. |
|
Denied |
Number of routes not matching the criterion. |
|
index |
Index of an item. |
|
deny |
Match mode of the item: · Permit. · Deny. |
|
6.6.6.0/24 |
IP address and mask. |
|
ge |
Greater-equal, the lower mask length. |
|
le |
Less-equal, the upper mask length. |
Related commands
ip prefix-list
reset ip prefix-list
if-match ip
Use if-match ip to match IPv4 routes whose destination, next hop, or source address matches an ACL or IPv4 prefix list.
Use undo if-match ip to remove the specified ACL or IPv4 prefix list.
Syntax
if-match ip { address | next-hop | route-source } { acl { ipv4-acl-number | name ipv4-acl-name } | prefix-list prefix-list-name }
undo if-match ip { address | next-hop | route-source } [ acl | prefix-list ]
Default
No ACL or IPv4 prefix list match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
address: Matches the destination address of IPv4 routes.
next-hop: Matches the next hop of IPv4 routes.
route-source: Matches the source address of BGP routes. This keyword corresponds to the Neighbor field in the output from the display ip routing-table verbose command.
acl ipv4-acl-number: Specifies an ACL by its number. The value range is 2000 to 3999 for the address keyword, and 2000 to 2999 for the next-hop and route-source keywords.
acl name ipv4-acl-name: Specifies an ACL by its name, a case-insensitive string of 1 to 63 characters. The ACL name must start with a letter and cannot be all.
prefix-list prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
Follow these restrictions and guidelines to use an IPv4 advanced ACL rule to configure an ACL match criterion:
· To match the destination address of IPv4 routes, execute the rule [ rule-id ] { deny | permit } ip source source-address source-wildcard command to create the rule.
· To match the destination address mask of IPv4 routes, execute the rule [ rule-id ] { deny | permit } ip destination dest-address dest-wildcard command to create the rule. Make sure the wildcard mask specified by the dest-wildcard argument is consecutive. If the wildcard mask is nonconsecutive, the rule is not applicable to the if-match ip command.
Examples
# Configure node 10 of routing policy policy1 to match IPv4 routes whose next hop matches IP prefix list p1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match ip next-hop prefix-list p1
ip prefix-list
Use ip prefix-list to configure an IPv4 prefix list or an item for the list.
Use undo ip prefix-list to remove an IPv4 prefix list or an item of it.
Syntax
ip prefix-list prefix-list-name [ index index-number ] { deny | permit } ip-address mask-length [ greater-equal min-mask-length ] [ less-equal max-mask-length ]
undo ip prefix-list prefix-list-name [ index index-number ]
Default
No IPv4 prefix lists exist.
Views
System view
Predefined user roles
network-admin
Parameters
prefix-list-name: Specifies a name for the IPv4 prefix list, a case-sensitive string of 1 to 63 characters.
index-number: Specifies an index number for an IPv4 prefix list item, in the range of 1 to 65535. An item with a smaller number is matched first.
deny: Specifies the deny mode. If a route matches the item, the route is denied without being compared with the next item. If not, the route is compared with the next item.
permit: Specifies the permit mode. If a route matches the item, it passes the IPv4 prefix list. If not, the route is compared with the next item.
ip-address mask-length: Specifies an IPv4 prefix and mask length. The value range for the mask-length argument is 0 to 32.
greater-equal min-mask-length, less-equal max-mask-length: Specifies a prefix length range. The greater-equal keyword means "greater than or equal to" and the less-equal keyword means "less than or equal to." The prefix length range relation is mask-length <= min-mask-length <= max-mask-length <= 32.
· If only the min-mask-length argument is specified, the prefix length range is [ min-mask-length, 32 ].
· If only the max-mask-length argument is specified, the prefix length range is [ mask-length, max-mask-length ].
· If both the min-mask-length and max-mask-length arguments are specified, the prefix length range is [ min-mask-length, max-mask-length ].
Usage guidelines
An IPv4 prefix list is used to filter IPv4 addresses. It can contain multiple items, each of which specifies a range of IPv4 prefixes. The relation between the items is logical OR. If an item is passed, the IPv4 prefix list is passed. If no item is passed, the IP prefix list cannot be passed.
If both the ip-address and mask-length arguments are specified as 0.0.0.0 0, only the default route will be matched.
To match all routes, use 0.0.0.0 0 less-equal 32.
Examples
# Configure IP prefix list p1 to permit routes destined for network 10.0.0.0/8 and with mask length 17 or 18.
<Sysname> system-view
[Sysname] ip prefix-list p1 permit 10.0.0.0 8 greater-equal 17 less-equal 18
Related commands
display ip prefix-list
reset ip prefix-list
reset ip prefix-list
Use reset ip prefix-list to clear IPv4 prefix list statistics.
Syntax
reset ip prefix-list [ prefix-list-name ]
Views
User view
Predefined user roles
network-admin
Parameters
prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this argument, the command clears statistics for all IPv4 prefix lists.
Examples
# Clear the statistics for IPv4 prefix list abc.
<Sysname> reset ip prefix-list abc
Related commands
display ip prefix-list
ip prefix-list
IPv6 routing policy commands
apply ipv6 fast-reroute
Use apply ipv6 fast-reroute to set a backup link for fast route (FRR).
Use undo apply ipv6 fast-reroute to restore the default.
Syntax
apply ipv6 fast-reroute { backup-interface interface-type interface-number [ backup-nexthop ipv6-address ] | backup-nexthop ipv6-address }
undo apply ipv6 fast-reroute
Default
No backup link for FRR is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
backup-interface interface-type interface-number: Specifies a backup output interface by its type and number. If the specified interface is a non-P2P interface, you must also specify a backup next hop. Non-P2P interfaces include NBMA and broadcast interfaces.
backup-nexthop ipv6-address: Specifies an IPv6 backup next hop.
Usage guidelines
This command sets a backup link in the routing policy for FRR.
Using the routing policy, a routing protocol can designate a backup link for specific routes to implement FRR. When the primary link fails, FRR immediately directs packets to the backup link to minimize interruption time.
Examples
# Configure node 10 of routing policy policy1 to set the backup next hop 1::1/64 for the route destined for 100::1/64.
<Sysname> system-view
[Sysname] ipv6 prefix-list abc index 10 permit 100::1 64
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match ipv6 address prefix-list abc
[Sysname-route-policy-policy1-10] apply ipv6 fast-reroute backup-nexthop 1::1
apply ipv6 next-hop
Use apply ipv6 next-hop to set a next hop for IPv6 routes.
Use undo apply ipv6 next-hop to restore the default.
Syntax
apply ipv6 next-hop ipv6-address
undo apply ipv6 next-hop
Default
No next hop is set for IPv6 routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
ipv6-address: Specifies the next hop IPv6 address.
Usage guidelines
This command cannot set a next hop for redistributed routes.
Examples
# Configure node 10 for routing policy policy1 to set next hop 3ffe:506::1 for IPv6 routes matching AS path list 1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 1
[Sysname-route-policy-policy1-10] apply ipv6 next-hop 3ffe:506::1
display ipv6 prefix-list
Use display ipv6 prefix-list to display IPv6 prefix list statistics.
Syntax
display ipv6 prefix-list [ name prefix-list-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the command displays statistics for all IPv6 prefix lists.
Examples
# Display the statistics for all IPv6 prefix lists.
<Sysname> display ipv6 prefix-list
Prefix-list6: 666
Permitted 0
Denied 0
index: 10 Permit 6::/64 ge 66 le 88
Table 182 Command output
|
Field |
Description |
|
Prefix-list6 |
Name of the IPv6 prefix list. |
|
Permitted |
Number of routes matching the criterion. |
|
Denied |
Number of routes not matching the criterion. |
|
index |
Index number of an item. |
|
permit |
Match mode of the item: · Permit. · Deny. |
|
6::/64 |
IPv6 address and prefix length for matching. |
|
ge |
Greater-equal, the lower prefix length. |
|
le |
Less-equal, the upper prefix length. |
Related commands
ipv6 prefix-list
reset ipv6 prefix-list
if-match ipv6
Use if-match ipv6 to match IPv6 routes whose destination, next hop, or source address matches an ACL or IPv6 prefix list.
Use undo if-match ipv6 to remove the specified ACL or IPv6 prefix list.
Syntax
if-match ipv6 { address | next-hop | route-source } { acl ipv6-acl-number | name ipv6-acl-name } | prefix-list prefix-list-name
undo if-match ipv6 { address | next-hop | route-source } [ acl | prefix-list ]
Default
No ACL or IPv6 prefix list match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
address: Matches the destination address of IPv6 routes.
next-hop: Matches the next hop of IPv6 routes.
route-source: Matches the source address of IPv6 routes.
acl ipv6-acl-number: Specifies an IPv6 ACL by its number. The value range is 2000 to 3999 for the address keyword, and 2000 to 2999 for the next-hop and route-source keywords.
acl name ipv6-acl-name: Specifies an IPv6 ACL by its name, a case-insensitive string of 1 to 63 characters. The ACL name must start with a letter and cannot be all.
prefix-list prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
Follow these restrictions and guidelines to use an IPv6 advanced ACL rule to configure an ACL match criterion:
· To match the destination address of IPv6 routes, execute the rule [ rule-id ] { deny | permit } ip source source-address source-wildcard command to create the rule.
· To match the destination address prefix of IPv6 routes, execute the rule [ rule-id ] { deny | permit } ip destination dest-address dest-wildcard command to create the rule. Make sure the address prefix specified by the dest-wildcard argument is consecutive. If the address prefix is nonconsecutive, the rule is not applicable to the if-match ipv6 command.
Examples
# Configure node 10 of routing policy policy1 to permit routes whose next hop matches IPv6 prefix list p1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match ipv6 next-hop prefix-list p1
ipv6 prefix-list
Use ipv6 prefix-list to configure an IPv6 prefix list or an item for it.
Use undo ipv6 prefix-list to remove an IPv6 prefix list or an item.
Syntax
ipv6 prefix-list prefix-list-name [ index index-number ] { deny | permit } ipv6-address { prefix-length | inverse inverse-prefix-length [ greater-equal min-prefix-length ] [ less-equal max-prefix-length ] }
undo ipv6 prefix-list prefix-list-name [ index index-number ]
Default
No IPv6 prefix lists exist.
Views
System view
Predefined user roles
network-admin
Parameters
prefix-list-name: Specifies a name for the IPv6 prefix list, a case-sensitive string of 1 to 63 characters.
index-number: Specifies an index number for an IPv6 prefix list item, in the range of 1 to 65535. An item with a smaller number is matched first.
deny: Specifies the deny mode. If a route matches the item, the route is denied without being compared with the next item. If not, the route is compared with the next item.
permit: Specifies the permit mode. If a route matches the item, it passes the IPv6 prefix list. If not, the route is compared with the next item.
ipv6-address: Specifies an IPv6 address.
prefix-length: Specifies the IPv6 prefix length. The value range for the prefix-length argument is 0 to 128.
inverse inverse-prefix-length: Matches IPv6 addresses from the least significant bit to the specified length. The value range for the inverse-prefix-length argument is 1 to 128.
greater-equal min-mask-length, less-equal max-mask-length: Specifies a prefix length range. The greater-equal keyword means "greater than or equal to" and the less-equal keyword means "less than or equal to."
The prefix length range relation is mask-length <= min-mask-length <= max-mask-length <= 128.
· If only the min-prefix-length argument is specified, the prefix length range is [ min-prefix-length, 128 ].
· If only the max-prefix-length argument is specified, the prefix length range is [ prefix-length, max-prefix-length ].
· If both the min-prefix-length and max-prefix-length arguments are specified, the prefix length range is [ min-prefix-length, max-prefix-length ].
Usage guidelines
An IPv6 prefix list can have multiple items, and each of them specifies a range of IPv6 prefixes. The relation between the items is logical OR. If a route passes an item, it passes the IPv6 prefix list.
If the ipv6-address prefix-length argument is specified as :: 0, only the default route matches.
To match all routes, configure :: 0 less-equal 128.
Examples
# Permit IPv6 addresses with a mask length between 32 bits and 64 bits.
<Sysname> system-view
[Sysname] ipv6 prefix-list abc permit :: 0 greater-equal 32 less-equal 64
# Deny IPv6 addresses with a prefix 3FFE:D00::/32 and a prefix length greater than or equal to 32 bits.
<Sysname> system-view
[Sysname] ipv6 prefix-list abc deny 3FFE:D00:: 32 less-equal 128
Related commands
display ipv6 prefix-list
reset ipv6 prefix-list
reset ipv6 prefix-list
Use reset ipv6 prefix-list to clear IPv6 prefix list statistics.
Syntax
reset ipv6 prefix-list [ prefix-list-name ]
Views
User view
Predefined user roles
network-admin
Parameters
prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this argument, the command clears statistics for all IPv6 prefix lists.
Examples
# Clear the statistics for IPv6 prefix list abc.
<Sysname> reset ipv6 prefix-list abc
Related commands
display ipv6 prefix-list
ipv6 prefix-list
MTR commands
The following matrix shows the feature and hardware compatibility:
|
Hardware |
MTR compatibility |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK |
Yes |
|
810-LMS/810-LUS |
No |
|
MSR2600-6-X1/2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28/3600-51 |
Yes |
|
MSR3600-28-SI/3600-51-SI |
No |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
Yes |
|
MSR 3610/3620/3620-DP/3640/3660 |
Yes |
|
MSR5620/5660/5680 |
Yes |
|
Hardware |
MTR compatibility |
|
MSR810-LM-GL |
Yes |
|
MSR810-W-LM-GL |
Yes |
|
MSR830-6EI-GL |
Yes |
|
MSR830-10EI-GL |
Yes |
|
MSR830-6HI-GL |
Yes |
|
MSR830-10HI-GL |
Yes |
|
MSR2600-6-X1-GL |
Yes |
|
MSR3600-28-SI-GL |
No |
apply topology
Use apply topology to specify a topology for the MTR policy node.
Use undo apply topology to remove the configuration.
Syntax
apply topology topo-name
undo apply topology
Default
No topology is specified for the MTR policy node.
Views
MTR policy node view
Predefined user roles
network-admin
Parameters
topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters.
Examples
# Specify topology topo1 for node 0 of MTR policy mtr.
<Sysname> system-view
[Sysname] mtr-policy mtr node 0
[Sysname-mtr-policy-mtr-0] apply topology topo1
display mtr-policy
Use display mtr-policy to display MTR policy information.
Syntax
display mtr-policy [ name mtr-policy-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name mtr-policy-name: Specifies an MTR policy by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the command displays information about all MTR policies.
Examples
# Display information about all MTR policies.
MTR-policy: mtr
Node: 0
if-match ip precedence critical
if-match ip acl 3333
apply topology 1
MTR-policy: p
Node: 1
if-match ip precedence routine
if-match ip dscp cs1
if-match ip acl 3501
MTR-policy: q
Node: 0
if-match ip precedence network
if-match ip dscp ef
if-match ip acl 3001
apply topology 1
Node: 1
MTR-policy: w
Node: 0
if-match ip precedence routine
if-match ip dscp 3
Table 183 Command output
|
Field |
Description |
|
MTR-policy |
MTR policy name. |
|
Node |
MTR policy node. |
display topology
Use display topology to display topology information.
Syntax
display topology [ name topo-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays brief information about all topologies.
Examples
# Display brief information about all topologies.
<Sysname> display topology
Total topologies : 4
Topology Address-family VRF
base IPv4 default
mt1 IPv4 default
mt2 IPv4 default
mt3 IPv4 default
# Display detailed information about topology mt1.
<Sysname> display topology name mt1
Topology Name and Index: mt1, 1
Address-family: IPv4
Interfaces: LoopBack0, GigabitEthernet1/0/1,
GigabitEthernet1/0/2, GigabitEthernet1/0/3,
GigabitEthernet1/0/4
Maximum routes limit : 100
Threshold value(%): 90
Table 184 Command output
|
Field |
Description |
|
Total topologies |
Total number of topologies. |
|
Topology |
Topology name. |
|
Address-family |
Address family to which the topology belongs. |
|
VRF |
VPN to which the topology belongs. |
|
Topology Name and Index |
Topology name and index number. |
|
Interfaces |
Interface with which the topology is associated. |
|
Maximum routes limit |
Maximum number of route prefixes supported by the topology. |
|
Threshold value(%) |
Warning threshold for routes supported by the topology. |
global-address-family ipv4
Use global-address-family ipv4 to create the global address family and enter its view.
Use undo global-address-family ipv4 to delete the global address family and all configurations in the view.
Syntax
global-address-family ipv4 [ unicast ]
undo global-address-family ipv4 [ unicast ]
Default
No global address family view exists.
Views
System view
Predefined user roles
network-admin
Parameters
unicast: Specifies the IPv4 unicast address family. If you do not specify this keyword, the command also specifies the IPv4 unicast address family.
Usage guidelines
Before you configure MTR, enter global address family view by using this command.
Examples
# Enter global address family view.
<Sysname> system-view
[Sysname] global-address-family ipv4 unicast
[Sysname-af]
if-match ip acl
Use if-match ip acl to configure an ACL match criterion.
Use undo if-match ip acl to restore the default.
Syntax
if-match ip acl acl-number
undo if-match ip acl
Default
No ACL match criterion is configured.
Views
MTR policy node view
Predefined user roles
network-admin
Parameters
acl-number: Specifies an advanced ACL by its number in the range of 3000 to 3999.
Usage guidelines
You can configure the ACL, DSCP, and IP precedence match criteria for an MTR node at the same time. The match criteria are in an OR relationship. If a packet matches one of the criteria, it matches the node, as well as the MTR policy. If a packet fails to match a node, it goes to the next node for a match.
Examples
# Configure an ACL match criterion for node 0 of MTR policy mtr, allowing packets matching ACL 3333 to pass.
<Sysname> system-view
[Sysname] mtr-policy mtr node 0
[Sysname-mtr-policy-mtr-0] if-match ip acl 3333
if-match ip dscp
Use if-match ip dscp to configure a DSCP match criterion.
Use undo if-match ip dscp to restore the default.
Syntax
if-match ip dscp dscp-value
undo if-match ip dscp
Default
No DSCP match criterion is configured.
Views
MTR policy node view
Predefined user roles
network-admin
Parameters
dscp-value: Specifies a DSCP value in the range of 0 to 63. You can also specify the DSCPs, as shown in Table 185, by description.
Table 185 Description of DSCP values
|
Description |
DSCP value (binary) |
DSCP value (decimal) |
|
default |
000000 |
0 |
|
af11 |
001010 |
10 |
|
af12 |
001100 |
12 |
|
af13 |
001110 |
14 |
|
af21 |
010010 |
18 |
|
af22 |
010100 |
20 |
|
af23 |
010110 |
22 |
|
af31 |
011010 |
26 |
|
af32 |
011100 |
28 |
|
af33 |
011110 |
30 |
|
af41 |
100010 |
34 |
|
af42 |
100100 |
36 |
|
af43 |
100110 |
38 |
|
cs1 |
001000 |
8 |
|
cs2 |
010000 |
16 |
|
cs3 |
011000 |
24 |
|
cs4 |
100000 |
32 |
|
cs5 |
101000 |
40 |
|
cs6 |
110000 |
48 |
|
cs7 |
111000 |
56 |
|
ef |
101110 |
46 |
Usage guidelines
You can configure the ACL, DSCP, and IP precedence match criteria for an MTR node at the same time. The match criteria are in an OR relationship. If a packet matches one of the criteria, it matches the node, as well as the MTR policy. If a packet fails to match a node, it goes to the next node for a match.
Examples
# Configure a DSCP match criterion for node 0 of MTR policy mtr, allowing packets with a DSCP value of 5 to pass.
<Sysname> system-view
[Sysname] mtr-policy mtr node 0
[Sysname-mtr-policy-mtr-0] if-match ip dscp 5.
if-match ip precedence
Use if-match ip precedence to configure an IP precedence match criterion.
Use undo if-match ip precedence to restore the default.
Syntax
if-match ip precedence precedence
undo if-match ip precedence
Default
No IP precedence match criterion is configured.
Views
MTR policy node view
Predefined user roles
network-admin
Parameters
precedence: Specifies an IP precedence value in the range of 0 to 7. You can also specify an IP precedence by its description. For more information, see Table 186.
Table 186 Description of IP precedence
|
Description |
IP precedence |
|
routine |
0 |
|
priority |
1 |
|
immediate |
2 |
|
flash |
3 |
|
flash-override |
4 |
|
critical |
5 |
|
internet |
6 |
|
network |
7 |
Usage guidelines
You can configure the ACL, DSCP, and IP precedence match criteria for an MTR node at the same time. The match criteria are in an OR relationship. If a packet matches one of the criteria, it matches the node, as well as the MTR policy. If a packet fails to match a node, it goes to the next node for a match.
Examples
# Configure an IP precedence match criterion for node 0 of MTR policy mtr, allowing packets with an IP precedence of 5 to pass.
<Sysname> system-view
[Sysname] mtr-policy mtr node 0
[Sysname-mtr-policy-mtr-0] if-match ip precedence 5
mtr-policy
Use mtr-policy to create an MTR policy node and enter its view, or enter the view of an existing MTR policy node.
Use undo mtr-policy to delete the specified MTR policy node.
Syntax
mtr-policy policy-name node node-value
undo mtr-policy policy-name [ node node-value ]
Default
No MTR policy nodes exist.
Views
System view
Predefined user roles
network-admin
Parameters
policy-name: Specifies an MTR policy by its name, a case-sensitive string of 1 to 63 characters.
node node-value: Specifies an MTR policy node by its number in the range of 0 to 255.
Usage guidelines
An MTR policy comprises multiple nodes that are in an OR relationship. If a packet matches one of the nodes, it matches the MTR policy.
Use the undo mtr-policy policy-name node node-value command to delete the specified node from the specified MTR policy. If the MTR policy has only one node, the command also deletes the MTR policy.
Use the undo mtr-policy policy-name command to delete the specified MTR policy.
Examples
# Create MTR policy mtr and node 0, and enter MTR policy node view.
<Sysname> system-view
[Sysname] mtr-policy mtr node 0
[Sysname-mtr-policy-mtr-0]
routing-table limit
Use routing-table limit to configure the maximum number of active routes supported by the topology.
Use undo routing-table limit to restore the default.
Syntax
routing-table limit number { warn-threshold | simply-alert }
undo routing-table limit
Default
The following matrix shows the default maximum number of active routes supported by the topology:
|
Hardware |
Default state |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK |
51024 |
|
MSR2600-6-X1/2600-10-X1 |
51024 |
|
MSR 2630 |
51024 |
|
MSR3600-28/3600-51 |
51024 |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
101024 |
|
MSR 3610 |
51024 |
|
MSR 3620/3620-DP/3640/3660 |
101024 |
|
MSR5620/5660/5680 |
101024 |
Views
Topology view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of active routes supported by the topology.
The following matrix shows the value ranges for the number argument:
|
Hardware |
Value range |
|
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK |
1 to 51024 |
|
MSR2600-6-X1/2600-10-X1 |
1 to 51024 |
|
MSR 2630 |
1 to 51024 |
|
MSR3600-28/3600-51 |
1 to 51024 |
|
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC |
1 to 101024 |
|
MSR 3610 |
1 to 51024 |
|
MSR 3620/3620-DP/3640/3660 |
1 to 101024 |
|
MSR5620/5660/5680 |
1 to 101024 |
warn-threshold: Specifies a warning threshold in the range of 1 to 100 in percentage. When the percentage of the number of existing active routes to the maximum number of active routes exceeds the specified threshold, the system generates an alarm message but still allows new active routes. If active routes in the topology reach the maximum, no more active routes are added.
simply-alert: Enables the topology to add new active routes but generate a system log message when the maximum number of active routes is exceeded.
Examples
# Configure the maximum number of active routes supported by topology mt1 as 1000. Enable the topology to add new active routes but generate a system log message when the maximum number of active routes is exceeded.
<Sysname> system-view
[Sysname] global-address-family ipv4 unicast
[Sysname-af-topology-mt1] routing-table limit 1000 simply-alert
topology
Use topology to create a topology and enter its view.
Use undo topology to remove a topology.
Syntax
topology topo-name
undo topology topo-name
Default
No topologies exist.
Views
Global address family view
Predefined user roles
network-admin
Parameters
topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters.
Examples
# Create topology mt and enter its view.
<Sysname> system-view
[Sysname] global-address-family ipv4 unicast
[Sysname-af] topology mt
[Sysname-af-topology-mt]
topology ipv4
Use topology ipv4 to associate the interface with a topology and enter IPv4 unicast topology view of the interface.
Use undo topology ipv4 to remove the association between an IPv4 unicast topology and the interface.
Syntax
topology ipv4 [ unicast ] topo-name
undo topology ipv4 [ unicast ] topo-name
Default
An interface is not associated with any topologies.
Views
Interface view
Predefined user roles
network-admin
Parameters
unicast: Specifies the unicast topology. If you do not specify this keyword, the command also specifies the unicast topology.
topo-name: Specifies a topology by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
Before you associate the interface with a topology, you must create the topology.
If the topology name is unicast, you must specify the unicast keyword for the command. Otherwise, the command cannot take effect.
Examples
# Associate interface Loopback 0 with topology mt1.
<Sysname> system-view
[Sysname] interface loopback 0
[Sysname-LoopBack0] topology ipv4 unicast mt1
[Sysname-LoopBack0-topology-1]
topology-routing mtr-policy
Use topology-routing mtr-policy to enable an MTR policy.
Use undo topology-routing mtr-policy to disable the MTR policy.
Syntax
topology-routing mtr-policy policy-name
undo topology-routing mtr-policy
Default
An MTR policy is disabled.
Views
Global address family view
Predefined user roles
network-admin
Parameters
policy-name: Specifies an MTR policy by its name, a case-sensitive string of 1 to 63 characters.
Examples
# Enable MTR policy mtr.
<Sysname> system-view
[Sysname] global-address-family ipv4
[Sysname-global-ipv4] topology-routing mtr-policy mtr
abr-summary (OSPF area view),109
abr-summary (OSPFv3 area view),551
address-family ipv4,314
address-family ipv4,215
address-family ipv4,1
address-family ipv6,637
address-family ipv6,1
address-family ipv6,315
address-family link-state,316
advertise-rib-active,317
aggregate,317
apply access-vpn vpn-instance,669
apply access-vpn vpn-instance,497
apply as-path,687
apply comm-list delete,687
apply community,688
apply continue,498
apply continue,670
apply cost,689
apply cost-type,690
apply default-next-hop,670
apply default-next-hop,498
apply default-output-interface,499
apply default-output-interface,671
apply extcommunity,690
apply fast-reroute,714
apply ip-address next-hop,715
apply ip-df,500
apply ip-precedence,691
apply ipv6 fast-reroute,719
apply ipv6 next-hop,720
apply isis,692
apply loadshare,672
apply loadshare,501
apply local-preference,692
apply mpls-label,693
apply next-hop,502
apply next-hop,674
apply origin,693
apply output-interface,675
apply output-interface,503
apply precedence,675
apply precedence,504
apply preference,694
apply preferred-value,695
apply prefix-priority,695
apply qos-local-id,696
apply remark-vpn,676
apply remark-vpn,505
apply tag,696
apply topology,725
apply traffic-index,697
area,551
area (OSPF view),109
area-authentication send-only,216
area-authentication-mode,216
asbr-summary,110
asbr-summary (OSPFv3 view),552
authentication-mode,111
auto-cost enable,637
auto-cost enable,218
balance,320
balance as-path-neglect,322
balance as-path-relax,322
bandwidth-reference,219
bandwidth-reference,638
bandwidth-reference,553
bandwidth-reference (OSPF view),112
bestroute as-path-neglect,323
bestroute compare-med,324
bestroute igp-metric-ignore,324
bestroute med-confederation,325
bfd all-interfaces enable,65
bgp,326
bgp update-delay on-startup,326
bgp update-delay on-startup prefix-list,327
bgp-policy accounting,328
checkzero,525
checkzero,66
circuit-cost,639
circuit-cost,219
compare-different-as-med,329
confederation id,330
confederation nonstandard,331
confederation peer-as,331
continue,698
cost-style,220
dampening,332
database-filter peer (OSPF view),113
default,114
default cost,66
default cost,525
default local-preference,333
default med,334
default tag,554
default-cost (OSPF area view),115
default-cost (OSPFv3 area view),554
default-route,67
default-route imported,335
default-route-advertise,221
default-route-advertise,640
default-route-advertise (OSPF view),116
default-route-advertise (OSPFv3 view),555
delete ipv6 static-routes all,517
delete static-routes all,53
description (OSPF/OSPF area view),117
discard-route,117
display bgp dampening parameter,336
display bgp group,337
display bgp instance-info,340
display bgp link-state,341
display bgp network,344
display bgp non-stop-routing status,346
display bgp paths,347
display bgp peer,348
display bgp routing-table dampened,358
display bgp routing-table flap-info,360
display bgp routing-table ipv4 multicast,363
display bgp routing-table ipv4 rtfilter,368
display bgp routing-table ipv4 unicast,375
display bgp routing-table ipv6 multicast,381
display bgp routing-table ipv6 unicast,389
display bgp routing-table ipv6 unicast inlabel,395
display bgp routing-table ipv6 unicast outlabel,396
display bgp update-group,397
display bgp-policy statistics,402
display ip as-path,698
display ip community-list,699
display ip extcommunity-list,700
display ip policy-based-route,506
display ip policy-based-route interface,506
display ip policy-based-route local,509
display ip policy-based-route setup,510
display ip prefix-list,716
display ip routing-table,2
display ip routing-table acl,6
display ip routing-table ip-address,8
display ip routing-table prefix-list,11
display ip routing-table protocol,12
display ip routing-table statistics,14
display ip routing-table summary,15
display ipv6 policy-based-route,677
display ipv6 policy-based-route interface,678
display ipv6 policy-based-route local,680
display ipv6 policy-based-route setup,682
display ipv6 prefix-list,721
display ipv6 rib attribute,16
display ipv6 rib graceful-restart,17
display ipv6 rib nib,18
display ipv6 route-direct nib,20
display ipv6 route-static nib,517
display ipv6 route-static routing-table,520
display ipv6 routing-table,22
display ipv6 routing-table acl,27
display ipv6 routing-table ipv6-address,31
display ipv6 routing-table prefix-list,33
display ipv6 routing-table protocol,35
display ipv6 routing-table statistics,37
display ipv6 routing-table summary,38
display isis,222
display isis graceful-restart event-log,224
display isis graceful-restart status,225
display isis interface,226
display isis lsdb,230
display isis mesh-group,234
display isis name-table,235
display isis non-stop-routing event-log,236
display isis non-stop-routing status,237
display isis peer,238
display isis redistribute,241
display isis redistribute ipv6,641
display isis route,243
display isis route ipv6,642
display isis spf-tree,246
display isis spf-tree ipv6,645
display isis statistics,251
display isis statistics ipv6,649
display mac-list,700
display mtr-policy,725
display osi,254
display osi statistics,256
display ospf,118
display ospf abr-asbr,124
display ospf abr-summary,125
display ospf asbr-summary,127
display ospf event-log,128
display ospf fast-reroute lfa-candidate,131
display ospf graceful-restart,132
display ospf hostname-table,135
display ospf interface,135
display ospf lsdb,138
display ospf nexthop,142
display ospf non-stop-routing status,143
display ospf peer,144
display ospf peer statistics,148
display ospf request-queue,149
display ospf retrans-queue,150
display ospf routing,151
display ospf spf-tree,154
display ospf statistics,157
display ospf vlink,161
display ospfv3,556
display ospfv3 abr-asbr,562
display ospfv3 abr-summary,563
display ospfv3 asbr-summary,565
display ospfv3 event-log,567
display ospfv3 graceful-restart,569
display ospfv3 interface,574
display ospfv3 lsdb,576
display ospfv3 nexthop,582
display ospfv3 non-stop-routing,583
display ospfv3 peer,584
display ospfv3 request-queue,587
display ospfv3 retrans-queue,588
display ospfv3 routing,589
display ospfv3 spf-tree,591
display ospfv3 statistics,594
display ospfv3 vlink,598
display rib attribute,38
display rib graceful-restart,40
display rib nib,41
display rip,67
display rip database,70
display rip graceful-restart,71
display rip interface,71
display rip neighbor,73
display rip non-stop-routing,74
display rip route,75
display ripng,526
display ripng database,527
display ripng graceful-restart,528
display ripng interface,528
display ripng neighbor,530
display ripng non-stop-routing,530
display ripng route,531
display route-direct nib,45
display route-policy,701
display router id,162
display route-static nib,53
display route-static routing-table,56
display topology,726
distribute bgp-ls,162
distribute bgp-ls,257
domain-authentication send-only,258
domain-authentication-mode,259
domain-distinguisher,404
dscp,163
ebgp-interface-sensitive,404
enable ipsec-profile,599
enable ipsec-profile,533
enable link-local-signaling,164
enable out-of-band-resynchronization,164
event-log,600
event-log,165
fast-reroute,651
fast-reroute,77
fast-reroute,533
fast-reroute,260
fast-reroute (OSPF view),165
fast-reroute (OSPFv3 view),600
fast-reroute route-policy,405
fib lifetime,47
filter (OSPF area view),166
filter (OSPFv3 area view),601
filter-policy export,261
filter-policy export,651
filter-policy export,406
filter-policy export,534
filter-policy export,78
filter-policy export (OSPF view),167
filter-policy export (OSPFv3 view),602
filter-policy import,80
filter-policy import,535
filter-policy import,408
filter-policy import,262
filter-policy import,653
filter-policy import (OSPF view),168
filter-policy import (OSPFv3 view),603
flash-flood,264
flush suboptimal-route,409
global-address-family ipv4,727
graceful-restart,81
graceful-restart,536
graceful-restart,410
graceful-restart,264
graceful-restart (OSPF view),169
graceful-restart enable,604
graceful-restart helper enable,171
graceful-restart helper enable,605
graceful-restart helper strict-lsa-checking,606
graceful-restart helper strict-lsa-checking,171
graceful-restart interval,537
graceful-restart interval,82
graceful-restart interval,606
graceful-restart interval (OSPF view),172
graceful-restart suppress-sa,265
graceful-restart t1,266
graceful-restart t2,266
graceful-restart t3,267
graceful-restart timer purge-time,411
graceful-restart timer restart,412
graceful-restart timer wait-for-rib,413
group,413
host-advertise,172
hostname,173
host-route,82
if-match acl,511
if-match acl,682
if-match app-group,511
if-match as-path,702
if-match community,703
if-match cost,703
if-match extcommunity,704
if-match interface,705
if-match ip,717
if-match ip acl,728
if-match ip dscp,729
if-match ip precedence,730
if-match ipv6,722
if-match local-preference,705
if-match mac-list,706
if-match mpls-label,706
if-match object-group,512
if-match packet-length,513
if-match packet-length,683
if-match route-type,707
if-match tag,708
if-match vlan,708
ignore-att,268
ignore-first-as,414
import-route,268
import-route,415
import-route,83
import-route,654
import-route,537
import-route (OSPF view),174
import-route (OSPFv3 view),607
import-route isis level-1 into level-2,270
import-route isis level-2 into level-1,271
import-route isisv6 level-1 into level-2,655
import-route isisv6 level-2 into level-1,656
import-route limit,272
import-route limit,657
inter-protocol fast-reroute,48
ip as-path,709
ip community-list,710
ip extcommunity-list,711
ip local policy-based-route,513
ip policy-based-route,514
ip prefix-list,718
ip route-static,58
ip route-static default-preference,61
ip route-static fast-reroute auto,61
ip route-static primary-path-detect bfd echo,62
ip route-static-group,62
ip vpn-instance (BGP instance view),417
ipv6 local policy-based-route,683
ipv6 policy-based-route (interface view),684
ipv6 policy-based-route (system view),685
ipv6 prefix-list,723
ipv6 route-static,522
ipv6 route-static default-preference,524
isis,273
isis authentication send-only,274
isis authentication-mode,275
isis bfd enable,277
isis circuit-level,277
isis circuit-type p2p,278
isis cost,279
isis dis-name,279
isis dis-priority,280
isis enable,281
isis fast-reroute lfa-backup exclude,281
isis ipv6 bfd enable,658
isis ipv6 cost,658
isis ipv6 enable,659
isis ipv6 fast-reroute lfa-backup exclude,660
isis ipv6 prefix-suppression,660
isis ipv6 primary-path-detect bfd,661
isis ipv6 tag,662
isis mesh-group,282
isis mib-binding,283
isis peer-ip-check,283
isis prefix-suppression,284
isis primary-path-detect bfd,285
isis silent,285
isis small-hello,286
isis tag,286
isis timer csnp,287
isis timer hello,288
isis timer holding-multiplier,289
isis timer lsp,289
isis timer retransmit,290
isis topology enable,291
is-level,292
is-name,292
is-name map,293
ispf enable,176
ispf enable,294
ispf enable,662
label-allocation-mode,418
log-peer-change,294
log-peer-change,608
log-peer-change,419
log-peer-change,176
lsa-arrival-interval,177
lsa-generation-interval,177
lsa-generation-interval,609
lsdb-overflow-interval,178
lsdb-overflow-limit,179
lsp-fragments-extend,295
lsp-length originate,295
lsp-length receive,296
mac-list,712
maximum load-balancing,84
maximum load-balancing,663
maximum load-balancing,297
maximum load-balancing,538
maximum load-balancing (OSPF view),179
maximum load-balancing (OSPFv3 view),610
mtr-policy,731
multi-topology,663
network,85
network,419
network (OSPF area view),180
network short-cut,420
network-entity,297
non-stop-routing,539
non-stop-routing,298
non-stop-routing,610
non-stop-routing,422
non-stop-routing,49
non-stop-routing,181
non-stop-routing,86
nssa,182
nssa,611
opaque-capability enable,183
ospf,184
ospf area,185
ospf authentication-mode,185
ospf bfd enable,187
ospf cost,187
ospf database-filter,188
ospf dr-priority,189
ospf fast-reroute lfa-backup,190
ospf mib-binding,190
ospf mtu-enable,191
ospf network-type,191
ospf prefix-suppression,193
ospf primary-path-detect bfd,193
ospf timer dead,194
ospf timer hello,195
ospf timer poll,195
ospf timer retransmit,196
ospf trans-delay,197
ospf ttl-security,197
ospfv3,613
ospfv3 area,613
ospfv3 bfd enable,614
ospfv3 cost,615
ospfv3 dr-priority,615
ospfv3 fast-reroute lfa-backup exclude,616
ospfv3 ipsec-profile,616
ospfv3 mib-binding,617
ospfv3 mtu-ignore,618
ospfv3 network-type,618
ospfv3 peer,619
ospfv3 prefix-suppression,620
ospfv3 primary-path-detect bfd,621
ospfv3 timer dead,621
ospfv3 timer hello,622
ospfv3 timer poll,623
ospfv3 timer retransmit,623
ospfv3 trans-delay,624
output-delay,540
output-delay,87
peer,198
peer,87
peer advertise-community,423
peer advertise-ext-community,424
peer advertise-policy exist-policy,426
peer advertise-policy non-exist-policy,427
peer allow-as-loop,428
peer as-number (for a BGP peer group),430
peer as-number (for a BGP peer),431
peer as-path-acl,432
peer bfd,433
peer capability-advertise conventional,434
peer capability-advertise route-refresh,436
peer capability-advertise suppress-4-byte-as,437
peer connect-interface,438
peer default-route-advertise,439
peer description,441
peer ebgp-max-hop,442
peer enable,443
peer fake-as,445
peer filter-policy,446
peer group,448
peer ignore,449
peer ignore-originatorid,450
peer ipsec-profile,451
peer keep-all-routes,452
peer label-route-capability,454
peer log-change,455
peer low-memory-exempt,456
peer next-hop-local,457
peer password,458
peer preferred-value,459
peer prefix-list,460
peer public-as-only,462
peer reflect-client,463
peer route-limit,465
peer route-policy,467
peer route-update-interval,468
peer soo,469
peer source-address,471
peer substitute-as,473
peer timer,474
peer timer connect-retry,475
peer ttl-security,476
pic,477
pic,199
pic,299
policy-based-route,515
preference,625
preference,478
preference,300
preference,88
preference,540
preference,664
preference,200
prefix,63
prefix-priority,300
prefix-priority,665
prefix-priority,201
prefix-suppression,202
prefix-suppression,625
primary-path-detect bfd,479
protocol lifetime,50
reflect between-clients,479
reflector cluster-id,480
refresh bgp,481
reset bgp,483
reset bgp all,485
reset bgp dampening,486
reset bgp flap-info,487
reset ip policy-based-route statistics,516
reset ip prefix-list,719
reset ip routing-table statistics protocol,51
reset ipv6 policy-based-route statistics,686
reset ipv6 prefix-list,724
reset ipv6 routing-table statistics protocol,51
reset isis all,301
reset isis graceful-restart event-log,302
reset isis non-stop-routing event-log,302
reset isis peer,303
reset mac-list,713
reset osi statistics,304
reset ospf event-log,202
reset ospf process,203
reset ospf redistribution,204
reset ospf statistics,204
reset ospfv3 event-log,626
reset ospfv3 process,627
reset ospfv3 redistribution,627
reset ospfv3 statistics,628
reset rip process,89
reset rip statistics,89
reset ripng process,541
reset ripng statistics,541
retain local-label,488
rfc1583 compatible,204
rib,52
rip,89
rip authentication-mode,90
rip bfd,91
rip bfd enable destination,92
rip default-route,93
rip enable,94
rip input,94
rip max-packet-length,95
rip metricin,95
rip metricout,96
rip mib-binding,97
rip output,98
rip output-delay,99
rip poison-reverse,99
rip primary-path-detect bfd,100
rip split-horizon,100
rip summary-address,101
rip triggered,102
rip version,102
ripng,542
ripng default-route,543
ripng enable,543
ripng ipsec-profile,544
ripng metricin,544
ripng metricout,545
ripng output-delay,546
ripng poison-reverse,546
ripng primary-path-detect bfd echo,547
ripng split-horizon,547
ripng summary-address,548
route-policy,713
router id,205
router id (system view),489
router-id,628
router-id (BGP instance view),490
router-id (BGP-VPN instance view),491
routing-table limit,732
set-att,304
set-overload,305
set-overload,666
silent-interface,103
silent-interface (OSPF view),206
silent-interface(OSPFv3 view),629
snmp context-name,306
snmp context-name,630
snmp context-name,492
snmp trap rate-limit,207
snmp trap rate-limit,631
snmp-agent trap enable bgp,493
snmp-agent trap enable isis,306
snmp-agent trap enable ospf,207
snmp-agent trap enable ospfv3,629
spf-schedule-interval,208
spf-schedule-interval,632
stub (OSPF area view),209
stub (OSPFv3 area view),632
stub-router,210
stub-router,633
summary,104
summary,308
summary,667
summary automatic,494
timer,494
timer connect-retry,495
timer lsp-generation,309
timer lsp-max-age,310
timer lsp-refresh,310
timer spf,668
timer spf,311
timer triggered,104
timer triggered,549
timers,105
timers,549
topology,733
topology,312
topology ipv4,734
topology-routing mtr-policy,734
transmit-pacing,211
transmit-pacing,634
trip retransmit count,106
trip retransmit timer,107
ttl-security,212
validate-source-address,107
version,108
virtual-system,313
vlink-peer (OSPF area view),213
vlink-peer (OSPFv3 area view),635
