[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

4068.0. "MIB problems" by ANOSWS::COMFORT (Spent a little time on the hill) Wed Nov 11 1992 15:29

    
    Hi,
    
    Out at another customer, Sterling Winthrop, the head of the networks
    group has indicated that MCC is not handling the data returned from
    SNMP entities correctly, even though the definitions are in the MIB.
    Has this behaviour been reported before or have I done something
    incorrect in compiling the MIB (I simply used the MTU com procedure ,
    but did nothing other than give it the MIB name and "load"). I watched
    as they traced the "get" and "got" SNMP packets returned from a Cisco
    router. The packets showed all sorts of MIB variables and text being
    returned, but the MCC display only showed one item and it did that
    incorrectly.  Specifically:
    
    MCC> show snmp .sw.mcc.dswn03 cisco local lsystem all attr
    
    SNMP .sw.mcc.dswn03 cisco local lsystem
    AT 11-NOV-1992 15:20:24 All Attributes
    
                                   writeMem = -- Attribute Not Available
    MCC>
    
    However the MIB has some 69 items in the attributes list under lsystem.

    If I specify an item as found in the MIB, MCC will not complain
    in the parser but will not return any information at all.  Ie.
    
    MCC> show snmp .sw.mcc.dswn03 cisco local lsystem romid
    
    SNMP .sw.mcc.dswn03 cisco local lsystem
    AT 11-NOV-1992 15:27:06 Characteristics
    
    MCC>
    
    I will apologize if this has already been reported.  The customer
    indicates similar problems with the Synoptics MIB.
    
    Regards,
    
    Dave Comfort
T.RTitleUserPersonal
Name
DateLines
4068.1See 4060.*RTR200::WOESTEMEYERWhy??...Why not!!!Thu Nov 12 1992 08:027
    Dave,
    
    I have been fighting exactly the same problem with another customer
    with Cisco's and the Lsystem group.  You might want to follow my note,
    4060.*.
    
    Steve Woestemeyer
4068.2YAHEY::BOSEThu Nov 12 1992 17:275
	Steve has kindly provided me with the ip address of his cisco router.
	Investigating this problem is the next thing on my list.

	/rb
4068.3YAHEY::BOSETue Dec 01 1992 21:386
	Dave,

		Please read note #4060.4 for an answer to your problem.

	Rahul.