Hi experts!!
Looking into the Alcatel NED we see that it tries to adapt to Alcatel/Nokia TiMOS CLI based on its version
For filter "action drop" it seems that TiMOS <13 the "action drop" is configured in a single line, while for TiMOS >=13 is done in two different lines "action" line + "drop" line
container action-flat {
tailf:info "Configure action for the filter entry";
tailf:cli-compact-syntax;
tailf:cli-embed-no-on-delete;
tailf:alt-name "action";
when "/alu:os-major < 13";
tailf:ned-data "/alu:os-major" {
tailf:transaction to;
}
Configuring this filter action drop using NSO device model the same command is able to push the right config on the device (independently of the version) using the NED logic
However when we try to map the service model to the device model we are unable to benefit from the NED logic and we have to add the extra logic for that command switch
<action when="{$USE_ACTION_FLAT='false'}">
<drop />
</action>
<action-flat when="{$USE_ACTION_FLAT='true'}">
<drop />
</action-flat>
This doesnt seem right as the NED logic and the abstraction it provides has to be replicated again at service template. Apparently the NED when condition "when "/alu:os-major < 13";" is not in stored in CDB (under device filter tree) when TiMOS is >13 and config is not pushed to the device.
We might be doing something wrong but it might be a NED defect
Thanks a lot
Regards
Rob
