T.R | Title | User | Personal Name | Date | Lines |
---|
6065.1 | Some answers | TAEC::PHOBOE::Flauw | C.E.M. Technical Office, Valbonne | Wed Aug 03 1994 03:35 | 21 |
| Meg,
My understanding of SNMP is somewhat limited, so if there is any SNMP guru around, please correct me.
You get partial registration messages when the Registration FM cannot get all the identifiers of your
entity. For an SNMP entity, there is 3 identifiers :
- Address of type IpAddress
- Name of type InternetName
- Registered Name of type FullName
When registering an entity, the Registration issues a show directive to get all identifiers and in your
case, there must be one missing. Did you provide a synonym for your SNMP entity when registering it ?
Do you have a name corresponding to the IPAddress of your device defined in /etc/hosts or in your Bind
server ?
Being able to access the characteristics of the object using its IPAddress is simply showing that the
object is there and answering this directive.
Hope this helps,
Marc.
|
6065.2 | MTU of Cisco MIB??? | DPDMAI::GALVIN | Ok Winnie, it'll just fall off again... | Wed Aug 03 1994 07:28 | 11 |
| Meg,
Obvious question, did you integrate the CISCO MIB into your dictionary?
This might be way off..., but if/when you do get it registered, you'll
see more functionality... of course, it may not be related to the
problems you're seeing...just thought I'd throw this out... There's an
MTU or some such procedure that allows you to integrate MIBs... check
in MCC_COMMON... good luck.
/Mic
|
6065.3 | | NPSS::WADE | Network Systems Support | Wed Aug 03 1994 13:10 | 17 |
|
When mcc registers an snmp entity it sends out a getnext against the dec
object. Why; I don't know.
If you get a trace you'll probably see that the Cisco AGS does not
respond to this getnext request. I saw the same thing with the
Packetprobe90 agent. The correct response for conformance to RFC1157 is
"no such name".
Everything else about the registration seems to be okay.
|
6065.4 | | MOLAR::MOLAR::BOSE | | Thu Aug 04 1994 15:51 | 16 |
| >> When mcc registers an snmp entity it sends out a getnext against the dec
>> object. Why; I don't know.
Actually a getnext is sent out for each toplevel object for
each mib extension loaded in the dictionary. So, if you have the
DEC mibs loaded, then you'll see a getnext request against the
"dec" object. The purpose of this query is to determine which mibs
are supported by the agent being registered. The supported
mibs will show up as child entities of the SNMP global entity in
the iconic map.
An agent, when it does not support a particular mib, should return
a "noSuchName" error for the getNext operation. If the agent chooses
to not respond at all, then you might get partial registration.
Rahul.
|