Acterna FST-2310

ATM Testing Application Note

OVERVIEW

Over the past few years, there has been an explosion in the growth of Internet usage. As more users gain access to high-speed connections and more applications requiring large amounts of bandwidth are developed, the demand for fast, reliable communications between end users increases. The rapid deployment of Intranets, Extranets, and Virtual Private Networks (VPNs) is also driving demand for communications technologies to connect multiple users in different geographical areas. Asynchronous Transfer Mode (ATM) was developed to answer the need for increased bandwidth, seamless internetworking, and a common format for services with different bandwidth requirements. ATM is a method of formatting, switching, and multiplexing information using fixed-length cells. This technology allows for the simultaneous transmission of voice, video, and data over the same network. Because it grew from Broadband Integrated Services Data Network (B-ISDN) standards, ATM operates on existing transport technologies worldwide. It is currently an international standard administered by the ITU, ANSI, and the ATM Forum.

Traditional communication networks (Figure 1) dedicate separate technologies and systems to each application. Frame relay, used for data communications, requires specific frame relay switching equipment. Traditional voice networks use one type of switch, while video networks typically require other types of equipment. In traditional networks, installing, provisioning, maintaining, and interconnecting multiple networks is both complex and costly. An ATM network, on the other hand, has many advantages over other technologies because it combines all types of traffic and applications into a single network (Figure 2). ATM makes it possible for LANs and WANs to use a common technology with minimal adjustments when changes or improvements are needed. ATM traffic is scaleable to higher speeds and can operate over a DS1, DS3, or high-speed SONET backbone without modifying the cell format. Because ATM is asynchronous, voice, video, and data applications can run simultaneously. Combining applications allows the network to allocate bandwidth on-demand for greater efficiency.

Router

Frame Relay

Router

Mux

T-Carrier SONET Network

Mux

ISDN PRI Line Video Conferencing

Figure 1. Traditional networks use different technologies for each application.

Video Conferencing

LAN

ATM/LAN Router ATM

ATM/LAN Router ATM

LAN

ATM Mux ATM Network

ATM IAD

ATM

Video Conferencing
Figure 2. The ATM network combines technologies.

Video Conferencing

ATM FUNDAMENTALS
ATM Cell Structure
An ATM network converts a bit stream of data (voice and video are also considered data) into discrete cells for transmission, and then it reassembles the data into its original form when it reaches its destination. ATM cells are based on a fixed-length, 53-byte cell. An ATM cell follows a route to its destination that is mapped by the ATM switches it passes through. Two cell structures are used in an ATM network, including the User Network Interface (UNI) and the Network to Node Interface (NNI). UNI cells transport data between the customer premises equipment and an ATM network switch. NNI cells carry data between ATM switches within a network. The first five bytes of both types of ATM cell structures contain address, error checking, and control information. These five bytes are referred to as header space. The remaining 48 bytes are allocated to the customers payload, which can be voice, video, or data signals. The structure of a UNI cell is illustrated in Figure 3, and the purpose of each field in the header is identified.
8 7 GFC VPI VCI VCI HEC PT CLP 6 ATM UNI Cell 5 4 3 VPI VCI 2 1 Byte 1 2 3 4 5 6 Information Payload (48 bytes) 53 Notes: GFC: Generic Flow Control VPI: Virtual Path Identifer VCI: Virtual Channel Identifer PT: Payload Type CLP: Cell Loss Priority HEC: Header Error Control

Figure 3. The ATM UNI cell.

Elements of an ATM UNI Cell

Generic Flow Control As of the time of this printing, standards are being developed for the Generic Flow Control (GFC) field. The GFC field is used to prioritize and control traffic flow when multiple devices share a common access . Virtual Path Identifier and Virtual Channel Identifier The Virtual Path Identifier (VPI) and Virtual Channel Identifier (VCI) fields identify specific cell addresses that will be used for cell switching. The VPI and VCI structure within the carrier signal is shown in Figure 4. The carrier signal is the physical transport signal (SONET, DS3, or DS1) used to transport ATM cells between Network Elements (NEs). An ATM cell may have several different VPI/VCI addresses as it is transported through a network since each ATM switch can assign a new address to the cell as it passes through the switch. This new address is significant to that specific ATM switch. Therefore, the ATM cell address does not necessarily indicate the source or destination of the data. Payload Type Identifier The Payload Type Identifier (PTI) indicates whether the cell payload contains user data cells or Operation, Administration, and Maintenance (OAM) cells. The PTI also carries traffic congestion notification information. The table below contains the definitions of the different PTI values.
PTI Value 000 001 010 011 100 101 110 111 Definition

Cell Loss Priority The Cell Loss Priority (CLP) field is used for traffic control and is set to either 0 or 1. When it is set to 1, the cell has a low priority, allowing switches to drop the cell if the network becomes congested. Header Error Control The Header Error Control (HEC) field is used for error detection and allows for some error correction capability. HEC is calculated from the first four bytes of the header and not from the payload. A correctable HEC error occurs when a single error exists in the header. Cells with a correctable HEC error should be corrected by the ATM switch. A non-correctable HEC error occurs when multiple errors exist in the header. Cells with non-correctable HEC errors should be dropped by the ATM switch.

User cell, no congestion encountered, user-to-user indication = 0 User cell, no congestion encountered, user-to-user indication = 1 User cell, congestion encountered, user-to-user indication = 0 User cell, congestion encountered, user-to-user indication = 1 OAM end-to-end associated cell OAM end-to-end associated cell Reserved for future use

Carrier signal Carrier channel

Virtual path

Figure 4. The carrier signal containing virtual paths and virtual channels.

Elements of an ATM NNI Cell

An NNI cell contains the same information as a UNI cell, but it has a slightly different cell structure. Instead of the GFC field, the NNI cell adds four bits to the VPI field. before transporting. OC-3c and OC-12c ATM can only support HEC cell alignment. DS1 and DS3 ATM support both HEC and PLCP cell alignment.

