asked on

nfs mount is not working with mksysb ?

we have AIX 5.3 nim server configured with mksysb backup through nfs. We have two NIC cards in NIM server. one card normal Normal. another one is Gigabit Ethernet. Both NICs configured with ip and working fine. from NIM server /export/mksysbs directoy has been hosted to nim clients for taking mksysb backup. From NIM client if we mount /export/mksysb directory through NIC card one(which is residing on NIM) we could able to write and it is working fine. But if access the same diretory through GIGABIT ethernet adapter ( adapter 2 which is residing on NIM server) the mount is not allowing to write saying that touch: 0652-046 Cannot create hi. I am able to access the server through NIC adapter 2 from NIM client ? Could any body help please ?

wcsjimmy

I am assuming that you have a different IP on each NIC.

When you do the NFS mount are you doing it by hostname or IP?

rammaghenthar

ASKER

yes We have different IP on each NIC.
yes We are using hostname when do NFS mount on client.
NIC card one is called with computer name. NIC 2 is called with computer name with -gb extension
example consider hostname is newnim
NIC 1 XXX.XXX.XXX.XXX newnim
NIC 2 XXX.XXX.XXX.XXX newnim-gb ( gigabit ethernet which is not allowing to write)

woolmilkporc

Hi again,
perhaps it could help if you forced the nfsd on your NIM box to only use UDP.
This can be accomplished by issuing

chgssys -s nfsd -a "-p udp"

and then recycle it with

stopsrc -g nfs
and
startsrc -g nfs

wmp

woolmilkporc

... sure, just for testing you don't need to modify nfsd.
Issue your mount command at the client with an additional
'-o proto=udp' and see what happens.
wmp

rammaghenthar

ASKER

Hi woolmilkporc
I had removed /export/mksysbs from export list and flush it from export list then given full permission (777) to /export/mksysbs directory and freshly configured it nfs on nim box. Then tried from client. It is working fine. Now I am waiting for scheduler to run. So that I could see automatic mksysb is working or not. I also tried to run

# chgssys -s nfsd -a "-p udp"
ksh: chgssys: not found.
#
and got following output . I could not progress further.

woolmilkporc

Hi rammaghenthar,

