From kkkong at ee.cuhk.edu.hk  Fri Nov  2 04:37:03 2007
From: kkkong at ee.cuhk.edu.hk (Alan Kong)
Date: Fri, 02 Nov 2007 17:37:03 +0800
Subject: Summary : Use of Partition 2 in partition table
Message-ID: <472AEFBF.8040803@ee.cuhk.edu.hk>

Hi,
Thank you to all the responses:
Roberto Fratelli <robertofratelli at yahoo.com>
Elliot Moore <elliot at devnull.org.uk>
"Sengor ." <sengork at gmail.com>
Chris Hoogendyk <hoogendyk at bio.umass.edu>
"Brad Heck" <bradandmarcia at gmail.com>
Edward Scown <eascown3 at yahoo.com>
Don Ratliff <ddratliff at yahoo.com>
"Bill R. Williams" <brw at etsu.edu>
"Coronel, David" <David.Coronel at melochemonnex.com>
"Truhn, Chad" <Chad.Truhn at argonst.com>
Ric Anderson <ric at Opus1.COM>
"Romeo Theriault" <romeotheriault at gmail.com>
peter winterflood <peter.winterflood at ossi.co.uk>
Sunmanagers Mailing List <sunmanagers at schelin.org>
inemes <inemes at iinet.net.au>
"Matthew Stier" <Matthew.Stier at us.fujitsu.com>
Rich Kulawiec <rsk at gsp.org>
<peter.van.gemert at accenture.com>
hike <mh1272 at gmail.com>

Some say "yes" and some say "no". But I agree that it is better to stick
to the traditional as most system admins expect the S2 is the whole disk
and is the "overlay" in Solaris.
Furthermore, a lot responded that some application will fail if s2 is
not the whole disk.
Sun also recommends s2 as the whole disk.

Regards
Alan

--- Alan Kong <kkkong at ee.cuhk.edu.hk> wrote:

> Hi,
> Partition 2 is usually used for backup in Solaris.
> Can I partition for 
> normal file systems? I searched Google and could not
> find much info. on 
> usage of this backup partition.
> 
> 
> Thank you.
> 
> Regards
> Alan
> _______________________________________________
> sunmanagers mailing list
> sunmanagers at sunmanagers.org
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From nskyrca at syr.edu  Fri Nov  2 09:28:20 2007
From: nskyrca at syr.edu (Nicole Skyrca)
Date: Fri, 2 Nov 2007 10:28:20 -0400
Subject: SUMMARY: Solaris 10 jumpstart question - boot server and
	install serveron different machines
In-Reply-To: <3039115F5F6550468E498DBC85F2EC54F460EA@SUEXCL-01.ad.syr.edu>
Message-ID: <3039115F5F6550468E498DBC85F2EC54F461E6@SUEXCL-01.ad.syr.edu>

Hello,
I am not sure exactly what was causing my jumpstart problems. I had a
few suggestions that the subnet mask might be getting set wrong and thus
causing the problem.

We are moving to a new jumpstart server, and the machine that I setup as
a boot server is our old jumpstart server. The old jumpstart server has
multiple network interfaces on it.  One is on the subnet of my client,
and one is on the same subnet as the new jumpstart server.   Someone
made the suggestion that perhaps the client was locking onto the server
that provided the RARP reply, and expected the bootparams information
from there as well.

I ended up creating another boot server on the same subnet as my client.
This boot server only has one interface. This worked- I boot from the
new boot server and get the sysidcfg and install information from the
install server.

Thank you all for your help.
Nicole

-----Original Message-----
From: sunmanagers-bounces at sunmanagers.org
[mailto:sunmanagers-bounces at sunmanagers.org] On Behalf Of Nicole Skyrca
Sent: Monday, October 22, 2007 4:42 PM
To: sunmanagers at sunmanagers.org
Subject: Solaris 10 jumpstart question - boot server and install
serveron different machines

Hi,

I am trying to jumpstart a Sunblade 2000 with Solaris 10.  The jumpstart
install server is on a different subnet than my sunblade, so I created a
boot server on the same subnet.


When I try "boot net -s", it hangs after the following lines:



Using RPC bootparams for network configuration information.

Attempting to configure interface eri0...

Configured interface eri0

/



At this point, I stop seeing traffic in snoop on my boot server, but I
never see anything in snoop on my install server.  I have never done a
jumpstart where the boot and install server were different servers.
This is my /etc/bootparams file entry. Is this correct for a boot
server?



builder4.syr.edu
root=data-4:/export/os-cd/5.10-0606/Solaris_10/Tools/Boot \

install=ncwis03:/export/os-cd/5.10
install_config=ncwis03:/export/install/5.10 \

sysid_config=ncwis03:/export/install/5.10/sysidcfg-local/subnet4 \

boottype=:in rootopts=:rsize=32768 term=:sun
ns=data-4:nis(255.255.255.0)



Any suggestions?



Thanks,

Nicole





Nicole Skyrca

Information Technology Analyst

Syracuse University

207 Machinery Hall

Syracuse, New York 13244

315-443-5310
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From romeotheriault at gmail.com  Fri Nov  2 10:59:49 2007
From: romeotheriault at gmail.com (Romeo Theriault)
Date: Fri, 2 Nov 2007 11:59:49 -0400
Subject: SUMMARY: rscadm lock file
Message-ID: <46cd475b0711020859l2eb3b20eme6474e4285b44b21@mail.gmail.com>

Thank you very much to the following people for pointing me in the correct
direction.

Saxon Stuart
Peter Winterflood
Francisco Puente

See Original Question at bottom of mail.

The suggestion that they all pointed me at was to truss the command to find
where the lock file was, and that indeed showed me where the lock file was.
It was /tmp/RSCLockFile.txt   . See below.

Here is what I did:

# truss ./rscadm help

execve("../../SUNW,Sun-Fire-280R/rsc/rscadm", 0xFFBFFD14, 0xFFBFFD20)  argc
= 2
resolvepath("/usr/lib/ld.so.1", "/usr/lib/ld.so.1", 1023) = 16
open(".", O_RDONLY|O_LARGEFILE)                 = 3
fstat64(3, 0xFFBFF400)                          = 0
close(3)                                        = 0
<snip bunch of output>

open("/tmp/RSCLockFile.txt", O_WRONLY|O_CREAT|O_EXCL, 0666) Err#17 EEXIST
nanosleep(0xFFBFFAF0, 0xFFBFFAE8)               = 0
open("/tmp/RSCLockFile.txt", O_WRONLY|O_CREAT|O_EXCL, 0666) Err#17 EEXIST
nanosleep(0xFFBFFAF0, 0xFFBFFAE8)               = 0
open("/tmp/RSCLockFile.txt", O_WRONLY|O_CREAT|O_EXCL, 0666) Err#17 EEXIST
nanosleep(0xFFBFFAF0, 0xFFBFFAE8) (sleeping...)
nanosleep(0xFFBFFAF0, 0xFFBFFAE8)               = 0
open("/tmp/RSCLockFile.txt", O_WRONLY|O_CREAT|O_EXCL, 0666) Err#17 EEXIST
open("/tmp/RSCLockFile.txt", O_RDONLY)          = 3




Original question: "I'm replacing an admin who didn't leave their passwords
for the servers ALOM (System Controllers). So far I've been able to reset
the SC passwords on the machines through the scadm or rscadm commands,
depending on the server type. But on one machine (Sun-Fire-880) when I try
to reset the SC password with the rscadm command or do anything with the
rscadm command for that matter I get this error:

# ./rscadm help

rscadm: The RSC lock file was found. Only one
        instance of rscadm can run at a given time

I've read the System Controller documentation and they mention this error
but they don't tell you where the lock file is or how to get rid of it. I've
done a pretty thorough search for the lock file and can't seem to find it.

Anyone know where the lock file is kept for this or how I might be able to
handle this?"


-- 
Romeo Theriault
<romeo.theriault at maine.edu>
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From aharrison at gmail.com  Fri Nov  2 13:59:28 2007
From: aharrison at gmail.com (Andy Harrison)
Date: Fri, 2 Nov 2007 14:59:28 -0400
Subject: SUMMARY: OT: Sun Type 7 keyboard and Linux
Message-ID: <a22ff2940711021159h28068462wc36944d601736679@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I just inadvertently figured out this issue of  pressing the
sleep/suspend (moon) button on my sun type 7 keyboard and having it
shut the machine down without a confirmation dialog.

In KDE, go to Configure Desktop -> Display -> Power Control tab ->
Configure KPowersave -> General Settings tab -> Button Events

I changed the selection for Power Button, problem solved.

- --
Andy Harrison
public key: 0x67518262
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHK3OpNTm8fWdRgmIRAlDyAJwIi4Y16tki/lbT/N0AZ4RR1jJCgQCgvEo3
lx4iraUqqR6uvmgQyX/sPrk=
=Wlm5
-----END PGP SIGNATURE-----
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From ashish.madhavan at gmail.com  Mon Nov  5 02:23:52 2007
From: ashish.madhavan at gmail.com (Ashish Madhavan)
Date: Mon, 5 Nov 2007 12:53:52 +0530
Subject: Summary: Labelling many emc disks together?
Message-ID: <56e4df110711042323g509c66aen76e510e743614751@mail.gmail.com>

Hi All,

  Thanks for all your replies.... Darren's mail about using "format -f" did
the trick. I wrote a small "for" loop around

format -s -f /tmp/cmd diskname

where /tmp/cmd contained:
label
quit

It took around 10hrs for the 1000+ disks to get labelled though :)

regards,
Ashish
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From presslaber at ips.at  Mon Nov  5 06:40:36 2007
From: presslaber at ips.at (=?ISO-8859-15?Q?Martin_Pre=DFlaber?=)
Date: Mon, 05 Nov 2007 12:40:36 +0100
Subject: [SUMMARY] SunCluster File System Performance (UFS/PxFS)
Message-ID: <472F0134.8020503@ips.at>

hi!

not many responses came on that question, but thanks to all that
answered...

special thanks to Brian Keith from Sun who forwarded my question directly
to Ellard Roush,
here's the answerer from Ellard, thank you Ellard ;)

""
I saw your query on SunManagers; I contacted Ellard Roush here at Sun for
you and here's his response to your query:

Parallel data bases, such as RAC, can benefit from more interconnect
bandwidth in some cases.

We do not run data bases on top of pxfs. For general purpose file system
work loads running on pxfs there is NO benefit to adding additional
interconnects. The limiting factor is CPU processing power. The
interconnect is not heavily stressed. I have not measured this recently.
But this has been true for many years.

Spend your money on more CPUs/memory.
""

best regards
- martin

[[QUESTION]]
i've read threw some articles about the Cluster FS Performance and how to
increase it, but still i am missing one simple answerer...

Does it help to increase the numbers of interconnects?

i found in the blueprint from Ellard Roush, 817-1593 "Cluster File System
Performance", that the client side cache has to make round trips across
the interconnect, PxFS checkpoints cross the interconnect and the
acknowledgements go threw... I found in an interconnect description that
data is striped across all available interconnects in a round-robin
fashion. So looking to the prices of gigabit copper ethernet cards
nowadays, it's no matter about money to increase the number of
interconnects like mr. roush mentioned in his blueprint in 2003... i
found a hint in my cluster-course training book "you can have more than
two that would be a performance benefit in certain circumstances ( <--
??? ), because global data access traffic is striped across all of the
transports"
so well, easy question, but i couldn't find any answerers.. does it
actually help to increase the throughput by adding additionally
interfaces?
[[QUESTION]]
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From warren.liang at cox.net  Thu Nov  8 18:38:31 2007
From: warren.liang at cox.net (Warren Liang)
Date: Thu, 8 Nov 2007 18:38:31 -0500
Subject: SUMMARY: flarcreate -x question
Message-ID: <20071108183831.29UN8.46377.root@fed1wml07.mgt.cox.net>

Hello:
Thanks for all responses. Here is a work around for flarcreate -x option under Solaris 8:
1. Make a copy of /etc/mnttab file. # cp /etc/mnttab /etc/mnttab.flar
2. Modify mnttab.flar, changes those file systems/directories you want to exclude from "ufs" to "autofs".
3. Modify /usr/sbin/flarcreate script. Change the 2 lines that define /etc/mnttab as input file to /etc/mnttab.flar.

