# Go back one pageGo to the next page#Go to this book's Index

Test tab

The Test tab allows you to run external and internal loopback tests on the port.


Items Description
External Loopback
Specifies an external loopback test, which requires an external loopback connector. This test changes the AdminStatus of the port to up. The CPU then sends data out the port and expects to see the same data returned. The electronics of the port's data path including the transceiver are tested.
Internal Loopback
Specifies an internal loopback test, which changes the AdminStatus of the port to testing (internal loopback mode). The CPU then sends data to the port, where it is looped back at the PHY. The electronics of the port's data path up to the transceiver are tested.

After the test is stopped, the port AdminStatus stays set to testing, and you must manually change it to up.
Stop
Stops either loopback test.
Result
The result of the most recently run (or current) test:
  • None
  • Success
  • InProgress
  • NotSupported
  • unAbleToRun
  • Aborted
  • Failed

The code contains more specific information on the test result (for example, an error-code after a failed test):
  • NoReceive (timeout on a send)
  • BadSeq (packets received out of sequence)
  • BadLen (packet length mismatch)
  • BadData (packet data mismatch)
Code
This object contains a code that contains more specific information on the test result (for example, an error-code after a failed test). Error codes and other values this object may take are specific to the type of interface and/or test. The value may have the semantics of either the AutonomousType or InstancePointer textual conventions as defined in RFC 1443. The identifier: testCodeUnknown OBJECT IDENTIFIER ::= { 0 0 } is defined for use if no additional result code is available.
PassCount
The number of iterations of the loopback test completed successfully.
FailCount
The number of iterations of the loopback test failed.


Go back one pageGo to the next page##Go to this book's Index