Loading...
Loading...
When a NAS server is unable to communicate with external services such as DNS, Active Directory, or LDAP, connectivity is impacted. As a result, new clients may experience authentication failures when attempting to establish sessions with the NAS server. How to identify the issue: Verify whether the NAS server’s file interface resides on a different subnet than the external services. These services, such as DNS and Active Directory, require routed network communication. Network alerts are seen in the PowerStore UI-indicating bond degradation: Major One or more bond ports are in link down state or Link Aggregation Control Protocol (LACP) is in degraded state. The file interface is degraded due to BaseEnclosure-NodeA-bond1 is degraded. At some point after this, the network is restored: All ports of the bond are in link up state and Link Aggregation Control Protocol (LACP) configuration is correct. The file interface is healthy. Shortly after recovery, the NAS server remains reachable on the network (for example, it can be pinged). However, alerts may occur indicating issues with the NAS server communicating with external services. For example: The DNS client of the XYZ NAS server is unable to connect to all configured DNS servers. Also, support may review internal logs for messages like the following indicating a route issue to the external services (DNS, DC, or similar services): <TIMESTAMP> <THREAD_ID> SOCK_STREAM: <LEVEL>:[core] epoll_wait (TPI_CONN_REQ):(fd=<FD>, NS=0) sending TSYERR for connect dst=<IP_ADDRESS> port=53: No route to host <TIMESTAMP> <THREAD_ID> SOCK_STREAM: <LEVEL>:[core] T_UNITDATA_REQ: Error in socket layer... (fd=<FD> NS=0 off=20 len=44 dstaddr=<IP_ADDRESS> port=53 len=69: No route to host)
PowerStoreOS 4.4 includes updates to internal networking behavior that can influence how routing is handled in certain environments. In routed network configurations, a temporary network (bond) outage may, sometimes, lead to the NAS server operating without a default gateway. When this occurs, the NAS server is unable to reach external services such as DNS and Active Directory if those services reside outside the local subnet. Environments where these services are located within the same subnet as the NAS server (flat networks) are not impacted.
Workaround To restore connectivity, use the PowerStore Manager (UI) to move the NAS server to the alternate node. This operation triggers a reinitialization of the NAS server’s network configuration, including the default gateway, and clears the external service connectivity alerts.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.