Thanks.
Warren
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From ghenry at cmi.univ-mrs.fr  Fri Nov 16 12:39:35 2007
From: ghenry at cmi.univ-mrs.fr (Gerard Henry)
Date: Fri, 16 Nov 2007 18:39:35 +0100
Subject: SUMMARY: dhcpd in exclusive-IP zone
In-Reply-To: <4739D9B1.4010104@cmi.univ-mrs.fr>
References: <4739D9B1.4010104@cmi.univ-mrs.fr>
Message-ID: <473DD5D7.7010005@cmi.univ-mrs.fr>

thanks to crist Clark for giving me the solution:
first using truss to see exactly what's happen, and discover that ISC 
dhcpd tries to open /dev/e1000g that doesn't exist into the zone, and 
add it with:
zonecfg:dhcp> add device
zonecfg:dhcp:device> set match=/dev/e1000g
zonecfg:dhcp:device> end

For Sun dhcpd, i have to add this param:
zonecfg:dhcp> set limitpriv="default,net_rawaccess"

if you don't want to be annoyed by this problem:
[ Nov 14 11:19:35 Executing start method ("/usr/lib/inet/in.dhcpd") ]
svc.startd could not set context for method: setppriv: Not owner

hth,

here is my original post:
> i have a t2000 with S10 08/07 and want to dedicate a zone to dhcpd service.
> This zone was configured according to:
> http://docs.sun.com/app/docs/doc/819-2450/z.config.ov-1?a=view
> 
> t2000-root% zonecfg -z dhcp export
> ...
> set ip-type=exclusive
> ...
> add net
> set physical=e1000g2
> end
> ...
> 
> t2000-root% dladm show-link
> e1000g2         type: non-vlan  mtu: 1500       device: e1000g2
> 
> t2000-root% dladm show-linkprop
> LINK         PROPERTY        VALUE          DEFAULT        POSSIBLE 
> 
> e1000g2      zone            dhcp           --             -- 
> 
> 
> but when i launch the service:
> /opt/csw/sbin/dhcpd -cf /etc/dhcpd.conf -lf /etc/dhcpd.leases -q e1000g2
> 
> i got this error:
> Nov 13 17:59:53 mary dhcpd: Can't open DLPI device for e1000g2: No such 
> file or directory
> 
> 
> Any chance to have this working?
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From presslaber at ips.at  Fri Nov 16 13:09:08 2007
From: presslaber at ips.at (=?ISO-8859-15?Q?Martin_Pre=DFlaber?=)
Date: Fri, 16 Nov 2007 19:09:08 +0100
Subject: [[SUMMARY/UPDATE]] 3 node SunCluster vs. Disk-Suite Mediators
	[[CLARIFICATION]]
Message-ID: <473DDCC4.5040401@ips.at>

hi once again!

thanks for the answerers, but it seems that my question was not clear
enough... or noone uses metasets in a sun-cluster, but i don't think so
;)

I am not talking about the cluster-quorum devices, indeed you will need 2
disk quorum votes within a three node cluster to get a majority...

What I was talking about, are disk-suite, LVM / SVM metasets. If you
don't use VxVM or ZFS, you can use the metaset feature which comes from
the Solaris Volume Manager.. you can build meta-devices for shared-disks
inside a metaset; if you do so in a two node cluster, you will have to
define mediators for the metaset. In a mediator configuration, two hosts
are physically connected to two strings of drives. This configuration can
survive the failure of a single host or a single string of drives. A
mediator host running the rpc.metamedd daemon keeps track of replica
updates. And you get a mediator quorum...

so, what comes out reading the documentation is, that you will need
mediators only with Solaris Volume Manager disk sets that are configured
with exactly two disk strings and two cluster nodes.
more information:
http://docs.sun.com/app/docs/doc/819-2970/6n57ljhmv?a=view

tanks once again,
best regards,
- martin

[orig]
hi!

as far as i understood the mediators in metasets, you would only need
them in a two-node environment... i added a third node to a two node
cluster, he could join the exiting metasets but not the mediator list, so
am i right, in a three node configuration you can delete all mediators
from the set? the replica-quorum is only used with two nodes so you can
survive the failure of a single node, but what would happen if two nodes
dies, can the third one still access the set?

[[Env: 3x 4900, Sol10_u3, SC_3.1-u4, SAP/Oracle]]

thanks for your time!
regards
- martin
[/orig]
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From sun.mail.list at oryx.cc  Mon Nov 19 16:21:26 2007
From: sun.mail.list at oryx.cc (Jerry K)
Date: Mon, 19 Nov 2007 15:21:26 -0600
Subject: [SUMMARY] memory test on v490
Message-ID: <4741FE56.8030401@oryx.cc>

Thank you to the following for your replies:

Mehran Salehi @ Kodak
Kenneth Stevens @ Rent sys
Sanjaya Srivastava
hike ???
Chris Buesgens @ System Source Tech
-----------------------------------

The original question is at the bottom of this email:
----------------------------------------------------

The following are suggestions that were provided:
================================================

* For Solaris 10 they could use the fmadm utility. This utility is part 
of Solaris 10. No download needed.

* to read all the mem you can do  wc -c /dev/mem as root

* SUNWvts or drop down to OBP and set the diag switch to max

* cddiag tool - url here:
http://sunsolve.sun.com/search/document.do?assetkey=1-9-82264-1

Thank you for all of the input.

Jerry K


-------- Original Message --------
Subject: memory test on v490
Date: Mon, 19 Nov 2007 10:27:30 -0600
From: Jerry K
To: sunmanagers at sunmanagers.org

I have a Sun v490 server that generated a few soft ram errors over the
weekend.

My boss asked me if there was any way to test a memory stick from the OS
level, vs dropping down to the OBP, and coming back up with the max-diag
-level switch set.

Prior to this post, I did review the archives and do some Yahoo
searches.  I came up with a couple of utilities, primarily memconf and
SunVTS.  Memconf provides nice detail about your system ram, but does
not do any testing.  the Sun SunVTS appears that it will test all ram,
but I don't feel that from reading the documentation, that I can
exclusively test only a specific ram stick (i.e. memory module slot
J8203) using SunVTS.

I feel that probably the right answer is just to bring the system down
to the OBP and test there, but am curious if anyone else has other tools
for this task.

Thank for any replies, I will summarize.

Jerry K
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From Ian.Topham at Digica.com  Tue Nov 20 04:40:22 2007
From: Ian.Topham at Digica.com (Ian Topham)
Date: Tue, 20 Nov 2007 09:40:22 -0000
Subject: Summary  Solaris 10 8_07 iso download disk2
In-Reply-To: <D4F9316ACC9D20489CC81D19B8A87D5B07704C32@UKEX01.Digica.local>
Message-ID: <D4F9316ACC9D20489CC81D19B8A87D5B0779ACC5@UKEX01.Digica.local>

 All
	Thanks to those of you who replied (hike & Eric Deblon).
The problem appears to lie with the Perle CS9000 that we are using for
console access.
It is sending 2 carriage returns, so when the first prompt arrives, the
first <CR> answers the prompt, the second <CR> which arrives almost
immediately answers the next prompt, skips the newly inserted cd and
ejects it.
We're now sending a CTRL-M instead and trying to mend the CS9000 as
well.
Another alternative would be to insert the cd between the 2 <CR>'s, but
we're not quite that quick!;o}


Thanks - Ian

-----Original Message-----
From: sunmanagers-bounces at sunmanagers.org
[mailto:sunmanagers-bounces at sunmanagers.org] On Behalf Of Ian Topham
Sent: 19 November 2007 13:35
To: sunmanagers at sunmanagers.org
Subject: RE: Solaris 10 8_07 iso download disk2

All
	Further to my earlier post, I have downloaded the iso image
multiple times and burned the image to more than one cd, in case there
was any corruption in either the download or burn processes. Still
getting the same problem!
	I've also installed the earlier version (6_06) successfully
since I had this issue, which hopefully rules out the cd-rom as well.
The hardware is an e450, 3GB RAM, 3 x 400MHZ CPU.


Thanks - Ian

-----Original Message-----
From: sunmanagers-bounces at sunmanagers.org
[mailto:sunmanagers-bounces at sunmanagers.org] On Behalf Of Ian Topham
Sent: 19 November 2007 13:03
To: sunmanagers at sunmanagers.org
Subject: Solaris 10 8_07 iso download disk2

Hi gurus
    Has anyone had any problems with the Solaris 10 8_07 download disk 2
iso image?
I've downloaded the 5 iso images from the Sun site and burned them to
cd, booted from cd 1 and gone for the 'complete + oem support' option.
When it asks for disk 2, I've inserted it and pressed enter as
requested, but the system fails to read it, ejects the cd and prompts
for disk2 again.
The cd looks fine when viewed on another system, and the label appears
to be ok.
The reason for the installation at this level is that we have been
trying to build a container and zfs, but there appears to be something
missing in the earlier release we have (6_06) which we require.

Thanks - Ian


This email is confidential and may be privileged. If you are not the
intended recipient please notify the sender immediately and delete the
email from your
computer.  You should not copy the email, use it or               any
purpose
or disclose its contents to any other person. Please note that any views
or opinions presented in this email may be personal to the author and do
not necessarily represent the views or opinions of Digica. It is the
responsibility of the recipient to check this email for the presence of
viruses. Digica accepts no liability for any damage caused by any virus
transmitted by this email.

Digica Group Limited
Registered in England No. 5244928

Digica Limited
Registered in England No. 3434654

Digica (FMS) Limited
Registered in England No. 3798091

Registered address: Phoenix House, Colliers Way, Nottingham, NG8 6AT UK
Reception Tel: + 44 (0) 115 977 1177 Support Centre: 0845 607 7070
Fax: + 44 (0) 115 977 7000
http://www.digica.com

SOUTH AFRICA:  Building 3, Parc du Cap, Mispel Road, Bellville, 7535,
South Africa
Tel: + 27 (0) 21 957 4900
Fax: + 27 (0) 21 948 3135
http://www.digica.com

This message has been scanned for viruses by Surfcontrol in Partnership
with Digica _______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From Ian.Topham at Digica.com  Tue Nov 20 06:40:40 2007
From: Ian.Topham at Digica.com (Ian Topham)
Date: Tue, 20 Nov 2007 11:40:40 -0000
Subject: Summary  Solaris 10 8_07 iso download disk2 take #2
In-Reply-To: <D4F9316ACC9D20489CC81D19B8A87D5B0779ACC5@UKEX01.Digica.local>
Message-ID: <D4F9316ACC9D20489CC81D19B8A87D5B0779AE63@UKEX01.Digica.local>

All
	Turns out that PuTTY has a setting that will cause this problem.
In the Connection Telnet settings, there is a tick box that says 'Return
key sends Telnet New Line instead of ^M'.
Untick this, and lo and behold, the problem disappears.
I know it's a bit off-topic, but every little helps!!!


Thanks - Ian

-----Original Message-----
From: sunmanagers-bounces at sunmanagers.org
[mailto:sunmanagers-bounces at sunmanagers.org] On Behalf Of Ian Topham
Sent: 20 November 2007 09:40
To: sunmanagers at sunmanagers.org
Subject: Summary Solaris 10 8_07 iso download disk2

 All
	Thanks to those of you who replied (hike & Eric Deblon).
The problem appears to lie with the Perle CS9000 that we are using for
console access.
It is sending 2 carriage returns, so when the first prompt arrives, the
first <CR> answers the prompt, the second <CR> which arrives almost
immediately answers the next prompt, skips the newly inserted cd and
ejects it.
We're now sending a CTRL-M instead and trying to mend the CS9000 as
well.
Another alternative would be to insert the cd between the 2 <CR>'s, but
we're not quite that quick!;o}


Thanks - Ian

-----Original Message-----
From: sunmanagers-bounces at sunmanagers.org
[mailto:sunmanagers-bounces at sunmanagers.org] On Behalf Of Ian Topham
Sent: 19 November 2007 13:35
To: sunmanagers at sunmanagers.org
Subject: RE: Solaris 10 8_07 iso download disk2

All
	Further to my earlier post, I have downloaded the iso image
multiple times and burned the image to more than one cd, in case there
was any corruption in either the download or burn processes. Still
getting the same problem!
	I've also installed the earlier version (6_06) successfully
since I had this issue, which hopefully rules out the cd-rom as well.
The hardware is an e450, 3GB RAM, 3 x 400MHZ CPU.


