On Thu, 5 Nov 2009, Zia-ul-Hassan Zia wrote: Before getting into the specifics, the usual points apply:
Solaris 9 is getting old and you should look at upgrading rather than complex patching. SRSS 3.0 is getting pretty old and you should probably look at a new release of SRSS (it's faster! better! steakier!) If these boxes aren't well maintained, test all changes on a model. If they are well maintained, test all changes on a model. Make sure you have a backout strategy, even if it's just splitting the mirrors before getting to work. Recruit some assistance if you need to. Even if it's just getting some solid advice and a poke through the current situation. It's rumoured that a bottle of whisky or a big steaky lunch will recruit a variety of seasoned professionals for a quick consult. > 1: Are these issues related to old firmware on clients? If I upgrade > firmware on server will it be automatically pushed to servers. I have no > past experience managing SUN Ray controller or client so unsure about it? It should be pushed to the clients automatically, but you may need to use ... > 2: How I can detect the current Firmware on server, I can see a few firmware > related commands in manual (utfwadm,utfwload,utfwsync)? Yep. They all have man pages and are pretty simple. > > 3:- Where from I can download the latest SUN Ray firmware for SRS 3.0? I try > to find on SUN standard software site but couldn't get it. Or it's part of > patch 114880-12? It's in the patches. You could also just fire up a new version of SRSS - it might actually make life easier. Firmware is backwards compatible, too, so if you fancy cheating you could slam all the DTUs with new, current firmware and then plonk them back on your old SRSS instance. > 4: I presume the latest 9_Recommended patch bundle would address the DST > issue or should I just apply the latest DST patch for Solaris 9 113225-17 > (SPARC)?. I'd be pretty careful about deploying a 9_Rec on production servers - make sure you test it on a model first, especially if they've been unmaintained for a long time. -- Andre van Eyssen. mail: andre at purplecow.org jabber: andre at interact.purplecow.org purplecow.org: UNIX for the masses http://www2.purplecow.org purplecow.org: PCOWpix http://pix.purplecow.org
