QoS/CoS TCPs using AE sub interfaces on a MX104

Hi Folks,

I have run into a problem where I am unable to apply CoS settings (specifically schedulers) to AE sub interfaces on an MX104 device. I have logged a tac call for this and they have mentioned that this will be a feature they will release in an upcoming version (15.2). 

What bothers me is that I find it hard to believe that we are the only guys trying to do this especially since there are articles out there explaining how to achieve this. Is there anyone out there that is successfully running this setup, if so what firmware version are you using? 

 Links to the articles mentioned.

http://www.juniper.net/techpubs/en_US/junos13.3/topics/reference/configuration-statement/hierarchical-scheduler-edit-cos.html

http://www.juniper.net/techpubs/en_US/junos15.1/topics/reference/configuration-statement/per-unit-scheduler-edit-interfaces.html

Here's a snippet of the relevant config including the error we get:

**omitted**@**omitted**# commit check
re1:
[edit class-of-service interfaces]
  'ae1'
    'per-unit-scheduler', 'hierarchical-scheduler', or 'shared scheduler' for this interface is required for output-traffic-control-profile configuration on interface unit
error: configuration check-out failed: (statements constraint check failed)

{master}[edit]
**omitted**@**omitted**# show | compare
[edit interfaces ae1]
+    unit 1059 {
+        description "**omitted**";
+        bandwidth 30m;
+        vlan-id 1059;
+        family inet {
+            address **omitted**;
+        }
+    }
[edit class-of-service traffic-control-profiles]
   
+   **omitted**-TCP {
+       scheduler-map **omitted**-SM;
+       shaping-rate 30m;
+       guaranteed-rate 20m;
+   }
[edit class-of-service interfaces]
+    ae1 {
+        unit 1059 {
+            output-traffic-control-profile **omitted**-TCP;
+        }
+    }
[edit class-of-service schedulers]
    
+   **omitted**-INTERNET {
+       transmit-rate percent 95;
+       buffer-size percent 95;
+       priority low;
+       drop-profile-map loss-priority any protocol any drop-profile INTERNET;
+   }
+   **omitted**-BEST-EFFORT {
+       transmit-rate percent 0;
+       buffer-size percent 0;
+       priority medium-low;
+       drop-profile-map loss-priority any protocol any drop-profile BUSINESS-BEST-EFFORT;
+   }
+  **omitted**-PRIORITY {
+       transmit-rate percent 0;
+       buffer-size percent 0;
+       priority medium-high;
+       drop-profile-map loss-priority any protocol any drop-profile BUSINESS-PRIORITY;
+   }
+   **omitted**-VVC {
+       transmit-rate percent 3;
+       buffer-size percent 3;
+       priority high;
+       drop-profile-map loss-priority any protocol any drop-profile VVC;
+   }
+   **omitted**-CONTROL {
+       transmit-rate percent 2;
+       buffer-size percent 2;
+       priority high;
+       drop-profile-map loss-priority any protocol any drop-profile NETWORK-CONTROL;
+   }
+   **omitted**-VOICE {
+       transmit-rate percent 0;
+       buffer-size percent 0;
+       priority strict-high;
+   }

Here's a simple diagram depicting what we are trying to achieve:

 Essentially we have connected two XE (10Gb/s) ports to a new core switch with an AE inbetween them. We would like to migrate all customer VRF interfaces to the AE sub interfaces for redundancy. Everything works except trying to apply a per-unit or a hierarchial-scheduler to the AE1.(x) sub interfaces.