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.
Werner Gerke (talk | contribs) (→Known Issue) |
Werner Gerke (talk | contribs) (→Documentation¶) |
||
| Line 75: | Line 75: | ||
*'''User manual for the EKB configuration tool''' | *'''User manual for the EKB configuration tool''' | ||
| − | [[Media:Manual_HiPath_4000_de.pdf]] | + | ''' '''[[Media:Manual_HiPath_4000_de.pdf]] |
<br> | <br> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | *'''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. | ||
| | ||
| Line 93: | Line 92: | ||
*'''Partial REGEN''' | *'''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.example [[Media:Teilreg_Beispiel.pdf]] | |
| − | |||
| − | example [[Media:Teilreg_Beispiel.pdf]] | ||
| − | |||
| − | |||
| − | |||
| + | *'''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. | ||
example [[Media:KONDA-Beispiel.jpg]] | example [[Media:KONDA-Beispiel.jpg]] | ||
Revision as of 09:33, 28 July 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.
Global Information¶
Releases:
Last delivery: Revision Package 31.1
Relase Date: 6.6.2011
- EKB Versionen
devices.ekb Version 31202
hip4000.ekb Version 31203
hip4000.sdb Version 31203
hip4000c.ekb Version 31203
hip4000c.sdb Version 31203
hp3kim8.ekb Version 31200
hp3kvd.ekb Version 31200
hpxpr.ekb Version 31012
kondah4.ekb Version 31002
oso3.ekb Version 31201
osvoice4.ekb Version 31200
osvoice5.ekb Version 31204
- Quicksale Modelizer
Version 31205
Releasedocumentation
Known Issue
ECS Errormessage: "No AMO UCSU......"
Possibly the wrong Partial regen was used. Correct control file can be found at SIRA's home page
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.
Workaround's
aktuell keine
Schedule for Delta Packages'''¶
Documentation¶
- Overview of products with configurator within the sales tools
- Media:Overview_EKB_products_Sales_Tools_06.07.2011.pdf
- User manual for the EKB configuration tool
Media:Manual_HiPath_4000_de.pdf
- 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.example Media:Teilreg_Beispiel.pdf
- 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. example Media:KONDA-Beispiel.jpg
- KONDA oder Teilregen
In der IBASE können KONDA Daten oder Teilregendaten hinterlegt sein je nachdem welche Instanz zuletzt aktualisiert hat.
Prinziepdarstellung Media:IBASE-Characteristics.pdf
- Was steht in der IBASE?
Die IBASE enthält 3 Datenblöcke je gespeichertes System.
- Kundendaten
- Leistungsmerkmaldaten
- Hardwaredaten d.h. KONDA oder Teilregen.
Bei jeder Erweiterung werden die Daten als kompletter Datensatz abgespeichert. Der Vorgängerdatensatz bleibt erhalten und wird als Historie abgelegt. Ein Datensatz aus der Historie kann jederzeit wieder aktiviert werden.
Upload Partial REGEN to IBASE
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
Media:User_Information_QuickSales_Order_Type.pdf
User Manual HiPath4000 Manager
Media:User_Manual_HiPath_Manager_Upgrade.pdf
How to Resolve Inventory Data Problems in Hipath 4000 Systems
Media:User Manual_HIP4000_Inventory_Data_Repair_EXT_V1.pdf
Required Information when Opening a Trouble Ticket
Media:Required_Info_for_QS-Trouble_Tickets.pdf
Salestool for IM
Quicksales
Product Structure ( QSBW Systeme)
Media:Systems-Structure--Delta-31-2.pdf
Products with EKB
HiPath 4000
HiPath 4000 Manager V5
OpenScape Xpressions V6
'Upload Partial REGEN via ConfigService
Media:Config_Service_Manual.pdf
'How to handle systems in LMT?
Prozess
HiPath4000 Erweiterung
Schematische Darstellung
Media:Erweiterungsprozess.pdf
Important Links
TI Online -- Technische Informationen
ti-online.global-intra.net/
