Konfigurasi lab sabtu

Hari sabtu ini merupakan hari terakhir untuk bootcamp ini di cisarua. Hari terakhir ini kami diminta oleh pak dedi gunawan untuk mengerjakan tshoot dan lab seperti layaknya ujian.

Jadi ada 2 jam untuk troubleshoot dan 7 jam untuk lab konfigurasi.

Topologi tshoot :

Berikut soal tshoot nya :

Ticket 1:
R22 can not establish OSPF neighbor with R23 , fix the problem so that OSPF neighbor is up

Ticket 2:
R16 can not telnet host 10.1.1.19 (r19 loopback ) with source loopback 0

Ticket 3:
R17 and R18 can not synchronize ntp from R16

Ticket 4:
get nat tarns output on r22 as given below
Pro Inside global          Inside local       Outside local      Outside global
tcp 172.29.7.12:21474    10.1.1.20:21474    100.10.10.10:23    100.10.10.10:23
tcp 172.29.7.11:43476   10.1.1.20:43476    100.10.10.10:80    100.10.10.10:80

Ticket 5 :
All the PE routers must see the other Pe routers loopback 0 in show ip bgp table with two entries.

Ticket 6 :
Fix the problem so that VPN Site-B can ping each others

Ticket 7 :
Fix the problem so that VPN Site-A can ping each others

Ticket 8 :
10.1.1.4 is a NMS ,ensure if R16 interface s0/0 goes down , R16 still can use loopback send snmp to trap link status

Ticket 9 :
Ensure R20 loopback interface 200.20.20.20 can ping 198.168.14.1 and 198.168.20.1

Ticket 10 :
Ensure R8 can ping R4 loopback 200 CC1E:1000:100::100  without configuring any routing rotocol  or static route on r8

Ticket 11 :
ensure r14 can telnet 10.1.1.8 with source loopback 0

Ticket 12 :
Traffic which mark precedence 4 from r11/r12 to r7/r8 need to be change to precedence 5

Ticket 13 :
R11, R12 should take the path R9-R7-R8 to R8 use pbr

Ticket 14 :
DOS attack to R20 lo add 200 ( 200.20.20.20)

Setelah tshoot maka kami juga harus mengerjakan mock lab nya dimana di session ini berlangsung selama lebih kurang 7 jam.

Untuk topologi yang harus kami kerjakan dan soal lab nya ada sbb :

Topologi lab konfigurasi :

Sedangkan soal lab nya :

soal lab

Troubleshooting Lab jumat dan kamis malam

Hari kamis sore semua pelajaran bab demi bab yang sy pelajari dari hari pertama bootcamp CCIE RS ini selesai juga. Mulai kamis malam sy dan rekans-rekans seperjuangan akan mulai melakukan lab secara keseluruhan, jadi bukan hanya frame relay saja atau bgp saja, tapi merupakan gabungan dari keseluruhan pelajaran mengenai CCIE ini.

Untuk kamis malam sy terlebih dahulu mengerjakan troubleshoot, yaitu mencari letak kesalahan dari sebuah konfigurasi dan memperbaikinya. Di ujian real CCIE, ujian ini memakan waktu selama 2 jam, dimana kita harus mengerjakan beberapa soal (tiket), dan harus selesai dalam waktu 2 jam dengan ambang batas nilai, yaitu 80%.

Apabila kita mengambil ujian CCIE RS, dan dalam 2 jam pertama kita merasa ga bisa menyelesaikan 80 % soal, maka kita daripada kita buang-buang waktu mengerjakan lab konfigurasi berikutnya. Kita tinggal datang ke proctor (penilai) dan ngomong, “hi sir, i think i have to go to disneyland, because i have booked the ticket” . 😀

Hal ini lebih baik dilakukan daripada meneruskan lebih kurang 7 jam sia-sia untuk lab konfigurasi.

• Troubleshooting kamis malam :

soal :

Ticket 1:
There is an issue that prevents R25 to ping R22, Check the issue and provide a solution
to this issue

Ticket 2 :
R22 is NTP Server and R23, R24 NTP Client, but R23 and R24 cannot get right time
from R22.. Check the problem and provide a solution to this problem.

Ticket 3 :
R15 cannot establish OSPF neighborship with R16. Check the problem and provide a solution to this problem.

Ticket 4 :
R18 cannot establish OSPF neighborship with R17. Check the problem and provide a
solution to this problem

Ticket 5 : R20 can not ping the routes in R21 RIP process. Check the problem and provide a solution to this problem.

Ticket 6 :
R9 and R10 want to access R11 go though R8>>R7>>R11, but it is going through R8>>R11,
Check the problem and provide a solution to this problem.

