[c-nsp] 67xx cards and full tables
Howard Leadmon
howard at leadmon.net
Fri Nov 25 15:06:18 EST 2016
I am also using a 7606, running multiple full BGP tables from transit
connections, plus a bunch of IX peering sessions to boot. Of course you
have to have the XL DFC's, and as many have said it has a limited lifespan,
but outside of that with the current cost of the hardware it's still a decent
platform. Also as you mentioned, we are running dual-stack with IPv4/IPv6
and have for a good while.
As a reference, here is my current layout:
Version: Cisco IOS Software, c7600rsp72043_rp Software
(c7600rsp72043_rp-ADVIPSERVICESK9-M), Version 15.3(3)S6, RELEASE SOFTWARE
(fc1)
7606#sho plat hard cap
System Resources
PFC operating mode: PFC3BXL
Supervisor redundancy mode: administratively sso, operationally sso
Switching resources: Module Part number Series CEF
mode
1 WS-X6724-SFP CEF720
dCEF
2 WS-X6708-10GE CEF720
dCEF
4 WS-X6748-GE-TX CEF720
dCEF
5 RSP720-3CXL-GE supervisor
CEF
6 RSP720-3CXL-GE supervisor
CEF
Memory/TCAM usage on the 6708-10GE-3CXL:
Processor memory: Module Bytes: Total Used
%Used
2 977205520 426457656
44%
So plenty of free RAM on the board.
L3 Forwarding Resources
Module FIB TCAM usage: Total Used
%Used
2 72 bits (IPv4, MPLS, EoM) 802816 614934
77%
144 bits (IP mcast, IPv6) 122880 34479
28%
detail: Protocol Used
%Used
IPv4 612879
76%
MPLS 2055
1%
EoM 0
0%
IPv6 34472
28%
IPv4 mcast 4
1%
IPv6 mcast 3
1%
Adjacency usage: Total Used
%Used
1048576 738
1%
TCAM is for sure used a good bit, but at least at this time still about a
quarter of it free, or at least from the views I am getting of the net.
So it may not be the perfect platform, but at least at this time it will
work. Having the 4G RP/2G SP on the RSP's takes care of the memory issues on
the RSP's, so it looks like running out of TCAM will become the real problem,
and when we have to replace it with something else..
---
Howard Leadmon
PBW Communications, LLC
http://www.pbwcomm.com
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
> krunal shah
> Sent: Thursday, November 24, 2016 12:52 PM
> To: James Bensley <jwbensley at gmail.com>
> Cc: cisco-nsp <cisco-nsp at puck.nether.net>
> Subject: Re: [c-nsp] 67xx cards and full tables
>
> Thnx James, Basically I wanted to push management to enable IPv6 and get
> transit circuit. But it is hard to justify cost vs benefit. So I wanted to
check if I
> can enable it with existing hardware. I am also running 15.3(3)S6 code for
all
> internet facing routers.
>
> Krunal
>
> On Thu, Nov 24, 2016 at 9:55 AM, James Bensley <jwbensley at gmail.com>
> wrote:
>
> > On 23 November 2016 at 22:02, krunal shah <krun.shah at gmail.com> wrote:
> > > Hello,
> > >
> > > Is there anyone importing full table IPv4 and IPv6 in 6708 line cards?
> > >
> > > I am looking to see if any operational issues with installing full
> > > BGP table in a VRF both IPv4 and IPv6 in VRF from more than 2 BGP
> > > sources on
> > > 7600 router with RSP720-3CXL 4GB RP and 2GB SP memory. I also need
> > > some room for MPLS routes may be around 2000 IPv4 routes and lables.
> > >
> > > System has only one VRF and and allocating labels per VRF.
> > >
> > > #sh mls cef maximum-routes
> > > FIB TCAM maximum routes :
> > > =======================
> > > Current :-
> > > -------
> > > IPv4 + MPLS - 768k (default)
> > > IPv6 - 127k
> > > IP Multicast - 1k
> > >
> > > Looking to see how much memory (show memory statistics) and
> > > processor utilization.
> >
> >
> > Hi Kruanl,
> >
> > You can run the full IPv4 and IPv6 tables on 6708 cards with
> > RS720-3CXL assuming DFC-3CXL on the line cards. This is an Internet
> > facing 7606 we have with such a configuration. Sadly this box has 2GB
> > of RP RAM not 4GBs, but not many of our 7600s have the full table. The
> > box is running 15.3(3)S6. Note that the full table is in the GRT not a
> > VPN for this box, we see the IPV4 BGL table as about 610k routes so we
> > have about 50k VPNv4 routes. If you are using per-VRF labels then I
> > wouldn't expect any more memory usage than we have below as we are
> > using a mixture of per-prefix and per-vrf so ours is probably higher
> > than what yours would be.
> >
> > Overall its "ok" with 2GBs of SP RAM but I wouldn't recommend
> > deploying this now, its time to move away from these 7600s. We have
> > some MX480s in the same racks and we are migrating stuff over. It
> > "will work" with what you have suggested but it won't have much
> > longevity. Also a BGP bounce on the transit bounce does NOT go
> > unnoticed.
> >
> > Cheers,
> > James.
> >
> >
> >
> > 7606-S-15.3(3)S6#show memory statistics
> > Head Total(b) Used(b) Free(b) Lowest(b)
> > Largest(b)
> > Processor 13FCECD8 1677923112 1191216368 486706744 474380240
> > 479577996
> > I/O 78000000 134217728 50041376 84176352 83398176
> > 83923804
> >
> >
> > 7606-S-15.3(3)S6#show platform hardware capacity forwarding
> > L2 Forwarding Resources
> > MAC Table usage: Module Collisions Total Used
> > %Used
> > 5 0 98304 879
> > 1%
> > 6 0 98304 897
> > 1%
> >
> > L3 Forwarding Resources
> > Module FIB TCAM usage: Total
> > Used %Used
> > 5 72 bits (IPv4, MPLS, EoM) 901120
> > 797960 89%
> > 144 bits (IP mcast, IPv6) 73728
> > 32647 44%
> >
> > detail: Protocol Used
> > %Used
> > IPv4 664911
> > 74%
> > MPLS 133045
> > 15%
> > EoM 4
> > 1%
> >
> > IPv6 32640
> > 44%
> > IPv4 mcast 4
> > 1%
> > IPv6 mcast 3
> > 1%
> >
> > Adjacency usage: Total Used
> > %Used
> > 1048576 210850
> > 20%
> > L3 Forwarding Resources
> > Module FIB TCAM usage: Total
> > Used %Used
> > 6 72 bits (IPv4, MPLS, EoM) 901120
> > 797960 89%
> > 144 bits (IP mcast, IPv6) 73728
> > 32647 44%
> >
> > detail: Protocol Used
> > %Used
> > IPv4 664911
> > 74%
> > MPLS 133045
> > 15%
> > EoM 4
> > 1%
> >
> > IPv6 32640
> > 44%
> > IPv4 mcast 4
> > 1%
> > IPv6 mcast 3
> > 1%
> >
> > Adjacency usage: Total Used
> > %Used
> > 1048576 210846
> > 20%
> >
> >
> >
> > 7606-S-15.3(3)S6#show module
> > Mod Ports Card Type Model
Serial
> > No.
> > --- ----- -------------------------------------- ------------------
> > -----------
> > 1 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX
> > 2 48 CEF720 48 port 1000mb SFP WS-X6748-SFP
> > 3 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE
> > 4 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX
> > 5 8 CEF720 8 port 10GE with DFC WS-X6708-10GE
> > 6 5 Route Switch Processor 720 10GE (Activ RSP720-3CXL-10GE
> >
> > Mod Sub-Module Model Serial Hw
> > Status
> > ---- --------------------------- ------------------ -----------
> > -------
> > -------
> > 1 Centralized Forwarding Card WS-F6700-CFC 4.1 Ok
> > 2 Centralized Forwarding Card WS-F6700-CFC 4.1 Ok
> > 3 Centralized Forwarding Card WS-F6700-CFC 4.1 Ok
> > 4 Centralized Forwarding Card WS-F6700-CFC 4.1 Ok
> > 5 Distributed Forwarding Card WS-F6700-DFC3CXL 1.6 Ok
> > 6 Policy Feature Card 3 7600-PFC3CXL-10GE 1.2 Ok
> > 6 C7600 MSFC4 Daughterboard 7600-MSFC4 2.2 Ok
> >
> >
> > 7606-S-15.3(3)S6#show platform hardware pfc mode PFC operating mode :
> > PFC3CXL
> >
> >
> > 7606-S-15.3(3)S6#show mls cef maximum-routes FIB TCAM maximum
> routes :
> > =======================
> > Current :-
> > -------
> > IPv4 + MPLS - 880k (default)
> > IPv6 - 64k
> > IP Multicast - 1k
> >
> _______________________________________________
> 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/
More information about the cisco-nsp
mailing list