|  | down show dev fxa0:
I think that's right.  You can't see the firmware revision of remote DEMFAs
using NDU.  (Though if you can trace the MOP SYSID packets, the firmware
revision is included at parameter 101)
From 08-00-2B-29-91-20 on device fta0 at Tue Feb 23 15:20:09 1993
To   AB-00-00-02-00-00, System ID (size = 37/37, reserved = 0x00, receipt = 0)
    Maintenance Version: V3.0.0
    Functions: Loop
    Hardware Address: 08-00-2B-29-91-20
    Communication Device: MFA (93)
        DEMFA XMI FDDI comm link
    Comm Device Related (101) (2 octets):
        1400.... ........ ........ ........     0x0000  ..
    Data Link: FDDI
From 08-00-2B-27-E2-55 on device fta0 at Tue Feb 23 15:20:29 1993
To   AB-00-00-02-00-00, System ID (size = 37/37, reserved = 0x00, receipt = 0)
    Maintenance Version: V3.0.0
    Functions: Loop
    Hardware Address: 08-00-2B-27-E2-55
    Communication Device: MFA (93)
        DEMFA XMI FDDI comm link
    Comm Device Related (101) (2 octets):
        1200.... ........ ........ ........     0x0000  ..
    Data Link: FDDI
 | 
|  |     
    Oh ya.  I saw the Note: within the VMS help that mentioned the FDDI
    controller 400 wouldn't respond, becuase it didn't use RBMS, but I
    didn't know that the 400 was actually a DEMFA, untill I did a "download
    list".
    
    Ok. What about the firware upgrade?  How will I be able to do the
    upgrades?   Will I be forced to install NDU on every system with a
    DEMFA?
    
    Another question:  From what I hear DECndu will soon be unsupported as
    we move to a replacement application.  What is this replacement called,
    when will it be available, and what will it require.  Oh, and will 
    remote upgrades work from source nodes using FDDI controllers as
    Network Interfaces?
    
    Thanks,
    Mike
    
 |