[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

4690.0. "SNMP AM Questions?" by SKULLY::COMPTON (Dorie) Mon Mar 15 1993 08:06

Ultrix 4.3 
DECmcc V1.2.3


 I have an OEM who is working with a proxy agent and has discovered that
when using the SNMP Access module to request an attribute it appears to 
always send two get requests when asking for a single attribute:  
 
1) Is this the expected behavior?  
2) The agent also doesn't preserve the order of the attributes and actually
sends them in reverse order, but the access module doesn't seem to look
at the OID number and when displaying the information some of the fields
are not correct.

The first request always seems to ask for the 
sysUptime
sysDescription
sysObjectID
 
and the second request seems to ask for
sysDescription
sysIfnumber
sysName
sysLocation
sysServices
 
This is when I am requesting a single attribute such as sysContact.


                   Dorie
T.RTitleUserPersonal
Name		DateLines
4690.1fixed in V1.3MCDOUG::dougpre-retinal integrationMon Mar 15 1993 09:289
    Sounds like the 'SNMP Hello Packet' problem that we ran into with
    StrataCom's proxy agent.    

    If you can use the new V1.3 MCC BMS kit (now called POLYCENTER Network
    Manager <mumble>), then you shouldn't see this problem anymore.  If you
    upgrade and still see it, then please us know here.
    
/doug
4690.2Please explain SNMP Hello MessageSKULLY::COMPTONDorieMon Mar 15 1993 10:516
    Does this mean the first Get Request is an SNMP hello message?
     
    I believe that two messages are also sent out when talking to a SNMP
    deamon directly and not just the proxy agent.
     
     			Dorie
4690.3TeMIP doesn't support BMS 1.3 YetSKULLY::COMPTONDorieMon Mar 15 1993 10:524
    Also, it does not look like can just use the MCC BMS 1.3 kit, because
    we are also using TeMIP.
     
    		Dorie
4690.4Agent must support the Mib I system groupMOLAR::PERRYTue Mar 16 1993 15:2922
    Dorie,
    
    The first Pdu the SNMP AM sends to any SNMP agent is what we call
    the "hello message". This message is an SNMP Get Pdu for the
    following objects:
    
    sysUptime
    sysDesc
    sysObjectID
     
    This Pdu is always the first one sent regardless of the actual objects 
    the user is requesting. Also, we did not remove this hello message in 
    V1.3. We "improved" the hello message error handling so that errors 
    in the hello message response Pdu don't affect the subsequent request 
    for the user's  data.
    
    In mcc version V1.2, any errors in the hello message reponse Pdu would 
    cause the SNMP AM to abort the user's request.
    
    Hope this helps.
    
    Jim
4690.5order is very importantMOLAR::PERRYTue Mar 16 1993 17:199
    Dorie,
    
    I forgot to mention that the agent must return the objects in the
    exact order in which they were requested. The SNMP specification specifies
    this and the DECmcc SNMP AM counts on it. Otherwise the results will be
    unpredictable.
    
    Jim