Vfiler Discovery

[rakesh_patel]

We have recently implemented DFM and successfully have discovered Physical System - However we am unable to discover the Vfilers.

Please can some one advice etc.

[agireesh]

Hi Rakesh,

You need to set the storage system credentials to discover the vfilers.

Please follow the below steps to discover the vfilers of storage system.

1.  Set the credential of storage system using “dfm host set <storage-system-name or ip> hostLogin <storage-system-user-name> hostPassword <storage-system-password>” command.

2.  Execute dfm host discover <storage-system-name or ip> command

3.  Wait for some time and then verify discovered vfiler using “dfm vfiler list <storage-system-name or ip> command.

Please revert for further clarification if any.

Regards,

Gireesh

[pradeepl]

Hi,

Set the credentials of the storage system. Do a host discover and wait for vFilerTimestamp to get updated.

Now you can see the vfilers.

Regards

Pradeep L

[scottgelb · Accepted solution]

Some other vFiler options... dfm host discover is more for physical controllers.

dfm option set discovervfilers=yes   # should be yes already

dfm vfiler add all -H filer  x.x.x.x       # add all vfilers for a controller

To see all vFilers discovered..  dfm vfiler list -a  

Also, you can authenticate with NMC but you can also enter vfiler credentials from the cli

dfm host set dfmvfiler hostlogin=root

dfm host set dfmvfiler hostpassword=password

[martin_jencik]

Hello guys,

I have most of the vFilers discovered in the dfm, but there is certain controller (I mean two of them as they are clustered) whose vFilers are not visible in the dfm. Have you ever, by chance, encountered such a behaviour?

hostlogin and hostpassword for the Controllers are set as on all other controllers:

dfm host set <Controller> hostLogin=Controller_login hostPassword=Controller_password

the option for discovering vFilers is set to enabled:

discoverVfilers                       Enabled

but still when I issue the command I get:

dfm vfiler add -H <Controller> <vFiler>

Error: Access denied. Please check host login and password for <Controller> (266701).

Martin

[agireesh]

Hi,

Please check the “Last Updated” timestamp for vfiler monitor using “dfm host diag <controller-name>” command.

vFilerTimestamp Normal 1 hour 1 hour 11 Oct 20:19 Error 12 Oct 02:21

If vfiler last updated timestamp is old then run the “dfm host discover <controller-name>” command, once vFilerTimestamp is updated, then check the vfliers of controller.

Regards,

Gireesh

[adaikkap]

Can you get the output for dfm host diag. As from the error message it clearly looks like the credentials are not set properly.

Regards

adai

[martin_jencik]

folks, the output of dfm host diag:

Network Connectivity

IP Address             xxxxxxxxxxxxxxx

Network                (discovery disabled)

DNS Aliases            xxxxxxxxxxxxxxx

DNS Addresses          xxxxxxxxxxxxxxx

SNMP Version in Use    SNMPv1

SNMPv1                 Passed (50 ms)

SNMP Community         xxxxxxxxxxxxxxx

SNMP sysName           xxxxxxxxxxxxxxx

SNMP sysObjectID       .1.3.6.1.4.1.789.2.3 (Clustered Filer)

SNMP productId         xxxxxxxxxxxxxxx

SNMPv3                 Passed (4 ms)

SNMPv3 Auth Protocol   MD5

SNMPv3 Privacy Enabled No

SNMPv3 Username        root

SNMP sysName           xxxxxxxxxxxxxxx

SNMP sysObjectID       .1.3.6.1.4.1.789.2.3 (Clustered Filer)

SNMP productId         xxxxxxxxxxxxxxx

ICMP Echo              Passed (2 ms)

HTTP                   Passed (2 ms)

NDMP (login not set)   Skipped

RSH                    timed out

SSH                    Passed (10469 ms)

RLM                    Skipped (hostRLMAddress is empty)

XML (https port 443)   HTTP POST - Authorization failed

Host Details

According to:   DataFabric Manager server       Host

Host Name       xxxxxxxxxxxxxxx                    xxxxxxxxxxxxxxx

System ID       xxxxxxxxxxxxxxx                      xxxxxxxxxxxxxxx

Model           FAS6080                        FAS6080

Type            Clustered Storage System       Clustered Storage System

OS Version      7.3.6                          7.3.6

Revisions       330,8.0,2.1                    330,8.0,2.1

Monitoring Timestamps

Timestamp Name       Status   Interval     Default      Last Updated     Status   Error if older than ...

ccTimestamp          Normal   4 hours      4 hours                                12 Oct 06:43

cfTimestamp          Normal   5 minutes    5 minutes    12 Oct 10:37     Warning  12 Oct 10:38

clusterTimestamp     Normal   15 minutes   15 minutes                             12 Oct 10:28

cpuTimestamp         Error    12 hours     5 minutes    12 Oct 10:02     Normal   11 Oct 22:43

dfTimestamp          Normal   30 minutes   30 minutes   12 Oct 10:32     Normal   12 Oct 10:13

diskTimestamp        Normal   4 hours      4 hours      12 Oct 10:07     Normal   12 Oct 06:43

envTimestamp         Normal   5 minutes    5 minutes    12 Oct 10:37     Warning  12 Oct 10:38

