Sponsored Content
Special Forums Hardware Updating OBP on a Sun Sunfire 280R Post 302419349 by DukeNuke2 on Friday 7th of May 2010 01:48:47 AM
Old 05-07-2010
you need to download this:
#118323-01: Sun Blade 1000, Sun Fire 280R, Netra[tm] T20, Sun Blade 2000
and follow the instructions inside the files README!
 

10 More Discussions You Might Find Interesting

1. Solaris

pls help urgently....for SUNfire 280R

hi, i hv received SUNfire 280R system ........for its initial configuration i want to connect to it through hyperterminal from the windows system..........i hv got one serial port to RJ-45 port converter with the system............can anybody tell me the normal console cable which is used to... (3 Replies)
Discussion started by: girish_shukla
3 Replies

2. Solaris

how to do live upgrade from solaris8 to 9 for sunfire 280R?

hi!!!!!! how to upgrade sunfire 280R server from solaris8 to solaris9? pls help me. Thanks & Regards -Vishal (1 Reply)
Discussion started by: Vishal Shroff
1 Replies

3. Solaris

Sunfire 280R Can't Recognize Floppy Drive

Greetings all, I'm in a bit of a situation. I have this Sunfire 280R system that did not have a floppy drive in it, yet we needed one. We grabbed one from another Sun box we had laying around unused, and installed it. The system couldnt recognize it. Tried another floppy drive (non-sun) and... (4 Replies)
Discussion started by: snackiesmores
4 Replies

4. Solaris

Sunfire 280R disks ?

Hi there Does anybody know what the biggest capacity disk I can get into a Sunfire 280R I currently have two 73gb disks , but I need to get these up to the biggest available Any help would be greatly appreciated (4 Replies)
Discussion started by: hcclnoodles
4 Replies

5. Solaris

replacing root disk SunFire 280R

Hi, We had a disk go bad in this SunFire 280R, running Solaris 8 - Generic_117350-46. We replaced the disk and partitioned it. We metadetached all the metadevices but for some reason the new disk is showing up in the metadb as Concat/Stripe and it won't let us re-sync the mirror. We are not... (2 Replies)
Discussion started by: mgb
2 Replies

6. Solaris

Sunfire 280R Solaris 5.9 booting

Hi, I have to question: 1) when O/S is booting, i see messages: /dev/rdsk/c1t0d0s5: is logging /dev/rdsk/c1t0d0s3: is logging /dev/rdsk/c1t0d0s7: is logging i partitioned these slices during installation of O/S 5.9. I can access to these mountpoint no problem. But... (3 Replies)
Discussion started by: lamoul
3 Replies

7. Solaris

Install Network component on Sunfire 280R Solaris 5.9

hi, i just completed installing O/S 5.9 on Sunfire 280R with O/S 5.9. During installation, i wasn't able to add IP, Default gateway, NDS and netmask because the lan port wasn't not active yet. Now that i have a lan port active, how to add network components onto the system? I did ifconfig to... (1 Reply)
Discussion started by: lamoul
1 Replies

8. Solaris

Patch update on sunfire 280R sparc for solaris 5.9

Hi, i just finished installing solaris 5.9 and I'm looking for the tools to tell me if i should update the patches or how to make sure that the current patches are ok? thanks (2 Replies)
Discussion started by: lamoul
2 Replies

9. Solaris

Install SUN O/S 5.9 on Sparc Sunfire 280R

Hi, I' trying to install O/S 5.9 on Sparc system Sunfire 280R. I downloaded CD install and CD 2 from Sun Website but later i dowloaded CD 2 that i forgot for my installation. All CD are in ISO formats. I boot system at OK prompt then issue OK boot cdrom when it asks for CD 1, i removed... (7 Replies)
Discussion started by: lamoul
7 Replies

10. Hardware

SunFire 280R maintenance LED is on and no display

I got the system couple of days back from one of my friend. Last night I turned it on and I noticed that maintenance LED is on. At the same time I added an LCD monitor via VGA and nothing was showing on the screen. Though the system does not have any HDD So not sure if system will even show a BIOS... (3 Replies)
Discussion started by: pgirish007
3 Replies
Kstat(3PERL)															      Kstat(3PERL)

