Skip to main content
NetApp Knowledge Base

COTV-6734: OTV10: Enhanced OTV iGroup Management for Improved Visibility, Naming, and Scalability

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

Issue

  • Customers have provided feedback that the current ONTAP Tools for VMware (OTV) nested igroup management model can become difficult to understand and manage in large VMware environments.
  • Today, OTV automatically creates parent and child igroups to support datastore provisioning and host access management.
  • While this design provides automation and scalability, customers have reported challenges due to:
    • Large numbers of automatically created igroups in environments with many hosts and datastores.
    • Igroup names that use system-generated identifiers rather than easily recognizable host, datacenter, or vCenter names.
    • Difficulty determining the purpose or ownership of an igroup at a glance.
    • Increased administrative complexity when managing storage connectivity and troubleshooting access issues.
  • Some customers have indicated that the volume of nested igroups can make ONTAP SAN configuration appear more complex than expected and may encourage manual modifications to igroup structures, which can interfere with OTV provisioning workflows.
  • This enhancement request seeks to improve the overall manageability and usability of OTV-generated igroups by exploring options such as more intuitive naming conventions, simplified igroup organization, and improved handling of igroup reuse.

 

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.