[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

2041.0. "Hubwatch & Lanview" by ISTWI1::AKALIN (MEHMET AKALIN @TKE) Thu Feb 23 1995 08:26

Hello,

We managed to sell DECswitch 900EF's and Hubwatch for Windows (V3.1) to a 
large Cabletron customer.  He is running Lanview (by Cabletron )(V2.07.00- HP 
OV B01.01).

First we installed HUBwatch on the same PC with LANview and we tried to start 
LANview, we get the err msg that "OVADL.DLKL and OVSNMP.DLL are not found."
So, we couldn't launch Hubwatch and LANview from the same map. Since HP OV is 
an old version, we then tried running Hubwatch separately under windows.
If Hubwatch is started first, everything is OK. But if we run Hubwatch after 
running LANview, we get "no response from agent" and the PC randomly hangs. 
Rebooting the PC enables Hubwatch again, till we run Lanview.

Can someone tell if:

- there is a way we can run them side by side,
- there is a version of LANview (with appropriate HP Openview) that enables
  Hubwatch to be launched from the same network map so that we can hopefully 
  persuade the customer to upgrade.

Best regards,

Mehmet AKALIN

T.R Title User Personal
Name Date Lines

2041.1 Cabeltron is not WinSOCK compliant! NAC::SEAVER Bill Seaver, HUBwatch Mktg Mon Feb 27 1995 19:24 32

T.R	Title	User	Personal Name	Date	Lines
2041.1	Cabeltron is not WinSOCK compliant!	NAC::SEAVER	Bill Seaver, HUBwatch Mktg	`Mon Feb 27 1995 19:24`	32
	From: NAC::FORREST 23-FEB-1995 09:52:08.50 To: MTS$::"tke::mehmet akalin",SEAVER CC: NETCAD::SWEET,NAAS,MELLO,DELNI::BOUCHARD Subj: HUBwatch with Remote LANview Mehmet, my understanding is that Cabletron's Remote LANview uses an early version of HP OpenView for Windows. This version did not use the WINSOCK API, which is the open standard today. I suspect that the reason you can't get both HUBwatch and Remote LANview to run on the same system is that you have IP stack conflicts when trying to run two different stacks. I don't believe there are any workarounds for this problem. Making HUBwatch work on a PC already configured for Remote LANview would take a lot of work. We would have to either rewrite our network stack calls to call their stack, or write a WINSOCK-to-their-stack converter. Then we would have to obtain one of the few supported NICs to test it. This is assuming we could obtain a specification somewhere that describes the calls to their stack. Then for each new release we would have to system test with two network interfaces. I think the better approach is to use the old Cabletron/HPOV technology as a Cabletron weakness in competitive sales situations where the customer hasn't already bought a management application. We'll just have to bypass those customers who have Remote LANview and refuse to consider a second PC running HUBwatch as a viable solution. jack

From:	NAC::FORREST      23-FEB-1995 09:52:08.50
To:	MTS$::"tke::mehmet akalin",SEAVER
CC:	NETCAD::SWEET,NAAS,MELLO,DELNI::BOUCHARD
Subj:	HUBwatch with Remote LANview

Mehmet, my understanding is that Cabletron's Remote LANview uses an 
early version of HP OpenView for Windows. This version did not use the 
WINSOCK API, which is the open standard today. I suspect that the reason 
you can't get both HUBwatch and Remote LANview to run on the same system 
is that you have IP stack conflicts when trying to run two different 
stacks. I don't believe there are any workarounds for this problem.

Making HUBwatch work on a PC already configured for Remote LANview would 
take a lot of work. We would have to either rewrite our network stack 
calls to call their stack, or write a WINSOCK-to-their-stack converter. 
Then we  would have to obtain one of the few supported NICs to test it.
This is assuming we could obtain a specification somewhere that 
describes the calls to their stack.

Then for each new release we would have to system test with two network 
interfaces.

I think the better approach is to use the old Cabletron/HPOV technology 
as a Cabletron weakness in competitive sales situations where the 
customer hasn't already bought a management application.

We'll just have to bypass those customers who have Remote LANview and 
refuse to consider a second PC running HUBwatch as a viable solution.

jack