NAME
Kstat - Perl tied hash interface to the kstat facility SYNOPSIS
use Sun::Solaris::Kstat; Sun::Solaris::Kstat->new(); Sun::Solaris::Kstat->update(); Sun::Solaris::Kstat->{module}{instance}{name}{statistic} Kernel statistics are categorized using a 3-part key consisting of the module, the instance, and the statistic name. For example, CPU information can be found under cpu_stat:0:cpu_stat0, as in the above example. The method Sun::Solaris::Kstat->new() creates a new 3-layer tree of Perl hashes with the same structure; that is, the statistic for CPU 0 can be accessed as $ks->{cpu_stat}{0}{cpu_stat0}. The fourth and lowest layer is a tied hash used to hold the individual statistics values for a particular system resource. For performance reasons, the creation of a Sun::Solaris::Kstat object is not accompanied by a following read of all possible statistics. Instead, the 3-layer structure described above is created, but reads of a statistic's values are done only when referenced. For example, accessing $ks->{cpu_stat}{0}{cpu_stat0}{syscall} will read in all the statistics for CPU 0, including user, system, and wait times, and the other CPU statistics, as well as the number of system call entries. Once you have accessed a lowest level statistics value, calling $ks->update() will automatically update all the individual values of any statistics you have accessed. There are two values of the lowest-level hash that can be read without causing the full set of statistics to be read from the kernel. These are "class", which is the kstat class of the statistics, and "crtime"n, which is the time that the kstat was created. See kstat(3KSTAT) for full details of these fields. Methods new() Create a new kstat statistics hierarchy and return a reference to the top-level hash. Use it like any normal hash to access the statistics. update() Update all the statistics that have been accessed so far. In scalar context, update() returns 1 if the kstat structure has changed, and 0 otherwise. In list context, update() returns references to two arrays: the first holds the keys of any kstats that have been added, and the second holds the keys of any kstats that have been deleted. Each key will be returned in the form "module:instance:name". Example 1: Sun::Solaris::Kstat example use Sun::Solaris::Kstat; my $kstat = Sun::Solaris::Kstat->new(); my ($usr1, $sys1, $wio1, $idle1) = @{$kstat->{cpu_stat}{0}{cpu_stat0}}{qw(user kernel wait idle)}; print("usr sys wio idle "); while(1) { sleep 5; if ($kstat->update()) { print("Configuration changed "); } my ($usr2, $sys2, $wio2, $idle2) = @{$kstat->{cpu_stat}{0}{cpu_stat0}}{qw(user kernel wait idle)}; printf(" %.2d %.2d %.2d %.2d ", ($usr2 - $usr1) / 5, ($sys2 - $sys1) / 5, ($wio2 - $wio1) / 5, ($idle2 - $idle1) / 5); $usr1 = $usr2; $sys1 = $sys2; $wio1 = $wio2; $idle1 = $idle2; } perl(1), kstat(1M), kstat(3KSTAT), kstat_chain_update(3KSTAT), kstat_close(3KSTAT), kstat_open(3KSTAT), kstat_read(3KSTAT) As the statistics are stored in a tied hash, taking additional references of members of the hash, such as my $ref = ks->{cpu_stat}{0}{cpu_stat0}{syscall}; print("$$ref "); will be recorded as a hold on that statistic's value, preventing it from being updated by refresh(). Copy the values explicitly if persis- tence is necessary. Several of the statistics provided by the kstat facility are stored as 64-bit integer values. Perl 5 does not yet internally support 64-bit integers, so these values are approximated in this module. There are two classes of 64-bit value to be dealt with: 64-bit intervals and timThese are the crtime and snaptime fields of all the statistics hashes, and the wtime, wlentime, wlastupdate, rtime, rlentime and rlastupdate fields of the kstat I/O statistics structures. These are measured by the kstat facility in nanoseconds, meaning that a 32-bit value would represent approximately 4 seconds. The alternative is to store the values as floating-point numbers, which offer approximately 53 bits of precision on present hardware. 64-bit intervals and timers as floating point values expressed in seconds, meaning that time-related kstats are being rounded to approximately microsecond resolution. 64-bit counters It is not useful to store these values as 32-bit values. As noted above, floating-point values offer 53 bits of precision. Accordingly, all 64-bit counters are stored as floating-point values. 21 Jul 2005 Kstat(3PERL)
All times are GMT -4. The time now is 10:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy