Service configuration

Overview

The NFM-P supports the following service types:

VLL
VPLS/HVPLS/MVPLS/PBB
IES
VPRN

VLAN
Mirror
Optical Transport
Composite

See “Service management” in the NSP NFM-P Classic Management User Guide for more information about service management.

The XML API allows you to create and manage services by using the classes specified in the following table.

Table 19-2: Service objects

Service type	Package and class
Apipe	apipe.Apipe, mpr.Apipe (for Wavence only)
Epipe	Epipe.Epipe, mpr.Epipe (for Wavence only)
Fpipe	fpipe.Fpipe
Ipipe	ipipe.Ipipe
Cpipe	cpipe.Cpipe, mpr.Cpipe (for Wavence only)
Hpipe	hpipe.Hpipe
VPLS, MVPLS, PBB	vpls.Vpls, mvpls.Mvpls
IES	ies.Ies
VPRN	vprn.Vprn

The service.Service class is the parent class of the service objects in the previous table. The id and serviceId properties in the class are inherited by the subclasses that are used to identify the service. The following table describes the properties.

Table 19-3: Service class properties

Property	Description
id	SVC Mgr service ID—a unique value that identifies the service in the NFM-P database. The ID is also included as part of the FDN for the service objects. For example, 620 is the ID for svc-mgr:service-620.
serviceId	service ID—this ID is unique on the NE but may not be unique in the NFM-P database.

The following example shows the minimum XML parameter tags required to develop an XML request to create a basic service.

The genericObject.configureChildInstance method is used in the XML request to create a service. The XML response returns the <objectFullName> parameter that can be used to identify the new service.

Service creation parameters

method - generic.GenericObject.configureChildInstance
distinguishedName - svc-mgr
childConfigInfo - creates and configures the following service parameters:
- Service object - see Table 19-2, Service objects
- actionMask - specifies the create operation
- <subscriberPointer> - assigns a subscriber
- <serviceId> - (optional) assigns a unique service ID. If an ID is not specified, the NFM-P automatically assigns the ID.

Figure 19-5: Service creation request example

<generic.GenericObject.configureChildInstance xmlns="xmlapi_1.0">

   <deployer>immediate</deployer>

   <synchronousDeploy>true</synchronousDeploy>

   <distinguishedName>svc-mgr</distinguishedName>

   <childConfigInfo>

      <epipe.Epipe>

         <actionMask>

            <bit>create</bit>

         </actionMask>

         <subscriberPointer>subscriber:1</subscriberPointer>

..

      </epipe.Epipe>

   </childConfigInfo>

</generic.GenericObject.configureChildInstance>

See the XML API Reference and Schema Reference for more information about classes, properties, and methods to create the required services.