[c-nsp] 7206VXR (NPE300) Images
Gert Doering
gert at greenie.muc.de
Tue Jul 19 16:00:03 EDT 2005
Hi,
On Tue, Jul 19, 2005 at 02:50:07PM -0500, Pete Templin wrote:
> >Since these questions appear here fairly often, I wonder who is
> >actually responsible for these "upgrades" 12.2T->12.2 - is it TAC, that
> >recommends this to you? Is this your Cisco reseller?
>
> Isn't 12.2T actually 12.3(-X), as in pre-12.3 code, taken from 12.2
> mainline and prepared for release as 12.3? That would explain why
> features disappeared, etc.
That's about how things work - which is why the word 'upgrades' above
was quoted.
Usually (there are documents on www.cisco.com that explains it in much
more detail) at a "(1)" release, like 12.2(1), a "T" train is forked off,
and lots of features are added.
So 12.2(x)T gets new features for every new subrelease.
In parallel, 12.2(x) with no letters, gets only bugfixes, for each new
releases. (Which isn't fully true for every train, but let's pretend
it is that way).
So at some point much later in time, you have 12.2(15)T and 12.2(29) -
(15)T has all the features, and (29) has no new features, and hopefully
none of the bugs.
12.2(15)T is then used to make 12.3(1), and the process repeats...
IOS versions with different letters, or with more than 1 letter, are
for the very brave of heart...
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany gert at greenie.muc.de
fax: +49-89-35655025 gert at net.informatik.tu-muenchen.de
More information about the cisco-nsp
mailing list