sorry, again a typo from my side :-(
the command is actually 'chssys'!

Try it if your job still doesn't work.

btw, why do you export and mount your directories by hand?
If using NIM, it will do it for you, if your mksysb job (run on the master NIM server) would look like something like this:

'nim -o define -t mksysb -F -a server=master \
-a location=/export/mksysbs/[your_name_for_this_mksysb] -a mk_image=y \
-a source=[NIM_name_of_your_machine_to_backup]'

Given your machine to backup was regularly defined as a NIM resource (standalone machine) on your NIM master, this should work fine. You wouldn't need any exports or mounts anymore.

To bind via GE, of course your NIM master must be known to your standalone machine by its GE IP address. (GE == GIGABIT Ethernet). To accomplish this, you might want to re-create your client's niminfo file. Use 'smit niminit' for this (fill in the values). Be sure to use your NIM master's GE name (from /etc/hosts) for 'Host Name of Network Install Master' and delete /etc/niminfo before re-creating.

wmp

rammaghenthar

ASKER

tried to run smit niminit on nimclient and it didn't proceed and stuck with

NFS server warunim001-g not responding still trying
Processing data ...
following info

how to identify warunim001-g gb ethernet is configured from nim server to nim client ?

ASKER CERTIFIED SOLUTION

woolmilkporc

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

rammaghenthar

ASKER

Hi Woolmilkporc

NIM server configuration

# netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
en0 1500 link#2 0.9.6b.1b.1d.72 15886777 0 7326769 2 0
en0 1500 10.114.55.3 10.114.55.35 15886777 0 7326769 2 0
en1 1500 link#3 0.9.6b.1b.1d.73 88493932 0 65566891 2 0
en1 1500 192.168.0 192.168.114.7 88493932 0 65566891 2 0
lo0 16896 link#1 754322 0 755858 0 0
lo0 16896 127 127.0.0.1 754322 0 755858 0 0
lo0 16896 ::1 754322 0 755858 0 0

# ifconfig -a
en0: flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>
inet 10.114.55.35 netmask 0xffffffe0 broadcast 10.114.55.63
en1: flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(INACTIVE),PSEG,LARGESEND,CHAIN>
inet 192.168.114.7 netmask 0xffff0000 broadcast 192.168.255.255
lo0: flags=e08084b<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1

# netstat -rn
Routing tables
Destination Gateway Flags Refs Use If Exp Groups

Route Tree for Protocol Family 2 (Internet):
default 10.114.55.33 UG 3 6773503 en0 - -
10.114.55.32 10.114.55.35 UHSb 0 0 en0 - - =>
10.114.55.32/27 10.114.55.35 U 4 283158 en0 - -
10.114.55.35 127.0.0.1 UGHS 0 9 lo0 - -
10.114.55.63 10.114.55.35 UHSb 0 1276 en0 - -
10.114.55.69/32 10.114.55.97 UG 0 0 en0 - -
127/8 127.0.0.1 U 11 698255 lo0 - -
192.168.0.0 192.168.114.7 UHSb 0 0 en1 - - =>
192.168.0/16 192.168.114.7 U 6 68470112 en1 - -
192.168.114.7 127.0.0.1 UGHS 0 574 lo0 - -
192.168.255.255 192.168.114.7 UHSb 0 4 en1 - -

Route Tree for Protocol Family 24 (Internet v6):
::1 ::1 UH 1 55099 lo0 - -
#

Working NIM client configuration

xxxxxxxxxx:root > netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
en6 1500 link#2 0.14.5e.c5.f0.e8 20412428 0 6314014 3 0
en6 1500 192.168.121 192.168.121.8 20412428 0 6314014 3 0
en4 1500 link#3 0.14.5e.c6.8a.57 44947577 0 28467457 2 0
en4 1500 10.114.55.6 10.114.55.99 44947577 0 28467457 2 0
en5 1500 link#4 0.14.5e.c6.8a.56 28581074 0 8384453 2 0
en5 1500 192.168.116 192.168.116.29 28581074 0 8384453 2 0
lo0 16896 link#1 1821555734 0 1818443910 0 0
lo0 16896 127 127.0.0.1 1821555734 0 1818443910 0 0
lo0 16896 ::1 1821555734 0 1818443910 0 0
xxxxxxxxxx:root > ifconfig -a
en6: flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT ,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>
inet 192.168.121.8 netmask 0xffffff00 broadcast 192.168.121.255
tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
en4: flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT ,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>
inet 10.114.55.99 netmask 0xffffffc0 broadcast 10.114.55.127
tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
en5: flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT ,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>
inet 192.168.116.29 netmask 0xffffff00 broadcast 192.168.116.255
tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
lo0: flags=e08084b<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT >
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1
xxxxxxxxxxxx:root > netstat -rn
Routing tables
Destination Gateway Flags Refs Use If Exp Groups

Route Tree for Protocol Family 2 (Internet):
default 10.114.55.97 UG 25 28297053 en4 - -
10.114.55.64 10.114.55.99 UHSb 0 0 en4 - - = >
10.114.55.64/26 10.114.55.99 U 1 154091 en4 - -
10.114.55.99 127.0.0.1 UGHS 82 3714573874 lo0 - -
10.114.55.127 10.114.55.99 UHSb 0 1 en4 - -
127/8 127.0.0.1 U 58 2402889015 lo0 - -
192.168.114/24 192.168.116.1 UG 1 1369204 en5 - -
192.168.116.0 192.168.116.29 UHSb 0 0 en5 - - = >
192.168.116/24 192.168.116.29 U 3 3358 en5 - -
192.168.116.29 127.0.0.1 UGHS 0 2 lo0 - -
192.168.116.255 192.168.116.29 UHSb 0 1 en5 - -
192.168.121.0 192.168.121.8 UHSb 0 0 en6 - - = >
192.168.121/24 192.168.121.8 U 72 6294424 en6 - -
192.168.121.8 127.0.0.1 UGHS 0 31 lo0 - -
192.168.121.255 192.168.121.8 UHSb 0 1 en6 - -
192.168.122/24 192.168.116.1 UG 0 7006817 en5 - -
192.169.0/24 192.168.116.1 UG 0 0 en4 - -

Route Tree for Protocol Family 24 (Internet v6):
::1 ::1 UH 0 2701 lo0 - -
xxxxxxxxx:root >

Notworking NIM client configuration

[xxxxxxxxxxxx:root:/home/root:] netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
en0 1500 link#2 0.11.25.7e.16.ce 7587303 0 3203355 2 0
en0 1500 10.114.19.2 10.114.19.248 7587303 0 3203355 2 0
en1 1500 link#3 0.11.25.7e.16.cf 18641 0 17 2 0
en1 1500 10.114.192 10.114.192.165 18641 0 17 2 0
lo0 16896 link#1 1350 0 1390 0 0
lo0 16896 127 127.0.0.1 1350 0 1390 0 0
lo0 16896 ::1 1350 0 1390 0 0

[xxxxxxxxxxxx:root:/home/root:] ifconfig -a
en0: flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>
inet 10.114.19.248 netmask 0xffffffe0 broadcast 10.114.19.255
en1: flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>
inet 10.114.192.165 netmask 0xffffff00 broadcast 10.114.192.255
lo0: flags=e08084b<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1
[xxxxxxxxxxxxx:root:/home/root:]

[xxxxxxxxxxxx:root:/home/root:] netstat -rn
Routing tables
Destination Gateway Flags Refs Use If Exp Groups

Route Tree for Protocol Family 2 (Internet):
default 10.114.19.225 UG 1 2646305 en0 - -
10.114.19.224 10.114.19.248 UHSb 0 0 en0 - - =>
10.114.19.224/27 10.114.19.248 U 2 556026 en0 - -
10.114.19.248 127.0.0.1 UGHS 2 1340 lo0 - -
10.114.19.255 10.114.19.248 UHSb 0 0 en0 - -
10.114.192.0 10.114.192.165 UHSb 0 0 en1 - - =>
10.114.192/24 10.114.192.165 U 0 1 en1 - -
10.114.192.165 127.0.0.1 UGHS 0 1 lo0 - -
10.114.192.255 10.114.192.165 UHSb 0 0 en1 - -
127/8 127.0.0.1 U 4 11 lo0 - -

Route Tree for Protocol Family 24 (Internet v6):
::1 ::1 UH 0 0 lo0 - -
[xxxxxxxxxxx:root:/home/root:]

How to check NIM server and client configuration side is it correct or not ?

woolmilkporc

Hi,
which of the interfaces are GE?

wmp

rammaghenthar

ASKER

en1 1500 192.168.0 192.168.114.7 88493932 0 65566891 2 0
this one is GE interface on NIM server .

SOLUTION

woolmilkporc

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

rammaghenthar

ASKER

1. Could it be that the not-working nimclient's gateway 10.114.19.225 does not forward traffic to 192.168.114.7/16? Can you ping 192.168.114.7 from the nimclient?
It is not pinging.

2. broadcast addresses inconsistent with netmasks?
In our environment NIM server and NIM client (which I am trying to configure as a client ) is not in same network. Right now these servers is not configured for mksysb and so I am trying configure it. In our environment we have only one nim server I am simply trying to configure as a nim client. originally NIM client which I am trying to configure is not planned setup. I took charge of it working setting up backup environment. Here we are using lot of subnets for administration purpose.
Conclusion:-
From our discussion I understand that due to network setup it is not functioning .
So what I am doing is whereever warunim001-g (192.168.114.7) IP pings there I am configuring GB setup for mksysb. other servers I am using 10.114.55.35 en0 ip , I configure it. It is working fine. Previously I had doupt with NIM configuration and looked at it. I am got clear . Thankyou for your kind support woolmilkporc. Right

rammaghenthar

ASKER

Hi woolmilkporc

As per your previous statement they below steps I had done on NIM server Then NIM server stopped responding to clients
chssys -s nfsd -a "-p udp"
stopsrc -g nfs
startsrc -g nfs

Then I had done the steps on NIM server
chssys -s nfsd -a "-p tcp"
stopsrc -g nfs
startsrc -g nfs

Then it started working. why you told this step ? and why it was not working ?

woolmilkporc

Hi rammaghenthar,
sorry that it did'nt work. It proposed it only because nfs/udp is a bit less sensitive in case the host had 2 or more interfaces, and I thought it was worth giving a try. Your NIM server and clients are on different subnets, which I didn't know when first posting, and NIM seems to rely on TCP when it comes to crossing subnets.
Glad to hear that things are clear now and that I could help you a bit.
Thanks for the points, you are always welcome!
Have fun and success,

Norbert (wmp)