Eduardo Fraga's HP-UX blog

Create a patch bundle from multiple depots

2015-08-10T10:56:00.001-03:00

First, you need to the depots using swcopy to a "central location":

#swcopy -x enforce_dependencies=false -s /tmp/First.depot \* @ /depot/MyBigDepot

#swcopy -x enforce_dependencies=false -s /tmp/Second.depot \* @ /depot/MyBigDepot

#swcopy -x enforce_dependencies=false -s /tmp/Third.depot \* @ /depot/MyBigDepot

Second and last, build your depot (The .depot files are actually images of swinstall tapes):

# swpackage -x media_type=tape -s /depot/MyBigDepot \* @ /tmp/MyBigDepot.depot

Disk migration - pvmove

2015-04-01T12:06:00.002-03:00

Migrate a disk can be necessary during storage migrations or even during a hw problem.

I will explain here how to do this using pvmove.

Migrating an entire disk:

# pvmove /dev/disk/disk4 /dev/disk/disk5

The first argument (disk4) represents the source followed by the destination (disk5).

Ps. You need both disks inside of the same Volume Group.

How to clone a HP-UX using a ignite backup?

2015-03-18T16:52:00.000-03:00

The recovery configurations and archives created by make_net_recovery are stored in a separate directory on the Ignite-UX server for each client. Using the configuration and archive created by make_net_recovery on one system to install a different system involves manually copying some configuration files, and allowing NFS access to the source system's archive.
Details
The steps to clone a system using make_net_recovery are:
Use make_net_recovery (or the ignite GUI) to create a system recovery archive of the source system.

Login into the Ignite-UX server

If the target system to be installed does not currently have a directory in /var/opt/ignite/clients but is up and running, then use the ignite GUI to create that directory using the 'Add New Client for Recovery' action. If the system is not running, you will either need to boot the client from the Ignite-UX server (or for a tape made with make_boot_tape) in order for this directory to be created.

Copy the CINDEX and recovery directory from the source client to the target client directory. Note that if the target client has previously used make_net_recovery then it will already have a CINDEX file. If the CINDEX file for the target system exists already, you may want to save a copy, and/or hand edit the file to add the desired entries from the source client. The commands below will copy the required files, you may specify src-client and target-client using either the LAN addresses (e.g., 0x0060B04AAB30), or by using the client's hostname (which is a symlink to the LAN address).

# vi /etc/hosts [Keep the new host name in /etc/hosts file on Ignite server]
# cd /var/opt/ignite/clients/src-client
# find CINDEX recovery | cpio -pdvma ../target-client

Give the target-client NFS access to the archive of the source system. To do this, login to the server that holds the archive (normally the Ignite-UX server).
Typically each client has its own directory for storing the archives, and the directory is exported only to the individual client. In this case, you will need to edit the /etc/exports file to allow access to both the source and target

