6.Reboot the StorEdge.

Note that the above changes do not take effect until after the reboot.

This action removes the undesired entries in almost every case. The only case where the entries may persist is in a multiple server WINS environment using replication. In this case, consult the provider of the WINS server operating system for removal instructions.

Anonymous connections restricted by Domain Controller: In this case, the master browser and domain controller are both located, but the system log shows a number of RPC errors related to security, along with the name and IP address of the Domain Controller to which it is attempting to authenticate.

Windows 2000 and later operating systems can be configured to refuse anonymous connections, otherwise known as null sessions. Typically, this is done for security reasons. Restricting anonymous connections is not recommended unless all clients and servers in the domain are running Windows 2000 or newer. StorEdge and other non-Windows servers require a change to this policy.

This setting is accessed via the registry editor on the Windows domain controller. Using the Registry Editor, navigate to the key: “HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Control\LSA”. Locate the value RestrictAnonymous. If it is set to “2”, modify it to “0” or “1”. A setting of “0”

The Domain Controller must be rebooted for this change to take effect.

Connected to a DC across a WAN link: In rare cases, it is possible that StorEdge will join a domain using a distant Domain Controller across a slow link. The symptoms in this case will vary. You could see timeouts, authentication failures due to a firewall, or even success with poor performance. The primary indication will be log messages indicating any of the above problems, and referring to communications with a Domain Controller on a faraway subnet.

To resolve this issue, first check the NetBIOS cache as directed above to ensure that the local domain controllers are present. If not, proceed as above to correct any difficulty locating them. After verifying the presence of one or more nearby Domain Controllers (<1B> or <1C> NetBIOS tags), proceed as follows to force StorEdge to use a particular Domain Controller:

1.Connect to the StorEdge via Telnet, and type “admin” at the [menu] prompt and enter the administrator password.

2.At the CLI, enter “set smb.pdc <IP address>”, replacing <IP address> with the IP address of one of the above domain controllers. In spite of the variable name, it is acceptable to use either a PDC <1B>, or a BDC <1C>.

3.After setting the variable, retry the attempt to join the domain. Check the system log to ensure success.

2-48Sun StorEdge 5310 NAS Troubleshooting Guide • December 2004

Page 93 Page 95
Page 94
Image 94
Sun Microsystems 5310 NAS manual Reboot the StorEdge
Page 93 Page 95

5310 NAS specifications

Sun Microsystems, known for its innovative computing solutions, launched the Sun 5310 Network Attached Storage (NAS) system, which marked a significant advancement in the realm of storage solutions in the early 2000s. The 5310 NAS was designed to provide high-performance, reliable, and scalable storage tailored for enterprise environments.

One of the standout features of the Sun 5310 NAS is its file-serving capabilities, which support multiple protocols, notably NFS (Network File System) and CIFS (Common Internet File System). This dual-protocol support allowed organizations to seamlessly integrate the NAS into diverse IT ecosystems, facilitating interoperability between UNIX, Linux, and Windows systems. The enhanced file-sharing capabilities made it an ideal solution for businesses with mixed operating environments.

The Sun 5310 NAS incorporates cutting-edge technologies to ensure high availability and data integrity. The system utilized a RAID (Redundant Array of Independent Disks) technology, providing various RAID levels to protect against data loss while optimizing performance. Additionally, the device featured hot-swappable drives, enabling maintenance and upgrades with minimal downtime, a crucial factor for business continuity.

Equipped with advanced management software, the Sun 5310 NAS offered users an intuitive interface for monitoring storage health and performance. This software included comprehensive reporting functionalities that allowed IT administrators to oversee usage patterns and capacity planning efficiently.

Scalability was another defining characteristic of the Sun 5310 NAS. The system could easily expand with additional storage modules, accommodating the growing needs of an organization without the necessity for complete system overhauls. This flexibility ensured that businesses could adapt their storage solutions to meet evolving data storage needs without incurring significant costs or disruptions.

In terms of performance, the Sun 5310 NAS featured high I/O throughput achieved through its robust hardware architecture and optimized file serving capabilities. This performance baseline was crucial for organizations that relied on heavy data workloads and required rapid access to information.

In summary, the Sun 5310 NAS from Sun Microsystems embodied a forward-thinking approach to network storage, blending reliability, scalability, and multi-protocol support. Its user-friendly management software, combined with the robustness of RAID technology and hot-swappable drives, made it a preferred choice for enterprises looking to streamline their storage infrastructure while safeguarding critical data.
Top Page Image Contents