Sponsored Content
Full Discussion: prtdiag -v troubleshooting
Operating Systems Solaris prtdiag -v troubleshooting Post 302643319 by jlliagre on Saturday 19th of May 2012 04:12:43 AM
Old 05-19-2012
That's a memory module (DIMM) :

SYS = system
MB = main (or mother) board
CMP1 = CPU Module #1
BR1 = Branch #1
CH1 = Channel #1
D0 = DIMM #0

Last edited by jlliagre; 05-19-2012 at 09:36 AM..
 

10 More Discussions You Might Find Interesting

1. Solaris

equivalent prtdiag and prtconf command

I have a very old sunOS 4.xx server on a SPARCstation 5. What is the command , if any, that is similar to prtdiag and prtconf? Thanks (4 Replies)
Discussion started by: antalexi
4 Replies

2. UNIX for Dummies Questions & Answers

Question on prtdiag output ...

Hello all , This is the output of my prtdiag command ...The speed of each of the CPUs is listed below (1281 MHz ) ..That's fine ..I'm confused about the (System clock frequency: 183 MHZ ) ..What is the difference between System Clock freq and CPU freq ...THanks.. System Configuration: Sun... (5 Replies)
Discussion started by: luft
5 Replies

3. Solaris

Prtdiag is Not working in Solaris 8 Ver

Hello Guys, :confused: I have tried Up to my Levels pls help me if u know any solution Pls look out the following O/P, Log Messages ================================================= SUN> pwd /usr/platform/SUNW,Sun-Fire-V240/sbin SUN> SUN> SUN> prtdiag -v bash: prtdiag: command not... (7 Replies)
Discussion started by: sure.solaris
7 Replies

4. Solaris

prtdiag and memory banks

hi, we have an e6900 and my sys admin says that the number of processors and memory were reduced to 4 and 8GB. However, a prtdiag |grep Memory returns 16GB of memory. So what is my system's memory? psrinfo returns 4 online and 4 offline CPUs. Thanks. Kumar (1 Reply)
Discussion started by: kumar27
1 Replies

5. Solaris

prtdiag - Segmentation Fault

Hi, Recently installed a Firmware patch on T5120 (solaris 10,138888-03). The patch installation was Success and system came up fine as well. My apps are running fine too. Problem is prtdiag does not work as it used to earlier. the output is very different from other t5120s I have and... (1 Reply)
Discussion started by: upengan78
1 Replies

6. Solaris

SF T2000 prtdiag problem

Hi, a couple of T2000 servers did not show the component status and the output was too short. There was a patch that needed to be installed. I also updated to the latest recommended patch cluster and OBP patch. After reboot/restart of picl, it worked ok for a couple of weeks. Then suddenly it went... (12 Replies)
Discussion started by: incredible
12 Replies

7. UNIX for Advanced & Expert Users

prtdiag -v show no output

Dear All....Help required prtdiag -v command shows no output on my V440 server. Following is the details: root@sdp16b>prtdiag -v root@sdp16b> root@sdp16b>uname -a SunOS sdp16b 5.9 Generic_122300-31 sun4u sparc SUNW,Sun-Fire-V440 root@sdp16b>echo $path /usr/sbin /usr/bin /usr/sbin... (6 Replies)
Discussion started by: Junaid
6 Replies

8. UNIX for Dummies Questions & Answers

Interpreting prtdiag output - 2 or 4 CPUs?

I am having trouble figuring this one out.....Is this a 2CPU or a 4CPU v490 with 16GB? I think it is a 2CPU system, looking for confirmation. $ prtdiag System Configuration: Sun Microsystems sun4u Sun Fire V490 System clock frequency: 150 MHz Memory size: 16384 Megabytes ... (1 Reply)
Discussion started by: config_boy
1 Replies

9. Solaris

Understanding memory config with prtdiag -v

Hi. I have 2 SunFire V490 servers running Solaris 10. We may have to upgrade with more memory on one of them to make it compatible with the other. Here's the one with 12GB of RAM: Memory size: 12288 Megabytes ========================= CPUs =============================================== ... (1 Reply)
Discussion started by: th1amigo
1 Replies

10. Solaris

prtdiag

Hi everyone, Please can you tell me what kind of memro we are talking about when we run : prtdiag -v Memory size: 98016 Megabytes Thank you (7 Replies)
Discussion started by: adilyos
7 Replies
cosEventApp(3erl)					     Erlang Module Definition						 cosEventApp(3erl)

NAME
cosEventApp - The main module of the cosEvent application. DESCRIPTION
To get access to the record definitions for the structures use: -include_lib("cosEvent/include/*.hrl"). This module contains the functions for starting and stopping the application. EXPORTS
install() -> Return Types Return = ok | {'EXCEPTION', E} | {'EXIT', R} This operation installs the cosEvent application. uninstall() -> Return Types Return = ok | {'EXCEPTION', E} | {'EXIT', R} This operation uninstalls the cosEvent application. start() -> Return Types Return = ok | {error, Reason} This operation starts the cosEvent application. stop() -> Return Types Return = ok | {error, Reason} This operation stops the cosEvent application. start_channel() -> Channel Types Channel = #objref This operation creates a new instance of a Event Channel using the default settings. start_channel(Options) -> Channel Types Options = [Option] Option = {pull_interval, Seconds} | {typecheck, Boolean} | {maxEvents, Integer} | {blocking, Boolean} Channel = #objref This operation creates a new instance of a Event Channel * {pull_interval, Seconds} - determine how often Proxy Pull Consumers will check for new events with the client application. The default value is 20 seconds. * {typecheck, Boolean} - if this option is set to true the proxies will check if the supplied client object is of correct type. The default value is false. * {maxEvents, Integer} - this option determine how many events the ProxyPullSuppliers will store before discarding events. If the limit is reached events will be discarded in any order. The default value is 300. * {blocking, Boolean} - this option determine the behavior of the channel when handling events internally. If set to true the risk of a single event supplier floods the system is reduced, but the performance may also be reduced. The default value is true . start_channel_link() -> Channel Types Channel = #objref This operation creates a new instance of a Event Channel , which is linked to the invoking process, using the default settings. start_channel_link(Options) -> Channel Types Options = [Option] Option = {pull_interval, Seconds} | {typecheck, Boolean} | {maxEvents, Integer} | {blocking, Boolean} Channel = #objref This operation creates a new instance of a Event Channel , which is linked to the invoking process, with settings defined by the given options. Allowed options are the same as for cosEventApp:start_channel/1 . stop_channel(Channel) -> Reply Types Channel = #objref Reply = ok | {'EXCEPTION', E} This operation stop the target event channel. Ericsson AB cosEvent 2.1.10 cosEventApp(3erl)
All times are GMT -4. The time now is 05:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy