ZHONE-CARD-DIAGNOSTICS-MIB: View SNMP OID List / Download MIB

Augment table of the unit/card resource but specific to the diagnostic results information. This card contains the index to create diagnostics table entries (zhoneCardDiagEntry) which contains all the data for executing and obtaining diagnostic results.

This is the card diagnostics next index table which contains all the data for: - index for creating next zhoneCardDiagEntry.

We allow ten diagnostic requests from multiple interfaces. The diagNextIndex represents the next available diagnostic request handle for requesting a diagnostic. NOTE: this operates as a wrap-around counter starting at 1 and wrapping around to 1 after reaching 10.

Augment table of the unit/card resource but specific to the diagnostic results information. This is the card diagnostics table which contains all the data for executing and obtaining diagnostic results.

This is the card diagnostics table which contains all the data for: - invoking diagnostics, - obtaining diagnostic results.

We allow ten diagnostic requests from multiple interfaces. The diagIndex represents the diagnostic request to start a diagnostic or obtain test results for a completed diagnostic. NOTE: this operates as a wrap-around counter starting at 1 and wrapping around to 1 after reaching 10.

This field specifies the diagnostic to execute. The default value is 'selftest'. NOTE: not all of the individual diagnostics are available on every Zhone card type. NOTE: Zhone card types (cardZhoneType) are defined in the genCardResources.mib List of possible diagnostics: ============================ Common to all PLS cards ----------------------- selftest(1) - this diagnostic will execute all of the individual tests available on this card. Supports: diagStart, diagStop, diagRepetition. cardEEprom(3) - this diagnostic will verify the main card EEPROM checksum. Supports: diagStart, diagStop, diagRepetition. frbus(4) - this diagnostic will verify that the BAN slot card can access the Fhrame Bus by doing a loopback with 10 message of 100 bytes. Supports: diagStart, diagStop, diagRepetition. backPlane(12) - this diagnostic will verify that the BAN slot card can access the back plane by verifying the back plane EEPROM checksum. Supports: diagStart, diagStop, diagRepetition. cardZhoneType::infoServices(3) specific --------------------------------------- supvBus(2) - this diagnostic will verify that the BAN slot card can access the supervisory Bus by doing a loopback of 20 bytes. Supports: diagStart, diagStop, diagRepetition. pcmcia(5) - this diagnostic will verify that the InfoServ card can access the PCMCIA flash card I/O by doing a file create, write, and read of length 4000 bytes. Supports: diagStart, diagStop, diagRepetition. shelfLamp(6) - this diagnostic will illuminate the shelf alarm indicators for a period of 1.5 seconds. The indicators will return to their original settings after the diagnostic completes. Supports: diagStart, diagStop, diagRepetition. realTimeClk(7) - this diagnostic will verify that the real time clock increments. Supports: diagStart, diagStop, diagRepetition. fanTray(8) - this diagnostic tests that the fan tray is operational by verifying the fan tray EEPROM checksum. Supports: diagStart, diagStop, diagRepetition. shelfMonitor(9) - this diagnostic tests the shelf monitor board is operational by checking the POST status register and verifying the shelf monitor board EEPROM checksum. Supports: diagStart, diagStop, diagRepetition. midPlane(13) - this diagnostic will verify that the mid plane card is present by verifying the mid plane card EEPROM checksum. Supports: diagStart, diagStop, diagRepetition. cardZhoneType::vasp(5) specific --------------------------------- ioCard(10) - this diagnostic will verify that the I/O card is present by verifying the I/O card EEPROM checksum. Supports: diagStart, diagStop, diagRepetition. mezzanineCard(11) - this diagnostic will test that the mezzanine card is operational by verifying the mezzanine card EEPROM checksum. Supports: diagStart, diagStop, diagRepetition. cardZhoneType::t3Tdm(6) specific --------------------------------- ioCard(10) - this diagnostic will verify that the I/O card is present by verifying the I/O card EEPROM checksum. Supports: diagStart, diagStop, diagRepetition. midPlane(13) - this diagnostic will verify that the mid plane card is present by verifying the mid plane card EEPROM checksum. Supports: diagStart, diagStop, diagRepetition. cardZhoneType::ethernet(9) specific ----------------------------------- midPlane(13) - this diagnostic will verify that the mid plane card is present by verifying the mid plane card EEPROM checksum. Supports: diagStart, diagStop, diagRepetition. cardZhoneType::hdsl2(10) specific --------------------------------- ioCard(10) - this diagnostic will verify that the I/O card is present by verifying the I/O card EEPROM checksum. Supports: diagStart, diagStop, diagRepetition. mezzanineCard(11) - this diagnostic will test that the mezzanine card is operational by verifying the mezzanine card EEPROM checksum. Supports: diagStart, diagStop, diagRepetition. Enumeration: 'ioCard': 10, 'shelfMonitor': 9, 'mezzanineCard': 11, 'shelfLamp': 6, 'frbus': 4, 'cardEEprom': 3, 'backPlane': 12, 'selftest': 1, 'supvBus': 2, 'fanTray': 8, 'realTimeClock': 7, 'pcmcia': 5, 'midPlane': 13.

