- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
08-22-2019 05:37 PM
Folks,
We have 2 Palo Alto FW and 4 aruba switches in the same area (area 0), we are noticing that the aruba fw is loosing neighbor relationship with the routers every couple of seconds 30-60 seconds. The configuration is very simple, any ideas?
guys i have palo alto and aruba switch in the same area and there neighbor relationshio is bounching. here is the debug any ideas?
Interface address = IP addr 10.16.180.2
2019-06-15T11:16:50.121+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|OSPF link category = 1
2019-06-15T11:16:50.121+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|Is neighbor virtual? = 0
2019-06-15T11:16:50.122+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|FSM input = QOAM_NBR_1WAY_RCVD (11)
2019-06-15T11:16:50.122+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|Old FSM state = AMB_OSPF_NBR_TWO_WAY (4)
2019-06-15T11:16:50.123+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|New FSM state = AMB_OSPF_NBR_INIT (3)
2019-06-15T11:16:50.123+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|FSM action = K (11)
2019-06-15T11:16:50.124+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|Neighbor friend status = 1
2019-06-15T11:16:50.124+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|Number of neighbor events = 321
2019-06-15T11:16:50.125+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|Number of database exchange timeouts = 0
2019-06-15T11:16:50.125+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|(OSPFv2 process Id = 50, VRF Name = default)
2019-06-15T11:16:50.126+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|OSPF 268748800 IP addr 10.16.180.2 i/f idx 0X00000000 Interface FSM has changed state.
2019-06-15T11:16:50.127+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|FSM input = QOAM_IF_NEIGHBOR_CHANGE (5)
2019-06-15T11:16:50.127+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|Old FSM state = AMB_OSPF_IF_OTHER_DESIGNATD_RTR (7)
2019-06-15T11:16:50.128+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|New FSM state = AMB_OSPF_IF_OTHER_DESIGNATD_RTR (7)
2019-06-15T11:16:50.128+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|FSM action = B (2)
2019-06-15T11:16:50.129+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|(OSPFv2 process Id = 50, VRF Name = default)
2019-06-15T11:16:54.684+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|OSPF 268748800 PM is starting a full routing calculation.
2019-06-15T11:16:54.685+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|(OSPFv2 process Id = 50, VRF Name = default)
2019-06-15T11:16:54.691+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|OSPF 268748800 PM has completed a full routing calculation.
2019-06-15T11:16:54.691+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|(OSPFv2 process Id = 50, VRF Name = default)
2019-06-15T11:17:00.104+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|OSPF 268748800 i/f idx 0X01000A78 rtr ID 10.16.2.5 IP addr 10.16.180.6 neighbor FSM has processed an input.
2019-06-15T11:17:00.105+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|FSM input = QOAM_NBR_HELLO_RCVD (0)
2019-06-15T11:17:00.105+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|Old FSM state = AMB_OSPF_NBR_INIT (3)
2019-06-15T11:17:00.106+00:00 hpe-routing[1784]: debug|LOG_INFO|AMM|-|OSPFV2|OSPFV2|New FSM state = AMB_OSPF_NBR_INIT (3)
08-23-2019 02:02 AM
Just to confirm the issue with OSPF between 2 Palo Altos? Is it constantly flapping or sporadically? MTU, packet loss, have you verified all that?
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClEWCA0
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!