跳转到主内容

搜索

正在以下范围内搜索：
关于 7 个结果
  • SVM 无法连接到外部服务器，并显示错误： connection refused.
    https://kb-cn.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Vserver_could_not_make_a_connection_to_an_outside_server_with_error__Connection_refused
    适用场景 ONTAP 9 问题描述 SVM 无法连接到外部服务器， Connection refused 并且 EMS 日志中存在错误。 Wed Jun 09 15:00:07 CST [node2: secd: secd.conn.auth.failure:error]: Vserver (SVM2) could not make a connection over the network to...适用场景 ONTAP 9 问题描述 SVM 无法连接到外部服务器， Connection refused 并且 EMS 日志中存在错误。 Wed Jun 09 15:00:07 CST [node2: secd: secd.conn.auth.failure:error]: Vserver (SVM2) could not make a connection over the network to server (ip xx.xx.xx.xx, port 389) via interface xx.xx.xx.xx. Error: Connection refused. Wed Jun 09 15:00:09 CST [node2: secd: secd.ldap.query.timed.out:error]: Vserver 'SVM2': LDAP server xx.xx.xx.xx did not respond to query within timeout (2 seconds) interval.
  • 信息无效的PTR导致secd.conn.auth.failure或secd.ldap.noServers:EMERGENCY错误
    https://kb-cn.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/PTR_with_invalid_IP_causes_secd_conn_auth_failure_notice_or_secd_ldap_noServers_EMERGENCY_errors_in_ONTAP_9
    FAILURE: Unable to SASL bind to LDAP server using GSSAPI: Local error Additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Server...FAILURE: Unable to SASL bind to LDAP server using GSSAPI: Local error Additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Server not found in Kerberos database) Unable to connect to LDAP (Active Directory) service on dc1.demo.netapp.com (Error: Local error) No servers available for MS_LDAP_AD, vserver: 3, domain: demo.netapp.com.
  • 导致 Secd 失败的原因是什么：“错误：查找 CIFS 帐户名称过程失败”？
    https://kb-cn.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/What_can_cause_the_secd_failure__Error__Lookup_of_CIFS_account_name_procedure_failed
    00000021.000a1369 08a158ce Tue Oct 06 2020 18:47:59 +02:00 [kern_secd:info:9817] .------------------------------------------------------------------------------. 00000021.000a136a 08a158ce Tue Oct 06 ...00000021.000a1369 08a158ce Tue Oct 06 2020 18:47:59 +02:00 [kern_secd:info:9817] .------------------------------------------------------------------------------. 00000021.000a136a 08a158ce Tue Oct 06 2020 18:47:59 +02:00 [kern_secd:info:9817] | RPC FAILURE: | 00000021.000a136b 08a158ce Tue Oct 06 2020 18:47:59 +02:00 [kern_secd:info:9817] | secd_rpc_auth_name_to_sid has failed | 00000021.000a136c 08a158ce Tue Oct 06 2020 18:47:59 +02:00 [kern_secd:info:9817] | Result = 0, RPC Result = 6909 | 00…
  • 如何使用文件目录show和显示-creds检查权限
    https://kb-cn.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/How_to_use_file-directory_show_and_show-creds_to_check_for_permissions
    适用场景 ONTAP 9 CIFS 问题描述 使用ONTAP命令行界面命令查看文件级权限、以便进行权限故障排除
  • 如何收集SECD跟踪
    https://kb-cn.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/How_to_collect_a_SECD_trace
    test1::diag secd*> trace clear ? [-node] <nodename> *Node [[-trace-all] {yes|no}] *Clear Trace All [ -vserverids {yes|no} ] *Clear VserverIds [ -ipaddrs {yes|no} ] *Clear Ipaddrs [ -domain-names {yes|...test1::diag secd*> trace clear ? [-node] <nodename> *Node [[-trace-all] {yes|no}] *Clear Trace All [ -vserverids {yes|no} ] *Clear VserverIds [ -ipaddrs {yes|no} ] *Clear Ipaddrs [ -domain-names {yes|no} ] *Clear Domains [ -dc-names {yes|no} ] *Clear DC [ -rpc-names {yes|no} ] *Clear RPC [ -module-names {yes|no} ] *Clear Module [ -trace-connectivity {yes|no} ] *Clear Trace Connection Errors
  • 使用安全 LDAP （ LDAPS ）时， SECD 遇到紧急情况
    https://kb-cn.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/SECD_encounters_a_panic_when_using_Secure_LDAP_(LDAPS)
    ONTAP 9.5+ 在 EMS 中使用 LDAPS 时、 SECD 遇到紧急情况并出现以下错误： Fri Aug 21 05:09:16 PDT [nodename: secd: ucore.panicString:error]: 'secd: Received SIGSEGV (Signal 11) at RIP 0x806d86ec4 accessing address 0x10 (pid ...ONTAP 9.5+ 在 EMS 中使用 LDAPS 时、 SECD 遇到紧急情况并出现以下错误： Fri Aug 21 05:09:16 PDT [nodename: secd: ucore.panicString:error]: 'secd: Received SIGSEGV (Signal 11) at RIP 0x806d86ec4 accessing address 0x10 (pid 67823, uid 0, timestamp 1566367572)' Fri Aug 21 05:09:16 PDT [nodename: spmd: spm.secd.process.exit:EMERGENCY]: Security daemon with ID 67823 exited as a result of signal signal 11. The service will attempt to restart.
  • 将UNIX映射到Windows用户时报告secd.nfsAuth.noNameMap
    https://kb-cn.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Unable_to_map_Unix_to_Windows_user__secd_nfsAuth_noNameMap
    适用场景 ONTAP 9 NFS NTFS安全模式 问题描述 ONTAP无法(通过NFS)将Unix用户映射到Windows用户以进行NTFS 权限授权 EMS报告： secd: secd.nfsAuth.noNameMap:error]: vserver (SVM01) Cannot map UNIX name to CIFS name. Error: Get user credentials ...适用场景 ONTAP 9 NFS NTFS安全模式 问题描述 ONTAP无法(通过NFS)将Unix用户映射到Windows用户以进行NTFS 权限授权 EMS报告： secd: secd.nfsAuth.noNameMap:error]: vserver (SVM01) Cannot map UNIX name to CIFS name. Error: Get user credentials procedure failed SECD日志可能会显示： ERR : RESULT_ERROR_SECD_USER_NOT_FOUND ERR : Name mapping for UNIX user 'UID' failed. No mapping found debug: Logged secd.nfsAuth.noNameMap to EMS