AnsweredAssumed Answered

Is there an "opposite" of asg_cp2blades?

Question asked by David Kozinn on Jul 30, 2018
Latest reply on Aug 10, 2018 by Alexander Wilke

On SP systems (e.g., 61000/41000) asg_cp2blades will allow you to copy a file from the current blade to any or all blades. I've been running some tcpdumps across all blades and the files are saving into /tmp. I want to bring them back to the SMO with modification to the filenames to indicate where it was pulled from, so this is sort of the opposite of what asg_cp2blades does. (Sort of: asg_cp2blades doesn't change the filename, which makes sense for what it does).

 

For my specific case I know what the filename is, so what I've been doing is to run this from the SMO:

 

g_all 'scp /tmp/capturefile0 192.0.2.1:/tmp/capturefile0.$HOSTNAME'

 

192.0.2.1 is the IP of the SMO that I'm running from, and /tmp/capturefile0 is the actual name of the captured file.

 

This works but it seems like perhaps there's a better way to do this. If I can help it, I don't want to put any executables on the other blades, though a local shell script would be OK.

 

Before I re-invent the wheel, does anyone have something that already does this?

 

Thanks.

Outcomes