Conference netcad::hub_mgnt

883.0. "Problems with Agent V2.0 S/W" by GIDDAY::COOPER () Wed Apr 06 1994 01:48

Hi,

Has anyone seen any problems with the decagent S/W version 2.0 (SSB version).

I have a customer who has seen the following problems with V2.0 and has 
had to go back to the older version.

The problems are:
        1. Intermittent hubwatch crash when accessing repeaters
        2. no cold start or warm start traps
        3. unable to change default community on denma V2.0 from hubwatch (this
		is the case with V2.0 but he doesnt like it)
        4. getting enterprise specific traps and they dont know what they are.

The crashes occurred on a 16 slot hub containing a decbridge, a decagent
and 14 decrepeater 90Ts and look like:

%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000,
PC=00076FDE, PSL=03C00004

  Improperly hahdled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                00000000
        Name   = 0000000C                00C5C320
                 00000000                00000008
                 00000000                00002914
                 00076FDE                7FEE3AF4
                 03C00004                7FEE3AF8
                                         00000002
                                         00109D6C
                                         00109D70

        Register dump

        R0 = 00000000  R1 = 00000000  R2 = 00000000  R3 = 00000000
        R4 = 00C6AC60  R5 = 00000000  R6 = 00000000  R7 = 00D8FBD8
        R8 = 00000000  R9 = 00000000  R10= 0004528C  R11= 7FEE3AE4
        AP = 7FEE3A08  FP = 7FEE39C8  SP = 7FEE3A44  PC = 00076FDE
        PSL= 03C00004


This crash occurred clicking refresh several times on a DETMR:

%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000,
PC=00076FDE, PSL=03C00004

  Improperly hahdled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                00000000
        Name   = 0000000C                00C5C320
                 00000000                00000008
                 00000000                00002914
                 00076FDE                7FEE3CDC
                 03C00004                7FEE3CE0
                                         00000002
                                         00109D6C
                                         00109D70

        Register dump


        R0 = 00000000  R1 = 0000126C  R2 = 00000171  R3 = 00000000
        R4 = 00C48090  R5 = 00000100  R6 = 00000009  R7 = 00D88838
        R8 = 00000009  R9 = 00000009  R10= 0004528C  R11= 7FEE3CCC
        AP = 7FEE3BF0  FP = 7FEE3BB0  SP = 7FEE3C2C  PC = 00076FDE
        PSL= 03C00004

Unfortunately no actual dump was taken.

Any assistance greatly appreciated.

Thanks,
Steve
CSC Sydney

There are known problems running HUBwatch for OpenVMS V2.0 with V2.0 of
the DENMA.  Alternatives:
	- Put the DENMA back to the previous rev.
	- Wait for V3.0 of HUBwatch (soon).

Tom Hood
HUBwatch

.0>    2. no cold start or warm start traps
 
We have just identified the problem with the coldStart and warmStart traps. 
DECagent V2.0.16 does not do this properly.  The very first trap that should be
sent by the DECagent gets thrown on the floor instead of being sent out.  Under
typical conditions, this would be the coldStart/warmStart trap.  A fix is
forthcoming, and the logistics of its availability are bring worked out now.

.0>    4. getting enterprise specific traps and they dont know what they are.

Please check the latest DECHUB90 MIB for information about enterprise-specific
traps.  They are all documented at the end of the MIB.

...Roger...

    >the DENMA.  Alternatives:
    >        - Put the DENMA back to the previous rev.
    >        - Wait for V3.0 of HUBwatch (soon).
                                             
    Or use HUBwatch for Windows V2.0 if you have a PC.

HI,

Thanks for the replies.

I found the enterprise traps in the MIB document.

Any idea when Hubwatch for VMS V3.0 will be available?

Thanks,
Steve
CSC Sydney

	Please monitor NAC::MANAGEMENT:STATUS.TXT for development schedule 
	info.