Support #423
omf.nicta.node34's exp0 not connected
| Status: | Closed | Start date: | 16/09/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Rodney Berriman | % Done: | 100% |
|
| Category: | Testbed maintenance | |||
| Target version: | - |
Description
Similar to #422 (I'm starting to suspect my images again...). Could someone check node34's exp0 ethernet cable? It doesn't appear to be connected.
2: exp0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:00:00:00:a6:42 brd ff:ff:ff:ff:ff:ff
inet 10.42.0.34/16 brd 10.42.255.255 scope global exp0
History
Updated by Christoph Dwertmann over 1 year ago
- Status changed from New to Assigned
- Assignee set to Christoph Dwertmann
Auto-negotiation issue, possibly a broken cable. Rodney's looking into it.
Updated by Rodney Berriman over 1 year ago
Helpline entered for Aun to locate faults with reflectometer.
2 cables are faulty somewhere between the box and the switch.
F5-1-P21-22 which runs to the switch in L5 comms room, labelled "Tempo L5-1" port 12
F5-1-P21-23 which runs to the switch in L5 comms room, labelled "Tempo L5-1" port 20
Updated by Rodney Berriman over 1 year ago
- Assignee changed from Christoph Dwertmann to Rodney Berriman
Updated by Rodney Berriman 11 months ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Repaired by Anthony.
All 3 cables tested OK.