BusinessPhone Communication Platform 4.0
Dialogs

## Maintenance

To use the maintenance parts of the BMS, the user must have the Access right “Maintenance”.

If the user has not the correct rights to access the maintenance parts, the following message is shown to the user:

This dialog shows:

#### Maintenance

Restart System: | Restart the BusinessPhone system.

#### Logs

Last cleared | Shows the date when the logs was cleared.
Clear Logs | Clears all warning logs and all total counters.
Clear Sum Counters | Clears the alarm total and error total counter.
Clear Trace Logs | Clear all trace logs.
Restore OM-Data | RESTORE OM-DATA is a simulated restart of all maintenance functions. All programmable maintenance data (warningcode definitions etc.) will be set to their default values. All logs etc. are cleared.
Call Log Reset | Resets the Call Log Buffer.
BBRAM Initialization | BBRAM Initialization Initializes certain parts of the BBRAM area, used by the OM-block, in order to provide a save path for upgrades of the central software. This function should be called before EVERY upgrade procedure. Check that you get ”BBRAM Initialization performed!”

#### Connect History

’Connect History’ displays a short history of connect and backup events.

The data was read immediately after the connection to the system was established. In OFFLINE-mode the data is read from the current data file.

The 'Previous connect by' field is the system identity plus the USERNAME.

A 'connect' is logged for each established connection.

A 'backup' is logged each time a complete configuration data file is saved in ONLINE mode.

#### Resources

System Resources | Shows the free PCM channels, the free timers and the free memory segments.
Voice Memory | Shows the cards with information about the voice memory storage capacities.
EEPROM Resources | Shows the size and the usage of the EEPROM resources.

##### Some explanations about BBRAM:

The BBRAM (Battery backed-up RAM) area is split in 2 parts, which are supported by the E2‑Interface (traditional area, former EEPROM) and the OS.BATT‑Interface (exists since R9).

The boarder between E2 and OS.BATT is defined per release and used features. With a new release usually the OS.BATT area grows and the E2 area shrinks (assuming that the same number of BBRAM are mounted).

But it is not always the case, that just the need of the OS.BATT area is increased, sometimes data from E2 area are moved to the OS.BATT area, e.g the CIL records since R14.

##### Some explanations about EEPROM Resources:

- EEPROM size shows the available E2 area. If Bytes for records (free) goes down to 0, then additional EEPROM (included in BBRAM component) must be mounted
- E2 records are split up in:

- Base records
- Linked records

- Base records in RAM - shows the usage of Base records in RAM
- The Flags show the mounted E2 area:
  each zero or one marks a 8KB block (Map). The uppermost line has no meaning for BBRAM. From the second line onwards there are the BBRAM Maps, each ’1’ marks an E2 Map.

Example:

|  |  |  | Map | area | BBRAM chip | remark
00000000 | 00000000 | 00000000 | 00000000 | 0 - 31 | no BBRAM area |  | zeros
00000000 | 00000000 | 00000000 | 00000000 | 32 - 63 | OS.BATT / E2 | 1 - lower half | OS.BATT
11111111 | 11111111 | 11111111 | 11111111 | 64 - 95 | OS.BATT / E2 | 1 - upper half | E2
00000000 | 00000000 | 00000000 | 00000000 | 96 - 127 | OS.BATT / E2 | 2 - lower half | not mounted
00000000 | 00000000 | 00000000 | 00000000 | 128 - 159 | OS.BATT / E2 | 2 - upper half | not mounted

See also System Description (1551-ASB 150 02 Uen).

Action

Repair |  | Repairs faulty E2 blocks |

Revision: A © Ericsson Enterprise 2003