Shulou(Shulou.com)06/01 Report--

[note] BGP comprehensive experiment is the classroom experiment of teacher Ande in Qianyitang, which is organized by myself.

Initial configuration:

All devices are configured with interface IP addresses

All device ring return addresses are xx.1.1.1/ 32 bits

EBGP experiment: [participating equipment: R1/R2/R4/R5]

On R1, check the value range of BGP AS number and state the value range of public AS number and private AS number.

On R1, set up the BGP process using AsDot mode and verify the AS number

Cancel the display of AsDot through the command. Verify the AS number by comparing with the above results

Undo the above operation. Open the debug program on R2

R1 and R2 establish eBGP through a directly connected interface. View BGP messages and close debug

Loopback declared on R1 and R2, respectively. On R2, view the neighbor table, database, routing table, and TCP status of BGP.

Tell me what the front "I" and the following "I" represent in BGP's database.

Describe the benefits of using loopback to build an EBGP:

On R4 and R5, establish EBGP through loopback, and pay attention to using two methods to solve multiple problems of ebgp.

On R1 and R5, shut down the e0ap0 interface

On R5, declare the loop return

IBGP experiment: [participating equipment: R3/R4/R5]

On R2\ R3\ R4, declare adjacent interfaces and loops, and establish an IGP relationship

On R2 and R4, only use the remote and update source commands to establish IBGP neighbors with each other

On R2 and R4, first look at the next-hop address on R4 for the route to 11.1.1.1Universe 32. Then use the next-hop-self command to verify the next-hop address replacement process

Detect the node location of the routing black hole

On R2, detect who is going to 55.1.1.1, the next hop in the routing table and the next hop in the physical connection

Solution to routing black hole 1:

On R2, redistribute the BGP into the EIGRP (filtering is needed in practice). Check the EIGRP database of R2 and the routing table of R3 to verify that all BGP are redistributed successfully. If not, why?

Revoke the EBGP relationship between R4 and R5 and change it to establish EBPG through a directly connected interface

On R4, test connectivity after redistributing BGP into EIGRP

On R4, undo the redistribution operation above

On R2, resolve the issue of redistributing all BGP into EIGRP. Conduct connectivity evaluation, if not explain the reason for the solution to the routing black hole 2:

Undo the operation of option one

Adopt "Full mesh"

Talk about the anti-ring mechanism of EBGP and IBGP

BGP related configuration: [participating device: R1/R2/R4/R5]

On R1, temporarily close the neighbor relationship with R2 before resuming

4 possible situations of neighbor status "Idle"? How do I activate an address family?

4 possible situations of neighbor status "active"?

On R1 and R2, turn on BGP authentication and restore

Describe the optimization conditions of BGP in MA network.

On R4, revoke the neighbor relationship with R2 and R3, and then establish the neighbor through the Peer-group method

On R4, revoke the Peer-group neighbor above, and then establish the neighbor through the BGP dynamic neighbor method. Observe two items in the BGP database

On R4, network a route learned from IGP-33.1.1.1. View how this route is represented in the BGP database of R4

On R2, it fails to see which BGP route is placed in the routing table. Check the details and explain why

On R2, see which routes are passed to 33.1.1.1

On R3, see which routes have been received from 22.1.1.1

On R4, the undo "Article 8" operation no dropped 33.1.1.1

On R4, undo the Article 7 operation, no and peer-group, and rebuild the IBGP neighbor

BGP routing reflector: [participating device: R2/R3R/R4]

On R3, establish RR relationships with R2 and R4

Temporarily close the adjacency between R2 and R4

Name the three roles of RR. The rule of saying that the way out depends on the reflector

View Originator ID and Cluster-list. And two kinds of anti-ring principles are given.

BGP aggregation: [participating device: R1/R2/R3/R4]

Undo the operation of the BGP routing reflector. Restore the topology diagram to the full mesh state

Automatic summarization:

On R4, establish a static route to 172.16.0. Candle 16 with the next hop empty, and redistribute the static in BGP.

Toggle automatic rollup on and off on R4 and verify the status of 172.16.0.0 on R3 or R5

Summary of non-proprietary commands (1): summary through static rout

Add two more loopback lo1 and lo2 on R1.

Establish a static route on R2 to the R1 loopback summary, and announce the R1 loopback summary into the R2 BGP process.

