- 1358 Reviews
Generate a default route
Route-map test permit 20
Address-family ipv6 neighbor 184.108.40.206 activate
Interface Serial0/0 ipv6 enable
Port-channel Ethernet Channel of interfaces
Router(config-rtr)# distance x
Offset-list 1 out 1 serial 0/0
IPv6 is enabled, link-local address is FE80::CE00:DFF:FE48:0 Global unicast address(es):
Complete the construction of the environment and the basic configuration of the device to ensure the interconnection of the entire network.
Ipv6 access-list v4map permit 2001:1::/64 2001:2::/96 ipv6 nat prefix 2001:2::/96 v4-mapped v4map
2. Pass the RIP update with an unnumbered address ( invalid source )
Requested node multicast address corresponding to each unicast and anycast address used
Ipv6 ospf 1 area 0
GRE tunnels also need to manually specify the destination of the tunnel at both ends of the tunnel.
Check the VPNv6 prefix 2001:5555::5 on PE1 . You can see that the out label is 403. It is obvious that R4 is the label assigned by PE2 . This label is actually the label of VPNv6 . In order for PE2 to know, this data belongs to VRF . You can also use the following command to view
!! ipv4 routing, so that the route can access the tunnel destination , which is 10.1.23.3
Ip address 220.127.116.11 255.255.255.0
For example, if you go to a destination and there may be multiple equal-cost paths, you may actually use one of them when forwarding data. Use this command to see which interface is actually used for traffic forwarding.
A tool used to control routing updates can only filter routing information and cannot filter LSAs .
Ip name-server 2012::2 ip domain-lookup
Neighbor 18.104.22.168 update-source Loopback0
R2 re-advertises the A route, then according to the preemptive rule, R3 will ignore the R1 update about the A route. At the same time, due to the deployment of two-way re-release, R3 will further re-publish the learned A- route back to process 1 .
Into, both are indispensable, such as 192.168.1.0/24 and 192.168.1.0/25 , although the network numbers of both are the same, both are 192.168.1.0 , but the two are definitely two different routes, two different Routing prefixes because their prefix lengths are not the same.
Interface Serial0/0 ipv6 enable
R4 released the RIP route of 22.214.171.124/24 , which can be learned by both ASBRs . The solution is to configure static summary routes on the two ASBRs :
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP U - Per-user Static route
The configuration of R4 is as follows:
Ipv6 unicast-routing interface Serial0/0 encapsulation frame-relay
Use the DHCP PD feature. On R2 , this test is valid locally as a PD identifier.
The command distribute-list out works only on the routes being redistributed by the Autonomous System Boundary Routers (ASBRs) into OSPF. It can be applied to external type 2 and external type 1 routes, but not to intra-area and interarea routes.
When a node starts the IPv6 protocol stack, each interface of the node automatically configures a link-local address. This mechanism allows two IPv6 nodes connected to the same link to communicate without any configuration. The default gateway recommends using a link-local address because this address is the most stable.
PE1 , P , and PE2 form an LDP neighbor relationship and deliver IGP labels.
EIGRP , BGP and other dynamic routes learned.
Dialer Dialer interface
LSP Seq Num
!! GW has no other configuration about routing
Note that the Linklocal address here : FE80::5EFE:202:202 is an ISATAP format address, the last 64bits are
After being injected into EIGRP , the tag is still carried.
Of R4 redistribute incoming IPv6 prefix summarize, reduce routing entries
Complete basic IP configuration
Verify the role of the match interface 2
CE1 The IPv6 routing to put PE1 , PE1 created on IPv6 in the VRF ,ccna preparation, the Fa0 / 0 Kou into the VRF . PE1 learned through BGP
Ipv6 ospf 1 area 2
Network 10.1.23.2 0.0.0.0 area 0
Label associated with the VPNV6 prefix:
Address family identifier. When the value is 2 , it indicates the IP protocol.
R1 release A network routing, R3 will learn this OSPF routing; Additionally, R2 also learned, assuming R2 deploy OSPF to RIP routes redistributed, which eventually route R3 will pass RIP also learned, then R3 will At the same time , the route is learned from RIP and OSPF . R3 will optimize the OSPF route. Because OSPF has a small AD , OSPF re-releases it to RIP without causing a suboptimal path problem.