HP iLO 3 Scripting and Command Line Guide - Business Support ...

4. SEC_DNS_SERVER
5. IPV6_TER_DNS_SERVER
6. TER_DNS_SERVER
When IPv4 protocol is preferred by iLO clients, the order of IPv6 and IPv4 is reversed for each of
primary, secondary, and then tertiary settings respectively.
IPV6_DEFAULT_GATEWAY allows you to add an IPv6 address to the default gateway address list
maintained by the ILO network stack. This is primarily for environments when no RA (router
advertised) messages are present on the network. The value must be a valid literal IPv6 address
in string form. Clear address entry by specifying a blank IPv6 address (“::”).
IPV6_ADDR_AUTOCFG enables or disables RFC 4862 SLAAC (Stateless Address Auto
Configuration). Value must be either “Y” (enabled) or “N” (disabled). When enabled, iLO creates
IPv6 addresses for itself from RA prefixes as appropriate. When disabled, only the link-local address
is automatically configured. Router advertisements are still monitored but not used for SLAAC
address creation.
IPV6_REG_DDNS_SERVER enables or disables automatic DNS server IPv6 address registration.
Value must be either “Y” (enabled) or “N” (disabled). When enabled, iLO attempts to register
AAAA and PTR records for its IPv6 addresses with the DNS server.
IPV6_PREFERRED_PROTOCOL enables or disables using IPv6 addresses as preferred. Value must
be either “Y” (enabled) or “N” (disabled). When enabled, iLO client applications use IPv6 service
addresses before IPv4 service addresses when both are configured. Client applications affected
by this setting currently are the DNS name resolver and SNTP. In SNTP, if FQDNs are configured,
and the DNS name resolver returns both A (IPv4) and AAAA (IPv6) records, the addresses are
tried in order specified by this setting. For the DNS name resolver, if both IPv4 and IPv6 DNS
addresses are configured, this setting determines the order of use for the primary addresses, then
the secondary addresses, and finally the tertiary addresses.
GET_GLOBAL_SETTINGS
The GET_GLOBAL_SETTINGS command requests the respective iLO global settings. For this
command to parse correctly, the command must appear within a RIB_INFO command block, and
RIB_INFO MODE can be set to read or write.
For example:
GET_GLOBAL_SETTINGS parameters
None
GET_GLOBAL_SETTINGS runtime errors
None
GET_GLOBAL_SETTINGS return messages
A possible GET_GLOBAL_SETTINGS return message is as follows:
RIB_INFO 81