Subscribe

OM & Provisioning Mgr don't display volumes as belonging to vfiler

When I run "vfiler status -r <vfiler>" on a storage controller, I show 5 volumes listed as resources belonging to that vfiler.  In both OM & Prov Mgr one of the volumes is listed as belonging to the hosting storage controller.  What do I need to to get OM & Prov Mgr to correctly display the volume as belonging to the vfiler?

sean.

Re: OM & Provisioning Mgr don't display volumes as belonging to vfiler

Hi,

Was the volume moved to vfiler recently?

Can you run a "dfm host discover <hosting-storage-system-ip-or-name>" & then recheck after a few mniutes.

Regards,

Prasad

Re: OM & Provisioning Mgr don't display volumes as belonging to vfiler

Hi Sean

For Operations Manager to properly discover volumes belonging to a vFiler unit please ensure the following

- Login credentials of storage controller are set in DFM

You can use the following command

dfm host set

- The vfiler monitoring interval is by default 1 hour

- After the monitor is run check the volume ownership in Operations Manager

Regards

Sharaf

Re: OM & Provisioning Mgr don't display volumes as belonging to vfiler

The storage controller credentials are correct. I added the volume to the vfiler using the CLI over 24 hours before posting this and the vfiler monitoring interval is at the default 1 hour. I specifically issued "dfm host discover " to refresh the items several times yesterday as well as this morning.

sean

Re: OM & Provisioning Mgr don't display volumes as belonging to vfiler

Hi Sean

Do you see any errors in dfmmonitor.log

You can also see "dfm about" and just check if 10% free space is available for monitors to run

Regards

Sharaf

Re: OM & Provisioning Mgr don't display volumes as belonging to vfiler

Hi Sean,

Do you see any ERROR messages in dfmmonitor.log?

Regards,

Prasad

Re: OM & Provisioning Mgr don't display volumes as belonging to vfiler

There is sufficient free space for monitoring.

The only errors that exist are due to having recreated the dataset a couple of times. Since using the CLI to remove then add the volume back into to the vfiler, there have been no entries in the dfmmonitor.log filer (including the remove/add just described).

sean.

Re: OM & Provisioning Mgr don't display volumes as belonging to vfiler

Just to confirm the steps

1. There were 5 volumes in the vfiler unit

2. These were discovered fine by Ops Mgr

3. One of volume were removed from the vFiler unit from the storage controller CLI

4. This volume was shown in OpsMgr as belonging to the storage controller

5. This volume was added back to the vfiler unit in the storage controller

6. There is problem in getting this particular volume discovered as part of vFiler in Ops Mgr after the volume is added back

Re: OM & Provisioning Mgr don't display volumes as belonging to vfiler

1. Yes 5 volumes

2. All were initially added via NMC/Provisioning Manager

3. The volume in question was initially removed by deleting the dataset with the physical volume still attached. Removed initially due to issues creating more than 15 qtrees. This limitation was resolved. The volume was then re-added via Provisioning Manager, however it showed that the physical storage was now the hosting filer. Vfiler status -r showed the volume correctly owned by the vfiler.

4. I removed the volume from the vfiler via the CLI, then waited.

5. I re-added the volume to the vfiler via the CLI.

6. Correct, OpsMgr only shows the volume to be owned by physical filer.

sean

Re: OM & Provisioning Mgr don't display volumes as belonging to vfiler

Hi Sean,

     I tried your secnario and even after multiple retries, i couldn't reproduce it.

The following are the steps i tried. Kindly reply if I missed out something or misunderstood anything.

1. A dataset NTN1 with 1 volume NTN1:/NTN1and 15 Qtrees. The vol resides on a vfiler NTN1.

2. Vfiler NTN1 has 4 more volumesi i.e. total 5 ( excluding the root volume)

lnx186-155:~ # dfm volume list NTN1
ID   Volume Name                          Type         Block Type Deleted  Deleted By
---- ------------------------------------ ------------ ---------- -------- ---------------
3658 NTN1:/NTN1                           Flexible     32_bit     No
3654 NTN1:/NTN1_root                      Flexible     32_bit     No
3664 NTN1:/NTN2                           Flexible     32_bit     No
3668 NTN1:/NTN2_1                         Flexible     32_bit     No
3672 NTN1:/NTN2_2                         Flexible     32_bit     No
3676 NTN1:/NTN2_3                         Flexible     32_bit     No
lnx186-155:~ #

the Qtress:

lnx186-155:~ # dfm qtree list NTN1:/NTN1/
ID   Qtree Name                                    Deleted  Deleted By
---- --------------------------------------------- -------- ---------------
3661 NTN1:/NTN1/NTN_vol1                           No
3707 NTN1:/NTN1/vol10                              No
3716 NTN1:/NTN1/vol11                              No
3717 NTN1:/NTN1/vol12                              No
3718 NTN1:/NTN1/vol13                              No
3719 NTN1:/NTN1/vol14                              No
3720 NTN1:/NTN1/vol15                              No
3699 NTN1:/NTN1/vol2                               No
3700 NTN1:/NTN1/vol3                               No
3701 NTN1:/NTN1/vol4                               No
3702 NTN1:/NTN1/vol5                               No
3703 NTN1:/NTN1/vol6                               No
3704 NTN1:/NTN1/vol7                               No
3705 NTN1:/NTN1/vol8                               No
3706 NTN1:/NTN1/vol9                               No
lnx186-155:~ #

3. The dataset NTN1 is now deleted using NMC/Prov Mgr. Now deleting detaset doesn't delete any volumes. So my vfiler NTN1 still has all 5 volumes.

after deleting the dataset from prov mgr.

lnx186-155:~ # dfpm dataset list
Id         Name                        Policy                      Provisioning Policy Storage Service
---------- --------------------------- --------------------------- ------------------- ---------------
      3509 Djoker                                                  Murray
      3522 Florian                                                 NAS_1
      3479 Murray                                                  Murray
      3663 NTN2                                                    NAS_NTN
lnx186-155:~ #

Dataset NTN1 is deleted.

lnx186-155:~ # dfm volume list NTN1
ID   Volume Name                          Type         Block Type Deleted  Deleted By
---- ------------------------------------ ------------ ---------- -------- ---------------
3658 NTN1:/NTN1                           Flexible     32_bit     No
3654 NTN1:/NTN1_root                      Flexible     32_bit     No
3664 NTN1:/NTN2                           Flexible     32_bit     No
3668 NTN1:/NTN2_1                         Flexible     32_bit     No
3672 NTN1:/NTN2_2                         Flexible     32_bit     No
3676 NTN1:/NTN2_3                         Flexible     32_bit     No
lnx186-155:~ #

The volume NTN1:/NTN1 still there on vfiler.

4. I go to filer CLI and remove the volume NTN1:/NTN1 from vfiler NTN1. f3050-184-85*> vfiler remove NTN1 /vol/NTN1.

5. After dfm host discovery.

lnx186-155:~ # dfm volume list NTN1
ID   Volume Name                          Type         Block Type Deleted  Deleted By
---- ------------------------------------ ------------ ---------- -------- ---------------
3654 NTN1:/NTN1_root                      Flexible     32_bit     No
3664 NTN1:/NTN2                           Flexible     32_bit     No
3668 NTN1:/NTN2_1                         Flexible     32_bit     No
3672 NTN1:/NTN2_2                         Flexible     32_bit     No
3676 NTN1:/NTN2_3                         Flexible     32_bit     No
lnx186-155:~ #


NO vol NTN1:/NTN1 seen ON vfiler.

vol is now seen by storage controller.

lnx186-155:~ # dfm volume list 10.72.184.85
ID   Volume Name                          Type         Block Type Deleted  Deleted By
---- ------------------------------------ ------------ ---------- -------- ---------------
3549 f3050-184-85:/Blake_root             Flexible     32_bit     No
3567 f3050-184-85:/Dell_root              Flexible     32_bit     No
3658 f3050-184-85:/NTN1                   Flexible     32_bit     No
3557 f3050-184-85:/Prov_NSDThkVl_root     Flexible     32_bit     No
3551 f3050-184-85:/Prov_NSDTkVSnp_root    Flexible     32_bit     No
3563 f3050-184-85:/Prov_NSDTnVl1_root     Flexible     32_bit     No
3559 f3050-184-85:/Prov_OffMig11_root     Flexible     32_bit     No
3681 f3050-184-85:/Prov_OffMig15_root     Flexible     32_bit     No
3565 f3050-184-85:/Prov_OffMig3_root      Flexible     32_bit     No
3571 f3050-184-85:/Prov_OffMig8_root      Flexible     32_bit     No
3690 f3050-184-85:/Prov_RBkiSCSIOnMigl_root Flexible     32_bit     No
3684 f3050-184-85:/provManagerTestCases_test_NASnapDelOffMig_ds Flexible     32_bit     No
3555 f3050-184-85:/provManagerTestCases_test_NASVfilerOffMig_ds_1 Flexible     32_bit     No
3693 f3050-184-85:/provManagerTestCases_test_RBkiSCSIOnMig_ds Flexible     32_bit     No
3573 f3050-184-85:/provManagerTestCases_test_SANIscsiLunOffMig_ds Flexible     32_bit     No
3553 f3050-184-85:/vol0                   Flexible     32_bit     No
3654 NTN1:/NTN1_root                      Flexible     32_bit     No
3664 NTN1:/NTN2                           Flexible     32_bit     No
3668 NTN1:/NTN2_1                         Flexible     32_bit     No
3672 NTN1:/NTN2_2                         Flexible     32_bit     No
3676 NTN1:/NTN2_3                         Flexible     32_bit     No
3709 Prov_RBkNFSOnMig:/Prov_RBkNFSOnMig_root Flexible     32_bit     No
3711 Prov_RBkNFSOnMig:/provManagerTestCases_test_RBkNFSOnMig_ds Flexible     32_bit     No
lnx186-155:~ #

