| Title: | FDDI - The Next Generation | 
| Moderator: | NETCAD::STEFANI | 
| Created: | Thu Apr 27 1989 | 
| Last Modified: | Thu Jun 05 1997 | 
| Last Successful Update: | Fri Jun 06 1997 | 
| Number of topics: | 2259 | 
| Total number of notes: | 8590 | 
    	Hello All,
    
    1. Is DECndu v1.1 for Ultrix available on the network?
    
    2. Will V1.1 of the DECbridge 610 f/w allow SNMP "sets"?
    
    3. Does it work dll'ing via the FDDI interface (instead of ethernet?)
    
    	I've a customer trying to use ndu v1.1 (setld shows NDUBIN110) on
    his DS5000 to upgrade a DB610 with the following command:
    
    "ndu -i -v -c fza0 -u ether_addr /usr/kits/FEB_II110/defeb_6xx_110.sys"
    
    he gets:
    
    "ndu: beginning downline load"
    "error during parameter load"
    
    	Then, a subsequent display of the bridge's attributes shows V1.0
    f/w still intact.
    
    	Any responses or pointers to s/w on the net (so's I can try it here
    in the lab) appreciated.
    
    					Chuck CSC/CS
    
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 431.1 | update - fails only on FDDI port of DS5000.. | BSS::C_OUIMETTE | Holographic Interference Repository | Wed Dec 18 1991 20:02 | 14 | 
|     	Update: I had the customer try doing the upgrade via the DS5000's
    ethernet port instead of the FDDI port- It worked fine. Ultrix 4.2.
    
    So: known bug/limitation with ndu V1.1?
    
    Also, he can't ping the DB610 unless he puts a manual ARP entry on the
    spurce node, we suspect perhaps a problem with the IP netmask on the
    DB610... is this settable? (thus, the request for documentation in this
    & following note...)
    
    	Any pointers/answers appreciated.
    
    				chuck
    
 | |||||
| 431.2 | Same problem | COMICS::REYNOLDSJ | Mad Dogs and Englishmen | Fri Jan 17 1992 10:14 | 9 | 
|     
    Chuck,
    
             I have just had the same problem  -trying to load a Decbridge
    600 from NDU for Ultrix using the FDDI port. This failed with the same
    error message so I tried using the Ethernet port and it worked ok.
    I would agree it looks like a bug  - thanks for posting the workaround!
    
    John.
 | |||||