[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

1559.0. "TCPware on VMS V5.5-2 and HUBwatch - Cannot start HWPOLLER" by CUJO::HILL (Dan Hill-NetConsultant-Denver-553-3624) Wed Oct 12 1994 18:56

    I understand that HUBwatch on VMS is supported and tested with UCX, TGV
    MultiNet, and Wollongong only, but I have a customer who would like to
    run HUBwatch using TCPware.
    
    When they start HUBwatch, the following error occurs when executing
    HUBWATCH$STARTUP.COM:
    
    	Cannot start HWPOLLER
    
    Is the customer out of luck, or is there something that can be easily
    modified to get HUBwatch running?  The customer understands that it is
    an unsupported configuration, but would like it try it anyway.
    
    Thanks,
    Dan
T.RTitleUserPersonal
Name		DateLines
1559.1MaybeSLINK::HOODI'd rather be at the PenobscotWed Oct 12 1994 20:4537
>    I understand that HUBwatch on VMS is supported and tested with UCX, TGV
>    MultiNet, and Wollongong only, but I have a customer who would like to
>    run HUBwatch using TCPware.

Wollongong is not supported, although some customers are using it.

>    Is the customer out of luck, or is there something that can be easily
>    modified to get HUBwatch running?  The customer understands that it is

It's hard to say.  If TCPware provides UCX emulation (and most of the TCP/IP
packages for OpenVMS do), then there are two steps your customer will have to
do...

1. Both UCX and TGV ship a file called UCX$IPC_SHR.EXE, which must be installed
   with privs for HUBwatch to work.  UCX sticks that file in SYS$LIBRARY,
   whereas MultiNet (TGV) puts it in multinet_common_root:[multinet].  So, if
   TCPware has UCX emulation, they also supplied such a file.  Look at
   HUBWATCH$STARTUP.COM for the exact install command.  This is a must!  If
   UCX$IPC_SHR.EXE does not exist, HUBwatch cannot run.

2. Another thing to look at is the ARP command file.  The HUBwatch kit supplies
   two of them, HUBWATCH$ARP_TGV.COM and HUBWATCH$ARP_UCX.COM.  The startup
   procedure copies one of them to SYS$SYSTEM:HUBWATCH$ARP.COM.  The diffs
   between the two files are the differences in the DCL commands for the two
   products, and for the differences in data format received by the two
   products.  This will most likely be a problem for TCPware if it doesn't
   return status from its "show arp" command in *exactly* the same format as
   either UCX or Multinet.  If this is a problem, HUBwatch will still run.
   However, for those screens which allow the user to enter MAC, IP, or DECnet,
   it will not be able to accept or display IP.

Does HUBwatch itself work?   If so, just comment-out the lines for the poller
in HUBWATCH$STARTUP.COM.

Hope this helps,
Tom Hood
HUBwatch
1559.2UCX$IPC_SHR.EXE is the culprit.CUJO::HILLDan Hill-NetConsultant-Denver-553-3624Thu Oct 13 1994 18:4210
    Tom,
    
    I am informed that one other error message does indeed refer to the
    fact that UCX$IPC_SHR.EXE cannot be found.
    
    I will have the customer check for the presence of this file in the
    TCPware kit.
    
    Thanks much,
    Dan
1559.3TCPware has logical defined for UCX$IPC_SHRCUJO::HILLDan Hill-NetConsultant-Denver-553-3624Mon Oct 17 1994 20:1510
    Tom,
    
    TCPware has the logical UCX$IPC_SHR defined to point to
    SYS$COMMON:[TCPWARE].  The image UCX$IPC_SHR.EXE is in that directory. 
    There is still a problem bringing up HUBwatch.  
    
    Any other ideas?
    
    Thanks,
    Dan
1559.4Not a clue, but more info might help.SLINK::HOODI'd rather be at the PenobscotMon Oct 17 1994 21:3423
Nope, no clue.

Make sure SYS$COMMON:[TCPWARE]UCX$IPC_SHR.EXE is installed shareable with privs:

$ INSTALL CREATE SYS$COMMON:[TCPWARE]UCX$IPC_SHR.EXE /PRIVILEGE=ALL /SHARE

This will need to be done at system startup time.  Normally HUBWATCH$STARTUP.COM
has the appopriate (UCX or TGV) line in it to do this.

Make sure the logical name HUBWATCH$SNMP_ASYNC is not defined.

What exactly happens when the customer tries to invoke HUBwatch?

ie:  $ WATCH/AGENT 16.20.224.5
     xxxxx  <-- What exactly gets printed?

And I'm not referring to either the poller (WATCH/POLLER) or the viewer (WATCH
/VIEWER), which are more complicated.


Blissfully running TGV MultiNet on SLINK,
Tom Hood
HUBwatch