Professional Documents
Culture Documents
Table of Contents
Table of Contents
Chapter 1 IPv6 Static Routing Configuration ............................................................................. 1-1 1.1 Introduction to IPv6 Static Routing .................................................................................... 1-1 1.1.1 Features and Functionalities of IPv6 Static Routes ................................................ 1-1 1.1.2 Default IPv6 Route .................................................................................................. 1-1 1.2 Configuring IPv6 Static Routes.......................................................................................... 1-2 1.2.1 Configuration prerequisites ..................................................................................... 1-2 1.2.2 Configuring IPv6 Static Routes ............................................................................... 1-2 1.3 Displaying and Maintaining IPv6 Static Routes ................................................................. 1-2 1.4 IPv6 Static Routing Configuration Example....................................................................... 1-3 Chapter 2 IPv6-RIPng Configuration ........................................................................................... 2-1 2.1 Introduction to RIPng ......................................................................................................... 2-1 2.1.1 RIPng Working Mechanism..................................................................................... 2-1 2.1.2 RIPng Packet Format.............................................................................................. 2-2 2.1.3 RIPng Packet Processing Procedure...................................................................... 2-3 2.1.4 Protocol Specification.............................................................................................. 2-4 2.2 RIPng Basic Configuration................................................................................................. 2-4 2.2.1 Configuration Prerequisites..................................................................................... 2-4 2.2.2 Configuring the Basic RIPng Function .................................................................... 2-4 2.3 RIPng Configuration .......................................................................................................... 2-5 2.3.1 Configuring an Additional Routing Metric................................................................ 2-5 2.3.2 Configuring RIPng Route Summarization ............................................................... 2-5 2.3.3 Configuring RIPng to Advertise a Default Route..................................................... 2-6 2.3.4 Configuring a RIPng Route Filtering Policy............................................................. 2-6 2.3.5 Configuring a RIPng Priority.................................................................................... 2-7 2.3.6 Configuring RIPng Route Redistribution ................................................................. 2-7 2.4 RIPng Network Adjustment and Optimization ................................................................... 2-8 2.4.1 Configuring RIPng Timers....................................................................................... 2-8 2.4.2 Configuring the Split Horizon and Poison Reverse Functions ................................ 2-8 2.4.3 Configuring Zero Field Check for RIPng Packet Headers ...................................... 2-9 2.4.4 Configuring the Maximum Number of Equivalent Routes ..................................... 2-10 2.5 Displaying and Maintaining RIPng................................................................................... 2-10 2.6 RIPng Configuration Example ......................................................................................... 2-10 Chapter 3 IPv6-OSPFv3 Configuration........................................................................................ 3-1 3.1 Introduction to OSPFv3 ..................................................................................................... 3-1 3.1.1 OSPFv3 Overview................................................................................................... 3-1 3.1.2 OSPFv3 Packets ..................................................................................................... 3-1 3.1.3 OSPFv3 LSA Types ................................................................................................ 3-2
Table of Contents
3.1.4 Timers of OSPFv3................................................................................................... 3-3 3.1.5 OSPFv3 Features Supported.................................................................................. 3-3 3.1.6 Related RFCs.......................................................................................................... 3-3 3.2 IPv6-OSPFv3 Configuration Task List............................................................................... 3-4 3.3 Configuring OSPFv3 Basic Functions ............................................................................... 3-4 3.3.1 Prerequisites ........................................................................................................... 3-4 3.3.2 Configuring OSPFv3 Basic Functions..................................................................... 3-4 3.4 Configuring OSPFv3 Area Parameters ............................................................................. 3-5 3.4.1 Prerequisites ........................................................................................................... 3-5 3.4.2 Configuring an OSPFv3 Stub Area ......................................................................... 3-5 3.4.3 Configuring OSPFv3 Virtual Links........................................................................... 3-6 3.5 Configuring OSPFv3 Routing Information Management ................................................... 3-7 3.5.1 Prerequisites ........................................................................................................... 3-7 3.5.2 Configuring OSPFv3 Route Summarization ........................................................... 3-7 3.5.3 Configuring OSPFv3 Inbound Route Filtering......................................................... 3-7 3.5.4 Configuring Link Costs for OSPFv3 Interfaces ....................................................... 3-8 3.5.5 Configuring the Maximum Number of OSPFv3 Load-balancing Routes ................ 3-8 3.5.6 Configuring OSPFv3 Route Redistribution ............................................................. 3-9 3.6 Configuring OSPFv3 Network Optimization ...................................................................... 3-9 3.6.1 Prerequisites ......................................................................................................... 3-10 3.6.2 Configuring OSPFv3 Timers ................................................................................. 3-10 3.6.3 Configuring the DR Priority for an Interface .......................................................... 3-11 3.6.4 Ignoring MTU Check for DD Packets .................................................................... 3-11 3.6.5 Disable Interfaces from Sending OSPFv3 Packets .............................................. 3-12 3.7 Displaying and Maintaining OSPFv3 ............................................................................... 3-13 3.8 OSPFv3 Configuration Examples .................................................................................... 3-14 3.8.1 Configuring OSPFv3 Areas................................................................................... 3-14 3.8.2 Configuring OSPFv3 DR Election ......................................................................... 3-18 3.9 Troubleshooting OSPFv3 Configuration.......................................................................... 3-21 3.9.1 No OSPFv3 Neighbor Relationship Established................................................... 3-21 3.9.2 Incorrect Routing Information................................................................................ 3-22 Chapter 4 IPv6-IS-IS Configuration.............................................................................................. 4-1 4.1 Introduction to IPv6-IS-IS................................................................................................... 4-1 4.2 IPv6-IS-IS Basic Configuration .......................................................................................... 4-1 4.2.1 Configuration Prerequisites..................................................................................... 4-2 4.2.2 Configuring IPv6-IS-IS Basic Functions.................................................................. 4-2 4.3 Configuring IPv6-IS-IS Routing Information Control.......................................................... 4-2 4.3.1 Configuration Prerequisites..................................................................................... 4-2 4.3.2 Configuration Procedure ......................................................................................... 4-2 4.4 Displaying and Maintaining IPv6-IS-IS .............................................................................. 4-4 4.5 IPv6-IS-IS Configuration Example ..................................................................................... 4-4
Table of Contents
Chapter 5 IPv6-BGP4+ Configuration.......................................................................................... 5-1 5.1 BGP4+ Overview ............................................................................................................... 5-1 5.2 Configuration Task List ...................................................................................................... 5-2 5.3 Configuring BGP4+ Basic Functions ................................................................................. 5-3 5.3.1 Prerequisites ........................................................................................................... 5-3 5.3.2 Configuring an IPv6 Peer ........................................................................................ 5-3 5.3.3 Advertising a Local IPv6 Route ............................................................................... 5-3 5.3.4 Configuring a Preferred Value for Routes Received from a Peer/Peer Group ....... 5-4 5.3.5 Specifying a Local Update Source Interface to a Peer/Peer Group ....................... 5-4 5.3.6 Configuring a Non Direct EBGP Connection to a Peer/Peer Group ....................... 5-5 5.3.7 Configuring Description for a Peer/Peer Group ...................................................... 5-5 5.3.8 Establishing No Session to a Peer/Peer Group ...................................................... 5-6 5.3.9 Logging Session State and Event Information of a Peer/Peer Group .................... 5-6 5.4 Controlling Route Distribution and Reception.................................................................... 5-7 5.4.1 Prerequisites ........................................................................................................... 5-7 5.4.2 Configuring BGP4+ Route Redistribution ............................................................... 5-7 5.4.3 Advertising Default Route to a Peer/Peer Group .................................................... 5-8 5.4.4 Configuring Route Distribution Policy...................................................................... 5-8 5.4.5 Configuring Route Reception Policy ....................................................................... 5-9 5.4.6 Configuring BGP4+ and IGP Route Synchronization ........................................... 5-10 5.4.7 Configuring Route Dampening.............................................................................. 5-11 5.5 Configuring BGP4+ Route Attributes............................................................................... 5-11 5.5.1 Prerequisites ......................................................................................................... 5-11 5.5.2 Configuring BGP4+ Preference and Default LOCAL_PREF and NEXT_HOP Attributes ........................................................................................................................ 5-11 5.5.3 Configuring the MED Attribute .............................................................................. 5-12 5.5.4 Configuring the AS_PATH Attribute ...................................................................... 5-13 5.6 Adjusting and Optimizing BGP4+ Networks .................................................................... 5-13 5.6.1 Prerequisites ......................................................................................................... 5-14 5.6.2 Configuring BGP4+ Timers ................................................................................... 5-14 5.6.3 Configuring BGP4+ Soft Reset ............................................................................. 5-15 5.6.4 Configuring the Maximum Number of Load-Balancing Routes............................. 5-16 5.7 Configuring a Large Scale BGP4+ Network .................................................................... 5-17 5.7.1 Prerequisites ......................................................................................................... 5-17 5.7.2 Configuring BGP4+ Peer Group ........................................................................... 5-17 5.7.3 Configuring BGP4+ Community............................................................................ 5-19 5.7.4 Configuring a BGP4+ Router Reflector................................................................. 5-20 5.8 Displaying and Maintaining BGP4+ Configuration .......................................................... 5-21 5.8.1 Displaying BGP ..................................................................................................... 5-21 5.8.2 Resetting BGP4+ Connections ............................................................................. 5-22 5.8.3 Clearing BGP4+ Information ................................................................................. 5-22 5.9 BGP4+ Configuration Examples...................................................................................... 5-23
Table of Contents
5.9.1 BGP4+ Basic Configuration .................................................................................. 5-23 5.9.2 BGP4+ Router Reflector Configuration................................................................. 5-25 5.10 Troubleshooting BGP4+ Configuration.......................................................................... 5-27 5.10.1 No BGP4+ Peer Relationship Established.......................................................... 5-27 Chapter 6 Routing Policy Configuration ..................................................................................... 6-1 6.1 Introduction to Routing Policy ............................................................................................ 6-1 6.1.1 Routing Policy and Policy Routing .......................................................................... 6-1 6.1.2 Filters....................................................................................................................... 6-1 6.1.3 Routing Policy Application....................................................................................... 6-3 6.2 Defining Filtering Lists ....................................................................................................... 6-3 6.2.1 Prerequisites ........................................................................................................... 6-3 6.2.2 Defining an IPv6-prefix List ..................................................................................... 6-3 6.2.3 Defining an AS Path ACL........................................................................................ 6-4 6.2.4 Defining a Community List ...................................................................................... 6-4 6.3 Configuring a Routing Policy ............................................................................................. 6-4 6.3.1 Prerequisites ........................................................................................................... 6-5 6.3.2 Creating a Routing Policy........................................................................................ 6-5 6.3.3 Defining if-match Clauses for the Routing Policy.................................................... 6-6 6.3.4 Defining apply Clauses for the Routing Policy ........................................................ 6-7 6.4 Displaying and Maintaining the Routing Policy.................................................................. 6-8 6.5 Routing Policy Configuration Example .............................................................................. 6-9 6.5.1 Applying Routing Policy When Redistributing IPv6 Routes .................................... 6-9 6.6 Troubleshooting Routing Policy Configuration ................................................................ 6-10 6.6.1 IPv6 Routing Information Filtering Failed.............................................................. 6-10
Note: The term router and router icon in this document refer to either a router in a generic sense or a Layer 3 switch running routing protocols. Verify that the system already operates in IPv4/IPv6 dual-stack mode before configuring IPv6 routing. All the IPv6 routing related configuration mentioned in this manual assumes that the system already operates in IPv4/IPv6 dual-stack mode. For dual stack mode configuration, see the part covering dual stack in the IPv6 Configuration module. For a manually established tunnel, routing protocols can be employed on the tunnel interfaces successfully if the tunnel is configured to support expedite termination subnet addresses. While for tunnels of other types, routing protocols cannot be employed on the tunnel interfaces successfully.
does not match any entries in the routing table, this default route will be used to forward the packet.
Note: Using the undo ipv6 route-static command deletes a single IPv6 static route, while using the delete ipv6 static-routes all command deletes all IPv6 static routes including the default route.
PC2 2::2/64 Vlan-interface400 2::1/64 Vlan-interface200 4::2/64 SwitchB Vlan-interface100 1::1/64 PC1 1::2/64 SwitchA Vlan-interface200 4::1/64 Vlan-interface300 5::1/64 SwitchC Vlan-interface500 3::1/64 PC3 3::2/64 Vlan-interface300 5::2/64
3)
Configure the IPv6 addresses of all the hosts based upon the network diagram, configure the default gateway of PC1 as 1::1, PC2 as 2::1, and PC3 as 3::1. 4) Display configuration information
Protocol
: Static
Preference: 60 Cost : 0
Protocol
: Direct
Preference: 0 Cost : 0
Protocol
: Direct
Preference: 0 Cost : 0
Protocol
: Direct
Preference: 0 Cost : 0
Protocol
: Direct
Preference: 0 Cost : 0
Protocol
: Direct
Preference: 0 Cost : 0
Protocol
: Direct
Preference: 0 Cost : 0
Reply from 3::1 bytes=56 Sequence=1 hop limit=63 Reply from 3::1 bytes=56 Sequence=2 hop limit=63 Reply from 3::1 bytes=56 Sequence=3 hop limit=63 Reply from 3::1 time = 4 ms time = 4 ms time = 5 ms
time = 4 ms
--- 3::1 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 4/4/5 ms
Note: The term router and router icon in this document refer to either a router in a generic sense or a Layer 3 switch running routing protocols. Verify that the system already operates in IPv4/IPv6 dual-stack mode before configuring IPv6 routing. All the IPv6 routing related configuration mentioned in this manual assumes that the system already operates in IPv4/IPv6 dual-stack mode. For dual stack mode configuration, see the part covering dual stack in the IPv6 Configuration module.
fail. After another 240 seconds, if no routing updates are received, the router will remove those routes from the routing table. RIPng supports Split Horizon and Poison Reverse to prevent routing loops, and route redistribution. Each RIPng router maintains a routing database, including route entries to all reachable destinations. These route entries contain the following information: Destination address: IPv6 address of a host or a network. Next hop address: IP address of a neighbor router along the path to the destination. Egress interface: Interface that forwards IPv6 packets. Metric: Cost from the local router to the destination. Routing time: Time elapsed since the routing entry is updated last time. Routing time is reset to 0 each time the routing entry is updated. Route tag: It is used for tagging external routes so that the routes can be controlled flexibly in routing policy based on the tags.
Figure 2-1 RIPng basic packet format Command: Type of message. 0x01 indicates Request, 0x02 indicates Response. Version: Version of RIPng. It can only be 0x01 for the moment. RTE: Route table entry, 20 bytes for each entry.
must be zero
must be zero
0xFF
Figure 2-2 Next hop RTE format IPv6 next hop address is the IPv6 address of the next hop. Figure 2-3 shows the format of the IPv6 prefix RTE.
0 7 15 31
route tag
prefix len
metric
Figure 2-3 IPv6 prefix RTE format IPv6 prefix: Destination IPv6 address prefix. Route tag: Intended to differentiate internal RIP routes from external RIP routes. Prefix len: Length of the IPv6 address prefix. Metric: Cost of a route.
Trigged update caused by route changes Before the router updates its RIPng routing table based on the received response, it must check the validation of the response packet, such as whether the IPv6 address is the link-local address, whether the port number is correct. The response packet failed the check will be discarded.
Note: If RIPng is not enabled on an interface, the interface will not send and receive any RIPng route.
To do Enter system view Enter interface view Advertise a summary IPv6 prefix
Use the command system-view interface interface-type interface-number ripng summary-address prefix-length ipv6-address
Remarks Required
Note: The RIPng default route is forced to send in the update message of the designated interface regardless of whether it exists in the IPv6 routing table.
Use the command filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name } export [ protocol [ process-id ] ]
Remarks Required By default, RIPng does not filter routing information to be advertised.
Redistribute a route
Configure timers
RIPng
30 seconds for the update timer 180 seconds for the timeout timer 120 seconds for the suppress timer 240 seconds for the garbage-collect timer
Note: When adjusting RIPng timers, you should consider the network performance and perform unified configurations on routers running RIPng to avoid unnecessary network traffic increase or route oscillation.
Note: If both the split horizon and poison reverse functions are configured, only the poison reverse function takes effect.
Note: Normally you are recommended to enable the split horizon to prevent routing loops.
To do Enter system view Enter RIPng view Enable the zero field check for RIPng packer headers
Remarks
display ripng process-id database display ripng process-id route display ripng process-id interface [ interface-type interface-number ]
Vlan-interface400 2::1/64
RIPng
Vlan-interface100 1::1 /64 Vlan-interface100 1::2 /64 Vlan-interface200 Vlan-interface200 3::1/64 3::2/64
SwitchA
SwitchB
SwitchC 5::1/64
# Configure Switch A.
<SwitchA> system-view [SwitchA] ipv6 [SwitchA] ripng 1 [SwitchA-ripng-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ripng 1 enable [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 400 [SwitchA-Vlan-interface400] ripng 1 enable [SwitchA-Vlan-interface400] quit
# Configure Switch B.
<SwitchB> system-view [SwitchB] ipv6 [SwitchB] ripng 1 [SwitchB-ripng-1] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] ripng 1 enable [SwitchB-Vlan-interface200] quit [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] ripng 1 enable [SwitchB-Vlan-interface100] quit
# Configure Switch C.
on Vlan-interface100
1, tag 0, A, 6 Sec
1, tag 0, A, 6 Sec
on Vlan-interface200
via FE80::20F:E2FF:FE00:100, cost Dest 4::/64, via FE80::20F:E2FF:FE00:100, cost Dest 5::/64, via FE80::20F:E2FF:FE00:100, cost
1, tag 0, A, 11 Sec
1, tag 0, A, 11 Sec
1, tag 0, A, 11 Sec
on Vlan-interface100
1, tag 0, A, 31 Sec
2, tag 0, A, 31 Sec
2, tag 0, A, 31 Sec
1, tag 0, A, 31 Sec
3)
[SwitchB] acl ipv6 number 2000 [SwitchB-acl6-basic-2000] rule deny source 3::/64 [SwitchB-acl6-basic-2000] rule permit [SwitchB-acl6-basic-2000] quit [SwitchB] ripng 1 [SwitchB-ripng-1] filter-policy 2000 import [SwitchB-ripng-1] filter-policy 2000 export [SwitchB-ripng-1] quit
on Vlan-interface100
1, tag 0, A, 2 Sec
1, tag 0, A, 2 Sec
on Vlan-interface200
via FE80::20F:E2FF:FE00:100, cost Dest 5::/64, via FE80::20F:E2FF:FE00:100, cost [SwitchA] display ripng 1 route
1, tag 0, A, 5 Sec
1, tag 0, A, 5 Sec
on Vlan-interface100
via FE80::20F:E2FF:FE00:1235, cost Dest 4::/64, via FE80::20F:E2FF:FE00:1235, cost Dest 5::/64, via FE80::20F:E2FF:FE00:1235, cost
1, tag 0, A, 2 Sec
2, tag 0, A, 2 Sec
2, tag 0, A, 2 Sec
Note: The term router and router icon in this document refer to either a router in a generic sense or a Layer 3 switch running routing protocols. Verify that the system already operates in IPv4/IPv6 dual-stack mode before configuring IPv6 routing. All the IPv6 routing related configuration mentioned in this manual assumes that the system already operates in IPv4/IPv6 dual-stack mode. For dual stack mode configuration, see the part covering dual stack in the IPv6 Configuration module.
0 Version # Type
31
Figure 3-1 OSPFv3 packet header Major fields: Version #: Version of OSPF, which is 3 for OSPFv3. Type: Type of OSPF packet, from 1 to 5 are hello, DD, LSR, LSU, and LSAck respectively. Packet Length: Packet length in bytes, including header. Instance ID: Instance ID for a link. 0: Reserved, which must be 0.
flooding scope. It was introduced because Router-LSAs and Network-LSAs contain no address information now.
Configuring OSPFv3 Inbound Route Filtering Configuring OSPFv3 Routing Information Management Configuring Link Costs for OSPFv3 Interfaces Configuring the Maximum Number of OSPFv3 Load-balancing Routes Configuring Redistribution OSPFv3 Route
Configuring OSPFv3 Timers Configuring the DR Priority for an Interface Ignoring MTU Check for DD Packets Disable Interfaces OSPFv3 Packets from Sending
Use the command interface interface-type interface-number ospfv3 process-id area area-id [ instance instance-id ]
Remarks
Note: Configure an OSPFv3 process ID when enabling OSPFv3. The process ID takes effect locally, without affecting packet exchange between routers. When configuring a router ID, make sure each router has a unique ID. If a router runs multiple OSPFv3 processes, you need to specify a router ID for each process. You need to specify a router ID manually, which is necessary to make OSPFv3 work.
3.4.1 Prerequisites
Enable IPv6 packet forwarding Configure OSPFv3 basic functions
Remarks Required
To do Enter OSPFv3 area view Configure the area as a stub area Configure the default route cost of sending a packet to the stub area
default-cost value
Note: Configurations on routers attached to the same area should be compatible to avoid information exchange failures even information block and routing loop. You cannot delete an OSPFv3 area directly. Only when you remove all configurations in area view and all interfaces attached to the area become down, can the area be removed automatically. All routers attached to a stub area must be configured with the stub command. The keyword no-summary is only available on the ABR. If you use the stub command with the keyword no-summary on an ABR, the ABR distributes a default summary LSA into the area rather than generating an AS-external-LSA or Inter-Area-Prefix-LSA. The stub area of this kind is also known as totally stub area.
Required
Note: Both ends of a virtual link are ABRs that are configured with the vlink-peer command.
3.5.1 Prerequisites
Enable IPv6 packet forwarding Configure OSPFv3 basic functions
Note: The abr-summary command is available on ABRs only. If contiguous network segments are available in an area, you can use the command to summarize them into one network segment on the ABR. The ABR will advertise only the summary route. Any LSA falling into the specified network segment will not be advertised, reducing the LSDB size in other areas.
To do Enter system view Enter OSPFv3 view Configure inbound route filtering
Use the command system-view ospfv3 [ process-id ] filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name } import
Remarks
Note: Use of the filter-policy import command can only filter routes computed by OSPFv3. Only routes not filtered can be added into the local routing table.
Redistribute routes from other protocols, including from other OSPFv3 processes
Note: Using the import-route command on a router makes the router become an ASBR. Since OSPFv3 is a link state based routing protocol, it cannot directly filter LSAs to be advertised. Therefore, you need to configure filtering redistributed routes before advertising routes that are not filtered in LSAs into the routing domain. Use of the filter-policy export command takes effect only on the local router. However, if the import-route command is not configured, executing the filter-policy export command does not take effect.
For a broadcast network, you can configure DR priorities for interfaces to affect DR/BDR election. By disabling an interface from sending OSPFv3 packets, you can make other routers on the network obtain no information from the interface.
3.6.1 Prerequisites
Enable IPv6 packet forwarding Configure OSPFv3 basic functions
Configure LSA retransmission interval Configure transmission delay Exit to system view Enter OSPFv3 view LSA
Note: The dead interval set on neighboring interfaces cannot be so small. Otherwise, a neighbor is so easy to be considered as down. The LSA retransmission interval cannot be so small to avoid unnecessary retransmissions.
Note: The DR priority of an interface determines the interfaces qualification in DR election. Interfaces having the priority 0 cannot become a DR or BDR.
Note: Multiple processes can disable the same interface from sending OSPFv3 packets. Use of the silent-interface command disables only the interfaces associated with the current process rather than interfaces associated with other processes. After an OSPF interface is set to silent, direct routes of the interface can still be advertised in Intra-Area-Prefix-LSAs via other interfaces, but hello packets for finding neighbors cannot be advertised, so no neighboring relationship can be established on the interface, enhancing adaptability of OSPFv3 networking.
display ospfv3 [ process-id ] display ospfv3 interface [ interface-type interface-number | statistic ] display ospfv3 [ process-id ] lsdb [ [ external | inter-prefix | inter-router | intra-prefix | link | network | router ] [ link-state-id ] [ originate-router router-id ] | total ] display ospfv3 lsdb statistic display ospfv3 [ process-id ] [ area area-id ] peer [ [ interface-type interface-number ] [ verbose ] | peer-router-id ] display ospfv3 peer statistic display ospfv3 [ process-id ] routing [ ipv6-address prefix-length | ipv6-address /prefix-length | abr-routes | asbr-routes | all | statistics ] display ospfv3 [ process-id topology [ area area-id ] display ospfv3 [ process-id ] vlink display ospfv3 next-hop [ process-id ] ] ] Available any view in
Display LSA statistics in OSPFv3 LSDB Display OSPFv3 neighbor information Display OSPFv3 neighbor statistics
Display OSPFv3 area topology information Display OSPFv3 virtual link information Display OSPFv3 next hop information Display OSPFv3 link state request list information Display OSPFv3 link state retransmission list information Display OSPFv3 statistics
display ospfv3 [ process-id request-list [ statistics ] display ospfv3 [ process-id retrans-list [ statistics ] display ospfv3 statistic
Vlan-interface100 2001::2/64
Vlan-interface400 2001:2::1/64
OSPFv3 Area1
Vlan-interface200 2001:1::2/64
OSPFv3 Area2
Vlan-interface400 2001:2::2/64
Stub
SwitchA
Vlan-interface300 2001:3::1/64
SwitchD
# Configure Switch A.
<SwitchA> system-view [SwitchA] ipv6 [SwitchA] ospfv3 [SwitchA-ospfv3-1] router-id 1.1.1.1 [SwitchA-ospfv3-1] quit [SwitchA] interface vlan-interface 300 [SwitchA-Vlan-interface300] ospfv3 1 area 1 [SwitchA-Vlan-interface300] quit [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] ospfv3 1 area 1 [SwitchA-Vlan-interface200] quit
# Configure Switch B
<SwitchB> system-view [SwitchB] ipv6 [SwitchB] ospfv3 [SwitchB-ospf-1] router-id 2.2.2.2 [SwitchB-ospf-1] quit [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] ospfv3 1 area 0 [SwitchB-Vlan-interface100] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] ospfv3 1 area 1 [SwitchB-Vlan-interface200] quit
# Configure Switch C
<SwitchC> system-view [SwitchC] ipv6 [SwitchC] ospfv3 [SwitchC-ospfv3-1] router-id 3.3.3.3 [SwitchC-ospfv3-1] quit [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] ospfv3 1 area 0 [SwitchC-Vlan-interface100] quit [SwitchC] interface vlan-interface 400 [SwitchC-Vlan-interface400] ospfv3 1 area 2 [SwitchC-Vlan-interface400] quit
# Configure Switch D
<SwitchD> system-view [SwitchD] ipv6 [SwitchD] ospfv3 [SwitchD-ospfv3-1] router-id 4.4.4.4 [SwitchD-ospfv3-1] quit [SwitchD] interface Vlan-interface 400 [SwitchD-Vlan-interface400] ospfv3 1 area 2 [SwitchD-Vlan-interface400] quit
OSPFv3 Area ID 0.0.0.0 (Process 1) ---------------------------------------------------------------------Neighbor ID 3.3.3.3 Pri 1 State Full/DR Dead Time 00:00:39 Interface Vlan100 Instance ID 0
OSPFv3 Area ID 0.0.0.1 (Process 1) ---------------------------------------------------------------------Neighbor ID 1.1.1.1 Pri 1 State Full/Backup Dead Time 00:00:38 Interface Vlan200 Instance ID 0
OSPFv3 Area ID 0.0.0.2 (Process 1) ---------------------------------------------------------------------Neighbor ID 4.4.4.4 Pri 1 State Full/DR Dead Time 00:00:38 Interface Vlan400 Instance ID 0
OSPFv3 Router with ID (4.4.4.4) (Process 1) -----------------------------------------------------------------------*Destination: 2001::/64 Type NextHop : IA : FE80::F40D:0:93D0:1 Cost : 2
Interface: Vlan400
Interface: Vlan400
Interface: Vlan400
Interface: Vlan400
3)
# Configure Switch D
[SwitchD] ospfv3
# Configure Switch C, with the default route cost to the stub area being 10.
[SwitchC] ospfv3 [SwitchC-ospfv3-1] area 2 [SwitchC-ospfv3-1-area-0.0.0.2] stub [SwitchC-ospfv3-1-area-0.0.0.2] default-cost 10
# Display OSPFv3 routing table information on Switch D. You can find a default route is added, whose cost is the cost of the directly connected route plus the configured cost.
[SwitchD] display ospfv3 routing E1 - Type 1 external route, E2 - Type 2 external route, IA - Inter area route, * - Selected route I - Intra area route
OSPFv3 Router with ID (4.4.4.4) (Process 1) -----------------------------------------------------------------------*Destination: ::/0 Type NextHop : IA : FE80::F40D:0:93D0:1 Cost : 11
Interface: Vlan400
Interface: Vlan400
Interface: Vlan400
Interface: Vlan400
Interface: Vlan400
4)
# Display OSPFv3 routing table information on Switch D. You can find route entries are reduced. All non directly connected routes are removed except the default route.
[SwitchD] display ospfv3 routing
OSPFv3 Router with ID (4.4.4.4) (Process 1) -----------------------------------------------------------------------*Destination: ::/0 Type NextHop : IA : FE80::F40D:0:93D0:1 Cost : 11
Interface: Vlan400
Interface: Vlan400
SwitchC
SwitchD
# Configure Switch A
Huawei Technologies Proprietary 3-18
# Configure Switch B
<SwitchB> system-view [SwitchB] ipv6 [SwitchB] ospfv3 [SwitchB-ospfv3-1] router-id 2.2.2.2 [SwitchB-ospfv3-1] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] ospfv3 1 area 0 [SwitchB-Vlan-interface200] quit
# Configure Switch C
<SwitchC> system-view [SwitchC] ipv6 [SwitchC] ospfv3 [SwitchC-ospfv3-1] router-id 3.3.3.3 [SwitchC-ospfv3-1] quit [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] ospfv3 1 area 0 [SwitchC-Vlan-interface100] quit
# Configure Switch D
<SwitchD> system-view [SwitchD] ipv6 [SwitchD] ospfv3 [SwitchD-ospfv3-1] router-id 4.4.4.4 [SwitchD-ospfv3-1] quit [SwitchD] interface vlan-interface 200 [SwitchD-Vlan-interface200] ospfv3 1 area 0 [SwitchD-Vlan-interface200] quit
# Display neighbor information on Switch A. You can find routers have the same default DR priority 1. In this case, the router with the highest Router ID is elected as the DR, so Switch D is the DR, Switch C is the BDR.
[SwitchA] display ospfv3 peer OSPFv3 Area ID 0.0.0.0 (Process 1)
---------------------------------------------------------------------Neighbor ID 2.2.2.2 3.3.3.3 4.4.4.4 Pri 1 1 1 State 2-Way/DROther Full/Backup Full/DR Dead Time 00:00:36 00:00:35 00:00:33 Interface Vlan200 Vlan100 Vlan200 Instance ID 0 0 0
# Display neighbor information on Switch D. You can find neighbor states between Router D and other routers are all full.
[SwitchD] display ospfv3 peer OSPFv3 Area ID 0.0.0.0 (Process 1) ---------------------------------------------------------------------Neighbor ID 1.1.1.1 2.2.2.2 3.3.3.3 Pri 1 1 1 State Full/DROther Full/DROther Full/Backup Dead Time 00:00:30 00:00:37 00:00:31 Interface Vlan100 Vlan200 Vlan100 Instance ID 0 0 0
3)
# Display neighbor information on Switch A. You can find DR priorities have been updated, but DR and BDR are not changed.
[SwitchA] display ospfv3 peer OSPFv3 Area ID 0.0.0.0 (Process 1) ---------------------------------------------------------------------Neighbor ID 2.2.2.2 3.3.3.3 4.4.4.4 Pri 0 2 1 State 2-Way/DROther Full/Backup Full/DR Dead Time 00:00:38 00:00:32 00:00:36 Interface Vlan200 Vlan100 Vlan200 Instance ID 0 0 0
#Display neighbor information on Switch D. You can find Switch D is still the DR.
[SwitchD] display ospfv3 peer OSPFv3 Area ID 0.0.0.0 (Process 1)
---------------------------------------------------------------------Neighbor ID 1.1.1.1 2.2.2.2 3.3.3.3 Pri 100 0 2 State Full/DROther Full/DROther Full/Backup Dead Time 00:00:33 00:00:36 00:00:40 Interface Vlan100 Vlan200 Vlan100 Instance ID 0 0 0
4)
# Use the shutdown and undo shutdown commands on interfaces to restart DR/BDR election (omitted). # Display neighbor information on Switch A. You can find Switch C becomes the BDR.
[SwitchA] display ospfv3 peer OSPFv3 Area ID 0.0.0.0 (Process 1) ---------------------------------------------------------------------Neighbor ID 2.2.2.2 3.3.3.3 4.4.4.4 Pri 0 2 1 State Full/DROther Full/Backup Full/DROther Dead Time 00:00:31 00:00:39 00:00:37 Interface Vlan200 Vlan100 Vlan200 Instance ID 0 0 0
# Display neighbor information on Switch D. You can find Switch A becomes the DR.
[SwitchD] display ospfv3 peer OSPFv3 Area ID 0.0.0.0 (Process 1) ---------------------------------------------------------------------Neighbor ID 1.1.1.1 2.2.2.2 3.3.3.3 Pri 100 0 2 State Full/DR 2-Way/DROther Full/Backup Dead Time 00:00:34 00:00:34 00:00:32 Interface Vlan100 Vlan200 Vlan100 Instance ID 0 0 0
II. Analysis
If the physical link and lower protocol work well, check OSPF parameters configured on interfaces. The two neighboring interfaces must have the same parameters, such as the area ID, network segment and mask, network type. If the network type is broadcast, at least one interface must have a DR priority higher than 0.
2) 3) 4) 5)
Display OSPFv3 interface information using the display ospfv3 interface command. Ping the neighbor routers IP address to check connectivity. Check OSPF timers. The dead interval on an interface must be at least four times the hello interval. On a broadcast network, at least one interface must have a DR priority higher than 0.
II. Analysis
The backbone area must maintain connectivity to all other areas. If a router connects to more than one area, at least one area must be connected to the backbone. The backbone cannot be configured as a Stub area. In a Stub area, all routers cannot receive external routes, and all interfaces connected to the Stub area must be associated with the Stub area.
Note: The term router and router icon in this document refer to either a router in a generic sense or a Layer 3 switch running routing protocols. Verify that the system already operates in IPv4/IPv6 dual-stack mode before configuring IPv6 routing. All the IPv6 routing related configuration mentioned in this manual assumes that the system already operates in IPv4/IPv6 dual-stack mode. For dual stack mode configuration, see the part covering dual stack in the IPv6 Configuration module.
Note: You can implement IPv6 networking through IPv6-IS-IS in IPv6 network environment.
network-entity net
ipv6 enable quit interface interface-type interface-number isis ipv6 enable [ process-id ] [ silent ]
Note: You need finish basic IPv6-IS-IS configuration before configuring IPv6-IS-IS routing features.
To do Enter system view Enter IS-IS view Define the routing priority of IPv6-IS-IS
Use command to system-view isis [ process-id ] ipv6 preference { route-policy route-policy-name | preference-value }* ipv6 summary ipv6-prefix prefix-length [ avoid-feedback | generate_null0_route | [ level-1 | level-1-2 | level-2 ] | tag tag-value ] * ipv6 default-route-advertise [ [ level-1 | level-2 | level-1-2 ] | route-policy route-policy-name ]* ipv6 filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name | route-policy route-policy-name } import ipv6 import-route protocol [ process-id | allow-ibgp ] [ cost cost-value | [ level-1 | level-2 | level-1-2 ] | route-policy route-policy-name | tag tag-value ]* ipv6 filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name | route-policy route-policy-name } export [ protocol process-id ] ipv6 import-route isisv6 level-2 into level-1 [ filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name | route-policy route-policy-name } | tag tag-value ]* ipv6 maximum load-balancing number
Remarks
Optional 15 by default
Optional No IPv6-IS-IS default route is defined by default. Optional No filtering policy is defined by default
Optional 4 by default
Note: The ipv6 filter-policy export command, usually used in combination with the ipv6 import-route command, filters the distributed route when advertising it to other routers. If no protocol parameter is specified, all distributed protocols will be filtered.
Display the IS-IS mesh group Display the mapping table between the host name and system ID Display information of the IS-IS peer Display the IS-IS routing information Display information of the SPF log Display statistic information of the IS-IS process Clear IS-IS configuration data Clear the IS-IS data information of a neighbor
name-table
display isis peer [ verbose ] [ process-id ] display isis route ipv6 [ [ level-1 | level-2 ] | verbose ]* [ process-id ] display isis [ process-id ] spf-log
display isis statistics [ level-1 | level-2 | level-1-2 ] [ process-id ] reset isis all [ process-id ] reset isis peer [ process-id ] system-id
Switch A and Switch B are Level-1 switches, Switch D is Level-2 switch, and Switch C is a Level-1-2 switch connecting two areas. Switch A, Switch B, Switch C are in area 10, while Switch D is in area 20.
Vlan- int erf ac e301 20 01 :4 ::1/64 Vlan- interf ac e300 200 1: 3::1 /64 Vlan- interf ac e30 0 20 01 :3 ::2/64
Sw itchC L 1/2
Sw itchD L2
Sw itchB L1
# Configure Switch A.
<SwitchA> system-view [SwitchA] isis 1 [SwitchA-isis-1] is-level level-1 [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] ipv6 enable [SwitchA-isis-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] isis ipv6 enable 1 [SwitchA-Vlan-interface100] quit
# Configure Switch B.
<SwitchB> system-view [SwitchB] isis 1 [SwitchB-isis-1] is-level level-1 [SwitchB-isis-1] network-entity 10.0000.0000.0002.00 [SwitchB-isis-1] ipv6 enable [SwitchB-isis-1] quit [SwitchB] interface vlan-interface 200
# Configure Switch C.
<SwitchC> system-view [SwitchC] isis 1 [SwitchC-isis-1] network-entity 10.0000.0000.0003.00 [SwitchC-isis-1] ipv6 enable [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] isis ipv6 enable 1 [SwitchC-Vlan-interface100] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] isis ipv6 enable 1 [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] isis ipv6 enable 1 [SwitchC-Vlan-interface300] quit
# Configure Switch D.
<SwitchD> system-view [SwitchD] isis 1 [SwitchD-isis-1] is-level level-2 [SwitchD-isis-1] network-entity 20.0000.0000.0004.00 [SwitchD-isis-1] ipv6 enable [SwitchD-isis-1] quit [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] isis ipv6 enable 1 [SwitchD-Vlan-interface300] quit [SwitchD] interface vlan-interface 301 [SwitchD-Vlan-interface301] isis ipv6 enable 1 [SwitchD-Vlan-interface301] quit
Note: This chapter describes only configuration for BGP4+. For BGP-related information, refer to the part covering BGP configuration in the IPv4 Routing module. Verify that the system already operates in IPv4/IPv6 dual-stack mode before configuring IPv6 routing. All the IPv6 routing related configuration mentioned in this manual assumes that the system already operates in IPv4/IPv6 dual-stack mode. For dual stack mode configuration, see the part covering dual stack in the IPv6 Configuration module.
Configuring a Non Direct EBGP Connection to a Peer/Peer Group Configuring Description for a Peer/Peer Group Establishing No Session to a Peer/Peer Group Logging Session State and Event Information of a Peer/Peer Group Configuring BGP4+ Route Redistribution Advertising Default Route to a Peer/Peer Group
Route and
Configuring Route Distribution Policy Configuring Route Reception Policy Configuring BGP4+ and IGP Route Synchronization Configuring Route Dampening Configuring BGP4+ Preference and Default LOCAL_PREF and NEXT_HOP Attributes Configuring the MED Attribute Configuring the AS_PATH Attribute Configuring BGP4+ Timers
and BGP4+
Configuring BGP4+ Soft Reset Configuring the Maximum Number of Load-Balancing Routes Configuring BGP4+ Peer Group Configuring BGP4+ Community Configuring a BGP4+ Router Reflector
Enter IPv6 address family view Specify an IPv6 peer and its AS number
5.3.4 Configuring a Preferred Value for Routes Received from a Peer/Peer Group
To configure a preferred value for routes received from a peer/peer group, use the following commands: To do Enter system view Enter BGP view Enter IPv6 address family view Configure a preferred value for routes received from a peer/peer group Use the command system-view bgp as-number ipv6-family peer { ipv6-group-name | ipv6-address } preferred-value value Required Optional By default, the preferred value is 0. Remarks
Note: To improve stability and reliability, you can specify the local interface of a BGP4+ connection as loopback interface. By doing so, a connection failure upon redundancy available will not affect BGP4+ connection.
Caution: In general, direct links should be available between EBGP peers. If not available, you can use the peer ebgp-max-hop command to establish a multi-hop TCP connection in between. However, you need not use this command for direct EBGP connection using loopback interfaces.
Note: The peer group for which to configure description must have been created.
Note: Refer to BGP Commands in IPv4 Routing for information about the log-peer-change command.
5.4.1 Prerequisites
Before configuring this task, you have: Enabled IPv6 function Configured BGP4+ basic functions You need to decide on: ACL number Routing policy names on both distribution and reception directions Route dampening parameters: half-life, threshold values
Note: If the default-route imported command is not configured, using the import-route command cannot redistribute any IGP default route.
Note: With the peer default-route-advertise command used, the local router advertises a default route with itself as the next hop to the specified peer/peer group, regardless of whether the default route is available in the routing table.
To do Apply a routing policy to routes advertised to a peer/peer group Specify an IPv6 ACL to filer routes advertised to a peer/peer group Specify an AS path ACL to filer routes advertised to a peer/peer group Specify an IPv6 prefix list to filer routes advertised to a peer/peer group
Use the command peer { ipv6-group-name | ipv6-address } route-policy route-policy-name export peer { ipv6-group-name | ipv6-address } filter-policy acl6-number export peer { ipv6-group-name | ipv6-address } as-path-acl as-path-acl-number export peer { ipv6-group-name | ipv6-address } ipv6-prefix ipv6-prefix-name export
Remarks Required Not applied by default Required Not specified default Required Not specified default Required Not specified default by by by
Note: Members of a peer group must have the same outbound route policy with the peer group. BGP4+ advertises routes not filtered by the specified policy to peers. Using the protocol argument can filter only the specified protocol routes. If no protocol specified, BGP4+ filters all routes to be advertised, including redistributed routes and routes imported using the network command.
ipv6-family filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name } import peer { ipv6-group-name | ipv6-address } route-policy route-policy-name import
To do Specify an ACL to filter routes imported from a peer/peer group Specify an AS path ACL to filter routing information imported from a peer/peer group Specify an IPv6 prefix list to filter routing information imported from a peer/peer group Specify the upper limit of address prefixes imported from a peer/peer group
Use the command peer { ipv6-group-name | ipv6-address } filter-policy acl6-number import peer { ipv6-group-name | ipv6-address } as-path-acl as-path-acl-number import peer { ipv6-group-name | ipv6-address } ipv6-prefix ipv6-prefix-name import peer { ipv6-group-name | ipv6-address } route-limit limit [ percentage ]
Remarks Required Not specified default Required Not specified default Required Not specified default Optional By default, no limit on prefixes by by by
Note: Only routes not filtered by the specified policy can be added into the local BGP4+ routing table. Members of a peer group can have different inbound route policies.
synchronization
5.5.1 Prerequisites
Before configuring this task, you have: Enabled IPv6 function Configured BGP4+ basic functions
5.5.2 Configuring BGP4+ Preference and Default LOCAL_PREF and NEXT_HOP Attributes
To do so, use the following commands: To do Enter system view Enter BGP view Enter IPv6 address family view Use the command system-view bgp as-number ipv6-family Required Remarks
To do Configure preference values for BGP4+ external, internal, local routes Configure the default value for local preference
Use the command preference { external-preference internal-preference local-preference | route-policy route-policy-name } default local-preference value Optional
Remarks
The default preference values of external, internal and local routes are 255, 255, 130 respectively Optional The value defaults to 100 Optional
Advertise routes to a peer/peer group with the local router as the next hop
| }
By default, the feature is available for routes advertised to the EBGP peer/peer group, but not available to the IBGP peer/peer group
Note: To make sure an IBGP peer can find the correct next hop, you can configure routes advertised to the peer to use the local router as the next hop. If BGP load balancing is configured, the local router sets the next hop of outbound routes for a peer/peer group to itself regardless of whether the peer next-hop-local command is configured. In a special networking environment of third-party next hop (that is, a broadcast network with two BGP4+ peers connected to the same network segment), by default, the router does not use its own address as the next hop when advertising routes to EBGP peers/peer groups; the router uses its own address as the next hop only after the peer next-hop-local command is used.
To do Enable to compare MED values of routes from different EBGP peers Prioritize MED values of routes from each AS Prioritize MED values of routes from confederation peers
Remarks Optional Not enabled by default Optional Not configured by default Optional Not configured by default
1)
BGP4+ timers
After establishing a BGP4+ connection, two routers send keepalive messages periodically to each other to keep the connection. If a router receives no keepalive message from the peer after the holdtime elapses, it tears down the connection. When establishing a BGP4+ connection, the two parties compare their holdtime values, taking the shorter one as the common holdtime. If the holdtime is 0, neither keepalive massage is sent, nor holdtime is checked. 2) BGP4+ connection soft reset
After modifying a route selection policy, you have to reset BGP4+ connections to make the new one take effect, causing a short time disconnection. The current BGP4+ implementation supports the route-refresh feature that enables dynamic BGP4+ routing table refresh without needing to disconnect BGP4+ links. With this feature enabled on all BGP4+ routers in a network, when a routing policy modified on a router, the router advertises a route-refresh message to its peers, which then send their routing information back to the router. Therefore, the local router can perform dynamic routing information update and apply the new policy without tearing down connections. If a router not supporting route-refresh exists in the network, you need to configure the peer keep-all-routes command on the router to save all route updates, and then use the refresh bgp ipv6 command to soft-reset BGP4+ connections.
5.6.1 Prerequisites
Before configuring BGP4+ timers, you have: Enabled IPv6 function Configured BGP4+ basic functions
To do Specify keepalive interval and holdtime Configure BGP4+ timers Configure keepalive interval and holdtime for a peer/peer group
Remarks
Optional The keepalive interval defaults to 60 seconds, holdtime defaults to 180 seconds.
Optional Configure the interval for sending the same update to a peer/peer group peer { ipv6-group-name | ipv6-address } route-update-interval seconds The interval for sending the same update to an IBGP peer or an EBGP peer defaults to 15 seconds or 30 seconds
Note: Timers configured using the timer command have lower priority than timers configured using the peer timer command. The holdtime interval must be at least three times the keepalive interval.
Required
Note: If the peer keep-all-routes command is used, all routes from the peer/peer group will be saved regardless of whether filtering policy available. These routes will be used to generate BGP4+ routes after soft-reset is performed.
5.7.1 Prerequisites
Before configuring BGP4+ peer group, you have: Made peer nodes accessible at network layer Enabled BGP and configured router ID.
To do Enter IPv6 address family view Create an IBGP peer group Add a peer into the group
Use the command ipv6-family group ipv6-group-name [ internal ] peer ipv6-address group ipv6-group-name [ as-number as-number ]
Remarks
Note: To create a pure EBGP peer group, you need to specify the AS number for the peer group. If a peer was added into an EBGP peer group, you cannot specify any AS number for the peer group.
Note: When creating a mixed EBGP peer group, you need to create a peer and specify its AS number that can be different from AS numbers of other peers, but you cannot specify any AS number for the EBGP peer group.
Note: When configuring BGP4+ community, you need to configure a routing policy to define the community attribute, and apply the routing policy to route advertisement. For routing policy configuration, refer to Chapter 6 Routing Policy Configuration .
reflector cluster-id
cluster-id
Note: In general, it is not required to make clients of a router reflector fully meshed. The router reflector forwards routing information between clients. If clients are fully meshed, you can disable route reflection between clients to reduce metrics. If a cluster has multiple router reflectors, you need to specify the same cluster ID for these router reflectors to avoid routing loops.
peer
display bgp ipv6 peer [ ipv6-address { log-info | verbose } | ipv6-group-name log-info | verbose ] display bgp ipv6 routing-table [ ipv6-address prefix-length ] display bgp ipv6 routing-table as-path-acl as-path-acl-number display bgp ipv6 routing-table community [ aa:nn<1-13> ] [ no-advertise | no-export | no-export-subconfed ]* [ whole-match ] display bgp ipv6 routing-table community-list { basic-community-list-number [ whole-match ] | adv-community-list-number }&<1-16> display bgp dampened ipv6 routing-table
Display BGP4+ routing table information Display routing information matched by a AS path ACL Display community information BGP4+ routing
Display routing information matched by a BGP4+ community list Display dampened information BGP4+ routing
routing-table
Remarks
flap
display bgp ipv6 routing-table flap-info [ regular-expression as-regular-expression | as-path-acl as-path-acl-number | network-address [ prefix-length [ longer-match ] ] ] display bgp ipv6 routing-table peer ipv6-address { advertised-routes | received-routes } [ network-address prefix-length | statistic ] display bgp ipv6 regular-expression as-regular-expression display statistic bgp ipv6 routing-table
Display routing information sent to/received from a peer Display information by a expression routing matched regular
routing-table
Use the command reset bgp ipv6 flap-info [ ipv6-address/prefix-length | regexp as-path-regexp | as-path-acl as-path-acl-number ]
Remarks
Note: Some BGP4+ configuration examples are similar to those of BGP4, so refer to BGP Configuration in IPv4 Routing for related information.
Vlan-interface401 8::1/64
Vlan-interface300 9:3::2/64
Vlan-interface200 9:2::1/64
Vlan-interface400 10::2/64
SwitchC
Vlan-interface300 9:3::1/64 Vlan-interface200 9:2::2/64
SwitchA
Vlan-interface400 10::1/64
AS 65008
AS 65009
SwitchD
# Configure Switch B.
<SwitchB> system-view
[SwitchB-bgp-af-ipv6] peer 9:1::2 as-number 65009 [SwitchB-bgp-af-ipv6] peer 9:3::2 as-number 65009 [SwitchB-bgp-af-ipv6] quit [SwitchB-bgp] quit
# Configure Switch C.
<SwitchC> system-view [SwitchC] ipv6 [SwitchC] bgp 65009 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] ipv6-family [SwitchC-bgp-af-ipv6] peer 9:3::1 as-number 65009 [SwitchC-bgp-af-ipv6] peer 9:2::2 as-number 65009 [SwitchC-bgp-af-ipv6] quit [SwitchC-bgp] quit
# Configure Switch D.
<SwitchD> system-view [SwitchD] ipv6 [SwitchD] bgp 65009 [SwitchD-bgp] router-id 4.4.4.4 [SwitchD-bgp] ipv6-family [SwitchD-bgp-af-ipv6] peer 9:1::1 as-number 65009 [SwitchD-bgp-af-ipv6] peer 9:2::1 as-number 65009 [SwitchD-bgp-af-ipv6] quit [SwitchD-bgp] quit
3)
# Configure Switch A.
<SwitchA> system-view [SwitchA] ipv6 [SwitchA] bgp 65008 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] ipv6-family [SwitchA-bgp-af-ipv6] peer 10::1 as-number 65009 [SwitchA-bgp-af-ipv6] quit [SwitchA-bgp] quit
# Configure Switch B.
[SwitchB] bgp 65009
BGP local router ID : 2.2.2.2 Local AS number : 65009 Total number of peers : 3 Peers in established state : 3
Peer
AS
MsgRcvd
MsgSent
State
3 2 2
3 3 4
0 0 0
BGP local router ID : 3.3.3.3 Local AS number : 65009 Total number of peers : 2 Peers in established state : 2
Peer
AS
MsgRcvd
MsgSent
State
9:3::1 9:2::2
4 65009 4 65009
4 4
4 5
0 0
Switch A and B established an EBGP connection; Switch B, C and D established IBGP connections with each other.
SwitchB
AS200
SwitchD
# Configure Switch A.
<SwitchA> system-view [SwitchA] ipv6 [SwitchA] bgp 100 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] ipv6-family [SwitchA-bgp-af-ipv6] peer 100::2 as-number 200 [SwitchA-bgp-af-ipv6] network 1:: 64 [SwitchA-bgp-af-ipv6] quit
#Configure Switch B.
<SwitchB> system-view [SwitchB] ipv6 [SwitchB] bgp 200 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] ipv6-family [SwitchB-bgp-af-ipv6] peer 100::1 as-number 100 [SwitchB-bgp-af-ipv6] peer 101::1 as-number 200
# Configure Switch C.
<SwitchC> system-view [SwitchC] ipv6 [SwitchC] bgp 200 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] ipv6-family [SwitchC-bgp-af-ipv6] peer 101::2 as-number 200 [SwitchC-bgp-af-ipv6] peer 102::2 as-number 200
# Configure Switch D.
<SwitchD> system-view [SwitchD] ipv6 [SwitchD] bgp 200 [SwitchD-bgp] router-id 4.4.4.4 [SwitchD-bgp] ipv6-family [SwitchD-bgp-af-ipv6] peer 102::1 as-number 200
3)
Use the display bgp ipv6 routing-table command on Switch B and Switch D respectively, you can find both of them have learned the network 1::/64.
II. Analysis
To become BGP4+ peers, any two routers need to establish a TCP session using port 179 and exchange open messages successfully.
Note: Verify that the system already operates in IPv4/IPv6 dual-stack mode before configuring IPv6 routing policy. All the IPv6 routing policy related configuration mentioned in this manual assumes that the system already operates in IPv4/IPv6 dual-stack mode. For dual stack mode configuration, see the part covering dual stack in the IPv6 Configuration module.
A routing policy is used on the router for route inspection, filtering, attributes modifying when routes are received, advertised, or redistributed.
6.1.2 Filters
Routing protocols can use five filters: ACL, IP prefix list, AS path, community-list and route policy.
I. ACL
When defining an ACL, you can specify IP addresses and prefixes for matching destinations or next hops of routing information.
V. Routing policy
A routing policy is used for matching some attributes in given routing information and modifying the attributes of the information if matching conditions are satisfied. A routing policy can utilize the above filters to define its own matching rules. A routing policy can comprise multiple nodes, which are in logic OR relationship. Each node is a matching unit, and the system checks nodes in the order of node sequence number. Once the matching test of a node is passed, the route-policy is passed without needing to match other nodes. Each node comprises a set of if-match and apply clauses. The if-match clauses define the matching rules. The matching objects are some attributes of routing information. The different if-match clauses on the same node is in logic AND relationship. Only when the matching conditions specified by all the if-match clauses on a node are satisfied, can routing information passes the matching test of the node. The apply clauses specify the actions performed after the node matching test passed, concerning the attribute settings for the routing information.
IPv6
Note: If all items are set to the deny mode, no route can pass the IPv6 prefix list. It is recommended to define the permit :: 0 less-equal 128 item following multiple deny mode items to allow other IPv6 routing information to pass.
For example, the following configuration filters routes 2000:1::/48, 2000:2::/48 and 2000:3::/48, but allows other routes to pass.
[Sysname] ip ipv6-prefix abc index 10 deny 2000:1:: 48 [Sysname] ip ipv6-prefix abc index 20 deny 2000:2:: 48 [Sysname] ip ipv6-prefix abc index 30 deny 2000:3:: 48 [Sysname] ip ipv6-prefix abc index 40 permit :: 0 less-equal 128
A routing policy can comprise multiple nodes, each node contains: if-match clauses: define the matching rules routing information must satisfy. The matching objects are some attributes of routing information. apply clauses: specifies the actions performed after specified matching rules satisfied, concerning attribute settings for passed routing information.
6.3.1 Prerequisites
Before configuring this task, you have completed: Filtering list configuration Routing protocol configuration You also need to decide on: Name of routing policy, node sequence numbers Matching rules Attributes to be modified
Note: If a node is specified as permit, routing information meeting the nodes conditions will be handled using the apply clauses of this node, without needing to match the next node. If routing information does not meet the nodes conditions, it will go to the next node for matching. If a node is specified as deny, the apply clauses of the node will not be executed. When routing information meets all if-match clauses, it cannot pass the node, nor can it go to the next node. If route information cannot meet any if-match clause of the node, it will go to the next node for matching. When a routing policy is defined with more than one node, at least one node should be configured using the permit keyword. If the routing policy is used to filter routing information, routing information that does not meet any nodes conditions cannot pass the routing policy. If all nodes of the routing policy are set using the deny keyword, no routing information can pass it.
Set conditions to match IPv6 routing information Set conditions to match AS path field of BGP4+ routing information Match community attribute of BGP4+ routing information
Optional Not configured default Optional Not configured default Optional Not configured default Optional Not configured default Optional Not configured default by by by by by
of
if-match interface { interface-type interface-number }&<1-16> if-match route-type { internal | external-type1 | external-type2 | external-type1or2 | is-is-level-1 | is-is-level-2 | nssa-external-type1 | nssa-external-type2 | nssa-external-type1or2 }* if-match tag value
Configure the matching condition for the tag field of the routing information
Note: The if-match clauses of a route-policy are in logic AND relationship, namely, routing information has to satisfy all if-match clauses before executed with apply clauses. You can specify no or multiple if-match clauses for a routing policy. If no if-match clause is specified, and the routing policy is in permit mode, all routing information can pass the node, or in deny mode, no routing information can pass.
apply community { none | additive | { community-number&<1-16> | aa:nn&<1-16> | no-export-subconfed | no-export | no-advertise }* [ additive ] } apply cost [ + | - ] value apply cost-type { external | internal | type-1 | type-2 } apply ipv6 ipv6-address next-hop
Set the cost of routing information Set the cost type of routing information Set the next hop for IPv6 routing information Redistribute routes to a specified ISIS level
Optional Not set by default Optional Not set by default Optional Not set by default Optional Not configured by default
To do Set the local preference of BGP4+ routing information Set origin attributes of BGP4+ routing information Set routing protocol preference Set the preferred value of BGP routing information Set the tag field of routing information
Remarks Optional Not set by default Optional Not set by default Optional Not set by default Optional Not set by default Optional Not set by default
apply origin { igp | egp as-number | incomplete } apply preference preference apply preferred-value preferred-value apply tag value
Note: The apply ipv6 next-hop commands do not apply to redistributed IPv6 routes.
Figure 6-1 Network diagram for routing policy application to route redistribution
[SwitchA-route-policy] if-match ipv6 address prefix-list a [SwitchA-route-policy] quit [SwitchA] route-policy static2ripng permit node 10 [SwitchA-route-policy] quit
2)
Configure Switch B.
# Enable RIPng.
[SwitchB] ripng
on Vlan-interface 100
via FE80::7D58:0:CA03:1, cost Dest 20::/32, via FE80::7D58:0:CA03:1, cost Dest 40::/32, via FE80::7D58:0:CA03:1, cost
1, tag 0, A, 18 Sec
1, tag 0, A, 8 Sec
1, tag 0, A, 3 Sec
II. Analysis
At least one item of the IPv6 prefix list should be configured as permit mode, and at least one node of the Route-policy should be configured as permit mode.
Huawei Technologies Proprietary 6-10