– “Layer 2 testing” on page 29
– “Layer 3 testing” on page 61
– “Capturing packets for analysis” on page 74
– “Loopback testing” on page 86
– “Inserting errors or pause frames” on page 86
– “Measuring round trip delay or packet jitter” on page 87
– “Measuring service disruption time” on page 88
– “OAM service and link layer testing” on page 89
– “MAC-in-MAC testing” on page 95
– “Synchronous Ethernet testing” on page 102
– “Transmitting and analyzing PTP/1588 traffic” on page 103
About Ethernet and IP testing
If your instrument is configured and optioned to do so, you can use it to provi- sion Ethernet and IP service, verify end-to-end connectivity, and analyze link performance by simulating different traffic conditions.
Features and capabilities
Features and capabilities include the following when testing Ethernet or IPservice:
– 10/100/1000, 1 Gigabit Ethernet, 10 Gigabit LAN, and 10 Gigabit WAN testing—Testing on each of theses circuits is supported.
– JDSU Discovery—You can automatically detect other JDSU test equip- ment on the network, and determine their services and capabilities. For details, see “Discovering another JDSU test instrument using J-Connect” on page 23.
– Cable diagnostics—You can use the T-BERD ⁄ MTS 5800 to examine the state of the cables used to transmit 10/100/1000 electrical signals before you begin testing. For details, see “Cable Diagnostics” on page 20. – Automatic traffic transmission—You can optionally set up optical Ethernet,
IP, and TCP/UDP Traffic, Multiple Streams, and Triple Play applications to generate and transmit traffic automatically whenever you turn the laser on. – BERtesting—You can verify circuit performance by sending BERT
patterns over switched (layer 2) and unswitched (layer 1) networks. You can also configure ATP payloads carrying a BERT pattern.
– Multiple source MAC addresses—When transmitting a single stream of Layer 2 traffic, you can simulate traffic from multiple sources by assigning a range of MAC addresses to be carried in the frames transmitted in the stream.
– Layer 2 transparency testing—You can transmit and analyze layer 2 traffic with CDP, VTP, STP, and R/STP headers to verify that a circuit can support a variety of control protocols irrespective of the transport method. For details, see “Using J-Proof to verify layer 2 transparency” on page 57. – Automated VLAN testing—An automated VLAN test is available that tests
a range of VLANs by transmitting and looping back frames for each VLAN in the range for a user-specified test period, and then comparing the number of frames transmitted to the number received. For details, see
“Automated VLAN tests” on page 202.
– Layer 3 testing—You can perform end to end tests to verify throughput. You can also:
– Transmit packets and determine if any are lost when looped back to your instrument.
– Filter traffic using layer 3 criteria. – Measure round trip delay.
– Send ping requests and respond to ping requests from another Ethernet device to verify connectivity.
– Record and observe the route of traffic through the network using the Traceroute application.
– Insert IP checksum errors into the traffic stream. – Insert Acterna payload errors into the traffic stream.
– PPPoE support—You can configure your unit to emulate a PPPoE client or server, login to a PPP peer to establish a PPPoE session, and then transmit IPv4 packets over an Ethernet circuit for analysis. For details, see
“Specifying the data mode and link initialization settings” on page 61 and
“Specifying PPPoE settings” on page 62.
– IPv6 support—If you purchased the IPv6 Traffic option, you can transmit and analyze IPv6 traffic using the terminate and monitor/thru applications. When configuring your test, you can specify the required addresses manu- ally, or you can use stateless or stateful auto-configuration to assign addresses for you.
– Packet capture and analysis—If your instrument is configured and
optioned to do so, you can use it to capture transmitted and received data, save it on the instrument or to a USB key, and then either send the data to another technician for analysis, or analyze it yourself using the Wireshark® protocol analyzer (provided on the instrument). For details, see “Capturing packets for analysis” on page 74.
– MPLS and VPLS testing—If you purchase the MPLS/VPLS test option, you can configure your unit to generate, transmit, and analyze MPLS and VPLS encapsulated frames when testing and qualifying core and metro networks. For details, see “Configuring MPLS over Ethernet tests” on page 18 and “Configuring Ethernet VPLS tests” on page 17.
– Q-in-Q testing—You can configure, transmit, and analyze traffic carrying SVLAN and CVLAN tags per IEEE 802.1ad to verify that your network can support and prioritize traffic for multiple customers without conflicts. You can also specify a user-defined TPID for the service provider when trans- mitting and filtering Q-in-Q encapsulated traffic. For details, see “Config- uring Q-in-Q traffic” on page 36.
– MiM testing—If you purchase the MiM testing option, you can transmit and analyze MAC-in-MAC Ethernet traffic over a PBB (Provider Backbone Bridged) network to verify end-to-end connectivity, and analyze link perfor- mance. For details, see “MAC-in-MAC testing” on page 95.
– Link and service layer OAM testing—OAM messages are supported, enabling you to identify trunk problems so you can initiate a switch to a protection path. When testing Ethernet First Mile OAM communications, you can loopback an adjacent node or Ethernet demarcation device (EDD), and then exchange messages with the node or device to verify that auto-discovery and error notification are functioning properly. For details, see “OAM service and link layer testing” on page 89.
– Test Access Management (TAM)—If your instrument is configured and optioned to do so, you can now use it to remotely log into and provision network elements such as switches and routers from a Mobility Switching Center (MSC). You can also use your instrument to emulate a router on the network end of the Ethernet Transport Service (ETS), run an RFC 2554 script to put a Network Interface Device (NID) in loopback mode, transmit traffic, then analyze looped back traffic to determine link characteristics such as throughput and latency. For details, see “Testing using TAM automation” on page 211 of Chapter 8 “Automated Testing”. – Stacked VLAN—You can configure, transmit, and analyze L2 traffic
carrying SVLAN and CVLAN tags per IEEE 802.1ad to verify that your network can support and prioritize traffic for multiple customers without conflicts. You can also specify a user-defined TPID for the service provider when transmitting and filtering stacked VLAN encapsulated traffic. For details, see “Configuring stacked VLAN traffic” on page 37.
– Trigger support. The instrument supports packet capture based on a trig- gering event. For details, see “Capturing packets based on a trigger” on page 79.
– Filter on byte pattern. The instrument supports filtering on a 16-byte pattern. For details, see “Filtering traffic using byte pattern criteria” on page 44.
Understanding the graphical
user interface
When you configure your instrument for testing, graphical displays of Ethernet frames and IP packets are provided on the setup tabs for the application you selected. You can specify frame or packet characteristics for transmitted and filtered traffic by selecting the corresponding field on the graphic, and then entering the value for transmitted or filtered traffic. Colored fields can be edited; fields in grey can not be modified.
Frame settings Figure 2 illustrates the frame settings for a layer 2 traffic test, with the Data field selected.
For details on each of the settings, see “Specifying Ethernet frame settings” on page 32 and “Specifying Ethernet filter settings” on page 38.
Packet settings Figure 3 illustrates the IP packet settings for a layer 3 traffic test.
For details on each of the settings, see “Specifying transmitted IPv4 packet settings” on page 65 and “Specifying IPv4 filter settings” on page 66.
Figure 2
Frame Settings
Ethernet and IP test
applications
This release supports the layer 2 and layer 3 applications listed in Table 5. – NewGen module applications are listed in the PDH, SONET, and SDH
Testing Manual that shipped with your instrument.
– MiM applications are listed in Table 7 on page 16.
– Layer 4 TCP/UDP applications are listed in Table 14 on page 115 of