HP Instant Capacity Version 10.x User Guide (762794-001, March 2014)

www.hp.com/go/bizsupport:
• For HP-UX 11i v1: Installing and Administering Internet Services available at:
www.hp.com/go/hpux-core-docs-11iv1
• For HP-UX 11i v2 and 11i v3: HP-UX Internet Services Administrator's Guide available at:
www.hp.com/go/hpux-networking-docs
On partitionable systems
To enable asset reporting, configure email connectivity on each partition. This makes it easier to
redistribute cores across partitions later (that is, load balance). For details, see “Load-balancing
active cores” (page 43).
IMPORTANT: The email is rejected by the mail servers at HP if, for email sent from the Instant
Capacity system to HP, the domain name in the From field is not DNS resolvable by HP. Also,
because asset reports are encrypted and must be decrypted at the HP portal, the decryption process
might not work correctly if outgoing email sent from your system is automatically modified in any
way, for example, to include a privacy notice.
Email configuration
Before you start
If you decide to enable email connectivity, your Instant Capacity system must be network accessible
to HP mail servers that are outside your company's firewalls. If your Instant Capacity system is on
an isolated network, email from the system does not reach HP. This causes your system to be out
of compliance with your Instant Capacity contract if you are using temporary capacity (TiCAP).
The sendmail application
The sendmail application is used by the Instant Capacity software to send encrypted email messages
from your system to HP. The sendmail daemon, if running, can also be used to receive email. For
purposes of this email configuration, only the ability to send email is required.
Mail applications invoke sendmail to send email. The configuration file, /etc/mail/
sendmail.cf, offers tremendous flexibility.
Overview of email routing across the internet
When the Instant Capacity software uses sendmail to send email to HP, sendmail determines where
it should initially send the email (the first hop). Mail often goes through multiple systems (hops)
before it reaches the final destination. To determine the first hop for the email, sendmail uses one
of the following:
• The email is routed to a mail relay host if it is configured in the /etc/mail/sendmail.cf
configuration file. This is the easiest implementation and can be done with just a one line
change (DS) to the default /etc/mail/sendmail.cf file.
Note that the relay host must be configured to properly route (forward) the email to the final
destination.
• DNS MX records — this method requires that the Instant Capacity system be in an environment
(network) where DNS (Domain Name Server) is operating and properly configured. sendmail
on the system queries a DNS server for the name of the email server to forward the email to
(for the first hop) in order for the email to reach the final destination (hp.com).
In all cases, the following requirements must be met:
• HP mail servers that receive email expect the host (the mail server in the last hop before
reaching HP) to be properly registered in DNS. If not, the HP mail server rejects, or “bounces”,
the email.
• The From field (email address) in the email message must be known by the receiving mail
server (that is, the hostname is registered in DNS and advertised on the internet). Otherwise,
Configuring email on Instant Capacity systems 207