CCIE Topic: 1.3c EIGRP Operations

Поділитися
Вставка
  • Опубліковано 23 гру 2024

КОМЕНТАРІ • 7

  • @sukhminderpal2465
    @sukhminderpal2465 4 роки тому +1

    Thanks Charles
    Well explained

  • @santasmooth6804
    @santasmooth6804 Рік тому

    Great video Charles. Am I right in thinking you had some other device physically between R1 and R2, perhaps a layer 2 Switch? Just wondering why disabling G0/0 on R1 didn't cause R2 to immediately remove R1 as a neighbor based on the link down status which should also have occurred on R2 G0/0?

  • @michaeldanquah9309
    @michaeldanquah9309 4 роки тому

    Very good one there Charles, keep them coming.

    • @AdventuresOfPepper
      @AdventuresOfPepper 4 роки тому

      Thats Real Talk Michael, Never heard of you before UA-cam recommended you but dang! You're content is pretty dang good Sir.

  • @ciscolive4062
    @ciscolive4062 4 роки тому

    very good video Charles .
    Do you think it is a good idea to desable the time limit or increase it before an outstanding query is stuck in active
    by the command "timers active-time [time-limit | disabled] "??

    • @CharlesJudd
      @CharlesJudd  4 роки тому

      This will certainly prevent stuck-in-active states, but a better solution proposed by Cisco is to limit the scope of our query messages. By limiting the number of devices able to respond to a query, this will greatly reduce the response time required to receive all of the replies, because this limits the number of hops for query messages. Two methods for this would be configuring route summarization and using EIGRP stub routers.

    • @ciscolive4062
      @ciscolive4062 4 роки тому +1

      @@CharlesJudd Thanks charles.