Thanks - Ian

-----Original Message-----
From: sunmanagers-bounces at sunmanagers.org
[mailto:sunmanagers-bounces at sunmanagers.org] On Behalf Of Ian Topham
Sent: 19 November 2007 13:03
To: sunmanagers at sunmanagers.org
Subject: Solaris 10 8_07 iso download disk2

Hi gurus
    Has anyone had any problems with the Solaris 10 8_07 download disk 2
iso image?
I've downloaded the 5 iso images from the Sun site and burned them to
cd, booted from cd 1 and gone for the 'complete + oem support' option.
When it asks for disk 2, I've inserted it and pressed enter as
requested, but the system fails to read it, ejects the cd and prompts
for disk2 again.
The cd looks fine when viewed on another system, and the label appears
to be ok.
The reason for the installation at this level is that we have been
trying to build a container and zfs, but there appears to be something
missing in the earlier release we have (6_06) which we require.

Thanks - Ian


This email is confidential and may be privileged. If you are not the
intended recipient please notify the sender immediately and delete the
email from your
computer.  You should not copy the email, use it or               any
purpose
or disclose its contents to any other person. Please note that any views
or opinions presented in this email may be personal to the author and do
not necessarily represent the views or opinions of Digica. It is the
responsibility of the recipient to check this email for the presence of
viruses. Digica accepts no liability for any damage caused by any virus
transmitted by this email.

Digica Group Limited
Registered in England No. 5244928

Digica Limited
Registered in England No. 3434654

Digica (FMS) Limited
Registered in England No. 3798091

Registered address: Phoenix House, Colliers Way, Nottingham, NG8 6AT UK
Reception Tel: + 44 (0) 115 977 1177 Support Centre: 0845 607 7070
Fax: + 44 (0) 115 977 7000
http://www.digica.com

SOUTH AFRICA:  Building 3, Parc du Cap, Mispel Road, Bellville, 7535,
South Africa
Tel: + 27 (0) 21 957 4900
Fax: + 27 (0) 21 948 3135
http://www.digica.com

This message has been scanned for viruses by Surfcontrol in Partnership
with Digica _______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From kfosburg at hughes.net  Tue Nov 20 11:48:15 2007
From: kfosburg at hughes.net (Karl Fosburg)
Date: Tue, 20 Nov 2007 11:48:15 -0500
Subject: SUMMARY: V440 ce0 interface no link issue
In-Reply-To: <4728BA39.6080605@hughes.net>
References: <4728BA39.6080605@hughes.net>
Message-ID: <47430FCF.6090402@hughes.net>

Thanks for all the suggestions regarding this issue.

I have not been 100% able to verify that this problem is fixed due to 
the fact that the servers that always experience it are in production 
and we don't have a scheduled maintenance window that I can test with 
until 2008. However, on the systems I did test with that are not yet in 
production, the suggestions work fine.

If anything changes due to later testing, I will repost the summary.

Basically:

1. Use a /platform/sun4u/kernel/drv/ce.conf file instead of ndd to set 
up the interface
2. There is also the potential for an openboot firmware issue, but I 
have not investigated that yet
3. Don't mix auto/auto with hard wired (not applicable here, but good 
advice all the same!)

Thanks to:

Brad
Mike
David
Martin
Eugene
Markus
Joe
Hike
Hoang
and George

Regards,

Karl

Karl Fosburg wrote:
> Hi,
>
> I have had an issue with V440 servers for several years now regarding 
> bringing up the ce0 interface upon boot. Upon boot, the ce0 interface 
> never successfully comes up linked to its switch. We always hardwire the 
> interfaces to 100/Full duplex - same as the switch ports. The only fix 
> that ever works is physically unplugging the cat5 cable and re-inserting 
> it - then the link comes up right away. Also, we can down the switch 
> port and re-up it and it will come up.
>
> Down/Up'ing the interface using ifconfig does not work. 
> Unplumbing/plumbing it does not work.
>
> Applies to Solaris 8, 9, and 10 and only on V440's. Same ndd 
> configuration on other types of servers (v480/490/240) works fine.
>
> Anyone else seen this behavior and/or a fix?
>
> Thanks,
>
> Karl
> _______________________________________________
> sunmanagers mailing list
> sunmanagers at sunmanagers.org
> http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From stepchung at gmail.com  Tue Nov 20 13:47:31 2007
From: stepchung at gmail.com (Stephanie C)
Date: Tue, 20 Nov 2007 10:47:31 -0800
Subject: SUMMARY: Refuse to boot
Message-ID: <6bdfa8ce0711201047j5a0ae8ecp71e42aa5da9d9ee4@mail.gmail.com>

It turned out that the server (HP DL360) did not see the internal disk
when trying to boot. I googled and found out that HP DL360 needs a
third generation array controller driver 'QPQary3' in able to
reboot/install solaris 10 x86 on the server. I downloaded 'QPQary3'
from HP site. The only 2 options to install this driver: OS install
and select option 5 for driver installation; or install from root.
Since this server is bootable, I decided to do a fresh OS install of
Solaris 10 dated 6/06 DVD with HP array driver. The OS installed and
is up fine except it does not see the NIC card. During OS
installation, it never asked for IP address.

ifconfig -a : shows only lo0;  does not see ethernet card
dladm show-link: nothing return
sys-unconfig: server does not ask for IP when setup

How do I make this server recognize the NIC card.

Thanks.

Stephanie


I would like to verify this issue.
- The console screen turn blank screen during reboot. Console screen
does not respond.
- No error shows on the console screen.
- Can not access the server from console or remote.
- If 'failsafe' mode seleted, server reboot and get the # prompt.

Here are the recommendations from the list what to do from the # prompt:
- Check the error logs and messages.
- Restart all the services manually (svcadm)

I will try and let you know.

Any recommendations? Thanks.

Stephanie


Original message:

I am having a problem with re-booting the Dell DL380 Solaris 10 x86
after applying the latest patches via updatemanager. After all patches
were installed, the server would not re-boot. Since using the
updatemanager and selected all updates available, I do not know what
updates I installed on the system. I even power off/on few times.
Everytimes, in the middle of booting the console screen turned blank
and stay that way forever. During the re-boot if I select 'failsafe'
mode, I get the '#' prompt. I tried to reboot from the prompt, but the
server is acting the same blank screen. I don't know what is wrong and
how to get the server to completely boot up. Any help is appreciated.
Thanks.
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From stepchung at gmail.com  Thu Nov 22 00:12:41 2007
From: stepchung at gmail.com (Stephanie C)
Date: Wed, 21 Nov 2007 21:12:41 -0800
Subject: SUMMARY: Solaris NIC Network Issue
Message-ID: <6bdfa8ce0711212112y5409e304ye1b721b5433ec96d@mail.gmail.com>

Ok, It turned out the IP/Gateway/Netmask I was using is not working on
the solaris 10 x86. The odd thing was when configured this same
IP/Gateway/Netmask on Windows, it is working fine. He convinced me
that it is not IP problem. I forced the network guy provided me
another IP with different Vlan and I am happy camper now. Thanks for
your help.

Stephanie


Original question:

Hi again! The same server (HP DL360 - Solaris 10 x86) is giving me one
after another problem. I resolved the disk drive and NIC card by
installing HP drivers. The server installed Solaris 10 x86 with
Network configured fine. The server is up and running except that this
server is not accessible.  Only the direct console access at this
time. The NIC device is 'bnx0' that shows configured with IP address
and UP. I have checked all network configuration files that I could
think of: hosts, hostname.bnx0,  nsswitch.conf, resolv.conf,
defautdomain, defaultrouter, ipdodes, networks, netmasks All seems to
be fine with the IP and hostname correctly configured.  All the
networks services are online. 'bnx0' is plumbed and up.

Someone please tell me what am I missing here to make this server networked.

The only odd thing that if I configure 'bnx0' with DHCP instead of
configuring the static IP than the server is accessible fine from in
and out from DHCP IP address.

Thanks for your help!

Stephanie
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From sunmoon208 at yahoo.com  Fri Nov 23 17:17:18 2007
From: sunmoon208 at yahoo.com (B Bong)
Date: Fri, 23 Nov 2007 14:17:18 -0800 (PST)
Subject: SUMMARY: SAN setup and configuration
In-Reply-To: <FA47C50F78D148428B32580987E11F4102D8A1FC@MOR-MAILPRD.bvnet.bv>
Message-ID: <183470.61578.qm@web30406.mail.mud.yahoo.com>

Hi,

Thank you everyone for your reply. 

Here are the replies to pick up the SAN knowledge.

google san 
download admin books from EMC
powerlink.emc.com
emc.com/techlib
docs.sun.com/app/docs/doc/819-0139
look for SFS on docs.sun.com

Someone also suggest to invest on training and attend
courses. For large hardware purchase, usually it will
credits with training and also I should bundle some of
the training fees in the purchase budget.

Thanks.

Regards,
Tim


> -----Original Message-----
> From: sunmanagers-bounces at sunmanagers.org
> [mailto:sunmanagers-bounces at sunmanagers.org] On
> Behalf Of B Bong
> Sent: Tuesday, November 20, 2007 7:03 AM
> To: sunmanagers at sunmanagers.org
> Subject: SAN setup and configuration
> 
> Dear Sun Managers,
> 
> I have null knowledge on SAN but I'm familiar with
> Solaris. My company is going to purchase a emc SAN
> storage and i need to prepare myself to learn the
> SAN
> concept, how to setup the SAN disk from scratch. 
> 
> Would really appreciate if someone can share with me
> is there any good documents that i can fast track on
> my learning, any good URL and information that i can
> pickup this knowledge from.
> 
> Thanks in advance.
> 
> Regards,
> Tim
> 
> 
>  
>
________________________________________________________________________
> ____________
> Never miss a thing.  Make Yahoo your home page. 
> http://www.yahoo.com/r/hs
> _______________________________________________
> sunmanagers mailing list
> sunmanagers at sunmanagers.org
>
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
> 



      ____________________________________________________________________________________
Be a better sports nut!  Let your teams follow you 
with Yahoo Mobile. Try it now.  http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From mymaillists at gmx.at  Mon Nov 26 09:17:14 2007
From: mymaillists at gmx.at (Markus Mayer)
Date: Mon, 26 Nov 2007 15:17:14 +0100
Subject: SUMMARY: Sun Cluster 3.2, did devices over 100
In-Reply-To: <200711211347.09107.mymaillists@gmx.at>
References: <200711211347.09107.mymaillists@gmx.at>
Message-ID: <200711261517.14896.mymaillists@gmx.at>

Hi all,

Thanks for the responses, only three (Francisco Mauro Puente, Dean Ross-Smith,
Martin Pre_laber), but sufficient to help me find my way.

Dean pointed out the did manual page, where it mentions that did devices are
dynamically generated in groups of 100 at a time -  the next 100 are
generated only when there are more disks available to the cluster than there
are did devices, hence nothing over 100 for me.

Martin suggested setting the cluster back into install mode and configure the
hdlm so that it doesn't show any disks.

In the end, I got our storage admin to remove all disks from the cluster, I
rebooted, cleared the did device tree, got rid of all did devices, all
references to anything with the storage, rebooted, made sure everything was
cleaned of the hdlm devices and storage devices (wasn't, repeated the
cleaning successfully a seond time), reboot, disks from storage made
available again, reconfigured the hdlm, rebooted, reconfigured the did
devices, rebooted because the devices weren't immediately accessible, renamed
the did devices again with lower numbers, rebooted again, and now everything
seems to be at least partly ok.  Somehow I had that win... feeling.

It also seems there is some kind of bug with the hdlm that we are using.  It
rears it head with the message "No such device" when trying to access any
disk with format, although I can actually access, partition, and put file
systems on all the disks.  Lets see if this changes in a newer version of
hdlm.

Thanks and regards
Markus




