Fred Oliver
2008-Dec-11 22:40 UTC
[crossbow-discuss] interface shutdowns after receiving vlan packet?
I have a Sun X2200 running nv103 plus an L2 filtering BFU (including crossbow from 11/29). Freshly booted, no filter rules, no vnics, no vlans, only bge1 with a default configuration:> bge1: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 6 > inet 192.168.2.16 netmask fffffe00 broadcast 192.168.3.255 > ether 0:16:36:8e:e:f1Several times today, a few minutes after reboot, the system has stopped responding to network traffic. If I unplumb and replumb bge1, traffic returns. (If I don''t, then a few minutes later the service processor also stops responding, so I have to power cycle the system.) I''ve run snoop on the console while pinging this system from another. When ping stops responding I look at the snoop output. The three times I''ve tried this procedure, the last packet is always a (gratuitous?) ARP on a vlan:> 15 0.84427 VLAN#42: OLD-BROADCAST -> (broadcast) ARP C Who is 192.168.123.29, 192.168.123.29 ?The sending system runs nv101a, and is likely the only system on the subnet plumbed for a vlan. Any clues what''s going wrong? Fred Oliver
Fred Oliver
2008-Dec-12 19:36 UTC
[crossbow-discuss] interface shutdowns after receiving vlan packet?
After further testing, this seems to be a problem with the L2 filter BFU. The problem is not reproducing with the plain crossbow download BFU. Fred Fred Oliver wrote:> I have a Sun X2200 running nv103 plus an L2 filtering BFU (including > crossbow from 11/29). Freshly booted, no filter rules, no vnics, no > vlans, only bge1 with a default configuration: > >> bge1: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 6 >> inet 192.168.2.16 netmask fffffe00 broadcast 192.168.3.255 >> ether 0:16:36:8e:e:f1 > > Several times today, a few minutes after reboot, the system has stopped > responding to network traffic. If I unplumb and replumb bge1, traffic > returns. (If I don''t, then a few minutes later the service processor > also stops responding, so I have to power cycle the system.) > > I''ve run snoop on the console while pinging this system from another. > When ping stops responding I look at the snoop output. The three times > I''ve tried this procedure, the last packet is always a (gratuitous?) ARP > on a vlan: > >> 15 0.84427 VLAN#42: OLD-BROADCAST -> (broadcast) ARP C Who is 192.168.123.29, 192.168.123.29 ? > > The sending system runs nv101a, and is likely the only system on the > subnet plumbed for a vlan. > > Any clues what''s going wrong? > > Fred Oliver > _______________________________________________ > crossbow-discuss mailing list > crossbow-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/crossbow-discuss
Zhijun Fu
2008-Dec-15 06:45 UTC
[crossbow-discuss] interface shutdowns after receiving vlan packet?
Fred, Can this be reproduced on other machines as well? Or could I access your test systems to take a look what''s happening there? The issue sounds weird to me. I just bfu''ed two of my machines to that particular build, with debug and non-debug bits respectively, and wasn''t able to reproduce the issue you mentioned. Thanks, Zhijun Fred Oliver wrote:> After further testing, this seems to be a problem with the L2 filter > BFU. The problem is not reproducing with the plain crossbow download BFU. > > Fred > > Fred Oliver wrote: > >> I have a Sun X2200 running nv103 plus an L2 filtering BFU (including >> crossbow from 11/29). Freshly booted, no filter rules, no vnics, no >> vlans, only bge1 with a default configuration: >> >> >>> bge1: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 6 >>> inet 192.168.2.16 netmask fffffe00 broadcast 192.168.3.255 >>> ether 0:16:36:8e:e:f1 >>> >> Several times today, a few minutes after reboot, the system has stopped >> responding to network traffic. If I unplumb and replumb bge1, traffic >> returns. (If I don''t, then a few minutes later the service processor >> also stops responding, so I have to power cycle the system.) >> >> I''ve run snoop on the console while pinging this system from another. >> When ping stops responding I look at the snoop output. The three times >> I''ve tried this procedure, the last packet is always a (gratuitous?) ARP >> on a vlan: >> >> >>> 15 0.84427 VLAN#42: OLD-BROADCAST -> (broadcast) ARP C Who is 192.168.123.29, 192.168.123.29 ? >>> >> The sending system runs nv101a, and is likely the only system on the >> subnet plumbed for a vlan. >> >> Any clues what''s going wrong? >> >> Fred Oliver >> _______________________________________________ >> crossbow-discuss mailing list >> crossbow-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/crossbow-discuss >> > _______________________________________________ > crossbow-discuss mailing list > crossbow-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/crossbow-discuss >-- #mdb -K [0]> eri.prc.sun.com::walk staff s|::print staff_t s_name| ::grep .== zhijun |::eval <s=K|::print staff_t Zhijun.Fu at Sun.COM, x84349 Network Virtualization & Performance Team, Solaris Core Operating Systems Since Jul 10,2006 [0]> :c -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/crossbow-discuss/attachments/20081215/b220dffb/attachment.html>