↑ Retornar para CCNP

EIGRP sobre L2L

Home Fórum CCNP EIGRP sobre L2L

Este tópico contém respostas, possui 4 vozes e foi atualizado pela última vez por  rgentil 5 anos, 2 meses atrás.

Visualizando 8 posts - 1 até 8 (de 8 do total)
  • Autor
    Posts
  • #48606

    AlanXT
    Participante

    Boa tarde amigos, poderia me ajudar com uma duvida de um colega de trabalho?

    Estou com um problema onde meu protocolo EIGRP não fecha conectividade com a ponta remota, o link sai do meu roteador e entra em um link L2L de uma provedora distinta eu tenho conectividade fim a fim sem perda de pacotes porém o protocolo fica no ar por exatamente 1min20segs e depois cai.

    essas sao as msgs de log:
    May 7 09:32:41.297: %DUAL-5-NBRCHANGE: EIGRP-IPv4 53063: Neighbor 172.16.42.1 (Vlan542) is up: new adjacency
    May 7 09:34:00.930: %DUAL-5-NBRCHANGE: EIGRP-IPv4 53063: Neighbor 172.16.42.1 (Vlan542) is down: retry limit exceeded
    May 7 09:34:01.702: %DUAL-5-NBRCHANGE: EIGRP-IPv4 53063: Neighbor 172.16.42.1 (Vlan542) is up: new adjacency
    May 7 09:35:21.344: %DUAL-5-NBRCHANGE: EIGRP-IPv4 53063: Neighbor 172.16.42.1 (Vlan542) is down: retry limit exceeded
    May 7 09:35:24.582: %DUAL-5-NBRCHANGE: EIGRP-IPv4 53063: Neighbor 172.16.42.1 (Vlan542) is up: new adjacency
    172.16.42.1
    172.16.42.1

    tenho o mesmo cenário no mesmo equipamento porém usando um link diferente, e neste link funciona, alguma ideia do que possar ser?

    0

    0
    #114106

    rvsouza
    Participante

    Estou com o mesmo problema, o eigrp estabelece conexão fim a fim, através de um Lan to Lan, não perde pacotes, não existem drops, erros.
    Eu acredito que seja algo na operadora, porém o que poderia estar impactando a adjacencia do EIGRP, Algum Queue in queue configurado incorretamente? Se fosse isso, eu acredito que eu não teria conectividade layer 3.
    Agradeço se puderem me ajudar também.

    0

    0
    #114107

    rgentil
    Participante

    Voce alterou os timers do eigrp ?
    default hello eh 5 segundos para LAN e 3x esse valor o hold timer.
    Em frame-relay, x25, atm, t1, os hellos sao geralmente 60 segundos e o hold timer 3x esse valor.

    Geralmente quando o erro eh “retry limit exceeded” eh porque o router consegue receber o hello, consegue enviar,porem a outra ponta nao recebe o hello enviado.
    Isso geralmente acontece em links unidirecionais. Se vc alterar a rede de forma que o link fique bidirecional o problema pode ser resolvido.

    voce pode tentar usar o comando: debug eigrp packets hello , vc consegue ver se esta recebendo e enviando hellos normalmente.

    0

    0
    #114108

    zekkerj
    Participante

    O temporizador de hello parece estar ajustado para 1m20s (80s), nesse caso vc tem que ajustar o hold-down para 3x isso, ou 240s (4min). Mas vale conversar com o responsável da outra ponta pra confirmar isso.

    0

    0

    -----------------------------------------------------------------------------
    Receba Johrei e purifique seu Espírito.
    http://www.messianica.org.br/o-johrei.jsp

    #114109

    rvsouza
    Participante

    Caros,

    Realizei alguns debugs,
    Vejam abaixo se pode ajudar a localizar a causa raiz do problema;

    EIGRP-IPv4 Interfaces for AS(53063)
    Xmit Queue Mean Pacing Time Multicast Pending
    Interface Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes
    Vl541 1 0/0 342 0/1 2072 0
    Hello-interval is 5, Hold-time is 15
    Split-horizon is enabled
    Next xmit serial
    Un/reliable mcasts: 0/11394 Un/reliable ucasts: 12802/2776
    Mcast exceptions: 58 CR packets: 58 ACKs suppressed: 20
    Retransmissions sent: 170 Out-of-sequence rcvd: 595
    Topology-ids on interface – 0

    Vl542 1 0/0 0 0/1 80 133
    Hello-interval is 5, Hold-time is 15
    Split-horizon is enabled
    Next xmit serial 1
    Un/reliable mcasts: 0/10409 Un/reliable ucasts: 11981/32793
    Mcast exceptions: 54 CR packets: 54 ACKs suppressed: 70
    Retransmissions sent: 28399 Out-of-sequence rcvd: 493
    Topology-ids on interface – 0

    May 13 10:34:24.744: Building unicast STARTUP packet for 172.16.42.1, serno 0-0 for tid 0
    May 13 10:34:24.744: No items in range
    May 13 10:34:24.744: EIGRP: Sending UPDATE on Vlan542 nbr 172.16.42.1, retry 15, RTO 5000 tid 0
    May 13 10:34:24.744: AS 53063, Flags 0x1:(INIT), Seq 28716/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/1
    May 13 10:34:24.819: EIGRP: Sending HELLO on Vlan542
    May 13 10:34:24.819: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
    May 13 10:34:24.844: EIGRP: received packet with MD5 authentication, key id = 1
    May 13 10:34:24.844: EIGRP: Received HELLO on Vlan542 nbr 172.16.42.1
    May 13 10:34:24.844: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/1
    May 13 10:34:27.009: EIGRP: Sending HELLO on Vlan541
    May 13 10:34:27.009: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
    May 13 10:34:28.460: EIGRP: received packet with MD5 authentication, key id = 1
    May 13 10:34:28.460: EIGRP: Received HELLO on Vlan541 nbr 172.16.41.1
    May 13 10:34:28.460: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0
    May 13 10:34:29.559: EIGRP: received packet with MD5 authentication, key id = 1
    May 13 10:34:29.559: EIGRP: Received HELLO on Vlan542 nbr 172.16.42.1
    May 13 10:34:29.559: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/1
    May 13 10:34:29.727: EIGRP: Sending HELLO on Vlan542
    May 13 10:34:29.727: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
    May 13 10:34:29.752: Building unicast STARTUP packet for 172.16.42.1, serno 0-0 for tid 0
    May 13 10:34:29.752: No items in range
    May 13 10:34:29.752: EIGRP: Sending UPDATE on Vlan542 nbr 172.16.42.1, retry 16, RTO 5000 tid 0
    May 13 10:34:29.752: AS 53063, Flags 0x1:(INIT), Seq 28716/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/1
    May 13 10:34:31.899: EIGRP: Sending HELLO on Vlan541
    May 13 10:34:31.899: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
    May 13 10:34:33.040: EIGRP: received packet with MD5 authentication, key id = 1
    May 13 10:34:33.040: EIGRP: Received HELLO on Vlan541 nbr 172.16.41.1
    May 13 10:34:33.040: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0
    May 13 10:34:33.996: EIGRP: received packet with MD5 authentication, key id = 1
    May 13 10:34:33.996: EIGRP: Received HELLO on Vlan542 nbr 172.16.42.1
    May 13 10:34:33.996: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/1
    May 13 10:34:34.458: EIGRP: Sending HELLO on Vlan542
    May 13 10:34:34.458: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
    May 13 10:34:34.760: EIGRP: Retransmission retry limit exceeded
    May 13 10:34:34.760: EIGRP: Sending HELLO on Vlan542
    May 13 10:34:34.760: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
    May 13 10:34:34.768: EIGRP: Holdtime expired
    May 13 10:34:34.768: %DUAL-5-NBRCHANGE: EIGRP-IPv4 53063: Neighbor 172.16.42.1 (Vlan542) is down: retry limit exceeded
    May 13 10:34:34.768: Going down: Peer 172.16.42.1 total=1 stub 0, iidb-stub=0 iid-all=0
    May 13 10:34:34.768: Peer 172.16.42.1 going down
    May 13 10:34:34.768: EIGRP: Handle deallocation failure [1]
    May 13 10:34:34.768: Freeing 0-0, refcount 1 from peer queue
    May 13 10:34:34.768: Startup update acked from 172.16.42.1, serno 0-0
    May 13 10:34:34.768: IIDB anchored. Startup target serno 1, tid 0
    May 13 10:34:34.768: Packets pending on Vlan542 tid 0
    May 13 10:34:34.768: Interface not flow-ready
    May 13 10:34:34.768: EIGRP: Neighbor 172.16.42.1 went down on Vlan542
    May 13 10:34:34.768: Last peer deleted from Vlan542
    May 13 10:34:34.785: Packetizing timer expired on Vlan542
    May 13 10:34:36.681: EIGRP: Sending HELLO on Vlan541
    May 13 10:34:36.681: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
    May 13 10:34:37.327: EIGRP: received packet with MD5 authentication, key id = 1
    May 13 10:34:37.327: EIGRP: Received HELLO on Vlan541 nbr 172.16.41.1
    May 13 10:34:37.327: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0
    May 13 10:34:38.694: EIGRP: received packet with MD5 authentication, key id = 1
    May 13 10:34:38.694: EIGRP: Received HELLO on Vlan542 nbr 172.16.42.1
    May 13 10:34:38.694: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0
    May 13 10:34:38.702: First peer: startup anchor at serno 1, target serno 157444
    May 13 10:34:38.702: EIGRP: New peer 172.16.42.1
    May 13 10:34:38.702: %DUAL-5-NBRCHANGE: EIGRP-IPv4 53063: Neighbor 172.16.42.1 (Vlan542) is up: new adjacency
    May 13 10:34:38.702: EIGRP: Enqueueing UPDATE on Vlan542 nbr 172.16.42.1 tid 0 iidbQ un/rely 0/1 peerQ un/rely 0/0
    May 13 10:34:38.711: EIGRP: Sending TIDLIST on Vlan542 – 1 items
    May 13 10:34:38.711: EIGRP: Sending HELLO on Vlan542
    May 13 10:34:38.711: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/1
    May 13 10:34:38.711: EIGRP: Requeued unicast on Vlan542
    May 13 10:34:38.719: Building unicast STARTUP packet for 172.16.42.1, serno 0-0 for tid 0
    May 13 10:34:38.719: No items in range
    May 13 10:34:38.719: EIGRP: Sending UPDATE on Vlan542 nbr 172.16.42.1 tid 0
    May 13 10:34:38.719: AS 53063, Flags 0x1:(INIT), Seq 28717/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/1
    May 13 10:34:40.724: Building unicast STARTUP packet for 172.16.42.1, serno 0-0 for tid 0
    May 13 10:34:40.724: No items in range
    May 13 10:34:40.724: EIGRP: Sending UPDATE on Vlan542 nbr 172.16.42.1, retry 1, RTO 3000 tid 0
    May 13 10:34:40.724: AS 53063, Flags 0x1:(INIT), Seq 28717/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/1
    May 13 10:34:41.446: EIGRP: Sending HELLO on Vlan541
    May 13 10:34:41.446: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
    May 13 10:34:42.033: EIGRP: received packet with MD5 authentication, key id = 1
    May 13 10:34:42.033: EIGRP: Received HELLO on Vlan541 nbr 172.16.41.1
    May 13 10:34:42.033: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0
    May 13 10:34:43.174: EIGRP: Sending TIDLIST on Vlan542 – 1 items
    May 13 10:34:43.174: EIGRP: Sending HELLO on Vlan542
    May 13 10:34:43.174: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
    May 13 10:34:43.585: EIGRP: received packet with MD5 authentication, key id = 1
    May 13 10:34:43.585: EIGRP: Received HELLO on Vlan542 nbr 172.16.42.1
    May 13 10:34:43.585: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/1
    May 13 10:34:43.727: Building unicast STARTUP packet for 172.16.42.1, serno 0-0 for tid 0
    May 13 10:34:43.727: No items in range
    May 13 10:34:43.727: EIGRP: Sending UPDATE on Vlan542 nbr 172.16.42.1, retry 2, RTO 4500 tid 0
    May 13 10:34:43.727: AS 53063, Flags 0x1:(INIT), Seq 28717/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/1
    May 13 10:34:45.875: EIGRP: Sending HELLO on Vlan541
    May 13 10:34:45.875: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
    May 13 10:34:46.647: EIGRP: received packet with MD5 authentication, key id = 1
    May 13 10:34:46.655: EIGRP: Received HELLO on Vlan541 nbr 172.16.41.1
    May 13 10:34:46.655: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0
    May 13 10:34:47.494: EIGRP: Sending TIDLIST on Vlan542 – 1 items
    May 13 10:34:47.494: EIGRP: Sending HELLO on Vlan542
    May 13 10:34:47.494: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
    May 13 10:34:48.064: EIGRP: received packet with MD5 authentication, key id = 1
    May 13 10:34:48.064: EIGRP: Received HELLO on Vlan542 nbr 172.16.42.1
    May 13 10:34:48.064: AS 53063, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/1
    May 13 10:34:48.232: Building unicast STARTUP packet for 172.16.42.1, serno 0-0 for tid 0
    May 13 10:34:48.232: No items in range
    May 13 10:34:48.232: EIGRP: Sending UPDATE on Vlan542 nbr 172.16.42.1, retry 3, RTO 5000 tid 0
    May 13 10:34:48.232: AS 53063, Flags 0x1:(INIT), Seq 28717/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/1

    0

    0
    #114110

    rgentil
    Participante

    Cara pelos logs parece que ele esta recebendo hello e enviando normalmente…..
    Voce fez os mesmos debugs do outro lado pra ver se acha algo ?

    Como esta sua topo ? Router1 -interface fa0/0


    switches


    int fa0/0 –Router2 ? Basicamente isso ?

    0

    0
    #114111

    zekkerj
    Participante

    Observei que os Hellos recebidos parecem estar marcados com autenticação MD5. Já verificou se as chaves de autenticação estão válidas?

    0

    0

    -----------------------------------------------------------------------------
    Receba Johrei e purifique seu Espírito.
    http://www.messianica.org.br/o-johrei.jsp

    #114112

    rgentil
    Participante

    Verifique as senhas de authenticacao, mas se tivesse alguem mismatch ia sair nesse debug e nao ia nem formar adjacencia……

    0

    0
Visualizando 8 posts - 1 até 8 (de 8 do total)

Você deve fazer login para responder a este tópico.