Conference netcad::hub_mgnt

              <<< EMDS::$1$DUA24:[NOTES$LIBRARY]HUB_MGNT.NOTE;1 >>>
                         -< Hub Management Conference >-
================================================================================
Note 161.3                     VMS Documentation?                         3 of 3
MAIL::CLAYTON "Merlin Clayton DTN 445-7217"          21 lines  18-FEB-1993 10:08
                                -< Now Working >-
--------------------------------------------------------------------------------
The problem with launching HUBwatch T1.1.8 was related to the method of
envoking HUBwatch from VMS.  

The old way was "mcr hubwatch ....."

The new way is "WATCH /AGENT <agent_name>"

I made the necessary changes to the MCC_APPL_HUBWATCH.def procedure and the 
launch from mcc now works.

The only problem I had was that I had to hard code the community name because
when I tried passing the variable it could not be found in the agent table.
This is most likely a problem with case sensitivity.  Hubwatch also did not
like the format of the IP address, so I just eliminated it from the argument
string.

Maybe someone can shed some light on these issues.

Thanks.

Merlin

    I'm having problems launching HUBwatch from DECmcc V1.3.0 VMS...
    
    I can manage the hub stand alone using:
    
    	Watch/agent nachub
                         
    but, via MCC I get a window with:
    
    		 HUBwatch: Error   The front panel type is unknown
    
    when I select the hub and launch Hubwatch from the applications menu.
    
    
    	I can expand the IP Icon and manage it via SNMP in MCC. So, I think
    I'm not registering the hub correctly? When I registered the hub I
    supplied the following:
    
    	Name: .ip.nachub
    
    	Synonym: nachub
    	IP Add:  16.63.96.10
        read comm: public
    	write comm: master
    
    nachub is listed in UCX as 16.63.96.10 and has the uppercase alias
    defined...
    
    
    
    I have added the following line in the HUBWATCH$LIBRARY:hubwatch_agents.dat 
    
    16.63.96.10 nachub master 5 2 DEBMA
    
    I also tried updating the HUBwatch.dat file to make the nachub the
    default hub. Invoking HUBwatch standalone via:
    
    	Watch /agent     works fine...
    
    Launching via DECmcc, the error message (now in the message window) : 
    
    	Application could not be launched. Argument not gettable.
    
    	In the window where I invoked MCC I get the following error
    messages:
    
    	(I) HUBWATCH$LIBRARY = SYS$LOGIN
    	(W) Current agent community name not in agent table
    	(D) retry[1/0/2] ...
    
    	(D) retry[2/0/2] ...
    
    						Any ideas?
    
    						rick
                              

    The HUBwatch version is T1.1.15...
    
    When running standalone, I looked at a few ports on a terminal server,
    repeater and decbridge 90 in the hub then, I tried to switch to the 
    logical view and the window disappeared and the hubwatch application 
    exited without any messages... 
    
    I started up HUBwatch again, 
    	switched to the logical view
    	looked at a few ports again...
    	switched back to the physical view 
    	
    	the window disappeared and provided the following error messages in
    the window I invoked HUBwatch from:
    
    	(E) Memory allocation failure
    	%XLIB-E_INSMEM, insufficient dynamic memory
    	%SYSTEM-F-ACCVIO, access violation
    
    		with stack dump...
    
    
    				rick

(re .3)
Looks like either your process quotas aren't big enough or your system
needs to be re-configed.

(re:.2)
Did you really type DEBMA?

    I'll try and do a little process and memory tuning and let you know...
    
    No, sorry DEBMA was a typo...
    
    				rick

    I bumped up the system virtualpagecnt and corrected the uaf quotas as
    per mcc_audit.com. I still get the same problem when lauching HUBwatch
    T1.1.15 from MCC V1.3: 
    
    In the window I invoked MCC I get....
    
    (I) HUBWATCH$LIBRARY = SYS$LOGIN
    (D) retry[1/0/2] (slot=0[1/0/2],vw=1,rq=2d0360)
    
    (D) retry[2/0/2] (slot=0[2/0/2],vw=1,rq=2d0360)
    
    Then in a separate window...
    
    	HUBwatch Error:
    
    	Front pannel type is unknown
    
    
    
    			vs (standalone $watch /agent nachub)
    
    (I) HUBWATCH$LIBRARY = SYS$LOGIN
    (W) Using community master
    (D)
    HUB CONFIGURATION:
    (I) _____________________________________________________________________
    (D) Slots:      1	   2      3       4      5      6      7      8
    (D) Cards:      DECMR  DETMR  DS90L+  EMPTY  EMPTY  Empty  DEWGB  DENMA
    (I) _____________________________________________________________________
    etc...
    
    
    
    	I use the same account when attempting to run HUBwatch from MCC or
    standalone... Any ideas?
    
    						thanks,
    
    						rick