Well, the "feautre navigator" provided by the TAC can help you establish
what image you need in terms of feature support. Deciding where you want
to be in terms of version is a much more difficult question.
Bug fixing in 12.0.7T stopped along time ago, if the features you need
are available in 12.0 mainline, 12.0.15 is a lot more mature.
If not, then you can consider that 12.1 mainline should contain all
the features that were introducted up thru 12.0.7T and should include
all the bug-fixes since then, however new bugs have been introduced.
If you need to run 12.1T to pick up features than you're much more into
the crap-shoot world, and while all those old bugs should have been
fixed, many new bugs have been introduced with many new features, and
some of them will affect what should have been stable.
George
> From cisco-nsp-request@puck.nether.net Sat Feb 10 13:14:17 2001
> Return-Path: <cisco-nsp-request@puck.nether.net>
> Received: from puck.nether.net (root@puck.nether.net [204.42.254.5])
> by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id NAA25606;
> Sat, 10 Feb 2001 13:14:10 -0500 (EST)
> Received: (from slist@localhost)
> by puck.nether.net (8.11.1/8.9.3) id f1AIE9705458;
> Sat, 10 Feb 2001 13:14:09 -0500
> (envelope-from cisco-nsp-request@puck.nether.net)
> Resent-Message-Id: <200102101811.f1AIBIX04975@puck.nether.net>
> Date: Sat, 10 Feb 2001 11:43:00 -0500
> X-From_: nathan@arteck.com Sat Feb 10 11:43:00 2001
> Received-Date: Sat, 10 Feb 2001 11:43:00 -0500
> From: "Nathan Casassa" <nathan@arteck.com>
> To: "Vinod Anthony Joseph Cherunni" <vac@dsqworld.com>,
> <cisco-nsp@puck.nether.net>
> Subject: RE: [nsp] REG: Cisco IOS Software
> Old-Date: Sat, 10 Feb 2001 11:36:46 -0500
> Message-ID: <001801c0937f$a88bae70$020210ac@ws>
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
> boundary="----=_NextPart_000_0019_01C09355.BFB8B3B0"
> X-Priority: 3 (Normal)
> X-MSMail-Priority: Normal
> X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
> In-Reply-To: <OF88D3C5A2.78C958FC-ON652569EF.00431F66@maa.antarix.net>
> Importance: Normal
> X-Loop-Detect: 1
> Old-X-Envelope-To: cisco-nsp
> Resent-From: jared@puck.nether.net
> Resent-Date: Sat, 10 Feb 2001 13:11:18 -0500
> Resent-To: cisco-nsp@puck.nether.net
> X-Mailing-List: <cisco-nsp@puck.nether.net> archive/latest/5215
> X-Loop: cisco-nsp@puck.nether.net
> Precedence: list
> Resent-Sender: cisco-nsp-request@puck.nether.net
> Status: R
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_0019_01C09355.BFB8B3B0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
> Have you used the IOS Feature Navigator? You can search by release or
> desired feature to find the supported IOS.
>
> http://www.cisco.com/go/fn/
> -----Original Message-----
> From: Vinod Anthony Joseph Cherunni [mailto:vac@dsqworld.com]
> Sent: Saturday, February 10, 2001 7:18 AM
> To: cisco-nsp@puck.nether.net
> Subject: [nsp] REG: Cisco IOS Software
>
>
>
> Hi All,
>
> Is there any method that Cisco provides to choose an appropriate IOS based
> on the role the router plays. For example I have been trying to use a 2610
> router for a customer multihoming to an upstream ISP. The customer is
> running BGP with his provider, uses NAT, & CAR. And I started by using an
> IOS that was quiet buggy. Now I have put him the 12.0.7 (T), & am observing
> it. In an couple of months we would be replacing the customer router with a
> 7206 - VXR, & this is a stopgap arrangement. I am again worried on what IOS
> I would need to choose fot the Cisco 7206-VXR.
>
> Kindly advice me.
>
> With warm regards,
> Vinod.
>
> ------=_NextPart_000_0019_01C09355.BFB8B3B0
> Content-Type: text/html;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META content=3D"text/html; charset=3Dwindows-1252" =
> http-equiv=3DContent-Type>
> <META content=3D"MSHTML 5.00.3103.1000" name=3DGENERATOR></HEAD>
> <BODY>
> <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
> class=3D771373316-10022001>Have=20
> you used the IOS Feature Navigator? You can search by release or desired =
> feature=20
> to find the supported IOS.</SPAN></FONT></DIV>
> <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
> class=3D771373316-10022001></SPAN></FONT> </DIV>
> <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
> class=3D771373316-10022001><FONT=20
> size=3D3><A=20
> href=3D"http://www.cisco.com/go/fn/">http://www.cisco.com/go/fn/></FON=
> T></SPAN></FONT></DIV>
> <BLOCKQUOTE=20
> style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: =
> 5px">
> <DIV class=3DOutlookMessageHeader><FONT face=3D"Times New Roman"=20
> size=3D2>-----Original Message-----<BR><B>From:</B> Vinod Anthony =
> Joseph=20
> Cherunni [mailto:vac@dsqworld.com]<BR><B>Sent:</B> Saturday, February =
> 10, 2001=20
> 7:18 AM<BR><B>To:</B> cisco-nsp@puck.nether.net<BR><B>Subject:</B> =
> [nsp] REG:=20
> Cisco IOS Software<BR><BR></DIV></FONT><BR><FONT face=3D"Courier New" =
> size=3D2>Hi=20
> All,</FONT> <BR><BR><FONT face=3D"Courier New" size=3D2>Is there any =
> method that=20
> Cisco provides to choose an appropriate IOS based on the role the =
> router=20
> plays. For example I have been trying to use a 2610 router for a =
> customer=20
> multihoming to an upstream ISP. The customer is running BGP with =
> his=20
> provider, uses NAT, & CAR. And I started by using an IOS that was =
> quiet=20
> buggy. Now I have put him the 12.0.7 (T), & am observing it. In an =
> couple=20
> of months we would be replacing the customer router with a 7206 - VXR, =
> &=20
> this is a stopgap arrangement. I am again worried on what IOS I =
> would=20
> need to choose fot the Cisco 7206-VXR.</FONT> <BR><BR><FONT =
> face=3D"Courier New"=20
> size=3D2>Kindly advice me.</FONT> <BR><BR><FONT face=3D"Courier New" =
> size=3D2>With=20
> warm regards,</FONT> <BR><FONT face=3D"Courier New"=20
> size=3D2>Vinod.</FONT></BLOCKQUOTE></BODY></HTML>
>
> ------=_NextPart_000_0019_01C09355.BFB8B3B0--
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:28 EDT