Home
You are not currently signed in.

MIB Smithy

Developer's Guide

  1. Document Conventions
  2. Getting Started
  3. General Provisions

SMI Databases

  1. Basics
  2. Creating Records
  3. Destroying Records
  4. Importing Modules
  5. Database Search
  6. Querying Properties
  7. Setting Properties
  8. Comparing OIDs
  9. Building/Parsing OIDs
  10. Logging
  11. Record Types
  12. Pattern Matching
  13. MIB Validation
  14. Tree Introspection

SNMP Sessions

  1. Basics
  2. Opening Sessions
  3. Closing Sessions
  4. Listing Sessions
  5. Configuring Sessions
  6. Session Aliases
  7. Get Requests
  8. Set Requests
  9. Get-Next Requests
  10. Get-Bulk Requests
  11. Inform Requests
  12. Sending Traps
  13. Walking Subtrees
  14. Receiving Traps
  15. Pending Requests
  16. Waiting for Requests
  17. Cancelling Requests
  18. Variable Bindings
  19. Callback Functions
  20. Formatting Data
  21. Scanning Data
  22. Logging

USM

  1. USM Key Management

Scotty/TNM Porting

  1. Compatibility Package
  2. MIB Commands
  3. SNMP Commands
  1. Up to Table of Contents

Determining Record Types

Given a search string, in particular an OID, it is often useful to determine what type of record it corresponds to. This information is available by way of the whatis database subcommand. The SDK also provides an API to perform the reverse action (seeing whether or not a record is of a specified type) using the is subcommand. See Built-in Pattern Matching for details.

Syntax:

% dbcmd whatis recordName

Where:

dbcmd
is the name of the database; and
recordName
is a record search string (name, OID, or combination of such) identifying the record in question.

Returns:

  • The return value generally corresponds to the name of the macro used to define the record in normal SMI syntax:
capability
AGENT-CAPABILITIES Statement.
compliance
MODULE-COMPLIANCE Statement.
conformance-group
GROUP reference within MODULE-COMPLIANCE module reference.
conformance-module
MODULE or SUPPORTS module reference ("conformance module") within an AGENT-CAPABILITIES or MODULE-COMPLIANCE statement.
file
File Record.
leaf
OBJECT-TYPE definition (including tables/rows).
module
MIB Module.
moduleid
MODULE-IDENTITY Statement.
node
OID Value Assignment or OBJECT-IDENTITY (see note).
notification
NOTIFICATION-TYPE or TRAP-TYPE definition.
notify-group
NOTIFICATION-GROUP definition.
object-group
OBJECT-GROUP definition.
typedef
ASN.1 Type Assignment or TEXTUAL-CONVENTION.
undefined
No record exists with the given search pattern.
valuedef
ASN.1 Value Assignment (see note).
variation
OBJECT or VARIATION reference within an MODULE-COMPLIANCE or AGENT-CAPABILITIES module reference.

See Also

Notes

ASN.1 value assignments of types other than OBJECT IDENTIFIER are forbidden by the SMI. The SDK treats OID value assignments as indistinguishable from OBJECT-IDENTITY statements without descriptions (although, strictly speaking, OBJECT-IDENTITY "registers" an OID while an OID value assignment does not according to the SMI rules). Therefore, when a module is loaded from file, this command will return "node" for OID value assignments as well as for OBJECT-IDENTITY statement. As well, the "node" record type should be used when creating either from Tcl.
  1. Up to Table of Contents
Copyright © 2024 Muonics, Inc. All Rights Reserved. Muonics, MIB Smithy, MIB Views, and their respective logos are trademarks of Muonics, Inc.