On Wednesday 21 November 2007, Markus Mayer wrote:
> Hi all,
>
> I'm having a hard time with Sun Cluster 3.2 in a two node cluster.  We have
> a Hitachi AMS500 and HDLM 5.9.0.0, Solaris 10 update 3, all patches until
> the start of September installed.  I have 30 disks from the storage array
> made available, and to try to keep an overview of what disk came from which
> pool on the array and for what purpose it was, I renamed the did devices on
> the disks (eg: didadm -t d35:d101).  The renaming procedure went through
> without any problems, however since rebooting, I can do nothing with these
> did devices any more.  For example, the boot messages for one of these
> disks is: Nov 21 13:12:48 wombat Cluster.CCR: /usr/cluster/bin/scgdevs:
> Could not register disk
> Nov 21 13:12:48 wombat Cluster.CCR: /usr/cluster/bin/scgdevs: Could not
> stat /dev/global/dsk/d123s2:
> Nov 21 13:12:48 wombat Cluster.CCR: No such file or directory
>
> didadm -c or -R returns no errors, so it thinks everything is ok.
>
> I have tried everything I can think of to access the disks, or to remove
> them
>
> >from the device tree, to rename them again to device numbers under 100, to
>
> clean the did device tree, and so on, all with no success.  (didadm -C
> then -r, devfsadm -Cv, didadm -t d101:d35)
>
> I have examined the problem and seen that there are no did device entries
> (links) in /dev/did greater than d100, the devices go from did/d0 to
> did/d100, there is nothing for did/d101 and onwards.  The same applies
> in /devices/pseudo/did.  According to Sun documentation, these should
> however be dynamically generated.
>
> I cna see two possibilities here -
> 1. Find a way to get cluster to generate the missing device entries.
> 2. Find a way to remove all the problem entries and go back to something
> more conservative.
> So far I have not been able to find a way to do either of these.  I have
> considered the possibility of manually brutally deleting the troublesome
> entries, however I don't know what consequences this will have.
>
> I would be grateful to anyone who could point me in a direction to either
> get cluster to delete the troublesome entries and start again, or generate
> the missing entries.
>
> Thanks
> Markus
> _______________________________________________
> sunmanagers mailing list
> sunmanagers at sunmanagers.org
> http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From pandey.abhimanyu at gmail.com  Mon Nov 26 12:21:42 2007
From: pandey.abhimanyu at gmail.com (Abhimanyu Pandey)
Date: Mon, 26 Nov 2007 12:21:42 -0500
Subject: SUMMARY: /proc file system
Message-ID: <343bf320711260921y260afe6bxb803bb78a68b3e80@mail.gmail.com>

thank for those great replies.

i do understand it is a virtual mem space .  pointers to actual
processes in a crude sense.  however recently we had a system non
responsiveness issue and folks seem to point their fingers at the high
/proc space (2.7T).  I will look into the connection/response issue
further.

One last question:

Rebooting a system would clean up /proc.  Would this have any effect
on system performance.  I don't think so but would like some
confirmation.

regards,

abhimanyu.
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From rumbiles at yahoo.com  Wed Nov 28 05:43:59 2007
From: rumbiles at yahoo.com (rumbidzayi gadhula)
Date: Wed, 28 Nov 2007 02:43:59 -0800 (PST)
Subject: Summary: Slow inetd services
Message-ID: <571700.10895.qm@web54404.mail.yahoo.com>

A big thank you to John Stoffel, Steiner Peter, Ing., mehran.saleh and Don Ratliff fro pointing me in the right direction..

It seems my network card had problems. The server was getting very slow in starting the internet services. We then brought down the server, after which we noticed the NIC was down, performed a reconfigure boot when devfsadm failed to bring up the card and the card now worked. All other issues were resolved after the NIC was up.

I have started checking the messages file and below is the output. The server had earlier been rebooted (that is when the problem started) about 6:15.

I am still trying to figure out what went wrong from the out put


Output (messages)

Nov 26 08:25:41 nmb-dr sendmail[21810]: [ID 801593 mail.crit] NOQUEUE: SYSERR(ro
ot): /etc/mail/sendmail.cf: line 77: fileclass: cannot open '/etc/mail/local-hos
t-names': World writable directory 
Nov 26 08:25:41 nmb-dr sendmail[21810]: [ID 801593 mail.crit] NOQUEUE: SYSERR(ro
ot): /etc/mail/sendmail.cf: line 492: fileclass: cannot open '/etc/mail/trusted-
users': World writable directory
Nov 26 11:41:31 nmb-dr sendmail[17540]: [ID 801593 mail.crit] lAQDfVn17540: SYSE
RR(root): fill_fd: disconnect: fd 0 not open: Bad file number
Nov 26 11:41:31 nmb-dr sendmail[17540]: [ID 801593 mail.alert] lAQDfVn17540: SYS
ERR(root): fill_fd: disconnect: cannot open /dev/null: No such file or directory
Nov 26 11:56:31 nmb-dr sendmail[17656]: [ID 801593 mail.crit] lAQDuVn17656: SYSE
RR(root): fill_fd: disconnect: fd 0 not open: Bad file number
Nov 26 11:56:31 nmb-dr sendmail[17656]: [ID 801593 mail.alert] lAQDuVn17656: SYS
ERR(root): fill_fd: disconnect: cannot open /dev/null: No such file or directory
Nov 26 12:11:31 nmb-dr sendmail[17779]: [ID 801593 mail.crit] lAQEBVn17779: SYSE
RR(root): fill_fd: disconnect: fd 0 not open: Bad file number
Nov 26 12:11:31 nmb-dr sendmail[17779]: [ID 801593 mail.alert] lAQEBVn17779: SYS
ERR(root): fill_fd: disconnect: cannot open /dev/null: No such file or directory
Nov 26 12:19:30 nmb-dr sendmail[17806]: [ID 801593 mail.crit] NOQUEUE: SYSERR(ro
ot): /etc/mail/sendmail.cf: line 77: fileclass: cannot open '/etc/mail/local-hos
t-names': World writable directory
Nov 26 12:19:30 nmb-dr sendmail[17806]: [ID 801593 mail.crit] NOQUEUE: SYSERR(ro
ot): /etc/mail/sendmail.cf: line 492: fileclass: cannot open '/etc/mail/trusted-
users': World writable directory
Nov 26 12:26:31 nmb-dr sendmail[25989]: [ID 801593 mail.crit] lAQEQVn25989: SYSE
RR(root): fill_fd: disconnect: fd 0 not open: Bad file number
Nov 26 12:26:31 nmb-dr sendmail[25989]: [ID 801593 mail.alert] lAQEQVn25989: SYS
ERR(root): fill_fd: disconnect: cannot open /dev/null: No such file or directory
Nov 27 06:13:17 nmb-dr pseudo: [ID 129642 kern.info] pseudo-device: tod0
Nov 27 06:13:17 nmb-dr genunix: [ID 936769 kern.info] tod0 is /pseudo/tod at 0
Nov 27 06:13:17 nmb-dr pseudo: [ID 129642 kern.info] pseudo-device: pm0
Nov 27 06:13:17 nmb-dr genunix: [ID 936769 kern.info] pm0 is /pseudo/pm at 0
Nov 27 06:13:18 nmb-dr syslogd: going down on signal 15
Nov 27 06:17:47 unknown genunix: [ID 540533 kern.notice] ^MSunOS Release 5.8 Ver
sion Generic_117350-44 64-bit
Nov 27 06:17:47 unknown genunix: [ID 913632 kern.notice] Copyright 1983-2003 Sun
 Microsystems, Inc.  All rights reserved.
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding f
ile entry "mc-us3i 194" conflicts with a previous entry on line 277 of /etc/name
_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding f
ile entry "bge 195" conflicts with a previous entry on line 278 of /etc/name_to_
major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding f
ile entry "rmc_comm 196" conflicts with a previous entry on line 279 of /etc/nam
e_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding f
ile entry "rmclomv 197" conflicts with a previous entry on line 280 of /etc/name
_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding f
ile entry "rmcadm 198" conflicts with a previous entry on line 281 of /etc/name_
to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "pmugpio 199" conflicts with a pre
vious entry on line 282 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "pca9556 200" conflicts with a pre
vious entry on line 283 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "bscbus 201" conflicts with a prev
ious entry on line 284 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "bscv 202" conflicts with a previo
us entry on line 285 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "i2bsc 203" conflicts with a previ
ous entry on line 286 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "ppm 204" conflicts with a previou
s entry on line 287 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "tomtppm 205" conflicts with a pre
vious entry on line 288 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "m1535ppm 206" conflicts with a pr
evious entry on line 289 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "ics951601 207" conflicts with a p
revious entry on line 290 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "adm1031 208" conflicts with a pre
vious entry on line 291 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "usba10_usb_ac 209" conflicts with
 a previous entry on line 292 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "usba10_usb_as 210" conflicts with
 a previous entry on line 293 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "mpt 211" conflicts with a previou
s entry on line 294 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "xcalwd 212" conflicts with a prev
ious entry on line 295 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "pic16f819 213" conflicts with a p
revious entry on line 296 of /etc/name_to_major
Nov 27 06:17:47 unknown genunix: [ID 678236 kern.info] Ethernet address = 0:3:ba:4:27:f0
Nov 27 06:17:47 unknown unix: [ID 389951 kern.info] mem = 8388608K (0x200000000)

