Filter
Top Products
18-5
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 18 Scripting Framework
Verifying Extension Scripts Availability in DPE Cache
Verifying Extension Scripts Availability in DPE Cache
When the device boots, it contacts DPE and invokes the extension scripts available in DPE cache based
on the extensions configured for the device.
To verify whether the extensions scripts are pushed to DPE cache from RDU:
Step 1 Log into DPE CLI.
Step 2 Verify that the extension scripts are available in the DPE cache, using the following command:
dpe# show files
The following is a sample output:
The list of files currently in DPE cache
filename size
main.js 2161
passthroughtest.js 4106
sample-firmware-image.bin 4239368
sampleextension.js 3319
samplehelper.js 2645
DPE caching 5 external files.
Listing the first 5 files, 0 files omitted
Verifying Status of the Extensions in DPE
The extensions scripts are executed in DPE, based on the extension points configured in device property
hierarchy.
To verify if the extensions are executed in the DPE after booting the device:
Step 1 Log into DPE CLI.
Step 2 Enable debug for DPE extensions using the command:
debug dpe dpe-ext
Step 3 Boot the device.
Step 4 Observe the dpe.log file to verify if the scripts are executed in DPE. To view DPE logs see Viewing the
dpe.log File, page 21-8.
The following is a sample output:
[Device [00000C-1234567890] Session [149eb9f53A137fed6a9c353A80000023]. Extension
[sampleextension.js].]: [Executing script [sampleextension.js] for the firs
t time]
Note The result is displayed in the dpe.log file.