01-15-2013
Quote:
Originally Posted by
hicksd8
So if you connect a serial console and power the whole box up from cold (ie, all volts removed and reconnected) can you see the ILOM (a Linux appliance) boot up on the console? Should take quite a long time whilst all the diags run.
Yes, I was afraid that would be your suggestion. I'll update this thread when I have more details.
10 More Discussions You Might Find Interesting
1. HP-UX
Here's a difficult one for you.
I am on HPUX 11.0. I have a hung port, it is stuck in FIN_WAIT_2. Short of rebooting, how can I terminate the connection the system thinks still exists? I found a script online that uses adb but have not been able to get it to work. I am still open to using... (6 Replies)
Discussion started by: TioTony
6 Replies
2. Solaris
Hello, I'm trying to fix this server System Board (CPU/Memory Unit). The error indicates that its missing 3.3VDC. So far all the fuses and caps have been checked. I new at this type of machine, need help for idea on this system. Thank you in advance.
Vu (0 Replies)
Discussion started by: vhtran
0 Replies
3. Solaris
Hi all ,
I am trying to install solaris 9 on E2900 that is connect to a 3320 SCSI storage , The issue is that i want to have the SCSI disks(3320) to start with controllers 1 and 2 ( c1t0 ....c2t0) and my 2 local disks on c3 and c4 .
Is there a way that i could accomplish that ...
Thanks... (3 Replies)
Discussion started by: ppass
3 Replies
4. Solaris
Hi men,
Have you ever meet this error ?
I install full Sun MC 4.0 packages (+ Add ons) exception of Sun Midrange Platform Administration because i don't know how to configure it
Then all other servers are ok, only E2900 servers have Config reader module error: Data Acquisition error
I... (12 Replies)
Discussion started by: tien86
12 Replies
5. HP-UX
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies
6. Solaris
Dear Friends,
Sun Fire E2900 crashed. I collected explorer output. core dump files been generated.
There some interesting output files related to crash dumps, that I need some help from you guys to understand.
The file in the explorer output is under /sysconfig/crash it's called:... (5 Replies)
Discussion started by: Sun Fire
5 Replies
7. Solaris
Hi,
I am fairly new to Solaris , i have an e2900 server which gives the following output on the console:
Fri Sep 23 08:20:57 noname.example.com lom: /N0/SB0 : F
ailed AR interconnect test. Status = 00060040
Fri Sep 23 08:21:00 noname.example.com lom: AR Intercon
nect test: System board... (7 Replies)
Discussion started by: steve_b72
7 Replies
8. Emergency UNIX and Linux Support
Hi,
I have a scheduled activity to reboot E2900 server. But suddenly I came to know that console ip is not pinging, not connecting via telnet, as it used to connect. I already checked with my onsite person and he changed cable, still no luck. Network person checked his switch, which is showing... (8 Replies)
Discussion started by: solaris_1977
8 Replies
9. Solaris
What would you think is a reasonable useful lifespan for a Sunfire e2900. I'm not referring to it's performance capabilities as much as I'm referring to the hardware's ability to perform reliably. (2 Replies)
Discussion started by: DustinT
2 Replies
10. Solaris
several newbie questions:
> how-to find serialnumber for Sun E2900
prtdiag -v does not show chassis serial number
> LOM is not connectable .
Are there any tools to get automatically Serial numbers for HW.
Thanks ! (7 Replies)
Discussion started by: magedfawzy
7 Replies
LEARN ABOUT OSF1
port_names
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)