TROUBLESHOOT YOUR SMARTCONNECT CONFIGURATION · 2020. 9. 12. · 7 - EMC Isilon Customer Troubleshooting Guide: Troubleshoot your SmartConnect Configuration _____ SmartConnect configuration

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/isilon-docfeedback.

___________________________

1 - EMC Isilon Customer Troubleshooting Guide: Troubleshoot your SmartConnect Configuration

___________________

Abstract This guide will help you to troubleshoot the following scenarios:

-- You are unable to connect to the SmartConnect name.-- The SmartConnect name resolves to an incorrect IP address.

September 3, 2019

EMC ISILON CUSTOMER TROUBLESHOOTING GUIDE

TROUBLESHOOT YOUR SMARTCONNECT CONFIGURATION

OneFS 7.2 - 8.2

https://community.emc.com/docs/DOC-49017

http://bit.ly/isilon-docfeedback



___________________________


___________________

Contents and overview

Before you beginPage 3

Appendix A If you need further assistance

Start troubleshootingPage 4

SmartConnect setupPage 13

Packet capturePage 17

Appendix D Example output

Note Follow all of these steps, in order, until you reach a resolution.

1. Follow these steps.

2. Perform troubleshooting steps in order.

3. Appendixes

Appendix BHow to use this flowchart

Appendix CExample output

Appendix E Example output

Appendix F Example output





___________________________


___________________

Configure screen 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 Isilon Technical Support, if you require assistance at any point during troubleshooting.

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.

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 console connection 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 304071 on the Online Support site.

Before you begin troubleshooting, confirm that you can connect through either another subnet or pool, or that you have physical access to the cluster.



https://support.emc.com/kb/304071



___________________________


___________________

Start troubleshooting

Start

If you have not done so already, log in to the cluster and configure screen logging through SSH, as described on page 3.

Verify that the SmartConnect processes are running by running the following command for your version of OneFS. Run the command from the node where the SmartConnect service IP (SSIP)

address resides:

OneFS 8.2 and laterisi_for_array -s ps awux | egrep "(isi_dnsiq_d|isi_sm artconnect_d)" | grep -v grep

OneFS 8.1 and earlieri si _f or _ar r ay - s ps awux | egr ep " ( i si _dnsi q_d| i si _smar t connect _d) " | gr ep - v gr ep

See Appendix G for example output.

Are the processesrunning?

Go to Page 5

Go to Page 6Yes

No

IntroductionStart troubleshooting here. For an overview of the conventions used in this flowchart, see Appendix B: How to use this flowchart.

_________





___________________________


___________________

SmartConnect configuration

Verify that the SmartConnect service is enabled by running the following command:

isi services -a isi_sm artconnect

Page 5

You could have arrived here from:

- Page 4 - Start troubleshooting

Does the output indicate that the

SmartConnect service is enabled?

NoEnable the SmartConnect service by running the

following command:

isi services -a isi_sm artconnect enable

Yes

Note the page number that you are currently on.

Upload log files and contact Isilon Technical Support, as instructed in

Appendix A.

Verify that the SmartConnect service is now enabled by running the following command:

isi services -a isi_sm artconnect

Is the SmartConnect

service now enabled?

No

Go to Page 6

Yes





___________________________


___________________

SmartConnect configuration (2)

Page 6


- Page 4 - Start troubleshooting- Page 5 - SmartConnect configuration

Identify the SSIP addresses for the specific subnet you are using by running the following command:

OneFS 8.2isi network subnets list -v | egrep -i "^ [ [ :space:] ] * (ID|SC Service Addrs)"

OneFS 8.0 - 8.1isi network subnets list

OneFS 7.2 isi networks list subnets

See Appendix C for example output. Copy the output to a text file for reference later in the troubleshooting process.

Find your SmartConnect Zone name by running the following command:

OneFS 8.xisi network pools list -v

OneFS 7.2isi networks list pools -v

See Appendix D for example output.

Go to Page 7

______________________________________________________

__________

__________





___________________________


___________________


Page 7


- Page 6 - SmartConnect configuration (2)

From the client, attempt to resolve the cluster name to an IP address by running the following command, where < sczone> is the

SmartConnect zone name:

