Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Universal CMDB

Discovery > Discovery Modules > Cloud and Virtualization > Virtualization > HP Partitioning Solution Discovery > Discovery Mechanism

Discovery Mechanism

This section includes the following commands:

Verify Discovery on the vPartition
Verify Discovery on the nPartition
Get Information about Complex
List General Information About All Cells
List Detailed Information About Each Cell
Get Information About I/O Chassis
Get the List of Names of the nPartitions on the System
Get Detailed Information About nPartition
Get the Name of the Current vPartition
Get Detailed Information About vPartition
Get Fibre Channel Adapters
Get Disk Devices
Get Network Interfaces
Get File Systems
Get Logical Volumes, Volume Groups, and Physical Volumes
Get Network Interfaces
Get Information About Link Aggregation Interfaces
Get MAC Addresses of the Aggregated Interfaces
Get Hardware Paths of the Aggregated Interfaces
Get IP Addresses of the Aggregated Interfaces

Verify Discovery on the vPartition

Goal	To verify if discovery has connected to the vPartition. To verify that further commands produce supported output.
Command	vparstatus -V
Output	Version 2.0
Values taken	2.0. The version of the vparstatus executable Return code
Comment	Supported versions of output are 2.0 and 1.3

Verify Discovery on the nPartition

Goal	To understand if discovery has connected to the partitionable server.
Command	parstatus -s
Output	None
Values taken	Return code
Comment	If return code is 0, discovery has connected to the partitionable system

Get Information about Complex

Goal	To retrieve properties of the HP Complex CIT.
Command	parstatus -X
Output rp8420	`[Complex]` `Complex Name : Complex 01` `Complex Capacity` `Compute Cabinet (4 cell capable) : 1` `Active GSP Location : cabinet 0` `Model : 9000/800/rp8420` `Serial Number : DEH45419K0` `Current Product Number : A6912A` `Original Product Number : A6912A` `Complex Profile Revision : 1.0` `The total number of Partitions Present : 2`
Output rx8640	`[Complex]` `Complex Name : Complex 01` `Complex Capacity` `Compute Cabinet (4 cell capable) : 1` `Active MP Location : cabinet 0` `Original Product Name : server rx8640` `Original Serial Number : DEH4831H1Y` `Current Product Order Number : AB297A` `OEM Manufacturer :` `Complex Profile Revision : 1.0` `The total number of partitions present : 1`
Output sx3000	`[Complex]` `Complex Name: Complex 1` `Complex UUID: ab111111-2222-3333-4444-555555555555` `Complex Capacity Compute Enclosure: 1 IO Enclosure: 8` `Monarch OA Location: 1` `Model: N/A` `Original Serial Number: AB11111111` `Current Product Order Number: CD2222` `OEM Manufacturer: N/A` `Total number of partitions present: 2`
Values taken	Complex Name > name Serial number/Original Serial Number > serialnumber, hostkey
Comment	HP Complex CIT derives from the Host CIT

List General Information About All Cells

Goal	To retrieve the list of names of all Cells of all Cabinets in the Complex.
Command	parstatus -C -M
Output rp8420	`cell:cab0,cell0:active core :8/0/8 :48.0/ 0.0:cab0,bay0,chassis0 :yes :yes :0` `cell:cab0,cell1:active core :4/0/8 :32.0/ 0.0:cab0,bay0,chassis1 :yes :yes :1` `cell:cab0,cell2:active base :8/0/8 :40.0/ 0.0:- :no :yes :0` `cell:cab0,cell3:active base :4/0/8 :32.0/ 0.0:- :no :yes :1`
Output rx8640	`cell:cab0,cell0:Active Core :8/0/8 :80.0/0.0 :cab0,bay0,chassis0 :yes :yes :0` `cell:cab0,cell1:Active Base :8/0/8 :80.0/0.0 :cab0,bay0,chassis1 :yes :yes :0` `cell:cab0,cell2:Active Base :4/0/8 :64.0/0.0 :- :no :yes :0` `cell:cab0,cell3:Absent :- :- :- :- :-`
Values taken	The names of the cells
Comment	The cell names are then used to retrieve detailed information about each cell.

List Detailed Information About Each Cell

Goal	To retrieve the properties of the Cell CIs and corresponding CPU and Memory CIs.
Command	parstatus -v -c <cell_number>
Output rp8420	`[Cell]` `Hardware Location : cab0,cell0` `Global Cell Number : 0` `Actual Usage : active core` `Normal Usage : base` `Connected To : cab0,bay0,chassis0` `Core Cell Capable : yes` `Firmware Revision : 24.1` `Failure Usage : activate` `Use On Next Boot : yes` `Partition Number : 0` `Partition Name : db01_ap02_db03_db04` `[CPU Details]` `Type : 88E0` `Speed : 1100 MHz` `CPU Status` `=== ======` `0 ok` `1 ok` `2 ok` `3 ok` `4 ok` `5 ok` `6 ok` `7 ok` `CPUs` `===========` `OK : 8` `Deconf : 0` `Max : 8` [Memory Details] DIMM Size (MB) Status ==== ========= ========= 0A 4096 ok 4A 4096 ok 0B 4096 ok 4B 4096 ok 1A 4096 ok 5A 4096 ok 1B 4096 ok 5B 4096 ok 2A 4096 ok 2B 4096 ok 3A 4096 ok 3B 4096 ok Memory ========================= DIMM OK : 12 DIMM Deconf : 0 Max DIMMs : 16 Memory OK : 48.00 GB Memory Deconf : 0.00 GB
Output rx8640	[Cell] Hardware Location : cab0,cell0 Global Cell Number : 0 Actual Usage : Active Core Normal Usage : Base Connected To : cab0,bay0,chassis0 Core Cell Capable : yes Firmware Revision : 9.48 Failure Usage : Normal Use On Next Boot : yes Partition Number : 0 Partition Name : db10_ap13_ap14_db15_db16_ap17_ap18_ap20 Requested CLM value : 0.0 GB Allocated CLM value : 0.0 GB Cell Architecture Type : Itanium(R)-based CPU Compatibility : CDH-640 Hyperthreading Capable : yes [CPU Details] Type : FFFF Speed : 1598 MHz CPU Status === ====== 0 OK 1 OK 2 OK 3 OK 4 OK 5 OK 6 OK 7 OK CPUs =========== OK : 8 Deconf : 0 Max : 8 [Memory Details] DIMM Size (MB) Status ==== ========= ========= 3A 8192 OK 3B 8192 OK 1A 8192 OK 1B 8192 OK 4A 8192 OK 4B 8192 OK 0A 8192 OK 0B 8192 OK 2A 8192 OK 2B 8192 OK Memory ========================= DIMM OK : 10 DIMM Deconf : 0 Max DIMMs : 16 Memory OK : 80.00 GB Memory Deconf : 0.00 GB

Values taken	Global Cell Number > name
	Hardware Location > hardware_path
	Actual Usage > is_core	If value of Actual Usage contains the word Core
	Core Cell Capable > core_capable	Convert yes/no to Boolean
	Requested CLM value > requested_clm_value	This parameter does not exist for rp8420 servers Need to convert GB to MB
	Allocated CLM value > allocated_clm_memory	This parameter does not exist for rp8420 servers Need to convert GB to MB
	Use On Next Boot > use_on_next_boot	Convert yes/no to Boolean
	Failure Usage > failure_usage
	Firmware Revision > firmware_revision
	Cell Architecture Type > architecture_type	This value does not exist for rp8420 servers
	CPU Compatibility > cpu_compatibility	This value does not exist for rp8420 servers
	Hyperthreading Capable > is_hyperthreading_capable	Convert yes/no to Boolean

