×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

PBR problem with 7600 12.2(33)SRD

Unanswered Question
Oct 19th, 2010
User Badges:

Dear all,

We face a serious problem with our Core backbone.

We used a WS-C3750G before and ran BGP, OSPF, with PBR.

But now, we migrate with 7606 routers with RSP720-3CXL-GE (MSFC4) and are very surprised that all 7606 routers
face a problem when PBR is applied.

All ping through the infrastructures have up to 25% of packet loss once we specify Datagram size of 1000, and all FTP and HTTP download
are very slow (not exceding 40 KB/Sec).


We do not understand why the 3750 supported this PBR (same configuration) without a performance issue, and the 7600, which is supposed
to be more powerfull does not support ?


I saw that on a former 7600 IOS Version, it was possible to optimize the PBR to be handled by hardware PFC and DFC card (usin TCAM table).

But our current IOS 12.2(33)SRD does not accept the commande platform ipv4 pbr optimize tcam


Any ideas are welcome.


Connect101.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
francisco_1 Tue, 10/19/2010 - 15:38
User Badges:
  • Gold, 750 points or more

Well PBR should be handle by hardware by programming TCAM tables but not all possible set actions can be available.



See below for some restriction



The Policy Feature Card (PFC) and any Distributed Feature Cards (DFCs) provide hardware support for policy-based routing (PBR) for route-map sequences that use the match ip address, set ip next-hop, and ip default next-hop PBR keywords.

#

When configuring PBR, follow these guidelines and restrictions:

#

The PFC provides hardware support for PBR configured on a tunnel interface.

#

The PFC does not provide hardware support for PBR configured with the set ip next-hop keywords if the next hop is a tunnel interface.

#

If the MSFC address falls within the range of a PBR ACL, traffic addressed to the MSFC is policy routed in hardware instead of being forwarded to the MSFC. To prevent policy routing of traffic addressed to the MSFC, configure PBR ACLs to deny traffic addressed to the MSFC.

#

Any options in Cisco IOS ACLs that provide filtering in a PBR route-map that would cause flows to be sent to the MSFC to be switched in software are ignored. For example, logging is not supported in ACEs in Cisco IOS ACLs that provide filtering in PBR route-maps.

#

PBR traffic through switching module ports where PBR is configured is routed in software if the switching module resets. (CSCee92191)


http://www.cisco.com/en/US/docs/routers/7600/ios/12.2SR/configuration/guide/layer3.html#wp1027016


Francisco

connect101 Tue, 10/19/2010 - 15:55
User Badges:

Hi Francisco,

Thanks for your prompt feed back.

But how to do this TCAM table programing ?

The command /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Tableau Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} platform ipv4 pbr optimize tcam supported ?


Pleas advise.

Sherif Ismail Wed, 09/28/2011 - 15:07
User Badges:

Hello connect101,

Have you solved this issue ?


Appreciate your resonse as this will help me a lot


Thanks

BR,

Sherif Ismail



Actions

This Discussion

Related Content