junglepax factory acceptance test procedure with albedo … · 2021. 3. 3. · junglepax factory...

JunglePAX Factory Acceptance Test Procedure

with ALBEDO xGenius tester

Feb 2021 V3.0

JunglePAX Factory Acceptance Test Procedure with ALBEDO xGenius tester

Table of Contents 1. Overview ................................................................................................................................................. 3

1.1 Objective ........................................................................................................................................... 3

1.2 Network Topology ............................................................................................................................. 3

1.3 Hardware Requirements ................................................................................................................... 4

1.4 Traffic Table ....................................................................................................................................... 5

2. Physical Inspection .................................................................................................................................. 6

2.1 Test Description ................................................................................................................................ 6

2.2 Results ............................................................................................................................................... 7

3. Visual Inspection ..................................................................................................................................... 7


3.2 Results ............................................................................................................................................... 7

4. Software Setup ........................................................................................................................................ 7


4.2 Results ............................................................................................................................................... 8

5. WAN ports verification ............................................................................................................................ 8

6. LAN ports verification ............................................................................................................................. 9

7. Traffic Testing (VPWS/VPLS ‐ Ethernet) ................................................................................................ 12

Ethernet Test Results: ............................................................................................................................ 14

8. Traffic Testing (VPWS ‐RS232)............................................................................................................... 14

RS.232 Test Results: ............................................................................................................................... 17

RS.232 Ports Verification: ...................................................................................................................... 17

9. Traffic Testing (VPWS‐ C37.94) ............................................................................................................. 18

xGenius configuration ....................................................................................................................... 18

BERT Test ........................................................................................................................................... 19

Propagation Delay Test ..................................................................................................................... 20

Failure Test ........................................................................................................................................ 23

C37.94 Test Results: ............................................................................................................................... 23

C37.94 Ports Verification: ...................................................................................................................... 23

10. Traffic Testing (E1‐VPWS) ................................................................................................................... 24

E1 Test Results: ...................................................................................................................................... 26

E1 Ports Verification: ............................................................................................................................. 26


1. Overview

1.1 Objective

This document describers the acceptance test procedure which will be used to validate the functionalities

of the 3‐node JunglePAX system.

1.2 Network Topology

Figure: Network Diagram (Option A)

Higüey II

80 km


1.3 Hardware Requirements

Equipment Quantity

JPAX Core Card 6

JPAX Chassis 3

Ethernet Access Card

(SFP)

12

C37.94 Access Card 3

E1 Access Card 6

DR4 Access Card 3

Power Supply Unit 6


1.4 Traffic Table


2. Physical Inspection

2.1 Test Description

1. Visually inspect the JPAX equipment to ensure that all the equipment is in good physical

condition. (Including all the cables/fiber optics)

2. Visually inspect that all JPAX chassis are securely installed in the rack and have a minimum of

1U spacing above and below each chassis.

3. Visually inspect that all JPAX chassis are supplied with a reliable power supply. Ensure that each JPAX node’s power supplies are fully engaged and locked in place as in below figure.

4. Visually inspect that each JPAX chassis has access cards fully engaged in the slots. 5. Visually inspect that all core cards are fully engaged, and its latches are locked in place, as

shown in below figure.

6. Visually inspect that all SFPs and SFP+s are located in the correct positions and are fully inserted, in accordance to GE’s node assignment drawings.

7. Visually inspect that all core cards are accessible via NMS cable and that all fiber optics are

correctly set up according to the network topology.


2.2 Results

Test Case Result Remarks

1.

2.

3.

4.

5.

6.

7.

3. Visual Inspection


1. Visually inspect that all the core cards are displaying green LEDs only. 2. Visually inspect that all the WAN port LED’s (that are connected) are green.

3. Visually inspect that all the LEDs on the SFP Ethernet ports that are connected are green.

3.2 Results

Test Case Results Remarks

1.

2.

3.

4. Software Setup


1. On the WebUI, under ‘Network > Node List’, check that all core cards’ data plane and

management statuses are green.


2. On the WebUI, under ‘Node > eMS’, check the core card has an IP address and that all the nodes

are displaying their chassis number. Repeat for all core cards to ensure that every core has its

own unique IP address.

3. On the WebUI, check all the tunnels and services are created as per the traffic table and firmware

of all units are latest.

4.2 Results


1.

2.

3

5. WAN ports verification

This section describes the instructions to perform a basic operational validation of all WAN ports in all

three JPAX nodes.

