[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

4299.0. "internal logic error 35" by MUNICH::SCHWEMMER () Mon Dec 21 1992 12:37

VMS V5.5-2/BMS V1.2/Hirschmann-private MIB V2.0.0

Customer looks into Hirschmann-Star-Coupler to see the boards and ports 
in it by clicking on the related symbols in the Iconic Map.

He gets:  

	internal logic error 35

whenever MCC looks for the following variables:

	hmBasicGroupEntry
	hmBasicPortEntry.


It's not possible for me to reproduce this inhouse, because we don't have
the required hardware.
But, if it helps, I have the MIB-definition and the MS-File.



Could anybody please give a hint?

Thanks in advance, 

Mathilde Schwemmer, DSC Munich


P.S:

The variables are defined within the MIB in the following manner:

...

--
-- The Basic Port Group Table
--

hmBasicGroupTable OBJECT-TYPE
    SYNTAX    SEQUENCE OF HmBasicGroupEntry
    ACCESS    not-accessible
    STATUS    mandatory
    DESCRIPTION
            "Table of descriptive and status information about
            the groups of ports."
    ::= { hmBasicGroup 2 }

hmBasicGroupEntry OBJECT-TYPE
    SYNTAX    HmBasicGroupEntry
    ACCESS    not-accessible
    STATUS    mandatory
    DESCRIPTION
            "An entry in the table, containing information
            about a single group of ports."
    INDEX    { hmBasGroupHubID, hmBasGroupID }
    ::= { hmBasicGroupTable 1 }

HmBasicGroupEntry ::=
    SEQUENCE {
        hmBasGroupHubID
            INTEGER,
        hmBasGroupID
            INTEGER,
        hmBasGroupNumOfPorts
            INTEGER
    }

...
...
...

--
-- The Basic Port Table
--

hmBasicPortTable OBJECT-TYPE
    SYNTAX    SEQUENCE OF HmBasicPortEntry
    ACCESS    not-accessible
    STATUS    mandatory
    DESCRIPTION
            "Table of descriptive and status information about
            the ports."
    ::= { hmBasicGroup 3 }

hmBasicPortEntry OBJECT-TYPE
    SYNTAX    HmBasicPortEntry
    ACCESS    not-accessible
    STATUS    mandatory
    DESCRIPTION
            "An entry in the table, containing information
            about a single port."
    INDEX    { hmBasPortHubID, hmBasPortGroupID, hmBasPortID }
    ::= { hmBasicPortTable 1 }

HmBasicPortEntry ::=
    SEQUENCE {
        hmBasPortHubID
            INTEGER,
        hmBasPortGroupID
            INTEGER,
        hmBasPortID
            INTEGER,
        hmBasPortAdminState
            INTEGER,
        hmBasPortAutoPartitionState
            INTEGER
    }

...
...
...
T.RTitleUserPersonal
Name
DateLines
4299.1Bad constructed Identifier2582::CHRISB::BRIENENNetwork Management Applications!Mon Dec 21 1992 19:509
My EFT Training Notes list  "Internal Error 35" as mapping to:

	
	"Bad constructed Identifier" -
	 May be due to bad info from agent.

Hopefully someone can provide more detail.

					Chris 
4299.2Upgrade the MIKEKAZAN::HOPEdtn: 858-1452, Paris, FranceMon Jan 04 1993 04:343
    We had this at Renault, but it disappeared when we upgraded the OS on
    the MIKE card.
    Steve
4299.3Fixed with MIKE V2.01BIKINI::KRAUSEEuropean NewProductEngineer for MCCWed Jan 20 1993 10:2111
>    We had this at Renault, but it disappeared when we upgraded the OS on
>    the MIKE card.

That's a known bug in the Hirschmann MIKE SNMP agent. They were
blaming MCC for it until I proved that it is their fault (the
old finger-pointing game). This was six month ago... 

Anyway, you need the latest MIKE software (V2.01) from 
Hirschmann which fixes the bug. It should be available now.

*Robert