Community

Subscribe
Highlighted

DFM Not Seeing Volumes Added to Vfilers

When adding a new volume to an existing vfiler on a V6080 running OnTap 7.3.6P1, NMC will only see the volume as located under the filer its self and not under the vfiler, we are running OnCommand 5.1

When running vol status on the vfiler we can see the vol as added to that vfiler

Has anyone come across this issue before and solved it

Re: DFM Not Seeing Volumes Added to Vfilers

Hi neil

You have to wait till the new Configuration is mapped in the dfm database. You can try to refresh the Controller via the Management Console:

or via CLI:

dfm host discover <Controller>

Another thing to speed up mapping new Configuration in the dfm Database is: Set the snmp to Version 3

https://communities.netapp.com/docs/DOC-9314

regards

Thomas

Re: DFM Not Seeing Volumes Added to Vfilers

Hi Braunt

We can see volume int_bal_nov_rg_10 as being added as a resource to vfiler pvfint006, the problem we are having is that when DFM refreshes the volume shows as being a resource of psaint006 and not vfiler pvfint006 under NMC

Vfiler Volume Information

np22@p01608:~> ssh -l internal\\admin-np22 psaint006 vfiler run pvfint006 vol status
internal\admin-np22@psaint006's password:

===== pvfint006
         Volume State           Status            Options
int_bal_nov_rg_6 online          raid_dp, flex     nosnap=on, no_atime_update=on,
                                sis               create_ucode=on,
                                                  convert_ucode=on,
                                                  maxdirsize=41861, guarantee=file,
int_bal_nov_rg_8 online          raid_dp, flex     nosnap=on, no_atime_update=on,
                                sis               create_ucode=on,
                                                  convert_ucode=on,
                                                  maxdirsize=41861, guarantee=file,
int_bal_nov_rg_2 online          raid_dp, flex     nosnap=on, no_atime_update=on,
                                sis               create_ucode=on,
                                                  convert_ucode=on,
                                                  maxdirsize=41861, guarantee=file,
int_bal_nov_rg_7 online          raid_dp, flex     nosnap=on, no_atime_update=on,
                                sis               create_ucode=on,
                                                  convert_ucode=on,
                                                  maxdirsize=41861, guarantee=file,
int_bal_nov_rg_9 online          raid_dp, flex     create_ucode=on,
                                sis               convert_ucode=on, guarantee=file,
int_bal_nov_rg online          raid_dp, flex     nosnap=on, no_atime_update=on,
                                sis               create_ucode=on,
                                                  convert_ucode=on,
                                                  maxdirsize=41861, guarantee=file,
int_bal_nov_rg_3 online          raid_dp, flex     nosnap=on, no_atime_update=on,
                                sis               create_ucode=on,
                                                  convert_ucode=on,
                                                  maxdirsize=41861, guarantee=file,
int_bal_nov_rg_4 online          raid_dp, flex     nosnap=on, no_atime_update=on,
                                sis               create_ucode=on,
                                                  convert_ucode=on,
                                                  maxdirsize=41861, guarantee=file,
int_bal_nov_rg_5 online          raid_dp, flex     create_ucode=on,
                                sis               convert_ucode=on, guarantee=none,
                                                  fractional_reserve=0
int_bal_nov_rg_10 online          raid_dp, flex     create_ucode=on,
                                sis               convert_ucode=on, guarantee=none,
                                                  fractional_reserve=0
int_bal_nov_rg_11 online          raid_dp, flex     create_ucode=on,
                                                  convert_ucode=on, guarantee=none,
                                                  fractional_reserve=0
pvfint006_root online          raid_dp, flex     create_ucode=on,
                                                  convert_ucode=on

NMC View
int_bal_nov_rg_1 online          raid_dp, flex     nosnap=on, no_atime_update=on,
                                sis               create_ucode=on,
                                                  convert_ucode=on,
                                                  maxdirsize=41861, guarantee=file,
int_bal_dbi_rg online          raid_dp, flex     create_ucode=on,
                                sis               convert_ucode=on, guarantee=file,

Re: DFM Not Seeing Volumes Added to Vfilers

Hi

Yes I know this. In the past sometimes I have to wait a long time, till my Volumes are show as a vfiler ressource in the NMC (DFM).

Till we use snmpv3 a lot things (eg renamed Volumes) changes  faster in the DFM Database.

Can you please enable snmpv3:

dfm host set  psaint006 prefsnmpVersion=3

Then a host diag:

dfm host diag psaint006

When all is OK, then run a discover:

dfm host discover psaint006

This was our Solution with FAS Systems. Perhaps at your side is the same Problem....

regards

Thomas

Re: DFM Not Seeing Volumes Added to Vfilers

Hi Braunt

I changed the  prefsnmpVersion=3 and then did the diag in psaint00

This however did not fix the issue we are having

I did see in the vfmon logs the following error

[DFMMonitor:ERROR]: [9384:0x31a0]: Failed to update storage resources for vFiler pvfint006.internal.vic.gov.au(11836)

Re: DFM Not Seeing Volumes Added to Vfilers

Hi Neil,

     Is there any volume or qtree names which are same but differ only by case of the letter, like in the example below ?

examplevol/qt_One

exampleVol/qt_one

This is one such situation in which you will hit the error as you mentioned in the vfMon. If thats your case, pls change the names, also raise a support case against bug186391

Regards

adai

Re: DFM Not Seeing Volumes Added to Vfilers

Here is the solution  

Stop dfm services (dfm service stop)

Start SQL (dfm service start sql)

Then run:

dfm query run -f "SELECT * FROM DFM.vfStoragePaths WHERE (spName = '/vol/int_bal_nov_rg_6_old') AND ( ( vfId = 11836 ) OR ( vfId = 5491 ) )"

verify the entries we will delete

dfm query run -f "DELETE FROM DFM.vfStoragePaths WHERE (spName = '/vol/int_bal_nov_rg_6_old') AND ( ( vfId = 11836 ) OR ( vfId = 5491 ) )"

delete those entries

dfm query run -f "SELECT * FROM DFM.vfStoragePaths WHERE (spName = '/vol/int_bal_nov_rg_6_old') AND ( ( vfId = 11836 ) OR ( vfId = 5491 ) )"

verify the entries are deleted

Please capture output of this session. Please note that this is only to address the specific vfId and volume that is currently in conflict. If that type of scenario (creating the volume, moving it to the vfiler, then moving it back to the pfiler and to a new vfiler) has happened more than once, we may have additional conflicting volumes. We won’t know until after this offending entry is removed and then services restarted and look in the dfmmonitor.log for new errors.

This is what fixed our vfiler issue

Re: DFM Not Seeing Volumes Added to Vfilers

Hi Neil's,

Happy that you got a solution. May I know how and where you got this solution?

Regards,

adai

Re: DFM Not Seeing Volumes Added to Vfilers

Hi Adai

This solution was provided by NetApp after going through the DFM logs

Re: DFM Not Seeing Volumes Added to Vfilers

Hi Niel,

                When you mean NetApp, do you mean netapp support ?

Regards

adai