Upgrade Guide

Appear TV Platform

 Appear TV AS Tel: +47 24 11 90 20

PO Box 8 Lilleaker Fax: +47 24 11 90 21
NO-0216 Oslo Email: support@appeartv.com
Norway appeartv.com

Doc. Name : Upgrade Guide

Revision : 3.28
Date : 20.03.2018
 Appear TV

1 Introduction
The Appear TV Maintenance Center is an independent web application running on the MMI
board of the Appear TV unit. Its main purpose is to provide a user friendly software upgrade.

The Maintenance Center provides:

o Software upgrade
o Module configuration
o Remote card reset
o Remote power reset (XC5000, XC5100, DC1001, SC2001, MC3001only)

The Appear TV Maintenance Center is always provided as part of the MMI software. Updates for
the Maintenance Center itself will therefore not be available until new software has been
installed on the MMI board. Therefore, we recommend that you install any new software on the
MMI board first. Then, upgrade the rest of the cards.

2 Requirements
2.1 Browser
The Maintenance Center is a web application and a browser is required to view it and interact
with it. This application was developed and tested to work properly in the following browsers:

o Mozilla Firefox 11.xx and above

o Microsoft Internet Explorer 11 and above
o Opera 9.xx and above
o Google Chrome

Browsers that are not in this list have not been tested for compatibility.

2.2 Software File

Upgrading software to an Appear TV unit using the Maintenance Center requires a repo file. This
is a file generated by Appear TV containing software files for the cards that are installed in your
unit. This file also contains an XML describing the software files stored in the repo file along with
the target cards for these software files.

Repo files should have filenames in the following formats, where x.xx.xxxx represents the
software version number.

The required software repo package is displayed in the Maintenance Center for each card. For
the 4RU view, this information can be found by hovering over the card. In the 1RU view, this is
available in the SW Package column. The full list of modules and corresponding repo files are as
follows:

Switch w/ Management
appear-mmi-repo-x.xx.xxxx.tar.gz
Switch w/ IP + Management
Bamboo platform card upgrade:
DVB-S/S2 Enhanced (input, 2 slot)
DVB-S/S2/S2X (input, 1 slot)
DVB-C (input, 1 slot)
appear-bamboo-repo-x.xx.xxxx.tar.gz
DVB-T (input, 1 slot)
DVB-T2 (input, 1 slot)
ASI (input/output 4 port)
Dual IP (in/out, cloned output or seamless input)

20/03/2018 2
 Appear TV

EPG (HW Rev 2)

DVB-T2 Gateway ASI / IP Output
DVB-S/S2/S2X Modulator (output, 1 slot)
ASIO based card upgrade:
ASI (input/output)
IP (input/output)
COFDM (input, 2 slot)
appear-asi-repo-x.xx.xxxx.tar.gz QAM (input, 2 slot)
DVB-S/S2 (input, 2 slot)
Scrambler/Bulk Descrambler (CSA/AES)
Audio leveling
EPG
appear-latens-repo-x.xx.xxx.tar.gz Bulk Descrambler (Latens only)
SDI Encoder
Analog Encoder
appear-coder-repo-x.xx.xxx.tar.gz Transcoder
Universal Multiscreen Transcoder (TC-200)
Universal Broadcast Transcoder (TC-200)
Universal HVQ SDI Encoder
Universal Dense SDI Encoder
Universal Multiscreen Encoder
appear-oak-repo-x.xx.xxx.tar.gz Universal HVQ Transcoder
Universal Multiscreen Transcoder (TC-400)
Universal Broadcast Transcoder (TC-400)
Audio Processor (AP-100)
qamout-a-repo-x.xx.x.tar.gz
qamout-b-repo-x.xx.x.tar.gz QAM/COFDM modulator (1 slot)
cofdmout-cable-repo-x.xx.x.tar.gz
dvbt2out-sfn-repo-x.xx.x.tar.gz
dvbt2out-mfn-repo-x.xx.x.tar.gz
DVB-T/T2 modulator
dvbtout-sfn-repo-x.xx.x.tar.gz
dvbtout-mfn-repo-x.xx.x.tar.gz
dvbs-lband-x.xx.xx-repo.tar.gz
DVB-S/S2 modulator (IF or L-Band)
dvbs-if-x.xx.xx-repo.tar.gz
isdbtout-cable-repo-x.xx.xx.tar.gz ISDB-T modulator
tvmod-repo-x.xx.x.tar.gz TV Modulator card
adm-repo-x.xx.xxx.tar.gz ADM based card (ADM-SDI, ADM-RF, ADM-BB)
clock-ref-repo-x.xx.xxx.tar.gz Clock Reference (GPS/SFN) card
ddm-mk2-x.xx.xxxx-repo.tar.gz DDM based RF output card
ddm-dci-mk2-x.xx.xxxx-repo.tar.gz DDM based Descrambler card
dab-repo-x.xx.xxx.tar.gz DAB Modulator
radio-repo-x.xx.xxxx.tar.gz FM Radio card

