[c-nsp] Whales 15.1 (was: ME3600 IOS / SPAN)

Jason Lixfeld jason at lixfeld.ca
Tue Nov 22 17:17:12 EST 2011


While we're on the subject -

Has anyone found any interoperability issues with xconnects between FCS 12.2 (and rebuilds) and FCS+1 15.1?

We've had one or two issues with 15.1 xconnects not passing traffic between 12.2(52)EY1 xconnects.  Our solution was to downgrade 15.1 to 12.2(52) EY2 which seems to be fully compatible with the lesser of the 12.2(52)EY builds.  We can't speak for anything more recent in the 12.2 train than EY2 because we were badly in need of 15.1 features, so we jumped right into it when it started shipping.

On 2011-11-22, at 5:05 PM, Tassos Chatzithomaoglou wrote:

> We migrated from ME-3400 to ME-3800X and we noticed that we started getting output drops on 1G interfaces, while the traffic was ~700 Mbps.
> I know about bursts and so on, but the same traffic wasn't causing any drops on the older platform.
> We tried some output shaping service policies under the interface, but the drops were still there, and then on the policy-map too.
> We also noticed that the rate counters on the policy-map were totally wrong.
> Then we applied shaping service policies under the service instances and increased the queue-limit to the max available, and the drops got very low (but still existent).
> Tac concluded that this is due to the default egress buffers being too small, and we're waiting for the developers to come up with a solution.
> Another issue we met, is that any match of non-default classes under the service policies under the service instances wasn't working at all, when there was no ingress L2 control traffic from the other side. I know it sounds very strange, but this was the conclusion we came to, after doing many different tests.
> 
> To summarize, we have quite a few of strange cases with tac on this platform.
> 
> --
> Tassos
> 
> 
> Nick Hilliard wrote on 22/11/2011 22:29:
>> On 22/11/2011 18:44, Tassos Chatzithomaoglou wrote:
>>> Unfortunately there are still a lot of features missing + some things that
>>> don't work well (primarily the -hardcoded- small egress buffers)
>> Can you elaborate on this?
>> 
>> Nick
>> 
> _______________________________________________
> 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