Editing SNMP MIB Implementation
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 152: | Line 152: | ||
===Binary File Format <name>_trap.bin=== | ===Binary File Format <name>_trap.bin=== | ||
* The binary file store TRAP information. It is generated by mib2bin tool. Agents will read binary file to get information of TRAP when something bad occurs. | * The binary file store TRAP information. It is generated by mib2bin tool. Agents will read binary file to get information of TRAP when something bad occurs. | ||
− | * In the binary file, An enterprise OID is stored first, followed by its first specific trap number and | + | * In the binary file, An enterprise OID is stored first, followed by its first specific trap number and ID (this ID matches with ID of leaf in <name>.bin) <font color=red>data bindings to be included in this trap to last specific trap number and ID data bindings to be included it. Next, the structure of next this enterprise is stored. This structure is repeated until all enterprise in MIB file is stored.</font> |
* The format of enterprise in <name>_trap.bin | * The format of enterprise in <name>_trap.bin | ||
<enterprise_oid><sibling_enterprise><enterprise_index>[specific_trap_number][sibling_specific_trap][number_varbinds][id_varbind]... | <enterprise_oid><sibling_enterprise><enterprise_index>[specific_trap_number][sibling_specific_trap][number_varbinds][id_varbind]... |