It is not advisable to rename files as they may become invalid for the Maintenance Center.
To load these files correctly, refer to Section 4. Appear TV will provide, upon request, a repo file
for the particular software version that you wish to upgrade your unit to.

3 Accessing the Maintenance Center

The Maintenance Center is part of the MMI software. You can access it by entering the IP
address of the Appear TV unit’s MMI card followed by a colon and the Maintenance Center’s
special port number 8088.

20/03/2018 3
 Appear TV

It is also possible to enable password protection for the Maintenance Center. This password is
identical to the one used for the MMI GUI. Consequently, the Maintenance Center’s password
cannot be set separately.

Figure 1 - Accessing the Maintenance Center

Figure 2 - Maintenance Center list view

Upon entering the Maintenance Center, you will be presented with Table View (see Figure 2) if
you have a 4RU chassis. To switch to Hardware View, simply click on the table view thumbnail
on the right.

In Hardware View, you can hover your mouse cursor over one of the cards to display the card
type, software version and boot version. This data is also listed in Table View for all cards.

20/03/2018 4
 Appear TV

Figure 3 - Maintenance Center hardware view

4 Upgrading Software
The main function of the Maintenance Center is to allow easy software upgrades of Appear TV
systems. The Maintenance Center allows multiple cards in the same chassis to be upgraded
using a single file.

To start the upgrade process, select the cards you want to upgrade by clicking on its slot in
Hardware View or by clicking on the list item in Table View. Selected cards are highlighted
orange. Slots with no cards installed are not selectable. To deselect a card, click on it a second
time. To select all invert the selected cards at once, click the chassis of the unit in hardware view.

Next, select the correct software file by clicking on the button inside the box. The text on this
button may vary, depending on your browser: Browse, Choose or Choose File. Be sure to select
the correct software file. You can change this software file while the upgrade sequence has not
begun yet by clicking on Remove.

Click on the Upgrade button to start upgrading the selected cards.

20/03/2018 5
 Appear TV

Figure 4 - Maintenance Center after the slots and software files have been selected

Figure 5 – Uploading files during a software upgrade

20/03/2018 6
 Appear TV

Figure 6 - Upgrading the cards

Figure 7 - Rebooting after an upgrade

Figure 8 - Successful upgrade

20/03/2018 7
 Appear TV

Once the upgrade sequence has completed successfully, a confirmation dialog will be displayed
(Figure 8). This dialog comes with three buttons: View Details, View MMI and Start Over.

o View Details - displays the text of the upgrade sequence.

o View MMI - will take you to the Web GUI of the MMI.
o Start Over - will clear the confirmation dialog, the upgrade sequence text and the
selections you have made so you can start a new task.

To further verify that the card has been upgraded to the new software, click Start Over and
check that the card has the new software version number. You can also verify this by clicking
View MMI then going to the Web GUI’s About Page.

5 Software Upgrade Procedure

When upgrading to the latest Appear TV software, we support this process from the previous
two major releases. If the software is older than this, then it is first recommended to upgrade to
an intermediate version of software before upgrading to the latest. For example:

When checking for compatible software for all modules, it may be there is no corresponding
software version for some cards. In these cases, the software made available, should be
compatible. If there is incompatible software being used, there will be an alarm raised in the
main Appear TV GUI.

When upgrading a unit, the following procedure should be followed to ensure an error free
upgrade of the unit. For the correct file type for each card, please see section 2.22 Software
File. Using the Maintenance Center, follow the steps below:

1) Upgrade the MMI card using the appear-mmi-bamboo-repo-x.xx.xxxx.tar.gz file

2) Refresh your browser window. This will ensure that the latest Maintenance Center
software is loaded correctly for the rest of the upgrade process.
3) Upgrade the remaining slave modules in the unit.
a. The files required will be displayed in the Maintenance Center list view (see
section 3, Figure 3 - Maintenance Center ) or see the table in section 2.2.
b. Each card that uses the same upgrade file can be selected together in order to
upgrade the modules in parallel.

Once this procedure is complete, all cards in the unit should be upgraded to the versions
specified in the filenames of the software upgrade packages.

If you encounter any errors during this process, please check the Appendix section or contact
Appear TV support.

20/03/2018 8
 Appear TV

6 Module Setup
From the Maintenance Center, it is possible to configure or change the firmware options on
some modules. This menu is available when clicking on an individual module and clicking the
Setup button. If there are no options for the module, then this button will not be selectable. The
various options are:

 Convert Card
o Board Type. If this option is available, it will list the compatible
modes/firmware that the module supports.
To change the firmware of the module, select the new mode and click Apply.

After this has been applied, then module should not be rebooted and will
need to be upgraded with the same or newer software in order for the
correct firmware to be loaded.

Once the upgrade has finished, it will be then possible to remove the previous
module type from the main GUI About page for the new module type to log in.

o MMI Selection. This is available on some modules (non Switch) and allows the
configuration of the default backplane/MMI to log into. If this is set to Auto
then the MMI in slot 0 will be selected. If Slot 17 is selected, the module will
then log into the MMI in slot 17 (if available).
 Please note that if the module is switched to log into the MMI in slot
17, but there is no MMI present, then this module may not log back
into the MMI in slot 0.
After this setting has been applied, the module will need to be reboot for the
settings to take effect.

Figure 9 – Convert Card dialog

 Setup Features (Switch / MMI only)

o Redundancy Mode. This allows you to select the redundancy mode of the
Switch module. The options are
 Internal – MMI in Internal Redundancy Mode

20/03/2018 9
 Appear TV

 MMI – The MMI uses MMI Redundancy Mode

Once the setting has been applied, the module will need to be reboot before
the settings will take effect.
For more details on the redundancy modes, please refer to the User Manual.

Figure 10 – Setup Feature dialog

 Virtual Split (Switch / MMI only)

o This allows the chassis to be virtually split in two with the MMI in slot 0
controlling some modules and the MMI in slot 17 controlling the others
o For MMI 0,the slot set here will force all modules less than or equal to this slot
to be forced to MMI 0
o For MMI 17 (backplane 2),the slot set here will force all modules greater than or
equal to this slot to be forced to MMI 17
 Exclusive output mode (Cloned Switch/Dual IP Output only)
o Enabling this mode will output streams on only the A port unless there is no
link on A in which port B will become active

20/03/2018 10
 Appear TV

7 Upgrade Scheduler
The upgrade scheduler is intended to ease the process of upgrading large scale environments.
The basic principle of the Upgrade Scheduler is to let the units themselves check for new
software located on a defined FTP server. The FTP server contains a schedule file, the software
images, and the log files of each units upgrade.

Unit 1
FTP Server
/schedule.xml
Unit 2
/Software
/Upgrade_log_files
Unit n

The FTP server is a passive component which provides the data, and a storage area where the
units push the upgrade result after a completed or failed upgrade. The actual process of
upgrading the units is managed by the units themselves.
The following algorithm applies:

 When the automatic upgrade scheduler is activated in a unit, it accesses the ftp server
and downloads the schedule file.
 The units are upgraded in the order at which they are listed in the schedule. If not listed
the unit is not part of the schedule.
 An upgrade is started only if the time is within the Date/time-field of the maintenance-
window specified in the schedule.
 All software packages listed in the schedule file will be processed by the unit. I.e.
o Download the first package listed in the schedule file to the controller card
(MMI Card)
o Unpack the image, and check what cards the image is intended for. If any cards
of that type are present in the unit, install the software to all matching cards.
o Only upgrade if the software version in the image is different from the one
already installed.
o Remove the software package from the controller card.
o Process next image listed
 When all images are processed, and then upload the report file. (For details see
separate section below)
 When a successful report file is pushed, then the next unit in line is free to start
upgrading.
 If the upgrade of a unit failed, then the entire upgrade process will terminate.

7.1 Schedule file

The schedule file (schedule.xml) is the main part of the system and defines which units to upgrade, and
how the upgrade shall be performed. This file is located at the root of the FTP account.

20/03/2018 11
 Appear TV

A typical schedule file: serial mode

<?xml version="1.0" encoding="UTF-8" ?>

<schedule>
<maintenance_window startdate="20140105" enddate="20141228" starttime="07:05"
endtime="22:05"/>
<options>
<run concurrent="false" dryrun="false" force="false" noreboot="false"/>
</options>
<units>
<unit ip="10.10.30.49"/>
<unit ip="10.10.30.40"/>
<unit ip="10.10.30.30"/>
<unit ip="10.10.30.41"/>
<unit ip="10.10.30.31"/>
</units>
<packages>
<package mmi="true">
ftp://192.168.1.200/software/3.26/appear-mmi-repo-3.26.203.tar.gz
</package>
<package>ftp://192.168.1.200/software/3.26/appear-bamboo-repo-3.26.431.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/appear-asi-repo-3.26.431.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/appear-coder-repo-3.26.431.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/adm-repo-3.26.2729.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/cofdm-cable-repo-3.26.2.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/dvbtout-sfn-repo-3.10.4.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/dvbt2out-sfn-repo-3.10.5.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/qamout-a-repo-3.26.2.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/qamout-b-repo-3.26.2.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/dvbs-lband-repo-3.26.3.tar.gz</package>
</packages>
</schedule>

Figure 1 Schedule file: serial mode

A typical schedule file: concurrent mode

<?xml version="1.0" encoding="UTF-8" ?>

<schedule>
<maintenance_window startdate="20140105" enddate="20141228" starttime="07:05"
endtime="22:05"/>
<options>
<run concurrent="true"/>
</options>
<units>
<unit ip="10.10.30.49"/>
<unit ip="10.10.30.40"/>
<unit ip="10.10.30.30"/>
<unit ip="10.10.30.41"/>
<unit ip="10.10.30.31"/>
</units>
<packages>
<package mmi="true">
ftp://192.168.1.200/software/3.26/appear-bamboo-mmi-repo-3.26.431.tar.gz
</package>
<package>ftp://192.168.1.200/software/3.26/appear-bamboo-repo-3.26.431.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/appear-asi-repo-3.26.431.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/appear-coder-repo-3.26.431.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/adm-repo-3.26.2729.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/cofdm-cable-repo-3.26.2.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/dvbtout-sfn-repo-3.10.4.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/dvbt2out-sfn-repo-3.10.5.tar.gz</package>

20/03/2018 12
 Appear TV

<package>ftp://192.168.1.200/software/3.26/qamout-a-repo-3.26.2.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/qamout-b-repo-3.26.2.tar.gz</package>
<package>ftp://192.168.1.200/software/3.26/dvbs-lband-repo-3.26.3.tar.gz</package>
</packages>
</schedule>
Figure 2 Schedule file: concurrent mode

The following parameters are available:

The maintenance window specifies the time the unit is allowed to perform an
upgrade. This is specified in the following format
Maintenance window
 startdate / enddate : YYYYMMDD
 starttime / endtime: HH:MM

The option fields changes the default behavior of the upgrade algorithm.
 dryrun: does everything except upgrade of unit.
 concurrent: By default the system will do a serial upgrade.
Option fields This can be bypassed by the concurrent attribute.
 force: This will override default behavior that prevents
upgrade if the version matches the version already installed
in the unit.

Lists the IP address of the units that is part of this schedule. The order is
Units
significant as the units are upgraded in the order listed in the schedule.

Lists all the packages that should be installed. Note the order is significant.
The mmi="1" attribute of the package tag forces the repo to be upgraded last
Packages when multiple repo files are scheduled for each unit; else the units are
upgraded in the same order the packages occurs in the scheduler
configuration file. Always set this for the MMI repo package.

7.2 Report format

When a schedule .xml file has been downloaded, verified and activated as the current schedule the
upgrade scheduler will create a folder on the FTP server for storing upgrade reports from all the units in a
schedule. The folder name is set equal to the <maintenace_window> startdate attrubute in the schedule
.xml and is created in the same folder as the scheduler .xml file is stored.

Each unit that completes a scheduled upgrade, uploads a "upgrade report" file into this folder, named by
it's IP address concatenated with the overall result of the upgrade. i.e <unit-ip-address>_OK.log. The
content is in plain ASCII and are a copy of the unit's local software upgrade log.

In addition to report logs, two hidden files .current.log and .versions.log, can be found in this folder.
These files are used to store the internal state of the units during upgrade, the content of these files are
proprietary and the content format can change without any notice.

Example:
File name - 10.10.30.32_OK.log

7.3 Unit Configuration

20/03/2018 13
 Appear TV

