Advertisement
Chapter
7
7.3.2 Configuring CCO on the OXO Connect
7.3.2.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 CCO services.
In case of BTCO, this is done at industrialization/integration.
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.
7.3.2.2 Enabling/Disabling CCO on the OXO Connect
To Enable/disable CCO:
•
In the OMC:
1. Select Cloud > Cloud Connect
2. Check/uncheck the box: Cloud Connect enabled
•
In the MMC (administrator session):
1. Go to System > cConnect
2. Press Choice to enable/disable Cloud Connect
After enabling CCO, the OXO Connect connects to the CCI. In case of connection failure, the OXO
Connect periodically retries:
•
Every five minutes during the first two hours
•
After the first two hours, the delay is doubled after each attempt, but cannot exceed twelve 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.
7.3.3 Maintenance
7.3.3.1 Replacing a CPU
To replace a CPU:
1. Perform rehosting on eLP
2. Replace the CPU and restore the configuration
The CPU connects to the CCI if enabled in configuration, and makes a new FTR.
7.3.3.2 Swapping a CPU with the same type of hardware
CPU swap with the same hardware is necessary in case of wrong association between hardware and
order in eLP. The CPU installed at customer 1 is associated with 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 CPUs are associated to the correct order. Both CPUs make a new FTR.
8AL91217USAA - Ed. 01 - July 2018 - Installation Manual
Configuring services
92/216
Advertisement
