Commissioning Wizard Before a Nokia MetroHub node is taken into use the first time, certain procedures must be performed to make the node operational. The Commissioning Wizard guides you through the steps of commissioning the node. Commissioning consists of three phases: Installation, Testing and Configuring. Installation In the installation phase the Commissioning Wizard asks the user if the node should be reset. If the node is already commissioned, a message box will ask for confirmation before applying default settings. If the node is new, the default settings are applied without asking for confirmation. After this, the Commissioning Wizard logically installs the units in the node. Testing The testing phase ensures that the hardware is functioning properly. A cross-connection test is run in the Nokia MetroHub node and the transmission units found in the node. Configuration The configuration phase contains activities needed to make the node functional and capable of relaying a payload/other signals. Configuration with the help of the Commissioning Wizard requires either 1. a Node File or 2. an XML file containing a valid site configuration and a cross-connection file exported from the MetroHub Manager. Integration to the network using the Commissioning Wizard cannot be implemented without a valid Node File. If the node file does not exist, you must perform the commissioning procedure manually without the Wizard. If radio hops exist, their functionality is verified. It is possible to fine-tune the direction of the hops (Hops are monitored by the Manager.). When the commissioning procedure is complete, a Commissioning Report is compiled, which comprises node configuration information (node settings, unit settings, cross-connections, etc.) and the results of node testing. This Commissioning Report can be stored as a file on the computer. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. You can connect to a node in two ways. Connecting locally Select the Connection | Connect Locally menu command. A connection to the node is established using a fixed Local Management Port (LMP) address (4080) and default port / speed. You can change the port / speed in the Manager Options dialog box. If several LMPs are chained together, you must use the Connection | Connection Tool menu command to connect to the node. Connecting to a node Select the Connection | Connection Tool menu command to open the Connect to Node dialog box. Enter the necessary settings. See Nokia Connection Tool Help for details. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. Make a connection to the node. (See the Help topic Connecting to a Node.) 2. Select the Maintenance | Restore Backup Settings menu command. 3. Use the Browse button to select which file you want to restore. 4. Select the units which are to be restored. 5. Click the Send button to send the selected units. 6. Click the Close button to close the dialog box. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. You can adjust the Service Interface port and timeout settings of a Hub node. Adjusting port settings 1. Connect to a node or open a node file. 2. Select the Configuration | Service Interface menu command to open the Service Interface dialog box. 3. Select the Port tab. 4. Adjust the settings. Adjusting timeout settings 1. Connect to a node or open a node file. 2. Select the Configuration | Service Interface menu command to open the Service Interface dialog box. 3. Select the Timeout tab. 4. Adjust the settings or Click the Defaults button to set the default values stored in the node. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. You can logically install a unit that is physically present. Installing a unit 1. Insert a new unit (or several new units) into the Hub. 2. Connect to a node or open a node file. 3. Click the right mouse button over the desired unit to access the Equipment window pop-up menu . 4. Select the Install Unit pop-up menu command for all new units. In the connect mode, units must be displayed with diagonal stripes in order to be installed. If a unit is not displayed correctly after it is inserted, select the Refresh command from the Equipment window pop-up menu. The installed unit(s) can now be used. When alarm polling is active, the status of the units is indicated by means of colour coding. You may also insert the new unit(s) when you already have a connection to the node. In that case, to make the new unit(s) appear in the Equipment window, you need to select the Refresh command from the Equipment window pop-up menu, after which you can select the Install Unit pop-up menu command. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. ou can logically uninstall a selected unit. Uninstalling a unit 1. Connect to a node or open a node file. 2. Point to the unit(s) to be uninstalled and click the left mouse button to access the Equipment window pop-up menu . 3. Select the Uninstall Unit pop-up menu command. The unit(s) can no longer be used, and you can physically remove the unit(s). After uninstalling a unit it is recommendable to perform a refresh operation by selecting the Refresh command from the Equipment window pop-up menu. Uninstalling the master card will disrupt management and traffic. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. Replacing a unit with a unit of the same type If a unit is faulty, for example, you can replace it with another unit of the same type by removing the faulty unit from the Hub and then inserting the replacement unit. Make sure all the cards have the same node software. Check the release documentation to verify the compatibility between the hardware and the Manager. 1. Connect to a node or open a node file. 2. Select Configuration | Cross-connections menu command to open the Cross-connections window and click the Export button to export the cross-connections. 3. Remove the faulty unit. 4. Insert a new unit into the Hub. 5. Click the Refresh button to read all data from the node. The new unit should be displayed with diagonal stripes. 6. Select Configuration | Cross-connections menu command to open the Cross-connections window and click the Import button to import the cross-connections from file. 7. Check that the settings in the card and the node are correct (e.g., Sync, EOC, Cross-connections). Uninstalling the master card will disrupt management and traffic. Replacing a unit (FXC or Outdoor) with a unit of a different type 1. Connect to a node or open a node file. 2. Point to the unit to be replaced and click the left mouse button to access the Equipment window pop-up menu . 3. Select the Uninstall Unit pop-up menu command. 4. The unit can no longer be used, and it can be physically removed. 5. Insert a new unit into the Hub. 6. Click the Refresh button to read all data from the node. The new unit should be displayed with diagonal stripes. 7. Click the left mouse button to access the Equipment window pop-up menu. 8. Select the Install Unit pop-up menu command. 9. Check that the settings in the card and the node are correct (e.g., Sync, EOC, Cross-connections). In the connect mode, units must be displayed with diagonal stripes in order to be installed. After inserting the unit, select the Refresh command from the Equipment window pop-up menu. The new unit is now ready for use. When alarm polling is active, the status of the units is indicated by means of colour coding. After replacing a unit you should refresh the Manager by selecting the Refresh command from the Equipment window pop-up menu. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. You can modify the settings of individual FXC/Outdoor units. 1. Connect to a node. See Connecting to a Node. 2. Select an FXC/Outdoor unit. 3. Select the FXC | Settings menu command to adjust the FXC and/or Outdoor unit settings. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. An XML file (or alternatively, a Node File) is required before you can commission a node using the Commissioning Wizard. 1. Plan the site. 2. Open the MetroHub Manager in the file mode. 3. Install the needed units. 4. Create the necessary cross-connections. 5. Select the File | Save As menu command and save the file with a .xml filename extension. Alternatively you can open a node file and save it as an XML file. You can also get the file from Nokia NetActT Planner. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. A Node File (or alternatively, an XML File) is required before you can commission a node using the Commissioning Wizard. 1. Plan the site. 2. Open the MetroHub Manager in the file mode. 3. Install the needed units. 4. Create the necessary cross-connections, EOC and synchronization settings. 5. Select the File | Save As menu command and save the file. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. You can use the Commissioning Wizard to commission a node. Commissioning a node with a node file (.nod) or with a Site Configuration File (.xml) 1. Use a Site Configuration File (SCF) exported from Nokia NetActT Planner, or create a Node File , or use an existing Node File or SCF file. 2. > Choose the Configuration | Commissioning Wizard menu command to start the Commissioning Wizard, which will guide you through the commissioning process. In the process, import the node file (.nod) or the site configuration file (.xml). The node will be reset during the commissioning process. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. Assume the base station is equipped with four TRX cards, an FXC E1/T1 transmission card and an FXC RRI transmission card. The following signals required by the base station are arriving at the base station (at the Abis interface): ú OMUSIG (Operation and Maintenance Signalling) in timeslot 1 at a sampling rate of 16 kHz ú TRXSIG 1 (TRX 1 signalling) in timeslot 2 at a sampling rate of 32 kHz, bits 1 - 4 ú TRXSIG 2 (TRX 2 signalling) in timeslot 2 at a sampling rate of 32 kHz, bits 5 - 8 ú TCH 1 (TRX 1 traffic channels) in two consecutive timeslots ú TCH 2 (TRX 2 traffic channels) in two consecutive timeslots The following example illustrates the use of the Traffic Manager: 1. Open the MetroHub Manager to establish a connection to the base station. ú The UltraSite E1/T1 Manager will automatically start running in the background and is integrated into the MetroHub Manager. ú A Transmission menu will appear in the MetroHub Manager menu bar. 2. Select the Transmission | Traffic Manager menu command to open the Traffic Manager dialog box. ú The Traffic Manager dialog box will show how the base station signals are connected (how they are arriving at the base station). ú If the base station has not been commissioned, the 2M frame in the Traffic Manager dialog box will be empty. Signal type Timeslot Sampling rate Bits OMUSIG 31 16 kHz 1 - 2 TRXSIG 1 30 32 kHz 1 - 4 TRXSIG 2 30 32 kHz 5 - 8 TRXSIG 3 29 32 kHz 1 - 4 TRXSIG 4 29 32 kHz 5 - 8 TCH 1 1 - 2 TCH 2 3 - 4 TCH 3 5 - 6 TCH 4 7 - 6 Set up the signals as follows: 3. For an FXC E1/T1 card, select a port (Port 1 - 4) from the Line Interface box. For an FXC RRI card, select a Flexbus channel (1 - 16 channels in two Flexbuses) from the Line Interface box. For an STM-1 card, select an Optical interface from the 'Interface' box, and a VC-12 channel from the 'Selected VC-12' box. 4. Select signal type OMUSIG (blue). 5. Point to timeslot 1, bits 1 - 2, and click the left mouse button. A pop-up menu will appear. Select the 64 kHz sampling rate. Timeslot 1 will be coloured blue. 6. Select signal type TCHs (yellow). 7. Point to timeslot 4 and click the left mouse button. A pop-up menu will appear. Select TCHs for TRXSIG 1. Timeslots 4 and 5 will be coloured yellow and number 1 will appear in the boxes. 8. Repeat step 6 - 7 for TCH 2, TCH 3 and TCH 4. To delete an allocation, point to the timeslot you wish to delete and click the right mouse button. Select the desired function from the pop-up menu that appears. 9. Select signal type TRXSIG (red). 10. Point to timeslot 2, bits 1 - 2, and click the left mouse button. A pop-up menu will appear. Select TRXSIG 1. Another pop-up menu will appear. Select the 32 kHz sampling rate. Timeslot 1, bits 1 - 2 will be coloured red and the number one will appear in the boxes. 11. Repeat step 9 - 10 for TRXSIG 2, TRXSIG 3 and TRXSIG 4. 12. Select another port from the Line Interface box and repeat steps 4 - 11. 13. Repeat steps 4 - 11 for the last two ports. 14. If signalling takes place through satellite, select the Satellite option button. (The Normal option button is selected as a default.) When all the necessary signals have been labelled, click the BTS icon or OK button. The Traffic Manager will automatically perform the following sequence: ú LIF 1 is taken into use if it is not already in use. ú Cross-connections are created for labelled signals LIF1 -> D-bus. ú A message is sent to the base station telling it where the required signals are located on the base station's internal 2M bus (D-bus). If the procedures are completed successfully, the Traffic Manager dialog box will be closed and you can monitor the establishment of connections to the BSC in the MetroHub Manager dialog box. If an error message is given, check the following: ú Are all the cables connected correctly? ú Were the signals labelled correctly? (The signals must be labelled in the Traffic Manager matrix exactly as they are arriving to the base station.) Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. se the Traffic Manager to change BTS capacity. See Using the Traffic Manager or the Traffic Manager dialog box topic. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. You can use D-Bus allocation to optimise the number of cross-connections and thereby speed up connection times. 1. Select the Configuration | D-Bus Allocation menu command to open the D-Bus Allocation dialog box. 2. Select an interface (D11 - 13) from the Interface box. Abis signals can be marked only into the D11 interface and EDAPs can be marked into all interfaces. If an Abis signal is marked into the D12 - D13 interface a warning is displayed. Other marking limitations are same as in the Traffic Manager. 3. Select signal type OMUSIG (blue). 4. Click a timeslot. A pop-up menu will appear. Select a sampling rate. The timeslot will be coloured blue. 5. Select signal type TCHs (yellow). 6. Click a timeslot. A pop-up menu will appear. Select TCHs for TRXSIG. The timeslots will be coloured yellow and the selected TRX number will appear in the boxes. To delete an allocation, point to the timeslot you wish to delete and click the right mouse button. Select the desired function from the pop-up menu that appears. 1. Select signal type TRXSIG (red). 2. Point to a timeslot and click the left mouse button. A pop-up menu will appear. Select TRXSIG. Another pop-up menu will appear. Select a sampling rate. The timeslot will be coloured red and the selected TRX number will appear in the boxes. When all the necessary signals have been labelled, click the OK button. The modified D-Bus allocation is sent to the node master/BTS. The dialog box does not create any cross-connections - it only manages D-Bus allocation information. Cross-connections have to be created in the cross-connection windows when this tool is used to configure the BTS. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. You can download software to a Hub node and activate the new software. Downloading and activating software 1. Connect to a node. 2. Select an FXC/Outdoor unit from the Equipment window. 3. Select the FXC | Software | Download menu command. 4. Select a file to be downloaded. (You must wait while the file is downloaded. Depending on the communication speed used, downloading takes 5 minutes or more.) 5. Select the FXC | Software | Activate menu command to activate the new software. Outdoor Unit software is downloaded through the related FXC RRI unit. See the Transmission Unit Help for details. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved. You can use the Cross-connection Wizard to add cross-connections to a Hub node. 1. Connect to a node or open a node file. (One or more FXC units must be installed.) 2. Select the Configuration | Cross-connections menu command to open the Cross-connections window . 3. Select the inactive bank. 4. Click the Add Cross-connections button to open the Add Cross-connection Wizard - TX1/RX1 dialog box. 5. Select the desired interface by clicking the interface symbol. 6. Fill in the information for the first termination point. Click the Next button. The Add Cross-connection Wizard - TX2/RX2 dialog box will open. 7. Fill in the information for the second termination point. Click the Next button. If the cross-connection type is Protected Bi-Directional, the Add Cross-connection Wizard - Protecting TX/RX dialog box will open where you can fill in the information for the protecting interface. The Overview dialog box will open. Depending on the cross-connection type, the fields in this dialog box will be enabled as follows: 8a. If the cross-connection type is Bi-Directional Masked, the Mask Properties controls are enabled. Fill in the mask information. 8b. If the cross-connection type is Protected Bi-Directional, the Protection Information controls are enabled. Click the Condition button to open the Condition dialog box, where you can specify the condition information. If the Condition type is Equal, the dialog box contains two tabbed Condition pages. If the type is Priority, it contains only one tabbed Condition page. Fill in the condition information. Click the OK button. 8c. If the cross-connection type is Uni-Directional Fixed Data, the Fixed Data control is enabled. Fill in the fixed data. 9. Click the Finish button. The Add Cross-connection Wizard dialog box will close and you will return to the Cross-connections window, where the new cross-connection appears in the list in the upper part of the window. Only in the connect mode , from ITN C3.0 onwards, if a pilot bit in cross-connection 1 has a different unit/interface/time-slot/bit location than another pilot bit in cross-connection 2, then the condition is illegal. Modification of data is possible only with Full Control. See Access Control help for more information. Copyright 2001. Nokia Networks Oy All rights reserved.