The system will be configured with six VPLS LANs between the three nodes. Each VPLS will be associated

to one specific WAN port on each node.

Test cases involve a ping test between 2 Eth ports communicating via one WAN connection at a time.

Only one pair fibers will be connected for each validation. Follow and record the results in the test matrix

below.

Instructions:

1. Ensure the WAN test script is loaded.

2. Configure two Ethernet testers with private IP addresses within the same subnet.

3. Connect one tester to the first Ethernet port to be tested. Refer to the test matrix below.

4. Connect a second tester to the associated port according to the test matrix.

5. Disconnect all WAN fibers except the target WAN connection between the two nodes under test.

Refer to test matrix below.

6. Perform a ping test between the two testers.

7. Record the results in the test matrix below.

8. Repeat all the steps above for the next set of Ethernet/WAN ports.

The WAN fiber will be connected to adjacent WAN ports and the ethernet cables will be

connected to the adjacent Ethernet ports.


5.1 Results


1. WAN ports verification

6. LAN ports verification

This section describes the instructions to perform a basic operational validation of all available LAN ports

in the system.

The system will be configured with one VPLS LAN between the three nodes for each equivalent port. i.e.

Node1.Slot1.P1 <‐> Node2.Slot1.P1 <‐> Node3.Slot1.P1


A ping test between 2 ports at a time will be used to validate each port functionality.

Instructions:

1. Ensure the Traffic test script is loaded in all nodes.

2. Configure two Ethernet testers with private IP addresses within the same subnet.

3. Connect one tester to the first Ethernet port to be tested. Refer to the test matrix below.

4. Connect a second tester to the associated port according to the test matrix.

5. Perform a ping test between the two testers.

6. Record the results in the test matrix below.

7. Repeat all the steps above for the next set of ports.

6.1 Results


1. LAN ports verification


7. Traffic Testing (VPWS/VPLS ‐ Ethernet) This test procedure describes the system level traffic test for the 4x1G SFP Ethernet Access Module (EF4A,

90200‐01) and/or 4xRJ‐45 Ethernet Access Module (EC‐4A, 90201‐01).

The Ethernet units to be tested will be part of a standard validation system. The system will be configured

according to the test setup tables defined in the Traffic table section.

An xGenius test set will be used to generate, send, receive, monitor and analyze all Ethernet frames for

BERT testing.

xGenius Configuration

1. Upon power‐up, select Home ( ) > Config > Mode to select operation mode (Ethernet Endpoint)

2. In Config menu, select Port A or B > Physical layer > Connector to setup Transceiver Mode: optical

or electrical

3. For Optical connector, select laser> on

4. Physical layer >Auto‐Negotiations: enabled or disabled

Choose Full Duplex mode from: Physical layer > Auto‐Negotiations>1000‐FD/100‐FD/10‐

FD: on or Off

Choose Clock mode from: Physical layer > Auto‐Negotiations > Clock role: Auto

5. From Config menu, select Port A or B > Local profile to setup:

Frame>Encapsulation> VLAN to enable VLAN

Frame> C‐VID

Frame> C‐VLAN priority

If IP Endpoint operation mode selected:

o Use DHCP> Yes or No

o IP address

o Network Mask

o DNS server

o IP gateway

6. Repeat the steps above for the second xGenius equipment.

BERT Test

1. From the Home panel ( ) >CONFIG

2. Select either Port A or Port B to enter in the port specific configuration.

3. Select the Payload menu.

Select Flow A1 (or Flow B1 in Port B) to enter in the flow 1 specific configuration.

Select BERT in Payload type

Choose the bit pattern you are going to use for generation and analysis

BERT patterns > User, enter a 32‐bit test pattern in payload in hexadecimal format

