Customer Service Center

Objective/Summary Spirent TestCenter streams by default has a signature and increments the IP identifier field. Spirent TestCenter stream results windows look for the signature when updating the counters. So how does Spirent create duplicate streams with a non changing signature and non changing IP identifier? Environment/Versions Spirent TestCenter PGA Streams Realtime Results Procedure To create a duplicate packet that will be able to shown in a stream results RX counter Create a signature packet to be the template of the duplicates. Send a single packet, capture this packet, then save this capture file. Uncheck "Exclude Ethernet FCS" from Settings->Traffic, Generate Stream Block Setting. In the generator of the port, click on Generate Stream Block using the saved capture. Uncheck "High Speed Results Analysis" from the newly created stream block. (this causes IP identifier to remain constant) Right click and either copy or duplicate it as many times as you need. (alternative is to retransmit the stream block) Notes These procedures create a static signature packet and thus will be considered a duplicate but yet has a signature to be seen by the realtime results. some things to be aware of: The stream ID is now static and will not change. The results will show this new stream to only be received on the designated stream with that stream ID. The results will show each duplicate to have its own stream ID which will most likely be different from the static ID that is in the signature. Thus the results will show Tx count on the stream block but the Rx will be shown on the designated stream that has the static ID. if this is confusing, you will come to understand it once you try to create a duplicate frame. These procedures were developed while working with the DX module. other modules may have different behavior Issue found with 400G modules which cannot uncheck HSRA (High Speed Results Analysis). In this case you need to create Custom payloads for both the IP header as well as the remainder of the packet. Attached is such a config which should work for all modules including 400G, except please note that some modules do not support the duplicate counter and you can only verify the duplicate through capture. 400G "DOES NOT" support the duplicate counter. Attachments Attachment DuplicateFrames2.tcc