Cisco 12000 series routers and IOS XR.

Tue Jul 14 15:36:49 UTC 2009

3.4.2

On Mon, Jul 13, 2009 at 8:53 PM, Jim Wininger <jwininger at indianafiber.net>wrote:

>  What release are you running? We are currently at 3.6.2 (as recommended
> by Cisco (our SE and some upper levels)).
>
>
>
> On 7/13/09 6:15 PM, "Dan Snyder" <sliplever at gmail.com> wrote:
>
> We also have a couple running full tables of BGP with XR code and they have
> been running solid for a couple of years now with no problems.
>
> -Dan
>
> On Mon, Jul 13, 2009 at 5:37 PM, Scott Berkman <scott at sberkman.net> wrote:
>
> We have 2 12k's on our borders and both are running IOS GS code, but are
> rock solid.
>
>         -Scott
>
> -----Original Message-----
> From: Jim Wininger [mailto:jwininger at indianafiber.net]<jwininger at indianafiber.net]>
> Sent: Monday, July 13, 2009 4:20 PM
> To: nanog at nanog.org
> Subject: Cisco 12000 series routers and IOS XR.
>
> Is anyone on the list running the Cisco 12000 Series routers with XR? We
> have a couple of these in our network and are having a few issues with
> them.
>
> Specifically the line cards will reboot for some unknown reason
> (12000-SIP-501). We recently replaced one of the cards and the new hardware
> (<6mo old) is doing the same thing.
>
> Anyone have issues with these routers?
> --
> Jim Wininger
>
>
>
>
>
>
>
>
> --
> Jim Wininger
> Indiana Fiber Network
> Desk - 317-777-7114
> Cell - 317-432-7609
> Office - 317-280-4636
>
> CONFIDENTIALITY NOTICE: The information contained in this electronic mail
> transmission (including any attachment) is intended for the exclusive use of
> the named recipient and may contain information that is privileged or
> otherwise confidential. It is not intended for transmission to, or receipt
> by, anyone other than the named recipient (or person authorized to deliver
> it to the named recipient). It should not be copied or forwarded to any
> unauthorized person. If you have received this electronic mail transmission
> in error, please delete it from your system including any attachment without
> copying or forwarding it, and notify the sender of the error by return
> e-mail.
>