(“FFFFFFF” for all 1s

4. From CONFIG > Port A or B > Frame layer > Flow A1 for port A or B1 for port B

Select Frame size > 64

Select Destination MAC address from > Manual

Select Destination MAC address > type MAC address for the destination


5. From CONFIG > Port A or B > Bandwidth Profile > Flow A1 for port A or B1 for port B

Select Mode > Choose Continuous

Select Transmission rate > type the required rate

6. In the CONFIG > Port A or B > Filters, ensure no filters are currently selected.

7. To generate graphical representation and report for the result, follow these steps:

From the Home ( ) > Test > Event logger setup

Click on Enable > Yes

Select Port A event filter > BERT > TSE/SLIP/LSS

From the Home ( ) > Files ( ) > Report files

Click on Generate report > Yes

8. Select the preferred report format

9. To save this configuration, select Home ( )> Files ( )> Configuration files > Internal memory >

Save > type the file name as “Ethernet_unit1_test” > Done

10. Complete connectivity according to the diagram above.

11. After the Link connection LED is Green, press the start button to initiate the BERT test.

12. Click on RESULTS > Port A or B > BERT > Filter A1 for port A or B1 for port B

Ensure there are no errors registered

13. Return to RESULTS > Port A or B

14. Click on Frame layer statistics

Ensure that transmitted frames match the ones received.


Ethernet Test Results:

Ethernet Test case Node / Slot / Port BERT Results

Standard conditions 1 / 1/ P1 <‐> 2 / 1 / P1

2 / 1/ P1 <‐> 3 / 1 / P1

1 / 1/ P1 <‐> 3 / 1 / P1

8. Traffic Testing (VPWS ‐RS232)

This test procedure describes the system level traffic test for the RS‐232 1 & 4‐port options (90350‐01 &

‐02) Access Cards. The RS‐232 units to be tested will be part of a standard validation system. The system

will be configured according to the test setup tables defined in the Traffic table section.

The xGenius.Data option provides DTE and DCE testing on RS‐232 (V.24) using a proprietary datacom

adaptor cable. To activate this option, follow the steps below. JPAX will act as a DCE device. So, set EX

Mode to DTE and use the DTE datacom cable.

1. Insert Datacom module (PHM‐20) in modules slot

2. From Home ( ) > CONFIG > Mode > Select Datacom endpoint

3. From CONFIG > Datacom

Press Line > Interface > select V.24/RS‐232

Select Emulation > DTE

Select Operation > synchronous / asynchronous


Set the Line rate, if you have set the line rate to Nx64 or Nx56 configure the Nx64/56 factor as

well. If you have set the line rate to User, configure the User rate.

Configure the TD clock circuit > TTC (DTE source) with DTE emulation or TC (DCE source) with

DCE emulation

Set TX clock offset (ppm) if required

For datacom BER and the ITU‐T G.821 require a test pattern which can be configured as below:

1. Go to Datacom > Test pattern

2. Select on of available RX patterns, the PRBS 215 is selected by default however other patterns

can be selected from the list: PRBS 6, PRBS 7, PRBS 9, PRBS 11, PRBS 15, PRBS 20, PRBS 23,

QRSS, All ones or their inverted versions, QBF / FOX) or a user defined pattern by selecting

Word in the list

If the received and the expected patterns do not match, an LSS defect will be raised. Isolated bit errors

are displayed as TSE anomalies. Repeated or missing bits in the test pattern are accounted as slips.

3. If you have selected Word in step 3, enter the user‐defined 32‐bit pattern in RX Word in

hexadecimal format.

4. Configure the TX Pattern block (test pattern generator) in the same way that the RX Pattern

block just configured. By default a pattern match to RX us selected

The datacom interface has been configured and the test pattern is ready, the test can be started by

pressing the run key. The results can be showed following the below steps:

1. Click on RESULTS > Datacom

a. For synchronous mode, click on Defects:


b. For asynchronous mode, click on Anomalies:

Event Description

LOC Loss Of Clock. The clock for the

RD circuit (RC circuit) or the

clock TD circuit (TC or TTC

circuits) are not available or do

not have the right format.

LSS Loss of Sequence

Synchronization. This event

indicates that the expected test

pattern does not match the

actually received pattern.

All 0 This alarm occurs when all the user bit capacity is set to ‘0’.

All 1 This alarm occurs when all the user bit capacity is set to ‘1’.

Slips Either one bit is missing or

repeated in the received test

pat‐ tern. This error is usually

related with timing problems

within the network.

Event Description

FRM Frame anomaly. The‐character

does not have the correct

structure of start bits, data bits,

parity bit and stop bits.

PRTY Parity anomaly. The asynchronous

interface does not have the

correct even / odd parity.

TSE Test Sequence Error. One TSE is

equivalent to a single bit

difference between the

transmitted and the received test

pat‐ tern (PRBS or other).

TSBE Test Sequence Block Error. One of

the user‐configurable data blocks

of contains at least one TSE.


c. For both operation modes, it is also possible to view circuit map and related activity

from:

i. RESULTS > Datacom > Circuit map

If any of alarms LED are red, this indicate a problem. Otherwise a gray LED refers to a connection or a

