Symptom

Custom applications created on vManage are missing on the cEdge device after upgrade to 17.15.2a. Secondary protocol pack updates successfully, but applications do not sync to the device. Prior to upgrade, custom applications were correctly reflected on the device. Eliminating a custom application and creating a new one resolves the issue temporarily.

Conditions

[+] Enviroment versions: vManage 20.15.2 Edge: 17.15.2/17.15.2a [+] Occurs after upgrading cEdge device software to version 17.15.2a. [+] Custom applications exist and are visible on vManage but not on the cEdge device. cEdge_DC1_West_R01#sh ip nbar protocol-id | in sdavc-test 2931 PPDK LOCAL speedtest 692 L7 STANDARD [+] ACtive connection to sd-avc is on the router cEdge_DC1_West_R01#show avc sd-service info summary Status: CONNECTED Device ID: cEdge_DC1_West_R01.us-west-2.compute.internal Device segment name: calo-auto-lab Device address: 10.1.0.50 Device OS version: 17.15.02a Device type: C8000V Active controller: Type : Primary Address : 1.1.1.7 Status : Connected Version : 4.6.0 Last connection: 09:48:05.000 PST Fri Feb 6 2026 Active SDAVC import files: Protocol pack: Not loaded Secondary protocol pack: PPDK_calo-auto-lab_dzaf22ac44174146d2740ccb07eb53.pack Rules pack: pp_update_calo-auto-lab_a_v2_cc52a16f4ff0.pack cEdge_DC1_West_R01# cEdge_DC1_West_R01#sh clock 09:48:36.584 PST Fri Feb 6 2026 [+] Custom applications managed via vManage and stored in neo4j and SDAVC databases. neo4j@neo4j> match (n:sdwandbPOLICYCUSTOMAPPSNODE) return n; +------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | n | +------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | (:sdwandbPOLICYCUSTOMAPPSNODE {owner: "admin", lastUpdated: 1768329551100, _rid: "0:PolicyCustomAppsNode:1768326970246:116", serverNames: "[\"*.FQND1.com\"]", appName: "test1", appId: "28da8843-863a-4f16-b54f-29cd5fc10d01", tenantId: "default", L3L4: "[]", sdavcStatus: "Edited"}) | | (:sdwandbPOLICYCUSTOMAPPSNODE {owner: "admin", lastUpdated: 1768328250767, _rid: "0:PolicyCustomAppsNode:1768327873030:123", serverNames: "[\"*FQND2.com\"]", appName: "test2", appId: "098b34b5-c3a2-46c8-a955-1f6723857daa", tenantId: "default", L3L4: "[]", sdavcStatus: "Edited"}) | | (:sdwandbPOLICYCUSTOMAPPSNODE {owner: "admin", lastUpdated: 1770307248312, _rid: "0:PolicyCustomAppsNode:1770307248283:8395", serverNames: "[\"*.FQND3.org\"]", appName: "test3", appId: "2a4ef773-2d6c-4ceb-bbf9-9b7fba9d7572", tenantId: "default", L3L4: "[]", sdavcStatus: "Created"}) | +------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 3 rows ready to start consuming query after 6 ms, results consumed after another 0 ms neo4j@neo4j> sdavcsummary=# select * from sd_persistent.custom_app_rules_entries; segment | app | rules | time | source ---------------+-------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- --+-------------------------+--------- calo-auto-lab | test2 | {"appName":"test2","serverNames":["*FQND1.com"]} | 2026-01-13 18:11:13.013 | vManage calo-auto-lab | test1 | {"appName":"test1","serverNames":["*.FQND2.com"]} | 2026-01-13 17:56:10.206 | vManage calo-auto-lab | test3 | {"appName":"test3","serverNames":["*.FQND3.org"],"metadata":{"commonName":"test3","userDefined":true,"sdavcBased":false,"cloudDefined":false,"generic":false,"autoDiscovered":false,"rating":0,"commonlyUsed":0,"id":3992} } | 2026-02-05 16:00:48.266 | vManage (3 rows)

Workaround

Workarounds [+] Eliminate an existing custom application and create a new one on vManage; this action causes the applications to appear again on the cEdge device.

Further Problem Description