Table Of Contents
Maintenance
12.1 Air Filter Inspection and Replacement
12.2 Fan-Tray Assembly Replacement
12.3 System Reset
12.4 Database Backup and Restore
12.5 Reverting to an Earlier Software Load
12.6 XTC-14 Card to XTC-28 Card Upgrade
12.7 Span Upgrades
12.8 Inhibit Protection Switching
12.9 Network Tests
12.9.1 Network Test Types
12.10 Network Test Procedures
12.10.1 Perform a Facility Loopback on a Source XTC Card
12.10.2 Perform a Hairpin Circuit on a Source Node XTC Card
12.10.3 Perform a Hairpin on a Destination Node XTC Card
12.10.4 Perform a Terminal Loopback on a Destination XTC Card
12.10.5 Perform a Facility Loopback on a Destination XTC Card
12.11 Creating Diagnostic Files
12.12 Optic Fiber Cleaning
12.13 Power Down the ONS 15327
Maintenance
This chapter describes procedures that can be necessary to maintain the Cisco ONS 15327, including:
•
Air filter inspection and replacement
•Fan-tray assembly replacement
•System reset
•Database backup and restore
•Reverting to an earlier software load
•XTC-14 card to XTC-28 card upgrade
•Span Upgrades
•Inhibit protection group switching
•Network Tests
•Creating diagnostic files
•Optic Fiber cleaning
•Powering down the ONS 15327
12.1 Air Filter Inspection and Replacement
The Cisco ONS 15327 contains an air filter that should be removed and visually inspected approximately every 30 days, depending on the cleanliness of the operating environment. The filter is reusable and made of a gray open-cell polyurethane foam, specially coated to provide fire and fungi resistance. Figure 12-1 illustrates the reusable fan-tray air filter. You do not need to remove the fan-tray assembly to remove the air filter.
Procedure: Inspect and Clean the Reusable Air Filter
Step 1 Move any cables that are routed in front of the fan-tray assembly and air filter so you can easily slide the filter out, as shown in Figure 12-1.
Step 2 Grasp the metal tab at the edge of the filter and slide the filter out of the bracket while being careful not to dislodge any dust that may have collected on the filter ( Figure 12-1).
Step 3 Visually inspect the filter material for dirt and dust.
Step 4 If the reusable air filter contains a concentration of dirt and dust, either vacuum the filter and replace it or wash the filter under a faucet with a light detergent. Prior to washing the air filter, replace the dirty air filter with a clean air filter (spare filters should be kept in stock). Wash the dirty air filter under a faucet with a light detergent.
Note Cleaning should take place outside the operating environment to avoid releasing dirt and dust near the equipment.
Step 5 If you washed the filter, allow it to completely air dry for at least eight hours.
Warning Do not put a damp filter back in the ONS 15327.
Step 6 Slide the filter back into the shelf ( Figure 12-1).
Figure 12-1 Removing and replacing the reusable fan-tray air filter
12.2 Fan-Tray Assembly Replacement
The fan tray is a removable drawer that holds fans and fan-control circuitry for the ONS 15327. You should not need to remove the fan-tray assembly unless a fan failure occurs and you must replace the fan-tray assembly. You cannot replace individual fans.
Procedure: Replace the Fan-Tray Assembly
Step 1 Move any cables that are routed in front of the fan-tray assembly and air filter away so you can easily slide the filter out.
Step 2 Loosen the fastening screw on the failed fan-tray assembly.
Step 3 Grasp the fan tray handle and gently pull it one inch out of the slot and wait until the fans stop.
Step 4 When the fans have stopped, pull the fan-tray assembly completely out of the shelf assembly ( Figure 12-2).
Figure 12-2 Removing a fan-tray assembly with installed cables
Step 5 Slide the new fan-tray assembly into the shelf until the electrical plug at the rear of the tray plugs into the corresponding receptacle on the backplane ( Figure 12-3).
Caution Do not force the fan-tray assembly into place while installing it. Forcing the fan-tray assembly into place can damage the connectors on the fan tray and/or the connectors on the back panel of the shelf assembly.
Figure 12-3 Replacing the fan-tray assembly
Step 6 Secure the fan tray into the slot using the attached fastening screw.
Step 7 Confirm that the FAN STATUS LED on the front of the fan tray is illuminated. This indicates that the fan tray is operating.
Note The FAN STATUS LED only illuminates when an XTC card is installed.
12.3 System Reset
You can reset the ONS 15327 XTC card using the Cisco Transport Controller (CTC) software, or by physically reseating the XTC card (card pull). A software reset reboots the XTC and reloads the operating system and the application software. Additionally, a card pull reset temporarily removes power from the XTC and clears all buffer memory.
You can apply a software reset to either an active or standby XTC without affecting traffic, but you should only perform a card pull on a standby XTC. If you need to perform a card pull on an active XTC, put the XTC into standby mode first by performing a software reset on the card.
Warning Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard.
Note A software or card pull reset of an active XTC card causes a standard Telcordia protection switch of less than 50 ms.
Procedure: Perform a Software Reset
Step 1 Log into the node where you will perform the software reset.
Step 2 In node view, right click on the XTC card to reveal a pull-down menu.
Step 3 Click Reset Card.
Step 4 Click Yes when the "Are You Sure?" dialog box appears.
Step 5 Click OK when the "Lost connection to node, changing to Network View" dialog box appears.
Step 6 Confirm that the XTC is in standby mode after the reset.
Note The XTC card takes several minutes to reboot. The Act/Stby LED glows amber during the reboot process. The AUTORESET alarm clears at the end of the boot process.
Procedure: Perform a Card Pull
Note To determine whether you have an active or standby XTC, position the cursor over the XTC card graphic to display the status.
Caution Always use the supplied electrostatic discharge band when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the front of the ONS 15327.
Step 1 If you need to perform a hard reset on an active XTC card, first perform a soft reset on the active XTC as described in the "Perform a Software Reset" procedure.
Step 2 When the XTC is in standby mode, unlatch both ejector levers on the XTC card.
Step 3 Physically pull the card at least partly out of the slot until the lighted LEDs turn off.
Step 4 Wait 30 seconds. Reinsert the card and close the ejector levers.
Step 5 The XTC will take several minutes to reboot. The Act/Stby LED glows amber during the reboot process. The AUTORESET alarm clears at the end of the boot process.
12.4 Database Backup and Restore
Each XTC card installed in the ONS 15327 contains two copies of the database. A save to the flash memory is written to the standby database, and the standby database then becomes the active database. The previously active database then becomes available for writing the next time. With dual XTCS, the standby XTC keeps both copies of the database synchronized with the active XTC as changes are made so that it is ready to take over control as needed. You can also store a back-up version of the database on the workstation running CTC. Backing up the database should be part of a regular ONS 15327 maintenance program at approximately weekly intervals and should also be completed when preparing an ONS 15327 for a pending natural disaster, such as a flood or fire.
Caution If you are restoring the database on multiple nodes, wait five minutes between each database restore.
Caution E10/100-4 cards lose traffic for approximately 90 seconds when an ONS 15327 database is restored. Traffic is lost during the period of spanning tree reconvergence. The CARLOSS alarm will appear and clear during this period.
Note The following parameters are not backed up and restored: node name, IP address, mask and gateway, and IIOP port. If you change the node name and then restore a backed up database with different node names, the circuits will map to the new node name. Cisco recommends keeping a record of the old and new node names.
Note You must back up and restore the database for each node on a circuit path in order to maintain a complete circuit
Procedure: Backup the Database
Step 1 Log into the node where you want to backup the database.
Step 2 In node view, click the Maintenance > Database tabs.
Figure 12-4 Backing up the ONS 15327 database
Step 3 Click Backup.
Step 4 Save the database on the workstation's hard drive or on network storage. Use an appropriate file name with the file extension .db, for example, database.db.
Step 5 Click Save and click OK on the Backup Database Complete dialog box.
Procedure: Restore the Database
Caution A restore from another node or an earlier backup may affect traffic.
Note The database must be restored to a compatible software version.
Step 1 Log into the node where you want to restore the database.
Step 2 In node view, click the Maintenance > Database tabs.
Step 3 Click Restore.
Step 4 Locate the database file stored on the workstation's hard drive or on network storage.
Step 5 Click the database file to highlight it.
Step 6 Click Open. The DB Restore dialog box appears. Opening a restore file from another node or from an earlier backup may affect traffic on the login node ( Figure 12-5).
Figure 12-5 Restoring the database-traffic loss warning
Step 7 Click Yes. The Restore Database dialog box monitors the file transfer ( Figure 12-6).
Figure 12-6 Restoring the XTC database-in-progress notification
Step 8 Wait for the file to complete the transfer to the XTC.
Step 9 Click OK when the "Lost connection to node, changing to Network View" dialog box appears. Wait for the node to reconnect.
12.5 Reverting to an Earlier Software Load
True Revert allows the system to revert to the protect system software image and its attendant database. The reversion does not affect DCC connectivity or traffic on circuits provisioned prior to the activation of the working software load. All versions of ONS 15327 software support this feature.
The ONS 15327 supports a working and protect software version on each XTC. The protect software version saves the provisioning that existed when the working load was activated. This means that the protect software load can only reinstate the circuits provisioned before the working load was activated. Circuits provisioned after the activation of the working load are lost during a revert.
When you click the Activate button after a software upgrade, the XTC copies the current working database and saves it in a reserved location in the XTC flash memory. If you later need to revert to the original working software load from the protect software load, the saved database installs automatically. You do not need to restore the database manually or recreate circuits.
Warning Working and protect XTCs must have the same version of the protect software load in order to revert to an earlier software load.
Tip The revert feature is useful if a maintenance window closes while you are upgrading CTC software. You can revert to the standby software load without losing traffic. When the next maintenance window opens, complete the upgrade and activate the new software load.
Note A revert to a maintenance release software load does not restore the database and no provisioning is lost. All other reverts do restore the database. (A maintenance release has a three-digit release number, e.g., 2.2.2).
Note Circuits created and provisioning performed after a software load is activated will not reinstate with a revert. The database configuration at the time of activation is reinstated after a revert. This note does not apply to maintenance reverts (e.g., 2.2.2 to 2.2.1).
Procedure: Revert to an Earlier Software Load
Step 1 Log into the node where you want to perform the revert.
Step 2 Record the IP address of that node.
Step 3 In node view, right-click the standby XTC card to reveal a pull-down menu.
Step 4 Choose Reset Card.
Step 5 Click Yes when the "Are You Sure?" dialog box appears.
Step 6 Click OK when the "Lost connection to node, changing to Network View" dialog box appears.
Step 7 Confirm that the XTC is in standby mode after the reset.
Step 8 Click the Maintenance > Software tabs.
Step 9 Click Revert.
The Revert button activates the protect software load. The ONS15327 node reboots and loses its connection to the CTC.
Step 10 Wait until the software upgrade finishes. This may take as long as 30 minutes.
Step 11 Completely close the browser.
Step 12 Restart the browser and log back into the node using the IP address you recorded in Step 2.
The browser downloads the CTC applet for the standby software load.
12.6 XTC-14 Card to XTC-28 Card Upgrade
This section explains how to upgrade XTC-14 cards to XTC-28 cards on an ONS 15327 with live traffic. The procedure is non-service affecting; the upgrade will cause a switch less than 50 ms in duration.
Note The UNEQ-P alarm might be raised during the upgrade if you have E10/E100-4 cards in the system. The alarm will appear and clear within a few seconds.
Note The MEA (card mismatch) alarm appears because CTC recognizes a mismatch between XTC card types. Disregard this alarm; it clears by the end of the procedure.
Step 1 Physically replace the standby XTC-14 card on the ONS 15327 with an XTC-28 card:
a. Unscrew and open the XTC-14 card ejector.
b. Slide the card out of the slot. This raises the IMPROPRMVL alarm which will clear when the upgrade is complete. Ensure that traffic is flowing over the 14 DS-1 ports.
c. Open the ejector on the XTC-28 card.
d. Slide the XTC-28 card into the slot along the guide rails.
e. Close the ejector and secure the screw.
f. Wait until the XTC-28 is fully booted and finishes synchronizing its software and database.
Note The LEDs will flash while the XTC-28 is loading.
Step 2 After the XTC-28 has finished synchronizing and is in standby mode, reset the active XTC-14:
a. In node view, right-click on the active XTC-14 and choose Reset from the pull-down menu ( Figure 12-7).
b. Traffic switches to the XTC-28.
Figure 12-7 Resetting the XTC card
Step 3 Physically replace the remaining XTC-14:
a. Unscrew and open the XTC-14 card ejector.
b. Slide the card out of the slot. This raises the IMPROPRMVL alarm which will clear when the upgrade is complete.
c. Open the ejector on the XTC-28 card.
d. Slide the XTC-28 card into the slot along the guide rails.
e. Close the ejector and secure the screw.
Step 4 Wait until the XTC-28 is fully booted and finishes synchronizing its software and database.
12.7 Span Upgrades
A span is the optical fiber connection between two ONS 15327 nodes. In a span upgrade, the transmission rate of a span is upgraded from a lower to a higher OC-N signal but all other span configuration attributes remain unchanged. With multiple nodes, a span upgrade is a coordinated series of upgrades on all nodes in the ring or protection group in which traffic carried at a lower OC-N rate is transferred to a higher OC-N. You can perform in-service span upgrades for the following ONS 15327 cards:
•OC-12 to OC-48
•OC-12 IR to OC-12 LR
•OC-48 IR to OC-48 LR
To perform a span upgrade, the higher-rate/long-reach optical card must replace the lower-rate/intermediate-reach card in the same slot. If the upgrade is conducted on spans residing in a BLSR, all spans in the ring must be upgraded. The protection configuration of the original lower-rate/intermediate-reach optical card (two-fiber BLSR, UPSR, and 1+1) is retained for the higher-rate/long-reach optical card.
When performing span upgrades on a large number of nodes, Cisco recommends that you upgrade all spans in a ring consecutively and in the same maintenance window. Until all spans are upgraded, mismatched card types will be present.
The Span Upgrade procedures require at least two technicians (one at each end of the span) who can communicate with each other during the upgrade. Upgrading a span is non-service affecting and will cause no more than three switches, each of which is less than 50 ms in duration. The Span Upgrade procedures can also be used to perform span downgrades.
Cisco recommends using the Span Upgrade Wizard to perform span upgrades from OC-12 to OC-48. Manual Span Upgrade procedures are mainly provided for OC-12 IR to OC-12 LR or OC-48 IR to OC-48 LR span upgrades, or as error recovery for the wizard. The Span Upgrade Wizard and the Manual Span Upgrade procedures require at least two technicians (one at each end of the span) who can communicate with each other during the upgrade. Upgrading a span is non-service affecting and will cause no more than three switches, each of which is less than 50 ms in duration.
Warning Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard.
Caution Do not perform any other maintenance operations or add any circuits during a span upgrade.
Note Span upgrades do not upgrade SONET topologies, for example, a 1+1 group to a two-fiber BLSR.
Note During the upgrade some minor alarms and conditions will be raised and will clear automatically. There should be no service-affecting (SA, Major, or Critical) alarms. If any service-affecting alarms occur, Cisco recommends backing out of the procedure.
BLSR Out of Sync alarms will be raised during span upgrades and will clear when the upgrade of all nodes is complete; a four-node BLSR can take up to five minutes to clear all of the Out of Sync alarms. Allow extra time for a large BLSR to clear all of the Out of Sync alarms.
Note If any of the cross connect cards reboot during the span upgrade, you must manually reset the card once the span upgrade procedure is completed on all the nodes in the ring.
Choose from four span upgrade options:
• "Perform a Span Upgrade Using the Span Upgrade Wizard" procedure
• "Perform a Manual Span Upgrade on a Two-Fiber BLSR" procedure
• "Perform a Manual Span Upgrade on a UPSR" procedure
• "Perform a Manual Span Upgrade on a 1+1 Protection Group" procedure
Downgrading can be performed to back out of a span upgrade. The procedure for downgrading is the same as upgrading except that you choose a lower-rate/intermediate-reach card type. You cannot downgrade if circuits exist on the STSs that will be removed (the higher STSs).
Note During the upgrade some minor alarms and conditions will be raised and will clear automatically. There should be no service-affecting (SA, Major, or Critical) alarms. If any service-affecting alarms occur, Cisco recommends backing out of the procedure.
BLSR Out of Sync alarms will be raised during span upgrades and will clear when the upgrade of all nodes is complete. Allow extra time for a large BLSR to clear all of the Out of Sync alarms.
Procedure: Perform a Span Upgrade Using the Span Upgrade Wizard
Warning Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard.
Caution Do not perform any other maintenance operations or add any circuits during a span upgrade.
Note The Span Upgrade Wizard only supports OC-N span upgrades. It does not support DS-3 upgrades.
Note You must use the Manual Span Upgrades when performing OC-12 IR to OC-12 LR or OC-48 IR to OC-48 LR span upgrades.
Step 1 Log into an ONS 15327 and ensure that no alarms or abnormal conditions (regardless of severity), including LOS, LOF, AIS-L, SF, SD, and FORCED-REQ-RING are present:
a. Navigate from the default (node) view to the network view.
b. In network view, click on the Alarms tab to view a list of current alarms.
c. In network view, click on the Conditions tab and click the Retrieve Conditions button to view a list of current conditions.
An unresolved alarm or abnormal condition is the most probable reason for upgrade failure. If alarms are present, refer to Chapter 14, "Alarm Troubleshooting."
Step 2 In network view, right-click the span you want to upgrade.
Step 3 Choose Span Upgrade from the pull-down menu ( Figure 12-8).
Figure 12-8 Span pull-down menu
Step 4 The first Span Upgrade dialog box appears ( Figure 12-9). Follow the instructions on the dialog box and the wizard will lead you through the rest of the span upgrade.
Note The <Back button is only enabled on Step 2 of the wizard; because you cannot back out of an upgrade via the wizard, close the wizard and initiate the manual procedure if you need to back out of the upgrade at any point beyond Step 2.
Figure 12-9 Beginning the Span Upgrade Wizard
Note Remember to attach the fiber after installing the OC-N cards.
Procedure: Perform a Manual Span Upgrade on a Two-Fiber BLSR
All spans connecting the nodes in a BLSR must be upgraded before the added bandwidth is available.
Step 1 Ensure that no alarms or abnormal conditions (regardless of severity), including LOS, LOF, AIS-L, SF, SD, and FORCED-REQ-RING are present on the BLSR that you will upgrade:
a. In network view, click the Alarms tab to view a list of current alarms.
b. In network view, click the Conditions tab and click the Retrieve Conditions button to view a list of current conditions.
An unresolved alarm or abnormal condition is the most probable reason for upgrade failure.
Step 2 Apply a force switch at both span endpoints (nodes) on the span that you will upgrade first:
a. At the first endpoint, in node view, click the Maintenance > Ring tabs.
b. Click either the West Switch or the East Switch field and choose FORCE RING from the menu.
c. Click Apply.
d. At the second endpoint, in node view, click the Maintenance > Ring tabs.
e. Click either the West Switch or the East Switch field and choose FORCE RING from the menu.
f. Click Apply.
Step 3 Remove the fiber from both endpoints and ensure that traffic is still running.
Step 4 Remove the OC-N cards from both endpoints. If you are performing a span upgrade from OC-12 cards to OC-48 cards, proceed to Step 5. If you are performing a span upgrade from IR cards to LR cards of the same type; for example, OC-12 IR to OC-12 LR, proceed to Step 8.
Step 5 From both endpoints, in node view, right-click on each OC-N slot and choose Change Card.
Step 6 In the Change Card dialog box, choose the new OC-N type.
Step 7 Click OK.
Step 8 Install the new OC-N cards in both endpoints and attach the fiber to the cards. Wait for the IMPROPRMVL alarm to clear and the cards to become active.
Step 9 When cards at both endpoints have been successfully upgraded and all the facility alarms (LOS, SD or SF) are cleared, remove the forced switch from both endpoints on the upgraded span:
a. At the first endpoint, in node view, click the Maintenance > Ring tabs.
b. Click the West Switch or the East Switch field and choose CLEAR from the menu.
c. Click Apply.
d. At the second endpoint, in node view, click the Maintenance > Ring tabs.
e. Click the West Switch or the East Switch field and choose CLEAR from the menu.
f. Click Apply.
The forced switch clears and traffic is running. If you have lost traffic, perform a downgrade. The procedure for downgrading is the same as upgrading except that you choose a lower-rate/intermediate-reach card.
Note You cannot downgrade if circuits exist on the STSs that you will remove (the higher STSs).
Step 10 Repeat these steps for each span in the BLSR.
When all spans in the BLSR have been upgraded, the span upgrade is complete.
Procedure: Perform a Manual Span Upgrade on a UPSR
Step 1 Ensure that no alarms or abnormal conditions (regardless of severity), including LOS, LOF, AIS-L, SF, SD, and FORCED-REQ-RING are present on the span that you will upgrade:
a. In node view, click on the Alarms tab to view a list of current alarms.
b. In node view, click on the Conditions tab and click the Retrieve Conditions button to view a list of current conditions.
An unresolved alarm or abnormal condition is the most probable reason for upgrade failure.
Step 2 Apply a force switch on the span that you will upgrade:
a. In network view, right-click the span and choose Circuits.
b. From the Circuits on Span dialog box in the Switch All UPSR Circuits Away field, choose FORCE.
c. Click Apply.
Step 3 Remove the fiber from both endpoints (nodes) on the span and ensure that traffic is still running.
Step 4 Remove the OC-N cards from both endpoints. If you are performing a span upgrade from OC-12 cards to OC-48 cards, proceed to Step 5. If you are performing a span upgrade from IR cards to LR cards of the same type; for example, OC-12 IR to OC-12 LR, proceed to Step 8.
Step 5 For both endpoints, in node view, right-click on each OC-N slot and choose Change Card.
Step 6 In the Change Card dialog box, choose the new OC-N type.
Step 7 Click OK.
Step 8 Install the new OC-N cards in both endpoints and attach the fiber to the cards. Wait for the IMPROPRMVL alarm to clear and the cards to become active.
Step 9 When cards at both span endpoints have been successfully upgraded and all the facility alarms (LOS, SD or SF) are cleared, remove the forced switch:
a. In network view, right-click the span and choose Circuits.
b. From the Circuits on Span dialog box in the Switch All UPSR Circuits Away field choose CLEAR.
c. Click Apply.
The forced switch clears and traffic is running. If you have lost traffic, perform a downgrade. The procedure for downgrading is the same as upgrading except that you choose a lower-rate/intermediate-reach card.
Note You cannot downgrade if circuits exist on the STSs that you will remove (the higher STSs).
Procedure: Perform a Manual Span Upgrade on a 1+1 Protection Group
When upgrading a 1+1 group, upgrade the protect line first regardless of which line is active. Both lines in a 1+1 group must be upgraded before the added bandwidth will be available.
Note If the switching mode is bidirectional in the 1+1 protection group, apply the Force command to only one end of the span, not both. The Clear command will apply to the end the Force was applied to. If the Force command is applied to both ends when the switching mode is bidirectional, it will cause a switch of more than 50 ms in duration.
Step 1 Ensure that no alarms or abnormal conditions (regardless of severity), including LOS, LOF, AIS-L, SF, SD, and FORCED-REQ-RING are present on the span that you will upgrade:
a. In node view, click on the Alarms tab to view a list of current alarms.
b. In node view, click on the Conditions tab and click the Retrieve Conditions button to view a list of current conditions.
An unresolved alarm or abnormal condition is the most probable reason for upgrade failure.
Step 2 Apply a force switch on the ports that you will upgrade, beginning with the protect port:
a. In node view, click the Maintenance > Protection tabs.
b. Under Protection Groups, choose the 1+1 protection group.
c. Under Selected Group, choose the protect port (regardless if it is active or standby).
d. From Switch Commands, click Force.
e. Click Yes on the confirmation dialog box.
Step 3 Repeat Step 2 for each port.
Step 4 Remove the fiber from both endpoints on the span and ensure that traffic is still running.
Step 5 Remove the OC-N cards from both span endpoints. If you are performing a span upgrade from OC-12 cards to OC-48 cards, proceed to Step 6. If you are performing a span upgrade from IR cards to LR cards of the same type; for example, OC-12 IR to OC-12 LR, proceed to Step 9.
Step 6 At both ends of the span, in node view, right-click the OC-N slot and choose Change Card.
Step 7 In the Change Card dialog box, choose the new OC-N type.
Step 8 Click OK.
Step 9 Install the new OC-N cards in both endpoints and attach the fiber to the cards. Wait for the IMPROPRMVL alarm to clear and the cards to become standby.
Step 10 When cards on each end of the line have been successfully upgraded and all the facility alarms (LOS, SD or SF) are cleared, remove the forced switch:
a. In node view for either endpoint, click the Maintenance > Protection tabs.
b. Under Protection Groups, choose the 1+1 protection group.
c. Under Selected Group, choose the port with the force on it.
d. From Switch Commands, click Clear.
e. Click Yes on the confirmation dialog box.
The forced switch clears and traffic is running. If you have lost traffic, perform a downgrade. The procedure for downgrading is the same as upgrading except that you choose a lower-rate/intermediate-reach card.
Note You cannot downgrade if circuits exist on the STSs that you will remove (the higher STSs).
Step 11 Repeat these steps for the other line in the 1+1.
When the other line in the 1+1 has been upgraded, the span upgrade is complete.
12.8 Inhibit Protection Switching
This procedure describes how to apply a lock on or lock out and how to remove a lock on or lock out on OC-12 or OC-48 protection groups.
Procedure: Apply a Lock On
Step 1 Use the following rules to determine if you can put the intended card in a Lock On state:
•For a 1+1 optical protection group, only the working card can be placed in the Lock On state.
Step 2 Log into the node where you will apply the Lock On.
Step 3 Click the Maintenance > Protection tabs.
Step 4 Under Protection Groups, click on the protection group where you want to apply a lock on.
Step 5 If you determine that the protect card is inactive and you want to apply the lock on to the protect card, make the protect card active:
a. Under Selected Group, click the protect card.
b. Under switch Commands, click Switch.
Step 6 Under Selected Group, click the active card you want to lock traffic onto.
Step 7 From Inhibit Switching, click on Lock On.
Step 8 Click Yes on the confirmation dialog box.
The Lock On has been applied and traffic cannot be switched to the opposite card. To clear the Lock On, see the "Clear a Lock On or Lock Out" procedure.
Procedure: Apply a Lock Out
Note Multiple Lock Outs in the same protection group is not allowed.
Step 1 Use the following rules to determine if you can put the intended card in a Lock Out state:
•For a 1+1 optical protection group, only the protect card can be placed in the Lock Out state.
Step 2 Log into the node where you will apply the Lock Out.
Step 3 In Node view, click the Maintenance > Protection tabs.
Step 4 Under Protection Groups, click on the protection group that contains the card you want to lock out.
Step 5 Under Selected Group, click the card you want to lock traffic out of.
Step 6 From Inhibit Switching, click on Lock Out.
Step 7 Click Yes on the confirmation dialog box.
The lock out has been applied and traffic is switched to the opposite card. To clear the Lock Out, see the "Clear a Lock On or Lock Out" procedure.
Procedure: Clear a Lock On or Lock Out
Step 1 Log into the node where you will clear the Lock Out or Lock On.
Step 2 Click the Maintenance > Protection tabs.
Step 3 Under Protection Groups, click the protection group that contains the card you want to clear.
Step 4 Under Selected Group, click the card you want to clear.
Step 5 From Inhibit Switching, click Unlock.
Step 6 Click Yes on the confirmation dialog box.
The Lock On or Lock Out is cleared.
12.9 Network Tests
Use loopbacks and hairpins to test newly-created circuits before adding live traffic or to logically isolate the source of a network failure. All ONS 15327 line (traffic) cards, except Ethernet cards, allow loopbacks and hairpins.
Caution On OC-N cards, the entire card is put into loopback rather than an individual STS. Exercise caution when using loopbacks on an OC-N card carrying live traffic.
12.9.1 Network Test Types
A facility loopback tests the line interface of a card and related cabling. To test, put a facility loopback on a card and use a test set to run traffic over the loopback. A successful facility loopback eliminates the line interface of the card or cabling plant as the cause or potential cause of a network problem. In the ONS 15327 system, the Mechanical Interface (MIC-28-3-A or MIC-28-3-B) card contain ports for DS-1 or DS-3 traffic. Figure 12-10 shows a facility loopback on an XTC-14 or XTC-28-3 card.
Caution Before performing a facility loopback on an OC-N card, make sure there is another SDCC path to the ONS 15327 containing the OC-N card being put in loopback. A second SDCC path is necessary to provide a non-looped path to log into the ONS 15327 containing the OC-N card being put in loopback to enable removal of the facility loopback. This is not necessary if you are directly connected to the ONS 15327 containing the OC-N card being put in facility loopback.
Figure 12-10 The facility loopback process on an XTC card
A hairpin circuit brings traffic in and out on a DS-N port instead of sending the traffic onto the OC-N. A hairpin loops back only the specific STS or VT circuit and does not cause an entire OC-N port to loop back, which would drop all traffic on the OC-N port. The hairpin allows you to test a circuit on nodes running live traffic.
Figure 12-11 The hairpin circuit process on an OC-N card
A terminal loopback tests a circuit path through the XTC card and as it loops back from the line card being tested. Figure 12-12 shows a terminal loopback set on an OC-N card. The test-set traffic comes in on the MIC card DS-N ports and goes through the XTC card to the OC-N card. The terminal loopback on the OC-N card turns the signal around before it reaches the line interface and sends it through the XTC card to the MIC card. This test verifies that the XTC cross-connect circuit paths are valid, but does not test the line interface on the OC-N card. To test the line interface on an OC-N card, connect an optical test set to the OC-N card ports and perform a facility loopback or use a loopback or hairpin on a card that is farther along the circuit path.
Figure 12-12 The terminal loopback process on an OC-N card
12.10 Network Test Procedures
Facility loopbacks, hairpin circuits and terminal loopbacks are often used together to test the circuit path through the network or to logically isolate a fault. Performing a network test at each point along the circuit path systematically eliminates possible points of failure. This example tests an XTC circuit on a two-node bidirectional line switched ring (BLSR). Using a series of facility loopbacks, hairpin circuits, and terminal loopbacks, the path of the circuit is traced and the possible points of failure eliminated.
A logical progression of five network test procedures apply to this scenario:
1. A facility loopback on the source-node XTC card,
2. A hairpin on the source-node XTC card,
3. A hairpin on the destination-node OC-N card,
4. A terminal loopback to the destination-node XTC card, and
5. A facility loopback to the destination XTC card.
Note These procedures are performed when power connections to the node(s) or site(s) are assumed to be within necessary specifications. If the network tests do not isolate the problems, troubleshoot outward for power failure.
12.10.1 Perform a Facility Loopback on a Source XTC Card
The first test is a facility loopback test performed on the first active card in the network circuit; in this example, the test is routed through the MIC card and performed on the XTC card in the source node. Completing a successful facility loopback on this card eliminates the cabling, MIC card, and XTC card as possible failure points.
Figure 12-13 Facility loopback on a source XTC card
Caution Performing a loopback on an in-service circuit is service-affecting.
Note Loopbacks operate only on in-service ports.
Procedure: Create the Facility Loopback on the Source XTC Card
Step 1 Connect an electrical test set to the port you are testing. Use appropriate cabling to attach the transmit (Tx) and receive (Rx) terminals of the electrical test set to the MIC card, which will interface with the XTC card. Both transmit (Tx) and receive (Rx) connect to the same port. Adjust the test set accordingly.
Step 2 Set the port into facility loopback mode.
Note It is normal for an alarm to appear during loopback setup. The alarm clears when you remove the loopback.
Step 3 Proceed to the "Test the Facility Loopback" procedure.
Procedure: Test the Facility Loopback
Step 1 If the test set is not already sending traffic, send test-set traffic on the loopback.
Step 2 Examine the traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
Step 3 If the test set indicates a good loop, no further testing is necessary with the facility loopback. Clear the loopback circuit before testing the next segment of the network circuit path. Proceed to the "Perform a Hairpin Circuit on a Source Node XTC Card" procedure.
Step 4 If the test set indicates a faulty circuit, the problem may be a faulty MIC card, faulty XTC card, or faulty cabling from the DS-N port. Proceed to the "Test the DS-N Cabling" procedure.
Procedure: Test the DS-N Cabling
Step 1 Replace the suspect cabling (the cables from the test set to the MIC ports) with a known-good cable.
Step 2 If a known-good cable is not available, test the suspect cable with a test set. Remove the suspect cable from the MIC and connect the cable to the transmit (Tx) and receive (Rx) terminals of the test set. Run traffic to determine whether the cable is good or suspect.
Step 3 Resend test-set traffic on the loopback circuit with a known-good cable installed.
Step 4 If the test set indicates a good circuit, the problem was probably the defective cable.
a. Make sure the faulty cable is replaced with known-good cable (such as the cable used for testing or another cable that has been tested before installation).
b. Clear the loopback circuit before testing the next segment of the network circuit path.
c. Proceed to the "Perform a Hairpin Circuit on a Source Node XTC Card" procedure.
Step 5 If the test set indicates a faulty circuit, the problem may be a faulty card. Proceed to the "Test the XTC Card" procedure.
Procedure: Test the XTC Card
Step 1 Replace the suspect card with a known-good card.
Step 2 Resend test-set traffic on the loopback circuit with a known-good card installed.
Step 3 If the test set indicates a good circuit, the problem was probably a defective card. Return the defective card to Cisco through the returned materials authorization (RMA) process. Call the Cisco Technical Assistance Center (TAC) at 1-877-323-7368 to open an RMA case.
a. Make sure the faulty card is replaced with known-good card (such as the card used for testing or another card which has been tested before installation).
b. Clear the loopback circuit before testing the next segment of the network circuit path.
Step 4 If the MIC card was at fault and has been replaced successfully, proceed to the "Perform a Hairpin Circuit on a Source Node XTC Card" procedure.
Step 5 If the MIC card was not shown to be at fault but the loopback test was unsuccessful, proceed to the "Test the MIC Card" procedure.
Procedure: Test the MIC Card
Step 1 Replace the suspect card with a known-good card.
Step 2 Resend test-set traffic on the loopback circuit with a known-good card installed.
Step 3 If the test set indicates a good circuit, the problem was probably a defective card. Return the defective card to Cisco through the returned materials authorization (RMA) process. Call the Cisco Technical Assistance Center (TAC) at 1-877-323-7368 to open an RMA case.
a. Make sure the faulty card is replaced with known-good card (such as the card used for testing or another card which has been tested before installation).
b. Clear the loopback circuit before testing the next segment of the network circuit path.
Step 4 If the MIC card was at fault and has been replaced successfully, proceed to the "Perform a Hairpin Circuit on a Source Node XTC Card" procedure.
12.10.2 Perform a Hairpin Circuit on a Source Node XTC Card
The second loopback test is a hairpin circuit performed on the first XTC card in the network circuit. A hairpin circuit uses the same port for both source and destination. Completing a successful hairpin through this card eliminates the possibility that the source XTC card is the cause of the faulty circuit.
Figure 12-14 Hairpin circuit on a source node XTC card
Note An XTC card is required to operate the ONS 15327 and can be used in a redundant or non-redundant configuration.
Procedure: Create the Hairpin Loopback Circuit on the Source Node
Step 1 Connect an electrical test set to the port you are testing.
•If you just completed the "Test the Facility Loopback" procedure, leave the electrical test set hooked up to the MIC card.
•If you are starting the current procedure without the electrical test set hooked up to the MIC card, use appropriate cabling to attach the transmit (Tx) and receive (Rx) terminals of the electrical test set to the MIC connectors for the port you are testing. Both transmit (Tx) and receive (Rx) connect to the same port.
•Adjust the test set accordingly.
Step 2 Use CTC to set up the hairpin loopback on the port being tested.
Step 3 Confirm that the newly-created circuit appears with a direction column noting that this circuit is 1-way.
Step 4 Proceed to the "Test the Hairpin Loopback Circuit" procedure.
Procedure: Test the Hairpin Loopback Circuit
Step 1 If the test set is not already sending traffic, send test-set traffic on the loopback circuit.
Step 2 Examine the test traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
Step 3 If the test set indicates a good circuit, no further testing is necessary with the hairpin loopback circuit.
a. Clear the hairpin loopback circuit before testing the next segment of the network circuit path.
b. Proceed to the "Perform a Hairpin on a Destination Node XTC Card" procedure.
Step 4 If the test set indicates a faulty circuit, there may be a problem with the XTC card. Proceed to the "Test the Alternate Source XTC Card" procedure.
Procedure: Test the Alternate Source XTC Card
Step 1 Perform a software reset on the active XTC card.
Caution XTC side switches are service-affecting. Any live traffic on any card in the node will endure a hit of up to 50 ms.
Note After the active XTC goes into standby, the original standby slot becomes active. This causes the ACT/STBY LED to become green on the former standby card.
Step 2 Resend test-set traffic on the loopback circuit. The test-set traffic now travels through the alternate XTC card.
Step 3 If the test set indicates a faulty circuit, assume the XTC card is not causing the problem.
a. Clear the loopback circuit before testing the next segment of the network circuit path.
b. Proceed to the "Perform a Hairpin on a Destination Node XTC Card" procedure.
Step 4 If the test set indicates a good circuit, the problem may be a defective card. To confirm a defective original XTC card, proceed to the "Retest the Original Source XTC Card" procedure.
Procedure: Retest the Original Source XTC Card
Step 1 Perform a side switch of the XTC cards to make the original card the active card.
Step 2 Resend test-set traffic on the loopback circuit.
Step 3 If the test set indicates a faulty circuit on the original card, the problem is probably the defective card.
a. Return the defective card to Cisco through the returned materials authorization (RMA) process. Call the Cisco Technical Assistance Center (TAC) at 1-877-323-7368 to open an RMA case.
b. Make sure the defective cross-connect card is replaced (such as with the former standby card, or with another known-good card).
c. Clear the loopback circuit before testing the next segment of the network circuit path.
d. Proceed to the "Perform a Hairpin on a Destination Node XTC Card" procedure.
Step 4 If the test set indicates a good circuit, the original XTC card may have had a temporary problem that was cleared by the side switch.
a. Clear the loopback circuit before testing the next segment of the network circuit path.
b. Proceed to the "Perform a Hairpin on a Destination Node XTC Card" procedure.
12.10.3 Perform a Hairpin on a Destination Node XTC Card
The third test is a hairpin circuit on the XTC card in the destination node. To perform this test, you must also create a bidirectional circuit from the source MIC card to the source OC-N node in the transmit direction. Creating the bidirectional circuit and completing a successful hairpin eliminates the possibility that the source and destination OC-N cards, the source and destination XTC cards, or the fiber span is responsible for the faulty circuit.
Figure 12-15 Hairpin on a destination node XTC card
Procedure: Create the Hairpin Loopback Circuit on the Destination Node XTC Card
Step 1 Connect an electrical test set to the port you are testing.
Step 2 Use CTC to set up the source loopback circuit on the port being tested.
Step 3 Use CTC to set up the destination loopback circuit on the port being tested.
Note The destination loopback circuit on a port is a one-way test.
For example in a typical east-to-west slot configuration, a slot 1 (east) OC-N card on the source node is one end of the fiber span, and the slot 2 (west) OC-N card on the destination node is the other end.
Step 4 Verify that the circuits connect to the correct slots. For example, source node/Slot 1 OC-N card (east slot) to destination node/Slot 2(west slot). If two east slots or two west slots are connected, the circuit will not work. Except for the distinct slots, all other circuit information, such as ports, should be identical.
Step 5 Proceed to the "Test the Hairpin Loopback Circuit on the Destination Node XTC Card" procedure.
Procedure: Test the Hairpin Loopback Circuit on the Destination Node XTC Card
Step 1 If the test set is not already sending traffic, send test-set traffic on the loopback circuit.
Step 2 Examine the test traffic received by the test set. Look for errors or any other signal information indicated by the test set.
Step 3 If the test set indicates a good circuit, no further testing is necessary with the loopback circuit.
a. Clear the loopback circuit before testing the next segment of the circuit path.
b. Proceed to the "Perform a Terminal Loopback on a Destination XTC Card" procedure.
Step 4 If the test set indicates a faulty circuit, the problem may exist with the destination XTC card. Proceed to the "Test the Alternate Destination XTC Card" procedure.
Procedure: Test the Alternate Destination XTC Card
Step 1 Perform a software reset on the active XTC card.
Caution XTC side switches are service-affecting. Any live traffic on any card in the node will endure a hit of up to 50 ms.
Note After the active XTC goes into standby, the original standby slot becomes active. This causes the ACT/STBY LED to become green on the former standby card.
Step 2 Resend test-set traffic on the loopback circuit. The test-set traffic routes through the alternate XTC card.
Step 3 If the test set indicates a faulty circuit, assume the cross-connect card is not causing the problem.
a. Clear the loopback circuit before testing the next segment of the network circuit path.
b. Proceed to the "Perform a Terminal Loopback on a Destination XTC Card" procedure.
Step 4 If the test set indicates a good circuit, the problem could be a defective card. To confirm a defective original XTC card, proceed to the "Retest the Original Destination XTC Card" procedure.
Procedure: Retest the Original Destination XTC Card
Step 1 Perform a side switch of the XTC cards to make the original card the active card.
Note After the active XTC goes into standby, the original standby slot becomes active. This causes the ACT/STBY LED to become green on the former standby card.
Step 2 Resend test-set traffic on the loopback circuit. The test-set traffic routes through the original XTC card.
Step 3 If the test set indicates a faulty circuit, the problem is probably the defective card.
a. Return the defective card to Cisco through the returned materials authorization (RMA) process. Call the Cisco Technical Assistance Center (TAC) at 1-877-323-7368 to open an RMA case.
b. Make sure the defective XTC card is replaced.
c. Clear the loopback circuit before testing the next segment of the network circuit path.
d. Proceed to the "Perform a Terminal Loopback on a Destination XTC Card" procedure.
Step 4 If the test set indicates a good circuit, the XTC card may have had a temporary problem that was cleared by the side switch.
a. Clear the loopback circuit before testing the next segment of the network circuit path.
b. Proceed to the "Perform a Terminal Loopback on a Destination XTC Card" procedure.
12.10.4 Perform a Terminal Loopback on a Destination XTC Card
This test is a terminal loopback performed on the fourth line card in the circuit. In the following example, the XTC card in the destination node is tested. First, create a bidirectional circuit that starts on the source node DS-N port and terminates on the destination node DS-N port, then proceed with the terminal loopback test. Completing a successful terminal loopback to a destination node XTC card port verifies that the circuit is good up to the destination XTC.
Figure 12-16 Terminal loopback on a destination XTC card
Caution Performing a loopback on an in-service circuit is service-affecting.
Procedure: Create the Terminal Loopback on a Destination XTC Card
Step 1 Connect an electrical test set to the port you are testing:
•If you are starting the current procedure with the electrical test set hooked up to the MIC card in the source node, leave the test set hooked up.
•If you are starting the current procedure without the electrical test set hooked up to the MIC card, use appropriate cabling to attach the transmit (Tx) and receive (Rx) terminals of the electrical test set to the MIC connectors for the port you are testing. Both transmit (Tx) and receive (Rx) connect to the same port.
Step 2 Use CTC to set up the source loopback circuit on the port being tested.
Step 3 Use CTC to set up the terminal loopback circuit on the port being tested.
Step 4 Confirm that the newly created circuit appears on a Circuits screen row with a direction column that shows a 2-way circuit.
Note Loopbacks operate only on in-service ports.
Note It is normal for an alarm to appear during a loopback setup. The alarm clears when you remove the loopback.
Step 5 Proceed to the "Test the Terminal Loopback Circuit on the Destination XTC Card" procedure.
Procedure: Test the Terminal Loopback Circuit on the Destination XTC Card
Step 1 If the test set is not already sending traffic, send test-set traffic on the loopback circuit.
Step 2 Examine the test traffic being received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
Step 3 If the test set indicates a good circuit, no further testing is necessary on the loopback circuit. Proceed to the "Perform a Facility Loopback on a Destination XTC Card" procedure.
Step 4 If the test set indicates a faulty circuit, the problem may be a faulty card. Proceed to the "Test the Destination XTC Card" procedure.
Procedure: Test the Destination XTC Card
Step 1 Replace the suspect card with a known-good card.
Step 2 Resend test-set traffic on the loopback circuit with a known-good card.
Step 3 If the test set indicates a good circuit, the problem was probably the defective card.
a. Return the defective card to Cisco through the returned materials authorization (RMA) process. Call the Cisco Technical Assistance Center (TAC) at 1-877-323-7368 to open an RMA case.
b. Replace the defective XTC card.
c. Proceed to the "Perform a Facility Loopback on a Destination XTC Card" procedure.
12.10.5 Perform a Facility Loopback on a Destination XTC Card
The final test is a facility loopback performed on the last port in the circuit, in this case the XTC card in the destination node. Completing a successful facility loopback on this card eliminates the possibility that the destination node cabling, MIC card, or line interface is responsible for a faulty circuit.
Figure 12-17 Facility loopback on a destination XTC card
Caution Performing a loopback on an in-service circuit is allowed but is service-affecting.
Note Loopbacks operate only on in-service ports.
Procedure: Create the Facility Loopback on a Destination XTC Card
Step 1 Connect an electrical test set to the port you are testing. Use appropriate cabling to attach the electrical test set transmit (Tx) and receive (Rx) terminals to the MIC connectors for the port you are testing. Both transmit (Tx) and receive (Rx) connect to the same port. Adjust the test set accordingly.
Step 2 Set the port into facility loopback mode.
Note It is normal for an alarm to appear during loopback setup. The alarm clears when you remove the loopback.
Step 3 Proceed to the "Test the Destination Facility Loopback" procedure.
Procedure: Test the Destination Facility Loopback
Step 1 If the test set is not already sending traffic, send test-set traffic on the loopback circuit.
Step 2 Examine the test traffic received by the test set. Look for errors or any other signal information that the test set is capable of indicating.
Step 3 If the test set indicates a good circuit, no further testing is necessary with the loopback circuit. Clear the facility loopback. The entire DS-N circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.
Step 4 If the test set indicates a faulty circuit, the problem may be a faulty MIC card, faulty cabling from the MIC card. Proceed to the "Test the DS-N Cabling" procedure.
Procedure: Test the DS-N Cabling
Step 1 Replace the suspect cabling (the cables from the test set to the MIC ports) with a known-good cable.
Step 2 If a known-good cable is not available, test the suspect cable with a test set. Remove the suspect cable from the MIC and connect the cable to the transmit (Tx) and receive (Rx) terminals of the test set. Run traffic to determine whether the cable is good or suspect.
Step 3 Resend test-set traffic on the loopback circuit with a known-good cable installed.
Step 4 If the test set indicates a good circuit, the problem was probably the defective cable. The entire DS-N circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.
a. Make sure the faulty cable is replaced with known-good cable (such as the cable used for testing or another cable which has been tested before installation).
b. Clear the loopback circuit before testing the next segment of the network circuit path.
Step 5 If the test set indicates a faulty circuit, the problem may be a faulty card. Proceed to the "Test the XTC Card" procedure.
Procedure: Test the XTC Card
Step 1 Replace the suspect card with a known-good card.
Step 2 Resend test-set traffic on the loopback circuit with a known-good card installed.
Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the returned materials authorization (RMA) process. Call the Cisco Technical Assistance Center (TAC) at 1-877-323-7368 to open an RMA case.
a. Make sure the faulty card is replaced with a known-good card (such as the card used for testing or another card that has been tested before installation).
b. Clear the loopback circuit. The entire DS-N circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.
Step 4 If the test set indicates a faulty circuit, proceed to the "Test the MIC Card" procedure.
Procedure: Test the MIC Card
Step 1 Replace the suspect card with a known-good card.
Step 2 Resend test-set traffic on the loopback circuit with a known-good card installed.
Step 3 If the test set indicates a good circuit, the problem was probably the defective card. Return the defective card to Cisco through the returned materials authorization (RMA) process. Call the Cisco Technical Assistance Center (TAC) at 1-877-323-7368 to open an RMA case.
a. Make sure the faulty card is replaced with a known-good card (such as the card used for testing or another card that has been tested before installation).
b. Clear the loopback circuit. The entire DS-N circuit path has now passed its comprehensive series of loopback tests. This circuit qualifies to carry live traffic.
Step 4 If the test set indicates a faulty circuit, contact the Cisco Technical Assistance Center.
12.11 Creating Diagnostic Files
When working with ONS 15327 customer support, you may need to record system information to a file and send it to technical personnel for diagnosis.
Procedure: Create a Diagnostic File
Step 1 Log into the node where you will retrieve the diagnostic files.
Step 2 In node view, click the Maintenance > Diagnostic tabs.
Step 3 Click Retrieve Diagnostics File.
Step 4 In the Save dialog box, type a file name. Do not add an extension to the file name; the CTC extension is added automatically.
Step 5 Choose a directory where you want to save the file.
Step 6 Click Save. A dialog box confirms a successful file transfer. (The dialog box may take 20-30 seconds to display.)
Step 7 E-mail the diagnostic file to the address given to you by customer support.
12.12 Optic Fiber Cleaning
You can clean the optic fiber connected to an ONS 15327 node according to local site practice or by following the procedures below.
Warning Invisible laser radiation may be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam or view directly with optical instruments.
Note Replace all dust caps whenever the equipment will be unused for 30 minutes or more.
Procedure: Clean Fiber Connectors and Adapters with Alcohol and Dry Wipes
Step 1 Using an inspection microscope, inspect each fiber connector for dirt, cracks, or scratches.
Step 2 Replace any damaged fiber connectors.
Step 3 Remove the dust cap from the fiber connector.
Step 4 Wipe the connector tip with the pre-moistened alcohol wipe.
Step 5 Blow dry using filtered air.
Step 6 Use an inspection microscope to inspect each fiber for dirt, cracks, or scratches. If the connector is not clean, repeat Steps 3- 5.
Step 7 Insert the fiber connector into the applicable adapter or attach a dust cap to the fiber connector.
Note If you must replace a dust cap on a connector, first verify that the dust cap is clean. To clean the dust cap, wipe the outside of the cap using a dry, lint-free wipe and the inside of the dust cap using a Cletop stick swab (14100400).
Procedure: Clean Fiber Connectors with Cletop
Step 1 Using an inspection microscope, inspect each fiber connector for dirt, cracks, or scratches.
Step 2 Replace any damaged fiber connectors.
Step 3 Remove the dust cap from the fiber connector.
Step 4 Press the lever down to open the shutter door. Each time you press the lever, you expose a clean wiping surface.
Step 5 Insert the connector into the Cletop cleaning cassette slot, rotate one quarter turn, and gently swipe downwards.
Step 6 Use an inspection microscope to inspect each fiber for dirt, cracks, or scratches. If the connector is not clean, repeat Steps 3- 5.
Step 7 Insert the fiber connector into the applicable adapter or attach a dust cap to the fiber connector.
Note If you must replace a dust cap on a connector, first verify that the dust cap is clean. To clean the dust cap, wipe the outside of the cap using a dry, lint-free wipe and the inside of the dust cap using a Cletop stick swab (14100400).
Procedure: Clean the Fiber Adapters
Step 1 Remove the dust plug from the fiber adapter.
Step 2 Using an inspection microscope, inspect each adapter for dirt, cracks, or scratches.
Step 3 Insert a Cletop stick swab (14100400) into the adapter opening and rotate the swab.
Step 4 Use an inspection microscope to inspect each fiber for dirt, cracks, or scratches. If the connector is not clean, repeat Step 3.
Step 5 Place dust plugs on the fiber adapters when not in use.
12.13 Power Down the ONS 15327
The following procedure describe how to power down a Cisco ONS 15327.
Warning Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard.
Caution The following procedure is designed to minimize traffic outages when powering down nodes, but traffic will be lost if you delete and recreate circuits that passed through a working node.
Note Always use the supplied ESD wristband when working with the Cisco ONS 15327.
Procedure: Power Down the ONS 15327
Step 1 Identify the node that you want to power down. If no cards are installed, go to Step 11. If cards are installed, log into the node.
Step 2 In network view, verify that the node is not connected to a working network:
a. If the node is part of a working network, log out of the node and remove the node from the network and proceed to Step 3.
b. If the node is not connected to a working network and the current configurations are no longer required, proceed to Step 3.
Note Current configurations will be saved if Steps 3- 11 are skipped.
Step 3 In node view, click the Circuits tab and verify that no circuits are displayed. If no circuits are displayed, proceed to Step 4. If circuits are displayed, delete all the circuits that originate or terminate in the node:
a. Click the circuits that need to be deleted and click Delete.
b. Click Yes.
Repeat until no circuits are displayed.
Step 4 In node view, click the Provisioning > Protection tabs and verify that no protection groups are displayed. If no protection groups are displayed, proceed to Step 5. If protection groups are displayed, delete the protection groups:
a. Click the protection group that needs to be deleted and click Delete.
b. Click Yes.
Repeat until no protection groups are displayed.
Step 5 In node view, click the Provisioning > SONET DCC tabs and verify that no SDCC terminations are displayed. If no SDCC terminations are displayed, proceed to Step 6. If SDCC terminations are displayed, delete the SDCC terminations:
a. Click the SDCC Termination that needs to be deleted and click Delete.
b. Click Yes.
Repeat until no SDCC Terminations are displayed.
Step 6 For each installed card, place all ports in Out of Service status:
a. In card view, click the Provisioning > Line tabs.
b. Click under the Status column for each port and choose Out of Service.
Step 7 Remove all fiber connections to the cards.
Step 8 In node view, right-click on an installed card and click Delete.
Step 9 Click Yes.
Step 10 After you have deleted the card, unscrew and open the card ejector and remove it from the node. Repeat Steps 6- 10 for each installed card.
Step 11 Shut off the power from the power supply that feeds the node.
Step 12 Disconnect the node from its external fuse source.
Step 13 Store all cards removed and update inventory records according to local site practice.
