A Solaris Node is not Discovered by a SAN Manager LM Administration Node

When adding Solaris nodes to the SAN, the following errors may occur:

•After adding a Solaris node to the SAN, it is not listed in the nodes pane of the SAN Manager administration application on a Windows NT node.

•When using the Add Node command, the SAN Manager LM application reports that it “cannot resolve IP address to host name” or “cannot ping SAN Manager LM on the node.”

SymptomCause/Solution

A Solaris node cannot There is an IP connectivity problem. To verify IP connectivity be successfully added between the nodes, ping both nodes.

to the SAN database.

Enter the following command to ping the Solaris node from the Windows NT node:

c:ping -tip_address

To ping a Windows NT node from a Solaris node, enter the following command:

ping -sip_address

The host file on either the Windows NT or Solaris node has not

been updated properly. On a Solaris node that is not running Samba and does not have DNS Services configured, verify that the /etc/hosts file is updated correctly with the host name and IP addresses of all nodes on the SAN. On Windows NT nodes, verify that the winnt\system32\drivers\etc\Hosts file has been updated.

The SAN Manager LM service may not be running on the Solaris

node. Enter the following command to verify that the service is running:

# ps -ef grep Service.

There is a connectivity problem between the Solaris node and the

SAN database. Run the get_wwn utility to see if any devices are attached.

Troubleshooting

A Solaris Node is not Discovered by a SAN Manager LM Administration Node

39