Unsolved
This post is more than 5 years old
2 Intern
•
202 Posts
0
3698
Changed boost user password in Networker
Dear NW Experts!
Our customer usning NW9 and DD2500 with boost devices with Ethernet.
We have two boost devices, and i created different boost user for each storage unit.
device1: boost1 user
device2: boost2 user
We can see the DD in the NMC gui screen.However i forgot boost1 password, and i unmounted
the device and changed the username to boost3 username and changed the password of the
user.So look like:
device1: boost3 user
device2: boost2 user
Meanwhile which i make this operation, Networker is doing the following thing:
Post the following message:
- Warning: making the device1 from normal to suspect
- Warning: making the device2 from normal to suspect
I cannot mount a previous volume on the device1:
opening the file ddp_open_file() failed
Err: 5034-access denied
And i cannot use device2 because it is suspect.
Please help us how can i fix quickly this problem!
Thanks a lot!
BR:
Pal
bingo.1
2.4K Posts
1
January 25th, 2018 05:00
Changing the username and passwords is only possible if you do that at the DD and within NetWorker.
Both settings must match, of course.
I am not sure whether the access information is also be placed on the backup media itself (in the label?).
If this would be the case, then you most likely have to retrieve your old password.
Support might be able to help here.
bingo.1
2.4K Posts
1
January 25th, 2018 10:00
Are you sure you are talking about a suspect device? - the only resource I know are suspect volumes.
If it is a volume you should be able to reset the status by running "nsrmm -o notsuspect ".
If you talk about the device, it could be in 'service mode'. Just set it to "enables = yes".
You my try to restart the NW service/daemon on the storage node to start wit a fresh nsrmmd process.
paulo3
2 Intern
2 Intern
•
202 Posts
0
January 25th, 2018 10:00
Thanks a lot!
Another thing which is found:
- one device is enabled on the server (user: xy)
- one device is marked suspect on the storage node (user: xy)
How can we that resolve? Do you have any suggestions?
I cannot unmount the device on the storage node, and i cannot disable and enable that device.
Thanks a lot!
BR: Pal
paulo3
2 Intern
2 Intern
•
202 Posts
0
January 25th, 2018 10:00
Thanks a lot!
Another thing which is found:
- one device is enabled on the server (user: xy)
- one device is marked suspect on the storage node (user: xy)
How can we that resolve? Do you have any suggestions?
I cannot unmount the device on the storage node, and i cannot
BR:
Pal Szabo
paulo3
2 Intern
2 Intern
•
202 Posts
0
January 25th, 2018 12:00
Hi!
Yes, it seems that for that device said: suspected
I set up to: service mode
After that i enabled, and it mounts well. (for device2, where not changed a password)
For the another device (device1) we still have issues with the mounting:
opening the file ddp_open_file() failed Err: 5034-access denied
BR:
Pal
bingo.1
2.4K Posts
0
January 25th, 2018 13:00
Please see Preston's blog (nsrd.info) on read his note dated 2017/09/28:
"Basics – device `X’ is marked as suspect"
I do not place the link here as EMC will moderate my answer and it will take longer before you get this info.
bingo.1
2.4K Posts
0
January 25th, 2018 13:00
One more thing ...
I am just cleaning up stuff an discovered that such happened even to myself a while ago:
In my case I saw the following message in the device's Volume tab:
The reason for my trouble was that I wanted to connect a NW 9.2.0.5 server to a DD running DDOS 5.6.
I am pretty sure that this is not supported. However, for a tiny test environment it might have work. Well, it did not.
So watch out for similar messages.
paulo3
2 Intern
2 Intern
•
202 Posts
0
January 28th, 2018 14:00
Hello!
Thanks a lot!
Your comments quite useful. I met a NW version / DD OS boost incompatibility some time.
This problem is solved.
I recognized the following:
1. It is advisable if all of the NW devices using the same boost user on the NW.
2 I have to restart the storage node daemon on the host, which causing the suspect / normal behaviour on the devices.
Thanks a lot!