Hello,
How cable-diagnostic behaves when the test cable-diagnostic is performed on a ethernet interface connected to a 100Mbit Full-Duplex (eventually with PoE) [*] host or a 100Mbit Half-Duplex [**] host?
I admit I've to diagnose if those host types are correctly set by using the Auto-Sensing...but, apart from that, I want to know if test cable-diagnostic results can differ if the cable's end is connected to hosts behaving differently (100FDx vs 100HDx vs 1000FDx).
[*] such as a DECT-IP Base Station (as per Auto-Sensing)
I observe this:
Aruba(config)# test cable-diagnostics ethernet 1
This command will cause a loss of link on all tested ports and will take
several seconds per port to complete. Use the 'show cable-diagnostics'
command to view the results.
Continue (y/n)? y
Aruba(config)# test cable-diagnostics ethernet 2
This command will cause a loss of link on all tested ports and will take
several seconds per port to complete. Use the 'show cable-diagnostics'
command to view the results.
Continue (y/n)? y
Aruba(config)# test cable-diagnostics ethernet 3
This command will cause a loss of link on all tested ports and will take
several seconds per port to complete. Use the 'show cable-diagnostics'
command to view the results.
Continue (y/n)? y
Aruba(config)# show cable-diagnostics ethernet 1
Cable Diagnostic Status - Copper Ports
MDI Cable Cable Length or
Port Pair Status Distance to Fault
---- ------ ----------- ---------------------
1 1-2 OK 33m
3-6 OK 38m
4-5 Short 31m
7-8 Short 32m
Aruba(config)# show cable-diagnostics ethernet 2
Cable Diagnostic Status - Copper Ports
MDI Cable Cable Length or
Port Pair Status Distance to Fault
---- ------ ----------- ---------------------
2 1-2 OK 51m
3-6 OK 51m
4-5 Open 1m
7-8 Short 53m
Aruba(config)# show cable-diagnostics ethernet 3
Cable Diagnostic Status - Copper Ports
MDI Cable Cable Length or
Port Pair Status Distance to Fault
---- ------ ----------- ---------------------
3 1-2 OK 31m
3-6 OK 36m
4-5 Short 34m
7-8 Short 34m
Aruba(config)# show interfaces status
Port Name Status Config-mode Speed Type Tagged Untagged
-------- ---------- ------- ------------- -------- ---------- ------ --------
1 DECT-IP... Up Auto 100FDx 100/1000T No 1000
2 DECT-IP... Up Auto 100FDx 100/1000T No 1000
3 DECT-IP... Up Auto 100FDx 100/1000T No 1000
Aruba(config)# show interfaces
Status and Counters - Port Counters
Flow Bcast
Port Total Bytes Total Frames Errors Rx Drops Tx Ctrl Limit
------------ -------------- -------------- --------- --------- ---- -----
1 26,397,080 401,898 0 0 off 0
2 26,444,482 402,386 0 0 off 0
3 26,359,582 401,525 0 0 off 0
As you note on all three ports (Spectralink DECT IP Base Station working at 100Mbps Full-Duplex) pair 7-8 results as "Short"...but on Port 2 pair 4-5 is "Open" while the very same pair on Port 1 and 3 results "Short"...so, in the end, is "Short" on 4-5 and 7-8 normal for 100Mbps Full-Duplex and "Open" means that our port 2 connected Spectralink DECT IP Base Station has a real problem?
[**] such as a Label Printer (as per Auto-Sensing)