Module records represent the highest-level structure of an actual MIB or PIB specification. It is a container record, like file records and databases, so it provides properties for heirarchical lists of the records defined within them. It also provides important properties for the specifications themselves, particularly for the IMPORTS, which specify the relationship between definitions of different modules such as types and layout of the OID tree.
% dbcmd get property ?property ...? module
-capabilities
Returns a list of all AGENT-CAPABILITIES statements defined within the module.
cap1 cap2 cap3 ...
-cgroups
Like -cmodules
, but each conformance module name is coupled with a list of all conformance groups (GROUP) defined within the conformance module of a MODULE-COMPLIANCE.
comp1 { MODULE1 { group1 group2 group3 ... } ... } ...
-cmodules
Like -capabilities
and -compliances
, but each conformance name is coupled with a list of all conformance modules (SUPPORTS/MODULE) defined within the conformance.
comp1 { MODULE1 MODULE2 ... } comp2 { MODULE1 MODULE2 ... } ...
-comments
-compliances
Returns a list of all MODULE-COMPLIANCE statements defined within the module.
comp1 comp2 comp3 ...
-container
-fullname
for the container record, or for the queried record with the last envelope stripped off.-exportslist
Returns the list of symbols that are exported from the module (i.e., those that can be imported into another module, as in the EXPORTS
section at the start of an ASN.1 module)). SMIv2 modules are forbidden to use the EXPORTS
convention: all symbols are implicitly exported from such modules.
symbol1 symbol2 symbol3 ...
-fullname
!
(exclamation point), as in @File1!SNMPv2-MIB
.-fulloid
1.3.6....
). If the OID is not able to be resolved all the way to one of the root nodes (ccitt, iso, joint-iso-ccitt), due to one or more dependent modules not being present in the database, then the first component will be that of the descriptor that could not be resolved.-groups
-importslist
IMPORTS
section at the start of an ASN.1 module). The result is a list of lists of the form: { symbolList moduleName ?oidvalue? }
, where symbolList
is a list of symbols to import from the module named moduleName
and oidvalue
is an optional object identifier value that unamibuously references the module (either assigned in the module header in ASN.1/SMIv1 modules or the value of an SMIv2/COPS-PR-SPPI module's MODULE-IDENTITY statement).-members
Returns a list of all records that are immediate children of the module.
Type1 Type2 rec1 rec2 rec3 ...
-moduleids
-name
-ngroups
Returns a list of all NOTIFICATION-GROUP records defined within the module.
group1 group2 group3 ...
-notifications
Returns a list of all NOTIFICATION-TYPE and TRAP-TYPE records defined within the module.
trap1 trap2 trap3 ...
-objects
Returns a list of all OBJECT-TYPEs defined within the module.
obj1 obj2 obj3 ...
-ogroups
Returns a list of all OBJECT-GROUP records defined within the module.
group1 group2 group3 ...
-oid
a.1.2.3
will be returned even if the OID value is declared in the ASN.1 as { EX-MIB.a b(1) c(2) 3 }
.-oids
Returns a list of all record definitions that are immediate children of the module and assign or register an object identifier value, including various macro invocations and ASN.1 OID Value Assignments.
rec1 rec2 rec3 ...
-rootnodes
-oids
whose OID values place them in the OID tree above all other records within the same module (i.e., the subset whose parents are in defined in other modules). For example, if all OIDs in an SMIv2 module are defined subordinate to the MODULE-IDENTITY statement, then this option will return the name of that MODULE-IDENTITY.-tags
EXPLICIT
or IMPLICIT
, with the former being the default.-typedefs
Returns a list of all ASN.1 Type Assignments and TEXTUAL-CONVENTIONs defined within the module.
Type1 Type2 Type3 ...
-value
-oid
for get
operations.-valuedecl
module.descriptor
form it is returned as module:descriptor
. That is, SNMPv2-MIB:system.1
will be returned if the OID value is declared in the ASN.1 it as { SNMPv2-MIB.system 1 }
.-values
Returns a list of all ASN.1 Value Assignments (other than OIDs) defined within the module.
rec1 rec2 rec3 ...
-variations
Like -cmodules
, but each conformance module name is coupled with a list of all variations (OBJECT/VARIATION) defined within the conformance statement.
comp1 { MODULE1 { var1 var2 var3 ... } ... } ...