Use Unix or Die !!

Thursday, October 14, 2010

dosent look good

Now that I have atleast two blogs, I have scrolled down to check them, Somehow I am not very convinced the way it looks, long and lengthy, I could imagine what would happen after I add another 20 blogs.

May be I am not at the right place. I will do more research to publish my work which can be useful for every unixite.

HPUX: IGNITE

Now on my second Blog, I would like to introduce IGNITE-UX

Setting up a Ignite Box depends on the h/w being used: PA-RISC/Itanium

NOW WE WILL SETUP AN IGNITE SERVER

1.Steps to setup On a Itanium Server

A>On the Server Side

a) Install Ignite-UX-11-ALL_C.7.6.100.depot from

http://docs.hp.com/en/IUX/download.html

#swinstall –s Ignite-UX-11-ALL_C.7.6.100.depot

b) Created the depots on the Server HP UX 11i V3[Both DVD 1 of 2 & 2 of 2]

#/opt/ignite/bin/make_depots -s /dvdrom \-d /var/opt/ignite/depots/Rel_B.11.31/core_media

c) Create the HP-UX OE Configuration Information on the Ignite-UX Server

#/opt/ignite/bin/make_config -s /var/opt/ignite/depots/Rel_B.11.31/core_media \-c /var/opt/ignite/data/Rel_B.11.31/core_media_cfg

d) Add the configuration information to the Ignite-UX /var/opt/ignite/INDEX file.

#/opt/ignite/bin/manage_index -n "HP-UX B.11.31 Default" \-c "B.11.31 From OE Media"

e) I have added the core_media_cfg file is added to the “B.11.23 From OE Media” clause.

#/opt/ignite/bin/manage_index -a \-f /var/opt/ignite/data/Rel_B.11.31/core_media_cfg \-c "B.11.31 From OE Media"

# /opt/ignite/bin/manage_index -x -c "B.11.31 From OE Media"

# /opt/ignite/bin/manage_index -c "B.11.31 From OE Media" -y "B.11.31 0803 OE"

f) Configure the System as an Ignite-UX Server

# /opt/ignite/lbin/setup_server -n

g) Enable the bootpd daemon with the following Procedure:

Procedure

i. Edit the /etc/inetd.conf file:

# vi /etc/inetd.conf

ii. Remove the comment character (#) from the bootpd line:

bootps dgram udp wait root /usr/lbin/bootpd bootpd

iii. Save the /etc/inetd.conf file and exit vi:wq!

iv. Make the inetd daemon reread the /etc/inetd.conf file:

# inetd -c

And after modification it looks as below:-

Entries in /etc/inetd.conf

--------------------------

bootps dgram udp wait root /usr/lbin/bootpd bootpd

#finger stream tcp nowait bin /usr/lbin/fingerd fingerd

shell stream tcp6 nowait root /usr/lbin/remshd remshd

exec stream tcp6 nowait root /usr/lbin/rexecd rexecd

#uucp stream tcp nowait root /usr/sbin/uucpd uucpd

ntalk dgram udp wait root /usr/lbin/ntalkd ntalkd

auth stream tcp6 wait bin /usr/lbin/identd identd

h) To Ignite a Client across the Network, add the Network Entry for the Client to the IP Address File on the Server @ /etc/bootptab.

Entries in /etc/bootptab looks like:-

--------------------------------------

ignite-defaults:\

ht=ethernet:\

hn:\

dn=domain_name.com:\

gw=10.3.90.1:\

sm=255.255.255.0:\

vm=rfc1048:\

bf=/opt/ignite/boot/nbp.efi:

bs=48

iuxclient1:\

tc=ignite-defaults:\

ha=0x00215af8a67c:\

ip=10.3.90.9:

NOTE:

# Example /etc/bootptab: database for bootp server (/usr/lbin/bootpd).

#@(#)B11.23_LR $Revision: 1.4.214.1 $ $Date: 96/10/08 12:46:42 $

# Format:

# nodename:tag=value:tag=value: ... :tag=value

# first field -- nodename (hostname) of terminal followed by colon

# (should be full domain name)