clients:
# vi /etc/exports
(append :target-client to the end of the source-client's line)
# exportfs –av

Now you can boot the target-client from the Ignite-UX server (using any method you wish). Then when you install the system, you can select from the recovery configurations of the source system.

Remove / cancel printer jobs

2014-09-24T13:40:00.003-03:00

Here is a command to remove all jobs from a printer queue (you need root):
# cancel -e hplj32

You can always list the jobs using lparstat (syntax lpstat queue_name) and then manually cancel just a single job using the command cancel followed by a job number.

Here I am requesting to cancel the hplj32-13 job

# cancel hplj32-13

Start/Stop EMS and Clean EMS logs - Prevent to resending old events

2013-06-09T16:01:00.001-03:00

This is very useful when you are getting old error messages, some problem that was fixed and you still receive warning about them.

1. Clear all logs in MP, SEL and FPL with the MP SL (System Logs) and the Clear all logs commands.
2. Stop the EMS deamon:
/etc/opt/resmon/lbin/monconfig (selecting K)
3. Now you can remove(or move them if you want keep) all logfiles /var/stm/logs/os/fpl.log* to prevent resending the old events after the restart of EMS.
4. Back up and Remove /var/stm/logs/monitor/fpl_em.dat .
5. Back up and Remove /var/stm/logs/monitor/fpltime.dat .
6. Back up and Remove /var/stm/logs/monitor/remindersel.dat .
7. Start the EMS deamon
/etc/opt/resmon/lbin/monconfig (enable event monitoring)

Quick Reference - FTP for dummies

2013-05-13T18:59:00.001-03:00

Here is a command line guide reference.

help <command>
This command provide a short description about a command.

?
Request help or information about the FTP commands

ascii
to set the mode of file transfer to ASCII
(this is the default and transmits seven bits per character)

binary
to set the mode of file transfer to binary
(the binary mode transmits all eight bits per byte and thus provides less chance of a transmission error and must be used to transmit files other than ASCII files)

bye
to exit the FTP environment (same as quit)

cd
to change directory on the remote machine

close
to terminate a connection with another computer

delete
to delete (remove) a file in the current remote directory (same as rm in UNIX)

get
to copy one file from the remote machine to the local machine

get ABC DEF
copies file ABC in the current remote directory to (or on top of) a file named DEF in your current local directory.

lcd
to change directory on your local machine (same as UNIX cd)

ls
to list the names of the files in the current remote directory

mkdir
to make a new directory within the current remote directory

mget
to copy multiple files from the remote machine to the local machine;
   you are prompted for a y/n answer before transferring each file

mput
to copy multiple files from the local machine to the remote machine;
   you are prompted for a y/n answer before transferring each file

open
to open a connection with another computer

put
to copy one file from the local machine to the remote machine

pwd
to find out the pathname of the current directory on the remote machine

quit
to exit the FTP environment (same as bye)

rmdir
to to remove (delete) a directory in the current remote directory

!<command>
Send a command locally not in the remote server.

Quick Reference - Data Protector command line

2013-05-09T21:20:00.000-03:00

A Data Protector command line (6.11) quick reference, it's quite useful on daily tasks.

omniabort
Aborts an active session.
This command is available on systems with the Data Protector User Interface
component installed.

omniamo
Starts an automated media operation session.
This command is available on the Data Protector Cell Manager.

omnib
Backs up filesystems, disk images, the Data Protector internal database (IDB),
Microsoft Exchange Server single mailboxes and Public Folders, Microsoft
Exchange Server, Microsoft SQL Server, Microsoft SharePoint Portal Server (SPS),
SAP R/3, SAP DB/MaxDB, Oracle, Informix Server, VMware Virtual Infrastructure
(VMware), Sybase, Lotus, IBM DB2 UDB, NetWare objects, and NDMP objects.
This is the only command supported with the MPE/iX integration.
This command is available on systems with the Data Protector User Interface
component installed.

omnicc
Handles the Data Protector licensing, reports the number of configured and
available Data Protector licenses, installs the licenses, imports and exports Data
Protector clients, and manages access to secured clients.
Command line interface reference 25This command is available on systems with any Data Protector component
installed.

omnicellinfo
Displays configuration information about the Data Protector cell.
This command is available on systems with the Data Protector User Interface
component installed.

omniclus
Manages load balancing in a cluster environment in the event of an application
(Data Protector or other) failover.
This command is available on systems with the Data Protector MS Cluster
Support component installed (Windows systems) and on the Data Protector
Cell Manager (UNIX systems).

omnicreatedl
Creates a Data Protectorbackup specification file (datalist); or an HP
StorageWorks Disk Array XP, HP StorageWorks Virtual Array, or HP
StorageWorks Enterprise Virtual Array Microsoft Exchange Server ZDB backup
specification file (datalist).
This command is available on systems with the Data Protector User Interface
component installed.

omnidb
Queries the Data Protector internal database (IDB).
This command is available on systems with the Data Protector User Interface
component installed.

omnidbsmis
Executes administrative tasks required for managing the HP StorageWorks
Enterprise Virtual Array (EVA) Command View.
This command is available on systems with the Data Protector User Interface
component installed.

omnidbva
Queries the ZDB database (VADB) and administers the VA LUN Exclude File,
instant recovery and password information.
This command is available on systems with the Data Protector User Interface
component installed.

omnidbvss
Queries the VSS database; manages, browses, and lists the items of the VSS
database.
This command is available on systems with the Data Protector User Interface
component installed.

omnidbxp
Queries the ZDB database (XPDB), manipulates the XP LDEV exclude file, and
configures the HP StorageWorks Disk Array XP command devices usage.
This command is available on systems with the Data Protector User Interface
component installed.

omnidownload
Downloads information about a backup device and a library from the Data
Protector internal database (IDB).
This command is available on systems with the Data Protector User Interface
component installed.

omniiso
Primarily serves as a pre-exec script to prepare the ISO image file for One Button
Disaster Recovery (OBDR); can also be used as a standalone command to
automate your backup and disaster recovery process.
This command is available on systems with the Data Protector Automatic
Disaster Recovery component installed.

omnimcopy
Makes a copy of a Data Protector medium using Data Protector backup devices
as the source and destination.
This command is available on systems with the Data Protector User Interface
component installed.

omniminit
Initializes a Data Protector medium.
This command is available on systems with the Data Protector User Interface
component installed.

omnimlist
Lists the contents of a Data Protector medium.
This command is available on systems with the Data Protector User Interface
component installed.

omnimm
Provides media management for Data Protector.
This command is available on systems with the Data Protector User Interface
component installed.

omnimnt
Responds to a Data Protector mount request for a medium.
Command line interface reference 27This command is available on systems with the Data Protector User Interface
component installed.

omnimver
Verifies data on a medium.
This command is available on systems with the Data Protector User Interface
component installed.

omniobjconsolidate
Consolidates Data Protector backup objects into synthetic full backups.
This command is available on systems with the Data Protector User Interface
component installed.

omniobjcopy
Creates additional copies of objects backed up with Data Protector on a different
media set.
This command is available on systems with the Data Protector User Interface
component installed.

omniobjverify
Verifies Data Protector backup objects, either interactively or using pre-configured
post-backup, or scheduled verification specifications.
This command is available on systems with the Data Protector User Interface
component installed.

omnir
Restores filesystems, disk images, the Data Protector database (IDB), Microsoft
Exchange Server single mailboxes and Public Folders, Microsoft Exchange Server,
Microsoft SQL Server, Microsoft SharePoint Portal Server (SPS), SAP R/3, SAP
DB/MaxDB, Informix Server, VMware Virtual Infrastructure (VMware), Lotus, IBM
DB2 UDB, NetWare objects, and NDMP objects backed up with Data Protector.
The command is also used to start the instant recovery process. To restore a
Sybase database, refer to the syb_tool man page.
This command is available on systems with the Data Protector User Interface
component installed.

omnirpt
Generates various reports about the Data Protector environment, for example,
about backup, object copy, object consolidation, and object verification sessions
in a specific time frame, session specifications, media, Data Protector
configuration, and single sessions.
This command is available on systems with the Data Protector User Interface
component installed.

omnistat
Displays the status of active Data Protector backup and restore sessions.
This command is available on systems with the Data Protector User Interface
component installed.

omniupload
Uploads information about a backup device from an ASCII file to the Data
Protector internal database (IDB).
This command is available on systems with the Data Protector User Interface
component installed.

omniusers
Adds or removes Data Protector users to or from an existing Data Protector user
group, or lists the configured Data Protector users. It enables you to use all GUI
functionality on a Cell Manager platform on which the GUI is not available,
using a GUI installed on another system.
This command is available on systems with the Data Protector User Interface
component installed.

syb_tool
A utility used to get ISQL command needed to restore a Sybase database that
was backed up by Data Protector.
This command is available on systems with the Data Protector Sybase
Integration component installed.

ADMINISTRATIVE COMMANDS (1M):

ob2install
Runs remote client installation, uninstallation, upgrade, or check of a client from
the selected Installation Server.
This command is available on the Data Protector Installation Server.

omnicheck
Performs a DNS connections check within a Data Protector cell and lists Data
Protector patches installed on Data Protector clients.
This command is available on systems with any Data Protector component
installed.

omnidbcheck
Checks the consistency of the Data Protector internal database (IDB).
This command is available on the Data Protector Cell Manager.

omnidbinit
Initializes the Data Protector internal database (IDB).
This command is available on the Data Protector Cell Manager.
Command line interface reference 29omnidbrestore
Restores the Data Protector internal database (IDB).
This command is available on the Data Protector Cell Manager.

omnidbupgrade
Converts filenames in the IDB to the new internal character encoding used in
Data Protector A.06.11 and thus enables the correct handling of non-ASCII
characters in filenames in the Data Protector GUI.
This command is available on the Data Protector Cell Manager.

omnidbutil
Handles various Data Protector internal database (IDB) maintenance tasks.
This command is available on the Data Protector Cell Manager.

omnidlc
Gathers or deletes Data Protector debug, log, and getinfo files from the Data
Protector cell or from a MoM environment.
This command is available on the Data Protector Cell Manager.

omnidr
A general purpose Data Protector disaster recovery command. Based on its input,
it decides on what type of restore to perform (online restore using omnir or
offline restore using omniofflr), as well as how to perform the restore (whether
or not to use live OS features).
This command is available on systems with the Data Protector User Interface
component installed.

omnihealthcheck
Checks the status of Data Protector services, the consistency of the Data Protector
internal database (IDB), and if at least one backup of the IDB exists.
This command is available on the Data Protector Cell Manager.

omniinetpasswd
Manages the local Data Protector Inet configuration on Windows systems where
the Inet process must be run under a specific user account, and sets a user account
to be used by the Installation Server during remote installation.
This command is available on systems with any Data Protector component
installed.

omniinstlic
Starts the HP AutoPass utility or synchronizes the Data Protector licenses between
Data Protector and HP AutoPass.
This command is available on the Data Protector Cell Manager.

omniintconfig.pl
30Configures, updates configuration parameters, and checks the configuration of
one or multiple Oracle databases.
This command is available on systems with the Data Protector User Interface
component installed.

omnikeymigrate
Helps you migrate your existing keystore file from Data Protector A.06.00 client
system and imports it into the central keystore file on the Data Protector A.06.11
Cell Manager.
This command is available on the Data Protector Cell Manager.

omnikeytool
Manages keys used for encryption.
This command is available on the Data Protector Cell Manager.

omnimigrate.pl
Helps you migrate your existing Cell Manager from a PA-RISC architecture based
HP-UX 11.x system to an HP-UX 11.23 system for the Intel Itanium 2 (IA-64)
architecture.
This command is available on the Data Protector Cell Manager.

omniofflr
Enables restore of any type of Data Protector backup object in the absence of a
working Data Protector internal database (IDB).
This command is available on systems with the Data Protector User Interface
component installed.

omniresolve
Resolves a filesystem object or a list of filesystem objects and writes the results
to the standard output or to a Unicode file.
This command is available on systems with any Data Protector integration
component installed.

omnirsh
Returns the hostnames of the physical and virtual nodes for the specified cluster
hostname, or returns the cell information stored in the cell_info file on the specified
cluster.
This command is available on the Data Protector Cell Manager.

omnisetup.sh
Installs or upgrades a Data Protector UNIX Cell Manager, Installation Server, or
client system locally.
This command is available on the Data Protector installation DVD-ROMs for UNIX
systems.

omnisrdupdate
Updates the System Recovery Data (SRD) file.
This command is available on systems with the Data Protector User Interface
component installed.

omnisv
Starts, stops, or displays the status of Data Protector daemons (HP-UX, Solaris,
or Linux systems) or services (Windows systems).
This command is available on the Data Protector Cell Manager.

omnitrig
Triggers Data Protector scheduled backups.
This command is available on the Data Protector Cell Manager.

sanconf
Auto-configures a library, modifies an existing library or drive configuration, or
removes drives from a library configuration, within a SAN environment.
This command is available on systems with the Data Protector User Interface
component installed.

upgrade_cm_from_evaa
Upgrades the EVADB entries created by the HP StorageWorks EVA Agent (legacy)
to the SMISDB entries created by the HP StorageWorks EVA SMI-S Agent.
This command is available on the Data Protector Cell Manager.

util_cmd
Sets, retrieves or lists the parameters stored in the Data Protector Oracle, SAP
R/3, VMware Virtual Infrastructure (VMware), Informix, and Sybase configuration
files.
This command is available on systems with any Data Protector component
installed.

util_oracle8.pl
Configures an Oracle database and prepares the environment for backup, and
checks the configuration of an Oracle database.
This command is available on systems with the Data Protector Oracle
Integration component installed.

util_vmware.exe
Configures a VMware datacenter, checks the configuration of a VMware
datacenter, and lists all configured VMware datacenters.
This command is available on systems with the Data Protector VMware
Integration component installed.

winomnimigrate.pl
Helps you migrate your existing Cell Manager from a 32-bit Windows system
to a 64-bit Windows system, or from a 64-bit Windows system to 64-bit Windows
Server 2008.
This command is available on the Data Protector Cell Manager.
COMMAND-LINE UTILITIES (1M):

cjutil
Starts, stops, and queries the Windows Change Journal.
This command is available on systems with the Data Protector Disk Agent
component installed.

NNMpost.ovpl
A script with no arguments that resumes the eight processes paused by

NNMpre.ovpl.
This command is available on systems with the Data Protector HP Network
Node Manager Integration component installed.

NNMpre.ovpl
Starts NNM embedded database backup.
This command is available on systems with the Data Protector HP Network
Node Manager Integration component installed.

NNMScript.exe
Finds the location of the NNM Perl compiler and the NNMpre.ovpl and
NNMpost.ovpl scripts and starts the two scripts.
This command is available on systems with the Data Protector HP Network
Node Manager Integration component installed.

omnicjutil
Remotely controls and administers the Windows Change Journal on Windows
clients.
This command is available on the Data Protector Cell Manager.

omnistoreapputil
Acts as a user interface to Storage Appliances, such as VLS.
This command is available on the Data Protector Cell Manager.

uma
Controls the robotics of SCSI compliant autochangers.
This command is available on systems with the Data Protector General Media
Agent or NDMP Media Agent component installed.

Source: Command line interface reference

MP commands

2013-05-04T14:13:00.003-03:00

Some commands are restricted to users with Operatoror Administrator authority. Also note that the available set of commands may differ depending on the utility revision level and server hardware model.

For details on these commands, use the help (HE: Help) feature at the service processor Main

menu. Enter the command name at the MP:HELP or GSP:HELP prompt for syntax, restrictions,

and other information.

Service Processor (MP or GSP) Command Reference

Command Description

BO Boot an nPartition past Boot is Blocked (BIB)

DF Display FRU information of an entity

MA Return to the Main menu

MR Modem reset

PCIOLAD Activate/deactivate a PCI card

PE Power entities on or off

RE Reset entity

Reset an nPartition for reconfiguration; the nPartition remains inactive, in the shutdown

for reconfig state

RS Reset an nPartition

TC Send a TOC signal to an nPartition

TE Broadcast a message to all users of the MP Command Handler

VM Margin the voltage in a cabinet

WHO Display a list of MP connected users

CP Display nPartition cell assignments

HE Display the list of available commands

IO Display IO chassis/cell connectivity

LS Display LAN connected console status

MS Display the status of the modem

PS Display detailed power and hardware configuration status

SYSREV Display revisions of all firmware entities in the complex

PARPERM Restrict/unrestrict nPartitionReconfiguration Privilege

PD Modify default nPartition for this login session

RL Rekey Complex Profile locks

SA Display and set (enable/disable) MP remote access methods

SO Configure security options and access control (user accounts and passwords)

XD MP diagnostics and reset

Source:

Service Processor (GSP or MP) User Guide

How do I install a software with Codeword ?

2013-04-23T12:48:00.000-03:00

You can type de Codeword direct on command line (using as paramter of swinstall):
-x codeword=xxxx and -x customer_id=xxx

Or via the Graphical User Interface (using the [Add New Codeword on "swinstall -i"] choice from the [Actions] menu).

Each Codeword is only applicable to a CD or DVD with a specific part number.

AutoFS - Automount

2013-04-19T09:55:00.002-03:00

The first step is export the FS to be used on NFS server.
If you don't know how to do that, check the link bellow.

Configuring NFS server

Before to configure autoFS in your client is better check if you can see the nfs FS in your client.
# showmount -e <nfs server>
The return will be the list of what is exported on nfs server and who is allowed to mount/access.

If everything is right until this point... configure the autoFS:
Include on /etc/auto_master what you want mount, we are using the FS /user/home in our example.
# vi /etc/auto_master
/users/home /etc/auto_home -nosuid,intr,soft,rsize=32768,wsize=32768

Include on /etc/auto_home the address of your FS (NFS server and mount point):
* <nfs server>:/home/&

Restart automount
/sbin/init.d/nfs.client stop
/sbin/init.d/nfs.client start
automount

Enable the auto start of AutoFS editing /etc/rc.config.d/nfsconf:
NFS_CLIENT=1
AUTOMOUNT=1
AUTOFS=1

Done

LDAP-UX - How to setup LDAP-UX to authenticate on OpenLDAP

2013-04-19T09:42:00.000-03:00

First of all, LDAP-UX does not support updating an OpenLDAP directory, so to get this to work, add the following profile to the LDAP directory (requires the DUAConfig.schema and possibly ldap-printer.schema):

dn: cn=uxprofile,ou=Profiles,dc=example,dc=com
cn: uxprofile
objectClass: DUAConfigProfile
defaultSearchBase: dc=example,dc=com
defaultSearchScope: one
profileTTL: 3600
serviceSearchDescriptor: passwd:OU=People,DC=example,DC=com
serviceSearchDescriptor: group:OU=Group,DC=example,DC=com
authenticationMethod: tls:simple
defaultServerList: <space separated list of LDAP server hosts:ports>

If you don't have the LDAP-UX package installed...

# swinstall -s /yourDepot

Create a key-store:

/opt/ldapux/contrib/bin/certutil -N -d /etc/opt/ldapux

Import the CA cert:
/opt/ldapux/contrib/bin/certutil -A -n ca-cert -t "C,," -d /etc/opt/ldapux -a -i cacert.crt

Configure LDAP-UX:
/opt/ldapux/config/setup
...specify TLS and use port 389.

NOTE: do NOT attempt to extend any sachems -- OpenLDAP does not support this.

To find out if you are working under 32 or 64-bits (PA-RISC)

2013-03-12T12:48:00.002-03:00

You can use the getconf command to get that on PA-RISC:

getconf KERNEL_BITS

You don't need to check that on Itanium, since Itanium is only 64bits.

Rebuild lvmtab

2013-03-12T12:34:00.001-03:00

It's quite easy.

Let's begin with a backup:

# cp -p /etc/lvmtab /etc/lvmtab.orig
Remove the old one:

# rm /etc/lvmtab

Now you are ready to rebuild using the vgscan:

# vgscan -v

Check "Real memory" on pa-risc and Ia64

2013-01-23T20:39:00.000-02:00

I'm listing just one way to check the memory on server but as usual there are many ways to do that.

PA-RISC

# getconf REAL_MEMORY HPUX

ITANIUM

# machinfo | grep -i memory

or

# dmesg | grep mem

Tusc - Process trace "Debug mode"

2013-01-13T12:17:00.001-02:00

- Why this process is running and is taking so much time???!??!

I am sure someday this question will pass for your mind, in order to try find out what is going on we have the possibility to install a software called "tusc" on HP-UX, a similar command in AIX is the truss (it's native on OS). The output can be not so friendly...

Follow an example using tusc to trace the system calls and signal.

# /usr/local/bin/tusc -apf <pid>

How to mount a windows share on HP-UX

2013-01-04T22:30:00.001-02:00

After some time away... here is a new post :-)
and by the way... Happy New Year!!

Requirements:

- User account on Windows box
- Root access on HP-UX box
- cifs patch installed on HP-UX
- Network communication between them (client and server)
- Directory shared on Windows

Check if cifs is running:
# cifsclient status

If it is not running..
# cifsclient start

Create a directory to be used for your mount point and use the bellow command to mount:
# cifsmount //WINDOWSserverHostname/DirectoryShared /YourMountpoint -U username

Check the man pages for more flags to be used with cifsmount command.

Forwarding the syslog to another server on network

2012-10-25T23:25:00.000-02:00

I'm using a linux to receive my logs for this explanation.

LogServer:
usually the syslog conf path for syslog on linux is /etc/sysconfig/syslog (red hat for example)
Setup the syslog on linux with the bellow options:

SYSLOGD_OPTIONS="-m 0 -r"
*.* /var/adm/messages

Refresh the syslog
# kill -HUP syslogPid

HP-UX :
Setup the syslog on HP-UX with the bellow options:
syslog conf path: /etc/syslog.conf
*.debug @LogServer

Get the syslog pid to refresh the process:
ps -ef | grep syslog

# kill -HUP syslogPid

Wrapper - Block the root password change

2012-10-20T16:00:00.000-03:00

For security reason is good dont give the "power" to change the root password for everyone :-)

