確認方法WF-500健康状態
9718
Created On 02/22/23 09:44 AM - Last Modified 10/20/24 11:59 AM
Objective
の正常性と動作状態を確認する方法WF-500.
Environment
- WF-500
- WF-500-B
Procedure
- 走るシステム ソフトウェアの状態を表示するプロセスとアプリケーションが稼働しているかどうかを確認します。
以下の正常な状態の例:
dmin@WF-500> show system software status Overall control-plane status: running ---------------------------------------- Group 'all' will list status of all process members Type Name State Info Group all running Group base running Group batch running Group cluster_svc running Group dsms running Group fips running Group ha_ssh running Group services running Group third_party running Group vm_mgr running Group wf_3party running Group wf_panav running Group wf_redis running Group wf_services running Process appwkr_01_elink running (pid: 21397) Process appwkr_02_doc running (pid: 21399) Process appwkr_03_doc running (pid: 21396) Process appwkr_04_doc running (pid: 21398) Process appwkr_05_pe running (pid: 21400) Process appwkr_06_url_upload_file running (pid: 21403) Process appwkr_07_sessiononly running (pid: 21401) Process appwkr_08_archive running (pid: 21402) Process authd running (pid: 5399) Process chasd running (pid: 4072) Process cluster-mgr running (pid: 7408) Process clusterd running (pid: 5381) Process configd running (pid: 5375) Process crypto running (pid: 4351) Process dagger running (pid: 4025) Process dockerd running (pid: 5395) Process ehmon running (pid: 4071) Process elinkbenignhdlr_01 running (pid: 2228) Process elinkbenignhdlr_02 running (pid: 2201) Process elinkparser_01 running (pid: 1953) Process elinkparser_02 running (pid: 1954) Process elinkparserupload_01 running (pid: 2227) Process elinkparserupload_02 running (pid: 2226) Process elinkrp_01 running (pid: 1917) Process gdb running (pid: 4030) Process gearmand running (pid: 8962) Process ha-sshd running (pid: 4390) Process ha_agent running (pid: 7654) Process masterd running (pid: 3834) Process mdadm running (pid: 5727) Process mgmtsrvr running (pid: 9172) Process mongodb running (pid: 8372) Process monitor running (pid: 4026) Process mysql running (pid: 5764) Process mysql_local running (pid: 8892) Process notifier_01 running (pid: 20296) Process notifier_02 running (pid: 20299) Process notifier_03 running (pid: 20228) Process panavdns_01 running (pid: 20374) Process panavdns_02 running (pid: 20373) Process panavsync_01 running (pid: 20375) Process panavsync_02 running (pid: 20372) Process rabbitmq running (pid: 8234) Process redis_6379 running (pid: 8886) Process redis_6380 running (pid: 8909) Process redis_6381 running (pid: 8931) Process rsyncd running (pid: 8019) Process sample_sync_01 running (pid: 9392) Process sla_01 running (pid: 20227) Process snmpd running (pid: 8093) Process sshd running (pid: 4408) Process sslmgr running (pid: 4035) Process sysd running (pid: 3853) Process sysdagent running (pid: 4034) Process urlvmctrl_01 running (pid: 2435) Process urlvmctrl_02 running (pid: 2499) Process uwsgi running (pid: 21735) Process varrcvr running (pid: 7625) Process verdict_sync_01 running (pid: 20226) Process vm_decoynet running (pid: 1931) Process vm_torsvc running (pid: 1945) Process vmctrl_01 running (pid: 2376) Process vmctrl_02 running (pid: 2373) Process vmctrl_03 running (pid: 2591) Process vmctrl_04 running (pid: 2682) Process vmctrl_05 running (pid: 2716) Process vmctrl_06 running (pid: 2406) Process vmctrl_07 running (pid: 2488) Process vmctrl_08 running (pid: 2593) Process vmctrl_09 running (pid: 2650) Process vmctrl_10 running (pid: 2702) Process vmctrl_11 running (pid: 2739) Process vmctrl_12 running (pid: 2518) Process vmctrl_13 running (pid: 2561) Process vmctrl_14 running (pid: 2656) Process vmctrl_15 running (pid: 2692) Process vmctrl_16 running (pid: 2762) Process vmctrl_17 running (pid: 3082) Process vmctrl_18 running (pid: 2603) Process vmctrl_19 running (pid: 2629) Process vmctrl_20 running (pid: 2434) Process vmctrl_21 running (pid: 2416) Process vmctrl_22 running (pid: 2586) Process vmctrl_23 running (pid: 2648) Process vmctrl_24 running (pid: 2382) Process vmctrl_25 running (pid: 2393) Process vmctrl_26 running (pid: 2498) Process vpnctl running (pid: 8016) Process websrvr running (pid: 8219) Process wf_devsrvr running (pid: 7506) Process wf_lisasrvr running (pid: 5385) Process wf_siggen running (pid: 20298) Process wf_superv running (pid: 20295) Process wf_task_queue running (pid: 5359) admin@WF-500>
以下の不健康な状態の例:
admin@WF-500>show system software status Overall control-plane status: startChildren ---------------------------------------- Group 'all' will list status of all process members Type Name State Info Group all startChildren Group base running Group batch scheduling - Requires services running Group cluster_svc startChildren - Waiting for wf_services and vm_mgr ready... Group dsms running Group fips running Group ha_ssh running Group services startChildren Group third_party startChildren Group vm_mgr scheduling - Requires wf_services running Group wf_3party startChildren Group wf_panav stopped - Never Started Group wf_redis startChildren Group wf_services scheduling - Requires wf_redis ready Process appwkr_01_elink stopped (pid: -1) - Never Started Process appwkr_02_doc stopped (pid: -1) - Never Started Process appwkr_03_doc stopped (pid: -1) - Never Started Process appwkr_04_doc stopped (pid: -1) - Never Started Process appwkr_05_pe stopped (pid: -1) - Never Started Process appwkr_06_url_upload_file stopped (pid: -1) - Never Started Process appwkr_07_sessiononly stopped (pid: -1) - Never Started Process appwkr_08_archive stopped (pid: -1) - Never Started Process authd running (pid: 5491) Process chasd running (pid: 3993) Process cluster-mgr running (pid: 6348) Process clusterd running (pid: 5469) Process configd running (pid: 5463) Process crypto running (pid: 4181) Process dagger running (pid: 3956) Process dockerd running (pid: 5486) Process ehmon running (pid: 3987) Process elinkbenignhdlr_01 stopped (pid: -1) - Never Started Process elinkbenignhdlr_02 stopped (pid: -1) - Never Started Process elinkparser_01 stopped (pid: -1) - Never Started Process elinkparser_02 stopped (pid: -1) - Never Started Process elinkparserupload_01 stopped (pid: -1) - Never Started Process elinkparserupload_02 stopped (pid: -1) - Never Started Process elinkrp_01 stopped (pid: -1) - Never Started Process gdb running (pid: 3961) Process gearmand running (pid: 9738) Process ha-sshd running (pid: 4303) Process ha_agent running (pid: 8628) Process masterd running (pid: 3765) Process mdadm running (pid: 5741) Process mgmtsrvr running (pid: 5593) Process mongodb running (pid: 8894) Process monitor running (pid: 3957) Process mysql running (pid: 5817) Process mysql_local running (pid: 9608) Process notifier_01 stopped (pid: -1) - Never Started Process notifier_02 stopped (pid: -1) - Never Started Process notifier_03 stopped (pid: -1) - Never Started Process rabbitmq running (pid: 8748) Process redis_6379 running (pid: 9620) Process redis_6380 execed (pid: 15763) Redis PING failed for too long! Process redis_6381 scheduling (pid: -1) - Requires redis_6380 running Process rsyncd running (pid: 8672) Process sample_sync_01 scheduling (pid: -1) - Requires wf_3party ready Process sla_01 stopped (pid: -1) - Never Started Process snmpd running (pid: 8737) Process sshd running (pid: 4321) Process sslmgr running (pid: 3967) Process sysd running (pid: 3784) Process sysdagent running (pid: 3966) Process urlvmctrl_01 stopped (pid: -1) - Never Started Process urlvmctrl_02 stopped (pid: -1) - Never Started Process uwsgi scheduling (pid: -1) - Requires wf_3party ready Process varrcvr running (pid: 8407) Process vm_decoynet stopped (pid: -1) - Never Started Process vm_torsvc stopped (pid: -1) - Never Started Process vmctrl_01 stopped (pid: -1) - Never Started Process vmctrl_02 stopped (pid: -1) - Never Started Process vmctrl_03 stopped (pid: -1) - Never Started Process vmctrl_04 stopped (pid: -1) - Never Started Process vmctrl_05 stopped (pid: -1) - Never Started Process vmctrl_06 stopped (pid: -1) - Never Started Process vmctrl_07 stopped (pid: -1) - Never Started Process vmctrl_08 stopped (pid: -1) - Never Started Process vmctrl_09 stopped (pid: -1) - Never Started Process vmctrl_10 stopped (pid: -1) - Never Started Process vmctrl_11 stopped (pid: -1) - Never Started Process vmctrl_12 stopped (pid: -1) - Never Started Process vmctrl_13 stopped (pid: -1) - Never Started Process vmctrl_14 stopped (pid: -1) - Never Started Process vmctrl_15 stopped (pid: -1) - Never Started Process vmctrl_16 stopped (pid: -1) - Never Started Process vmctrl_17 stopped (pid: -1) - Never Started Process vmctrl_18 stopped (pid: -1) - Never Started Process vmctrl_19 stopped (pid: -1) - Never Started Process vmctrl_20 stopped (pid: -1) - Never Started Process vmctrl_21 stopped (pid: -1) - Never Started Process vmctrl_22 stopped (pid: -1) - Never Started Process vmctrl_23 stopped (pid: -1) - Never Started Process vmctrl_24 stopped (pid: -1) - Never Started Process vmctrl_25 stopped (pid: -1) - Never Started Process vmctrl_26 stopped (pid: -1) - Never Started Process vpnctl running (pid: 8671) Process websrvr running (pid: 9301) Process wf_devsrvr running (pid: 8216) Process wf_lisasrvr running (pid: 5475) Process wf_siggen stopped (pid: -1) - Never Started Process wf_superv stopped (pid: -1) - Never Started Process wf_task_queue running (pid: 5449) admin@WF-500>
ボックスが異常な状態にある場合、考えられる理由とさらなるヘルスアップのチェック。
- ディスク容量 - 重要なパーティションがありません
以下の健全な状態の例。
admin@WF-500>show system disk-space Filesystem Size Used Avail Use% Mounted on /dev/sda3 17G 5.1G 11G 33% / /dev/sda5 27G 11G 15G 44% /opt/pancfg /dev/sda6 21G 13G 7.2G 64% /opt/panrepo tmpfs 63G 176K 63G 1% /dev/shm /dev/sda8 56G 563M 53G 2% /opt/panlogs /dev/md1 275G 15G 247G 6% /opt/panlogs/ld1_1 /dev/md2 642G 6.6G 603G 2% /opt/panlogs/ld1_2 /dev/md3 275G 45G 217G 18% /opt/vmrepo /dev/md4 642G 6.5G 603G 2% /opt/panlogs/ld2_2 ! ! Full output omitted for brevity as it is not relevant for this article ! ! admin@WF-500>
以下は、異常な状態 (/dev/md2 がない) の出力の考えられる例の 1 つです。
admin@WF-500> show system disk-space Filesystem Size Used Avail Use% Mounted on /dev/sda3 17G 3.0G 13G 19% / /dev/sda5 27G 4.8G 21G 20% /opt/pancfg /dev/sda6 21G 11G 8.8G 56% /opt/panrepo tmpfs 63G 0 63G 0% /dev/shm /dev/sda8 56G 186M 53G 1% /opt/panlogs /dev/md1 275G 14G 248G 5% /opt/panlogs/ld1_1 /dev/md3 275G 45G 217G 18% /opt/vmrepo /dev/md4 642G 33G 577G 6% /opt/panlogs/ld2_2 ! ! Full output omitted for brevity as it is not relevant for this article ! ! admin@WF-500>
注: /dev/sda3 の代わりに、/dev/sda2 が表示されることがあります。これは、出力がボックスの現在アクティブなパーティションに依存するためです。
- RAIDディスクチェック
admin@WF-500> show system raid detail
Disk Pair A Available
Status Partition 1: active ; Partition 2: clean ;
Disk id A1 Present
model : ST1000NX0423
size : 953869 MB
partition_1 : active sync
partition_2 : active sync
Disk id A2 Present
model : ST1000NX0423
size : 953869 MB
partition_1 : active sync
partition_2 : active sync
Disk Pair B Available
Status Partition 1: clean ; Partition 2: clean ;
Disk id B1 Present
model : ST1000NX0423
size : 953869 MB
partition_1 : active sync
partition_2 : active sync
Disk id B2 Present
model : ST1000NX0423
size : 953869 MB
partition_1 : active sync
partition_2 : active sync
admin@WF-500>
以下は、異常な状態の出力の例の 1 つです。
admin@WF-500>show system raid detail
Disk Pair A Unavailable
Status Disk mount failure
Disk id A1 Present
model : ST1000NX0423
size : 953869 MB
partition_1 :
partition_2 : active sync
Disk id A2 Present
model : ST1000NX0423
size : 953869 MB
status : not in use
Disk Pair B Available
Status Partition 1: clean; Partition 2: clean;
Disk id B1 Present
model : ST1000NX0423
size : 953869 MB
partition_1 : active sync
partition_2 : active sync
Disk id B2 Present
model : ST1000NX0423
size : 953869 MB
partition_1 : active sync
partition_2 : active sync
admin@WF-500>
ノート：状況によっては一時的で不健康な状態が見られることが予想されます.
状況とシナリオ 1:
最も一般的で予想される理由はWF-500リブート。 ボックスが正しく起動するまでに時間がかかります。 ありませんSLA起動自体のためですが、すべてがOKボックスは、再起動後約 15 ～ 20 分後に動作状態になります。 この時間帯にボックスが起動しない場合でも、動作ステータスを自己修復するためにボックスによって自動的にトリガーされるバックエンド手順があります。
再起動がアップグレード プロセスの一部である場合、異なるメジャー間の変更が発生する可能性があるため、起動時間枠が長くなる可能性があります。PAN-OSたとえば、9.1 から 10.0 にアップグレードする場合。
状況とシナリオ 2:
コンテンツのインストール中またはコンテンツのアップグレード中に、プロセス自体のアトミック ロックを防ぐために一部のプロセスが再起動することが予想されます。最も注目すべきプロセスは vmctrl* です。 これを確認する方法は？ ボックスに現在のジョブまたはキューに入れられたジョブがあるかどうかを確認し、さらに masterd.log を確認します。 ジョブが終了すると、トリガーされたジョブが原因でさらに関連するプロセスが再起動される理由はありません。
admin@WF-500>show jobs id 3 Enqueued Dequeued ID Type Status Result Completed ------------------------------------------------------------------------------------------------------------------------------ 2022/05/19 15:44:31 15:44:31 3 WF-Content FIN OK 19:42:47 Warnings: Details:Configuration committed successfully Successfully committed last configuration admin@WF-500>
admin@WF-500> tail follow yes mp-log masterd.log 2022-05-19 15:55:21.193 +0200 INFO: urlvmctrl_01: process running with pid 32213 2022-05-19 15:55:21.197 +0200 INFO: vmctrl_06: process running with pid 32221 2022-05-19 15:55:21.448 +0200 INFO: vmctrl_21: process running with pid 32233 2022-05-19 15:55:21.456 +0200 INFO: vmctrl_02: process running with pid 32250 2022-05-19 15:55:21.459 +0200 INFO: vmctrl_20: process running with pid 32275 2022-05-19 15:55:21.462 +0200 INFO: vmctrl_25: process running with pid 32294 2022-05-19 15:55:21.464 +0200 INFO: vmctrl_26: process running with pid 32311 2022-05-19 15:55:21.467 +0200 INFO: vmctrl_07: process running with pid 32327 2022-05-19 15:55:21.470 +0200 INFO: vmctrl_12: process running with pid 32336 2022-05-19 15:55:21.472 +0200 INFO: urlvmctrl_02: process running with pid 32337 2022-05-19 15:55:27.935 +0200 INFO: vmctrl_03: process running with pid 32739 2022-05-19 15:55:27.941 +0200 INFO: vmctrl_04: process running with pid 32745 2022-05-19 15:55:28.073 +0200 INFO: vmctrl_13: process running with pid 32649 2022-05-19 15:55:28.080 +0200 INFO: vmctrl_08: process running with pid 321 2022-05-19 15:55:28.085 +0200 INFO: vmctrl_09: process running with pid 336 2022-05-19 15:55:28.089 +0200 INFO: vmctrl_18: process running with pid 32681 2022-05-19 15:55:28.094 +0200 INFO: vmctrl_22: process running with pid 32691 2022-05-19 15:55:28.098 +0200 INFO: vmctrl_14: process running with pid 371 2022-05-19 15:55:28.102 +0200 INFO: vmctrl_15: process running with pid 378 2022-05-19 15:55:28.106 +0200 INFO: vmctrl_19: process running with pid 380 2022-05-19 15:55:28.116 +0200 INFO: vmctrl_23: process running with pid 386 2022-05-19 15:55:28.249 +0200 INFO: vmctrl_10: process running with pid 403 2022-05-19 15:55:28.773 +0200 INFO: vmctrl_05: process running with pid 434 2022-05-19 15:55:29.881 +0200 INFO: vmctrl_11: process running with pid 477 2022-05-19 15:55:30.398 +0200 INFO: vmctrl_16: process running with pid 490 2022-05-19 15:55:32.039 +0200 INFO: vmctrl_17: process running with pid 561 2022-05-19 15:55:32.047 +0200 INFO: vm_mgr: running
状況とシナリオ 3:
ボックスの最初のジョブは Auto-Commit である必要があり、完了する必要があります。 これは、ボックスが正常な状態にあるための要件です。
admin@WF-500>show jobs id 1 Enqueued Dequeued ID Type Status Result Completed ------------------------------------------------------------------------------------------------------------------------------ 2022/04/04 14:13:38 14:13:38 1 AutoCom FIN OK 14:13:42 Configuration committed successfully Successfully committed last configuration admin@WF-500>
状況とシナリオ 4:
再起動後、RAID ディスクが再構築状態になる可能性があり、完了するまでにさらに時間がかかります。 このプロセスが終了する前に、Auto-Commit が開始されていないことがわかります。
admin@WF-500>tail follow yes mp-log raid.log Jun 12 03:35:21 DEBUG: raid_util: argv: ['Rebuild80', '/dev/md3'] Jun 12 03:35:21 DEBUG: Rebuild of Disk Pair B Partition 1 80 percent complete. Jun 12 03:35:52 DEBUG: raid_util: argv: ['Rebuild60', '/dev/md1'] Jun 12 03:35:52 DEBUG: Rebuild of Disk Pair A Partition 1 60 percent complete. Jun 12 03:43:10 DEBUG: raid_util: argv: ['RebuildFinished', '/dev/md3'] Jun 12 03:43:10 INFO: Rebuild of Disk Pair B Partition 1 finished. Jun 12 03:44:11 DEBUG: raid_util: argv: ['Rebuild80', '/dev/md1'] Jun 12 03:44:11 DEBUG: Rebuild of Disk Pair A Partition 1 80 percent complete. Jun 12 03:52:31 DEBUG: raid_util: argv: ['RebuildFinished', '/dev/md1'] Jun 12 03:52:32 INFO: Rebuild of Disk Pair A Partition 1 finished. admin@WF-500>
Additional Information
次はどうする？
上記で問題が解決せず、妥当な時間内にボックスが起動しない場合、または一部のプロセスがダウンしている場合は、次のケース分類でサポート チケットを作成できます。
タイプ: 技術サポート
テクノロジー: 地層
製品/問題領域:PAN-OS
SMEエリア: 管理
最初のトラブルシューティングでは、テクニカル サポート ファイルを共有するのが最善の方法ですが、それができない場合は、少なくとも共有してくださいCLIこの記事で共有されているコマンドからの出力。 また、ソフトウェアのアップグレード後、構成の変更後など、問題が発生または観察されたときのコンテキストと時間枠に関する情報を共有してください。