ATM Network Components

ATM is a service that requires a backbone transport signal such as DS3 or SONET. The customers traffic (voice, video, or data) is converted into ATM cells by means of an ATM edge device. The traffic is then switched through an ATM edge switch or sent directly to the DS3 or SONET transport signal. An ATM backbone switch in the central office may further switch ATM cells as well as provide a connection to other service providers. Figure 5 illustrates the components of an ATM network transported over a SONET backbone.

ATM Cell Payload ATM Cell Alignment

The purpose of cell alignment is to allow the receiving network element the ability to synchronize with the framing of the incoming transport signal so that it can extract the cells from the bit stream for processing. Cell alignment is also referred to as cell delineation. In addition to the two ATM cell structures, two types of cell alignment are used in an ATM network, Header Error Control (HEC) alignment and Physical Layer Convergence Protocol (PLCP) alignment. HEC alignment places ATM cells directly within the DS1 or DS3 payload without allocating any extra overhead. As discussed in the section on UNI cell structure elements, HEC has limited error correction capability. PLCP alignment requires more overhead bytes than HEC, providing additional error checking capability. With PLCP alignment, ATM cells are first aligned with a PLCP frame, then they are mapped into the payload of a DS1 or DS3 frame There are several ATM cell payload categories. The two most common categories are user cells and OAM cells. User cells contain live customer information in the payload. OAM cells include Alarm Indication Signal (AIS), Remote Defect Indication (RDI), and loopback cells, which are used for network fault management. AIS and RDI cells indicate alarms in the same manner as SONET carrier signals. If a switch port is not configured properly or loses service, AIS cells are sent to indicate the address with the anomaly. RDI is the response that other switches send to incoming AIS alarms. RDI alarms are sent on the return address. Loopback cells may be transmitted to a switch in order to determine if a return path has been established. If an ATM switch responds to a loopback cell, the cell is returned on the return address. Unlike traditional loopbacks, the entire channel is not looped up, just the loopback cell itself.

ATM Edge Switches Installed at network edge ATM Switch Frame Relay T1 ATM Edge Device ATM Edge Switch ATM ATM Switch OC-3c OC-3c OC-3c ATM Switch OC-12 Ring ATM Switch OC-3c ATM Switch ATM ATM Switch ATM Switch

ATM Backbone Switches Installed at CO

Frame Relay ATM Switch ATM Edge Device T1

Video OC-3c Los Angeles West ATM Switch ATM Switch OC-3c ATM Switch New Tork East

Video

Figure 5. Components of an ATM network.

ATM TESTING OVERVIEW

A Layered Testing Strategy
This application note is the second comprehensive guide for service providers using the Acterna FST-2310 to install and maintain telecommunications networks. Both application notes contain specific tests and a troubleshooting appendix to isolate common problems associated with the transport network. If you have difficulty with any of the tests, please contact Acternas Technical Assistance Center (TAC) at 1-800-638-2049. The TAC staff would also appreciate hearing from you regarding additional tips to enhance the troubleshooting appendix. The testing strategy outlined in these application notes is an efficient, bottom-up testing approach designed to systematically eliminate problems found at the transport testing layer that may affect higher-layer services. Unlike the layers in the Open Systems Interconnection (OSI) Basic Reference Model, which describe protocol relationships, the testing layers that are referred to in this document represent categories of common problems and solutions gathered from numerous field installation and maintenance calls. Figure 6 identifies the layers used in these testing applications.
Testing Strategy ATM Configuration Layer SONET Configuration Layer Physical Layer

Physical layer testing identifies a variety of problems caused by improper line build-out, connector or cabling faults, repeater failure, optical reflections, and optical loss. Tests include pulse shape, jitter, signal measurements, BERT, optical return loss, and optical insertion loss. These tests are performed primarily at DS3 demarcation points as well as in the optical backbone. Since physical layer problems commonly cause intermittent and hard-to-find problems at higher layers, it is critical to verify DS3 and optical backbone operation during installation to prevent callbacks. SONET configuration layer testing eliminates common problems associated with SONET circuit setup. Tests include SONET timing, SONET path configuration, error and alarm reporting, and concatenated signal configuration. These tests, detailed in the SONET Testing with the Acterna FST-2310 application note, ensure that the signal is properly installed for the desired service. SONET configuration layer testing will result in reduced turn-up time and fewer maintenance calls.

ATM configuration layer testing verifies ATM Virtual Path/Virtual Channel (VP/VC) configuration. Specific tests include ATM switch configuration, endto-end channel setup, DSLAM configuration, alarm and error reporting, errored cell handling, throughput, and priority configuration. These tests are performed during the installation of the backbone ATM transport network or during the configuration of ATM service. It is important to include in-service testing since data transport problems, such as delay variation and congestion, can only be roughly simulated during out-of-service testing. The unpredictable nature of data networks can cause problems to surface even after out-of-service simulations have functioned properly. The in-service tests include monitoring ATM congestion, alarms, errors, and delay variation. This application note thoroughly tests and verifies ATM transport configuration to ensure trouble-free service turn-up.

Figure 6. Transport testing layers.

ATM Network Testing

Customers expect error-free delivery of data, voice, and video services. ATM service quality depends not only on error-free transmission facilities, but it also depends on error-free performance of the ATM network elements. ATM network elements, unlike those in SONET networks, support very little switch-to-protect circuit redundancy. Also, since ATM networks are designed for speed, the underlying assumption is that the physical layer will perform flawlessly. Because of this assumption, ATM switches do not re-transmit cells. Instead, the ATM network places the responsibility for re-transmission on the application using ATM. As a result, less-than-perfect physical layer performance causes excessive retransmission, which ultimately causes network congestion, more dropped cells, and more cell re-transmission. To avoid this spiraling effect, this application note presents four tests that verify different elements in the ATM network, provide an end-to-end check of the network, perform in-service monitoring, and verify adequate Quality of Service (QoS) metrics. It is strongly recommended that all of these tests are performed to ensure proper operation of the ATM network. The tests are briefly described as follows. (1) ATM Switch Verification Test - Verifies proper installation and provisioning of the ATM switch. This test is vital, as the ATM switch is the entry point for customer traffic into the ATM network. (2) End-to-End ATM Network Performance Test - Verifies the proper operation of all of the elements in the ATM network. This test simulates customer traffic to ensure proper routing of traffic and proper configuration of the network elements. (3) In-Service ATM Monitoring Test Helps maintain proper operation of the ATM network after customer traffic is applied. This test provides continuing information on network status and performance without affecting customer traffic. (4) DSLAM Provisioning Test - Used to verify proper installation and configuration of the DSLAM for Digital Subscriber Line (DSL) service.

