Conference netcad::hub_mgnt

875.0. "Dump / SNMP timeout" by BERN01::FUCHS (FRED FUCHS) Thu Mar 31 1994 10:41

Hi,

I have the following Problems with:
Hubwatch SW Version 2.0.1
Agent 90 SW Version 2.0.16
I have HUB 90 with a DECbridge 90 in slot 8, a Agent 90 in slot 7 a 
Repeater 90 in slot 6 and a Server 90L+ in slot 1
All other Hub's are similar configured.
There are only DEChub 90's in my environment.

1st Problem
When i Click on the Server in Slot 1 it opens a nearly empty window and i 
get the following warning message: 
(W) DS90L/90L+: SNMP timeout in SUMSESS group, port 8

2nd Problem
When i Click on the Repeater in slot 6, i get the following dump.
In fact, i allways get a dump when i select a  repeater no matter if it is 
Repeater 90C or a Repeater 90T.
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=
00000000, PC
=00076FDE, PSL=03C00004

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                00000000
        Name   = 0000000C                0088B430
                 00000000                00000008
                 00000000                00002914
                 00076FDE                7FEDDC98
                 03C00004                7FEDDC9C
                                         00000002
                                         00000002
                                         00109D6C
                                         00109D70

        Register dump

        R0 = 00000000  R1 = 00000000  R2 = 00000000  R3 = 00000000
        R4 = 00881770  R5 = 00000000  R6 = 00000000  R7 = 00A2E810
        R8 = 00000000  R9 = 00000000  R10= 0004528C  R11= 7FEDDC88
        AP = 7FEDDBAC  FP = 7FEDDB6C  SP = 7FEDDBE8  PC = 00076FDE
        PSL= 03C00004



2nd Crash Clicking on the DETMR in Slot 1
(I) HUB CONFIGURATION:
(I) 
___________________________________________________________________________
(I) Slots:      1       2       3       4       5       6       7       8
(I) Cards:      DETMR   Empty   Empty   Empty   Empty   Empty   DENMA   
DEWGB
(I) 
(I) Slot 1: Port 1:  status = ONLINE
(I) Slot 1: Port 2:  status = ONLINE
(I) Slot 1: Port 3:  status = DISCONNECTED (OFF)
(I) Slot 1: Port 4:  status = ONLINE
(I) Slot 1: Port 5:  status = DISCONNECTED (OFF)
(I) Slot 1: Port 6:  status = ONLINE
(I) Slot 1: Port 7:  status = DISCONNECTED (OFF)
(I) Slot 1: Port 8:  status = DISCONNECTED (OFF)
(I) Slot 8: Port 1:  status = ONLINE
(I) Slot 8: Port 2:  status = ONLINE
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=
00000000, PC
=00076FDE, PSL=03C00004

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                00000000
        Name   = 0000000C                00BB08D0
                 00000000                00000008
                 00000000                00002914
                 00076FDE                7FEDDC98
                 03C00004                7FEDDC9C
                                         00000002
                                         00000002
                                         00109D6C
                                         00109D70

        Register dump

        R0 = 00000000  R1 = 0000020C  R2 = 00000029  R3 = 00000000
        R4 = 00BB0910  R5 = 00000000  R6 = 00000001  R7 = 00BEC4A0
        R8 = 00000001  R9 = 00000001  R10= 0004528C  R11= 7FEDDC88
        AP = 7FEDDBAC  FP = 7FEDDB6C  SP = 7FEDDBE8  PC = 00076FDE
        PSL= 03C00004


Before i had Hubwatch V 1.1 Agent Version 1.1 and no Problems at all.
After that i downgraded all DECagent 90 from Version 2.0 to Version 1.1
and the above described Problems are gone.

Have someone else seen this behavior. If Yes, is there a fix around?


Regards
Fred 

    I'll give this a try here with V2.0.1 and see if we can reproduce
    it.
    
    Bob
    

    
    After further discussions, I discovered that these are known
    bugs in HUBwatch V2.0.1 when you are using DENMA V2.0.
    Remember HUBwatch V2.0.1 shipped on VMS before the V2.0
    DENMA code was available so this configuration was not tested.
    
    Until we can get some kind of patch together you have two options:
    
    1) Use the HUBwatch Windows V2.0.  These problems are fixed there.
    
    2) Continue running DENMA V1.1 until HUBwatch V3.0 is available
    on VMS.
    
    
    These bugs are fixed in HUBwatch V3.0.  But this version is not
    ready for external use yet.
    
    Regards,
    
    Bob

Bob,

Thank you very much for your help.

>    These bugs are fixed in HUBwatch V3.0.  But this version is not
>    ready for external use yet.
>    
 When will HUBwatch V3.0. for VMS be availabel for customers?

Regards Fred