ISILON Trouble Shooting PDF

EMC ISILON CUSTOMER TROUBLESHOOTING GUIDE
TROUBLESHOOT PROBLEMS
WITH YOUR NIS
AUTHENTICATION PROVIDER
OneFS 7.2.0 - 8.1.0
Abstract
This guide helps you to troubleshoot the following scenarios:
 The user is unable to connect to the cluster by using an IP address.
 The user is unable to connect to the cluster by using FQDN or SmartConnect zones.
 The user is unable to connect to some nodes.
 The domain or NIS authentication provider reports as offline.
January 4, 2018
1 - EMC Isilon Customer Troubleshooting Guide: Troubleshoot Problems With Your NIS
Authentication Provider
___________________________
For links to all Isilon customer troubleshooting guides, visit the Customer Troubleshooting - Isilon Info Hub.
We appreciate your help in improving this document. Submit your feedback at _________________
http://bit.ly/isi-docfeedback.
Contents and overview
Note
Follow all of these steps, in order, until you reach a resolution.
1. Follow these Before you begin

steps. Page 3
2. Perform
troubleshooting Start troubleshooting
Page 4
steps in order.
3. Appendixes Appendix A
If you need further assistance
Appendix B
How to use this flowchart
___________________________
Before you begin
CAUTION!
If the node, subnet, or pool that you are working on goes down during the course of
troubleshooting and you do not have any other way to connect to the cluster, you could
experience data unavailability.
Therefore, make sure that you have more than one way to connect to the cluster before
you start this troubleshooting process. The best method is to have a serial cable
available. This way, if you are unable to connect through the network, you will still be
able to connect to the cluster physically.
For specific requirements and instructions for making a physical connection to the
cluster, see article 16744 on the EMC Online Support site.
Before you begin troubleshooting, confirm that you can connect either through another
subnet or pool, or that you have physical access to the cluster.
Configure logging through SSH

We recommend that you configure screen logging to log all session input and output during your troubleshooting session.
This log file can be shared with EMC Isilon Technical Support if you require assistance at any point during troubleshooting.
Note: The screen session capability does not work in OneFS 7.1.0.6 and 7.1.1.2. If you are running either of these versions,
configure logging by using your local SSH client's logging feature.
1. Open an SSH connection to the cluster and log in by using the root account.
Note: If the cluster is in compliance mode, use the compadmin account to log in. All compadmin commands must be
preceded by the sudo prefix.
2. Change the directory to /ifs/data/Isilon_Support by running the following command:
cd /ifs/data/Isilon_Support
3. Run the following command to capture all input and output from the session:
screen -L
This will create a file named screenlog.0 that will be appended to during your session.
4. Perform troubleshooting.
___________________________
Start troubleshooting
Introduction
Start troubleshooting here. If you need
help to understand the flowchart Start
conventions used in this guide, see
Appendix B: How to use this flowchart.
If you have not done so already, log in to

the cluster and configure screen logging
through SSH, as described on page 3.
Establish an SSH connection to any node in the

cluster and log in using the root account.
Verify that the NIS authentication provider is online by

running the following command:
isi auth status
See the example output at the bottom of this page.
From the isi auth status output, note the

name of the NIS provider for use in the next steps.
See the bolded line in the example on this page.
Go to:
Is the NIS EMC Isilon Customer
provider Troubleshooting Guide:
Go to Page 5 No reporting as Yes Troubleshoot Identity
online? Mapping
Example output
Cluster-1# isi auth status
ID Active Server Status
------------------------------------------------------------------
lsa-activedirectory-provider:AD.TEST ADDOMAIN.com online
lsa-local-provider:System - active
lsa-file-provider:System - active
lsa-ldap-provider:ldap-test - online
lsa-nis-provider:nis.test - offline
------------------------------------------------------------------
___________________________
NIS offline
You could have arrived here from:

Page
 Page 4 - Start troubleshooting
5
View the NIS provider details by running the following command,

where <provider> is the name of the NIS provider:
isi auth nis view <provider>
Verify that the settings are correct, as follows:
 The Name field is the name of your NIS provider from the Isilon side.
 The NIS Domain field is the domain name of the NIS master server.
 The Servers field lists the IP address of the NIS master server.
See __________
Appendix C for example output and an explanation of the provider
settings that are required for authentication.
If the provider settings are incorrect, fix them.

For instructions on how to fix the settings, see the "Modify a NIS
__________________________
provider" section of the OneFS CLI Administration Guide for your
version of OneFS.
Recheck the status of the NIS provider by running the following command:
isi auth status
See the example output on ______

page 4.
Is the NIS
Yes provider reporting as No
online?
End troubleshooting Go to Page 6
___________________________
NIS offline (2)
 Page 5 - NIS offline Page

6
From a node in the cluster, perform a ping test to each NIS server by running
the following command once for each server, where <nisIP> is the IP
address of the NIS server:
ping <nisIP>
Did all the ping tests fail,

