UNSOLVED
Set CDI=not used by command or script
Hi,
I have a Networker Server 7.1.3 in a Solaris 8 with sevaral SN and DDS tapes in a SAN environmet and a Silo ACSLS.
Each time I install a new SN, I have to run jbconfig to create the new tape devices in SN. Then I must edit all tape devices and set CDI = not used. I have about 90 tape devices and this is a hard task, because I am setting this value by Networker Admin.
Is it possible to create a script to set the value of CDI parameter of all tape devices at the same time??? How??
Regards,
I have a Networker Server 7.1.3 in a Solaris 8 with sevaral SN and DDS tapes in a SAN environmet and a Silo ACSLS.
Each time I install a new SN, I have to run jbconfig to create the new tape devices in SN. Then I must edit all tape devices and set CDI = not used. I have about 90 tape devices and this is a hard task, because I am setting this value by Networker Admin.
Is it possible to create a script to set the value of CDI parameter of all tape devices at the same time??? How??
Regards,
416
0
Posted September 25th, 2006 07:00
Hi,
I set CDI=not use because some errors.
Can you tell me how do it via nsradmin??
Thanks416
0
Posted September 25th, 2006 07:00
Hm...OK, it your call.
There are two ways; via script and interactive one. Here is the second one (for the first one there are examples in past threads):hcrvelinin NetWorker administration program. Use the "help" command for help, "visual" for full-screen mode. nsradmin> show name nsradmin> show CDI nsradmin> print type: NSR device [list of devices and their CDI status] nsradmin> update CDI: Not used CDI: Not used; Update? yes updated resource id 1.175.25.139.0.0.0.0.0.0.0.0.69.9.81.108.10.1.8.30(176) CDI: Not used; [typing yes n times where n in sumber of devices]
Obviously first approach would be better via script (as you don't need to type anything at all), but as I said - do some research and you will find it. And once you see it how easy it is you will use it until end of your life.416
0
Posted October 17th, 2006 19:00
View NW Admin in diagnostic mode >>
devices >> advanced tab
CDI: not used SCSI commands
click ok
will need to restart the NW deamons for change to take
will prompt to let you know this.416
0
Posted October 18th, 2006 08:00
Access the /nsr/debug directory and create a file named
cdidisable. Then restart the NetWorker server. This file does not need any
contents ¿it simply needs to exist. This will disable the use of CDI for that
server and all storage nodes controlled by that server.
After this, all the created new devices and the configured ones, will appear like CDI Not used.416
0
Posted December 16th, 2006 01:00
Although not officially supported you can add devices to a silo without having to use jbconfig:
- create the needed tape unit
- open nsradmin
- option hidden
- . name: ; type nsr jukebox
- edit (only on unix)
use vi to edit the jukebox resource:
- add the drive in the correct place in the device listing
- add 1 to number of devices
- add an empty field in: loaded volumes/slots/barcodes.
In nw73 and up you may need to add some other fields for this to work, but I do not have a 73 server with silo.416
0
Posted December 17th, 2006 12:00
Although not officially supported you can add devices
to a silo without having to use jbconfig:
Procedure you listed won't work for silo. Besides, why would you use nsradmin to add devices belonging to jukxbos/silo?416
0
Posted December 23rd, 2006 16:00
Hrvoje,
the procedure I describe will not only work, we use it several times a month when adding drives to a powderhorn silo of ours. I do not know if it will work on nw73 though.
recently I have rearranged the devices in our powderhorn te reflect their acsls location, so you can even change the order in which they are represented by nsrjb.416
0
Posted December 24th, 2006 03:00
Xander, is there any reason why one should use unsupported resource editing instead of jbconfig script which is fully supported? It takes less than a second to run such script. With nsradmin editing you re in waters which are not supported and from what I have seen there are at least two good reasons for that (out of the scope of this thread). Actually 3 if we involve the fact that support will tell you to take a walk after describing what and how did you do it.
ble1
6 Operator
•
14354 Posts
•
56186 Points
416
0
Posted September 25th, 2006 05:00
I know 7.3.2 had in plan to enable jbedit to work with Silo devices - didn't check it if made to GA, but future looks bright from that perspective. May I ask why do you set CDI not to be used? I use silo and we do use CDI.