Sponsored Content
Operating Systems Solaris Installing OpenSolaris on Sun v120 Post 302298842 by TonyFullerMalv on Wednesday 18th of March 2009 06:10:48 PM
Old 03-18-2009
If the "console" command does not give you a response from the LOM try moving your serial cable to the TTYA port (first serial port), the console might be using that instead.

An inherited machine can be "fun" to try and gain access to!
 

5 More Discussions You Might Find Interesting

1. Solaris

Weird behavior on a Sun Fire V120 running solaris 10.

All, After a power loss I went to power on our sun fire v120 that is running solaris 10 and now it will not boot. I tried power cycling it from the lom and pulling the cord but nothing works. All it does is after a power cycle it will start to boot and then start to spit out a bunch of hex... (2 Replies)
Discussion started by: jsandova
2 Replies

2. Solaris

Help - Accessing Sun Fire V120 A/LOM

Hi All, My company has three V120 servers and two V245 servers. Currently we access ALOM on v245 thru NET MGT port. There are no NET MGT on V120. We use to access A/LOM on the V120s thru Windows Hyper Terminal connected to the Serial A port of v120. Since all of our Windows boxed are... (6 Replies)
Discussion started by: glieu
6 Replies

3. Solaris

Sun Fire v120 memory compatibility

Hi, I recently acquired an old Sun Fire v120 from work. I plan to play around with this at home whilst I'm studying for my SCSA exams. Only problem is it currently has no memory installed. I believe the memory modules required are 168 pin PC133 DIMMs. Unfortunately, the original Sun modules are... (3 Replies)
Discussion started by: skinyana
3 Replies

4. Solaris

Error while installing zone in opensolaris

while installing zone this error is coming zoneadm -z test install ERROR: Error: no zonepath dataset. Steps done to create one sample zone zonecfg -z test create set zonepath=/zones/test set autoboot=true verify commit exit zoneadm -z test install ERROR: Error: no zonepath dataset.... (9 Replies)
Discussion started by: vijaysachin
9 Replies

5. Solaris

Clone Production Server (Sun v120)

It's a DHCP server. We want to make a clone for fail over purpose since there are some identical systems available here. We do have a secondary DHCP server. Hardware: Sun v120. OS: Solaris 9. Two disks without array, /var and /opt on the secondary disk. How can I clone the system via network... (1 Reply)
Discussion started by: aixlover
1 Replies
ace(7)							 Miscellaneous Information Manual						    ace(7)

NAME
ace - Serial communications interface SYNOPSIS
controller ace0 at * slot ? vector aceintr DESCRIPTION
The ace serial line controller provides a serial communications interface on DEC 2000, AlphaStation, and AlphaServer platforms. The serial communications ports that are controlled by ace adhere to the RS-232 standard and can operate at rates from 50 to 115200 baud (see tty(7)). These communications ports support serial-line printers, modems, and terminals. In alternate console configurations (that is, no graphics head), the terminal to be the system console must be connected to the port that is mapped to /dev/tty00. (See ports(7) for information about mapping AlphaStation and AlphaServer port labels to device pathnames.) Cur- rently, some processors that use the ace driver limit the serial console port to 9600 baud, 8-bit, no parity and no modem support. However, some processor consoles do support baud rates other than 9600 baud and allow the use of modems as console devices. Consult your hardware documentation to determine the type of console support your system provides. The driver for the ace interface supports hardware flow control using the Request to Send (RTS) and Clear to Send (CTS) signals. When hardware flow control is enabled, the flow of input data is controlled by the RTS signal and the flow of output data is controlled by the CTS signal. If the CTS signal is off, the driver suspends output to that line until the CTS lead is reasserted. Likewise the driver turns off the RTS lead to tell the device connected to the line to stop sending data as a result of congestion on the host side. When the condi- tion clears, the driver turns on the RTS lead to tell the device to resume sending data. The DCD (carrier detect) timer value defaults to 2 seconds. This value may be changed if your modem hardware requires a different value. the change can be made in the /etc/sysconfigtab file as follows: ace: dcd_timer=n where n is the time interval in seconds, and can be set to 0 (no timeout), 1, or 2 seconds. Alternatively, you can use the sysconfig com- mand to set the same time interval option as follows: # sysconfig -r ace dcd_timer=[n] If you use the sysconfig command, the value will not be preserved when the system is rebooted. To preserve the setting, put the entry in the /etc/sysconfigtab file NOTES
If you are using the alternate system console to perform kernel debugging, you must change the kdebug entry in the /etc/remote file to use /dev/tty01; when the kernel is running in debugging mode, no other application can use the port. See Kernel Debugging for information on setting up your system for kernel debugging. RESTRICTIONS
Unless alternative specifications are stated in your system hardware documentation, data communications equipment attached to the console serial port in alternate console configurations must be set to 9600 baud, 8-bits, no parity. If a serial console is being used, /dev/tty00 cannot be opened by another process. The ace driver enforces this restriction. Baud rates greater than 38400 are not supported on the two primary serial ports on the DEC 2000 system. However, if you use an ISA serial or modem card that is capable of communicating at the higher rates, the higher rates are supported. FILES
console terminal local terminal local terminal RELATED INFORMATION
MAKEDEV(8), console(7), devio(7), modem(7), ports(7), tty(7) Kernel Debugging System Administration delim off ace(7)
All times are GMT -4. The time now is 06:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy