Description

This article explains how to save a template if it fails with "save failure: invalid CLI" for the below configurations in the Junos Space Network Management Platform.

The error is seen to occur when the template is saved from the Device Template > Templates > Create Quick Template > CLI-based Template Editor location. 

set event-options policy pri-vpn-down attributes-match kmd_vpn_down_alarm_user.interface-name matches st0.2
set event-options policy sec-vpn-down attributes-match kmd_vpn_down_alarm_user.interface-name matches st0.3
set event-options policy pri-vpn-up attributes-match kmd_vpn_up_alarm_user.interface-name matches st0.2
set event-options policy sec-vpn-up attributes-match kmd_vpn_up_alarm_user.interface-name matches st0.3

Note: This issue is seen on SRX devices running Junos OS release 15.1x and earlier.

 

Symptoms

While saving a template in Junos Space Network Management Platform, the action fails with the error message "save failure: invalid CLI error".

The following error is seen in server.log : 

[root@host ~]# grep -i "invalid key" /var/log/jboss/servers/server1/server.log
2020-12-20 14:41:05,588 ERROR [net.juniper.jmp.apps.datastorage.data.CliToXmlTransformer] (ajp-space-0050569e2471/10.85.187.43:8009-11) invalid key: kmd_vpn_down_alarm_user.interface-name
2020-12-20 14:41:05,619 ERROR [net.juniper.jmp.apps.datastorage.data.CliToXmlTransformer] (ajp-space-0050569e2471/10.85.187.43:8009-11) invalid key: kmd_vpn_down_alarm_user.interface-name
2020-12-20 14:41:05,619 ERROR [net.juniper.jmp.apps.datastorage.data.CliToXmlTransformer] (ajp-space-0050569e2471/10.85.187.43:8009-11) invalid key: kmd_vpn_up_alarm_user.interface-name
2020-12-20 14:41:05,620 ERROR [net.juniper.jmp.apps.datastorage.data.CliToXmlTransformer] (ajp-space-0050569e2471/10.85.187.43:8009-11) invalid key: kmd_vpn_up_alarm_user.interface-name

alt

 

Solution

This issue is due to a bug in schema version 15.1x and earlier.

 

To resolve the issue, update the schema version to 17.3R1.10 with the junos-es device family selected. Use the following screenshot as a guide to change the version.

For steps to update the schema, refer to KB21796 - [Junos Space] Example - How to update the DMI schema [juniper.net] .

alt

  • The following screenshot will help you to select the proper device family:

alt