| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
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 was encountered
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 characteristics 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 DECbridge90 ?
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
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 158.1 | SNMP AM Internal Logic Errors. | MOLAR::CHRISB::BRIENEN | Network Management Applications! | Fri Feb 19 1993 09:39 | 39 |
SNMP AM V1.2 Internal Logic Errors
-----------------------------------
Internal Logic Errors occur when the AM encounters something unexpected.
Most should never occur and indicate a fairly serious problem.
Some are the result of a limitation in the AM that is encountered due
to stress of MIB extension (e.g. MIB depth limitations in DECmcc V1.2,
lifted in V1.3). Some are the result of bad stuff returned from the agent
(ie, snmp protocol violations).
Internal Description
Logic Error
---------------- ---------------------------------------------------
3 Error processing Handle (memory corruption)
* 4,9,10,11,12,17 Error processing object id (objid exceeds 32 items,
hard coded limitation in AM)
6 Table index contains more than one variable length
component
7,8,13,18 Buffer too small (internal routine call problem)
14,16,19-22 Bad tranceiver control state
15 Error trying to read dictionary (MIB extensions)
* 27,28,33 Bad value encountered in pdu returned from agent
* 29,40,41 Objid from agent not recognized as valid attribute
* 30 Bad data type encountered in pdu returned from agent
* 31 Error processing "hello" message
32 Error reading internal tables (bad pointer)
* 35,36 Bad constructed Identifier
39 Error processing synthesized attributes
42 Bad entity (internal call interface problem)
43 Error sending packet (couldn't send all data)
104,105 Bad handle received from the sink.
106 Bad handle received from the PM.
107 Bad event code received from the sink
108 Bad partition (Attribute) received from the PM
* May be due to bad info from agent
| |||||
| 158.2 | More information... | MOLAR::CHRISB::BRIENEN | Network Management Applications! | Fri Feb 19 1993 10:22 | 32 |
Our resident SNMP AM mib guru is on vacation for a few weeks, so I'm taking
a stab at supplying some information...
1. Internal Error codes -
Note 158.1 lists the mapping of "SNMP AM V1.2 Internal Errors" to reality,
as presented at CSC Training in June 1992 (one hopes these obscure codes
will get mapped to real user errors in a future release of the AM).
Error #28 = "Bad value encountered in pdu returned from agent".
The SNMP AM provides a means of dumping packets for debugging problems
like this, but I don't have the details at my fingertips.
2. Version of SNMP AM -
The SNMP AM shipped with MCC V1.2, and had a version number of "V1.2"
(V1.2 added generic trap support, which V1.1 did not have).
Was the "SNMP AM V 1.1" mentioned in the base note a typo?
Any chance this can be tried with the latest version of MCC? V1.3
had some significant fixes made to SNMP AM, particularly in the area
of mib depth. (Bob H., I know you guys are running V1.3 at TAY!).
3. MIB version / date -
The file DEC_HUB90_MIBDEF.TXT packaged with MCC V1.3 is dated 16-JUL-1992.
There's no header in that file mentioning the "last update", but the
one shipping with MCC V1.3 has NOT been updated after July 1992. Wanna
try my version to see if it works?
Hope this helps...
Chris
| |||||
| 158.3 | There is spanning tree error in bridge 3.0 | EMDS::SEAVER | Bill Seaver, HUBwatch Mktg | Fri Feb 26 1993 11:04 | 3 |
There is a spanning tree error in the 3.0 bridge code. I'm told 3.1
fixes this. I will check with bridge engineering to see if this is
caused by the spanning tree error.
| |||||
| 158.4 | not caused by bridge | EMDS::SEAVER | Bill Seaver, HUBwatch Mktg | Fri Feb 26 1993 19:35 | 2 |
Thisis not caused by the spanning tree error. Will now check MCC and
the agent.
| |||||