This website uses Cookies. By clicking Accept, you agree to the storing of cookies on your device to enhance your community and translation experience. Read our Privacy Policy.
Click Preferences to customize your cookie settings.
Accept
Reject
Preferences

Eventid eq routed-OSPF-neighbor-down

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Eventid eq routed-OSPF-neighbor-down

Mohammed_Yasin
L4 Transporter

‎04-18-2020 11:45 PM

 

PAN-OS - 8.1.12

 

Want to understand the below Massage and Why it occurs ??

 

>less mp-log routed.log

 

2020-04-15 09:28:05.296 +0400 TM_SPF: start full SPF calculation rid 172.16.80.16
2020-04-15 09:28:05.296 +0400 TM_SPF: Do the full SPF calculation rid 172.16.80.16
2020-04-15 09:28:05.296 +0400 TM_SPF: full routing calculation finished rid 172.16.80.16
67%2020-04-15 09:28:41.421 +0400 TM_SPF: start full SPF calculation rid 172.16.80.16
2020-04-15 09:28:41.421 +0400 TM_SPF: Do the full SPF calculation rid 172.16.80.16
2020-04-15 09:28:41.423 +0400 TM_SPF: full routing calculation finished rid 172.16.80.16
2020-04-15 09:28:42.768 +0400 Received dp HA status 'sw.dha.status' event change
2020-04-15 09:28:42.768 +0400 Received dp HA status 'sw.dha.status' event change
2020-04-15 09:28:42.768 +0400 Received dp HA status 'sw.dha.status' event change
2020-04-15 09:28:42.768 +0400 Received dp HA status 'sw.dha.status' event change
2020-04-15 09:28:42.768 +0400 Received dp HA status 'sw.dha.status' event change
2020-04-15 09:28:42.768 +0400 Received dp HA status 'sw.dha.status' event change
**** AUDIT 0x3e01 - 91 (0000) **** I:01d49552 F:00000002
qodmnmi.c 215 :at 09:28:46, 15 April 2020 (1225940386 ms)
OSPF 1 An adjacency with a neighbor has gone down.
Resources associated with database exchange for this neighbor will be
freed.
Neighbor router ID 172.16.80.12
Neighbor IP address 172.16.80.12
Interface category network interface
Interface neighbor IP addr 172.16.80.12 i/f idx 0X00000000

**** AUDIT 0x3e01 - 210 (0000) **** I:01d49552 F:00000002
qoamnfsa.c 768 :at 09:28:46, 15 April 2020 (1225940388 ms)
OSPF 1 i/f idx 0X00000011 rtr ID 172.16.80.12 IP addr 172.16.80.12 neighbor FSM state has deteriorated.
Interface address = IP addr 172.16.80.16
OSPF link category = 1
Is neighbor virtual? = 0
FSM input = QOAM_NBR_1WAY_RCVD (11)
Old FSM state = AMB_OSPF_NBR_FULL (8)
New FSM state = AMB_OSPF_NBR_INIT (3)
FSM action = K (11)
Neighbor friend status = 1
Number of neighbor events = 7
Number of database exchange timeouts = 0

2020-04-15 09:28:51.178 +0400 TM_SPF: start full SPF calculation rid 172.16.80.16
2020-04-15 09:28:51.178 +0400 TM_SPF: Do the full SPF calculation rid 172.16.80.16
2020-04-15 09:28:51.179 +0400 TM_SPF: full routing calculation finished rid 172.16.80.16
2020-04-15 09:28:54.109 +0400 IFMon: refresh ifstates, server path sw.dev.runtime.
2020-04-15 09:29:13.340 +0400 TM_SPF: start full SPF calculation rid 172.16.80.16
2020-04-15 09:29:13.340 +0400 TM_SPF: Do the full SPF calculation rid 172.16.80.16
2020-04-15 09:29:13.341 +0400 TM_SPF: full routing calculation finished rid 172.16.80.16
2020-04-15 09:29:41.955 +0400 TM_SPF: start full SPF calculation rid 172.16.80.16
2020-04-15 09:29:41.955 +0400 TM_SPF: Do the full SPF calculation rid 172.16.80.16
2020-04-15 09:29:41.956 +0400 TM_SPF: full routing calculation finished rid 172.16.80.16
2020-04-15 09:29:42.768 +0400 Received dp HA status 'sw.dha.status' event change
2020-04-15 09:29:42.768 +0400 Received dp HA status 'sw.dha.status' event change
2020-04-15 09:29:42.768 +0400 Received dp HA status 'sw.dha.status' event change
2020-04-15 09:29:42.768 +0400 Received dp HA status 'sw.dha.status' event change
2020-04-15 09:29:42.769 +0400 Received dp HA status 'sw.dha.status' event change
2020-04-15 09:29:42.769 +0400 Received dp HA status 'sw.dha.status' event change
**** AUDIT 0x0303 - 76 (0000) **** I:01d49696 F:00000002
sckutil.c 1612 :at 09:29:43, 15 April 2020 (1225997979 ms)
Closed a socket
Socket ID = 2577
Socket type = 0X00000003
Socket family = 0X00000002
Socket protocol = 0X000000FA

