How to convert server types in DCImanager
This article describes how you can inventory servers in DCImanager, and convert server types. New mechanism is available in version 5.38 and later.
DCImanager now supports a new mechanism that you can use to keep track of server types (their configuration). We haven't changed the old mechanism of server types yet, (integration with BILLmanager, etc. have not been changed), but we will do so in future releases.
With the new mechanism, a server type is created for each server by changing the corresponding fields in the server edit form. A new type name suitable for BILLmanager is generated automatically. You won't need to create an additional type after the server configuration has been changed. The new mechanism allows to add new data (HDD, CPU, etc.) into the server configuration form when running diagnostics. Once completed, a new Chassis name will be generated for the server.
Call the following functions under the procedure described below to successfully convert your server types.
Add devices that will be available in the "Equipment" module.
/usr/local/mgr5/sbin/mgrctl -m dcimgr internal.create.equipmenttype su=admin
su is a username with admin permissions. This function will create hard disks and processors based on data from the database (data from the tables cpulist, hddlist, which are added during diagnosis).
This function will get information from every server and generate server types based on data from the database (received during diagnostics).
/usr/local/mgr5/sbin/mgrctl -m dcimgr internal.assign.equipment su=admin
Attention! Function execution may take some time (5-15 minutes), because multiple SELECT and UPDATE requests will be made in the database.
Once completed, the corresponding fields in the server edit form will be filled out (amount of RAM, HDD, CPU). A name for the new type will be generated. You can find it in the server edit form and in the Chassis column in the list of servers.
The following function is optional, but sometimes it can be useful, for example if you have many servers with a certain type specified, but the database doesn't contain any information about them, as diagnostics was not run.
/usr/local/mgr5/sbin/mgrctl -m dcimgr internal.assign.equipment.fromsrvtype su=admin
Attention! We strongly recommend that you call the function only after internal.assign.equipment. In internal.assign.equipment information is collected from all servers regardless whether they have Chassis specified or not. Thus, you first call internal.assign.equipment.fromsrvtype, then - internal.assign.equipment, and the Chassis for all the servers that were assigned by internal.assign.equipment.fromsrvtype will be overwritten when calling internal.assign.equipment. However, internal.assign.equipment.fromsrvtype is trying to specify Chassis only for those servers that have empty or NULL Chassis ( (the field gen_chassis_name in the database). So, you first need to call internal.assign.equipment, once completed, a number of servers without Chassis will be available (they will have the empty field gen_chassis_name). Call internal.assign.equipment.fromsrvtype that will manage the rest of the servers.
The function will try to convert the server type based on a server name from the previous mechanism, rather than on data in the database
If in the Server types module "DHX-2.4-32G-A5405B-4x600SAS" already exists and is associated with certain servers, this type will be converted as follows:
- DHX-2.4 processor will be created in CPU.
- HDD SAS named will be created in Hard disks.
- RAID-controller A5405B will be created in PCI devices.
- Processor, 4 hard disks, and RAID controller mentioned above will be added into the server edit form. RAM amount - 32Gb.
- A new type name will be generated for servers (Chassis in the Server list): DHX-2.4-32G-4x600SAS-A5405B
The function can convert types in the following format:
A2D-1.6-2G-1x250SATA C2Q-2.4-8G-ASR3405-4x150SAS DHX-2.4-32G-A5405B-4x600SAS E3-1240v1-16G-2x2000SATA QX-2.53-8-2x500SATA
Attention! Types such as E5-2620-32GB-2x2TB(size in TB), QX-3.4-16G-2x2000SATA+1x250SSD (the "+" symbol) or QX-3.4-16G-2x2000SATA-1x250SSD (only one entry per hard disk) won't be converted. For successful conversion the "-" symbol should be used for elements (CPU, HDD, RAM). At the end of every HDD specify its type (SATA, SAS).
We can not identify you and respond to your message.