| Well, I took your advice, using the mib query utility, and used the
example OID to feed to the Tektronix agent, and specified GetNexts,
and I got a bunch of stuff back that looked good, and a lot of empty
things too. Tektronix says that this stuff is MIB-I compliant only,
and I don't have the extensions for this particular mib integrated
into MCC yet.
But, I can use the FCL to get things like sysuptime,
countercreationtime from the Tek terminal. However, these things
don't fully register with MCC, they fail with a "no response from
entity" message, which is the same response I get with the issue of
an "show snmp "name" sysdescr. If I issue the same command to an
RS/6000 it comes back fine.
Does this illustrate a difference between MIB-I and MIB-II behavior?
Do I have to run the Tektronix MIB-I extensions through MTU before
these monsters register fully?
-Craig
|
| > Do I have to run the Tektronix MIB-I extensions through MTU before
> these monsters register fully?
NO! The pre-loaded MIB-II is only a superset of MIB-I; in other words:
you got MIB-II, so you got MIB-I as well.
Since the Tektronix agent seems to have a problem with GetNext, this may
well be the cause for the problem. MCC tries each loaded MIB extension
to see if the agent can support it. If it gets no response here (which
is a bug in the agent!), it'll stop and report a 'partial registration'.
But even with partial registration you should be able to handle the
Tektronix. Just remember that MCC assumes MIB-II and you'll get a lot of
'not gettable' messages which you may ignore.
*Robert
|