GENERAL SETUP
Required Equipment and Options
In order to perform the tests described in this application note, the following equipment is required: Fiber Optic Cleaning Kit (Part #2550) Two FST-2310s test sets with the following options:
TB2310-OC12 SONET OC-12 TX/RX (may be required if test access is OC-12) TB2310-OC3 SONET OC-1/3/3c Transmitter and Receiver TB2310-ATM-OC12, ATM Analysis for OC-12 and/or TB2310-ATM-OC3, ATM Analysis for OC-3 and/or TB2310-ATM-DS3, ATM Analysis for DS3 and/or TB2310-ATM-DSN, ATM Analysis for DS1 and DS3

Configuration Parameters
The Acterna FST-2310s ATM functionality supports the configuration of the following settings:

For OC-3c or OC-12c ATM: three fiber optic cables (single mode or multi-mode depending on the configuration) with the proper connector (FC/PC, ST, or SC on the FST-2310 top panel) For DSLAM provisioning: one Acterna DSL-350 test set

Configuring the FST-2310 TestPad for Different Access Rates

Test Setup for ATM Testing at a DS1 Access Point

1. Select the DS1 ATM test as follows: On the Application Bar, tap the Term button. Select Terminate T1. Select T1 ATM. Select QoS. 2. Configure the DS1 signal as follows: Tap the Setup button. Set T1 Framing to ESF, Timing to Internal, and PLCP to On or Off (as appropriate for the network being tested). Select OK. 3. Examine the DS1 Primary LEDs: Verify that no red LEDs are illuminated. Verify that the following DS1 Primary LEDs are illuminated (green): Signal, Frame. 4. After the expected testing time, access the results as follows: For each results pane, tap the Result Group button, and then select T1 Pri. On the left results pane, tap the Result Category button, and then select Summary. Verify that the left results pane indicates Results OK.

Test Setup for ATM Testing at a DS3 Access Point

1. Select the DS3 ATM test as follows: On the application bar, tap the Term button. Select Terminate DS3. Select the appropriate ATM payload being tested. Select QoS. 2. Configure the DS3 signal as follows: Tap the Setup button. Set DS3 Framing to M13 or C-BIT, Timing to Internal, and PLCP to On or Off (as appropriate for the network being tested). Select OK. 4. Examine the DS3 Primary LEDs: Verify that no red LEDs are illuminated. Verify that the following DS3 Primary LEDs are illuminated (green): Signal, Frame. 5. After the expected testing time, access the results as follows: For each results pane, tap the Result Group button, and then select DS3 Pri. On the left results pane, tap the Result Category button, and then select Summary. Verify that the left results pane indicates Results OK.

10

Test Setup for ATM Testing at a SONET Access Point

1. Select the SONET ATM test as follows: On the Application Bar, tap the Term button. Select the appropriate rate for the carrier signal being accessed. Select the appropriate ATM payload being tested. Select QoS. 2. If testing DS3 ATM, configure the DS3 signal by following step 2 of Test Setup for ATM Testing at a DS3 Access Point. 3. Configure the SONET transmit signal as follows: Tap the Setup button. Set Timing to Internal, and then select the appropriate transmit wavelength for the network being tested. Where applicable, select the channel(s) mapped for the ATM payload. Verify that Tx=Rx is checked. Select OK. Verify that Laser On is illuminated. 4. Examine the SONET LEDs: Verify that no red LEDs are illuminated. Verify that the following SONET LEDs are illuminated (green): Signal, Frame, Path Ptr. If testing DS3 ATM or DS3 Muxed ATM, verify that the following DS3 LEDs are illuminated (green): Signal, Frame. If testing DS3 Muxed ATM or VT1.5 ATM, verify that the following DS1 LEDs are illuminated (green): Signal, Frame. 5. After the expected testing time, access the results as follows: On the left results pane, tap the Result Group button, and then select SONET Pri. On the left results pane, tap the Result Category button, and then select Summary. Verify that the left results pane indicates Results OK. On the left results pane, tap the Result Category button, and then select Signal. Verify that the SONET Rx Frequency is within range, depending on the test access. NOTE: Appendix D lists SONET line rates and their associated frequencies. On the left results pane, tap the Result Category button, and then select Line. Verify the following results: Path Ptr Just = 0 Path Ptr Value = stable, anywhere from 0 to 782

#1: ATM Switch Verification Test

The ATM Switch Verification Test, performed during out-of-service testing, verifies the proper provisioning of the most critical element in an ATM network. Symptoms of an improperly provisioned ATM switch include misrouted, dropped, or incorrectly prioritized cells. These symptoms can prevent cells from arriving at their destinations and/or corrupt another users data. Consequently, one or more customers may experience lost data, echoing during voice conversations, or jitter during a video transmission. In addition, failure of the ATM switch to regenerate correctable ATM cells or drop non-correctable ATM cells can result in unnecessary re-transmission or misrouting. The purpose of this test is to verify that each switch in the ATM network has been properly provisioned in order to isolate potential service problems before live traffic is applied. The objectives of this test are to verify: Routing table configuration Correction (by the switch) of correctable errors Dropping of non-correctable errors Proper handling of ATM AIS and RDI alarms Proper BIP error operation Configuring the FST-2310 TestPad
1. Configure the FST-2310 for the correct carrier signal as follows: On the Application Bar, tap the Term button. Select the appropriate rate for the carrier signal being accessed. Select the appropriate ATM payload being tested. Select QoS. Tap the Setup button. Select Internal timing, set the appropriate framing format, and set PLCP to On or Off (as appropriate for the network being tested). For testing at a SONET access point, select the channel(s) mapped for the ATM payload. Verify that Tx=Rx is checked. 2. Configure the ATM transmit channel addresses as follows: Set the Correlation Tag to 2310 and the Tx/Rx Cell Type to TTC 1. Set the Interface to UNI, select Profile 1 and select the desired address of the VPI and VCI being tested. Note: PTI and CLP are normally set to 0 unless testing special network functions. Select Profile P2, P3, or P4 to program additional background traffic or other addresses that require testing. Program these profiles in the same manner as described above. If additional traffic is not desired, leave these background profiles at all zeros (idle cells). 3. Select the foreground transmit channel in the Pri Tx Profile box. Select the background transmit channel in the Sec Tx Profile box. 4. Select the bandwidth as follows: Set the Bit Rate to Variable. Note: This test can also be performed using a Constant Bit Rate. Select the Continuous Bandwidth and Burst Gap desired. Select the Peak Bandwidth and Burst Length desired. Select the Background Bandwidth desired in the Secondary Profile Tx Cells. Select OK. Note: When the background and foreground total less than 100%, the remaining cell traffic sent by the FST-2310 is idle.

Connecting the FST-2310 to the Circuit

1. For fiber jumpers, clean all fiber connectors and test set connectors. 2. Connect the cables to the FST-2310 and the ATM network device as shown in Figure 8. Note: Perform the appropriate pre-test setup, equipment verification, and carrier signal procedures before proceeding.

ATM Switch FST-2310

Figure 8. Connecting the FST-2310 to an ATM Switch.

11

Performing the ATM Switch Verification Test

Verify that no red LEDs are illuminated. Verify that the green Signal and Frame LEDs are illuminated for the carrier signal being accessed. For testing at a SONET access point, verify the following results: The carrier signal frequency is within the allowed range. Path Ptr Just = 0 Path Ptr Value = stable, anywhere from 0 to 782 Note: Appendix D lists SONET line rates and their associated frequencies. a) Verify proper routing table configuration Tap the Restart button. In the left results pane, tap the Results Group button, and then select ATM. Tap the Results Category button, and then select Summary. Verify that the left results pane indicates Results OK. Verify the results in the following results categories: ATM LEDs No red LEDs are illuminated. ATM STATS Mask Cells = The number of cells being transmitted from the FST-2310 Total Utilization % < 100% Total Congestion % = 0.00% Mask Congestion % = 0.00% Correlation Tag = 2310 % Mask CLP = 0% ATM QoS Mis-inserted Cells = 0 Out-of-Sequence Cells = 0 Lost Cells = 0 ATM ERRORS HEC Errors = 0 Correctable HEC Errors = 0 Non-Correctable HEC Errors = 0 For DS3 PLCP framing, also verify: PLCP Frame Word Errors = 0 PLCP BIP Errors = 0 PLCP FEBEs = 0 b) Verify proper non-correctable HEC error operation Note the following results on the network ATM switch. Number of Correctable HEC Errors Number of Non-Correctable HEC Errors Note: The ATM switch may not have these results. Set the Error Type to HEC (Noncorr). Tap the Noncorr HEC Error button to insert one noncorrectable error. In the left results pane, tap the Results Group button, and then select ATM. Tap the Results Category button, and then select 12

