lsparent: 0514-520 Cannot find information ... after Installation of Emulex' LP8000 driver

[Heiko Swars]

Hi Experts,

HW: 44p Model 170
OSlevel: 4330-10

We removed IBM's FC-Adapter and added an Emulex LP8000.
According to the instructions from Emulex we removed the IBM-FC-driver (with
option "remove dependend software", however) before installing Emulex'
driver.

After that action we receive the following message:
root@host1# lsparent -P -k scsi
lsparent: 0514-520 Cannot find information in the predefined device
configuration database for the following:
PdDv

This problem remained also after reinstalling all the devices.* packages.

Any hint is welcome!
Heiko

[K. B.]

"Heiko Swars" <heiko.swars@ixos.de> wrote in message news:<3f5c9463$0$275$4d4ebb8e@businessnews.de.uu.n et>...

> Hi Experts,
>
> HW: 44p Model 170
> OSlevel: 4330-10
>
> We removed IBM's FC-Adapter and added an Emulex LP8000.
> According to the instructions from Emulex we removed the IBM-FC-driver (with
> option "remove dependend software", however) before installing Emulex'
> driver.
>
> After that action we receive the following message:
> root@host1# lsparent -P -k scsi
> lsparent: 0514-520 Cannot find information in the predefined device
> configuration database for the following:
> PdDv
>
> This problem remained also after reinstalling all the devices.* packages.
>
> Any hint is welcome!
> Heiko

Hi we had a simlar problem....except we had to remove the Emulex cards
and add the IBM b/c we needed the native IBM drivers....a call to IBM
support gave us this script....run at your own risk....but it did fix
our problem. Apparently it is a known issue.

HTH,
Kristie

Could you run the following script, that will identify but not change
any
anomalies in your ODM? Read the header info carefully, as it has
instructions on backing up your ODM before running the script.


#!/bin/ksh
#
################################################## ###########
################################################## ###########
#
# Use this script at your own risk! IBM does not support
# this script. It is supplied to help resolve specific
# problems and has not been heavily tested.
#
################################################## ###########
################################################## ###########
# This script helps repair ODM issues where a fileset is removed
# from the system but does not clean up the ODM completely.
# One sign of this problem is the following error message:
#
# lsparent: 0514-520 Cannot find information in the predefined
# device configuration database for the following:
# PdDv
#
# This script will *IDENTIFY* the bad entry in the PdCn database.
# It does *NOT* remove it. That needs to be done manually.
#
# You *MUST* save the original ODM. This can be done with:
#
# tar -cvf /tmp/ODM.save.tar /etc/objrepos /usr/lib/objrepos
#
# Then to fix the problem, run:
#
# odmdelete -o PdCn -q uniquetype='bad_unique_type'
#
# for example, if this script lists:
#
# Bad link!!! if/IE3/ie3
#
# then run:
#
# odmdelete -o PdCn -q uniquetype='if/IE3/ie3'
#
# This needs to be run for each unique type called out!
#
#
for x in `odmget PdCn | egrep uniquetype | tr -d '"' | awk '{print
$3}' |
sort -u`
do
zz=`odmget -q uniquetype="$x" PdDv `
if [ "$zz" = "" ]
then
echo "Bad link!!! $x"
fi
done