Page MenuHomePhabricator

Broken network connection on ms-be1044 after reboot
Closed, ResolvedPublic

Description

After a reboot for a kernel update, ms-be1044 has no network connectivity, I can see the interface up when logging in over the serial console, but ethtool shows "Link detected: No", maybe the cable died?

Event Timeline

Cmjohnson closed this task as Resolved.Apr 18 2019, 4:50 PM

The cable looks good and appears to be passing traffic, I have a link at the server and shows up on the switch
xe-2/0/8 up up ms-be1044

Steps Taken:
Reseat DAC cable on both ends (switch and server)
Power Cycle Server

The network came back after the power cycle, resolving

PING ms-be1044.eqiad.wmnet (10.64.0.138) 56(84) bytes of data.
64 bytes from ms-be1044.eqiad.wmnet (10.64.0.138): icmp_seq=1 ttl=63 time=0.128 ms
64 bytes from ms-be1044.eqiad.wmnet (10.64.0.138): icmp_seq=2 ttl=63 time=0.112 ms
64 bytes from ms-be1044.eqiad.wmnet (10.64.0.138): icmp_seq=3 ttl=63 time=0.119 ms
64 bytes from ms-be1044.eqiad.wmnet (10.64.0.138): icmp_seq=4 ttl=63 time=0.123 ms
64 bytes from ms-be1044.eqiad.wmnet (10.64.0.138): icmp_seq=5 ttl=63 time=0.159 ms
64 bytes from ms-be1044.eqiad.wmnet (10.64.0.138): icmp_seq=6 ttl=63 time=0.118 ms
64 bytes from ms-be1044.eqiad.wmnet (10.64.0.138): icmp_seq=7 ttl=63 time=0.129 ms
64 bytes from ms-be1044.eqiad.wmnet (10.64.0.138): icmp_seq=8 ttl=63 time=0.124 ms
64 bytes from ms-be1044.eqiad.wmnet (10.64.0.138): icmp_seq=9 ttl=63 time=0.124 ms
64 bytes from ms-be1044.eqiad.wmnet (10.64.0.138): icmp_seq=10 ttl=63 time=0.309 ms
^C

  • ms-be1044.eqiad.wmnet ping statistics ---

10 packets transmitted, 10 received, 0% packet loss, time 9223ms
rtt min/avg/max/mdev = 0.112/0.144/0.309/0.057 ms