•
•
•
•
What is DaniWeb IT Discussion Community?
You're currently browsing the Software Developers' Lounge section within the Software Development category of DaniWeb, a massive community of 401,508 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 3,294 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Views: 409 | Replies: 0
![]() |
•
•
Join Date: Dec 2007
Posts: 3
Reputation:
Rep Power: 0
Solved Threads: 0
Hi, I am new to SNMP and am trying to define MIB for a product. I am struggling while defining two tables that are interrelated.
While expanding a base table with an exapnsion table is it necessary that the INDEX of the expansion table are in the order baseTableIndexes-->expansionTableIndexes as below :
-- row definition in base table
baseEntry OBJECT-TYPE
... -- other clauses here
INDEX { baseIndex1, baseIndex2 }
::= { baseTable 1 }
-- row definition in expansion table
expEntry OBJECT-TYPE
... -- other clauses here
INDEX { baseIndex1, baseIndex2, expIndex1}
::= { expTable 1 }
Can define the expansion table INDEX in the order
expansionTableIndexes-->baseTableIndexes as shown below :
-- row definition in base table
baseEntry OBJECT-TYPE
... -- other clauses here
INDEX { baseIndex1, baseIndex2 }
::= { baseTable 1 }
-- row definition in expansion table
expEntry OBJECT-TYPE
... -- other clauses here
INDEX { expIndex1, baseIndex1, baseIndex2 }
::= { expTable 1 }
Any ideas, what the standard says about this ?
Rahul
While expanding a base table with an exapnsion table is it necessary that the INDEX of the expansion table are in the order baseTableIndexes-->expansionTableIndexes as below :
-- row definition in base table
baseEntry OBJECT-TYPE
... -- other clauses here
INDEX { baseIndex1, baseIndex2 }
::= { baseTable 1 }
-- row definition in expansion table
expEntry OBJECT-TYPE
... -- other clauses here
INDEX { baseIndex1, baseIndex2, expIndex1}
::= { expTable 1 }
Can define the expansion table INDEX in the order
expansionTableIndexes-->baseTableIndexes as shown below :
-- row definition in base table
baseEntry OBJECT-TYPE
... -- other clauses here
INDEX { baseIndex1, baseIndex2 }
::= { baseTable 1 }
-- row definition in expansion table
expEntry OBJECT-TYPE
... -- other clauses here
INDEX { expIndex1, baseIndex1, baseIndex2 }
::= { expTable 1 }
Any ideas, what the standard says about this ?
Rahul
![]() |
•
•
•
•
•
•
•
•
DaniWeb Software Developers' Lounge Marketplace
•
•
•
•
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
•
•
•
•
ajax applications asp blog browsing bt business business software developer development devices download erp systems experiment india intel internet it japan java linux malware mcafee media microsoft mmorpg mobile applications news office open-source pricing programming project management publishing rss search security software software selection spyware sql sun technology evaluation tips vista web wiki windows xp
- Previous Thread: list of free e books on internet
- Next Thread: need help in designing a project


Linear Mode