From what I remember, the docsDevFilterLLCProtocol only supports ARP and IPv4. To be able to filter IPv6 you need to use Upstream Drop Classifiers. So possibly if you are wanting to permit only IPv6 you could deny all via docsDevFilterLLCProtocol and IPv6 should still work. I haven't tried this though.
able to get their filters working by removing the line option 11 .docsDevFilterLLCStatus.1,INTEGER,active from each of the filter instances,I’m puzzled as to what the real meaning of option 11 .docsDevFilterLLCStatus.1,INTEGER,active
From what I remember, the docsDevFilterLLCProtocol only supports ARP and IPv4. To be able to filter IPv6 you need to use Upstream Drop Classifiers. So possibly if you are wanting to permit only IPv6 you could deny all via docsDevFilterLLCProtocol and IPv6 should still work. I haven't tried this though.
able to get their filters working by removing the line option 11 .docsDevFilterLLCStatus.1,INTEGER,active from each of the filter instances,I’m puzzled as to what the real meaning of option 11 .docsDevFilterLLCStatus.1,INTEGER,active
if docsDevFilterLLCProtocolType.1 = 1 (ethertype)
then the corresponding ethertype for ipv6 is 0x86DD which in decimal is: 34525
so setting docsDevFilterLLCProtocol.1 to 34525 should do what you want.
With this filter in the dynamic template, CM devices get stuck in the “init6(o)” state