On R3, to test the connectivity to the R1 loop, the R3 loop needs to be notified to establish the back path.

On R1, Down drops any of the detail routes. On R3, detail routes lost by traceroute, observe the result

The significance of summarizing the route pointing to the null interface

On R2, cancel the static route to R1. Undo the summary of R1 loops declared in the BGP process of R2

On R1, establish a static route to the loop backport summary, pointing to null0. And advertise the loop loop summary into the BGP process

On R3, to test the connectivity to the R1 loop, the R3 loop needs to be notified to establish the back path.

On R1, Down drops any of the detail routes. On R3, the detail routes lost by traceroute are compared with the results above

Summary of non-proprietary commands (2): summary through IGP

On R4, in the EIGRP process, summarize a route for 44.1.0.0swap 16. Verify how this summary route is represented in the local routing table

On R3, view the routing table of R3 to verify this summary route. And verified in the BGP database of R3

BGP proprietary aggregation command (1): detailed routing and aggregation on the same device

On R1, undo the static route summarized to and from the loop. Undo the loop rebate summary declared in BGP

On R4, undo the redistributed static in BGP

On R1, announce 11.1.1.2 and 11.1.1.3 into BGP

On R1, the loop loop routes are summarized without any parameters. Verify summary and detail routes in the BGP database

On R1, the loop return routes are summarized and only the summary routes are displayed. View the BGP databases on R1 and R2 to verify suppressed routes

On R1, by suppressing the list, only two routes, 11.1.1.0 and 11.1.1.2, are retained.

BGP proprietary aggregation command (2): detailed routing and summarization on different devices

On R1, undo aggregations, summarize only, and suppress lists

On R2, aggregate the loop return summary of R1 and add the "Summary only" parameter. Validate in the BGP database

When you say aggregation, why configure the AS-set property

On R1, view the atomic collection of summary routes

On R2, aggregate the loopback summary of R1, adding the "AS-set" and "summary only" parameters. Then verify the atomic aggregation attribute of the summary route on R2

On R1, check to see if any aggregation routes exist and why?

BGP default route: [participating device: R1/R2/R5]

On R5, establish a default route using an empty interface. Verify on R1

Retain the above experimental results. On R1, implement a default route for R2. Verify on R1 and R2, respectively

There will be two default routes on R2 in different directions. Test for loops and explain why

BGP conditional announcement: [participating device: R4/R5]

On R5, a conditional declaration of existence is used for neighbor R4: the requirement is that 55.1.1.1 can only be announced when 5.5.5.5 is declared. Once configured, verify on the required device.

Make changes based on the above experiments and use a conditional declaration that does not exist: the requirement is 55.1.1.1 can only be announced when 5.5.5.5 is not declared. Once configured, verify on the required device.

Remove private AS number

Name the range of private AS numbers

On R5, no changes bgp 300 to 64512 and establishes an EBGP relationship with R4

On R5, advertise the loop return route and verify the AS-path on R5

Requirement 1: remove private AS on R2 and R4, enter the command to remove private AS, and verify on R1

Requirement 2: on R2, use your own AS instead of the number of the removed AS. And verify on R1

Requirement 3: on R2, create a spoofed AS500 and re-establish an EBGP relationship with R1. And verify on R1

BGP Federation: [participating device: R1/R2/R3/R4/R5]

On R2, no drops AS200 on R2, establishes AS20, and belongs to AS200. Establish a federal EBGP neighbor relationship with AS21. Announce 22.1.1.1 Loop return Route

On R3, no drops AS200 on R3, establishes AS21, and belongs to AS200. Establish a federal EBGP relationship with AS20 and an IBGP relationship with R4

On R4, no drops AS200 on R4, establishes AS21, and belongs to AS200. Establish IBGP relationship with R3

Re-establish the EBGP relationship between R1 and R2 and announce the loopback of R1

The re-established EBGP relationship between R4 and R5 announces the loop return of R5

BGP Community attribute

State the concept and function of group attributes, and when to use group attributes

State the meaning of group attributes of no-export, no-advertise and local-as

What is the difference between declaring a route and establishing a neighbor when using community attributes

Requirement 1: on R1, declare 11.1.1.1 but not propagate to neighbors through the "no-advertise" community attribute

Requirement 2: undo the declaration in requirement 1. On R1, call route-map in the outbound direction for neighbor 12.1.1.2Acue 24. Make 11.1.1.1 pass only to R2 and not to R3