Ticket 7 :
The link between R22 and R3 is PPP and this link have enabled PPP authentication. The link is down, Check the problem and provide a solution to this problem

Ticket 8 :
R4 try to ping R5 With extended parameters with a size of 500 bytes and ip precedence of 5, but ping is not working. Check the problem and provide a solution to this problem.

Ticket 9 :
R22 and R15 are CEs, they learn the routes through MPLS VPN, but they can not ping MPLS VPN routes. Check the problem and provide a solution to this problem.

Ticket 10 :
R7 CE can not ping R15 CE routes, Check the problem and provide a solution to this problem.

Ticket 11 :
R14 can not ping R7, Check the problem and provide a solution to this problem.

Ticket 12 :
On R12 one policy map is configured with ip precedence 1 but we need this policy map to be match ip precedence 5. so make this configuration. Change and check if it working or not.

Ticket 13 :
R5 try to ping R4 with extended parameters with a packet size of 46 byte but ping is not working. Check the problem and provide solution to this problem.

Solusi

1.  masalah DHCP , perbesar network range dalam pool di DHCP server
2. timezone nya tidak sama
3. Masalah di Frame Relay Switch
4. masalah di Frame relay switch
5. Masalah di Frame relay switch
6. tambahkan OSPF cost

• Troubleshooting Jumat 1

Soal  :
Ticket 1:
The link between R27 and R8 is not in use. Configure your network to ensure that PC from AS300 connection to router 27 need to access the AS100, the traffic should goes over the link from Router R27 to Router R8. use only one command

Ticket2:
Router R7 can not establish ssh connection to router R8 using port 2009 with user cisco and password ccie.

Ticket 3:
The traffic stream from host 10.1.24.1 to host 10.1.1.4 is not receiving critical precedence. Fix the problem so that the stream is marked with the precedence of priority in EIGRP 200, marked with the precedence of network in OSPF area 2 and precedence of critical in OSPF area 0, area 1.

Ticket 4:
On R30, there is a multicast group 224.2.1.1, join into loopbak0, but router 17 can not ping 224.2.1.1.

Ticket 5:
The traffic from R21 to R24 should load balance across link between R22 and R23 .

Ticket 6:
R4 and R6 cant establish OSPF neighborship. Fix the problem.

Ticket 7:
The link between R25 and R24 is not working.

Ticket 8:
R13 and R15 cant establish ospf neighbor.

Ticket 9
R14 is not sending SNMP messages to SNMP server 172.14.14.14 when serial interface status become up or down, fix this problem so that the SNMP message can be sent to the server. send trap message.

Ticket 10:
PC connected to R1 cant ping R4, fix this problem

Ticket 11:
After R2 telnet to R1 with user cisco and password ccie, you can use the show run and config terminal command.

Ticket 12:
Enable Authentication for R8 and R29 with one command.

Ticket 13:
There is a server with ip 1.100.100.100 connect to R18, but can not find this network on R27.
Fix this problem

Ticket 14
R1 and R2 cannot access R4 .

Ticket 15:
R25 cannot receive 10.1.24.1

• Troubleshooting Jumat-2

Soal :
Ticket1.
R22 can not establish ospf neighbor with R23, Fix this problem so that the OSPF-neighbor relationship is up.

Ticket2.
The eigrp relationship between R17 and R19, R18 and R19 are down, fix this problem and ensure the eigrp neighbor relationship is up.

Ticket3.
R17 and R18 cannot synchronize time with NTP server R16, fix this problem so that R17 and R18 can synchronize and authenticate with the NTP server.

Ticket4.
R24 can not reach host 198.168.14.1, fix this problem so that R24 can access it.

Ticket5.
The traffic stream from host 10.1.1.14 to host 10.1.1.7 is not receiving precedence critical, fix this problem so that the traffic stream is marked with precedence critical.

Ticket6
A stream of ICMP packet of 46 bytes each which are sourced from R5 to R4 E0/1 is currently resulting in a 97% success rate, fix this problem so that the ICMP is 100% succeed.

Ticket 7.
Host 10.1.1.11 and host 10.1.1.12 can not go to R8 with path R9-R7-R8, fix this problem and make sure the traffic go through R9-R7-R8.

Ticket 8
The host 171.1.1.1 in VPN site-b can not reach host 171.2.2.2 in VPN site-a, fix this problem so that those two hosts can access each other.

Ticket9.
R15 and R16 can not establish eigrp-neighbor, fix this problem without removing authentication.

Ticket10.
R16 has been getting DoS attacks from R18 and R17 find a way to fix the problem so R16 is protected from DOS attacks

Ticket11
fix a problem between R19 and R16 EIGRP

Ticket12
problem between R14 and R7 with telnet

Ticket13
Pc 171.2.2.2 can not ping 192.168.20.1 in RIP.