07-16-2014
Server wipe tool for AIX and Linux
Hi Friends,
I am looking for a opensource/inbuilt server wipe tools similar to DBAN for the server decommissions.
I have several AIX and Linux machines to decom as part of datacenter shutdowns. But these 'DOESNT' have console access and I need to do the wipe remotely. Can you please suggest me some tools for it. I know the challenge here is the 'no console' part.
As per company standards full OS wipe is required.
Thanks in advance
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a .sh script which was running fine on all the UNIX Servers (AIX, SunSolaris). The script requires two mandatory parameters and many optional parameters. Now at a different client place who are on a Windows Server, when I try to execute the script through MKS Toolkit, there are couple of... (5 Replies)
Discussion started by: madhunk
5 Replies
2. Fedora
Hi,
Is it possible to install Linux on an AIX server?
Is there any doc available with anyone for installation? Please help. (1 Reply)
Discussion started by: dwiravi
1 Replies
3. AIX
Hi,
I am a newbie to AIX. We have 2 AIX5.3 servers in our environment, I need to transfer some files in Binary mode from one server to another and some files in ASCII mode from one server to another server. Could you please help me as to how I need to do that?
Thanks,
Rakesh (4 Replies)
Discussion started by: rakeshc.apps
4 Replies
4. AIX
Guy's
AIX Monitoring Tool - under preparing .....
I'm working to make and prepare tool to monitor AIX system and my idea it's based on the following outputs
I want command to give me shout outpous about the following ...
CPU load
Memory load
Used load
Number of... (5 Replies)
Discussion started by: Mr.AIX
5 Replies
5. Red Hat
Hi,
Can anyone help me on migration the print server from AIX to RHEL 4?
Appreciate your help? (1 Reply)
Discussion started by: brby07
1 Replies
6. AIX
Hi,
I am trying to mount a nfs folder from AIX client to Linux NFS Server, but I got the following error:
# mount 128.127.11.121:/aix /to_be_del
mount: 1831-010 server 128.127.11.121 not responding: RPC: 1832-018 Port mapper
failure - RPC: 1832-008 Timed out
mount: retrying... (1 Reply)
Discussion started by: victorcheung
1 Replies
7. HP-UX
Hi,
Please suggest wipe tool for hp-ux. (2 Replies)
Discussion started by: manoj.solaris
2 Replies
8. AIX
Hello everybody,
Please let me know if there are any free C profiling tool for AIX environment
Thanks in advance (0 Replies)
Discussion started by: SteAlma
0 Replies
9. AIX
Hi,
is any one using nagios monitoring solution on AIX ? if yes, is it supported on AIX 7.1 TL 03 as well ?
I tried to search online and unix.com , could not find it.
Thank you (5 Replies)
Discussion started by: aaron8667
5 Replies
10. AIX
Hi folks,
How can i configure an AIX LDAP client to authenticate against an Linux Openldap server over TLS/SSL?
It works like a charm without TLS/SSL.
i would like to have SSL encrypted communication for ldap (secldapclntd) and ldapsearch etc. while accepting every kind of certificate/CA.... (6 Replies)
Discussion started by: paco699
6 Replies
LEARN ABOUT REDHAT
lamgrow
LAMGROW(1) LAM COMMANDS LAMGROW(1)
NAME
lamgrow - Extend a LAM multicomputer.
SYNTAX
lamgrow [-hv] [-c <bhost>] [-u <userid>] [<node>] <hostname>
OPTIONS
-h Print useful information on this command.
-c <bhost> Update this boot schema.
-v Be verbose.
<hostname> Extend LAM with this host.
<node> Assign this ID to the new node.
-u <userid> Use this userid to access the new host.
DESCRIPTION
An existing LAM session, initiated by lamboot(1), can be enlarged to include more nodes with lamgrow. One new node is added for each invo-
cation. At a minimum, the host name that will run the new node is given on the command line. If a different userid is required to access
the host, it is specified with the -u option.
It can be useful to update the original boot schema used by lamboot(1) with the new node added by lamgrow. The -c option specifies a boot
schema filename and causes lamgrow to append the host name. The updated boot schema is ready to be used by wipe(1) to terminate the ex-
tended LAM session. New nodes added by lamgrow will not be cleaned up by wipe(1) if the original boot schema is used. They can be termi-
nated individually, as always, with tkill(1).
The new node can be assigned any unused, non-negative identifier. If no identifier is specified, the highest node identifier in the cur-
rent LAM session plus one is used. Note that lamboot(1) always assigns node identifiers consecutively from 0.
lamgrow can be run from any node. As a LAM command program it must be run from a node in the existing LAM session. It cannot be run from
the intended new host. Two invocations of lamgrow should not run concurrently and the command attempts to detect this situation. There is
no protection against specifying the name of host that is already part of the user's existing LAM session. This is not the proper use of
lamgrow.
Resource managers will be the most common user of lamgrow. When hosts become idle and a user has expressed a desire to the manager that
extra cycles should be exploited, the manager could invoke lamgrow and then launch the specified application process(es) on the new node.
EXAMPLES
lamgrow -v newhost
Start LAM on newhost and add it to the existing LAM session. Choose the next available node identifier and report about important
steps as they are done.
lamgrow n30 newhost
Start LAM on newhost with node ID 30 and add it to the existing LAM session. Operate silently.
FILES
$LAMHOME/etc/lam-conf.lam default configuration file for LAM nodes
SEE ALSO
lamboot(1), hboot(1), wipe(1), tkill(1), bhost(5), conf(5)
LAM 6.5.8 November, 2002 LAMGROW(1)