|
|
Sponsored Content
Operating Systems
Solaris
Reset ILOM from cmd line
Post 302337230 by skamal4u on Thursday 23rd of July 2009 05:25:31 PM
07-23-2009
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I need to know if this command
echo NEWPASSWORD | passwd --stdin USERNAME
that works fine on Red Hat Linux, is also available on other Unix/Linux machines (AIX, FreeBSD, OpenBSD, SunOS, Mandrake, Debian, Gentoo, Lindows, Slackware, Xandros, HP-UX, IRIX, SCO, MacOS, BSDi ...).
... (2 Replies)
Discussion started by: margi973
2 Replies
2. Shell Programming and Scripting
hi
I'm trying to query a directory, check it's the right directory, return the results into a text file, put text file into an array and navigate the subdirectories and delete contents.
find `pwd` -type d | grep TESTINGDIR > dirList.txt
The txt file is created from the cmd-line but not in... (4 Replies)
Discussion started by: OFFSIHR
4 Replies
3. AIX
I have seen references in the forum about getting yesterday's date but it is either by changing something in the system (date, time zone, ...) or with more then one line of script cmds.
How can I get yesterday's date without changing anything in the system and in one single command line ? (4 Replies)
Discussion started by: Browser_ice
4 Replies
4. Shell Programming and Scripting
Hi everyone.
I am trying to develop my own shell,and i am in the part of redirection.
let's say the user gives as input
cat test > test2
in the array of arguments i want to keep only arg=cat,arg=test.
">" token is not an input file so cat cannot worka and test2 is output.how can i remove > and... (1 Reply)
Discussion started by: bashuser2
1 Replies
5. Shell Programming and Scripting
Folks,
I have a 3 problems. In a sh script, I call a server name from a list and rex to a distant machine to get the boot date.
for i in `cat list`
do
(echo "$i|"; /bin/rexsh $i -l bozo -t10 who -b | cut -d" " -f14-16) >>getBootTimes.out
sleep 1
done
The results are on 2 lines instead... (8 Replies)
Discussion started by: linux_lou
8 Replies
6. Programming
Hi, I want to be able to write a simple program that takes in input from the command line. I;m am at the level of getchar and putchar. Any examples would be a great help thanks.
I intend/prefer also to use the pipe command | eg: input | file1
---------- Post updated at 04:08 PM ----------... (4 Replies)
Discussion started by: metros
4 Replies
7. UNIX for Advanced & Expert Users
OK , ..
This is an odd one. I have a new server and I need to have a tunnel open to it.
I have this exact process running on a few others but this new one I just got is not allowing the script to connect.
I set up my users account and ssh keys
from the server that will host the tunneling i... (6 Replies)
Discussion started by: jeffsandman0035
6 Replies
8. Windows & DOS: Issues & Discussions
Hi All,
This command works when I type it on but when I run the batch file it doesn't..any ideas why?
attrib.exe * | find /c /v "" >filecount.txt (1 Reply)
Discussion started by: Grueben
1 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I am writing a little script to update a parameters on JMQ. however the JMQ requires a "y" confirmation to be input as part of the cmd I am running. However I want run this script to offline with no input from a user.
it works if a I create a file with with just y in it and pass that in... (3 Replies)
Discussion started by: shropshirehobbi
3 Replies
10. Shell Programming and Scripting
when i try the snippet in the console its working fine:
ps awwwux | grep php-fpm | grep -v grep | grep -v master | awk '{total_mem = $6 * 1024 + total_mem; total_proc++} END{printf("%d\n", total_mem / total_proc)}'
output:
but when i try the bash script:
#!/bin/sh
# -*- sh -*-
#... (3 Replies)
Discussion started by: danieloooo
3 Replies
LEARN ABOUT LINUX
powerman-devices
powerman-devices(7) powerman powerman-devices(7) NAME
powerman-devices - Powerman Device Configuration Notes DESCRIPTION
Following are notes on configuring various remote power controllers and related equipment supported by PowerMan. CYCLADES TS-1000 A cyclades TS-1000 configured so that PowerMan can connect to serial-port-based remote power control devices using telnet is set up as fol- lows: Attach console cable between laptop running minicom and console port at 9600,8n1 and authenticate with default account: root/tslinux. Edit the following files (assumes no off-subnet routing or name service required): /etc/portslave/portslave.conf conf.eth_ip 192.168.54.151 conf.eth_mask 255.255.255.0 conf.dhcp_client 0 # all.speed 9600 all.datasize 8 all.stopbits 1 all.parity none all.flow none all.dcd 0 all.DTR_reset 1 all.protocol socket_server all.authtype none #all.ipno all.socket_port 7001+ # s1.tty ttyS1 s2.tty ttyS2 s3.tty ttyS3 s4.tty ttyS4 s5.tty ttyS5 s6.tty ttyS6 s7.tty ttyS7 s8.tty ttyS8 s9.tty ttyS9 s10.tty ttyS10 s11.tty ttyS11 s12.tty ttyS12 s13.tty ttyS13 s14.tty ttyS14 s15.tty ttyS15 s16.tty ttyS16 /etc/hostname cyclades-ts-test /etc/hosts 127.0.0.1 localhost 192.168.54.151 cycaldes-ts-test Next, run signal_ras hup and saveconf and finally, power cycle the unit. It should be possible to configure PowerMan to connect to host- name:7001 for port 1, hostname:7002 for port 2, etc.. BAYTECH RPC-3 (non-NC models) (network port 23) Attach console cable between laptop running minicom and console port at 9600,8n1. Main menu should display. From main menu, select 3)...Configuration, then set IP parameters. From Configuration menu, select 5)...Access, then disable command confirmation, set admin password to baytech, and enable prompt for pass- word. Exit Access menu by typing return. From Configuration menu, select 6)...Outlets. Ensure that 1)...Outlet Status display is disabled, and 2)...Command Confirmation is dis- abled. Exit back to main menu by typing return twice, then answer Y to the Accept changes? prompt. BAYTECH RPC-28-NC (serial 9600,8n1) Attach console cable between laptop running minicom and console port at 9600,8n1. Type return to get RPC-28> prompt. Type Help for a list of commands. Select config. Select 3)...Enable/Disable Confirmation and disable confirmation. Select 4)...Enable/Disable Status Menu and disable sta- tus menu LNXI ICEBOX V2 (network port 1010) Attach console cable between laptop running minicom and console port at 9600,8n1. Enter default password of icebox. net ip 192.168.54.153 Sets IP address. net mask 255.255.255.0 Sets network mask net gw 192.168.54.254 Set default gateway. Note: this may need to be set to an address in the same subnet as the ice box regardless of whether it is to be used or not. reboot Reboots the icebox. LNXI ICEBOX V3 (network port 1010) Attach console cable between laptop running minicom and console port at 9600,8n1. Authenticate with default account admin/icebox. Config- uration is the same as the V2 ICE BOX. APC MASTERSWITCH MODEL AP9606 (network port 23) Attach console cable between laptop running minicom and console port (may be labeled ``advanced port'') at 2400,8n1. Press enter, then authenticate with default account apc/apc. Choose Network from main menu. Choose TCP/IP from Network menu, then diable BOOTP, and accept changes. Set the IP address, subnet mask, and default gateway, and accept changes. Pres ESC until the main menu appears, then select Logout. WTI RPS10 (serial 9600,8n1) Set address of box using the rotary dial on the back. The Master module must be set to address 0. Slave modules may be set to unique val- ues from 1-9. The address corresponds to the plug name in the powerman.conf file. Setup switches on each module should be set to 9600 baud (sw1 down), 5 sec toggle delay (sw2 down), power up to previous state (sw3 down). WTI NPS (network port 23) Attach console cable between laptop running minicom and console port at 9600,8n1. Try password "wti" if prompted. Select /N - View/set network parameters, then set the IP address, subnet mask, and gateway. Select /G - General paramters, then disable command confirmation, enable command echo, and set disconnect timeout to the maximum value (30 minutes). Set password to "wti". CYCLADES PM8 and PM8i (serial 9600,8n1) Attach console cable between laptop running minicom and serial port 9600,8n1. Press enter, then authenticate with default account admin/pm8. Run factory_defaults command. The PM8 can run in a mode where it can be daisy chained from a Cyclades terminal server. This mode is not yet supported by PowerMan. Sun ILOM The dedicated ILOM serial port (SER MGT RJ-45) runs at 9600,8n1 and the default login is root/changeme. Use a Sun/NETRA/Cisco RJ45 adapter to connect to Cyclades TS. The dedicated ILOM ethernet port (NET MGT RJ-45) can be configured for DHCP (the default) or static IP settings. To configure static IP via the ILOM serial port, run: cd /SP/network set pendingipdiscovery=static set pendingipaddress=xxx.xxx.xxx.xxx set pendingipnetmask=xxx.xxx.xxx.xxx set pendingipgateway=xxx.xxx.xxx.xxx set commitpending=true The ILOM network configuration can alternatively be set up via the system BIOS setup screen. Hit F2 during boot to access BIOS setup, go to the "Advanced" tab, select "IPMI 2.0 configuration" and "set LAN configuration". Make your changes and commit them. IPMI (via Ipmipower) IPMI based power control is supported via FreeIPMI's ipmipower. It is configured by running ipmipower in coprocess mode in powerman.conf Due to semantic differences between IPMI and traditional remote power control devices, some power control operations may not seem to work properly by default with Powerman. For example, several IPMI power control operations are allowed to return prior to the operation fully completing. A machine that has been powered off by IPMI may be later queried as being powered on. This is because IPMI may successfully return from a power off operation to the user, but the machine may elect to power itself off at a later time. In order to get around sev- eral of these issues, it is recommended that the user configure ipmipower with the --wait-until-on and --wait-until-off options. With these options set, ipmipower will behave more like traditional remote power control devices. In order to hide IPMI usernames and passwords from ps(1), it is also recommended that the user configure the username and password (and at your discretion, the above options) using the FreeIPMI configuration file and not in the powerman.conf file. Please see the ipmipower sec- tion of the freeipmi.conf(5) manpage for more information. Because IPMI usernames and passwords are sensitive, the default FreeIPMI configuration file is only readable and writable by root. This may conflict with the default powermand daemon settings, thus making the configuration file non-readable. Administrators may wish to run the powermand daemon as root or adjust the configuration file permissions as needed. HP iLO The "hpilo" script supports the Integrated Lights-Out management processor in HP ProLiant servers, including both rack-mount and blade servers. Configure the iLO to allow Telnet access on port 23, and add a user "Admin" with password "Admin". You may have to reduce the minimum password length on the Administration/Access/Options tab of the web interface. HP MP
The "hpmp" script supports the Management Processor in HP non-cellular, rack-mount Integrity servers. Configure the MP to allow Telnet access with the "CM:SA" command, and make sure there's a user "Admin" with password "Admin". If the MP enforces a minimum password length, you may have to use "uc -all default" to restore the default Admin/Admin user. HP MP (cellular) The "hpmpcell" script supports the Management Processor in HP mid-range cellular servers. Configure the MP to allow Telnet access with the "CM:SA" command, and make sure there's a user "Admin" with password "Admin". HP MP (Superdome) The "hpmpdome" script supports the Management Processor in HP Superdome servers. Configure the MP to allow Telnet access with the "CM:SA" command, and make sure there's a user "Admin" with password "Admin". HP MP (Integrity blades) The "hpmpblade" script supports the Management Processor in HP Integrity blade servers. Configure the MP to allow Telnet access with the "CM:SA" command, and make sure there's a user "Admin" with password "Admin". ORIGIN
PowerMan was originally developed by Andrew Uselton on LLNL's Linux clusters. This software is open source and distributed under the terms of the GNU GPL. SEE ALSO
powerman(1), powermand(8), httppower(8), plmpower(8), vpcd(8), powerman.conf(5), powerman.dev(5), powerman-devices(7). http://sourceforge.net/projects/powerman powerman-2.3.5 2009-02-09 powerman-devices(7)