Tools

Channel Area

Service Product Area

Forum Affairs

Why is the format of cable length tested using the MIB tool different from that of cable length tested using commands in the VCT test

37

You can run the virtual-cable-test command to test the cable length.

system-view
[HUAWEI] interface gigabitethernet 0/0/1
[HUAWEI-GigabitEthernet0/0/1] virtual-cable-test
Warning: The command will stop service for a while, Continue?[Y/N]y
Info: This operation may take a few seconds. Please wait for a moment......done.
Pair A length: 189meter(s)
Pair B length: 189meter(s)
Pair C length: 189meter(s)
Pair D length: 189meter(s)
Pair A state: Ok
Pair B state: Ok
Pair C state: Ok
Pair D state: Ok The lengths displayed in the command output are lengths of several wire pairs and the distance between the local interface and the fault point. The test result is for reference only and does not guarantee the accuracy for network cables produced by all manufacturers.

The length tested using the MIB tool is only a value. The value is the average length of multiple wire pairs.

NOTE:
If the cable length is displayed as Unknown, the cable status is OK, but the cable length test result cannot be used.

Other related questions:

You can run the virtual-cable-test command to test whether a cable is faulty. You can locate and rectify cable faults according to the command output.
-If the cable works properly, the total length of the cable is displayed.
-If the cable is faulty, the distance between the local interface and the fault point is displayed.
The cable length displayed in the VCT test is for reference only.

Command and method used to test I2000 alarms:
Solution:
Caution:
Run the following MML commands:
a. Simulate alarm reporting.
Log in to the MML mode of storage and enter spu ui>sys almsendone 48 6011 1 0,0.
Use command lines to check whether alarms are reported successfully. Then, whether alarms are reported is displayed on the OSM. On the I2000 page, an alarm indicating that the power supply status is abnormal is displayed.
b. Simulate alarm recovery.
Log in to the MML mode of storage and enter spu ui>sys almsendone 48 6011 2 0,0 to check whether the alarm is recovered.
If Print the fault list: is null, the alarm is recovered.