Create a list of users that you want to deny the change of password.:
# vi /usr/local/etc/passwd_not_allowed
root
bin

Now create the wrapper:
# vi /tmp/passwd
file=/usr/local/etc/passwd_not_allowed
user=$1
grep -q ${user] ${file} && echo "${user} - You don't have access to change this passwd" && exit
/usr/bin/passwd.dist ${User}

Set the right permissions:
# chmod 755 /tmp/passwd

Move the real passwd for another place:
# mv /usr/bin/passwd /usr/bin/passwd.dist

Put your wrapper in the place of passwd:
# mv /tmp/passwd /usr/bin/

Now you can configure a sudo for this script, if you don't want move the passwd bin you can create the wrapper in another place.

Renaming a logical volume

2012-10-01T11:21:00.004-03:00

old name: /dev/vgwow/lvol1
new name: /dev/vgwow/data_lv

# umount /dev/vgwow/lvol1
# ll /dev/vgwow/lvol1                                      take note of the minor ( e.g 0x010001 )
brw-r-----   1 root       root        64 0x010001 Dec 31 17:59 lvol1
#       create new logical volume name
# mknod /dev/vgwow/rdata_lv c 64 0x010001
# vi /etc/fstab                                               ( reflect the new logical volume )
# mount -a

# rmsf /dev/vgwow/lvol1
# rmsf /dev/vgwow/rlvol1

