Hello,
Thanks for a detailed response.
Putting the question now is:
Snmpwalk on one of the Enterasys devices 'Matrix N7 Platinum Rev 05.22.03' took
more than 30 hours and yet could not get completed.
Later when I checked the SNMP output, I see that one specific MIB attribute,
dot1qVlanFdbId, being indexed on INDEX { dot1qVlanTimeMark, dot1qVlanIndex }. I
keep getting dot1qVlanTimeMark recursively and it is looping through it.
I would like to know if Enterasys supports Q-BRIDGE-MIB and if so, how can this
problem be rectified.
Should I use "set snmp timefilter break" to avoid this situation ?
Thanks in advance.
Regards,
Karthik
-----Original Message-----
From: Eaton, Ernest [mailto:[email protected]]
Sent: Thursday, March 26, 2009 10:08 PM
To: Enterasys Customer Mailing List
Subject: [enterasys] RE: [enterasys] "set snmp timefilter break"
Is "set snmp timefilter break" configured?
Several MIB tables are indexed by timeFilter. A proper implementation of the
MIB will return an entry for every possible timeFilter index value that is less
than the sysUpTime during which the table entry last changed. Used properly
this mechanism allows management stations to query a potentially large table
once, remember the sysUpTime of that query and then only query change by using
getnext with the timeFilter equal to the previous query sysUpTime. When the
SNMP tool fails to detect the change in TimeFilter the results can be millions
of responses for what would otherwise be a small table. A system that had been
operating for ~497 days (sysuptime = 0xFFFFFFFF) could return 4+ billion
objects.
The "set snmp timefilter break" command causes our system to violate the
timefilter mechanism and only return data for the table until the timefilter
would need to increment. I.E. you only get one copy of the table.
Most snmpwalk tools are not smart enough to interpret the timeFilter index and
skip to the next MIB. Enable the snmp timefilter break mechanism when using
such a tool.
The following is excerpted from the RFC 2021 RMON2 MIB which provided the
initial definition and use of TimeFilter. You can see that they clearly intend
for the system to return entries for every valid timeFilter value.
TimeFilter ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"To be used for the index to a table. Allows an application
to download only those rows changed since a particular time.
A row is considered changed if the value of any object in the
row changes or if the row is created or deleted.
When sysUpTime is equal to zero, this table shall be empty.
One entry exists for each past value of sysUpTime, except that
the whole table is purged should sysUpTime wrap.
As this basic row is updated new conceptual rows are created
(which still share the now updated object values with all
other instances). The number of instances which are created
is determined by the value of sysUpTime at which the basic row
was last updated. One instance will exist for each value of
sysUpTime at the last update time for the row. A new
timeMark instance is created for each new sysUpTime value.
Each new conceptual row will be associated with the timeMark
instance which was created at the value of sysUpTime with
which the conceptual row is to be associated.
By definition all conceptual rows were updated at or after
time zero and so at least one conceptual row (associated with
timeMark.0) must exist for each underlying (basic) row.
See the appendix for further discussion of this variable.
Consider the following fooTable:
fooTable ...
INDEX { fooTimeMark, fooIndex }
FooEntry {
fooTimeMark TimeFilter
fooIndex INTEGER,
fooCounts Counter
}
Should there be two basic rows in this table (fooIndex == 1,
fooIndex == 2) and row 1 was updated most recently at time 6,
while row 2 was updated most recently at time 8, and both rows
had been updated on several earlier occasions such that the
current values were 5 and 9 respectively then the following
fooCounts instances would exist.
fooCounts.0.1 5
fooCounts.0.2 9
fooCounts.1.1 5
fooCounts.1.2 9
fooCounts.2.1 5
fooCounts.2.2 9
fooCounts.3.1 5
fooCounts.3.2 9
fooCounts.4.1 5
fooCounts.4.2 9
fooCounts.5.1 5
fooCounts.5.2 9
fooCounts.6.1 5
fooCounts.6.2 9
fooCounts.7.2 9 -- note that row 1 doesn't exist for
fooCounts.8.2 9 -- times 7 and 8"
SYNTAX TimeTicks
-----Original Message-----
From: Senthilkumar, Karthikeyan (BTO-NMC) [mailto:[email protected]]
Sent: Thursday, March 26, 2009 2:41 AM
To: Enterasys Customer Mailing List
Subject: [enterasys] set snmp timefilter brea
Hello All,
I am stumped with the problem in trying to do a snmpwalk on one of the
Enterasys devices 'Matrix N7 Platinum Rev 05.22.03'. It took more than 30 hours
and yet could not get completed.
Later when I checked the SNMP output, I see that one specific MIB attribute,
dot1qVlanFdbId, being indexed on INDEX { dot1qVlanTimeMark, dot1qVlanIndex }. I
keep getting dot1qVlanTimeMark recursively and it is looping through it.
I would like to know if Enterasys supports Q-BRIDGE-MIB and if so, how can this
problem be rectified.
Thanks,
Karthik
---
To unsubscribe from enterasys, send email to [email protected] with the body:
unsubscribe enterasys [email protected]
---
To unsubscribe from enterasys, send email to [email protected] with the body:
unsubscribe enterasys [email protected]
---
To unsubscribe from enterasys, send email to [email protected] with the body:
unsubscribe enterasys [email protected]
