tag:blogger.com,1999:blog-85019896281035984822024-03-08T10:06:18.326-03:00Eduardo Fraga's HP-UX blognixUnknownnoreply@blogger.comBlogger141125tag:blogger.com,1999:blog-8501989628103598482.post-70033098707200694182015-08-10T10:56:00.001-03:002015-08-10T11:29:30.383-03:00Create a patch bundle from multiple depotsFirst, you need to the depots using swcopy to a "central location":<br />
<br />
<i>#swcopy -x enforce_dependencies=false -s /tmp/First.depot \* @ /depot/MyBigDepot</i><br />
<i><br />#swcopy -x enforce_dependencies=false -s /tmp/Second.depot \* @ /depot/MyBigDepot<br /> </i><br />
<i>#swcopy -x enforce_dependencies=false -s /tmp/Third.depot \* @ /depot/MyBigDepot</i><br />
<br />
Second and last, build your depot (The .depot files are actually images of swinstall tapes):<br />
<br />
<br />
<i># swpackage -x media_type=tape -s /depot/MyBigDepot \* @ /tmp/MyBigDepot.depot</i>Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-37729583608194034722015-04-01T12:06:00.002-03:002015-04-01T12:06:44.684-03:00Disk migration - pvmoveMigrate a disk can be necessary during storage migrations or even during a hw problem.<br />
<br />
I will explain here how to do this using pvmove.<br />
<br />
Migrating an entire disk:<br />
<br />
<pre class="screen"><tt class="computeroutput"># </tt><b class="userinput"><tt>pvmove /dev/disk/disk4 /dev/disk/disk5</tt></b></pre>
<pre class="screen"><b class="userinput"><tt> </tt></b></pre>
<pre class="screen"><span class="userinput"></span><b class="userinput"><tt> </tt></b></pre>
<pre class="screen"><b class="userinput"><tt> </tt></b></pre>
The first argument (disk4) represents the source followed by the destination (disk5).<br />
<br />
Ps. You need both disks inside of the same Volume Group.<br />
<pre class="screen"><b class="userinput"><tt> </tt></b></pre>
Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-13244881935506644172015-03-18T16:52:00.000-03:002015-03-18T16:53:48.378-03:00How to clone a HP-UX using a ignite backup?<br />
<br />
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.<br />Details<br />The steps to clone a system using make_net_recovery are:<br />Use make_net_recovery (or the ignite GUI) to create a system recovery archive of the source system.<b> </b><br />
<br />
<b>Login into the Ignite-UX server</b><br />
<br />
If the target system to be installed does not currently have a directory in <b>/var/opt/ignite/clients</b> 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.<br />
<br />
Copy the <b>CINDEX</b> 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 <b>CINDEX</b> file. If the <b>CINDEX</b> 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).<br />
<br />
<b># vi /etc/hosts [Keep the new host name in /etc/hosts file on Ignite server]<br /># cd /var/opt/ignite/clients/src-client<br /># find CINDEX recovery | cpio -pdvma ../target-client</b><br />
<br />
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).<br />
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<br />
<br />
clients:<br />
<b># vi /etc/exports</b><br />
(append :target-client to the end of the source-client's line)<br />
<b># exportfs –av</b><br />
<br />
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.Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-61467950494077190792014-09-24T13:40:00.003-03:002014-09-24T14:07:43.032-03:00Remove / cancel printer jobs<span style="font-family: inherit;">Here is a command to remove all jobs from a printer queue (you need root):</span><br />
<b><span style="font-family: inherit;"></span></b><span style="font-family: inherit;"><b># cancel -e hplj32</b> <i></i></span><br />
<span style="font-family: inherit;"><br /></span>
<span style="font-family: inherit;"></span><span style="font-family: inherit;"><i></i></span><br />
<div style="margin-bottom: 0in;">
<span style="font-family: inherit;">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.</span></div>
<div style="margin-bottom: 0in;">
<span style="font-family: inherit;"><i> </i></span></div>
<div style="margin-bottom: 0in;">
<br />
<span style="font-family: inherit;">Here I am requesting to cancel the hplj32-13 job</span></div>
<div style="margin-bottom: 0in;">
<span style="font-family: inherit;"><b> # cancel </b><b>hplj32-13</b></span></div>
Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-68424458583751184622013-06-09T16:01:00.001-03:002013-06-09T16:01:58.722-03:00Start/Stop EMS and Clean EMS logs - Prevent to resending old eventsThis is very useful when you are getting old error messages, some problem that was fixed and you still receive warning about them.<br /><br />1. Clear all logs in MP, SEL and FPL with the MP SL (System Logs) and the Clear all logs commands.<br /> 2. Stop the EMS deamon:<br />
<strong>/etc/opt/resmon/lbin/monconfig</strong> (selecting<strong> K</strong>)<br /> 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.<br /> 4. Back up and Remove /var/stm/logs/monitor/fpl_em.dat .<br /> 5. Back up and Remove /var/stm/logs/monitor/fpltime.dat .<br /> 6. Back up and Remove /var/stm/logs/monitor/remindersel.dat .<br /> 7. Start the EMS deamon<br />
<strong>/etc/opt/resmon/lbin/monconfig</strong> (enable event monitoring)Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-1443808301564294072013-05-13T18:59:00.001-03:002013-05-13T18:59:36.057-03:00Quick Reference - FTP for dummiesHere is a command line guide reference.<br />
<br />
<strong>help <command></strong><br />
This command provide a short description about a command.<br />
<br /><strong>? </strong><br />
Request help or information about the FTP commands <br />
<br />
<strong>ascii</strong> <br />to set the mode of file transfer to ASCII <br />(this is the default and transmits seven bits per character) <br />
<strong></strong><br />
<strong>binary</strong> <br />to set the mode of file transfer to binary <br />(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) <br />
<br />
<strong>bye</strong> <br />to exit the FTP environment (same as quit) <br />
<br />
<strong>cd</strong> <br />to change directory on the remote machine <br />
<br />
<strong>close</strong> <br />to terminate a connection with another computer <br /> <br /><strong>delete</strong> <br />to delete (remove) a file in the current remote directory (same as rm in UNIX) <br />
<br />
<strong>get</strong> <br />to copy one file from the remote machine to the local machine <br /> <br /><strong>get ABC DEF</strong> <br />copies file ABC in the current remote directory to (or on top of) a file named DEF in your current local directory. <br /> <br /><strong>lcd</strong> <br />to change directory on your local machine (same as UNIX cd) <br />
<br />
<strong>ls</strong> <br />to list the names of the files in the current remote directory <br />
<br />
<strong>mkdir</strong> <br />to make a new directory within the current remote directory <br />
<br />
<strong>mget</strong> <br />to copy multiple files from the remote machine to the local machine; <br /> you are prompted for a y/n answer before transferring each file <br /> <br /><strong>mput</strong> <br />to copy multiple files from the local machine to the remote machine; <br /> you are prompted for a y/n answer before transferring each file <br />
<br />
<strong>open</strong> <br />to open a connection with another computer <br /> <br /><strong>put</strong> <br />to copy one file from the local machine to the remote machine <br />
<strong></strong><br />
<strong>pwd</strong> <br />to find out the pathname of the current directory on the remote machine <br />
<br />
<strong>quit</strong> <br />to exit the FTP environment (same as bye) <br />
<br />
<strong>rmdir</strong> <br />to to remove (delete) a directory in the current remote directory <br /><br />
<strong>!<command></strong><br />
Send a command <em>locally</em> not in the remote server.Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-20587376426037926832013-05-09T21:20:00.000-03:002013-05-09T21:39:26.267-03:00Quick Reference - Data Protector command line<br />
A Data Protector command line (6.11) quick reference, it's quite useful on daily tasks.<br />
<b><br /></b>
<b>omniabort</b><br />
Aborts an active session.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omniamo</b><br />
Starts an automated media operation session.<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>omnib</b><br />
Backs up filesystems, disk images, the Data Protector internal database (IDB),<br />
Microsoft Exchange Server single mailboxes and Public Folders, Microsoft<br />
Exchange Server, Microsoft SQL Server, Microsoft SharePoint Portal Server (SPS),<br />
SAP R/3, SAP DB/MaxDB, Oracle, Informix Server, VMware Virtual Infrastructure<br />
(VMware), Sybase, Lotus, IBM DB2 UDB, NetWare objects, and NDMP objects.<br />
This is the only command supported with the MPE/iX integration.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnicc</b><br />
Handles the Data Protector licensing, reports the number of configured and<br />
available Data Protector licenses, installs the licenses, imports and exports Data<br />
Protector clients, and manages access to secured clients.<br />
Command line interface reference 25This command is available on systems with any Data Protector component<br />
installed.<br />
<br />
<b>omnicellinfo</b><br />
Displays configuration information about the Data Protector cell.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omniclus</b><br />
Manages load balancing in a cluster environment in the event of an application<br />
(Data Protector or other) failover.<br />
This command is available on systems with the Data Protector MS Cluster<br />
Support component installed (Windows systems) and on the Data Protector<br />
Cell Manager (UNIX systems).<br />
<br />
<b>omnicreatedl</b><br />
Creates a Data Protectorbackup specification file (datalist); or an HP<br />
StorageWorks Disk Array XP, HP StorageWorks Virtual Array, or HP<br />
StorageWorks Enterprise Virtual Array Microsoft Exchange Server ZDB backup<br />
specification file (datalist).<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnidb</b><br />
Queries the Data Protector internal database (IDB).<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnidbsmis</b><br />
Executes administrative tasks required for managing the HP StorageWorks<br />
Enterprise Virtual Array (EVA) Command View.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnidbva</b><br />
Queries the ZDB database (VADB) and administers the VA LUN Exclude File,<br />
instant recovery and password information.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnidbvss</b><br />
Queries the VSS database; manages, browses, and lists the items of the VSS<br />
database.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnidbxp</b><br />
Queries the ZDB database (XPDB), manipulates the XP LDEV exclude file, and<br />
configures the HP StorageWorks Disk Array XP command devices usage.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnidownload</b><br />
Downloads information about a backup device and a library from the Data<br />
Protector internal database (IDB).<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omniiso</b><br />
Primarily serves as a pre-exec script to prepare the ISO image file for One Button<br />
Disaster Recovery (OBDR); can also be used as a standalone command to<br />
automate your backup and disaster recovery process.<br />
This command is available on systems with the Data Protector Automatic<br />
Disaster Recovery component installed.<br />
<br />
<b>omnimcopy</b><br />
Makes a copy of a Data Protector medium using Data Protector backup devices<br />
as the source and destination.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omniminit</b><br />
Initializes a Data Protector medium.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnimlist</b><br />
Lists the contents of a Data Protector medium.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnimm</b><br />
Provides media management for Data Protector.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnimnt</b><br />
Responds to a Data Protector mount request for a medium.<br />
Command line interface reference 27This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnimver</b><br />
Verifies data on a medium.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omniobjconsolidate</b><br />
Consolidates Data Protector backup objects into synthetic full backups.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omniobjcopy</b><br />
Creates additional copies of objects backed up with Data Protector on a different<br />
media set.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omniobjverify</b><br />
Verifies Data Protector backup objects, either interactively or using pre-configured<br />
post-backup, or scheduled verification specifications.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnir</b><br />
Restores filesystems, disk images, the Data Protector database (IDB), Microsoft<br />
Exchange Server single mailboxes and Public Folders, Microsoft Exchange Server,<br />
Microsoft SQL Server, Microsoft SharePoint Portal Server (SPS), SAP R/3, SAP<br />
DB/MaxDB, Informix Server, VMware Virtual Infrastructure (VMware), Lotus, IBM<br />
DB2 UDB, NetWare objects, and NDMP objects backed up with Data Protector.<br />
The command is also used to start the instant recovery process. To restore a<br />
Sybase database, refer to the syb_tool man page.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnirpt</b><br />
Generates various reports about the Data Protector environment, for example,<br />
about backup, object copy, object consolidation, and object verification sessions<br />
in a specific time frame, session specifications, media, Data Protector<br />
configuration, and single sessions.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnistat</b><br />
Displays the status of active Data Protector backup and restore sessions.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omniupload</b><br />
Uploads information about a backup device from an ASCII file to the Data<br />
Protector internal database (IDB).<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omniusers</b><br />
Adds or removes Data Protector users to or from an existing Data Protector user<br />
group, or lists the configured Data Protector users. It enables you to use all GUI<br />
functionality on a Cell Manager platform on which the GUI is not available,<br />
using a GUI installed on another system.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>syb_tool</b><br />
A utility used to get ISQL command needed to restore a Sybase database that<br />
was backed up by Data Protector.<br />
This command is available on systems with the Data Protector Sybase<br />
Integration component installed.<br />
<br />
<b>ADMINISTRATIVE COMMANDS (1M):</b><br />
<br />
<b>ob2install</b><br />
Runs remote client installation, uninstallation, upgrade, or check of a client from<br />
the selected Installation Server.<br />
This command is available on the Data Protector Installation Server.<br />
<br />
<b>omnicheck</b><br />
Performs a DNS connections check within a Data Protector cell and lists Data<br />
Protector patches installed on Data Protector clients.<br />
This command is available on systems with any Data Protector component<br />
installed.<br />
<br />
<b>omnidbcheck</b><br />
Checks the consistency of the Data Protector internal database (IDB).<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>omnidbinit</b><br />
Initializes the Data Protector internal database (IDB).<br />
This command is available on the Data Protector Cell Manager.<br />
Command line interface reference 29omnidbrestore<br />
Restores the Data Protector internal database (IDB).<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>omnidbupgrade</b><br />
Converts filenames in the IDB to the new internal character encoding used in<br />
Data Protector A.06.11 and thus enables the correct handling of non-ASCII<br />
characters in filenames in the Data Protector GUI.<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>omnidbutil</b><br />
Handles various Data Protector internal database (IDB) maintenance tasks.<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>omnidlc</b><br />
Gathers or deletes Data Protector debug, log, and getinfo files from the Data<br />
Protector cell or from a MoM environment.<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>omnidr</b><br />
A general purpose Data Protector disaster recovery command. Based on its input,<br />
it decides on what type of restore to perform (online restore using omnir or<br />
offline restore using omniofflr), as well as how to perform the restore (whether<br />
or not to use live OS features).<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnihealthcheck</b><br />
Checks the status of Data Protector services, the consistency of the Data Protector<br />
internal database (IDB), and if at least one backup of the IDB exists.<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>omniinetpasswd</b><br />
Manages the local Data Protector Inet configuration on Windows systems where<br />
the Inet process must be run under a specific user account, and sets a user account<br />
to be used by the Installation Server during remote installation.<br />
This command is available on systems with any Data Protector component<br />
installed.<br />
<br />
<b>omniinstlic</b><br />
Starts the HP AutoPass utility or synchronizes the Data Protector licenses between<br />
Data Protector and HP AutoPass.<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>omniintconfig.pl</b><br />
30Configures, updates configuration parameters, and checks the configuration of<br />
one or multiple Oracle databases.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnikeymigrate</b><br />
Helps you migrate your existing keystore file from Data Protector A.06.00 client<br />
system and imports it into the central keystore file on the Data Protector A.06.11<br />
Cell Manager.<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>omnikeytool</b><br />
Manages keys used for encryption.<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>omnimigrate.pl</b><br />
Helps you migrate your existing Cell Manager from a PA-RISC architecture based<br />
HP-UX 11.x system to an HP-UX 11.23 system for the Intel Itanium 2 (IA-64)<br />
architecture.<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>omniofflr</b><br />
Enables restore of any type of Data Protector backup object in the absence of a<br />
working Data Protector internal database (IDB).<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omniresolve</b><br />
Resolves a filesystem object or a list of filesystem objects and writes the results<br />
to the standard output or to a Unicode file.<br />
This command is available on systems with any Data Protector integration<br />
component installed.<br />
<br />
<b>omnirsh</b><br />
Returns the hostnames of the physical and virtual nodes for the specified cluster<br />
hostname, or returns the cell information stored in the cell_info file on the specified<br />
cluster.<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>omnisetup.sh</b><br />
Installs or upgrades a Data Protector UNIX Cell Manager, Installation Server, or<br />
client system locally.<br />
This command is available on the Data Protector installation DVD-ROMs for UNIX<br />
systems.<br />
<br />
<b>omnisrdupdate</b><br />
Updates the System Recovery Data (SRD) file.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>omnisv</b><br />
Starts, stops, or displays the status of Data Protector daemons (HP-UX, Solaris,<br />
or Linux systems) or services (Windows systems).<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>omnitrig</b><br />
Triggers Data Protector scheduled backups.<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>sanconf</b><br />
Auto-configures a library, modifies an existing library or drive configuration, or<br />
removes drives from a library configuration, within a SAN environment.<br />
This command is available on systems with the Data Protector User Interface<br />
component installed.<br />
<br />
<b>upgrade_cm_from_evaa</b><br />
Upgrades the EVADB entries created by the HP StorageWorks EVA Agent (legacy)<br />
to the SMISDB entries created by the HP StorageWorks EVA SMI-S Agent.<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>util_cmd</b><br />
Sets, retrieves or lists the parameters stored in the Data Protector Oracle, SAP<br />
R/3, VMware Virtual Infrastructure (VMware), Informix, and Sybase configuration<br />
files.<br />
This command is available on systems with any Data Protector component<br />
installed.<br />
<br />
<b>util_oracle8.pl</b><br />
Configures an Oracle database and prepares the environment for backup, and<br />
checks the configuration of an Oracle database.<br />
This command is available on systems with the Data Protector Oracle<br />
Integration component installed.<br />
<br />
<b>util_vmware.exe</b><br />
Configures a VMware datacenter, checks the configuration of a VMware<br />
datacenter, and lists all configured VMware datacenters.<br />
This command is available on systems with the Data Protector VMware<br />
Integration component installed.<br />
<br />
<b>winomnimigrate.pl</b><br />
Helps you migrate your existing Cell Manager from a 32-bit Windows system<br />
to a 64-bit Windows system, or from a 64-bit Windows system to 64-bit Windows<br />
Server 2008.<br />
This command is available on the Data Protector Cell Manager.<br />
COMMAND-LINE UTILITIES (1M):<br />
<br />
<b>cjutil</b><br />
Starts, stops, and queries the Windows Change Journal.<br />
This command is available on systems with the Data Protector Disk Agent<br />
component installed.<br />
<br />
<b>NNMpost.ovpl</b><br />
A script with no arguments that resumes the eight processes paused by<br />
<br />
<b>NNMpre.ovpl.</b><br />
This command is available on systems with the Data Protector HP Network<br />
Node Manager Integration component installed.<br />
<br />
<b>NNMpre.ovpl</b><br />
Starts NNM embedded database backup.<br />
This command is available on systems with the Data Protector HP Network<br />
Node Manager Integration component installed.<br />
<br />
<b>NNMScript.exe</b><br />
Finds the location of the NNM Perl compiler and the NNMpre.ovpl and<br />
NNMpost.ovpl scripts and starts the two scripts.<br />
This command is available on systems with the Data Protector HP Network<br />
Node Manager Integration component installed.<br />
<br />
<b>omnicjutil</b><br />
Remotely controls and administers the Windows Change Journal on Windows<br />
clients.<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>omnistoreapputil</b><br />
Acts as a user interface to Storage Appliances, such as VLS.<br />
This command is available on the Data Protector Cell Manager.<br />
<br />
<b>uma</b><br />
Controls the robotics of SCSI compliant autochangers.<br />
This command is available on systems with the Data Protector General Media<br />
Agent or NDMP Media Agent component installed.<br />
<br />
Source: <a href="http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01631222/c01631222.pdf" target="_blank">Command line interface reference</a>Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-53813959017942726072013-05-04T14:13:00.003-03:002013-05-04T14:14:30.019-03:00MP commands<br />
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.<br />
<div>
<div>
For details on these commands, use the help (HE: Help) feature at the service processor Main</div>
<div>
menu. Enter the command name at the MP:HELP or GSP:HELP prompt for syntax, restrictions,</div>
<div>
and other information.</div>
</div>
<div>
<br /></div>
<div>
<div>
<b>Service Processor (MP or GSP) Command Reference</b></div>
<div>
Command Description</div>
<div>
<b>BO</b> Boot an nPartition past Boot is Blocked (BIB)</div>
<div>
<b>DF</b> Display FRU information of an entity</div>
<div>
<b>MA</b> Return to the Main menu</div>
<div>
<b>MR</b> Modem reset</div>
<div>
<b>PCIOLAD</b> Activate/deactivate a PCI card</div>
<div>
<b>PE</b> Power entities on or off</div>
<div>
<b>RE</b> Reset entity</div>
<div>
Reset an nPartition for reconfiguration; the nPartition remains inactive, in the shutdown</div>
<div>
for reconfig state</div>
<div>
<b>RR</b></div>
<div>
<b>RS</b> Reset an nPartition</div>
<div>
<b>TC</b> Send a TOC signal to an nPartition</div>
<div>
<b>TE</b> Broadcast a message to all users of the MP Command Handler</div>
<div>
<b>VM</b> Margin the voltage in a cabinet</div>
<div>
<b>WHO</b> Display a list of MP connected users</div>
<div>
<b>CP</b> Display nPartition cell assignments</div>
<div>
<b>HE</b> Display the list of available commands</div>
<div>
<b>IO</b> Display IO chassis/cell connectivity</div>
<div>
<b>LS</b> Display LAN connected console status</div>
<div>
<b>MS</b> Display the status of the modem</div>
<div>
<b>PS</b> Display detailed power and hardware configuration status</div>
<div>
<b>SYSREV</b> Display revisions of all firmware entities in the complex</div>
<div>
<b>PARPERM</b> Restrict/unrestrict nPartitionReconfiguration Privilege</div>
<div>
<b>PD</b> Modify default nPartition for this login session</div>
<div>
<b>RL</b> Rekey Complex Profile locks</div>
<div>
<b>SA</b> Display and set (enable/disable) MP remote access methods</div>
<div>
<b>SO</b> Configure security options and access control (user accounts and passwords)</div>
<div>
<b>XD</b> MP diagnostics and reset</div>
</div>
<div>
<br /></div>
<div>
Source:</div>
<div>
<br /></div>
<div>
<a href="http://www.blogger.com/"><span id="goog_507934957"></span>Service Processor (GSP or MP) User Guide<span id="goog_507934958"></span></a></div>
<div>
<br /></div>
<div>
<br /></div>
Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-15280897606609309372013-04-23T12:48:00.000-03:002013-04-23T12:50:51.650-03:00How do I install a software with Codeword ?You can type de Codeword direct on command line (using as paramter of <b>swinstall</b>):<br />
<b>-x codeword=xxxx and -x customer_id=xxx</b><br />
<br />
Or via the Graphical User Interface (using the [Add New <b>Codeword</b> on <b>"swinstall -i"</b>] choice from the [Actions] menu).<br />
<br />
Each <b>Codeword</b> is only applicable to a CD or DVD with a specific part number.Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-88376966938826031302013-04-19T09:55:00.002-03:002013-04-19T10:03:26.190-03:00AutoFS - Automount<br />
The first step is export the FS to be used on NFS server.<br />
If you don't know how to do that, check the link bellow.<br />
<br />
<b><a href="http://hp-ux-br.blogspot.com/search/label/NFS">Configuring NFS server</a></b><br />
<br />
Before to configure autoFS in your client is better check if you can see the nfs FS in your client.<br />
<b># showmount -e <nfs server></b><br />
The return will be the list of what is exported on nfs server and who is allowed to mount/access.<br />
<br />
If everything is right until this point... configure the autoFS:<br />
Include on /etc/auto_master what you want mount, we are using the FS /user/home in our example.<br />
<b># vi /etc/auto_master</b><br />
/users/home /etc/auto_home -nosuid,intr,soft,rsize=32768,wsize=32768<br />
<br />
Include on <b>/etc/auto_home </b>the address of your FS (NFS server and mount point):<br />
* <nfs server>:/home/&<br />
<br />
Restart automount<br />
/sbin/init.d/nfs.client stop<br />
/sbin/init.d/nfs.client start<br />
automount<br />
<br />
<br />
<br />
Enable the auto start of AutoFS editing /etc/rc.config.d/nfsconf:<br />
NFS_CLIENT=1<br />
AUTOMOUNT=1<br />
AUTOFS=1<br />
<br />
Done<br />
<br />Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-48156585442501047382013-04-19T09:42:00.000-03:002013-04-19T09:42:17.548-03:00LDAP-UX - How to setup LDAP-UX to authenticate on OpenLDAPFirst 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):<br />
<br />
<br />
<pre style="background-color: #f9f9f9; border: 1px dashed rgb(47, 111, 171); line-height: 1.1em; padding: 1em;">dn: cn=uxprofile,ou=Profiles,dc=<b>example</b>,dc=com
cn: uxprofile
objectClass: DUAConfigProfile
defaultSearchBase: dc=example,dc=com
defaultSearchScope: one
profileTTL: 3600
serviceSearchDescriptor: passwd:OU=People,DC=<b>example</b>,DC=com
serviceSearchDescriptor: group:OU=Group,DC=<b>example</b>,DC=com
authenticationMethod: tls:simple
defaultServerList: <b><space separated list of LDAP server hosts:ports></b></pre>
<br />
<br />
<br />
If you don't have the LDAP-UX package installed...<br />
<br />
# <b>swinstall -s /yourDepot</b><br />
<br />
Create a key-store:<br />
<br />
<b>/opt/ldapux/contrib/bin/certutil -N -d /etc/opt/ldapux</b><br />
<br />
Import the CA cert:<br />
<b>/opt/ldapux/contrib/bin/certutil -A -n ca-cert -t "C,," -d /etc/opt/ldapux -a -i cacert.crt</b><br />
<b><br /></b>
Configure LDAP-UX:<br />
<b>/opt/ldapux/config/setup</b><br />
...specify TLS and use port 389.<br />
<br />
NOTE: do NOT attempt to extend any sachems -- OpenLDAP does not support this.<br />
Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-29032285571784751852013-03-12T12:48:00.002-03:002013-03-21T22:21:51.137-03:00To find out if you are working under 32 or 64-bits (PA-RISC)You can use the getconf command to get that on PA-RISC:<br />
<br />
<strong>getconf KERNEL_BITS</strong><br />
<strong></strong><br />
You don't need to check that on Itanium, since Itanium is only 64bits.<br />
<br />Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-91683673827156892152013-03-12T12:34:00.001-03:002013-03-12T12:35:06.608-03:00Rebuild lvmtabIt's quite easy.<br />
<br />
Let's begin with a backup:<br />
<br />
<strong># cp -p /etc/lvmtab /etc/lvmtab.orig</strong><br />
Remove the old one:<br />
<br />
<strong># rm /etc/lvmtab</strong><br />
<br />
Now you are ready to rebuild using the vgscan:<br />
<br />
<strong># vgscan -v</strong>Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-1780221079304056112013-01-23T20:39:00.000-02:002013-01-23T20:39:14.063-02:00Check "Real memory" on pa-risc and Ia64I'm listing just one way to check the memory on server but as usual there are many ways to do that.<br />
<br />
PA-RISC<br />
<br />
<em># getconf REAL_MEMORY HPUX </em><br />
<br />
ITANIUM<br />
<br />
# machinfo | grep -i memory<br />
<br />or<br />
<br /># dmesg | grep mem Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-45967605810874427442013-01-13T12:17:00.001-02:002013-05-09T21:02:22.410-03:00Tusc - Process trace "Debug mode"- Why this process is running and is taking so much time???!??!<br />
<br />
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...<br />
<br />
Follow an example using tusc to trace the system calls and signal.<br />
<br />
<em># /usr/local/bin/tusc -apf <pid></em>Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-53909340220667433752013-01-04T22:30:00.001-02:002013-01-04T22:32:42.209-02:00How to mount a windows share on HP-UX After some time away... here is a new post :-)<br />
and by the way... Happy New Year!!<br />
<br />
Requirements:<br />
<br />
- User account on Windows box<br />
- Root access on HP-UX box<br />
- cifs patch installed on HP-UX<br />
- Network communication between them (client and server)<br />
- Directory shared on Windows<br />
<br />
Check if cifs is running:<br />
<em># cifsclient status</em><br />
<br />
If it is not running..<br />
<em># cifsclient start</em><br />
<br />
Create a directory to be used for your mount point and use the bellow command to mount:<br />
<em># cifsmount //WINDOWSserverHostname/DirectoryShared /YourMountpoint -U username</em> <br />
<br />
Check the man pages for more flags to be used with cifsmount command.Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-35257267023092095932012-10-25T23:25:00.000-02:002012-10-25T23:43:52.260-02:00Forwarding the syslog to another server on networkI'm using a linux to receive my logs for this explanation.<br />
<br />
LogServer:<br />
usually the syslog conf path for syslog on linux is <strong>/etc/sysconfig/syslog </strong>(red hat for example)<br />
Setup the syslog on linux with the bellow options:<br />
<br />
<em>SYSLOGD_OPTIONS="-m 0 -r"</em><br />
<em>*.* /var/adm/messages</em><br />
<br />
Refresh the syslog<br />
<em># kill -HUP syslogPid</em><br />
<br />
HP-UX :<br />
Setup the syslog on HP-UX with the bellow options:<br />
syslog conf path: <strong>/etc/syslog.conf</strong><br />
<em>*.debug @LogServer</em><br />
<br />
Get the syslog pid to refresh the process:<br />
<em>ps -ef | grep syslog</em><br />
<br />
<em># kill -HUP syslogPid</em>Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-40726069434358940632012-10-20T16:00:00.000-03:002012-10-25T19:48:14.846-02:00Wrapper - Block the root password changeFor security reason is good dont give the "power" to change the root password for everyone :-)<br />
<br />
Create a list of users that you want to deny the change of password.:<br />
<em># vi /usr/local/etc/passwd_not_allowed <br />root</em><br />
<em>bin</em><br />
<br />
Now create the wrapper:<br />
<em># vi /tmp/passwd</em><br />
<em>file=/usr/local/etc/passwd_not_allowed <br />user=$1 <br />grep -q ${user] ${file} && echo "${user} - You don't have access to change this passwd" && exit<br />/usr/bin/passwd.dist ${User}</em><br />
<br />
Set the right permissions:<br />
<em># chmod 755 /tmp/passwd</em><br />
<br />
Move the real passwd for another place:<br />
<em># mv /usr/bin/passwd /usr/bin/passwd.dist</em><br />
<br />
Put your wrapper in the place of passwd:<br />
<em># mv /tmp/passwd /usr/bin/</em><br />
<br />
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.Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-17024067347495747062012-10-01T11:21:00.004-03:002012-10-01T11:26:16.348-03:00Renaming a logical volumeold name: /dev/vgwow/lvol1<br />
new name: /dev/vgwow/data_lv<br />
<br />
# umount /dev/vgwow/lvol1<br />
# ll /dev/vgwow/lvol1 take note of the minor ( e.g 0x010001 )<br />
brw-r----- 1 root root <strong>64 0x010001</strong> Dec 31 17:59 lvol1<br />
# create new logical volume name<br />
# mknod /dev/vgwow/rdata_lv c <strong>64 0x010001</strong><br />
# vi /etc/fstab ( reflect the new logical volume )<br />
# mount -a<br />
<br />
# rmsf /dev/vgwow/lvol1<br />
# rmsf /dev/vgwow/rlvol1 Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-75993409584770519392012-07-29T09:08:00.000-03:002012-07-29T12:58:14.725-03:00Serviceguard - how to change package IP on line/ off line<strong>Change package IP address off line</strong><br />
<br />
Halt the package<br />
<em># cmhaltpkg -v <package></em><br />
<br />
Update control files<br />
<em>/etc/cmcluster/package/package.conf</em><br />
<br />
Propagate the changes manually or use cmapplyconf<br />
(legacy or modular)<br />
<br />
Start package<br />
<em># cmrunpck <package></em><br />
<br />
Check that the IP was added.<br />
<em># cmviewcl -v</em><br />
<br />
<strong>Change package IP address on line</strong><br />
<br />
You can change the IP address while a package is up but there's some risky... but can be done.<br />
The recommended is do it off line to avoid any problems.<br />
<br />
Use the command <em>cmmodnet</em> to remove the IP addres and after to add.<br />
<br />
Using <em>netstat -in</em> check that the ip address is correct.<br />
<br />
Check the cluster status:<br />
<em># cmviewcl -v</em><br />
<em><br /></em>Update the package script, propagate the change to other nodes.<br />
<br />
For more infos about cmmodnet check man pages.Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-75153947478280304702012-07-29T08:38:00.000-03:002012-07-29T08:49:03.297-03:00Serviceguard - Change node ip address**In this situation we are changing just the ip, the subnet stil is the same**<br />
<br />
<strong>Backup configuration files:</strong><br />
<br />
<em>/etc/hosts</em><br />
<em>/etc/rc.config.d/netconf</em><br />
<em>/etc/cmcluster/</em><br />
<br />
<strong>Move the package(s) to another node</strong><br />
<em># cmhaltpkg -v <package></em><br />
<em># cmrunpkg -v -n NODE <package></em><br />
<br />
<strong>Remove node from all packages</strong><br />
<br />
<strong>Run <em>cmapplyconf</em> (or send the configuration files for others nodes manualy)</strong><br />
<br />
<strong>Stop the node</strong><br />
<em># cmhaltnode -v <node></em><br />
<br />
<strong>Remove node from cluster configuration</strong><br />
<br />
<strong>Apply new cluster configuration</strong><br />
<br />
<strong>Change IP on node</strong><br />
<em>/etc/rc.config.d/netconf</em><br />
<em>/etc/hosts</em><br />
Restart the net deamon for apply the new network configuration<br />
<em># /sbin/init.d/net stop<br /># /sbin/inti.d/net start</em><br />
<br />
<strong>Add node to cluster</strong><br />
The bellow link is another post showing how to include a new node in the cluster running.<br />
<a href="http://hp-ux-br.blogspot.com.br/2012/05/adding-new-node-in-running-cluster.html">http://hp-ux-br.blogspot.com.br/2012/05/adding-new-node-in-running-cluster.html</a><br />
<br />
<strong>Apply cluster configuration</strong><br />
<br />
<strong>Start the node again</strong><br />
<em># cmrunnode -v <node></em><br />
<br />
<strong>Add node to all relevant packages</strong><br />
<br />
<strong>Apply package configuration</strong><br />
<br />
<strong>Move package(s) back to node</strong><br />
<em># cmrunpkg -v -n NODE <package></em><br />
<em># cmhaltpkg -v <package></em><br />
<br />
<strong>Check cluster status</strong><br />
<em># cmviewcl -v</em>Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-35686735539809502152012-07-26T11:16:00.000-03:002012-07-26T11:16:00.924-03:00Configuring LAN on MPThis 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).<br />
<br />
1. Connect to the serial port.<br />2. At the MP Main Menu, enter CM and press Enter to select command mode.<br />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.<br />4. Use the LC command to disable DHCP.<br />a. From the LC command menu, type D and press Enter.<br />b. Follow the instructions on the screen to change the DHCP status from Enabled to Disabled.<br />c. Enter XD -R to reset the iLO MP.<br />5. Use the LC command to enter information for the IP address, host, subnet mask, gateway parameters, and so on.<br />6. Enter XD -R to reset the iLO MP.<br />7. After the iLO MP resets, log in to the iLO MP again and enter CM at the MP:> prompt.<br />8. Enter LC to confirm that DHCP is disabled and display a list of updated LAN configuration<br />settings.Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-89705853303896145512012-07-21T12:15:00.003-03:002012-07-21T12:15:50.994-03:00Glance Adviser Script - Averaged over # of CPU'sThe 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.<br />
<br />
Script<br /><em>#<br /># Sample glance script showing average CPU utilization across all CPU's<br /># </em><br />
<em>headersprinted = 0<br />total_total = 0 <br />total_sys = 0 <br />total_user = 0 <br />count = 0</em><br />
<em># For each CPU<br />cpu loop {<br /> # print headers if this is the first row<br /> if headersprinted == 0 then {<br /> print " Sys CPU User CPU Total CPU"<br /> headersprinted = 1<br /> }<br /> total_total=total_total+GBL_CPU_TOTAL_UTIL<br /> total_sys=total_sys+GBL_CPU_SYS_MODE_UTIL<br /> total_user=total_user+GBL_CPU_USER_MODE_UTIL<br /> count = count + 1<br /> }<br />print total_sys/count, " ", total_user/count, " ", total_total/count</em><br />
<br />
Output<br /><em># glance -j 5 -adviser_only -syntax <strong>cpu.cfg</strong> -iterations 3</em><br />
Welcome to GlancePlus <br />
<br /> Sys CPU User CPU Total CPU<br /> 8 30 38<br /> Sys CPU User CPU Total CPU<br /> 5 31 35<br /> Sys CPU User CPU Total CPU<br /> 4 24 28Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-85450494424280089832012-07-21T12:13:00.001-03:002012-07-21T12:13:44.152-03:00Glance Adviser Script - Detailed Process Gathering<strong>You must be carefull with this example as it will generate a lot of data very quickly</strong>, depending on the interval. I.e. listing all processes every second is a lot of lines in a short period of time.<br />
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.<br />
<br />
Script<br />
<em>process loop {</em><br />
<em> if ((proc_cpu_total_util > 0) or ( proc_stop_reason != "SLEEP" ))<br /> then {<br /> print gbl_statdate, "|", gbl_stattime, "|", proc_cpu_last_used, "|",<br /> proc_mem_virt, "|", proc_mem_res, "|",<br /> proc_cpu_total_util, "|",<br /> proc_stop_reason, "|", proc_disk_logl_io_rate, "|",<br /> proc_proc_id, "|", proc_parent_proc_id, "|", <br /> proc_user_name, "|", proc_proc_name, "|", <br /> proc_cache_wait_time, "|", proc_cdfs_wait_time, "|", <br /> proc_disk_subsystem_wait_time, "|", proc_disk_wait_time, "|", <br /> proc_graphics_wait_time, "|", proc_inode_wait_time, "|", <br /> proc_ipc_subsystem_wait_time, "|", proc_ipc_wait_time, "|", <br /> proc_jobctl_wait_time, "|", proc_lan_wait_time, "|", <br /> proc_mem_wait_time, "|", proc_msg_wait_time, "|", <br /> proc_nfs_wait_time, "|", proc_other_io_wait_time, "|", <br /> proc_other_wait_time, "|", proc_pipe_wait_time, "|", <br /> proc_pri_wait_time, "|", proc_rpc_wait_time, "|",<br /> proc_sem_wait_time, "|", proc_socket_wait_time, "|",<br /> proc_stream_wait_time, "|", proc_sys_wait_time, "|",<br /> proc_term_io_wait_time<br /> }<br />}</em>Unknownnoreply@blogger.comtag:blogger.com,1999:blog-8501989628103598482.post-75041065054241275142012-07-21T12:09:00.005-03:002012-07-21T12:09:59.607-03:00Glance Adviser script - Lan statisticsThis example will produce packet level statistics (in, out, collisions, errors...) for every lan interface in the server.<br />
<br />
Script<br />
<br /># initialize variables:<br />
<em>netif_to_examine = "" # lan0 would only report on lan0, etc.<br />headers_printed = headers_printed</em><br />
<em>netif loop {<br /> </em># print information for the selected interface or if null THEN all:<br /><em> IF (BYNETIF_NAME == netif_to_examine) or<br /> (netif_to_examine == "") THEN<br /> {</em><br />
<em> </em># print headers the first time through the loop:<br /><em> IF headers_printed == 0 THEN<br /> {</em><br />
<em> print "Date Time Interface InPkts OutPkts OutQ Colls Errs"<br /> print " "</em><br />
<em> headers_printed = 1</em><br />
<em> }</em><br />
# print one line per interface reported:<br />
<em> print GBL_STATDATE, " ", GBL_STATTIME, " ", BYNETIF_NAME|8,</em><br />
<em> BYNETIF_IN_PACKET, BYNETIF_OUT_PACKET,</em><br />
<em> BYNETIF_QUEUE, BYNETIF_COLLISION, BYNETIF_ERROR</em><br />
# (note that some interface types do not report collisions or errors)<br />
<em> }</em><br />
<em>}<br />print " "</em><br />
<br />
Execute your lan script (lan.cfg) now:<br />
<em># glance -j 5 -adviser_only -syntax lan.cfg -iterations 3</em><br />
<br />
Welcome to GlancePlus <br />
<pre>
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</pre>
<br />
You can redirect the output for a file.Unknownnoreply@blogger.com