At the CLI, yes, in an MMC, no, because the MMC is making MSRPC calls to the LWIOD on just one node at a time, which as you've indicated is very hit and miss.
So at the CLI, you could do something like this:
isi_for_array -s "isi smb openfiles list"
Here is my output on an empty and idle cluster:
isilon3-1: ID Path
isilon3-1: -------
isilon3-1: -------
isilon3-1: Total: 0
isilon3-2: ID Path
isilon3-2: -------
isilon3-2: -------
isilon3-2: Total: 0
isilon3-3: ID Path
isilon3-3: -------
isilon3-3: -------
isilon3-3: Total: 0
isi_for_array = runs the command on every node
(-s switch) = runs the command in a serial manner, 1 node at a time, get all those responses then move to the next node. This is slower than without the -s switch, however the results are easier to interpret.
crklosterman
450 Posts
0
July 10th, 2017 08:00
At the CLI, yes, in an MMC, no, because the MMC is making MSRPC calls to the LWIOD on just one node at a time, which as you've indicated is very hit and miss.
So at the CLI, you could do something like this:
isi_for_array -s "isi smb openfiles list"
Here is my output on an empty and idle cluster:
isilon3-1: ID Path
isilon3-1: -------
isilon3-1: -------
isilon3-1: Total: 0
isilon3-2: ID Path
isilon3-2: -------
isilon3-2: -------
isilon3-2: Total: 0
isilon3-3: ID Path
isilon3-3: -------
isilon3-3: -------
isilon3-3: Total: 0
isi_for_array = runs the command on every node
(-s switch) = runs the command in a serial manner, 1 node at a time, get all those responses then move to the next node. This is slower than without the -s switch, however the results are easier to interpret.
Hope this helps:
~Chris
Marco951
1 Rookie
•
2 Posts
0
July 10th, 2017 09:00
Thank you, that makes sense to me. I'll go through the CLI instead.