Tag Archives: install

Using AIX commands to install a firmware fix permanently

You can install a firmware fix permanently by using either the flash command or the AIX diagnostic service aids.

Note: To perform this task, you must meet the following criteria:

  • You must have root user authority.
  • You must start your server from the temporary side. For details, see Working with the temporary and permanent side of the service processor.

Using the flash command

At an AIX command prompt, type the following:

/usr/lpp/diagnostics/bin/update_flash -c

The update_flash -c command might run for 10 or more minutes.

Using the AIX diagnostic service aids

  1. At the AIX command prompt, type
  2. Initialize the terminal type, if requested.
  3. On the function selection screen, select Tasks and Service Aids.
  4. On the task selection screen, scroll to the bottom of the list of options, and select Update and Manage Flash.
  5. Select Commit the Temporary Image, and press Enter. The process might run for 10 or more minutes.

Linux Install & configure Squid in three easy steps

  1. Squid configuration so that it will act as a transparent proxy


  2. Iptables configuration

    • Configure system as router
    • Forward all http requests to 3128 (DNAT)
  3. Run scripts and start squid service

First, Squid server installed (use up2date squid) and configured by adding following directives to file:
# vi /etc/squid/squid.conf

Modify or add following squid directives:

acl all src
acl manager proto cache_object
acl localhost src
acl to_localhost dst
acl SSL_ports port 443
acl Safe_ports port 80          # http
acl Safe_ports port 21          # ftp
acl Safe_ports port 443         # https
acl Safe_ports port 70          # gopher
acl Safe_ports port 210         # wais
acl Safe_ports port 1025-65535  # unregistered ports
acl Safe_ports port 280         # http-mgmt
acl Safe_ports port 488         # gss-http
acl Safe_ports port 591         # filemaker
acl Safe_ports port 777         # multiling http
http_access allow manager localhost
http_access deny manager
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access allow localhost
http_access allow all
icp_access allow all
http_port 3128
hierarchy_stoplist cgi-bin ?
access_log /var/log/squid/access.log squid
acl QUERY urlpath_regex cgi-bin ?
cache deny QUERY
refresh_pattern ^ftp:           1440    20%     10080
refresh_pattern ^gopher:        1440    0%      1440
refresh_pattern .               0       20%     4320
acl apache rep_header Server ^Apache
broken_vary_encoding allow apache
coredump_dir /var/spool/squid



  • acl all src  : Access control list, only allow LAN computers to use squid
  • http_access allow localhost: Squid access to LAN and localhost ACL only
  • http_access allow all: — same as above —

Here is the complete listing of squid.conf for your reference grep will remove all comments and sed will remove all empty lines:

# grep -v "^#" /etc/squid/squid.conf | sed -e '/^$/d'


Iptables configuration


Next, I had added following rules to forward all http requests (coming to port 80) to the Squid server port 3128 :
iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 80 -j DNAT --to
iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 3128

How to check and install missing perl modules

  • Check if module is installed. Errors mean missing module.

    # perl -MModule::Name -e 1
  • See documentation of the module if installed.
    # perldoc Module::Name
  • Open CPAN shell
    # perl -MCPAN -e shell
  • To reconfigure the shell if needed.
    cpan>o conf init
  • Install an available module.
    cpan> install HTML::Template
  • You can run the Perl CPAN module via command line perl and get it installed in a single line:

# perl -MCPAN -e ‘install HTML::Template

  • Force install if test fails.
    cpan> force install Module::Name
  • To manual install perl modules. Unzip and go to module directory.

# tar -zxvf HTML-Template-2.8.tar.gz

  • # perl Makefile.PL
    # make
    # make test
    # make install

Aix: Install and Configuration HACMP [ Overview]

1. Overview

The High Availability (HA) feature of application allows a properly configured application system to automatically recover from a number of possible failures, with the goal of eliminating all single points of failure in the system. The same functionality can be used to minimize the impact of regularly scheduled maintenance and/or software upgrades.

The High Availability feature is only available on AIX platforms.

Failures of the following components will be protected against when using a properly configured HA application system:

  • Core server
  • Network-related
  • adapters
  • cables
  • Disk-related
  • adapters
  • cables
  • disks
  • Power-related
  • node power supply
  • disk power supply
  • power distribution strip

High availability is not the same as fault tolerance. The failures above are “protected against” from the standpoint that the HA application system will be able to return to an operational state without intervention when any one of the above failures occur. There certainly may be some down-time, especially when the core server fails (crashes).

After a recovery, application will function properly, but it will no longer be in a Highly Available state. A subsequent failure may not be recoverable. For instance, if the core server crashes and the backup takes over, there is no longer a backup node. It will be necessary to correct the original failure in order to return the system to a Highly Available state.

1.1 Architecture

The following diagram shows the necessary components for an HA application configuration:

Figure G-1 HA application Architecture

This diagram does not include the power system, but it does have several features that are very important:

  • At any point in time, either Node 1 or Node 2 can act as the core application server.
  • The two shared disk busses are mirrored to one another and accessed by each node using separate adapter cards so that any single failure (disk, adapter, or bus) will result in accessibility of at least one good copy of the data.
  • Each node has two connections to the ethernet network. One is a “standby” that can take over the IP and hardware addresses of the primary adapter in case of failure.
  • There is an RS-232 serial cable connecting Node 1 and Node 2 to enable communication even in the event that the main network fails.