RE: sunmanagers Digest, Vol 20, Issue 34

bhidayat@itdiv.kompasgramedia.com

--
Steve Rieger
Direct 212-804-1131
Cell 646-335-8915
------------------------------
Message: 5
Date: Tue, 23 Nov 2004 16:53:32 +0000
From: aggunia@comcast.net
Subject: SNMP on Solaris 2.6
To: sunmanagers@sunmanagers.org
Message-ID:
	
<112320041653.8253.41A36B0C000627F30000203D22070016410E07029A09090E@comc
ast.net>
	
Content-Type: text/plain; charset="us-ascii"
Hi all,
I have some old Solaris 2.6 boxes that our enterprise wants to monitor
via SNMP.  I have configured the snmpd.conf and snmpdx.acl files
accordingly, and when running '/etc/rc3.d/S76snmpdx start', I cannot
view any MIB values (using SNMPview 2.5 from my workstation).  I've
checked the community name, and made sure my workstation name (did
nslookup on workstation) is listed in the manager line I am not getting
any errors in my /etc/adm/messages.  I did confirm that the boxes have
Solstice Enterprise Agent 1.0 installed.  Any thoughts from anyone out
there would be appreciated.  Thanks!
Anthony
aggunia@comcast.net
------------------------------
Message: 6
Date: Tue, 23 Nov 2004 12:12:00 -0500
From: loonux fc <loonux@gmail.com>
Subject: Tips and tricks for running a busy mail server?
To: sunmanagers@sunmanagers.org
Message-ID: <93bef0760411230912783754f5@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII
Greetings,
I am presently getting ready to build a new set of mail servers for
our organization.  I will be using a set of Netra AC200 units [500Mhz]
with 2Gb of RAM and dual 36Gb SCSI disks running on Solaris 8.  Due to
the nature of our mail product, I must use sendmail as my MTA.  Given
this constraint, I am looking to optimize this system as much as
possible in terms of filesystem layout (RAID/mirroring) and sendmail
configuration tweaks.
Each system presently handles upwards of 200,000 messages a day.  I
would like this to be able to scale as far as possible.  Here is how I
plan to proceed, and I'd welcome any comments and feedback that you
can give me.  After I have placed the systems into production I will
write up a summary and post to the list.
Since the systems will be installed 3500 miles away from our main
facility, I would like to make them as resilient as possible.  I am
planning on using disksuite (whatever it is called these days) to
perform RAID0 mirroring between the two 36Gb drives.  Accordingly, I
would create a rather large /var with more inodes than default, since
mail spool files are generally small and copious.  I'm wondering,
however, if using disk striping would be a better decision (for /var,
anyway) since the filesystem will incur lots of reads and writes.  My
concern with striping is that if one disk fails, how easily will I be
able to remotely recover the machine having it use just one disk until
I get another disk shipped out?  And are there any other performance
penalties that I might incur here?
As far as sendmail goes, I will most likely be compiling my own
version of sendmail 8.13.1 and playing with some of the new options
for fine tuning of queue runners and the like.  I figure that I will
have some wiggle room here since our current performance isn't that
bad (with 8.11.7p1+SUN running a fairly standard configuration).
Anyway, I would appreciate any feedback or experience in dealing with
busy mail servers and RAID/striping.  Thank you!
------------------------------
Message: 7
Date: Tue, 23 Nov 2004 09:15:50 -0800 (PST)
From: Tony Magtalas <ttk67@yahoo.com>
Subject: How to change MAC address and hostid in Sun's 280R
	(correction)
To: Sun Managers List <sunmanagers@sunmanagers.org>
Message-ID: <20041123171550.26383.qmail@web81610.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Does anybody know how to modify the content of the
NVRAM in a Sun's 280R, specifically to change the
MAC address or hostid etc... after battery goes dead?
I used to be able to do it in older systems such as
Ultra 1,2,10,220R using the "mkpl" commands.
Now when I tried to use mpk and mpkl commands at the
ok prompt on a 280R, it says command not recognized
Please help.
I will summarize if there is enough interest
Tony
------------------------------
Message: 8
Date: Tue, 23 Nov 2004 13:15:53 -0500
From: "Pawel Branski" <pawel.branski@foreseeresults.com>
Subject: SUMMARY: Solaris 8 to 9 upgrade problem with disk space
To: <sunmanagers@sunmanagers.org>
Cc: pbranski@gmail.com
Message-ID:
	<048CCF2084B1A24B9366E16D6AF177BECBEC21@MAIL.foreseeresults.com>
Content-Type: text/plain; charset="us-ascii"
Thank you to Caper Dik for help - /usr file system was over 68% full.
I was able to get the procedure to work.  I used jump start server with
Solaris 09/04.  The upgrade recognized the SVM with out any problems - I
did not have to un-mirror root.
The problem I had was with the /usr file system too small.
Pawel
-----Original Message-----
From: sunmanagers-bounces@sunmanagers.org
[mailto:sunmanagers-bounces@sunmanagers.org] On Behalf Of Pawel Branski
Sent: Tuesday, November 16, 2004 9:45 AM
To: sunmanagers@sunmanagers.org
Cc: pbranski@gmail.com
Subject: Solaris 8 to 9 upgrade problem with disk space
Hi,
I am working on the Solaris 8 to Solaris 9 upgrade procedure.  The
system is running Solaris 8 recommended patch level 08/04 with SVM
(SDS), used to mirror the internal drives.
According to sun docs starting from 04/04 upgrade will recognize SVM -
this seems to be working.
According to sun docs I would need around 2GB of free space to have full
release of Solaris 9 installed.
During the upgrade process installation I am always asked to provide
more disk space.  The original swap file I have was 1.38GB size, I
thought this could be a problem - so I have created additional swap
space on slice 6 - size 5.00GB - still the same problem.  I am attaching
some stats from the system as well as the error message from the
installation process.
I try the installation from Jump server and from the CD.
Please let me know what I am missing in this procedure.  I will
summarize.
Thank you,
Pawel
Info from installation process:
Searching disks for upgradable Solaris root devices...
The following root devices were found to be upgradable:
        Release         Root Device
        -----------     --------------
        Solaris 8       d30 (c0t0d0s0 c0t1d0s0)
Searching for locations to accommodate a temporary copy of the Solaris
installation software.  Swap slices are usually erased at reboot, so it
is
preferable to place the Solaris installation software on slice labeled
swap.
No swap slices that begin at the first usable cylinder have enough space
to accommodate a temporary copy of the Solaris installation software.
Using a slice that begins at the first usable cylinder allows the most
flexibility during filesystem layout. If you are doing an initial
install and
you are not preserving any filesystems, you can re-partition a disk with
the
swap slice starting at the first usable cylinder.
.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers