Skip to main content
NetApp Knowledge Base

OTV: Issues registering OTV to vCenter after implementing CA signed certificate

Views:
398
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
virt
Last Updated:

Applies to

ONTAP Tools for VMware vSphere (OTV)

Issue

When replacing VSC's (Virtual Storage Console) self signed certificate with a certificate signed by a CA (certificate authority), the following issues are seen:

  • Discovery tasks tied to VSC / OTV appear as Recent Tasks in the vSphere HTML5 UI as expected
  • However OTV menus and icons do not appear in the vSphere HTML5 UI
  • When reviewing registered OTV extensions via VMware's Managed Object Browser (MOB) at https://<vcenter>/mob/?moid=ExtensionManager, the com.netapp.vsch5 extension is missing
    • clipboard_e38e77d9051b51e7bf14b4ea169b02bf7.png
  • During registration, OTV's out.log shows the following Null Pointer Exception when updating the vSphere extension:

16:14:24.139 [timerFactory-1] INFO com.netapp.nvpf.container.vsphere.VSphereExtensionRegistrationManager - Updated vSphere extension definition (key: com.netapp.nvpf) with vCenter server at https://192.168.0.31:443/sdk.
16:14:24.145 [timerFactory-1] DEBUG com.netapp.common.util.ConfigProperty - UTIL-00100: Application property server.host is not defined
16:14:24.145 [timerFactory-1] DEBUG com.netapp.nvpf.container.ServerProperties - VSC returninig pureIPv4 : 192.168.0.31
16:14:24.238 [timerFactory-1] WARN com.netapp.nvpf.container.vsphere.VSphereExtensionRegistrationManager - Failed to register or update vSphere extension.
java.lang.NullPointerException: null
    at com.netapp.nvpf.container.vsphere.HTMLClientExtensionBuilder.getSSLThumbPrint(HTMLClientExtensionBuilder.java:107)
    at com.netapp.nvpf.container.vsphere.HTMLClientExtensionBuilder.build(HTMLClientExtensionBuilder.java:57)
    at com.netapp.nvpf.container.vsphere.VSphereExtensionRegistrationManager$1.execute(VSphereExtensionRegistrationManager.java:182)
    at org.apache.commons.collections.functors.ClosureTransformer.transform(ClosureTransformer.java:73)
    at com.netapp.nvpf.container.vsphere.ServiceInstanceManager.withServiceInstance(ServiceInstanceManager.java:53)
    at com.netapp.nvpf.container.vsphere.ServiceInstanceProvider.withServiceInstance(ServiceInstanceProvider.java:73)
    at com.netapp.nvpf.container.vsphere.ServiceInstanceProvider.withServiceInstance(ServiceInstanceProvider.java:90)
    at com.netapp.nvpf.container.vsphere.ServiceInstanceProvider.withAdminServiceInstance(ServiceInstanceProvider.java:219)
    at com.netapp.nvpf.container.vsphere.ServiceInstanceProvider.withAdminServiceInstance(ServiceInstanceProvider.java:197)
    at com.netapp.nvpf.container.vsphere.VSphereExtensionRegistrationManager.registerOrUpdateExtension(VSphereExtensionRegistrationManager.java:67)
    at com.netapp.nvpf.container.vsphere.VSphereExtensionRegistrationManager.tryAndWarnExtensionRegistration(VSphereExtensionRegistrationManager.java:247)
    at com.netapp.nvpf.container.vsphere.VSphereCredentialFileWatcher.onChange(VSphereCredentialFileWatcher.java:45)
    at com.netapp.nvpf.container.vsphere.VSphereCredentialFileWatcher.checkForChange(VSphereCredentialFileWatcher.java:39)
    at com.netapp.nvpf.container.vsphere.VSphereCredentialFileWatcher.run(VSphereCredentialFileWatcher.java:51)

 

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.