Hi Robert,<div><br></div><div>This limitation holds true for IPv4 and IPv6 as well, it does not change if you're not using IPv6. I double-checked on my device and even without any ipv6 config or ipv6 NDE, if you have a dest-only QoS microflow policer and NDE enabled, there's a flowmask conflict. I can give you the outputs in unicast if you're interested.</div>
<div><br></div><div>You have the following options if you would like to use UBRL:</div><div>- Disable Netflow only on the interface where microflow QoS should be applied, by removing 'ip flow ingress'.</div><div>- Use 'full-flow' mask instead of 'dest-only' in the QoS policy-map.</div>
<div><br></div><div>Feel free to check it yourself by using the 'sh fm fie int gi x/y' command and check the "Flowmask conflict status for protocol IP" line which should state FIE_FLOWMASK_STATUS_SUCCESS. If it shows something else, there's a conflict.</div>
<div><br></div><div>Best regards,</div><div>Andras</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Dec 9, 2012 at 7:03 PM, Robert Williams <span dir="ltr"><<a href="mailto:Robert@custodiandc.com" target="_blank">Robert@custodiandc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div style="PADDING-BOTTOM:1em;PADDING-LEFT:1em;PADDING-RIGHT:1em;PADDING-TOP:1em"><font face="Arial"><font><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi Andras,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Yes that has indeed applied without error, however as you point out it does not meet with the requirements I have from the customer. In short, the customer needs a limit which is applied per IP (of his clients) to restrict inbound traffic in the direction Internet->Client. This is because downstream of us the client has several links which are only 1GB serving large numbers of his clients. I know there are several ways this could be resolved (not least of which a switch upgrade within the client’s network) however they are not currently options so we are trying to come up with something for them which we can deploy ahead of their connection with us.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">My understanding of the full-flow mask is that it will limit flow, only, so two transfers to the same IP will count as 2 x the limit. Which in this scenario makes it inappropriate unfortunately.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">So, it looks like we will have to deploy it for IPv4 for them only; and skip IPv6, which is a shame because the client is a growing IPv6 user so I can see the problem surfacing again soon.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Interestingly, can anyone confirm that the Sup-2T can do what we are trying to do without this IPv6 oddness?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Once again, my thanks to you!<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Tóth András [mailto:<a href="mailto:diosbejgli@gmail.com" target="_blank">diosbejgli@gmail.com</a>] <br>
<b>Sent:</b> 09 December 2012 17:16</span></p><div><div class="h5"><br><b>To:</b> Robert Williams<br><b>Cc:</b> cisco-nsp NSP<br><b>Subject:</b> Re: [c-nsp] Multiple flow-masks<u></u><u></u></div></div><p></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Hi Robert,<u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Thanks for the clarification. What I meant is that QoS microflow policy which needs to have full-flow mask, otherwise you might likely have a conflict with NDE. I understand that it's a requirement for you to have destination based policing.<u></u><u></u></p>
</div><div><p class="MsoNormal">In addition to that, if the NDE flowmask is interface-full-flow, it will not work with QoS microflow policing.<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div>
<p class="MsoNormal">Try configuring the following:<u></u><u></u></p></div><div><div><p class="MsoNormal">mls flow ip interface-destination-source<u></u><u></u></p></div><div><p class="MsoNormal">mls flow ipv6 full<u></u><u></u></p>
</div></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><div><p class="MsoNormal">policy-map test-policy<u></u><u></u></p></div><div><p class="MsoNormal"> class class-default<u></u><u></u></p></div><div><p class="MsoNormal">
police flow mask full-flow 200000000 512000 conform-action transmit exceed-action drop<u></u><u></u></p></div></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">This should work but this will use full-flow mask for the QoS.<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Best regards,<u></u><u></u></p></div><div><p class="MsoNormal">Andras<u></u><u></u></p></div><div><p class="MsoNormal" style="margin-bottom:12.0pt">
<u></u> <u></u></p><div><p class="MsoNormal">On Sun, Dec 9, 2012 at 4:36 PM, Robert Williams <<a href="mailto:Robert@custodiandc.com" target="_blank">Robert@custodiandc.com</a>> wrote:<u></u><u></u></p><div><div><p class="MsoNormal">
<span style="font-family:"Courier New"">Hi Andras,<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal">
<span style="font-family:"Courier New"">Many thanks for that – sorry the outputs were misleading but I have already tried all 6 variants of the mls flow ipv6 <…> command, including "mls flow ipv6 full" – they all produce the same results, culminating in the %FM-2-FLOWMASK_CONFLICT error.<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">I have removed all other policies off the device to rule them out, so a clean test / demonstration of the issue is as follows:<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">mls commands currently set:<u></u><u></u></span></p>
</div><div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">mls ipv6 acl compress address unicast<u></u><u></u></span></p>
</div></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">mls netflow interface <- (there is no non-interface version of this command)<u></u><u></u></span></p></div><div>
<div><p class="MsoNormal"><span style="font-family:"Courier New"">mls nde sender<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">mls qos<u></u><u></u></span></p>
</div></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">mls flow ip interface-destination-source <- (there is no version of this command which doesn’t include the ‘interface’ keyword for ipv4)<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">mls flow ipv6 full<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">flow commands currently set:<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">ip flow-export source xx<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">ip flow-export version 9<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">ip flow-export destination x.x.x.x xxxx<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">ip flow-top-talkers<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div>
<div><p class="MsoNormal"><span style="font-family:"Courier New"">With all the above in place, I do get the Full Flow mask as you say:<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv6: 0 reserved none<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv6: 1 Full Flo FM_IPV6_GUARDIAN <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv6: 2 Null <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv6: 3 reserved none<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Plus there is a space in slot 2 - however, when I try to apply my policy:<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">policy-map test-policy<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> class class-default<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> police flow mask dest-only 200000000 512000 conform-action transmit exceed-action drop<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">interface xx<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">service-policy input test-policy<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">I still get: %FM-2-FLOWMASK_CONFLICT: Features configured on interface xx have conflicting flowmask requirements, traffic may be switched in software<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">My policy has to be destination based so I cannot change that, but apart from that I think I'm trying what you are describing, but my apologies if I'm still missing the point!<u></u><u></u></span></p>
</div><div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Cheers!<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div>
<div><p class="MsoNormal"><span style="font-family:"Courier New"">From: Tóth András [<a href="mailto:diosbejgli@gmail.com" target="_blank">mailto:diosbejgli@gmail.com</a>] <u></u><u></u></span></p></div></div><div>
<p class="MsoNormal"><span style="font-family:"Courier New"">Sent: 09 December 2012 14:47<u></u><u></u></span></p></div><div><div><div><p class="MsoNormal"><span style="font-family:"Courier New"">To: Robert Williams<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Cc: cisco-nsp NSP<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Subject: Re: [c-nsp] Multiple flow-masks<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">The outputs you pasted suggests that you're using "interface-full" flowmask. The workaround is to use "full" flowmask instead of "interface-full" as mentioned in my last email. IPv6 entries consume more TCAM space than IPv4, so comparing them should take this fact into account.<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Best regards,<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Andras<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">On Sun, Dec 9, 2012 at 2:52 PM, Robert Williams <<a href="mailto:Robert@custodiandc.com" target="_blank">Robert@custodiandc.com</a>> wrote:<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Hi,<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div>
<div><p class="MsoNormal"><span style="font-family:"Courier New"">Thanks very much for that, I’ll have to run through everything in that document because the tests I’m doing suggest that it ‘should’ work, for example: <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">With both my policy and the mls ipv6 flow interface-full disabled I see one entry, which is presumably because ‘mls qos’ is enabled:<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv6: 1 Intf Ful FM_IPV6_QOS <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv6: 2 Null <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Then if I enable only “mls ipv6 flow interface-full”, the FM_IPV6_GUARDIAN ‘feature’ appears:<u></u><u></u></span></p></div><div><p class="MsoNormal">
<span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv6: 1 Intf Ful FM_IPV6_GUARDIAN FM_IPV6_QOS <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv6: 2 Null <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">As you can see there is still a gap for the policy to take the second flow mask and use whatever type of mask it wants.<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">As a test - if I disable the ipv6 flow and just enable my policy by itself, it goes in the second slot correctly - and uses the Destination Only mask:<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv6: 1 Intf Ful FM_IPV6_QOS <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv6: 2 Dest onl FM_IPV6_QOS<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">So, I was assuming that a combination of these two features would be acceptable to it, since they operate in different mask slots when enabled separately anyway I didn’t see why they should collide.<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">I am correct as far as its operation in IPv4 goes because for v4 there is no conflict warning (and the policy works in hardware perfectly!). However, in IPv6 that does not appear to be the case.<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Looks like yet another unhappy IPv6 feature on the Sup-720, unless anyone can see a way around it that I’m missing?<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">As an aside, does anybody know why it is called FM_IPV6_GUARDIAN instead of FM_IPV6_QOS (like in v4)? I’m wondering if this difference is the reason for its inability to combine the two masks successfully…<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Cheers!<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">From: Tóth András [<a href="mailto:diosbejgli@gmail.com" target="_blank">mailto:diosbejgli@gmail.com</a>] <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Sent: 08 December 2012 21:09<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">To: Robert Williams<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Cc: cisco-nsp NSP<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Subject: Re: [c-nsp] Multiple flow-masks<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Hi Robert,<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">A few things to keep in mind.<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">With Release 12.2(33)SXI4 and later releases, when appropriate for the configuration of the policer, microflow policers use the interface-full flow mask, which can reduce flowmask conflicts. Releases earlier than Release 12.2(33)SXI4 use the full flow mask.<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">The flowmask requirements of QoS, NetFlow, and NetFlow data export (NDE) might conflict, especially if you configure microflow policing.<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""><a href="http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/qos.html" target="_blank">http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/qos.html</a><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">To add to this, note the following restrictions/recommendations well:<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">The micro-flow policing full flow mask is compatible with NDE’s flow masks that are shorter than or equal to full flow (except for destination source interface).<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">With any micro-flow policing partial mask an error message is displayed and either the micro-flow policer or NDE might get disabled.<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Best regards,<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Andras<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">On Sat, Dec 8, 2012 at 3:50 PM, Robert Williams <<a href="mailto:Robert@custodiandc.com" target="_blank">Robert@custodiandc.com</a>> wrote:<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Hi,<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div>
<div><p class="MsoNormal"><span style="font-family:"Courier New"">Unfortunately we use Netflow for an automated system we have (it doesn't need to accurately record everything, just the highest number of flows / packets etc). So I cannot just remove it, however I have made some progress.<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">I've tracked it down to the problem actually being with the IPv6 netflow / masks. With all netflow removed I am able to add my policy-map in and it works. Then by adding netflow commands back in I can get everything back except the command:<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> mls flow ipv6 <any command><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">So even if I specify:<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> mls flow ipv6 destination<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">I still get:<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">%FM-2-FLOWMASK_CONFLICT: Features configured on interface <name> have conflicting flowmask requirements, traffic may be switched in software<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">At this point in time, with my policy attached and working I'm showing:<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> Flowmasks: Mask# Type Features<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv4: 0 reserved none<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv4: 1 Intf Ful FM_QOS Intf NDE L3 Feature<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv4: 2 Dest onl FM_QOS <--- My policy (V4)<u></u><u></u></span></p></div><div><p class="MsoNormal">
<span style="font-family:"Courier New""> IPv4: 3 reserved none<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv6: 0 reserved none<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv6: 1 Intf Ful FM_IPV6_QOS<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> IPv6: 2 Dest onl FM_IPV6_QOS <--- My policy (V6)<u></u><u></u></span></p></div><div><p class="MsoNormal">
<span style="font-family:"Courier New""> IPv6: 3 reserved none<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">The command "mls flow ipv6 <anything>" just plain refuses to go active in the config, so if I re-send it I get the error shown above every time.<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">The flowmasks are correctly showing "Intf Full" and "Dest only" in slots 1 and 2 respectively. So, why does my netflow request not attach alongside either one of them when it's looking for the same mask as is already active in those slots?<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">The policy itself is working correctly at this point, but I cannot enable IPv6 netflow.<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Can anyone help?<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Robert Williams<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Backline / Operations Team<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Custodian DataCentre<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">tel: <a href="tel:%2B44%20%280%291622%20230382" target="_blank">+44 (0)1622 230382</a><u></u><u></u></span></p></div><div><p class="MsoNormal">
<span style="font-family:"Courier New"">email: <a href="mailto:Robert@CustodianDC.com" target="_blank">Robert@CustodianDC.com</a><u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""><a href="http://www.custodiandc.com/disclaimer.txt" target="_blank">http://www.custodiandc.com/disclaimer.txt</a><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Robert Williams<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Backline / Operations Team<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">Custodian DataCentre<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">tel: <a href="tel:%2B44%20%280%291622%20230382" target="_blank">+44 (0)1622 230382</a><u></u><u></u></span></p></div><div><p class="MsoNormal">
<span style="font-family:"Courier New"">email: <a href="mailto:Robert@CustodianDC.com" target="_blank">Robert@CustodianDC.com</a><u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""><a href="http://www.custodiandc.com/disclaimer.txt" target="_blank">http://www.custodiandc.com/disclaimer.txt</a><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><br><b><span style="color:gray">Robert Williams</span></b></span><span style="font-family:"Courier New""><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:gray">Backline / Operations Team</span><span style="font-family:"Courier New""><u></u><u></u></span></p></div>
<div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:gray">Custodian DataCentre</span><span style="font-family:"Courier New""><u></u><u></u></span></p></div><div><p class="MsoNormal">
<span style="font-family:"Arial","sans-serif";color:gray">tel: <a href="tel:%2B44%20%280%291622%20230382" target="_blank">+44 (0)1622 230382</a></span><span style="font-family:"Courier New""><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:gray">email: <a href="mailto:Robert@CustodianDC.com" target="_blank">Robert@CustodianDC.com</a></span><span style="font-family:"Courier New""><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><a href="http://www.custodiandc.com/disclaimer.txt" target="_blank">http://www.custodiandc.com/disclaimer.txt</a><br><br></span><span style="font-family:"Courier New""></span></p>
</div></div></div></div></div></div></div></div></div></font><div><div class="h5"> <br>
<p><font color="#808080" face="Arial"><strong>Robert Williams</strong></font></p>
<p><font color="#808080" face="Arial">Backline / Operations Team</font></p>
<p></p>
<p></p>
<p></p>
<p></p>
<p></p>
<p></p>
<p></p></div></div></font>
<table border="0" cellpadding="0" cellspacing="0" style="BORDER-COLLAPSE:collapse" width="900">
<tbody>
<tr>
<td nowrap style="PADDING-RIGHT:1em" width="300">
<p><font face="Arial"><strong><font color="#be5c2c"></font></strong><a href="http://www.CustodianDC.com/" target="_blank"><img align="baseline" alt="Custodian DataCentre" border="0" hspace="0" src="cid:imageb9d65d.jpg@acf57610.0c8a4454"></a></font></p>
</td>
<td style="BACKGROUND-COLOR:#a3b901;WIDTH:0.3em">
<p><font style="BACKGROUND-COLOR:#a4ba00"></font></p></td>
<td nowrap style="padding-right:1em;padding-left:1em" width="300">
<p>
</p><table border="0" cellpadding="0" cellspacing="0" name="d152bf90-79e0-4ab1-a59e-10bb3b622505excontact" style="BORDER-COLLAPSE:collapse">
<tbody>
<tr>
<td>
<p align="right"><strong><font><font face="Arial"><font color="#808080"><font color="#333333">Tel:</font> </font></font></font></strong></p></td>
<td>
<p><font color="#a3b901" face="Arial"><strong><a href="tel:%2B44%20%280%291622%20230%20382" value="+441622230382" target="_blank">+44 (0)1622 230 382</a></strong></font></p></td></tr>
<tr>
<td>
<p align="right"><strong><font><font face="Arial"><font color="#333333">Email: </font></font></font></strong></p></td>
<td><font color="#00aeef" face="Arial"><a href="mailto:support@CustodianDC.com" style="TEXT-DECORATION:none" target="_blank"><font color="#a3b901" face="Arial"><strong>Robert@CustodianDC.com</strong></font></a></font></td>
</tr>
<tr>
<td>
<p align="right"><strong><font><font face="Arial"><font color="#333333">Web: </font></font></font></strong></p></td>
<td>
<p><a href="http://www.CustodianDC.com/" style="TEXT-DECORATION:none" target="_blank"><font color="#a3b901" face="Arial"><strong>www.CustodianDC.com</strong></font></a></p></td></tr>
<tr>
<td>
<p align="right"><strong><font><font face="Arial"><font color="#333333">Status: </font></font></font></strong></p></td>
<td>
<p><a href="http://status.custdc.net/" style="TEXT-DECORATION:none" target="_blank"><font color="#a3b901" face="Arial"><strong>status.CustDC.net</strong></font></a></p></td></tr></tbody></table><p></p></td>
<td style="BACKGROUND-COLOR:#a3b901;WIDTH:0.3em">
<p></p></td>
<td nowrap style="padding-right:1em;padding-left:1em" width="175">
<p align="center"><strong><img align="baseline" alt="" border="0" hspace="0" src="cid:image9e7fb8.png@d5057fdf.12c14486"><br><font face="Arial">ISO:27001 IS:567248</font></strong></p></td></tr></tbody></table>
<p></p>
<p></p><font face="Arial"><a href="http://www.custodiandc.com/disclaimer.txt" target="_blank"><font color="#000000" size="1">Click to view our email disclaimer</font></a><div class="im"><br><br><div><div><div><div><div><div>
<div><p class="MsoNormal"><span style="font-family:"Courier New"">_______________________________________________</span></p></div></div></div></div></div></div></div><div><div><div><div><div><div><div><p class="MsoNormal">
<span style="font-family:"Courier New""><u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New"">cisco-nsp mailing list <a href="mailto:cisco-nsp@puck.nether.net" target="_blank">cisco-nsp@puck.nether.net</a><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""><a href="https://puck.nether.net/mailman/listinfo/cisco-nsp" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-nsp</a><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New"">archive at <a href="http://puck.nether.net/pipermail/cisco-nsp/" target="_blank">http://puck.nether.net/pipermail/cisco-nsp/</a><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div>
<div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Courier New""> <u></u><u></u></span></p></div></div>
</div></div></div><p class="MsoNormal"><u></u> <u></u></p></div></div></div></font>
<p></p>
<p></p>
<p></p>
<p></p>
<p></p>
<p></p>
<p></p>
<p></p></div></div></blockquote></div><br></div>