More generically, whatever version you specify in the mls nde sender CLI is completely overridden when you enter the ip flow-export version 9 CLI (intuitive, I know), and both the h/w & s/w flows will export in v9 format.
tstevens-6509e(config)#mls nde send ver 5 tstevens-6509e(config)#do sh mls nde | in Ver Version: 5 tstevens-6509e(config)#ip flow-export vers 9 tstevens-6509e(config)#do sh mls nde | in Ver Version: 9 tstevens-6509e(config)#mls nde send tstevens-6509e(config)#no ip flow-export vers 9 tstevens-6509e(config)#do sh mls nde | in Ver Version: 7 tstevens-6509e(config)#ip flow-export vers 9 tstevens-6509e(config)#do sh mls nde | in Ver Version: 9 tstevens-6509e(config)# Tim At 10:26 AM 6/7/2007 -0700, Ian Cox opined: >At 12:00 PM 6/6/2007 -0400, Jeff Fitzwater wrote: > >MLS has no commands to enable version 9. CISCO states that you do not > >use MLS for version 9. Does that mean I cannot get hardware switches > >flows for version 9? Maybe I should use version 5 which is supported > >in MLS. > >Enable version 5 for mls nde, then it will export the hardware flows >in version in v9 format. For v9 with SXF, the template that will get >used to export the hardware switched traffic will be based upon the >flow mls flow mask set. Tim Stevenson, [EMAIL PROTECTED] Routing & Switching CCIE #5561 Technical Marketing Engineer, Data Center BU Cisco Systems, http://www.cisco.com IP Phone: 408-526-6759 ******************************************************** The contents of this message may be *Cisco Confidential* and are intended for the specified recipients only. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