ov 27 06:17:47 unknown unix: [ID 930857 kern.info] avail mem = 8189575168
Nov 27 06:17:47 unknown rootnex: [ID 466748 kern.info] root nexus = Sun Fire 4800
Nov 27 06:17:47 unknown rootnex: [ID 349649 kern.info] ssm0 at root: SSM Node 0
Nov 27 06:17:47 unknown genunix: [ID 936769 kern.info] ssm0 is /ssm at 0,0
Nov 27 06:17:47 unknown ssm: [ID 349649 kern.info] pci108e,80010 at ssm0: Node 0 Safari id 24 0xc700000
Nov 27 06:17:47 unknown genunix: [ID 936769 kern.info] pcisch0 is /ssm at 0,0/pci at 18,700000
Nov 27 06:17:47 unknown ssm: [ID 349649 kern.info] pci108e,80011 at ssm0: Node 0 Safari id 24 0xc600000
Nov 27 06:17:47 unknown genunix: [ID 936769 kern.info] pcisch1 is /ssm at 0,0/pci at 18,600000
Nov 27 06:17:47 unknown ssm: [ID 349649 kern.info] pci108e,80012 at ssm0: Node 0 Safari id 25 0xcf00000
Nov 27 06:17:47 unknown genunix: [ID 936769 kern.info] pcisch2 is /ssm at 0,0/pci at 19,700000
Nov 27 06:17:47 unknown ssm: [ID 349649 kern.info] pci108e,80013 at ssm0: Node 0 Safari id 25 0xce00000
Nov 27 06:17:47 unknown genunix: [ID 936769 kern.info] pcisch3 is /ssm at 0,0/pci at 19,600000
Nov 27 06:17:47 unknown ssm: [ID 349649 kern.info] pci108e,80014 at ssm0: Node 0 Safari id 28 0xe700000
Nov 27 06:17:47 unknown genunix: [ID 936769 kern.info] pcisch4 is /ssm at 0,0/pci at 1c,700000
Nov 27 06:17:47 unknown ssm: [ID 349649 kern.info] pci108e,80015 at ssm0: Node 0 Safari id 28 0xe600000
Nov 27 06:17:47 unknown genunix: [ID 936769 kern.info] pcisch5 is /ssm at 0,0/pci at 1c,600000
Nov 27 06:17:47 unknown ssm: [ID 349649 kern.info] pci108e,80016 at ssm0: Node 0 Safari id 29 0xef00000
Nov 27 06:17:47 unknown genunix: [ID 936769 kern.info] pcisch6 is /ssm at 0,0/pci at 1d,700000
Nov 27 06:17:47 unknown ssm: [ID 349649 kern.info] pci108e,80017 at ssm0: Node 0 Safari id 29 0xee00000
Nov 27 06:17:47 unknown genunix: [ID 936769 kern.info] pcisch7 is /ssm at 0,0/pci at 1d,600000
Nov 27 06:17:47 unknown pcisch: [ID 370704 kern.info] PCI-device: pci at 1, pci_pci0
Nov 27 06:17:47 unknown genunix: [ID 936769 kern.info] pci_pci0 is /ssm at 0,0/pci at 18,700000/pci at 1
Nov 27 06:17:47 unknown pcisch: [ID 370704 kern.info] PCI-device: pci at 1, pci_pci1
Nov 27 06:17:47 unknown genunix: [ID 936769 kern.info] pci_pci1 is /ssm at 0,0/pci at 1c,700000/pci at 1
Nov 27 06:17:47 unknown pci_pci: [ID 370704 kern.info] PCI-device: SUNW,isptwo at 4, isp0
Nov 27 06:17:47 unknown genunix: [ID 936769 kern.info] isp0 is /ssm at 0,0/pci at 18,700000/pci at 1/SUNW,isptwo at 4
Nov 27 06:17:47 unknown scsi: [ID 365881 kern.info] /ssm at 0,0/pci at 18,700000/pci at 1/SUNW,isptwo at 4 (isp0):
Nov 27 06:17:47 unknown         Firmware Version: v4.66, Customer: 0, Product: 4
Nov 27 06:17:47 unknown pci_pci: [ID 370704 kern.info] PCI-device: SUNW,isptwo at 4, isp1
Nov 27 06:17:47 unknown genunix: [ID 936769 kern.info] isp1 is /ssm at 0,0/pci at 1c,700000/pci at 1/SUNW,isptwo at 4
Nov 27 06:17:47 unknown scsi: [ID 365881 kern.info] /ssm at 0,0/pci at 1c,700000/pci at 1/SUNW,isptwo at 4 (isp1):
Nov 27 06:17:47 unknown         Firmware Version: v4.66, Customer: 0, Product: 4
Nov 27 06:17:47 unknown genunix: [ID 247825 kern.warning] WARNING: Cannot create minor node for <JNI,FCR> <jnic146x> <0>
ov 27 06:17:47 unknown jnic146x: [ID 665907 kern.notice] jnic146x0: Hba: JNI,FCR  Model: FCE-6460-N
Nov 27 06:17:47 unknown jnic146x: [ID 178835 kern.notice] jnic146x0: FCode: Version 3.6.2 [3B32]
Nov 27 06:17:47 unknown jnic146x: [ID 188160 kern.notice] jnic146x0: IRQ: 1  Channel: 1
Nov 27 06:17:47 unknown jnic146x: [ID 539489 kern.notice] jnic146x0: SubVend: 1242  Sub: 6460  Rev: 100  Vend: 1242  Dev: 14
60
Nov 27 06:17:47 unknown jnic146x: [ID 653792 kern.notice] jnic146x0: WWNN: 10000001730073E3  WWPN: 20000001730073E3
Nov 27 06:17:47 unknown jnic146x: [ID 695386 kern.notice] jnic146x0: Auto-negotiating link speed
Nov 27 06:17:47 unknown jnic146x: [ID 873028 kern.notice] jnic146x0: Configured as Private Loop port
Nov 27 06:17:48 unknown jnic146x: [ID 643004 kern.notice] jnic146x0: JNIC v5.1.1 (02051300)
Nov 27 06:17:48 unknown jnic146x: [ID 592703 kern.notice] jnic146x0: Copyright(c) 1995-2001 JNI Corp, All Rights Reserved.
Nov 27 06:17:50 unknown jnic146x: [ID 806513 kern.notice] jnic146x0: Link Up
Nov 27 06:17:50 unknown jnic146x: [ID 356212 kern.notice] jnic146x0: Port 0000E4 (WWN 200400A0B80BB278:200500A0B80BB279) onl
ine.
Nov 27 06:17:50 unknown jnic146x: [ID 995893 kern.notice] jnic146x0: Target (WWN 200400A0B80BB278:200500A0B80BB279) online.
Nov 27 06:17:53 unknown pcisch: [ID 370704 kern.info] PCI-device: JNI,FCR at 1, jnic146x0
Nov 27 06:17:53 unknown genunix: [ID 936769 kern.info] jnic146x0 is /ssm at 0,0/pci at 19,600000/JNI,FCR at 1
Nov 27 06:17:53 unknown genunix: [ID 247825 kern.warning] WARNING: Cannot create minor node for <JNI,FCR> <jnic146x> <1>
Nov 27 06:17:53 unknown genunix: [ID 983219 kern.notice] Can't find clone devinfo node
Nov 27 06:17:53 unknown jnic146x: [ID 786466 kern.notice] jnic146x1: Hba: JNI,FCR  Model: FCE-6460-N
Nov 27 06:17:53 unknown jnic146x: [ID 211603 kern.notice] jnic146x1: FCode: Version 3.6.2 [3B32]
Nov 27 06:17:53 unknown jnic146x: [ID 429278 kern.notice] jnic146x1: IRQ: 1  Channel: 1
Nov 27 06:17:53 unknown jnic146x: [ID 794624 kern.notice] jnic146x1: SubVend: 1242  Sub: 6460  Rev: 100  Vend: 1242  Dev: 14
60
Nov 27 06:17:53 unknown jnic146x: [ID 718421 kern.notice] jnic146x1: WWNN: 1000000173006D7C  WWPN: 2000000173006D7C
Nov 27 06:17:54 unknown jnic146x: [ID 728154 kern.notice] jnic146x1: Auto-negotiating link speed
Nov 27 06:17:54 unknown jnic146x: [ID 993587 kern.notice] jnic146x1: Configured as Private Loop port
Nov 27 06:17:54 unknown jnic146x: [ID 643260 kern.notice] jnic146x1: JNIC v5.1.1 (02051300)
Nov 27 06:17:54 unknown jnic146x: [ID 600895 kern.notice] jnic146x1: Copyright(c) 1995-2001 JNI Corp, All Rights Reserved.
Nov 27 06:17:59 unknown pcisch: [ID 370704 kern.info] PCI-device: JNI,FCR at 1, jnic146x1
Nov 27 06:17:59 unknown genunix: [ID 936769 kern.info] jnic146x1 is /ssm at 0,0/pci at 1d,600000/JNI,FCR at 1
Nov 27 06:17:59 unknown jnic146x: [ID 494751 kern.notice] jnic146x0: Target2: Lun0 present.
Nov 27 06:17:59 unknown jnic146x: [ID 119058 kern.notice] jnic146x0: Target2: Lun1 present.
 v 27 06:17:59 unknown genunix: [ID 936769 kern.info] sd122 is /ssm at 0,0/pci at 19,600000/JNI,FCR at 1/sd at 2,1
Nov 27 06:17:59 unknown scsi: [ID 365881 kern.info]     <STK-OPENstorageD173-0520 cyl 61219 alt 2 hd 256 sec 64>
Nov 27 06:17:59 unknown jnic146x: [ID 650705 kern.notice] jnic146x0: Target2: Lun2 supported.
Nov 27 06:17:59 unknown jnic146x: [ID 651217 kern.notice] jnic146x0: Target2: Lun3 supported.
Nov 27 06:17:59 unknown jnic146x: [ID 651729 kern.notice] jnic146x0: Target2: Lun4 supported.
Nov 27 06:17:59 unknown scsi: [ID 193665 kern.info] sd0 at isp0: target 0 lun 0
Nov 27 06:17:59 unknown genunix: [ID 936769 kern.info] sd0 is /ssm at 0,0/pci at 18,700000/pci at 1/SUNW,isptwo at 4/sd at 0,0
Nov 27 06:17:59 unknown scsi: [ID 365881 kern.info]     <SUN18G cyl 7506 alt 2 hd 19 sec 248>
Nov 27 06:17:59 unknown scsi: [ID 193665 kern.info] sd15 at isp1: target 0 lun 0
Nov 27 06:17:59 unknown genunix: [ID 936769 kern.info] sd15 is /ssm at 0,0/pci at 1c,700000/pci at 1/SUNW,isptwo at 4/sd at 0,0
Nov 27 06:17:59 unknown scsi: [ID 365881 kern.info]     <SUN18G cyl 7506 alt 2 hd 19 sec 248>
Nov 27 06:18:00 unknown scsi: [ID 193665 kern.info] sd6 at isp0: target 6 lun 0
Nov 27 06:18:00 unknown genunix: [ID 936769 kern.info] sd6 is /ssm at 0,0/pci at 18,700000/pci at 1/SUNW,isptwo at 4/sd at 6,0
Nov 27 06:18:02 unknown swapgeneric: [ID 308332 kern.info] root on /pseudo/vxio at 0:0 fstype ufs
Nov 27 06:18:03 unknown genunix: [ID 370176 kern.warning] WARNING: forceload of drv/pci failed
Nov 27 06:18:03 unknown ssm: [ID 349649 kern.info] memory-controller8 at ssm0: Node 0 Safari id 0 0x400000 ...
Nov 27 06:18:03 unknown genunix: [ID 936769 kern.info] mc-us38 is /ssm at 0,0/memory-controller at 0,400000
Nov 27 06:18:03 unknown ssm: [ID 349649 kern.info] memory-controller9 at ssm0: Node 0 Safari id 1 0xc00000 ...
Nov 27 06:18:03 unknown genunix: [ID 936769 kern.info] mc-us39 is /ssm at 0,0/memory-controller at 1,400000
Nov 27 06:18:03 unknown ssm: [ID 349649 kern.info] memory-controller10 at ssm0: Node 0 Safari id 2 0x1400000 ...
Nov 27 06:18:03 unknown genunix: [ID 936769 kern.info] mc-us310 is /ssm at 0,0/memory-controller at 2,400000
Nov 27 06:18:03 unknown ssm: [ID 349649 kern.info] memory-controller11 at ssm0: Node 0 Safari id 3 0x1c00000 ...
Nov 27 06:18:03 unknown genunix: [ID 936769 kern.info] mc-us311 is /ssm at 0,0/memory-controller at 3,400000
Nov 27 06:18:03 unknown ssm: [ID 349649 kern.info] memory-controller4 at ssm0: Node 0 Safari id 8 0x4400000 ...
Nov 27 06:18:03 unknown genunix: [ID 936769 kern.info] mc-us34 is /ssm at 0,0/memory-controller at 8,400000
Nov 27 06:18:03 unknown ssm: [ID 349649 kern.info] memory-controller5 at ssm0: Node 0 Safari id 9 0x4c00000 ...
Nov 27 06:18:03 unknown genunix: [ID 936769 kern.info] mc-us35 is /ssm at 0,0/memory-controller at 9,400000
Nov 27 06:18:03 unknown ssm: [ID 349649 kern.info] memory-controller6 at ssm0: Node 0 Safari id 10 0x5400000 ...
Nov 27 06:18:03 unknown genunix: [ID 936769 kern.info] mc-us36 is /ssm at 0,0/memory-controller at a,400000
Nov 27 06:18:03 unknown ssm: [ID 349649 kern.info] memory-controller7 at ssm0: Node 0 Safari id 11 0x5c00000 ...
Nov 27 06:18:03 unknown genunix: [ID 936769 kern.info] mc-us37 is /ssm at 0,0/memory-controller at b,400000
Nov 27 06:18:03 unknown pcisch: [ID 370704 kern.info] PCI-device: bootbus-controller at 4, sgsbbc0