nslookup < sczone>

See Appendix E for example output and explanation of what to look for.

From the client, attempt to resolve the cluster name to an IP address by running the following command, where < SC_FQDN> is the fully

qualified domain name (FQDN) for the SmartConnect zone:

nslookup < SC_FQDN>

See Appendix E for example output and explanation of what to look for.

Do the commands return an IP address as per the

examples in Appendix E?

Go to Page 8

Go to Page 12

Note These two commands should return similar output, but both should return an IP address that resides on the cluster. Yes

No

_________

_________

_________





___________________________


___________________


Page 8



Determine whether the returned IP address resides on the cluster by running the following command where

< returnedIP> is the IP address that was returned:

isi_for_array -l " ifconfig | grep < returnedIP> "

See the note box on this page for example output.

Does the returned IP address

reside on the cluster?

Go to Page 9No

Yes

Did the nslookup query

resolve to the SSIPaddress?

Go to Page 13

Go to Page 11

No

Yes

Example outputCl ust er - 1# i si _f or _ar r ay - l " i f conf i g | gr ep 192. 168. 228. 10"Cl ust er - 1: i net 192. 168. 228. 10 net mask 0xf f f f f f 00 br oadcast 192. 168. 228. 255 zone 1





___________________________


___________________


Page 9



Note The SmartConnect service will respond only if the query comes in on the SSIP address for the SmartConnect zone. An SSIP address for another zone will not respond for a SmartConnect name that does not belong to it.

Locate which node the SSIP address resides on by running the following command, where < ssip>

is the SmartConnect service IP address:

isi_for_array -l " ifconfig | grep < ssip> "

See the example output at the bottom of this page.

From the node where the SSIP address resides, attempt to resolve the cluster name by running the following command, where

< SC_FQDN> is the fully qualified domain name of the SmartConnect zone, and < ssip> is the SmartConnect service IP address:

nslookup < SC_FQDN> < ssip>

Did the nslookup query resolve to an

IP address?Go to Page 13

Go to Page 10

Yes

No

Example outputCl ust er - 1# i s i _f or _ar r ay - s " i f conf i g | gr ep 192. 168. 228. 3"cl ust er - 1: i net 192. 168. 228. 3 net mask 0xf f f f e000 br oadcast 192. 168. 228. 255 zone 1





___________________________


___________________


Page 10



From the client, locate the IP address of the client's DNS server by running the following

command from a Windows CMD prompt:

ipconfig /all

See Appendix F for example output.

From the cluster, run the following command, where < SC_FQDN> is the fully qualified domain

name of the SmartConnect zone, and < dnsIP> is the IP address of the client's DNS server:

nslookup < SC_FQDN> < dnsIP>

Did the command return an IP address?

Go to Page 13

No

YesDoes the IP

address reside on the cluster?

Go to Page 17

Go to Page 11No

Yes

__________





___________________________


___________________


Page 11


- Page 8 - SmartConnect configuration (4)- Page 10 - SmartConnect configuration (6)

The IP address returned by the DNS server does not reside on the cluster. This indicates

an IP address conflict or DNS issue. The queries are being answered with an IP address

that does not reside on the cluster. Contact your local networking team to check the

network and DNS configuration.

Did your networking team

make any changes to your network?

Go to Page 13Yes

No



Appendix A.

__________________________________________________________________





___________________________


___________________


Page 12



Was the failure presented as a

refusal, a timeout, or other failure?

Timeoutor otherfailure

Go to Page 17

Refusal

The SmartConnect service will not return an IP address if the query is for a SmartConnect zone that

is not connected to the SSIP address. In these cases, SmartConnect will return REFUSED status.

Go to Page 13





___________________________


___________________

SmartConnect setup

Page 13


- Page 8 - SmartConnect configuration (4)- Page 9 - SmartConnect configuration (5)- Page 10 - SmartConnect configuration (6)- Page 11 - SmartConnect configuration (7)- Page 12 - SmartConnect configuration (8)

Verify that the SmartConnect name is typed correctly in the configuration.

If the SmartConnect name is typed incorrectly, fix it.

Did fixing the configured

SmartConnect name resolve the

issue?

Yes End troubleshooting

Go to Page 14

No

___________________________________________________________________________________________________________________________________________________________________





___________________________


___________________

SmartConnect setup (2)

Page 14


- Page 13 - SmartConnect setup

Look up the configuration of the delegation record (or NS record) by running the following command from the cluster, where < fqdn> is the fully qualified

domain name, and < dnsIP> is the IP address of the DNS server:

nslookup -norecurse -type-ns < fqdn> < dnsIP>

See the example output at the bottom of this page.

Go to Page 15

Example outputNotes:

- A delegation record (or NS record) should exist, and it should match the zone name.- An A record (IPv4 address) or AAAA record (IPv6 address), shown in the output as i nt er net addr ess, should

show as the SmartConnect Service IP address.

cl ust er - 1# nsl ookup - nor ecur se - t ype=ns exampl e. i si l on. l ocal 192. 168. 38. 101Ser ver : 192. 168. 38. 101Addr ess: 192. 168. 38. 101#53

Non- aut hor i t at i ve answer :exampl e. i si l on. l ocal nameser ver = exampl esi p. i si l on. l ocal .

Aut hor i t at i ve answer s can be f ound f r om:exampl esi p. i si l on. l ocal i nt er net addr ess = 192. 168. 38. 60

Delegation record

A record or AAAA record





___________________________


___________________


Page 15


- Page 14 - SmartConnect setup (2)

Does the output contain a line with the

SmartConnect service IP (SSIP) address?

Go to Page 17Yes

Every SmartConnect name on the cluster needs to have a delegation record (or NS record). Check your DNS server to verify that this

delegation record (or NS record) is configured.

The delegation record (or NS record) should point to a SmartConnect IP address name A record (IPv4) or an AAAA record (IPv6).

The A or AAAA record should point to a specific SSIP address for the zone and the subnet where the SmartConnect name resides. If this is

not the case, you need to adjust your A or AAAA record so that it points to the correct zone and subnet.

Go to Page 16





___________________________


___________________


Page 16


- Page 15 - SmartConnect setup (3)

Depending on which DNS you are using, see one of the following articles about configuring SmartConnect:

- Windows DNS OneFS: How to configure Windows DNS for a SmartConnect zone, article 442679

- Infoblox DNS How to configure Infoblox DNS to use with SmartConnect, article 304465

- Bind DNS Isilon OneFS: How to create a UNIX-based BIND DNS setup for use with SmartConnect, article 468688

Did you make any configuration

changes?Yes Retest client access.

Has access been

restored?

Yes

End troubleshooting

Go to Page 17

No

No

___________

___________

___________








___________________________


___________________

Packet capture

Page 17


- Page 10 - SmartConnect configuration (6)- Page 12 - SmartConnect configuration (8)- Page 15 - SmartConnect setup (3)- Page 16 - SmartConnect setup (4)

Perform a packet capture (PCAP) on the cluster to ensure that requests from the client are reaching the cluster.

Open an SSH connection on any node in the cluster and log in by using the root account.

Run the following command, where < node> is the logical node number (LNN) of the node that the SSIP address resides on, and

< ssip> is the SmartConnect service IP address:

isi_net logger -a -i all -n < node> -s 384 -- host < ssip>

Note If no spaces exist between the arguments, be aware that isi_netlogger will parse flags improperly. The result is that the isi_netlogger execution is ineffective and captures nothing. Ensure you leave a space between any argument and the specified value.

Also, isi_netlogger is unable to capture traffic on VLANs. If you need to capture traffic on a VLAN, you will need to specify the parent interface, such as em0 or l agg0, or use the tcpdump utility. If you need guidance on using the tcpdump utility, reference the man page by typing man t cpdump from the cluster's command-line interface.

To locate the parent interface, run i f conf i g and look for the VLAN you are on (see the example output at the bottom of this page).

Reproduce the issue while the PCAP is running on the cluster.

Go to Page 18

Example outputvl an0: f l ags=8843<UP, BROADCAST, RUNNI NG, SI MPLEX, MULTI CAST> met r i c 0 mt u 1500 opt i ons=3<RXCSUM, TXCSUM> et her 00: 25: 90: c7: 06: ee i net 192. 168. 10. 1 net mask 0xf f f f f f 00 br oadcast 192. 168. 255. 255 zone 1 medi a: Et her net aut osel ect ( 1000baseTX <f ul l - dupl ex>) st at us: act i ve vl an: 1897 par ent i nt er f ace: em0

