[f-nsp] XMR Software Upgrade Path from 4.0.1a
Gerald Krause
gk at ax.tc
Tue Jan 11 17:17:49 EST 2011
Hi Chris,
yes, looks like that I have to upgrade the FPGAs as well. But I'm a
little bit more interested in opinions concerning the 5.1 software in
general. How does it feel in the real - does anybody use this train in
production currently at all?
The main reason for the decision to upgrade our systems is that we
observed some (rare) FIB issues in the past, e.g. "IPv4/Pv6 route exist
but no corresponding record is in th FIB" or the other way around - we
saw "records in the FIB without a matching IPv4/IPv6 route".
I've checked nearly all release notes since 4.0.1a and every notes for a
newer version has make think "oh my good, don't use the former one" and
so I'm simply end up in 5.1 ;-).
--
Gerald (ax/tc)
Am 11.01.11 16:13, schrieb Chris Costa:
> I believe your IronWare upgrade to 5.0 will have to include upgrading FPGA images as well:
>
> Mgmt Modules:
> - Requires MBRIDGE, Rev 32
>
> Interface Modules:
> - PBIFSP2.bin, Rev 3.21
> - XPPSP2.bin, Rev 6.03
>
>
> Chris
>
>
> On Jan 11, 2011, at 3:24 AM, Gerald Krause wrote:
>
>> Hi,
>>
>> we have some XMRs in production, all with the older 4.0.1a code. The
>> Systems are doing mainly L3 things like OSPF, BGP and VRRP within an
>> IPv4/IPv6 dualstack environment but no *PLS or special L2 services at
>> the moment.
>> We plan to upgrade the systems with an newer software release and I
>> wondering if there exist any arguments against using the latest 5.1 code?
>>
>> Cheers,
>> --
>> Gerald (ax/tc)
>> _______________________________________________
>> foundry-nsp mailing list
>> foundry-nsp at puck.nether.net
>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
>
More information about the foundry-nsp
mailing list