Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

rate-limit llq-classify

Hello,

what is the purpose and effect of the command

Router(config)#rate-limit llq-classify

Obviously it is undocumented, but I have a question at hand, why this command is in a router config and what it does.

Thank you in advance.

Martin

1 ACCEPTED SOLUTION

Accepted Solutions
Silver

Re: rate-limit llq-classify

Hi ,

Need llq classification after rate-limit:

For this purpose they integrated rate-limit llq-classify feature CSCds30737.

Description :

Specifically from 121-1a.T1 to 121-3a.T3.

In 121-1a.T1 output CAR acts on the packets and these packets are then classfied by queueing feature for putting them in the appropriate queues.Therefore the classification will work off the packets that are marked by CAR.Since 12.1(2)T this has changed: Now common classification happens

for all the features before the packets are marked by the CAR. This means that any attributes changed by CAR (for eg the "setting ip precedence")is not considered for classification purposes and hence the behaviour is different from 121-1a.T1.

This posed a major migration issue. The solution is to introduce a hidden command that will provide some limited backward compatibility.

Once enabled, common classification will occur after CAR has acted on the packets thereby giving the same behaviour as the 121-1a.T1 code.

This is relevant only when output CAR and output common classification are enabled. This knob will be known as "rate-limit llq-classify"and needs to be turned on at the global config level to force llq classification to happen after CAR has acted on the packets.

Hope it helps you.

Thanks,

Satish

1 REPLY
Silver

Re: rate-limit llq-classify

Hi ,

Need llq classification after rate-limit:

For this purpose they integrated rate-limit llq-classify feature CSCds30737.

Description :

Specifically from 121-1a.T1 to 121-3a.T3.

In 121-1a.T1 output CAR acts on the packets and these packets are then classfied by queueing feature for putting them in the appropriate queues.Therefore the classification will work off the packets that are marked by CAR.Since 12.1(2)T this has changed: Now common classification happens

for all the features before the packets are marked by the CAR. This means that any attributes changed by CAR (for eg the "setting ip precedence")is not considered for classification purposes and hence the behaviour is different from 121-1a.T1.

This posed a major migration issue. The solution is to introduce a hidden command that will provide some limited backward compatibility.

Once enabled, common classification will occur after CAR has acted on the packets thereby giving the same behaviour as the 121-1a.T1 code.

This is relevant only when output CAR and output common classification are enabled. This knob will be known as "rate-limit llq-classify"and needs to be turned on at the global config level to force llq classification to happen after CAR has acted on the packets.

Hope it helps you.

Thanks,

Satish

286
Views
0
Helpful
1
Replies
CreatePlease to create content