Serviceguard - how to change package IP on line/ off line

2012-07-29T09:08:00.000-03:00

Change package IP address off line

Halt the package
# cmhaltpkg -v <package>

Update control files
/etc/cmcluster/package/package.conf

Propagate the changes manually or use cmapplyconf
(legacy or modular)

Start package
# cmrunpck <package>

Check that the IP was added.
# cmviewcl -v

Change package IP address on line

You can change the IP address while a package is up but there's some risky... but can be done.
The recommended is do it off line to avoid any problems.

Use the command cmmodnet to remove the IP addres and after to add.

Using netstat -in check that the ip address is correct.

Check the cluster status:
# cmviewcl -v

Update the package script, propagate the change to other nodes.

For more infos about cmmodnet check man pages.

Serviceguard - Change node ip address

2012-07-29T08:38:00.000-03:00

**In this situation we are changing just the ip, the subnet stil is the same**

Backup configuration files:

/etc/hosts
/etc/rc.config.d/netconf
/etc/cmcluster/

Move the package(s) to another node
# cmhaltpkg -v <package>
# cmrunpkg -v -n NODE <package>

Remove node from all packages

Run cmapplyconf (or send the configuration files for others nodes manualy)

Stop the node
# cmhaltnode -v <node>

Remove node from cluster configuration

