s

HLRi 1.1 Installation procedure

Update Ulticom SS7 Board Extension

Customer Project System Type Location Country

XXX HLRi 1.1

Document State Final 1.1 Date of Release 10.05.2004 Date of Adaption 27.05.2004

Update physical SS7 Board Configuration

New SS7 boards can be added to a TSP cluster without service interruption. One CE after the other has to be stopped, the new boards configured and the new boards plugged. Signalware offers a menu driven shell script utility reconfigureBoards to update the physical SS7 board configuration. This utility allows the user to dynamically add new SS7 boards. Note: The removal of SS7 boards is not supported!

1.1

ReconfigureBoards
/export/home/omni/conf/reconfigureBoards will configure an additional physical SS7 board to the system by asking the user questions about the new board. reconfigureBoards will assign the next consecutive board number to the new board. Similarly, the next consecutive port number will be assigned to the each new port that is being added by the user. The questions are similar to the ones asked by configurePlatform script. The reconfigureBoards script has two modes of operation: the super-user and the regular user mode (rtp99). In super-user mode the GENERIC configuration files get updated and as user rtp99 the user specific files get updated. reconfigureBoards has to be called in both modes with exactly the same answers! Example of reconfigureBoards adding one SS7 card PC0200 using ITU-T protocol (C7):
# /export/home/omni/conf/reconfigureBoards [-generic] *************************************************************** *** *** *** Dynamic Board Reconfiguration Tool *** *** *** *************************************************************** +------+ | INFO | OMNI_HOME = /export/home/omni +------+ 1. 2. 3. 4. DISPLAY ADD ADD DELETE Current Board M2PA Logical SS7 Physical M2PA Logical Configuration Board Board Board

Issued by ICM N PG SI TS A7, Information and Communication Mobile - Networks Siemensdamm 62, D-13627 Berlin, Germany

Copyright Siemens AG 2011

All Rights Reserved.

SIEMENS AKTIENGESELLSCHAFT
Author: Adapted: Petra Froelich Axel Dellin ICM N PG NM PF A 2 ICM N PG SI HI 1 +49 30 386 42372

5. MODIFY 6. EXIT

M2PA Logical Board Save/Discard Changes

Enter your choice>1 Following boards are currently found on the system: 0) SS7 1. 2. 3. 4. 5. 6. DISPLAY ADD ADD DELETE MODIFY EXIT Physical Board 0 contains 16 port(s) Current Board Configuration M2PA Logical Board SS7 Physical Board M2PA Logical Board M2PA Logical Board Save/Discard Changes

Enter your choice>3 Choose SS7 protocol for board 1 on bari2 1) A7 2) C7 3) CH7 4) J7 Select protocol: 2 Choose board type for board 1 on bari2 1) CC0200 2) PC0200 3) CC0202 4) CC0203 5) PS0204 6) CC0205 7) MC0207 Select board type: 2 Port Type for bari2, board 1, port 0 1) E1 2) T1 Enter choice [E1]: 1 Choose from the following items: 1) double-frame 2) multi-frame Enter choice [multi-frame]: 2 Impedance for bari2, board 1 1) Balanced 2) Unbalanced Enter choice: 1 T1E1_1 Clock Source Mode for bari2, board 1 1) Master 2) Slave 3) Reference 4) None Enter choice [Slave]: 2 1. 2. 3. 4. 5. 6. DISPLAY ADD ADD DELETE MODIFY EXIT Current Board Configuration M2PA Logical Board SS7 Physical Board M2PA Logical Board M2PA Logical Board Save/Discard Changes

Enter your choice>1 Following boards are currently found on the system:

0) SS7 1) SS7 1. 2. 3. 4. 5. 6. DISPLAY ADD ADD DELETE MODIFY EXIT

Physical Board 0 contains 16 port(s) Physical Board 1 contains 16 port(s) Current Board Configuration M2PA Logical Board SS7 Physical Board M2PA Logical Board M2PA Logical Board Save/Discard Changes

Enter your choice>6 Save changes & Exit [yes/no] [yes] : yes Saving changes ... Copy configurePlatform.Conf configuration file to all of the CEs [yes/no] [yes] : yes Copying configurePlatform.Conf to node1:/export/home/omni/conf/configurePlatform.Conf Done. Copying configurePlatform.Conf to node2:/export/home/omni/conf/configurePlatform.Conf Done. Good bye.

Hint: The following message can be ignored:

port_daemon is not running on CE <uname> No reconfiguration will be done on CE <uname> Good bye.

1.2

Configuration Sequence
On one CE after other the follow this sequence to add boards: 1. 2. 3. 4. 5. 6. 7. 8. 9. Stop TSP on one CE Login as user root and create file /reconfigure. Set variable OMNI_HOME=/export/home/omni Run /export/home/omni/conf/reconfigureBoards generic Login as user rtp99 and run /export/home/omni/conf/reconfigureBoards without any option and give exactly the same answers as above. Power off the machine. Plug the boards. Reboot the machine (e.g. 'boot -r' from OBP). Start TSP.

After the upgrade of both CEs 10. login as user root to the CE which was updated first. Due to copying the configuration files to the other CE, Signalware thinks that the user rtp99 specific configuration is out-of-date. As a workaround update the timestamp of the user rtp99 configuration: touch /export/home/omni/conf/*99*

1.3

Link and Port Configuration

For a SS7 link configuration the port number is important. With a first installation and configuration of Signalware and SS7 cards in a machine the board and port numbers are consecutively. On each SS7 board 16 physical ports exist. The numbering of these ports follows simple pattern: the first board on the first CE hosts the ports 0-15. The second board on the first CE hosts the port 16-31, etc. When all boards of the first CE are enumerated, the numbering continues with the first board of the second CE and so on. The order of CEs is determined by the CEs hostnames, in alphabetical order. This sequence can be achieved with a complete new configuration of Signalware calling configurePlatform and configureNodes. This can not be done online. But the advantage would be an easy assignment of ports to the the location of the boards. An already existing SS7 configuration must be changed concerning the new numbering of all ports. Adding additional boards with the script reconfigureBoards changes this order. The next consecutive port numbers will be assigned. This has to be considered finding a board and configuring new links.

1.4

Important Hints
Due to the impact this procedure can have on a running operation the following hints must necessarily be considered: Perform the procedure only during 'low traffic hours'. Keep in mind that answering the question Save changes & Exit [yes/no] [yes] with yes will lead into an update of the port configuration even if no new boards have been configured (e.g. you just selected the option 1 DISPLAY Current Board Configuration). This can cause a malfunction of the port daemon ! After the procedure has successfully been performed it must be taken into account that the new port configuration does not correspond to a port configuration of an initial installation. Example: you have two nodes with two boards on each node then normally you have port 0 to 31 on the first node and port 32 to 63 on the second node. After board extension (e.g. one board on each node) you will have additionally port 64 to 79 on the first node and port 80 to 95 on the second node. In contrast to this after initial installation you would have port 0 to 47 on the first node and port 48 to 95 on the second node. This means that in case you have to perform configurePlatform or an initial installation the former SS7 link configuration will not fit to the new port configuration. If you use an 'install server' then the added boards should be included in the configuration (e.g. by editing the file 'aiParameter.sh' and performing prepTspInstall).