vPar Hardware Paths


 
Thread Tools Search this Thread
Operating Systems HP-UX vPar Hardware Paths
# 1  
Old 09-02-2009
vPar Hardware Paths

I wonder if anyone could assist with this.

We have taken over administration of an rp8440 that has been split into 2 nPars and has 4vPars per nPar.

I have to add a network card into one of the vPars that was missed at the time the vPar was created. That bit i have no problem with.

The issue i have is that i do not know which of the available resources relates to this i/o slot, so i wonder if anyone could give me any ideas on how to find this out. I am sure there must be a way of working it out, but i cannot figure it out.

I know the card is in chassis 0, slot 1

Available resources from vparstatus -A command

[Available I/O devices (path)]: 0.0.1
0.0.2
0.0.8
0.0.10
0.8.1
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. HP-UX

How to shutdown a vpar from another vpar?

Hi, How can I shutdown a vpar from another vpar ? Please provide the command. Thanks. (0 Replies)
Discussion started by: snchaudhari2
0 Replies

2. HP-UX

VPAR Resource Capacity Limit

Hello Guys Could you please let me know the command to find the resource (vCPU & Memory) capacity limit for the VPAR's (HPUX 11.23) on integrity Virtual host servers running HPUX 11.31 OS. For eg. I want to know what is the max vCPU and memory that I can assign to one VPAR. The Base Virtual... (0 Replies)
Discussion started by: prvnrk
0 Replies

3. HP-UX

VPar hardware migration - ERRATA document

Hi guys, I'm moving some vPars from BL860c I2 and BL870c I2 using the DRD clone and relocation. In some case, as instance to upgrade to BL870c I2, the ERRATA document reports some additional driver to be added to the image made by the DRD and then recompile the kernel before the move to the... (0 Replies)
Discussion started by: cecco16
0 Replies

4. Programming

Can't find paths.h

I wasn't sure which forum to post this in. I am trying to compile logsurfer. After I run configure and the make, I get a complaint that paths.h is not found. I see three places where there is a paths.h: /usr/include/pgsql/server/optimizer/paths.h... (3 Replies)
Discussion started by: brownwrap
3 Replies

5. Solaris

Hardware faulty, but which hardware?

Hi folk, I have this hardware faunty message, but dont know which hardware is this ? can you guide me ? --------------- ------------------------------------ -------------- --------- TIME EVENT-ID MSG-ID SEVERITY ---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies

6. HP-UX

vPar Boot Error

Hi All, Please help me out in below issue in creating vPar. We have one nPar in which we have to create 2 vPars, out of which first vPar is already created and it is running well which have local disk as a boot device.Now we have to create 2nd vPar which need to use SAN disk for booting.... (3 Replies)
Discussion started by: laxmikant
3 Replies

7. HP-UX

vpar ignite

Hi Can I use a vpar as an ignite server? (1 Reply)
Discussion started by: mahlathini
1 Replies

8. UNIX for Advanced & Expert Users

Spoofing paths.

There is a program that I am trying to run on a shell account. It depends on another program, which I have also copied to the shell account. Both are in my home directory, yet the first program has a different path hardcoded into it, which I cannot use because of permissions problems. How can I... (3 Replies)
Discussion started by: fahadsadah
3 Replies

9. UNIX for Dummies Questions & Answers

create paths

Hello! If I have file like that: AAA ->bbb ->ccc ->ddd ->eee how to create full paths like: AAA->bbb AAA->ccc->ddd AAA->ccc->eee ? (I'm sorry for mistakes - english is not my native language) :) (4 Replies)
Discussion started by: alias47
4 Replies

10. UNIX for Dummies Questions & Answers

paths

Hi there! People, i'm a new unix user, and i'm having some problems... I'm updating some scripts (korn shell) in different servers. I use telnet to access these servers and emacs to write the scripts. One of them is an HP, and there´s no problem. But the other one is an AIX, and when i call... (1 Reply)
Discussion started by: caiohn
1 Replies
Login or Register to Ask a Question
vparstatus(1M)															    vparstatus(1M)

NAME
vparstatus - display information about one or more virtual partitions SYNOPSIS
vp_name]... db_file] vp_name] vp_name] DESCRIPTION
The various forms of the command display: o The attributes and hardware resources associated with one or more virtual partitions (vPars), presented in summary format by default. The option presents the same data in detailed format, while the option presents it in machine-readable format. o Resources currently available, that is, not assigned to any virtual partition. The option presents the same data in machine-readable format. o Processor Information Module (PIM) data from the most recent resetting of a virtual partition. o The state, the vPar owning the CPU, and any siblings of any or all CPUs in the vPars environment, presented in summary format by default. The option presents the same data in detailed format, while the option presents it in machine-readable format. The monitor must be running. o The virtual partition monitor event log. o Various monitor-related data items, such as the file name and path of the active monitor, and the active DB file. The option presents the same data in machine-readable format. The monitor must be running. o The name of the local virtual partition, that is, the virtual partition from which the command is run. The option displays only the name. Otherwise a full sentence that includes the name is displayed. o The version number of the output format. There are two major display groups, one for vPars and a second for CPU/memory configuration. Each is subdivided into one of three listing formats: summary, detailed or verbose, and machine-readable. All are described below. vPars: If no arguments are supplied and the virtual partition monitor is running, displays a summary format of all attributes and resources of all vPars in the monitor database. One or more vPars may be specified explicitly in order to restrict the output to information about the specified vPars. The option lists similar information from an alternate database file. If the option is not specified and the monitor is not running, information is taken from the default database if it exists. Otherwise a command error occurs. In either case, there is a major differ- ence in the displayed information. See the description of the option for further details. There are three major vPar listing formats. The format chosen depends on command options and forms: o The summary format lists name, attributes, and resource totals. It is displayed if neither the option is used. o The detailed format lists name, attributes, and detailed resource assignments, one per line with annotative headings. The option pro- duces this format. o The machine-readable format displays the same information as the detailed format, except that field descriptive headers are omitted, and the information is all on one line. Individual fields are separated from each other by four delimiters. The delimiters are all described later. A related display, shows all unassigned (available) resources, either one per line (default) or machine-readable CPU configuration (-d): There are three formats for display of CPU configuration information, and they are similar to those used for vPars. If neither the nor option is specified, a summary display is produced. The option produces a detailed format, while the option results in a machine-readable format. Five additional formats are provided for the and options. When displaying vPar-related information, includes the following: o The version of the command output format (only if has been specified). o The name of the virtual partition (limited to 30 characters in summary format) o The state of the virtual partition. Possible states are listed below. The virtual partition has notified the monitor that it is up. This is the normal state of a running virtual partition. However, it does not necessarily mean that the virtual partition has completed its initialization and is fully operational. The virtual partition is fully halted. This could be the result of a normal command, or a of a partition with its autoboot attribute set to It is also the initial state of a virtual partition immediately after the virtual partition monitor is started. The monitor is loading the kernel image of the virtual partition. This state precedes the Boot state. The virtual partition has been launched, but has not completely booted. The virtual partition is shutting down ungracefully (due to either a panic or a reset) The virtual partition is shutting down gracefully The virtual partition has stopped sending heartbeat messages to the monitor. The virtual partition is in an alternate database file that is not active, and so has no state. o The static/dynamic resource attribute o The auto/manual boot attribute o The search/nosearch boot attribute o The path to the kernel (limited to 23 characters in summary format) o The boot options (limited to 5 characters in summary format) o Summary of detailed CPU, I/O, and memory resource allocations. The summary memory allocation display includes a count of Cell Local Memory (CLM) and InterLeaved Memory (ILM) ranges (both user-specified and monitor-assigned), total megabytes for each memory type, and the granularity (least common multiple) of each memory type. The detailed and machine-readable displays include the actual memory base and size for each range, and the granularity of each memory type. All CPUs except the vPars boot processor may be assigned to or de-assigned from a running vPar. The total count of assigned CPUs is com- prised of several sub-counts. De-assignment must come from the same count as assignment. Refer to the vparresources(5) manpage for details. Assignment or de-assignment of CPUs is called and requires a certain amount of time, especially if a CPU is being deleted from a vPar. A CPU being added is immediately assigned to its target vPar. A CPU being deleted remains assigned to its vPar and does not appear in a dis- play until migration has completely finished. Migrating CPUs are indicated in the various displays as follows: o Summary format: A letter in the column following the Num CPUs count indicates that one or more CPUs are migrating in or out of a vPar. o Detail format: Any CPU that is migrating in or out is indicated by the additional string, o Machine readable format: A separate list of migrating CPUs is added to the display following the list of monitor-assigned CPUs. If no CPU is migrating, this list is empty. Refer to the section below. Assignment or de-assignment of memory is called and requires a certain amount of time, especially if memory is being deleted from a vPar. Memory being added is immediately assigned to its target vPar. Memory being deleted remains assigned to its vPar and does not appear in a display until migration has completely finished. Migrating memory is indicated in the various displays as follows: o Summary format: A letter in the column following the ILM size indicates that ILM memory is migrating in or out of a vPar. A letter in the column following the CLM size indicates that CLM memory is migrating in or out of a vPar. o Detail format: Any memory by size or range that is migrating in or out is indicated by the additional string, o Machine readable format: If there is any pending memory migration, the last sub-field in the memory field will have the letter If no memory is migrating, this field will be empty. Refer to the section below. Virtual partitions may be configured on a partitionable platform such as the HP Superdome. Configuration changes made to the underlying hard partition do become effective until all virtual partitions on that hard partition have been shut down and the virtual partition moni- tor has been rebooted. If a configuration change is pending, the command displays a message to that effect following any summary or detailed display. Refer to "Performing a Reboot for Reconfig for an nPartition" in the for more information. If the option has been specified for either the config- ured resources or available resources, the configuration change message is replaced by an additional field appended to the machine-readable output. Refer to the description of the option. When displaying CPU configuration information, includes the following: o The version of the command output format (only if has been specified). o The hardware path of each specified CPU. o The Hardware Physical Address (HPA) (PA platform) of the processor, or the contents of the processor's Local ID (LID) register (Ita- nium(R)-based platforms). o The CellID of the cell on which the CPU resides. o The status of the CPU, displayed as one or more of the following: Enabld, Inactv, Failed, MarkDC, Pendng o The name of the vPar, if any, to which the CPU is assigned. o If the CPU is one of multiple cores on the same socket, the paths and assigned vPars of all its siblings. Options recognizes the following command line options and arguments: Restricts the command display to information about vp_name. By default, information about all virtual partitions in the monitor database or specified alternate partition data- base is displayed. Multiple vp_names may be specified, except when used to display PIM data or available resources. Displays information from the alternate partition database file db_file rather than from the monitor database. Exception: If the monitor is running and db_file specifies the file originally loaded into the monitor, information is from the monitor's copy of the database. The attributes and resources of a vPar in an alternate database file were specified in either the or command, but have not nec- essarily been checked for existence on a running system. They are referred to as "requested" information. Existence of the attributes and resources of a vPar in the live monitor database have been verified; they are referred to as "effective" infor- mation. If no cpu_path is specified, displays configuration information for all CPUs in the nPar that are known to the monitor. The option may be specified repeatedly with any number of cpu_paths to limit the display to those CPU paths. A summary display is shown by default. When used with the option, a detailed or machine-readable (respectively) display is shown. Displays monitor-related information, such as the hardware path from which the monitor is booted, its file system path, and the file system path of the loaded database. Each item is annotated and shown on its own line unless the option is also specified, which produces a machine-readable, one-line display. Presents a detailed display, one attribute or resource per line. Each attribute and resource type is identified. CPU resources are identified by path, when path information is available, and by count. Some CPU paths may not be known when displaying the status of alternate database vPars or vPars in the state. In this case, is displayed. CPU path information is shown in three lists: o User assigned CPU paths. o The path of the boot processor, the first CPU assigned when the vPar is booted. If the vPar is or in an alternate database, this list is empty. The list has at most one CPU path. o Monitor assigned CPU paths. User assigned CPUs, shown in a separate list (above), are always associated with and assigned to a vPar, even when that vPar is or in an alternate database. The monitor assigns the remaining allocated CPUs only when the vPar is booted. If the vPar is not this list shows the explicit paths of these CPUs. Otherwise, the placeholder is shown for each allocated CPU. Note that the boot processor, if any, is either user assigned or monitor assigned. There are no other CPU categories. If a CPU is shown as the boot processor, the CPU is not shown in either of the other lists. This is so that the sum of processors in the three lists always represents the total CPU allocation of the vPar. CPU count information is also shown in three lists: o The count of user assigned CPUs, always in the non-cell-specific category. o The count of non-cell-specific, monitor assigned CPUs. o A list of counts, by cell, of CPUs designated to be assigned from a specific cell. Since counts do not represent specific paths, they are valid for all vPars, whether or in an alternate database. Counts in an alternate database are "requested". Refer to CPUs and Cell Local Processors in the vparresources(5) manpage for more details on the use of counts. Memory resources are listed by type (ILM or CLM), and within those types by user assigned ranges, monitor assigned ranges, total megabytes, and granularity. If there is any floating memory configured in the vPar, it is indicated by the additional string OL* resources are listed by sequence ID, type of operation (memory add/delete, cpu add/delete) and status of the operation. The OL* details are applicable only if the target virtual partition is Displays information about available resources (that is, those not assigned to any virtual partition) in the virtual partition monitor's database. The monitor must be running. Resources are displayed one per line. The option no longer has any function when used with the option. It is ignored if specified (unless multiply specified, which is still a syntax error). Displays attribute and resource information in a machine-readable format, or restricts output of the option to the name of the local virtual partition. The rest of this description applies only to the attribute and resource display. Individual fields are separated by one of four delimiters. Examples are shown following the delimiter descriptions: o The colon separates each major field, including resource types. o The semicolon separates subfields of a resource type. o The comma separates individual items in a list of similar items. o The slash separates all other related items. There are four machine-readable formats, one for vPar configurations alone), one for available resources one for CPU configura- tion and one for monitor-related data o vPar configurations: The full list of major fields, and their order, is: vPar name, vPar state, attributes, kernel path, boot options, CPU resources, I/O resources, memory resources,OL* resources, reboot for reconfiguration flag. Each vPar is displayed on a separate line, regardless of length. An example of the CPU resources subfields is: where each subfield is interpreted as follows: minimum and maximum CPUs configured for the vPar. path(s) of all user assigned CPUs. (empty): The path of the boot processor. This vPar is so this field is empty. for the four configured CPUs this vPar will have when it is booted. (empty): A list of CPUs undergoing migration (pending). This vPar is so this field is empty. Even if the vPar were this field would only be populated temporarily. The count of user assigned CPUs. The count of non-cell-specific monitor assigned CPUs. The cell ID(1) and count(2) of CPUs designated to be assigned to this vPar from cell 1 when the vPar is booted. Since counts do not represent specific paths, they are valid for all vPars, whether or in an alternate database. Counts in an alternate database are "requested". Refer to CPUs and Cell Local Processors in the vparresources(5) manpage for more details on the use of counts. An example of the memory resources subfields is: where each subfield is interpreted as follows: (empty): A comma-separated list of user specified memory ranges, both CLM and ILM. This is a legacy subfield; more detailed information is found in ILM and CLM specific subfields later in the display. The total memory (ILM and CLM) assigned to the vPar. This is also a legacy subfield. (empty): A comma-separated list of user assigned ILM memory ranges. comma-separated list of monitor assigned memory ranges. Total ILM assigned to the vPar. ILM granularity, in megabytes. Total memory must be in multiples of this quantity. The same four subfields for CLM. As with CPUs, the monitor assigns memory ranges only when a vPar is booted. Therefore, the vPar in this example is running. o If floating memory is configured, a separate list of floating memory is added to the display following the CLM granularity subfield. The list will be in the following order: floating user assigned ILM ranges floating monitor assigned ILM ranges floating ILM size floating user assigned CLM ranges floating monitor assigned CLM ranges floating CLM size If there is no floating memory configured in the vPar, this list is empty. o If there is any pending memory migration, the last sub-field in the memory field will have the letter If no memory is migrating, this field will be empty. An example of the OL* resources subfields is: where each subfield is interpreted as follows: The sequence id of the last initiated OL* operation. The type of the last initiated OL* operation. The status of the last initiated OL* operation. Available resources: The list of major fields is: CPU resources, I/O resources, memory resources, reboot for reconfiguration flag. The three subfields within CPU resources are: o A comma-separated list of available CPU paths. o The total number of CPUs available for assignment to a vPar, assuming that all are licensed. Note that this number will be less than the number in the CPU path list if any vPar is This is because the monitor reserves (allocates) CPUs for a vPar, for assignment when the vPar is booted. o A comma-separated list of cells and available CLPs on them. The subfields within memory resources are: available ILM ranges, total available ILM, available CLM ranges, total avail- able CLM. The entire list of available resources is displayed on one line, regardless of length. o CPU configuration: The list of major fields is: CPU information, CPU state, assigned vPar, sibling information. The CPU information field includes the following subfields: hardware path, HPA or LID, cell ID. The CPU state field is one or more of the following: Enabld, Inactv, Failed, MarkDC, Pendng The sibling information field consists of the hardware path and assigned vPar of sibling CPUs on the same core of a mul- ticore socket. Here is an example: Information is shown for all CPUs in the underlying hard partition, one CPU per line, except those deconfigured by the firmware. o Monitor-related information. This consists of five major (colon-separated) fields: o The hardware path of the nPartition console. o The hardware path of the disk from which the monitor (and its database) was booted. o The file path of the monitor on that disk. o The file path of the database loaded into the monitor. o The ILM and CLM memory ranges used by the monitor itself for its operation. The need to reboot the underlying hard partition on a partitionable platform is indicated by a in the final field of the vPar configuration and available resource displays (for example, Otherwise the field contains The reboot state is not shown in the CPU configuration display. Displays the local virtual partition (the one in which the command is executed) in a full sentence. The option restricts the display to just the name of the virtual partition. The mon- itor must be running. Displays the monitor event log. The monitor event log is a buffer in the monitor memory. The command displays roughly 4K bytes of the latest data. In the monitor memory buffer, new entries overlay old ones to the nearest character. As a result, the first entry displayed may be missing some leading characters. The monitor must be running. Displays Processor Information Module (PIM) data from the most recent reset of the specified virtual partition. If a virtual partition is not specified, PIM data from the local virtual partition (the virtual partition that issued the command) is displayed. If the virtual partition has not been reset, or if PIM data has been cleared since then, no PIM data is available so a message about the lack of data is displayed. The monitor must be running. Displays the version number of the output format. If no other option is specified, only the version number is displayed. If this option is combined with other options, the version number is displayed first, followed by the data specified by the other option(s). Displays the current virtual partition and vPar monitor release versions along with the OS version and State of all the virtual partitions. The version information displayed depends on the state of the vPar. If the vPar is o - the exact OS version will be displayed. o Not but the vPar has been booted earlier - the OS version last booted on the vPar would be displayed. o Not and if that vpar has never been booted - the OS version would be displayed as Unknown. SECURITY RESTRICTIONS
This command is restricted to processes owned by superuser. RETURN VALUE
The command exits with one of the following values: Successful completion. Syntax error or invalid option. EXAMPLES
Display a summary format of all attributes and resources in all virtual partitions: # vparstatus [Virtual Partition] Boot Virtual Partition Name State Attributes Kernel Path Opts ============================ ===== ============ ===================== ===== vparsd1 Up Dyn,Auto,Nsr /stand/vmunix vparsd2 Down Dyn,Auto,Nsr /stand/vmunix [Virtual Partition Resource Summary] CPU Num Num Memory Granularity Virtual Partition Name Min/Max CPUs IO ILM CLM ============================ ======= ==== ==== ========== ========== vparsd1 1/ 16 7 5 128 128 vparsd2 1/ 16 5 6 128 128 Memory (MB) ILM CLM # User # User Virtual Partition Name Ranges/MB Total MB Ranges/MB Total MB ============================ ====================== ==================== vparsd1 0/ 0 2048 0/ 0 0 vparsd2 0/ 0 2048 0/ 0 0 Display the detailed attributes and resources of # vparstatus -p vparsd2 -v [Virtual Partition Details] Name: vparsd2 State: Down Attributes: Dynamic,Autoboot,Nosearch Kernel Path: /stand/vmunix Boot Opts: [CPU Details] Min/Max: 1/16 User assigned [Path]: 7.12 7.13 Boot processor [Path]: Monitor assigned [Path]: <no path> <no path> <no path> Non-cell-specific: User assigned [Count]: 2 Monitor assigned [Count]: 3 Cell-specific [Count]: Cell ID/Count <none> [IO Details] 0.0.8 8.0.4 0.0.11 8.0.6 8.0.8 0.0.11.0.0.8.0.0.0.0.0 BOOT [Memory Details] ILM, user-assigned [Base /Range]: (bytes) (MB) ILM, monitor-assigned [Base /Range]: (bytes) (MB) ILM Total (MB): 2048 ILM Granularity (MB): 128 CLM, user-assigned [CellID Base /Range]: (bytes) (MB) CLM, monitor-assigned [CellID Base /Range]: (bytes) (MB) CLM (CellID MB): CLM Granularity (MB): 128 [OL* Details] Sequence ID: Operation Type: Status: The same display in machine-readable format (line breaks are artificial): # vparstatus -p vparsd2 -M vparsd2:Down:Dynamic,Autoboot,Nosearch:/stand/vmunix: :1/16;7.12,7.13;;<>,<>,<>;;2;3;:0.0.8,8.0.4,0.0.11,8.0.6,8.0.8, 0.0.11.0.0.8.0.0.0.0.0 BOOT:;2048;;;2048;128;;;;128;;;;;;;:;;:N Display Available resources in the monitor: # vparstatus -A [CPUs (path)]: 8.10 8.13 11.13 [CLP (cellID Count)]: 0 0 3 0 5 0 6 0 7 0 8 2 11 1 13 0 [Available CPUs]: 3 [Available I/O devices (path)]: 0.0.2 0.0.6 8.0.3 8.0.12 [Available ILM (Base /Range)]: 0x0/128 (bytes) (MB) 0x58000000/640 0x2b0000000/54528 [Available ILM (MB)]: 55296 [Available CLM (CellID Base /Range)]: (bytes) (MB) [Available CLM (CellID MB)]: 0 0 3 0 5 0 6 0 7 0 8 0 11 0 13 0 Display the local virtual partition: # vparstatus -w The current virtual partition is vparsd1. Display CPU configuration information for a particular CPU: # vparstatus -d 0.13 CPU Cell Config Sibling Information path CPU HPA ID Status Assigned to Path /vPar name ===== ================== ==== ====== ================== ==================== 0.13 0xfffffffffc07e000 0 E vparsd1 - - Display monitor related information: # vparstatus -m Console path: console(0/0/0/0/0.0.0.0.0.0.0) Monitor boot disk path: disk(0/0/3/0/0.8.0.0.0.0.0) Monitor boot filename: /stand/vpmon Database filename: /stand/vpdb Memory ranges used by monitor: 0x0/58 Display version related information: # vparstatus -P Current Virtual Partition Version: A.04.03 Monitor Version: A.05.01 [Virtual Partition OS Version] Virtual Partition Name OS Version State ============================== ========== ===== vparsd1 B.11.31 Up vparsd2 B.11.23 Down vparsd3 Unknown Down AUTHOR
was developed by the Hewlett-Packard Company. SEE ALSO
vparadmin(1M), vparboot(1M), vparconfig(1M), vparcreate(1M), vpardump(1M), vparefiutil(1M), vparenv(1M), vparextract(1M), vparmodify(1M), vparreloc(1M), vparremove(1M), vparreset(1M), vparutil(1M), vparresources(5), vpartition(5), vpmon(5). vparstatus(1M)