Lanscan error

[likid0]

Hy,

We are usind 11.23 os, and we are having some problems after patching the system with itrc swainv analysis. anyone has an idea what patch or what is the posible cause workaround to get lanscan working?

i get this error:

hwiftp: bad read (1) lanscan


there is not a lof of info in google about this error

[Raj D.]

Daniel,

You can execute # lanscan from command prompt and check if it is working. Then go further debugging the error,

Cheers,
Raj.

[Coolmar]

Hi,

Yeah, there isn't much but I did find this thread which might help you out. It turned out that the kernel that booted was not the same as what was in /stand. That may or may not be your problem, but there are some good troubleshooting ideas.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=984515

[likid0]

Thnx Coolmar, that thread has helped, but i still have the problem, what i have found out is this:

co2:/stand# lanscan
hwiftp: bad read (1)
co2:/stand# mv vmunix vmunix.good
co2:/stand# mv vmunix.prev vmunix
co2:/stand# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
1/0/10/1/0/6/0 0x0016353E9 0 UP lan0 snap0 1 ETHER Yes 119
1/0/12/1/0/6/0 0x0016353E9 1 UP lan1 snap1 2 ETHER Yes 119
1/0/8/1/0 0x00306EEA6 2 UP lan2 snap2 3 ETHER Yes 119


if i move the prev kernel into stand it works ok, so my question is what do i do next??, i dont want to go back to the old kernel because i loose the changes the patches have made to the kernel so ....

what is the best choice??

[V. Nyga]

Hi,

check which patches belong to lan and try to patch your system without these patches.

See what happens ...
HTH
Volkmar

[Sameer_Nirmal]

The error indicates a bad structure of network interfaces information in the /stand/vmunix.

Check the patch state first using
# swlist -l fileset -a state
# cleanup -s

Check the lan patches applied. I guess removal of Lan Cummulative patch and generating the new kernel would resolve the issue.

[Coolmar]

Yeah, I would remove any lan related patches from the patch depot. Then if it all works, try and install each lan patch one at a time and try and find out which one causes your problem. I don't know if swverify will show any valuable information to you but you can try that on the patches.
When you narrow it down to which patch is the problem, then try and find an earlier version of the patch or even open a call with HP.

[Coolmar]

Hi again Daniel,

I found the following thread, but it also seems to be left unsolved. It may have some more troubleshooting you could do. Also, see what Sridhar says about having the same problem after installing a patch bundle, without rebooting and then running lanscan. Did you reboot after the patch install? I think he might be suggesting that, but can't really tell. You could also try and get hold if him and see how he solved it as there really is not much out there regarding your error on the internet.

Good luck, and when you solve it make sure to post "how" to this thread for the next guy.

[Coolmar · Accepted solution]

I guess it helps if I actually paste the link in for you....

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=105801

[Bill Hassell]

lanscan is just one of many symptoms where the current kernel does not match /stand/vmunix. Another command is ipcs. These commands need to refer to the bootable kernel file as part of their operation. Normally, this happens when root builds a new kernel but defers the reboot.

[likid0]

Yes, i would relate ir more to some problems when the patches where installed, than actually the patches, because i have used this bundle in 8 servers and all of them installed the same amount of patches, and only 2 have the same problem.

the machine actually had a reboot when i installed the patch, is recompiling the actual kernel put it in place and recompile a good idea??

thnx a again

[Sp4admin]

Hi Daniel,

Verify that your at the right patch level. If this is do to a kernel change I would back out the kernel and see if the problem is still there. if the problem continues open a call with HP.


sp,

[likid0]

hy people,

The problem is over, this had happen to me some time ago, and i just remember yesterday, the thing is:

Before patching a split the mirror, once it is in split a forgot to check that the disk where in the lable is the sames as the one that is in the primary boot.

So i was patching one disk and booting from the
other one, once i got to boot from the same disk as the one i patched it all works ok.

Its a good thing to remember:

after spliting vg00, always check that the disk you have in the lable is the same as the primary boot disk.


Thnx!!

[likid0]

i posted the solution in the above post


thnx all