Unable to to add an IE-9320 as edge node on SDA with Catalyst Center

[Giovanni Vegezzi]

The switch is present in the inventory and has been successfully provisioned. It is also displayed as a white box within the fabric topology.

Despite this, it fails to register as an edge device, with the following error:
"Unable to push configuration to device IP x.x.x.x. Device Response - sgt ^ % Invalid input detected at '^' marker."

Upon investigation, I have determined the specific CLI command causing the configuration deployment failure. When I attempt to manually input the command on the switch, it is not recognized.

The command sequence is:

switch(config)# router lisp
switch(config-router-lisp)# service ipv4
switch(config-lisp-srv-ipv4)# sgt

The 'sgt' command is absent from the available command list.

Has anyone experienced a similar problem or have any suggestions as to why this command is not available?

Catalyst Center version: 2.3.7.7-70047
Switch model: IE-9320-24P4X
Switch software version: 17.15.02 (I tried also with the suggested version 17.12.1 but same result)

Thank you.

[jedolphi]

@Giovanni Vegezzi , please raise a TAC case. I ***belive*** this command is added because Bridge VM / Multiple IP to MAC has been enabled on one of the VLANs, remove Bridge VM / Multiple IP to MAC from all VLANs and try again. Long term we need to support multiple IP to MAC in IE9300 Fabric Edge Node, there is an a bug to get this capabilitiy added to IE9300 Edge Node and there is a workaround for the short term, please raise TAC case.

[Giovanni Vegezzi]

Thank you jedolphi, for your respose.

Unfortunately this is not the issue, as I've never activated that feature on any VLAN. Therefore, the Bridge VM / Multiple IP to MAC feature is not the cause.

thank you

[jedolphi]

I beg your pardon Giovanni, you're absolutely right! I searched some TAC cases. Someone else had same problem because switch license level was not set to network advantage + dna advantage.

[Giovanni Vegezzi]

This is a good point, i will investigate on license and let you know.

thank you

[x00008037]

i have the same issue. i have raise a tac case. cannot provision this device as a fabric edge 

[Giovanni Vegezzi]

Finally, I managed to add the device as an Edge node.

As jedolphi suggested, the issue was related to the license level. The license level was not set to 'network advantage + DNA advantage', which is why Catalyst Center failed to deploy the device as an Edge node due to the missing command.

After manually setting the license level to 'network advantage + DNA advantage' (switch(config)#license boot level network-advantage add-on dna-advantage), Catalyst Center was able to deploy the configuration.

The strange thing is that CC failed to automatically set the license level on the switch.

Anyway, it's working for me now.

Thank you.