Difference between revisions of "FAQ Configurator and Modelizer"
The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.
|Line 183:||Line 183:|
''''How to handle systems in LMT?'''
''''How to handle systems in LMT?'''
== <br>'''''' ==
Revision as of 08:58, 11 August 2011
Master Data Configurator and Modelizer
This Wiki provides explainations and answers for ECS and Quicksales Modelizer related topics. As a sales engineer you might be interested in this subject.
Last delivery: Delta Package 32
Relase Date: 1.8.2011
- 'EKB Version
devices.ekb Version 32002
hip4000.ekb Version 32008
hip4000.sdb Version 32008
hip4000c.ekb Version 32008
hip4000c.sdb Version 32008
hpxpr.ekb Version 32006
kondah4.ekb Version 32007
osoV3.ekb Version 31202
osvoice4.ekb Version 32001
osvoice5.ekb Version 32002
HPDAKS3.ekb Version 32000
- Quicksale Modelizer
ECS Errormessage: "No AMO UCSU......"
Possibly the wrong Partial regen was used.
Correct Partial regen control file can be accessed via your channel manager from our internal SIRA homepage.
ECS Errormessage: "Missing Shelf at KOORD......"
Please generate and upload new Partial Regen File
ECS Errormessage: "Shelf ........... not distributed"
Planing Note AYP800 HiPath 4000 Installation Variant is missing in IBASE ?
ECS Errormessage: "Set!Subsystem Failed............Fehlerursache:
Error in configuration data of IPDA or SoftGate location. Wrong value entered for STANDOID parameter of UCSU AMO.
STANDOID parameter: German acronym! This parameter identifies the location in the configuration tool. Service engineers must not change this parameter to any other value than that defined and required by the configuration tool! See also HiPath 4000 V5 Service Manual, Volume 1 – AMO Descriptions, Service Documentation.
- At the moment none necessarily
Schedule for Delta Packages
- Overview of products with configurator within the sales tools
- User manual for the EKB configuration tool
- HiPath4000 Expansion Orders
Expansion orders of HiPath4000 systems using the IBASE data. The tool support for HiPath4000 expansion orders is based on the "as-is" data of the customer system concerned, i.e., the actual hardware (and software) configuration at the time of the order. The necessary hardware information is obtained from the system in the form of a "partial REGEN" batch file, which contains AMO commands for "regenerating" the relevant system hardware configuration (line cards, shelves, locations, etc.). This data is stored in IBASE under the appropriate system number, in addition to the feature numbers (L-numbers) and quantities ordered in previous tool sessions. In the case of new orders, the information is provided by the original KONDA (CONDA) generating batch file, which reflects the "as-is" configuration status of the system only until the first partial REGEN file can be generated. The partial REGEN batch file is generated in the HiPath system concerned with the aid of a special Service procedure, and automatically stored in the IBASE inventory data. Please refer to the relevant Service page for details. A newer partial REGEN file obtained from a customer system and loaded in the tool for a system expansion order can also be transferred to IBASE using the "Configuration Service" function of the tool. See also below.
- Partial REGEN
A "partial REGEN" is an AMO batch file that contains configuration data similar to the KONDA/CONDA (see below), but obtained as output from a HiPath system in response to a REGEN AMO call-up. The AMO commands reflect the "as-is" hardware configuration status of the system concerned, i.e., information on line cards, shelves, locations, etc. The name "partial REGEN" is derived from the fact that the file is required to contain only a limited subset of the total AMO information available in a HiPath system.
- KONDA/CONDA = Configuration Data
The CONDA file (KONDA is the German acronym) contains an AMO command batch for generating the hardware and software configuration data in the HiPath system (e.g., boxes, shelf types, line cards, system software, etc.). The CONDA file is generated in the configuration tool when a system is first ordered, and also later as a result of each subsequent system expansion order. The information is stored in IBASE and can also be downloaded from DIAMOS by Service engineers. The CONDA file reflects the "as-sold" status of a system.
- KONDA/CONDA or partial REGEN
The IBASE data of a HiPath 4000 system will always contain CONDA files ("as-sold" information) and, once this information has first been generated and stored, partial REGEN files ("as-is" information) . For the purposes of the configuration tool, the hardware information contained in the newest file is always definitive.
- What information is stored in the IBASE?
For each HiPath system number stored, the IBASE data contains three (3) distinct data blocks with relevant inventory information.
- Customer data - Feature data (ordered L-numbers and quantities) - Hardware configuration data, as defined in the CONDA ("as-sold" information) or partial REGEN ("as-is" information).
After each expansion order, the IBASE content for the system concerned is updated and stored in full. The previous IBASE records remain unchanged and available in the archive. Archived data records can be restored (re-activated) at any time, if required.
- Upload Partial REGEN to IBASE
For direct Sales
please see SIRA-Hompage
Upload Partial REGEN via ConfigService CS Manual Media:Config_Service_Manual.pdf
IBASE Content Beispiel Media:IBASE-Inhalt-ext.pdf
How To Documents¶
Send Order from Quicksales
User Manual HiPath4000 Manager
How to Resolve Inventory Data Problems in Hipath 4000 Systems
Required Information when Opening a Trouble Ticket
Salestool for IM
Product Structure ( QSBW Systeme)
Products with EKB
HiPath 4000 Manager V5
OpenScape Xpressions V6
'Upload Partial REGEN via ConfigService
'How to handle systems in LMT?
TI Online -- Technische Informationen