The diagAction field represents the diagnostic operation to execute. Current supported actions are as follows: diagStart : begin diagnostics and initialize results. diagStop : stop diagnostics if not yet complete. diagSuspend: suspend diagnostics at current point. diagResume : resume diagnostics from point of suspension.

This field specifies the number of repetitions of diagnostics to execute. The default value is 1. NOTE: this field operates as an OR with the diagDuration field. If this field is set to non-zero then the diagnostics will be executed that amount of repetitions.

This field specifies the duration of diagnostics to execute. The default value is 60 seconds. NOTE: this field operates as an OR with the diagRepetition field. If this field is set to non-zero then the diagnostics will be executed that amount of time.

This represents the overall diagnostic result.

The number of diagnostics that executed successfully.

The number of diagnostics that have failed.

The failure reason, if any, for the last diagnostic which has executed. NOTE: An empty string indicates that no additional information is available.

Starting date and time of last selftest execution.

Ending date and time of last selftest execution.

In any case where a new row can be created either via the cli or zms there will always be a proprietary mib entity of type ZhoneRowStatus which has the basic equivalence of the standard rowstatus object_id.

This table contains one entry for each tac test channel available on Zhone devices. In the initial release only the primary channel (1) is supported. Future line cards may support the second channel. If the second channel is supported the row will be populated, if the second channel is not supported a get will return no such instance.

One row per tac test channel.

This field is the index field for the tac test channel which will be connected on the external port. This device supports a maximum of two channels, one or both channels may be supported by a device depending on which lines cards are installed.

This field contains the InterfaceIndex of the physical line to be tested. If no line is currently being tested this value is 0. The ability of a physical line type to support tac test may vary depending on the line cards installed and the external test equipment. This field may not be modified when an tac test is in progress as indicated by a non-zero value in this field and the test mode set to one of tacModeLookIn, tacModeLookOut or tacModeBridge

This field is used to set the mtac test mode for a given line. The options are: mtacModeBridge - All traffic on the given line is bridged across the mtac lines mtacModeLookIn - All outbound traffic on the given line originates exclusively to the mtac lines mtacModeLookIn - All inbound traffic on the given line originates exclusively to the mtac lines mtacModeNone - No mtac test is in progress. The mtac test mode may be changed only if the zhoneInterfaceIndex is set, Otherwise it defaults to mtacModeNone. And can be changed again by setting InterfaceIndex to non-zero values. Enumeration: 'mtacModeNone': 4, 'mtacModeLookOut': 3, 'mtacModeBridge': 1, 'mtacModeLookIn': 2.