# Blank lines and lines beginning with '#' are ignored.

# Make sure you include a colon and a backslash to continue a line.

# Don't put any spaces in the tag=value string.

# The ht tag MUST precede the ha tag.

# The options listed below are commonly used for HP X Window terminals

# HPUX

# see the bootpd.1m man page.

# ba -- broadcast bootp reply for testing with bootpquery

# bf -- bootfile (for tftp download)

# bp -- bootp server IP addresses to relay the bootp requests

# bs -- bootfile size in 512-octet blocks

# ci -- client ID (for dhcp clients only)

# cs -- cookie server IP address

# dn -- domain name

# ds -- domain name server IP address

# ef -- extensions file, containing more options for the client

# gw -- gateway IP address (must have sm tag defined also)

# ha -- hardware address (link level address) (hex)

# hd -- home directory for bootfile (chrooted to tftp home directory)

# hn -- send nodename (boolean flag, no "=value" needed)

# hm -- hardware mask (hex) (must be preceded the ht tag)

# hp -- maximum hops value (cannot exceed 16)

# ht -- hardware type (ether) (must precede the ha and hm tag)

# im -- impress server IP address

# ip -- (client) IP address

# lg -- (MIT-LCS UDP) log server IP address

# lp -- LPR (line printer) server IP address

# md -- file to dump core image to in the event of a crash

# na -- NETBIOS name server IP address

# nb -- NETBIOS datagram distribution server IP address

# nc -- NETBIOS over TCP/IP node type (B-node, P-node, M-node, or H-node)

# nd -- NETBIOS over TCP/IP scope

# ns -- name server (IEN 116) IP address

# nt -- network time protocol server IP address

# rl -- resource location server

# rp -- path name to client's root disk

# sm -- network subnet mask

# ss -- swap server IP address

# tc -- template for common defaults (should be the first option listed)

# th -- threshold value in seconds

# to -- time offset in seconds from Coordinated Universal Time

# tr -- renewal (T1) time value (a percentage of the lease time)

# ts -- time server IP address

# tv -- rebinding (T2) time value (a percentage of the lease time)

# vm -- vendor magic cookie selector (should be rfc1048)

# xd -- X window system display manager IP address

# xf -- X window system font server IP address

# yd -- NIS domain name

# ys -- NIS server IP address

# Tn -- generic option tag n

# T144 remote config file name (file name must be enclosed in "")

# Vn -- vendor specific information for vendor option tag of n

B>At the client side(Itanium):

Shell>lanboot select –dn

Shell>search

C>Direct Boot Profiles for Itanium-Based Systems at the Clint side

The following dbprofile command, when run from EFI,

Shell>dbprofile -dn testprofile -sip 10.3.90.14 -cip 10.3.90.9 -gip 10.3.90.1 -m 255.255.255.0 -b "/opt/ignite/boot/nbp.efi"

creates a new direct boot profile (or updates the profile if it exists) called testprofile.

The profile contains the following information:

Ignite-UX server IP address (-sip) 10.3.90.14

Ignite client IP address (-cip) 10.3.90.9

Gateway IP address (-gip) 10.3.90.1

Network mask (-m) 255.255.255.0

Boot file name (-b) /opt/ignite/boot/nbp.efi

Shell>lanboot select -dn testprofile

2.Steps to setup On a PA-RISC Server

A>On the Server Side

a) Edit the /etc/opt/ignite/instl_boottab file (don't worry that it appears to be [Read-only]):

# vi /etc/opt/ignite/instl_boottab

b) Add an entry for your client. If a network entry already exists for your client, you may edit it so it looks like the entry below. The client's MAC address should be in hexadecimal, with a leading “0x”.

client_IP_address:client_MAC_address::reserve

c) Save the /etc/opt/ignite/instl_boottab file and exit vi:

:wq!

B>At the client side(Itanium):

Shell>boot lan

USEFUL/HANDY LINKS:

http://www.hp.com/go/sw-deployment-docs

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&taskId=101&prodClassId=10008&contentType=SupportManual&docIndexId=64255&prodTypeId=18964&prodSeriesId=4077173

