3Com 4007, Implementation Manual, Page: 108 / 684

108 C
HAPTER
4: C
ONFIGURING AND
U
SING
EME O
PTIONS
Reporting Diagnostic
Errors
If the
servdiag
test encounters an error, and if it is set to stop on the
error, the module does not function. If this occurs, call your 3Com reseller
or 3Com Technical Support immediately to obtain assistance.
See “The cont_mode Characteristic” later in this chapter for information
about how to set the
servdiag
diagnostic tests to stop on different types
of errors.
Setting
servdiag
Characteristics
With the
set servdiag
command, you can specify how the EME
executes the diagnostics tests on the module that you specify. The
characteristics are:
■
cont_mode
■
loop_count
■
verbosity
The
cont_mode
Characteristic
The
cont_mode
(continuation mode) of the diagnostic test determines
whether the test continues after it encounters an error. The continuation
mode can be one of the following:
■
continue
— The test reports an error then proceeds to the next test
after it encounters the error.
■
halt_on_fatal
— The test stops when it encounters a fatal error. The
module is no longer functional. This is the default continuation mode.
■
halt_on_nonfatal_and_fatal
— The test stops when it encounters
a nonfatal error or a fatal error. The module is not longer functional.
The following example sets the
cont_mode
to
continue
:
CB9000> set servdiag cont_mode continue
The
loop_count
Characteristic
The
loop_count
characteristic determines how many times the EME runs
the diagnostic test on the module that you specify. Because the module
does not pass network traffic during the tests, do not set a high loop
count when you need to use the module in your network.
Valid values for the
loop_count
characteristic are 0 through 65535. The
default
loop_count
value is 1. A value of zero causes the test to run
indefinitely. The following example sets the
loop_count
to 5:
CB9000> set servdiag loop_count 5