BusinessPhone Communication Platform 6.0
Maintenance Instruction ASB 150 02

## ASB 150 02 R14 (and higher) Software licensing

### General

Together with ASB 150 02 Release 14 the software licensing concept based on the hardware key FECU is replaced by a software key concept.

The software key is represented by a license file which is stored on the compact flash card of the CPU‑D5 if available. If there is no CPU-D5 in the system (upgraded system based on a CPU-D4) it is possible to store the license file on the compact flash card of the MFU, IPU or VMU-HD.

Compared to a hardware key, the software key provides a high flexibility regarding feature bundling (license steps) and a high flexibility regarding license updates as they can be done remotely via the BusinessPhone Management Suite (BMS).

The licenses can be ordered via the normal order process, each license step is represented by an own article number. For each ordered article number a Unique Pick Number (UPN) will be delivered. This UPN is used for the the Ericsson License Center (ELC, part of the Ericsson Partner Network) to create the customer’s license file with the bought features. The Ericsson License Center web page provides authorised users the possibility to create the license file directly.

### Pre-requisites

In order to use the software licensing concept, following minimum requirements have to be fulfilled.

#### Hardware configuration

Configuration | CPU-D4 | CPU-D5 | FECU | License carrier
Alternative | Type | CPU-D5 | MFU or VMU‑HD or IPU
1 | New sales (R14 or higher) |  | X |  | X |
2 | R9-R12 upgrade to R14 or higher | X |  | X |  | X
3 | R13 upgrade to R14 or higher | X |  | X |  | X
4 | R13 upgrade to R14 or higher |  | X | X | X |
5 | Repair CPU-D4 (R9-R13 ) to CPU‑D5 (R14 or higher) |  | X | X | X |
6 | Repair CPU-D4(R14 or higher) to CPU-D5 (R14 or higher) |  | X | X |  | X

#### Hardware, Software & Firmware revisions

- FECU KDUBS 130 06 / x (x = Package 1-10)
- CPU-D4 (ROF 157 5124/1)

  |  | R-state PCB |  | R2A |
  |  | HW-code |  | 3 |
  |  | FW |  | RYS 102 533 R3G |
  |  | SW |  | LZY 203 2234 (Release 14) |

- CPU-D5 (ROF 157 5124/2)

  |  | R-state PCB |  | no limitations |
  |  | HW-code |  | no limitations |
  |  | FW |  | RYS 102 548 R1A |
  |  | SW |  | LZY 203 2234 (Release 14) |

- IPU (ROF 157 5133/1 )

  |  | FW |  | RYS 102 539 R4A |

- MFU (ROF 157 5132/_ )

  |  | FW |  | RYS 102 538 R5A |