HP-UX INTEGRITY VIRTUAL MACHINES(Integrity VM)

Now that I have started my first Technical Blog....

HP Integrity Virtual Machines (Integrity VM) is a virtualization or hypervisor technology within the HP Insight Dynamics – VSE that enables you to create multiple virtual servers or machines with shared resourcing within a single HP Integrity server or nPartition—each with its own 'guest' operating system instance, applications and users. Integrity VM provides automatic, dynamic, resource allocation, based on demand and entitlement.

Online VM Migration

Online VM Migration additionally enables a running VM, its guest OS, and all of its applications to be moved to a different VM Host without any service interruption. Services remain active with no OS reboots or application restarts. All I/O connections to storage and networks remain active during the migration, leaving the change transparent to applications and users.

Using Online VM Migration allows an administrator to do online maintenance (patch, update, or reconfigure) of VM Hosts, as well as balance server (host) loads, without interruption to the VM Host or virtual machines. The functionality can be used in conjunction with other HP tools, such as HP Serviceguard Solutions to provide improved availability and flexibility.

At a Glance

Current version: B.04.20.05
Hardware platforms: Any HP Integrity server (including blades, legacy, Integrity i2 blades and Superdome 2), with or without nPartitions
VM Host Operating Systems: HP-UX 11i v3 (on the new Integrity servers)
Shared resources: processor cores, I/O, tape and DVD changer
Virtualized resources: processor cores, I/O, memory, switch, vLAN
Dynamic: Automatic CPU & memory resource reallocation, memory migration, online VM migration

I have tried out 4.1 and hence I give the description for HPVM 4.1, however there is no much difference in the creation of the Host/Guest.

Download HPVM 4.1 from the below website:

https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=integrity_vm41

NOTE: The above is only a trial version. You will have to buy the full version. Also just fyi.. HPVM 4.2.5 is the latest version.

Having said that HPVM 4.1 is supported only on HPUX 11.31 and onwards.

Install the below patches from http://www.itrc.hp.com

PHSS_37312 (Integrity VM)

PHSS_37306 (VMagent)

Install the Integrity VM Media Kit

I am creating lvols cos I do not have any left on my Box.

# lvcreate -L 40960m -n lvol9 vg00

# lvcreate -L 40960m -n lvol10 vg00

# lvcreate -L 40960m -n lvol11 vg00

# lvcreate -L 40960m -n lvol12 vg00

Now I will create a VM Guest:

# hpvmcreate -P VM03A -O HPUX:11.31 -c2 -r1G

# hpvmmodify -P VM03A -a disk:scsi::lv:/dev/vg00/rlvol9

# hpvmmodify -P VM03A -a network:lan::vswitch:vswth01

# hpvmstart -P VM03A

Initializing System Event Log

Initializing Forward Progress Log

Opening minor device and creating guest machine container

Creation of VM, minor device 2

Allocating guest memory: 1024MB

allocating low RAM (0-40000000, 1024MB)

/opt/hpvm/lbin/hpvmapp (/var/opt/hpvm/uuids/8ad310ce-8fe0-11dd-8403-001f29f280f2

/vmm_config.next): Allocated 1073741824 bytes at 0x6000000100000000

allocating datalogger memory: FF800000-FF840000 (256KB for 155KB)

/opt/hpvm/lbin/hpvmapp (/var/opt/hpvm/uuids/8ad310ce-8fe0-11dd-8403-001f29f280f2

/vmm_config.next): Allocated 262144 bytes at 0x6000000180000000

locking datalogger memory

allocating firmware RAM (fff00000-fff20000, 128KB)

/opt/hpvm/lbin/hpvmapp (/var/opt/hpvm/uuids/8ad310ce-8fe0-11dd-8403-001f29f280f2

/vmm_config.next): Allocated 131072 bytes at 0x6000000180080000

locked SAL RAM: 00000000fff00000 (8KB)

locked ESI RAM: 00000000fff02000 (8KB)

locked PAL RAM: 00000000fff04000 (8KB)

locked Min Save State: 00000000fff06000 (8KB)

locked datalogger: 00000000ff800000 (256KB)

Loading boot image

