Use this task only when you want customized domain security. Customize domains to establish and maintain different domains for multiple Hardware Management Consoles attached to the same Local Area Network (LAN). Multiple consoles can be on the same LAN for two reasons:
Stranding objects is a potential pitfall of establishing customized domain security.
Stranded objects are objects in a domain that does not include any Hardware Management Consoles. Consoles cannot communicate with a stranded object, so the object can never be defined to a console. And not being able to define an object isolates it from all other console tasks.
There are two ways objects can become stranded:
The objects are in a domain with only one Hardware Management Console.
-and-
A new name or password is applied to the domain of the console and its defined objects.
The objects are in a domain with only one Hardware Management Console.
-and-
A new name or password is applied to the domain of the console only.
Note: It does not matter whether the objects are defined or undefined at the time.
To avoid stranding objects:
Before assigning a new name or password to the domain of a console and its defined objects, either define all undefined objects, or make sure at least one other console will remain in the current domain with the undefined objects.
Before assigning a new name or password to the domain of a console only, make sure all defined objects and undefined objects are in the domain of at least one other console. Make sure at least one other console will remain in the current domain with the defined and undefined objects.
If you know the domain name and password of the stranded objects, then simply assign the same name and password to any available Hardware Management Console. This moves the console into the domain of the stranded objects.
If you do not know the domain name or password of the stranded objects, then you must report the problem to IBM.