For a scheduled upgrade to occur each unit must be enabled to scheduled upgrades. To do these Go-> to
the maintenance node under the admin page.

Figure 3 Unit configuration

The following parameters are available:

Enable Schedule
Activate the scheduling feature.
upgrades

The location of the schedule file. Note the schedule file itself must be called
Repository FTP server
schedule.xml.

FTP username Specify the FTP username.

FTP password Specify FTP password.

How often the unit will check for new schedule file. i.e 10 min, 30 min, 1hr, 12
Update interval
hr. or 24 hr.

Next scheduled
The estimated time until unit upgrade starts for this unit.
upgrade

Following are the state that can be displayed

 Disabled
Upgrade state
 Idle
 Upgrading
 Waiting as #number in queue.
Maintenance center URL to the Maintenance Cetner GUI.

7.4 Upgrade of units with Twin MMI

When upgrading units with two MMI modules, it is recommended to keep these two IP addresses
adjacent in the schedule file. This will minimize the offset regarding upgrade of the two cards. The
general procedure should be as follows:

20/03/2018 14
 Appear TV

 First upgrade the MMI in slot 0 card

o This is to ensure that the slave modules are logged into the MMI in slot 0 after upgrade.
 Also: if one or more cards are logged into the the other MMI during upgrade then the upgrade
will not terminate in slot 0, as the system will assume that the card will be upgraded when the
card in slot 17 is processed. If however the card that was not upgrade from slot 0 is not reachable
when slot 17 is processed, then the system will regard this as a failure.
This could happen if an internal card switches in between the upgrade of the first vs the second
MMI. Hence the upgrade script should perform the two cards as close as possible in time.

In concurrent mode the cards logged into the local MMI will be upgraded. Cards logged into the other
side will be ignored. Hence in concurrent mode it is technically possible to miss slave modules if they
switch login-state at a "bad" time during the upgrade.

7.5 Timing for upgrade using scheduler.

The time consumed during upgrade is highly dependent on the number of files in flash that needs to be
updated. When upgrading cards from one major release to a later major release, the number of files in
flash that needs update is usually high.

In general the time taken for the Upgrade Scheduler will be similar to that of a manual upgrade using
Maintenance Center. As a guide for this upgrade time, the below table can be used as a reference:

Type of card Time

MMI 14-18 minutes
Bamboo platform cards 10-14 minutes
ASIO platform card 8-12 minutes
Coder card 10-12 minutes
Modulator card 10-12 minutes
ADM /DDM card 6-10 minutes
Complete Unit 35-45 minutes

20/03/2018 15
 Appear TV

8 Switch Card Hardware Upgrade Process

For existing chassis that currently have the older switch card (without management) installed,
you will have to follow the following process in order to upgrade to the new switch card. This will
allow you to replace the existing switch card and move the configuration (and MMI function) to
the new switch/MMI card.

Things you will need before the upgrade:

- A unit running latest 2.16 MMI software. Slave modules will also need to be running 2.16
software.
- A configuration export of the current MMI card
o You can perform this by going to the Import/Export page in the GUI and clicking
the Export button

Once the above is performed, then you will need to follow the following steps:
1) Convert the current ASIO MMI card to slave mode and reboot. Please see section 12.1
Changing ASIO MMI to slave for details.
2) Physically remove the old switch card and insert the new. By default this will be in slot 0,
and also in slot 17 if using Internal Redundancy.
3) Connect to the control port on the new switch (MMI) card to a local connection with
access to the 192.168.1.xxx network
a. This will have a default IP address of 192.168.1.100
4) Restore the configuration file
a. This can be done by going to the Import/Export page and selecting the
configuration file.
b. In this step, it is best to also tick the Include local IP addresses checkbox to also
restore any IP addresses previously configured.
c. If there are any issues with the configuration import, please see the note below
and/or contact Appear TV Support.
5) Navigate to the Admin page and change the IP address of the switch control port to that
of the previous MMI
a. At this stage you can also assign the MMI a new IP address if required
6) Remove the local Ethernet connection and move the connection from the Control port
previous MMI card to the Control port of the new switch card.
7) Access the unit IP address and check the GUI is present
a. In order for you to access the IP address, you may need to delete the ARP entry
for this IP address on your computer. This can be done by running the following
command:
arp –d <ip-addr>
8) Complete the upgrade of the unit to the latest software assuring that the upgrade path is
at maximum two major versions at a time

