Conference netcad::hub_mgnt

196.0. "Latest HubWatch for VMS Dies in Bridge Plotting Part" by ANGLIN::ORTHOBER () Fri Apr 02 1993 18:52

	Hi All:

	I am having a problem with the VMS hubwatch product.
	It dies when I try and use the graph portion of the
	bridge card.  It also dies when trying to use the filter
	interface.

	Here is the info...

	The kit that I installed Hub Watch from is like this...

HUBWATCH_TG011.A;1      189  24-MAR-1993 18:29:51.00
HUBWATCH_TG011.B;1     7560  24-MAR-1993 18:25:36.00

--------------------------
GBOVS1 $ sp watch/agent/ip_address=16.76.0.100
%DCL-S-SPAWNED, process SYSTEM_1 spawned
GBOVS1 $
(I) HUBWATCH$LIBRARY = SYS$LOGIN
(W) Can't open HUBWATCH$LIBRARY:HUBWATCH_AGENTS.DAT - no such file
(I) AGENT_TABLE: Created new agents file: HUBWATCH$LIBRARY:HUBWATCH_AGENTS.DAT
(W) Current agent not in the agent table
(W) Using default community: public
(W) Unresolved agent node IP name
(D)
HUB CONFIGURATION:
(I) ___________________________________________________________________________
(D) Slots:      1       2       3       4       5       6       7       8
(D) Cards:      Empty   Empty   Empty   Empty   DS90L   DETMR   DENMA   DEWGB
(I) ___________________________________________________________________________
(E) Failed to get IF interface.
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000018, PC
=00045E2F, PSL=03C00004

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                000000A8
        Name   = 0000000C                000000A8
                 00000000                000000A0
                 00000018                000000A0
                 00045E2F                00000098
                 03C00004                00000098
                                         00000090
                                         00000090
                                         00000088
                                         00000088

        Register dump

        R0 = 00000006  R1 = 00000000  R2 = 00000000  R3 = 006C5958
        R4 = 003E3150  R5 = 00031BA8  R6 = 0000AEFC  R7 = 00000003
        R8 = 006C5778  R9 = 7FF052CC  R10= 7FF052D0  R11= 7FF052D4
        AP = 7FF05090  FP = 7FF05050  SP = 7FF050CC  PC = 00045E2F
        PSL= 03C00004

Subprocess SYSTEM_1 has completed

----------------------------------------
	Here is the agent firmare info.  This is the
	latest agent version that I could find and it 
	is from the vms file...

	DENMAT011.SYS;1         513  31-MAR-1993 09:03:40.00

Sets Enabled       DECagent 90 SNMP Network Management Agent               X1.76
Community: public [1]                                             Name: GBOagent
Type: DEChub 90-8     IP Address: 16.76.0.100        System Uptime:   0 00:02:45

----------------------------------------------
	Here is Bridge firmware information....

NCP>connect node gbobrg
Console connected (press CTRL/D when finished)
DECbridge 90 V1.14  08-00-2B-2E-FC-BB � 1991 Digital Equipment Corp
FPROM V3.1 �1991,93 Digital Equip Corp 15-JAN-93

DECbridge>
	

    Your bridge code needs to be updated from 1.14 to 3.0 or 3.1.  
    
    see EMDS::MANAGEMENT:BRIDGE_LOAD.TXT

	If you look closer, the bridge is at feprom V3.1.

	It turns out that the agent stops itself (literally stops
	running) the version that I had.

	I am copying over a new version right now for the agent and
	I'll try it out....

thanks
ort1

--------------------------

Directory DIRT::USER2:[DENMA.FIELD_TEST.T1_1]

$$WHAT_ARE_THESE_FILES.READ_ME;15
                          2  12-APR-1993 08:34:09.00
BRIDGE_MIB.TXT;11        90  12-MAY-1992 15:35:30.00
CHAR_MIB.TXT;7           42  12-MAY-1992 15:32:37.00
DENMA_DATA.SYS;2          2   4-AUG-1992 10:57:22.00
DENMA_FT011.A;1         648  12-APR-1993 08:28:38.00
DENMA_FT110.TAR;1       440  12-APR-1993 08:57:55.00
DENMA_LOAD_PROCEDURE.TXT;2
                         12   2-FEB-1993 13:57:22.00
DH90_MIB.TXT;34         189   9-APR-1993 11:37:11.00
MOBJ_MIBII_MIB.TXT;3
                        163  28-DEC-1990 18:54:50.00
MOBJ_PARENT_MIB.TXT;3
                          6  12-MAY-1992 13:00:17.00
RS232_MIB.TXT;6          37  12-MAY-1992 15:37:56.00

	Well, I installed the 12-apr version and it
	does the same thing.  The code in the agent runs
	for about a minute and then dies and after power
	up it is simply not running.

	I went back to the V1.0 version and that seems
	to be working...

	How do I log this as a problem?  Who is developing
	this code that does not work?  Do I need a hardware
	upgrade?

thanks
ort1

    I'd probably be out of a job if my goal was to develop code that does
    not work.  However, if non-working code was the goal, I would have had
    a lot more time to read NOTES over the last 12 months.  And I probably
    wouldn't be reading this file at 8:15 p.m.  :-}
    
    With that said, perhaps you can provide some useful information which
    will help us figure out why your agent is not performing as expected.
    
    First, you are running a "fairly old" version of HUBwatch.  The latest
    kit is the "J" kit (T1.1.18).  You can find a pointer to this kit
    elsewhere in this file.  I have no reason to believe this will help
    your problem, but FYI.  Second, can you tell me what the version
    string says when you do a Show Module of the agent's slot at the agent
    console (or bring up the agent summary screen in HUBwatch)?
    
    ...Roger...  DECagent 90 devo.

	It says:

	HW=D01 ROM=BL05.00 SW=V1.0

Thanks
ort1

	Hi, Well just for grins I tried loading the latest agent
	code and now it works fine (x1.77).  The downloads must have failed
	for some reason the other times I did it.

thanks
ort1