[c-nsp] Sup32 Memory upgrade

Tim Stevenson tstevens at cisco.com
Mon May 1 09:46:27 EDT 2006


At 06:55 AM 4/29/2006, Yuri Selivanov quipped:
>           Hi.
>
>      Btw, is there any info about max. # of hardware assisted NAT-entries
>on Sup32 and Sup720-clones? Sorry for 99% OT -- I didn't find anything on
>CCO... :(

<sigh> There is a short answer & a long answer. I'll try sticking to 
the short answer ;)

H/w NAT entries in PFC3 are bound by the size of the netflow table. 
Each NAT entry requires 2 NF entries, hence, you can get at most 
64K/128K (PFC3AB/BXL) NAT entries in h/w. For overload (PAT) case, 
each NAT entry requires 4 NF entries, so 32K/64K.

Note that these NF entries are for each SESSION, not just for each 
xlation - a single NAT xlation may consist of multiple/many sessions.

HTH,
Tim



>      TIA!
>
> > That's correct. You can change this with mls cef maximum-routes. You
> > can monitor it with show mls cef maximum-routes. It does require a reboot.
> >
> > tstevens-6509-02#sh mls cef maximum-routes
> > Load for five secs: 0%/0%; one minute: 0%; five minutes: 0%
> > Time source is NTP, 22:56:11.489 PDT Thu Apr 27 2006
> > FIB TCAM maximum routes :
> > =======================
> > Current :-
> > -------
> >   IPv4 + MPLS         - 192k (default)
> >   IPv6 + IP Multicast - 32k (default)
> >
> >
> > tstevens-6509-02#conf t
> > Enter configuration commands, one per line.  End with CNTL/Z.
> > tstevens-6509-02(config)#mls cef max
> > tstevens-6509-02(config)#mls cef maximum-routes
> > % Incomplete command.
> >
> > tstevens-6509-02(config)#mls cef maximum-routes ?
> >    ip            number of ip routes
> >    ip-multicast  number of multicast routes
> >    ipv6          number of ipv6 routes
> >    mpls          number of MPLS labels
> >
> > tstevens-6509-02(config)#mls cef maximum-routes ip ?
> >    <1-239>  number of 1K entries
> >
> > tstevens-6509-02(config)#mls cef maximum-routes ip 239
> > Maximum routes set to 244736. Configuration will be effective on reboot.
> >
> > tstevens-6509-02(config)#^Z
> > tstevens-6509-02#sh mls cef max
> > tstevens-6509-02#sh mls cef maximum-routes
> > Load for five secs: 0%/0%; one minute: 0%; five minutes: 0%
> > Time source is NTP, 22:57:08.830 PDT Thu Apr 27 2006
> > FIB TCAM maximum routes :
> > =======================
> > Current :-
> > -------
> >   IPv4 + MPLS         - 192k (default)
> >   IPv6 + IP Multicast - 32k (default)
> >
> > User configured :-
> > ---------------
> >   IPv4                - 239k
> >   MPLS                - 1k (default)
> >   IPv6 + IP multicast - 8k (default)
> >
> >
> > tstevens-6509-02#
> >
> > Tim
> >
> > At 10:32 PM 4/27/2006, sthaug at nethelp.no pronounced:
> > > > I was under the impression that it will hold 256K
> > > > routes and thus the system would hold for ~2-3
> > > > years.
> > >
> > >Part of the TCAM is reserved for multicast routes, as far as I remember.
> > >
> > >Steinar Haug, Nethelp consulting, sthaug at nethelp.no
> > >_______________________________________________
> > >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/
> >
> >
> >
> > Tim Stevenson, tstevens at cisco.com
> > Routing & Switching CCIE #5561
> > Technical Marketing Engineer, Catalyst 6500
> > Cisco Systems, http://www.cisco.com
> > IP Phone: 408-526-6759
> > ********************************************************
> > The contents of this message may be *Cisco Confidential*
> > and are intended for the specified recipients only.
> > _______________________________________________
> > 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/
>
>--
>Best Regards,
>Yuri Selivanov [URI2-RIPE]



Tim Stevenson, tstevens at cisco.com
Routing & Switching CCIE #5561
Technical Marketing Engineer, Catalyst 6500
Cisco Systems, http://www.cisco.com
IP Phone: 408-526-6759
********************************************************
The contents of this message may be *Cisco Confidential*
and are intended for the specified recipients only.


More information about the cisco-nsp mailing list