Conference 7.286::fddi

>>    Is DEFPA-AA firmware rev 2.46 supported on 4.0a Dunix 4100??

I believe the 4100 (Rawhide) systems have only officially qual'd the DEFPA-*B
variants.  In any event, the firmware (v2.46 for -AA/AB, -DA/DB, and -UA/UB) is
the same for now.

We do have a new firmware image (v3.1) release which is already available
electronically for Intel-based upgrades and is scheduled to ship with
the v3.9 Alpha FW CD.

>>    ON bootup, we get fwa0 pdq_state_k_link_unavailable. Check cable. 
>>    
>>    Same error with loopback connector or cabled up to fddi multiplexer.

Are you only seeing this behavior on the 4100?  Does the link ever come up?  If
so, I wouldn't be too concerned about the error message during boot since it
does take a second or two to start the link even with a cable attached.

-Larry

    
    the link never comes up. 

Since the DEFPA uses SC connectors, trying swapping the cables into
the DEFPA.  (it's easy to get them backwards) 

    Hi.
    I got the same problem on two 8400's.
    There are two DEFPA-AA in each pci-box and each of the DEFPA's is
    connected point to point between the 8400's.
    I'm using BN34B-10 cables and they are crossed at the other end.
    
    The LED comes on flashing on boot/init but thats all.
    I get same error as .0 and there is no change when unix comes up.
    Console FW is 4.1-6,I also tested 4.0-4. DEFPA fw is 2.46.
    
    Am I missing someting ?
    Please,any hints most welcome.
    
    regards, Jonas

>>    I got the same problem on two 8400's.
>>    There are two DEFPA-AA in each pci-box and each of the DEFPA's is
>>    connected point to point between the 8400's.
>>    I'm using BN34B-10 cables and they are crossed at the other end.

OK, here's how it should work when link is coming up.

You have both DEFPA-AA adapters connected point-to-point and BOTH LEDs are
constantly flashing green.  I don't mean they flash green a few times then go
out.  I mean a STEADY on-off of the LED on BOTH adapters.

Once you're in this state, the adapters are trying to establish a link.  If you
don't have cable connected properly, if it's not crossed-over properly, or
simply if the cable is bad, you will NOT establish a link and both adapters
will continue to have a STEADY flashing green.

>>    The LED comes on flashing on boot/init but thats all.

During power cycles or bus resets, the DEFPA LED will flash green 3 times then
go off.  This is an indication that the on-board diagnostics have passed.  This
event is separate from the link (un)available state.

>>    I get same error as .0 and there is no change when unix comes up.
>>    Console FW is 4.1-6,I also tested 4.0-4. DEFPA fw is 2.46.

It's quite possible that the console is testing the link before it's brought
the adapter to a start state.  Please recheck the LEDs.  If they're not both
steady flashing green at the point you're interested in, don't bother checking
the cable, you'll never establish a link.

- Larry

    Hi.
    I notice the following.
    Alpha "A" allready booted.
    
    On Alpha "B":
    -------------
    power on machine            : led's off
    machine does selftest       : led's doing several very quick flashes
    machine config I/O devices  : led's going to steady on/off
    
    and the following messages
    "fwa0.0.0.10.1 pdq_state_k_link_unavail"
    "DEFPA Error: fwa0.0.0.10.1 can not be started"
    "DEFPA Error: please check FDDI connection"
    
    machine boots               :  led's steady on/off
    machine booted              :    ------  "  ------
    
    I have used all four DEFPA's and replaced fddi-cable;same result.
    
    / Jonas

    Try looping back the BN34B cable at the adapter to see what happens.
    For example, both black (or red) colored connectors of one BN34B 
    into the SC port.  You should see the green LED blink three times 
    approximately 7s after power up.  Then if the system tries to
    establish a link the LED should go solid green.  Try this on both
    systems and report the results here...
    
    Roger
     

    Hi.
    The result is exatly as in .6
    After powerup there is three fast blink and when system 
    configuring I/O devices, defpa switch to slower blink and
    these slower blink is on until I shutdown system.
    I've tested all four defpa's with two different BN34B.
    
    I just checked another entry I made about this error.
    Please read note 1096 in msbcs::turbolaser conference.
    This seems to the fix.
    I'll try to get V4.8-6 from the net.
    
    Thanks for your help , / Jonas

Note extracted from MSBCS::TURBOLASER conference which addresses link
unavailable issue and suggested fix.

- Larry


          <<< MSBCS::DISK$SYSTEM2:[NOTES$LIBRARY]TURBOLASER.NOTE;1 >>>
                                -< TurboLaser >-
================================================================================
Note 1096.8                        DEFPA Error                            8 of 9
AFW4::CROXON "Peanuts, Popcorn, Consoles anyone?"     4 lines  13-FEB-1997 07:46
--------------------------------------------------------------------------------
    Fixed in the V4.8-6 Console firmware version.
    Which will be on the 3.9 AXP CD, due out in March 97.
    
    -Nigel

    Hello.
    This new FW didn't fix it.
    It's the same steady flashing.The only difference now is that 
    system initializion doesn't try to start the link it just finds
    the adapters (fta0 and fta1) and there are no error messages.
    
    Later during boot, links tries to start and there is 
    a "no link available" message.
    
    What to do ???
    
    / Jonas

Jonas,

Did you install the loopback as suggested in .7?  Did the LED ever go from
blinking green to solid green?

If not, then either the loopback is bad or the adapter is bad.  You're using a
DEFPA-AA (SAS multimode fiber), right?  Do you see the same behavior with other
models?

- Larry

    Hi, Larry
    I used the fiber cable as a loopback.
    Red to red on the defpa connection.I tried this on all four defpa's-aa
    I tried another 10 meters fibercable.
    Summary:
    I have tested four difference defpa and two fibercables,using the four
    pairs (black/red) as loopback.
    The LED NEVER go from blinking green to solid green.
    
    I have not tested other defpa models.
    
    / Jonas 
    

>>                             -< NEVER solid green >-

It sounds like there's something wrong with those boards.  If the cable is
good, the boards are at a link unavailable state (denoted by a steading
flashing green LED), and the loopback is good, the LED should become solid
green.

I don't know why you're seeing this behavior after testing 4 boards and various
cables, but you should bring field service in.  If you happen to have a
Intel-based machine running DOS, you may want to plug one of the DEFPAs into
that system and run the INSTVER.EXE utility.  This DOS-based diagnostics
utility can run various tests on the DEFPA and see where any failures are.
You can also run internal and external loopback tests using INSTVER.

- Larry

    Hi.
    I managed to get the defpa's to work OK.
    The problem is that they doesn't work in all pci slots.
    Right now they are working ok in slot # 4 ( 0-11) in the DWLPB's .
    I'm not sure of wich slot's are OK but slot # 10 doesn't work !!
    ( It's same in both systems )
    I did some testing yesterday but unfortunally one of the defpa's
    was bad,so that one gave me strange results.
    
    The pci box config right now:
    slot #   device  
    ------   ------
    11
    10
     9
     8
     7       KZPSA
     6
     5       KZPSA
     4       DEFPA-AA
     3       Memory channel
     2       Memory Channel
     1
     0        
    
    Today I will do some more testing.
    I'll put the result in the turbolaser conference ,note 1096
    
    / Jonas

    I don't know about turbolaser's PCI backplane, but some systems
    have 1 or more PCI slots that do not support bus mastering (no REQ
    or GNT signals), while the other PCI slots in the system do.
    The DEFPA requires a PCI slot that supports bus mastering. 
    
    Regards,
    Roger