Data Domain Hostname / IP Change

The following is information on how to re-ip and change the hostname on a Data Domain appliance.  This was done on both a Data Domain 510 and 565.

Check to see what host name mappings are in the Data Domain.  If replacing a unit and using its IP, the old servers information would have to be removed from here.  In this case, dd01 would cause local lookups to have problems, since that’s the one being replaced by the new unit.

newdd# net hosts show
Hostname Mappings:
x.x.x.190 -> dd04.x.com
x.x.x.191 -> dd01.x.com dd01
x.x.x.192 -> dd03.x.com dd03

I decided to just wipe the hosts file and remove all static mappings.
newdd# net hosts reset
Host mappings reset to empty.

Change the IP on a single interface
newdd# net config eth0 x.x.x.191 netmask x.x.x.0
Configuring interface…

Change the IP on a virtual interface if you are doing NIC teaming.  This example will be used in the ping below

newdd# net config veth0 x.x.x.191 netmask x.x.x.0
Configuring interface…

Test connectivity from a server on the network.  It took the DD 565 about 2 minutes to come up on the new IP.

server# ping x.x.x.191
PING x.x.x.191 (x.x.x.191) 56(84) bytes of data.
64 bytes from x.x.x.191: icmp_seq=20 ttl=61 time=217 ms
64 bytes from x.x.x.191: icmp_seq=21 ttl=61 time=1.52 ms
64 bytes from x.x.x.191: icmp_seq=22 ttl=61 time=1.55 ms
64 bytes from x.x.x.191: icmp_seq=23 ttl=61 time=1.52 ms
64 bytes from x.x.x.191: icmp_seq=24 ttl=61 time=1.73 ms

Time to change the hostname of the box
newdd# net set hostname dd01.x.com
The Hostname is: dd01.x.com
CIFS active directory authentication will stop working after hostname change.
Run ‘cifs set authentication’ command again.

As directed, cifs set authentication command had to be ran to to join the new Data Domain back to Active Directory.

Note:  A reboot of the Data Domain had to be done to get the cifs authentication back onto the Acitve Directory domain.  This could have been due to two different issues.  Either the hostname change caused the issue, or the NTP settings.  The system was 5 minutes off from the domain controller before the reboot forced the NTP service to query the timeserver.

~ by Kevin Goodman on October 28, 2008.

Leave a Reply