Integrated Management Module (IMM) static IP address and Dynamic Domain Name System (DDNS) issue - IBM System x



Source

RETAIN tip: H197724

Symptom

The Integrated Management Module (IMM) Dynamic Domain Name System (DDNS) feature may not work when the network interface is configured to use static Internet Protocol (IP) configuration. IBM has tested the feature and found that there is an issue with the configuration. This RETAIN tip demonstrates how to set up IMM and name the server.

Affected configurations

The system may be any of the following IBM servers:

  • System x3100 M3, type 4253, any model
  • System x3200 M2, type 4367, any model
  • System x3200 M2, type 4368, any model
  • System x3200 M2, type 9233, any model
  • System x3200 M3, type 7327, any model
  • System x3200 M3, type 7328, any model
  • System x3250 M2, type 4190, any model
  • System x3250 M2, type 4191, any model
  • System x3250 M2, type 4194, any model
  • System x3250 M3, type 4251, any model
  • System x3250 M3, type 4252, any model
  • System x3250 M3, type 4261, any model
  • System x3400 M2, type 7836, any model
  • System x3400 M2, type 7837, any model
  • System x3400 M3, type 7378, any model
  • System x3400 M3, type 7379, any model
  • System x3500 M2, type 7839, any model
  • System x3500 M3, type 7380, any model
  • System x3550 M2, type 4198, any model
  • System x3550 M2, type 7946, any model
  • System x3550 M3, type 4254, any model
  • System x3550 M3, type 7944, any model
  • System x3620 M3, type 7376, any model
  • System x3630 M3, type 7377, any model
  • System x3650 M2, type 4199, any model
  • System x3650 M2, type 7947, any model
  • System x3650 M3, type 4255, any model
  • System x3650 M3, type 7945, any model
  • System x3690 X5, type 7148, any model
  • System x3690 X5, type 7149, any model
  • System x3755 M3, type 7164, any model
  • System x3850 M2, type 7141, any model
  • System x3850 M2, type 7144, any model
  • System x3850 M2, type 7233, any model
  • System x3850 M2, type 7234, any model
  • System x3850 X5, type 7145, any model
  • System x3850 X5, type 7146, any model
  • System x3950 X5, type 7145, any model

This tip is not option specific.

This tip is not software specific.

Workaround

Complete the following steps to configure the IMM and name the server:

Note: The following Domain Name System (DNS) server and IMM firmware are used in these examples:

  • DDNS server: Ubuntu 10.04 LTS, Bind9 1.9.7.0, IP: 10.0.0.2

    OR

  • DNS server: Windows 2003 or 2008 DNS Server

    AND

  • IMM: YUOO91E or above, IP: 10.0.0.100

1. Configure the IMM with the following settings:

Under the IMM Web Interface page "Network Interface":

  IPv6: Disabled
Hostname: immtest01
Domain Name: mydomain.org
DDNS Status: Enabled
Domain Name Used: Manual
Dynamic Host Configuration Protocol (DHCP): Disabled - Use static IP configuration
Static IP Address: 10.0.0.100
Save settings.

Under the IMM Web Interface page "Network Protocols":

  DNS: Enabled
DNS Server: 10.0.0.2
Preferred DNS Servers: IPv4
Save all settings and restart the IMM.

2A. If using a Linux DNS server:

Add the following zone configuration file to the bind9 configuration and change the IP address and domain name to a name of your choice:

  /etc/bind/named.conf.local
zone "mydomain.org" IN <open_curly_brace>
type master;
file "/var/lib/bind/mydomain.org.db";
allow-update <open_curly_brace>any;<close_curly_brace>;
notify yes;
<close_curly_brace>;

zone "0.0.10.in-addr.arpa"<open_curly_brace>
type master;
file "/var/lib/bind/rev.0.0.10.in-addr.arpa";
<close_curly_brace>;

/var/lib/bind/mydomain.org.db
$ORIGIN .
$TTL 259200 ; 3 days
mydomain.org IN SOA dns1.mydomain.org. root.mydomain.org.
(
2007091366 ; serial
28800 ; refresh (8 hours)
14400 ; retry (4 hours)
2419200 ; expire (4 weeks)
86400 ; minimum (1 day)
)
NS dns1.mydomain.org.
$ORIGIN mydomain.org.
dns1 A 10.0.0.2

/var/lib/bind/rev.0.0.10.in-addr.arpa
$TTL 86400;
@ IN SOA dns1.mydomain.org. root.mydomain.org.(
2007091340;
28800;
14400;
2419200;
86400;
);
IN NS dns1.mydomain.org.
40 IN PTR dns1.mydomain.org.

2B. If using a Linux DNS server:

Manually remove the A record of the IMM's Full Qualified Domain Name (FQDN) in the zone configuration and restart the bind9 service.

  1. Ping or nslookup to make sure the FQDN cannot be resolved.
  2. Restart the IMM.
  3. Wait until the IMM Web Graphical User Interface (GUI) starts.
  4. Ping or nslookup the IMM's FQDN.

These steps create a working DDNS test environment for the IMM.

The bind9 configuration files are following:

3. If using a Windows DNS Server:

On the Windows DNS server management console:

  1. Right-click on the forward look-up domain and go to "Properties"
  2. On the "General" tab for the drop-down box "Dynamic Updates" you must change the setting to "Nonsecure and secure" (The IMM does not have the ability to send secure DNS updates.)
  3. Save these settings for the Windows DNS server. You may need to reload the forward look-up domain.

4. On the IMM log you should see the following message:

  "DDNS registration successful. The domain name is <yourdomain.com>"

If you do not see this message, please reboot your IMM so that the Service Processor can register with the DDNS server properly.

Additional information

The cause of the issue is the wrong configuration of the DNS server or IMM.

DDNS support was added to IMM firmware at level 91E.

Applicable countries and regions

 


Document id:  MIGR-5086090
Last modified:  2013-04-26
Copyright © 2014 IBM Corporation