Conference 7.286::fddi

    You need a product called DECndu. It is a layered product and is
    licensed. You and find DECndu on CDROM distribution, but your customer
    will need a License PAK to run it.

    It seems to me wholly unfair to expect a customer, (remember this one
    is running a field test for our benefit), to license a product (DECndu)
    from us in order for us to be able to check his firmware revision. 
    
    What happens in the situation where an FCO is announced which upgrades
    the firmware. How do we get population figures affected? If it means
    running ndu then that implies the customer must have a license.
    
    Is there not some other method, such as SDA poking the device UCB which
    will return a firmware revision for us.
    
    As an aside, does or will ndu ship (and therefore be licensed) with
    every FDDI device. If so then I apologise.
    
    I would like to see another method for getting this information. SDA
    can return it for other devices, can't it? If mail would be more
    appropriate here then thats fine by me, but what does the FDDI
    community think?
    
    Stuart

    I think I may have answered my own question. A kind person has lost his
    DEMFA problem solving guide.!!
    
    In the guide in Appendix C page C-6 it explains how to access H/W F/W
    revision status using SDA. Great stuff!
    
    Well it would be except that the example shows a longword where the
    upper 16 bits decode to h/w and s/w revisions. Well how do these values
    relate to say version 1.3 of firmware? What code should I expect to see
    here for various revisions?
    
    Thanks again for any help.
    
    Stuart

	Show config on the console will show you the firmware revision.

>>> show config

      Type           Rev      Mod SN        Cycle-time
  3+  DEMFA   (0823) C613
  4+  DEMFA   (0823) C613
  9+  MS65A   (4001) 0084     ZG10201367
  A+  KA65A   (8080) 000A     SG104DWC59    q5.3  ns
  D+  DWMBA/A (2001) 0002
  E+  DWMBA/A (2001) 0002
   

	The C6 (upper word) represents the revision field for the module
hardware. The 13 (lower word) is the firmware revision (V1.3 in this case).


Joe

    re:.2 
    
    I agree with you, but in most cases where there is a fix to the code,
    NDU will be given to the customer along with the license at no charge
    (btw, the NDU license charge is very small). From what I understand,
    NDU was originally intended to be use for firmware upgrades for new
    functionality. But anymore these days, new functionality and code fixes
    are in the same releases so it is very likely, it will just be given to
    the customer.

    re .4
    
    Thanks very much, just what I wanted.
    
    re .5
    
    I had a feeling it would be something like this. 
    
    Thanks
    Stuart

	Gentlemen,

	I've recently installed DEMFA's on 2 9210's, 1 on each system.
	Everything went smoothly, so the customer is happy.

	Got one question left:

	With the >>> show config -command I get different printouts:
	once 2512, once 0512 on the version column. Both modules have
	the revision tagged as E03.

	The 12 part of the version means firmware 1.2, so this could
	be updated to 1.3, no questions.

	Can anyone give me the meaning of the difference (05 vs. 25)
	in the rest of the VERSION printout?

	Thanks,

	Bart Rietkerk.
    

    That is supposedly a hardware revision,.. but I don't recognize the
    values nor can I tell you what distinguishes a certain hardware
    revison from another.
    
    Try one of these people (they probably don't read this conference):
    
    	TALLIS::DOLL	! Fred
    	DANGER::GERARD	! Gerard
    	DELNI::G_NIELSEN	! George
    
    								/Bill
    

This is how you can determine that the firmware revision is out of date.
The current revision is 1.0 and it should be 1.3.

SDA> sho lan/summ
LAN Data Structures
-------------------
                -- LAN Device Summary  2-JUN-1992 10:30:25 --

LAN block address  = 945D63A0  (3 stations)
LAN flags:  0002 LAN_init


    Press RETURN for more.
LAN Data Structures
-------------------
LSB address  = 95205380
Device state = 4013 Inited,Run,Timer

                 -- FXA Unit Summary  2-JUN-1992 10:30:30 --

UCB     UCB Addr  Fmt   Value           Client     State
---     --------  ---   -----           ------  -----------
FXA0    945D60F0
FXA1    945DEBE0  Eth   60-07           SCA     0017 Strtn,Len,Uniq,Strtd
FXA2    948D1890  Eth   60-03           DECNET  0017 Strtn,Len,Uniq,Strtd
FXA3    948D1FF0  Eth   60-01           MOPDL   001F Strtn,Len,Uniq,Share,Strtd
FXA4    948D22A0  Eth   90-00           LOOP    001D Strtn,Uniq,Share,Strtd


    Press RETURN for more.
SDA> ex 95205380+784 	! This is the offset into the LSB that contains the REV
FXA+00784:  05100823   "#..."
SDA> ! the hardware rev is 05 and the firmware revision is 1.0
SDA> exit
    

    While .-1 seems to have worked correctly for this release of VMS,
    the offset to the field in the LSB that contains the hardware/frimware
    revision may changhew ithout warning in future releases. You need
    to locate the correct listing for FXDRIVER for each release and
    verify the offset before putting much faith in what SDA shows.
    
    The '0823' (hex) in the low order 16 bits is a big clue that you 
    got it right because thats the XMI device ID for the DEMFA. That
    should always be there regardless of hardware/frimware revision
    which appear in the high order 16 bits.
    
    							/Bill
    

    Use the DOWNLOAD SHOW VERSION command on NDU, if you have it installed
    on the system. Consult help on DOWNLOAD for more information about
    using this command.