
The Shared Blade Server
Issue 2.4 June 2006 37
Note:
Note: DEFINITY migrations cannot use FET to extract existing features. Instead the
GES configurator provides tracking or migration codes that carry forward optional
features and capacities previously purchased to the new system record and
license file. When the account team requests a DEFINITY migration in the GES
configurator, they manually identify and input the existing features. The
configurator produces an output containing both existing features and new
capabilities on a single SAP order.
The Shared Blade Server
The Shared Blade Server (SBS3000) system uses virtual machines plus multiple blades to
allow multiple instances of Communication Manager on one SBS3000 system. RFA contains a
system record for each instance of Communication Manager running on an SBS3000 system.
Each system record is populated based on the specific instance of Communication Manger.
RFA is also used to generate additional licenses over the life of the system to support
maintenance activities such as an IPSI or gateway replacement. Communication Manager
software sets the license mode accordingly at system initialization and checks the license file at
installation and periodically thereafter.
Note:
Note: RFA is not used to for registration to Avaya. You must manually register the
SBS3000 and the associated applications that run on the SBS3000’s virtual
machines.
For Communication Manager, RFA defaults to using CLAN registration to download a license
file. If an alternate PCLAN configuration is used, the changes outlined in Table 12
are required.
Table 12: SBS licensing information
Licensed
Object
FEAT_IP_PNC FEAT_PNS FEAT_
PRETH
LSP
SBS3000:
Communication
Manager in CLAN
mode (default)
Reference
ISPI
Off On Off Off
1 of 2
Comentarios a estos manuales