跳转到主内容

由于此原因,无法向 OnCommand Unified Manager 添加新集群 到无效名称

Views:
24
Visibility:
Public
Votes:
0
Category:
oncommand-unified-manager
Specialty:
om
Last Updated:

适用于

  • Active IQ Unified Manager 9.6+%
  • OnCommand Unified Manager 9.5+

问题

  • 在尝试向 Unified Manager ( UM )添加新集群时,如果接受集群安全证书,则会显示以下错误:

    Unable to add cluster data source. This can occur if the clocks on the systems are not synchronized and the Unified Manager HTTPS certificate start date is later than the date on the cluster, or if the cluster has reached the maximum number of EMS notification destinations.

  • server_acq.log UM 服务器上的将包含以下错误:

    2020-10-01 12:09:33,130 ERROR [default task-2] c.o.s.a.s.AcquisitionFacadeUtil (AcquisitionFacadeUtil.java:171) - failed to register EMS: : com.netapp.oci.netapp.client.interfaces.data.EmsZapiManagerException: Invalid name. The name must start and end either with an alphanumeric or _(underscore) and must be in the length of 2 to 64 characters. The allowed special characters are _(underscore) and -(hyphen). (errno=27103)

  • 在查看 mlog/audit.log 集群上的文件(或 AUDIT-MLOG-TXT.GZASUP 中的部分)时,请求将显示拒绝的主机名

    示例 1
    Thu Oct 10 2020 12:09:33 +00:00 [kern_audit:info:2274] X:: filer1:ontapi :: 10.1.2.3:51336 :: filer1:admin :: <netapp version='1.0' xmlns='http://www.netapp.com/filer/admin' nmsdk_version='9.5' nmsdk_platform='CentOS Linux release 7.8.2003 x86_64' nmsdk_language='Java'><ems-event-notification-destination-create><name>-this-hostname-starts-with-a-hyphen-has-an-unsupported-$pecial-character-is-longer-than-64-characters-and-will-cause-issues-as-a-result</name><rest-api-url>XXX</rest-api-url><certificate-authority>123-456-789</certificate-authority><certificate-serial>X</certificate-serial></ems-event-notification-destination-create></netapp> :: Pending: 

    示例 2
    Thu Oct 10 2020 12:09:33 +00:00 [kern_audit:info:2274] X:: filer1:ontapi :: 10.1.2.3:51336 :: filer1:admin :: <netapp version='1.0' xmlns='http://www.netapp.com/filer/admin' nmsdk_version='9.5' nmsdk_platform='Linux unknown' nmsdk_language='Java'><ems-event-notification-destination-create><name>*-bad-hostname-with-wildcard</name><rest-api-url>XXX</rest-api-url><certificate-authority>123-456-789</certificate-authority><certificate-serial>X</certificate-serial></ems-event-notification-destination-create></netapp> :: Pending: 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.