HP Integrated Lights-Out 4 - Manual (Page 100)

If a DHCPv6 address is not available for the primary or secondary address, a DHCPv4
address (if available) is used.
•
Enter NTP server addresses in the Primary Time Server and Secondary Time Server boxes.
You can enter the server addresses by using the server FQDN, IPv4 address, or IPv6
address.
4. If you selected only Use DHCPv6 Supplied Time Settings, or if you entered a primary and
secondary time server, select the server time zone from the Time Zone list.
This setting determines how iLO adjusts UTC time to obtain the local time, and how it adjusts
for Daylight Savings Time (Summer Time). In order for the entries in the iLO Event Log and
IML to display the correct local time, you must specify the time zone in which the server is
located.
If you want iLO to use the time the SNTP server provides, without adjustment, configure iLO
to use a time zone that does not apply an adjustment to UTC time. In addition, that time zone
must not apply a Daylight Savings Time (Summer Time) adjustment. There are several time
zones that fit this requirement. One example is the Atlantic/Reykjavik time zone, which is
neither east or west of the Prime Meridian, and in which the time does not change in the
spring or fall. If you select the Atlantic/Reykjavik time zone, iLO web pages and log entries
will display the exact time provided by the SNTP server.
NOTE: Configure the NTP servers to use Coordinated Universal Time (GMT).
5. Configure the NTP time propagation setting by selecting or clearing the Propagate NTP Time
to Host check box (ML, DL, and SL servers) or the Propagate NTP or OA Time to Host check
box (BL servers).
These settings are enabled by default, and they determine whether the server time is
synchronized with the iLO time during the first POST after AC power is applied, a blade is
inserted, or iLO is reset to the default settings.
For BladeSystems only: When Propagate NTP or OA Time to Host is enabled, and NTP is not
configured or functional, the server time is synchronized with the OA time.
6. Click Submit to save the changes you made on the SNTP Settings page.
7. If you are finished configuring the iLO network settings on the General, IPv4, IPv6, and SNTP
tabs, click Reset to restart iLO.
It might take several minutes before you can re-establish a connection.
TIP: If you notice that iLO Event Log entries have an incorrect date or time, make sure that the
NTP server addresses and time zone are correct. The iLO Event Log includes entries that indicate
success or failure when contacting the NTP server(s).
Configuring and using the iLO Shared Network Port
The iLO Shared Network Port feature enables you to choose between the Shared Network Port
LOM, FlexibleLOM, and the iLO Dedicated Network Port for server management. When you enable
the iLO Shared Network Port, regular network traffic and iLO network traffic pass through the
selected Shared Network Port NIC. The iLO Shared Network Port does not incur an iLO performance
penalty. Peak iLO traffic is less than 2 Mb/s on a NIC capable of a speed of 1 GB/s or 10 GB/s.
iLO traffic volume is low unless the Virtual Media or Remote Console feature is in use.
On servers that do not have an iLO Dedicated Network Port, the standard hardware configuration
provides iLO network connectivity only through the iLO Shared Network Port connection. The iLO
firmware automatically defaults to the Shared Network Port.
The iLO Shared Network Port uses the network port labeled NIC 1 on the rear panel of the server
when Use Shared Network Port – LOM is selected, and uses the network port labeled 1 on the
100 Configuring iLO