Apply new cluster configuration

Change IP on node
/etc/rc.config.d/netconf
/etc/hosts
Restart the net deamon for apply the new network configuration
# /sbin/init.d/net stop
# /sbin/inti.d/net start

Add node to cluster
The bellow link is another post showing how to include a new node in the cluster running.
http://hp-ux-br.blogspot.com.br/2012/05/adding-new-node-in-running-cluster.html

Apply cluster configuration

Start the node again
# cmrunnode -v <node>

Add node to all relevant packages

Apply package configuration

Move package(s) back to node
# cmrunpkg -v -n NODE <package>
# cmhaltpkg -v <package>

Check cluster status
# cmviewcl -v

Configuring LAN on MP

2012-07-26T11:16:00.000-03:00

This tutorial explain how to change the LAN configuration on MP. You can also leave the DHCP enable if you want use the bootp from your server (or other).

1. Connect to the serial port.
2. At the MP Main Menu, enter CM and press Enter to select command mode.
3. At the command mode prompt, enter LC and press Enter. The screen displays the default LAN configuration values. Write down the default values, or log the information to a file. You may need the information for future troubleshooting.
4. Use the LC command to disable DHCP.
a. From the LC command menu, type D and press Enter.
b. Follow the instructions on the screen to change the DHCP status from Enabled to Disabled.
c. Enter XD -R to reset the iLO MP.
5. Use the LC command to enter information for the IP address, host, subnet mask, gateway parameters, and so on.
6. Enter XD -R to reset the iLO MP.
7. After the iLO MP resets, log in to the iLO MP again and enter CM at the MP:> prompt.
8. Enter LC to confirm that DHCP is disabled and display a list of updated LAN configuration
settings.

