h
Windows NT Domain Issues
The intent of SAN Manager LM is that the SAN should parallel the Windows NT domain. The SAN Manager LM design reflects this in the following ways:
•Administration groups are selected from domain groups.
•Host names are discovered by enumerating machines in the domain.
•Configuring a SAN that has no domain, or spans or crosses domains, can cause the following administration difficulties:
–To add groups from other machines or domains, you may have to first log on to the machines or domains through Network Neighborhood or via the Command Line with a net use command.
–SAN Manager LM cannot automatically discover hosts in domains other than that of the host running the application. For more information about host discovery and adding hosts to the SAN database, see page 106 of the Administrator’s Guide.
–Depending on the type(s) of name resolution used on the Microsoft network and on the TCP/IP configuration, SAN Manager LM may not be able to reliably communicate with hosts on other domains.
•SAN Manager LM may be unable to authenticate users whose accounts exist in domains other than the domain of the machine that is running the SAN Manager LM administration application
Miscellaneous Notes
•There is a limit of 255 characters on Domain Name System (DNS) names of hosts in the SAN Manager LM database.
•SAN Manager LM’s Identify Device feature may not be able to blink the lights on RAID disks because the RAID controllers may satisfy I/O from cache.
•When hosts are disconnected from the Fibre Channel SAN, the main window of the SAN Manager LM administration application shows them as present.
| Page 7 of 7 |
