|
|
This chapter describes the turn up and test procedures for the ONS 15200 system. This chapter includes the ONS 15252 MCU turn up, the ONS 15201 SCU turn up, and the system span test. "Acceptance Test Plan" contains the tables and forms that you must complete during system turn up and testing.
This chapter also describes test procedures for the ONS 15216 MUX/DEMUX system. The ONS 15216 MUX/DEMUX is an optical multiplexing and demultiplexing system, with 32 channels with 100-GHz spacing on the ITU grid. Channels 21 to 39 are handled in the ONS 15216 RED MUX/DEMUX and channels 41 to 59 are handled in the ONS 15216 BLUE MUX/DEMUX. When it is protected system with up to 32 channels, four ONS 15216 MUX/DEMUX are used: one RED MUX/DEMUX for the A side and one for the B side and one BLUE MUX/DEMUX for the A side and one for the B side.
All ONS 15216 MUX/DEMUX that are mentioned in this chapter are red band filters. For further details, see the ONS 15216 MUX/DEMUX documentation.
This chapter also includes test procedure for the ONS 15216 OADM. The ONS 15216 OADMs are passive units consisting of 100 GHz unidirectional 1-, 2-, and 4-channel modules. Each 1-, 2- or 4-channel ONS 15216 OADM module transmits in opposite directions (designated as east and west) in the 1530.33 to 1560.61-nm wavelength range. For further information see the ONS 15216 OADM documentation.
This chapter does not include test procedure for the ONS 15501 EDFA. The ONS 15501 EDFA is an optical amplifier that can amplify the optical signal. Before installing the ONS 15501 EDFA please check in the Metro Planner to determine on which side the ONS 15501 EDFA should be installed. For further details see the documentation of the ONS 15501 system.
You need the following equipment to turn up and test the ONS 15200 system:
This section describes how to set up the NCB module so you can communicate with the MCU and SCUs. It also describes how to configure the ONS 15200 network.
Step 2 Use HyperTerminal to configure the EIA/TIA-232 parameters listed in Table 4-1. See the following substeps for an example of the procedure you may follow when using HyperTerminal:
 |