Errors. Verify that Non-Correctable HEC Errors = 1. Tap the Results Category button, and then select QoS. Verify that Lost Cells = 1. Verify the following results on the network ATM switch: Correctable HEC Errors value does not increment from previous result. Non-Correctable HEC Errors value increments by 1 from previous result. c) Verify proper correctable HEC error operation Set the Error Type to HEC (Corr). Tap the Correctable HEC Error button to insert one correctable error. Verify that Lost Cells = 1 (remaining from Step 3). Verify that Correctable HEC Errors = 1. Verify the following results on the network ATM switch: Correctable HEC Errors value increments by 1 from previous result. Non-correctable HEC Errors value does not increment from previous result. d) Verify proper ATM alarm operation Set the OAM Type to Segment and the Alarm Type to VC AIS (F5). Tap the Restart button. If the ATM network device does not support AIS/RDI alarms, then verify that the ATM alarms are passed through. Tap the VC AIS (F5) Alarm button. In the results category of the left results pane, select LED. Verify that the VC AIS (F5) LED is illuminated. Tap the VC AIS (F5) Alarm button again to cancel the AIS alarm. Verify that the VC AIS (F5) history LED is illuminated. Set the Alarm Type to VC RDI (F5). Tap the VC RDI (F5) Alarm button. Verify that the VC RDI (F5) LED and the VC AIS (F5) history LED are illuminated. Tap the VC RDI (F5) Alarm button again to cancel the RDI alarm. Verify that the VC RDI (F5) history LED is illuminated. If the ATM network device supports AIS/RDI alarms, then verify that ATM alarms are handled properly. Tap the VC AIS (F5) Alarm button. Verify that the VC RDI (F5) LED is illuminated. Verify that the ATM device reports the AIS alarm. Tap the VC AIS (F5) Alarm button again to cancel the AIS alarm. Verify that the VC RDI (F5) history LED is illuminated. Set the Alarm Type to VC RDI (F5). Tap the VC RDI (F5) Alarm button. Verify that the VC RDI (F5) LED is illuminated. Tap the VC RDI (F5) Alarm button again to cancel RDI alarm.