Glance Adviser Script - Averaged over # of CPU's

2012-07-21T12:15:00.003-03:00

The following script will return the average CPU utilization (averaged over number of CPU's) for system, user and total utilization. It could easily be modified to be a feed into MRTG for graphing purposes.

Script
#
# Sample glance script showing average CPU utilization across all CPU's
#
headersprinted = 0
total_total = 0
total_sys = 0
total_user = 0
count = 0
# For each CPU
cpu loop {
    # print headers if this is the first row
    if headersprinted == 0 then {
      print "   Sys CPU   User CPU Total CPU"
      headersprinted = 1
    }
    total_total=total_total+GBL_CPU_TOTAL_UTIL
    total_sys=total_sys+GBL_CPU_SYS_MODE_UTIL
    total_user=total_user+GBL_CPU_USER_MODE_UTIL
    count = count + 1
}
print total_sys/count, " ", total_user/count, " ", total_total/count

Output
# glance -j 5 -adviser_only -syntax cpu.cfg -iterations 3
Welcome to GlancePlus

   Sys CPU   User CPU Total CPU
         8         30         38
   Sys CPU   User CPU Total CPU
         5         31         35
   Sys CPU   User CPU Total CPU
         4         24         28

Glance Adviser Script - Detailed Process Gathering

2012-07-21T12:13:00.001-03:00

You must be carefull with this example as it will generate a lot of data very quickly, depending on the interval. I.e. listing all processes every second is a lot of lines in a short period of time.
It would be pretty easy to modify this script to simply count the processes if you wanted to report back to MRTG the number of processes.

Script
process loop {
    if ((proc_cpu_total_util > 0) or ( proc_stop_reason != "SLEEP" ))
then {
    print gbl_statdate, "|", gbl_stattime, "|", proc_cpu_last_used, "|",
proc_mem_virt, "|", proc_mem_res, "|",
proc_cpu_total_util, "|",
proc_stop_reason, "|", proc_disk_logl_io_rate, "|",
proc_proc_id, "|", proc_parent_proc_id, "|",
proc_user_name, "|", proc_proc_name, "|",
        proc_cache_wait_time, "|", proc_cdfs_wait_time, "|",
        proc_disk_subsystem_wait_time, "|", proc_disk_wait_time, "|",
        proc_graphics_wait_time, "|", proc_inode_wait_time, "|",
        proc_ipc_subsystem_wait_time, "|", proc_ipc_wait_time, "|",
proc_jobctl_wait_time, "|", proc_lan_wait_time, "|",
proc_mem_wait_time, "|", proc_msg_wait_time, "|",
proc_nfs_wait_time, "|", proc_other_io_wait_time, "|",
proc_other_wait_time, "|", proc_pipe_wait_time, "|",
proc_pri_wait_time, "|", proc_rpc_wait_time, "|",
proc_sem_wait_time, "|", proc_socket_wait_time, "|",
proc_stream_wait_time, "|", proc_sys_wait_time, "|",
proc_term_io_wait_time
    }
}

Glance Adviser script - Lan statistics

2012-07-21T12:09:00.005-03:00

This example will produce packet level statistics (in, out, collisions, errors...) for every lan interface in the server.

Script

# initialize variables:
netif_to_examine = ""   # lan0 would only report on lan0, etc.
headers_printed = headers_printed
netif loop {
# print information for the selected interface or if null THEN all:
IF (BYNETIF_NAME == netif_to_examine) or
     (netif_to_examine == "") THEN
{
    # print headers the first time through the loop:
    IF headers_printed == 0 THEN
    {
      print "Date     Time    Interface InPkts OutPkts OutQ Colls Errs"
      print "   "
      headers_printed = 1
    }
    # print one line per interface reported:
    print GBL_STATDATE, " ", GBL_STATTIME, " ", BYNETIF_NAME|8,
      BYNETIF_IN_PACKET, BYNETIF_OUT_PACKET,
      BYNETIF_QUEUE, BYNETIF_COLLISION, BYNETIF_ERROR
    # (note that some interface types do not report collisions or errors)
}
}
print " "

Execute your lan script (lan.cfg) now:
# glance -j 5 -adviser_only -syntax lan.cfg -iterations 3

Welcome to GlancePlus

Date     Time    Interface  InPkts OutPkts  OutQ  Colls  Errs
   
04/28/04 15:01:00 lan0          3      2     0      0      0
04/28/04 15:01:00 lan3         35     39     0      0      0
04/28/04 15:01:00 lan6         31     32     0      0      0
04/28/04 15:01:00 lan7         50     31     0      0      0
04/28/04 15:01:00 lan8          0      0     0      0      0
04/28/04 15:01:00 lan4          0      0     0      0      0
04/28/04 15:01:00 lan9          0      0     0      0      0
04/28/04 15:01:00 lan10         0      0     0      0      0
04/28/04 15:01:00 lan11         0      0     0      0      0
04/28/04 15:01:00 lan5          3      2     0      0      0
04/28/04 15:01:00 lo0          26     26     0     na      0
  
04/28/04 15:01:05 lan0         13      7     0      0      0
04/28/04 15:01:05 lan3        173    230     0      0      0
04/28/04 15:01:05 lan6        121    129     0      0      0
04/28/04 15:01:05 lan7        197    142     0      0      0
04/28/04 15:01:05 lan8          1      1     0      0      0
04/28/04 15:01:05 lan4          1      1     0      0      0
04/28/04 15:01:05 lan9          1      1     0      0      0
04/28/04 15:01:05 lan10         1      1     0      0      0
04/28/04 15:01:05 lan11         1      1     0      0      0
04/28/04 15:01:05 lan5         13      7     0      0      0
04/28/04 15:01:05 lo0           3      3     0     na      0
  
04/28/04 15:01:10 lan0         12      7     0      0      0
04/28/04 15:01:10 lan3        151    221     0      0      0
04/28/04 15:01:10 lan6         97    105     0      0      0
04/28/04 15:01:10 lan7        165    126     0      0      0
04/28/04 15:01:10 lan8          1      1     0      0      0
04/28/04 15:01:10 lan4          1      1     0      0      0
04/28/04 15:01:10 lan9          1      1     0      0      0
04/28/04 15:01:10 lan10         1      1     0      0      0
04/28/04 15:01:10 lan11         1      1     0      0      0
04/28/04 15:01:10 lan5         12      7     0      0      0
04/28/04 15:01:10 lo0           0      0     0     na      0

You can redirect the output for a file.