Mixed all pass, or did you get All failed
results mixed results?
If some ping tests passed and

others failed, record the
results and continue.
The failed pings indicate that

The failed pings indicate that something is wrong with the
something is wrong with the network or your NIS servers,
network or those particular not the Isilon cluster. Ask your
NIS servers, not the Isilon local networking team to check
cluster. Ask your local and resolve any issues with
networking team to check and All passed end-to-end connectivity. If you
resolve any issues with still cannot connect, contact
connectivity for those NIS Isilon Technical Support.
servers. If you still cannot
connect, contact Isilon
Technical Support.
Using the NIS servers that

passed the ping tests, Go to Page 7 End troubleshooting
continue troubleshooting.
___________________________
NIS offline (3)
 Page 6 - NIS offline (2) Page

7
Run the following command once for each NIS server,

where <nisIP> is the IP address of the NIS server:
rpcinfo -s <nisIP>
Note the page number that

you are currently on.
Did you receive
an RPC error? Yes Upload log files and contact
Isilon Technical Support, as
instructed in Appendix A.
No
Is the ypserv
Enable the ypserv
service listed in the output?
process on your NIS
servers. Enabling this
No See the bold text in the Yes Go to Page 8
example at the bottom of
process is OS specific.
this page.
Example output
Cluster-1# rpcinfo -s <nisIP)
program version(s) netid(s) service owner
100000 2,3,4 local,udp,tcp,udp6,tcp6 rpcbind superuser
100009 1 udp yppasswdd superuser
600100069 1 tcp,udp - superuser
100004 1,2 tcp,udp ypserv superuser
___________________________
NIS offline (4)
 Page 7 - NIS offline (3)

Page
8
Run both of the following commands for each NIS server,

where <nisIP> is the IP address of the NIS server:
rpcinfo -T tcp <nisIP> 100004

rpcinfo -T udp <nisIP> 100004
Does the output Note the page number that you

indicate that all the 100004 are currently on.
versions are ready and No Upload log files and contact Isilon
waiting for all the NIS Technical Support, as instructed in
servers? Appendix A.
Yes
Go to Page 9
Example output
Cluster-1# rpcinfo -T tcp 10.11.12.13 100004
program 100004 version 1 ready and waiting
Cluster-1# rpcinfo -T udp 10.11.12.13 100004

___________________________
NIS offline (5)
 ___________________
Page 8 - NIS offline (4) Page
 ____________________
Page 10 - NIS offline (6) 9
Validate that the client is connected to the NIS server by running the following three
commands on the client:
ypwhich
ypcat ypservers
ypcat passwd | head -3
See the example output and an explanation of each command at the bottom of this page.
Go to Page 10
Example output
The command ypwhich lists the NIS domain that the client is using. Example output:
cluster-1# ypwhich
nis1.example.jblogs.com
The command ypcat ypservers shows the NIS servers that the client is using. Example output:
cluster-1# ypcat ypservers
The command ypcat passwd | head -3 lists the first three users configured on the NIS server.
Head indicates the initial entries and -3 indicates the first three lines of entries. Example output:
cluster-1# ypcat passwd | head -3
user2083:x:2083:2083::/home/user2083:/bin/bash
___________________________
NIS offline (6)
 Page 9 - NIS offline (5) Page

10
Did any of the

This indicates a problem
commands on ______
page 9 return an
in your local environment.
Contact your local NIS Yes error message that indicates No
that the client is unable to reach
administrator.
the NIS servers?
Note The lack of an error message

The allowed file location and indicates that the problem is
contents will vary depending on between the Isilon cluster and the
the NIS server. NIS server, not between the client
For example, the file and the NIS server.
/var/yp/securenets is either
empty, or it contains all the Validate that the node IP address
authorized NIS clients (including ranges are allowed and are not
the Isilon network pools). blocked. Make any necessary
changes to allow access.
Note the page number that you

are currently on. Is the issue
Upload log files and contact Isilon Technical No resolved?
Support, as instructed in Appendix A.
Yes
End troubleshooting
___________________________
Appendix A: If you need further assistance
Contact EMC Isilon Technical Support

If you need to contact Isilon Technical Support during troubleshooting, reference the page or step that you need help with.
This information and the log file will help Isilon Technical Support staff resolve your case more quickly.
Upload node log files and the screen log file to EMC Isilon Technical Support
1. When troubleshooting is complete, type exit to end your screen session.
2. Gather and upload the node log set and include the SSH screen log file by using the command appropriate for your
method of uploading files. If you are not sure which method to use, use FTP.
ESRS:
isi_gather_info --esrs --local-only -f /ifs/data/Isilon_Support/screenlog.0
FTP:
isi_gather_info --ftp --local-only -f /ifs/data/Isilon_Support/screenlog.0
HTTP:
isi_gather_info --http --local-only -f /ifs/data/Isilon_Support/screenlog.0
SMTP:
isi_gather_info --email --local-only -f /ifs/data/Isilon_Support/screenlog.0
SupportIQ:
Copy and paste the following command.
Note: When you copy and paste the command into the command-line interface, it will appear on multiple lines (exactly
as it appears on the page), but when you press Enter, the command will run as it should.
isi_gather_info --local-only -f /ifs/data/Isilon_Support/screenlog.0 --noupload \
--symlink /var/crash/SupportIQ/upload/ftp
3. If you receive a message that the upload was unsuccessful , refer to ___________
article 16759 on the EMC Online Support site for
directions on how to upload files over FTP .
___________________________
Appendix B: How to use this flowchart
Introduction
Describes what the section helps you to
accomplish.
 Page # - "Page title"

