Someone sitting in front of a mib browser might chime in with a more specific
answer, but in general, Mib variables that have these variable instance ids are
not what the data collector was designed to handle. There is likely a table
somewhere else in the mib that maps the ports to those instance ids, so it is
really a two-step process and the data collector is designed for a one-step
process - mostly to gather counts that increase rather than monitor changes
in state of an enumeration field.
Many devices are more than willing to send traps when these state changes
occur, and those traps often contain port/slot information. Have you checked
into enabling those traps?
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager
---------------------- Forwarded by Leslie Clark/Southfield/IBM on 10/05/99
05:03 PM ---------------------------
Alec Himwich <HIMWICH@QUALEXPHOTO.COM> on 10/05/99 11:33:40 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc:
Subject: MIB collection vs MIB browsing on NetView for NT
I am attempting to collect data relating to port insertion on a Centillion 5000.
The ObjID of the data being collected is .1.3.6.1.4.1.4.5.1.6.7.1.1.1.5
(s5TrPortTable.s5TrPortInsrtStatus). When I look at this data via the MIB
browser, I get data like MIB Instance: 2.14 and MIB value: notInserted. When I
look at the same data as it is collected via snmpcollect, I get data like MIB
Instance: 6 and MIB value: 2. This is the sort of data that gets dumped into
the database. I can deal with the difference in the MIB value since this is
just an enumeration value. However, valuable data is being lost on the report
of the MIB instance since we are trying to track which ports on the device are
actually being used. As it is, the snmpcollected data is useless.
Is this a bug? Is there someway to actually collect what I need?
TIA
Alec Himwich
IBM Global Services
|