6. Adding the volume back to the vfiler using filer CLI.

f3050-184-85*> vfiler add NTN1 /vol/NTN1
WARNING: reassigning storage to another vfiler does not change the
security information on that storage. If the security domains are
not identical, unwanted access may be permitted, and wanted access
may be denied.
exportfs [NTN1]: NFS service is disallowed.
f3050-184-85*>
f3050-184-85*>
f3050-184-85*>
f3050-184-85*> vfiler status -a NTN1
NTN1                             running
   ipspace: default-ipspace
   IP address: 33.11.2.11 [e0a]
   Path: /vol/NTN1_root [/etc]
   Path: /vol/NTN2
   Path: /vol/NTN2_1
   Path: /vol/NTN2_2
   Path: /vol/NTN2_3
   Path: /vol/NTN1
   UUID: 0675cb7c-185c-11df-a960-00a098076372
   Protocols allowed: 4
   Allowed: proto=rsh
   Allowed: proto=ssh
   Allowed: proto=ftp
   Allowed: proto=http
   Protocols disallowed: 3
   Disallowed: proto=nfs
   Disallowed: proto=cifs
   Disallowed: proto=iscsi
f3050-184-85*>

7. After dfm host discovery.

lnx186-155:~ # dfm volume list NTN1
ID   Volume Name                          Type         Block Type Deleted  Deleted By
---- ------------------------------------ ------------ ---------- -------- ---------------
3658 NTN1:/NTN1                           Flexible     32_bit     No
3654 NTN1:/NTN1_root                      Flexible     32_bit     No
3664 NTN1:/NTN2                           Flexible     32_bit     No
3668 NTN1:/NTN2_1                         Flexible     32_bit     No
3672 NTN1:/NTN2_2                         Flexible     32_bit     No
3676 NTN1:/NTN2_3                         Flexible     32_bit     No
lnx186-155:~ #


vol NTN1 is back on vfiler.

And no longer managed by filer.

lnx186-155:~ # dfm volume list 10.72.184.85
ID   Volume Name                          Type         Block Type Deleted  Deleted By
---- ------------------------------------ ------------ ---------- -------- ---------------
3549 f3050-184-85:/Blake_root             Flexible     32_bit     No
3567 f3050-184-85:/Dell_root              Flexible     32_bit     No
3557 f3050-184-85:/Prov_NSDThkVl_root     Flexible     32_bit     No
3551 f3050-184-85:/Prov_NSDTkVSnp_root    Flexible     32_bit     No
3563 f3050-184-85:/Prov_NSDTnVl1_root     Flexible     32_bit     No
3559 f3050-184-85:/Prov_OffMig11_root     Flexible     32_bit     No
3681 f3050-184-85:/Prov_OffMig15_root     Flexible     32_bit     No
3565 f3050-184-85:/Prov_OffMig3_root      Flexible     32_bit     No
3571 f3050-184-85:/Prov_OffMig8_root      Flexible     32_bit     No
3690 f3050-184-85:/Prov_RBkiSCSIOnMigl_root Flexible     32_bit     No
3709 f3050-184-85:/Prov_RBkNFSOnMig_root  Flexible     32_bit     No
3684 f3050-184-85:/provManagerTestCases_test_NASnapDelOffMig_ds Flexible     32_bit     No
3555 f3050-184-85:/provManagerTestCases_test_NASVfilerOffMig_ds_1 Flexible     32_bit     No
3693 f3050-184-85:/provManagerTestCases_test_RBkiSCSIOnMig_ds Flexible     32_bit     No
3711 f3050-184-85:/provManagerTestCases_test_RBkNFSOnMig_ds Flexible     32_bit     No
3573 f3050-184-85:/provManagerTestCases_test_SANIscsiLunOffMig_ds Flexible     32_bit     No
3553 f3050-184-85:/vol0                   Flexible     32_bit     No
3658 NTN1:/NTN1                           Flexible     32_bit     No
3654 NTN1:/NTN1_root                      Flexible     32_bit     No
3664 NTN1:/NTN2                           Flexible     32_bit     No
3668 NTN1:/NTN2_1                         Flexible     32_bit     No
3672 NTN1:/NTN2_2                         Flexible     32_bit     No
3676 NTN1:/NTN2_3                         Flexible     32_bit     No
lnx186-155:~ #


Warm regards,

Abhishek

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.