fcTimestamp          Normal   5 minutes    5 minutes    12 Oct 10:39     Normal   12 Oct 10:38

fsTimestamp          Normal   15 minutes   15 minutes   12 Oct 10:29     Normal   12 Oct 10:28

hostPingTimestamp    Normal   1 minute     1 minute     12 Oct 10:40     Error    12 Oct 10:42

ifTimestamp          Error    12 hours     15 minutes   12 Oct 10:02     Normal   11 Oct 22:43

licenseTimestamp     Normal   4 hours      4 hours      12 Oct 10:03     Normal   12 Oct 06:43

lunTimestamp         Error    12 hours     30 minutes   12 Oct 10:26     Normal   11 Oct 22:43

opsTimestamp         Normal   10 minutes   10 minutes   12 Oct 10:33     Normal   12 Oct 10:33

qtreeTimestamp       Normal   8 hours      8 hours                                12 Oct 02:43

rbacTimestamp        Normal   1 day        1 day        12 Oct 10:02     Normal   11 Oct 10:43

userQuotaTimestamp   Normal   1 day        1 day        12 Oct 10:04     Normal   11 Oct 10:43

sanhostTimestamp     Error    1 day        5 minutes                              11 Oct 10:43

snapmirrorTimestamp  Error    4 hours      30 minutes                             12 Oct 06:43

snapshotTimestamp    Error    1 day        30 minutes                             11 Oct 10:43

statusTimestamp      Normal   10 minutes   10 minutes   12 Oct 10:34     Normal   12 Oct 10:33

sysInfoTimestamp     Normal   1 hour       1 hour       12 Oct 10:02     Normal   12 Oct 09:43

svTimestamp          Normal   30 minutes   30 minutes                             12 Oct 10:13

svMonTimestamp       Normal   8 hours      8 hours                                12 Oct 02:43

xmlQtreeTimestamp    Normal   8 hours      8 hours      12 Oct 10:09     Normal   12 Oct 02:43

vFilerTimestamp      Error    2 minutes    1 hour       12 Oct 10:41     Warning  12 Oct 10:41

vserverTimestamp     Normal   1 hour       1 hour                                 12 Oct 09:43

Performance Advisor Checklist

perfAdvisorEnabled     Passed

hostType               Passed

hostRevision           Passed

hostLogin              Passed

perfAdvisorTransport   Passed

---I have also installed the additional plugin for Ontap ver 7..3.6 to /opt/NTAPdfm/plugins/filer with "dfm plugin add" but this seems not to be the problem.

[agireesh]

Hi Martin,

Output of dfm host diag command show XML authentication is failed (XML (https port 443) HTTP POST - Authorization failed), due to that you are not able to discover the vfilers of controller.

XML authentication might be failed because

Ssl (httpd.admin.ssl.enable) is disable on storage system and “hostAdminTransport” of controller is set to “https”.

Please use “dfm host set <controller-ip-address> hostAdminTransport=http” command to change the admin transport of the controller and then check the XML is passing or not.

If XML is passed, discover the host using “dfm host discover < controller-ip-address >” command, check the vfiler timestamp and then check the discovered vfilers.

Regards,

Gireesh

[martin_jencik]

Hi Gireesh,

I was wondering why the "dfm host diag" tested:

XML (https port 443)   HTTP POST - Authorization failed

if the "dfm host get -q Controller-name" showed:

host=XXXXXXXXXX

hostLogin=root

hostPassword=********

hostLoginProtocol=ssh

hostPreferredAddr1=

hostPreferredAddr2=

hostPrimaryAddress=XXX.XXX.XXX.XXX

hostRLMAddress=

hostConsoleAddress=

cpuTooBusyThreshold=95

cpuBusyThresholdInterval=00:15:00

hostPingMethod=echo_snmp

hostAdminTransport=http <------------------------------------------this

hostNdmpLogin=

hostNdmpPassword=********

hostAdminPort=80  <--------------------------------------------------this

perfAdvisorTransport=httpsOk

prefsnmpVersion=1

useHostsEquiv=Yes

perfDataExportEnabled=No

defaultvFilerInterface=

processHostIP=

so I have changed the "hostAdminTransport" manually to "http" and after that the "dfm host diag" passed the XML (http port 80)     Passed (20 ms).

However the vFilers could not been seen from that particullar controller after "dfm host discover <Controller-Name>".

Only after I have changed the "useHostsEquiv" to "No" and run the "dfm host discover" the vFilers have been found.

PS: for the other controller (cluster partner) I have changed only the "useHostEquiv" and ran the "dfm host discover" after that the vFilers from the partner are visible too. So no changing the "hostAdminTransport" to "http" manually.

dfm host diag ran on partner before the useHostEquiv switched to "No":

...

XML (https port 443)   HTTP POST - Authorization failed

dfm host diag ran on partner after the useHostEquiv switched to "No":

XML (https port 443)   Passed (40 ms)

"dfm host get" for the partner:

...

hostAdminTransport=http

I hope I have not made all of this too confusing by stating all. Why is the dfm host get showing other values and the dfm host diag is testing the other option?

THANK YOU Giresh and Adai with your great help I have figured out what the problem was ... and now the vFilers are visible on the dfm.

Message was edited by: Martin Jencik This is what I have found a while ago: https://kb.netapp.com/support/index?page=content&id=2013946