Conference azur::mcc

4546.0. "MCC SNMP AM & HUB90/Agent90 internal logic error 28" by CHILKA::JAGGI () Mon Feb 15 1993 14:44

    Hi,
    
    On customer having 13 hubs, have tried to manage these hubs using DECmcc
    SNMP and with the private extension DIGITAL_HUB90_MIBDEF.TXT. This was
    part of a demo to show management using DECmcc SNMP and HUBwatch on
    PC. During the demo I met a problem that I share here if not already
    known.
    
    When looking at the 802.1d spanning characteristing using all attributs,
    I received a fatal error :
    
            MCC>show Snmp .ip.hagen1 dot1dbridge dot1dstp all attr, by passw public2
    
                    SNMP .ip.hagen1 dot1dBridge dot1dStp
                    AT 28-JAN-1993 17:22:21 All Attributes
    
                    dot1dStpTimeSinceTopologyChange = 0
                    dot1dStpTopChanges = 0
    
                    Internal logic error 28 
    
    The configuration was as follows :
            o DECmcc V 1.2
            o SNMP AM V 1.1
            o The DECagent 90 was running firmware V 1.0
            o DECbridge90 firmware V 3.0
            o The DECagent 90 was installed as standalone unit.
            o The HUB 90 MIB definition :
              ------------------------------------------------------------------
              ---
              --  DECagent 90 and DEChub 90 Vendor MIB Document for SNMP V1implementation
              --
              --      Last updated    "Thu Oct 15 17:42:55 EDT 1992"     BLL
              --
              -------------------------------------------------------------
             - Is it the last HUB90 MIB extension version ?
            - If no, where could we found the last official version since it's
              not part of DECmcc kit ?
    
    
    My understanding is that spanning characteristic definition have nothing to
    see with MIB definition for the DEChub 90. Where the problem could be ?
    In the mib extension provided with DECmcc for HUB90, in the DECagent 90
    or in the DECbridge90, in the SNMP AM ?
    What could cause this internal logic error 28 ?
    
    I can get the spanning attributs of the bridge using HUBWATCH, so may be
    something wrong with DECagent90 reporting info received from DECbridge
    90 ?
    
    
    Any comments or suggestions ?
    Michel
    
    
    PS : I understand that managing the HUB directly from SNMP AM is not
    the most easy way and HUBwatch should be the prefered solution, however it
    should work.
    
    Note posted in MCC and HUB_MGNT.

Michel,

You'll get an internal logic error 28 when the SNMP AM receives a Response PDU
from an agent with an error code other than one of the following:


	- tooBig
	- noSuchName
	- badValue
	- readOnly
	- genErr

These are the only valid error-status codes defined in RFC1157 so it appears
that the agent is sending an invalid error-status code.

In order to determine exactly what the agent is returning, turn on inbound packet
tracing in the SNMP AM (define log mcc_tcpip_am_log  20) and issue the command
causing the problem. If you don't know how to read the packet dump, post the
results here.

jim