RoutingNE Doesn't Support More Than 1 ASDL

Last updated on OCTOBER 25, 2013

Applies to:

Symptoms

I have a NetworkElement(NE) created via Service Configuration Environment(SCE),version 3.3.2, Build id: M20080221-1800. The requirement is  4 atomic actions need to be routed via this Network Element, (for the sake of throttling these specific work orders to a specified throughput level).

I try to achieve this by having the RoutingNE for this Network Element to map to the 4 AtomicActions, on the 'Remote Network Element' tab of the NetworkElement Editor. SCE allows me to do this and the SCE project builds fine. The XML file generated for this Network Element also shows that for routing, 4 Atomic Actions are mapped on the same Routing NE.

However when I deploy this NE on an ASAP instance and then look into the SARM DB,tbl_clli_route, the entry exists only for 1 AtomicAction, rather than 4. If I try to manually add the additional Atomic actions to this NE on the SARM DB, I'm able to do so, implying that the ASAP product supports multiple Atomic Actions to be mapped to a single Routing NE. But when deploying the same,via a SCE-generated deployable XML file, these additional Atomic Actions are lost.

Cause