Stopped Devices

[SaraLouise]

When I enter lsdev -C the en0 device is listed as "Stopped". How do I make this device available again.

 

[PSD]

Sara,

You could try a few things:

mkdev -l en0

ifconfig en0 up

or smitty tcpip - and press return in the en0 config. panel.

Hope that helps

PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP

 

[SaraLouise]

I have tried the following with these results:
mkdev -l en0 en0 Stopped
ifconfig en0 up can't stat driver path, /dev/en0: No such file or directory
smitty tcpip A list of errors including lsattr 0514-530


This last error implies that en0 is not in the predefined database and yet I know it is. used odmget to put it there.

Any other ideas

 

[PSD]

Sara,

O.K., have you tried removing it and running cfgmgr to see if it gets picked up correctly:

i.e.

rmdev -l ent0 -d
rmdev -l en0 -d
cfgmgr

If this does not work then you may have a case of ODM corruption. Let me know the results of the above first and then we will look at the ODM side of things.

Cheers PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP

 

[SaraLouise]

Thanks for those tips, here are the results:
rmdev -l ent0 -d
0514-519 the following device was not found in the customized device configuration database name = "ent0"

So I tried to add it using odmget from another box, ftp and odmadd but to no avail cfgmgr still doesn't pick it up.

I think you may be correct in that the ODM is corrupt. But as this is a ubique box here I don't know what to do next. Any Ideas!

Just to confirm I have checked the hardware side of things and that is all OK

Cheers

 

[PSD]

Sara,

Hi, what happens when you just try removing en0?

rmdev -dl en0

If you then do an lsdev -Cc adapter it should disappear from the list, then run cfgmgr. Does it then re-appear correctly?

Also, lets check the output of the following, below is a list of all en0 and ent0 configuration from the ODM perhaps you could compare this with yours:

CuAt:
name = "en0"
attribute = "netaddr"
value = "10.10.10.1"
type = "R"
generic = "DU"
rep = "s"
nls_index = 4

CuAt:
name = "en0"
attribute = "netmask"
value = "255.255.255.0"
type = "R"
generic = "DU"
rep = "s"
nls_index = 8

CuAt:
name = "en0"
attribute = "state"
value = "up"
type = "R"
generic = "DU"
rep = "sl"
nls_index = 5

CuAt:
name = "ent0"
attribute = "busio"
value = "0xbff800"
type = "O"
generic = "D"
rep = "nr"
nls_index = 3

CuAt:
name = "ent0"
attribute = "busintr"
value = "6"
type = "I"
generic = "D"
rep = "nl"
nls_index = 4
name = "ent0"
name = "ent0"

CuDep:
name = "en0"
dependency = "inet0"

CuDv:
name = "en0"
status = 1
chgstatus = 1
ddins = "if_en"
location = ""
parent = "inet0"
connwhere = ""
PdDvLn = "if/EN/en"

CuDv:
name = "ent0"
status = 1
chgstatus = 2
ddins = "pci/phxentdd"
location = "10-60"
parent = "pci0"
connwhere = "96"
PdDvLn = "adapter/pci/23100020"
name = "ent0"
value3 = "ent0"

CuVPD:
name = "ent0"
vpd_type = 2
vpd = "*YL P1/E1"

CuVPD:
name = "ent0"
vpd_type = 0
vpd = "*NA "
name = "ent0"
name = "ent0"


Let me know if this output concurs with yours?

Cheers

PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP

 

[SaraLouise]

After removing the ent0 and en0 cfgmgr does not bring the device back into the list of lsdev -C.

So next I tried checking out the ODM files to compare with yours. At this point I am going beyond my current knowledge base.

I went to the /etc directory there I found CuAt and more but when I used cat to open them I got nothing back. So I tried to open them with vi. Now the files show as empty. with the exception of CuVPD to which the response was "cannot open"

I am looking in the right place? If so do you have any other suggestions. I am out of the office for the rest of this week but will check back on Monday. Any suggestions would be greatly appreciated.

Cheers

 

[PSD]

Sara,

To be honest that should have sorted your problem out, have you tried configuring an IP address? Also it you run lsattr -El ent0 : this should now return an output.

If you want to compare the output to my machine you need to use the odmget command:

Here is a simple for loop I used to interrogate the ODM:

cd /etc/objrepos

for i in `ls`
do
echo $i
odmget -q "name=en0" $i >> /tmp/odm.result
odmget -q "name=ent0" $i >> /tmp/odm.result
done

You will see some errors as you cannot open all files in /etc/objrepos but the command just fails on those. The output in /tmp/odm.result file will be similar to mine in the previous post : the title of the file above and the en0 and ent0 and what details it has on which in each file. Post up the results if you still have a problem, but in theory you should be o.k.

Take Care



PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP

 

[PSD]

Sara,

Ignore the first part of my last message, I read it wrong, I thought that you said it DID bring back the adapter in the lsdev list. Wishful thinking!!

Run the for loop and compare with the output from mine.

Cheers

PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP

 

[SaraLouise]

Eventaully back in the Office and have run your excellent script. The output is a little worrying! There are only 2 entries in the results file which are:
CuAt:
name = "ent0"
attribute = "dma_bus_mem"
value = "0x200000"
type = "M"
generic = "D"
rep = "nr"
nls_index = 16

CuAt:
name = "ent0"
attribute = "dma_bus_mem"
value = "0x200000"
type = "M"
generic = "D"
rep = "nr"
nls_index = 16

In my limited knowledge I believe this means the database is corrupted. How do I progress this as I have no similar boxes? Any help will greatly appreciated.

Many Thanks
Sara

 

[PSD]

Sara,

I have just come back after a week off last week, off sick unfortunately.

I would expect more entries than just two in your ODM database. Can you just confirm what version of AIX you are using?

One thing you could try is:

rmdev -dl ent0

rmdev -dl en0

then:

smitty mkinet

Add en0 through the smit menu rather than through cfgmgr, this sometimes works when cfgmgr does not. Input all the IP configuration.

If this does not work:

Do you have any backups of /etc/objrepos when the interface was working? if so you could try restoring them i.e. into /tmp and then set the ODMDIR environment variable to be the said directory:

i.e.

insert mksysb

cd /tmp

mkdir test

cd test

restore -s4 -xvqdf /dev/rmt0.1 ./etc/objrepos

export ODMDIR=/tmp/test/etc/objrepos

Re-run my little ODM script.....

Hope that helps

PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP