Re: [c-nsp] ME3400-24FS 12.2(46)SE METROIPACCESS with no MLS QOS commands

2009-04-15 Thread Wyatt Mattias Gyllenvarg
Hey All Thanks for your answers. Here is the end result. The equivalent config for "mls qos trust dscp" on a physical interface on a ME3400 is. policy-map uplink class class-default set dscp dscp interface gix/y service-policy input uplink User friendly clue was: me3400(config-pmap-c)#se

Re: [c-nsp] ME3400-24FS 12.2(46)SE METROIPACCESS with no MLS QOS commands

2009-04-15 Thread Tassos Chatzithomaoglou
Mattias, I believe the default mode is to not change the CoS/DSCP of packets, so you shouldn't have any problem. Also, you can use a policy-map under the interface if you want to modify the above. -- Tassos Wyatt Mattias Gyllenvarg wrote on 15/04/2009 09:47: Hi all! I've been racking my

Re: [c-nsp] ME3400-24FS 12.2(46)SE METROIPACCESS with no MLS QOS commands

2009-04-15 Thread Wyatt Mattias Gyllenvarg
Hi Claes I figured that something like that would work, but it seems a like a stretch compared too "mls qos trust". I will run a version of your config for the time being. Thanks Mattias Gyllenvarg 2009/4/15 Claes Jansson : > Hi Mattias! > > I've been in the same position as you are now :-) But

[c-nsp] ME3400-24FS 12.2(46)SE METROIPACCESS with no MLS QOS commands

2009-04-14 Thread Wyatt Mattias Gyllenvarg
Hi all! I've been racking my brain over this for a day now. I have a multicast stream that I have marked with a DSCP value close at the core of my net. I subscribe too it in an ME3400-24FS (12.2(46)SE METROIPACCESS). The problem is that the switch, contrary too documentation, has no "mls qos" co