NAS mount... tricks

🔹 NAS Mount Troubleshooting and Tips

1. Verify the NAS mount details

<NAS_IP>:/DataVolume/Public   2748.03   2438.04   12%       49     1% /nas1

2. Check connectivity from the client server

server2:/root # ping <NAS_IP>

3. Check the routing table on server2

server2:/root # netstat -rn

If the NAS subnet (<NAS_SUBNET>) is not listed, the server cannot reach the NAS.

---

4. Compare with a server where the NAS is mounted successfully

server1:/root # netstat -rn

Here, the subnet <NAS_SUBNET> exists with gateway <NAS_GATEWAY>.

---

5. Add the missing route on server2

server2:/root # route add <NAS_SUBNET> <NAS_GATEWAY>

Then try pinging the NAS IP (<NAS_IP>).

If it still doesn’t work, proceed with the trick below.

---

🔹 Trick to Access NAS

1. Find an unused IP in the NAS subnet (<NAS_SUBNET>) using nslookup:

server1:/root # nslookup <UNUSED_IP>

If the IP is free (NXDOMAIN), it can be used temporarily.

2. Assign the unused IP as an alias on the network interface (e.g., en1) using smitty inetalias.

3. Retry mounting the NAS filesystem.

---

6. Check NFS parameters if mount fails

server1:/root # nfso -a | grep port
      nfs_use_reserved_ports = 1
                   portcheck = 0

Adjust these if necessary and remount the NAS.

---

7. Verify the NAS mount

<NAS_IP>:/DataVolume/Public   5763040016 5112939624   12%       49     1% /nas1

---

✅ Key Notes:

• Replace <NAS_IP>, <NAS_SUBNET>, <NAS_GATEWAY>, and <UNUSED_IP> with the appropriate network values.

• Ensure the NAS subnet is reachable via proper routing.

• Use a free IP alias if direct access fails.

• Adjust NFS options if mounting errors occur.