e) Verify BIP error operation Note: Perform the following steps for DS3/DS1 PLCP ATM only. Note the following result on the network ATM switch: Number of PLCP BIP Errors Note: The ATM switch may not have this result. Tap the Restart button. Set the DS3 or T1 Error Type to BIP. Tap the Error Insert button to send one BIP error. Verify the BIP results as follows: PLCP Frame Word Errors = 0 PLCP FEBEs = 1 Note: The switch may not support FEBEs. Therefore, this result may be 0. Verify the following results on the network ATM switch. PLCP BIP Error increments by 1 from previous result. Note: The ATM switch may not have this result. Refer to Appendix C for results interpretation. If any of the tests result in a failed response, refer to Appendix B for troubleshooting tips.

#2: End-To-End ATM Network Performance Test

The End-to-End ATM Network Performance Test verifies the end-to-end setup and configuration of all of the ATM elements responsible for transmitting cells. These elements include ATM switches, SONET network elements, and SONET cross-connect devices. This outof-service test simulates customer ATM addresses and bandwidths, verifies the proper configuration of all of the devices, and verifies that the destination properly receives the transmitted ATM cells. The objectives of the test are to verify: Proper cell routing through the ATM network Compliance of QoS measurements to SLAs Proper handling of loopback cells Configuring the FST-2310 TestPad
1. Place an FST-2310 at each end of the circuit and arbitrarily identify them as East and West. If only one FST-2310 is available (East), the far end (West) will be looped back using a jumper cable. 2. At East and West, configure the ATM transmit channel addresses as follows: Tap the Setup button. Set the Tx/Rx Cell Type to O.191 and the Interface to UNI, and then select Profile P1 Select the desired address of the VPI and VCI being tested. Note: PTI and CLP are normally set to 0 unless testing special network functions. Select PROFILE P2, P3, or P4 to program additional background traffic or other addresses that require testing. Program these profiles in the same manner as described above. If additional traffic is not desired, leave these background profiles at all zeros (idle cells). 3. At East and West, select the foreground transmit channel in the Pri Tx Profile box. Select the background transmit channel in the Sec Tx Profile box. 4. At East and West, select the bandwidth as follows: Set the Bit Rate to Variable. Note: This test can also be performed using a Constant Bit Rate. Select the Continuous Bandwidth and Burst Gap desired. Select the Peak Bandwidth and Burst Length desired. Select the Background Bandwidth desired in the Secondary Profile Tx Cells box.

Note: When the background and foreground total less than 100%, the remaining cell traffic sent by the FST-2310 is idle. 5. At East, set the Correlation Tag to 2310. 6. At West (ignore if loopback), set the Correlation Tag to 1212. 7. Select OK.

(ms), Avg. Round Trip Delay (ms), Max. Round Trip Delay (ms) conform to the established SLAs. ATM ERRORS HEC Errors = 0 Correctable HEC Errors = 0 Non-Correctable HEC Errors = 0 For DS3 PLCP framing, also verify: PLCP Frame Word Errors = 0 PLCP BIP Errors = 0 PLCP FEBEs = 0 If a loopback exists at West, verify the following East result: Correlation Tag = 2310 If a loopback does not exist at West, verify the following results: Correlation Tag = 2310 at West Correlation Tag = 1212 at East b) Verify proper handling of loopback cells 1. At East, configure the test set for the appropriate signal rate and payload as follows: On the Application Bar, tap the Term button. Select the appropriate rate for the carrier signal being tested. Select the appropriate payload being tested. Select Stats. Complete the Configuring the FST-2310 TestPad section above. 2. Tap the Setup button. Set OAM Loopback Type to VC Loopback. Select OK. Tap the Restart button. 3. Tap the Insert Loopback button to insert the desired number of loopback cells. 4. Verify the test results as follows: In the left results pane, tap the Results Group button, and then select ATM. Tap the Results Category button, and then select Stats. Verify the following results: Loopback Cells = The number of loopback cells transmitted by the FST-2310 Timed-Out Loopback Cells = 0 Refer to Appendix C for results interpretation. If any of the tests result in a failed response, refer to Appendix B for troubleshooting tips.

Connecting the FST-2310 to the Circuit

1. For fiber cables, clean all fiber connectors and test set connectors. 2. At East and West, connect the cables as shown in Figure 9. If only one FST-2310 is available (East), loopback the far end (West) using a jumper cable. Note: Perform the appropriate pre-test setup, equipment verification, and carrier signal procedures before proceeding.

Performing the End-to-End ATM Network Performance Test

a) Verify proper cell routing and QoS measurements Tap the Restart button. At East and West, allow the test to run for the expected testing time, and then verify the test results as follows: In the left results pane, tap the Results Group button, and then select ATM. Tap the Results Category button, and then select Summary. Verify that the left results pane indicates Results OK. Verify the results in the following results categories: ATM LEDs No red LEDs are illuminated. ATM STATS Mask Cells = The number of cells being transmitted from the FST-2310. Total Congestion % = 0.00% Mask Congestion % = 0.00% % Mask CLP = 0 % ATM QoS Mis-inserted Cells = 0 Out-of-Sequence Cells = 0 Lost Cells = 0 Avg. Delay Variation (ms), Max. Delay Variation

West or

DS3 or OC-3c ATM Connections

East

ATM Switch FST-2310

Transport Network

ATM Switch FST-2310

Figure 9. Connecting two FST-2310s for end-to-end testing.

13

#3: In-Service ATM Monitoring Test

The In-Service ATM Monitoring Test is a valuable tool for maintaining proper ATM network operation without affecting customer traffic. Since ATM network utilization is difficult to predict, ATM network performance can be compromised even after end-toend simulations pass testing. Sometimes, the only way to determine how a network is performing is to monitor it in-service. This test provides early detection of service degradation and indicates delay variation, congestion, and overall utilization of the circuit. Installing test access monitoring points using splitters, monitor jacks, or dedicated ATM test access points allows proactive problem correction and isolation before network performance is degraded. The objectives of the test are to: Locate congested VPI/VCIs Identify low-priority traffic that may be dropped Obtain an indication of the total utilization of the circuit Locate AIS or RDI alarms Monitor ATM results and bandwidth utilization Monitor Quality of Service metrics Configuring the FST-2310 TestPad 1. Configure the test set for the appropriate signal rate and payload as follows: On the Application Bar, tap the MON/THRU button. Select the appropriate rate for the carrier signal being tested. Select the appropriate payload being tested. Select Stats. 2. Configure the ATM receive primary channel address as follows: Tap the Setup button. Select Summary. Set Timing to Recovered and ATM Search Type to Live Traffic Cells. Select OK.

Performing the In-Service ATM Monitoring Test

a) Locate the congested VPI/VCIs and AIS/RDI alarms Locate all active addresses as follows: Tap the Start Search button. Tap Next VPI/VCI. Note: The results for each address found can be viewed in the left results group Tap Next VPI/VCI to find other VPI/VCI addresses. Note any addresses that indicate AIS or RDI alarms and refer to Appendix B to correct these alarms. Tap Save VPI/VCI to Rx Profile. Set the Rx Profile to Rx P. Tap the Restart button. In the left results pane, tap the Results Group button, and then select ATM. Tap the Results Category button, and then select Summary. Verify that the left results pane indicates Results OK. Verify the following results: ATM LEDs No red LEDs are illuminated. ATM STATS Total Utilization % < 100% Total Congestion % = 0.00% Mask Congestion % = 0.00% % Mask CLP = 0.00% ATM ERRORS HEC Errors = 0 Correctable HEC Errors = 0 Non-Correctable HEC Errors = 0 For DS3 PLCP alignment, also confirm the following: PLCP Frame Word Errors = 0 PLCP BIP Errors = 0 PCLP FEBEs = 0 Repeat this procedure until all alarms and congested addresses are found and corrected. b) Monitor Quality of Service metrics For addresses that correspond to constant bit rate (CBR) service: Tap Save VPI/VCI to Rx Profile. Set the Rx Profile to Rx P. On the Application Bar, tap the MON/THRU button. Select the appropriate rate for the carrier signal being tested. Select the appropriate payload being tested. Select QoS. Tap the Restart button. In the left results pane, tap the Results Group button, and then select ATM. Tap the Results Category button, and then select Summary. Verify that the left results pane indicates Results OK. Verify the following results:

ATM QoS Avg. Delay Variation (ms), Max. Delay Variation (ms), Avg. Round Trip Delay (ms), Max. Round Trip Delay (ms) conform to the established SLAs. Refer to Appendix C for results interpretation. If any of the tests result in a failed response, refer to Appendix B for troubleshooting tips.

#4: DSLAM Provisioning Test

The DSLAM Provisioning Test verifies the proper installation and configuration of the DSLAM. The test simulates incoming traffic from the ATM network in order to identify problems (before customer traffic is applied) that may arise during the turn-up of the DSLAM, such as faulty connections, low throughput, and inadequate QoS metrics. The objectives of the test are to verify: Proper cabling connections to the DSLAM Acceptable throughput Compliance to the established QoS Configuring the FST-2310 TestPad and the DSL-350
1. Configure the ATM transmit channel addresses as follows: Tap the Setup button. Set the Correlation Tag to 2310 and the Tx/Rx Cell Type to TTC 1. Set the Interface to UNI, select Profile P1, and then select the desired address of the VPI and VCI being tested. Note: PTI and CLP are normally set to 0 unless testing special network functions. Select PROFILE P2, P3, or P4 to program additional background traffic or other addresses that require testing. Program these profiles in the same manner as described above. If additional traffic is not desired, leave these background profiles at all zeros (idle cells). 2. Select the foreground transmit channel in the Pri Tx Profile box. Select the background transmit channel in the Sec Tx Profile box. 3. Select the bandwidth as follows: Set the Bit Rate to Variable. Note: This test can also be performed using a Constant Bit Rate. Select the Continuous Bandwidth and Burst Gap desired. Select the Peak Bandwidth and Burst Length desired. Select the Background Bandwidth desired in the Secondary Profile Tx Cells box. Note: When the background and foreground total

Connecting the FST-2310 to the Circuit

1. For fiber cables, clean all fiber connectors and test set connectors. 2. Connect the cables to the

ATM Switch

ATM Switch

FST-2310
Figure 10. Connecting the FST-2310 to the ATM switch.

14

less than 100%, the remaining cell traffic sent by the FST- is idle. 4. Configure the DSL-350 350+ as follows: Tap the Setup button. Tap the Scroll Menu button until Mode is highlighted. Tap the + button until ATM Loopback is displayed. Tap the Accept button. Tap the Scroll Menu button to return to the main ADSL setup menu. Tap the Loopback button.

ATM QoS Lost Cells = 0 Mis-inserted Cells = 0 Errored Cells = 0 c) Verify compliance to established QoS Verify the following results: ATM QoS Avg. Delay Variation (ms), Max. Delay Variation (ms), Avg. Round Trip Delay (ms), Max. Round Trip Delay (ms) conform to the established SLAs.

Connecting the FST-2310 and DSL-350 to the Circuit

1. For fiber cables, clean all fiber connectors and test set connectors. 2. Connect the cables to the FST-2310 and the DSL350 as shown in Figure 11. Note: Perform the appropriate pre-test setup, equipment verificqtion, and carrier signal procedures before proceeding.

Performing the DSLAM Provisioning Test

a) Verify proper connection of the DSLAM to the network Tap the Restart button. After the expected testing time, verify the following results on the DSL-350 Verify that the ATM Sync LED is illuminated. b) Verify acceptable throughput Verify that the Cells Received on the DSL-350 matches the Cells Transmitted on the FST-2310. In the left results pane, tap the Results Group button, and then select ATM. Tap the Results Category button, and then select Summary. Verify that the left results pane indicates Results OK. Verify the following results: ATM LEDs No red LEDs are illuminated. ATM STATS Mask Cells = The number of cells being transmitted from the FST-2310.

DSLAM FST-2310
Figure 11. Connecting the FST-2310 to the DSLAM.

