02-16-2010
There are 4, 6 and 8 core UltraSPARC-T2 CPUs available. A 4 core will display 32 virtual processors while a 8 core will display 64 ones.
RAM size isn't related to the number of CPUs or the number of cores inside them.
9 More Discussions You Might Find Interesting
1. Solaris
We used kstat on netra240/440 to check if the link is full duplex. So we do something like:
bash-3.00# kstat -pc net bge:1::/'link_duplex'/ | cut -f2
2
The output 2 indicates the link is full duplex. This kind of check worked all right for Netra 240/440 systems.
However, the nxge... (2 Replies)
Discussion started by: illcar
2 Replies
2. Solaris
I 've 2 different T5220 and both are showing different prompts when i ssh to the console.
1. Shows sc> ALOM
2. Shows -> ILOM
as far as i know the T5220 comes with ILOM , so why i 'm seeing 2 different type of console for same tyep of hardware ?
and i found that we... (6 Replies)
Discussion started by: fugitive
6 Replies
3. Solaris
Hi,
SC on one of my T5220 is not responding .. it does not show not let me type anything .. what could be the reason for it ? though when i powercycle the box from sc it shows me the system coming up but after that does not let me login thru sc
sc> console -f
Enter #. to return to ALOM. (2 Replies)
Discussion started by: fugitive
2 Replies
4. Solaris
We're just about to migrate a large application from an Enterprise 6900 to a pair of T5220s utilising LDOMs. Does anyone have any experience of LDOMs on this kit and can provide any recommendations or pitfalls to avoid?
I've heard that use of LDOMs can have an impact on I/O speeds as it's all... (9 Replies)
Discussion started by: JerryHone
9 Replies
5. Solaris
Hi Guys and Gals,
Wondering if anyone could help me, tricky one this.
Got a T5220 with a graphics card. When you power it on, it outputs its output to the screen and you can type commands with the keyboard etc.
But no matter what version of Solaris 10 you use, when you do a boot cdrom... (1 Reply)
Discussion started by: callmebob
1 Replies
6. Solaris
Hello guys,
can anyone give me some advice on how to perform
clean installation of Solaris 10 on T5220 ?
I am connected with serial management port on the machine,
i have the ok promt and now i should eject the dvdrom to insert
Solaris dvd into and start the clean install.
So how to do that... (3 Replies)
Discussion started by: tonijel
3 Replies
7. Solaris
Hi all,
I have written the following program and run on both T5440 and T5220 on same OS version. I found that T5540 server takes more time than T5220. Please find below the details.
test1.cpp
#include <iostream>
#include <pthread.h>
using namespace std;
#define NUM_OF_THREADS 20... (17 Replies)
Discussion started by: sanjay_singh85
17 Replies
8. Solaris
Hi,
I got a (used) server to install Solaris 11 and wipe out every information on existing disks. There are 6 disks of 300GB and two disks of 146GB. I am not able to figure out, how to find out RAID (if there is any) and break it. Can anybody help me with that ? Below is configuration. I have... (18 Replies)
Discussion started by: solaris_1977
18 Replies
9. Solaris
hi:)
i can't boot my sun server by iso solaris 10 sparc dvd that i did download from oracle site.
my hardware is sun T5220.
i receive these after running boot cdrom -s :
can't read disk lable
can't open disk lable package
ERROR: boot-read fail
whould u help me?
Please use CODE... (1 Reply)
Discussion started by: Arefdel
1 Replies
GCORE(1) General Commands Manual GCORE(1)
NAME
gcore - get core image of running process
SYNOPSIS
gcore [-s][-c core] pid
DESCRIPTION
gcore creates a core image of each specified process, suitable for use with adb(1). By default the core image is written to the file
<pid>.core.
The options are:
-c Write the core file to the specified file instead of <pid>.core.
-s Stop the process while creating the core image and resume it when done. This makes sure that the core dump will be in a consistent
state. The process is resumed even if it was already stopped. Of course, you can obtain the same result by manually stopping the
process with kill(1).
The core image name was changed from core.<pid> to <pid>.core to prevent matching names like core.h and core.c when using programs such as
find(1).
FILES
<process-id>.core The core image.
BUGS
If gcore encounters an error while creating the core image and the -s option was used the process will remain stopped.
Swapped out processes and system processes (the swapper) may not be gcore'd.
4.2 Berkeley Distribution April 15, 1994 GCORE(1)