Paradyne Hotwire 8620 - Manual (Page 58)

1. Network Management Specification
52 June 2003 8000-A2-GB30-00
6.5 ATM Loopback
pdnATMfM4VcLoopbackTestTable in pdn_atmM4Ext.mib is supported to provide detailed
test results on ATM F5 loopback test. This tabular object augments atmfM4VcTestTable
(see Section 3.15).
In order to distinguish a single-cell loopback test from a multi-cell loopback test, In
addition to ATM Forum M4 Test Types atmfM4VcTestOAMLoopbackSeg and
atmfM4VcTestOAMLoopbackE2E, which indicate a single-cell loopback test, two new
test commands pdnATMfM4TestOAMLoopbackSegMultiCell and
pdnATMfM4VcTestOAMloopbackE2EMultiCell are defined to stop but not dealloc the
ATM F5 loopback test resource (such as result).
In order to initiate an ATM F5 Segment loopback test, an NMS must first obtain
‘ownership’ of the entry in the atmfM4VcTestTable for the VCC or VCL to be tested. This
is accomplished with atmfM4VcTestId and atmfM4VcTestStatus object as follows:
try_again:
get (atmfM4VcTestId, atmfM4VcTestStatus)
while (atmfM4TestStatus != notInUse)
/* Loop while a test is running or some other
* manager is configuring a test.
*/
short delay
pdnATMVclCurrEntry
(pdn_ATMStats.mib)
Yes
pdnATMVclCurrElapsedTime Gauge32 Read-Only
pdnATMVclCurrTotalCellIns Gauge32 Read-Only
pdnATMVclCurrTotalInDiscards Gauge32 n
pdnATMVclCurrTotalCellOuts Gauge32 Read-Only
pdnATMVclCurrTotalOutDiscards Gauge32 Read-Only
pdnATMVclHistEntry
(pdn_ATMStats.mib)
pdnATMVclHistIndex INTEGER Read-Only
pdnATMVclHistElapsedTime TimeInterval Read-Only
pdnATMVclHistTotalCellIns Gauge32 Read-Only
pdnATMVclHistTotalInDiscards Gauge32 n
pdnATMVclHistTotalCellOuts Gauge32 Read-Only
pdnATMVclHistTotalOutDiscards Gauge32 Read-Only
Table 1-56. Paradyne Extensions to ATM MIBs (2 of 2)
Table Object Type
Sup-
ported
Table 1-57. ATM Loopback
Table Comments
pdnATMfM4VcLoopbackTestEntry Supported as is