Yeah, but then which "Cat-IOS" are we going to be using??? Some of the
platforms, although they do similar things and look like they run IOS, do
them entirely different, thus adding to the fun! :-)
For example, the Cat2948G-L3 vs. a Native-mode 6500/MSFC combo routing
vlans. The command-sets are totally different (prolly doing two different
things to achieve the same results). IMO, I think a little cross-platform
uniformity in command-sets would be refreshing or at least more router-like.
Scott
-----Original Message-----
From: kevin graham [mailto:kgraham@dotnetdotcom.org]
Sent: Thursday, April 18, 2002 2:49 PM
To: Keoseyan, Scott (Broadwing)
Cc: ryan-nsp@complicity.co.uk; klong@UBmail.ubalt.edu;
cisco-nsp@puck.nether.net
Subject: RE: [nsp] questions on 4006, 6509 *SFC cards
> I'd not waste time with the Cat4000 Sup2/Layer-3 card combo... go with the
> Sup3 engine.
[...]
> I also think it runs native IOS as well instead of presenting as two
> separate devices.
It does, and though the Access Gateway module isn't supported, you'd be
just as well off w/ a 2600 handling that, as it only provided WIC's as
opposed to PA's of the FlexWAN. As with native IOS on the 6k, its nowhere
near as L2 featureful as CatOS on the Sup1 (ie. fundamental things like
adjustable MTU and niceties like MIST aren't there). I don't recall the
specs on the l3 services module, but also be aware of its limitations,
namely that >100k routes are "not recommended".
With the prevalence of the pure-IOS switches now (native 6k, 4k/sup2,
{29|35}{00|50}, it'd be nice to know just how far out it is until catos is
considered deprecated and new L2 development becomes IOS features..
..kg..
+++The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and destroy any copies of this
document.+++
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:12 EDT