2013-03-18 09:16 AM
I used end to end process to create a dataset with a Storage Service and I've been surprised to see that QSM uses the preferred IP addresses of storage systems rather than those of source and destination vFiler Units
Preferred IP addresses are set for each host (Storage systems and vFiler Units).
Each host uses its dedicated preferred IP address.
Storage Service uses a provisioning policy and a protection policy.
Provisioning service :
Protection policy :
vFiler Units are attached to Primary data and Backup.
During dataset creation OCUM assigns created volumes to corresponding vFilers
... and all storage objects are created.
However, in snapmirror.conf the IP addresses are those of hosting storage systems
Here under the Storage Service settings
Did I missed something ?
Thanks a lot for your help
2013-03-18 09:40 AM
The described behavior is expected when managing vFiler relationships using OnCommand Unified Manager.
You can read more about this behavior in this KB:
How does OnCommand discover and display SnapVault and SnapMirror relationships with a vFiler as one or both the endpoints of a relationship?
2013-03-18 09:54 AM
Many thanks Kevin, I forgot something important in the description.
All preferred IP addresses belong to hosting system storages. They do not belong to the vFiler units.
However, as we are building a secure multi-tenancy environment, each individual tenant and its dedicated vFilers use dedicated and separated backup networks.
For each tenant the backup dedicated vlan interface and its associated IP address belong to the vFiler0.
Each vFiler unit preferred IP address is a dedicated one but is not attached to the vFiler.
Using the preferred IP address for each host should enforce the data traffic to use the tenant dedicated backup network.
This works perfectly when importing external relationships. I do not understand why it does not work when creating new volumes on same vFilers from storage service and dataset.
2013-03-20 07:46 AM
We really need help from any Guru on this topic.
According to our understanding of the KB on ocum management of relationships between vFilers (thanks to Kevin https://kb.netapp.com/support/index?page=content&id=3013156), we were supposing that ocum uses IP addresses available on physical storage systems and that it uses prefered IP addresses assigned to vFilers Units hosts in the same way it uses the physical storage systems ones.
We imported several external relationships without any problem (thanks to Adaikkappan https://communities.netapp.com/message/102548#102548)
Imports created and modified several entries in snapmirror.conf file on destination storage system.
OCUM created connections lines using the name and the preferred IP address of the vFilers: this is what we were expecting
A few examples from several storage systems:
The first one is physical to physical
The second one is vFiler to vFiler
The third one is physical to vFiler
The fourth one is vFiler to physical
These results show that ocum is able to use prefered IP addresses defined for vFiler Units hosts and creates lines in snapmirror.conf accordingly.
Now, when we provision a new storage from scratch for a dataset with storage service attached and using the same storage systems and/or vFilers, the result is different.
In all cases ocum creates relationships using preferred IP addresses of hosting storage systems...
We do not understand why such differences exists. We think that something is missing in the configuration of dataset / storage service / policies ...
We will appreciate any help to make it working or explanation of this strange behaviour.