Requirement 3: use the "no-export" attribute, based on the above test results, so that 11.1.1.1 this route propagates only in IBGP, not from R4 to R5. Verify on R4 and R5

Requirement 4: use the "AS-path" attribute on R1 so that 11.1.1.1 this route is not propagated to EBGP neighbor R2. Verify on R1 and R2

Requirement 5: apply the AS_Path attribute value for neighbor 12.1.1.2: in which AS range will R2 update this route? AS200 or AS20?

Undo the route-map used when declaring loopback on R1, and only declare loopback. On R1, call route-map when establishing a neighbor with R2

Requirement 6: use Community-list,R1 to establish an EBGP relationship with R5. By changing the weight value, 55.1.1.1 on R5 will be passed to R1 via 15.1.1.5.

On R1, establish custom community attributes. Because the community attribute is passed to R2, on R2, use the command to switch the display form to verify the difference in the display result.

Directly connected to establish EBGP neighbors between R1 and R5

On R5, propagate the community attribute to R1.

On R5, declare a loop return and call route-map COM

On R5, create a route-map COM and establish a community attribute 300PUR 10

On R1, create ip community-list 10 and match the community attribute 300PUR 10

On R1, create a router-map Weight and match ip community-list 10

On R1, establish an adjacency with 15.1.1.5 and call router-map Weight

On R1, create an empty route-map

On R1, verify the result

BGP routing principle

Describe the 13 routing principles of BGP

Topology changes:

Initialize the topology diagram and set R2 and R5 to RR,R3 and R4 as clients for R2 and R5. R1, directly connected to R2 and R5 to establish EBGP.

On R1, announce 11.1.1.1Universe 11.1.2Universe 11.1.1.3 three loops

Weight-weight valu

Name the characteristics of Weight: is Cisco private? Does it make sense only locally? What is the default value, how to determine priority, and what is the locally generated weight value? How much did the neighbors learn? Can I update between neighbors?

Verify the BGP database on R3 and R4 and state which rule the current routing principle follows

On R3, set the weight value to 10 for neighbor 55.1.1.1 and verify it on R1

Undo the above operation. On R4, set the weight of 11.1.1.2 route to 10 through route-map for neighbor 22.1.1.1, so that when you go to 11.1.1.2, take another path and verify

Local Preference-Local priority

Undo the operation of weight above

State the scope of notification of Local Preference, the main role of Local Preference, the difference from MED, and whether the choice of ASBR will be propagated in EBGP and federal EBGP, what is the default value, and how to determine priority

Undo the operation of Weight above

On R5, grab 11.1.1.2 Universe 32 via route-map. Route-map is applied in the outgoing direction and incoming direction respectively, and verified on R3 and related routers respectively. Tell the difference between the two methods, which is better, and why?

Force the method of changing the local-preference

Local origin attribute

Undo the operation of Local Preference above

What is the meaning of the attribute of local origin? Three forms of local routing? The meaning of the preceding "I" in BGP database

33.1.1.1 is advertised on both R2 and R3

Through route-map on R3, change the locally advertised weight value of 33.1.1.1 to 0 to ensure that the weight value and LoaclPerence value of the two paths to 33.1.1.1 are the same in R3.

Verify "Local Origin first" on R3

AS_Path attribute

Based on the above experiment, on R1, change the AS_Path by grabbing the route of 33.1.1.1 through route-map, so that the next hop to 33.1.1.1 is 12.1.1.2

Verify on R1

Use commands to prevent BGP from following AS_Path routing principles

Origin origin code

State the meaning of the latter "I" in the BGP database.

I > E >?

MED

What is the meaning of MED? How are MED values inherited? Does MED affect EBGP or IBGP? How to determine the priority?

On R1, grab 11.1.1.1 and 11.1.1.3 routes through route-map and change their MED value to 12

On R1, use route-map to establish an adjacency with R2

On R2, verify the results

Use the command to make MED compare when the AS-Path is different

Metric value

How to view the metrics in the BGP database

On R3, change the Metrics value through the offset list to affect routing

Load balancing: on R3, enabling the load balancing attribute gives priority to those with the longest EBGP survival time.

On R1, view the BGP setup time

The routing principle of how to use commands to skip survival time

Routing for minimum router-ID: how to view RID

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.