Sponsored Content
Operating Systems Solaris Sun 6800 - SC's- neither are contactable! Post 302303878 by 1jnike on Friday 3rd of April 2009 06:02:32 PM
Old 04-03-2009
Quote:
Originally Posted by sbk1972

Thanks for the reply. The terminal Concentrator (TC) is like a laptop, as it connects to the serial port, like you would a laptop + serial cable. This allows you two doorways into the SC.

SBK
Hi sbk1972,

I should have made my self clear, using a laptop is to confirm the terminal Server is in fact operational. If you can use a laptop or dumb terminal connected directly in the SF6800 serial port you should be provided with a SC prompt.

This is assuming you have power feeding the SF6800 platform. The domains may be down or unconfigured, but you should still be presented with the system control prompt if directly attached to the main SC or slave sc.

I hope this is of help.

Jnike
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Help: Sun Disk partitioning for Sun V240 & StorEdge 3300

Dear Sun gurus, I have Sun Fire V240 server with its StorEdge 3300 disk-array. Following are its disks appeared in format command. I have prepared its partitions thru format and metainit & metattach (may be i have made wrong steps, causing the errors below because I have done thru some document... (1 Reply)
Discussion started by: shafeeq
1 Replies

2. UNIX for Dummies Questions & Answers

Sun Solaris 10: How do I create a bootup disc? The Sun website confuses me

Hey there, I am starting a Computer Science Foundation year at the end of this month and am trying to get a little bit ahead of the game. I have always wanted to learn Unix and am currently struggling with creating a boot disc to run Solaris (I have chosen to study this) from as opposed to... (0 Replies)
Discussion started by: Jupiter
0 Replies

3. Solaris

Sunfire 6800 / sol 8 / scadm

Good morning all Once again, I come seeking wisdom :-) I have a sunfire 6800 with two domains. Both Sc controllers are uncontactabe, probably due to network issues, but as the server is on a different site, Im a little stuck. So, am trying to use scadm, as I know I can view / configure... (7 Replies)
Discussion started by: sbk1972
7 Replies

4. Solaris

Sun Fire 280R Sun Solaris CRT/Monitor requirements

I am new to Sun. I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor? Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies

5. Solaris

d240 media tray is automatically restarting on sunfire 6800

d240 media tray(domain C) is which is connected to SUNFIRE 6800 (DOMAIN C),automatically restarting.remaining domains A and B are working fine..why i dont know..with out human intervention this domain is restarting automatically for 3 to 4 days in a day..plz solve this problem.why like this going... (4 Replies)
Discussion started by: tv.praveenkumar
4 Replies

6. Solaris

Application running too slow on Sun SPARC T5440 but run normal on sun M3000

Hi all, I have application running on sun server T5440 4x8x1.4 GHz, 64 GB RAM, application running very slow though load average too low. when I install my application on another server SUN M3000 (One CPU 1x8x2.5GHz, 8GB RAM), application run smoothly. Here is my server T5440 info: ... (6 Replies)
Discussion started by: insatiable1610
6 Replies
DMESG(1)							   User Commands							  DMESG(1)

NAME
dmesg - print or control the kernel ring buffer SYNOPSIS
dmesg [options] dmesg --clear dmesg --read-clear [options] dmesg --console-level level dmesg --console-on dmesg --console-off DESCRIPTION
dmesg is used to examine or control the kernel ring buffer. The default action is to read all messages from kernel ring buffer. OPTIONS
The --clear, --read-clear, --console-on, --console-off and --console-level options are mutually exclusive. -C, --clear Clear the ring buffer. -c, --read-clear Clear the ring buffer contents after printing. -D, --console-off Disable printing messages to the console. -d, --show-delta Display the timestamp and time delta spent between messages. If used together with --notime then only the time delta without the timestamp is printed. -e, --reltime Display the local time and delta in human readable format. -E, --console-on Enable printing messages to the console. -F, --file file Read log from file. -f, --facility list Restrict output to defined (comma separated) list of facilities. For example dmesg --facility=daemon will print messages from system daemons only. For all supported facilities see dmesg --help output. -H, --human Enable human readable output. See also --color, --reltime and --nopager. -h, --help Print a help text and exit. -k, --kernel Print kernel messages. -L, --color Colorize important messages. -l, --level list Restrict output to defined (comma separated) list of levels. For example dmesg --level=err,warn will print error and warning messages only. For all supported levels see dmesg --help output. -n, --console-level level Set the level at which logging of messages is done to the console. The level is a level number or abbreviation of the level name. For all supported levels see dmesg --help output. For example, -n 1 or -n alert prevents all messages, except emergency (panic) messages, from appearing on the console. All levels of messages are still written to /proc/kmsg, so syslogd(8) can still be used to control exactly where kernel messages appear. When the -n option is used, dmesg will not print or clear the kernel ring buffer. -P, --nopager Do not pipe output into a pager, the pager is enabled for --human output. -r, --raw Print the raw message buffer, i.e., do not strip the log level prefixes. Note that the real raw format depends on method how dmesg(1) reads kernel messages. The /dev/kmsg uses different format than sys- log(2). For backward compatibility dmesg(1) returns data always in syslog(2) format. The real raw data from /dev/kmsg is possible to read for example by command 'dd if=/dev/kmsg iflag=nonblock'. -S, --syslog Force to use syslog(2) kernel interface to read kernel messages. The default is to use /dev/kmsg rather than syslog(2) since kernel 3.5.0. -s, --buffer-size size Use a buffer of size to query the kernel ring buffer. This is 16392 by default. (The default kernel syslog buffer size was 4096 at first, 8192 since 1.3.54, 16384 since 2.1.113.) If you have set the kernel buffer to be larger than the default then this option can be used to view the entire buffer. -T, --ctime Print human readable timestamps. The timestamp could be inaccurate! The time source used for the logs is not updated after system SUSPEND/RESUME. -t, --notime Do not print kernel's timestamps. -u, --userspace Print userspace messages. -V, --version Output version information and exit. -w, --follow Wait for new messages. This feature is supported on systems with readable /dev/kmsg only (since kernel 3.5.0). -x, --decode Decode facility and level (priority) number to human readable prefixes. SEE ALSO
syslogd(8) AUTHORS
Karel Zak <kzak@redhat.com> Theodore Ts'o <tytso@athena.mit.edu> AVAILABILITY
The dmesg command is part of the util-linux package and is available from Linux Kernel Archive <ftp://ftp.kernel.org/pub/linux/utils/util- linux/>. util-linux July 2012 DMESG(1)
All times are GMT -4. The time now is 01:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy