Vous êtes sur la page 1sur 39

HPUXCheatSheet

HPUXCheatSheet

Contents
1 HP UNIX Administration Cheat Sheet...........................................................................................................1/37 1.1 Scope...................................................................................................................................................2/37 1.2 Audience.............................................................................................................................................2/37 1.3 Typographic Convention....................................................................................................................2/37 1.4 Contractual support and contact information ......................................................................................2/37 1.5 Accessing Console..............................................................................................................................2/37 1.5.1 MP on the Integrity Line...........................................................................................................2/37 1.6 Hardware Configuration.....................................................................................................................3/37 1.6.1 Looking at the H/W Configuration (aka prtdiag)......................................................................3/37 1.6.2 Adding a Card on a HPUX system ............................................................................................5/37 1.6.3 Removing a card from a HPUX system....................................................................................5/37 1.6.4 Replacing a card from a HPUX system .....................................................................................5/37 1.6.5 Cell-board based architecture....................................................................................................5/37 1.7 Starting up and shutting down the servers..........................................................................................5/37 1.7.1 Booting Integrity servers...........................................................................................................5/37 1.7.1.1 {{{shutdown}}}..............................................................................................................5/37 1.7.1.2 Breaking a hung system...................................................................................................5/37 1.7.2 shutdown or reboot on node and vPARs...................................................................................5/37 1.7.3 EFI Shell....................................................................................................................................5/37 1.8 Installing the OS...............................................................................................................................13/37 1.8.1 Recommended Filesystem Layout in the SAP landscape.......................................................13/37 1.8.2 Installing from DVD/CDROM ................................................................................................13/37 1.8.3 Setting up the Golden Image and Ignite server.......................................................................14/37 1.8.4 Installing via network using an Ignite Image..........................................................................16/37 1.8.4.1 Initiate ignite installation from the client.......................................................................18/37 1.8.5 Removing old LVM (factory-set) boot disk and mirroring rootdisk .......................................19/37 1.8.6 Verifying encapsulated Rootdisk............................................................................................20/37 1.8.7 Mirroring the rootdisk.............................................................................................................21/37 1.9 Configuring Network interfaces and other network-related information.........................................22/37 1.9.1 Configuring Ethernet Adapters...............................................................................................22/37 1.9.2 Configuring Default routes ......................................................................................................23/37 1.9.3 Checking Duplex mode and link-speed on HPUX..................................................................23/37 1.9.3.1 lanscan...........................................................................................................................23/37 1.9.3.2 landiag............................................................................................................................23/37 1.9.4 Setting Duplex mode, link speed .............................................................................................23/37 1.9.4.1 lanadmin .........................................................................................................................23/37 1.9.5 Checking for network health...................................................................................................24/37 1.10 Configuring Storage devices...........................................................................................................24/37 1.10.1 Add a local scsi disk..............................................................................................................24/37 1.10.2 Add a local SCSI Tape device...............................................................................................24/37 1.10.3 Configure FC HBAs..............................................................................................................24/37 1.10.3.1 Add a SAN LUN disk..................................................................................................24/37 1.10.3.2 Before Configuring the LUNs.....................................................................................24/37 1.10.3.3 Create the devlinks for these new LUNs now.............................................................25/37 1.10.3.4 After the device links have been created (ie Device files) ...........................................26/37 1.10.3.5 Verify that the LUNs are usable..................................................................................27/37 1.10.3.6 Add the LUNs to Veritas Volume Manager................................................................27/37 1.10.3.7 Verify the disk information ..........................................................................................27/37 1.10.3.8 Check the disk details using {{{vxdisk list}}} ............................................................28/37 1.10.3.9 Check whether Veritas Dynamic Multipathing has been enabled...............................28/37 1.10.3.10 remove a SAN LUN Disk..........................................................................................30/37 1.10.3.11 Add a SAN Tape device............................................................................................30/37 1.10.3.12 Remove a SAN Tape device......................................................................................34/37 1.11 Install software................................................................................................................................34/37 1.11.1 Set up a depot........................................................................................................................34/37 1.11.2 Register the depot..................................................................................................................34/37 1.12 install patches..................................................................................................................................34/37 1.12.1 Identifying required patches..................................................................................................34/37 1.12.2 set up a patch depot...............................................................................................................35/37 1.12.3 Register the depot..................................................................................................................35/37 1.12.4 Setting system and nodename...............................................................................................35/37 1.12.5 Enabling long hostnames .......................................................................................................35/37 1.12.5.1 Installing the Core enhancements extension................................................................36/37

1 HP UNIX Administration Cheat Sheet


Contents 1. HP UNIX Administration Cheat Sheet 1. Scope 2. Audience 3. Typographic Convention 4. Contractual support and contact information 5. Accessing Console 1. MP on the Integrity Line 6. Hardware Configuration 1. Looking at the H/W Configuration (aka prtdiag) 2. Adding a Card on a HPUX system 3. Removing a card from a HPUX system 4. Replacing a card from a HPUX system 5. Cell-board based architecture 7. Starting up and shutting down the servers 1. Booting Integrity servers 1. Breaking a hung system 2. 2. shutdown or reboot on node and vPARs 3. EFI Shell 8. Installing the OS 1. Recommended Filesystem Layout in the SAP landscape 2. Installing from DVD/CDROM 3. Setting up the Golden Image and Ignite server 4. Installing via network using an Ignite Image 1. Initiate ignite installation from the client 5. Removing old LVM (factory-set) boot disk and mirroring rootdisk 6. Verifying encapsulated Rootdisk 7. Mirroring the rootdisk 9. Configuring Network interfaces and other network-related information 1. Configuring Ethernet Adapters 2. Configuring Default routes 3. Checking Duplex mode and link-speed on HPUX 1. lanscan 2. landiag 4. Setting Duplex mode, link speed 1. lanadmin 5. Checking for network health 10. Configuring Storage devices 1. Add a local scsi disk 2. Add a local SCSI Tape device 3. Configure FC HBAs 1. Add a SAN LUN disk 2. Before Configuring the LUNs 3. Create the devlinks for these new LUNs now 4. After the device links have been created (ie Device files) 5. Verify that the LUNs are usable 6. Add the LUNs to Veritas Volume Manager 7. Verify the disk information 8. Check the disk details using 9. Check whether Veritas Dynamic Multipathing has been enabled 1. List by Controller number 2. Check by Enclosure 3. Check subpaths by Controller number 4. Verifying Lun grouping/paths 5. Check whether DMP is enabled 10. remove a SAN LUN Disk 11. Add a SAN Tape device 12. Remove a SAN Tape device 11. Install software 1. Set up a depot 2. Register the depot 12. install patches 1. Identifying required patches 1/37

HPUXCheatSheet 2. set up a patch depot 3. Register the depot 4. Setting system and nodename 5. Enabling long hostnames 1. Installing the Core enhancements extension

07/17/07 13:40:06

1.1 Scope
Covers some key elements of HPUX System adminstration -- common (and uncommon) SA commands, HOWTOs etc.

1.2 Audience
Any UNIX Admin who is starting out on HPUX (or even seasoned admins with Memory deficiencies)

1.3 Typographic Convention


Normal Text System Cmds and outputs This is normal text This is cmd and output text -- # df -lk

1.4 Contractual support and contact information 1.5 Accessing Console


1.5.1 MP on the Integrity Line
# tty /dev/console # MP MAIN MENU: CO: Console VFP: Virtual Front Panel CM: Command Menu SMCLP: Server Management Command Line Protocol CL: Console Log SL: Show Event Logs HE: Main Help Menu X: Exit Connection [mp0014c29c14b7] MP> vfp [mp0014c29c14b7] MP> vfp Welcome to the Virtual Front Panel (VFP). Use Ctrl-B to exit. System state Activity # of logs since boot ----------------------------------------OS Running OS heartbeat: * 174 E indicates error since last boot LEDs | LOCATOR | SYSTEM | INT. HEALTH | EXT. HEALTH | POWER ----------------------------------------------------------------------------| OFF | ON GREEN | ON GREEN | ON GREEN | ON GREEN ----------------------------------------------------------------------------Status | POW:System Power on | INT:Internal parts, including CPUs and Memory, okay | EXT:Externally accessible fans and power supplies okay | SYS:OS Booting or Running ----------------------------------------------------------------------------[mp0014c29c14b7] MP:VFP(Use '?' to display VFP terminal info or Ctrl-B to Quit)> [mp0014c29c14b7] MP:CM> ls LS Current LAN Configuration: MAC Address : 0x0014c29c14b7 DHCP Status : Enabled IP Address : 0.0.0.0 MP Host Name : mp0014c29c14b7 Subnet Mask : 0.0.0.0 Gateway Address : 0.0.0.0 Link State : Auto Negotiate Remote Serial Console Port : 2023 SSH Access Port : 22 LAN status: UP and RUNNING [mp0014c29c14b7] MP:CM> df DF

2/37

HPUXCheatSheet
To dump all available FRU information without any paging, use the command line interface: DF -ALL -NC Display FRU Information Menu: S - Specific FRU A - All available FRUs V - Display Mode: Text Enter menu item or [Q] to Quit: A A FRU Entry # 0 : FRU NAME: Processor 0 ID:20 PROCESSOR DATA S-spec/QDF: L9PB Sample/Prod: 01 CORE DATA Arch Revision : 00 Core Family : 20 Core Model : 00 Core Stepping : 07 Max Core Frequency : 1420 MHZ Max SysBus Frequency : 267 MHZ Core Voltage : 1100 mV Core Voltage Tolerance,High : 32 mV Core Voltage Tolerance,Low : 96 mV CACHE DATA Cache Size : 12 MB PACKAGE DATA Package Revision : NE Substrate Revision: 01 PROC PART NUMBER DATA Part Number : 80549KE Electronic Signature : 000180E853DCDBCE THERMAL REF DATA Upper Temp Ref : 92 C Calibr Offset : 12 C FEATURES DATA IA-32 Proc Core Feature Flags: FFFB8743 IA-64 Proc Core Feature Flags: 1B81806300000000 Package Feature Flags : 3F000000 Devices on TAP Chain : 2 Type <CR> for next entry, or Q to quit: [mp0014c29c14b7] MP:CM> ^b (Control-B) to exit to main menu MP MAIN MENU: CO: Console VFP: Virtual Front Panel CM: Command Menu SMCLP: Server Management Command Line Protocol CL: Console Log SL: Show Event Logs HE: Main Help Menu X: Exit Connection [mp0014c29c14b7] MP> CO (to access console) [mp0014c29c14b7] MP> co (Use Ctrl-B to return to MP main menu.) - - - - - - - - - - Prior Console Output - - - - - - - - - dr-xr-xr-x 14 bin bin 8192 Feb 5 16:34 dev dr-xr-xr-x 30 bin bin 8192 Feb 5 17:05 etc drwxr-xr-x 15 root root 8192 Mar 2 11:03 .. drwxr-xr-x 15 root root 8192 Mar 2 11:03 . drwxrwxrwt 4 root root 8192 Mar 2 11:19 tmp -rw------1 root sys 300 Mar 2 11:20 .sh_history # clear # tty /dev/console # - - - - - - - - - - - - Live Console - - - - - - - - - - - #

07/17/07 13:40:06

1.6 Hardware Configuration


1.6.1 Looking at the H/W Configuration (aka prtdiag)

3/37

HPUXCheatSheet

07/17/07 13:40:06

# ioscan -f Class I H/W Path Driver S/W State H/W Type Description ==================================================================================== root 0 root CLAIMED BUS_NEXUS ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (4030) ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e tty 0 0/0/1/0 rmp3f01 CLAIMED INTERFACE PCI class(255,0) (103c1303) tty 1 0/0/1/1 rmp3f01 CLAIMED INTERFACE PCI SimpleComm (103c1302) tty 2 0/0/1/2 asio0 CLAIMED INTERFACE PCI Serial (103c1048) OO 0 0/0/2/0 UsbOhci CLAIMED INTERFACE USB OHCI Interface OO 1 0/0/2/1 UsbOhci CLAIMED INTERFACE USB OHCI Interface OO 2 0/0/2/1.0 UsbMiniBus CLAIMED INTERFACE USB Composite Device OO 3 0/0/2/1.0.0 UsbBulkOnlyMS CLAIMED DEVICE USB Bulk Only ext_bus 0 0/0/2/1.0.16 UsbScsiAdaptor CLAIMED INTERFACE USB SCSI Stack Adaptor target 0 0/0/2/1.0.16.0 tgt CLAIMED DEVICE disk 0 0/0/2/1.0.16.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-N target 1 0/0/2/1.0.16.7 tgt CLAIMED DEVICE ctl 0 0/0/2/1.0.16.7.0 sctl CLAIMED DEVICE Initiator OO 4 0/0/2/2 UsbEhci CLAIMED INTERFACE USB EHCI Interface ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e ba 2 0/2 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e ba 3 0/3 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee ba 4 0/4 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e escsi_ctlr 0 0/4/1/0 sasd CLAIMED INTERFACE HP PCI/PCI-X SAS MPT Adapter ext_bus 1 0/4/1/0.0.0 sasd_vbus CLAIMED INTERFACE SAS Device Interface target 2 0/4/1/0.0.0.0 tgt CLAIMED DEVICE disk 1 0/4/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP DG072A9BB7 target 3 0/4/1/0.0.0.1 tgt CLAIMED DEVICE disk 2 0/4/1/0.0.0.1.0 sdisk CLAIMED DEVICE HP DG072A9BB7 lan 0 0/4/2/0 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000 lan 1 0/4/2/1 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000 ba 5 0/5 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e ba 6 0/6 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e ba 7 0/7 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee processor 0 120 processor CLAIMED PROCESSOR Processor processor 1 121 processor CLAIMED PROCESSOR Processor processor 2 122 processor CLAIMED PROCESSOR Processor processor 3 123 processor CLAIMED PROCESSOR Processor ba 8 250 pdh CLAIMED BUS_NEXUS Core I/O Adapter ipmi 0 250/0 ipmi CLAIMED INTERFACE IPMI Controller tty 3 250/1 asio0 CLAIMED INTERFACE Built-in RS232C acpi_node 0 250/2 acpi_node CLAIMED INTERFACE Acpi Hardware #

4/37

HPUXCheatSheet

07/17/07 13:40:06

ioscan scans the system (see diagram above) -- and the device h/w path (eg: 0/4/2/1) represents the following: The SBA/The LBA/PCI Bus/PCI Slot. That is, if the device path is 0/4/2/1 -- that represents PCI slot 1 on PCI Bus 2 connected to the LBA 4 which in turn is connected to System Bus 0. For more descriptive/detailed information, look for docs in http://docs.hp.com.

1.6.2 Adding a Card on a HPUX system


The reference system used here was an rx3600. Similar rules should apply for all the Non-Cellboard based systems (rx3600,2620,4640,6600). Shut the system down completely and remove the power cords in the back. Remove the top cover of the system. Insert the PCI card in an appropriate slot (eg: If card is 66MHz, don't insert it into a 133 MHz slot). See the H/W reference manual for the server in http://docs.hp.com or http://itrc.hp.com for more details. After installing the cards, ensure that the MRL (Manual Retention Latch) is securely locked (you should here a distinct "click" when you press down on the tab). If the MRL isn't secure, system will on enable power to these PCI slots and you might observe the Internal Health LED (server front panel) glowing amber and blinking at about 2Hz frequency. Verify that cards are installed using ioscan and where applicable olrad -q

1.6.3 Removing a card from a HPUX system 1.6.4 Replacing a card from a HPUX system 1.6.5 Cell-board based architecture

1.7 Starting up and shutting down the servers


1.7.1 Booting Integrity servers
1.7.1.1 {{{shutdown}}}
# shutdown -y 60 # Shutdown # shutdown -hy 60 # shutdown # shutdown -ry 60 # shutdown # shutdown -ry 0 # shutdown ==== Shutting down from the MP ==== {{{ MP>cm MP:CM>rs in 60 seconds to single user mode and halt in 60s and reboot in 60s and reboot immediately

In case of larger frames (cell-based boxes) such as the 7640 or superdome, use the (((pe}}} command (power entity) instead of the pc command (for smaller boxes). Can be used to power on and power off a server from the MP.
MP>cm MP:CM> pc

1.7.1.2 Breaking a hung system tc or rs to reboot the hung system.

1.7.2 shutdown or reboot on node and vPARs


???

1.7.3 EFI Shell


In the Integrity line of servers, the EFI shell lets you choose which disk to boot from, or can go into an interactive mode (by selecting the "EFI Shell [Built-in]). To access the EFI shell, interrupt the EFI Autoboot process and select the EFI shell option (from boot manager menu). The startup.nsh script is run to give the "shell" prompt.
Shell> info sys SYSTEM INFORMATION Date/Time: Mar 7, 2007

18:08:43

(20:07:03:07:18:08:43)

5/37

HPUXCheatSheet

07/17/07 13:40:06

Manufacturer: hp Product Name: server rx3600 Product Number: AB596A Serial Number: USE4651794 UUID: 6ADC0BAF-A937-11DB-BA3D-78D3C986778F System Bus Frequency: 266 MHz Shell> info boot BOOT INFORMATION Monarch CPU: Current Preferred Monarch Monarch CPU CPU Module/ Module/ Logical Logical Warnings ------- --------- -------0/0 0/0 AutoBoot: ON - Timeout is : 7 sec Boottest: BOOTTEST Settings Default Variable OS is not speedy boot aware. Selftest Setting ---------------------early_cpu Run this test late_cpu Run this test platform Run this test chipset Run this test io_hw Run this test mem_init Run this test mem_test Run this test LAN Address Information: LAN Address Path ----------------- ---------------------------------------*Mac(0017A451CECC) Acpi(HWP0002,PNP0A03,400)/Pci(2|0)/Mac(0017A451CECC) Mac(0017A451CECD) Acpi(HWP0002,PNP0A03,400)/Pci(2|1)/Mac(0017A451CECD) Shell> info fw FIRMWARE INFORMATION *System Firmware A Revision: 1.32 [4642] System Firmware B Revision: 1.32 [4642] BMC Revision: 5.07 Management Processor Revision: F.01.41 Updatable EFI Drivers: Floating-Point Software Assistance Handler: 00000118 Broadcom Gigabit Ethernet Driver: 0007000A SCSI Bus Driver: 00000021 SCSI Tape Driver: 00000020 Usb Ohci Driver: 00000033 USB Bus Driver: 00000014 USB Bot Mass Storage Driver: 00000014 Generic USB Mass Storage Driver: 00000015 * Indicates active system firmware image Shell> info spu Usage: INFO [-b] [target] target : all, boot, chiprev, cpu, fw, io, mem, sec, sys, warning -b : Break after full page of info -a : Include extended information Exit status code: Invalid Parameter Shell> info mem MEMORY INFORMATION Extender 0: ---- DIMM A ----- ---- DIMM B ----- ---- DIMM C ----- ---- DIMM D ----DIMM Current DIMM Current DIMM Current DIMM Current --- ------ ---------- ------ ---------- ------ ---------- ------ ---------0 1024MB Active 1024MB Active 1024MB Active 1024MB Active 1 1024MB Active 1024MB Active 1024MB Active 1024MB Active 2 ------------Extender 1: ---- DIMM A ----- ---- DIMM B ----- ---- DIMM C ----- ---- DIMM D ----DIMM Current DIMM Current DIMM Current DIMM Current --- ------ ---------- ------ ---------- ------ ---------- ------ ---------0 1024MB Active 1024MB Active 1024MB Active 1024MB Active 1 1024MB Active 1024MB Active 1024MB Active 1024MB Active 2 ------------Active Memory : 16384 MB Installed Memory : 16384 MB Shell> info -b all SYSTEM INFORMATION Date/Time: Mar 7, 2007 18:10:50 (20:07:03:07:18:10:50) Manufacturer: hp Product Name: server rx3600 Product Number: AB596A Serial Number: USE4651794

6/37

HPUXCheatSheet

07/17/07 13:40:06

UUID: 6ADC0BAF-A937-11DB-BA3D-78D3C986778F System Bus Frequency: 266 MHz PROCESSOR MODULE INFORMATION # of L3 L4 Family/ CPU Logical Cache Cache Model Processor Module CPUs Speed Size Size (hex.) Rev State ------ ------- -------- ------ ------ ------- --- -----------0 2 1.4 GHz 6 MB None 20/00 C2 Active 1 2 1.4 GHz 6 MB None 20/00 C2 Active CPU threads are turned off. MEMORY INFORMATION Press ENTER to continue, 'q' to exit: Extender 0: ---- DIMM A ----- ---- DIMM B ----- ---- DIMM C ----- ---- DIMM D ----DIMM Current DIMM Current DIMM Current DIMM Current --- ------ ---------- ------ ---------- ------ ---------- ------ ---------0 1024MB Active 1024MB Active 1024MB Active 1024MB Active 1 1024MB Active 1024MB Active 1024MB Active 1024MB Active 2 ------------Extender 1: ---- DIMM A ----- ---- DIMM B ----- ---- DIMM C ----- ---- DIMM D ----DIMM Current DIMM Current DIMM Current DIMM Current --- ------ ---------- ------ ---------- ------ ---------- ------ ---------0 1024MB Active 1024MB Active 1024MB Active 1024MB Active 1 1024MB Active 1024MB Active 1024MB Active 1024MB Active 2 ------------Active Memory : 16384 MB Installed Memory : 16384 MB I/O INFORMATION Press ENTER to continue, 'q' to exit: BOOTABLE DEVICES Order Media Type Path ----- ---------- --------------------------------------1 CDROM Acpi(HWP0002,PNP0A03,0)/Pci(2|1)/Usb(0, 0)/CDROM(Entry0) 2 HARDDRIVE Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012B32642,Lun0)/HD(Part1,SigD 3 HARDDRIVE Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012B32642,Lun0)/HD(Part3,SigD Seg Bus Dev Fnc Vendor Device Slot # # # # ID ID # Path --- --- --- --- ------ ------ --- ----------00 00 01 00 0x103C 0x1303 XX Acpi(HWP0002,PNP0A03,0)/Pci(1|0) 00 00 01 01 0x103C 0x1302 XX Acpi(HWP0002,PNP0A03,0)/Pci(1|1) 00 00 01 02 0x103C 0x1048 XX Acpi(HWP0002,PNP0A03,0)/Pci(1|2) 00 00 02 00 0x1033 0x0035 XX Acpi(HWP0002,PNP0A03,0)/Pci(2|0) 00 00 02 01 0x1033 0x0035 XX Acpi(HWP0002,PNP0A03,0)/Pci(2|1) 00 00 02 02 0x1033 0x00E0 XX Acpi(HWP0002,PNP0A03,0)/Pci(2|2) 00 14 01 00 0x1000 0x0054 01 Acpi(HWP0002,PNP0A03,400)/Pci(1|0) 00 14 02 00 0x8086 0x1079 02 Acpi(HWP0002,PNP0A03,400)/Pci(2|0) Press ENTER to continue, 'q' to exit: 00 14 02 01 0x8086 0x1079 02 Acpi(HWP0002,PNP0A03,400)/Pci(2|1) Fast initialization: Enabled System Wake-On-LAN: Enabled BOOT INFORMATION Monarch CPU: Current Preferred Monarch Monarch CPU CPU Module/ Module/ Logical Logical Warnings ------- --------- -------0/0 0/0 AutoBoot: ON - Timeout is : 7 sec Boottest: BOOTTEST Settings Default Variable Press ENTER to continue, 'q' to exit: OS is not speedy boot aware. Selftest Setting ---------------------early_cpu Run this test late_cpu Run this test platform Run this test chipset Run this test io_hw Run this test mem_init Run this test mem_test Run this test LAN Address Information: LAN Address Path ----------------- ---------------------------------------*Mac(0017A451CECC) Acpi(HWP0002,PNP0A03,400)/Pci(2|0)/Mac(0017A451CECC) Mac(0017A451CECD) Acpi(HWP0002,PNP0A03,400)/Pci(2|1)/Mac(0017A451CECD) FIRMWARE INFORMATION Press ENTER to continue, 'q' to exit: *System Firmware A Revision: 1.32 [4642]

7/37

HPUXCheatSheet

07/17/07 13:40:06

PAL_A: 7.31/7.46 PAL_B: 7.46 EFI Spec: 1.10 EFI Intel Drop: 14.62 EFI Build: 5.37 SAL Spec: 3.01 SAL_A: 2.00 SAL_B: 1.32 POSSE: 0.20 ACPI: 7.00 SMBIOS: 2.3.2a System Firmware B Revision: 1.32 [4642] BMC Revision: 5.07 IPMI: 1.00 Management Processor Revision: F.01.41 Updatable EFI Drivers: Floating-Point Software Assistance Handler: 00000118 Broadcom Gigabit Ethernet Driver: 0007000A SCSI Bus Driver: 00000021 SCSI Tape Driver: 00000020 Usb Ohci Driver: 00000033 USB Bus Driver: 00000014 USB Bot Mass Storage Driver: 00000014 Press ENTER to continue, 'q' to exit: Shell> lanaddress LAN Address Information LAN Address Path ----------------- ---------------------------------------*Mac(0017A451CECC) Acpi(HWP0002,PNP0A03,400)/Pci(2|0)/Mac(0017A451CECC) Mac(0017A451CECD) Acpi(HWP0002,PNP0A03,400)/Pci(2|1)/Mac(0017A451CECD) Shell> time 18:25:50 Shell> date 03/07/2007 Shell> map -b -r -fs (map potential boot devices) Device mapping table fs0 : Acpi(HWP0002,PNP0A03,0)/Pci(2|1)/Usb(0, 0)/CDROM(Entry0) fs1 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012B32642,Lun0)/HD(Part1,SigD5EAE962-9062fs2 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012B32642,Lun0)/HD(Part3,SigD5EAEA02-9062Shell> # shutdown -hy 0 SHUTDOWN PROGRAM 03/07/07 12:01:27 CST Broadcast Message from root (console) Wed Mar 7 12:01:27... SYSTEM BEING BROUGHT DOWN NOW ! ! ! /sbin/auto_parms: DHCP access is disabled (see /etc/auto_parms.log) System shutdown in progress ___________________________ Stop CDE login server ........................................... Stop kwdbd ...................................................... Stopping HP-UX Apache-based Web Server .......................... Stopping HP-UX Tomcat-based Servlet Engine. ..................... Stopping HP-UX Webmin-based Admin ............................... Stopping the HPUX Webproxy subsystem ............................ Stopping HP-UX XML Web Server Tools ............................. Stop X print server(s) .......................................... Stop NFS server subsystem ....................................... Shutting down CIFS Client ....................................... Stopping Event Monitoring Service ............................... Shutting down the Winbind Daemon ................................ Unload/Uninstall XF86 DLKM Helper Modules ....................... Stopping the gWLM Agent ......................................... Shutting down the System Management HomePage server ............. Stopping USB hub daemon ......................................... Stopping audio server daemon .................................... Stop auditing subsystem ......................................... Stop environment monitoring daemon .............................. Stop diagnostic subsystem ....................................... Stop clock daemon ............................................... Stop print spooler .............................................. Stopping HP Disk Array Manager daemons. ......................... Stop accounting ................................................. Stopping time synchronization ................................... Stop vt daemon .................................................. Terminating X Font Server ....................................... Stopping HP-UX Secure Shell ..................................... Stopping Instant Capacity ....................................... Stop CIM cimserver subsystem .................................... Stop RPC daemon ................................................. Stopping SNMP PCI FDDI Network Management subAgent ..............

OK N/A OK N/A OK OK OK N/A OK N/A OK OK OK OK OK OK OK N/A OK OK OK OK OK N/A N/A OK OK OK N/A OK OK OK

8/37

HPUXCheatSheet

07/17/07 13:40:06

Stop DCE daemons ................................................ OK Stopping OSPF MIB Network Management subAgent ................... N/A Stopping SNMP HP-UNIX Network Management subAgent ............... OK Stopping SNMP IPv6 Network Management subAgent .................. OK Stopping SNMP MIB-2 Network Management subAgent ................. OK Stopping Native Adapter Agent ................................... OK Stopping SNMP Trap Dest Network Management subAgent ............. OK Stopping SNMP Master Network Management daemon .................. OK Stopping outbound connection daemons for DDFA software .......... N/A Stopping syslog-ng daemons ...................................... N/A Stopping cfengine's cfservd daemon .............................. N/A Stopping mail daemon ............................................ OK Stopping IPv6 router advertisement daemon ....................... N/A Stopping remote system status daemon ............................ N/A Stopping RARP protocol daemon ................................... N/A Stop PPPoE configuration ........................................ N/A Stop PPP configuration .......................................... OK Stopping router discover protocol daemon ........................ N/A Stopping dynamic routing daemon ................................. N/A Stopping Internet services daemon ............................... OK Stopping multicast routing daemon ............................... N/A Stop the Trusted Mode with NIS+ subsystem ....................... OK Stop NFS client subsystem ....................................... OK Stop NIS client subsystem ....................................... OK Stop ldap client daemon ......................................... OK Stop NIS/LDAP server subsystem .................................. N/A Stop NIS server subsystem ....................................... OK Stop NIS+ client subsystem ...................................... OK Stop NIS+ server subsystem ...................................... OK Stop NFS core subsystem ......................................... OK Stop Runner ..................................................... N/A Stopping ISEE hpservices mad daemon. ............................ OK Stopping name server daemon ..................................... N/A VxVM VVR INFO V-5-4-2419 Stopping VRAS daemon ................... OK VxVM VVR INFO V-5-4-2419 Stopping VxRSync daemon ................ OK Unconfiguring DHCPv6 Interfaces ................................. OK VxVM VVR INFO V-5-2-3620 Stopping Communication Daemon .......... OK Stopping DHCPv6 Server daemon ................................... N/A Stopping sfmdb PostgreSQL daemons ............................... OK Unconfigure LAN interfaces ...................................... OK Unconfigure LAN interfaces for IPv6 ............................. OK Unconfigure HP gelan Gigabit Ethernet interfaces ................ OK Unconfigure HP iether 100BT/Gigabit Ethernet interfaces ......... OK Unconfigure HP igelan Gigabit Ethernet interfaces ............... OK Stop network tracing and logging daemon ......................... OK Stop pty allocator daemon ....................................... OK Stop system message logging daemon .............................. OK Stop Software Distributor agent daemon .......................... OK Unconfigure Loopback interfaces (lo0) ........................... OK Stopping VERITAS Enterprise Administrator Service (vxsvc) ....... OK Stop Utmp Daemon ................................................ OK Stop syncer daemon .............................................. OK Stop Kernel Logging facility .................................... OK Killing user processes .......................................... OK Move nextboot kernel configuration into place ................... N/A Unmount file systems ............................................ OK VxVM INFO V-5-2-3254 Stopping all Volume Manager I/O Daemons .... OK Transition to run-level 0 is complete. Executing "/sbin/reboot -h ". Shutdown at 12:02 (in 0 minutes) *** FINAL System shutdown message from root@uapm3501p *** System going down IMMEDIATELY System shutdown time has arrived sync'ing disks (0 buffers to flush): 0 buffers not flushed 0 buffers still dirty Closing open logical volumes... Done MP MAIN MENU: CO: Console VFP: Virtual Front Panel CM: Command Menu SMCLP: Server Management Command Line Protocol CL: Console Log SL: Show Event Logs HE: Main Help Menu X: Exit Connection [mp0014c29c14b7] MP> cm (Use Ctrl-B to return to MP main menu.) [mp0014c29c14b7] MP:CM> help HE ==== MP Help: Main Menu =======================================================

9/37

HPUXCheatSheet

07/17/07 13:40:06

Hardware Revision R0 Firmware Revision F.01.41 Jun 27 2006,17:28:15 Integrated Lights-Out for HP Integrity and HP 9000 - Management Processor (MP) MP Help System Use Ctrl-B to exit MP command interface and return to the main MP menu. Enter a command at the help prompt: OVerview : Launch the help overview LIst : Show the list of MP Command Menu commands <COMMAND> : Enter the command name for help on individual command TOPics : Show all MP Help topics and commands HElp : Display this screen Q : Quit help ==== MP:HE> lis lis ==== MP Help: Command Menu List ============================================= BP : Reset BMC Passwords PC : Remote Power Control CA : Configure asynch/serial ports PR : Power Restore Policy Config. DATE: Display Date PS : Power management module Status DC : Default Configuration RB : Reset BMC DF : Display FRU Information RS : Reset System through RST signal DI : DIsconnect users SA : Set MP Access DNS : Configure DHCP and DNS SNMP: Configure SNMP parameters FW : Upgrade MP firmware SO : Security Options HE : Display Help SS : System processors Status ID : System Information SYSREV: Display System firmware Revs. IT : Modify MP inactivity timeouts TC : Reset system via INIT LC : Configure LAN, SSH and Web ports TE : TEll- send a msg. to other users LDAP: Configure Directory parameters UC : User Configuration LM : License Management WHO : Display connected MP users LOC : Locator LED display XD : Diagnostics and reset of MP LS : LAN Status ==== (HE for main help, enter command name, or Q to quit) MP:HE> li cm li cm ==== MP Help: Command Menu List ============================================= BP : Reset BMC Passwords PC : Remote Power Control CA : Configure asynch/serial ports PR : Power Restore Policy Config. DATE: Display Date PS : Power management module Status DC : Default Configuration RB : Reset BMC DF : Display FRU Information RS : Reset System through RST signal DI : DIsconnect users SA : Set MP Access DNS : Configure DHCP and DNS SNMP: Configure SNMP parameters FW : Upgrade MP firmware SO : Security Options HE : Display Help SS : System processors Status ID : System Information SYSREV: Display System firmware Revs. IT : Modify MP inactivity timeouts TC : Reset system via INIT LC : Configure LAN, SSH and Web ports TE : TEll- send a msg. to other users LDAP: Configure Directory parameters UC : User Configuration LM : License Management WHO : Display connected MP users LOC : Locator LED display XD : Diagnostics and reset of MP LS : LAN Status ==== (HE for main help, enter command name, or Q to quit) MP:HE> MP MAIN MENU: CO: Console VFP: Virtual Front Panel CM: Command Menu SMCLP: Server Management Command Line Protocol CL: Console Log SL: Show Event Logs HE: Main Help Menu X: Exit Connection [mp0014c29c14b7] MP> cp *** Invalid Selection *** MP MAIN MENU: CO: Console VFP: Virtual Front Panel CM: Command Menu SMCLP: Server Management Command Line Protocol CL: Console Log SL: Show Event Logs HE: Main Help Menu X: Exit Connection [mp0014c29c14b7] MP> pc *** Invalid Selection *** MP MAIN MENU: CO: Console VFP: Virtual Front Panel CM: Command Menu SMCLP: Server Management Command Line Protocol

10/37

HPUXCheatSheet

07/17/07 13:40:06

CL: Console Log SL: Show Event Logs HE: Main Help Menu X: Exit Connection [mp0014c29c14b7] MP> cm (Use Ctrl-B to return to MP main menu.) [mp0014c29c14b7] MP:CM> pc PC Current System Power State: Off Power Control Menu: C - Power Cycle ON - Power On OFF - Power Off G - Graceful Shutdown Enter menu item or [Q] to Quit: on on System will be powered on. Confirm? (Y/[N]): y y -> System is being powered on. [mp0014c29c14b7] MP:CM> ? HE ==== MP Help: Main Menu ======================================================= Hardware Revision R0 Firmware Revision F.01.41 Jun 27 2006,17:28:15 Integrated Lights-Out for HP Integrity and HP 9000 - Management Processor (MP) MP Help System Use Ctrl-B to exit MP command interface and return to the main MP menu. Enter a command at the help prompt: OVerview : Launch the help overview LIst : Show the list of MP Command Menu commands <COMMAND> : Enter the command name for help on individual command TOPics : Show all MP Help topics and commands HElp : Display this screen Q : Quit help ==== MP:HE> MP MAIN MENU: CO: Console VFP: Virtual Front Panel CM: Command Menu SMCLP: Server Management Command Line Protocol CL: Console Log SL: Show Event Logs HE: Main Help Menu X: Exit Connection [mp0014c29c14b7] MP> vfp Welcome to the Virtual Front Panel (VFP). Use Ctrl-B to exit. System state Activity # of logs since boot ----------------------------------------System Starting BOOT_CPU_PRESENT 15 E indicates error since last boot LEDs | LOCATOR | SYSTEM | INT. HEALTH | EXT. HEALTH | POWER ----------------------------------------------------------------------------| OFF | OFF | ON GREEN | ON GREEN | ON GREEN ----------------------------------------------------------------------------Status | POW:System Power on | INT:Internal parts, including CPUs and Memory, okay | EXT:Externally accessible fans and power supplies okay ----------------------------------------------------------------------------[mp0014c29c14b7] MP:VFP(Use '?' to display VFP terminal info or Ctrl-B to Quit)> MP MAIN MENU: CO: Console VFP: Virtual Front Panel CM: Command Menu SMCLP: Server Management Command Line Protocol CL: Console Log SL: Show Event Logs HE: Main Help Menu X: Exit Connection [mp0014c29c14b7] MP> co (Use Ctrl-B to return to MP main menu.) - - - - - - - - - - Prior Console Output - - - - - - - - - System shutdown time has arrived sync'ing disks (0 buffers to flush): 0 buffers not flushed 0 buffers still dirty Closing open logical volumes... Done - - - - - - - - - - - - Live Console - - - - - - - - - - - ***********************************************************

11/37

HPUXCheatSheet

07/17/07 13:40:06

* ROM Version : 01.32 * ROM Date : 10/16/2006 * BMC Version : 05.07 *********************************************************** 0 0 0x0015B2 0x0000000022689104 boot time event 1 0 0x0000A4 0x0000000000000000 start memory configuration 0 0 0x0015B2 0x0000000035707845 boot time event 1 0 0x000014 0x0000000000000000 CPU0 starting cell relocation 1 0 0x000009 0x0000000000000000 CPU0 launch EFI 3h 3h EFI version 1.10 [14.62] EFI64 Running on Intel(R) Itanium Processor Family EFI 1.10 IPF server rx3600 5.37 [Thu Nov 10 16:08:03 2005] firmware by HP Loading 'SysROM:Floating-Point Software Assistance Handler'... -- 'SysROM:Floating-Point Software Assistance Handler' returned Success Loading 'SysROM:Broadcom Gigabit Ethernet Driver'... Copyright (c) 2000-2005 Broadcom Corporation Broadcom NetXtreme Gigabit Ethernet EFI driver v7.0.10 -- 'SysROM:Broadcom Gigabit Ethernet Driver' returned Success Loading 'SysROM:SCSI Bus Driver'... -- 'SysROM:SCSI Bus Driver' returned Success Loading 'SysROM:SCSI Tape Driver'... -- 'SysROM:SCSI Tape Driver' returned Success Loading device drivers EFI Boot Manager ver 1.10 [14.62] /----------------------------------\ Use <^|v> to scroll <ENTER> to Select <ESC> or <X/x> for Previous Menu

OS might use only the /------------------

Searching for devices Loading.: EFI Shell [Built-in] EFI Shell version 1.10 [14.62] Device mapping table fs0 : Acpi(HWP0002,PNP0A03,0)/Pci(2|1)/Usb(0, 0)/CDROM(Entry0) fs1 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012B32642,Lun0)/HD(Part1,SigD5EAE962-9062fs2 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012B32642,Lun0)/HD(Part3,SigD5EAEA02-9062blk0 : Acpi(HWP0002,PNP0A03,0)/Pci(2|1)/Usb(0, 0) blk1 : Acpi(HWP0002,PNP0A03,0)/Pci(2|1)/Usb(0, 0)/CDROM(Entry0) blk2 : Acpi(HWP0002,PNP0A03,0)/Pci(2|1)/Usb(0, 0)/CDROM(Entry1) blk3 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012B32642,Lun0) blk4 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012B32642,Lun0)/HD(Part1,SigD5EAE962-9062blk5 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012B32642,Lun0)/HD(Part2,SigD5EAE98A-9062blk6 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012B32642,Lun0)/HD(Part3,SigD5EAEA02-9062blk7 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012AFDE82,Lun0) startup.nsh> echo -off Welcome to HP-UX Install Media (C) Copyright 1999-2006 Hewlett-Packard Development Company, L.P. All rights reserved HP-UX Boot Loader for IPF -- Revision 2.028 Press Any Key to interrupt Autoboot AUTO ==> boot :IINSTALL Seconds left till autoboot 1 Type 'help' for help HPUX> HPUX> ? -- HPUX bootloader for IPF Help --------- supported commands --------boot [kernel] - boots HPUX kernel help [-d] - help screen (-d to list debug commands) mmap - show current EFI memory map ls [-aRdnlogrtucpFLis] [path...] ll [-aRdnlogrtucpFLis] [path...] (same as ls -alF) setauto [-d] [str] - sets AUTO file (-d to delete AUTO file) showauto - shows AUTO file ver - prints version numbers exit - exits bootloader HPUX> exit Exiting bootloader. Shell> Shell> Shell> ? List of classes of commands: boot -- Booting options and disk-related commands configuration -- Changing and retrieving system information device -- Getting device, driver and handle information memory -- Memory related commands shell -- Basic shell navigation and customization scripts -- EFI shell-script commands Use 'help <class>' for a list of commands in that class Use 'help <command>' for full documentation of a command

