I am working with a device that is SNMP manageable and has 2 card types in
it. A highspeed card and a lowspeed card. Each card has a separate MIB
definition that goes with it. Each MIB has a parameter called 'baudRate',
which is a list of 16 items. The definition for each of these numbers is
different for each card. For instance- the baudRate item number 1 text of
the Lowspeed is = ds1. The text for item number 1 on the list if the
highspeed card baudRate variable is 14.1M.
If I connect to the High Speed Card e.g.
set s [snmp session -address 156.88.88.122] and load the associated MIB 'mib
load HSSv2.0'
and then do a '$s get baudRate' the answer 14.1M will return.
HOWEVER,
If I do the same procedure on a different workstation I get the response
'ds1'. It is associating the wrong baudRate list for the card.
Just as some clarifiers:
- I do NOT have a low speed card available in the lab (i.e. it CANNOT be
connecting to it by accident).
- I deleted all of the lowspeed card MIBs from the computer so it cannot
lookup the wrong baudRate
- I am running the same scotty and Tcl on both workstations and have as
similar environments (paths, libs, etc) as is possible.
- It is consistent for all values on the MIB list (lowspeed 4 is received
when highspeed 4 is the real answer, etc)
When I examine the SNMP packets on an analyzer, the OID is correct for the
variable and the response (equal to 1) is also correct. Somehow it is being
converted by Scotty when it receives number 1 and looking up the actua text
associated with the variable list and extracting the wrong name. I do not
see how it is possible if the MIB file it is getting this info from is not
there!!! I also checked the highspeed MIB file for the 'ds1' parameter and
it does not exist....so it can't be getting it frmo the loaded MIB.
HELP!!!
Thanks