 |
» |
|
|
|
The iCOD software sends an encrypted e-mail message, which
contains the iCOD system’s asset report, to an audit system
located at HP. See “iCOD
System Configuration Information Reported to HP” for details
of the information reported to HP. The e-mail requirements are: The iCOD system/partition
is required to have sendmail installed and
configured such that it has the ability to send e-mail to the hp.com domain. The domain name in the iCOD FROM e-mail
address, for the e-mail sent from the iCOD system to HP, must be
DNS resolvable by HP. See “Configuring
iCOD’s FROM E-mail Address” for details.
| | | |  | IMPORTANT: The e-mail is bounced/rejected by the mail servers
at HP if the domain name in the FROM address,
for the e-mail sent from the iCOD system to HP, is not DNS resolvable
by HP. | | | | |
Note that the sendmail configuration
and routing may vary, but the iCOD system must have the ability
to send e-mail to the hp.com domain. The ability to receive e-mail from HP is optional, but you
may find it useful for testing the capability of sending e-mail
to HP. For more information see “Configuring
Your Server to Send but Not Receive E-Mail”. Refer to the sendmail(1M) manpage
for more information on sendmail. sendmail is part of the HP-UX core
and is installed with the HP-UX operating system. However, a sendmail configuration
process needs to be followed to complete its installation. For information,
refer to the chapter titled Installing and Administering
sendmail, in the appropriate documentation: For HP-UX 11.0: Installing
and Administering Internet Services (B2355-90147) For HP-UX 11i v1: Installing
and Administering Internet Services (B2355-90685)
You can retrieve the above documentation from the HP web site:
docs.hp.com
Select:
Networking and Communications -> Internet Services
to access either of the documents. On Superdome SystemsFor Superdome systems all iCOD partitions
must be configured to send e-mail to HP. This is because each iCOD
partition reports the processor information for itself. It is recommended
that the e-mail capability be configured and the iCOD software be
installed on the non-iCOD partitions, as well. This makes it easier
for you to later redistribute processors across partitions (that
is, load balance). See “Load-balancing
Active Processors” for details. E-Mail
Configuration | |
Before
you Start. Your iCOD system must be network accessible to HP mail servers
that are outside your company's firewalls. If your iCOD system is
on an isolated network, e-mail from the iCOD system does not reach
HP. This causes your iCOD system to be out of compliance with HP’s
On Demand Solutions program. Sendmail. sendmail is the application used
by the iCOD software to send encrypted mail messages from your system
to HP. The sendmail daemon, if running,
can also be used to receive e-mail. For the purposes of this e-mail
configuration, only the ability to send e-mail is required. Mail applications invoke sendmail to
send e-mail. The configuration file, /etc/mail/sendmail.cf, offers tremendous flexibility. Overview
of E-mail Routing Across the Internet. When sendmail is invoked, by the
iCOD software, to send e-mail to HP, sendmail determines
where it should initially send the e-mail (the first hop). Mail
often goes through multiple systems (hops) before it reaches the
final destination. To determine the first hop for the e-mail, sendmail uses
one of the following: The e-mail 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 mail to the final destination. DNS MX records - this method requires that the iCOD
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
mail server to forward the e-mail to (for the first hop) in order
for the e-mail to reach the final destination (hp.com).
In all cases, the following requirements must be met: HP’s mail servers receiving
mail expect the host (the mail server in the last hop before reaching
HP) to be properly registered in DNS. Otherwise the HP mail server
rejects or “bounces” the e-mail. The 'From' field (e-mail address), in the e-mail
message, must be known by the receiving mail server (that is, the
hostname is registered in DNS and advertised on the internet). Otherwise
the receiving mail server at HP rejects the mail. This field in
the e-mail can be configured with a simple one line modification
(DM) to the /etc/mail/sendmail.cf file. In some DNS environments no changes to the default /etc/mail/sendmail.cf file may be needed to properly route e-mail from the
iCOD system to HP. In some environments, configuring your iCOD system
to properly send e-mail from the system to HP can require as little
as a two line edit (or none) to the /etc/mail/sendmail.cf file. Configuring mail, including sendmail and DNS configurations, is usually handled by the IT
team in most organizations.
Example 2-1 Example
Edit to Sendmail Configuration (/etc/mail/sendmail.cf) DMmy_company.com
DSmailhub.my_company.com |
This example assumes the following: the iCOD system’s hostname
is: myICODsystem.my_site.my_company.com the From field of the e-mail
is set to my_company.com rather than the exact
hostname of the iCOD system. This is because most organizations
do not advertise the names of their internal servers to the internet;
however, they do advertise a few (select) high level domain names
to the internet. the iCOD system is not advertised to the internet
but hostname mycompany.com is advertised and
reachable from the internet e-mail is forwarded from the iCOD system to a mail
relay host called mailhub. The mail server called mailhub may
either be directly connected to the internet and send the e-mail
directly to HP, or it may forward the e-mail to another mail server
on its way to HP.
| | | |  | NOTE: Any bounced iCOD e-mail messages are in the adm mailbox. | | | | |
Steps
to Confirm or Diagnose E-mail Configuration | |
After you have configured your iCOD system to send e-mail
over the internet you can use the following steps to confirm the
e-mail configuration or to aid in debugging the configuration: Send an e-mail
message from your iCOD system to an e-mail address in the same domain
(intranet) and confirm receipt of the e-mail message. Send an e-mail message from
your iCOD system to an e-mail address outside of your domain (to
the internet, for example, to a yahoo or
hotmail e-mail address) and confirm receipt
of the e-mail message. Send an e-mail message from
your iCOD system to someone at HP (for example, a HP representative
in a local account team) and confirm the person at HP received the
e-mail message. As root, execute the command:
/usr/sbin/icod_notify
This command sends an e-mail message to HP’s
audit application. HP sends a confirmation e-mail message to the
iCOD system contact that is configured for your iCOD system. Receipt
of the confirmation e-mail message confirms successful iCOD e-mail
configuration.
Configuring
iCOD’s FROM E-mail Address | |
One of the e-mail requirements of the iCOD program is that
the FROM e-mail address, on e-mail messages sent
by the iCOD software from your iCOD system to HP, must be DNS resolvable. The iCOD software uses adm@localhost.domain as the default FROM e-mail
address (where localhost is the hostname of your iCOD system and domain is its DNS domain). If the default FROM e-mail
address is undesirable, you can configure the iCOD B.05.x software
to use a FROM address you specify. Configuring a Specified FROM AddressTo configure your specified iCOD FROM e-mail
address, execute the following command:
/usr/sbin/icod_modify -f from_address You can verify the configured iCOD FROM e-mail address by
using the /usr/sbin/icod_stat command. After you have configured a specified FROM e-mail address,
the iCOD software uses it on all subsequent e-mail messages sent
from your iCOD system to HP. Reverting to the Default FROM AddressIf you have specified an iCOD FROM e-mail
address and you want to revert to the default iCOD FROM e-mail
address (adm@localhost.domain), execute the following command:
/usr/sbin/icod_modify -f ““ Configuring
Your Server to Send but Not Receive E-Mail | |
For security reasons, some organizations do not wish to allow
incoming mail. If you want your iCOD system to be capable of only
sending e-mail, and not receiving e-mail, complete the following
configuration procedure: To prevent the sendmail daemon from starting up again when your system reboots,
edit the /etc/rc.config.d/mailservs file, changing the value of SENDMAIL_SERVER to 0: vi /etc/rc.config.d/mailservs
|
#########################################
# Mail configuration. See sendmail(1m) #
#########################################
#
# BSD’s popular message handling system
#
# SENDMAIL_SERVER: Set to 1 if this is a mail server
# and should run the sendmail deamon.
# SENDMAIL_SERVER_NAME: If this is not a mail server, but a
# client being served by another
# system, then set this variable to
# the name of the mail server system
# name so that site hiding can be
# performed.
#
export SENDMAIL_SERVER=0
export SENDMAIL_SERVER_NAME=
To immediately stop the server from receiving e-mail,
kill the active sendmail daemon by executing the following command: /sbin/init.d/sendmail stop
iCOD
System Configuration Information Reported to HP | |
The iCOD software sends an asset report, via encrypted internet
e-mail, to HP’s audit application when one of the following
events occur: the periodic
iCOD cron task is triggered the iCOD system is booted the iCOD system is shut down the number of requested active
processors is changed
The asset report contains iCOD system configuration information.
The following data is reported to HP: - iCOD Version
The version number of the
asset report (formatting) - Client Type
The type of contract, either
iCOD-purchase or iCOD-utility - Date
The date and time in UTC (Coordinated
Universal Time) - Local Date
The local date and time,
including the time zone - Event Type
The type of event that caused
an asset report to be sent to HP - Serial Number
The serial number of the
system - Software ID
The software identifier of
the system - Hostname
The system host name - NIS Domain Name
The NIS domain name - Domain Name
The fully qualified domain
name - Model
The model number of the system - Uname Output
The HP-UX system information - Total CPUs
The total number of physically installed
processors - Active CPUs
The number of active processors - Reply to Contact
Status of System Contact’s
request for reply e-mail — if set to “true” (1) causes
HP to return an acknowledgment e-mail, if set to “false” (0)
causes HP to not return an acknowledgment e-mail - System Contact Name
The name of the person who
is the System Contact (responsible for the system) - System Contact Phone
The phone number of the person
who is the System Contact - System Contact E-mail
The e-mail address of the
person who is the System Contact
Configuration ChangeIf the iCOD system configuration has changed, by the activation
or deactivation of processors, the following information is reported
as well: - Authorizing
Manager Name
The name of the manager who
is authorizing the change to the number of requested active processors - Authorizing Manager Phone
The phone number of the authorizing manager - Authorizing Manager E-mail
The e-mail address of the
authorizing manager - System Administrator Name
The name of the system administrator
(person) activating or deactivating the processors - Change Description
Text that describes the reason
for the system configuration change
On Hardware- Partitionable Systems:In addition to the above information, hardware-partitionable
systems also report the following to HP (note that all partitions
should be configured to send e-mail to HP): - Local Partition
ID
The identifier of the iCOD
partition, that the information in the above section applies, and
through which the complex information was obtained - Total Reporting Partitions
The total number of reporting partitions
in the complex - Reporting Partition IDs
The identifiers of reporting
partitions defined in the complex - Total Inactive Partitions
The total number of inactive partitions
in the complex - Inactive Partition IDs
The identifiers of inactive
partitions in the complex - Total CPUs in Complex
The total number of processors
in the complex including active and inactive processors - Total Free CPUs
The total number of processors
in free cells in the entire complex - Total Partitions
The total number of partitions
in the entire complex - Partition
The partition identifier,
followed by the total number of processors in the partition including
active and inactive processors (repeated for each partition in the
entire complex) - Total Cells
The total number of cells
in the entire complex - Cell
The cell number, partition
ID, Active|Inactive, number of processors,
and gigabytes of memory (repeated for each cell in the entire complex)
HP receives an asset report from your iCOD system. Here is
an example of an asset report sent from a hardware-partitionable
iCOD system: Example 2-2 iCOD
B.05.x Asset Report iCOD Version:5.0
Client Type:iCOD-purchase
Date:01/01/2002 08:00
Local Date:01/01/2002 02:00 MST
Event Type:PERIODIC_SYSTEM_AUDIT
Serial number:USR0000000
Software ID:abcdef
Hostname:par2
NIS Domain name:.
Domain name:par2.corp.com
Model:9000/800/SD32000
Uname Output:HP-UX par2 B.11.11 U 9000/800 unlimited-user
Total CPUs:4
Active CPUs:4
Reply to Contact:1
System Contact Name:A.Contact
System Contact Phone:Number:970-888-9999
System Contact Email:acontact@corp.com
Local Partition ID:0
Total Reporting Partitions:1
Reporting Partition IDs:0
Total Inactive Partitions:1
Inactive Partition IDs:1
Total CPUs in Complex:16
Total Free CPUs:4
Total Partitions:3
Partition:0,4
Partition:1,0
Partition:2,8
Total Cells:4
Cell:0,0,Active,4,16.0
Cell:2,2,Active,4,16.0
Cell:3,2,Active,4,16.0
Cell:4,-1,Inactive,4,16.0
|
|
Printable version
