ITEM: DJ3504L

swap_adapter fails with error code 0514-062: device busy


Env:  4.2  Model C10  HACMP 4.2

Problem:  Adapter swap - 0514-062

Action Taken:  Joe is having an ethernet adapter swap fail with 
        0514-062 device is busy when it issues the rmdev -l ent1 command.
        He is currently running SNA and has informed me that it is set 
        to come down forcefully.  I told Joe that he will have to find 
        out what process has a hold of the ent1 and is not releasing it 
        during the IPAT with hardware address takeover.  He will test 
        this and callback

*ACTION TAKEN:  Spoke to the customer and he indicated that he is still
        having the same problem after he killed all his apps.
        *ACTION TAKEN:  NLM informing customer that we just release HACMP 
        4.2.1.1 upgrade.  I informed him that I would like to send him 
        the upgrade to see if that helps him.  I basically needed to 
        confirm his address and the type of media he needs.  

Action taken: Customer upgraded his hacmp and he is still seeing a
        problem with doing a rmdev -l on ent0, getting a device
        busy. I explained this is not really a hacmp problem but
        a tcpip problem with some process hanging on the device.
        The only process that looks like it could be causing a
        problem is the dpid2 process which allow video viewers
        access to SNMP.

Action taken: I used the following procedure to find out what 
        was holding open ent1.

ndb
address of tcb is 0x01a17ef0
address of udb is 0x01a1bca8
type ? for help

ndb> ndd
address of ndd is 0x0016d8b4
    ---------------------- NDD INFO -----(@0x054c901c)----------
    name: ascsi0*        alias: none    ndd_next:0x0a0f0020
    flags:0x00000008    (RUNNING)

.... bunch of info ...

ndb.ndd> n
    ---------------------- NDD INFO -----(@0x0a0f0020)----------
    name: ent0           alias: en0     ndd_next:0x00000000
    flags:0x0240010b    (UP|BROADCAST|RUNNING|ALT ADDRS)

    ndd_open():  0x019a45cc  ndd_close():0x019a4614  ndd_output():0x019a4608
    ndd_ctl():   0x019a45d8  ndd_stat(): 0x019a73f8  receive():   0x019a73d4

    ndd_correlator: 0x0a0f0000   ndd_refcnt:         1
    ndd_mtu:           17800     ndd_mintu:          16
    ndd_addrlen:           6     ndd_hdrlen:         14
    ndd_physaddr: 08005a0d23f3   ndd_type:           9 (Ethernet)

    ndd_demuxer:    0x019a7528  ndd_nsdemux:     0x05a60000

... more info ...

ndb.ndd> dmx 019a7528 (from ndd_demuxer)
    ------------------ DEMUXER INFO -----(@0x019a7528)----------
    type: 9 (Ethernet)        nd_next:0x00000000

... more info ....

802.2 Filters:
type DSAP org  etype  isr      isr_data   queue    fmt  netisr   ifp
---- ---- ---  -----  ---      --------   -----    ---  ------   ---
SNAP AA   000  800    1a17388         0         0   2      0     a12f000
SNAP AA   000  806    1a17544         0         0   2      0     a12f000

ndb.ndd> quit
ndb> quit

Exiting.
\# crash
WARNING: Using crash on a live system can potentially
         cause a system crash and/or data corruption.
> ts 1a17388   (from isr)
        .[edl.ext:DATA] + 0x00001568
> q

        Through some data searches I found that this kernel extension
        is used by DLC which is manily used by SNA. 
                I told the customer this and he said he was not using SNA 
        over ent1, but he went ans looked at his SNA configuration
        and sure enough ent1 was in there. He removed this adapter
        from SNA and the swap_adapter test worked fine.

Action Plan: close



Support Line: swap_adapter fails with error code 0514-062: device busy ITEM: DJ3504L
Dated: September 1997 Category: N/A
This HTML file was generated 99/06/24~13:30:16
Comments or suggestions? Contact us