Strange EIGRP messages filling logging buffer on router

Answered Question
Jun 25th, 2009

I noticed this morning that our WAN router is receiving these EIGRP messages constantly in the log buffer and filling them.

I am not sure why these are constantly rolling. Any input would be welcome:


521285: Jun 25 10:34:28.479: EIGRP: Sending HELLO on GigabitEthernet0/0

521286: Jun 25 10:34:28.479: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

521287: Jun 25 10:34:31.103: EIGRP: Received HELLO on GigabitEthernet0/0 nbr 192.168.15.4

521288: Jun 25 10:34:31.103: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

521289: Jun 25 10:34:31.143: EIGRP: Received HELLO on GigabitEthernet0/0 nbr 192.168.15.5

521290: Jun 25 10:34:31.143: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

521291: Jun 25 10:34:32.911: EIGRP: Sending HELLO on GigabitEthernet0/0

521292: Jun 25 10:34:32.911: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

521293: Jun 25 10:34:35.651: EIGRP: Received HELLO on GigabitEthernet0/0 nbr 192.168.15.5

521294: Jun 25 10:34:35.651: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

521295: Jun 25 10:34:35.727: EIGRP: Received HELLO on GigabitEthernet0/0 nbr 192.168.15.4

521296: Jun 25 10:34:35.727: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

521297: Jun 25 10:34:37.543: EIGRP: Sending HELLO on GigabitEthernet0/0

521298: Jun 25 10:34:37.543: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

521299: Jun 25 10:34:39.967: EIGRP: Received HELLO on GigabitEthernet0/0 nbr 192.168.15.5

521300: Jun 25 10:34:39.967: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

521301: Jun 25 10:34:40.595: EIGRP: Received HELLO on GigabitEthernet0/0 nbr 192.168.15.4

521302: Jun 25 10:34:40.595: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

521303: Jun 25 10:34:42.523: EIGRP: Sending HELLO on GigabitEthernet0/0

521304: Jun 25 10:34:42.523: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

521305: Jun 25 10:34:44.411: EIGRP: Received HELLO on GigabitEthernet0/0 nbr 192.168.15.5

521306: Jun 25 10:34:44.411: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

521307: Jun 25 10:34:44.907: EIGRP: Received HELLO on GigabitEthernet0/0 nbr 192.168.15.4

521308: Jun 25 10:34:44.907: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

521309: Jun 25 10:34:47.387: EIGRP: Sending HELLO on GigabitEthernet0/0

521310: Jun 25 10:34:47.387: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

521311: Jun 25 10:34:48.839: EIGRP: Received HELLO on GigabitEthernet0/0 nbr 192.168.15.5

521312: Jun 25 10:34:48.839: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

521313: Jun 25 10:34:49.863: EIGRP: Received HELLO on GigabitEthernet0/0 nbr 192.168.15.4

521314: Jun 25 10:34:49.863: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

521315: Jun 25 10:34:51.927: EIGRP: Sending HELLO on GigabitEthernet0/0

521316: Jun 25 10:34:51.927: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

521317: Jun 25 10:34:53.343: EIGRP: Received HELLO on GigabitEthernet0/0 nbr 192.168.15.5

521318: Jun 25 10:34:53.343: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

521319: Jun 25 10:34:54.367: EIGRP: Received HELLO on GigabitEthernet0/0 nbr 192.168.15.4

521320: Jun 25 10:34:54.367: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

521321: Jun 25 10:34:56.239: EIGRP: Sending HELLO on GigabitEthernet0/0

521322: Jun 25 10:34:56.239: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

521323: Jun 25 10:34:57.615: EIGRP: Received HELLO on GigabitEthernet0/0 nbr 192.168.15.5

521324: Jun 25 10:34:57.615: AS 13, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

GAMPLSRTR01#


Thanks

Correct Answer by Collin Clark about 7 years 8 months ago

Looks like a debug. Verify debugging is off with 'u all'.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Collin Clark Thu, 06/25/2009 - 07:15

Looks like a debug. Verify debugging is off with 'u all'.


Actions

This Discussion