signal is not been detected. You should check all circuit connections, Datacom setup and Handshake

signals from the map (see above).

The results in gray indicate the history which last been detected during the test and in which are no longer

present.

RS.232 Test Results:

RS‐232 Test cases Node / Slot / Port BERT Results


Traffic with fiber disruption 1 / 11 / P1 <‐> 2 / 11 / P1

Traffic with Core card removal 1 / 11 / P1 <‐> 2 / 11 / P1

RS.232 Ports Verification:

Repeat the RS.232 traffic test under standard conditions for each of the RS.232 available ports in the

system.

Record the results in the following table:


9. Traffic Testing (VPWS‐ C37.94)

This test procedure describes the system level traffic test for the C3794‐1A (90360‐01) & C3794‐4A

(90360‐02) Access Cards. The C37.94 units to be tested will be part of a standard validation system. The

system will be configured according to the test setup tables defined in the Traffic Table section.

An xGenius test set will be used to generate, send, receive, monitor and analyze all C37.94 traffic for

optical power, data propagation delay and bit error free operation of the optical ring.

The list of equipment including shelves and units is:

‐ Lentronics shelves as described in section Network Topology

‐ Two xGenius test sets with appropriate cables

xGenius configuration

1. Insert the IEEE C37.94 module (PHM‐21) in modules slot

2. Connect the IEEE C37.94 transceivers to your PHM‐21 module

3. Connect the optical cables to the SFPs into Port A (Port B is not enabled)

4. Connect the equipment to the device or network under test.

5. From the Home ( ) > CONFIG, the port configuration panel is displayed.

6. Select Mode and choose C37.94 endpoint, C37.94 monitor or C37.94 through, depending on the test

you wish to run.

7. Go to the Port A or Port B menu.

8. Enable optical transmission by selecting laser> on

9. If you are operating in C37.94 endpoint mode, configure the Port mode to either TX / RX to generate

and analyze traffic or Loopback to loop the traffic back to the origin.

10. Configure TX clock source to Synthesized or Recovered.

Note: The C37.94 monitor and C37.94 through modes do not accept TX clock source configurations.

11. If you have configured a Synthesized clock source you can optionally configure a frequency offset to the transmitter through the TX clock offset (ppm) control.


12. Press Frame to configure the framing settings for your test.

13. Configure encapsulation to either Unframed or C37.94.

1. If you have configured C37.94 in the previous step, configure the data rate either through TX

timeslots to any number between 1 and 12 or TX data rate.

Note: This value is a multiplicative factor for the basic 64 kb/s IEEE C37.94 bit rate. N=1 corresponds to

64 kb/s and N=12 to 768 kb/s.

14. Go to Test pattern 15. Configure TX Pattern and RX Pattern to suitable values. 16. To generate graphical representation and report for the result, follow these steps:

1. From the Home ( ) > Test > Event logger setup

2. Click on Enable > Yes 3. Select Port A event filter > BERT > TSE/SLIP/LSS

4. From the Home ( ) > Files ( ) > Report files

5. Click on Generate report > Yes 6. Select the preferred report format

17. Save this configuration as “C3794_test”. 18. Repeat the steps above for the second xGenius set.

BERT Test

1. Check the integrity of the IEEE C37.94 circuit by referring to Line, frame LED indications and from

the results as following:

A. Go to RESULTS > Port A > Line

2. The default BERT test pattern is PRBS 215 which can be modified from Test pattern menu

3. Complete the fiber connectivity according to the diagram below, then press the start button to

initiate the BERT test.


4. Go to RESULTS > Port A > Anomalies

5. Observe the following: A. If any of alarms LED are red, this indicate a problem. Otherwise a gray LED refers to a

connection or a signal is not been detected. You should check all C37.94 connections.

B. The results in gray indicate the history which last been detected during the test and in which are no longer present.

6. Record test result in the Test Result table below.

Propagation Delay Test

The xGenius has the capability of testing two types of delays on the network, Round trip Delay (RTD)

and One‐Way Delay (OWD) using a GPS or other external reference.

1. Testing Round trip Delay (RTD):

1) Enable optical transmission Port A > Enable > yes


2) Configure Tester A to Generate & Analyze traffic

i. Config > Port A > Port Mode > TX/RX

ii. Config > Port A > TX clock source > Synthesized

iii. Config > Port A > Laser > On

iv. Test > Delay test > Enable > Yes

v. Test > Delay test > Measurement mode > Round trip

3) It is necessary to cancel the intrinsic delay of the tester that may modify the results:

i. Disconnect the unit from the network and loop Tx ‐ Rx with a patch cord

ii. Test > Delay test > Adjust zero offset > Auto‐calibrate

iii. Go to Results > Delay (All delay parameters shall be zero)

iv. Once you have set the zero offset in Tester A, reconnect to the network

v. No special settings are required in the other unit

4) Configure Tester B to Loopback:

i. Config > Port A > Port Mode > Loopback

ii. Config > Port A > TX clock source > Recovered

iii. Config > Port A > Laser > On

5) Press RUN to start the test

6) Go to Home ( ) > Results > Delay test

7) The results are shown as below

2. Testing One Way Delay (OWD):

1) Configuring the built‐in GNSS receiver:

i. Connect the cable to the SMA and orient the antenna oriented to open sky


ii. Home > Config > Reference clock > Input clock > GNSS

iii. Press LEDS to check the status

iv. Wait for the REF and LOCK LEDs to become green as shown below

v. Repeat the same operation for the other unit

2) Go to Test > Delay test > Enable > Yes

3) Select One‐way from Test > Measurement mode >One way

4) Repeat the same configuration for the other unit

5) Press RUN to start the test

6) Go to Home ( ) > Results > Delay test

7) The results are shown as below


3. Delay is measured and reported in Microseconds (us) but can be changed to different unit

measurement.

4. Results can be exported as graphic and report format following the mentioned steps in BERT

testing procedure

5. Record test results in the Test Result table below.

Failure Test

1. Repeat the BERT and Delay Test from previous sections, introducing a) fiber disruption and b) core

card removal. Record test result in the Test Result table below.

C37.94 Test Results:

C37.94 Test case Node / Slot / Port BERT Results PDL Results


Traffic with fiber

disruption 1 / 10 / P1 <‐> 2 / 10 / P1

Traffic with Core card

removal 1 / 10 / P1 <‐> 2 / 10 / P1

C37.94 Ports Verification:

Repeat the C37.94 traffic test under standard conditions for each of the C37.94 available ports in the

system.



10. Traffic Testing (E1‐VPWS)

This test procedure describes the system level traffic test for the T1/E1‐4A Unit (90300‐01) Access

Cards. The T1/E1 units to be tested will be part of a standard validation system. The system will be

configured according to the test setup tables defined in the Traffic Table section.

xGenius is equipped with one single full featured 2048 kb/s (E1) port (Port C) and it may optionally

include a second port (Port D) to be connected to the unit.

E1 testing configuration is as the following:

1. From Home ( ) > CONFIG, the port configuration panel is displayed.

2. Select Mode to enter in the mode selection Menu

3. Select E1/T1 Endpoint

4. From CONFIG > Port C > port mode

5. Select operation mode > TX/RX or Loopback

6. Select Connector > Balanced (RJ45 75 Unbalanced (BNC 120 7. Connect the unit using to the appropriate interface in port C (RJ45 75 or BNC 120 )

8. Select Auto‐configuration > Enable > Yes

9. If the configuration were successful, it will be shown In the status as below

10. If Port D is not used, from CONFIG > Port C > port mode > Disabled


11. Press RUN to start the test 12. Go to Home ( ) > Results > Port C

13. Select Anomalies.

14. The results are reported as per counts, error rates and seconds. Also, the E1 Summary Panel

indicates test results per frame block as below

15. Any results, including Alarms, are also can be exported as a report or as a graphic following

the above‐ mentioned steps in C37.94 BERT testing procedure

Check the results and observe the following:

The result indicator is green with “PASS” reflect the test pattern objectives have been met.

If an Anomaly (Code, FAS, CRC, CAS, REBE, MFAS, TSE, TSBE) occurs, the corresponding gray

history area will remain until the test is restarted.

The real‐time Line, FAS, CRC and CAS (with Framed data) indicators at the left of the screen are Green. Red indicates a problem. If these indicators are red, should check all circuit connections and E1 setup.


E1 Test Results:

E1 Test cases Node / Slot / Port BERT Results


Traffic with fiber disruption 1 / 13 / P1 <‐> 2 / 13 / P1

Traffic with Core card removal 1 / 13 / P1 <‐> 2 / 13 / P1

E1 Ports Verification:

Repeat the E1 traffic test under standard conditions for each of the E1 available ports in the system.


End‐of‐Document

junglepax factory acceptance test procedure with albedo … · 2021. 3. 3. · junglepax factory...

Documents