Conference netcad::hub_mgnt

2639.0. "hubloader failure upgrading Gigaswitch SCP" by KAOFS::S_HYNDMAN (Ride life's curves) Mon Aug 14 1995 17:44

	I am unable to upgrade one SCP module in a gigaswitch via the latest
version of Hubwatch/Hubloader.  I am upgrading to version 2.2 of the firmware
from v2.10 DL 1.00 BB0.00.  I was able to upgrade the other SCP in this 
gigaswitch and 4 other SCPs in two more gigaswitches.

	I have started the TFTP server.  I am able to show the version and the
community string is correct.  I click on load and the transfer completes.  
However shortly after the transfer begining, Hubloader fails with the folling
error messages.

	Any Ideas?

Scott

Load Agent Name:  kaogiga3;   Agent Address:  xxx.xxx.xxx.xxx <-- its ok
Slot Number: 4
Community String: XXXXXXX  <---- its ok
[GIGAswitch] Setting TFTP Server IP Address.
[GIGAswitch] Setting firmware image file name.
[GIGAswitch] Triggering image file transfer.
Community String: madness
[GIGAswitch] Polling for file transfer completion.
[INFO] Return code: -6090
[ERROR] Problem initializing socket (get)
[ERROR] Return code: -6090
[ERROR] FILE TRANSFER FAILED
 

>>[ERROR] Problem initializing socket (get)

What IP stack are you using?? 

If you are using HUBwatch or PATHWORKS V5.x, increase the UDPMaxSock and 
TCPMaxSock in the [TCPIP] section of the C:\PW or C:\HUBWATCH\IPSTACK 
PWTCP.INI file. 
This is usually the cause of socket(s) not initializing.

If you are using another IP stack increase these attributes accordingly.

Barb

    
    
    Barb,
    
    	Thanks for the reply.  I increaded the UDPMaxSock from 10 to 20 and
    it loaded correctly.  Funny how it worked for all the others.
    
    
    Scott