Sponsored Content
Operating Systems Solaris strange issue with ALOM in t51... Post 302289902 by upengan78 on Friday 20th of February 2009 05:16:55 PM
Old 02-20-2009
strange issue with ALOM in t51...

Hi ,

running solaris 10 on t5120 and i see ILOM and ALOM (SC) interfaces working fine earlier and suddenly they are responding strangely,

First thing , I can connect fine to ILOM or ALOM but then console -f just hangs..

resetsc error :
Quote:
Daemons ready

Sun(TM) Integrated Lights Out Manager

Version 2.0.4.19

Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.

sc> resetsc
Are you sure you want to reset the SC (y/n)? n

sc> resetsc
Are you sure you want to reset the SC (y/n)? y
Performing hard reset on the SC failed
resetsc: No such inventory

sc>

I do not really want to poweroff and poweron this system at this moment,

is there any solution or is this a known issue?

showenvironment command hung aswell. the user has rights of everything in ALOM.

Any ideas , if needed I can try more commands...

if there is no solution other than rebooting or power cycle? then how can I do it safely ? I can access server using ssh and physcially if needed.

Thanks
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Strange Number comparison issue

Hi, I am comparing two numbers, but it gives strange results: My Code: if then echo "True" else echo "False" fi This code gives False for the follwoing comparison where as True for the following: Any reason for this? Both Should have given False... I am using... (9 Replies)
Discussion started by: shihabvk
9 Replies

2. UNIX for Dummies Questions & Answers

Strange issue

I have created a server monitor program in Java that connects to servers via SSH and constantly refreshes the new server load every 3 mins. The problem is that even though it is a Java app running shell commands to get the load info, the commands still appear in 'history'. The question is.. is... (1 Reply)
Discussion started by: AndrewSH
1 Replies

3. UNIX for Advanced & Expert Users

strange aunthentication issue with email

hi again i'm running a centos 4.x box with sendmail and openwebmail. I had a weird situation where users couldn't not get authenticated using a pop mail client but but were able to aunthenticate using the openwebmail webmail client. I looked through the logs and didn't see anything strange. I... (0 Replies)
Discussion started by: mcraul
0 Replies

4. Web Development

Strange Mysql issue

Hi all, I recently changed the name of my hostname from 'abc123' to 'abc456' (as an example). I then added a user in my mysql database with the new host and removed references to the old users and hostname. The strange thing is though, a process using the database still uses the old... (1 Reply)
Discussion started by: muay_tb
1 Replies

5. AIX

strange route issue in powerha 5.4?

hi all we upgraded hacmp(powerha) from 5.2 to 5.4 recently . during the failover testing, we found a strange network issue. after standby node took service ip address (172.15.100.8) online at standby NIC, we were able to log in the standby node by telnet 172.15.100.8 which stays at... (1 Reply)
Discussion started by: rs6000er
1 Replies

6. Solaris

Difference b/n ALOM and ALOM CMT

Hi Everyone. What is the differece b/n ALOM and ALOM CMT Service processor. I am trying reset ALOM login/passwd using scadm utility on T2000, while I am googling I came cross ALOM CMT doesnt support scadm utility, but ALOM supports. Not sure how different are these. Thanks, (0 Replies)
Discussion started by: bobby320
0 Replies

7. Solaris

Remote managemnt - looking at hardware issue (using ALOM ) Server rebooting

Hi we have A sun4v SPARC Enterprise T2000 It has started to go down frequently without producing any corefiles. There is nothing in the logs to induicate any issues. So I'm trying to remotely check this and get to see if there are any hardware issue. I heard about ALOm and I think this is... (4 Replies)
Discussion started by: mnassiri
4 Replies

8. UNIX for Dummies Questions & Answers

Strange Keyboard and Mouse Issue

Hello All, PC: CuBox-i (*i.MX6) Mini-PC OS: openSUSE 13.1 (Bottle) (armv7hl) Kernel: 3.14.14-cubox-i # uname -a Linux CuBox-HQ 3.14.14-cubox-i #1 SMP Sat Sep 13 03:48:24 UTC 2014 armv7l armv7l armv7l GNU/LinuxSo I've been having this random issue happen on this PC where a few strange... (12 Replies)
Discussion started by: mrm5102
12 Replies

9. Shell Programming and Scripting

Strange Issue with sendmail

more works.sh #!/bin/ksh { print "From: reportgenerator@myserver.com" print "To: randomguy@myfirm.com" print "MIME-Version: 1.0" print "Content-Type: text/html" print "Subject: Disk Report" print "<body>" print "<table border=1>" ... (3 Replies)
Discussion started by: mohtashims
3 Replies

10. AIX

Strange issue installing Java 8

I just intalled java8_64.jre and .sdk respectively installp -agXYd . Java8_64.jre Java8_64.sdk 2>&1 | tee installp.log Worked like a champ. Now I see this-- jeff@server:/usr> ls -l | grep java drwxr-xr-x 9 bin bin 512 Sep 22 2010 java14 drwxr-xr-x 7 bin bin ... (9 Replies)
Discussion started by: jeffs42885
9 Replies
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)
All times are GMT -4. The time now is 12:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy