| OID symbolic | OID numeric | Type | Access | Description |
|---|
| bbSelt | 1.3.6.1.4.1.193.72.602.10 | | | In this module are defined the control entries for input
and output data for different types of broadband line tests. |
| bbSeltTestGroup | 1.3.6.1.4.1.193.72.602.10.5 | | | |
| bbSeltTestTable | 1.3.6.1.4.1.193.72.602.10.5.1 | | not-accessible | This table contains one entry per line. It
defines objects which allow a network manager to
instruct an agent to test a line for various
faults. Tests for a line are defined in the
media-specific MIB for that line. After invoking
a test, the object bbSeltTestResult can be read to
determine the outcome. If an agent can not perform
the test, bbSeltTestResult is set to so indicate. The
object bbSeltTestCode can be used to provide further
test-specific or line-specific (or even
enterprise-specific) information concerning the
outcome of the test. Only one test can be in progress
on each line at any one time. If one test is in
progress when another test is invoked, the second test
is rejected. Some agents may reject a test when a
prior test is active on another line.
Before starting a test, a manager-station must first
obtain 'ownership' of the entry in the bbSeltTestTable for
the line to be tested. This is accomplished with
the bbSeltTestId and bbSeltTestStatus objects as follows:
try_again:
get (bbSeltTestId, bbSeltTestStatus)
while (bbSeltTestStatus != notInUse)
/*
* Loop while a test is running or some other
* manager is configuring a test.
*/
short delay
get (bbSeltTestId, bbSeltTestStatus)
}
/*
* Is not being used right now -- let's compete
* to see who gets it.
*/
lock_value = bbSeltTestId
if ( set(bbSeltTestId = lock_value, bbSeltTestStatus = inUse,
bbSeltTestOwner = 'my-IP-address') == FAILURE)
/*
* Another manager got the bbSeltTestEntry -- go
* try again
*/
goto try_again;
/*
* I have the lock
*/
set up any test parameters.
/*
* This starts the test
*/
set(bbSeltTestType = test_to_run);
wait for test completion by polling bbSeltTestResult
when test completes, agent sets bbSeltTestResult
agent also sets bbSeltTestStatus = 'notInUse'
retrieve any additional test results, and bbSeltTestId
if (bbSeltTestId == lock_value+1) results are valid
A manager station first retrieves the value of the
appropriate bbSeltTestId and bbSeltTestStatus objects,
periodically repeating the retrieval if necessary,
until the value of bbSeltTestStatus is 'notInUse'. The
manager station then tries to set the same bbSeltTestId
object to the value it just retrieved, the same
bbSeltTestStatus object to 'inUse', and the corresponding
bbSeltTestOwner object to a value indicating itself. If
the set operation succeeds then the manager has
obtained ownership of the bbSeltTestEntry, and the value of
the bbSeltTestId object is incremented by the agent (per
the semantics of TestAndIncr). Failure of the set
operation indicates that some other manager has
obtained ownership of the bbSeltTestEntry.
Once ownership is obtained, any test parameters can be
setup, and then the test is initiated by setting
bbSeltTestType. On completion of the test, the agent sets
bbSeltTestStatus to 'notInUse'. Once this occurs, the
manager can retrieve the results. In the (rare) event
that the invocation of tests by two network managers
were to overlap, then there would be a possibility that
the first test's results might be overwritten by the
second test's results prior to the first results being
read. This unlikely circumstance can be detected by a
network manager retrieving bbSeltTestId at the same time as
retrieving the test results, and ensuring that the
results are for the desired request.
If bbSeltTestType is not set within an abnormally long
period of time after ownership is obtained, the agent
should time-out the manager, and reset the value of the
bbSeltTestStatus object back to 'notInUse'. It is
suggested that this time-out period be 5 minutes.
In general, a management station must not retransmit a
request to invoke a test for which it does not receive
a response; instead, it properly inspects an agent's
MIB to determine if the invocation was successful.
Only if the invocation was unsuccessful, is the
invocation request retransmitted.
Some tests may require the line to be taken off-
line in order to execute them, or may even require the
agent to reboot after completion of the test. In these
circumstances, communication with the management
station invoking the test may be lost until after
completion of the test. An agent is not required to
support such tests. However, if such tests are
supported, then the agent should make every effort to
transmit a response to the request which invoked the
test prior to losing communication. When the agent is
restored to normal service, the results of the test are
properly made available in the appropriate objects.
Note that this requires that the lineIndex value assigned
to a line must be unchanged even if the test
causes a reboot. An agent must reject any test for
which it cannot, perhaps due to resource constraints,
make available at least the minimum amount of
information after that test completes. |
| bbSeltTestEntry | 1.3.6.1.4.1.193.72.602.10.5.1.1 | | not-accessible | An entry containing objects for invoking tests on a line. |
| TES bbSeltTestId | 1.3.6.1.4.1.193.72.602.10.5.1.1.1 | TestAndIncr | read-write | This object identifies the current invocation of the
line's test. |
| INT bbSeltTestStatus | 1.3.6.1.4.1.193.72.602.10.5.1.1.2 | INTEGER | read-write | This object indicates whether or not some manager
currently has the necessary 'ownership' required to
invoke a test on this line. A write to this
object is only successful when it changes its value
from 'notInUse(1)' to 'inUse(2)'. After completion of
a test, the agent resets the value back to
'notInUse(1)'. |
| OID bbSeltTestType | 1.3.6.1.4.1.193.72.602.10.5.1.1.3 | AutonomousType | read-write | A control variable used to start and stop operator-
initiated line tests. Most OBJECT IDENTIFIER
values assigned to tests are defined elsewhere, in
association with specific types of line.
However, this document assigns a value for a full-
duplex loopback test, and defines the special meanings
of the subject identifier:
noTest OBJECT IDENTIFIER ::= { 0 0 }
When the value noTest is written to this object, no
action is taken unless a test is in progress, in which
case the test is aborted. Writing any other value to
this object is only valid when no test is currently in
progress, in which case the indicated test is
initiated.
When read, this object always returns the most recent
value that bbSeltTestType was set to. If it has not been
set since the last initialization of the network
management subsystem on the agent, a value of noTest
is returned. |
| INT bbSeltTestResult | 1.3.6.1.4.1.193.72.602.10.5.1.1.4 | INTEGER | read-only | This object contains the result of the most recently
requested test, or the value none(1) if no tests have
been requested since the last reset. Note that this
facility provides no provision for saving the results
of one test when starting another, as could be
required if used by multiple managers concurrently. |
| OCT bbSeltTestResultDetails | 1.3.6.1.4.1.193.72.602.10.5.1.1.5 | OCTET STRING | read-only | This object contains a comment-string, which gives more
specific information about the test result. For instance, after
a failed test a comment will describe the reason of the fault.
The comment that the agent will be able to send towards the manager
is listed below.
1) When the bbSeltTestResult value is 'success(2)', the comment-string
will be 'No Errors'.
2) Instead, when the bbSeltTestResult value is different from 'success(2)',
then the comment-string will be one of these slogans: 'Off-Hook Detected',
'Stop-test Forced','Line Busy','Ownership Error - Line notInUse',
'Operational Status already in-testing','Test Type not supported',
'Surveillance Timer Expired','DVP Error','Received Unexpected DVP Event'. |
| STR bbSeltTestOwner | 1.3.6.1.4.1.193.72.602.10.5.1.1.6 | OwnerString | read-write | The entity, which currently has the 'ownership'
required to invoke a test on this line. For instance,
it could be the IP address of the manager-station or
the IP line-card (to handle the test only on one line
at the time). |
| INT bbSeltTestAbort | 1.3.6.1.4.1.193.72.602.10.5.1.1.7 | INTEGER | read-write | This object indicates whether or not the owner manager
requires the 'abort' of the sub-tests current set on
the line where the test is running. A writing to this
object is only successful when it changes its value
from 'none(0)' to 'abort(2)'. After completion of
abort request, the agent resets the value back to
'none(0)'. |
| bbSeltEchoGroup | 1.3.6.1.4.1.193.72.602.10.10 | | | |
| bbSeltEchoInputTable | 1.3.6.1.4.1.193.72.602.10.10.1 | | not-accessible | This table provides the input parameters for the Extended NB SELT test |
| bbSeltEchoInputEntry | 1.3.6.1.4.1.193.72.602.10.10.1.1 | | not-accessible | An entry contains input parameters for the SELT test for the subscriber line
identified by ifIndex. |
| INT bbSeltEchoMeasLength | 1.3.6.1.4.1.193.72.602.10.10.1.1.1 | INTEGER | read-write | This parameter controls the duration of the echo measurement.
The measurment is performed over a period equal to 2^measurmentLength DMT
signals (without the cyclic prefix, i.e. with a duration equal to
1/4321.5 seconds = 231.4 microseconds).
A value of 12 corresponds approximately to one second. |
| bbSeltEchoOutputTable | 1.3.6.1.4.1.193.72.602.10.10.2 | | not-accessible | This table provides the output parameters for the Extended NB SELT test |
| bbSeltEchoOutputEntry | 1.3.6.1.4.1.193.72.602.10.10.2.1 | | not-accessible | An entry contains Output parameters for
the SELT test for the subscriber line
identified by ifIndex. |
| OCT bbSeltEchoVec0 | 1.3.6.1.4.1.193.72.602.10.10.2.1.1 | OCTET STRING | read-only | Part 0 (0-63) of BB-SELT echo vector. |
| OCT bbSeltEchoVec1 | 1.3.6.1.4.1.193.72.602.10.10.2.1.2 | OCTET STRING | read-only | Part 1 (64-127) of BB-SELT echo vector. |
| OCT bbSeltEchoVec2 | 1.3.6.1.4.1.193.72.602.10.10.2.1.3 | OCTET STRING | read-only | Part 2 (128..191) of BB-SELT echo vector. |
| OCT bbSeltEchoVec3 | 1.3.6.1.4.1.193.72.602.10.10.2.1.4 | OCTET STRING | read-only | Part 3 (192..255) of BB-SELT echo vector. |
| OCT bbSeltEchoVec4 | 1.3.6.1.4.1.193.72.602.10.10.2.1.5 | OCTET STRING | read-only | Part 4 (256-319) of BB-SELT echo vector. |
| OCT bbSeltEchoVec5 | 1.3.6.1.4.1.193.72.602.10.10.2.1.6 | OCTET STRING | read-only | Part 5 (320-383) of BB-SELT echo vector. |
| OCT bbSeltEchoVec6 | 1.3.6.1.4.1.193.72.602.10.10.2.1.7 | OCTET STRING | read-only | Part 6 (384-447) of BB-SELT echo vector. |
| OCT bbSeltEchoVec7 | 1.3.6.1.4.1.193.72.602.10.10.2.1.8 | OCTET STRING | read-only | Part 7 (448-512) of BB-SELT echo vector. |
| INT bbSeltAgcValue | 1.3.6.1.4.1.193.72.602.10.10.2.1.9 | INTEGER | read-only | Receiver gain used during last BB-SELT echo measurement. |
| bbSeltNoiseGroup | 1.3.6.1.4.1.193.72.602.10.15 | | | |
| bbSeltNoiseInputTable | 1.3.6.1.4.1.193.72.602.10.15.1 | | not-accessible | This table provides the input parameters for the BB SELT Noise test |
| bbSeltNoiseInputEntry | 1.3.6.1.4.1.193.72.602.10.15.1.1 | | not-accessible | An entry contains input parameters for the SELT for the
subscriber line identified by ifIndex. |
| INT bbSeltNoiseMeasLength | 1.3.6.1.4.1.193.72.602.10.15.1.1.1 | INTEGER | read-write | This parameter controls the duration of the noise measurement.
The measurment is performed over a period equal to 2^measurmentLength DMT
signals (without the cyclic prefix, i.e. with a duration equal to
1/4321.5 seconds = 231.4 microseconds).
A value of 12 corresponds approximately to one second. |
| bbSeltNoiseOutputTable | 1.3.6.1.4.1.193.72.602.10.15.2 | | not-accessible | This table provides the output parameters for the BB SELT Noise test |
| bbSeltNoiseOutputEntry | 1.3.6.1.4.1.193.72.602.10.15.2.1 | | not-accessible | An entry contains output parameters for the SELT for the
subscriber line identified by ifIndex. |
| OCT bbSeltPeakNoise | 1.3.6.1.4.1.193.72.602.10.15.2.1.1 | OCTET STRING | read-only | Peak PSD from tone [0-63] observed over the testDuration.
Unit is 1/256 dBm/tonebin and is referred to 100 ohm line. |
| OCT bbSeltTotalNoise | 1.3.6.1.4.1.193.72.602.10.15.2.1.2 | OCTET STRING | read-only | Total PSD from tone [0-63] observed over the testDuration.
Unit is 1/256 dBm/tonebin and is referred to 100 ohm line. |
| OCT bbSeltSignalNoise | 1.3.6.1.4.1.193.72.602.10.15.2.1.3 | OCTET STRING | read-only | Signal PSD from tone [0-63] observed over the testDuration.
Unit is 1/256 dBm/tonebin and is referred to 100 ohm line. |
| bbSeltNotificationGroup | 1.3.6.1.4.1.193.72.602.10.100 | | | |
| bbSeltNotificationTypes | 1.3.6.1.4.1.193.72.602.10.100.0 | | | |
| NTF bbSeltCompletion | 1.3.6.1.4.1.193.72.602.10.100.0.1 | | | When a test is ready an ifTestCompletion trap is sent to
the Manager / Trap Receiver.
Parameters:
1: Managed object class MSAN Port
2: Managed object ID MAC + PortNo
3: Sequence number alarm sequence number
4: Perceived severity warning
5: Event time timestamp retrieved from SNTP server
6: Event type equipment
7: Probable cause other(255)
timeoutExpired(165)
softwareError(164)
unexpectedInformation(303)
corruptedData(153)
8: Result of most recent test
success(2)
notSupported(4)
unAbleToRun(5)
aborted(6)
failed(7)
9: Type of test performed
bbSeltEchoTest
bbSeltNoiseTest |
| bbSeltNotificationParameters | 1.3.6.1.4.1.193.72.602.10.100.1 | | | |