12/37

HPUXCheatSheet

07/17/07 13:40:06

Use 'help -a' to display list of all commands Shell> map -b -r -fs Device mapping table fs0 : Acpi(HWP0002,PNP0A03,0)/Pci(2|1)/Usb(0, 0)/CDROM(Entry0) fs1 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012B32642,Lun0)/HD(Part1,SigD5EAE962-9062fs2 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012B32642,Lun0)/HD(Part3,SigD5EAEA02-9062Shell> Shell> fs1:\efi\hpux\hpux.efi (C) Copyright 1999-2006 Hewlett-Packard Development Company, L.P. All rights reserved HP-UX Boot Loader for IPF -- Revision 2.028 Press Any Key to interrupt Autoboot \efi\hpux\AUTO ==> boot vmunix Seconds left till autoboot 0 AUTOBOOTING...> System Memory = 16354 MB loading section 0 .......................................................... (complete) loading section 1 .............. (complete) loading symbol table loading System Directory (boot.sys) to MFS .... loading MFSFILES directory (bootfs) to MFS ............... Launching /stand/vmunix SIZE: Text:29267K + Data:7078K + BSS:5240K = Total:41586K Console is on a Serial Device Booting kernel...

1.8 Installing the OS


1.8.1 Recommended Filesystem Layout in the SAP landscape
The following rules should be followed while building servers in this AES SAP landscape. Improvise when in a bind though... Filesystem / /stand /var /crashvol /tmp /util swap Size Comment 15GB 1GB 10GB see comment 0.5 x Physical Memory on server (eg: 16GB RAM == 8GB crashvol) 10GB 10GB see comment 2 x Physical RAM (preferred) or 1 x Physical RAM

1.8.2 Installing from DVD/CDROM


Boot from internal bootable DVD or get to the EFI shell and then launch the install.efi program from the cd/dvd device.

Shell> map -b -r -fs Device mapping table fs0 : Acpi(HWP0002,PNP0A03,0)/Pci(2|1)/Usb(0, 0)/CDROM(Entry0) fs1 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012B32642,Lun0)/HD(Part1,SigD5EAE962-9062 fs2 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E012B32642,Lun0)/HD(Part3,SigD5EAEA02-9062 Shell> fs0:\install.efi (C) Copyright 1999-2006 Hewlett-Packard Development Company, L.P. All rights reserved HP-UX Boot Loader for IPF -- Revision 2.028 Press Any Key to interrupt Autoboot AUTO ==> boot :IINSTALL Seconds left till autoboot 0 AUTOBOOTING...

And then follow the options to do a manual installation of HPUX.


User Interface and Media Options This screen lets you pick from options that will determine if an Ignite-UX server is used, and your user interface preference. Source Location Options: [ * ] Media only installation [ ] Media with Network enabled (allows use of SD depots) [ ] Ignite-UX server based installation User Interface Options:

13/37

HPUXCheatSheet

07/17/07 13:40:06

[ ] Guided Installation (recommended for basic installs) [ * ] Advanced Installation (recommended for disk and filesystem management) [ ] No user interface - use all the defaults and go Hint: If you need to make LVM size changes, or want to set the final networking parameters during the install, you will need to use the Advanced mode (or remote graphical interface). [ OK ] [ Cancel ] [ Help ]

Choose the "Advanced Installation option". Be sure to remember to choose the VxVM and VxFS option (defaults to LVM and VxFS).

Once the installation is done, the system will reboot and come up with VxVM-encapsulated root disk. You will have to manually configure the mirror disk.

1.8.3 Setting up the Golden Image and Ignite server


create Golden Image archive directory on the HP-UX Ignite server (now its UAPA3500D, a.k.a AESA17) # mkdir p /var/opt/ignite/archives/Rel_B.11.23 share /var/opt/ignite/archives/Rel_B.11.23 as read-only and /var/opt/ignite/clients as read-write on the Ignite server
# cat /etc/exports /var/opt/ignite/clients -anon=2

14/37

HPUXCheatSheet
/var/opt/ignite/archives/Rel_B.11.23 -ro,anon=2 # exportfs a # exportfs /var/opt/ignite/clients -anon=2 /var/opt/ignite/archives/Rel_B.11.23 -ro,anon=2

07/17/07 13:40:06

created the archive directory on the server (Golden Image source server) whose image will be used as Golden Image
# mkdir p /var/opt/ignite/archives/Rel_B.11.23

make sure there is NO user and activity on the Golden Image source server before proceeding to the next step on the Golden Image source server, copy the make_sys_image script to /tmp and make it executable
# cp make_sys_image /tmp/make_sys_image # chmod 755 /tmp/make_sys_image

create the golden Image under the archive directory on the source server, the file name will be hostname.gz, do NOT interrupt once make_sys_image is running
# /tmp/make_sys_image -d /var/opt/ignite/archives/Rel_B.11.23 -s local * Preparing to create a system archive. * Testing for necessary pax patch. * Passed pax tests. WARNING: CLEAN_LEVEL set to 2: (see -l option for make_sys_image(1M)) While this command is executing at clean level 2, the system should be as quiet as possible. The host and/or networking information on the system are temporarily set to newconfig values. After the command is complete these files are returned to their previous state. Creating keepsafe archive with file /stand/system Creating your system file in the file /var/tmp/make_sys_image.hwsys.a06738 Appending file /.profile to keepsafe archive .Appending file /etc/rc.config.d/hpfcmsconf to keepsafe archive .Appending file /etc/rc.config.d/netconf to keepsafe archive .Appending file /etc/rc.config.d/netdaemons to keepsafe archive .Appending file /etc/rc.config.d/namesvrs to keepsafe archive .Appending file /etc/rc.config.d/mailservs to keepsafe archive .Appending file /etc/rc.config.d/xfs to keepsafe archive .Appending file /etc/hosts to keepsafe archive .Appending file /etc/group to keepsafe archive .Appending file /etc/mail/sendmail.cw to keepsafe archive .Appending file /etc/netgroup to keepsafe archive .Appending file /etc/ntp.conf to keepsafe archive .Appending file /etc/vue/config/Xsession.d/0070.recs to keepsafe archive .Appending file /var/adm/sw/security/_ACL to keepsafe archive .Appending file /var/adm/sw/security/_OWNER to keepsafe archive .Appending file /var/adm/sw/security/_PROD_DFLT_ACL to keepsafe archive .Appending file /var/adm/sw/security/_SOC_DFLT_ACL to keepsafe archive .Appending file /var/adm/sw/security/secrets to keepsafe archive .Appending file /var/adm/sw/security/secrets.pag to keepsafe archive Appending file /var/adm/sw/security/secrets.dir to keepsafe archive * NOTE: The following core file(s) was/were found on your system and will be archived in the system image. /sapmnt/sap/E02/D21/work/core /core * Archiving contents of uapa3500d via tar to /var/opt/ignite/archives/Rel_B.11.23/uapa3500d.gz. * Creation of system archive complete. * Clean up: Do not interrupt; restoring files, kernel, and transition links.

transfer the Golden Image archive hostname.gz to IgniteServer:/var/opt/ignite/archives/Rel_B.11.23 on Ignite server, copy the archive configuration file to Ignite core configuration directory
# cp B.11.23.golden_image.cfg /var/opt/ignite/data/Rel_B.11.23/core_archive_cfg

edit core_archive_cfg file to add the Golden Image archive into software selection sets
# vi /var/opt/ignite/data/Rel_B.11.23/core_archive_cfg nfs_source = "10.228.137.57:/var/opt/ignite/archives/Rel_B.11.23" init sw_sel "B.11.23 IA golden image archive IA64 04/25/2007" {

15/37

HPUXCheatSheet
description sw_source sw_category archive_type = = = = "B.11.23 IA golden image archive IA64 04/25/2007" "golden image archive" "HPUXEnvironments" gzip tar

07/17/07 13:40:06

# For NFS, the path to the archive is relative to the mount point # specified in the "nfs_source" keyword within the sw_source stanza # above: archive_path = "uapa3501p.gz" # Here we describe how much space is used in each of the mentioned # subdirectories. This information is obtained by running the # "archive_impact" command against an archive as follows: # /opt/ignite/lbin/archive_impact -tg hostname.gz # The output from the above command should replace the "impacts" # statements below. # impacts = "/" 31Kb impacts = "/.mozilla" 2309Kb impacts = "/.ssh" 1Kb impacts = "/Solaris" 4Kb impacts = "/aessapd" 1Kb impacts = "/dev" 17Kb impacts = "/etc" 134700Kb impacts = "/export" 1Kb impacts = "/home" 5Kb impacts = "/opt" 4348551Kb impacts = "/oracle" 69983Kb impacts = "/sapmnt" 815Kb impacts = "/sbin" 175705Kb impacts = "/stand" 125403Kb impacts = "/temp_tombstone" 1Kb impacts = "/usr" 2517284Kb impacts = "/var" 1368229Kb } = TRUE vxvm_version="5.0"

edit INDEX file to include the Golden Image archive


# vi /var/opt/ignite/INDEX cfg "HP-UX B.11.23 Golden Archive Image IA64 04/25/2007" { description "This is the golden image archive for B.11.23 release IA64." "/opt/ignite/data/Rel_B.11.23/config" "/var/opt/ignite/data/Rel_B.11.23/core_archive_cfg" "/var/opt/ignite/config.local" }

make sure the Golden Image archive is in the list


# manage_index -l HP-UX B.11.00 Default HP-UX B.11.11 Default HP-UX B.11.23 Golden Archive Image UAPA3500D 04/24/2007 HP-UX B.11.23 Golden Archive Image IA64 04/25/2007 HP-UX B.11.23 Default

1.8.4 Installing via network using an Ignite Image


Prepare Golden Image on the HP-UX Ignite server, please refer to Make HP-UX Ignite Golden Image Make sure the install target (the client) is on the same subnet as the Ignite server On the client, run add_new_client to add its configuration onto Ignite server # add_new_client s 10.228.137.57 on the Ignite server, copy the customized config file to clients directory

# cp /var/opt/ignite/clients/SAP_APPS_RX6600/config /var/opt/ignite/clients/clien on the Ignite server, edit the config file for the client
# cd /var/opt/ignite/clients/client_name/ # vi config

16/37

HPUXCheatSheet
system_name="client_name" init _hp_ikernel_os_release="B.11.23" init _hp_boot_dev_path="0/4/1/0.0.0.0.0" init _hp_default_cur_lan_dev="0/4/2/0" init _hp_primary_path="0/4/1/0.0.0.1.0" init sw_sel "B.11.23 IA golden image archive IA64 04/25/2007"{ description="B.11.23 IA golden image archive IA64 04/25/2007" sw_source="golden image archive" sw_category="HPUXEnvironments" archive_path="uapa3501p.gz" archive_type=gzip tar impacts="/" 31K impacts="/.mozilla" 2309K impacts="/.ssh" 1K impacts="/Solaris" 4K impacts="/aessapd" 1K impacts="/dev" 17K impacts="/etc" 134700K impacts="/export" 1K impacts="/home" 5K impacts="/opt" 4348551K impacts="/oracle" 69983K impacts="/sapmnt" 815K impacts="/sbin" 175705K impacts="/stand" 125403K impacts="/temp_tombstone" 1K impacts="/usr" 2517284K impacts="/var" 1368229K } = TRUE # # Disk and Filesystems # _hp_disk_layout+={"Modified VxVM Layout"} init _hp_disk_layout="Modified VxVM Layout" (_hp_disk_layout=="Modified VxVM Layout") { # Disk/Filesystem Layout: volume_group "rootdg" { usage=VXVM physical_volume disk[_hp_root_disk] { } # end pv_options max_physical_extents=2500 physical_extent_size=32 logical_volume "standvol"{ mount_point="/stand" disk[_hp_root_disk] usage=VxFS size=1048576K BLKSIZE=8192 bad_block_relocate=FALSE contiguous_allocation=TRUE } # end logical_volume logical_volume "swapvol"{ mount_point="primary" disk[_hp_root_disk] usage=SWAP_DUMP size=_hp_min_swap |remaining | _hp_pri_swap bad_block_relocate=FALSE contiguous_allocation=TRUE } # end logical_volume logical_volume "rootvol"{ mount_point="/" disk[_hp_root_disk] usage=VxFS size=15728640K BLKSIZE=8192 bad_block_relocate=FALSE contiguous_allocation=TRUE } # end logical_volume logical_volume "tmpvol"{ mount_point="/tmp" usage=VxFS size=10485760K BLKSIZE=8192 largefiles=TRUE } # end logical_volume logical_volume "varvol"{ mount_point="/var" usage=VxFS size=10485760K BLKSIZE=8192 largefiles=TRUE } # end logical_volume

07/17/07 13:40:06

17/37

HPUXCheatSheet
logical_volume "crashvol"{ mount_point="/var/adm/crash" usage=VxFS size=10485760K BLKSIZE=8192 largefiles=TRUE } # end logical_volume } # end volume_group "rootdg" } # end "Modified VxVM Layout"

07/17/07 13:40:06

After editing the client config file, run this command to verify whether the syntax is correct -instl_adm -T -f config add install client into /etc/bootptab on the Ignite server
# vi /etc/bootptab IA64_AES_LC-defaults:\ ht=ethernet:\ hn:\ bf=/opt/ignite/boot/nbp.efi:\ bs=48:\ sm=255.255.252.0:\ gw=10.228.139.250 uapa3501p:tc=IA64_AES_LC-defaults:ip=10.228.137.51:ha=0017A451D212 uapa3501q:tc=IA64_AES_LC-defaults:ip=10.228.137.56:ha=0017A451D0DC

On the Ignite server, start the Golden Image installation on the client
# bootsys -a -v -i " B.11.23 IA golden image archive IA64 04/25/2007" client_name

answer yes when asked if you want bootp to create /.rhosts file on the install client for remsh to work 1.8.4.1 Initiate ignite installation from the client Go into the EFI shell of the server (ignite client) and run the following command to set up a profile that can be used to access a specific ignite server.
Shell> dbprofile -dn sNap -sip 10.228.137.57 -cip \ dbprofile: Client IP address is invalid Exit status code: Invalid Parameter Shell> dbprofile -dn snap -sip 10.228.137.57 -cip 10.228.136.18 -gip 10.228.139.250 -m 255.255.252.0 Creating profile snap

Now run the following command to access that lanboot profile (in our case "snap") and kick off the installation.
Shell> lanboot select -dn snap 01 Acpi(HWP0002,PNP0A03,200)/Pci(1|0)/Pci(6|0)/Mac(00163573854A) 02 Acpi(HWP0002,PNP0A03,200)/Pci(1|0)/Pci(6|1)/Mac(00163573854B) 03 Acpi(HWP0002,PNP0A03,300)/Pci(1|0)/Pci(6|0)/Mac(0017A4A4B4F0) 04 Acpi(HWP0002,PNP0A03,300)/Pci(1|0)/Pci(6|1)/Mac(0017A4A4B4F1) 05 Acpi(HWP0002,PNP0A03,400)/Pci(2|0)/Mac(001A4B066BF2) 06 Acpi(HWP0002,PNP0A03,400)/Pci(2|1)/Mac(001A4B066BF3) 07 Acpi(HWP0002,PNP0A03,500)/Pci(1|0)/Pci(4|0)/Mac(0018714EB780) 08 Acpi(HWP0002,PNP0A03,500)/Pci(1|0)/Pci(4|1)/Mac(0018714EB781) 09 Acpi(HWP0002,PNP0A03,500)/Pci(1|0)/Pci(6|0)/Mac(0018714EB782) 10 Acpi(HWP0002,PNP0A03,500)/Pci(1|0)/Pci(6|1)/Mac(0018714EB783) 11 Acpi(HWP0002,PNP0A03,600)/Pci(1|0)/Pci(6|0)/Mac(00163573954A) 12 Acpi(HWP0002,PNP0A03,600)/Pci(1|0)/Pci(6|1)/Mac(00163573954B) 13 Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Pci(4|0)/Mac(0018714EB738) 14 Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Pci(4|1)/Mac(0018714EB739) 15 Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Pci(6|0)/Mac(0018714EB73A) 16 Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Pci(6|1)/Mac(0018714EB73B) Select Desired LAN: 05 Selected Acpi(HWP0002,PNP0A03,400)/Pci(2|0)/Mac(001A4B066BF2)

Client MAC Address: 00 1A 4B 06 6B F2 Client IP Address: 10.228.136.18 Subnet Mask: 255.255.252.0 BOOTP Server IP Address: 10.228.137.57 DHCP Server IP Address: 0.0.0.0 Boot file name: /opt/ignite/boot/nbp.efi Retrieving File Size. Retrieving File (TFTP).

18/37

HPUXCheatSheet
@(#) HP-UX IA64 Network Bootstrap Program Revision 1.0 Downloading HPUX bootloader Starting HPUX bootloader Obtaining size of fpswa.efi (328192 bytes) Downloading file fpswa.efi (328192 bytes) (C) Copyright 1999-2006 Hewlett-Packard Development Company, L.P. All rights reserved HP-UX Boot Loader for IPF -Revision 2.028

07/17/07 13:40:06

Booting from Lan Obtaining size of AUTO (26 bytes) Downloading file AUTO (26 bytes) Press Any Key to interrupt Autoboot AUTO ==> boot Rel_B.11.23/IINSTALL Seconds left till autoboot 0 AUTOBOOTING...Obtaining size of Rel_B.11.23/IINSTALL Downloading file Rel_B.11.23/IINSTALL /

(22186598 bytes)

Boots of the network via the nbp.efi -Creating VxVM volume "rootdg/crashvol" (/var/adm/crash). CREATE_VOLUME: Disk "c9t1d0s2" is not a valid dmpnode name. CREATE_VOLUME: Using dmpnode "c9t1d0s2" instead. Making VxFS filesystem for "/stand", (/dev/vx/rdsk/rootdg/standvol). Making VxFS filesystem for "/", (/dev/vx/rdsk/rootdg/rootvol). Making VxFS filesystem for "/tmp", (/dev/vx/rdsk/rootdg/tmpvol). Making VxFS filesystem for "/var", (/dev/vx/rdsk/rootdg/varvol). Making VxFS filesystem for "/var/adm/crash", (/dev/vx/rdsk/rootdg/crashvol). * Configure_Disks: Complete * Download_mini-system: Begin ./usr/sbin/idisk, 77068 bytes, 151 tape blocks ./sbin/fs/hfs/mkfs, 586996 bytes, 1147 tape blocks ./sbin/fs/hfs/newfs, 461420 bytes, 902 tape blocks ./sbin/fs/vxfs/mkfs, 1966500 bytes, 3841 tape blocks ./sbin/fs/vxfs/newfs, 461988 bytes, 903 tape blocks ./sbin/fs/vxfs5.0/mkfs, 3147180 bytes, 6147 tape blocks ./sbin/fs/vxfs5.0/newfs, 1704600 bytes, 3330 tape blocks ./sbin/mkfs symbolic link to /sbin/fs_wrapper ./sbin/newfs symbolic link to /sbin/fs_wrapper ./sbin/lib/mfsconfig.d/hfs, 1053 bytes, 3 tape blocks ./sbin/lib/mfsconfig.d/vxfs5.0, 3040 bytes, 6 tape blocks ./sbin/fs_wrapper, 488324 bytes, 954 tape blocks ./sbin/sh, 989732 bytes, 1934 tape blocks * * * * * * * *

x x x x x x x x x x x x x

The installation will prompt you for some inputs (like whether you want to continue with the automated install or want to manually customize the installation, etc) after which, complete installing the OS and reboot the server.

1.8.5 Removing old LVM (factory-set) boot disk and mirroring rootdisk
When the ignite installation completes, it will usually install to the non-LVM internal disk of the server (when using VxVM based installation) and mark the original rootdisk as owned by LVM and therefore, unusable. While this disk can be initialized as an "hpdisk", it doesn't show the complete size of the disk (for eg: it might show that it's short by 40GB (in case of an 140GB disk)). In order to remedy that, we need to do the following -# vxdisk list DEVICE TYPE DISK GROUP STATUS c1t0d1 auto:none online invalid c1t0d2 auto:none online invalid c1t0d3 auto:none online invalid c1t0d4 auto:none online invalid c1t0d5 auto:none online invalid c3t0d0 auto:none online invalid c3t0d1 auto:none online invalid c3t0d2 auto:none online invalid c3t0d3 auto:none online invalid c3t0d4 auto:none online invalid c3t0d5 auto:none online invalid c5t0d0 auto:none online invalid c9t0d0 auto:hpdisk online c9t1d0s2 auto:hpdisk rootdisk01 rootdg online root@uapa3505d:/ # vxdisksetup -ifB c9t0d0 VxVM vxdisk ERROR V-5-1-3421 Device c9t0d0s2 is already in use by LVM. root@uapa3505d:/ # vxdestroy_lvmroot -v c9t0d0 VxVM vxdestroy_lvmroot INFO V-5-2-3941 12:24: Device c9t0d0 is actually c9t0d0s2

19/37

HPUXCheatSheet

07/17/07 13:40:06

VxVM vxdestroy_lvmroot INFO V-5-2-2440 12:24: Checking device c9t0d0s2 for LVM status VxVM vxdestroy_lvmroot INFO V-5-2-2439 12:24: Checking LVM device c9t0d0s2 private region VxVM vxdestroy_lvmroot INFO V-5-2-2438 12:24: Checking LVM device c9t0d0s2 Volume Group status Are you sure about destroying c9t0d0s2 (imported on VG /dev/vg_death1) ? y VxVM vxdestroy_lvmroot INFO V-5-2-1670 12:25: Tearing down /dev/vg_death1 on device c9t0d0s2 VxVM vxdestroy_lvmroot INFO V-5-2-1680 12:25: Unmounting and removing any volumes associated with /dev/vg_death1 VxVM vxdestroy_lvmroot INFO V-5-2-1689 12:25: removing logical volume /dev/vg_death1/lvol1 VxVM vxdestroy_lvmroot INFO V-5-2-1689 12:25: removing logical volume /dev/vg_death1/lvol2 VxVM vxdestroy_lvmroot INFO V-5-2-1689 12:25: removing logical volume /dev/vg_death1/lvol3 VxVM vxdestroy_lvmroot INFO V-5-2-1689 12:25: removing logical volume /dev/vg_death1/lvol4 VxVM vxdestroy_lvmroot INFO V-5-2-1689 12:25: removing logical volume /dev/vg_death1/lvol5 VxVM vxdestroy_lvmroot INFO V-5-2-1689 12:25: removing logical volume /dev/vg_death1/lvol6 VxVM vxdestroy_lvmroot INFO V-5-2-1689 12:25: removing logical volume /dev/vg_death1/lvol7 VxVM vxdestroy_lvmroot INFO V-5-2-1689 12:25: removing logical volume /dev/vg_death1/lvol8 VxVM vxdestroy_lvmroot INFO V-5-2-2578 12:25: Removing Volume Group /dev/vg_death1 VxVM vxdestroy_lvmroot INFO V-5-2-2579 12:25: Removing device files in /dev/vg_death1 VxVM vxdestroy_lvmroot INFO V-5-2-2577 12:25: Removing LVM Physical Volume c9t0d0s2 VxVM vxdestroy_lvmroot INFO V-5-2-1660 12:25: Removal of device c9t0d0s2, volume group /dev/vg_death1 was successful root@uapa3505d:/ # # vxdisk list DEVICE TYPE DISK c1t0d1 auto:none c1t0d2 auto:none c1t0d3 auto:none c1t0d4 auto:none c1t0d5 auto:none c3t0d0 auto:none c3t0d1 auto:none c3t0d2 auto:none c3t0d3 auto:none c3t0d4 auto:none c3t0d5 auto:none c5t0d0 auto:none c9t0d0s2 auto:none c9t1d0s2 auto:hpdisk rootdisk01 root@uapa3505d:/etc/vx/bin #

GROUP rootdg

STATUS online online online online online online online online online online online online online online

invalid invalid invalid invalid invalid invalid invalid invalid invalid invalid invalid invalid invalid

Notice that now it shows up as a sliced disk (with the "s2" at the end) and can be make a bootable hpdisk (for mirroring the root disk).

1.8.6 Verifying encapsulated Rootdisk


The default encapsulated disk and rootdg-related information looks like this:

20/37

HPUXCheatSheet
# bdf Filesystem kbytes used avail %used Mounted on /dev/vx/dsk/rootdg/rootvol 14680064 6431944 8183704 44% / /dev/vx/dsk/rootdg/standvol 1048576 81208 959920 8% /stand /dev/vx/dsk/rootdg/varvol 10485760 1741448 8677240 17% /var /dev/vx/dsk/rootdg/crashvol 8388608 18524 7846961 0% /var/adm/crash /dev/vx/dsk/rootdg/utilsvol 8388608 18524 7846961 0% /utils /dev/vx/dsk/rootdg/tmpvol 10485760 16992 10386992 0% /tmp # # vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS c1t0d0 auto:none online invalid c1t1d0s2 auto:hpdisk rootdisk01 rootdg online # vxprint -g rootdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 dg rootdg rootdg dm rootdisk01 c1t1d0s2 70762400 v crashvol fsgen ENABLED 8388608 ACTIVE pl crashvol-01 crashvol ENABLED 8388608 ACTIVE sd rootdisk01-07 crashvol-01 ENABLED 8388608 0 v rootvol root ENABLED 14680064 ACTIVE pl rootvol-01 rootvol ENABLED 14680064 ACTIVE sd rootdisk01-03 rootvol-01 ENABLED 14680064 0 v standvol fsgen ENABLED 1048576 ACTIVE pl standvol-01 standvol ENABLED 1048576 ACTIVE sd rootdisk01-01 standvol-01 ENABLED 1048576 0 v swapvol swap ENABLED 16777216 ACTIVE pl swapvol-01 swapvol ENABLED 16777216 ACTIVE sd rootdisk01-02 swapvol-01 ENABLED 16777216 0 v tmpvol fsgen ENABLED 10485760 ACTIVE pl tmpvol-01 tmpvol ENABLED 10485760 ACTIVE sd rootdisk01-04 tmpvol-01 ENABLED 10485760 0 v utilsvol fsgen ENABLED 8388608 ACTIVE pl utilsvol-01 utilsvol ENABLED 8388608 ACTIVE sd rootdisk01-05 utilsvol-01 ENABLED 8388608 0 v varvol fsgen ENABLED 10485760 ACTIVE pl varvol-01 varvol ENABLED 10485760 ACTIVE sd rootdisk01-06 varvol-01 ENABLED 10485760 0 #

07/17/07 13:40:06

PUTIL0 -

1.8.7 Mirroring the rootdisk

# vxdisk list DEVICE TYPE DISK GROUP STATUS c1t0d0 auto:none online invalid c1t1d0s2 auto:hpdisk rootdisk01 rootdg online # vxdisksetup -i c1t0d0 format=hpdisk # vxdisk list DEVICE TYPE DISK GROUP STATUS c1t0d0 auto:hpdisk online c1t1d0s2 auto:hpdisk rootdisk01 rootdg online # # vxdg -g rootdg adddisk rootdisk02=c1t0d0 # vxprint -g rootdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg rootdg rootdg dm rootdisk01 c1t1d0s2 70762400 dm rootdisk02 c1t0d0 71681696 # vxrootmir rootdisk02 Then some barfies like this: ddl_get_dynamic_attr: Could not do stat on path /dev/dsk/UUUUUUUUUUUUUUUUUUUUUU <truncated for brevity> # vxtask list TASKID PTID TYPE/STATE PCT PROGRESS 162 ATCOPY/R 82.93% 0/16777216/13913088 PLXATT swapvol swapvol-02 rootdg # # vxprint -g rootdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg rootdg rootdg dm rootdisk01 c1t1d0s2 70762400 dm rootdisk02 c1t0d0s2 70762560 v crashvol fsgen ENABLED 8388608 ACTIVE pl crashvol-01 crashvol ENABLED 8388608 ACTIVE sd rootdisk01-07 crashvol-01 ENABLED 8388608 0 v rootvol root ENABLED 14680064 ACTIVE -

21/37

HPUXCheatSheet
pl sd pl sd v pl sd pl sd v pl sd pl sd v pl sd pl sd v pl sd v pl sd pl sd # rootvol-01 rootvol rootdisk01-03 rootvol-01 rootvol-02 rootvol rootdisk02-03 rootvol-02 standvol fsgen standvol-01 standvol rootdisk01-01 standvol-01 standvol-02 standvol rootdisk02-01 standvol-02 swapvol swap swapvol-01 swapvol rootdisk01-02 swapvol-01 swapvol-02 swapvol rootdisk02-02 swapvol-02 tmpvol fsgen tmpvol-01 tmpvol rootdisk01-04 tmpvol-01 tmpvol-02 tmpvol rootdisk02-04 tmpvol-02 utilsvol fsgen utilsvol-01 utilsvol rootdisk01-05 utilsvol-01 varvol fsgen varvol-01 varvol rootdisk01-06 varvol-01 varvol-02 varvol rootdisk02-05 varvol-02 ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED 14680064 14680064 14680064 14680064 1048576 1048576 1048576 1048576 1048576 16777216 16777216 16777216 16777216 16777216 10485760 10485760 10485760 10485760 10485760 8388608 8388608 8388608 10485760 10485760 10485760 10485760 10485760 0 0 0 0 0 0 0 0 0 0 0 ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE -

07/17/07 13:40:06

The non-standard volumes aren't mirrored by "vxrootmir". Run vxassist as follows to mirror these:
And lo and behold!!! # vxassist -g rootdg mirror crashvol layout=diskalign,contig VxVM vxassist ERROR V-5-1-1401 Your license does not include support for mirroring Cannot mirror volume crashvol #

NOTE: That is because there isn't any valid Veritas License installed. Go to http://vlicense.veritas.com and generate a new license key (you'll need the Customer ID -- 1035 and the voucher or serial number off the license purchase receipt in order to generate the license.

1.9 Configuring Network interfaces and other network-related information


Network related information is stored in /etc/rc.config.d/netconf. Shown below is relevant content of an /etc/rc.config.d/netconf file:
HOSTNAME="uapm3501p" OPERATING_SYSTEM=HP-UX LOOPBACK_ADDRESS=127.0.0.1 INTERFACE_NAME[0]="lan0" IP_ADDRESS[0]="10.228.137.59" SUBNET_MASK[0]="255.255.252.0" BROADCAST_ADDRESS[0]="" INTERFACE_STATE[0]="" DHCP_ENABLE[0]=0 INTERFACE_MODULES[0]="" ROUTE_DESTINATION[0]=default ROUTE_MASK[0]="" ROUTE_GATEWAY[0]="10.228.139.250" ROUTE_COUNT[0]="1" ROUTE_ARGS[0]="" GATED=0 GATED_ARGS="" RDPD=0 RARP=0 DEFAULT_INTERFACE_MODULES="" export NODENAME=uapm3501

1.9.1 Configuring Ethernet Adapters


See above (edit the /etc/rc.config.d/netconf file).

22/37

HPUXCheatSheet

07/17/07 13:40:06

1.9.2 Configuring Default routes


Manual, non-persistent method:
# route add default gateway <IP address>

For persistent configuration, see above.

1.9.3 Checking Duplex mode and link-speed on HPUX


And we embark on the round-about... Here's how -1.9.3.1 lanscan Run the command (as shown below) to see the complete list of all NICs on the box with all associated information.
uapm3501p:(/) # lanscan Hardware Station Crd Hdw Path Address In# State 0/2/1/0/6/0 0x0016357345AC 2 UP 0/2/1/0/6/1 0x0016357345AD 3 UP 0/4/2/0 0x0017A451CECC 0 UP 0/6/1/0/6/0 0x001635733584 4 UP 0/6/1/0/6/1 0x001635733585 5 UP 0/4/2/1 0x0017A451CECD 1 UP uapm3501p:(/) # Net-Interface NamePPA lan2 snap2 lan3 snap3 lan0 snap0 lan4 snap4 lan5 snap5 lan1 snap1 NM ID MAC Type 1 ETHER 2 ETHER ETHER 4 ETHER 5 ETHER ETHER HP-DLPI Support Yes Yes Yes Yes Yes Yes DLPI Mjr# 119 119 119 119 119 119

In order to check for link speed, duplex mode etc, however, all that jumble of information is garbage (Lord I hope we can run Solaris on HP Hardware soon!). We need the following - the PPA id of the NIC you want to check We need to get that using the command shown below (our nic is lan0 and it's PPA id is 0)
uapm3501p:(/) # lanscan -pi lan2 snap2 2 lan3 snap3 3 lan0 snap0 0 lan4 snap4 4 lan5 snap5 5 lan1 snap1 1

1.9.3.2 landiag Now run landiag as shown below -uapm3501p:(/) # landiag -x 0 Speed = 1000 Full-Duplex. Autonegotiation = On.

1.9.4 Setting Duplex mode, link speed


1.9.4.1 lanadmin You could run lanadmin to check the link speed, etc (just like landiag above)
uapm3501p:(/) # lanadmin -x 0 Speed = 1000 Full-Duplex. Autonegotiation = On. uapm3501p:(/) #

But you could use it to set the speed, mode etc as well --# lanadmin -X 100FD 0

The command listed above will set the PPA ID 0 to 100FD (hundred full duplex) See the URL given below for detailed instructions -23/37

HPUXCheatSheet ['http://docs.hp.com/en/J5683-90002/ch02s02.html']

07/17/07 13:40:06

1.9.5 Checking for network health


Check for collisions, retransmitted packets, congestion in the LAN segment (that a particular server might be on).

1.10 Configuring Storage devices


1.10.1 Add a local scsi disk 1.10.2 Add a local SCSI Tape device 1.10.3 Configure FC HBAs
After installing the HBA, ensure that you install the driver(s). Usually, HP's HBAs have their drivers bundled with the HP Installation software. Or simply download the driver's software depot and install it with swinstall. 1.10.3.1 Add a SAN LUN disk Once the HBAs are installed and driver configured, you will be able to see them via ioscan. The HBA needs to be zoned, and LUNs presented from the SAN array. 1.10.3.2 Before Configuring the LUNs This is how "unconfigured" LUNs will look (just after zoning has been done), but before configuring into the system.
uapm3501p:(/) # ioscan -funC disk Class I H/W Path Driver S/W State H/W Type Description ==================================================================================== disk 0 0/0/2/1.0.16.0.0 sdisk CLAIMED DEVICE TEAC /dev/dsk/c0t0d0 /dev/rdsk/c0t0d0 disk 4 0/2/1/0/4/0.1.2.0.0.0.0 sdisk CLAIMED DEVICE HITACHI disk 5 0/2/1/0/4/0.1.2.0.0.0.1 sdisk CLAIMED DEVICE HITACHI disk 7 0/2/1/0/4/0.1.2.0.0.0.2 sdisk CLAIMED DEVICE HITACHI disk 9 0/2/1/0/4/0.1.2.0.0.0.3 sdisk CLAIMED DEVICE HITACHI disk 11 0/2/1/0/4/0.1.2.0.0.0.4 sdisk CLAIMED DEVICE HITACHI disk 13 0/2/1/0/4/0.1.2.0.0.0.5 sdisk CLAIMED DEVICE HITACHI disk 15 0/2/1/0/4/0.1.2.0.0.1.0 sdisk CLAIMED DEVICE HITACHI disk 17 0/2/1/0/4/0.1.2.0.0.2.0 sdisk CLAIMED DEVICE HITACHI disk 19 0/2/1/0/4/0.1.2.0.0.3.0 sdisk CLAIMED DEVICE HITACHI disk 22 0/2/1/0/4/0.1.2.0.0.4.0 sdisk CLAIMED DEVICE HITACHI disk 24 0/2/1/0/4/0.1.2.0.0.5.0 sdisk CLAIMED DEVICE HITACHI disk 26 0/2/1/0/4/0.1.2.0.0.6.0 sdisk CLAIMED DEVICE HITACHI disk 28 0/2/1/0/4/0.1.2.0.0.7.0 sdisk CLAIMED DEVICE HITACHI disk 30 0/2/1/0/4/0.1.2.0.0.8.0 sdisk CLAIMED DEVICE HITACHI disk 32 0/2/1/0/4/0.1.2.0.0.9.0 sdisk CLAIMED DEVICE HITACHI disk 34 0/2/1/0/4/0.1.2.0.0.10.0 sdisk CLAIMED DEVICE HITACHI disk 36 0/2/1/0/4/0.1.2.0.0.11.0 sdisk CLAIMED DEVICE HITACHI disk 38 0/2/1/0/4/0.1.2.0.0.12.0 sdisk CLAIMED DEVICE HITACHI disk 40 0/2/1/0/4/0.1.2.0.0.13.0 sdisk CLAIMED DEVICE HITACHI disk 42 0/2/1/0/4/0.1.2.0.0.14.0 sdisk CLAIMED DEVICE HITACHI disk 44 0/2/1/0/4/0.1.2.0.0.15.0 sdisk CLAIMED DEVICE HITACHI disk 3 0/2/1/0/4/0.2.13.0.0.0.0 sdisk CLAIMED DEVICE HITACHI disk 6 0/2/1/0/4/0.2.13.0.0.0.1 sdisk CLAIMED DEVICE HITACHI disk 8 0/2/1/0/4/0.2.13.0.0.0.2 sdisk CLAIMED DEVICE HITACHI disk 10 0/2/1/0/4/0.2.13.0.0.0.3 sdisk CLAIMED DEVICE HITACHI disk 12 0/2/1/0/4/0.2.13.0.0.0.4 sdisk CLAIMED DEVICE HITACHI disk 14 0/2/1/0/4/0.2.13.0.0.0.5 sdisk CLAIMED DEVICE HITACHI disk 16 0/2/1/0/4/0.2.13.0.0.1.0 sdisk CLAIMED DEVICE HITACHI disk 18 0/2/1/0/4/0.2.13.0.0.2.0 sdisk CLAIMED DEVICE HITACHI disk 20 0/2/1/0/4/0.2.13.0.0.3.0 sdisk CLAIMED DEVICE HITACHI disk 21 0/2/1/0/4/0.2.13.0.0.4.0 sdisk CLAIMED DEVICE HITACHI disk 23 0/2/1/0/4/0.2.13.0.0.5.0 sdisk CLAIMED DEVICE HITACHI disk 25 0/2/1/0/4/0.2.13.0.0.6.0 sdisk CLAIMED DEVICE HITACHI disk 27 0/2/1/0/4/0.2.13.0.0.7.0 sdisk CLAIMED DEVICE HITACHI disk 29 0/2/1/0/4/0.2.13.0.0.8.0 sdisk CLAIMED DEVICE HITACHI disk 31 0/2/1/0/4/0.2.13.0.0.9.0 sdisk CLAIMED DEVICE HITACHI disk 33 0/2/1/0/4/0.2.13.0.0.10.0 sdisk CLAIMED DEVICE HITACHI disk 35 0/2/1/0/4/0.2.13.0.0.11.0 sdisk CLAIMED DEVICE HITACHI disk 37 0/2/1/0/4/0.2.13.0.0.12.0 sdisk CLAIMED DEVICE HITACHI disk 39 0/2/1/0/4/0.2.13.0.0.13.0 sdisk CLAIMED DEVICE HITACHI disk 41 0/2/1/0/4/0.2.13.0.0.14.0 sdisk CLAIMED DEVICE HITACHI

DV-28E-N

OPEN-L OPEN-L OPEN-L OPEN-L OPEN-L OPEN-L DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY OPEN-L OPEN-L OPEN-L OPEN-L OPEN-L OPEN-L DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY DISK-SUBSY

24/37

HPUXCheatSheet
disk disk 43 1 0/2/1/0/4/0.2.13.0.0.15.0 sdisk 0/4/1/0.0.0.0.0 sdisk /dev/dsk/c1t0d0 /dev/dsk/c1t0d0s1 /dev/dsk/c1t0d0s2 /dev/dsk/c1t0d0s3 0/4/1/0.0.0.1.0 sdisk /dev/dsk/c1t1d0 /dev/dsk/c1t1d0s1 /dev/dsk/c1t1d0s2 /dev/dsk/c1t1d0s3 CLAIMED DEVICE CLAIMED DEVICE /dev/rdsk/c1t0d0 /dev/rdsk/c1t0d0s1 /dev/rdsk/c1t0d0s2 /dev/rdsk/c1t0d0s3 CLAIMED DEVICE /dev/rdsk/c1t1d0 /dev/rdsk/c1t1d0s1 /dev/rdsk/c1t1d0s2 /dev/rdsk/c1t1d0s3

07/17/07 13:40:06

HITACHI DISK-SUBSY HP DG072A9BB7

disk

HP

DG072A9BB7

1.10.3.3 Create the devlinks for these new LUNs now


uapm3501p:(/) # insf -e insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special insf: Installing special files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files files for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for for asio0 instance 2 address 0/0/1/2 sdisk instance 0 address 0/0/2/1.0.16.0.0 sctl instance 0 address 0/0/2/1.0.16.7.0 sdisk instance 4 address 0/2/1/0/4/0.1.2.0.0.0.0 sdisk instance 5 address 0/2/1/0/4/0.1.2.0.0.0.1 sdisk instance 7 address 0/2/1/0/4/0.1.2.0.0.0.2 sdisk instance 9 address 0/2/1/0/4/0.1.2.0.0.0.3 sdisk instance 11 address 0/2/1/0/4/0.1.2.0.0.0.4 sdisk instance 13 address 0/2/1/0/4/0.1.2.0.0.0.5 sdisk instance 15 address 0/2/1/0/4/0.1.2.0.0.1.0 sdisk instance 17 address 0/2/1/0/4/0.1.2.0.0.2.0 sdisk instance 19 address 0/2/1/0/4/0.1.2.0.0.3.0 sdisk instance 22 address 0/2/1/0/4/0.1.2.0.0.4.0 sdisk instance 24 address 0/2/1/0/4/0.1.2.0.0.5.0 sdisk instance 26 address 0/2/1/0/4/0.1.2.0.0.6.0 sdisk instance 28 address 0/2/1/0/4/0.1.2.0.0.7.0 sdisk instance 30 address 0/2/1/0/4/0.1.2.0.0.8.0 sdisk instance 32 address 0/2/1/0/4/0.1.2.0.0.9.0 sdisk instance 34 address 0/2/1/0/4/0.1.2.0.0.10.0 sdisk instance 36 address 0/2/1/0/4/0.1.2.0.0.11.0 sdisk instance 38 address 0/2/1/0/4/0.1.2.0.0.12.0 sdisk instance 40 address 0/2/1/0/4/0.1.2.0.0.13.0 sdisk instance 42 address 0/2/1/0/4/0.1.2.0.0.14.0 sdisk instance 44 address 0/2/1/0/4/0.1.2.0.0.15.0 sctl instance 2 address 0/2/1/0/4/0.1.2.255.0.0.0 sdisk instance 3 address 0/2/1/0/4/0.2.13.0.0.0.0 sdisk instance 6 address 0/2/1/0/4/0.2.13.0.0.0.1 sdisk instance 8 address 0/2/1/0/4/0.2.13.0.0.0.2 sdisk instance 10 address 0/2/1/0/4/0.2.13.0.0.0.3 sdisk instance 12 address 0/2/1/0/4/0.2.13.0.0.0.4 sdisk instance 14 address 0/2/1/0/4/0.2.13.0.0.0.5 sdisk instance 16 address 0/2/1/0/4/0.2.13.0.0.1.0 sdisk instance 18 address 0/2/1/0/4/0.2.13.0.0.2.0 sdisk instance 20 address 0/2/1/0/4/0.2.13.0.0.3.0 sdisk instance 21 address 0/2/1/0/4/0.2.13.0.0.4.0 sdisk instance 23 address 0/2/1/0/4/0.2.13.0.0.5.0 sdisk instance 25 address 0/2/1/0/4/0.2.13.0.0.6.0 sdisk instance 27 address 0/2/1/0/4/0.2.13.0.0.7.0 sdisk instance 29 address 0/2/1/0/4/0.2.13.0.0.8.0 sdisk instance 31 address 0/2/1/0/4/0.2.13.0.0.9.0 sdisk instance 33 address 0/2/1/0/4/0.2.13.0.0.10.0 sdisk instance 35 address 0/2/1/0/4/0.2.13.0.0.11.0 sdisk instance 37 address 0/2/1/0/4/0.2.13.0.0.12.0 sdisk instance 39 address 0/2/1/0/4/0.2.13.0.0.13.0 sdisk instance 41 address 0/2/1/0/4/0.2.13.0.0.14.0 sdisk instance 43 address 0/2/1/0/4/0.2.13.0.0.15.0 sctl instance 1 address 0/2/1/0/4/0.2.13.255.0.0.0 sdisk instance 1 address 0/4/1/0.0.0.0.0 sdisk instance 2 address 0/4/1/0.0.0.1.0 ipmi instance 0 address 250/0 asio0 instance 3 address 250/1 pseudo driver cn pseudo driver mm pseudo driver ptym pseudo driver ptys pseudo driver udp pseudo driver tcp pseudo driver rawip pseudo driver nuls pseudo driver ip pseudo driver dmem pseudo driver arp pseudo driver tlcotsod pseudo driver tlcots pseudo driver tlclts pseudo driver devkrs pseudo driver dmp

25/37

HPUXCheatSheet
insf: insf: insf: insf: insf: insf: insf: insf: insf: insf: insf: insf: insf: insf: insf: insf: insf: Installing Installing Installing Installing Installing Installing Installing Installing Installing Installing Installing Installing Installing Installing Installing Installing Installing special special special special special special special special special special special special special special special special special files files files files files files files files files files files files files files files files files for for for for for for for for for for for for for for for for for pseudo pseudo pseudo pseudo pseudo pseudo pseudo pseudo pseudo pseudo pseudo pseudo pseudo pseudo pseudo pseudo pseudo driver driver driver driver driver driver driver driver driver driver driver driver driver driver driver driver driver dev_config strlog sad stcpmap tels telm vols asyncdsk echo dlpi ptm pts klog sy kepd diag2 root

07/17/07 13:40:06

Or you could choose to run insf -e -C disk to target only the disk devices. 1.10.3.4 After the device links have been created (ie Device files) Now we can see the /dev/dsk/ctd and the /dev/rdsk/ctd paths now in the ioscan output.
uapm3501p:(/) # ioscan -funC disk Class I H/W Path Driver S/W State H/W Type Description ==================================================================================== disk 0 0/0/2/1.0.16.0.0 sdisk CLAIMED DEVICE TEAC /dev/dsk/c0t0d0 /dev/rdsk/c0t0d0 disk 4 0/2/1/0/4/0.1.2.0.0.0.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t0d0 /dev/rdsk/c2t0d0 disk 5 0/2/1/0/4/0.1.2.0.0.0.1 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t0d1 /dev/rdsk/c2t0d1 disk 7 0/2/1/0/4/0.1.2.0.0.0.2 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t0d2 /dev/rdsk/c2t0d2 disk 9 0/2/1/0/4/0.1.2.0.0.0.3 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t0d3 /dev/rdsk/c2t0d3 disk 11 0/2/1/0/4/0.1.2.0.0.0.4 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t0d4 /dev/rdsk/c2t0d4 disk 13 0/2/1/0/4/0.1.2.0.0.0.5 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t0d5 /dev/rdsk/c2t0d5 disk 15 0/2/1/0/4/0.1.2.0.0.1.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t1d0 /dev/rdsk/c2t1d0 disk 17 0/2/1/0/4/0.1.2.0.0.2.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t2d0 /dev/rdsk/c2t2d0 disk 19 0/2/1/0/4/0.1.2.0.0.3.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t3d0 /dev/rdsk/c2t3d0 disk 22 0/2/1/0/4/0.1.2.0.0.4.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t4d0 /dev/rdsk/c2t4d0 disk 24 0/2/1/0/4/0.1.2.0.0.5.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t5d0 /dev/rdsk/c2t5d0 disk 26 0/2/1/0/4/0.1.2.0.0.6.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t6d0 /dev/rdsk/c2t6d0 disk 28 0/2/1/0/4/0.1.2.0.0.7.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t7d0 /dev/rdsk/c2t7d0 disk 30 0/2/1/0/4/0.1.2.0.0.8.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t8d0 /dev/rdsk/c2t8d0 disk 32 0/2/1/0/4/0.1.2.0.0.9.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t9d0 /dev/rdsk/c2t9d0 disk 34 0/2/1/0/4/0.1.2.0.0.10.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t10d0 /dev/rdsk/c2t10d0 disk 36 0/2/1/0/4/0.1.2.0.0.11.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t11d0 /dev/rdsk/c2t11d0 disk 38 0/2/1/0/4/0.1.2.0.0.12.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t12d0 /dev/rdsk/c2t12d0 disk 40 0/2/1/0/4/0.1.2.0.0.13.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t13d0 /dev/rdsk/c2t13d0 disk 42 0/2/1/0/4/0.1.2.0.0.14.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t14d0 /dev/rdsk/c2t14d0 disk 44 0/2/1/0/4/0.1.2.0.0.15.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c2t15d0 /dev/rdsk/c2t15d0 disk 3 0/2/1/0/4/0.2.13.0.0.0.0 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c4t0d0 /dev/rdsk/c4t0d0 disk 6 0/2/1/0/4/0.2.13.0.0.0.1 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c4t0d1 /dev/rdsk/c4t0d1 disk 8 0/2/1/0/4/0.2.13.0.0.0.2 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c4t0d2 /dev/rdsk/c4t0d2 disk 10 0/2/1/0/4/0.2.13.0.0.0.3 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c4t0d3 /dev/rdsk/c4t0d3 disk 12 0/2/1/0/4/0.2.13.0.0.0.4 sdisk CLAIMED DEVICE HITACHI /dev/dsk/c4t0d4 /dev/rdsk/c4t0d4

DV-28E-N OPEN-L OPEN-L OPEN-L OPEN-L OPEN-L OPEN-L

DISK-SUBSY

DISK-SUBSY

DISK-SUBSY

DISK-SUBSY

DISK-SUBSY

DISK-SUBSY

DISK-SUBSY

DISK-SUBSY

DISK-SUBSY

DISK-SUBSY

DISK-SUBSY

DISK-SUBSY

DISK-SUBSY

DISK-SUBSY

DISK-SUBSY OPEN-L OPEN-L OPEN-L OPEN-L OPEN-L

26/37

HPUXCheatSheet
disk disk disk disk disk disk disk disk disk disk disk disk disk disk disk disk disk 14 16 18 20 21 23 25 27 29 31 33 35 37 39 41 43 1 0/2/1/0/4/0.2.13.0.0.0.5 sdisk /dev/dsk/c4t0d5 0/2/1/0/4/0.2.13.0.0.1.0 sdisk /dev/dsk/c4t1d0 0/2/1/0/4/0.2.13.0.0.2.0 sdisk /dev/dsk/c4t2d0 0/2/1/0/4/0.2.13.0.0.3.0 sdisk /dev/dsk/c4t3d0 0/2/1/0/4/0.2.13.0.0.4.0 sdisk /dev/dsk/c4t4d0 0/2/1/0/4/0.2.13.0.0.5.0 sdisk /dev/dsk/c4t5d0 0/2/1/0/4/0.2.13.0.0.6.0 sdisk /dev/dsk/c4t6d0 0/2/1/0/4/0.2.13.0.0.7.0 sdisk /dev/dsk/c4t7d0 0/2/1/0/4/0.2.13.0.0.8.0 sdisk /dev/dsk/c4t8d0 0/2/1/0/4/0.2.13.0.0.9.0 sdisk /dev/dsk/c4t9d0 0/2/1/0/4/0.2.13.0.0.10.0 sdisk /dev/dsk/c4t10d0 0/2/1/0/4/0.2.13.0.0.11.0 sdisk /dev/dsk/c4t11d0 0/2/1/0/4/0.2.13.0.0.12.0 sdisk /dev/dsk/c4t12d0 0/2/1/0/4/0.2.13.0.0.13.0 sdisk /dev/dsk/c4t13d0 0/2/1/0/4/0.2.13.0.0.14.0 sdisk /dev/dsk/c4t14d0 0/2/1/0/4/0.2.13.0.0.15.0 sdisk /dev/dsk/c4t15d0 0/4/1/0.0.0.0.0 sdisk /dev/dsk/c1t0d0 /dev/dsk/c1t0d0s1 /dev/dsk/c1t0d0s2 /dev/dsk/c1t0d0s3 0/4/1/0.0.0.1.0 sdisk /dev/dsk/c1t1d0 /dev/dsk/c1t1d0s1 /dev/dsk/c1t1d0s2 /dev/dsk/c1t1d0s3 CLAIMED /dev/rdsk/c4t0d5 CLAIMED /dev/rdsk/c4t1d0 CLAIMED /dev/rdsk/c4t2d0 CLAIMED /dev/rdsk/c4t3d0 CLAIMED /dev/rdsk/c4t4d0 CLAIMED /dev/rdsk/c4t5d0 CLAIMED /dev/rdsk/c4t6d0 CLAIMED /dev/rdsk/c4t7d0 CLAIMED /dev/rdsk/c4t8d0 CLAIMED /dev/rdsk/c4t9d0 CLAIMED /dev/rdsk/c4t10d0 CLAIMED /dev/rdsk/c4t11d0 CLAIMED /dev/rdsk/c4t12d0 CLAIMED /dev/rdsk/c4t13d0 CLAIMED /dev/rdsk/c4t14d0 CLAIMED /dev/rdsk/c4t15d0 CLAIMED /dev/rdsk/c1t0d0 /dev/rdsk/c1t0d0s1 /dev/rdsk/c1t0d0s2 /dev/rdsk/c1t0d0s3 CLAIMED /dev/rdsk/c1t1d0 /dev/rdsk/c1t1d0s1 /dev/rdsk/c1t1d0s2 /dev/rdsk/c1t1d0s3 DEVICE DEVICE DEVICE DEVICE DEVICE DEVICE DEVICE DEVICE DEVICE DEVICE DEVICE DEVICE DEVICE DEVICE DEVICE DEVICE DEVICE

07/17/07 13:40:06
HITACHI OPEN-L

HITACHI DISK-SUBSY

HITACHI DISK-SUBSY

HITACHI DISK-SUBSY

HITACHI DISK-SUBSY

HITACHI DISK-SUBSY

HITACHI DISK-SUBSY

HITACHI DISK-SUBSY

HITACHI DISK-SUBSY

HITACHI DISK-SUBSY

HITACHI DISK-SUBSY

HITACHI DISK-SUBSY

HITACHI DISK-SUBSY

HITACHI DISK-SUBSY

HITACHI DISK-SUBSY

HITACHI DISK-SUBSY HP

DG072A9BB7

disk

DEVICE

HP

DG072A9BB7

1.10.3.5 Verify that the LUNs are usable


uapm3501p:(/) # diskinfo /dev/rdsk/c2t0d0 SCSI describe of /dev/rdsk/c2t0d0: vendor: HITACHI product id: OPEN-L type: direct access size: 35596080 Kbytes bytes per sector: 512 uapm3501p:(/) #

1.10.3.6 Add the LUNs to Veritas Volume Manager


uapm3501p:(/) # vxdctl enable uapm3501p:(/) # vxdisk -o alldgs list DEVICE TYPE DISK c1t0d0s2 auto:hpdisk rootdisk02 c1t1d0s2 auto:hpdisk rootdisk01 c2t0d0 auto:none c2t0d1 auto:none c2t0d2 auto:none c2t0d3 auto:none c2t0d4 auto:none c2t0d5 auto:none c4t0d0 auto:none c4t0d1 auto:none c4t0d2 auto:none c4t0d3 auto:none c4t0d4 auto:none c4t0d5 auto:none uapm3501p:(/) #

GROUP rootdg rootdg -

STATUS online online online online online online online online online online online online online online

invalid invalid invalid invalid invalid invalid invalid invalid invalid invalid invalid invalid

1.10.3.7 Verify the disk information


uapm3501p:(/) # diskinfo /dev/dsk/c4t0d5 diskinfo: Character device required uapm3501p:(/) # diskinfo /dev/rdsk/c4t0d5

27/37

HPUXCheatSheet
SCSI describe of /dev/rdsk/c4t0d5: vendor: HITACHI product id: OPEN-L type: direct access size: 35596080 Kbytes bytes per sector: 512

07/17/07 13:40:06

1.10.3.8 Check the disk details using {{{vxdisk list}}}


uapm3501p:(/) # vxdisk list c4t0d5 Device: c4t0d5 devicetag: c4t0d5 type: auto info: format=none flags: online ready private autoconfig invalid pubpaths: block=/dev/vx/dmp/c4t0d5 char=/dev/vx/rdmp/c4t0d5 Multipathing information: numpaths: 1 c4t0d5 state=enabled uapm3501p:(/) # vxdisk list c2t0d0 Device: c2t0d0 devicetag: c2t0d0 type: auto info: format=none flags: online ready private autoconfig invalid pubpaths: block=/dev/vx/dmp/c2t0d0 char=/dev/vx/rdmp/c2t0d0 Multipathing information: numpaths: 1 c2t0d0 state=enabled

1.10.3.9 Check whether Veritas Dynamic Multipathing has been enabled


1.10.3.9.1 List by Controller number uapm3501p:(/) # vxdmpadm listctlr all CTLR-NAME ENCLR-TYPE STATE ENCLR-NAME ===================================================== c1 Disk ENABLED Disk c4 Disk ENABLED Disk c2 Disk ENABLED Disk

uapm3501p:(/) # vxdmpadm getctlr all LNAME PNAME =============== c1 0/4/1/0.0.0 c4 0/2/1/0/4/0.2.13.0.0 c2 0/2/1/0/4/0.1.2.0.0

1.10.3.9.2 Check by Enclosure uapm3501p:(/) # vxdmpadm listenclosure all ENCLR_NAME ENCLR_TYPE ENCLR_SNO STATUS ARRAY_TYPE ============================================================================ Disk Disk DISKS CONNECTED Disk OTHER_DISKS OTHER_DISKS OTHER_DISKS DISCONNECTED 1.10.3.9.3 Check subpaths by Controller number uapm3501p:(/) # vxdmpadm getsubpaths ctlr=c4 NAME STATE[A] PATH-TYPE[M] DMPNODENAME ENCLR-TYPE ENCLR-NAME ATTRS ================================================================================ c4t0d0 ENABLED(A) c4t0d0 Disk Disk c4t0d1 ENABLED(A) c4t0d1 Disk Disk c4t0d2 ENABLED(A) c4t0d2 Disk Disk c4t0d3 ENABLED(A) c4t0d3 Disk Disk c4t0d4 ENABLED(A) c4t0d4 Disk Disk c4t0d5 ENABLED(A) c4t0d5 Disk Disk uapm3501p:(/) # vxdmpadm getsubpaths ctlr=c2 NAME STATE[A] PATH-TYPE[M] DMPNODENAME ENCLR-TYPE ENCLR-NAME ATTRS ================================================================================ c2t0d0 ENABLED(A) c2t0d0 Disk Disk c2t0d1 ENABLED(A) c2t0d1 Disk Disk c2t0d2 ENABLED(A) c2t0d2 Disk Disk c2t0d3 ENABLED(A) c2t0d3 Disk Disk c2t0d4 ENABLED(A) c2t0d4 Disk Disk c2t0d5 ENABLED(A) c2t0d5 Disk Disk -

28/37

HPUXCheatSheet
1.10.3.9.4 Verifying Lun grouping/paths uapm3501p:(/) # vxdmpadm getlungroup dmpnodename=c2t0d0 NAME STATE ENCLR-TYPE PATHS ENBL DSBL ENCLR-NAME ========================================================================= c2t0d0 ENABLED Disk 1 1 0 Disk uapm3501p:(/) #

07/17/07 13:40:06

Very strange...the LUNs should show both paths (unless they are not dual-pathed across c2 and c4 respectively...
1.10.3.9.5 Check whether DMP is enabled

Vxlicrep lies, apparently...


uapm3501p:(/var/adm) # vxlicrep -e|grep -i vxvm VxVM#VERITAS Volume Manager = Enabled HP_VXVM_FULL = Disabled VxVM = Enabled VxVM Base = Disabled

This is the "more" authoritative report --uapm3501p:(/var/adm) # vxdctl license All features are available: Mirroring Root Mirroring Concatenation Disk-spanning Striping RAID-5 VxSmartSync Clustering-lite DMP (multipath enabled) CDS Dynamic LUN Expansion Hardware assisted copy

If you see "DMP (multipath enabled" as above, DMP is enabled, but in an Active/Passive mode. With the "Full" license (from vxlicrep output), DMP is active/active (in a load-balancing type mechanism). NOTE -- The Trick was in installing the Hitachi 99xx Array Support Library file(s) from Veritas' website. Once that was installed, and after a reboot -uapm3501p:(/) # vxdmpadm getctlr all LNAME PNAME =============== c1 0/4/1/0.0.0 c6 0/6/1/0/4/0.1.2.0.0 c2 0/2/1/0/4/0.1.2.0.0 c8 0/6/1/0/4/0.2.2.0.0 c4 0/2/1/0/4/0.2.13.0.0 uapm3501p:(/) # uapm3501p:(/) # vxdisk list c2t0d0 Device: c2t0d0 devicetag: c2t0d0 type: auto info: format=none flags: online ready private autoconfig invalid pubpaths: block=/dev/vx/dmp/c2t0d0 char=/dev/vx/rdmp/c2t0d0 Multipathing information: numpaths: 2 c2t0d0 state=enabled c6t0d0 state=enabled uapm3501p:(/) # uapm3501p:(/) # vxdmpadm getsubpaths dmpnodename=c2t0d0 NAME STATE[A] PATH-TYPE[M] CTLR-NAME ENCLR-TYPE ENCLR-NAME ATTRS ================================================================================ c2t0d0 ENABLED(A) c2 HDS9980V HDS9980V1 c6t0d0 ENABLED(A) c6 HDS9980V HDS9980V1 uapm3501p:(/) #

29/37

HPUXCheatSheet 1.10.3.10 remove a SAN LUN Disk 1.10.3.11 Add a SAN Tape device

07/17/07 13:40:06

After connecting the Tape SAN fiber and zoning the Tape devices with correct HBA (and all the SAN blah-blah), run insf -e. After that, run
uapm3501p:(/) # ioscan -funC tape uapm3501p:(/) #

That doesn't return anything! What's the problem? We see that ioscan does't recognize the tape devices (in our case Ultrium-2 ie LTO-2) as valid devices (or no associated drivers in kernel).
uapm3501p:(/dev) # ioscan 2>&1|grep -i ultrium|more 0/2/1/0/4/1.19.6.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.7.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.8.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.9.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.10.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.11.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.12.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.13.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.14.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.15.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.16.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.17.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.18.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.19.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.20.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.21.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.22.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.19.23.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.20.2.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.20.3.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.20.8.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.20.9.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.20.10.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.20.11.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.20.16.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.20.17.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.20.18.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.20.19.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.20.24.255.0.0.0 Ultrium 2-SCSI 0/2/1/0/4/1.20.25.255.0.0.0 Ultrium 2-SCSI uapm3501p:(/dev) # unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown unknown HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP HP

30/37

HPUXCheatSheet So, as almighty HP-UX Gods dictate, patch the darn kernel and *ribbit!*!!
uapm3501p:(/dev) # kcmodule -v stape Module stape [45EF2D4C] Description SCSI Tape Driver State unused State at Next Boot unused Capable static unused Depends On module sctl:0.0.0 interface HPUX_11_23:1.0 uapm3501p:(/dev) # kcmodule stape=best NOTE: The configuration being loaded contains the following change(s) that cannot be applied immediately and which will be held for the next boot: -- The configuration is supposed to include a module 'stape' which is not available without a kernel rebuild. WARNING: The automatic 'backup' configuration currently contains the configuration that was in use before the last reboot of this system. ==> Do you wish to update it to contain the current configuration before making the requested change? y * The automatic 'backup' configuration has been updated. * Building a new kernel for configuration 'nextboot'... * Adding version information to new kernel... * The requested changes have been saved, and will take effect at next boot. Module State Cause stape (now) unused (next boot) static explicit uapm3501p:(/dev) # kcmodule -v stape Module stape [45EF2D4C] Description SCSI Tape Driver State unused State at Next Boot static (as requested) Capable static unused Depends On module sctl:0.0.0 interface HPUX_11_23:1.0 uapm3501p:(/dev) #

07/17/07 13:40:06

And indeed, after a reboot, we see the tapes now -uapm3501p:(/) # ioscan -funC tape Class I H/W Path Driver S/W State H/W Type Description =========================================================================== tape 11 0/2/1/0/4/1.19.6.255.0.0.0 stape CLAIMED DEVICE /dev/rmt/11m /dev/rmt/c10t0d0BEST /dev/rmt/11mb /dev/rmt/c10t0d0BESTb /dev/rmt/11mn /dev/rmt/c10t0d0BESTn /dev/rmt/11mnb /dev/rmt/c10t0d0BESTnb tape 12 0/2/1/0/4/1.19.7.255.0.0.0 stape CLAIMED DEVICE /dev/rmt/12m /dev/rmt/c11t0d0BEST /dev/rmt/12mb /dev/rmt/c11t0d0BESTb /dev/rmt/12mn /dev/rmt/c11t0d0BESTn /dev/rmt/12mnb /dev/rmt/c11t0d0BESTnb tape 13 0/2/1/0/4/1.19.8.255.0.0.0 stape CLAIMED DEVICE /dev/rmt/13m /dev/rmt/c12t0d0BEST /dev/rmt/13mb /dev/rmt/c12t0d0BESTb /dev/rmt/13mn /dev/rmt/c12t0d0BESTn /dev/rmt/13mnb /dev/rmt/c12t0d0BESTnb tape 14 0/2/1/0/4/1.19.9.255.0.0.0 stape CLAIMED DEVICE /dev/rmt/14m /dev/rmt/c13t0d0BEST /dev/rmt/14mb /dev/rmt/c13t0d0BESTb /dev/rmt/14mn /dev/rmt/c13t0d0BESTn /dev/rmt/14mnb /dev/rmt/c13t0d0BESTnb tape 16 0/2/1/0/4/1.19.10.255.0.0.0 stape CLAIMED DEVICE /dev/rmt/16m /dev/rmt/c14t0d0BEST /dev/rmt/16mb /dev/rmt/c14t0d0BESTb /dev/rmt/16mn /dev/rmt/c14t0d0BESTn /dev/rmt/16mnb /dev/rmt/c14t0d0BESTnb tape 15 0/2/1/0/4/1.19.11.255.0.0.0 stape CLAIMED DEVICE /dev/rmt/15m /dev/rmt/c15t0d0BEST /dev/rmt/15mb /dev/rmt/c15t0d0BESTb /dev/rmt/15mn /dev/rmt/c15t0d0BESTn /dev/rmt/15mnb /dev/rmt/c15t0d0BESTnb tape 19 0/2/1/0/4/1.19.12.255.0.0.0 stape CLAIMED DEVICE /dev/rmt/19m /dev/rmt/c16t0d0BEST /dev/rmt/19mb /dev/rmt/c16t0d0BESTb /dev/rmt/19mn /dev/rmt/c16t0d0BESTn /dev/rmt/19mnb /dev/rmt/c16t0d0BESTnb

HP

Ultrium 2-SCSI

HP

Ultrium 2-SCSI

HP

Ultrium 2-SCSI

HP

Ultrium 2-SCSI

HP

Ultrium 2-SCSI

HP

Ultrium 2-SCSI

HP

Ultrium 2-SCSI

31/37

HPUXCheatSheet
tape 17 0/2/1/0/4/1.19.13.255.0.0.0 stape /dev/rmt/17m /dev/rmt/17mb /dev/rmt/17mn /dev/rmt/17mnb 0/2/1/0/4/1.19.14.255.0.0.0 stape /dev/rmt/18m /dev/rmt/18mb /dev/rmt/18mn /dev/rmt/18mnb 0/2/1/0/4/1.19.15.255.0.0.0 stape /dev/rmt/20m /dev/rmt/20mb /dev/rmt/20mn /dev/rmt/20mnb 0/2/1/0/4/1.19.16.255.0.0.0 stape /dev/rmt/22m /dev/rmt/22mb /dev/rmt/22mn /dev/rmt/22mnb 0/2/1/0/4/1.19.17.255.0.0.0 stape /dev/rmt/23m /dev/rmt/23mb /dev/rmt/23mn /dev/rmt/23mnb 0/2/1/0/4/1.19.18.255.0.0.0 stape /dev/rmt/24m /dev/rmt/24mb /dev/rmt/24mn /dev/rmt/24mnb 0/2/1/0/4/1.19.19.255.0.0.0 stape /dev/rmt/25m /dev/rmt/25mb /dev/rmt/25mn /dev/rmt/25mnb 0/2/1/0/4/1.19.20.255.0.0.0 stape /dev/rmt/29m /dev/rmt/29mb /dev/rmt/29mn /dev/rmt/29mnb 0/2/1/0/4/1.19.21.255.0.0.0 stape /dev/rmt/21m /dev/rmt/21mb /dev/rmt/21mn /dev/rmt/21mnb 0/2/1/0/4/1.19.22.255.0.0.0 stape /dev/rmt/27m /dev/rmt/27mb /dev/rmt/27mn /dev/rmt/27mnb 0/2/1/0/4/1.19.23.255.0.0.0 stape /dev/rmt/28m /dev/rmt/28mb /dev/rmt/28mn /dev/rmt/28mnb 0/2/1/0/4/1.20.2.255.0.0.0 stape /dev/rmt/3m /dev/rmt/3mb /dev/rmt/3mn /dev/rmt/3mnb 0/2/1/0/4/1.20.3.255.0.0.0 stape /dev/rmt/26m /dev/rmt/26mb /dev/rmt/26mn /dev/rmt/26mnb 0/2/1/0/4/1.20.8.255.0.0.0 stape /dev/rmt/0m /dev/rmt/0mb /dev/rmt/0mn /dev/rmt/0mnb 0/2/1/0/4/1.20.9.255.0.0.0 stape /dev/rmt/1m /dev/rmt/1mb /dev/rmt/1mn /dev/rmt/1mnb 0/2/1/0/4/1.20.10.255.0.0.0 stape /dev/rmt/2m /dev/rmt/2mb /dev/rmt/2mn /dev/rmt/2mnb 0/2/1/0/4/1.20.11.255.0.0.0 stape /dev/rmt/4m CLAIMED DEVICE /dev/rmt/c17t0d0BEST /dev/rmt/c17t0d0BESTb /dev/rmt/c17t0d0BESTn /dev/rmt/c17t0d0BESTnb CLAIMED DEVICE /dev/rmt/c18t0d0BEST /dev/rmt/c18t0d0BESTb /dev/rmt/c18t0d0BESTn /dev/rmt/c18t0d0BESTnb CLAIMED DEVICE /dev/rmt/c19t0d0BEST /dev/rmt/c19t0d0BESTb /dev/rmt/c19t0d0BESTn /dev/rmt/c19t0d0BESTnb CLAIMED DEVICE /dev/rmt/c20t0d0BEST /dev/rmt/c20t0d0BESTb /dev/rmt/c20t0d0BESTn /dev/rmt/c20t0d0BESTnb CLAIMED DEVICE /dev/rmt/c21t0d0BEST /dev/rmt/c21t0d0BESTb /dev/rmt/c21t0d0BESTn /dev/rmt/c21t0d0BESTnb CLAIMED DEVICE /dev/rmt/c22t0d0BEST /dev/rmt/c22t0d0BESTb /dev/rmt/c22t0d0BESTn /dev/rmt/c22t0d0BESTnb CLAIMED DEVICE /dev/rmt/c23t0d0BEST /dev/rmt/c23t0d0BESTb /dev/rmt/c23t0d0BESTn /dev/rmt/c23t0d0BESTnb CLAIMED DEVICE /dev/rmt/c24t0d0BEST /dev/rmt/c24t0d0BESTb /dev/rmt/c24t0d0BESTn /dev/rmt/c24t0d0BESTnb CLAIMED DEVICE /dev/rmt/c25t0d0BEST /dev/rmt/c25t0d0BESTb /dev/rmt/c25t0d0BESTn /dev/rmt/c25t0d0BESTnb CLAIMED DEVICE /dev/rmt/c26t0d0BEST /dev/rmt/c26t0d0BESTb /dev/rmt/c26t0d0BESTn /dev/rmt/c26t0d0BESTnb CLAIMED DEVICE /dev/rmt/c27t0d0BEST /dev/rmt/c27t0d0BESTb /dev/rmt/c27t0d0BESTn /dev/rmt/c27t0d0BESTnb CLAIMED DEVICE /dev/rmt/c28t0d0BEST /dev/rmt/c28t0d0BESTb /dev/rmt/c28t0d0BESTn /dev/rmt/c28t0d0BESTnb CLAIMED DEVICE /dev/rmt/c29t0d0BEST /dev/rmt/c29t0d0BESTb /dev/rmt/c29t0d0BESTn /dev/rmt/c29t0d0BESTnb CLAIMED DEVICE /dev/rmt/c30t0d0BEST /dev/rmt/c30t0d0BESTb /dev/rmt/c30t0d0BESTn /dev/rmt/c30t0d0BESTnb CLAIMED DEVICE /dev/rmt/c31t0d0BEST /dev/rmt/c31t0d0BESTb /dev/rmt/c31t0d0BESTn /dev/rmt/c31t0d0BESTnb CLAIMED DEVICE /dev/rmt/c32t0d0BEST /dev/rmt/c32t0d0BESTb /dev/rmt/c32t0d0BESTn /dev/rmt/c32t0d0BESTnb CLAIMED DEVICE /dev/rmt/c33t0d0BEST

07/17/07 13:40:06
HP Ultrium 2-SCSI

tape

18

HP

Ultrium 2-SCSI

tape

20

HP

Ultrium 2-SCSI

tape

22

HP

Ultrium 2-SCSI

tape

23

HP

Ultrium 2-SCSI

tape

24

HP

Ultrium 2-SCSI

tape

25

HP

Ultrium 2-SCSI

tape

29

HP

Ultrium 2-SCSI

tape

21

HP

Ultrium 2-SCSI

tape

27

HP

Ultrium 2-SCSI

tape

28

HP

Ultrium 2-SCSI

tape

HP

Ultrium 2-SCSI

tape

26

HP

Ultrium 2-SCSI

tape

HP

Ultrium 2-SCSI

tape

HP

Ultrium 2-SCSI

tape

HP

Ultrium 2-SCSI

tape

HP

Ultrium 2-SCSI

32/37

HPUXCheatSheet

07/17/07 13:40:06

/dev/rmt/4mb /dev/rmt/c33t0d0BESTb /dev/rmt/4mn /dev/rmt/c33t0d0BESTn /dev/rmt/4mnb /dev/rmt/c33t0d0BESTnb tape 5 0/2/1/0/4/1.20.16.255.0.0.0 stape CLAIMED DEVICE HP Ultrium 2-SCSI /dev/rmt/5m /dev/rmt/c34t0d0BEST /dev/rmt/5mb /dev/rmt/c34t0d0BESTb /dev/rmt/5mn /dev/rmt/c34t0d0BESTn /dev/rmt/5mnb /dev/rmt/c34t0d0BESTnb tape 6 0/2/1/0/4/1.20.17.255.0.0.0 stape CLAIMED DEVICE HP Ultrium 2-SCSI /dev/rmt/6m /dev/rmt/c35t0d0BEST /dev/rmt/6mb /dev/rmt/c35t0d0BESTb /dev/rmt/6mn /dev/rmt/c35t0d0BESTn /dev/rmt/6mnb /dev/rmt/c35t0d0BESTnb tape 7 0/2/1/0/4/1.20.18.255.0.0.0 stape CLAIMED DEVICE HP Ultrium 2-SCSI /dev/rmt/7m /dev/rmt/c36t0d0BEST /dev/rmt/7mb /dev/rmt/c36t0d0BESTb /dev/rmt/7mn /dev/rmt/c36t0d0BESTn /dev/rmt/7mnb /dev/rmt/c36t0d0BESTnb tape 8 0/2/1/0/4/1.20.19.255.0.0.0 stape CLAIMED DEVICE HP Ultrium 2-SCSI /dev/rmt/8m /dev/rmt/c37t0d0BEST /dev/rmt/8mb /dev/rmt/c37t0d0BESTb /dev/rmt/8mn /dev/rmt/c37t0d0BESTn /dev/rmt/8mnb /dev/rmt/c37t0d0BESTnb tape 9 0/2/1/0/4/1.20.24.255.0.0.0 stape CLAIMED DEVICE HP Ultrium 2-SCSI /dev/rmt/9m /dev/rmt/c38t0d0BEST /dev/rmt/9mb /dev/rmt/c38t0d0BESTb /dev/rmt/9mn /dev/rmt/c38t0d0BESTn /dev/rmt/9mnb /dev/rmt/c38t0d0BESTnb tape 10 0/2/1/0/4/1.20.25.255.0.0.0 stape CLAIMED DEVICE HP Ultrium 2-SCSI /dev/rmt/10m /dev/rmt/c39t0d0BEST /dev/rmt/10mb /dev/rmt/c39t0d0BESTb /dev/rmt/10mn /dev/rmt/c39t0d0BESTn /dev/rmt/10mnb /dev/rmt/c39t0d0BESTnb uapm3501p:(/) # ioscan -fnk|grep -i hp fc 0 0/2/1/0/4/0 fcd CLAIMED INTERFACE HP AB465-60001 PCI/PCI-X Fibr fc 1 0/2/1/0/4/1 fcd CLAIMED INTERFACE HP AB465-60001 PCI/PCI-X Fibr tape 11 0/2/1/0/4/1.19.6.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 12 0/2/1/0/4/1.19.7.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 13 0/2/1/0/4/1.19.8.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 14 0/2/1/0/4/1.19.9.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 16 0/2/1/0/4/1.19.10.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 15 0/2/1/0/4/1.19.11.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 19 0/2/1/0/4/1.19.12.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 17 0/2/1/0/4/1.19.13.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 18 0/2/1/0/4/1.19.14.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 20 0/2/1/0/4/1.19.15.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 22 0/2/1/0/4/1.19.16.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 23 0/2/1/0/4/1.19.17.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 24 0/2/1/0/4/1.19.18.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 25 0/2/1/0/4/1.19.19.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 29 0/2/1/0/4/1.19.20.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 21 0/2/1/0/4/1.19.21.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 27 0/2/1/0/4/1.19.22.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 28 0/2/1/0/4/1.19.23.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 3 0/2/1/0/4/1.20.2.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 26 0/2/1/0/4/1.20.3.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 0 0/2/1/0/4/1.20.8.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 1 0/2/1/0/4/1.20.9.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 2 0/2/1/0/4/1.20.10.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 4 0/2/1/0/4/1.20.11.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 5 0/2/1/0/4/1.20.16.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 6 0/2/1/0/4/1.20.17.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 7 0/2/1/0/4/1.20.18.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 8 0/2/1/0/4/1.20.19.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 9 0/2/1/0/4/1.20.24.255.0.0.0 stape CLAIMED DEVICE HP Ultrium tape 10 0/2/1/0/4/1.20.25.255.0.0.0 stape CLAIMED DEVICE HP Ultrium lan 2 0/2/1/0/6/0 igelan CLAIMED INTERFACE HP AB465-60001 PCI/PCI-X 1000 lan 3 0/2/1/0/6/1 igelan CLAIMED INTERFACE HP AB465-60001 PCI/PCI-X 1000 escsi_ctlr 0 0/4/1/0 sasd CLAIMED INTERFACE HP PCI/PCI-X SAS MPT Adapter disk 1 0/4/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP DG072A9B disk 2 0/4/1/0.0.0.1.0 sdisk CLAIMED DEVICE HP DG072A9B lan 0 0/4/2/0 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000 lan 1 0/4/2/1 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000 fc 2 0/6/1/0/4/0 fcd CLAIMED INTERFACE HP AB465-60001 PCI/PCI-X Fibr fc 3 0/6/1/0/4/1 fcd CLAIMED INTERFACE HP AB465-60001 PCI/PCI-X Fibr lan 4 0/6/1/0/6/0 igelan CLAIMED INTERFACE HP AB465-60001 PCI/PCI-X 1000 lan 5 0/6/1/0/6/1 igelan CLAIMED INTERFACE HP AB465-60001 PCI/PCI-X 1000 uapm3501p:(/) #

33/37

HPUXCheatSheet 1.10.3.12 Remove a SAN Tape device

07/17/07 13:40:06

1.11 Install software


1.11.1 Set up a depot
# mkdir /depot # cd /depot # mount -o ro,cdcase,rr /dev/dsk/c0t0d0 /cdrom ---- /!\ '''Edit conflict - other version:''' ---# swcopy -s /cdrom \ > -x enforce_dependencies=false \ '*' @ /depot ======= 03/14/07 10:25:07 CDT BEGIN swcopy SESSION (non-interactive) (jobid=uapm3501-0087) * Session started for user "root@uapm3501". * Beginning Selection * "uapm3501:/depot": This target does not exist and will be created. * "uapm3501:/cdrom": Cannot open the logfile on this target or source. Possibly the media is read-only or there is a permission problem. Check the daemon logfile and "/var/tmp//swagent.log" on this host for more information. <truncated for brevity> NOTE: More information may be found in the agent logfile using the command "swjob -a log uapm3501-0087 @ uapm3501:/depot". ======= 03/14/07 10:38:49 CDT END swcopy SESSION (non-interactive) (jobid=uapm3501-0087) ---- /!\ '''Edit conflict - your version:''' ---# swcopy -s /cdrom \ > -x enforce_dependencies=false \ '*' @ /depot ======= 03/14/07 10:25:07 CDT BEGIN swcopy SESSION (non-interactive) (jobid=uapm3501-0087) * Session started for user "root@uapm3501". * Beginning Selection * "uapm3501:/depot": This target does not exist and will be created. * "uapm3501:/cdrom": Cannot open the logfile on this target or source. Possibly the media is read-only or there is a permission problem. Check the daemon logfile and "/var/tmp//swagent.log" on this host for more information. <truncated for brevity> NOTE: More information may be found in the agent logfile using the command "swjob -a log uapm3501-0087 @ uapm3501:/depot". ======= 03/14/07 10:38:49 CDT END swcopy SESSION (non-interactive) (jobid=uapm3501-0087) ---- /!\ '''End of edit conflict''' ----

1.11.2 Register the depot


# swreg -l depot @ /depot ======= 03/14/07 10:43:41 CDT BEGIN swreg SESSION (non-interactive) * Session started for user "root@uapm3501". * Beginning Selection * Targets: * Selection succeeded.

/depot

=======

03/14/07 10:43:41 CDT

END swreg SESSION (non-interactive)

1.12 install patches


1.12.1 Identifying required patches
Use this script to create a snapshot of patches installed on your system. It will create an XML file called inventory.xml. attachmen:swainv You can run it as a non-root user. Once it's done, upload it by following the steps in the webpage here --

34/37

HPUXCheatSheet https://www1.itrc.hp.com/service/patch/assessSystemsPage.do?BC=main| NOTE: You will need a valid ITRC login in order to do that.

07/17/07 13:40:06

Download the patches you want from itrc.hp.com. Patches can be downloaded individually or as a tarball bundle.

1.12.2 set up a patch depot


Copy the patch bundle over to your target host and run the following commands:
uapm3501p:(/tmp/patches) # gzcat ../hpux*tgz|tar xvf x patch_manifest, 796 bytes, 2 tape blocks x README_hp-ux, 1779 bytes, 4 tape blocks x create_depot_hp-ux_11, 5776 bytes, 12 tape blocks x PHCO_31607, 95362 bytes, 187 tape blocks x PHCO_31618, 155793 bytes, 305 tape blocks x PHCO_31621, 96845 bytes, 190 tape blocks x PHCO_32146, 362411 bytes, 708 tape blocks x PHCO_33487, 361917 bytes, 707 tape blocks x PHCO_34208, 6320262 bytes, 12345 tape blocks x PHCO_34764, 635632 bytes, 1242 tape blocks x PHKL_31500, 103143254 bytes, 201452 tape blocks x PHSS_32674, 1803314 bytes, 3523 tape blocks x PHCO_31616, 139384 bytes, 273 tape blocks x PHCO_34215, 1176783 bytes, 2299 tape blocks x PHCO_34740, 1320590 bytes, 2580 tape blocks x PHKL_34094, 1960441 bytes, 3829 tape blocks uapm3501p:(/tmp/patches) #

Run the create_depot_hp-ux script to set up a depot.

1.12.3 Register the depot


# swreg -l depot @ /depot ======= 03/14/07 10:43:41 CDT BEGIN swreg SESSION (non-interactive) * Session started for user "root@uapm3501". * Beginning Selection * Targets: * Selection succeeded.

/depot

=======

03/14/07 10:43:41 CDT

END swreg SESSION (non-interactive)

1.12.4 Setting system and nodename


# uname -a uapm3501 unknown B.11.23 U ia64 1792805807 unlimited-user license # setuname -n uapm3501 # uname -a uapm3501 uapm3501 B.11.23 U ia64 1792805807 unlimited-user license #

NOTE: DO NOT use the setuname program with the "-s" switch to set the "system" name to the hostname. The "-s" is the OS name (which in all cases has to be HP-UX). Use it to only set the "nodename". From personal experience it's been seen that setting the OS name to something other than HP-UX will cause some baffling and weird errors on the system.

1.12.5 Enabling long hostnames


Install the NodeHostNameXpnd bundle and set the expanded_node_host_names parameter to 1 (default is 0).
uapm3501p:(/) # kctune expanded_node_host_names=1

kernel

The following is required -The optional Node and Host Name Expansion (NodeHostNameXpnd) product bundle, revision B.11.23.01, provides you with the ability to set node and host names up to 255 bytes. This product is available on Software Pack (SPK) for HP-UX 11i v2 May 2005. (For more information about SPK, see Software Pack (Optional HP-UX 11i v2 Core Enhancements).) Summary of Change 35/37

HPUXCheatSheet

07/17/07 13:40:06

Without NodeHostNameXpnd, node names are limited to 8 bytes, and host names are limited to 64 bytes. With NodeHostNameXpnd, node and host names can be expanded to 255 bytes each. Impact This product allows you to set longer node and host names for your HP-UX 11i v2 systems. Compatibility If you choose to load only the May 2005 version of this feature, without doing a complete update to the May 2005 version of HP-UX 11i v2, you must first load the September 2004 version of HP-UX 11i v2. The default HP-UX system parameters ensure that node and host names do not exceed the compatible lengths of 8 and 64 bytes, respectively. The NodeHostNameXpnd product bundle includes a new system tunable parameter by which you can enable the system to accept node and host names up to 255 bytes in length. Setting node and host names longer than 8 or 64 bytes, respectively, can cause some applications that use the node and/or host names to exhibit anomalous behavior or fail. HP strongly recommends that you understand all NodeHostNameXpnd documentation (manpages and the Node and Host Name Sizes on HP-UX whitepaper) before enabling the system to accept longer names. The whitepaper Node and Host Name Sizes on HP-UX can be found at /usr/share/doc/NodeHostNameSize.pdf following installation of the NodeHostNameXpnd optional product bundle. The whitepaper can also be found on the Software Pack media at /DOCS/NodeHostNameXpnd/NodeHostNameSize.pdf. The NodeHostNameXpnd product bundle is supported only on the HP-UX 11i v2 operating system. 1.12.5.1 Installing the Core enhancements extension Download the NodeHostXpnd bundle depot from HP download site (http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=NodeHostNameXpnd) Log in as root. Download the depot file to /var/tmp/NodeHostNameXpnd Verify the file has down-loaded correctly using swlist. Note that swlist and swinstall require you to specify the full path name to the source depot. # swlist -s /var/tmp/NodeHostNameXpnd Backup your system before installing the product. Use SD to install the NodeHostNameXpnd bundle. Note that because the bundle includes updates to kernel components, the autoreboot flag must be specified. The system will reboot after installation: HP strongly recommends that you read and understand the documentation before using the product. The detailed documentation describes application issues and limitations as well as provides instructions for preparing your system for product use. The documentation is installed at: /usr/share/doc/NodeHostNameSize.pdf. You can install just the product documentation. Installation of the documentation will also require a system reboot. Select documentation only installation using the swinstall interface or enter:
# swinstall -x autoreboot=true \ -s /var/tmp/NodeHostNameXpnd \ NodeHostNameXpnd.NodeHostXpndEnbl.NODEHOSTXP-MAN

Full installation will install the expanded_node_host_names kernel tunable, its manpage, OS extensions to support expanded names, and the product documentation. Select full installation using the swinstall interface or enter:
# swinstall -x autoreboot=true \ -s /var/tmp/NodeHostNameXpnd NodeHostNameXpnd

The system will reboot following installation. NOTE The software distribution/installation package cannot ensure that optional HP products have the latest revision which accommodates expanded names. You must manually check the dependencies list included earlier in this document before enabling and using long node and/or host names. If you later install other optional products, be sure to obtain a version which accommodates the longer names. When the system comes up following installation, please verify the installation logs using: # swverify NodeHostNameXpnd Enabling and Disabling the Node and Host Name Expansion Option Once you have installed the Node and Host Name Expansion Option, it must be enabled before use. There are several considerations that should be made prior to enabling the option. These considerations and the procedures for enabling and disabling the expanded name option are provided in the document Node and Host Name Sizes on HP-UX located at: /usr/share/doc/NodeHostNameSize.pdf after installation of the product bundle. This document 36/37

HPUXCheatSheet

07/17/07 13:40:06

describes important product limitations and should be read and understood before enabling the product. Removing the Node and Host Name Expansion Option To remove the Node and Host Name expansion option, use the following procedure: Ensure all node and host names conform to the non-expanded constraints of 8 and 64 bytes, respectively. Ensure that the Option is disabled. Turn off the expanded_node_host_names tunable parameter using the administrative command line: # kctune expanded_node_host_names=0 Use the swremove command to remove the product: # swremove -x autoreboot=true NodeHostNameXpnd This will remove the product, including kernel tunable, its manpage, and OS extensions to support expanded names, and reboot your system. You may find that the NodeHostNameXpnd product bundle is not entirely removed due to the inclusion of a non-removable patch (PHKL_31500), if that patch was not present before NodeHostNameXpnd was installed. However, all other products from the bundle should be successfully removed. HPUXCheatSheet (last edited 2007-05-30 20:34:13 by DLahiri)

37/37