Comments on: Remote Network (and More!) Management via the Command-Line http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line.html Big, Honkin' Systems Stuff Mon, 09 Jan 2012 19:19:37 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: systemsboy http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line.html/comment-page-1#comment-3643 systemsboy Thu, 05 Jan 2012 22:11:12 +0000 http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line/#comment-3643 Well, there's no way to change just the IP using networksetup. Also, you can't batch send a different command to multiple machines. That's kind of the opposite of what ARD is for. So I don't think you can do this exactly the way you're thinking. There may be scripting options in the form of lists and for loops that could get the job done, but they'd probably be pretty ugly. -systemsboy Well, there’s no way to change just the IP using networksetup. Also, you can’t batch send a different command to multiple machines. That’s kind of the opposite of what ARD is for. So I don’t think you can do this exactly the way you’re thinking. There may be scripting options in the form of lists and for loops that could get the job done, but they’d probably be pretty ugly.

-systemsboy

]]> By: Dave http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line.html/comment-page-1#comment-3642 Dave Thu, 05 Jan 2012 20:27:36 +0000 http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line/#comment-3642 How do I change just the IP? I want t select a group of computers in ard and send a unix command to change their ip in sequence so computer#1 would be 192.168.1.2 and computer#2 192.168.1.3 and so on How do I change just the IP? I want t select a group of computers in ard and send a unix command to change their ip in sequence so computer#1 would be 192.168.1.2 and computer#2 192.168.1.3 and so on

]]> By: systemsboy http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line.html/comment-page-1#comment-388 systemsboy Tue, 04 Jul 2006 19:42:00 +0000 http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line/#comment-388 Yes, changing DNS can have unintended effects, especially on servers, and especially if those servers are Mac OS X Servers which have some serious DNS dependencies. I've been learning a whole lot about DNS lately. If there's one thing I've realized it's that setting DNS up properly on your network at the outset is extremely important and makes life so much easier. Again, particularly before building servers. Without it, stuff just won't work right.<br/><br/>Anyway, glad you found success with networksetup.<br/><br/>-systemsboy Yes, changing DNS can have unintended effects, especially on servers, and especially if those servers are Mac OS X Servers which have some serious DNS dependencies. I’ve been learning a whole lot about DNS lately. If there’s one thing I’ve realized it’s that setting DNS up properly on your network at the outset is extremely important and makes life so much easier. Again, particularly before building servers. Without it, stuff just won’t work right.

Anyway, glad you found success with networksetup.

-systemsboy

]]> By: matx http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line.html/comment-page-1#comment-387 matx Tue, 04 Jul 2006 05:10:00 +0000 http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line/#comment-387 finally got a good opportunity to use 'networksetup' as I had to change to DNS info on all the machines in the entire place. worked like a charm, except on the Xserves and the Quads, it's "networksetup -setdnsservers Built-in\ Ethernet\ 1" but two batches of Send Unix command in ARD3 and voila. Though on another note changing DNS can have some funny effects everywhere. So many things depend on it, e.g. Xsan, Render apps, etc finally got a good opportunity to use ‘networksetup’ as I had to change to DNS info on all the machines in the entire place. worked like a charm, except on the Xserves and the Quads, it’s “networksetup -setdnsservers Built-in\ Ethernet\ 1″ but two batches of Send Unix command in ARD3 and voila. Though on another note changing DNS can have some funny effects everywhere. So many things depend on it, e.g. Xsan, Render apps, etc

]]> By: systemsboy http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line.html/comment-page-1#comment-386 systemsboy Wed, 21 Jun 2006 15:06:00 +0000 http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line/#comment-386 No, that wouldn't really work. With networksetup you have to specify a specific network interface — in this case "Built-In Ethernet" or "en0" — and you have to specify IP, Subnet and Router addresses for that interface, in that order. So if you want to change the Router setting, but not the IP Address you need to insert some variable in the command that returns the current IP Address of the system in question in place of the IP Address in the command.<br/><br/>It seems to me like it would be fairly common to want to change a router address across a whole bunch of machines, but leave the IP Address alone, as IP Addresses are generally unique to machines, whereas Router addresses are generally not. So yeah, I do sort of have issues with it. It's not a big deal, and I can work around it. I just wish I didn't have to. If the command were better thought out, I wouldn't.<br/><br/>-systemsboy No, that wouldn’t really work. With networksetup you have to specify a specific network interface — in this case “Built-In Ethernet” or “en0″ — and you have to specify IP, Subnet and Router addresses for that interface, in that order. So if you want to change the Router setting, but not the IP Address you need to insert some variable in the command that returns the current IP Address of the system in question in place of the IP Address in the command.