Note The following substeps are an example of the steps you might follow when using HyperTerminal to configure the EIA/TIA-232 parameters. Not all HyperTerminal installations are the same. The following example lists the necessary steps when using the Microsoft Windows NT operating system. |
a. Choose Start > Programs > Accessories > Communications > HyperTerminal. HyperTerminal opens.
b. In the Connection Description dialog box, type a session name and click OK.
c. In the Connect To dialog box, choose COM1 from the Connect Using drop-down list. Click OK.
d. In the COM1 Properties dialog box, choose the port settings shown in Table 4-1. Click OK.
f. In the Properties dialog box, click the Settings tab and then click the ASCII Setup button.
g. On the ASCII Setup dialog box, check Send line ends with line feeds. Click OK until all dialog boxes are closed. Leave the HyperTerminal window open.
Step 3 After you have connected the CIM EIA/TIA-232 adapter cable (Step 1) and set the parameters in Table 4-1, press Enter in the HyperTerminal window. The system responds with a logon prompt. Press Enter again. Because no password is needed, press Enter a third time.
Step 2 The computer used to connect directly to the ONS 15200 system must be configured to use the same subnet and subnet mask as the ONS 15200 system. To configure the IP address, refer to the Microsoft Windows user documentation for instructions.
Table 4-2 shows the default NCB address assigned in the factory.
| Item | Specification |
|---|---|
Step 2 Log in with the proper HyperTerminal settings, by pressing Enter twice.
Step 3 Create a user with administrator privileges:
a. At the NCB:> prompt, type create user user1 and press Enter. The system responds: Created user1. The user1:# prompt appears on the screen.
b. At the user1:# prompt, type password password1 and press Enter to create a password for a new user.
c. Type privileges administrator and press Enter to assign administrator privileges to the new user.
d. Type exit to return to the NCB:> prompt.
e. At the NCB:> prompt, type commit user user1 to finish adding a user with administrator privileges.
Step 4 Create a user with operator privileges:
a. At the NCB:> prompt, type the command create user user2 and press Enter. The system responds: Created user2. The user2:# prompt appears on the screen.
b. Type password password2 and press Enter to create a password for the new user.
c. Type privileges operator and press Enter to assign operator privileges to the new user.
d. Type exit to return to the NCB:> prompt.
e. At the NCB:> prompt, type commit user user2 to finish adding a user with operator privileges.
Step 5 Set the initial IP address of the NCB module:
a. At the NCB:> prompt, type con sys and press Enter.
b. At the NCB:= prompt, type ipconf ipaddr subnet gateway and press Enter.
Step 6 Reboot the system for the changes to take effect. At the NCB:= prompt, type reboot and press Enter.
Step 7 Disconnect the CIM EIA/TIA-232 adapter cable. The Subnetwork Manager on the NCB module now has an IP address and can be accessed directly at the Ethernet port on the NCB module front panel with the standard protocols (Telnet, ftp, and http), provided that the subnet mask and gateway are set appropriately and that your PC has an appropriate IP address.
Step 8 Connect a crossover Ethernet cable to the PC and the Ethernet port on the NCB module. Alternatively, connect the NCB module via CAT5 cable to LAN/WAN and to the PC/laptop.
Step 9 Start a Telnet session on the host computer by typing the command telnet ipaddr at a command prompt (MS-DOS prompt).
Step 10 Log into the system as a user with operator privileges.
Step 11 Set the system time (in 24-hour format), if necessary. A soft reboot does not restart the clock.
a. At the NCB:> prompt, type con sys and press Enter.
b. At the NCB:= prompt, type the time yyyy:mm:dd hh:mm:ss command and press Enter.
c. At the NCB:= prompt, type exit and press Enter to return to the NCB:> prompt.
Step 12 At the NCB:> prompt, type show inventory and press Enter. The ID of the SNM you are logged into displays.
|
Note For the next step you need at least SNM 1.1. If you have SNM 1.0 see Cisco ONS 15200 Command Line Interface manual. |
Step 13 Set the unit ID of the NCB module. This step is necessary for the NCB to scan the network for nodes.
a. At the NCB:> prompt, type and press Enter.
b. At the Network: # prompt, type configure snm <snm_xxx> and press Enter.
c. At the snm_xxx: # prompt, type unitid snm_# (where snm_# is snm_1 or snm_2) and press Enter.
d. At the snm_xxx: # prompt, type commit.
e. At the snm_xxx: # prompt, type exit twice to return to the NCB:> prompt.
Step 14 At the NCB:> prompt, type show inventory and press Enter. Verify that an inventory of all installed CLIP modules appears, and the CLIP module slot number and ITU channel number match the information in Table 4-3 (not shown until you are manager of the CLIP). Complete Step A in Table A-3. The NCBs and CLIPs are not assigned at this point to any MCU or SCU.
Step 15 Create the MCU and its container name:
a. At the NCB:> prompt, type configure network and press Enter.
b. At the Network: # prompt, type create mcu neid and press Enter. This creates the MCU, and associates it with a network element (NE) ID (neid).
c. At the Network: # prompt, type name mcu_name and press Enter. This sets the container name.
Step 16 Configure the MCU:
a. At the mcu_name: # prompt, type insert snm_##### and press Enter.
b. At the mcu_name: # prompt, type insert clip_### and press Enter. Repeat for all CLIPs.
Step 17 Create the SCUs and the container names:
a. At the Network: # prompt, type create scu neid and press Enter. This creates the SCU and associates it with an NE ID (neid), an arbitrary number which must be SCU specific.
b. At the scu_name: # prompt, type name scu_name and press Enter. This sets the container name.
Step 18 Configure each SCU:
Step 19 Set available NCBs as the primary or secondary manager:
a. At the Network: # prompt, type con clip clip_xxxx. Press Enter.
b. To set the NCB as the primary manager, type primary this. To set the NCB as the secondary manager, type secondary this.
Step 20 Set up performance monitoring, if applicable:
a. Remain in the configure network mode.
b. At the Network: # prompt, type configure clip clip_xxx and press Enter.
c. At the clip_xxx:# prompt, type pm on and press Enter.
d. Type commit and press Enter.
This section describe how to install an additional SCU in the network.
To install an additional channel in an ONS 15200 system, see the "Additional Channel Installation" procedure. To add a channel, two CLIP modules are necessary at different nodes, either an MCU or an SCU.
Step 2 Ensure that the A side is activated on the SCU by looking at the LED or through a management interface.
Step 3 Ensure that all channels are present on the MCU B side.
Step 4 Ensure that only the expected channels are visible on the MCU A side, i.e., the channels between the new SCU and the MCU A side.
Step 5 Repeat 1 to 4 for Rx B and Tx A.
Step 6 Check the transmission line as described in the "Channel Addition Using an ONS 15201 SCU" procedure.
This section describes how to add an SCU in the SNM software.
Step 2 Check that you have the proper NCB part number and revision number. SNM Rel 1.1 requires a minimum NCB board level of 800-09474-02.
a. Enter configure system mode by typing config system and press Enter.
b. Type version and press Enter.
c. Verify that the NCB Part No shown has -02 at the end, and that it agrees with the number above.
If it does not, contact TAC to get the board replaced.
Step 3 Type show inventory and press Enter. The only thing that should show up is the NCB board you are connected to. Observe and write down the name of the NCB/SNM.
Step 4 Set the unit ID (unitid) on the NCB, by configuring the SNM.
At the NCB:> prompt, type configure snm snm_xxxxx and press Enter.
Step 5 Set unitid to either snm_1 or snm_2, according to preference. If two NCBs share the same CAN bus, they have to have different unitids. Type unitid snm_1 or unitid snm_2 and press Enter. Type exit when finished to get back to the login prompt. Type commit snm to save the information to file.
Step 6 After about 15 seconds, type show inventory and press Enter to get the inventory displayed. This should allow the system enough time to create inventory, but depending on your particular configuration it may take longer time.
Step 7 If you want to use SNM as a manager, set it as the primary or secondary manager of the different CLIPs according to your preference.
a. At the NCB:> prompt, go into network configuration mode by typing configure network and press Enter.
b. Type configure clip clip_xxxxx and press Enter.
c. Type primary this and press Enter.
d. Type exit and press Enter to get back to configure network mode.
To assign a secondary manager:
a. If not in network configuration mode, enter it by typing configure network and press Enter at the prompt.
b. Type configure clip clip_xxxxx and press Enter.
c. Type secondary this and press Enter.
d. Type exit and press Enter to get back to configure network mode.
Step 8 Define your MCUs/SCUs (containers). To create an MCU from configuration network mode (after the command configure network is executed), type create mcu neid and press Enter, where neid is an identifier, an arbitrary number. The number neid has to be unique. To create an SCU from network configuration mode, type create scu neid, where neid is an identifier, an arbitrary number unique for the SCU.
Step 9 Although it is not required, we suggest that you name each MCU that you create.
a. At the mcu_x_y:# prompt, type name <xxxxx> where <xxxxx> is your choice of MCU name and press Enter.
b. Type exit and press Enter to get back to the network configuration menu.
Step 10 Although it is not required, we suggest that you name each MCU that you create.
a. At the scu_z:# prompt, type name yyyyy where yyyyy is your choice of SCU name and press Enter.
b. Type exit and press Enter to get back to the network configuration menu.
Step 11 Insert your CLIPs and SNMs into the defined containers (MCUs and SCUs).
From the configuration network mode, for all CLIPs assigned to a particular MCU, do the following:
a. Type configure mcu zzzzz where zzzzz is mcu_name of the MCU to be configured and press Enter.
b. Type insert clip_xxxxx and press Enter, and repeat this step for all CLIPs concerned.
c. Type insert snm_yyyyy and press Enter.
d. Type exit and press Enter to get to network configuration mode
From the configuration network mode, for the CLIP assigned to a particular SCU, do the following:
a. Type configure scu wwwww where wwwww is scu_name of the SCU to be configured and press Enter.
b. Type insert clip_xxxxx and press Enter.
c. Type exit and press Enter to get to network configuration mode.
Although it is not required, we suggest that you name each CLIP.
a. At the configure network prompt, type configure clip clip_xxxxx and press Enter.
b. Type name zzzzz where zzzzz is what you want the CLIP to be called and press Enter.
d. Type commit clip and press Enter to save the change to file.
Step 12 Although it is not required, we suggest that you name each SNM.
a. At the configure network prompt, type configure snm snm_yyyyy and press Enter.
b. Type name yyyyy where yyyyy is what you want the snm to be called and press Enter.
d. Type commit snm and press Enter to save the change to file.
Step 13 At the configure network prompt, issue a commit network and press Enter to create a network.cfg file for the network. Type exit to exit network configuration mode.
Step 14 Type show inventory and press Enter. Make sure all of the expected hardware in your system appears in the inventory.
This section describes how to turn up and test an ONS 15252 MCU.
All procedures must be completed in the order given.
Table 4-3 ONS 15200 Wavelengths Plan for Release 2.0
| Channel Number | Frequency (THz) | Wavelength (nm) | Remarks |
|---|---|---|---|
Step 2 Compare the data in Table A-5 with data provided by the network planner, and verify that the data is consistent. Complete Step A of Table A-4.
Step 3 Check wavelength and output power on the A side:
a. Connect a fiber from the lower 50 NAM output port to a wavelength meter or an OSA.
b. Set the wavelength range to 1530 and 1570 nm. Make sure all expected wavelengths are recorded.
Record the wavelength and output power of all channels in Table A-6.
Step 4 Check wavelength and output power on the B side:
a. Connect a fiber from the upper 50 NAM output port to a wavelength meter or an OSA.
b. Set the wavelength range to 1530 and 1570 nm. Make sure all expected wavelengths are recorded.
Record the wavelength and output power of all channels in Table A-7.
|
Note Your network planner should provide the following values: expected output power, maximum, and minimum. Actual transmit power on the ONS 15216 MUX/DEMUX Monitor port must fall within the range provided by the network planner. |
Use the following steps to check DWDM receivers and client transmit levels:
Start with the A side MUX/DEMUX.
Step 2 Attenuate the DWDM line between COMMON OUT on the MUX side and the COMMON IN on the DEMUX side of the ONS 15216 MUX/DEMUX.
Step 3 Make sure the optical power levels on all receivers are within specification.
The receiver operating range is -31 and -8 dBm, but the default warning thresholds of -28 and -10 should be used on all CLIP interfaces.
Step 4 Record the attenuated power level for each channel in Table A-8.
Step 5 Retrieve the DWDM receive level:
a. At the NCB:> prompt, type show power. Press Enter. This retrieves the measured optical power levels from the DWDM receivers. Record the values in Table A-8.
b. Calculate the expected receive power on the A and B sides and record the values in Table A-8.
Step 6 Set the data rate for each path if the desired rate differs from the default value. (The default is OC-48/STM-16.)
a. At the con net:> prompt, type configure path path_xxxxx_yyyyy, where xxxxx is the neid of the first CLIP, yyyyy is the neid of the second CLIP . Press Enter. (The CLIP neid can be found by typing the show inventory command.)
b. Type list value and press Enter. Verify the data rate.
c. To change the data rate, type datarate rate, where rate is STM-1, OC-3, STM-4, OC-12, STM-16, OC-48, or gbit_eth. Press Enter.
d. Type list value and press Enter to verify that the change was accepted.
Step 7 Check the client side transmit levels:
a. Connect a fiber from the transmit port of the signal generator to the client IN port for the first CLIP (slot one). The valid input range on the client side receiver is -3 to -18 dBm.
b. Run a jumper cable from the client OUT port of the first CLIP to your power meter.
c. Set the wavelength on the power meter to 1310 nm.
d. Measure and record the output power of the client side transmitter in Table A-9.
e. Repeat Steps a to d for each remaining CLIP. Be sure to the test set to the IN port of the current CLIP and the power meter to the OUT port of the same CLIP.
Continue with the following steps to verify that no alarms exist:
a. Connect a fiber from the transmit port of the signal generator to the client IN port on the first CLIP (1). The default input range on the client side receiver is -6 to -16 dBm.
b. Run a jumper cable from the Client OUT port of the first CLIP module to the client IN port of the second CLIP module (2).
c. Repeat until all CLIP modules are daisy-chained together with the last CLIP module's OUT port returning to the test set, as shown in Figure 4-6.
Step 2 Type show alarm and press Enter. Verify that no alarms exist and that no red diodes are lit on any of the NAMs or on the CIM. Complete Step B in Table A-4.
If the network design does not provide optical protection, skip the "Check Optical Protection on the DWDM Side" procedure and proceed to the "Test the Bit Error Rate" procedure.
Continue with the following steps to check optical protection. Use the test setup shown in Figure 4-3.
a. Record the current switchmode setting for each CLIP module in Table A-10. You will need to revert to the original switchmode setting after checking the bit error rate.
b. At the NCB:> prompt, type conf clip clip_xxx (where xxx is the serial number of the CLIP module) and press Enter.
c. Type cd dwdm and press Enter.
d. Type list value and press Enter.
e. Type switchmode automatic and press Enter.
Step 2 Remove the connection between the COMMON OUT port of the MUX side of the ONS 15216 MUX/DEMUX A-sid' and the COMMON IN port of the ONS 15216 MUX/DEMUX B-side. See Figure 4-3. Verify that the Active LED on the A side goes out and the B side switches from Standby to Active on the CLIP module. Complete Step C in Table A-4.
Step 3 Reconnect the the fiber jumper and verify that the A-side green Standby LED is illuminated on the CLIP module and that the B-side Active LED remains illuminated. Complete Step D in Table A-4.
Step 4 Remove the connection between the COMMON OUT port of the MUX side of the ONS 15216 MUX/DEMUX B-side and the COMMON IN port of the ONS 15216 MUX/DEMUX 'A-side. See Figure 4-3. Verify that the Active LED on the B side turns off. Verify that the A side switches from Standby to Active on each CLIP module. Complete Step E in Table A-4.
Step 5 Reconnect the fiber jumper and verify that the B-side green Standby LED is illuminated on each CLIP module and that the A-side Active LED remains illuminated. Complete Step F in Table A-4.
Step 6 Repeat Step 2 to Step 5 for each CLIP.
Step 7 Before continuing with the bit error rate testing, complete the following:
Continue with the following steps (as applicable) to test the BER:
|
Note The maximum number of spans is six for a 3R CLIP, and two for a 2R CLIP. |
Step 2 Test A-side protected channels and all non-protected channels of the node:
a. Interrupt the connection from the ONS 15216 A-side MUX/DEMUX COMMON OUT to the B-side MUX/DEMUX COMMON IN. All of the protected channels should have the active light on the A side illuminated and no LED illuminated on the B side. Unprotected channels should have either the Active light on the A side illuminated or no lights illuminated. Bit errors are caused by a broken connection of the unprotected channels.
b. Reconnect the removed patch cord and ensure that the A-side Active LED remains illuminated on protected CLIP modules and that all unprotected CLIP modules are active on either the A side or B side.
c. Clear all errors on the test set and run the BER test error-free for 15 minutes. Complete Step G in Table A-4.
Step 3 Test B-side protected channels and all non-protected channels of the NAM:
a. Interrupt the connection between the COMMON OUT of the B-side MUX/DEMUX and the COMMON IN of the A-side MUX/DEMUX. All of the protected channels should have the B-side Active LED illuminated and no LED illuminated on the A side. Unprotected channels should either have the B-side Active LED illuminated or no LED illuminated. Bit errors are caused by a broken connection.
b. Reconnect the patch cord and verify the following: the B-side Active LED remains lit on the protected CLIP modules, the A-side Standby LED illuminates, and all unprotected CLIP modules are Active on either the B side or the A side.
c. Clear all errors on the test set and run the BER test error-free for 15 minutes. Complete Step H in Table A-4.
Step 4 Return the CLIP switchmode setting to the original setting (Table A-10).
Use the following procedures to turn up and test the ONS 15201 SCU with the CSM and the ONS 15216 OADM. Complete the procedures in the order shown.
Step 2 Open Maintenance Manager and expand the ONS 15201 SCU information.
Step 3 Record the information for the CLIP module in Table A-12. Locate the CLIP information in the following places:
Step 4 Compare data in Table A-12 with data provided by the network planner, and verify that the data is consistent. Complete Step A in Table A-11.
Step 5 Check the output power. Unprotected channels will have an output on only one of the DWDM ports.
a. Connect an optical-fiber jumper cable from the A-side output port to a wavelength meter, or an OSA.
b. Set the wavelength range on the OSA to 1530 and 1570 nm. Record the wavelength and the output power in Table A-13.
c. Repeat Steps a to b for the B side and record the information in Table A-13.
Continue with the following steps to check DWDM receivers and client transmit levels. Use the test setup shown in Figure 4-6.
Step 6 Attenuate the DWDM transmit port.
a. Connect the SCU A out port with the West add port of the ONS 15216 OADM-1.
b. Connect the West out port of the ONS 15216 OADM-1 through the variable attenuator that is include in the ONS 15216 OADM-1 with the West in port of the ONS 15216 OADM-1.
c. Connect the West drop port to the SCU A in port. (Figure 4-6). Attenuate the ONS 15216 OADM-1 so that the optical power measured is within the DWDM receiver specification. The receiver operating range is -31 and -8 dBm, but the default warning thresholds of -28 and -10 should be used on all CLIP interfaces.
d. Record the A-side attenuated power level in Table A-14.
e. Connect the SCU B out port with the East add port of the ONS 15216 OADM-1.
f. Connect the East out port of the ONS 15216 OADM-1 through the variable attenuator that is include in the ONS 15216 OADM-1 with the East in port of the ONS 15216 OADM-1.
g. Connect the East drop port to the SCU B in port (Figure 4-6). Attenuate the ONS 15216 OADM-1 so that the optical power measured is within the DWDM receiver specification. The receiver operating range is -31 and -8 dBm, but the default warning thresholds of -28 and -10 should be used on all CLIP interfaces.
h. Record the B-side attenuated power level in Table A-14.
i. Check the received power using the Maintenance Manager, and record the values in Table A-14. Observe that the levels on the receivers depend on how the OADM-1 is configured.
To calculate the expected receive power, take the measured transmit power and subtract the associated losses caused by the channel dropping. Actual received power should be within 3 dB of the expected received power.
Add p—Set attenuated value of the OADM-1 (with attenuators attached) on the OUT port of the SCU side in use
3—Value (in dB) that must be subtracted to account for the combined loss from the connectors and drop in the CSM
Step 7 Double-click the data rate parameter in Maintenance Manager, and set the data rate to OC-48 (datarate stm_16). Verify the data rate.
Step 8 Check the client side transmit levels.
a. Connect a fiber from the transmit port of the signal generator to the client IN port for the CLIP. (The valid input range on the client side receiver is -3 to -18 dBm.)
b. Run a jumper cable from the client OUT port of the CLIP to your power meter.
c. Set the wavelength on the power meter to 1310 nm.
d. Measure and record the output power of the client side transmit in Table A-15.
Step 9 Disconnect the power meter from the client side output and run a fiber from the client OUTPUT interface to the receive end of the signal generator.
|
Note This is a general picture, not corresponding to the actual layout of the OADM-1. |
Step 10 Verify that the red LED on the ONS 15201 SCU is not illuminated. Click on the CLIP alarms folder and ensure that no alarms are active. Complete Step B in Table A-11.
If the network design is not configured with protected channels, skip the "Check Optical Protection" procedure and proceed to the "Test the Bit Error Rate (Single SCU)" procedure.
Continue with the following steps to check optical protection. Use the test setup shown in Figure 4-6.
|
Note Before changing the switchmode, record the current setting for the CLIP module in Table A-15. You will need to reset the original switchmode setting after checking the bit error rate. |
a. Record the current switchmode setting for each CLIP module in Table A-16. You will need to revert to the original switchmode setting after checking the bit error rate.
b. At the NCB:> prompt, type conf clip clip_xxx (where xxx is the serial number of the CLIP module) and press Enter.
c. Type cd dwdm and press Enter.
d. Type list value and press Enter.
e. Type switchmode automatic and press Enter.
Step 2 Remove the fiber jumper cable from the B side INPUT of the SCU to simulate a break in the B side path.The Standby green LED should go out. The Active LED for the A side should be illuminated. Complete Step C in Table A-11.
Step 3 Reconnect the fiber jumper cable pulled in Step 2. The Standby green light for the B side should be illuminated, and the A side Active LED should remain illuminated. Complete Step D in Table A-11.
Step 4 Remove the fiber jumper cable from the A side INPUT of the SCU and verify that the Active LED on the A side goes out and the B side switches from Standby to Active. Complete Step E in Table A-11.
Step 5 Replace the jumper on the A side and verify that the A green Standby LED is illuminated and that the B Active LED remains illuminated. Complete Step F in Table A-11.
Continue with the following steps, if applicable, to test the bit error rate for a single SCU. Use the test setup in Figure 4-6.
If using multiple SCUs at one site, skip to next section.
a. Remove the jumper cable from the B-side input of the SCU and verify that the A side is Active.
b. Reconnect the B-side jumper cable. Verify that the A-side Active LED and the B-side Standby LED are illuminated.
c. Clear all errors on the test set and run the BER test error-free for 15 minutes. Complete Step G in Table A-11.
Step 2 Test the B-side protected channel or unprotected channel:
a. Remove the jumper cable from the A-side input of the SCU. For a protected SCU or an unprotected SCU configured as 0/100, verify that the B side is Active. For an unprotected SCU configured as 100/0, verify that neither the A side or B side is Active.
b. Reconnect the A-side jumper cable. For a protected SCU, verify that the B-side Active LED and the A-side Standby LED are illuminated. For an unprotected SCU configured as 0/100, the B-side Active will be illuminated with no Standby, and for an unprotected SCU configured as 100/0, the A-side Active will be illuminated with no Standby.
c. Clear all errors on the test set and run the BER test error-free for 15 minutes. Complete Step H in Table A-11. The turn up and test for a single ONS 15201 SCU is complete.
Step 3 Reset the original switchmode settings (Table A-16).
Continue with the following steps to test the bit error rate for multiple SCUs at a site. Figure 4-7 displays the test setup with an ONS 15216 OADM2 (2 channels).
a. Connect the signal generator transmit fiber to the client INPUT port of the bottom SCU.
b. Connect the receive end of the signal generator to the top SCU client-side OUTPUT port.
c. Daisy-chain client INPUT and OUTPUT ports of both SCUs together as shown in Figure 4-7.
d. Configure the ONS 15216 OADM-2 so that the power level received is compliant with the specification of the CLIPs.
e. Ensure that all expected wavelengths are present on the Monitor out port on both the east and west sides of the OADM-2. Verify that the level of the channel to be dropped at the SCU is within operating levels of the DWDM receivers. As a rough guide, the input power should be between -25 and -10 dBm (receiver operating range is -30 and -8 dBm).
f. Repeat Step 3 d to e for all ONS 15216 OADM-2 output ports, connecting the SCU input port as shown in Figure 4-7.
Step 2 Test A-side protected channels and all unprotected channels.
a. Disconnect the jumper cable between the EAST out and EAST in ports (on the right side of the OADM-2).
b. Reconnect the cable and verify that all protected SCUs identify the A side as Active and the B side as Standby.
c. Clear all errors on the test set and run the BER test error-free for 15 minutes. Complete Step I in Table A-11.
Step 3 Test B-side protected channels and all unprotected channels.
a. Disconnect the jumper cable between the WEST OUT and WEST IN ports (on the right side of the OADM-2).
b. Reconnect the cable and verify that all protected ONS 15201 SCUs identify the B side as Active and the A side as Standby.
c. Clear all errors on the test set and run the BER test error-free for 15 minutes. Complete Step K in Table A-11.
Step 4 Reset the original switchmode settings (Table A-16).
Posted: Thu Apr 17 13:56:43 PDT 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
