| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 2842.1 | Not Supported | NETCAD::DRAGON |  | Mon Oct 09 1995 08:25 | 8 | 
|  |     
    Mohan,
    
    	AGL2 card on a Gigaswitch/FDDI is not currently supported by
        HUBwatch.
    
    Regards,
    Bob
 | 
| 2842.2 |  | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Mon Oct 09 1995 10:29 | 12 | 
|  |     Mohan,
    
        Are you asking if Hubloader will load the AGL-2 firmware?
    
        The firmware load delays are not caused by or related to Hubloader.
    They are caused by the way the AGL-2 itself does the upgrade to its
    flash.  This delay will happen regardless of the mechanism used for the
    upgrade.
    
        It may get fixed in the future...
    
    MDL
 | 
| 2842.3 | More Info please | GIDDAY::KULHALLI |  | Mon Oct 09 1995 22:51 | 25 | 
|  |     
    Bob and Michael,
    
    My apologies for not wording the question correctly. What I wanted to
    ask was whether hubloader can successfully down load the firmware to
    AGL2 card on Gigaswitch/FDDI. From Michael's reply in .2 - it does
    work - but takes around 25 minutes or so as with PNV.
    Is this correct?
    
    We had one of our Engineer - try upgrading AGL2 with hubloader and
    failed/aborted half way thru just the last week.
    
    However - hubloader "show" command displays correct version of AGL2
    firmware and the latest reqd version etc. 
    
    Another question - is it likely that new version of hubwatch will support
    front panel display for AGL2 ? 
    Is it correct to assume that the cusrrent version of Hubwatch does not
    support filter set ups on AGL2 ports?
    
    thanks
    
     /mohan
    
    thanks
 | 
| 2842.4 |  | NETCAD::DRAGON |  | Tue Oct 10 1995 08:04 | 12 | 
|  |     
    Mohan,
    
    	AGL2 support is being considered. Since we are still in the
        planning phase no definite answer can be given at this point.
    
        I think that the filter setup may work on the AGL2, since its
        dealing with things at the bridge port level. However, I do 
        not presently have a card to try it. Perhaps someone who has
        tried this could shed some light.
    
    Bob
 | 
| 2842.5 |  | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Wed Oct 11 1995 16:03 | 20 | 
|  |         I just tried a couple of AGL-2 upgrades using Hubloader V1.1,
    loading AGL-2 firmware 2.00 and then 2.05.  Both of them worked as
    expected, although I needed to edit the dcffiles.dat file and change
    AGL2 to AGL.  
    
        The upgrade took about 16 minutes each on the LKG network, from
    start of load on Hubloader to when the AGL-2 actually started
    forwarding after the reboot.  This is the same as any other upgrade
    method.  ...the time has nothing to do with the upgrade method, and
    everything to do with the AGL-2 firmware which does the upgrade.  Your
    load times may vary based on the network activity during the file
    transfer, and the number of active MAC addresses which affects the
    amount of time it takes the card to enter forwarding.  I suspect the
    absolute minimum using the current firmware (BL2.2) and an unloaded
    unoccupied LAN would be slightly over 15 minutes.
    
        I wouldn't expect any problems setting filters on AGLs as the
    sets don't involve Hubwatch talking to the card directly.
    
    MDL
 | 
| 2842.6 |  | GIDDAY::KULHALLI |  | Thu Oct 12 1995 19:35 | 4 | 
|  |     
    Thanks for the help
    
     /mohan
 |