- VMU-HD (ROF 157 5133/_

  |  | FW |  | RYS 102 526 R4A |

### Licensed features

Equal to the former FECU Index 1, there exists a basic license entry in the license file, which covers all basic features up to the latest release. For a detailed feature overview see document
Facility description General, 15534‑ASB150 02 Uen.

On top of the basic license entry there exists additional license entries for following features:

- Mobile Extension
- Unified Messaging
- CTI
- Networking
- VoIP Gateway

License modularity and order rules

The licensed features are available in different modularity steps. From commercial point of view, these modularity steps are defined as so called color packs which are available in green, orange and red color (see table below).

Functional area/Pack | included in the Basic license | Green Pack | Orange Pack | Red Pack | Plus Pack | Maximum
Mobile Extension | 2 | 5 FALBS 102 44/G | 20 FALBS 102 44/O | 40 FALBS 102 44/R | 5 FALBS 102 44/P | 100 | [users]
Unified Messaging | 2 | 20 FALBS 102 45/G | 50 FALBS 102 45/O | 100 FALBS 102 45/R | 5 FALBS 102 45/P | 200 | [users]
CTI | 2 | 5 FALBS 102 46/G | 80 FALBS 102 46/O | - | to 80 FALBS 102 46/P | 80 | [users]
Networking | Full, 2 Interface | Standard unlimited FALBS 102 49/G | Full 32 FALBS 102 49/O | Full unlimited FALBS 102 49/R | to Full unlimted FALBS 102 49/P | Full unlimited | [function]
VoIP Gateway | - | Gateway open FALBS 102 50/G | - | - | - | Gateway open | [function]

Each field in the table represents one article number. Packs from different features can be freely combined (modular concept), for instance, the Mobile Extension Green Pack (5 users) and the Unified Messaging Orange Pack (50 users). For each of the listed article numbers a Unique Pick Number will be delivered. This Unique Pick Number is used for the web license application within the Ericsson Partner Network (http:\\enterprise.ericsson.net) to create the customer’s license file with the bought features.

For each of the listed features one of the available color packs can be chosen. For optional expansions the plus pack can be added to one of the color packs - also multiply, if desired. For instance, in case of the feature Mobile Extension either the green pack (5 users), the orange pack (20 users) or the red pack (40 users) can be ordered. It is not possible to combine a Mobile Extension green pack and a Mobile Extension orange pack in order to gain 25 users. But it is possible to add 4 times a Mobile Extension plus pack (+ 5 users) to a Mobile Extension green pack in order to expand from existing 5 users to 25 users. Such expansions are done in multiple steps, meaning one order for x plus packs causes a delivery of x UPN numbers.

Note

A plus pack can only be registered when following criteria’s are fulfilled:
- it will be used for new sales in combination with a colour pack.
- it will be used for add on sales with an existing installed colour pack.
- it will be used for add on sales in conjunction with an installed FECU (Index 2 –10).

Note

The Unified Messaging license requires in addition also a CTI license.
( £ 20 Unified Messaging users 5 CTI users are required, >20 Unified Messaging users, 80 CTI users are required)

Note

The software VoIP Gateway license requires also the corresponding VoIP Gateway IPU lincese (see chapter IPU - Software licensing.

Note

The VoIP Gateway license disables all other licenses except the basic license.From technical point of view there exists no direct relation in ASB 150 02 between the licensed features and the licensed modularity, to their dedicated article numbers nor to their defined commercial names. By using the BMS only the licensed features and the current modularity can be read out (for details see the following chapter).

Note

The Basic License also enables two BackStage 5.0 (or higher) reference users without the need of a CTI License nor a WIBU-Box on the BackStage Client side.

Note

In order to give the sales people an accurate input for the ordering of feature enhancements at the customer site, use following rule of thumb:
“As far as there exists an entry in the Licensed feature table for the desired feature, only a plus pack can be registered. If there exists no entry for the desired feature, color packs in combination with plus packs can be registered.”

### The license file

The license file which is stored on the CPU‑D5, MFU, IPU or VMU-HD compact flash card contains license entries for all features which were bought by the customer and which are registered in the Ericsson License Center (ELC).

All license entries are encrypted by the ELC by using a two key security mechanism based on the system ID of ASB 150 02 and the storage ID of the compact flash card.

- System ID
  The system ID is provided by a CPU-D5 board or by a FECU, whereby the later one has the higher priority.
- Storage ID
  The storage ID is given by the unique serial number of the compact flash card.

This encryption makes it impossible to reuse the license file in multiple customer systems.

The base for any feature licensing in Release 14 (or higher) is the availability of the license file. As far as a license file exists the feature level of the system is defined according to it‘s license entries and their values.

Following license entries exists:

- Basic license
- Mobile Extension license
- Unified Messaging License
- CTI license
- Networking
- VoIP Gateway license

Features which have no valid license entry, will be treated as temporary features which are active for
1440 hours = 60 days (timer automatically starts after a coldstart or after a software release upgrade to Release 14 or higher). Temporary features are fully open towards the customer (maximum number of users and highest feature level).

Once the trialtime is expired, the feature level of the system will be limited according to the following criteria’s:

- If there exist valid license entries, the feature level will be limited according to their values.
- If there exist no valid license entries, the feature level of the connected FECU will be used.

Note

In the later case the trialtime can be restarted once by importing at least a valid basic license entry.

In case of new sales, the CPU-D5 always contains a license file with a valid basic license entry. All other features which require an additional license will be treated as temporary features with full feature level. When the trailtime expires before any additional process has taken place, features like Mobile Extension, Unified Messaging, CTI or Networking are still available but they are limited to the level which is defined by the basic license

In case of an upgraded system (formally a FECU based Release 9-13 system), it is necessary to create a license file by using the BMS. This created license file is empty and provides temporary unlimited access to all Release 14 (or higher) features. In order to change the status from temporary features to licensed ones and to remap the existing FECU feature level into the new scheme, the license file has to be registered at the ELC (details see chapter Request a release update license (from Release 9-13 to Release 14 or higher)).

#### To create a license file

The creation of a license file is only necessary if a software upgrade from Release 9-13 to Release 14 or higher has taken place.

Note

When using the CPU-D5 board in a new installed system with Release 14 or higher, it will use the license file which is by default stored on it‘s attached compact flash card.

1. Connect the BMS to the system.
2. Keep the existing FECU plugged to the CPU-D4/CPU-D5.
3. Click on the system in the tree view.
4. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   The BMS detects automatically that there exists no license file in the system and propose all boards which can be used for the creation of a new license file.
5. Select the desired board and click on the ’Submit’ button. The license file will be created and the ASB 150 02 licensing dialog will be displayed.

Note

As there exist no license entry at this stage all features will be treated as temporary. If the trailtime expires before at least a valid license entry will be imported, the system automatically uses the feature level of a connected FECU or if there is no FECU connected to the CPU-D4/CPU-D5, the feature level of a Release 8 system is used. This feature level limitation will also be displayed in the licensing dialog, see below:

#### The ASB 150 02 license dialog

The license of the system is controlled via the ASB 150 02 licensing dialog.

1. Connect the BMS to the system
2. Click on the system in the tree view
3. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.

The example below shows a system which has already some licensed features, a license file

##### License Status

The license status table provides read only information for following values:

- Licensing board
  States the board position which carries the license file
- Remaining trial time
  States the remaining operating hours for all features which have no valid entry in the license file. Licensed features are indicated in the Licensed feature table with a value in the “Release” and “#” column. The counter will be decreased in 5 minutes steps.
- System ID
  States either the serial number of the connected FECU or the serial number the CPU-D5. If a CPU-D5 is installed in the system with a connected FECU, then always the FECU serial number will be used as the system ID.

Note

The FECU serial number contains the dedicated software release as well as the FECU Index. The first digit on the left site describes the software release ( 0=R10, 1=R11, 2=R12, 3=R13). The second digit on the left site decribes the FECU-Index (1=Index 1, 2 =Index 2, ......A=Index10). According to the example above a FECU from R13 Index 10 is used.

- Serial Number of Flash Disk
  States the unique serial number of the storage media on which the license file is stored.

##### Licensed feature table

The table provides an overview of all features which are requiring a license

- Feature Name
  States all the features (feature packages) which require a license entry .
- Release
  States the dedicated system release of the licensed feature (prepared for future purpose).
- #
  States the licensed number of the users or the feature level of the license feature

If a listed feature does not contain an entry in the “Release” and “#” column then this feature is not licensed or does not have a valid entry in the license file. In this specific case the feature is active until the “Remaining trail time” elapses.

Values in the ’Licensed feature’ table:

Feature Name | Value (#) | Description
BASIC_LICENSE | 1 | initial value
MOBILE_EXT_LICENSE | 5 -100 | 5 -100 users (in steps of five)
UNIFIED_MSG_LICENSE | 20 -200 | 20 -200 users (in steps of five)
CTI_LICENSE | 5 | 5 users
80 | 80 users
NETWORKING | 3 | Standard digital networking with unlimited trunk interfaces
4 | Full digital networking with 32 trunk interfaces
5 | Full digital networking with unlimited trunk interfaces
VOIP_GATEWAY | 1 | initial value

Note

The Unified Messaging license entry requires in addition also a CTI license entry.
( £ 20 Unified Messaging users 5 CTI users are required, >20 Unified Messaging users, 80 CTI users are required).

Note

The software VoIP Gateway license requires also the corresponding VoIP Gateway IPU license (see chapter IPU - Software licensing).

Note

The VoIP Gateway license entry disables all other license entries.

##### Buttons

- Export license file
  This button is used to fetch the license file from the board on which it is stored and to export it to a desired destination on the PC or LAN. For further details see chapter To export the license file.
- Import license file
  This button is used to import a license file, which was received from the Ericsson License Center, into the system to replace the existing one. For further details see chapter To import the license file.
- Show license file
  This button is used to view the content of the license file. For further details see chapter Show license file.
- Reload
  This button is used to refresh all indications from the license dialog.

#### Show license file

In order to show the license file of ASB 150 02 click on the “Show license file” button in the ASB 150 02 dialog

##### Description of the license file entries

- ASB150 02 license
  This entry contains following values:

- the board on which the license file is stored
- the board position in the system
- the installed central software at the time of the license file generation
- the firmware revision of the board at the time of the license file generation
- whether the license file was created in the factory (FACT‑Init) or created by the ASB 150 02 itself (OAM‑Init)

- created-storage ID, created-system ID, control-info
  These entries are only relevant for the ELC
- Storage ID
  This entry contains the unique serial number of the compact flash card on which the license file is stored
- System ID
  States either the serial number of the connected FECU or the serial number the CPU-D5. If a CPU-D5 is installed in the system with a connected FECU, then always the FECU serial number will be used as the system ID.
- The remaining entries in the license file are describing the licensed features. These entries contain values about the dedicated system release (prepared for future purpose), the feature level and an encrypted license key. For detailed description about the feature level values see chapter Licensed feature table.

#### To export the license file

1. Click on the ’Export license file’ button in the ASB 150 02 Licensing dialog
   The system ID will automatically be used as the filename for the license file .
2. Click on the filename to download the license file to your desired destination
3. The exported file is then ready for registration purpose on the Ericsson Partner Network.

Note

Before the license file can be registered on Ericsson Partner Network, Unique Pick Numbers have to be available for the desired functions.

Note

The exported license file must not be modified by using any editor.

#### To import the license file

1. Click on the ’Import license file’ button in the ASB 150 02 Licensing dialog.
   The expected filename will be displayed on the screen.
2. Click the on the ’Browse’ button to search for the expected license file.

Note

Although a certain filename is expected the BMS also accepts any other *.ULK filename.

1. Click on ’Transfer Licensing File to ASB’ to import the selected file.
   In the case of a successful import of the license file, the license status for all licensed features will be updated immediately.

Note

Before the BMS imports the new license file, it performs automatically a check whether the system ID and the storage ID matches with the data in the customer system and rejects the request with an error message if the validation fails.

### Request a new license

#### Basic license

By default an ASB 150 02 Release 14 (or higher) system delivery contains a license file with a valid basic license entry on the CPU-D5 which provides the possibility to activate all available basic features in the customer‘s system.

All other licensed features can be used temporarily for 1440 hours = 60 days (timer automatically starts after a coldstart or after a software release upgrade to Release 14 or higher) with their maximum number of users and their highest feature level.

The following picture of the ASB 150 02 Licensing dialog shows that only the ‘BASIC_LICENSE’ is completed in the ’Licensed feature’ table.

#### Color pack

Independent from the order of a color pack, an ASB 150 02 Release 14 (or higher) system delivery always contains a license file with a valid basic license entry on the CPU-D5

In order to get a valid license entry for the ordered color pack, use following procedure:

1. Order the desired color pack(s).
2. After you have received the Unique Pick Number(s) for the placed order, connect the BMS to the system.
3. Due to the fact that all features which need to be licensed are fully open for 1440 hours = 60 days (timer automatically starts after a coldstart or after a software release upgrade to Release 14 or higher), you can configure and activate the desired features in the system.
4. Click on the system in the tree view
5. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
6. Export the license file.
   Detailed description see To export the license file.
7. Build up an Internet connection via the Service PC or the customer PC and login to the Ericsson Partner Network (http:\\enterprise.ericsson.net).
8. Open the Web page of the ELC and follow the offered instructions to create and and download the desired license by using the available Unique Pick Numbers
9. Import the downloaded license file into the system.
   Detailed description see To import the license file.

Note

The received license file must not be modified by using any editor.

Note

Before the BMS imports the new license file, it performs automatically a check whether the system ID and the storage ID matches with the data in the customer system and rejects the request with an error message if the validation fails.

1. Verify whether the new content of the ’Licensed feature’ table matches with the features which have been ordered.

### Request an add on license (additional color pack or plus pack)

1. Connect the BMS to the system.
2. Click on the system in the tree view.
3. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   The Licensed feature table provides an overview of all the licensed features and their feature level.
4. Order the desired feature enhancement (for the article numbers see Licensed features).
5. Verify the ’Remaining trail time’ counter. If the counter has not been elapsed and if it still provides enough operating hours until the final license will imported, you can configure and activate the desired temporary features in the system.
6. After you have received the Unique Pick Number(s) for the placed order, connect the BMS to the system again.

Note

The activation can not be applied for features which have already a licensed number of users or a licensed feature level.

1. Export the license file .
   Detailed description see To export the license file.
2. Build up an Internet connection via the Service PC or the customer PC and login to the Ericsson Partner Network (http:\\enterprise.ericsson.net).
3. Open the Web page of the ELC and follow the offered instructions to create and download the desired license by using the available Unique Pick Numbers
4. Import the downloaded license file into the system. Detailed description see To import the license file.

Note

The received license file must not be modified by using any editor.

Note

Before the BMS imports the new license file, it performs automatically a check whether the system ID and the storage ID matches with the data in the customer system and rejects the request with an error message if the validation fails.

1. Verify whether the new content of the ’Licensed feature’ table matches with the features which have been ordered.
2. If it has not already be done in step 5 you can configure and activate the desired features in the system.

### Request a release update license (from Release 9-13 to Release 14 or higher)

Before a system can be upgraded to the latest Release, please verify the Pre-requisites.

Note

If no FECU is connected to the CPU-D4, the system is running on a Release 8 feature level independent from the installed software. In this specific case the licensing concept can not be applied after the software upgrade to Release 14 or higher, as the system still remains on a Release 8 feature level. In order to use the Release 14 or higher functions, the CPU-D4 has to be replaced by a CPU-D5 or any FECU has to be connected to the CPU-D4 (exception: KDUBS 130 13/11).

#### Mapping of the FECU Index into the license file

When upgrading an ASB 150 02 system from the hardware key based licensing (FECU) to the software key based licensing the existing FECU index (independent from it‘s dedicated Release) will be considered by the ELC and be re-mapped into the license file.

A re-mapping of the existing FECU will be performed by the ELC when ordering one of the following licenses:

- Basic upgrade license - FASBS 102 051/B

- upgrades the FECU feature level to Release 14 (or higher)

- Any color pack of type: Mobile Extension, Unified Messaging, Computer Telephony and Networking

- upgrades the FECU feature level to Release 14 (or higher)
- adds a new feature which requires an additional license

- Any plus pack of type: Mobile Extension, Unified Messaging, Computer Telephony and Networking

- upgrades the FECU feature level to Release 14 (or higher)
- enhances the Networking features defined by the FECU

The table below describes how the different FECU indexes will be remapped when ordering a basic upgrade license

FECU | License File
Index | Description | Feature Name | Value (#)
1 | Basic Functions + Full digital networking with 2 trunk interfaces | BASIC_LICENSE | 1
2 | Standard digital networking with 32 trunk interfaces | BASIC_LICENSE | 1
NETWORKING | 3
3 | Standard digital networking with unlimited trunk interfaces | BASIC_LICENSE | 1
NETWORKING | 3
4 | Full digital networking with 32 trunk interfaces | BASIC_LICENSE | 1
NETWORKING | 4
5 | Full digital networking with unlimited trunk interfaces | BASIC_LICENSE | 1
NETWORKING | 5
6 | CTI + Full digital networking with 4 trunk interfaces *) | BASIC_LICENSE | 1
NETWORKING | 4
CTI_LICENSE | 80
7 | CTI + Standard digital networking with 32 trunk interfaces | BASIC_LICENSE | 1
NETWORKING | 3
CTI_LICENSE | 80
8 | CTI + Standard digital networking with unlimited trunk interfaces | BASIC_LICENSE | 1
NETWORKING | 3
CTI_LICENSE | 80
9 | CTI + Full digital networking with 32 trunk interfaces | BASIC_LICENSE | 1
NETWORKING | 4
CTI_LICENSE | 80
10 | CTI + Full digital networking with unlimited trunk interfaces | BASIC_LICENSE | 1
NETWORKING | 5
CTI_LICENSE | 80
11 | Voice over IP Gateway | BASIC_LICENSE | 1
VOIP_GATEWAY | 1

*) In this specific case the additional full digital networking features for 4 trunk interfaces will be enhanced to 32 trunk interfaces which are defined in the networking orange pack.

The colors in the table shall indicate the equivalent color pack. See also chapter Licensed features.

#### License update procedure

1. Order the Basic upgrade license (FASBS 102 051/B) or any color or plus pack.
2. After you have received the Unique Pick Number for the upgrading process, connect the BMS to the system.
3. Upgrade the system according to the procedures described in chapter Special considerations for the software upgrade.
4. Keep the existing FECU plugged to the CPU-D4/CPU-D5.
5. Click on the system in the tree view.
6. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   The BMS automatically detects that there exists no license file in the system and proposes all boards (CPU‑D5, MFU, IPU or VMU-HD) which can be used for the creation of a new license file.
   Select the desired board and click on the ’Submit’ button. The license file will be created and the ASB 150 02 licensing dialog will be displayed.

Note

When using the CPU-D5 in Release 13 the license file which is by default stored on the compact flash card will be deleted and has to be generated again, when upgrading to a Release 14 (or higher) system software.

1. Verify the entries in the ’Licensed feature’ table
   The table has no entries in the ’Release’ and in the ’#’ column which means that there are no valid entries in the license file.

Note

As the license file does not contain valid entries, the system uses the feature level which is defined by the connected FECU.

1. Export the license file.
   Detailed description see To export the license file.
2. Build up an Internet connection via the Service PC or the customer PC and login to the Ericsson Partner Network (http:\\enterprise.ericsson.net).
3. Open the Web page of the ELC and follow the offered instructions to create and and download the desired license by using the available Unique Pick Numbers
4. Import the downloaded license file into the system.
   Detailed description see To import the license file.

Note

The received license file must not be modified by using any editor.

Note

Before the BMS imports the new license file, it performs automatically a check whether the system ID and the storage ID matches with the data in the customer system and rejects the request with an Error message if the validation fails.

Note

For the first import of a license file with valid license entries (minimum Basic License entry) the trialtime counter will be restarted.

1. Verify whether the new content of the ’Licensed feature table’ matches with the features defined by the connected FECU, see chapter Request a new license.

Note

It is a must that the FECU is always connected to the system as it provides the system ID. The removal of the FECU has the consequence that all licenses will become invalid and the feature level of the system will automatically fall backfall back to Release 8.

### Request a repair license

Following hardware problems are causing the request for repair license:

- Faulty CPU-D5 without a connected FECU
- Faulty CPU-D5 with a connected FECU
- Faulty FECU on a CPU-D4 or CPU-D5
- Faulty license carrier MFU, VMU-HD or IPU
- Faulty Compact Flash Card on the license carrier CPU-D5
- Faulty Compact Flash Card on the license carrier MFU, VMU-HD or IPU

##### Faulty CPU-D5 without a connected FECU

1. Switch off the system
2. Exchange the faulty CPU-D5 but keep the previous Compact Flash Card.
3. Insert the coldstart strap on the CPU-D5
4. Start up the system again.
5. Remove the coldstart strap
6. Connect the BMS to the system
7. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   As the system ID has been changed due to the new hardware, all entries in the ’Licensed feature’ table were removed as they became invalid. As a consequence of the invalid license entries the feature level of the system will automatically fall backfall back to Release 8.
8. Click on ’Show license file’

Note

The hardware change is indicated by adding the entry ’Old system ID’.

1. Export the license file.
   Detailed description see To export the license file.
2. Build up an Internet connection via the Service PC or the customer PC and login to the Ericsson Partner Network (http:\\enterprise.ericsson.net).
3. Open the Web page of the ELC and follow the offered instructions to create a repair license. As the license is always based on the system ID and the storage ID, and one of these components is still the same, the former license file can easily be recovered.
4. Import the downloaded license file into the system.
   Detailed description see To import the license file.

Note

The received license file must not be modified by using any editor.

Note

Before the BMS imports the new license file, it performs automatically a check whether the system ID and the storage ID matches with the data in the customer system and rejects the request with an Error message if the validation fails.

1. Verify whether the new content of the ’Licensed feature’ table matches with the previously installed features.
2. Reload the customer data into the system.

##### Faulty CPU-D5 with a connected FECU

Note

This process does not require any licensing activity towards the ELC, and will only be stated for the sake of completeness.

1. Switch off the system.
2. Exchange the faulty CPU-D5 but keep the previous Compact Flash Card and the FECU.
3. Insert the coldstart strap on the CPU-D5.
4. Start up the system again.
5. Remove the coldstart strap
6. Connect the BMS to the system.
7. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   As the system ID which is given by the FECU is still the same, also all the licensed features are still valid. No further licensing activities are necessary.
8. Reload the customer data into the system.

##### Faulty FECU on a CPU-D4 or CPU-D5

1. Replace the faulty FECU on the CPU-D4 by any other FECU (Release independent, but Index must be the same as faulty FECU).

Note

As the CPU-D5 also provides a system ID, it is not necessary to connect a FECU to the CPU-D5 again.

1. Connect the BMS to the system.
2. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   As the system ID has been changed due to the new or missing FECU, all entries in the ’Licensed feature’ table were removed as they became invalid. As a consequence of the invalid license entries the feature level of the system will automatically fall backfall back to the one given by a connected FECU or to the feature level of Release 8 if there is no FECU connected.
3. Export the license file.
   Detailed description see To export the license file.
4. Build up an Internet connection via the Service PC or the customer PC and login to the Ericsson Partner Network (http:\\enterprise.ericsson.net).
5. Open the Web page of the ELC and follow the offered instructions to create a repair license. As the license is always based on the system ID and the storage ID, and one of these components is still the same, the former license file can easily be recovered.
6. Import the downloaded license file into the system.
   Detailed description see To import the license file.

Note

The received license file must not be modified by using any editor.

Note

Before the BMS imports the new license file, it performs automatically a check whether the system ID and the storage ID matches with the data in the customer system and rejects the request with an Error message if the validation fails.

##### Faulty license carrier MFU, VMU-HD or IPU

Note

This process does not require any licensing activity towards the ELC, and will only be stated for the sake of completeness.

1. Connect the BMS to the system.
2. Shut down the faulty board.
3. Exchange the faulty board but keep the previous Compact Flash Card.
4. Activate the board again.
5. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   As the storage ID of the Compact Flash card is still the same, also all the licensed features are still valid. No further licensing activities are necessary.

Note

When replacing a faulty IPU board, the IPU related licensing process has to be considered as well. See chapter Update of the IPU license because of a faulty IPU board.

##### Faulty Compact Flash Card on the license carrier CPU-D5

1. Switch off the system.
2. Replace the Compact Flash Card on the CPU-D5 by a new one.
3. Switch on the system again.
4. Connect the BMS to the system.
5. Click on the system in the tree view.
6. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   The BMS automatically detects that there exists no license file in the system and propose all boards (CPU‑D5, MFU, IPU or VMU-HD) which can be used for the creation of new license file.
7. Select the CPU-D5 and click on the ’Submit’ button. The license file will be created and the ASB 150 02 licensing dialog will be displayed.

Note

As the license file does not contain valid entries, the feature level of the system will automatically fall backfall back to the one given by a connected FECU or to the feature level of Release 8 if there is no FECU connected.

1. Export the license file.
   Detailed description see To export the license file.
2. Build up an Internet connection via the Service PC or the customer PC and login to the Ericsson Partner Network (http:\\enterprise.ericsson.net).
3. Open the Web page of the ELC and follow the offered instructions to create a repair license. As the license is always based on the system ID and the storage ID, and one of these components is still the same, the former license file can easily be recovered.
4. Import the downloaded license file into the system.
   Detailed description see To import the license file.

Note

The received license file must not be modified by using any editor.

Note

Before the BMS imports the new license file, it performs automatically a check whether the system ID and the storage ID matches with the data in the customer system and rejects the request with an Error message if the validation fails.

1. Verify whether the new content of the ’Licensed feature’ table matches with the previously installed features.

##### Faulty Compact Flash Card on the license carrier MFU, VMU-HD or IPU

1. Connect the BMS to the system.
2. Shut down the board with the faulty Compact Flash Card.
3. Replace the Compact Flash Card by a new one.
4. Activate the board again.
5. Click on the system in the tree view.
6. Click on ’Licensing’ in the system context menu to open the ASB 150 02 licensing dialog.
   The BMS automatically detects that there exists no license file in the system and propose all boards (CPU‑D5, MFU, IPU or VMU-HD) which can be used for the creation of new license file.
7. Select the previous defined board again and click on the ’Submit’ button. The license file will be created and the ASB 150 02 licensing dialog will be displayed.

Note

As the license file does not contain valid entries, the feature level of the system will automatically fall backfall back to the one given by a connected FECU or to the feature level of Release 8 if there is no FECU connected.

1. Export the license file.
   Detailed description see To export the license file.
2. Build up an Internet connection via the Service PC or the customer PC and login to the Ericsson Partner Network (http:\\enterprise.ericsson.net).
3. Open the Web page of the ELC and follow the offered instructions to create a repair license. As the license is always based on the system ID and the storage ID, and one of these components is still the same, the former license file can easily be recovered.

Note

When replacing a faulty Compact Flash Card on the IPU board, the IPU related licensing process has to be considered as well. See chapter Update of the IPU license because of a faulty Compact Flash Card..

1. Import the downloaded license file into the system.
   Detailed description see To import the license file.

Note

The received license file must not be modified by using any editor.

Note

Before the BMS imports the new license file, it performs automatically a check whether the system ID and the storage ID matches with the data in the customer system and rejects the request with an Error message if the validation fails.

1. Verify whether the new content of the ’Licensed feature’ table matches with the previously installed features.

### Error situations

#### Shut down of a license carrier (MFU, VMU-HD or IPU)

The shut down state of a license carrier has no impact on the current license status as long as no re-programming of one of the licensed features will be performed which will cause a reload of the license information. As the license file is not available, the system automatically fetches the feature level from a connected FECU. If no FECU is available the feature level of the system will automatically fall backfall back to the one of Release 8.

Note

When removing a shut down license carrier, please be aware that at this stage any restart of the system will automatically cause a change of the current feature level either to the one of the connected FECU or to the system feature level of Release 8..

#### Multiple license files

During hardware changes it might happen that a board will be inserted which also carries a license file. The system automatically detects the second license file and performs a check which one matches with the system ID . The license file which does not match will be deleted automatically.

Note

If this error condition is detected during a system start-up, further restarts will take place until all unnecessary license file are deleted.

Revision: L © Ericsson Enterprise 2004