Experience in Passing the CCIE R&S Lab Certification Exam at First Try.

I passed the CCIE R&S Lab test on April 6, 2019

After arriving at Beijing West Railway Station, I took the bus all the way to the Huawei Building. Passing a glance, I went to the hotel to stay.

I arrived at 8 o'clock in the morning and said that it was an exam with the gate. The gatekeeper gave a list, let me see which one is my name, let it go in, and then went to the hall to wait. Wait until 8:40, only the teacher shouted, and he saved the package in the automatic locker on the first-floor lobby. The examination room was on the 2nd floor and the teacher took it up.

The seats are all allocated. After sitting, there is a document paper, a blank paper, and a pen on the desktop. The document paper has login information, test system information and personal information of the test computer.

According to the teacher's prompt, log in to the computer, look at the PDF document on the desktop to view the exam notes, then open the exam system through Google Chrome through the desktop shortcut and log in.

After logging into the exam system, there is also an exam description. After reading, wait for the teacher to explain and click to start the exam.

After the exam starts, it will automatically count down, and you can view the exam questions and instructions, which is basically the same as the test video in the group. In the morning, TAC is a remote desktop. After the completion of the process, copy it to the local and compress it. In the afternoon, the local computer is a SecureCRT connection. After copying and pasting the configuration into the folder txt, the folder is compressed and uploaded.

Overall, the afternoon operation was a little bit stuck, not smooth enough. Beijing is now also a double screen.

Morning field: TS+TAC

Telling the truth, when I first started doing TS, there were some small tensions, and it was just a matter of time.

TS test sites: STP, Eth-Trunk, BGP routing, MUX VLAN, MPLS-VPN, Sharm-link, VRRP, OSPFv3, Telnet, MSDP.

Compared with the actual practice, I feel that there are too few mistakes. There are so many points in practice, I feel that the overall troubleshooting, the idea has some floating.

STP:

1, SW2 instance vlan settings are reversed

2, SW2 does not set stp 2 root primary

Eth-Trunk:

1, SW1 has an interface not joined eth-trunk

2. SW2 has an interface that is not added to eth-trunk. The two interfaces that are not added to eth-trunk are different.

BGP routing:

1, SW1 BGP router-id setting error

2. One interface of R1 is not bound to VPN.

3, R1 specifies SW2's peer as setting error

MUX VLAN:

1. In the mux vlan 100 of the switch LSW8, vlan50 is set to group

2. The port mux-vlan enable is not configured on the switch interface.

MPLS-VPN:

1. R4 and R5 are connected to R2 without deleting Mpls ldp.

2. Under the interconnection interface between AR2 and R4 and R5, no Mpls is configured.

3. Loopback 0 of AR9 is lsr-id but has not been announced into ISIS.

Sharm-link:

1. Loopback0 of AR13 is not imported into BGP.

2, AR13 Sharm-link original address configuration is reversed

VRRP:

1. AR10's vrrp vrid 2 virtual address setting error

2. The track of the AR10 vrrp is not set.

3. The AR10 vrrp vrid2 is not configured with authentication.

4. The vrrp vrid 1 of AR11 is configured with preemption time.

5, AR11 vrrp does not set track

6. The vrrp vrid1 of AR11 is not configured with authentication.

OSPFv3:

1, AR18 set the silent-interface

2, Client9 gateway setting error

3, Client10 gateway setting error

4, Client13 gateway settings error

MSDP:

1. The static-rp setting of AR23 is incorrect.

I didn't find this problem at first, the card was here, and then an hour was almost gone, I quickly made the last TS behind, and I was in an hour. Just hurry to write TAC, and finished TAC in nearly 40 minutes. After writing the TAC, I will fold back and continue to investigate.

2. The AR23 is not enabled and configured with IGMP.

Telnet:

1. The AR16 admin user service type is set incorrectly.

2. The AR16 admin level is set incorrectly.

3. Under the user-interface of AR17, the level is set to 1, and the requirement is 0.

TAC:

Loopback 0 of the AR2 and AR29 cannot access the loopback 0 of the AR33. According to the debugging, the Hello times of the AR29 and AR33 are the same. Only the area IDs are inconsistent. However, in the description of the whole question, it is not stated whether AR29 and AR33 are common area types or NSSA area types. When I wrote the problem, I said both things.

About lunch, luxurious yarn. Didn't eat enough, didn't eat enough! The invigilator went to the box lunch in the examination room. Four dishes, less, carrots, bitter melon eggs, green vegetables, braised pork, a bottle of cola... Many people have not finished eating, I have finished eating it because I cherish the good habits of food...

LAB:

LAB2, overall, the latter ones, the teacher said that the lyrics came, cannot remember, is QoS, ssh those. Very few tests.

1, trunk

2, mstp

3, smart-link

4, frame-relay

5, PPP

Pap authentication, R1 is the authenticated end, and R2 is the authentication end.

6, RIPv2

7, OSPF

8, OSPF Availability

9, Area 34

The requirement is that area34 does not introduce other routes, so I configured the stub.

10, routing introduction

When the two-point bidirectional introduction is introduced, the specific requirement is that R2 is preferably accessed via SW2 and configured only on R2. Inconsistent round-trip paths are not considered.

11, BGP

Preferably, the route from BB2 is implemented by a minimum of commands, regardless of the inconsistency of the round-trip path.

12, multicast

13, MPLS VPN

14, QOS flow classification

15, CQB (LLQ)

16, TCP and UDP attack defense

17, DHCP

The exam encountered a question, two-point two-way redistribution, R1 and SW2, the test requirement is R2 preferred SW2 path, you need to configure rip metric in 5 on R2 S2/0/0 interface, then configure PIM, R5 configuration Igmp, asked R2 to learn this multicast route, found that R2 can not learn, and later configured IP RFP-route-static 10.1.2.2 0 10.1.145.1 on R5. I clearly remember the solution of LAB2, I don't need to knock this command. Later, I simply checked it and found that the RIP neighbors of R1 and R2 are gone. I later deleted the rip metric in 5 configured on the R2 interface, and then downed an R2 interface. The RIP neighbors of R2 and R1 were normal. Later, with rip metric in 5, the RIP neighbors of R1 and R2 still did not exist. Then I left it and configured rip metric in 5 and ip RFP-route-static 10.1.2.2 0 10.1.145.1 as the last configuration save submission.