Are you trying to add device to existing library or new jukebox definition? If enw library you need jbconfig to be run from host which controls robotic.
Also, if running this from everest you don't need to specify rd= thing.
This environment has this configuration: Nepal is the NetWorker Server ( he detects the library and its devices). Everest is the storage node ( ls -lart inside /dev/rmt returns the path to the devices, but inquire can not find. Theres a document about this problem but doesnt help to do the configuration that I am trying to do - 420 The inquire Command Does Not Display Devices on Solaris 10.htm). The library is shared between this two servers (DDS) What I am trying to do is to include the storage node in this environment (everest), but the new NetWorker has a new jbedit ( that asks the element address... )
Why don't you simply run jbconfig from server? If I get this correctly you don't have library defined yet. Also, with DDS (if devices would be already defined, you need a bit different approach with jbedit - dunno top of my head correct line, but it has been several times mentioned on this forum so you may search for it).
there is a standard for element addresses, try using changer -va c.t.l:
1 MT Element(s) starting at address 1 102 ST Element(s) starting at address 4096 12 IE Element(s) starting at address 16 5 DT Element(s) starting at address 256
Robotic arms are always from 1-15 (max 15 arms per library) Import/Export slots are always from 16-255 (240 I/E slots) Drives are always from 256-4095 (max 3839 drives!! per library) tape slots are always from 4096 upward.
Basicly if you know the order of drives in the library, you can deduce, drive 1: E=256, drive 2: E=257 etc.
This standard is not always followed by virtualized libraries, like alphastor. ================= You can also check your library resource in nsradmin:
. name: ; type: nsr jukebox show library drive base address; unconfigured devices print
You will have to do a device scan from the gui before you get unconfigured devices.
ble1
4 Operator
•
14.4K Posts
0
December 14th, 2006 06:00
jonatas1
65 Posts
0
December 14th, 2006 08:00
# jbedit -s nepal -j SL500 -a -f everest:/dev/rmt/0cbn -E 500
jbedit: Changing device name from everest:/dev/rmt/0cbn to rd=everest:/dev/rmt/0cbn.
jbedit: RAP error: Cannot find device `rd=everest:/dev/rmt/0cbn' in 'unconfig device names' resource.
Message was edited by:
jgs
ble1
4 Operator
•
14.4K Posts
0
December 14th, 2006 08:00
Also, if running this from everest you don't need to specify rd= thing.
jonatas1
65 Posts
0
December 14th, 2006 09:00
Nepal is the NetWorker Server ( he detects the library and its devices).
Everest is the storage node ( ls -lart inside /dev/rmt returns the path to the devices, but inquire can not find. Theres a document about this problem but doesnt help to do the configuration that I am trying to do - 420 The inquire Command Does Not Display Devices on Solaris 10.htm).
The library is shared between this two servers (DDS)
What I am trying to do is to include the storage node in this environment (everest), but the new NetWorker has a new jbedit ( that asks the element address... )
ble1
4 Operator
•
14.4K Posts
0
December 14th, 2006 09:00
molivier1
2 Posts
0
December 21st, 2006 07:00
xvan_egmond
74 Posts
0
December 23rd, 2006 15:00
there is a standard for element addresses, try using changer -va c.t.l:
1 MT Element(s) starting at address 1
102 ST Element(s) starting at address 4096
12 IE Element(s) starting at address 16
5 DT Element(s) starting at address 256
Robotic arms are always from 1-15 (max 15 arms per library)
Import/Export slots are always from 16-255 (240 I/E slots)
Drives are always from 256-4095 (max 3839 drives!! per library)
tape slots are always from 4096 upward.
Basicly if you know the order of drives in the library, you can deduce, drive 1: E=256, drive 2: E=257 etc.
This standard is not always followed by virtualized libraries, like alphastor.
=================
You can also check your library resource in nsradmin:
. name: ; type: nsr jukebox
show library drive base address; unconfigured devices
print
You will have to do a device scan from the gui before you get unconfigured devices.
regards,
Xander