Procedure 12-4: Upgrade OC-12 UPSR to OC-48 UPSR
Overview
Important!
The Alcatel-Lucent 1665 DMXtend does not support upgrading a UPSR where all nodes are connected to the UPSR using single-rate circuit packs in the Function/Growth slots. At least one node must be connected to the UPSR using the Main slots and this node must be the starting node.
Use this procedure to upgrade an in-service OC-12 UPSR to an OC-48 UPSR.
Important!
The UPSR must be equipped with Alcatel-Lucent 1665 DMXtend and/or Alcatel-Lucent 1665 DMX nodes only. This upgrade procedure does not support upgrading UPSRs equipped with nodes other than Alcatel-Lucent 1665 DMXtend and/or Alcatel-Lucent 1665 DMX.
This procedure assumes that one or more Alcatel-Lucent 1665 DMXtend nodes are interconnected in an OC-12 UPSR using the Main slots or a port pair in the Function/Growth slots with Alcatel-Lucent 1665 DMX. Alcatel-Lucent 1665 DMX nodes may be connected to the UPSR using the Main slots or a port pair in the Function/Growth slots.
At nodes connected to the UPSR using single-rate circuit packs in the Main slots, the OC-12 circuit packs in the Main slots are replaced with OC-48 circuit packs. At nodes connected to the UPSR using single-rate circuit packs in the Function/Growth slots, traffic is bridged/rolled to an OC-48 port pair in a different Function/Growth group.
At nodes connected to the UPSR using multirate OC-3/OC-12/OC-48 OLIU circuit packs in the Main/Function/Growth slots equipped with single-rate pluggable transmission modules, the OC-12 pluggable transmission modules are replaced with OC-48 pluggable transmission modules.
At nodes connected to the UPSR using multirate OC-3/OC-12/OC-48 OLIU circuit packs in the Main/Function/Growth slots equipped with multirate pluggable transmission modules, the port Signal Type parameter of each port in the OC-12 port pair is independently reprovisioned to OC-48.
This procedure assumes that in the UPSR, the circuit pack in Main/Function/Growth slot 1 is always connected to the circuit pack in Main/Function/Growth slot 2 at the adjacent node. (Refer to the UPSR example at the end of the procedure.) If other network connections exist, for example, the circuit pack in Main slot 2 is connected to the circuit pack in Function/Growth slot 2 at the adjacent node, modify this procedure as required.
Ring Upgrade Mode
During the upgrade, the following nodes must be provisioned in the Ring Upgrade Mode.
-
Each node connected to the UPSR using single-rate circuit packs in the Main slots
-
Each node connected to the UPSR using multirate OC-3/OC-12/OC-48 OLIU circuit packs in the Main slots
-
Each node connected to the UPSR using multirate OC-3/OC-12/OC-48 OLIU circuit packs in the Function/Growth slots.
During upgrades with single-rate circuit packs, the Ring Upgrade Mode allows cross-connections and provisioning data to be mapped to the replacement circuit pack.
During upgrades with multirate OC-3/OC-12/OC-48 OLIU circuit packs, the Ring Upgrade Mode allows ports in the protected port pair to be independently reprovisioned and operate at different rates.
The Ring Upgrade Mode prohibits the following operations:
The node remains in the Ring Upgrade Mode until it is manually provisioned back to the Normal mode. While in the Ring Upgrade Mode, the upgrade may be temporarily suspended or backed out. To prevent errors in the upgraded ring, keep all nodes in Ring Upgrade Mode until all nodes have been upgraded.
The Ring Upgrade Mode is an abnormal condition. Therefore, the ABN LED is lighted on the SYSCTL circuit pack faceplate and the WaveStar® CIT Alarm List shows the Ring Upgrade Mode as Not Alarmed.
Reported alarm severity levels
The alarm severity levels are reported using the Alarm List and the SYSCTL circuit pack faceplate LED indicators (CR, MJ, MN, or ABN).
Alarm List
The Alarm List is obtained by clicking the Alarm List button. The Alarm List reports detailed information about the current alarms on the local network element. This includes the assigned ASAP alarm severity levels.
For more information about provisioning and assigning ASAPs, refer to Chapter 6, System configuration procedures.
SYSCTL circuit pack faceplate LEDs
The SYSCTL circuit pack faceplate LEDs report the highest active alarm severity level at the local network element or within the alarm group based on the provisioned value of the Remote NE Status parameter.
|
If the Remote NE Status parameter is... |
Then... |
|---|---|
|
Enabled, |
the SYSCTL circuit pack faceplate LEDs at the local network element display the highest active alarm severity level (if any) within the Alarm Group and the FE LED is lighted. |
|
Disabled, |
the SYSCTL circuit pack faceplate LEDs at the local network element display the highest active alarm severity level (if any) at the local network element only. |
|
Enable Far End, |
the SYSCTL circuit pack faceplate FE LED is lighted to indicate an alarm within the alarm group. However, the SYSCTL circuit pack faceplate LEDs at the local network element display the highest active alarm severity level (if any) at the local network element only. |
For more information about provisioning the Remote NE Status feature, refer to Procedure 7-9: Set NE defaults — alarm gateway, alarm group, remote NE status, FTP/FTTD, security and history log thresholds.
Privilege level
You must log in as a Privileged user to complete this procedure.
Required equipment
The following equipment is required to perform this procedure:
-
As optical spans are upgraded around the UPSR, ensure that technicians are available at each end of an optical span as it is upgraded.
-
At the Alcatel-Lucent 1665 DMXtend starting node, one LNW52 OC-48 circuit pack is temporarily required. The LNW52 OC-48 circuit pack is a special upgrade circuit pack that is intended for use only as the temporary transition circuit pack at the Alcatel-Lucent 1665 DMXtend starting node only.
-
At each Alcatel-Lucent 1665 DMXtend node connected to the UPSR using the Main slots, 2 LNW41 OC-48 OLIU circuit packs and the required pluggable transmission modules.
-
At each Alcatel-Lucent 1665 DMXtend and Alcatel-Lucent 1665 DMX node connected to the UPSR using single-rate circuit packs in the Function/Growth slots, an OC-48 port pair on an LNW31, LNW62, LNW55, LNW402, or LNW421–459 OC-48 OLIU circuit pack pair in a different Function/Growth group.
The LNW421, LNW423, LNW431, LNW433, LNW435, LNW437, LNW443, LNW445, and LNW457 circuit packs are DA'ed and are no longer available.
If required, install the OC-48 OLIU circuit packs in the Function/Growth group and provision the OC-48 port and DCC termination parameters. Refer to Chapter 4, Install and provision circuit packs/OLIUs procedures.
-
At each Alcatel-Lucent 1665 DMXtend and Alcatel-Lucent 1665 DMX node connected to the UPSR using multirate OC-3/OC-12/OC-48 OLIU circuit packs in the Main/Function/Growth slots, 2 replacement OC-48 pluggable transmission modules may be required.
To determine whether the pluggable transmission module to be upgraded supports a single optical rate or multiple optical rates, select View → Equipment and expand the required circuit pack. Click on the original pluggable transmission module and Select to obtain the pluggable transmission module information.
-
Refer to the Alcatel-Lucent 1665 Data Multiplexer (DMX) User Operations Guide, 365-372-301 for the circuit packs required at Alcatel-Lucent 1665 DMX nodes connected to the UPSR.
Important!
The replacement circuit packs/ports/pluggable transmission modules must have compatible optics. For example, do not replace a circuit pack that has long reach optics with a circuit pack that has intermediate reach optics. Refer to Alcatel-Lucent 1665 Data Multiplexer Extend (DMXtend) Applications and Planning Guide, 365-372-324 for the SONET optical specifications.
Important!
All nodes in the existing network must have the same software release before upgrading the network.
|
NOTICE Equipment damage |
Rocking circuit packs back and forth when removing or installing them can damage circuit pack and/or shelf connectors.
Do not rock circuit packs back and forth when removing or installing them. Carefully slide circuit packs into or out of the shelf slot.
 |
