CA Spectrum Modeling gateway import problems
Article ID: 126297
Updated On:
Products
CA Spectrum
Issue/Introduction
Issue:
When importing an xml into modeling gateway, there were errors:
Modeling Gateway import exception:
java.lang.Throwable: Unknown attribute identifier_name in model element com.aprisma.tie.parse.C
ontainerElement: null:null
at com.aprisma.tie.TopologyIEModel.addAttrVal(TopologyIEModel.java:119)
at com.aprisma.tie.parse.ModelElement.setAttr(ModelElement.java:241)
at com.aprisma.tie.parse.ContainerElement.parseAttrs(ContainerElement.java:174)
at com.aprisma.tie.parse.ContainerElement.parse(ContainerElement.java:473)
at com.aprisma.tie.parse.ContainerElement.<init>(ContainerElement.java:73)
at com.aprisma.tie.parse.DiscoveryElement.parse(DiscoveryElement.java:160)
at com.aprisma.tie.parse.DiscoveryElement.<init>(DiscoveryElement.java:43)
at com.aprisma.tie.parse.ModuleElement.parseChildren(ModuleElement.java:322)
at com.aprisma.tie.parse.ModuleElement.parseModule(ModuleElement.java:227)
at com.aprisma.tie.parse.FileElement.parse(FileElement.java:671)
at com.aprisma.tie.parse.FileElement.parseXmlFile(FileElement.java:375)
at com.aprisma.tie.parse.FileElement.<init>(FileElement.java:118)
at com.aprisma.tie.imprt.MgImportMain.startImport(MgImportMain.java:89)
at com.aprisma.tie.ModelingGateway.performAction(ModelingGateway.java:305)
at com.aprisma.tie.ModelingGatewayMain.main(ModelingGatewayMain.java:155)
Root Cause:
------------------
The export file had "null" device attributes
<Device name="null" model_type="null" model_handle="0x101f112" />
<Device name="null" model_type="null" model_handle="0x101f113" />
<Device name="null" model_type="null" model_handle="0x101f114" />
Issue:
Global Collections were not created even though the output showed the creation:
Model GlobalCollection:ADMIN_CAPM Palmetto General - PGH is in remote landscape with model ID 11154d3
Model GlobalCollection:ADMIN_CAPM Palmetto General - PGH has current mh: 11154d3, prevMH = 11154d3
GC GlobalCollection:ADMIN_CAPM Palmetto General - PGH exists in DSS with MH 11154d3
Found model GlobalCollection:ADMIN_CAPM Palmetto General - PGH with handle 11154d3
Try to find staticGlobalCollects GC GlobalCollection:ADMIN_CAPM Palmetto General - PGH
GlobalCollection:ADMIN_CAPM Palmetto General - PGH has no staticGlobalCollects contents.
GlobalCollectionImporter.topologyLayout( GlobalCollection:ADMIN_CAPM Palmetto General - PGH ) starting
Root Cause:
------------------
Modeling Gateway export/import is not supporting Huge landscape Handle
Issue:
Device models are created even though the following modeling gateway options were used:
do_not_process_pre_existing_devices_under_container_node = "true"
export_devices = "false"
Root Cause:
------------------
This is happening because the device model only has a relation with the Global Collection and not the Topology. This happens when a model is "removed" from the Topology when it should be "deleted" from the Topology.
If the devices in the GC do not have a relation with the Topology they will be exported by modeling gateway.
When importing an xml into modeling gateway, there were errors:
Modeling Gateway import exception:
java.lang.Throwable: Unknown attribute identifier_name in model element com.aprisma.tie.parse.C
ontainerElement: null:null
at com.aprisma.tie.TopologyIEModel.addAttrVal(TopologyIEModel.java:119)
at com.aprisma.tie.parse.ModelElement.setAttr(ModelElement.java:241)
at com.aprisma.tie.parse.ContainerElement.parseAttrs(ContainerElement.java:174)
at com.aprisma.tie.parse.ContainerElement.parse(ContainerElement.java:473)
at com.aprisma.tie.parse.ContainerElement.<init>(ContainerElement.java:73)
at com.aprisma.tie.parse.DiscoveryElement.parse(DiscoveryElement.java:160)
at com.aprisma.tie.parse.DiscoveryElement.<init>(DiscoveryElement.java:43)
at com.aprisma.tie.parse.ModuleElement.parseChildren(ModuleElement.java:322)
at com.aprisma.tie.parse.ModuleElement.parseModule(ModuleElement.java:227)
at com.aprisma.tie.parse.FileElement.parse(FileElement.java:671)
at com.aprisma.tie.parse.FileElement.parseXmlFile(FileElement.java:375)
at com.aprisma.tie.parse.FileElement.<init>(FileElement.java:118)
at com.aprisma.tie.imprt.MgImportMain.startImport(MgImportMain.java:89)
at com.aprisma.tie.ModelingGateway.performAction(ModelingGateway.java:305)
at com.aprisma.tie.ModelingGatewayMain.main(ModelingGatewayMain.java:155)
Root Cause:
------------------
The export file had "null" device attributes
<Device name="null" model_type="null" model_handle="0x101f112" />
<Device name="null" model_type="null" model_handle="0x101f113" />
<Device name="null" model_type="null" model_handle="0x101f114" />
Issue:
Global Collections were not created even though the output showed the creation:
Model GlobalCollection:ADMIN_CAPM Palmetto General - PGH is in remote landscape with model ID 11154d3
Model GlobalCollection:ADMIN_CAPM Palmetto General - PGH has current mh: 11154d3, prevMH = 11154d3
GC GlobalCollection:ADMIN_CAPM Palmetto General - PGH exists in DSS with MH 11154d3
Found model GlobalCollection:ADMIN_CAPM Palmetto General - PGH with handle 11154d3
Try to find staticGlobalCollects GC GlobalCollection:ADMIN_CAPM Palmetto General - PGH
GlobalCollection:ADMIN_CAPM Palmetto General - PGH has no staticGlobalCollects contents.
GlobalCollectionImporter.topologyLayout( GlobalCollection:ADMIN_CAPM Palmetto General - PGH ) starting
Root Cause:
------------------
Modeling Gateway export/import is not supporting Huge landscape Handle
Issue:
Device models are created even though the following modeling gateway options were used:
do_not_process_pre_existing_devices_under_container_node = "true"
export_devices = "false"
Root Cause:
------------------
This is happening because the device model only has a relation with the Global Collection and not the Topology. This happens when a model is "removed" from the Topology when it should be "deleted" from the Topology.
If the devices in the GC do not have a relation with the Topology they will be exported by modeling gateway.
Environment
Release:
Component: SPCCSS
Component: SPCCSS
Resolution
This is tentatively scheduled to be fixed in future release CA Spectrum 10.3.2.
As a temporary workaround, the import xml file can be edited to remove the null entries for names, the "model_handle" entries in the Global Collections, and if needed, manually delete the device models that are created.
As a temporary workaround, the import xml file can be edited to remove the null entries for names, the "model_handle" entries in the Global Collections, and if needed, manually delete the device models that are created.
Feedback
Powered by