________________________________________________________________________________________________________________________





___________________________


___________________

Packet capture (2)

Page 18 You could have arrived here from:

- Page 17 - Packet capture

To stop the PCAP, press CTRL+C. The compressed PCAP file is saved in the / i f s/ net l og/ bundl ed directory and is named using the following time stamp format:

net log-yyyy-m m -dd-hh.m m .ss.tar.bz2

The file produced by i si _net l ogger can be extracted using a common file compression utility.

If your tool of choice doesn't work, alternatives such as 7-zip, exist.

Review the results of the PCAP with your network and security teams to ensure that the DNS queries from your DNS server are

reaching the node where the SSIP address resides.

Can you resolve the issue with the

PCAP results?Yes End troubleshooting

No

Gather a full log set and PCAP output by running the following two commands, in succession:

isi_gather_info

isi_gather_info --local-only --nologs -f /ifs/net log



Appendix A.





___________________________


___________________

Appendix A: If you need further assistance

Contact Isilon Technical SupportIf 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 Isilon Technical Support1. When troubleshooting is complete, type exi t 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 --ht tp --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 \--sym link /var/crash/Support IQ/upload/ftp

3. If you receive a message that the upload was unsuccessful, refer to article 304567 for directions on how to upload files over FTP.

____________



http://www.emc.com/contact/contact-us.htm




___________________________


___________________

Decision diamondYes No

Process stepProcess step with command:

command xyz

Go to Page #

Page # Note

Provides context and additional information. Sometimes a note is linked to a process step with a colored dot.

CAUTION!Caution boxes warn that a particular step needs to be performed with great care, to prevent serious consequences.

End pointDocument ShapeCalls 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.

Optional process step

IntroductionDescribes what the section helps you to accomplish.

Appendix B: How to use this flowchart


- Page 4 - Start Troubleshooting

Directional arrows indicate the path through

the process flow.





___________________________


___________________

Appendix C: Example output



Example output for OneFS 8.2cl ust er - 1# i si net wor k subnet s l i st - v | egr ep - i " ^[ [ : space: ] ] * ( I D| SC Ser vi ce Addr s) "I D: gr oupnet 0. subnet 0SC Ser vi ce Addr s: 1. 2. 3. 1- 1. 2. 3. 4I D: gr oupnet 0. subnet 1SC Ser vi ce Addr s: 1111: 0: 000: 9999: 0: beef : 7b0: eb00- 0000: 0: 170: 0001: 0: beef : 7b0: eb05

Example output for OneFS 8.0 - 8.1cl ust er - 1# i si net wor k subnet s l i stI D Subnet Gat eway| Pr i or i t y Pool s SC Ser vi ce Addr s- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -gr oupnet 0. subnet 0 192. 168. 222. 0/ 24 1. 2. 3. 1| 10 pool 0 192. 168. 222. 3- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Tot al : 1

Example output for OneFS 7.2cl ust er - 1# i si net wor ks l i st subnet sName Subnet Gat eway: Pr i o SC Ser vi ce Pool s- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -subnet 0 192. 168. 222. 0/ 24 192. 168. 222. 2: 1 192. 168. 222. 3 1subnet 1 192. 168. 111. 0/ 24 192. 168. 111. 2: 2 192. 168. 111. 3 1





___________________________


___________________

Continued on next page...

Appendix D: Example output



