PA500 boot error with message "unable to connect to Sysd" and NIC in dataplane does not worked.

songjixian — Sat, 02 Oct 2021 22:43:53 GMT

The firwall PA500 had a poweroff and boot,and after reboot the PA500 get a error with "Error: sysd_construct_sync_importer(sysd_sync.c:328): sysd_sync_register() failed: (146) Unknown error code
Error: unable to connect to Sysd"

When the device boot finished,the NIC port on dataplane did not power up and did not work.

We could connect PA500 using console or mgmt interface.

In the file brdagent.log, the port does not power up normol, such as blow:

"* PAN BrdAgent (v2.0)
*
2021-04-27 16:35:26.059 +0800 Start time.
2021-04-27 16:35:26.143 +0800 sysd worker[1]: fff60ec210: starting up...
2021-04-27 16:35:26.143 +0800 sysd worker[0]: fff64ec210: starting up...
Version string: 2.1
2021-04-27 16:35:28.197 +0800 Reading cfg.brdagent.dp.module_dir
2021-04-27 16:35:28.199 +0800 Using given module dir /usr/local/lib64/brdagent
2021-04-27 16:35:28.200 +0800 Loading: libports.so...
* -- Peregrine-port Board Support
*
* Revision: 2.1
* Model: PA-500
* Serial: 009401039360
* Mac: 34:e5:ec:54:5a:00
* Mac-Count: 254
*
2021-04-27 16:35:29.578 +0800 MAC initialization: success
2021-04-27 16:35:29.745 +0800 I2C and Uplink MAC initialization: success
2021-04-27 16:35:29.866 +0800 PHY initialization: success
2021-04-27 16:35:29.945 +0800 Port mapping initialization: success
2021-04-27 16:35:29.955 +0800 libports.so done
2021-04-27 16:35:29.955 +0800 Loading: libocteon.so...
2021-04-27 16:35:30.001 +0800 Interface 0: RGMII
2021-04-27 16:35:30.004 +0800 Interface 0: RGMII
2021-04-27 16:35:30.005 +0800 Interface 0: RGMII
2021-04-27 16:35:30.006 +0800 Verifying GMX3 link
2021-04-27 16:35:30.006 +0800 libocteon.so done
2021-04-27 16:46:56.278 +0800 Port 1: Power up
2021-04-27 16:46:56.287 +0800 Port 2: Power up
2021-04-27 16:46:56.297 +0800 Port 3: Power up
2021-04-27 16:46:56.305 +0800 Port 4: Power up
2021-04-27 16:46:56.314 +0800 Port 5: Power up
2021-04-27 16:46:56.321 +0800 Port 6: Power up
2021-04-27 16:46:56.329 +0800 Port 7: Power up
2021-04-27 16:46:56.335 +0800 Port 8: Power up
2021-04-27 16:46:58.296 +0800 Port 5: Up 100Mb/s-full duplex
2021-04-27 16:46:58.299 +0800 Port 5: MAC enabled
2021-04-27 16:46:59.005 +0800 Port 6: Up 1Gb/s-full duplex
2021-04-27 16:46:59.006 +0800 Port 6: MAC enabled
2021-04-27 16:46:59.010 +0800 Port 8: Up 1Gb/s-full duplex
2021-04-27 16:46:59.010 +0800 Port 8: MAC enabled
*
* PAN BrdAgent (v2.0)
*
2021-10-01 10:28:23.454 +0800 Start time.
2021-10-01 10:28:23.641 +0800 sysd worker[1]: fff60ec210: starting up...
2021-10-01 10:28:23.641 +0800 sysd worker[0]: fff64ec210: starting up...
Version string: 2.1
2021-10-01 10:28:25.644 +0800 Reading cfg.brdagent.dp.module_dir
2021-10-01 10:28:25.646 +0800 Using given module dir /usr/local/lib64/brdagent
2021-10-01 10:28:25.647 +0800 Loading: libports.so...
* -- Peregrine-port Board Support
*
* Revision: 2.1
* Model: PA-500
* Serial: 009401039360
* Mac: 34:e5:ec:54:5a:00
* Mac-Count: 254
*
2021-10-01 10:28:26.641 +0800 MAC initialization: success
2021-10-01 10:28:26.829 +0800 I2C and Uplink MAC initialization: success
2021-10-01 10:28:26.949 +0800 PHY initialization: success
2021-10-01 10:28:27.089 +0800 Port mapping initialization: success
2021-10-01 10:28:27.120 +0800 libports.so done
2021-10-01 10:28:27.135 +0800 Loading: libocteon.so...
2021-10-01 10:28:27.168 +0800 Interface 0: RGMII
2021-10-01 10:28:27.171 +0800 Interface 0: RGMII
2021-10-01 10:28:27.171 +0800 Interface 0: RGMII
2021-10-01 10:28:27.172 +0800 Verifying GMX3 link
2021-10-01 10:28:27.172 +0800 libocteon.so done
*
* PAN BrdAgent (v2.0)
*
2021-10-01 12:58:41.471 +0800 Start time.
2021-10-01 12:58:41.610 +0800 sysd worker[1]: fff60ec210: starting up...
2021-10-01 12:58:41.610 +0800 sysd worker[0]: fff64ec210: starting up...
Version string: 2.1
2021-10-01 12:58:43.654 +0800 Reading cfg.brdagent.dp.module_dir
2021-10-01 12:58:43.656 +0800 Using given module dir /usr/local/lib64/brdagent
2021-10-01 12:58:43.657 +0800 Loading: libports.so...
* -- Peregrine-port Board Support
*
* Revision: 2.1
* Model: PA-500
* Serial: 009401039360
* Mac: 34:e5:ec:54:5a:00
* Mac-Count: 254
*
2021-10-01 12:58:45.070 +0800 MAC initialization: success
2021-10-01 12:58:45.363 +0800 I2C and Uplink MAC initialization: success
2021-10-01 12:58:45.482 +0800 PHY initialization: success
2021-10-01 12:58:45.610 +0800 Port mapping initialization: success
2021-10-01 12:58:45.648 +0800 libports.so done
2021-10-01 12:58:45.648 +0800 Loading: libocteon.so...
2021-10-01 12:58:45.764 +0800 Interface 0: RGMII
2021-10-01 12:58:45.767 +0800 Interface 0: RGMII
2021-10-01 12:58:45.767 +0800 Interface 0: RGMII
2021-10-01 12:58:45.768 +0800 Verifying GMX3 link
2021-10-01 12:58:45.769 +0800 libocteon.so done
*"

Also, we had find a error with task in web ui that auto commit failed:

Error:Threat database handler failed
(Module:device)
Commit failed
Failed to commit policy to device

I want to know, what the problem happend for this device and how could I do for this problem?

Re: PA500 boot error with message "unable to connect to Sysd" and NIC in dataplane does not worked.

BPry — Sun, 03 Oct 2021 05:02:24 GMT

@songjixian,

PA-500s are getting up there and you could be running into an actual hardware issue. That being said, this error can also simply be caused by a software issue. I would try to either revert if you just did a software upgrade and switch over to the other partition using the debug swm revert aftger you've verified that your sysroot partition is revertable through debug swm status to see if that fixes your issue.

If the revert doesn't fix the issue the next step would be a factory reset through maintenance mode, and if that still doesn't work then it would be a likely hardware issue with the PA-500.

topic Re: PA500 boot error with message "unable to connect to Sysd" and NIC in dataplane does not worked. in General Topics

PA500 boot error with message "unable to connect to Sysd" and NIC in dataplane does not worked.

Re: PA500 boot error with message "unable to connect to Sysd" and NIC in dataplane does not worked.