NOTICE Service-disruption hazard |
Removing or installing circuit packs during a System Reset can cause system errors.
Do not remove or install a circuit pack during a System Reset. If a System Reset occurs, wait until the System Reset is complete, then remove or install the circuit pack.
| |
NOTICE Service-disruption hazard |
If the OLIU circuit packs being upgraded carry Ethernet traffic, transmission hits (up to 6 seconds) may occur as Ethernet traffic is switched.
The length of the service hits varies based on shelf equipage and TDM/Ethernet service provisioning.
Before you begin
Prior to performing this procedure:
-
Refer to Laser safety and Electrostatic discharge in Chapter 1, Safety.
-
Review the applicable office records for each fiber span in the UPSR and the Alcatel-Lucent 1665 Data Multiplexer Extend (DMXtend) Applications and Planning Guide, 365-372-324 for detailed SONET optical specifications of the OC-48 OLIU circuit packs. Ensure that the OC-48 OLIU circuit packs are compatible with each fiber span in the UPSR. If required, refer to the Alcatel-Lucent 1665 Data Multiplexer (DMX) Applications and Planning Guide, 365-372-300.
-
Review the applicable Alcatel-Lucent 1665 Data Multiplexer Extend (DMXtend) Software Release Description for any detailed procedures or cautions that may apply to this upgrade procedure. If required, refer to the Alcatel-Lucent 1665 Data Multiplexer (DMX) Customer Release Notes.
-
If required, review the Alcatel-Lucent 1665 Data Multiplexer (DMX) User Operations Guide, 365-372-301 for procedures or cautions that may apply to this upgrade procedure.
-
Determine the local operating procedures for removing a circuit pack/pluggable transmission module. Local operating procedures for removing a circuit pack/pluggable transmission module may vary. One method is to disconnect the optical fibers and remove the circuit pack/pluggable transmission module. Another method is to verify the circuit pack/port active/standby status, perform manual switches if the circuit pack/port is active, and then disconnect the optical fibers and remove the circuit pack/pluggable transmission module.
-
At nodes using multirate circuit packs, select View → Equipment to access the required circuit pack and verify that the port and port grouping will support the upgrade to the OC-48 rate. Only the first port in the port grouping supports the OC-48 rate. The remaining ports in the port grouping must be unavailable. When the first port in a port group is provisioned to OC-48, the other ports become unavailable. If the OC-12 port to be upgraded is not the first port in the port grouping or other ports in the port grouping are carrying service, the service must be moved before performing this upgrade procedure. To move service to another port pair refer to Procedure 12-4.1: Upgrade low-speed OC-12 UPSR connections at node with single-rate circuit packs. For more information about port groupings, refer to Procedure 4-16: Install pluggable transmission modules.
Steps
Important!
When optical fibers are disconnected during this procedure, inc. LOS, section DCC channel failed, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.
Complete the following steps to upgrade an in-service OC-12 UPSR to an OC-48 UPSR.
1 |
From office records and work instructions, determine the current network configuration. Note how the nodes are connected in the ring and make a drawing of the ring to reference during this upgrade. | ||||||||||||||
2 |
Log in to a node in the UPSR to be upgraded. Reference: Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar® CIT session | ||||||||||||||
3 |
Click the Alarm List button in the top right corner of the System View to view the NE Alarm List and verify that no alarms are present. Refer to the appropriate trouble-clearing procedures to clear all existing alarms before continuing with this procedure. Reference:
| ||||||||||||||
4 |
To verify that no loopbacks, protection switch lockouts, or protection switches are present, select View → Rolling Events. Under the line reading RTRV-COND-ALL determine if any loopbacks, protection switch lockouts, or protection switches are displayed. Remove all existing loopbacks, protection switch lockouts, or protection switches before continuing with this procedure. Reference:
| ||||||||||||||
5 |
If required, select Fault → Analysis → Test Access to access the Test Access Wizard and verify that no test access sessions exist. If required, select Fault → Analysis → Test Access to access the Test Access Wizard and delete all existing test access sessions. Reference: | ||||||||||||||
6 |
At each of the remaining nodes in the UPSR, log in to the node and repeat Step 3 through Step 5. Then continue with the next step. Reference: Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar® CIT session | ||||||||||||||
7 |
If spanning tree is used for protection on the network being upgraded, this upgrade could cause Ethernet traffic loss when the spanning tree switches to a new topology. Ensure that the spanning tree is configured correctly. Important! Alcatel-Lucent 1665 DMXtend and Alcatel-Lucent 1665 DMX support Ethernet service with spanning tree protection. If Ethernet service is provisioned with spanning tree protection, verify that the existing spanning tree configuration is correct. Reference: Procedure 12-4.4: Verify spanning tree configuration | ||||||||||||||
8 |
Important! The starting node must be connected to the UPSR using the Main slots. This procedure assumes that the starting node is a Alcatel-Lucent 1665 DMXtend. Identify and log in to the Alcatel-Lucent 1665 DMXtend starting node. (Refer to the UPSR example at the end of the procedure.) Reference: Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar® CIT session | ||||||||||||||
9 |
At the WaveStar® CIT System View at the starting node, select Configuration → Ring Upgrade Mode. Result: A dialog box appears asking you to confirm changing the NE Mode to Ring Upgrade Mode. Click Yes. The ABN LED is lighted on the SYSCTL circuit pack faceplate and the WaveStar® CIT Alarm List shows the Ring Upgrade Mode as Not Alarmed. For more information about the Ring Upgrade Mode, refer to Ring Upgrade Mode. | ||||||||||||||
10 |
If required, verify the active/standby status of the OC-12 OLIU circuit pack/port in Main slot M2 and perform manual switches to switch traffic away from an active circuit pack/port. Reference: Procedure 12-4.3: Verify active/standby status of circuit pack/port to be upgraded | ||||||||||||||
11 |
Important! If the starting node is equipped with single-rate circuit packs, the OC-12 OLIU circuit pack in Main slot M2 must be first replaced with the temporary replacement LNW52 OC-48 OLIU circuit pack. The temporary replacement LNW52 OC-48 OLIU circuit pack maintains traffic while slot M1 and the other nodes in the ring are upgraded. As a final step, this temporary replacement LNW52 OC-48 OLIU circuit pack is upgraded. If the circuit pack/port is active for timing and/or transmission, opening the latch or disconnecting fibers causes timing and/or transmission switches. Transmission hits (less than 60 ms) will occur for each separate protection switch. Do not reconnect the optical fibers until instructed to do so. The optical fibers are reconnected after the OC-12 circuit pack/port is upgraded at each end of the optical span. Reference: This completes the first phase of the upgrade at the starting node. The starting node upgrade will be completed after all the other nodes in the ring are upgraded. The following figure shows the state of the starting node and the adjacent optical spans. Important! If the upgraded OC-48 port in Main slot M2 at the starting node is equipped with a multirate pluggable transmission module, inc. LOF alarms are reported.  | ||||||||||||||
12 |
Log in to the adjacent node connected to Main/Function/Growth slot 2. (Refer to the UPSR example at the end of the procedure.) Reference: Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar® CIT session | ||||||||||||||
13 |
Determine how the node is connected to the UPSR and upgrade the UPSR connections.
| ||||||||||||||
14 |
Except for the starting node, have all nodes in the UPSR been upgraded?
| ||||||||||||||
15 |
Log in to the starting node. (Refer to the UPSR example at the end of the procedure.) Reference: Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar® CIT session | ||||||||||||||
16 |
| ||||||||||||||
17 |
If required, verify the active/standby status of the OC-12 port on the multirate circuit pack in Main slot M1 and perform manual switches to switch traffic away from an active circuit pack/port. Reference: Procedure 12-4.3: Verify active/standby status of circuit pack/port to be upgraded | ||||||||||||||
18 |
Select Configuration → Equipment and expand the circuit pack in Main slot M1. Click on the required OC-12 port and Select to obtain the port parameters. Provision the port Signal Type parameter to OC-48 and click Apply. Result:
| ||||||||||||||
19 |
Important! If the port is active for timing and/or transmission, disconnecting the optical fibers causes timing and/or transmission switches. Transmission hits (less than 60 ms) will occur for each separate protection switch. If required, disconnect the optical fibers from the single-rate OC-12 pluggable transmission module in Main slot M1. Then replace the single-rate OC-12 pluggable transmission module in Main slot M1 with the replacement OC-48 pluggable transmission module. Result: The replacement OC-48 pluggable transmission module in Main slot M1 is tested and autoprovisioned. The unexpected or failed Pluggable Transmission Module alarm for Main slot M1 clears, and the system reports an inc. OC48 LOS alarm for Main slot M1. Alarms may also be reported at other nodes in the ring. Reference: Procedure 4-16: Install pluggable transmission modules | ||||||||||||||
20 |
If required at both ends of the optical span to be upgraded, perform the following to connect the replacement OC-48 circuit pack/port in Main slot M1 and the required OC-48 circuit pack/port at the opposite end of the upgraded OC-48 optical span:
Result: The inc. OC48 LOS alarms clear. Transmission is now supported on the upgraded optical span. Reference: Procedure 14-4: Perform connection and verification of optical facility | ||||||||||||||
21 |
Important! Perform this step only if the opposite end of the upgraded optical span is an OC-48 port in a Function/Growth group and the Optical Synchronization Source is to be reprovisioned to the upgrade OC-48 port. If required at the opposite end of the upgraded optical span, select Configuration → Timing/Sync to reprovision the Optical Synchronization Source to the upgrade OC-48 port on the OC-48 OLIU circuit pack in slot 2 of the Function/Growth group. Reference: Procedure 6-5: Network Element synchronization provisioning STOP! To complete the upgrade, proceed to Step 31. | ||||||||||||||
22 |
Important! The UPD/INIT button does not work during this upgrade. At the System View select Configuration → Update System → Upgrade. Select main-2 as the Directed Slot Choice and click OK. Result: A dialog box appears asking you to confirm executing this command. Click Yes. The unexpected circuit pack type condition for Main slot M2 clears, and the system reports an unexpected circuit pack type condition for Main slot M1. | ||||||||||||||
23 |
If required, verify the active/standby status of the OC-12 OLIU circuit pack in Main slot M1 and perform manual switches to switch traffic away from an active circuit pack. Reference: Procedure 12-4.3: Verify active/standby status of circuit pack/port to be upgraded | ||||||||||||||
24 |
Important! If the circuit pack is active for timing and/or transmission, opening the latch causes timing and/or transmission switches. Transmission hits (less than 60 ms) will occur for each separate protection switch. Open the faceplate latch on the OC-12 OLIU circuit pack in Main slot M1. Disconnect the optical fibers from the OC-12 OLIU circuit pack in Main slot M1. Then replace the OC-12 OLIU circuit pack in Main slot M1 with the replacement OC-48 OLIU circuit pack. Result: The unexpected circuit pack type condition for Main slot M1 clears, and the system reports an unexpected CP type alarm for Main slot M1. Reference: Procedure 4-2: Install OLIU circuit packs in Main slots | ||||||||||||||
25 |
If required at both ends of the optical span to be upgraded, perform the following to connect the replacement OC-48 OLIU circuit pack in Main slot M1 and the required OC-48 circuit pack/port at the opposite end of the upgraded OC-48 optical span:
Reference: Procedure 14-4: Perform connection and verification of optical facility | ||||||||||||||
26 |
If the OLIU circuit packs being upgraded carry Ethernet traffic, transmission hits (up to 6 seconds) may occur as Ethernet traffic is switched. The length of the service hits varies based on shelf equipage and TDM/Ethernet service provisioning. Important! The UPD/INIT button does not work during this upgrade. At the System View select Configuration → Update System → Upgrade. Select main-1 (default) as the Directed Slot Choice and click OK. Result: A dialog box appears asking you to confirm executing this command. Click Yes. The replacement OC-48 OLIU circuit pack in Main slot M1 is tested and autoprovisioned. The system performs an automatic path protection switch, and all traffic is now active on Main slot M1. Transmission hits (less than 60 ms) occur as traffic switches from the circuit pack in Main slot M2 to the circuit pack in Main slot M1. The unexpected CP type alarm for Main slot M1 clears, and the system reports an unexpected CP type alarm for Main slot M2. Alarms may also be reported at other nodes in the ring. Transmission is now supported on the upgraded optical span between Main slot M1 and the required OC-48 circuit pack/port at the opposite end of the upgraded OC-48 optical span. | ||||||||||||||
27 |
Important! Perform this step only if the opposite end of the upgraded optical span is an OC-48 port in a Function/Growth group and the Optical Synchronization Source is to be reprovisioned to the upgrade OC-48 port. If required at the opposite end of the upgraded optical span, select Configuration → Timing/Sync to reprovision the Optical Synchronization Source to the upgrade OC-48 port on the OC-48 OLIU circuit pack in slot 2 of the Function/Growth group. Reference: Procedure 6-5: Network Element synchronization provisioning | ||||||||||||||
28 |
Open the faceplate latch on the temporary replacement OC-48 OLIU circuit pack in Main slot M2. Disconnect the optical fibers from the temporary replacement OC-48 OLIU circuit pack in Main slot M2. Then replace the temporary replacement OC-48 OLIU circuit pack in Main slot M2 with the replacement OC-48 OLIU circuit pack. Result: The replacement OC-48 OLIU circuit pack in Main slot M2 is tested and autoprovisioned. The unexpected CP type alarm for Main slot M2 clears, and the system reports an inc. OC48 LOS alarm for Main slot M2. Reference: Procedure 4-2: Install OLIU circuit packs in Main slots | ||||||||||||||
29 |
Measure the optical receive power of the receive fiber using an optical power meter. Select the appropriate LBO to attenuate the receive signal to the middle of the allowable optical receive power range. (Refer to the Alcatel-Lucent 1665 Data Multiplexer Extend (DMXtend) Applications and Planning Guide, 365-372-324 for the SONET optical specifications of the OC-48 OLIU circuit packs.) | ||||||||||||||
30 |
Clean all fiber connectors, and connect the transmit and receive optical fibers to the replacement OC-48 OLIU circuit pack in Main slot M2. Result: The inc. OC48 LOS alarms clear. Transmission is now supported on the upgraded optical span. Reference: Procedure 14-3: Clean optical fibers, dual LC adapters and LC lightguide buildouts (LBOs) | ||||||||||||||
31 |
Important! At nodes connected to the UPSR using single-rate circuit packs in the Main slots and multirate circuit packs in the Main/Function/Growth slots, the system reports the ring upgrade mode standing condition (not alarmed) in the NE Alarm List until the node is manually provisioned back to the Normal mode. At nodes connected to the UPSR using single-rate circuit packs in the Main slots and multirate circuit packs in the Main/Function/Growth slots, click the Alarm List button in the top right corner of the System View to view the NE Alarm List and verify that no alarms or standing conditions are present (except ring upgrade mode and ABN condition). Refer to the appropriate trouble-clearing procedures to clear all existing alarms and standing conditions (except ring upgrade mode and ABN condition) before continuing with this procedure. Reference:
| ||||||||||||||
32 |
At each node connected to the UPSR using single-rate circuit packs in the Function/Growth slots, select Configuration → Update System → Update All. Result: A dialog box appears asking you to confirm executing this command. Click Yes. The inc. OC12 LOS alarms are cleared on the original OC-12 ports. | ||||||||||||||
33 |
At each node connected to the UPSR using single-rate circuit packs in the Function/Growth slots, select Configuration → Cross-Connections and use the Cross-Connection Wizard to delete the remaining add and through cross-connections to the original OC-12 ports. | ||||||||||||||
34 |
Important! The UPSR network must be alarm free with normal transmission before manually provisioning the nodes back to the Normal mode. After a node is manually provisioned back to the Normal mode, the node can not be returned to the pre-upgrade state using the backout procedure. At each node connected to the UPSR using single-rate circuit packs in the Main slots and multirate circuit packs in the Main/Function/Growth slots, select Configuration → Normal Mode. Result: A dialog box appears asking you to confirm changing the NE Mode to Normal mode. Click Yes. The ABN LED is turned off on the SYSCTL circuit pack faceplate and the Ring Upgrade Mode will be removed from the WaveStar® CIT alarm list. | ||||||||||||||
35 |
Important! It is recommended that the network element database be backed up to a remote OS (for example, OMS) after an upgrade. This creates a current backup copy that includes the replacement circuit packs/port pairs. The remote OS could use this backup copy to restore the network element database in the event of a catastrophic failure. Attempts to restore the network element database using a backup copy created prior to the upgrade may result in circuit pack failures. At each node in the UPSR, back up the network element database using the Configuration → Software → Remote Backup command. Reference: End of steps |
UPSR example
Starting Node: Alcatel-Lucent 1665 DMXtend or Alcatel-Lucent 1665 DMX connected to the UPSR using the Main Slots
Starting Circuit Pack: Main-2 at the Starting Node
Direction of Upgrade: Clockwise around UPSR from Main-2 at the Starting Node to Main/Function/Growth slot 1 at the adjacent node
