Customer Service Center
Home
Knowledge Base
Contact Support
License Activation
|
Contact Support
|
License Activation
|
Spirent KB Article
Doc ID: FAQ18055
Printer Friendly
Email Article Link
Lumos / STCLive 7561 Probe: Why does REPT-DIAG fail with "FAIL - FAILED LOOPBACK TEST" on some 7561 probe?
Environment/Versions
Lumos / STCLive 7561 Probe
Answer
Example of the REPT-DIAG fail message:
;rept-diag:::asdf;
OK 0
7561-PROBE 17-07-27 15:57:04
M ASDF COMPLD
SELF TEST OUTPUT:
FAIL
MAIN CARD
FAIL - FAILED LOOPBACK TEST
PORT-1: BOTH, 100000/FULL, GTP
HARD DRIVE
PASS
There are a few different reasons this may occur.
In releases prior to 11.50.15, there was an intermittent defect that caused the problem. The intermittent issue is resolved in release 11.50.15 and later.
In releases prior to 12.00.10, there is a defect where the error will be reported if the "DEFUID" setting in RTRV-ATTR-IP is not set to at least USER. In release 12.00.10 and later releases, the DEFUID setting can be set to "nologin".
If the probe is not able to communicate with the chassis, the command will fail with the error. An indication the probe is not able to talk to the chassis is with the "RTRV-VRSN-EQPT" command. If the response of the command shows "NA" values for the Chassis components this problem may be happening.
Example:
"APPL-VRSN=RA12.00.01 OS-VRSN=Linux 2.6.32.27-Cavium-Octeon"
"MCH-VRSN=n/a PM-VRSN=n/a MCMC-VRSN=n/a"
"CU1-VRSN=n/a"
"1-EMPTY-VRSN=n/a 2-AMC738-VRSN=n/a"
"3-DA193-VRSN=n/a"
Note: The "
1-EMPTY-VRSN=n/a" is expected and normal. The other components should have actual values.
If this is happening, power down the chassis and reseat the module to attempt to restore communication to the chassis.
The CFP Transceiver is bad or an untested possibly unsupported CFP.
Version
3.0
Publish Date
2018-02-23
Categories
Product : VisionWorks Probe
Related Articles