Thank you both for the quick replies. In summary the NMC is used to work with Protection Manager & Provisioning Manager and the Web Interface is Operations Manager? correct and one more correction Performance Advisor also uses, NMC. Also all three use the same Sybase database, which is located where? Its generally under <installation dir>/NTAPdfm/data. I checked Computer Management and I dont see a sybase service that runs. As I already said, its a embedded db, you can find the sql service running using the cli dfm service list. [root@lnx ~]# dfm service list sql: started http: started eventd: not started monitor: not started scheduler: not started server: started watchdog: not started [root@lnx~]# Regards adai ... View more

Hi Adam,      Operations Manger generate the following events, the license reaches limit. [root@lnx]# dfm eventtype list | grep -i license management-station:license-expired            Error        dfm.license.expiration management-station:license-nearly-expired     Warning      dfm.license.expiration management-station:license-not-expired        Normal       dfm.license.expiration management-station:node-limit-nearly-reached  Warning      dfm.license.limit management-station:node-limit-ok              Normal       dfm.license.limit management-station:node-limit-reached         Error        dfm.license.limit management-station:protmgr-node-limit-nearly-reached Warning      dfm.protlicense.limit management-station:protmgr-node-limit-ok      Normal       dfm.protlicense.limit management-station:protmgr-node-limit-reached Error        dfm.protlicense.limit management-station:provmgr-node-limit-nearly-reached Warning      dfm.provlicense.limit management-station:provmgr-node-limit-ok      Normal       dfm.provlicense.limit management-station:provmgr-node-limit-reached Error        dfm.provlicense.limit [root@lnx]# you cant stop the events by you can change/modify the severity of the event to information so that you dont find nagging messages. [root@lnx]# dfm eventtype modify help NAME     modify -- SYNOPSIS     dfm eventType modify -v <event-severity> <event-name> [root@lnx]# [root@lnx]# dfm eventtype modify -v Information  management-station:node-limit-reached Modified event "management-station:node-limit-reached". [root@lnx]# dfm eventtype list management-station:node-limit-reached Event Name                                         Severity     Class -------------------------------------------------- ------------ ------------------ management-station:node-limit-reached         Information  dfm.license.limit [root@lnx]# Regards adai ... View more

Pls do the following steps. Suspend the dataset,using dfpm dataset suspend <dsid/name> cli. Note the FS id of the volumes being moved. Then using traditional method VSM the volume from aggr1 to aggr3, quiesce and break the mirror. Then resync the snapvault( though i thing this would not be needed as they are in the same filer). After that rewrite the FSID of the migrated volume using ontap cli rewrite fsid. Now do a dfm host disover <filername> on the filer on which volumes are moved from aggr1 to 3. Resume the dataset using dfpm datsaet resume <dsid> Now things should work fine. Regards adai ... View more

you are hitting bug 496605, please raise a case and attach your call_rec to this bug Regards adai ... View more