This object is only valid for Tac Cards which support the new Legerity Suite of tests. This object identifies which test is to be run, or can be set to abort the current test. Test results are sent to the zhoneTacTestResultsTable. There are 3 Legerity software packages: Basic Test (VCP-BT), Advanced Test (VCP-AT), and Advanced Test Plus (VCP-ATP). We currently support Basic Test package. The following lists which tests are supported in each software package. Calibration VCP-ATP Foreign DC Voltage Test VCP-BT, VCP-AT, VCP-ATP Foreign AC VoltageTest VCP-BT, VCP-AT, VCP-ATP DC Loop Resistance Test VCP-BT, VCP-AT, VCP-ATP Three-Element Insulation Resistance Test VCP-BT, VCP-AT, VCP-ATP Five-Element Insulation Resistance Test VCP-ATP Three-Element Capacitance Test VCP-BT, VCP-AT Receiver Off-Hook Test VCP-BT, VCP-AT, VCP-ATP Distance to Open Test VCP-BT, VCP-AT Foreign AC Currents Test VCP-BT, VCP-AT Ringer Equivalency Number Test VCP-BT, VCP-AT, VCP-ATP DTMF and Pulse Digit Measurement Test VCP-BT, VCP-AT Noise Measurement Test VCP-BT, VCP-AT, VCP-ATP Signal to Noise Ratio Test VCP-ATP Arbitrary Single Tone Measurement Test VCP-ATP Tone Generation Test VCP-BT, VCP-AT Trans-Hybrid Loss Test VCP-BT, VCP-AT, VCP-ATP Draw and Break Dial Tone Test VCP-BT, VCP-AT Inward Current Test VCP-ATP DC Feed Self-Test VCP-BT, VCP-AT, VCP-ATP On/Off Hook Self-Test VCP-BT, VCP-AT, VCP-ATP Ringing Self-Test VCP-BT, VCP-AT, VCP-ATP Ringing Monitor Test VCP-BT, VCP-AT, VCP-ATP Metering Self-Test VCP-BT, VCP-AT Transmission Self-Test VCP-BT, VCP-AT, VCP-ATP Dialing Sef Test VCP-BT, VCP-AT Howler Test VCP-BT, VCP-AT Fuse Test VCP-ATP Read Loop and Battery Conditions VCP-BT, VCP-AT, VCP-ATP Enumeration: 'howlerTest': 30, 'arbitrarySignalToneMeasurement': 18, 'ringingMonitor': 26, 'inwardCurrent': 22, 'threeElementInsulationResistance': 8, 'foreignACVoltage': 6, 'fuseTest': 31, 'readLoopAndBatteryConditions': 32, 'transmissionSelfTest': 28, 'calibration': 4, 'distanceToOpen': 12, 'onAndOffHookSelfTest': 24, 'abortTest': 3, 'receiverOffHook': 11, 'transHybridLoss': 20, 'foreignDCVoltage': 5, 'dtmfAndPulseDigitMeasurement': 15, 'drawAndBreakDialTone': 21, 'meteringSelfTest': 27, 'fiveElementInsulationResistance': 9, 'signalToNoiseRatio': 17, 'dcFeedSelf': 23, 'ringingSelfTest': 25, 'runAllTests': 2, 'threeElementCapacitance': 10, 'foreignACCurrents': 13, 'ringerEquivalencyNumber': 14, 'none': 1, 'dcLoopResistance': 7, 'dialingSelfTest': 29, 'toneGeneration': 19, 'noiseMeasurement': 16.

Optional Test Parameter #1

Optional Test Paramerter #2

Optional Test Parameter #3

Optional Test Parameter #4

Optional Test Parameter #5 Value: 0x00000001 Force Line-Test mode

Table of Tac Test Results objects. Indexed by same index as zhoneTacTestTable. This table is only valid for Tac cards which support the Legerity Suite of tests.

Entry of Test Results objects. Indexed by same index as zhoneTacTestEntry. This entry is only valid for Tac cards which support the Legerity Suite of tests.

Description.

Description.

Contains test results. Enumeration: 'testInProgress': 2, 'testNotSupported': 5, 'testNotStarted': 1, 'testCompleted': 3, 'testAborted': 4.

For Legerity Test Suite, results of test(s) are output to this object as one string, separated by UNIX '/n' for newline characters and terminated by the NULL character. This test results will persist until the next test is run or until tac card reboot.

Traps for the tac system.

Traps associated with ring generator. Traps should be added below - the .0 on this entry is required.

This trap occurs when a ring signal fails to be detected, or when it re-starts after failure.

This trap occurs when a fault in the ringer power bus is detected. Such fault may be caused by the possible shortage in the POTS or DSL line.

Contains the diagnostics and results available on a per card or resource basis.

This group contains objects associated with Zhone Card Diagnostics

This group contains objects associated with initiating tac tests