Registration Of The Product; Configuring Cco On Oxo Connect; Maintenance - Alcatel-Lucent OXO Connect Series Installation Manual

Table of Contents

Advertisement

Chapter
3

3.3.2 Registration of the product

3.3.3 Configuring CCO on OXO Connect

3.3.3.1 Associating the order with the CPUID
The association between the order identified by the CC-Suite-ID and the Hardware ID of the CPU is
mandatory to use the CCO services.
In case of BTCO, this is done at industrialization/integration step.
In case of non BTCO, before product installation:
1. Connect to eLP
2. Select an order
3. Associate the Hardware-ID of a CPU to the CC-Suite-ID
This creates the requested accounts to connect to the CCI.
3.3.3.2 Enabling/Disabling CCO on OXO Connect
To Enable/disable CCO:
By OMC:
1. Select Cloud > Cloud Connect
2. Check/uncheck the box: Cloud Connect enabled
By MMC (administrator session):
1. Go to System > cConnect
2. Press Choice to enable/disable Cloud Connect
After enabling CCO, OXO Connect connects to the CCI. In case of connection failure, the OXO
Connect periodically retries:
Every 5 minutes during the first two hours
After the first two hours, the delay is doubled after each attempt, but cannot exceed 12 hours
At any time, it is possible to trigger a connection attempt by disabling and re-enabling CCO. This resets
the delay between two attempts in case of connection failure.

3.3.4 Maintenance

3.3.4.1 Replacing a CPU
To replace a CPU:
1. Perform rehosting on eLP. The Activation Account of the new CPU has to be activated in the CCI
2. Replace the CPU and restore the configuration
The CPU connects to the CCI if enabled in the configuration, and makes a new FTR.
3.3.4.2 CPU swap with same hardware
CPU swap with same hardware is necessary in case of wrong association between hardware and
order in eLP. The CPU installed at customer 1 is associated with the customer 2 order and vice versa.
The CPUs have retrieved the wrong licenses (CPU at customer 1 has licenses for customer 2 and CPU
at customer 2 has licenses for customer 1).
To solve the problem: swap the CPUs in eLP. The Activation Accounts of the both CPUs must be
activated in the CCI.
The CPUs are associated to the correct order. Both CPUs make a new FTR.
3EH21123USAA - Ed. 01 - April 2017 - Installation Manual
System Services
36/207

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents

Save PDF