[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

1405.0. "HUBwatch for Windows V3.1 Seeds" by NACAD::SWEET () Mon Sep 12 1994 11:27

 
SUBJECT: HUBwatch for Windows 3.1 seeds available

HUBwatch for Windows 3.1 seeds are now available at:
	NAC::NIPG:[MANAGE.WINDOWS.WINDOW31.DISK1]*.*
	NAC::NIPG:[MANAGE.WINDOWS.WINDOW31.DISK2]*.*

These files will be updated frequently until SSB submission around the
    end of
September.  We are ready for widespread testing on this kit and are especially 
looking for feedback in the following areas:
	- Do we have a reasonable set of non-DEC adapters and drivers 
		(see NAC::NIPG:[WINDOWS]DRIVERS.TXT for a list)
	- How it plays with HP OpenView 
		(see NAC::NIPG:[MANAGE.WINDOWS.HP] for kit)
	- ODI (Novell driver)
	- Installation in general
 
Bug reports can be posted as replies to this note. Thank you for your 
patience in waiting for this release; and thanks for all the testing 
and feedback you will provide.

The manuals can be copied from
TNPUBS::PUBLIC$651:[PUBLIC.ONEHUB]HUBWATCH_WINDOWS_V31_USE.PS;1
and
TNPUBS::PUBLIC$651:[PUBLIC.ONEHUB]HUBWATCH-V31-INSTALL-CONFIG.PS;1

FDDI hub devices are now managed - DECbridge 900MX/DECswitch 900EF,EE, 
DECconcentrator 900MX, and PEswitch 900EF. This version also manages 
the DECrepeaters 900FP, 90FS and 90TS, and the Roamabout bridge. Like 
VMS, it also gives you the option of a Physical or a Logical view.
GIGAswitch will be managed from Windows in the next version.  Currently 
it is only manageable from VAX/VMS and OSF1 AXP.


T.RTitleUserPersonal
Name
DateLines
1405.1STRWRS::KOCH_PIt never hurts to ask...Mon Sep 12 1994 16:033
    
    Should we make sure we've loaded the latest firmware levels into all
    the devices before this is made available to the customer?
1405.2HPOV questions?PADNOM::PEYRACHEJean-Yves Peyrache Country Support Group FranceTue Sep 13 1994 13:0713
    are manuals covered HPOV parts ??     
      _installation
      _configuration
    
    Which IP stack works with this version , i have  already HP-Openview
    installed on my PC with Netmanage IP stack , are this stack is purely
    compatible with this version of HPOV ?
    Same questions for Hubwatch X3.1     ?
    
    
      thanks for any comments
      Jean-Yves
      (waiting completion of copy for printing the doc )
1405.3Try the HP stackNACAD::SWEETTue Sep 13 1994 14:006
    As always, use the latest and greatest f/w.
    
    HUBwatch should work with the stack from HP PCOV. Please try it
    and let us know the results.
    
    Bruce
1405.4because it is there ODIF11::LICATATue Sep 20 1994 00:179
    I have tried the FTP stack and Hubwatch works fine.
    
    Will it work on a PC connected to Token ring 
    then routed to an Ethernet that is running the FTP stack ?
    
    BTW I tried it and received a failed to create socket error. 
    just to pursue an idle fantsy -- any ideas if this might work.
    
    Jim         
1405.5Problem with X3.1 and/or HPOVCLPR01::PEYRACHEJean-Yves Peyrache Country Support Group FranceTue Sep 20 1994 09:3046

 Hello,


  i have some trouble to install/and works with X3.1 of HUBWatch for dos
  and /or HPOV:

   my configuration is a DECPC425 and Etherworks 3 with 10M of memory 
   and before installing X3.1 and HPOV  X7.2 
   i  works with Hubwatch T2.0.1 and/or HPOV 7.1 and
   on-Demand (Chipcom Hub Products) and or course with no problem.

    First Problem:

   Starting Hubwatch X3.1 after installation in Stand-alone mode (without HPOV)
   an error message occured during the netbind (this problem has already        
   described in notefiles 1437).
    error message is 
   "MAC0020E hardware does not match MEMORYMODE parameter in protocol.ini file"
   "LD0014 driver failed to initialize"
   replacing with old networks files (ewrk3.protocol.ini,netbind) from V2.0 kits
   cured the error message but Hubwatch could'nt display any HUB with
   a new message "windows error Hubwatch error in Hubwatch.exe at 0009:78CF"
   

   Second Problem:

   during the startup of HPOV just after the first banner "HPOPENVIEW FOR       
   Windows" 
   2 errors messages appears (already described in notes 1435)
   "Stop ping init failure  ovnetmon err 20"
   "NETOV Apllication did'net initialise OV212"

   i have the same error message with the TCP-IP stack from NETmanage and
   the Stack form Pathworks (Hubwatch for Dos V2.0 kit).

   despite of that ,HPOV seems to be worked :
   i can query some SNMP informations from a lot of Hub using SNMP Manager      
   option under HPOV.


   thanks for any comments,pointers,replies
   Jean-Yves

   
1405.6Can't communicate with DECbrouter 90DECPRG::PILARWed Sep 28 1994 18:5715
    Hi,
    I'm preparing some demo of LAN/WAN networks and network management. I
    have installed HUBwatch for Windows X3.1 3 a I have problem to
    communicate with DECbrouter90T. I have one brouter in DEChub 900MS when
    click on it I have message "No agent specified for the mac address".
    When enter MAC address everything works fine. Second brouter is off
    LAN. It is standalone unit. I can access it without problem for
    HUBwatch for OpenVMS and OSF/1 but not from HUBwatch for Windows. I can
    even ping to the brouter but when trying to run HUBwatch I have message
    "No response from agent". It seems to me HUBwatch for Windows can't
    communicate with DECbrouter 90T SNMP agent. Is this known problem or is
    it already fixed. 
    
    Regards
    Jarry
1405.7The same with X3.1.5DECPRG::PILARWed Sep 28 1994 21:295
    Hi,
    just now I'm trying HUBwatch for Windows X3.1.5. It seems to be the
    same.
    Regards
    Jarry
1405.8known problem with windows FT kitNETCAD::HAROKOPUSThu Sep 29 1994 11:058
    Jarry,
    
    This is a known bug in the Windows version.  You can manage the 
    brouter in a hub but not standalone.   It is being worked on now.
    
    Regards,
    
    Bob  
1405.9FATAL ERROR AT SCRIPT LINE 827DECPRG::PAVLUPWed Oct 05 1994 08:0614
    I encountered an installation problem with the X3.1.5 kit at my
    notebook (DECpc 325SL with Xircom PCMCIA Ethernet adapter). 
    When doing the full installation (HUBwatch and
    network), at the stage after "Getting configuration info...", the
    installation gives an error: "FATAL ERROR AT SCRIPT LINE 827" with an
    explanation "Invalid dialog type".
    
    This happens after all installations are completed. However, the
    installation does not change the system files for HUBwatch use.
    
    Thanks for any hints and information.
    
    Regards Petr.
    
1405.10HUBwatch windows V3.1 seedsIJSAPL::ROLINGJos R�ling, Network Consultant, HollandTue Oct 11 1994 06:5914
I encountered an installation problem with the HUBwatch version X3.1.6 when use HUBwatch and Netywork option.
I try to install it on a DECpc 325SL with 12MB internal and 80MB harddisk. For use with SLIP.
On the second floppy an "FATAL ERROR AT SCRIPT LINE 333! 
                        cannot open MediaBuilder library file .



I'm testing this installation since a customer was shiped with HUbwatch for Windows V2.0 to manage an
DECconcentrator 900MX; DECbridge 900MX and DECrepeater 900FP. Can I please ship the customer a working
HUbwatch to configure his network?

Thanks for any hints and information.

Jos roling
1405.11Ooops....IJSAPL::ROLINGJos R�ling, Network Consultant, HollandTue Oct 11 1994 09:226
I used the wrong software.

The VMS directory I used as a spool area for disk2 was not cleared before I started. Hence I used the V2.0
software on the second floppy but the correct X3.1 on the first. (I will dubble check before posing in the future)

sorry... jos