configuration differences when converting from ME3750 to ME3800x

[alukes]

system mtu routing 1500  Is there a replacement command for this?

MLS QOS commands not accepted. Has the ME3800 been designed so these buffers don't need to be adjusted?

in the policy map:

class class-default

     random-detect dscp-based           not accepted. Is there a work around?
     random-detect exponential-weighting-constant 9         not accepted. Is there a work around?

On the Gigabit ports:

SSR-QUEUE command is not accepted. Again, not a problem due to the design?

priority queue not accepted. Same reason?

On the Tengig interface:

tx-ring-limit 2        still needed? If so, what is the recommended value?  

tx-queue-limit 2     still needed? If so, what is the recommended value? 

mls qos trust dscp  Isn't accepted. How do I trust DSCP?

Thanks

[antonkolev]

Did you find solution for your conversion ?

[aducey01]

no, no one responded...Do you know how to convert this?

Our 3750 MLS QOS commands are as follows:

mls qos map cos-dscp 0 8 16 26 32 46 48 56
mls qos srr-queue input bandwidth 90 10
mls qos srr-queue input threshold 1 8 16
mls qos srr-queue input threshold 2 34 66
mls qos srr-queue input buffers 67 33
mls qos srr-queue input cos-map queue 1 threshold 2 1
mls qos srr-queue input cos-map queue 1 threshold 3 0
mls qos srr-queue input cos-map queue 2 threshold 1 2
mls qos srr-queue input cos-map queue 2 threshold 2 4 6 7
mls qos srr-queue input cos-map queue 2 threshold 3 3 5
mls qos srr-queue input dscp-map queue 1 threshold 2 9 10 11 12 13 14 15
mls qos srr-queue input dscp-map queue 1 threshold 3 0 1 2 3 4 5 6 7
mls qos srr-queue input dscp-map queue 1 threshold 3 32
mls qos srr-queue input dscp-map queue 2 threshold 1 16 17 18 19 20 21 22 23
mls qos srr-queue input dscp-map queue 2 threshold 2 33 34 35 36 37 38 39 48
mls qos srr-queue input dscp-map queue 2 threshold 2 49 50 51 52 53 54 55 56
mls qos srr-queue input dscp-map queue 2 threshold 2 57 58 59 60 61 62 63
mls qos srr-queue input dscp-map queue 2 threshold 3 24 25 26 27 28 29 30 31
mls qos srr-queue input dscp-map queue 2 threshold 3 40 41 42 43 44 45 46 47
mls qos srr-queue output cos-map queue 1 threshold 3 5
mls qos srr-queue output cos-map queue 2 threshold 3 3 6 7
mls qos srr-queue output cos-map queue 3 threshold 3 2 4
mls qos srr-queue output cos-map queue 4 threshold 2 1
mls qos srr-queue output cos-map queue 4 threshold 3 0
mls qos srr-queue output dscp-map queue 1 threshold 3 40 41 42 43 44 45 46 47
mls qos srr-queue output dscp-map queue 2 threshold 3 24 25 26 27 28 29 30 31
mls qos srr-queue output dscp-map queue 2 threshold 3 48 49 50 51 52 53 54 55
mls qos srr-queue output dscp-map queue 2 threshold 3 56 57 58 59 60 61 62 63
mls qos srr-queue output dscp-map queue 3 threshold 3 16 17 18 19 20 21 22 23
mls qos srr-queue output dscp-map queue 3 threshold 3 32 33 34 35 36 37 38 39
mls qos srr-queue output dscp-map queue 4 threshold 1 8
mls qos srr-queue output dscp-map queue 4 threshold 2 9 10 11 12 13 14 15
mls qos srr-queue output dscp-map queue 4 threshold 3 0 1 2 3 4 5 6 7
mls qos queue-set output 1 threshold 1 138 138 92 138
mls qos queue-set output 1 threshold 2 138 138 92 400
mls qos queue-set output 1 threshold 3 36 77 100 318
mls qos queue-set output 1 threshold 4 20 50 67 400
mls qos queue-set output 2 threshold 1 149 149 100 149
mls qos queue-set output 2 threshold 2 118 118 100 235
mls qos queue-set output 2 threshold 3 41 68 100 272
mls qos queue-set output 2 threshold 4 42 72 100 242
mls qos queue-set output 1 buffers 10 10 26 54
mls qos queue-set output 2 buffers 16 6 17 61
mls qos 

[aducey01]

Wow, really disappointing that no one answered this question in 3 years...

I have the same question, do I need to cal TAC for an answer???

MLS QOS commands not accepted...I'd heard that this command was deprecated, how do we translate our QoS statements onto the new platform?

-anne

[alukes]

I never got a clear answer so I tested it with a traffic generator to make sure it could handle the load with QOS markings respected.

Here are configurations on the ME3800 that worked for me.

policy-map standard5
 class voice
  priority
 class voice-control
  bandwidth remaining percent 4
 class scavenger
  bandwidth remaining percent 4
 class video-conference
  bandwidth remaining percent 13
 class class-default
  random-detect dscp-based
  random-detect exponential-weighting-constant 9
  bandwidth remaining percent 79

interface GigabitEthernet0/23
 description XXXXXXX     In other words, no qos commands needed on the interface

 switchport mode trunk
 speed nonegotiate
 service-policy output ES1

BIG surprise when installing: I used the Ten gig port to connect to a test OPT-E-MAN cloud during testing. It worked fine.  Connecting to the AT&T OPT-E-MAN switch during the install, the Ten gig port coudn't negotiate with the AT&T switch. I had to use a gigabit port.

It has been working reliably in a network with significant voice traffic for 1.5 years with no problems, so  the old commands aren't needed. DSCP is trusted automatically.

I agree with your irritation. An upgrade guide would have been nice.

[aducey01]

We aren't using the ME switch, these are poe closet switches for a voip deployment.