Values taken (cont'd)

CPUs

===========

OK : 8

Deconf : 0

Max : 8

deconf_cpu_number: 0

max_cpu_number: 8

Memory

=============

DIMM OK : 10

DIMM Deconf : 0

Max DIMMs : 16

Memory OK : 80.00 GB

Memory Deconf : 0.00 GB

memory_amount: 80.00 GB

deconf_memory: 0.00 GB

max_dimms:16

deconfigured_dimms: 0

Need to convert GB to MB

Comment

The Memory CI is not created for UCMDB 9.x since there is no such CIT. The partition number is used to connect the cell to the nPartition (represented as a host).

Get Information About I/O Chassis

Goal	To retrieve the data of all I/O chassis in the Complex (including I/O extension cabinets).
Command	parstatus -I -M
Output rp8420	`chassis:cab0,bay0,chassis0 :active :yes :cab0,cell0:0` `chassis:cab0,bay0,chassis1 :active :yes :cab0,cell1:1`
Output rx8640	`chassis:cab0,bay0,chassis0 :Active :yes :cab0,cell0:0` `chassis:cab0,bay0,chassis1 :Active :yes :cab0,cell1:0`
Values taken	name: cab0,bay0,chassis0
	usage: Active
	is_core: yes	To convert to Boolean values.
Comment	The Cell hardware path is used to connect the chassis to the Cell.

Get the List of Names of the nPartitions on the System

Goal	To retrieve the list of the nPartition numbers configured on the system.
Command	parstatus -P -M
Output rp8420	`partition: 0 :active : 2 : 1 :cab0,cell0:db01_ap02_db03_db04` `partition: 1 :active : 2 : 1 :cab0,cell1:wdb1_wdb4`
Output rx8640	`partition:0 :Active :3 :2 :cab0,cell0:db10_ap13_ap14_db15_db16_ap17_`
Values taken	The list of nPartition numbers
Comment	These numbers are used to retrieve detailed information about each nPartition.

Get Detailed Information About nPartition

Goal	To retrieve detailed information for each nPartition and create a Host, connected to the Cells and to the HP nPar Config CI.
Command	parstatus -v -p <npartition_number>
Output rp8420	`[Partition]` `Partition Number : 0` `Partition Name : db01_ap02_db03_db04` `Status : active` `IP address : 0.0.0.0` `Primary Boot Path : 0/0/0/2/0.6.0` `Alternate Boot Path : 0/0/0/2/1.2.0` `HA Alternate Boot Path : 0/0/0/3/0.6.0` `PDC Revision : 24.1` `IODCH Version : 88E0` `CPU Speed : 1100 MHz` `Core Cell : cab0,cell0` `[Cell]` `CPU Memory Use` `OK/ (GB) Core On` `Hardware Actual Deconf/ OK/ Cell Next Par` `Location Usage Max Deconf Connected To Capable Boot Num` `========== ============ ======= ===` `cab0,cell0 active core 8/0/8 48.0/ 0.0 cab0,bay0,chassis0 yes yes 0` `cab0,cell2 active base 8/0/8 40.0/ 0.0 - no yes 0` `[Chassis]` `Core Connected Par` `Hardware Location Usage IO To Num` `=================== ============ == ===` `cab0,bay0,chassis0 active yes cab0,cell0 0`
Output rx8640	`[Partition]` `Partition Number : 0` `Partition Name : db10_ap13_ap14_db15_db16_ap17_ap18_ap20` `Status : Active` `IP Address :` `Primary Boot Path : 0/0/8/1/0/4/0.8.0.255.0.12.0` `Alternate Boot Path : 0/0/8/1/0/4/1.8.0.255.0.13.0` `HA Alternate Boot Path :` `PDC Revision : 9.48` `IODCH Version : ffff` `Cell Architecture : Itanium(R)-based` `CPU Compatibility : CDH-640` `CPU Speed : 1598 MHz` `Core Cell : cab0,cell0` `Core Cell Choice [0] : cab0,cell0` `Total Good Memory Size : 224.0 GB` `Total Interleave Memory: 224.0 GB` `Total Requested CLM : 0.0 GB` `Total Allocated CLM : 0.0 GB` `Hyperthreading Enabled : no` `[Cell]` `CPU Memory Use` `OK/ (GB) Core On` `Hardware Actual Deconf/ OK/ Cell Next Par` `Location Usage Max Deconf Connected To Capable Boot Num` `========== ============ ======= ========` `cab0,cell0 Active Core 8/0/8 80.0/0.0 cab0,bay0,chassis0 yes yes 0` `cab0,cell1 Active Base 8/0/8 80.0/0.0 cab0,bay0,chassis1 yes yes 0` `cab0,cell2 Active Base 4/0/8 64.0/0.0 - no yes 0` `Notes: * = Cell has no interleaved memory.` `[Chassis]` `Core Connected Par` `Hardware Location Usage IO To Num` `=================== ============ ====` `cab0,bay0,chassis0 Active yes cab0,cell0 0` `[Chassis]` `Core Connected Par` `Hardware Location Usage IO To Num` `=================== ============ ==== ========== ===` `cab0,bay0,chassis1 Active yes cab0,cell1 0`

Values taken	Host (nPartition)
	hostkey	Host key is composed of nPartition name and Complex Serial number
	Partition Name > tname
	HP nPar Config
	Constant "nPar Config" > name
	Partition Name > npar_name
	Status > npar_status
	PDC Revision > pdc_revision
	Hyperthreading Enabled > hyperthreading_mode	This value does not exist on the rp8420 servers
	Partition Number > partition_number
	Primary Boot Path > primary_boot_path
	Alternate Boot Path > alternate_boot_path

Get the Name of the Current vPartition

Goal	To retrieve the name of the current vPartition.
Command	vparstatus -w -M
Output	`doidb01`
Values taken	The name of the vPartition that discovery has connected to.
Comment	The list includes detailed information for the current vPartition only. It is possible to retrieve detailed information about all vPartitions on the nPartition, but it is not possible to retrieve their IP addresses and/or lower MAC address to create a host in UCMDB.

Get Detailed Information About vPartition

Goal	To retrieve detailed information about vPartition and create Host and HP vPar Config CIs.
Command	vparstatus -v -p <vpartition_name>
Output rp8420	`[Virtual Partition Details]` `Name: doidb01` `State: Up` `Attributes: Dynamic,Autoboot,Nosearch` `Kernel Path: /stand/vmunix` `Boot Opts: -lq` `[CPU Details]` `Min/Max: 3/16` `Bound by User [Path]: 0.15` `0.16` `0.17` `Bound by Monitor [Path]:` `Unbound [Path]: 2.14` `2.15` `[IO Details]` `0.0.12` `0.0.14` `0.0.12.1.0.4.0.8.0.255.0.0.0` `0.0.14.1.0.4.0.8.0.255.0.1.0` `0.0.12.1.0.4.0.111.128.19.4.0.0` `0.0.12.1.0.4.0.111.88.19.5.0.0 BOOT` `0.0.14.1.0.4.0.112.88.19.5.0.0, ALTBOOT` `[Memory Details]` `Specified [Base /Range]:` `(bytes) (MB)` `Total Memory (MB): 24448`
Output rx8640	`[Virtual Partition Details]` `Name: doiap17` `State: Up` `Attributes: Dynamic,Autoboot,Nosearch` `Kernel Path: /stand/vmunix` `Boot Opts: -lq` `[CPU Details]` `Min/Max: 1/12` `User assigned [Path]:` `Boot processor [Path]: 1.122` `Monitor assigned [Path]:` `Non-cell-specific:` `User assigned [Count]: 1` `Monitor assigned [Count]: 0` `Cell-specific [Count]: Cell ID/Count` `<none>` `[IO Details]` `0.0.8` `0.0.8.1.0.4.0.8.0.255.0.13.0` `0.0.8.1.0.4.0.8.0.255.0.12.0 BOOT` `0.0.8.1.0.4.1.8.0.255.0.13.0,ALTBOOT` `[Memory Details]` `ILM, user-assigned [Base /Range]:` `(bytes) (MB)` `ILM, monitor-assigned [Base /Range]: 0x11c0000000/8192` `(bytes) (MB)` `ILM Total (MB): 8192` `ILM Granularity (MB): 512` `CLM, user-assigned [CellID Base /Range]:` `(bytes) (MB)` `CLM, monitor-assigned [CellID Base /Range]:` `(bytes) (MB)` `CLM (CellID MB):` `CLM Granularity (MB): 128`
Values taken	Const "HP vPar Config" > name
	Name > vpar_name
	Boot Opts > boot_options
	Boot processor [Path] > boot_processor_path	This value does not exist for rp8420 servers
	State > vpar_status
	Attributes: Dynamic, Autoboot, Nosearch	autoboot_mode: Autoboot autosearch_mode: Nosearch modification_mode: Dynamic
	Bound by User [Path]/User assigned [Path] > cpus_bound_by_user	Actual parameter is different between server versions
	Unbound [Path] > unbound_cpus
Comment	For the attribute format of attributes such as cpus_bound_by_user, refer to the Data Model specification.

Get Fibre Channel Adapters

Goal	To model Fibre Channel adapters
Command	ioscan -FnkCfc
Output	`pci:wsio:F:T:F:-1:50:4294967295:fc:fcd: 0/0/12/1/0/4/0:16 119 35 18 0 0 0 0 :0: root.cell.sba.lba.PCItoPCI.fcd:fcd: CLAIMED:INTERFACE:HP AB465-60001 PCI/PCI-X Fibre Channel 2-port 2Gb FC /2-port 1000B-T Combo Adapter (FC Port 1):0` `/dev/fcd0` `pci:wsio:F:T:F:-1:50:4294967295:fc:fcd: 0/0/12/1/0/4/1:16 119 35 18 0 0 0 0 :1: root.cell.sba.lba.PCItoPCI.fcd:fcd: CLAIMED:INTERFACE:HP AB465-60001 PCI/PCI-X Fibre Channel 2-port 2Gb FC/2-port 1000B-T Combo Adapter (FC Port 2):1` `/dev/fcd1` `pci:wsio:F:T:F:-1:50:4294967295:fc:fcd: 0/0/14/1/0/4/0:16 119 35 18 0 0 0 0 : 2:root.cell.sba.lba.PCItoPCI.fcd:fcd: CLAIMED:INTERFACE:HP AB465-60001 PCI/PCI-X Fibre Channel 2-port 2Gb FC/2-port 1000B-T Combo Adapter (FC Port 1):2` `/dev/fcd2` `pci:wsio:F:T:F:-1:50:4294967295:fc:fcd: 0/0/14/1/0/4/1:16 119 35 18 0 0 0 0 :3: root.cell.sba.lba.PCItoPCI.fcd:fcd: CLAIMED:INTERFACE:HP AB465-60001 PCI/PCI-X Fibre Channel 2-port 2Gb FC/2-port 1000B-T Combo Adapter (FC Port 2):3` `/dev/fcd3`
Values taken	name	/dev/fcd0
	data_description	HP AB465-60001 PCI/PCI-X Fibre Channel 2-port 2Gb FC/2-port 1000B-T Combo Adapter (FC Port 2)
Comment	The hardware path serves to locate the Cell and use it as a container for FC HBA. Example value: `0/0/14/1/0/4/0`. The first integer value is the Global ID of the Cell; the second value is the ID of the I/O chassis.

Get Disk Devices

Goal	To retrieve information about the dependency between I/O chassis, physical disk, and SCSI adapter.
Command	ioscan -FnkCdisk
Output	`scsi:wsio:T:T:F:31:188:2031616: disk:sdisk:0/0/12/1/0/4/0. 111.88.19.5.0.0:0 0 4 50 0 0 0 0 51 248 164 14 99 72 178 210 :3:root.cell.sba.lba.PCItoPCI.fcd.fcd_fcp.fcd_vbus.tgt.sdisk: sdisk:CLAIMED:DEVICE:EMC SYMMETRIX:31` `/dev/dsk/c31t0d0 /dev/rdsk/c31t0d0` `scsi:wsio:T:T:F:31:188:2031872: disk:sdisk:0/0/12/1/0/4/0. 111.88.19.5.0.1:0 0 4 50 0 0 0 0 51 248 164 14 76 238 217 30 :59:root.cell.sba.lba. PCItoPCI.fcd.fcd_fcp.fcd_vbus.tgt. sdisk:sdisk:CLAIMED:DEVICE:EMC SYMMETRIX:31` `/dev/dsk/c31t0d1 /dev/rdsk/c31t0d1` `scsi:wsio:T:T:F:31:188:2032128: disk:sdisk:0/0/12/1/0/4/0. 111.88.19.5.0.2:0 0 4 50 0 0 0 0 51 248 164 14 101 17 172 238 :61:root.cell.sba.lba. PCItoPCI.fcd.fcd_fcp.fcd_vbus.tgt.sdisk:sdisk: CLAIMED:DEVICE:EMC SYMMETRIX:31` `/dev/dsk/c31t0d2 /dev/rdsk/c31t0d2`
Values taken	slot_number	0/0/12/1/0/4/0.111.88.19.5.0.0
	name	/dev/dsk/c31t0d2
	Cell ID	0/0/12/1/0/4/0.111.88.19.5.0.0
	IO chassis ID	0/0/12/1/0/4/0.111.88.19.5.0.0

Get Network Interfaces

Goal	To retrieve information about the dependency between network interfaces and the I/O chassis.
Command	ioscan -FnkClan
Output	`pci:wsio:F:F:F:-1:-1:4294967295:lan: igelan:0/0/12/1/0/6/0:20 228 22 72 0 0 0 0 :0: root.cell.sba.lba.PCItoPCI.igelan:igelan: CLAIMED:INTERFACE:HP AB465-60001 PCI/PCI-X 1000Base-T 2-port 2Gb FC/2-port 1000B-T Combo Adapter:0` `pci:wsio:F:F:F:-1:-1:4294967295:lan: igelan:0/0/12/1/0/6/1:20 228 22 72 0 0 0 0 :1: root.cell.sba.lba.PCItoPCI.igelan:igelan: CLAIMED:INTERFACE:HP AB465-60001 PCI/PCI-X 1000Base-T 2-port 2Gb FC/2-port 1000B-T Combo Adapter:1` `pci:wsio:F:F:F:-1:-1:4294967295:lan: igelan:0/0/14/1/0/6/0:20 228 22 72 0 0 0 0 :2: root.cell.sba.lba.PCItoPCI.igelan:igelan: CLAIMED:INTERFACE:HP AB465-60001 PCI/PCI-X 1000Base-T 2-port 2Gb FC/2-port 1000B-T Combo Adapter:2` `pci:wsio:F:F:F:-1:-1:4294967295:lan: igelan:0/0/14/1/0/6/1:20 228 22 72 0 0 0 0 :3: root.cell.sba.lba.PCItoPCI.igelan:igelan: CLAIMED:INTERFACE:HP AB465-60001 PCI/PCI-X 1000Base-T 2-port 2Gb FC/2-port 1000B-T Combo Adapter:3`
Values taken	The hardware path which reflects the Cell and I/O chassis that this interface belongs to.

Get File Systems

Goal	To retrieve information about the file systems and corresponding logical volumes.
Command	df -P
Output	`Filesystem 512-blocks Used Available Capacity Mounted on` `/dev/vg01/lv106 9837710 115094 9722616 2% /usr/vw/rvs` `/dev/vg01/lv124 7915344 814616 7100728 11% /home/kdov12` `/dev/vg01/lv125 10222640 6275190 3947450 62% /home/ebrev` `/dev/vg01/lv123 20829536 2796208 18033328 14% /home/temp` `/dev/vg01/lv110 2080832 4608 2076224 1% /oracle2/arch/inst_aebp`
Values taken	name for FileSystem CIT: /usr/vw/rvs Name of the logical volume: /dev/vg01/lv106

Get Logical Volumes, Volume Groups, and Physical Volumes

Goal	To retrieve data for modeling Logical volumes, Volume groups, and Physical volumes.
Command	vgdisplay -v
Output	`--- Volume groups ---` `VG Name /dev/vg00` `VG Write Access read/write` `VG Status available` `Max LV 255` `Cur LV 10` `Open LV 10` `Max PV 16` `Cur PV 1` `Act PV 1` `Max PE per PV 4384` `VGDA 2` `PE Size (Mbytes) 16` `Total PE 4315` `Alloc PE 4156` `Free PE 159` `Total PVG 0` `Total Spare PVs 0` `Total Spare PVs in use 0` `--- Logical volumes ---` `LV Name /dev/vg00/lvol1` `LV Status available/syncd` `LV Size (Mbytes) 256` `Current LE 16` `Allocated PE 16` `Used PV 1` `--- Physical volumes ---` `PV Name /dev/dsk/c31t0d0` `PV Name /dev/dsk/c32t0d0 Alternate Link` `PV Status available` `Total PE 4315` `Free PE 159` `Autoswitch On` `Proactive Polling On`
Values taken	Volume group
	VG Name > name VG Write Access > write_access
	VG Status > vg_status PE Size (Mbytes)	This value is used to calculate the size of the physical volume
	Logical Volume
	LV Name > name LV Status > lv_status
	Physical Volume
	PV Name > name	Alternate link may also be used. It depends on the output of the ioscan FnkCdisk command.
	PV Status > pv_status
	Total PE > pv_size	This attribute is calculated on the PE Size (Mbytes) value.

Get Network Interfaces

Goal	To retrieve information about the network interfaces.
Command	lanscan
Output	`Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI` `Path Address In# State NamePPA ID Type Support Mjr#` `0/0/4/1/0/6/1 0x0014C254D9BD 1 UP lan1 snap1 2 ETHER Yes 119` `0/0/6/1/0/6/1 0x0014C254C961 3 UP lan3 snap3 4 ETHER Yes 119` `LinkAgg0 0x0014C254D9BC 900 UP lan900 snap900 6 ETHER Yes 119` `LinkAgg1 0x000000000000 901 DOWN lan901 snap901 7 ETHER Yes 119` `LinkAgg2 0x000000000000 902 DOWN lan902 snap902 8 ETHER Yes 119` `LinkAgg3 0x000000000000 903 DOWN lan903 snap903 9 ETHER Yes 119` `LinkAgg4 0x000000000000 904 DOWN lan904 snap904 10 ETHER Yes 119`
Values taken	The hardware path to create the link between the network interface and I/O chassis. The MAC address to create the network interface. The MAC address of the Link aggregation interface, the indicator that the interface is up, and the device name.

Get Information About Link Aggregation Interfaces

Goal	To model the links between interfaces and link aggregation.
Command	lanscan -q
Output	`1` `3` `900 0 2` `901` `902` `903` `904`
Values taken	The interface number and IDs of the aggregated interfaces.

Get MAC Addresses of the Aggregated Interfaces

Goal	To retrieve the MAC addresses of the aggregated interfaces.
Command	lanadmin -a <interface_id>
Example	lanscan -a 0
Output	`Station Address = 0x0014c254d9bc`
Values taken	The MAC address of the aggregated interface

Get Hardware Paths of the Aggregated Interfaces

Goal	To retrieve the hardware path of the aggregated interfaces
Command	lanscan -v \| grep -E <list_of_aggregated_interfaces>
Example	lanscan -v \| grep -E "lan0\|lan2"
Output	`0/0/4/1/0/6/0 0 UP lan0 snap0 1 ETHER Yes 119 igelan` `0/0/6/1/0/6/0 2 UP lan2 snap2 3 ETHER Yes 119 igelan`
Values taken	The hardware path that allocates the I/O chassis that holds this interface.

Get IP Addresses of the Aggregated Interfaces

Goal	To get IP addresses of the interfaces
Command	netstat -rn
Output	`Routing tables` `Destination Gateway Flags Refs Interface Pmtu` `127.0.0.1 127.0.0.1 UH 0 lo0 4136` `10.186.112.115 10.186.112.115 UH 0 lan0 4136` `10.186.116.13 10.186.116.13 UH 0 lan1 4136` `192.168.121.1 192.168.121.1 UH 0 lan2 4136` `10.186.115.18 10.186.115.18 UH 0 lan3 4136` `10.186.116.19 10.186.116.19 UH 0 lan1:1 4136` `10.186.116.0 10.186.116.13 U 3 lan1 1500` `10.186.116.0 10.186.116.19 U 3 lan1:1 1500` `10.186.115.0 10.186.115.18 U 2 lan3 1500` `10.186.112.0 10.186.112.115 U 2 lan0 1500` `192.168.121.0 192.168.121.1 U 2 lan2 1500` `10.186.86.0 10.186.115.1 UG 0 lan3 1500` `127.0.0.0 127.0.0.1 U 0 lo0 4136` `default 10.186.116.1 UG 0 lan1 1500`
Values taken	The IP addresses of the interfaces. The netstat command does not require root privileges, in contrast to ifconfig.