NAS mount... tricks

NAS mount... tricks



172.25.92.193:/DataVolume/Public   2748.03   2438.04   12%       49     1% /nas1

server2:/root # ping 172.25.92.193

server2:/root # netstat -rn
Routing tables
Destination        Gateway           Flags   Refs     Use  If   Exp  Groups

Route Tree for Protocol Family 2 (Internet):
default            130.29.133.65     UG       38   2009595 en0      -      -
127/8              127.0.0.1         U        14       462 lo0      -      -
130.29.133.64      130.29.133.116    UHSb      0         0 en0      -      -   =>
130.29.133.64/26   130.29.133.116    U         4     66744 en0      -      -
130.29.133.116     127.0.0.1         UGHS      1        20 lo0      -      -
130.29.133.127     130.29.133.116    UHSb      0         4 en0      -      -
172.25.95.0        172.25.95.77      UHSb      0         0 en1      -      -   =>
172.25.95/24       172.25.95.77      U         0   8281785 en1      -      -
172.25.95.77       127.0.0.1         UGHS      0        16 lo0      -      -
172.25.95.255      172.25.95.77      UHSb      0         4 en1      -      -

Route Tree for Protocol Family 24 (Internet v6):
::1%1              ::1%1             UH        0       133 lo0      -      -



92 subnet is not there in routing table... 

so, we checked the routing table on the other server, where the /nas1 is mounted


server1:/root # netstat -rn
Routing tables
Destination        Gateway           Flags   Refs     Use  If   Exp  Groups

Route Tree for Protocol Family 2 (Internet):
default            130.29.133.65     UG        9 227980978 en0      -      -
127/8              127.0.0.1         U        20     67317 lo0      -      -
130.29.133.64      130.29.133.113    UHSb      0         0 en0      -      -   =>
130.29.133.64/26   130.29.133.113    U         4     92236 en0      -      -
130.29.133.113     127.0.0.1         UGHS      2        26 lo0      -      -
130.29.133.127     130.29.133.113    UHSb      0         1 en0      -      -
172.25.92.0        172.25.92.172     UHSb      0         0 en1      -      -   =>
172.25.92/24       172.25.92.172     U         1   5959282 en1      -      -
172.25.92.172      127.0.0.1         UGHS      0         1 lo0      -      -
172.25.92.255      172.25.92.172     UHSb      0         1 en1      -      -

Route Tree for Protocol Family 24 (Internet v6):
::1%1              ::1%1             UH        0       326 lo0      -      -




Hence tried to add the routing table on server2, using the gateway 172.25.92.172   



server2:/root # route add 172.25.92/24 172.25.92.172  
and tried to ping the nas IP  "172.25.92.193" from server2.

NO LUCK

Tricks
========

Try to find an IP address closer to nas IP  "172.25.92.193" which is not assigned to any server so far... do nslookup

server1:/root # nslookup 172.25.92.199
Server:         130.29.152.21
Address:        130.29.152.21#53

** server can't find 199.92.25.172.in-addr.arpa: NXDOMAIN


So, use this IP address 172.25.92.199 and make an alias in en1.. using smitty inetalias.


Now, try to mount the nas fs. If you get any error while mounting the NAS FS, makesure to change the nfso parameter. and mount again.

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



172.25.92.193:/DataVolume/Public 5763040016 5112939624   12%       49     1% /nas1