Oracle ZFS Storage Appliance: NAS in Exadata/Exalogic gets Duplicate IP Address Warnings and Disables the N/W Interfaces

Asset ID:	1-71-1900210.1
Update Date:	2014-06-26
Keywords:

Solution Type Technical Instruction Sure

Solution 1900210.1 : Oracle ZFS Storage Appliance: NAS in Exadata/Exalogic gets Duplicate IP Address Warnings and Disables the N/W Interfaces

Related Items


Exadata X3-8b Hardware
 Oracle ZFS Storage ZS3-2
 Oracle ZFS Storage ZS3-4
 Oracle Exalogic Elastic Cloud X2-2 Hardware
 Sun ZFS Storage 7420
 Oracle Exalogic Elastic Cloud X2-2 Half Rack
 Exadata Database Machine X2-2 Hardware
 Exadata X3-2 Hardware
 Oracle Exalogic Elastic Cloud X2-2 Full Rack

Related Categories


PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS

In this Document

Goal

Solution

Created from <SR 3-9196070959>

Applies to:

Oracle Exalogic Elastic Cloud X2-2 Full Rack - Version X3 to X4 [Release X3 to X4]
Oracle Exalogic Elastic Cloud X2-2 Half Rack - Version X4 to X4 [Release X4]
Oracle Exalogic Elastic Cloud X2-2 Hardware - Version X4 to X4 [Release X4]
Exadata X3-8b Hardware - Version All Versions to All Versions [Release All Releases]
Exadata X3-2 Hardware - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)

Goal

How to resolve duplicate address warnings in debug.sys and that the affected interfaces get disabled

This is normal behaviour for Solaris network interfaces when faced with other devices on the network that share the same IP address

Example

ip: [ID 759807 kern.warning] WARNING: ipmp2 has duplicate address xxx.xxx.xxx.x (in use by xx:00:00:xx:xx:xx:00:00:00:00:00:00:00:xx:xx:00:xx:xx:xx:x; disabled

Loss of network connectivity is the result

Solution

It was found that there was a Private IP address that was in conflict with new storage cell that was installed.

The NAS had its duplicate IP addresses changed to ones that did not conflict.

8 IP ZFS Storage Appliance was changed from 192.168.10.xxx - 192.168.10.xxx

to become 192.168.11.x - 192.168.11.x (with netmask 255.255.248.0)

Attachments

This solution has no attachment