Unable to remove unused port templates (Not Default) In site engine

[Brent_Addis]

Howdy,

In Site Engine, We have around 30 port templates we were going to use in a rollout for a customer we have decided not to use, vouching for NAC based port config instead. They were originally tagged against L2 service objects, however these objects have long since been removed.

Attempting to remove the old port templates complains they are in use by a service application, and lists a non existent service ID. Is there a workaround for this?

Thanks,

[Robert_Haynes · Accepted solution]

I would suggest opening a case with GTAC support to investigate this further. If you do, please provide a show support ZIP and if possible a config-only backup of your Site Engine system.

[Brent_Addis]

Yeah that's what I thought I would need to do, just wondered if there was a quick fix.

Thanks for the reply!

[Brent_Addis]

Thought I would report back to say this is resolved in case anyone else has a similar issue!

---------------------------------------------------

I’ve received feedback from the escalation team, and here's what they found:

They were able to observe numerous dependencies on the port templates primarily linked to Service Application L2VSNs on the test system where your backup has been uploaded.

To view these dependencies, you can navigate to:
Administration > Diagnostics (Advanced) > System > Site Details

In the “Port Template Usage Details” section, you’ll find entries similar to the following:

ID: 100004, Name: Service-Name
  SvcKeys       : [SiteName/Services/13000080.SWITCHED.80.CONFIG]

ID: 100005, Name: Service-Name
  SvcKeys       : [SiteName/Services/13000080.SWITCHED.4096.CONFIG]

ID: 100006, Name: Service-Name
  SvcKeys       : [SiteName/Services/13001100.SWITCHED.4096.CONFIG]

ID: 100007, Name: Service-Name
  SvcKeys       : [SiteName/Services/13001100.SWITCHED.1100.CONFIG]

Could you please confirm whether the same dependencies appear on your production XIQ-SE server?

To address this, go to:
Administration > Diagnostics (Advanced) > System > Site Details
Then click “Reset” followed by “Refresh”

This action will clear and rebuild the port template usage cache.

----------------------------------------------

After performing this all the “orphaned” references were cleared, and the system returned to normal.