I am doing a Disaster Recovery test at a remote site
My OS is AIX 7.1
Networker is 8.2
The OS sees the jukebox and the drives:
but jbconfig says there none or all configured
And jbverify also says there are none
The NMC does not show any either
Any help is appreciated
NW does not use special drivers for drives. Consequently it has to rely upon what the OS reports.
What does inquire report?
If this does not work, NW will not be able to successfully install the jbox.
Of course you must run jbconfig at the node which controls the jbox.
the inquire command shows Total: 0
the jbconfig command shows: All jukeboxes that are connected are already configured. No new jukeboxes are found on host
the jbverify command shows: no enabled stand alone devices found. no enabled jukeboxes found in database
the lsdev -Cc tape command shows:
rmt0 Available 01-01-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt1 Available 01-01-02 IBM 3580 Ultrium Tape Drive (FCP)
smc0 Available 01-01-02 IBM 3584 Library Medium Changer (FCP)
I expected the smc0 to be showing "Defined", not "Available"
Please refer to the following knowledge base article for additional information
smc0 driver conflict causes MODE_SENSE failure during jbconfig run
Cause: If the atape driver is already installed, when you do a reboot with the IBM autochanger connected, the device with the logical name smc0 claims the robotic device initially. A conflict exists with the lus driver which prevents NetWorker from accessing the driver properly.
You can verify this by using the lsdev -Cs tape command. Look for smc0 to determine whether it is in the "Available'' state.
# lsdev -Cc tape
rmt0 Available 00-01-01-4,0 Differential SCSI DLT Tape Drive
rmt1 Available 00-01-01-5,0 Differential SCSI DLT Tape Drive
smc0 Available 00-01-01-6,0 IBM 7337 Tape Medium Changer
To place smc0 in a "Defined" state, please issue the following command:
rmdev -l smc0
DO NOT remove smc driver if in a SAN environment, (do not run"rmdev -d")!
Note that if the AIX Networker server reboots, smc0 will automatically become "Available'' and the lus driver becomes "Defined" and Networker will not be able to operate the jukebox. Edit the /etc/rc.nsr startup file so that the lus driver will continue to be available after a reboot. Add the two lines below:
rmdev -l smc0
mkdev -l lus
when I did that, rmdev -l smc0 and mkdev -l lus I get:
mkdev: 0514-519 The following device was not found in the customized device configuration database:
name = 'lus'
the lus driver is installed as part of the NetWorker storage node package. So there is no reason I can think of why it would not be on your system.
What specific version are you using? 8.2.what.what?
Try reinstalling and see if you still having the same problem.
Since this is a DR test, what steps have you done so far?
Is NetWorker already installed? Is it the same version as the production Networker server?
What is the DR Networker server's hostname. Is it the same as the production Networker server?
At this DR site, are the n/w server, storage node, and clients all defined in DNS? Alternatively, are they defined in the Networker server's host file?
If there are no configured devices yet, then use NetWorker Management Console to scan for new devices, and then configure your jukebox and drives.
Have you recovered the Networker bootstrap?
After recovering the bootstrap, you may have to delete the jukebox and drives, and then scan and configure the jukebox and drives again.
Networker is installed and I am trying to get the jukebox to work on the host
There is no DNS server, all clients are in the /etc/hosts file
Here's the scenario for the DR site:
They spin up the correct number of Lpars (virtual servers) with our specifications for size and IP addresses
We boot from an image (mksysb) and from there we are supposed to be able to recover using Networker
I have booted the Networker server/NIM server but now I cannot get it to see a jukebox