[f-nsp] IPv6 on MLX stopped working
Jethro R Binks
jethro.binks at strath.ac.uk
Tue Jun 16 03:59:02 EDT 2015
After a long time being spooked by release notes(!), and reviewing the
various conversations about good/bad versions, I went for 5600fb over the
last few days on three core MLXs.
I had high CPU issues in ip_rx on my second MLX after the upgrade where it
was trunked and in metro-rings with the third which hadn't been upgraded,
however when I upgraded that other MLX it all settled down (was previously
running either 5500c or 5300c).
I certainly seem to be over the nasty multicast and snmp problems I was
having, so looking good for me on 5600fb so far.
For reference, here is a summary of the data points gleaned from the
worthy members of this list over the last few months:
5.7c to get X2 hardware support, fixes an SNMP issue
5.6g mid-june ('part of "Target Path"'), fixes DEFECT000541038 concerns
ssh process and causes MP crash and failover on MLX in 5.6f - this issue
also affects 5.7 until 5.7c. There is also a 5.6fb version which has an
ssh process fix.
5.6f reported by one user good for long time, many defects from 5.6e fixed
5.6d is supposed to fix various issues
5.6c has been noted to be buggy
5.6b has been noted to have security issue, and sflow defect fixed in 5.6c
5.5d has been noted to be stable for 5.5.
5.5e reported ipv6/is-is problems DEFECT000500944, fixed in some 5.6
Jethro.
On Mon, 15 Jun 2015, Daniel Schmidt wrote:
> FYI - I'm running 5.6.00fb, they told me I was hitting that but on 05600b
>
> On Mon, Jun 15, 2015 at 12:07 PM, Mike Allen <mkallen at gmail.com> wrote:
>
> > There is actually a quick patch for the SSH bug, use 5.6.00fb. Agreed on
> > the release notes, its a double edged sword. Some people want to know all
> > the bugs, others will use all the bugs as ammo. The reality is everyone
> > has software bugs, the difference is how many they tell you about.
> >
> > Mike
> >
> > On Mon, Jun 15, 2015 at 9:40 AM, Youssef Bengelloun-Zahr <youssef at 720.fr>
> > wrote:
> >
> >> Watch out for 05600f as it is affected by a nasty SSH bug.
> >>
> >> 05600g is due by August 31st.
> >>
> >> Best regards.
> >>
> >>
> >>
> >> > Le 15 juin 2015 à 17:55, Eldon Koyle <
> >> esk-puck.nether.net at esk.cs.usu.edu> a écrit :
> >> >
> >> > 05600b is a pretty early version. I think the latest is 05600f.
> >> >
> >> > I try not no look too closely at release notes, as they can cause
> >> > various undesirable emotions ranging from depression to sheer terror.
> >> >
> >> > --
> >> > Eldon Koyle
> >> >
> >> >> On Jun 15 16:55+0200, "Rolf Hanßen" wrote:
> >> >> Hello,
> >> >>
> >> >> anybody seen such behaviour on a MLX yet?
> >> >> IPv6 stopped working for a ve interface, re-entering the IP solved it.
> >> >> As far as I see this affected only that interface/IP.
> >> >>
> >> >> Ironware: 05600b
> >> >> Cards: NI-MLX-MR with NI-MLX-10Gx4 NI-MLX-10Gx2 NI-MLX-1Gx20-SFP
> >> >>
> >> >> SSH at de-dus-dc2-gw-001#sh run int ve 1359
> >> >> interface ve 1359
> >> >> port-name resolver1
> >> >> ip address x.x.x.x/30
> >> >> ipv6 address XXXX:XXXX:200:5::1/64
> >> >> ipv6 enable
> >> >> ipv6 nd suppress-ra
> >> >>
> >> >> SSH at de-dus-dc2-gw-001#ping ipv6 XXXX:XXXX:200:5::1
> >> >> Sending 1, 16-byte ICMPv6 Echo to XXXX:XXXX:200:5::1
> >> >> timeout 5000 msec, Hop Limit 64
> >> >> Type Control-c to abort
> >> >> Request timed out.
> >> >> No reply from remote host.
> >> >>
> >> >> SSH at de-dus-dc2-gw-001#sh ipv6 route XXXX:XXXX:200:5::1
> >> >> Type Codes - B:BGP C:Connected I:ISIS L:Local O:OSPF R:RIP S:Static
> >> >> BGP Codes - i:iBGP e:eBGP
> >> >> ISIS Codes - L1:Level-1 L2:Level-2
> >> >> OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2
> >> >> STATIC Codes - d:DHCPv6
> >> >> Type IPv6 Prefix Next Hop Router Interface
> >> >> Dis/Metric Uptime src-vrf
> >> >> 1 C XXXX:XXXX:200:5::/64 :: ve 1359
> >> 0/0
> >> >> 151d
> >> >>
> >> >> SSH at de-dus-dc2-gw-001#sh ipv6 neighbor
> >> >> Total number of Neighbor entries: 5
> >> >> Type Codes - *:Static
> >> >> Entries in default VRF:
> >> >> IPv6 Address VLAN LinkLayer-Addr State
> >> >> Age Port R
> >> >> ...
> >> >> 4 fe80::250:56ff:fe9e:33c2 1359 0050.569e.33c2 STALE
> >> >> 12 4/2 0
> >> >> 5 XXXX:XXXX:200:5::2 1359 0050.569e.33c2
> >> DELAY 2
> >> >> 4/2 0
> >> >>
> >> >>
> >> >> SSH at de-dus-dc2-gw-001#conf t
> >> >> SSH at de-dus-dc2-gw-001(config)#int ve 1359
> >> >> SSH at de-dus-dc2-gw-001(config-vif-1359)#no ipv6 address
> >> XXXX:XXXX:200:5::1/64
> >> >> SSH at de-dus-dc2-gw-001(config-vif-1359)#ipv6 address
> >> XXXX:XXXX:200:5::1/64
> >> >> SSH at de-dus-dc2-gw-001(config-vif-1359)#exit
> >> >> SSH at de-dus-dc2-gw-001(config)#exit
> >> >> SSH at de-dus-dc2-gw-001#ping ipv6 XXXX:XXXX:200:5::1
> >> >> Ping self done.
> >> >> SSH at de-dus-dc2-gw-001#
> >> >>
> >> >> kind regards
> >> >> Rolf
> >> >>
> >> >> _______________________________________________
> >> >> foundry-nsp mailing list
> >> >> foundry-nsp at puck.nether.net
> >> >> http://puck.nether.net/mailman/listinfo/foundry-nsp
> >> > _______________________________________________
> >> > foundry-nsp mailing list
> >> > foundry-nsp at puck.nether.net
> >> > http://puck.nether.net/mailman/listinfo/foundry-nsp
> >> _______________________________________________
> >> foundry-nsp mailing list
> >> foundry-nsp at puck.nether.net
> >> http://puck.nether.net/mailman/listinfo/foundry-nsp
> >>
> >
> >
> > _______________________________________________
> > foundry-nsp mailing list
> > foundry-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/foundry-nsp
> >
>
> --
>
> E-Mail to and from me, in connection with the transaction
> of public business, is subject to the Wyoming Public Records
> Act and may be disclosed to third parties.
>
. . . . . . . . . . . . . . . . . . . . . . . . .
Jethro R Binks, Network Manager,
Information Services Directorate, University Of Strathclyde, Glasgow, UK
The University of Strathclyde is a charitable body, registered in
Scotland, number SC015263.
More information about the foundry-nsp
mailing list