search cancel

Modeling Gateway fails to destroy a device in Spectrum

book

Article ID: 255023

calendar_today

Updated On:

Products

DX NetOps

Issue/Introduction

Below is the debug output in relation to destroy a model. This import is not successful, and I would like to know the reason why and how to solve this.

 


<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE Import SYSTEM ".modelinggateway.dtd">
<Import>
    <Destroy>
        <Device ip_dnsname="10.156.40.66" />
    </Destroy>
</Import>

 

 

Modeling Gateway import started.  Mon, Oct 17, 2022, at 09:23:11 AM CEST

Parsing import file test_destroy.xml
Start importing file test_destroy.xml
Identifying device ports...
Destroying 1 models...
Number of errors in Destroy section: 1
Number of total errors:           1
Modeling Gateway import failed.  Mon, Oct 17, 2022, at 09:23:12 AM CEST

Debug option was selected.  Debug file is test_destroy.xml.debug.
#####################################################

 

...

Sending action to identify 1 devices
Invoking FIND_DEV_MODELS_PER_IP action 
Found 1 existing model for 10.156.40.66.  Byte array length = 8
Model 10.156.40.66 has current mh: 340ee, prevMH = ffffffff
Failed to retrieve device model 10.156.40.66's activation info.
Checking device model's contact and interface modeling status...
Failed to get device 10.156.40.66 contact status.  Error: PARTIAL_FAILURE  20221017.09.23.12
Device 10.156.40.66 exists but not active.
 TImport.identifyDevices() ending
TImport.identifyPorts() starting
identifyDevPorts( dev = 10.156.40.66 ) starting
Device has no ports to identify.
TImport.identifyPorts() ending
Destroying model 10.156.40.66
Failed to destroy model 10.156.40.66: PARTIAL_FAILURE  20221017.09.23.12

Environment

Release : 21.2.x / 22.x

Cause

The model that was selected to be destroyed was using an invalid (legacy model handle) instead of an expected (huge model handle)

Resolution

The reason is wrong use of landscape mask in modeling gateway. Actually in 0xFFFFFFFF model handle, first two hex digits are used for landscape handle another rest 6 HEX digits are used to identify model handle. But in Modeling gateway first three hex digits are used to identify landscape handle and rest 5 digits are used to identify model handle. This works fine for legacy landscapes where we support less number of models but it don't work correctly for huge landscapes.
 
 
This issue is identified and fixed in 22.2.3 through user story US819150. Hence in future once customer upgrades to latest release, this problem will not occur.

 

As a temporary workaround an export and reimport of this device model will work and allow for Modeling Gateway destroy as an export and import will fix the faulty model handle.