Dynamically-created objects

General information

Network objects in a dynamic service are read-only on the NE and in the NFM-P, and cannot be modified except through RADIUS CoA messages. As a result, some operations are not supported on dynamically-created sites. When a dynamic object is created or deleted, the action is recorded in the dynamic service activity log. This section describes the unsupported operations, and the dynamic service activity log.

Dynamically created service sites are discovered and synchronized with the NFM-P in the same manner as manually created service sites. A service that contains a dynamically created object has the Contains Dynamically Created Sites parameter enabled, and cannot be deleted until the dynamically created object is removed from the service.

Unsupported operations
Table 86-1: Unsupported operations on dynamically created objects

Operation

Description

Object configuration operations

Delete

You cannot delete dynamically created objects. A RADIUS CoA message must request their deletion, or the control channel for the dynamic service that created the object must be disconnected.

Create child objects

You cannot create objects within dynamically created sites; for example, subscriber interfaces or spoke SDP bindings.

Topology map actions

You cannot interact with dynamically-created objects that appear on the service topology map, except to display their parameters.

SAP copy/move

Dynamically created SAPs are not included in SAP copy or move operations. The operations proceed normally, but skip any dynamically created SAPs.

MDA or card removal

You cannot delete MDAs or cards with dynamic sites.

Automated operations

Automatic MEP/MIP creation

MEGs skip MEP or MIP creation on SAPs and SDP bindings that are on a dynamically-created site.

SDP binding auto-completion

Dynamically-created sites are skipped during SDP binding auto-completion.

Service Throughput site list

Dynamically-created sites do not appear on the Service Throughput form

Dynamic services activity log

The NFM-P maintains a log of dynamic service actions for each NE, adding an entry whenever an object is created or deleted on the NE. Log entries are deleted after a configurable amount of time, as specified by the ageout constraint policy defined in the NFM-P. For information about configuring the ageout constraint policy, see the NSP System Administrator Guide; for information about viewing the dynamic services activity log, see To view the dynamic services activity log .

ID range behavior

Each NE that is configured for dynamic service must specify an ID range for dynamically-created sites. Dynamically-created sites can only use IDs from the specified range, and non-dynamic sites cannot use IDs from that range. When a dynamic service is created on an NE, the next available ID from the specified range is used.