•  
  • 0 items - R$0.00
  •  
Entendendo RIP com um Comando !!!

Entendendo RIP com um Comando !!!

Bom Dia Pessoal

Neste artigo a ideia é demonstrar um segredo que utilizo quando preciso aprender algo e memorizar pra sempre, pois acredito que este seja um dos grandes diferenciais quando ensinamos algo, explicar de forma que seja fixado. Legal então vamos falar sobre RIP, sabemos que RIP é um protocolo legado e que não se utiliza mais em larga escala, porem para efeito de exames ainda é um tópico válido, então temos que aprender. Estamos cansado de saber o conceito básico do RIP, que envia atualizações periodicamente, nesta atualização enviamos toda tabela de roteamento, depois de X tempo se não recebemos tal atualização descartamos a entrada da tabela de roteamento, porem como isto funciona na prática???

Quero demonstrar pra vocês que podemos aprender RIP via um, e somente um comando, ou seja, se aprendemos o comando que vou descrever abaixo, aprendemos 90% do RIP, o resto é praticamente detalhe, mas que comando é este? segue:

timers basic update invalid holddown flush

Este comando explica praticamente 90% do control plane do protocolo RIP, seja RIPv1 ou RIPv2, na verdade RIPv2 é uma melhoria do RIPv1,  vejamos a explicação deste comando:

Este comando tem a finalidade de ajustar de forma global os parâmetros de temporizadores do RIP, e perceba o seguinte RIP não é um protocolo que mantem estados de vizinho de forma direta, ou seja, não estabelece vizinhaça via pacotes hello, é claro que que indiretamente sabemos se um vizinho esta disponível ou não pois temos que receber informações periodicamente, porem na verdade sabemos se uma rota ainda esta disponível e não vizinhos, desta forma o RIP e totalmente projetado em cima destes temporizadores de rota. Vejamos:

timers basic = Comando global aplicado dentro do processo do RIP
update = Em quanto tempo que enviamos as atualizações periódicas do RIP, padrão 30 segundos
invalid = O tempo que será aguardado após receber uma atualização de um rota e inserir na tabela de roteamento e banco de dados do RIP até a próxima atualização, caso este tempo expire e não recebemos NOVAMENTE outra atualização, colocaremos tal rota em holdown. RFC indica 3xupdate = 90 segundos.
holdown – Neste estado o processo RIP não aceita rotas de vizinhos que sejam pior em relação a métrica, ou seja, que tenha um valor de contagem de salto (hop count) maior.
Flush – Tempo total até tal rota ser descartada do banco de dados do RIP e da tabela de roteamento.

Vejamos o Vídeo Abaixo que explica em detalhes o conceito e demonstra na prática

LOGS DO LABORATÓRIO

!
!
09:14:29.125 – RECEBIMENTO DA ROTAS
09:15:12.645:   3.3.3.3/32 via 0.0.0.0, metric 16, tag 0 – INVALID
09:15:38.205 – HOLD DOWN / FLUSH
!
!

!R3
!
do show clock
passive-interface default

NCE-R4#!!!!!!!!!!!PONTO DE PARTIDA !!!!!!!!!!!
NCE-R4#!!!!!!!!!!!PONTO DE PARTIDA !!!!!!!!!!!
NCE-R4#!!!!!!!!!!!PONTO DE PARTIDA !!!!!!!!!!!
NCE-R4#!!!!!!!!!!!PONTO DE PARTIDA !!!!!!!!!!!
NCE-R4#deb
NCE-R4#debug ip ri
NCE-R4#ter
NCE-R4#terminal mon
NCE-R4#deb
NCE-R4#debug ip ri
NCE-R4#debug ip rip
RIP protocol debugging is on