It seems to me like it would be fairly common to want to change a router address across a whole bunch of machines, but leave the IP Address alone, as IP Addresses are generally unique to machines, whereas Router addresses are generally not. So yeah, I do sort of have issues with it. It’s not a big deal, and I can work around it. I just wish I didn’t have to. If the command were better thought out, I wouldn’t.

-systemsboy

]]> By: Michael http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line.html/comment-page-1#comment-385 Michael Wed, 21 Jun 2006 13:51:00 +0000 http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line/#comment-385 I'm not near a mac right now so I can't get at a manpage for networksetup, but it would seem that if you have issues with this command setting the IP address of an interface at the same time as it sets the default route you could let it set lo0 to 127.0.0.1, no harm to doing that on as many boxen as it wants. I’m not near a mac right now so I can’t get at a manpage for networksetup, but it would seem that if you have issues with this command setting the IP address of an interface at the same time as it sets the default route you could let it set lo0 to 127.0.0.1, no harm to doing that on as many boxen as it wants.

]]> By: systemsboy http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line.html/comment-page-1#comment-384 systemsboy Tue, 13 Jun 2006 05:50:00 +0000 http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line/#comment-384 Actually, that looks like a good article. Seems to focus more on the systemsetup bits I left out. I wasn't familiar at all with kickstart.<br/><br/>Yeah, like I said: This post's more a reminder to me 'cause every time I need to use those commands I end up having to look up their location on the 'net. For that reason, I'm quite painfully aware that this is covered many other places. It's just nice to have the reference handy on my own site so I don't have to go hunting, 'cause, you know, I'm lazy. Plus, writing it out helps me remember.<br/><br/>Thanks for the link, though. Could be useful some day.<br/><br/>For whatever reason, I never use /etc/profile. I guess I just learned about .bash_profile first and was never terribly comfortable altering that stuff system-wide. I have added some paths in my .bash_profile. Mostly folders full of commands though (like /Developer/Tools). If it's just a command or two, I usually do aliases. Not sure why. I guess I'm weird.<br/><br/>Cheers!<br/><br/>-systemsboy Actually, that looks like a good article. Seems to focus more on the systemsetup bits I left out. I wasn’t familiar at all with kickstart.

Yeah, like I said: This post’s more a reminder to me ’cause every time I need to use those commands I end up having to look up their location on the ‘net. For that reason, I’m quite painfully aware that this is covered many other places. It’s just nice to have the reference handy on my own site so I don’t have to go hunting, ’cause, you know, I’m lazy. Plus, writing it out helps me remember.

Thanks for the link, though. Could be useful some day.

For whatever reason, I never use /etc/profile. I guess I just learned about .bash_profile first and was never terribly comfortable altering that stuff system-wide. I have added some paths in my .bash_profile. Mostly folders full of commands though (like /Developer/Tools). If it’s just a command or two, I usually do aliases. Not sure why. I guess I’m weird.

Cheers!

-systemsboy

]]> By: matx http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line.html/comment-page-1#comment-383 matx Tue, 13 Jun 2006 00:08:00 +0000 http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line/#comment-383 oh yeah, one more thing: i guess it's a personal taste kind of thing, but instead of the alias you could just put that directory in your path, so that you could call those commands buried in there. Add em in /etc/profile or elsewhere as needed. oh yeah, one more thing: i guess it’s a personal taste kind of thing, but instead of the alias you could just put that directory in your path, so that you could call those commands buried in there. Add em in /etc/profile or elsewhere as needed.

]]> By: matx http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line.html/comment-page-1#comment-382 matx Tue, 13 Jun 2006 00:06:00 +0000 http://systemsboy.com/2006/06/remote-network-and-more-management-via-the-command-line/#comment-382 Welch covered this topic back in Feb 06, Check it out: http://www.bynkii.com/archives/2006/02/some_command_line_tips_for_app.html Welch covered this topic back in Feb 06, Check it out: http://www.bynkii.com/archives/2006/02/some_command_line_tips_for_app.html

]]>