Page
# Note
Provides context and additional
information. Sometimes a note is linked
Directional arrows indicate
to a process step with a colored dot.
the path through the
process flow.
Yes Decision diamond No
Process step with command:

Process step
CAUTION! command xyz
Caution boxes warn that
a particular step needs
to be performed with
great care, to prevent
serious consequences.
Optional process step Go to Page #
End point Document Shape

Calls out supporting documentation
for a process step. When possible,
these shapes contain links to the
reference document.
Sometimes linked to a process step
with a colored dot.
___________________________
Appendix C: Example isi auth nis view <provider> output

Example output
 Page 5 - NIS offline Cluster-1# isi auth nis view nis1
Name: nis1
NIS Domain: nis.test
Servers: 10.11.12.13
Status: online
Authentication: Yes
Balance Servers: Yes
Cache Entry Expiry: 15m
Check Online Interval: 3m
Create Home Directory: No
Enabled: Yes
Enumerate Groups: Yes
Enumerate Users: Yes
Findable Groups: -
Findable Users: -
Group Domain: NIS_GROUPS
Home Directory Template:
Hostname Lookup: Yes
Listable Groups: -
Listable Users: -
Login Shell:
NIS Domain field Normalize Groups: No
The NIS Domain field must match Normalize Users: No
the domain name of the NIS master Provider Domain:
server. Ntlm Support: all
Request Timeout: 20
To find the NIS Domain name, run Restrict Findable: No
the following command from the NIS Restrict Listable: No
master server: Retry Time: 5
Unfindable Groups: -
domainname Unfindable Users: -
Unlistable Groups: -
Example output: Unlistable Users: -
nis.trest User Domain: NIS_TEST
Ypmatch Using Tcp: No
Servers field
The Servers field must match the IP address of the NIS master server.
To find the NIS master server IP address, run the following command from the NIS
master server:
ifconfig -a |grep "inet addr"
Example output:
inet addr: 10.1.1.1 Bcast: 255.255.255.1 Mask: 255.255.255.0
___________________________
Copyright © 2018 Dell Inc. or its subsidiaries. All rights reserved.
Dell believes the information in this publication is accurate as of its publication date. The
information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS-IS. DELL MAKES NO

REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL
SOFTWARE DESCRIBED IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE .
Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other
trademarks may be the property of their respective owners.
EMC Corporation
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 in North America 1-866-464-7381
www.EMC.com
___________________________

ISILON Trouble Shooting PDF

Uploaded by

Copyright:

Available Formats

ISILON Trouble Shooting PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ISILON Trouble Shooting PDF

Uploaded by

Copyright:

Available Formats

EMC ISILON CUSTOMER TROUBLESHOOTING GUIDE

OneFS 7.2.0 - 8.1.0

1. Follow these Before you begin

Configure logging through SSH

If you have not done so already, log in to

Establish an SSH connection to any node in the

Verify that the NIS authentication provider is online by

isi auth status

See the example output at the bottom of this page.

From the isi auth status output, note the

You could have arrived here from:

View the NIS provider details by running the following command,

isi auth nis view <provider>

Verify that the settings are correct, as follows:

If the provider settings are incorrect, fix them.

isi auth status

See the example output on ______

End troubleshooting Go to Page 6

You could have arrived here from:

 Page 5 - NIS offline Page

Did all the ping tests fail,

If some ping tests passed and

The failed pings indicate that

Using the NIS servers that

You could have arrived here from:

 Page 6 - NIS offline (2) Page

Run the following command once for each NIS server,

See the example output at the bottom of this page.

Note the page number that

You could have arrived here from:

 Page 7 - NIS offline (3)

Run both of the following commands for each NIS server,

rpcinfo -T tcp <nisIP> 100004

See the example output at the bottom of this page.

Does the output Note the page number that you

Cluster-1# rpcinfo -T udp 10.11.12.13 100004

You could have arrived here from:

ypcat passwd | head -3

You could have arrived here from:

 Page 9 - NIS offline (5) Page

Did any of the

Note The lack of an error message

Note the page number that you

Contact EMC Isilon Technical Support

You could have arrived here from:

 Page # - "Page title"

Yes Decision diamond No

Process step with command:

End point Document Shape

You could have arrived here from:

ifconfig -a |grep "inet addr"

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS-IS. DELL MAKES NO

You might also like