El proceso "ntp" no aparece en la salida de "mostrar estado del software del sistema" en algunas plataformas
5524
Created On 03/19/21 03:09 AM - Last Modified 12/19/24 08:44 AM
Symptom
"ntp" aparece en la salida de "mostrar estado del software del sistema" en la PA-3000 plataforma de la serie, pero no aparece en PA-800 la plataforma. Por ejemplo :
[ PA-3020 ]
> show system software status
Slot 0, Role mp
----------------------------------------
Type Name State Info
Group all running
Group base running
Group batch running
Group batch_secondary running
Group chassis running
Group data_plane running
Group dsms running
Group fips running
Group gdb running
Group grp_plugins running
Group ha_ssh running
Group internal_monitor running
Group mgmt_services running
Group ntlm-grp running
Group services running
Group third_party running
Process authd running (pid: 4305)
Process cdb running (pid: 4487)
Process chasd running (pid: 2361)
Process cord running (pid: 3867)
Process crypto running (pid: 2848)
Process dagger running (pid: 2279)
Process devsrvr running (pid: 3868)
Process dhcp running (pid: 4301)
Process dnsproxy running (pid: 4302)
Process dp-console running (pid: 2362)
Process ehmon running (pid: 2360)
Process ha-sshd running (pid: 2860)
Process ha_agent running (pid: 4298)
Process ifmgr running (pid: 4295)
Process ikemgr running (pid: 4290)
Process keymgr running (pid: 4294)
Process l2ctrl running (pid: 4297)
Process l3svc running (pid: 18613)
Process logrcvr running (pid: 4292)
Process masterd running (pid: 2192)
Process mgmtsrvr running (pid: 4054)
Process monitor running (pid: 2280)
Process path_monitor running (pid: 7554)
Process pppoe running (pid: 4303)
Process rasmgr running (pid: 4293)
Process redis_useridd running (pid: 4071)
Process routed running (pid: 4304)
Process satd running (pid: 4299)
Process snmpd running (pid: 4333)
Process sshd running (pid: 2885)
Process sslmgr running (pid: 4300)
Process sslvpn running (pid: 4285)
Process sslvpn_ngx running (pid: 4404)
Process sysd running (pid: 2212)
Process sysdagent running (pid: 2285)
Process useridd running (pid: 3872)
Process varrcvr running (pid: 4296)
Process web_backend running (pid: 4280)
Process websrvr running (pid: 4275)
Slot 1, Role dp0
----------------------------------------
Type Name State Info
Group all running
Group gdb running
Group platform running
Group supervisor running
Group tasks running
Process all_pktproc_2 running (pid: 1226)
Process all_pktproc_3 running (pid: 1225)
Process all_pktproc_4 running (pid: 1227)
Process bfd running (pid: 1214)
Process brdagent running (pid: 1180)
Process comm running (pid: 1217)
Process dha running (pid: 1215)
Process ehmon running (pid: 1183)
Process flow_mgmt running (pid: 1228)
Process masterd running (pid: 1154)
Process monitor running (pid: 1229)
Process mprelay running (pid: 1216)
Process ntp running (pid: 20551)
Process pktproc_n_log running (pid: 1224)
Process sysdagent running (pid: 1181)
Process tund running (pid: 1218)[PA-850]
> show system software status Slot 1, Role mp ---------------------------------------- Type Name State Info Group all running Group base running Group batch running Group batch_secondary running Group chassis running Group data_plane running Group dsms running Group fips running Group gdb running Group grp_plugins running Group ha_ssh running Group mgmt_services running Group ntlm-grp running Group services running Group supervisor running Group tasks running Group third_party running Process all_task_1 running (pid: 3422) Process all_task_2 running (pid: 3423) Process authd running (pid: 4468) Process brdagent running (pid: 3028) Process chasd running (pid: 3030) Process comm running (pid: 3377) Process crypto running (pid: 3324) Process dagger running (pid: 2995) Process devsrvr running (pid: 4289) Process dha running (pid: 3375) Process dhcp running (pid: 4464) Process dnsproxy running (pid: 4465) Process ehmon running (pid: 3029) Process flow_ctrl running (pid: 3424) Process flow_mgmt running (pid: 3425) Process ha-sshd running (pid: 3380) Process ha_agent running (pid: 4458) Process ifmgr running (pid: 4455) Process ikemgr running (pid: 4451) Process keymgr running (pid: 4454) Process l2ctrl running (pid: 4457) Process l3svc running (pid: 1643) Process logrcvr running (pid: 4452) Process masterd running (pid: 2832) Process mgmtsrvr running (pid: 4326) Process monitor running (pid: 2996) Process monitor-dp running (pid: 3432) Process mprelay running (pid: 3376) Process pktlog_forwarding running (pid: 3421) Process pppoe running (pid: 4466) Process rasmgr running (pid: 4453) Process redis_useridd running (pid: 4329) Process routed running (pid: 4467) Process satd running (pid: 4461) Process sdwand running (pid: 3374) Process snmpd running (pid: 4477) Process sshd running (pid: 3426) Process sslmgr running (pid: 4462) Process sslvpn running (pid: 4449) Process sslvpn_ngx running (pid: 4500) Process sysd running (pid: 2852) Process sysdagent running (pid: 3007) Process tund running (pid: 3384) Process useridd running (pid: 4293) Process varrcvr running (pid: 4456) Process web_backend running (pid: 4438) Process websrvr running (pid: 4429)
Cause
Este es nuestro diseño.
No mostramos ntpd en el estado del sistema de espectáculos en ninguna plataforma en el MP , porque masterd no administra este servicio.
En el DP tenemos un servicio administrado por masterizado para ntpd, pero esto se debe a que los planes de datos independientes necesitan ejecutar un ntpd esclavo para conectarse con el ntpd que se ejecuta en el para mantener el tiempo igual encendido y en la plataforma que no tiene procesador dedicado para like MP , no hay necesidad de un servicio MP DP
DP PA-800 ntpd administrado por separado.
Con respecto a la arquitectura de nuestra plataforma, consulte este artículo.
Cómo interpretar la salida de "mostrar recursos del sistema" para CPU
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PLZZCA4 multinúcleo