While we undertake to test configuration import from 2.16 to the 3.26 software, there
may be some cases where the configuration is no longer supported.
In these cases, the configuration of the unit will have to be set back to factory default
and the configuration done manually by the operator.

20/03/2018 16
 Appear TV

9 Rebooting Unit and Cards

The Maintenance Center enables you to reboot the power supply (for XC5000, XC5100, DC1001,
SC2001 and MC3001 units) and one card or multiple cards from the same unit quickly.

To reset the power supplies, click the Reset Power button. As this will affect the whole chassis,
you will then be prompted if you are sure. If you click OK the power supplies will be reset.

To reset cards in the unit, select a slot (or several slots) you want to reboot simply by clicking on
it. Then, click Reboot to start rebooting. Wait for the process to complete to verify that the
reboot has been successful.

Figure 11 - Rebooting a card using the Maintenance Center

10 Licensing
In the Appear TV unit, licenses are stored on the individual cards and are valid after an upgrade.
If you encounter any issues with licensing after an upgrade, please contact Appear TV either via
your Sales/Support contact, or email support@appeartv.com.

11 Downgrade Procedure
Downgrade is not recommended via the Maintenance Center. If you are required to downgrade
a module, please contact support@appeartv.com for the correct procedure for the module.

20/03/2018 17
 Appear TV

12 Appendix
12.1 Changing ASIO MMI to slave
This describes the process of changing a card which was previously set to MMI mode, to be in
slave mode. This is only applicable to input cards and it is only valid to have one MMI present per
unit/backplane.
1) Telnet to the slave card
- User: asio, password: bozo
- If the IP address of the card is not known, please use the hardware jumper to
reset it to the factory default (192.168.1.100). More details of this procedure can
be found in the User Manual.
2) Enter the following commands:

su
hostname
atvcardsetup <module> slave
reboot
- The <module> is the name of the card returned from the ‘hostname’ command
- The list of possible <module> values can also be checked by running the
‘atvcardsetup’ command without any parameters.
- If you receive a warning about missing FPGA when the ‘atvcardsetup’ command
is run, please press ‘N’ and contact Appear TV.
- In the case that you are changing a slave IP input card to be an MMI on backplane
2 for Internal Redundancy, <module> can be set to ipin_bp2.
3) After the reboot of the module it should now be in slave mode.

12.2 Removing Configuration Database

In some cases it is required to clear the configuration database on the MMI card. This is achieved
by doing the following:
- Telnet/SSH to the MMI IP address
- User: asio
- Pass: bozo
- Type the following
- su
- factory-default

You will then be prompted as to which settings you would like to clear:

 Wipe configuration database ? [y/N]:

o Remove and re-build the configuration database. This will remove any
configured input/output services as well as IP address of any dataports
 Reset external ip-address ? [y/N]:
o Remove the IP address of the switch control port. After applying this setting,
the IP address of the unit will be 192.168.1.100
 Reset http password ? [y/N]:
o Reset the web GUI password. After applying this setting, the user/pass will be
reset to admin/admin.

12.3 Troubleshooting
12.3.1 Module does not boot (blue LED)
A blue LED on the module can indicate the following:
1) There is no module firmware file present

20/03/2018 18
 Appear TV

- To remedy this, you will need a direct connection to the control port of the
module. You should be able to ping the device and load the Maintenance
Center. If the IP address is unknown, please use the hardware reset to set this to
default (192.168.1.100)
- With the Maintenance Center loaded, re-load the latest software
2) There is problem booting the card to the operating system
- First try to ping the device, if this is possible, follow the above firmware missing
steps
- If this is not possible, there is a chance that the card is not booting into Linux and
will need to be returned for RMA. Please contact Appear TV support in these
cases.
3) Unable to connect to the switch card, or a failure with the backplane
- Please try the module in another slot in the chassis. This will check if there is a
problem with the backplane connection on this slot
- If available, change the switch card with a spare

12.3.2 Maintenance Center: Software Upgrade Failed

When the software upgrade fails in the Maintenance Center, it is best to click the ‘View Details’
to see the explanation text. This can sometimes point to the cause and resolution of the
problem. Below are further explications:
Not enough memory for upgrade, please run mc-update before applying this repository
 This indicates that the MMI card does not have enough memory to perform the upgrade.
The next steps to try are:
1. Reboot the MMI card
2. Try the upgrade again
3. Re-run the original upgrade on the slave cards
 In these situations, it is also possible to perform a manual upgrade on the target
cards.

20/03/2018 19