[Lerftest-ctrls] Issue with LLRF-CPU networking
Sonya Hoobler
sonya at slac.stanford.edu
Wed Sep 12 17:15:06 EDT 2018
Hi Hugo,
Thanks for your reply.
> - Is this also happening to the other CPU?
I can't say for sure because we have not used that CPU as much. I will
keep an eye out for it.
> - Can you send the output of ifconfig -a before the issue and after it happens?
Yes, pasted below.
> - Was any board added to the cpu?
No.
Here's the console output:
# ifconfig
eth1 Link encap:Ethernet HWaddr 74:FE:48:28:BC:6F
inet addr:192.168.1.31 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::76fe:48ff:fe28:bc6f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:458 errors:0 dropped:0 overruns:0 frame:0
TX packets:330 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:37974 (37.0 KiB) TX bytes:30524 (29.8 KiB)
Memory:fbc40000-fbc5ffff
eth4 Link encap:Ethernet HWaddr 74:FE:48:28:BC:73
inet addr:129.57.244.50 Bcast:129.57.244.255 Mask:255.255.255.0
inet6 addr: fe80::76fe:48ff:fe28:bc73/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:204696 errors:0 dropped:0 overruns:0 frame:0
TX packets:87614 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:151125119 (144.1 MiB) TX bytes:58701018 (55.9 MiB)
Memory:fbb00000-fbb7ffff
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:2565 errors:0 dropped:0 overruns:0 frame:0
TX packets:2565 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:112828 (110.1 KiB) TX bytes:112828 (110.1 KiB)
# ifconfig eth0 192.168.0.31
[ 4317.679571] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
# [ 4321.134743] igb 0000:06:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps
Full Duplex, Flow Control: RX/TX
[ 4321.145309] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
# ifconfig
eth0 Link encap:Ethernet HWaddr 74:FE:48:28:BC:6E
inet addr:192.168.0.31 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::76fe:48ff:fe28:bc6e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1039 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:43950 (42.9 KiB)
Memory:fbc60000-fbc7ffff
eth1 Link encap:Ethernet HWaddr 74:FE:48:28:BC:6F
inet addr:192.168.1.31 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::76fe:48ff:fe28:bc6f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:498 errors:0 dropped:0 overruns:0 frame:0
TX packets:355 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:41010 (40.0 KiB) TX bytes:32294 (31.5 KiB)
Memory:fbc40000-fbc5ffff
eth4 Link encap:Ethernet HWaddr 74:FE:48:28:BC:73
inet addr:129.57.244.50 Bcast:129.57.244.255 Mask:255.255.255.0
inet6 addr: fe80::76fe:48ff:fe28:bc73/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:221120 errors:0 dropped:0 overruns:0 frame:0
TX packets:93130 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:163125857 (155.5 MiB) TX bytes:62840378 (59.9 MiB)
Memory:fbb00000-fbb7ffff
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:3471 errors:0 dropped:0 overruns:0 frame:0
TX packets:3471 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:188468 (184.0 KiB) TX bytes:188468 (184.0 KiB)
Thanks again,
Sonya
On Wed, 12 Sep 2018, Slepicka, Hugo Henrique wrote:
> Hi,
>
> I personally never saw this behavior.
> Looping Ernest and Thuy too so they can also contribute on this case.
>
> *Larry and Sonya*:
> - Is this also happening to the other CPU?
> - Can you send the output of ifconfig -a before the issue and after it happens?
> - Was any board added to the cpu?
>
> Thank you,
> Hugo
>
>
> On 9/12/18, 1:23 PM, "Lerftest-ctrls on behalf of Sonya Hoobler" <lerftest-ctrls-bounces at jlab.org on behalf of sonya at slac.stanford.edu> wrote:
>
> Hi again,
>
> Larry called and repoted that the interface seemed to be down again and,
> indeed, eth0 no longer appeared in ifconfig.
>
> *Larry*, do you know if anything was power-cycled or disconnected before
> you found the problem? That info would help for our troubleshooting.
>
> *Hugo*, have you encountered this before? This is not the first time I've
> found eth0 missing for these systems, but since I'm remote and not fully
> aware of what is happening locally, I have not yet tried to troubleshoot
> it.
>
> Thanks everyone,
> Sonya
>
>
>
> On Wed, 12 Sep 2018, Sonya Hoobler wrote:
>
> > Hi Wesley,
> >
> > The ifconfig eth0 was not set (which is odd but I believe I have seen this
> > before). I have set it and it should be working now.
> >
> > Sonya
> >
> >
> > On Wed, 12 Sep 2018, Wesley Moore wrote:
> >
> >> Sonya,
> >>
> >>
> >> Larry is seeing a comm issue from lcls-llrfcpu01 to the rack's switch.
> >> Port 1 on the cpu appears inactive/dead (pic 1). This results in the
> >> uplink in the rack being down (pic 2). Larry moved from Port 1 to another
> >> port up and saw the uplink briefly. So it's believed that everything
> >> downstream of cpu01 is fine. Please advise.
> >>
> >>
> >> # pic 1: lcls-llrfcpu01, port 1 inactive.
> >>
> >> [cid:1ffd57f5-4469-41d5-885a-0ba16ff448a9]
> >>
> >>
> >> # pic 2: LLRF rack switch, all lights on left are solid, uplink on
> >> far-right is inactive.
> >>
> >> [cid:7cd84393-99e7-4dab-a88d-8bedc95f7115]
> >>
> >>
> >> Wesley
> >>
> >
> _______________________________________________
> Mailing List: Lerftest-ctrls at jlab.org
> https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls
> Wiki: https://wiki.jlab.org/lerf/index.php/Network
>
>
>
More information about the Lerftest-ctrls
mailing list