Image initial IP=102000 GP=67E000

Initialize guest memory mapping tables

Starting event polling thread

Starting thread initialization

No NVRAM persistent variables on disk

Daemonizing....

hpvmstart: Successful start initiation of guest 'VM03A'

Assigning a Virtual dvd

hpvmmodify -P VM03A -a dvd:scsi::disk:/dev/rdsk/c1t0d0

hpvmmodify -P VM03B -a dvd:scsi::disk:/dev/rdsk/c1t0d0

hpvmmodify -P VM04A -a dvd:scsi::disk:/dev/rdsk/c1t0d0

hpvmmodify -P VM04B -a dvd:scsi::disk:/dev/rdsk/c1t0d0

I have now managed to create four Virtual Guests viz., VM03A,VM03B,VM04A,VM04B

Assign the LVOLS:

# hpvmmodify -P VM04A -a disk:scsi::lv:/dev/vg00/rlvol9

# hpvmmodify -P VM04B -a disk:scsi::lv:/dev/vg00/rlvol10

Now each VM has a disk.

Next is LAN.

Create a virtual switch on a physical NIC (here lan0), name it vswitch01:

# hpvmnet -c -S vswth01 -n 0

power on the vswitch:

# hpvmnet -b -S vswth01

assign the network:

# hpvmmodify -P VM04A -a network:lan::vswitch:vswth01

# hpvmmodify -P VM04B -a network:lan::vswitch:vswth01

start the VMs:

# hpvmstart -P VM04A

# hpvmstart -P VM04B

Connect to the vMP of the first VM:

# hpvmconsole -P VM04A

and proceed to install HP-UX via IGNITE-UX.

NOTE: You can install OS on the Guest using Disk/ISO/IGNITE.I have chosen IGNITE.

In my second blog we can discuss on IGNITE-UX.

USEFUL/HANDY LINKS

http://h10025.www1.hp.com/ewfrf/wc/document?lc=en&dlc=en&cc=emea_middle_east&docname=c01794546

http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c02018678/c02018678.pdf

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&taskId=101&prodClassId=10008&contentType=SupportManual&docIndexId=64255&prodTypeId=18964&prodSeriesId=4146186

Useful Integrity VM commands:

hpvmclone: Creates a cloned copy of a virtual machine. Runs on the VM Host.

hpvmcollect: Collects crash dumps, logs, system status, and configuration on host and guest. Runs on the VM Host and on guests.

hpvmconsole: Connects to the console of a virtual machine. Runs on the VM Host.

hpvmcreate: Creates a new virtual machine. Runs on the VM Host.

hpvmdevmgmt: Manages the device database. Runs on the VM Host.

hpvmmgmt: Manages the guest memory allocation. Runs on guests only.

hpvminfo: Displays information about the Integrity VM environment. Runs on the VM Host and on guests.

hpvmmigrate: Moves a virtual machine from one VM Host to another. Runs on the VM Host.

hpvmmodify: Renames or modifies the attributes of a virtual machine. Runs on the VM Host.

hpvmnet: Configures virtual network devices. Runs on the VM Host.

hpvmremove: Removes a virtual machine. Runs on the VM Host.

hpvmstart: Starts a virtual machine. Runs on the VM Host.

hpvmstatus: Displays status of one or more virtual machines. Runs on the VM Host.

hpvmstop: Stops a virtual machine. Runs on the VM Host.

p2vassist: Moves a system workload from a discreet server to a virtual machine. Runs on the VM Host.

All commands except hpvmconsole require superuser privileges

Introduction

Well, i was going through the 1000's of Blogs related to the Environment UNIX, and something struck my head and thought to create one more to add to the 1000's.

However I wanted this one to be useful to everyone right from learners,Jr. Sys. Admins to Sr. Sys. Admins.

I would like to include anything & everything which hits my head with the limitation to the Unix Environment(HP-UX; Solaris; AIX; Linux; MAC OS) including Operating System, Hardware, Storage connected to it and if possible Networking though my knowledge on this is limited.

Any kind of comments to improve this blog or ideas to create a new one would be helpful.

Happy Blogging!!