It's as Georg notes, i.e. FQ is no longer an interface command, instead we use CBWFQ (often with a simple policy, like the one Georg shows).
It's likely in the documentation that Georg references, but besides defining a policy map with FQ in it, you need to apply the policy to the interface (as an out policy).
BTW:
policy-may your-name
class class-default
fair-queue
Is likely all the policy defining commands you need.
Also, BTW, the later (since HQF) CBWFQ's classes FQ implementations are just FQ, not WFQ, which is what the interface FQ command provided. If this is an issue, you would need to define multiple classes and apportion their bandwidth allocations to obtain similar results.
