[c-nsp] IPv6 on MSFC2

[Hank Nussbacher]

At 10:25 AM 09-02-07 +1100, Richard Gallagher wrote:
>Chuck, try ipc-con <slo#t> <cpu# 0|1>

Chuck,

In addition you might want to cut and paste the following that was 
previously posted to cisco-nsp:

7600 cheat-sheet
----------------

sho catalyst          [Catalyst 6000 info]
sho cwan              [Catalyst WAN info]
sho diagnostic result [Diagnostics]
sho fabric            [Crossbar switching data]
sho fm inter g7/1     [Feature Manager]
sho ibc br            [Traffic to CPU]
sho inventory         [Equipment inventory]
sho idprom module n   [IDPROM info]
sho mac-address-table [MAC]
sho mls               [Multilayer switching]
  sho mls statistics
  sho mls netflow ip nowrap
  sho mls status       [undocumented]
sho module            [Linecard info]
sho platform          [hardware]
sho power             [Power info]
  show platform hardware pfc mode
sho tcam              [TCAM info]
  sho tcam detail
sho upgrade fpd       [Field Programmable Device upgrade]

attach n              [Connect to SUP]
hw-module             [Reset of power-cycle specific module]
remote command switch sho xxxx [Connect to SUP]
ipc-cons n            [Connect to Flexwan - undocumented]

Hank Nussbacher
http://www.interall.co.il



>Rich
>
>Church, Chuck wrote:
> > Thanks Oli.  From what I've read, the Enhanced FlexWAN can do about
> > 640,000 PPS per slot.  I guess the non-enhanced version is about half
> > that.  Assuming memory isn't an issue on the FlexWAN, are these PPS
> > numbers accurate for IPv6 also, or just IPv4?  Also, how the heck does
> > one console into the flexwan to check CPU?  I've tried a variety of
> > remote, session, and attach commands.  Session slot slot# processor
> > proc# seems to try, but I'm not sure of the processor number.  Tried
> > both 0 and 1, both time out as it tries to connect to a loopback
> > address.  It's a Sup2 in hybrid mode, CatOS 6.4, IOS 12.1E on MSFC.
> >
> > Thanks again,
> >
> > Chuck
> >
> > -----Original Message-----
> > From: Oliver Boehmer (oboehmer) [mailto:oboehmer at cisco.com]
> > Sent: Thursday, February 08, 2007 12:44 PM
> > To: Church, Chuck; nsp
> > Subject: RE: [c-nsp] IPv6 on MSFC2
> >
> > Church, Chuck <> wrote on Thursday, February 08, 2007 6:23 PM:
> >
> >> Anyone,
> >>
> >>     I understand that IPv6 is done in software on the MSFC2 on a Sup2.
> >> I've read that the forwarding performance is about 500,000 pps for
> >> software-switched CEF packets on this MSFC, and about 20,000 for
> >> process switched.  Anyone have an idea if IPv6 is done in CEF on this
> >> module? If so, does that 500,000 pps number seem realistic?  Assuming
> >> no features like NAT, QoS, ACLs, etc.  We've got several hundred of
> >> these in place for WAN connectivity, everything from DS-3 to OC-3 in
> >> FlexWANs, and some OSMs doing POS OC-12.  Almost all are just one WAN
> >> link, with ethernet connectivity down from there.  I'm thinking that
> >> the Sup2 will probably work for speeds up to OC-3, but want to make
> >> sure.
> >
> > I've seen tests with ~200kpps on Sup2, but then your MSFC CPU will be at
> > 90+%, so not really something I'd do in production ;-)
> >
> > Filling an OC3 with some IMIX packet distribution should work, however,
> > not sure about the Flexwan as this also needs to be checked here.
> >
> >       oli
> >
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>_______________________________________________
>cisco-nsp mailing list  cisco-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>
>
>+++++++++++++++++++++++++++++++++++++++++++
>  This Mail Was Scanned By Mail-seCure System
>  at the Tel-Aviv University CC.