NCE-R4#
NCE-R4#
001546: *Jun 18 09:14:29.125: RIP: received v2 update from 10.3.4.3 on FastEthernet0/0
001547: *Jun 18 09:14:29.125:      3.3.3.3/32 via 0.0.0.0 in 1 hops
001548: *Jun 18 09:14:29.129:      10.1.3.0/24 via 0.0.0.0 in 1 hops
001549: *Jun 18 09:14:29.133:      10.3.6.0/24 via 0.0.0.0 in 1 hops
NCE-R4#
NCE-R4#
NCE-R4#
NCE-R4#
001550: *Jun 18 09:14:35.269: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (10.3.4.4)
001551: *Jun 18 09:14:35.269: RIP: build update entries
001552: *Jun 18 09:14:35.269:   4.4.4.4/32 via 0.0.0.0, metric 1, tag 0
001553: *Jun 18 09:14:35.269:   10.2.4.0/24 via 0.0.0.0, metric 1, tag 0
001554: *Jun 18 09:14:35.269:   10.4.9.0/24 via 0.0.0.0, metric 1, tag 0
NCE-R4#
NCE-R4#
NCE-R4#
001555: *Jun 18 09:14:36.765: RIP: sending v2 update to 224.0.0.9 via FastEthernet1/0 (10.4.9.4)
001556: *Jun 18 09:14:36.765: RIP: build update entries
001557: *Jun 18 09:14:36.765:   3.3.3.3/32 via 0.0.0.0, metric 2, tag 0
001558: *Jun 18 09:14:36.765:   4.4.4.4/32 via 0.0.0.0, metric 1, tag 0
001559: *Jun 18 09:14:36.765:   10.1.3.0/24 via 0.0.0.0, metric 2, tag 0
001560: *Jun 18 09:14:36.765:   10.2.4.0/24 via 0.0.0.0, metric 1, tag 0
001561: *Jun 18 09:14:36.765:   10.3.4.0/24 via 0.0.0.0, metric 1, tag 0
001562: *Jun 18 09:14:36.765:   10.3.6.0/24 via 0.0.0.0, metric 2, tag 0
NCE-R4#show ip route
001563: *Jun 18 09:14:40.965: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/1 (10.2.4.4)
001564: *Jun 18 09:14:40.969: RIP: build update entries
001565: *Jun 18 09:14:40.969:   3.3.3.3/32 via 0.0.0.0, metric 2, tag 0
001566: *Jun 18 09:14:40.969:   4.4.4.4/32 via 0.0.0.0, metric 1, tag 0
001567: *Jun 18 09:14:40.969:   10.1.3.0/24 via 0.0.0.0, metric 2, tag 0
001568: *Jun 18 09:14:40.969:   10.3.4.0/24 via 0.0.0.0, metric 1, tag 0
001569: *Jun 18 09:14:40.969:   10.3.6.0/24 via 0.0.0.0, metric 2, tag 0
001570: *Jun 18 09:14:40.969:   10.4.9.0/24 via 0.0.0.0, metric 1, tag 0
001571: *Jun 18 09:14:41.489: RIP: sending v2 update to 224.0.0.9 via Loopback0 (4.4.4.4)
NCE-R4#show ip route
001572: *Jun 18 09:14:41.493: RIP: build update entries
001573: *Jun 18 09:14:41.497:   3.3.3.3/32 via 0.0.0.0, metric 2, tag 0
001574: *Jun 18 09:14:41.501:   10.1.3.0/24 via 0.0.0.0, metric 2, tag 0
001575: *Jun 18 09:14:41.505:   10.2.4.0/24 via 0.0.0.0, metric 1, tag 0
001576: *Jun 18 09:14:41.505:   10.3.4.0/24 via 0.0.0.0, metric 1, tag 0
001577: *Jun 18 09:14:41.509:   10.3.6.0/24 via 0.0.0.0, metric 2, tag 0
001578: *Jun 18 09:14:41.509:   10.4.9.0/24 via 0.0.0.0, metric 1, tag 0
001579: *Jun 18 09:14:41.509: RIP: ignored v2 packet from 4.4.4.4 (sourced from one of our addresses)
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 1
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:00:19 ago
Routing Descriptor Blocks:
* 10.3.4.3, from 10.3.4.3, 00:00:19 ago, via FastEthernet0/0
Route metric is 1, traffic share count is 1
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 1
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:00:22 ago
Routing Descriptor Blocks:
* 10.3.4.3, from 10.3.4.3, 00:00:22 ago, via FastEthernet0/0
Route metric is 1, traffic share count is 1
NCE-R4#
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 1
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:00:24 ago
Routing Descriptor Blocks:
* 10.3.4.3, from 10.3.4.3, 00:00:24 ago, via FastEthernet0/0
Route metric is 1, traffic share count is 1
NCE-R4#
001580: *Jun 18 09:14:52.481: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (10.3.4.4)
001581: *Jun 18 09:14:52.481: RIP: build update entries
001582: *Jun 18 09:14:52.481:   4.4.4.4/32 via 0.0.0.0, metric 1, tag 0
001583: *Jun 18 09:14:52.481:   10.2.4.0/24 via 0.0.0.0, metric 1, tag 0
001584: *Jun 18 09:14:52.481:   10.4.9.0/24 via 0.0.0.0, metric 1, tag 0
NCE-R4#
001585: *Jun 18 09:14:54.929: RIP: sending v2 update to 224.0.0.9 via FastEthernet1/0 (10.4.9.4)
001586: *Jun 18 09:14:54.933: RIP: build update entries
001587: *Jun 18 09:14:54.937:   3.3.3.3/32 via 0.0.0.0, metric 2, tag 0
001588: *Jun 18 09:14:54.941:   4.4.4.4/32 via 0.0.0.0, metric 1, tag 0
001589: *Jun 18 09:14:54.945:   10.1.3.0/24 via 0.0.0.0, metric 2, tag 0
001590: *Jun 18 09:14:54.949:   10.2.4.0/24 via 0.0.0.0, metric 1, tag 0
001591: *Jun 18 09:14:54.949:   10.3.4.0/24 via 0.0.0.0, metric 1, tag 0
001592: *Jun 18 09:14:54.953:   10.3.6.0/24 via 0.0.0.0, metric 2, tag 0
NCE-R4#
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 1
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:00:30 ago
Routing Descriptor Blocks:
* 10.3.4.3, from 10.3.4.3, 00:00:30 ago, via FastEthernet0/0
Route metric is 1, traffic share count is 1
NCE-R4#
001593: *Jun 18 09:14:58.745: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/1 (10.2.4.4)
001594: *Jun 18 09:14:58.745: RIP: build update entries
001595: *Jun 18 09:14:58.745:   3.3.3.3/32 via 0.0.0.0, metric 2, tag 0
001596: *Jun 18 09:14:58.745:   4.4.4.4/32 via 0.0.0.0, metric 1, tag 0
001597: *Jun 18 09:14:58.745:   10.1.3.0/24 via 0.0.0.0, metric 2, tag 0
001598: *Jun 18 09:14:58.745:   10.3.4.0/24 via 0.0.0.0, metric 1, tag 0
001599: *Jun 18 09:14:58.745:   10.3.6.0/24 via 0.0.0.0, metric 2, tag 0
001600: *Jun 18 09:14:58.745:   10.4.9.0/24 via 0.0.0.0, metric 1, tag 0
NCE-R4#
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 1
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:00:32 ago
Routing Descriptor Blocks:
* 10.3.4.3, from 10.3.4.3, 00:00:32 ago, via FastEthernet0/0
Route metric is 1, traffic share count is 1
NCE-R4#
001601: *Jun 18 09:15:00.689: RIP: sending v2 update to 224.0.0.9 via Loopback0 (4.4.4.4)
001602: *Jun 18 09:15:00.693: RIP: build update entries
001603: *Jun 18 09:15:00.697:   3.3.3.3/32 via 0.0.0.0, metric 2, tag 0
001604: *Jun 18 09:15:00.701:   10.1.3.0/24 via 0.0.0.0, metric 2, tag 0
001605: *Jun 18 09:15:00.701:   10.2.4.0/24 via 0.0.0.0, metric 1, tag 0
001606: *Jun 18 09:15:00.701:   10.3.4.0/24 via 0.0.0.0, metric 1, tag 0
001607: *Jun 18 09:15:00.701:   10.3.6.0/24 via 0.0.0.0, metric 2, tag 0
001608: *Jun 18 09:15:00.701:   10.4.9.0/24 via 0.0.0.0, metric 1, tag 0
001609: *Jun 18 09:15:00.701: RIP: ignored v2 packet from 4.4.4.4 (sourced from one of our addresses)
NCE-R4#
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 1
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:00:37 ago
Routing Descriptor Blocks:
* 10.3.4.3, from 10.3.4.3, 00:00:37 ago, via FastEthernet0/0
Route metric is 1, traffic share count is 1
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:00:42 ago
Hold down timer expires in 59 secs
NCE-R4#
001610: *Jun 18 09:15:09.861: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (10.3.4.4)
001611: *Jun 18 09:15:09.865: RIP: build update entries
001612: *Jun 18 09:15:09.869:   4.4.4.4/32 via 0.0.0.0, metric 1, tag 0
001613: *Jun 18 09:15:09.869:   10.2.4.0/24 via 0.0.0.0, metric 1, tag 0
001614: *Jun 18 09:15:09.869:   10.4.9.0/24 via 0.0.0.0, metric 1, tag 0
NCE-R4#
001615: *Jun 18 09:15:12.637: RIP: sending v2 flash update to 224.0.0.9 via Loopback0 (4.4.4.4)
001616: *Jun 18 09:15:12.641: RIP: build flash update entries
001617: *Jun 18 09:15:12.645:   3.3.3.3/32 via 0.0.0.0, metric 16, tag 0
001618: *Jun 18 09:15:12.649:   10.1.3.0/24 via 0.0.0.0, metric 16, tag 0
001619: *Jun 18 09:15:12.649:   10.3.6.0/24 via 0.0.0.0, metric 16, tag 0
001620: *Jun 18 09:15:12.653: RIP: sending v2 flash update to 224.0.0.9 via FastEthernet0/0 (10.3.4.4)
001621: *Jun 18 09:15:12.653: RIP: build flash update entries
001622: *Jun 18 09:15:12.653:   3.3.3.3/32 via 0.0.0.0, metric 16, tag 0
001623: *Jun 18 09:15:12.653:   10.1.3.0/24 via 0.0.0.0, metric 16, tag 0
001624: *Jun 18 09:15:12.653:   10.3.6.0/24 via 0.0.0.0, metric 16, tag 0
001625: *Jun 18 09:15:12.653: RIP: sending v2 flash update to 224.0.0.9 via FastEthernet0/1 (10.2.4.4)
001626: *Jun 18 09:15:12.653: RIP: build flash update entries
001627: *Jun 18 09:15:12.653:   3.3.3.3/32 via 0.0.0.0, metric 16, tag 0
001628: *Jun 18 09:15:12.657:   10.1.3.0/24 via 0.0.0.0, metric 16, tag 0
001629: *Jun 18 09:15:12.657:   10.3.6.0/24 via 0.0.0.0, metric 16, tag 0
001630: *Jun 18 09:15:12.657: RIP: sending v2 flash update to 224.0.0.9 via FastEthernet1/0 (10.4.9.4)
NCE-R4#
001631: *Jun 18 09:15:12.657: RIP: build flash update entries
001632: *Jun 18 09:15:12.657:   3.3.3.3/32 via 0.0.0.0, metric 16, tag 0
001633: *Jun 18 09:15:12.657:   10.1.3.0/24 via 0.0.0.0, metric 16, tag 0
001634: *Jun 18 09:15:12.657:   10.3.6.0/24 via 0.0.0.0, metric 16, tag 0
001635: *Jun 18 09:15:12.657: RIP: ignored v2 packet from 4.4.4.4 (sourced from one of our addresses)
001636: *Jun 18 09:15:13.253: RIP: sending v2 update to 224.0.0.9 via FastEthernet1/0 (10.4.9.4)
001637: *Jun 18 09:15:13.257: RIP: build update entries
001638: *Jun 18 09:15:13.257:   3.3.3.3/32 via 0.0.0.0, metric 16, tag 0
001639: *Jun 18 09:15:13.257:   4.4.4.4/32 via 0.0.0.0, metric 1, tag 0
NCE-R4#
001640: *Jun 18 09:15:13.257:   10.1.3.0/24 via 0.0.0.0, metric 16, tag 0
001641: *Jun 18 09:15:13.257:   10.2.4.0/24 via 0.0.0.0, metric 1, tag 0
001642: *Jun 18 09:15:13.257:   10.3.4.0/24 via 0.0.0.0, metric 1, tag 0
001643: *Jun 18 09:15:13.257:   10.3.6.0/24 via 0.0.0.0, metric 16, tag 0
NCE-R4#
001644: *Jun 18 09:15:17.105: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/1 (10.2.4.4)
001645: *Jun 18 09:15:17.109: RIP: build update entries
001646: *Jun 18 09:15:17.113:   3.3.3.3/32 via 0.0.0.0, metric 16, tag 0
001647: *Jun 18 09:15:17.117:   4.4.4.4/32 via 0.0.0.0, metric 1, tag 0
001648: *Jun 18 09:15:17.117:   10.1.3.0/24 via 0.0.0.0, metric 16, tag 0
001649: *Jun 18 09:15:17.121:   10.3.4.0/24 via 0.0.0.0, metric 1, tag 0
001650: *Jun 18 09:15:17.121:   10.3.6.0/24 via 0.0.0.0, metric 16, tag 0
001651: *Jun 18 09:15:17.125:   10.4.9.0/24 via 0.0.0.0, metric 1, tag 0
NCE-R4#
001652: *Jun 18 09:15:18.765: RIP: sending v2 update to 224.0.0.9 via Loopback0 (4.4.4.4)
001653: *Jun 18 09:15:18.765: RIP: build update entries
001654: *Jun 18 09:15:18.765:   3.3.3.3/32 via 0.0.0.0, metric 16, tag 0
001655: *Jun 18 09:15:18.765:   10.1.3.0/24 via 0.0.0.0, metric 16, tag 0
001656: *Jun 18 09:15:18.765:   10.2.4.0/24 via 0.0.0.0, metric 1, tag 0
001657: *Jun 18 09:15:18.765:   10.3.4.0/24 via 0.0.0.0, metric 1, tag 0
001658: *Jun 18 09:15:18.765:   10.3.6.0/24 via 0.0.0.0, metric 16, tag 0
001659: *Jun 18 09:15:18.765:   10.4.9.0/24 via 0.0.0.0, metric 1, tag 0
001660: *Jun 18 09:15:18.769: RIP: ignored v2 packet from 4.4.4.4 (sourced from one of our addresses)
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:00:51 ago
Hold down timer expires in 50 secs
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:00:56 ago
Hold down timer expires in 45 secs
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:00:57 ago
Hold down timer expires in 44 secs
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:00:58 ago
Hold down timer expires in 43 secs
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:00:59 ago
Hold down timer expires in 42 secs
NCE-R4#show ip route 3.3.3.3
001661: *Jun 18 09:15:27.009: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (10.3.4.4)
001662: *Jun 18 09:15:27.013: RIP: build update entries
001663: *Jun 18 09:15:27.017:   3.3.3.3/32 via 0.0.0.0, metric 16, tag 0
001664: *Jun 18 09:15:27.021:   4.4.4.4/32 via 0.0.0.0, metric 1, tag 0
001665: *Jun 18 09:15:27.025:   10.1.3.0/24 via 0.0.0.0, metric 16, tag 0
001666: *Jun 18 09:15:27.025:   10.2.4.0/24 via 0.0.0.0, metric 1, tag 0
001667: *Jun 18 09:15:27.029:   10.3.6.0/24 via 0.0.0.0, metric 16, tag 0
001668: *Jun 18 09:15:27.029:   10.4.9.0/24 via 0.0.0.0, metric 1, tag 0
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:01:00 ago
Hold down timer expires in 41 secs
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:01:01 ago
Hold down timer expires in 40 secs
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:01:02 ago
Hold down timer expires in 39 secs
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:01:03 ago
Hold down timer expires in 38 secs
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:01:03 ago
Hold down timer expires in 38 secs
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:01:04 ago
Hold down timer expires in 37 secs
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:01:05 ago
Hold down timer expires in 36 secs
NCE-R4#
001669: *Jun 18 09:15:33.133: RIP: sending v2 update to 224.0.0.9 via FastEthernet1/0 (10.4.9.4)
001670: *Jun 18 09:15:33.137: RIP: build update entries
001671: *Jun 18 09:15:33.141:   3.3.3.3/32 via 0.0.0.0, metric 16, tag 0
001672: *Jun 18 09:15:33.145:   4.4.4.4/32 via 0.0.0.0, metric 1, tag 0
001673: *Jun 18 09:15:33.145:   10.1.3.0/24 via 0.0.0.0, metric 16, tag 0
001674: *Jun 18 09:15:33.145:   10.2.4.0/24 via 0.0.0.0, metric 1, tag 0
001675: *Jun 18 09:15:33.145:   10.3.4.0/24 via 0.0.0.0, metric 1, tag 0
001676: *Jun 18 09:15:33.145:   10.3.6.0/24 via 0.0.0.0, metric 16, tag 0
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:01:06 ago
Hold down timer expires in 35 secs
NCE-R4#
001677: *Jun 18 09:15:34.265: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/1 (10.2.4.4)
001678: *Jun 18 09:15:34.265: RIP: build update entries
001679: *Jun 18 09:15:34.265:   3.3.3.3/32 via 0.0.0.0, metric 16, tag 0
001680: *Jun 18 09:15:34.265:   4.4.4.4/32 via 0.0.0.0, metric 1, tag 0
001681: *Jun 18 09:15:34.265:   10.1.3.0/24 via 0.0.0.0, metric 16, tag 0
001682: *Jun 18 09:15:34.265:   10.3.4.0/24 via 0.0.0.0, metric 1, tag 0
001683: *Jun 18 09:15:34.265:   10.3.6.0/24 via 0.0.0.0, metric 16, tag 0
001684: *Jun 18 09:15:34.265:   10.4.9.0/24 via 0.0.0.0, metric 1, tag 0
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:01:07 ago
Hold down timer expires in 34 secs
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:01:08 ago
Hold down timer expires in 33 secs
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:01:09 ago
Hold down timer expires in 32 secs
NCE-R4#show ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via “rip”, distance 120, metric 4294967295 (inaccessible)
Redistributing via rip
Last update from 10.3.4.3 on FastEthernet0/0, 00:01:10 ago
Hold down timer expires in 31 secs
NCE-R4#
001685: *Jun 18 09:15:38.205: RIP: sending v2 update to 224.0.0.9 via Loopback0 (4.4.4.4)
001686: *Jun 18 09:15:38.205: RIP: build update entries
001687: *Jun 18 09:15:38.205:   3.3.3.3/32 via 0.0.0.0, metric 16, tag 0
001688: *Jun 18 09:15:38.205:   10.1.3.0/24 via 0.0.0.0, metric 16, tag 0
001689: *Jun 18 09:15:38.205:   10.2.4.0/24 via 0.0.0.0, metric 1, tag 0
001690: *Jun 18 09:15:38.205:   10.3.4.0/24 via 0.0.0.0, metric 1, tag 0
001691: *Jun 18 09:15:38.205:   10.3.6.0/24 via 0.0.0.0, metric 16, tag 0
001692: *Jun 18 09:15:38.205:   10.4.9.0/24 via 0.0.0.0, metric 1, tag 0
001693: *Jun 18 09:15:38.205: RIP: ignored v2 packet from 4.4.4.4 (sourced from one of our addresses)
NCE-R4#show ip route 3.3.3.3
% Network not in table
NCE-R4#undeb
NCE-R4#undebug all
NCE-R4#undebug all
All possible debugging has been turned off

Slider - CCNA_SP1

 

About Leandro Almeida - DOUBLE CCIE#29765 (R&S/SP)

Leandro Almeida
MBA (FGV / UCI)
DOUBLE CCIE#29765 (R&S / SP)
CCIP, CCNA

Leandro Almeida é especialista de redes sênior com 12 anos de experiência, Instrutor Sênior e desenvolvedor do Material da NCE Treinamentos, possui duas certificações CCIE, Routing and Switching (2011) e Service Provider (2013) alem das certificações CCIP (2010) e CCNA (2003) e especializações em Data Center DCUFD – Designing Cisco Data Center Unified Fabric e DCUCD -Designing Cisco Data Center Unified Computing.
Leandro também possuir MBA em Gerenciamento de Projetos adquirido pela Universidade de Irvine e FGV (2013). Aprovado no Exame CCIE Data Center Wirtten Exam em 2013 seu próximo foco em certificação é passar no lab do CCIE DC.
Cursos Ministrados: CCDA, CCNA R&S, CCNA SP, CCNA DC, CCNP R&S, CCNP SP, CCNP DC, CCIE R&S, CCIE SP, CCIE DC, DCUFD e DCUCD

Leave a Reply

Your email address will not be published. Required fields are marked *

*