Do you use 12.2(33)SRC2 in a box as Aggregation Router ?
One bug we discovered was a Netflow bug wich resulted in crashes
(CSCsu87248)
kind regards Rinse
Paul Stewart schreef:
We're running 12.2(33)SRC2 on NPE-2G's with no real issues - we were very
brave and ran some 12.4T code for a while and had a major issue every 3-4
weeks that required a reboot (inbound sessions would just stop coming in
pretty much via l2tp tunnels).
On the NPE-1G's we're running same release with no issue neither....
Paul
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rinse Kloek
Sent: Thursday, November 06, 2008 4:14 PM
To: Roddy Strachan
Cc: Cisco-nsp
Subject: Re: [c-nsp] Cisco IOS for broadband aggregation
What kind of features do you use with the 7206VXR box ? We are also
looking to upgrade to 12.2.31SB13 because we have some problems with
12.2(31)SB6.
regards Rinse
Roddy Strachan schreef:
Ruben,
Funny you mention it.
I've just finished an upgrade of a mixture of 7301 and 7206vxr to
12.2(31)SB13.
Had a 7301 running in production for 1 week, no issues, the LNS seems a
lot
more stable if you ask me.
Don't know how the 7206 will go as they have been in production less than
an
hour :).
So far so good, no real issues to report.
On 7/11/08 8:03 AM, "Ruben Alvarez" <[EMAIL PROTECTED]> wrote:
Hi All,
I'm upgrading IOS on my c7206VXR with an npe-300 and:
UBR7200-I/O-2FE/E
PA-A3-T3=
PA-IMA-T1=
PA-4E=
I'm currently using 122-28.SB2 and noticed a 122-31.SB. Is anyone using
the
12.2(31)SB instead of the 12.2(28)SB? I've been looking online and
haven't
seen much about it. I assume it's got the same features as (28)? If
anyone
has any feedback let me know.
Thanks.
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are
addressed.
Please notify the sender immediately by email if you have received this
email by mistake and delete this email from your system. Please note that
any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of the organisation.
Finally, the recipient should check this email and any attachments for
the presence of viruses. The organisation accepts no liability for any
damage caused by any virus transmitted by this email.
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
