[c-nsp] Adjusting TCAM allocation weird behavior on 7600
Mack McBride
mack.mcbride at viawest.com
Thu Aug 7 11:19:12 EDT 2014
This does look like an issue with the dual sup configuration :(.
You may need cisco support to sort it out.
One solution may be to remove the second sup while configuring
And then reinserting it once the box is booted with the desired configuration.
Mack McBride | Network Architect | ViaWest, Inc.
O: 720.891.2502 | mack.mcbride at viawest.com | www.viawest.com | LinkedIn | Twitter | YouTube
-----Original Message-----
From: Rod James Bio [mailto:rjubio at gmail.com]
Sent: Thursday, August 07, 2014 4:38 AM
To: Antonio Soares; Mack McBride; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Adjusting TCAM allocation weird behavior on 7600
Issuing just "reload" should have been fine, no? I've always done it like that multiple times trying different values.
I suspect, as Mack pointed earlier, the new values are not copied to the slave-sup after a write mem, but it never gets copied.
Regards,
On 8/7/14, 18:27, Antonio Soares wrote:
> When you changed the settings, you rebooted the all box, right ?
>
> Check this:
>
> https://supportforums.cisco.com/discussion/11333356/cisco-7609-rsp720-
> 3cxl-g
> e-mls-cef-maximum-routes
>
>
>
> Regards,
>
> Antonio Soares, CCIE #18473 (RS/SP)
> amsoares at netcabo.pt
> http://www.ccie18473.net
>
> -----Original Message-----
> From: Rod James Bio [mailto:rjubio at gmail.com]
> Sent: quinta-feira, 7 de Agosto de 2014 03:18
> To: Mack McBride; Antonio Soares; cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] Adjusting TCAM allocation weird behavior on 7600
>
> On my OP, I mentioned that I have two supervising engine on SSO mode
> which
> is:
> 1 5 Route Switch Processor 720 10GE (Activ RSP720-3CXL-10GE
> 2 5 Route Switch Processor 720 10GE (Hot) RSP720-3CXL-10GE
>
> Though, the second one was added much later. I was running
> c7600rsp72043-adventerprisek9-mz.153-1.S1.bin before but now I updated
> it to c7600rsp72043-adventerprisek9-mz.153-3.S3.bin.
>
> Running "sh mls cef max", I see:
> #sh mls cef maximum-routes
> FIB TCAM maximum routes :
> =======================
> Current :-
> -------
> IPv4 + MPLS - 512k (default)
> IPv6 + IP Multicast - 256k (default)
>
> User configured :-
> ---------------
> IPv4 - 768k
> MPLS - 24k
> IPv6 + IP Multicast - 112k (default)
>
> Upon reboot :-
> -----------
> IPv4 - 768k
> MPLS - 24k
> IPv6 + IP Multicast - 112k (default)
>
>
> BUT "remote command switch show mls cef max", I see:
> FIB TCAM maximum routes :
> =======================
> Current :-
> -------
> IPv4 + MPLS - 512k (default)
> IPv6 + IP Multicast - 256k (default)
>
> Could this mean that the two sups are not sync? Here is the output of
> show redundancy states:
>
> #sh redundancy states
> my state = 13 -ACTIVE
> peer state = 8 -STANDBY HOT
> Mode = Duplex
> Unit = Primary
> Unit ID = 1
>
> Redundancy Mode (Operational) = sso
> Redundancy Mode (Configured) = sso
> Redundancy State = sso
> Maintenance Mode = Disabled
> Communications = Up
>
> client count = 169
> client_notification_TMR = 30000 milliseconds
> keep_alive TMR = 9000 milliseconds
> keep_alive count = 1
> keep_alive threshold = 18
> RF debug mask = 0x0
>
>
> Regards,
>
> On 8/6/14, 23:51, Mack McBride wrote:
>> This is a silly question but do you have dual sups?
>> That could be causing the issue.
>>
>> Also what code revision are you running?
>> Finally, what line cards are installed?
>> The message you are getting indicates the config is not working For
>> whatever reason, one of the reasons could be line card incompatibility.
>>
>> A show module should list the line cards.
>>
>> Also once you configure the routes on the supervisor and save the
>> config Execute the following command:
>>
>> remote command switch show mls cef max
>>
>> That will determine if the max routes command is getting properly
>> Pushed to the switch processor.
>>
>> And a side note multicast and ipv6 both use two entries.
>> The other poster that said you were 28 short was incorrect.
>> Those settings should have worked.
>>
>> Mack McBride | Network Architect | ViaWest, Inc.
>> O: 720.891.2502 | mack.mcbride at viawest.com | www.viawest.com |
>> LinkedIn | Twitter | YouTube
>>
>>
>>
>> -----Original Message-----
>> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf
>> Of Rod James Bio
>> Sent: Tuesday, August 05, 2014 1:38 PM
>> To: Antonio Soares; cisco-nsp at puck.nether.net
>> Subject: Re: [c-nsp] Adjusting TCAM allocation weird behavior on 7600
>>
>> Hmm I somewhat tried that with these,
>>
>> sh mls cef maximum-routes
>> FIB TCAM maximum routes :
>> =======================
>> Current :-
>> -------
>> IPv4 + MPLS - 512k (default)
>> IPv6 + IP Multicast - 256k (default)
>>
>> User configured :-
>> ---------------
>> IPv4 - 768k
>> MPLS - 16k
>> IPv6 + IP Multicast - 120k (default)
>>
>> Upon reboot :-
>> -----------
>> IPv4 - 768k
>> MPLS - 16k
>> IPv6 + IP Multicast - 120k (default)
>>
>> but still no dice. IOS bug?
>>
>> Regards,
>>
>> On 8/6/14, 3:27, Antonio Soares wrote:
>>> Maybe IPv6 and IP Multicast must share the same region of the TCAM.
>>>
>>> Just try to remove all the "mls cef maximum-routes" commands then
>>> just add this one:
>>>
>>> mls cef maximum-routes ip 768
>>>
>>>
>>>
>>>
>>> Regards,
>>>
>>> Antonio Soares, CCIE #18473 (RS/SP)
>>> amsoares at netcabo.pt
>>> http://www.ccie18473.net
>>>
>>>
>>> -----Original Message-----
>>> From: Rod James Bio [mailto:rjubio at gmail.com]
>>> Sent: terça-feira, 5 de Agosto de 2014 19:41
>>> To: Antonio Soares; cisco-nsp at puck.nether.net
>>> Subject: Re: [c-nsp] Adjusting TCAM allocation weird behavior on
>>> 7600
>>>
>>> This is what I tried,
>>>
>>> #sh mls cef maximum-routes
>>> FIB TCAM maximum routes :
>>> =======================
>>> Current :-
>>> -------
>>> IPv4 + MPLS - 512k (default)
>>> IPv6 + IP Multicast - 256k (default)
>>>
>>> User configured :-
>>> ---------------
>>> IPv4 + MPLS - 768k (default)
>>> IPv6 - 100k
>>> IP Multicast - 28k
>>>
>>> After a wr mem and reboot this is what I got:
>>> *Aug 6 02:15:46.975 PHT: %MLSCEF-SP-1-MAX_ROUTE_MISMATCH: Maximum
>>> routes config mismatch. Reconfigure the maximum routes values and
>>> reload
> the box.
>>>
>>> As you will see the max routes adds to 1024k but still It resets to
>>> the default values.
>>>
>>> Regards,
>>>
>>> On 8/6/14, 1:28, Antonio Soares wrote:
>>>> As already mentioned, the sum should be 1024k, for example, I have
>>>> this on a
>>>> SUP720-3BXL:
>>>>
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> sup720-3bxl#show mls cef maximum-routes FIB TCAM maximum routes :
>>>> =======================
>>>> Current :-
>>>> -------
>>>> IPv4 - 1007k
>>>> MPLS - 1k (default)
>>>> IPv6 + IP Multicast - 8k (default)
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>
>>>>
>>>> 1007+1+(2x8) = 1024
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Antonio Soares, CCIE #18473 (RS/SP) amsoares at netcabo.pt
>>>> http://www.ccie18473.net
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On
>>>> Behalf Of
>>> Rod
>>>> James Bio
>>>> Sent: terça-feira, 5 de Agosto de 2014 16:13
>>>> To: cisco-nsp at puck.nether.net
>>>> Subject: Re: [c-nsp] Adjusting TCAM allocation weird behavior on
>>>> 7600
>>>>
>>>> I read before the link you sent.
>>>>
>>>> BTW, Here is the output of "sh mls cef max":
>>>>
>>>> #sh mls cef maximum-routes
>>>> FIB TCAM maximum routes :
>>>> =======================
>>>> Current :-
>>>> -------
>>>> IPv4 + MPLS - 512k (default)
>>>> IPv6 + IP Multicast - 256k (default)
>>>>
>>>> User configured :-
>>>> ---------------
>>>> IPv4 - 600k
>>>> MPLS - 10k
>>>> IPv6 - 100k
>>>> IP Multicast - 28k
>>>>
>>>> Upon reboot :-
>>>> IPv4 - 600k
>>>> MPLS - 10k
>>>> IPv6 - 100k
>>>> IP Multicast - 28k
>>>>
>>>> Regards,
>>>>
>>>> On 8/5/14, 22:15, Antonio Soares wrote:
>>>>> Check this document, maybe it can help you:
>>>>>
>>>>> http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-s
>>>>> e r ie s-swit ches/117712-problemsolution-cat6500-00.html
>>>>>
>>>>> Can you share the "show mls cef max" output ?
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> Antonio Soares, CCIE #18473 (RS/SP) amsoares at netcabo.pt
>>>>> http://www.ccie18473.net
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On
>>>>> Behalf Of Rod James Bio
>>>>> Sent: terça-feira, 5 de Agosto de 2014 12:03
>>>>> To: cisco-nsp at puck.nether.net
>>>>> Subject: [c-nsp] Adjusting TCAM allocation weird behavior on 7600
>>>>>
>>>>> Hi, I'd like to ask anyone in the group who owns cisco 7600 if
>>>>> they had experience when they adjusted the allocation to increase
>>>>> the maximum routes for ipv4 etc. We are near the 512K ipv4 limit
>>>>> (~509K) for the
>>>>> 7600 (default size) and I tried adjusting the tcam allocation by
> running:
>>>>>
>>>>> mls cef maximum-routes ip 750
>>>>> mls cef maximum-routes ipv6 100
>>>>> mls cef maximum-routes mpls 10
>>>>> mls cef maximum-routes ip-multicast 28
>>>>>
>>>>> But after rebooting the whole box I got an error, "Maximum routes
>>>>> config mismatch. reconfigure the maximum routes values and reload
>>>>> the box" (Sorry this is all I copied from the console) and the
>>>>> tcam was back to the default values.
>>>>>
>>>>> I have a dual RSP720-3CXL-10GE sups on sso mode and
>>>>> c7600rsp72043-adventerprisek9-mz.153-1.S1.bin if those info help.
>>>>>
>>>>> Thanks,
>>>>> _______________________________________________
>>>>> 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/
>>>>
>>>
>> _______________________________________________
>> 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