Technical NoteMIGRATING VSG HUB SITE TO RC Cambridge Broadband Networks Limited CBNL_120 Issue A02 1 INTRODUCTION For larger Hub Sites, using a VectaStar Radio Controller (RC) offers significant advantages in terms of number of remote terminals and Data Aggregation performance when compared to using separate Zero Footprint Sectors (ZFS). Therefore, it is common to start building a network using ZFS and at some stage combine one or more ZF Sectors into a Hub site managed by a Radio Controller. All aspects of the commissioning and management of the RC based Hub site are documented in the main CBNL VectaStar manuals. This Technical Note aims to provide customers with a guide on the process for migrating one or more existing ZFS Sectors into a hub site managed by either a Radio Controller or a redundant Radio Controller pair. 2 PREREQUISITES Before starting the migration ensure you have access to: • The correct software release for the RC and ODU e.g. 5.1.0-23 or later. For a particular <VERSION>, the filenames of the required packages are: vectastar-rc-<VERSION>-Intel.tar.gz tar file for the RC site vectastar-<VERSION>-cpe.zip for the ZFS and CPE upgrade tool These are included in the released SW packages • Access to the ZFS and the RC from a VNMS or EMS • An IP address and other network details for the RC TECHNICAL NOTE MIGRATING VSG HUB SITE TO RC PAGE 2 OF 11 3 MIGRATING FROM ZFS TO RC HUB The migration from a number of ZF Sectors to an RC based Hub site has a number of separate steps. These are: • Installing the RC • Upgrading each ZFS, including RT and AP to an RC compatible release • Changing the mode of each ZFS AP to allow it to be RC controlled • Configuring the RC • Connecting the AP to the RC 3.1 INSTALLING THE RC The steps to install the RC physically are detailed in the RC install guide: D001283_RC_Install_A00.pdf Once the RC is physically installed, you will need to commission it as a sector controller. This is detailed in the RC Hub site commissioning guide D001284_A01_RC_Commission.pdf. The steps include: 1. Running settime command 2. Configuring the RC’s IP address and access parameters using configtool 3. Ensuring that the VNMS Server can communicate with the RC via ssh 4. Adding the radio controller to the VNMS vsnet window Once the RC is connected to the network, add it to the VNMS using vsnet in the usual way. You will need to confirm it is correctly configured for VNMS management. There are a number of ways to do this; the simplest way is from the command line by opening a terminal window as the vnms user on the VNMS Server and running the command: vnms_configure_apc.py -t <RC IP> e.g. root@vnms:/home# vnms_configure_apc.py -t 10.10.10.10 Processing APC:10.10.10.10 ( all ) no problems root@vnms:/home# This will report the status of the tests. Any errors will need to be corrected before proceeding. If you are not sure how to correct these errors then contact Support for assistance. TECHNICAL NOTE MIGRATING VSG HUB SITE TO RC PAGE 3 OF 11 3.2 PREPARING TO UPGRADE EACH ZFS 3.2.1 Making a backup of the ZFS configuration If you have not already done so, add each ZFS to a VNMS server in the VNMS vsnet window and ensure that from the VNMS server you can configure the ZFS; there should be a green tick next to the ZFS and the Configure button should be enabled. Record the configuration of each ZFS. To take a backup, you need ssh access from the VNMS server to the operational ZFS. Open a terminal session on the VNMS server. To prepare for the backup, first run the following command which will test and add ssh keys to each ZFS: vnms_configure_apc.py -s ssh -c <ZFS IP> Then make a backup of each ZFS e.g. sudo /etc/cron.daily/00_vnms_grab_apc_backup <ZFS IP> The backup files generated for each ZFS will be stored in the usual directories on the VNMS server which are: /usr/local/vectastar/backup/<ZFS IP> Repeat this process for each ZFS that is going to be combined into an RC based Hub Site. 3.2.2 Prepare the VNMS configuration On the VNMS, install the ppc images file for the RC release in the usual way following the VNMS instructions. Typically for a VNMS Server connected to the internet you will need the following three commands: apt-get update aptitude search ppcimages i vectastar-5.0.35-1-ppcimages - VectaStar PPC ICU installation images i vectastar-5.1.0-17-ppcimages - VectaStar PPC ICU installation images p vectastar-5.1.0-23-ppcimages - VectaStar PPC ICU installation images apt-get install vectastar-5.1.0-23-ppcimages In some circumstances if the package is supplied by e-mail or on CD, you can install it by copying the deb file onto the VNMS Server and installing it manually e.g. dpkg –i vectastar-5.1.0-23-ppcimages.deb TECHNICAL NOTE MIGRATING VSG HUB SITE TO RC PAGE 4 OF 11 3.3 UPGRADING EACH ZFS 3.3.1 ZFS Upgrade process In the VNMS vsnet window, under the Base Stations tab: 1. Select the required ZFS 2. Click Configure 3. In the Users tab select all the CPEs 4. Click Upgrade CPE Once the CPE upgrade window opens: 1. Select the check box to upgrade the AP as well as the CPEs 2. Ensure that you have selected the RC release of software from the pull down menu; this will be numbered 5.1.x or greater 3. Click Upgrade Now This will start the process of upgrading all the CPEs. The upgrade of all the CPEs will occur first and after this upgrade is complete, the upgrade of the ZFS AP will be started. Once the ZFS AP upgrade process has finished, confirm the upgrade was a success by performing the following: 1. Check that the ZFS has become operational, this is shown in the VNMS vsnet window by a green tick, you may need to click Get a couple of times to refresh the display until the green tick is displayed. 2. Check that all the CPEs have registered correctly. This is shown with a green tick next to each CPE under the Users tab in the VNMS vsbs window. You may need to click Get a couple of times to refresh the display until the CPEs register. Repeat all the steps in 3.3.1 for each ZFS that is to be migrated. 3.3.2 Upgrade failures If the upgrade process fails at any point then, depending at which point it fails, you may need to try the following: • If the CPE upgrades fail, restart the upgrade process. • If the ZFS AP upgrade fails it can be upgraded from the VNMS vsnet window. To perform the upgrade, highlight the ZFS and click upgrade. • If the ZFS upgrade fails from the VNMS vsnet window, upgrade the ZFS directly using the vsinstall tool (3.12 or later). TECHNICAL NOTE MIGRATING VSG HUB SITE TO RC PAGE 5 OF 11 3.4 MIGRATING THE ZFS TO GBITAP 3.4.1 Migrating a copper-connected ZFS If the ZFS is currently set to use the copper interface, then connect to the ZFS with a laptop and run vsinstall (version 3.12 or later) Change the AP type to be a GbitAP Change the interface to be Fibre 3.4.2 Migrating fibre-connected ZFS If the ZFS is currently set to fibre then you can change the AP type to GbitAP using configtool. In VNMS vsnet window select the ZFS and click configtool. Enter the vectastar menu and then set type to be VSG-AP. e.g. vs:main> vectastar vs:main:vectastar> type set VSG-AP vs:main:vectastar> up Also, after conversion from a ZFS to an AP, the ODU configuration files retain the previous IP address that was used to communicate with the ZFS. This IP address is not used if the ODU is connected to a correctly configured RC. However should the RC be miss-configured then there is a small chance that the IP address will be visible on the network. To prevent this it is possible to remove this configured IP address: e.g. vs:main> eth0 vs:main:eth0> ip set 0.0.0.0 vs:main:eth0> netmask set 255.255.255.0 vs:main:eth0> broadcast set 0.0.0.0 vs:main:eth0> gateway set 0.0.0.0 vs:main:eth0> sh IP address: 0.0.0.0 [*] Netmask: 255.255.255.0 [*] Broadcast: 0.0.0.0 [*] Gateway: 0.0.0.0 [*] VLAN tag: (none) vs:main:eth0> up TECHNICAL NOTE MIGRATING VSG HUB SITE TO RC PAGE 6 OF 11 To make both these changes permanent save the configuration with the write command. Remember this may result in loss of service: vs:main> write The following parameters have been changed and applying these changes will result in a loss of service VectaStar eth0 configuration Are you sure you wish to apply these changes now? (Yes/No) Yes Stopping VectaStar services: Starting VectaStar services: After writing the configuration the ssh connection will close to the ZFS. TECHNICAL NOTE MIGRATING VSG HUB SITE TO RC PAGE 7 OF 11 3.5 ATTACHING THE GBITAP TO THE RC To complete the migration of the ZFS to the RC Hub site, the fibre ports on the RC need to be configured to accept the new Gbit APs. If there are no Gbit APs already on the RC, then we recommend starting at port P1 and adding ports incrementally. 1. From the VNMS vsnet window, select the RC and click configure 2. In vsbs click configure next to the RC identifier 3. In vsrc select the port that is to have an AP attached and click configure 4. Change the mode to VectaStar and click Apply 5. Once you have modified the settings for all affected ports, press Reconfigure to action the changes 6. Repeat steps 1 to 3 for each port that will have a Gbit AP attached. Note that there is an RC requirement for port pairs (P1/P2, P3/P4 etc) to be configured to the same type. Therefore if you are configuring P1 for VectaStar, then P2 will also need to be used for VectaStar services. The Gbit APs now need to be bought into operation: 1. Power off the Gbit APs that are to be added 2. Connect the APs to the RC starting with port P1 for example 3. Power on the APs in turn 4. Check that the APs have become operational; this is shown in vsbs by a green tick. You may need to click Get a couple of times to refresh the display until the green tick is displayed 5. Select each AP in turn and configure the AP to set its channel parameters Confirm the RTs have registered: 1. Check that all the RTs have registered correctly. This is shown with a green tick next to each RT under the users tab in vsbs. You may need to click Get a couple of times to refresh the display until the RTs register. If any RTs do not re-register then it is likely that there is a configuration issue and this should be investigated. TECHNICAL NOTE MIGRATING VSG HUB SITE TO RC PAGE 8 OF 11 4 REVERTING TO ZFS MODE Most problems with the conversion from ZFS to RC can be resolved quickly by investigating the configuration of the RC. Sometimes, however, it is necessary to revert the AP to ZFS mode and run the ZFS for a short period of time using the upgraded software release. If this does not solve the problem it will be necessary to return all ZFS-APs and RTs to the original release. 4.1 REVERTING A GBITAP TO ZFS MODE WITH LATER SOFTWARE 1. Connect a laptop to copper port on the Gbit AP. 2. Use the vsinstall app (3.12 or later) to reinstall the original software build onto the ZFS. You may also need to: • Reconfigure the ZFS, during the reconfigure stage set the ODU to ZFS mode • If necessary also change the interface type to fibre • Configure the IP address and optional VLAN tag that was removed during the upgrade process 3. Connect the ZFS back into your network and use the VNMS to run the zfs_restore.sh utility. This will restore the previously saved configuration. For example: vnms@vnms:~$sudo –s [sudo] password for vnms: root@vnms:~#cd /usr/local/vectastar/bin root@vnms:~#./zfs_restore.sh 192.168.117.141 ../backup/192.168.117.141/BU_AP-1_backup_20110923_1153.tar.gz The output will be something like the following: /usr/local/vectastar/backup/192.168.117.141/BU_AP-1_backup_20110923_1153.tar.gz /usr/local/vectastar/backup/192.168.117.141/BU_AP-1_backup_20110923_1153.tar.gz is a valid configuration for ZFS Please wait while backup is restored... This may take up to 30 seconds Warning: Permanently added '192.168.117.141' (RSA) to the list of known hosts.
[email protected]'s password: copied config and rebooting - may take a few mins to return Warning: Permanently added '192.168.117.141' (RSA) to the list of known hosts.
[email protected]'s password: Connection to 192.168.117.141 closed by remote host. IP Config for interface eth0 on the ZFS and the VLAN TAG status is... DEVICE=eth0 BOOTPROTO=static IPADDR=192.168.117.141 NETMASK=255.255.255.0 BROADCAST=192.168.117.255 NETWORK=192.168.117.0 HOSTNAME=AP-1 cat: flashC/icu/bridge.conf: No such file or directory Don’t worry about the warning in the last line. TECHNICAL NOTE MIGRATING VSG HUB SITE TO RC PAGE 9 OF 11 4.2 REVERTING A GBITAP TO ZFS MODE WITH ORIGINAL SOFTWARE You will probably need to visit CPE sites if you are performing these steps: 1. Connect a laptop to the copper port on the Gbit AP 2. Use the vsinstall app (3.12 or later) to reinstall the original software build onto the ZFS. You may also need to: • Reconfigure the ZFS, during the reconfigure stage set the ODU to ZFS mode • Configure the IP address and optional VLAN tag that was removed during the upgrade process 3. Reboot the ZFS 4. Connect the ZFS back into your network 5. Use the VNMS to run the zfs_restore.sh utility to restore the previously saved configuration. See the instructions in the previous section. 6. In the vsbs Users tab, check the CPEs have registered (they should have green ticks). 7. If they do register then from the vsnet application on the VNMS select configure and in the vsbs tool user window select all the RTs and press upgrade. This will offer the old software release and the RTs can be downgraded to the old release. 8. If the CPEs do not register then they will need a site visit to re-install the original software. TECHNICAL NOTE MIGRATING VSG HUB SITE TO RC PAGE 10 OF 11 5 DOCUMENT PROPERTIES Revision Action Reference Date Released A01 Initial release PVD 29/05/11 A02 Updates to procedures LAJ 23/09/11 A03 DOCUMENT REVISION HISTORY The information contained within this document is subject to change without notice. Cambridge Broadband Networks Limited makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for purpose. Cambridge Broadband Networks Limited shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance or use of this material. Cambridge Broadband Networks Limited assumes no responsibility for the use or reliability of interconnected equipment that is not supplied by Cambridge Broadband Networks Limited. This document contains proprietary information, which is protected by copyright. All rights reserved. No part of this document may be photocopied, reproduced, or translated to another program or language without prior written consent of Cambridge Broadband Networks Limited. Information contained herein has been prepared by Cambridge Broadband Networks Limited solely for the use of Cambridge Broadband Networks’ employees, agents and customers. Any dissemination of the information and concepts contained herein to other parties is prohibited without prior written consent of Cambridge Broadband Networks Limited. Copyright © 2011 Cambridge Broadband Networks Limited. Cambridge Broadband Networks reserves the right to make changes to the specifications of the products detailed in this document at any time without notice and obligation to notify any person of such changes. VectaStar, Cambridge Broadband, and the Cambridge Broadband logo are trademarks of Cambridge Broadband Networks Limited. All other trademarks are acknowledged and observed. Mention of third-party products does not constitute an endorsement or recommendation. This document is based on template DOC-TMPL-0009-C00. TECHNICAL NOTE MIGRATING VSG HUB SITE TO RC PAGE 11 OF 11