1. Network Management Specification
Table 1-56. Paradyne Extensions to ATM MIBs (2 of 2)
|
|
| Sup- |
Table | Object | Type | ported |
|
|
|
|
pdnATMVclCurrEntry |
|
| Yes |
(pdn_ATMStats.mib) |
|
|
|
pdnATMVclCurrElapsedTime | Gauge32 | ||
|
|
|
|
| pdnATMVclCurrTotalCellIns | Gauge32 | |
|
|
|
|
| pdnATMVclCurrTotalInDiscards | Gauge32 | n |
|
|
|
|
| pdnATMVclCurrTotalCellOuts | Gauge32 | |
|
|
|
|
| pdnATMVclCurrTotalOutDiscards | Gauge32 | |
|
|
|
|
pdnATMVclHistEntry | pdnATMVclHistIndex | INTEGER | |
(pdn_ATMStats.mib) |
|
|
|
pdnATMVclHistElapsedTime | TimeInterval | ||
|
|
|
|
| pdnATMVclHistTotalCellIns | Gauge32 | |
|
|
|
|
| pdnATMVclHistTotalInDiscards | Gauge32 | n |
|
|
|
|
| pdnATMVclHistTotalCellOuts | Gauge32 | |
|
|
|
|
| pdnATMVclHistTotalOutDiscards | Gauge32 | |
|
|
|
|
6.5ATM 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).
Table 1-57. ATM Loopback
Table | Comments |
|
|
pdnATMfM4VcLoopbackTestEntry | Supported as is |
|
|
In order to distinguish a
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
52 | June 2003 |