Sponsored Content
Operating Systems AIX How to check the LPAR in a AIX box ? Post 302571208 by gito on Sunday 6th of November 2011 08:20:46 PM
Old 11-06-2011
How you are logging to that server without IP? do you have HMC?
Just seeing the hostname i am quite sure it is not a VIO..
have you checked prtconf ?
Code:
lsdev -Cc disk


Last edited by zaxxon; 11-07-2011 at 05:47 AM.. Reason: code tags please
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

difference between AIX box and Sun Solaris box

Hi, I need a clarification. Is there any difference between AIX box and Sun Solaris box? The bzip command with -c option works in AIX box and the same does not work in Sun Solaris box. Can anyone please explain if there is an implementation difference in both these boxes for the shell... (1 Reply)
Discussion started by: nisha4680
1 Replies

2. AIX

Setting Dual Ip address on LPAR AIX 5.3

Hi Guys, Can somebody help me how to add and activate addtional ip address on AIX. My server is IBM p5-570 i already set ipadress on ent1 ent0 -- 192.168.206.105 ( default ) ent1 -- 192.168.0.89 (additional) i can ping from outside to 192.168.0.89 but i can not telnet or ftp. for... (6 Replies)
Discussion started by: cahyo3074
6 Replies

3. AIX

p6 570 network for AIX LPAR

know how to do it. (3 Replies)
Discussion started by: rainbow_bean
3 Replies

4. AIX

How to Find if AIX machine is LPar or not

Hi, I want to know if there is any command which will tell me if an AIX machine is a LPar or not. I am using "lparstat -i" but it does not work on all AIX machines. Is there any generic command by whose output I will come to know if it is an LPar or not? Please help. Thanks, Vineet (3 Replies)
Discussion started by: vineetd
3 Replies

5. AIX

AIX admin - lpar question

Hi Guru, my question is that can I create LPAR in AIX 5.3, 6.0, 6.1 by using smit lpar, rather than using HMC or AIX Commands? Thank you very much. Mir Alihttp://xwww.unix.com/images/icons/icon5.gif (3 Replies)
Discussion started by: Tahniet
3 Replies

6. AIX

AIX 5.2.0 on own hardware -> i550 LPAR

We are running into a problem that we thought had solved but no go... We have multiple machine types but 1 AIX and 2 i550 (AS/400) with 4 lpar each. Existing AIX is an old (2004 vintage) machine with 5.2 on it for historical use only. Existing Power6 i550 running code that will used... (6 Replies)
Discussion started by: jackb_guppy
6 Replies

7. AIX

Newbie - AIX LPAR performance problem

Running into performance issues with WAS application servers on two of LPAR's or like configuration under high load web pages crawl. Please forgive me I'm new to AIX and most my expertise is in the Linux space. Thanks for your help!! Here's the run down: The problem appears to be CPU... (3 Replies)
Discussion started by: margeson
3 Replies

8. AIX

Will it affect my AIX LPAR security, when i set up email alerts on AIX server.

Hello, I've set up email alerts on AIX Servers. so that i can get email notifications (via mail relay server) when ever there is abnormal behavior. for example 1) my script monitors CPU/disk/memory etc... when it reaches high water ark, it will send an email alert. 2) disk usage alerts 3)... (5 Replies)
Discussion started by: System Admin 77
5 Replies

9. AIX

AIX LPAR FC connection to SAN

Hi all, In my system, I have HMC 7 with Power Machine 6 & 7. On the managed system, we have many lpars. In some lpars, I can see they are using virtual fiber channel to connect to DS8K storage. In search with google, I understand that it is configured with VIOS server to share the physical FC... (7 Replies)
Discussion started by: Phat
7 Replies

10. UNIX for Beginners Questions & Answers

AIX - SAN Mount and Unmount on LPAR

We have 2 LPAR. LPAR #1 have a Application, Database Server process (ctree Server) and SAN+Physical Table. LPAR#2 has only Application. Both Application process are connected to Database via C-tree Server Process (Running on LPAR #1.. We want to keep one Active C-tree Server and one Backup... (1 Reply)
Discussion started by: gabhanes
1 Replies
prtconf(1M)															       prtconf(1M)

NAME
prtconf - print system configuration SYNOPSIS
/usr/sbin/prtconf [-V] | [-F] | [-x] | [-bpv] | [-acDPv] [dev_path] The prtconf command prints the system configuration information. The output includes the total amount of memory, and the configuration of system peripherals formatted as a device tree. If a device path is specified on the command line for those command options that can take a device path, prtconf will only display informa- tion for that device node. The following options are supported: -a Display all the ancestors device nodes, up to the root node of the device tree, for the device specified on the command line. -b Display the firmware device tree root properties for the purpose of platform identification. These properties are "name", "compat- ible", "banner-name" and "model". -c Display the device subtree rooted at the device node specified on the command line, that is, display all the children of the device node specified on the command line. -D For each system peripheral in the device tree, displays the name of the device driver used to manage the peripheral. -F Returns the device path name of the console frame buffer, if one exists. If there is no frame buffer, prtconf returns a non-zero exit code. This flag must be used by itself. It returns only the name of the console, frame buffer device or a non-zero exit code. For example, if the console frame buffer on a SUNW,Ultra-30 is ffb, the command returns: /SUNW,ffb@1e,0:ffb0. This option could be used to create a symlink for /dev/fb to the actual console device. -p Displays information derived from the device tree provided by the firmware (PROM) on SPARC platforms or the booting system on platforms.The device tree information displayed using this option is a snapshot of the initial configuration and may not accu- rately reflect reconfiguration events that occur later. -P Includes information about pseudo devices. By default, information regarding pseudo devices is omitted. -v Specifies verbose mode. -V Displays platform-dependent PROM (on SPARC platforms) or booting system (on platforms) version information. This flag must be used by itself. The output is a string. The format of the string is arbitrary and platform-dependent. -x Reports if the firmware on this system is 64-bit ready. Some existing platforms may need a firmware upgrade in order to run the 64-bit kernel. If the operation is not applicable to this platform or the firmware is already 64-bit ready, it exits silently with a return code of zero. If the operation is applicable to this platform and the firmware is not 64-bit ready, it displays a descriptive message on the standard output and exits with a non-zero return code. The hardware platform documentation contains more information about the platforms that may need a firmware upgrade in order to run the 64-bit kernel. This flag overrides all other flags and must be used by itself. The following operands are supported: dev_path The path to a target device minor node, device nexus node, or device link for which device node configuration information is displayed The following exit values are returned: 0 No error occurred. non-zero With the -F option (SPARC only), a non-zero return value means that the output device is not a frame buffer. With the -x option, a non-zero return value means that the firmware is not 64-bit ready. In all other cases, a non-zero return value means that an error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWesu | +-----------------------------+-----------------------------+ |Interface Stability |Unstable | +-----------------------------+-----------------------------+ fuser(1M), modinfo(1M), sysdef(1M), attributes(5) Sun Hardware Platform Guide SPARC Only openprom(7D) The output of the prtconf command is highly dependent on the version of the PROM installed in the system. The output will be affected in potentially all circumstances. The driver not attached message means that no driver is currently attached to that instance of the device. In general, drivers are loaded and installed (and attached to hardware instances) on demand, and when needed, and may be uninstalled and unloaded when the device is not in use. On platforms, the use of prtconf -vp provides a subset of information from prtconf -v. The value of integer properties from prtconf -vp might require byte swapping for correct interpretation. 9 Aug 2005 prtconf(1M)
All times are GMT -4. The time now is 02:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy