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)#set dscp ? <snip> dscp Set packet dscp from dscp Enjoy Mattias Gyllenvarg 2009/4/15 Tassos Chatzithomaoglou <ach...@forthnet.gr>: > 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 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" commands. >> Neither global nor interface commands. I haven't found any reference >> too this "change" anywhere. >> >> So, how do I get it too trust the DSCP values it on the uplink port so >> I can reserve bandwidth for it on the outgoing port. >> >> Best regards >> Mattias Gyllenvarg >> _______________________________________________ >> cisco-nsp mailing list cisco-nsp@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@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/