DSL-350

15

Appendix A: Troubleshooting Tips for SONET, DS3, and DS1 Carrier Signal Testing
This appendix provides a list of items to check if your test setup or test results do not show the expected results as described in this application note.
Rx Pulses on the top panel connector does not illuminate. Replace the possibly defective optical patch cord. Clean the optical fiber and test set connector. Verify that the optical connector keys are lined up at both ends of the jumper cable. Verify carrier signal test setup. Verify physical layer and SONET configuration. Signal LED on the front panel does not illuminate. Verify carrier signal test setup. Verify that the proper line rate is selected and that test connections are correct. Verify physical layer and SONET configuration. SONET payload is Auto or Unknown after the test starts. Verify carrier signal test setup. Verify that the proper line rate is selected and that test connections are correct. If alarm conditions exist on the FST-2310 LEDs, reconfigure the SONET network element (NE) for a concatenated signal (OC3c ATM payload) or a non-concatenated signal (DS3 ATM payload). Verify SONET configuration. Summary category indicates Path Pointer Size This indicates that the SONET NE is incorrectly configuring the pointer size bits of the H1 byte in the SONET overhead. Interconnecting this signal with other vendors equipment may cause some SONET NEs and ATM switches to alarm with Loss of Pointer (LOP). SONET BIP Errors exist. This indicates that the end-to-end carrier signal is suffering parity errors. This can cause DS3 Parity Errors, excessive retransmission of ATM traffic, and ultimately a congested network. Verify the physical and configuration test layers. For an optical carrier signal, check insertion loss and return loss to verify fiber performance is within specifications. OC-n Rx Frequency is displayed in Summary. DS3 Rx Frequency is displayed in Summary. DS1 Rx Frequency is displayed in Summary. Path Ptr LED is illuminated. Path Ptr Just is not equal to 0. This indicates that the carrier signal is not timed properly, causing problems in the asynchronous ATM network. Verify the physical and configuration test layers. Check timing source configuration on the NE to verify that the configuration is External. Verify that the SONET NE is not configured for non-revertive holdover. Data Sync on the front panel is not illuminated. For an optical carrier, verify that the Concat LED is illuminated in the SONET LEDs category. If not illuminated, reconfigure the ATM NE for concatenated signal transmission (if applicable). Verify carrier signal test setup. Check the Summary category for physical layer errors corrupting the ATM payload. If found, re-verify the carrier signal.

16

Appendix B: Troubleshooting Tips for ATM Testing

This appendix provides a list of items to check when your test setup or test results do not match what is described in this application note during the carrier signal test setup.
HEC Errors is not equal to 0. PLCP BIP Errors is not equal to 0. PLCP Frame Errors is not equal to 0. PLCP FEBEs is not equal to 0. Check the Summary category for carrier errors. If found, re-verify the carrier signal. Lost Cells is not equal to 0. Verify that the channel is properly mapped through the ATM NEs. Verify that Non-Correctable Errors are not being generated on the far side of the channel connection, causing the switch to drop the cells. Examine the congestion result, Total Congestion %. If this result is non-zero, then the switch may be congested, causing it to drop cells. If the % Mask CLP result is also non-zero (this address has a low priority), then these cells should be dropped. If the % Mask CLP result is zero, then high priority traffic is being dropped. To correct the congestion problem, determine which addresses are exceeding their bandwidth and correct problems on those channels. Verify that the address is not exceeding its allowable bandwidth. Reduce the simulated bandwidth in the ATM Tx setup. If the Lost Cells result stops incrementing at a lower utilization, note the maximum rate that can be supported. Verify that the port is configured for the proper data rate. Correlation Tag is not equal to the transmitted value. Check for physical loopbacks on the switch or network. Check ATM switches to identify internal loopbacks. Use Any TTCTest Cell mode in the ATM Search Type function to locate other Acterna test cells that may be on the network. Mis-inserted Cells is not equal to 0. This indicates that the FST-2310 is receiving cells with the same address as programmed in the ATM Rx Profile, but some of the incoming cells are not Acterna test cells. Ensure that the ATM Rx Profile has the correct address programmed as the mask and that this address excludes other possible active cell addresses. This can be accomplished by removing the X (dont care) from the GFC, VPI, or VCI fields and programming specific addresses. Verify that the ATM Tx background cell addresses are not configured to transmit the same address as the primary test cell. Verify that the ATM switch will drop Non-Correctable HEC Errors as described in the ATM Switch Verification Test. Otherwise, the ATM switch may incorrectly route a cell based on an errored VPI/VCI address. Verify that the routing table in the ATM switch does not have any conflicting destination addresses. Out-of-Sequence Cells is not equal to 0. Contact the switch manufacturer. Total Congestion % is not equal to 0. Mask Congestion % is not equal to 0. This indicates that an ATM switch is sending out congestion indications. If the Total Congestion % is much larger than the Mask Congestion %, then the problem is probably local to the ATM switch under test. If the Mask Congestion % and the Total Congestion % are small and very close together, then the congestion problem is probably originating from an ATM switch downstream. Backtrack to find the ATM switch, which is the source of the ATM cell address corresponding to the receive mask. Verify that the transmitted cells are not configured with congestion indications by ensuring that the PTI field is set to 0. Correct the ATM switch congestion problem by analyzing active channels and rerouting addresses, as necessary.

17