Example output for OneFS 8.xcl ust er - 1# i si net wor k pool s l i st - v I D: gr oupnet 0. subnet 0. pool 0 Gr oupnet : gr oupnet 0 Subnet : subnet 0 Name: pool 0 Rul es: r ul e0 Access Zone: Syst em Al l ocat i on Met hod: st at i c Aggr egat i on Mode: l acp SC Suspended Nodes: - Descr i pt i on: I ni t i al ext - 1 pool I f aces: 1: ext - 1, 2: ext - 1, 3: ext - 1 I P Ranges: 1. 2. 3. 4- 1. 2. 3. 6 Rebal ance Pol i cy: aut oSC Aut o Unsuspend Del ay: 0 SC Connect Pol i cy: r ound_r obi n SC Zone: exampl e. i si l on. com SC DNS Zone Al i ases: cl ust er . exampl e. i si l on. com SC Fai l over Pol i cy: r ound_r obi n SC Subnet : SC TTL: 0 St at i c Rout es: -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I D: gr oupnet 0. subnet 0. pool 1 Gr oupnet : gr oupnet 0 Subnet : subnet 0 Name: pool 1 Rul es: - Access Zone: Syst em Al l ocat i on Met hod: dynami c Aggr egat i on Mode: l acp SC Suspended Nodes: - Descr i pt i on: I f aces: 1: ext - 1, 2: ext - 1, 3: ext - 1 I P Ranges: 1. 2. 3. 7- 1. 2. 3. 9 Rebal ance Pol i cy: aut oSC Aut o Unsuspend Del ay: 0 SC Connect Pol i cy: r ound_r obi n SC Zone: exampl e2. i si l on. com SC DNS Zone Al i ases: - SC Fai l over Pol i cy: r ound_r obi n SC Subnet : SC TTL: 0 St at i c Rout es: -





___________________________


___________________

Appendix D: Example output (2)


- Previous page

Example output for OneFS 7.2

cl ust er - 1# i si newor ks l i st pool s - vsubnet 0: pool 0 - Test Pool I n Subnet : subnet 0 Al l ocat i on: St at i c Ranges: 1 10. 1. 1. 1- 10. 1. 1. 2 Pool Member shi p: 5 1: ext - agg ( up) 2: ext - agg ( up) 3: ext - agg ( up) 4: ext - agg ( up) 5: ext - agg ( up) Aggr egat i on Mode: Li nk Aggr egat i on Cont r ol Pr ot ocol ( LACP) Access Zone: Syst em ( 1) Smar t Connect : Suspended Nodes : None Aut o Unsuspend . . . 0 Zone : exampl e. i si l on. com Ti me t o Li ve : 0 Ser vi ce Subnet : subnet 0 Connect i on Pol i cy: Round Robi n Fai l over Pol i cy : Round Robi n Rebal ance Pol i cy : Aut omat i c Fai l back

subnet 0: pool 1 - SMB Test Pool I n Subnet : subnet 0 Al l ocat i on: St at i c Ranges: 1 10. 1. 1. 2- 10. 1. 1. 5 Pool Member shi p: 5 1: ext - agg ( up) 2: ext - agg ( up) 3: ext - agg ( up) 4: ext - agg ( up) 5: ext - agg ( up) Aggr egat i on Mode: Li nk Aggr egat i on Cont r ol Pr ot ocol ( LACP) Access Zone: t est - Zone ( 2) Smar t Connect : Suspended Nodes : None Aut o Unsuspend . . . 0 Zone : exampl e2. i si l on. com Ti me t o Li ve : 0 Ser vi ce Subnet : subnet 0 Connect i on Pol i cy: Round Robi n Fai l over Pol i cy : Round Robi n Rebal ance Pol i cy : Aut omat i c Fai l back





___________________________


___________________

Appendix E: Example output



Example output for nsl ookup <sczone>The expectation is for the command to return rotating IP addresses, or, at the very least, to show node IP addresses that are not the SSIP address.

A successful result will show the IP address. In this example, the returned IP address is 192.168.228.14, shown in bold in the following code example. If no IP address is listed, the command failed. If you receive other failures (for example a timeout or an error message), contact Isilon Technical Support.

Cl ust er - 1# nsl ookup t est 1Ser ver : 192. 168. 228. 99Addr ess: 192. 168. 228. 99#53

Name: exampl e. i si l on. l ocalAddr ess: 192. 168. 228. 14

___________________

Example output for nsl ookup <SC_FQDN>Cl ust er - 1# nsl ookup t est 1. i si l on. l ocal Ser ver : 192. 168. 228. 99Addr ess: 192. 168. 228. 99#53

Name: exampl e. i si l on. l ocalAddr ess: 192. 168. 228. 14



http://www.emc.com/contact/contact-us.htm



___________________________


