Sponsored Content
Operating Systems Solaris Any hope for this bootlooping Sun V210? Post 303026446 by gull04 on Wednesday 28th of November 2018 04:03:48 AM
Old 11-28-2018
Hi,

Having had a quick look through the logs that you've posted - I suspect that the ALOM has the issue!

Although it's a long shot here, the system should disable any faulty FRU's and allow you to login over the network. This presumes that the system is set to do that and that the faulty FRU has some redundancy.

You can then use the eeprom command to change the console output to TTYB (10101 on the rear panel) using eeprom setenv input-device ttyb where you should see the ok prompt you may also have to set the console as well.

Regards

Gull04
 

7 More Discussions You Might Find Interesting

1. Solaris

Sun Fire v210 display card

hi all, how can install a display card on a sun fire v210. regards. marcel (2 Replies)
Discussion started by: marcelious
2 Replies

2. Solaris

V210 to V440

I recently acquired a server for home use. Currently, I'm running a V210. I was wondering of a way to basically swap hard drives into the V440. I would like to avoid reinstall on the V440 for many reasons. Currently on the V440, when I try to boot up it forces itself into System Maintenance... (1 Reply)
Discussion started by: adelsin
1 Replies

3. Solaris

V210 to V440

I'm currently trying to move a perfectly find harddrive from a V210 to a V440. From what I can tell, the disk labeling a bit different, (V210 is c1t0d0 and V440 is c0t0d0). My question is, what all do I have to change to get the V440 to boot off of this with very little complications. Right now, it... (21 Replies)
Discussion started by: adelsin
21 Replies

4. Solaris

Booting error in Sun V210

Sun Fire V210, No Keyboard Copyright 1998-2003 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.13.2, 4096 MB memory installed, Serial #61203679. Ethernet address 0:3:ba:a5:e4:df, Host ID: 83a5e4df. Boot device: net File and args: 100 Mbps FDX Link up Timeout waiting for... (5 Replies)
Discussion started by: Mrudhul
5 Replies

5. Solaris

Connect using ALOM to Sun Fire V210

I have bought from eBay a second hand Sun Fire V210 server and I'm really stumped at the lack of complete instructions on how to connect to it. I don't have a Windows machine, I've only got Ubuntu and OS X computers. None of them have an old RS-232 port on them either. In saying that, I have... (12 Replies)
Discussion started by: danijeljames
12 Replies

6. UNIX for Dummies Questions & Answers

New to Forum & Sun Surefire V210 Access

Purchased a Sun Surefire V210 Server off eBay. Unable to Access the Terminal Mode via the Terminal MGT. Using Windows 7 home, and downloaded the ConEmu. The ConEmu brings up a Command line on the PC, and that's it. Being new to all this, I was expecting a Login prompt to pop up. Read the... (22 Replies)
Discussion started by: screenprintr
22 Replies

7. Solaris

Sun Fire V210 CPU Fan Temp too high?

Hey, I have a V210 with a failed CPU fan. The temperature is currently at 84C and I've been asked to wait a few weeks before replacing as its a production system and it cant be shut down yet. Is it too hot? Do I risk killing the CPU at this temp? Its been like this for a few weeks now... (5 Replies)
Discussion started by: magarvo
5 Replies
consadm(1m)						  System Administration Commands					       consadm(1m)

NAME
consadm - select or display devices used as auxiliary console devices SYNOPSIS
/usr/sbin/consadm /usr/sbin/consadm [-a device...] [-p] /usr/sbin/consadm [-d device...] [-p] /usr/sbin/consadm [-p] DESCRIPTION
consadm selects the hardware device or devices to be used as auxiliary console devices, or displays the current device. Only superusers are allowed to make or display auxiliary console device selections. Auxiliary console devices receive copies of console messages, and can be used as the console during single user mode. In particular, they receive kernel messages and messages directed to /dev/sysmsg. On Solaris x86 based systems they can also be used for interaction with the bootstrap. By default, selecting a display device to be used as an auxiliary console device selects that device for the duration the system remains up. If the administrator needs the selection to persist across reboots the -p option can be specified. consadm runs a daemon in the background, monitoring auxiliary console devices. Any devices that are disconnected (hang up, lose carrier) are removed from the auxiliary console device list, though not from the persistent list. While auxiliary console devices may have been removed from the device list receiving copies of console messages, those messages will always continue to be displayed by the default con- sole device. The daemon will not run if it finds there are not any auxiliary devices configured to monitor. Likewise, after the last auxiliary console is removed, the daemon will shut itself down. Therefore the daemon persists for only as long as auxiliary console devices remain active. See eeprom(1M) for instructions on assigning an auxiliary console device as the system console. OPTIONS
The following options are supported: -a device Adds device to the list of auxiliary console devices. Specify device as the path name to the device or devices to be added to the auxiliary console device list. -d device Removes device from the list of auxiliary console devices. Specify device as the path name to the device or devices to be removed from the auxiliary console device list. -p Prints the list of auxiliary consoles that will be auxiliary across reboots. When invoked with the -a or -d options , tells the application to make the change persist across reboot. EXAMPLES
Example 1: Adding to the list of devices that will receive console messages The following command adds /dev/term/a to the list of devices that will receive console messages. example# consadm -a /dev/term/a Example 2: Removing from the list of devices that will receive console messages The following command removes /dev/term/a from the list of devices that will receive console messages. This includes removal from the per- sistent list. example# consadm -d -p /dev/term/a Example 3: Printing the list of devices selected as auxiliary console devices The following command prints the name or names of the device or devices currently selected as auxiliary console devices. example# consadm ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of consadm: LC_CTYPE, LC_MESSAGES, and NLSPATH. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ |ATTRIBUTE TYPE |ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Stability Level |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), eeprom(1M), svcadm(1M), syslogd(1M), kadb(1M), environ(5), attributes(5), smf(5), sysmsg(7d), console(7d) NOTES
Auxiliary console devices are not usable for kadb or firmware I/O, do not receive panic messages, and do not receive output directed to /dev/console. The consadm service is managed by the service management facility, smf(5), under the service identifier: svc:/system/consadm Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. SunOS 5.10 27 Oct 2004 consadm(1m)
All times are GMT -4. The time now is 03:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy