Skip to main content
NetApp Knowledge Base

COTV-6433: Unable to create a ONTAP RBAC user using OTV provided json file

  1. Last updated
  2. Save as PDF
Views:
190
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
virt
Last Updated:

Issue

  • When trying to create an ONTAP RBAC user using the user_roles.json from ONTAP Tools Manager to create the user within System Manager per Use ONTAP RBAC with ONTAP tools for VMware vSphere 10, users hit an error 'invalid command directory name'. 
  • This impacts customers using the ASA - A30 as well as AFF-C30 ONTAP platforms.
  • Continuous Product Engineering (CPE) team further investigated the error and found that there are few commands present in the .json file which are obsolete for an ASAr2 ONTAP platform ONTAP CLI support for ASA r2 storage systems.  
  • Below are few such commands which are present in .json file but were are not supported on ASA on r2:

lun comment
lun igroup set
lun move
lun move-in-volume
lun geometry

  • CPE also found issues with AFF-C platform models running ONTAP 9.16.1 which encounter the same 'invalid command directory name' error.
  • This is due to the AFF-C arrays not recognizing ASAr2 commands.
  • Below is the ASAr2 command that AFF-C models will not recognize:

storage availability-zone show
  • Since these unsupported commands are present in the .json file, System Manager is unable to create a RBAC user and encountering an error. 

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.