Commit failure on routed after adding next hop attribute in BGP-aggregate route.

Commit failure on routed after adding next hop attribute in BGP-aggregate route.

9592
Created On 02/05/19 03:14 AM - Last Modified 02/20/19 16:05 PM


Symptom


  • After adding next hop attribute in BGP-aggregate route, commit fails  
  • When viewing the system log, the following error message "Route daemon configuration load phase-2 failed" is shown in the image
show log system output


Environment


  • PAN-OS


Cause


Phase 2 commit failure for the routed process 

Resolution


 Restart the routed process fixes this commit failed error
> debug software restart process routed
Note: Restarting routed causes all the routes in the routing table to be cleared and is impacting to production traffic
Maintenance window recommended


Additional Information


To verify if routed process successfully restarts, check the pid (process id number) is different before and after running the software restart command

Before restart:
> show system software status

Slot 1, Role mp
----------------------------------------

Type     Name                 State    Info
...
Process  rasmgr               running  (pid: 6929)
Process  routed               running  (pid: 6940)

After restart:
admin@Lab196-118-PA-VM1> show system software status

Slot 1, Role mp
----------------------------------------

Type     Name                 State    Info
...
Process  rasmgr               running  (pid: 6929)
Process  routed               running  (pid: 18733)

 


Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Cmk2CAC&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail