Sponsored Content
Operating Systems Solaris sun 8 unable to communicate through console Post 302265889 by TonyFullerMalv on Monday 8th of December 2008 05:21:14 PM
Old 12-08-2008
If you can access your E450 over the network run:
$ eeprom | grep device
and ensure that input-device and output-device are set to ttya, or if you are using the serial port of a remote admin. (ILOM) card they may be set to rsc, they may be set to keyboard and display respectively if your server has a frame buffer (graphics card) in which the serial port will not be the console.
 

9 More Discussions You Might Find Interesting

1. Solaris

Hooking up to Console's on sun's

it there any docs out there anyhwre that have the specs for cabing to a sun console. I have an e420 here, i cant seem to get a console connection, i have triewd the silver serial connectors that come with the new dsun servers, but no luck with those. (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

2. HP-UX

Unable to login at console and telnet

Hi friend, I'm facing a problem to access the console and telnet to the HP ux 11 server due to the system file is full. How to access this server via single mode and how to mount the folder / and folder /var? thanks. vestro (1 Reply)
Discussion started by: vestro
1 Replies

3. Red Hat

unable to communicate with Linux machine

Hi all, I installed red hat 2.6.9-5 and when I am trying to ping it.I am able to ping any other machine in the network but unable to do vice-versa(means unable to ping this machine from any other machine) and getting the message -- please provide your valuable suggestions ... (2 Replies)
Discussion started by: smartgupta
2 Replies

4. Infrastructure Monitoring

unable to load console info in SUNMC 4.0

hi all, unable to load console info in SUNMC 4.0 in alarm it is giving error info i.e..Agent on host (.....),1161 port not responding. plz try to solve the problem Regards spandhan (5 Replies)
Discussion started by: spandhan
5 Replies

5. Solaris

unable to load console info in SUNMC 4.0

Hi all, unable to load console info in SUNMC 4.0 in alarm it is giving error info i.e..Agent on host (.....),1161 port not responding. Iam using M9000 server solaris 10 plz try to solve the problem Regards spandhan (0 Replies)
Discussion started by: spandhan
0 Replies

6. Solaris

Sun Fire V890 - Unable to access RSC or Serial console

Hello Folks, I am having trouble to login to rsc or serial console of V890. The rsc2.2.3 has been configured with required parameters, resetrs and even rebooted. When serial port is connected to laptop, The hyper terminal does not get the console or POSt messages when the server is rebooting... (8 Replies)
Discussion started by: defflepord
8 Replies

7. AIX

P550 Unable to access Console

I have recently aquired the following machine: IBM,9113-550 Up until yesterday we could connect a dumb terminal to serial port 1 and get console login. However the dumb terminal died. We are now using a laptop with a null modem cable attached to serial port 1. This works perfectly for all of... (1 Reply)
Discussion started by: rsw7724
1 Replies

8. Solaris

Unable to take console

When trying to connect to console, I am getting the below error. plathwsvcd: Another instance is running. plathwsvcd: Another instance is running. plathwsvcd: Another instance is running. plathwsvcd: Another instance is running. INIT: Id "plhw" respawning too fast: disabled for 5 minutes ... (3 Replies)
Discussion started by: aksijain
3 Replies

9. Solaris

Unable to start webconsole:console

Here is issue... bash-3.00# svcs system/webconsole:console STATE STIME FMRI maintenance 1:15:54 svc:/system/webconsole:console bash-3.00# svcadm clear svc:/system/webconsole:console bash-3.00# svcs -a |grep /system/webconsole offline* 1:20:44... (0 Replies)
Discussion started by: lingeshwaran
0 Replies
ports(7)						 Miscellaneous Information Manual						  ports(7)

NAME
ports, port_names - Device (tty and lp) names for serial and parallel ports SYNOPSIS
Default Serial Ports: /dev/tty00 /dev/tty01 (not present on a single-port system) Parallel Port: /dev/lp0 DESCRIPTION
AlphaStation and AlphaServer systems provide one or two 9-pin serial communication ports. These ports are usually labelled 1 (COMM1) and 2 (COMM2), but they may be identified by different icons. Using the appropriate serial cable and terminator, you can connect a serial printer, external modem, or character-cell terminal to a serial port. Most AlphaStation and AlphaServer systems also provide one parallel port, for use with a parallel printer. When you add a device to your system, the installation documentation may instruct you to map the device pathname to the port. These devices are located in the /dev directory. For serial-line ports, the two default device pathnames are: This pathname always maps to 1, COMM1, the lowest port number, an icon for a terminal console, or the only serial port (on a single-port system). This pathname always maps to 2, COMM2, the next numbered port, or (if one serial port is labeled with an icon for a terminal console) the remaining serial port. If your system hardware has been extended to include additional serial ports, the pathnames /dev/tty02, /dev/tty03, and so forth, may also be available to you. However, most systems have only /dev/tty00 and /dev/tty01 as the device pathnames for serial ports. The one parallel port on an AlphaStation or AlphaServer may be labeled with the word printer or a printer icon. On some systems, the paral- lel port may not be labeled. The device pathname for the parallel port is /dev/lp0. Currently, Tru64 UNIX does not fully support parallel printers, so fewer devices are connected to this port as compared to serial ports. If you are connecting a terminal console to your system, it must be connected to the serial port mapped to /dev/tty00. For other serial devices, it does not matter which of the serial ports you choose for the connection. For example, suppose you are setting up a system that has two serial ports, labeled 1 and 2. You intend to use a serial-line terminal rather than a workstation monitor as the system console and also want to connect a serial-line printer to the system. In this case, you must connect the terminal to the port labeled 1 (with the device pathname /dev/tty00). Therefore, you must connect the printer to the remaining port labeled 2 (with the device pathname /dev/tty01). If, for the same type of system, you intend to use a workstation monitor as the system console, it does not matter which serial port you use for a serial-line printer or modem. In other words, you can connect the printer to either port 1 (with pathname /dev/tty00) or port 2 (with pathname /dev/tty01). When prompted to enter a /dev/tty** pathname by the lprsetup script or the Print configuration tool in the CDE Application Manager, you would specify /dev/tty00 if you connected the printer to port 1 or /dev/tty01 if you connected the printer to port 2. See the System Administration manual for more information on setting up consoles (including remote consoles) and printers. See the modem(7) reference page for more information on setting up modems. SEE ALSO
Commands: lprsetup(8) Devices: ace(7), modem(7) System Administration delim off ports(7)
All times are GMT -4. The time now is 06:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy