Hi !
There is a new bug in the above mentioned version which took us 2-3 hours to find:
Preface: since recent when you define "set chassis aggegated-interfaces Ethernet device-count 23"you are not longer bound to ae0 up o ae22 but you can freely chose your interface number as long as the amount of AEs is below the stated number and commit only gives an error if the amount of aes is higher than the device-count.
At least this is only partly true as:
Our customer wanted to set the ae-numbers equal to the main VLAN numbers so he created ae1337 and attached 2 physical interfaces to that ae.The ae1337 came up, LACP worked as planned, but only LLDP packets from the switch could be seen on the attached server.
We first blamed the server, the bonding, the server interfaces, the SFPs....
BUT
After 2-3 hours of testing every possible and impossible cause we found out, that for ae numbers > around 500 the forwarding of packets from the physical interface unit to the ae unit does not work.
The only visible indication is that the counters on the ge-x/y/z.0 interfaces of the ae are incrementing whereas the ae1337.0 counters stay at 0, but the ae1337 physical interface counters show packets in and out.
Changing the ae number to a number below around 500 everything works fine again
Commit or any log does not state any error.
So my result:s
1. it is a bug, as you can specify interface numbers > 500 but they are not working
2. the control mechanism at commit does not detect it
3. it is very very complicated to find
therefore
4. do not use ae numbers higher than around 500
5. hopefully someone@juniper will forward this to engineering
regards
Alexander