Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Networker\]\s+identifying\s+storage\s+nodes\s+and\s+their\s+clients\.\s*$/: 7 ]

Total 7 documents matching your query.

1. [Networker] identifying storage nodes and their clients. (score: 1)
Author: Brian Greenberg <bgreenberg AT GLASSHOUSE DOT COM>
Date: Tue, 12 Jul 2005 10:56:04 -0400
Does anyone have a shell script that would generate a report of all the storage nodes on an nsr server and all the clients for that storagenode that I could easily import into excel? I'm having a hec
/usr/local/webapp/mharc-adsm.org/html/Networker/2005-07/msg00077.html (12,435 bytes)

2. Re: [Networker] identifying storage nodes and their clients. (score: 1)
Author: Darren Dunham <ddunham AT TAOS DOT COM>
Date: Tue, 12 Jul 2005 09:54:13 -0700
Nsradmin is pretty simple once you figure out what you want to see and where the data is stored. For instance, the client mapping to storage nodes appears to be in the client resource. So we'd need
/usr/local/webapp/mharc-adsm.org/html/Networker/2005-07/msg00080.html (13,216 bytes)

3. Re: [Networker] identifying storage nodes and their clients. (score: 1)
Author: "Brian J. Greenberg" <bgreenberg AT GLASSHOUSE DOT COM>
Date: Tue, 12 Jul 2005 13:32:30 -0400
That is a good start but that's where I kinda already was. I'm trying to get the data in reverse so there'd be a listing kinda like this: sn1 client1 client2 client3 sn2 client4 client5 Brian bjgreen
/usr/local/webapp/mharc-adsm.org/html/Networker/2005-07/msg00081.html (12,032 bytes)

4. Re: [Networker] identifying storage nodes and their clients. (score: 1)
Author: Darren Dunham <ddunham AT TAOS DOT COM>
Date: Tue, 12 Jul 2005 11:00:11 -0700
Well, you were asking about the nsradmin part. If you've got that, you're done there. It can't give you information it doesn't have. The rest is up to you. In this case, I don't believe it maintains
/usr/local/webapp/mharc-adsm.org/html/Networker/2005-07/msg00082.html (13,690 bytes)

5. Re: [Networker] identifying storage nodes and their clients. (score: 1)
Author: Davina Treiber <Treiber AT HOTPOP DOT COM>
Date: Wed, 13 Jul 2005 14:02:56 +0100
Here's a pretty simple no frills script to do this. It's flawed slightly because the client-storage node relationship is many to many, and this scripts works on the assumption that you will only have
/usr/local/webapp/mharc-adsm.org/html/Networker/2005-07/msg00094.html (13,567 bytes)

6. Re: [Networker] identifying storage nodes and their clients. (score: 1)
Author: "Brian J. Greenberg" <bgreenberg AT GLASSHOUSE DOT COM>
Date: Mon, 18 Jul 2005 18:00:10 -0400
This script is so close. I have a many to many relationship for storage nodes and clients. For example, the output of the nsradmin script: echo " show name; storage nodes print type: NSR client " | n
/usr/local/webapp/mharc-adsm.org/html/Networker/2005-07/msg00139.html (14,820 bytes)

7. Re: [Networker] identifying storage nodes and their clients. (score: 1)
Author: Tim Mooney <mooney AT DOGBERT.CC.NDSU.NODAK DOT EDU>
Date: Tue, 19 Jul 2005 14:19:40 -0500
In regard to: Re: [Networker] identifying storage nodes and their clients.,...: This script is so close. I have a many to many relationship for storage nodes and clients. For example, the output of t
/usr/local/webapp/mharc-adsm.org/html/Networker/2005-07/msg00155.html (16,169 bytes)


This search system is powered by Namazu