**** AUDIT 0x3e01 - 215 (0000) **** I:01d496a0 F:00000010
qoamddsc.c 260 :at 09:29:43, 15 April 2020 (1225997982 ms)
DB DESCRIPTION packet received with mismatched interface MTU size 9000 but
it will be accepted because the MtuIgnore MIB option is set to true.
An adjacency may form but it could fail later due to the mismatch.
67%Expected MTU size = 1500
Neighbor router ID = 172.16.80.12
Packet data =
23285202 3919AEDA 06952201 AC100152 AC100152 80003209 8346003C 00060201
AC10500A AC10500A 80011A17 3FDA0024 00062201 AC10500C AC10500C 80011437
BE6E0030 00390201 AC105010 AC105010 8000DE09 D8140024 02F10201 C2AA8784
C2AA8784 800037D9 B24E0030 07042202 AC10015B AC10500C 800031E0 31A30020
00012202 AC10500C AC10500C 800051FD 09BF0020 00390202 AC105010 AC105010
80000001 D8520020 06050205 00000000 AC105010 8000819E 088D0024 00AC8205
0A000000 C2AA8784 800001DE E4F60024 04060205 0A103200 AC10500A 80006CCD
A1930024 04060205 0A103300 AC10500A 80006CCD 969D0024 04060205 >>>>>>

2020-04-15 09:29:46.957 +0400 TM_SPF: start full SPF calculation rid 172.16.80.16
2020-04-15 09:29:46.957 +0400 TM_SPF: Do the full SPF calculation rid 172.16.80.16
2020-04-15 09:29:46.958 +0400 TM_SPF: full routing calculation finished rid 172.16.80.16
2020-04-15 09:29:54.609 +0400 IFMon: refresh ifstates, server path sw.dev.runtime.
2020-04-15 09:29:56.282 +0400 TM_SPF: start full SPF calculation rid 172.16.80.16
2020-04-15 09:29:56.282 +0400 TM_SPF: Do the full SPF calculation rid 172.16.80.16
2020-04-15 09:29:56.282 +0400 TM_SPF: full routing calculation finished rid 172.16.80.16
2020-04-15 09:30:25.112 +0400 TM_SPF: start full SPF calculation rid 172.16.80.16
2020-04-15 09:30:25.112 +0400 TM_SPF: Do the full SPF calculation rid 172.16.80.16
2020-04-15 09:30:25.112 +0400 TM_SPF: full routing calculation finished rid 172.16.80.16
2020-04-15 09:30:37.926 +0400 TM_SPF: start full SPF calculation rid 172.16.80.16
2020-04-15 09:30:37.926 +0400 TM_SPF: Do the full SPF calculation rid 172.16.80.16
2020-04-15 09:30:37.927 +0400 TM_SPF: full routing calculation finished rid 172.16.80.16
**** AUDIT 0x3e01 - 200 (0001) **** I:01d4981c F:00000002
qoamutil.c 278 :at 09:30:41, 15 April 2020 (1226056165 ms)
OSPF 1 Database exchange with an adjacent OSPF neighbor has been completed.
The adjacency with this neighbor is now fully up.
Neighbor router ID 172.16.80.12
Neighbor IP address 172.16.80.12
Interface category network interface
Interface neighbor IP addr 172.16.80.12 i/f idx 0X00000000

2020-04-15 09:30:42.768 +0400 Received dp HA status 'sw.dha.status' event change
2020-04-15 09:30:42.768 +0400 Received dp HA status 'sw.dha.status' event change

3 people had this problem.
0 Likes Likes
1 REPLY 1

kiwi
Community Team Member

‎04-20-2020 05:32 AM

Hi @Mohammed_Yasin ,

 

It looks like your OSPF adjacency flapped.

 

As to why this happened you'll need to do further debugging.

The timeframe allows you to narrow down and check other logs for related events.  Also check the traffic log during the timeframe when this occured.

 

Get the TSF and have it analysed by support.

 

Cheers,

-Kiwi.

 
LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.
  • 5702 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!

LEGAL NOTICES
RESOURCES
Khoros awards 2022
Copyright 2007 - 2024 - Palo Alto Networks