1833059 Members
2940 Online
110049 Solutions
New Discussion

ignite

 
jona_1
Frequent Advisor

Re: ignite

HI manix,
could you please find the attachment..unable to understand why showmount is throwing that error ..what does it mean..

Regards,
Jona
Manix
Honored Contributor

Re: ignite

please send /etc/rc.config.d/nfsconf file

Check your /etc/rc.config.d/nfsconf on the client and see what START_MOUNTD is set to.

If it is '0' then you need to make it '1'.
START_MOUNTD=1

then stop /start the services.

More over just check if nfs is running fine on the server side any try to mount some exported
directory on the different client machine
HP-UX been always lovable - Mani Kalra
Manix
Honored Contributor

Re: ignite

Please have a look at this thread as well for nfs server/client configuration in nfsconf file

change needed on /etc/rc.config.d/nfsconf as,

NFS_CLIENT=1
NFS_SERVER=1
NUM_NFSD=16
NUM_NFSIOD=16
START_MOUNTD=1

http://h30499.www3.hp.com/t5/System-Administration/NFS-RPC-Program-not-registered/m-p/3699124#M249018


If still failing make the above entries like above on client /server and restart all NFS
services nfs.server,core & client

Whats the nfs version on the client & server
swlist -l product | grep -i nfs

HP-UX been always lovable - Mani Kalra
jona_1
Frequent Advisor

Re: ignite

HI,
in this attachment i am sending you the conffile of serverside...
I choose other client & tried to do nfs mount with the server & surprised to see that its not happening....so problem in server side??

Regards,
Jona
Manix
Honored Contributor

Re: ignite

Is the server pingable by name & IP, try nslookup from both the client & server side ,check /etc/host files entries at each end with
host names & FQDN names.

Try stopping & starting all the NFS services @
server side.
HP-UX been always lovable - Mani Kalra
INH
Regular Advisor

Re: ignite

Hello Jona,
You need to ensure all teh configuration is fine as said above. Such as /etc/hosts entires and DNS entry of your client in teh network, DNS entry should work with forward and reverse lookup ( IP & hostname vice versa). Ensure nfs daemon is running on server as well as client.
Then perfrom folwllowing steps to configure your client for Ignite netrecovery.

Add new ignite client on ignite servers in your environment

Add client to /etc/exports on ignite server

Example
/var/opt/ignite/recovery/archives/client_name -anon=2,access=client_name

Create recovery archive directory on Ignite server
Eg.
# mkdir /var/opt/ignite/recovery/archives/client_name
# chown bin:bin /var/opt/ignite/recovery/archives/ client_name
Add the /var/opt/ignite/clients//recovery/archive_content file, with the following contents (ensure file is owned by bin:bin and is world readable):

inc_entire /dev/vg00

Once server is added to the ignite server, create a full Ignite-UX backup of the vg00 volume group to both ignite servers.

# make_net_recovery â s Ignite_server â v

Verify and check

HTH,
Regards,
INH
Knowledge is power
ani007
Super Advisor

Re: ignite

Hi,
Tnx all, I have cheked & found in etc/hosts entry was not there so i put the entry in both client & server , now i am able to ping by name & ip from both client & server.& again reexport the.. but now working ..
in client if i fire showmount -a it showes the following error
"showmount: xxxx02: RPC: Program not registered"
yesterday i have restarted nfs.core & nfs.client on client machine. so what you suggest now shall i restart nfs.server in server machine?

REgards,
Jona
ani007
Super Advisor

Re: ignite

Jona same problem is our envirnment ... i am also facing the sam problem .... you can also check my thread..
jona_1
Frequent Advisor

Re: ignite

HI Manix,
I am able to do it.. i choose another server & make it as ignite server. Thank you .
Regards,
Jona