Sponsored Content
Full Discussion: LPAR CPU capacity planning
Operating Systems AIX LPAR CPU capacity planning Post 302804437 by gsaray101 on Wednesday 8th of May 2013 02:56:52 PM
Old 05-08-2013
AIX CPU sizing and threshold

I have to admit, this couldn't be more confusing. Do you know of any documentation that that explain this stuf.
 

7 More Discussions You Might Find Interesting

1. Solaris

Planning for DR, I have to collect information

Dear All, We are going for Disaster Recovery project, the vendor asked for more details about how much is the daily data changes only. using sar / iostat can any one help me to collect this ?! Note: only I need the changed data size not the daily increasing data. this is to know how much... (1 Reply)
Discussion started by: adel8483
1 Replies

2. What is on Your Mind?

Planning to be certified , your advice?

Hi, I got 2 courses Intermediate and advanced Solaris 10 Administration before 1 month. I was studying the material of the 1st course I will finish it soon. I want to get the Exam. What is your advice? Which is the best Exam Quastion ( Testking or ,,,,,,,, Etc) .... Regards (1 Reply)
Discussion started by: adel8483
1 Replies

3. AIX

capacity planning on aix

Hi All, What do you usually use for capacity planning on AIX? Any idea will do? Thanks in advance, itik (1 Reply)
Discussion started by: itik
1 Replies

4. Solaris

tools for capacity planning

Hi All, What do you usually use for capacity planning tool on solaris 8 or later? Thanks in advance. (2 Replies)
Discussion started by: itik
2 Replies

5. AIX

LPAR freezes after switching of storage (lpar is mirrored)

Hi all, I have the following configuration 2 ds3524 storage disk systems located over 2 locations 2 P720 server located over 2 locations DS3524 are connected to san switch. Each vio server has 1 fc adapter attached to a san switch. per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Discussion started by: markiemark
2 Replies

6. AIX

How to differentiate between a standalone LPAR and a VIOC (which again is a lpar)?

There can be configurations in IBM Server wherein a standalone partition is created on some supported IBM Server Or A VIOS - VIOC LPARs created. Now in both cases they are lpars. But if I want to differentiate b/w a standalone LPAR vs an VIOC LPAR how can I do..? On a... (2 Replies)
Discussion started by: Manish00712
2 Replies

7. AIX

FS capacity

can anyone tell me how to reduce Fs capacity by using echo zero. (3 Replies)
Discussion started by: nkchand
3 Replies
CPU(1)							      General Commands Manual							    CPU(1)

NAME
cpu - connection to cpu server SYNOPSIS
cpu [ -h server ] [ -c cmd args ... ] DESCRIPTION
Cpu starts an rc(1) running on the server machine, or the machine named in the $cpu environment variable if there is no -h option. Rc's standard input, output, and error files will be /dev/cons in the name space where the cpu command was invoked. Normally, cpu is run in an 81/2(1) window on a terminal, so rc output goes to that window, and input comes from the keyboard when that window is current. Rc's cur- rent directory is the working directory of the cpu command itself. The name space for the new rc is an analogue of the name space where the cpu command was invoked: it is the same except for architecture- dependent bindings such as /bin and the use of fast paths to file servers, if available. If a -c argument is present, the remainder of the command line is executed by rc on the server, and then cpu exits. The name space is built by running /usr/$user/lib/profile with the root of the invoking name space bound to /mnt/term. The service envi- ronment variable is set to cpu; the cputype and objtype environment variables reflect the server's architecture. FILES
The name space of the terminal side of the cpu command is mounted on the CPU side on directory /mnt/term. SOURCE
/sys/src/cmd/cpu.c SEE ALSO
rc(1), 81/2(1) BUGS
Binds and mounts done after the terminal lib/profile is run are not reflected in the new name space. CPU(1)
All times are GMT -4. The time now is 10:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy