0.0.0.0 is not a valid secondary ip address

0.0.0.0 is not a valid secondary IP address

Cluster enabled pool resources goes to DEACTIVE state

Fixed in NetWare 6.5 Support Pack 3, the cluster pool enable screen will now validate the ip address.

Workaround: Always assign an IP address while creating a Cluster Enabled Pool.

New cluster enabled pool has been created using NetWare Remote Manager, selecting the Auto Pool Activate option, without specifying the IP address the new pool MUST have.


Steps to Duplicate:

• NetWare Remote Manager (no matter from which of the node) | Manage Server | Partition Disks |
• Select free space on the SAN and click Create
• Select to create a new NSS pool
• Give to the pool the size and the name you like
• Check Cluster Enable Pool
• Click Create
• Click OK
• Leave everything as default, and DO NOT enter an IP address for the Pool
• Click Create

System will allow you to create the new pool even without specifying the IP address to assign to it, will then try to activate the newly created pool, causing the following error on the Logger Screen:

0.0.0.0 is not a valid secondary IP address

and causing all other cluster pool resource to be deactivated, no failover occurring, resources down until user intervention. Checking the objects created for the resource in eDirectory, the address 0.0.0.0 was actually assigned from the system to the newly created pool.

NSSMU does not allow the creation of a new Cluster Enabled Pool on the SAN, if an IP address is not specified, will exit with 2 errors and the pool will not be created.

Formerly known as TID# 10095535