Total Utilization percent is high or is 100%. When examined in-service, this indicates that the circuit does not have any excess capacity to handle bursts of data or additional capacity. This situation can place addresses on the circuit at risk, particularly those addresses with CLP=1. ATM results are unavailable. Verify the carrier signal test setup. The FST-2310 is not receiving ATM cells or is receiving ATM cells that do not match the ATM Rx Profile. Verify address setup. Lost Cells is unavailable. Mis-inserted Cells is unavailable. Out-of-Sequence Cells is unavailable. Correlation Tag is unavailable. Errored Cells is unavailable. The FST-2310 is not receiving Acterna test cells. Use Any TTCTest Cell in the ATM Search Type function to locate and use these cells. ATM categories display Results Unavailable. Verify the carrier signal test setup. For Min./Max./Avg. Delay Variation results, the ATM test must be configured for QoS. Delay Variation results are not applicable (N/A) if the receive mask is configured with an X (dont care) in the GFC, VPI, or VCI fields in the ATM Rx Profile. This configuration allows for the analysis of multiple cells and will give a confusing result. Remove the X from each of the fields and program specific addresses. % Mask CLP is not equal to 0. Verify that the specific address being analyzed is intended to have a low priority. Idle cells (address 0) will often have a CLP=1. Verify that the address is not exceeding its allocated bandwidth, causing the switch to mark it as eligible to drop. Measure utilization using Mask Cells and compare this result to the configured ATM switch port and the customers bandwidth. Delay Variation displays Unavailable. Wait a few moments for the result to stabilize. Cell rate is too low to accurately measure delay variation. Message window displays Search: Match Not Found. In Preview mode, this indicates that no active addresses were found on the circuit. Verify ATM NE configuration. In Search mode, this indicates that the specified search parameter was not found. Specified search parameters include both Acterna test cells and AIS/RDI alarms. Verify ATM NE configuration. Some ATM NEs do not support these alarms. AIS and RDI alarms exist. OAM AIS alarms indicate that an address coming into the switch has been lost. Use AIS Cells mode in the ATM Search Type function to identify the address with the alarm. Verify this address on the ATM switch as well as on the corresponding incoming signal for proper configuration. OAM RDI alarms indicate that a switch is responding to an OAM AIS alarm. Use RDI Cells mode in the ATM Search Type function to identify the address with the alarm. This address will be the return path for an address coming into the switch. Examine that incoming address for alarms and configuration.

18

Appendix C: Results Interpretation

This appendix provides an explanation of the various results that you may see during testing, helping you to understand the effect of certain test results on network services and to determine the source of network problems.
Mask Cells These results indicate the number of cells that match the current ATM Rx Profile. The bandwidth should be the same as that transmitted from the FST-2310. Total Congestion % Mask Congestion % A single bit in the PTI field is used by ATM equipment to indicate congestion. Congested switches set this bit when they are overloaded. Since overloaded switches drop cells, the Total Congestion % and Mask Congestion % results are crucial to determine the state of the ATM network. These two results should remain low on lightly loaded ATM switches or networks. % Mask CLP The CLP results provide a percentage and count of cells which have a CLP equal to 1 (for mask cells only). This result is important because ATM switches, if overloaded, can drop cells with CLP=1. Switches can also change CLP from 0 to 1 if the cell traffic exceeds contracted levels or if the switch is overloaded. Thus % Mask CLP indicates the percentage of cells that could be dropped by the switch or network. HEC Errors HEC Error Rate The HEC error count and rate results will indicate serious bit error problems on the line. Correctable HEC Errors are single bit errors that occur within the ATM header. Although these errors can be corrected by ATM switches, they indicate bit error problems on a SONET line. Non-Correctable HEC Errors are two or more bit errors in an ATM header. Cells with these errors will be dropped by network equipment. Min. Delay Variation Max. Delay Variation Avg. Delay Variation Delay variation is the difference between the actual arrival times of ATM cells from their expected arrival times. The result is measured in milliseconds (ms). Min. Delay Variation is the measurement of the late arrival of cells from their expected arrival time (-0.01 ms late, for example). The cell that arrived last is displayed. This number is always a negative value. Max. Delay Variation is the measurement of the early arrival of cells from their expected arrival time. The cell that arrived the earliest is displayed. Avg. Delay Variation is a variable average of the absolute value of the cells that arrived early and late. For constant bit rate (CBR) service, these results should be very low.

19

Appendix D: SONET Line Rates and Frequencies

Line Rate STS-1/OC-1 OC-3 OC-12 OC-48 Minimum Frequency (Hz) 51,838,963 155,516,890 622,067,558 2,448,270,234 Maximum Frequency (Hz) 51,841,037 155,523,110 622,092,442 2,488,369,766

20

21

Worldwide Headquarters One Milestone Center Court Germantown, Maryland 20876-7100 USA Acterna is present in more than 80 countries. To find your local sales office go to: www.acterna.com

Regional Sales Headquarters North America One Milestone Center Court Germantown, Maryland 20876-7100 USA Toll Free: 1 866 ACTERNA Toll Free: 1 866 228 3762 Tel: +1 301 353 1560 x 2850 Fax: +1 301 353 9216 Latin America Acterna do Brasil Ltda. Av. Eng. Luis Carlos Berrini 936 9th Floor 04571-000 So Paulo SP-Brazil Tel: +55 11 5503 3800 Fax:+55 11 5505 1598 Asia Pacific Acterna Hong Kong Ltd. Room 902, 9th Floor Bank of East Asia Harbour View Centre 56 Gloucester Road Wanchai, Hong Kong Tel: +852 2892 0990 Fax:+852 2892 0770 Western Europe Acterna Germany GmbH Mhleweg 5 Germany Tel: +49 7121 86 2222 Fax:+49 7121 86 1222 Eastern Europe, Middle East & Africa Acterna Austria GmbH Aredstrasse 16-18 A-2544 Leobersdorf Tel.: +43 2256 65610 Fax: +43 2256 65610-22 Acterna Moscow Prospect Mira 26, stroenie 5 RF-129090 Moscow Tel.: +7 095 937 88 04 Fax: +7 095 775 26 05
FST2310ATM/AN/ACC/08-04/AE/PDFONLY

Copyright 2004 Acterna, LLC. All rights reserved. Acterna, Communications Test and Management Solutions, and its logo are trademarks of Acterna, LLC. All other trademarks and registered trademarks are the property of their respective owners. Major Acterna operations sites are IS0 9001 registered.

Note: Specifications, terms and conditions are subject to change without notice.