Hi,
I sent out an email a week ago which I wish could get some feedback.
Continuing my research, I found in RFC2741 an Example which is exactly what I want to do to avoid conflict of ifTable between master agent and my subagent.
7.1.4.2.3. Examples
Example 1:
A subagent implements an interface, and wishes to register a
single row of the RFC 2233 ifTable. It requests an allocation for
the index object "ifIndex", for a value that has never been
allocated (since ifIndex values must be unique). The master agent
returns the value "7".
The subagent now attempts to register row 7 of ifTable, by
specifying a MIB region in the agentx-Register-PDU of
1.3.6.1.2.1.2.2.1.[1-22].7. If the registration succeeds, no
further processing is required. The master agent will dispatch to
this subagent correctly.
Would you give me some advise on how this subagent should register or allocate a single row of ifTable?
Thank you very much.
-Emi
----- Forwarded by Emi Yanagi/Radisys_Corporation/US on 03/24/2005 09:33 AM -----
03/15/2005 03:39 PM |
|
I have a question about ifIndex and its instances. If I do a snmpwalk on ifIndex, I got
$snmpwalk 10.1 ifIndex
IF-MIB::ifIndex.1 = INTEGER: 1
IF-MIB::ifIndex.2 = INTEGER: 2
IF-MIB::ifIndex.3 = INTEGER: 3
IF-MIB::ifIndex.4 = INTEGER: 4
In order to avoid some sort of collision with my switchport subagent, I want the master agent start ifIndex instance from 13, not 1. Is it possible to move the instances to 13-16? If the answer is yes, I would appreciate if you point me where these instance implementation is.
Thanks,
-Emi
<<inline: pic09161.gif>>
<<inline: ecblank.gif>>
