您可以設定 NSX 應用裝置、NSX Edge 及 Hypervisor 以傳送記錄訊息至遠端記錄伺服器。
NSX Manager、NSX Edge 和 Hypervisor 支援遠端記錄。您必須在每個節點上個別設定遠端記錄。
如果針對 NSX 分散式惡意程式碼防護服務啟用了主機叢集,則可以登入每個主機上的 NSX 惡意程式碼防護服務虛擬機器 (SVM),並在 SVM 上設定遠端記錄。從 NSX 4.1.2 開始支援此功能。如需詳細資訊,請參閱在 NSX 惡意程式碼防護服務虛擬機器上設定遠端記錄。
對於通訊協定參數,選項包括 UDP、TCP、LI 以及安全通訊協定 TLS 和 LI-TLS。請注意,LI 和 LI-TLS 是 Aria Operations for Logs 通訊協定。Aria Operations for Logs 記錄伺服器支援所有通訊協定。僅當記錄伺服器為 Aria Operations for Logs 時,才可使用通訊協定 LI 和 LI-TLS。使用 LI 或 LI-TLS 的好處是它們能夠最佳化網路使用量。如果記錄伺服器為 Aria Operations for Logs,建議使用 LI 或 LI-TLS。如果無法使用 LI,則 TCP 的優勢是更加可靠,而 UDP 的優勢是需要較少的系統和網路額外負荷。
必要條件
- 請自行熟悉 CLI 命令 set logging-server。如需詳細資訊,請參閱《NSX 命令列介面參考》。
- 如果指定安全通訊協定 TLS 或 LI-TLS,則伺服器和用戶端憑證必須儲存在每個 NSX 應用裝置上的 /image/vmware/nsx/file-store 中。請注意,只有在使用 NSX CLI 來設定匯出工具時,才需要檔案存放區中的憑證。如果您使用 API,則不需要使用檔案存放區。完成 Syslog 匯出工具設定後,您必須從這個位置刪除所有的憑證和金鑰,以免產生潛在的安全性漏洞。
- 若要設定記錄伺服器的安全連線,請確認已為伺服器設定 CA 簽署的憑證。例如,如果您使用 Aria Operations for Logs 伺服器 vrli.prome.local 作為記錄伺服器,則可以從用戶端執行下列命令,以查看伺服器上的憑證鏈結:
echo -n | openssl s_client -connect vrli.prome.local:443 | sed -ne '/^Certificate chain/,/^---/p'
例如:
root@caserver:~# echo -n | openssl s_client -connect vrli.prome.local:443 | sed -ne '/^Certificate chain/,/^---/p' depth=2 C = US, L = California, O = GS, CN = Orange Root Certification Authority verify error:num=19:self signed certificate in certificate chain Certificate chain 0 s:/C=US/ST=California/L=HTG/O=GSS/CN=vrli.prome.local i:/C=US/L=California/O=GS/CN=Green Intermediate Certification Authority 1 s:/C=US/L=California/O=GS/CN=Green Intermediate Certification Authority i:/C=US/L=California/O=GS/CN=Orange Root Certification Authority 2 s:/C=US/L=California/O=GS/CN=Orange Root Certification Authority i:/C=US/L=California/O=GS/CN=Orange Root Certification Authority --- DONE
程序
- 若要在 NSX 應用裝置或 NSX Edge 上設定遠端記錄,請執行以下操作:
- 執行下列命令來設定記錄伺服器和要傳送至記錄伺服器的訊息類型。您可以使用逗號分隔且無空格的清單來指定多個設施或訊息識別碼。
set logging-server <hostname-or-ip-address[:port]> proto <proto> level <level> [facility <facility>] [messageid <messageid>] [serverca <filename>] [clientca <filename>] [certificate <filename>] [key <filename>] [structured-data <structured-data>]
您可以執行此命令多次,以新增多個組態。例如:set logging-server 192.168.110.60 proto udp level info facility local6 messageid SYSTEM,FABRIC
set logging-server 192.168.110.60 proto udp level info facility auth,user
若要將多租戶記錄轉送至遠端記錄伺服器,請在 structured-data 參數中指定專案和 VPC。例如,set logging-server <server-ip> proto udp level err structured-data proj=<project-shortId> set logging-server <server -ip proto udp level err structured-data vpc=<vpc-shortId>
若要僅將稽核記錄轉送至遠端伺服器,請在 structured-data 參數中指定 audit="true"。例如:set logging-server <server-ip> proto udp level info structured-data audit="true"
所有 NSX 記錄均使用設施 local6。唯有當未設定設施篩選器或指定的設施中包含 local6 時,才應使用 messageid 和 structured-data 篩選器。 - 設定安全遠端記錄:
- 若要使用 LI-TLS 通訊協定設定安全遠端記錄,請指定 proto li-tls 參數。例如:
set logging-server vrli.prome.local proto li-tls level info messageid SWITCHING,ROUTING,FABRIC,SYSTEM,POLICY,HEALTHCHECK,SHA,MONITORING serverca intermed-ca-full-chain.crt
如果設定成功,您將會收到不含任何文字的提示。若要查看伺服器憑證鏈結的內容 (中繼後面是根),請以 root 使用者身分登入,並執行下列命令:
keytool -printcert -file /image/vmware/nsx/file-store/intermed-ca-full-chain.crt
例如,root@nsx1:~# keytool -printcert -file /image/vmware/nsx/file-store/intermed-ca-full-chain.crt Certificate[1]: Owner: CN=Green Intermediate Certification Authority, O=GS, L=California, C=US Issuer: CN=Orange Root Certification Authority, O=GS, L=California, C=US Serial number: 3e726e7fbb3b0a7a6b4edd767f867fd2 Valid from: Sun Mar 15 00:00:00 UTC 2020 until: Mon Mar 17 00:00:00 UTC 2025 Certificate fingerprints: MD5: 94:C8:9F:92:56:60:EB:DB:ED:4B:11:17:33:27:C0:C9 SHA1: 42:9C:3C:51:E8:8E:AC:2E:5E:62:95:82:D7:22:E0:FB:08:B8:64:29 SHA256: 58:B8:63:3D:0C:34:35:39:FC:3D:1E:BA:AA:E3:CE:A9:C0:F3:58:53:1F:AD:89:A5:01:0D:D3:89:9E:7B:C5:69 Signature algorithm name: SHA256WITHRSA Subject Public Key Algorithm: 4096-bit RSA key Version: 3 Certificate[2]: Owner: CN=Orange Root Certification Authority, O=GS, L=California, C=US Issuer: CN=Orange Root Certification Authority, O=GS, L=California, C=US Serial number: 3e726e7fbb3b0a7a6b4edd767f867fd1 Valid from: Mon Mar 16 07:16:07 UTC 2020 until: Fri Mar 10 07:16:07 UTC 2045 Certificate fingerprints: MD5: ED:AC:F1:7F:88:05:83:2A:83:C0:09:03:D5:00:CA:7B SHA1: DC:B5:3F:37:DF:BD:E0:5C:A4:B7:F4:4C:96:12:75:7A:16:C7:61:37 SHA256: F2:5B:DE:8A:F2:31:9D:E6:EF:35:F1:30:6F:DA:05:FF:92:B4:15:96:AA:82:67:E3:3C:C1:69:A3:E5:27:B9:A5 Signature algorithm name: SHA256WITHRSA Subject Public Key Algorithm: 4096-bit RSA key Version: 3
成功和失敗情況的記錄均位於 /var/log/loginsight-agent/liagent_2020-MM-DD-<file-num>.log 中。如果設定成功,您可以使用下列命令來檢視 Aria Operations for Logs 組態:cat /var/lib/loginsight-agent/liagent-effective.ini
例如,root@nsx1:/image/vmware/nsx/file-store# cat /var/lib/loginsight-agent/liagent-effective.ini ; Dynamic file representing the effective configuration of VMware Log Insight Agent (merged server-side and client-side configuration) ; DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN ; Creation time: 2020-03-22T19:41:21.648800 [server] hostname=vrli.prome.local proto=cfapi ssl=yes ssl_ca_path=/config/vmware/nsx-node-api/syslog/bb466082-996f-4d77-b6e3-1fa93f4a20d4_ca.pem ssl_accept_any_trusted=yes port=9543 filter={filelog; nsx-syslog; pri_severity <= 6 and ( msgid == "SWITCHING" or msgid == "ROUTING" or msgid == "FABRIC" or msgid == "SYSTEM" or msgid == "POLICY" or msgid == "HEALTHCHECK" or msgid == "SHA" or msgid == "MONITORING" )} [filelog|nsx-syslog] directory=/var/log include=syslog;syslog.* parser=nsx-syslog_parser [parser|nsx-syslog_parser] base_parser=syslog extract_sd=yes [update] auto_update=no
- 若要使用 TLS 通訊協定設定安全遠端記錄,請指定 proto tls 參數。例如:
set logging-server vrli.prome.local proto tls level info serverca Orange-CA.crt.pem clientca Orange-CA.crt.pem certificate gc-nsxt-mgr-full.crt.pem key gc-nsxt-mgr.key.pem
請注意下列事項:- serverCA 參數只需要根憑證,而不需要完整鏈結。
- 如果 clientCA 與 serverCA 不同,則只需要根憑證。
- 憑證應保留 NSX Manager 的完整鏈結 (應符合 NDcPP 標準 - EKU、BASIC 和 CDP (CDP - 可忽略此檢查))。
您可以使用 keytool 命令檢查每個憑證的內容。例如,keytool -printcert -file /image/vmware/nsx/file-store/Orange-CA.crt.pem
keytool -printcert -file gc-nsxt-mgr-full.crt.pem
範例輸出:root@gc3:~# keytool -printcert -file /image/vmware/nsx/file-store/Orange-CA.crt.pem Owner: CN=Orange Root Certification Authority, O=GS, L=California, C=US Issuer: CN=Orange Root Certification Authority, O=GS, L=California, C=US Serial number: 3e726e7fbb3b0a7a6b4edd767f867fd1 Valid from: Mon Mar 16 07:16:07 UTC 2020 until: Fri Mar 10 07:16:07 UTC 2045 Certificate fingerprints: MD5: ED:AC:F1:7F:88:05:83:2A:83:C0:09:03:D5:00:CA:7B SHA1: DC:B5:3F:37:DF:BD:E0:5C:A4:B7:F4:4C:96:12:75:7A:16:C7:61:37 SHA256: F2:5B:DE:8A:F2:31:9D:E6:EF:35:F1:30:6F:DA:05:FF:92:B4:15:96:AA:82:67:E3:3C:C1:69:A3:E5:27:B9:A5 Signature algorithm name: SHA256WITHRSA Subject Public Key Algorithm: 4096-bit RSA key Version: 3 root@gc3:~# root@gc3:/image/vmware/nsx/file-store# keytool -printcert -file gc-nsxt-mgr-full.crt.pem Certificate[1]: Owner: CN=gc.prome.local, O=GS, L=HTG, ST=California, C=US Issuer: CN=Green Intermediate Certification Authority, O=GS, L=California, C=US Serial number: bdf43ab31340b87f323b438a2895a075 Valid from: Mon Mar 16 07:26:51 UTC 2020 until: Wed Mar 16 07:26:51 UTC 2022 Certificate fingerprints: MD5: 36:3C:1F:57:96:07:84:C0:6D:B7:33:9A:8D:25:4D:27 SHA1: D1:4E:F9:45:2D:0D:34:79:D2:B4:FA:65:28:E0:5C:DC:74:50:CA:3B SHA256: 3C:FF:A9:5D:AA:68:44:44:DD:07:2F:DD:E2:BE:9C:32:19:7A:03:D5:26:8D:5F:AD:56:CA:D2:6C:91:96:27:6F Signature algorithm name: SHA256WITHRSA Subject Public Key Algorithm: 4096-bit RSA key Version: 3 Certificate[2]: Owner: CN=Green Intermediate Certification Authority, O=GS, L=California, C=US Issuer: CN=Orange Root Certification Authority, O=GS, L=California, C=US Serial number: 3e726e7fbb3b0a7a6b4edd767f867fd2 Valid from: Sun Mar 15 00:00:00 UTC 2020 until: Mon Mar 17 00:00:00 UTC 2025 Certificate fingerprints: MD5: 94:C8:9F:92:56:60:EB:DB:ED:4B:11:17:33:27:C0:C9 SHA1: 42:9C:3C:51:E8:8E:AC:2E:5E:62:95:82:D7:22:E0:FB:08:B8:64:29 SHA256: 58:B8:63:3D:0C:34:35:39:FC:3D:1E:BA:AA:E3:CE:A9:C0:F3:58:53:1F:AD:89:A5:01:0D:D3:89:9E:7B:C5:69 Signature algorithm name: SHA256WITHRSA Subject Public Key Algorithm: 4096-bit RSA key Version: 3 Certificate[3]: Owner: CN=Orange Root Certification Authority, O=GS, L=California, C=US Issuer: CN=Orange Root Certification Authority, O=GS, L=California, C=US Serial number: 3e726e7fbb3b0a7a6b4edd767f867fd1 Valid from: Mon Mar 16 07:16:07 UTC 2020 until: Fri Mar 10 07:16:07 UTC 2045 Certificate fingerprints: MD5: ED:AC:F1:7F:88:05:83:2A:83:C0:09:03:D5:00:CA:7B SHA1: DC:B5:3F:37:DF:BD:E0:5C:A4:B7:F4:4C:96:12:75:7A:16:C7:61:37 SHA256: F2:5B:DE:8A:F2:31:9D:E6:EF:35:F1:30:6F:DA:05:FF:92:B4:15:96:AA:82:67:E3:3C:C1:69:A3:E5:27:B9:A5 Signature algorithm name: SHA256WITHRSA Subject Public Key Algorithm: 4096-bit RSA key Version: 3
在 /var/log/syslog 中記錄成功的範例:<182>1 2020-03-22T21:54:34.501Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="admin" level="INFO"] Successfully created CA PEM file /config/vmwarensx-node-api/syslog/92a78d8a-acfd-4515-b05a-2927b70ae920_ca.pem for logging server vrli.prome.local:6514 <182>1 2020-03-22T21:54:36.269Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="admin" level="INFO"] Successfully created client CA PEM file /config/vmwarensx-node-api/syslog/92a78d8a-acfd-4515-b05a-2927b70ae920_client_ca.pem for logging server vrli.prome.local:6514 <182>1 2020-03-22T21:54:36.495Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="root" level="INFO"] cert issuer = /C=US/L=California/O=GS/CN=Green IntermediateCertification Authority <182>1 2020-03-22T21:54:36.514Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="root" level="INFO"] cert subject = /C=US/ST=California/L=HTG/O=GS/CN=gc.promelocal <182>1 2020-03-22T21:54:36.539Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="root" level="INFO"] certificate trust check succeeded. status: 200, result:{'status': 'OK'} <182>1 2020-03-22T21:54:36.612Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="root" level="INFO"] Certificate already exists, skip import <182>1 2020-03-22T21:54:37.322Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="admin" level="INFO"] Successfully created certificate PEM file /config/vmwarensx-node-api/syslog/92a78d8a-acfd-4515-b05a-2927b70ae920_cert.pem for logging server vrli.prome.local:6514 <182>1 2020-03-22T21:54:38.020Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="admin" level="INFO"] Successfully created key PEM file /config/vmwarensx-node-api/syslog/92a78d8a-acfd-4515-b05a-2927b70ae920_key.pem for logging server vrli.prome.local:6514
在 /var/log/syslog 中記錄失敗的範例:<182>1 2020-03-22T21:33:30.424Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="admin" level="INFO"] Successfully created client CA PEM file /config/vmwarensx-node-api/syslog/76332782-1ec6-483a-95d4-2adeaf2ef112_client_ca.pem for logging server vrli.prome.local:6514 <182>1 2020-03-22T21:33:30.779Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="root" level="INFO"] cert issuer = /C=US/L=California/O=GS/CN=Green IntermediateCertification Authority <182>1 2020-03-22T21:33:30.803Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="root" level="INFO"] cert subject = /C=US/ST=California/L=HTG/O=GS/CN=gc.promelocal <179>1 2020-03-22T21:33:30.823Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="root" level="ERROR" errorCode="NODE10"] Certificate trust check failed. status:200, result: {'error_message': 'Certificate CN=gc.prome.local,O=GS,L=HTG,ST=California,C=US was not verifiably signed by CN=gc.prome.local,O=GS,L=HTG,ST=California,C=US: certificate does not verifywith supplied key', 'status': 'ERROR'} <179>1 2020-03-22T21:33:30.824Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="admin" level="ERROR" errorCode="NODE10"] Failed to create certificate PEM file config/vmware/nsx-node-api/syslog/76332782-1ec6-483a-95d4-2adeaf2ef112_cert.pem for logging server vrli.prome.local:6514 <182>1 2020-03-22T21:33:31.578Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="admin" level="INFO"] Successfully deleted CA PEM file /config/vmwarensx-node-api/syslog/76332782-1ec6-483a-95d4-2adeaf2ef112_ca.pem <182>1 2020-03-22T21:33:32.342Z gc3.prome.local NSX 5187 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="admin" level="INFO"] Successfully deleted client CA PEM file /config/vmwarensx-node-api/syslog/76332782-1ec6-483a-95d4-2adeaf2ef112_ca.pem <182>1 2020-03-22T21:33:32.346Z gc3.prome.local NSX 16698 - [nsx@6876 comp="nsx-cli" subcomp="node-mgmt" username="admin" level="INFO" audit="true"] CMD: set logging-server vrli.prome.local prototls level info serverca Orange-CA.crt.pem clientca Orange-CA.crt.pem certifi cate gc-nsxt-mgr.crt.pem key gc-nsxt-mgr.key.pem (duration: 6.365s), Operation status: CMD_EXECUTED
您可以使用下列命令檢查憑證與私密金鑰是否相符。例如:diff <(openssl x509 -in certs/gc-nsxt-mgr.crt.pem -pubkey -noout) <(openssl rsa -in private/gc-nsxt-mgr.key.pem -pubout)
如果憑證與私密金鑰相符,則輸出為 writing RSA key。若是任何其他輸出,皆表示兩者不相符。例如,如果憑證與私密金鑰相符,您將看到:root@caserver:~/server-certs# diff <(openssl x509 -in certs/gc-nsxt-mgr.crt.pem -pubkey -noout) <(openssl rsa -in private/gc-nsxt-mgr.key.pem -pubout) writing RSA key
私密金鑰已損毀的範例:root@caserver:~/server-certs# diff <(openssl x509 -in certs/gc-nsxt-mgr.crt.pem -pubkey -noout) <(openssl rsa -in private/gc-nsxt-mgr-corrupt.key.pem -pubout) unable to load Private Key 140404188370584:error:0D07209B:asn1 encoding routines:ASN1_get_object:too long:asn1_lib.c:147: 140404188370584:error:0D068066:asn1 encoding routines:ASN1_CHECK_TLEN:bad object header:tasn_dec.c:1205: 140404188370584:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:386:Type=RSA 140404188370584:error:04093004:rsa routines:OLD_RSA_PRIV_DECODE:RSA lib:rsa_ameth.c:119: 140404188370584:error:0D07209B:asn1 encoding routines:ASN1_get_object:too long:asn1_lib.c:147: 140404188370584:error:0D068066:asn1 encoding routines:ASN1_CHECK_TLEN:bad object header:tasn_dec.c:1205: 140404188370584:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:386:Type=PKCS8_PRIV_KEY_INFO 140404188370584:error:0907B00D:PEM routines:PEM_READ_BIO_PRIVATEKEY:ASN1 lib:pem_pkey.c:141: 1,14d0 < -----BEGIN PUBLIC KEY----- < MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAv3yH7pZidfkLrEP3zVa9 < EcOKXlFFjkThZRZMfguenlm8s6QHYVvuUX8IRB48Li3/DUfOj0bzaPWktpv+Q2P0 < N/j4LoX2RzjV/DPxYfLP6GMNMc21L3s9ruBeWUthtUP8khCWd2d2rZ09cUZVl0P9 < kIYBb5RMFC7Z1OUtH3bKdepEf+sXz3DaKZ/WySzYq9x86QDaA3ABO3Q0i7txBscI < FvXuMDOMQaC3pPp9FWO6IPRAWB57wahLJv6K5qGIfwubSBFg53grT4snf1lDZAhZ < 9hz5JgGr80GVyWyb7rgigpl9iUWAZx8U9De9XoxmvBN5iEGTIuKGaEgICL176crb < RMkhjnCqNHI+z6sQvpYJ7U0zZc72eBIWoHUkcWWk3eU6Oy4OiyW6jYuXG7hZYlly < nSkme3mZUWJKvcoX05+3zeCP623/HzE7X2sNyWFjzeF3XEvauZrIbsJh/xp2ShDa < uKKEY0gUGhLtCa3TpV9l8d6tFWVy8XjVjdjoVt4s7MfUo/airVmRykfsWrKyNUOQ < qRZvSbqjt8pm+3bSvKdXX4ul7ptPG2GF20ETWHPwjk2JwQpGhR9zK8fsKzvm6hXi < kq76zI4FefuVps3e1r39+0F+p6d6i2oUoo24sC1iSePTDhU74efVp6iv8HmnDgYX < Ylm6Kusr0JT5TJFDfASmrj8CAwEAAQ== < -----END PUBLIC KEY-----
私密金鑰和憑證皆有效,但兩者不相符的範例:root@caserver:~/server-certs# diff <(openssl x509 -in certs/gc-nsxt-mgr.crt.pem -pubkey -noout) <(openssl rsa -in private/vrli.key.pem -pubout) writing RSA key 2,13c2,13 < MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAv3yH7pZidfkLrEP3zVa9 < EcOKXlFFjkThZRZMfguenlm8s6QHYVvuUX8IRB48Li3/DUfOj0bzaPWktpv+Q2P0 < N/j4LoX2RzjV/DPxYfLP6GMNMc21L3s9ruBeWUthtUP8khCWd2d2rZ09cUZVl0P9 < kIYBb5RMFC7Z1OUtH3bKdepEf+sXz3DaKZ/WySzYq9x86QDaA3ABO3Q0i7txBscI < FvXuMDOMQaC3pPp9FWO6IPRAWB57wahLJv6K5qGIfwubSBFg53grT4snf1lDZAhZ < 9hz5JgGr80GVyWyb7rgigpl9iUWAZx8U9De9XoxmvBN5iEGTIuKGaEgICL176crb < RMkhjnCqNHI+z6sQvpYJ7U0zZc72eBIWoHUkcWWk3eU6Oy4OiyW6jYuXG7hZYlly < nSkme3mZUWJKvcoX05+3zeCP623/HzE7X2sNyWFjzeF3XEvauZrIbsJh/xp2ShDa < uKKEY0gUGhLtCa3TpV9l8d6tFWVy8XjVjdjoVt4s7MfUo/airVmRykfsWrKyNUOQ < qRZvSbqjt8pm+3bSvKdXX4ul7ptPG2GF20ETWHPwjk2JwQpGhR9zK8fsKzvm6hXi < kq76zI4FefuVps3e1r39+0F+p6d6i2oUoo24sC1iSePTDhU74efVp6iv8HmnDgYX < Ylm6Kusr0JT5TJFDfASmrj8CAwEAAQ== --- > MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAqvsjay7+o7gCW7szT3ho > bC34XX2l6u5Jl4/X/pUDI/YHmIf06bsZ1r/l4bTL4Q7BM6+9MI6UYEE7DxUoINGO > o4FEEQE32KWVFe3gw3homHU39q4pQjsJsxTcTE3oDMlIY0nWJ0PRUst3DffyUH1L > W0NUN9YdN+fAl2Uf021iuDqVy9V8AH3ON6fu+QCA8nt71ZkzeTxSA0ldpl2NA17F > rD8rm05wxnV7WtuV7V8PstISiClzhHgZRMl+B0r30OitnyAzEGLaRT3//PKfe0Oe > HCdxGMlrUtMqxIItJahEsqvMufyqNYecVscyXLHPelizKCsQfy8cO8LnznG8VAdc > YILSn3uYGZap6aF1SgVxsvZicwvlYnssmgE13Af0nScmfM96k9h5joHVEkWK6O8v > oT5DGG1kVL2Qly97x0b6EnzUorzivv5zJMKvFcOektR8HdMHQit5uvmMRY3S5zow > FtvfSDfWxxKyTy6GBrpP+8F+Jq91yGy/qa9lhKBzT2lg+rJp7T8k7/Nm9Tjyx7jL > EqgEKZEL4chxpo8ucF98hbvXWRuaFHC2iDzGuUmuS1FfjVvHTuIbEMQfjapLZrHx > 8jHfOP/PL+6kPbvNZZ2rTpczuEoGTQFFW9vX48GzIEyMeR6QWpPR0F7r4xak68P5 > 2PJmMveinDhU35IqWEXHAwcCAwEAAQ==
- 若要使用 LI-TLS 通訊協定設定安全遠端記錄,請指定 proto li-tls 參數。例如:
- 若要檢視記錄組態,請執行下列命令:
get logging-server
例如,nsx> get logging-servers 192.168.110.60 proto udp level info facility local6 messageid SYSTEM,FABRIC 192.168.110.60 proto udp level info facility auth,user
- 若要清除遠端記錄組態,請執行下列命令:
clear logging-servers
- 執行下列命令來設定記錄伺服器和要傳送至記錄伺服器的訊息類型。您可以使用逗號分隔且無空格的清單來指定多個設施或訊息識別碼。
- 在 ESXi 主機上設定遠端記錄:
- 執行下列命令以設定 Syslog 和傳送測試訊息:
esxcli network firewall ruleset set -r syslog -e true
esxcli system syslog config set --loghost=udp://<log server IP>:<port> --log-level=info
esxcli system syslog reload
esxcli system syslog mark -s "This is a test message"
- 您可以執行下列命令以顯示組態:
esxcli system syslog config get
- 執行下列命令以設定 Syslog 和傳送測試訊息: