[c-nsp] 7600 ES20 first questions

[Tassos Chatzithomaoglou]

Thanks for the info Saku,

I finally managed to complete my tests and everything seems to be working fine.

btw, this is the qos config i used:


class-map match-all TRAFFIC1
   match cos 6 7
!
policy-map TRAFFIC1
   class TRAFFIC1
     shape average 128000
   class class-default
     shape average 10000000
!
interface GigabitEthernet5/0/0
  mls qos trust cos
  service instance 2999 ethernet
   service-policy output TRAFFIC1


class-map match-all TRAFFIC2
   match cos 3 5
!
policy-map TRAFFIC2
   class TRAFFIC2
     police 5000000
     priority
   class class-default
     shape average 1000000
!
interface GigabitEthernet5/0/0.2999103
  description ** local termination - vlan 2999/103 **
  encapsulation dot1Q 2999 second-dot1q 103
  ip address x.x.x.x
  service-policy output TRAFFIC2


Generally, i'm little bit disappointed by the awkward qos "restrictions" and i'm sure that the CCO 
configuration page about ES20 is definitely the worst ever written.


Regarding the locally significant vlans, we're actually evaluating the ES20 card for some 
double-tagged vlan scenarios, so we're "luckier" than you. But i'll include your note in our 
results, since we might need it in the future.

--
Tassos


Saku Ytti wrote on 8/2/2008 8:54 μμ:
> On (2008-02-08 19:51 +0200), Tassos Chatzithomaoglou wrote:
> 
> Hello Tassos,
> 
>> vlan 3500/x -------------- vlan 3600/x
>>         6500 ---- 7600 ---- 6500
>>
>> 1) Will the following work?
> Should work. If not, it's config error, but what you want to do
> is supported.
>  
>> 2) If i want to terminate locally on the 7600 an inner vlan, can i use the following along with the above translation:
> Will work as is.
> 
>> 3) What kind of egress QoS can i use on the main interface and on the subinterface? I did some tests but i wasn't successful.
> 
> On egress you can only shape, policer is possible in hardware but
> not supported today. On ingress you can only police, shaper is not
> supported in hardware.
> So change police to shape. This should work in subinterface.
> 
>> 7609#sh policy-map TR2
>>
>>    Policy Map TR2
>>      Class class-default
>>        Average Rate Traffic Shaping
>>        cir 50000000 (bps)
>>
>> 7609(config-if)#service-policy output TR2
>> Service-policy can not be applied to main interface when service-instances are configured.
> 
> Apply it under the EVC instance configration, it should work as-is.
> Matching in EVC is very limited, only CoS so far, it's software not
> hardware limitation.
> 
> 
> I was extremely disappointed to notice that ES20 does not support
> locally signifacant VLAN subinterfaces when using single tags,
> when using double tags it does. This however should be fixable
> in unknown time frame (I'd recommend to wait if this is
> important requirement and tell your account team it's stopping
> you from investing in this card).
> 
> Thanks,