Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Networker Solaris 7.2 Storage Node

Status
Not open for further replies.

ToBe25

Technical User
Jan 23, 2007
13
DE
Hi,

I have a problem with the configuration of a Storage Node. I have a FSC Primepower with attached DN30 (HDD Storage). All is running under Solaris 9, with Networker 7.2 Here is what I did:

I have installed the storage node pkg (Version 7.2).

I filled the /etc/hostfiles at the server and the storage node.

I added the licences for storage nodes at the server.

I created a new device at the server with:
name= rd=storage_node_hostname:/dev/dsk/c3t0d0s0
media type= file

When I try to mount or label the device I get the message:

"nsr server $servername$ cannot request from mmd8"

Can anyone help me with that? Thanks in advance!

Tobe

 
This will most likely not work as you must specify a directory instead of a devicename.
 
Hi 605,

thank you for your post. I mounted the device to /space/1 and changed the Networker Device to this directory.

But I still get the stupid error message.

Thanks for more ideas!

Tobe
 
Well, before i discovered the wrong device name i though already that there must be a problem with the servers file on either side. "Cannot request" usually points to such direction. Also, do not forget that nsrexecd on the client must be running as the server needs to control the nsrmmd process remotely.
 
Hi,

yes I checked it in the meantime and it seems there goes something wrong with the setting of the hostname.

When I look to the nsr_shutdown command it gives me:

/opt/SMAW/SMAWnw/nsrmmd -n 11 -s servername

And the Server tells me he can't connect to servername-backup.

So I tried to start the nsrmmd processes myself with -s servername-backup. And after that the Server mounts the file, so it works.

So the error is the wrong name. Starting the processes by hand is not the best idea though, because the Networker Server starts them automatically when a savegroup starts. So it has the wrong name again...

How can I change that name?! How does the Node know which server to take? Where can I change that! I can't remember giving that name to the networker...

Thanks again!

ToBe
 
You have 2 choices, depending on how you authorize:
- Usually, on UNIX/Linux, the specification is done in the startup scripts (/etc/init.d/networker) and its associated system startup script.
- You can also create the file /nsr/res/servers where you specify each server (one per line).
However, to make this change become effective, you must delete the "-s server" options from the startup script.

If you are not familiar with the editing of the startup scripts, the best would be to reinstall the client without any server name. Then create the servers file AND restart nsrexecd.
 
Hi,

I finally found out, what the problem was. The Server was sending the RPC on the wrong interface. I added a route and now it works fine.

I can label and mount the Storage Node and I can try to write Data. Unfortunately it still does not work.

When I start the savegroup I get:

clientname:/ savepnpc: error, no matching devices; check storage nodes, devices or pools

What is the problem with that?

Any ideas?

Tobe
 
This is most likely due to one or more of these facts:

- You did not adjust the Storage Node list for the client
- You did assign a device to a pool and this combination will not match for that backup.
Do NOT assign a device to a pool unless you know EXACTLY what you do.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top