___________________

Appendix F: Example output



Example output for i pconf i g / al lRun this command from a Windows CMD prompt to determine the IP address of your local DNS servers. The IP address is shown in bold in the following example output.

C: \ User s\ Admi ni st r at or . DC>i pconf i g / al l

Wi ndows I P Conf i gur at i on

Host Name . . . . . . . . . . . . : dc Pr i mar y Dns Suf f i x . . . . . . . : exampl e. l ocal Node Type . . . . . . . . . . . . : Hybr i d I P Rout i ng Enabl ed. . . . . . . . : No WI NS Pr oxy Enabl ed. . . . . . . . : No DNS Suf f i x Sear ch Li st . . . . . . : exampl e. l ocal

Et her net adapt er Local Ar ea Connect i on:

Connect i on- speci f i c DNS Suf f i x . : Descr i pt i on . . . . . . . . . . . : I nt el ( R) PRO/ 1000 MT Net wor k Connect i on Physi cal Addr ess. . . . . . . . . : 00- 0C- 29- 96- 0A- C0 DHCP Enabl ed. . . . . . . . . . . : No Aut oconf i gur at i on Enabl ed . . . . : Yes I Pv4 Addr ess. . . . . . . . . . . : 192. 168. 228. 99( Pr ef er r ed) Subnet Mask . . . . . . . . . . . : 255. 255. 255. 0 Def aul t Gat eway . . . . . . . . . : 192. 168. 228. 2 DNS Ser ver s . . . . . . . . . . . : 192. 168. 228. 250 Net BI OS over Tcpi p. . . . . . . . : Enabl ed





___________________________


___________________

Appendix G: Example output


- Page 4 - Start troubleshooting

Example output for OneFS 8.2 and latercl ust er - 1# i si _f or _ar r ay - s ps awux | egr ep " ( i si _dnsi q_d| i si _smar t connect _d) " | gr ep - v gr ep cl ust er - 1: r oot 1789 0. 0 0. 2 183888 18260 - Ss Fr i 18 1: 55. 91 / usr / sbi n/ i si _dnsi q_d cl ust er - 1: r oot 1795 0. 0 0. 3 223268 23168 - I s Fr i 18 8: 59. 80 / usr / sbi n/ i si _smar t connect _d cl ust er - 2: r oot 1785 0. 0 0. 2 183888 18220 - Ss 24Jul 19 7: 55. 56 / usr / sbi n/ i si _dnsi q_d cl ust er - 2: r oot 62132 0. 0 0. 3 226104 25680 - I s Fr i 17 21: 26. 69 / usr / sbi n/ i si _smar t connect _d cl ust er - 3: r oot 6777 0. 0 0. 2 183888 19736 - Ss Fr i 17 2: 36. 49 / usr / sbi n/ i si _dnsi q_d cl ust er - 3: r oot 6787 0. 0 0. 3 224984 25412 - I s Fr i 17 14: 41. 21 / usr / sbi n/ i si _smar t connect _d

Example output for OneFS 8.1 and earlier cl ust er - 1# i si _f or _ar r ay - s ps awux | egr ep " ( i si _dnsi q_d| i si _smar t connect _d) " | gr ep - v gr ep cl ust er - 1: r oot 94227 0. 0 0. 9 174624 18384 - Ss 11: 50AM 0: 00. 14 / usr / sbi n/ i si _dnsi q_d cl ust er - 2: r oot 13929 0. 0 0. 9 174112 17932 - Ss 11: 50AM 0: 00. 13 / usr / sbi n/ i si _dnsi q_d cl ust er - 3: r oot 93708 0. 0 0. 9 174112 17932 - Ss 11: 50AM 0: 00. 15 / usr / sbi n/ i si _dnsi q_d





___________________________


___________________

Copyright © 2019 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 CorporationHopkinton, Massachusetts 01748-91031-508-435-1000 in North America 1-866-464-7381www.EMC.com



https://www.emc.com

Documents

TROUBLESHOOT YOUR SMARTCONNECT CONFIGURATION · 2020. 9. 12. · 7 - EMC Isilon Customer Troubleshooting Guide: Troubleshoot your SmartConnect Configuration _____ SmartConnect configuration