ov 27 06:18:03 unknown genunix: [ID 936769 kern.info] sgsbbc0 is /ssm at 0,0/pci at 18,700000/bootbus-controller at 4
Nov 27 06:18:03 unknown pcisch: [ID 370704 kern.info] PCI-device: bootbus-controller at 4, sgsbbc1
Nov 27 06:18:03 unknown genunix: [ID 936769 kern.info] sgsbbc1 is /ssm at 0,0/pci at 1c,700000/bootbus-controller at 4
Nov 27 06:18:03 unknown pseudo: [ID 129642 kern.info] pseudo-device: sgenv0
Nov 27 06:18:03 unknown genunix: [ID 936769 kern.info] sgenv0 is /pseudo/sgenv at 0
Nov 27 06:18:03 unknown unix: [ID 758372 kern.notice] Hardware watchdog enabled
Nov 27 06:18:08 unknown unix: [ID 270833 kern.info] cpu0: UltraSPARC-III+ (portid 0 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 06:18:08 unknown unix: [ID 270833 kern.info] cpu1: UltraSPARC-III+ (portid 1 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 06:18:08 unknown unix: [ID 721127 kern.info] cpu 1 initialization complete - online
Nov 27 06:18:08 unknown unix: [ID 270833 kern.info] cpu2: UltraSPARC-III+ (portid 2 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 06:18:08 unknown unix: [ID 721127 kern.info] cpu 2 initialization complete - online
Nov 27 06:18:08 unknown unix: [ID 270833 kern.info] cpu3: UltraSPARC-III+ (portid 3 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 06:18:08 unknown unix: [ID 721127 kern.info] cpu 3 initialization complete - online
Nov 27 06:18:08 unknown unix: [ID 270833 kern.info] cpu8: UltraSPARC-III+ (portid 8 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 06:18:08 unknown unix: [ID 721127 kern.info] cpu 8 initialization complete - online
Nov 27 06:18:08 unknown unix: [ID 270833 kern.info] cpu9: UltraSPARC-III+ (portid 9 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 06:18:08 unknown unix: [ID 721127 kern.info] cpu 9 initialization complete - online
Nov 27 06:18:08 unknown unix: [ID 270833 kern.info] cpu10: UltraSPARC-III+ (portid 10 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 06:18:08 unknown unix: [ID 721127 kern.info] cpu 10 initialization complete - online
Nov 27 06:18:08 unknown unix: [ID 270833 kern.info] cpu11: UltraSPARC-III+ (portid 11 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 06:18:08 unknown unix: [ID 721127 kern.info] cpu 11 initialization complete - online
Nov 27 06:18:11 unknown scsi: [ID 365881 kern.info] /ssm at 0,0/pci at 1c,700000/pci at 1/SUNW,isptwo at 4/st at 6,0 (st13):
Nov 27 06:18:11 unknown         <HP DDS-4 DAT (Sun)>
Nov 27 06:18:11 unknown scsi: [ID 193665 kern.info] st13 at isp1: target 6 lun 0
Nov 27 06:18:11 unknown genunix: [ID 936769 kern.info] st13 is /ssm at 0,0/pci at 1c,700000/pci at 1/SUNW,isptwo at 4/st at 6,0
Nov 27 06:18:11 unknown pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Nov 27 06:18:11 unknown genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo at 0
Nov 27 06:18:13 unknown rootnex: [ID 349649 kern.info] wrsm0 at root: SAFARI 0xffff 0x0
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm0 is /wrsm at ffff,0
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm100
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm100 is /pseudo/wrsm at 100
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm101
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm101 is /pseudo/wrsm at 101

 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm102
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm102 is /pseudo/wrsm at 102
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm103
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm103 is /pseudo/wrsm at 103
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm104
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm104 is /pseudo/wrsm at 104
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm105
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm105 is /pseudo/wrsm at 105
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm106
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm106 is /pseudo/wrsm at 106
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm107
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm107 is /pseudo/wrsm at 107
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm108
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm108 is /pseudo/wrsm at 108
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm109
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm109 is /pseudo/wrsm at 109
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm110
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm110 is /pseudo/wrsm at 110
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm111
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm111 is /pseudo/wrsm at 111
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm112
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm112 is /pseudo/wrsm at 112
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm113
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm113 is /pseudo/wrsm at 113
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm114
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm114 is /pseudo/wrsm at 114
Nov 27 06:18:13 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm115
Nov 27 06:18:13 unknown genunix: [ID 936769 kern.info] wrsm115 is /pseudo/wrsm at 115
Nov 27 06:18:19 unknown jnic146x: [ID 947908 kern.notice] jnic146x1: Link Failure event detected
Nov 27 06:18:20 unknown genunix: [ID 454863 kern.info] dump on /dev/dsk/c1t0d0s1 size 8193 MB
Nov 27 06:18:34 unknown inetd[322]: [ID 965992 daemon.error] talk/udp: unknown service
Nov 27 06:18:34 unknown inetd[322]: [ID 965992 daemon.error] finger/tcp: unknown service
Nov 27 06:18:36 unknown pseudo: [ID 129642 kern.info] pseudo-device: tod0

 06:18:36 unknown genunix: [ID 936769 kern.info] tod0 is /pseudo/tod at 0
Nov 27 06:18:36 unknown pseudo: [ID 129642 kern.info] pseudo-device: pm0
Nov 27 06:18:36 unknown genunix: [ID 936769 kern.info] pm0 is /pseudo/pm at 0
Nov 27 06:18:36 unknown sendmail[381]: [ID 801593 mail.crit] NOQUEUE: SYSERR(root): /etc/mail/sendmail.cf: line 77: fileclas
s: cannot open '/etc/mail/local-host-names': World writable directory
Nov 27 06:18:37 unknown sendmail[381]: [ID 801593 mail.crit] NOQUEUE: SYSERR(root): /etc/mail/sendmail.cf: line 492: filecla
ss: cannot open '/etc/mail/trusted-users': World writable directory
Nov 27 06:18:37 unknown pseudo: [ID 129642 kern.info] pseudo-device: vol0
Nov 27 06:18:37 unknown genunix: [ID 936769 kern.info] vol0 is /pseudo/vol at 0
Nov 27 06:18:38 unknown pseudo: [ID 129642 kern.info] pseudo-device: fcode0
Nov 27 06:18:38 unknown genunix: [ID 936769 kern.info] fcode0 is /pseudo/fcode at 0
Nov 27 06:19:16 unknown pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Nov 27 06:19:16 unknown genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo at 0
Nov 27 06:22:35 unknown statd[324]: [ID 859811 daemon.warning] statd: host ipv4.192.168.253.117 is not responding
Nov 27 06:24:35 unknown statd[324]: [ID 859811 daemon.warning] statd: host ipv4.192.168.254.65 is not responding
Nov 27 08:20:47 unknown jnic146x: [ID 553580 kern.notice] jnic146x0: Link Down event (Stop I/O) detected
Nov 27 08:20:47 unknown jnic146x: [ID 132654 kern.notice] jnic146x0: Link Down
Nov 27 08:20:47 unknown jnic146x: [ID 941218 kern.notice] jnic146x0: Port 0000E4 (WWN 200400A0B80BB278:200500A0B80BB279) off
line.
Nov 27 08:20:47 unknown jnic146x: [ID 937024 kern.notice] jnic146x0: Target (WWN 200400A0B80BB278:200500A0B80BB279) offline.
Nov 27 08:33:03 unknown genunix: [ID 540533 kern.notice] ^MSunOS Release 5.8 Version Generic_117350-44 64-bit
Nov 27 08:33:03 unknown genunix: [ID 913632 kern.notice] Copyright 1983-2003 Sun Microsystems, Inc.  All rights reserved.
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "mc-us3i 194" conflicts with a pre
vious entry on line 277 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "bge 195" conflicts with a previou
s entry on line 278 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "rmc_comm 196" conflicts with a pr
evious entry on line 279 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "rmclomv 197" conflicts with a pre
vious entry on line 280 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "rmcadm 198" conflicts with a prev
ious entry on line 281 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "pmugpio 199" conflicts with a pre
ov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "pca9556 200" conflicts with a pre
vious entry on line 283 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "bscbus 201" conflicts with a prev
ious entry on line 284 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "bscv 202" conflicts with a previo
us entry on line 285 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "i2bsc 203" conflicts with a previ
ous entry on line 286 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "ppm 204" conflicts with a previou
s entry on line 287 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "tomtppm 205" conflicts with a pre
vious entry on line 288 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "m1535ppm 206" conflicts with a pr
evious entry on line 289 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "ics951601 207" conflicts with a p
revious entry on line 290 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "adm1031 208" conflicts with a pre
vious entry on line 291 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "usba10_usb_ac 209" conflicts with
 a previous entry on line 292 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "usba10_usb_as 210" conflicts with
 a previous entry on line 293 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "mpt 211" conflicts with a previou
s entry on line 294 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "xcalwd 212" conflicts with a prev
ious entry on line 295 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 243001 kern.warning] WARNING: The binding file entry "pic16f819 213" conflicts with a p
revious entry on line 296 of /etc/name_to_major
Nov 27 08:33:03 unknown genunix: [ID 678236 kern.info] Ethernet address = 0:3:ba:4:27:f0
Nov 27 08:33:03 unknown unix: [ID 389951 kern.info] mem = 8388608K (0x200000000)
Nov 27 08:33:03 unknown unix: [ID 930857 kern.info] avail mem = 8189575168
Nov 27 08:33:03 unknown rootnex: [ID 466748 kern.info] root nexus = Sun Fire 4800
 27 08:33:03 unknown rootnex: [ID 349649 kern.info] ssm0 at root: SSM Node 0
Nov 27 08:33:03 unknown genunix: [ID 936769 kern.info] ssm0 is /ssm at 0,0
Nov 27 08:33:03 unknown ssm: [ID 349649 kern.info] pci108e,80010 at ssm0: Node 0 Safari id 24 0xc700000
Nov 27 08:33:03 unknown genunix: [ID 936769 kern.info] pcisch0 is /ssm at 0,0/pci at 18,700000
Nov 27 08:33:03 unknown ssm: [ID 349649 kern.info] pci108e,80011 at ssm0: Node 0 Safari id 24 0xc600000
Nov 27 08:33:03 unknown genunix: [ID 936769 kern.info] pcisch1 is /ssm at 0,0/pci at 18,600000
Nov 27 08:33:03 unknown ssm: [ID 349649 kern.info] pci108e,80012 at ssm0: Node 0 Safari id 25 0xcf00000
Nov 27 08:33:03 unknown genunix: [ID 936769 kern.info] pcisch2 is /ssm at 0,0/pci at 19,700000
Nov 27 08:33:03 unknown ssm: [ID 349649 kern.info] pci108e,80013 at ssm0: Node 0 Safari id 25 0xce00000
Nov 27 08:33:03 unknown genunix: [ID 936769 kern.info] pcisch3 is /ssm at 0,0/pci at 19,600000
Nov 27 08:33:03 unknown ssm: [ID 349649 kern.info] pci108e,80014 at ssm0: Node 0 Safari id 28 0xe700000
Nov 27 08:33:03 unknown genunix: [ID 936769 kern.info] pcisch4 is /ssm at 0,0/pci at 1c,700000
Nov 27 08:33:03 unknown ssm: [ID 349649 kern.info] pci108e,80015 at ssm0: Node 0 Safari id 28 0xe600000
Nov 27 08:33:03 unknown genunix: [ID 936769 kern.info] pcisch5 is /ssm at 0,0/pci at 1c,600000
Nov 27 08:33:03 unknown ssm: [ID 349649 kern.info] pci108e,80016 at ssm0: Node 0 Safari id 29 0xef00000
Nov 27 08:33:03 unknown genunix: [ID 936769 kern.info] pcisch6 is /ssm at 0,0/pci at 1d,700000
Nov 27 08:33:03 unknown ssm: [ID 349649 kern.info] pci108e,80017 at ssm0: Node 0 Safari id 29 0xee00000
Nov 27 08:33:03 unknown genunix: [ID 936769 kern.info] pcisch7 is /ssm at 0,0/pci at 1d,600000
Nov 27 08:33:03 unknown pcisch: [ID 370704 kern.info] PCI-device: pci at 1, pci_pci0
Nov 27 08:33:03 unknown genunix: [ID 936769 kern.info] pci_pci0 is /ssm at 0,0/pci at 18,700000/pci at 1
Nov 27 08:33:03 unknown pcisch: [ID 370704 kern.info] PCI-device: pci at 1, pci_pci1
Nov 27 08:33:03 unknown genunix: [ID 936769 kern.info] pci_pci1 is /ssm at 0,0/pci at 1c,700000/pci at 1
Nov 27 08:33:03 unknown pci_pci: [ID 370704 kern.info] PCI-device: SUNW,isptwo at 4, isp0
Nov 27 08:33:03 unknown genunix: [ID 936769 kern.info] isp0 is /ssm at 0,0/pci at 18,700000/pci at 1/SUNW,isptwo at 4
Nov 27 08:33:03 unknown scsi: [ID 365881 kern.info] /ssm at 0,0/pci at 18,700000/pci at 1/SUNW,isptwo at 4 (isp0):
Nov 27 08:33:03 unknown         Firmware Version: v4.66, Customer: 0, Product: 4
Nov 27 08:33:03 unknown pci_pci: [ID 370704 kern.info] PCI-device: SUNW,isptwo at 4, isp1
Nov 27 08:33:03 unknown genunix: [ID 936769 kern.info] isp1 is /ssm at 0,0/pci at 1c,700000/pci at 1/SUNW,isptwo at 4
Nov 27 08:33:03 unknown scsi: [ID 365881 kern.info] /ssm at 0,0/pci at 1c,700000/pci at 1/SUNW,isptwo at 4 (isp1):
Nov 27 08:33:03 unknown         Firmware Version: v4.66, Customer: 0, Product: 4
Nov 27 08:33:03 unknown genunix: [ID 247825 kern.warning] WARNING: Cannot create minor node for <JNI,FCR> <jnic146x> <0>
Nov 27 08:33:03 unknown genunix: [ID 983219 kern.notice] Can't find clone devinfo node
Nov 27 08:33:03 unknown jnic146x: [ID 665907 kern.notice] jnic146x0: Hba: JNI,FCR  Model: FCE-6460-N 
ov 27 08:33:03 unknown jnic146x: [ID 178835 kern.notice] jnic146x0: FCode: Version 3.6.2 [3B32]
Nov 27 08:33:03 unknown jnic146x: [ID 188160 kern.notice] jnic146x0: IRQ: 1  Channel: 1
Nov 27 08:33:03 unknown jnic146x: [ID 539489 kern.notice] jnic146x0: SubVend: 1242  Sub: 6460  Rev: 100  Vend: 1242  Dev: 14
60
Nov 27 08:33:03 unknown jnic146x: [ID 653792 kern.notice] jnic146x0: WWNN: 10000001730073E3  WWPN: 20000001730073E3
Nov 27 08:33:03 unknown jnic146x: [ID 695386 kern.notice] jnic146x0: Auto-negotiating link speed
Nov 27 08:33:03 unknown jnic146x: [ID 873028 kern.notice] jnic146x0: Configured as Private Loop port
Nov 27 08:33:04 unknown jnic146x: [ID 643004 kern.notice] jnic146x0: JNIC v5.1.1 (02051300)
Nov 27 08:33:04 unknown jnic146x: [ID 592703 kern.notice] jnic146x0: Copyright(c) 1995-2001 JNI Corp, All Rights Reserved.
Nov 27 08:33:06 unknown jnic146x: [ID 806513 kern.notice] jnic146x0: Link Up
Nov 27 08:33:06 unknown jnic146x: [ID 356212 kern.notice] jnic146x0: Port 0000E4 (WWN 200400A0B80BB278:200500A0B80BB279) onl
ine.
Nov 27 08:33:06 unknown jnic146x: [ID 995893 kern.notice] jnic146x0: Target (WWN 200400A0B80BB278:200500A0B80BB279) online.
Nov 27 08:33:09 unknown pcisch: [ID 370704 kern.info] PCI-device: JNI,FCR at 1, jnic146x0
Nov 27 08:33:09 unknown genunix: [ID 936769 kern.info] jnic146x0 is /ssm at 0,0/pci at 19,600000/JNI,FCR at 1
Nov 27 08:33:09 unknown genunix: [ID 247825 kern.warning] WARNING: Cannot create minor node for <JNI,FCR> <jnic146x> <1>
Nov 27 08:33:09 unknown genunix: [ID 983219 kern.notice] Can't find clone devinfo node
Nov 27 08:33:09 unknown jnic146x: [ID 786466 kern.notice] jnic146x1: Hba: JNI,FCR  Model: FCE-6460-N
Nov 27 08:33:09 unknown jnic146x: [ID 211603 kern.notice] jnic146x1: FCode: Version 3.6.2 [3B32]
Nov 27 08:33:09 unknown jnic146x: [ID 429278 kern.notice] jnic146x1: IRQ: 1  Channel: 1
Nov 27 08:33:09 unknown jnic146x: [ID 794624 kern.notice] jnic146x1: SubVend: 1242  Sub: 6460  Rev: 100  Vend: 1242  Dev: 14
60
Nov 27 08:33:09 unknown jnic146x: [ID 718421 kern.notice] jnic146x1: WWNN: 1000000173006D7C  WWPN: 2000000173006D7C
Nov 27 08:33:10 unknown jnic146x: [ID 728154 kern.notice] jnic146x1: Auto-negotiating link speed
Nov 27 08:33:10 unknown jnic146x: [ID 993587 kern.notice] jnic146x1: Configured as Private Loop port
Nov 27 08:33:10 unknown jnic146x: [ID 643260 kern.notice] jnic146x1: JNIC v5.1.1 (02051300)
Nov 27 08:33:10 unknown jnic146x: [ID 600895 kern.notice] jnic146x1: Copyright(c) 1995-2001 JNI Corp, All Rights Reserved.
Nov 27 08:33:15 unknown pcisch: [ID 370704 kern.info] PCI-device: JNI,FCR at 1, jnic146x1
Nov 27 08:33:15 unknown genunix: [ID 936769 kern.info] jnic146x1 is /ssm at 0,0/pci at 1d,600000/JNI,FCR at 1
Nov 27 08:33:15 unknown jnic146x: [ID 494751 kern.notice] jnic146x0: Target2: Lun0 present.
Nov 27 08:33:15 unknown jnic146x: [ID 119058 kern.notice] jnic146x0: Target2: Lun1 present.
Nov 27 08:33:15 unknown scsi: [ID 193665 kern.info] sd122 at jnic146x0: target 2 lun 1
Nov 27 08:33:15 unknown genunix: [ID 936769 kern.info] sd122 is /ssm at 0,0/pci at 19,600000/JNI,FCR at 1/sd at 2,1
ov 27 08:33:15 unknown scsi: [ID 365881 kern.info]     <STK-OPENstorageD173-0520 cyl 61219 alt 2 hd 256 sec 64>
Nov 27 08:33:15 unknown jnic146x: [ID 650705 kern.notice] jnic146x0: Target2: Lun2 supported.
Nov 27 08:33:15 unknown jnic146x: [ID 651217 kern.notice] jnic146x0: Target2: Lun3 supported.
Nov 27 08:33:15 unknown jnic146x: [ID 651729 kern.notice] jnic146x0: Target2: Lun4 supported.
Nov 27 08:33:15 unknown scsi: [ID 193665 kern.info] sd15 at isp1: target 0 lun 0
Nov 27 08:33:15 unknown genunix: [ID 936769 kern.info] sd15 is /ssm at 0,0/pci at 1c,700000/pci at 1/SUNW,isptwo at 4/sd at 0,0
Nov 27 08:33:15 unknown scsi: [ID 365881 kern.info]     <SUN18G cyl 7506 alt 2 hd 19 sec 248>
Nov 27 08:33:15 unknown scsi: [ID 193665 kern.info] sd0 at isp0: target 0 lun 0
Nov 27 08:33:15 unknown genunix: [ID 936769 kern.info] sd0 is /ssm at 0,0/pci at 18,700000/pci at 1/SUNW,isptwo at 4/sd at 0,0
Nov 27 08:33:15 unknown scsi: [ID 365881 kern.info]     <SUN18G cyl 7506 alt 2 hd 19 sec 248>
Nov 27 08:33:16 unknown scsi: [ID 193665 kern.info] sd6 at isp0: target 6 lun 0
Nov 27 08:33:16 unknown genunix: [ID 936769 kern.info] sd6 is /ssm at 0,0/pci at 18,700000/pci at 1/SUNW,isptwo at 4/sd at 6,0
Nov 27 08:33:18 unknown swapgeneric: [ID 308332 kern.info] root on /pseudo/vxio at 0:0 fstype ufs
Nov 27 08:33:19 unknown genunix: [ID 370176 kern.warning] WARNING: forceload of drv/pci failed
Nov 27 08:33:19 unknown ssm: [ID 349649 kern.info] memory-controller8 at ssm0: Node 0 Safari id 0 0x400000 ...
Nov 27 08:33:19 unknown genunix: [ID 936769 kern.info] mc-us38 is /ssm at 0,0/memory-controller at 0,400000
Nov 27 08:33:19 unknown ssm: [ID 349649 kern.info] memory-controller9 at ssm0: Node 0 Safari id 1 0xc00000 ...
Nov 27 08:33:19 unknown genunix: [ID 936769 kern.info] mc-us39 is /ssm at 0,0/memory-controller at 1,400000
Nov 27 08:33:19 unknown ssm: [ID 349649 kern.info] memory-controller10 at ssm0: Node 0 Safari id 2 0x1400000 ...
Nov 27 08:33:19 unknown genunix: [ID 936769 kern.info] mc-us310 is /ssm at 0,0/memory-controller at 2,400000
Nov 27 08:33:19 unknown ssm: [ID 349649 kern.info] memory-controller11 at ssm0: Node 0 Safari id 3 0x1c00000 ...
Nov 27 08:33:19 unknown genunix: [ID 936769 kern.info] mc-us311 is /ssm at 0,0/memory-controller at 3,400000
Nov 27 08:33:19 unknown ssm: [ID 349649 kern.info] memory-controller4 at ssm0: Node 0 Safari id 8 0x4400000 ...
Nov 27 08:33:19 unknown genunix: [ID 936769 kern.info] mc-us34 is /ssm at 0,0/memory-controller at 8,400000
Nov 27 08:33:19 unknown ssm: [ID 349649 kern.info] memory-controller5 at ssm0: Node 0 Safari id 9 0x4c00000 ...
Nov 27 08:33:19 unknown genunix: [ID 936769 kern.info] mc-us35 is /ssm at 0,0/memory-controller at 9,400000
Nov 27 08:33:19 unknown ssm: [ID 349649 kern.info] memory-controller6 at ssm0: Node 0 Safari id 10 0x5400000 ...
Nov 27 08:33:19 unknown genunix: [ID 936769 kern.info] mc-us36 is /ssm at 0,0/memory-controller at a,400000
Nov 27 08:33:19 unknown ssm: [ID 349649 kern.info] memory-controller7 at ssm0: Node 0 Safari id 11 0x5c00000 ...
Nov 27 08:33:19 unknown genunix: [ID 936769 kern.info] mc-us37 is /ssm at 0,0/memory-controller at b,400000
Nov 27 08:33:19 unknown pcisch: [ID 370704 kern.info] PCI-device: bootbus-controller at 4, sgsbbc0
Nov 27 08:33:19 unknown genunix: [ID 936769 kern.info] sgsbbc0 is /ssm at 0,0/pci at 18,700000/bootbus-controller at 4
Nov 27 08:33:19 unknown pcisch: [ID 370704 kern.info] PCI-device: bootbus-controller at 4, sgsbbc1

v 27 08:33:19 unknown genunix: [ID 936769 kern.info] sgsbbc1 is /ssm at 0,0/pci at 1c,700000/bootbus-controller at 4
Nov 27 08:33:19 unknown pseudo: [ID 129642 kern.info] pseudo-device: sgenv0
Nov 27 08:33:19 unknown genunix: [ID 936769 kern.info] sgenv0 is /pseudo/sgenv at 0
Nov 27 08:33:19 unknown unix: [ID 758372 kern.notice] Hardware watchdog enabled
Nov 27 08:33:24 unknown unix: [ID 270833 kern.info] cpu0: UltraSPARC-III+ (portid 0 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 08:33:24 unknown unix: [ID 270833 kern.info] cpu1: UltraSPARC-III+ (portid 1 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 08:33:24 unknown unix: [ID 721127 kern.info] cpu 1 initialization complete - online
Nov 27 08:33:24 unknown unix: [ID 270833 kern.info] cpu2: UltraSPARC-III+ (portid 2 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 08:33:24 unknown unix: [ID 721127 kern.info] cpu 2 initialization complete - online
Nov 27 08:33:24 unknown unix: [ID 270833 kern.info] cpu3: UltraSPARC-III+ (portid 3 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 08:33:24 unknown unix: [ID 721127 kern.info] cpu 3 initialization complete - online
Nov 27 08:33:24 unknown unix: [ID 270833 kern.info] cpu8: UltraSPARC-III+ (portid 8 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 08:33:24 unknown unix: [ID 721127 kern.info] cpu 8 initialization complete - online
Nov 27 08:33:24 unknown unix: [ID 270833 kern.info] cpu9: UltraSPARC-III+ (portid 9 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 08:33:24 unknown unix: [ID 721127 kern.info] cpu 9 initialization complete - online
Nov 27 08:33:24 unknown unix: [ID 270833 kern.info] cpu10: UltraSPARC-III+ (portid 10 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 08:33:24 unknown unix: [ID 721127 kern.info] cpu 10 initialization complete - online
Nov 27 08:33:24 unknown unix: [ID 270833 kern.info] cpu11: UltraSPARC-III+ (portid 11 impl 0x15 ver 0x23 clock 1050 MHz)
Nov 27 08:33:24 unknown unix: [ID 721127 kern.info] cpu 11 initialization complete - online
Nov 27 08:33:27 unknown scsi: [ID 365881 kern.info] /ssm at 0,0/pci at 1c,700000/pci at 1/SUNW,isptwo at 4/st at 6,0 (st13):
Nov 27 08:33:27 unknown         <HP DDS-4 DAT (Sun)>
Nov 27 08:33:27 unknown scsi: [ID 193665 kern.info] st13 at isp1: target 6 lun 0
Nov 27 08:33:27 unknown genunix: [ID 936769 kern.info] st13 is /ssm at 0,0/pci at 1c,700000/pci at 1/SUNW,isptwo at 4/st at 6,0
Nov 27 08:33:27 unknown pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Nov 27 08:33:27 unknown genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo at 0
Nov 27 08:33:29 unknown rootnex: [ID 349649 kern.info] wrsm0 at root: SAFARI 0xffff 0x0
Nov 27 08:33:29 unknown genunix: [ID 936769 kern.info] wrsm0 is /wrsm at ffff,0
Nov 27 08:33:29 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm100
Nov 27 08:33:29 unknown genunix: [ID 936769 kern.info] wrsm100 is /pseudo/wrsm at 100
Nov 27 08:33:29 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm101
Nov 27 08:33:29 unknown genunix: [ID 936769 kern.info] wrsm101 is /pseudo/wrsm at 101
Nov 27 08:33:29 unknown pseudo: [ID 129642 kern.info] pseudo-device: wrsm102
Nov 27 08:33:29 unknown genunix: [ID 936769 kern.info] wrsm102 is /pseudo/wrsm at 102







       
---------------------------------
Never miss a thing.   Make Yahoo your homepage.
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From stepchung at gmail.com  Wed Nov 28 19:39:56 2007
From: stepchung at gmail.com (Stephanie C)
Date: Wed, 28 Nov 2007 16:39:56 -0800
Subject: SUMMARY: Configure zone on the same NIC
Message-ID: <6bdfa8ce0711281639r6012c4aat40e24da18280f380@mail.gmail.com>

Thank you!

On Nov 28, 2007 4:33 PM, John England <john_w_england at yahoo.com> wrote:

>  Stephanie;
>
> Go into zonecfg for the zone you wish to create or modify
> and run.
>
>
> add net
> set physical=eri0
> set address=the ip you want to use.   i.e.  set address=10.1.1.22
>
> The ip will show up as a virtual interface.
>
> Hope this helps.
>
> John
>
> ----- Original Message ----
> From: Stephanie C <stepchung at gmail.com>
> To: Sun Managers <sunmanagers at sunmanagers.org>
> Sent: Wednesday, November 28, 2007 6:08:58 PM
> Subject: Configure zone on the same NIC
>
> Hi,
>
> Can I configure the non-global zone (zone1) IP address on the same global
> zone NIC card? And how do I do that? My server has only one NIC card. Here
> it shows with ifconfig -a:
>
> lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
> index 1
>         inet 127.0.0.1 netmask ff000000
> lo0:1: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
> 8232
> index 1
>         zone zone1
>         inet 127.0.0.1 netmask ff000000
> eri0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
>         inet 209.xx.xx.xx netmask ffffffe0 broadcast 209.xx.xx.xx
>         ether 0:3:ba:xx:xx:xx
>
> Thanks for your help.
>
> Stephanie
> _______________________________________________
> sunmanagers mailing list
> sunmanagers at sunmanagers.org
> http://www.sunmanagers.org/mailman/listinfo/sunmanagers
>
>
> ------------------------------
> Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See
> how. <http://us.rd.yahoo.com/evt=51732/*http://overview.mail.yahoo.com/>
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From raindoctor at gmail.com  Thu Nov 29 09:09:18 2007
From: raindoctor at gmail.com (Pedro Espinoza)
Date: Thu, 29 Nov 2007 09:09:18 -0500
Subject: SUMMARY: dig and dns problem
Message-ID: <b86c876f0711290609l4bf665earf44e7fac4d91424b@mail.gmail.com>

The problem as described in the first mail occured only on solaris
boxes; but not on linux. Researching further showed that
/etc/inet/hosts and /etc/hosts are out of sync. /etc/inet/hosts    was
mapping ns1.domain to x.y.z.130. Changing that fixed the problem.

Thanks, Pedro.




My original question:

I have changed the IP address of one of our name servers (ns1).
ns1 old IP is x.y.z.130; now ns1old is the hostname for the old IP, x.y.z.130
ns1 new IP x.y.z.150

on ns1:

When I do, nslookup ns1, I am getting x.y.z.150 (no problems at all).
When I do, host ns1, i am getting x.y.z.150 (no issues at all).
When I do, dig ns1, i am getting x.y.z.150 (no issues at all).

When I do, dig @ns1 ns1.ourdomain, I am getting the proper A record in
the answer question.

However, I am getting FALSE information in the comments.

;; Query time: 31 msec
;; SERVER: x.y.z.130#53(x.y.z.130) <------- THIS IS THE PROBLEM
;; WHEN: Thu Nov 29 01:54:34 2007
;; MSG SIZE  rcvd: 107


The @ns1 is leading to old IP address. Any suggestions?



My resolver.conf is perfectly fine. I even changed keep_hot_count
hosts to 0 in nscd.conf, and bounced that daemon.

Even the reverse lookup of x.y.z.130 is giving me ns1old.domain.



Thanks, Pedro
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From Rob.McMahon at warwick.ac.uk  Thu Nov 29 10:03:20 2007
From: Rob.McMahon at warwick.ac.uk (Rob McMahon)
Date: Thu, 29 Nov 2007 15:03:20 +0000
Subject: SUMMARY: Disk contention problems
In-Reply-To: <4746B4EB.7040403@warwick.ac.uk>
References: <4746B4EB.7040403@warwick.ac.uk>
Message-ID: <474ED4B8.9050609@warwick.ac.uk>

Thanks for all your suggestions, there were some good points in there.  
Thanks to Ric Anderson,  John Leadeham,  Tobias Nutt, Joe Fletcher, 
Bhaskar G, Pawel Osiczko, and Grzegorz Bakalarski for their prompt 
replies, and apologies for the late summary.  It's only today I'm 
completely happy, and it's involved moving a bunch of data into the SAN 
(it needed doing anyway).

Suggestions were that having UFS filesystem 95% full is a bad idea in 
the first place, because of the overhead looking for free inodes / free 
data blocks.  Also UFS doesn't do so well on filesystems with milliions 
of files. Hence the move of a chunk of data to the SAN. 

Fragmentation can apparently still be an issue, the only real cure for 
that would be a dump | restore.  A messy option when you're talking 500 
GB data.

If a controller had actually failed, this can trigger the array to 
switch through to write-through mode, clobbering performance.  In my 
case `show cache-param' still showed `mode: write-back', but definitely 
worth checking.

UFS can throttle writes in the case of high write-rates, which is tweakable.

A failed / failing drive can hurt performance.  All my drives were good.

UFS journalling is important, and was turned on.

The optimisation mode can make a big difference, and think before you 
create a volume, because you can't change it later!  I have mine 
optimised for random access, which seems about right for a mail spool.

There's were also a couple of comments that the 3510 isn't a great 
performer in the first place, to check for bad memory, and to make sure 
the firmware's up to date.  I'm a happy bunny at the moment, and 
firmware upgrades mean more downtime, so I'm going to schedule that for 
Christmas.

Anyway, I finally seem to have got it sorted, and it appears to have 
been due to the controllers being in a dodgy state, i.e. this

sccli> show redundancy-mode
 Primary controller serial number: 8040592
 Primary controller location: Lower
 Redundancy mode: Active-Active
 Redundancy status: Failed
 Secondary controller serial number: 8009331
sccli>

On the suggestion of a guy from Sun, I tried

sccli> unfail

The Redundancy status changed to Scanning, and then to Detected, and 
then I lost one of my LUNs.  Bugger.  Then he suggested

sccli> reset controller

and the machine panicked and came back to single-user because of loss of 
metadb quorum.  Bugger, bugger.  I should have known better than that, I 
would have known that would happen if I hadn't been panicking myself.

Anyway, I shut the machine down, power-cycled the array, waited for the 
array to look healthy, and brought the machine back up.  Redundancy 
status is now "Enabled", asvc_t is a 10th of what it was, throughput 
(kw/s) is 2-3 times what it was, and all's back well with the world.

Thanks again everybody,

Rob

The original problem:

Rob McMahon wrote:
> I've got a machine here which has recently (over the last few weeks) 
> degenerated into being unusable at times.  It's a V890 running Solaris 
> 10, cyrus-imap (2.2.13) and squirrelmail.  The mail partitions are on a 
> 3510 FC, 500GB a piece, and RAID 5.  The filesystems are UFS, and the 
> problematic one is 95% full. When it becomes unusable, iostat shows the 
> asvc_t times hitting 1000, 2000 or more.  %b is pinned at 100% all the 
> time.  %w hits 60% on the one partition.  At quiet times I don't seem to 
> get better than:
>
>     r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t  %w  %b device
>    71.8  258.8  618.7 4334.6  0.0 26.0    0.0   78.7   0 100 
> c6t600C0FF0000000000855613BE6F2D900d0
>    35.6  129.6  322.3 2068.4  0.0  0.0    0.0    0.0   0   0 
> c6t600C0FF0000000000855613BE6F2D900d0.fp1
>    36.2  129.2  296.5 2266.2  0.0  0.0    0.0    0.0   0   0 
> c6t600C0FF0000000000855613BE6F2D900d0.fp3
>
> which is lower throughput than I'd expect.  Truss shows creates, renames 
> and fdsyncs (which cyrus-imap seems to like using a lot) taking seconds.
>
> sccli does show
>
> sccli> show redundancy-mode
>  Primary controller serial number: 8040592
>  Primary controller location: Lower
>  Redundancy mode: Active-Active
>  Redundancy status: Failed
>  Secondary controller serial number: 8009331
> sccli>
>
> and I have a call in about that with Sun, although they seem to be 
> arguing about maintenance levels as normal.
>
> Really, I'm a bit desperate out here, and I'd like to hear any 
> suggestions or pointers to things I might not have thought about.
>
> Any input gratefully received.
>
> Thanks,
>
> Rob
>
>   


-- 
E-Mail:	Rob.McMahon at warwick.ac.uk		PHONE:  +44 24 7652 3037
Rob McMahon, IT Services, Warwick University, Coventry, CV4 7AL, England
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

From Karl.Rossing at Federated.CA  Fri Nov 30 11:13:15 2007
From: Karl.Rossing at Federated.CA (Karl.Rossing at Federated.CA)
Date: Fri, 30 Nov 2007 10:13:15 -0600
Subject: SUMMARY: SSL needed for "gem install rails"
In-Reply-To: <OFF630D753.83CE217B-ON862573A2.0055FCEB-862573A2.0059ABE2@LocalDomain>
Message-ID: <OF723C5584.F44849EC-ON862573A3.0052948C-862573A3.00591A53@Federated.CA>

ruby did have openssl installed

        bash-3.00# ruby -e "puts require('openssl')"
        true

switched to rubygem-0.9.4 and i was able to get rails installed

        bash-3.00# gem install rails --include-dependencies
        Successfully installed rails-1.2.6

Karl Rossing/fhcc wrote on 11/29/2007 10:19:27 AM:

> Hello,
> 
> I'm having trouble doing a "gem install rails --include-
> dependencies" in Solaris 10. I have been following the SUN doc http:
> //developers.sun.com/webtier/reference/techart/rubyonrails.html
> 
> I'm getting the following error
> 
> bash-3.00# gem install rails --include-dependencies
> INFO:  `gem install -y` is now default and will be removed
> INFO:  use --ignore-dependencies to install only the gems you list
> ERROR:  While executing gem ... (Gem::Exception)
>     SSL is not installed on this system
> 
> Online searches seem to indicate that "libopenssl-ruby" on debian 
> needs to be installed. I'm confused on how that correlates to 
> Solaris since ./configure of ruby-1.8.6 doesn't seem to have any 
> openssl options.
> 
> Here is a little bit more system info
> ---
> cat /etc/release
>                          Solaris 10 3/05 s10_74L2a SPARC
>            Copyright 2005 Sun Microsystems, Inc.  All Rights Reserved.
>                         Use is subject to license terms.
>                             Assembled 22 January 2005
> ruby-1.8.6
> rubygems-0.9.5
> SunOS w00t 5.10 Generic_118833-36 sun4u sparc SUNW,Sun-Fire-V240
> ---
> 
> Any suggestions would be appreciated.
> 
> Karl
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers