1. MIB Testing
Dr. K. Arvind
Networks Engineering
Digital Equipment Corporation
Session: NE016
Date: June 9, 1993
Time: 12:00 - 1:00 PM
Slide No. 1
2. PLAN
1. Management Information Base
(MIB) Framework
2. MIB Testing.
3. MIB Test Engine (MTE).
4. Current Status.
Slide No. 2
3. Management
Information Base
1. Internet-standard Network
Management Framework
2. SMI: Structure of Management
Information.
RFC 1155.
3. MIB: Management Information Base
RFC 1213, ...
4. Mechanism: Simple Network
Management Protocol (SNMP).
RFC1157.
Slide No. 3
4. SMI
1. Structure of management
information:
A. Tree structured.
B. Descendants of the internet
node (1.3.6.1) in the ASN.1
naming tree.
2. Components of management
information:
A. Example
B. Object types and instances
C. New data types:
DisplayString, IpAddress, Counter,
Gauge, TimeTicks, Opaque
Slide No. 4
5. OBJECT-TYPE
EXAMPLE
sysDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-only
STATUS mandatory
DESCRIPTION
quot;A textual description of the entity.
This value should include the full
name and version identification of
the system’s hardware and
software operating-system, and
networking software.It is
mandatory that this only contain
printable ASCII characters.quot;
::= {system 1}
1. Object-type: sysDescr
Object identifier: system.1 = 1.3.6.1.2.1.1.1
2. Attributes:
Syntax, Access, Status
3. Description
Slide No. 5
6. MIB
1. Management Information Base:
A. Collection of Managed
Objects.
B. Documents defining the
collection.
2. MIB-II: Core set of objects to be
implemented by all TCP/IP
nodes.
3. Other MIBs
A. Extensions to MIB-II
B. Experimental subtree
C. Enterprises subtree
Slide No. 6
7. What is MTE?
1. MIB Test Engine
MIB Test Environment
2. Quality Assurance support for
management firmware.
3. Integrated test engine for
a posteriori testing of MIB
implementations.
4. Collection of tools to support
testing and debugging.of
management firmware.
Slide No. 7
8. MTE Features
1. Regression testing
2. High degree of automation
3. Test Information Management
4. Composite tool set
A. Translation tools
B. Generation tools
C. Interrogation tools
D. Management tools
5. PERL !!!
6. Standard Style
Slide No. 8
10. MTE Organization
Product
Test
Script
Specs Translate Execute Pass/Fail
Translate Execute
Not as simple as it appears !!!
1. Specification notation
2. Composite object
3. Manual intervention
Slide No. 10
11. OTE Organization
MIB MIBC
MIBC
TGEN
TGEN
Aux AUXC
AUXC
a
TIBTOOLS
TIBTOOLS
TIB
TIB
T
TIB
CMW LCE NMS
MODULE
UNDER
TEST
Slide No. 11
12. MIBC
MIB MIBC
MIBC
1. Applications
A. Input for TGEN
B. ASN.1 conformance
C. Online reference
D. Name/OID maps
2. Limitations:
Not a generalized ASN.1 compiler.
Understands only the subset of ASN.1
used in MIB specifications.
3. Example:
mibc -f rfc1213.mib
mibc -m -f rfc1213.mib >rfc1213.map
mibc oid sysDescr
Slide No. 12
13. AUXC
AUX MIBC
AUXC
1. Generates input for TGEN
2. AUX: Notation for specifying auxiliary
information not deducible from MIBs.
3. Auxiliary information:
A. Overide SYNTAX/ACCESS fields
B. Dependencies
C. Traps
D. Volatility
E. Configurability
F. Table bounds
4. Example:
portControlObject:nt:trunkControlObject{(1 2)}
Slide No. 13
14. TGEN
PERL scripts
from MIBC MIBC
from AUXC TGEN
English specs
1. Test generator
2. Test scripts and specifications
3. Test types
A. existense
B. modifiability
C. configurability
D. traps
E. dependency
F. volatility
Slide No. 14
16. SPEC EXAMPLE
Test generic-rfc9999.10.1.1.3.6.1.4.1.999.2.2.0.1
SUMMARY
Make sure that the mandatory mib object:
1.3.6.1.4.1.999.2.2.0.1 (moduleIpAddress)
is readable and has a permissible value. Also
verify that any other mib object that should
track the value of this object does so.
DESCRIPTION
(1) Do a get on:
1.3.6.1.4.1.999.2.2.0.1 (moduleIpAddress).
-- The get must be successful and the value
must match:
pattern(/^[0-9]+(.[0-9]+){3}$/).
(2) Do a get on:
extIpAddress.
-- The get must be successful and the value
must be equal to the value obtained in
Step(1)
Slide No. 16
17. TIB
TIBTOOLS
TIB
TIB
TIB
1. Test Information Management
2. Modeled after the SNMP MIB
framework
3. Components
A. STI: Structure of test
information
B. TIB: Test Information Base
C. MTI: Management of test
information
Slide No. 17
18. STI
root
0 1 2 3
misc int ext ...
0 1 2
misc 3 4
com tr rep fddi
0 1 2
commisc comp1 comp2
0 1
1. Structure of test information
2. Classification is important for
management
3. Tree structured space
4. Nomenclature: tib identifiers
5. Batteries: Interior nodes
6. Tests: Leaves
Slide No. 18
19. TIB
1. Test: Abstract entity
2. Test Information Base
3. TIB files:
a. Script file
b. Initialization script file (.init)
c. Specification file (.spec)
d. Synopsis file (.synopsis)
e. Command file (.com)
f. Reference file (.ok)
g. Result file (.res)
h. Time file (.time)
i. Special instructions file (.ins)
Slide No. 19
20. MTI
1. Management of Test Information
2. Operations:
A. Information creation and structuring
B. Information retrieval
C. Running tests
3. TIBTOOLS: Toolkit
A. Information creation and structuring
a. mktree, rmtree, rmbat
b. mktest, rmtest
c. mvnode, cpnode
d. tibedit
B. Information retrieval
a. battery
b. tibfiles, tibspecs, tibres, tibstat
C. Running tests
a. tibrun, cmptest
b. bugmail
D. Miscellaneous operations
a. deftest, defbat, deftree
b. tibnext
Slide No. 20
