[WPXperVideo id=127 ]in this tutorial we’re going to provide an overview of teledyne lecroy SAS sierra infusion capability this is an error injection system that’s designed to test error recovery at the system level it’s fully integrated within the sierra analyzer platform and it’s designed to sit in line between a real initiator and a target port and programmatically inject errors including symbol coding crc and disparity errors to verify that the system can recover properly fundamental to this type of testing is that you need to be transparent to the system under test where you’re running real workloads and then you modify traffic on the fly and then while the system is operating you inject errors or create marginal link conditions this way you can verify the error recovery and also see the impact at the system level this kind of error handling is built into the SAS protocol but you really need to verify that it’s working as designed and see the impact on performance this is an optional feature that’s built into the Sierra analyzer platform it sits in line and provides a lot of control over when the air occurs you can wait for specific link States or inject errors randomly it can also drop primitives or entire frames from the traffic this makes it easy to test all your timers from your open except to your credit timeout these are soft errors that may have only been tested in simulation now you can force them into the line during periods of heavy activity the stress test the system hackett modification is possibly the most powerful capability we have here you can change any field within the header or payload of a frame you can basically create countless protocol errors with this mechanism invalid addresses invalid commands length mismatch bad lbas literally any protocol error you can imagine you can create on top of that this is the only jammer on the market that can insert d words within a frame by extending the length of a frame you can now intercept a response frame change the status good to check condition and then insert the additional sense key and sense data to simulate basically dozens of different scuzzy level errors now is it possible to do this type of testing with a traffic generator probably but writing target emulation scripts much harder and of course it’s not real world with real traffic on the line to see the infusion jammer in action please download the next training segment where we’ll start with a simple crc error example and then cover some of the other cases including credit starvation for target ports and check condition handling for host controllers along the way we’ll see how the analyzer is an essential part of this testing because it lets you see and confirm the recovery behaviors including any Layton sees that are introduced

Please let us know...

Q 1. Which of the Following Devices You Need Help With?

  • Hard Drive
  • RAID Array
  • Memory Card / Stick
  • Cell Phone / Tablet

Next >

en_USEnglish es_MXSpanish