Cisco Systems OL-27172-01 Mobility Aid User Manual


 
4-9
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 4 CPE Management Overview
Multi-Instance Object Support
The behavior of BAC to push the above template configuration during configuration sync is explained
below:
1. BAC discovers the instances in the object Device.Services.FAPService. by issuing
GetParameterNames RPC with next level set to true.
2. Since last() method is used, it gets the last instance and discovers the instances in the next level by
issuing GetParameterNames RPC for the parameter
Device.Services.FAPService.{last()}.REM.UMTS.GSM.Cell.{i}. with next level set to true.
3. BAC performs DeleteObject one by one on all the instances returned.
Example 4-3 Multi-Instance Object Using delete in Pre-requisites of Configuration Template
The following example illustrates usage of multi-instance object using delete in pre-requisites of
configuration template:
<Configuration templateVersion="3.0">
<ParameterDictionaries>
<ParameterDictionary>tr196-cwmp-dictionary.xml</ParameterDictionary>
</ParameterDictionaries>
<Prerequisites>
<MaintenanceWindow>
<StartTime>00:00:00</StartTime>
<Duration>15:00</Duration>
</MaintenanceWindow>
<Expression>
<ParameterName>Device.Services.FAPService.{i}.REM.UMTS.GSM.Cell.{i}.BSIC
</ParameterName>
<InstanceConfiguration>
<Instance>
<Path>Device.Services.FAPService.{i}.REM.UMTS.GSM.Cell.</Path>
<Value>compare(LAC lessThanEquals 65534)</Value>
</Instance>
<Instance>
<Path>Device.Services.FAPService.</Path>
<Value>last()</Value>
</Instance>
<MatchCondition>OR</MatchCondition>
</InstanceConfiguration>
<Value>18</Value>
<Operator>matchAllIgnoreCase</Operator>
</Expression>
</Prerequisites>
<ObjectInstance name="Device">
<ObjectInstance name="Services">
<ObjectInstance name="FAPService">
<ObjectInstance sync-method="discovered" instance="last()">
<ObjectInstance name="REM.UMTS.GSM.Cell" sync-method="delete" instance="2">
</ObjectInstance>
</ObjectInstance>
</ObjectInstance>
</ObjectInstance>
</Configuration>
The behavior of BAC to apply the above template configuration during configuration sync is explained
below:
1. During configuration sync execution, BAC validates the time to ensure that the configuration sync
falls in the maintenance window