mtosi adapter using junos space sdk - juniper networks · tabel 21: mtosi-junos space ... mtosi...

IMPLEMENTATION GUIDE

Copyright © 2013, Juniper Networks, Inc. 1

MTOSI ADAPTER USING JUNOS SPACE SDK

Although Juniper Networks has attempted to provide accurate information in this guide, Juniper Networks does not warrant or guarantee the accuracy of the information provided herein. Third party product descriptions and related technical details provided in this document are for information purposes only and such products are not supported by Juniper Networks. All information provided in this guide is provided “as is”, with all faults, and without warranty of any kind, either expressed or implied or statutory. Juniper Networks and its suppliers hereby disclaim all warranties related to this guide and the information contained herein, whether expressed or implied of statutory including, without limitation, those of merchantability, fitness for a particular purpose and noninfringement, or arising from a course of dealing, usage, or trade practice.

2 Copyright © 2013, Juniper Networks, Inc.

IMPLEMENTATION GUIDE - MTOSI Adapter Using Junos Space SDK

Table of ContentsMTOSI Adapter—Multi-Technology Operations System Interface Using Junos Space SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

MTOSI Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

The Challenge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

The MTOSI-Junos Space Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Request and Response Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Mapping Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

XML Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Platform Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Junos Space Network Management Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Junos Space SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Features and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

MTOSI Supported Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Termination Point Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Subscribe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Unsubscribe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Notify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Supported Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Supported Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Supported Layer Rate and Layer Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

MTOSI Junos Space Mapping Table Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

MTOSI Adapter Customization Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Input Details for Flow Domain-Related Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Request Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Operations System Retrieval Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Managed Domain Retrieval Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Managed Element Retrieval Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Equipment Inventory Retrieval Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Resource Inventory Retrieval Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Common Resource Provisioning Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Termination Point Control Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Flow Domain Control Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Flow Domain Retrieval Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

MTOSI Solution Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Juniper Device Modeling Using MTOSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Use Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Modifying the physical properties of the termination point from the OSS systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configuring the L2VPN: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

About Juniper Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61



List of TablesTable 1: XML Binding Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Table 2: MTOSI and Junos Space Element Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Table 3: Configuration Service Operations System Manager Port Types Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Table 4: Operations System Response Elements Supported/Mapped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Table 5: Managed Domain Service Elements Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Table 6: Managed Domain Response Elements Supported/Mapped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Table 7: Managed Element Retrieval Service Operations Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Table 8: Managed Element Retrieval Response Elements Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Table 9: Equipment Retrieval Service Operations Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Table 10: Equipment Holder T Elements Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Table 11: Flow Domain Control Service Operations Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Table 12: Flow Domain Control Response Elements Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Table 13: Flow Domain Retrieval Service Operations Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Table 14: Flow Domain Retrieval Response Elements Supported/Mapped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Table 15: Get Inventory Resource Operations Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Table 16: Retrieval of Termination Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table 17: Flow Domain Elements Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Table 18: Matrix Flow Domain Elements Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Table 19: Flow Domain Fragment Elements Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Table 20: Matrix Flow Domain Fragment Elements Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 5: MTOSI Simulation Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Tabel 21: MTOSI-Junos Space Element Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Table 22: MTOSI Services and Termination Points Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

List of FiguresFigure 1: Multiple Vendor Technologies Interconnected Using MTOSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Figure 2: Junos Space-MTOSI High-Level Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Figure 3: MTOSI to Junos Space Element Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 4: MTOSI Customization Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Figure 6: Juniper Device Modeling Using MTOSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Figure 7: Shows the Inventory and Discovery OSS Screen Displaying the Discovered Network From Junos Space. . . . . . 50

Figure 8: Shows the Inventory and Discovery OSS Screen Displaying the Physical Interfaces of the Network Element(s)

Retrieved From Junos Space Using REST APIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Figure 9: Inventory and Discovery OSS Screen Showing Physical Interfaces of the Network Element(s) Retrieved From

Junos Space Using REST APIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Figure 10: Shows the Inventory and Discovery OSS Screen Displaying the Hardware Inventory of the Network Elements

Retrieved From Junos Space Using REST APIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Figure 11: Shows a View of Inventory Interface Properties on the Inventory and Discovery OSS. . . . . . . . . . . . . . . . . . . . . . . 52

Figure 12: Shows the Inventory and Discovery OSS Screen Where Device Notifications are Made Whaen Changes Occur

in Junos Space for Cases Like Those Listed Below: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Figure 13: Creating a Flow Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Figure 14: Creating a Matrix Flow Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Figure 15: Creating a Flow Domain Fragment (screen one) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Figure 16: Creating a Flow Domain Fragment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Figure 17: Creating a Flow Domain Fragment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Figure 18: Manageing Jobs in Space Network Management Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Figure19: Querying the Flow Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Figure 20: Querying the Matrix Flow Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Figure 21: Querying the Flow Domain Fragment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60



MTOSI Adapter—Multi-Technology Operations System Interface Using Junos Space SDKWith MTOSI, the Service Provider Can Integrate Systems Quickly, Have Them Interoperate Seamlessly, and Deliver Differentiated Services in a Cost-Effective Manner

Multi-Technology Operations Systems Interface (MTOSI) is a unified open interface that can be used by multiple types

of management systems to provide network and service management. The MTOSI standard covers all communication

technologies (from Layer 1 such as SONET/SDH, through higher layer technologies such as VoIP). MTOSI facilitates

application-to-application interworking, reduces time to deployment, and lowers the cost of system ownership for

service providers and their customers.

Current management and support system implementations employ diverse middleware technologies, a reality that

is not likely to change in the immediate future. To be widely adopted, MTOSI cannot mandate specific middleware

technologies for its implementation. Therefore, the MTOSI interfaces are sufficiently abstract to be middleware neutral,

yet rigorous enough that vendors can map them quickly to their middleware of choice.

Common Communication Vehicle (CCV) is the common middleware required to implement MTOSI. CCV is a

middleware abstraction that allows MTOSI interfaces to be bound to different middleware technologies as needed.

By exploiting the expressive power of Web Services Description Language (WSDL), MTOSI interfaces are composed of

both logical and physical definitions.

SolutionMTOSI 2.0 capabilities are enabled on Juniper Networks Junos Space Network Management Platform.

Benefits• MTOSI provides a standard interface between different business and operations systems for an open systems

environment.

• HTTP and HTTPS are both enabled by default using SOAP.

• The MTOSI Adapter is implemented in a way that is generic enough to include new layer parameters with and without

customization.

MTOSI Advantages The MTOSI standard offers a number of unique business advantages (#1-4), as well as advantages applicable to any

well designed and well supported interface standard (#5-8):

1. MTOSI provides a standard interface between different systems for fulfillment and assurance functionality. In

effect, different instances of the same interface are reused at different reference points.

Benefit: Knowledge can be reused in the design of systems.

2. MTOSI uses XML (eXtended Mark-Up Language)-based messaging.

Benefit: XML technology is a widely accepted and used technology.

3. MTOSI provides rules for versioning and for vendor extensions to the XML messages.

Benefit: When MTOSI is deployed, the server and consumer application ends of the interfaces can be upgraded

independently. Also, when several vendors’ equipment is deployed, the proprietary extensions are managed in a

consistent manner.

4. MTOSI uses standard communication patterns to support business activities that can be implemented by a range

of IT platforms and transport protocols.

Benefit: The underlying platform can be changed without propagating the change to the applications.

5. MTOSI allows service providers to implement management and support systems quickly. For example, without

MTOSI, each of the four electronic manufacturing services (EMS) providers in Figure 1 would need to define and

agree upon a common interface (on a pair-wise basis), build the interface, and then do interoperability testing.

Benefit: MTOSI lowers the time and costs needed to integrate management and support system software from

different suppliers.

6. MTOSI is designed to support service provider requirements for an open systems environment.

Benefit: This allows service providers to more easily deploy management and support systems from multiple

vendors and to replace existing ones. This increase in choice creates a more competitive environment for service

providers, allowing them to choose products that best fit their functional and financial needs.



7. MTOSI encourages system integrators to integrate products that are MTOSI-compliant in advance.

Benefit: This results in lower upfront costs and faster deployment for service providers.

8. MTOSI helps carriers avoid wholesale replacements of legacy systems and instead allows them to introduce and

integrate point applications that can address new solutions and services.

Benefit: This allows a service provider to preserve its investment in legacy systems while still addressing the need

to manage new technologies and services.

InventoryManagement

ServiceActivation

WorkflowManager

OSS/J MTOSI MTOSI MTOSI MTOSI

MTOSI MTOSI MTOSI

Underlying Network

MTOSI

DiscoveryService

Assurance

Common Communication Vehicle (CCV)

Mediation Services

Core Transports

EMS EMS EMS EMS

Figure 1: Multiple Vendor Technologies Interconnected Using MTOSI

The ChallengeToday’s service providers are faced with a number of issues that are preventing them from rolling out services in

an efficient and cost-effective manner. While attempting to create sophisticated services, they must contend with

complex systems built from multiple competing technologies delivered by different vendors. Instead of focusing on the

delivery of new services, service providers are forced to deal with vendor integration complexity leading to unnecessary

integration costs, reduced feature sets, and ultimately delay in revenue generation.

The MTOSI-Junos Space Solution As part of the MTOSI Application Development program, HCL is enabling MTOSI 2.0 capabilities on Juniper Networks®

Junos® Space Network Management Platform. Junos Space MTOSI Adapter is a message-oriented middleware (MOM)

system designed to fill the gap between the MTOSI OSS and the Junos Space Platform. This system translates the

MTOSI messages into Junos Space-specific messages and vice versa, and it provides a channel for exchanging the

translated messages between the OSS and Junos Space.



This new functionality addresses the challenges and issues described above. It helps Junos Space users integrate with

OSS/BSS systems and launch new and innovative business services that effectively leverage those systems. It also

makes Junos Space an eTOM-compliant product that enables OS to OS integration. In addition, since MTOSI is based

on Web technologies such as JMS, XML, Simple Object Access Protocol (SOAP), and WSDL, it provides the following

benefits:

• Since the above mentioned tools are widely used in the industry, they have cost advantages over the use of specialized

management technologies such as Common Management Information Protocol (CMIP) and Simple Network

Management Protocol (SNMP).

• Management systems can be integrated quickly and easily with other operations support systems (OSS) such as billing,

service activation, inventory management, etc.

• Each system can be upgraded independently without significantly affecting other systems, minimizing overall network

downtime.

By adding MTOSI capabilities through Junos Space to some of the core functions of the service provider’s management

system—inventory retrieval interface for the configuration service, device discovery and provisioning interface, alarm

monitoring interface with support for coarse-grained alarm retrieval operations for fault service, topic-based publisher

and subscriber notifications for the notification service, service activation interface, and billing interface—the overall

cost of integration with the existing OSS can be cut down dramatically.

By basing the platform around MTOSI, the service provider is able to integrate systems quickly, have them interoperate

seamlessly, and deliver differentiated services in a cost-effective manner, setting itself apart from the competition.

B

A

MTOSIInventory andDiscovery UI

OSS Client UI

(ReferenceImplementation

for demo andtesting)

MTOSI Adapter

MTOSI AdapterConfiguration UI

Junos Space

NotificationConsumer(Reference

Implementationfor demo and

tesing)

QueryNotification

Response

QueryNotification

Subscribe (DBchanges, Device

managment)

Notification 1

Notification 2

Notification N

Inventory or Configuration Response

Inventory or Configuration Request

MTOSINotification

Notification DB5 5

2

4

1

Figure 2: Junos Space-MTOSI High-Level Architecture

Request and Response HandlingMTOSI Adapter has intelligence to perform the following operations:

1. Convert multiple responses from Junos Space Network Management Platform and send back one response to the

OSS.

2. Convert one request from the MTOSI OSS into multiple requests towards Junos Space (request spawning) and

aggregate the multiple responses into a single one towards OSS.

3. Convert one request from the OSS and receive multiple responses from Junos Space, sending back multiple

responses to OSS Systems



Mapping IntelligenceMTOSI Adapter has the intelligence to map the MTOSI data model to the Junos Space data model. It also has the

intelligence to map the following:

• MTOSI data model to a Junos Space-specific message data model

• MTOSI data model to a Junos Space configuration data model

• MTOSI data model to a Junos Space data notification data model

• MTOSI operation model to a Junos Space operation model

• MTOSI operation model to a Junos Space RESTful API operation

XML BindingMTOSI Adapter uses different technologies to bind the XML document to Java Objects. Table 1 explains the way

different XML documents are bound and interpreted.

Table 1: XML Binding Technologies

Document Type Technology Remarks

MTOSI SOAP XML document Axis2 framework MTOSI Adapter uses the Axis2 framework to bind the MTOSI SOAP XML document to Java Objects. Axis2 generates the Java Classes by using the MTOSI entity model.

Junos Space-specific XML document

XML DOM/SAX parser MTOSI Adapter uses the DOM/SAX parser to parse the Junos Space XML documents and construct XML document objects. The parsed XML objects will be traversed to find the appropriate node.

Platform EnvironmentThe MTOSI Adapter application uses the Axis2 framework to bind the MTOSI Web service (WS) to XML objects. The

MTOSI Adapter application expects that the Axis2 runtime environment will be configured in the Junos Space Network

Management Platform.

Junos Space Network Management PlatformJunos Space is an open network application platform that uses multilayered network abstractions, operator-centric

automation schemes, embedded element management functionality, and the simplicity of a point-and-click user

interface. Space helps network operators in enterprise and service provider organizations scale their operations, reduce

operational complexity, and enable new applications and services to be brought to market quickly.

Junos Space is based on service-oriented architecture (SOA) and uses industry-standard technologies to provide an

enhanced user experience, massive application transparent scale, high availability, and feature velocity. The platform

provides a single abstracted network model across Juniper’s networking infrastructure, and it extends this to third

parties through standards-based Representational State Transfer (RESTful) APIs. The use of a standards-based

Device Management Interface (DMI), an XML schema-driven device access API, zero-day support for new devices, and

a plug-and-play application environment allows in-service device and software upgrades.

Users can access the platform functionality using a simple, Web 2.0 graphical user interface (GUI), which uses

persona-based workflows and progressive disclosure to enable operator-centric and scope-specific visibility and

control. Along with a set of robust, out-of-the-box, and easy-to-use applications that provide comprehensive business

solutions for security, mobility, the data center, and cloud solutions, the platform offers Junos Space SDK, a software

development kit specifically designed to enable developers to use the information embedded in the network to create

unique, differentiated applications—sophisticated workflow engines, core business logic, streamlined interfaces for

operational tools—quickly, easily, and economically.

Junos Space SDKSpace SDK enables developers to leverage the Junos Space Network Management Platform to abstract the capability

and connections to Juniper Networks routers, switches, and firewalls. It encompasses a rich set of tools including

RESTful APIs, the Eclipse Integrated developer environment, device simulators, reference applications, support tools,

and documentation. There are various types of applications one can build using this SDK, including rich applications,

data applications, workflows, and integrations.



Features and Benefits• HTTP and HTTPS—HTTP and HTTPS are both enabled by default. The default HTTP port is 8080 and the default

HTTPS port is 8443. In the production environment, the port used will be 443.

• SOAP—MTOSI 2.0 northbound interface uses the SOAP protocol message. SOAP is a lightweight protocol for exchanging

information in a decentralized, distributed environment. It is an XML-based protocol that consists of three parts: an

envelope that defines a framework for describing what is in a message and how to process it; a set of encoding rules for

expressing instances of application-defined data types; and a convention for representing remote procedure calls and

responses. SOAP can potentially be used in combination with a variety of other protocols. However, the only bindings

defined in this document describe how to use SOAP in combination with HTTP and HTTP Extension Framework.

• Operator Requirement—Operators are required to build their OSS applications using MTOSI as interface on top of the

Junos Space Network Management Platform.

- MTOSI Element Reference: This is the value referred in the MTOSI request to refer the instance of the MTOSI element.

For instance, in order to refer the managed element, the MTOSI request contains the name as “ME” and value as

instance of the Managed Element.

- MTOSI Element: This is the descriptive name of the MTOSI element.

- Junos Space Element: This is used to refer to the Junos Space Element in the Junos Space data model.

Table 2: MTOSI and Junos Space Element Mapping

MTOSI Element Reference

MTOSI Element Junos Space Element

MD Managed Domain /managed-domain

ME Managed Element /managed-element/{id}

NE Network Element Device ID

PTP Physical Termination Point /ptp

CTP Connection Termination Point /ptp/{ptpid}/ctp

FTP Floating Termination Point Not supported

CPTP Connectionless Port Termination Point /ptp/{ptpid}/ctp

SNC Subnetwork Connection Not supported

FD Flow Domain Not supported

FP Flow Point Not supported

MFD Matrix Flow Domain Not supported

TL Topological Link Not supported

FPC Flexible PIC Concentrator (FPC) board Interface name interfacetype-fpc/slot/port:logical-channel

Slot Slot in the FPC board Interface name interfacetype-fpc/slot/port:logical-channel

Port Port in the slot Interface name interfacetype-fpc/slot/port:logical-channel

EH Equipment Holder

EQ Contained Equipment

• Customization—The MTOSI Adapter is implemented in a way that is generic enough to include new layer parameters with

and without customization.

- Without customization: Operator can include a new layer parameter, which is part of the existing supported operation,

in the mapping table as per the mapping configuration. The MTOSI adapter will take care of handling new parameters

without any implementation at the MTOSI Adapter level.

- With customization: If an operator wants to include a new parameter in the operation that will not be supported by the

MTOSI adapter, then the MTOSI adapter code will need to undergo customization.



MTOSI Supported Operations The following table shows which operations of the Configuration Service Operations System Manager port type are

supported on objects in this domain.

Table 3: Configuration Service Operations System Manager Port Types Supported

Operation Name Supported Implementation Details

getAllOperationsSystems Y Input: Not applicableOutput: List of operating systems

getOperationsSystem Y Input: Not applicableOutput: Details of the operating system

getOperationSystemsIterator N

getSubordinateOperationsSystem N

Table 4: Operations System Response Elements Supported/Mapped

Attribute Supported Notes

name Y

discoveredName Y

namingOS Y

userLabel Y

source Y Value is always Network_EMS.

networkAccessDomain Y

meiAttributes Y

owner N

aliasNameList N

resourceState N

softwareVersion Y

productName Y

manufacturer Y

resourceFulfillmentState Y Value is always “IN_SERVICE”.

vendorExtensions N No vendor extensions are applicable.

getAllManagedDomains Y Input: OSS ID, EMS IDOutput: List of all managed domains

getManagedDomain Y Input: OSS ID, EMS ID, MD IDOutput details of the Managed Domain

Table 5: Managed Domain Service Elements Supported


getAllManagedDomains Y Input: OSS ID, EMS IDOutput: List of all managed domains

getManagedDomain Y Input: OSS ID, EMS ID, MD IDOutput details of the Managed Domain



Table 6: Managed Domain Response Elements Supported/Mapped


name Y

discoveredName Y

namingOS Y

userLabel Y

owner N

aliasNameList N


Table 7: Managed Element Retrieval Service Operations Supported


getAllManagedElements Y Input: The OSS ID, Network Element ID, Managed Domain IDOutput: All managed elements under the given Managed Domain

getAllManagedElementsPassingFilter N

getAllManagedElementsWrtOS N

getManagedElement Y Input: The OSS ID, Network Element ID, Managed Element IDOutput: All details of the Managed

getManagedElementsIterator N

Table 8: Managed Element Retrieval Response Elements Supported


name Y This maps to the native attribute.

discoveredName Y The discoveredName contains the final name string from the name’s meNm component.

namingOS Y

userLabel Y


owner Y

aliasNameList Y

resourceState Y

location Y This is mapped to the IP address (ipAddr).

manufacturer Y

manufacturerDate Y

productName Y

softwareVersion Y This is the software version.

isInSyncState Y

supportedRates N

communicationState Y This is mapped to the Connection state.


vendorExtensions N



Table 9: Equipment Retrieval Service Operations Supported


getAllEquipment Y Input: The OSS ID, Network element ID, Managed Domain ID, Managed Element ID

Output: It returns the equipment holders and the list of complete equipments It returns the list of both the equipment holders, equipments that belongs.

The naming attribute of the equipment tells the containment relationship of that equipment. For instance, the “Port” in the interface will have the following syntax of the naming attribute to identify the relationship of the equipment:

Chasis=”value”; FPC=”value” Slot=”value”; Port=”Value”

getAllSupportingEquipment N

getEquipment Y Input: The OSS ID, Network Element ID, Managed Domain ID, Managed Element ID, equipment ID

Output: All details of the given equipment

getEquipment (Holder) Y Input: The OSS ID, Network element ID, Managed Domain ID, Managed Element ID, Equipment Holder ID

Output: Returns the list of equipment that belongs to the given holder

getContainedEquipment Y Input: The OSS ID, Network Element ID, Managed Domain ID, Managed Element ID, equipment ID

Output: List of equipment under the given contained equipment

getEquipmentIterator N

getSupportedEquipment N

getSupportedEquipmentIterator N

Table 10: Equipment Holder T Elements Supported


name Y

discoveredName Y

namingOS Y

userLabel Y



meiAttribute Y

owner Y

aliasNameList Y

resourceState Y

isReportingAlarms Y Mapped to reporting alarms.

holderType Y

acceptableEquipmentTypeList Y

expectedOrInstalledEquipment Y

holderState Y

Location Y Mapped to path.

Manufacturer Y

manufacturerDate Y




This is the logical grouping of administrative domain of flows. Flow Domain contains the logical grouping of one or

more flow domain fragments. The following table shows the operations supported in the Flow Domain Control Service.

Table 11: Flow Domain Control Service Operations Supported


createFlowDomain Y Input: Refer to Table 1

createMatrixFlowDomain Y Input: Refer to Table 2

createAndActivateFlowDomainFragment Y Input: Refer to Table 3

deleteFlowDomain Y Input: OSS ID, EMS ID, MD ID, FD ID

deleteMatrixFlowDomain Y Input: OSS ID, EMS ID, MD ID, FD ID, MFD ID

deactivateAndDeleteFlowDomainFragment Y Input: OSS ID, EMS ID, MD ID, FD ID, FDFr ID

assignConnectionlessPortTerminationPointsToMfd Y

associateConnectionlessPortTerminationPointsWithFd Y

associateMatrixFlowDomainsWithFd Y

deAssociateConnectionlessPortTerminationPointsFromFd Y

deAssociateMatrixFlowDomainsFromFd Y

modifyFlowDomain Y

modifyFlowDomainFragment Y

modifyMatrixFlowDomain Y

unassignConnectionlessPortTerminationPointsFromMfd Y

Location Y

Manufacturer Y

manufacturerDate Y

vendorExtensions N

Table 12: Flow Domain Control Response Elements Supported


name Y This maps to the value given for the element. For example, Flow Domain would be “engrFlowDomain21.”

discoveredName Y The discoveredName would be mapped to “FlowDomain.”

namingOS Y Junos Space EMS.

userLabel Y This would map to the name value of the given element.

ConnectivityState N The ConnectivityState of the Flow Domain would map to a Enum value.

owner Y By default, owner would be mapped to “Juniper Inc.”

isFlexible N



Table 13: Flow Domain Retrieval Service Operations Supported


getAllFlowDomains N

getFlowDomain Y Input: OSS ID, EMS ID, MD ID, FD ID

Output: The FD details

getFlowDomainFragmentRoute N

getAllFlowDomainFragments N

getFlowDomainFragment Y Input: OSS ID, EMS ID, MD ID, FD ID, FDFr ID

Output: The FDFr details

getAllAssociatedMatrixFlowDomains N

getAllSupportedMatrixFlowDomains N

getAssigningMatrixFlowDomain N

getAssociatingFlowDomain N

getFlowDomainFragmentsByUserLabel N

getFlowDomainFragmentsIterator N

getFlowDomainFragmentsWithTp N

getFlowDomainsByUserLabel N

getFlowDomainsIterator N

getMatrixFlowDomain Y Input: OSS ID, EMS ID, MD ID, FD ID, MFDFr ID

Output: The MFDFr details

getMatrixFlowDomainsIterator N

Table 14: Flow Domain Retrieval Response Elements Supported/Mapped


name Y This maps to the value given for the element. For example, Flow Domain = “engrFlowDomain21.”

discoveredName Y The discoveredName would be mapped to “FlowDomain.”

namingOS Y Junos Space EMS.

userLabel Y This would map to the name value of the given element.

Table 15: Get Inventory Resource Operations Supported


getInventory Y Input: OS ID, MD ID, EMS ID

Output: Complete information of the Managed Domain

getInventoryIterator N

The getInventoryResponse returns complete details of the Managed Domain, along with the elements, PTPs, CTPs,

and equipment under the specified Managed Domain. The response structure will be similar to the individual ones as

defined above. For example, the Managed Element details section will be similar to the getManagedElement response;

the PTP details section will be similar to getTerminationPoint response; and so on.



Termination Point Control

Table 16: Retrieval of Termination Points

Operation Name Implementation Details

setTerminationPoint This is the operation supported for changing the configuration parameters of the interface (Termination Point).Input: OSS ID, EMS ID, Managed Domain ID, Network Element ID, FPC, slot, port, and necessary parametersOutput: Result of the operation

setCommonAttribute Input: OSS ID, EMS ID, Managed Domain ID, Managed Element ID, PTP ID/CEQ :Connection Equipment IDOutput: Result of the operation

The response of setCommonAttribute returns only the VendorExtension.

SubscribeThe subscribe operation is used for subscribing to a particular OSS. The notifications related to the particular OSS like

change in state, etc. will be sent to the URI specified in the Subscribe request.

Input: ConsumerEPR, Notification Type, IP address of the device, user name and password of the device, and

scheduling information.

Output: SubscriptionID

UnsubscribeThe unsubscribe operation is used to stop receiving any further notifications from the subscribed OSS.

Input: SubscriptionID and NotificationType

Output: Status

NotifyThe notify response is sent from the OSS whenever a change occurs such as device addition/modification/deletion, etc.

Supported InterfaceThe following physical interfaces are the representative list of interfaces which are configured and mapped towards

the Juniper configuration commands. There might be some other parameters that need to be configured as well. Since

MTOSI Adapter is framework, it supports configuration layer parameters with minor customization.

• Ethernet (Fast, gigabit, 10-gigabit, 10/100)

• Aggregated Ethernet

• SONET/SDH

• Aggregated SONET

Supported Configuration• Physical and link-layer configuration

• Link-layer protocols configuration—Spanning Tree Protocol (STP), link aggregation group (LAG), LCAP

• VLAN (to be decided)

Supported Layer Rate and Layer Parameters• LR_DSR_10Gigabit_Ethernet

• LR_DSR_Fast_Ethernet

• LR_DSR_Gigabit_Ethernet

• LR_Encapsulation

• LR_Ethernet

• LR_LAG_Fragment

• LR_Line_OC1_STS1_and_MS_STM0







• LR_Low_Order_TU3_VC3



MTOSI Junos Space Mapping Table Schema

Figure 3: MTOSI to Junos Space Element Mapping

Operation: The operation contains the list of supported operations along with mapping for each MTOSI element to the

Junos Space element.

Element details:

• <MTOSIElement> contains the name used in the MTOSI Adapter implementation.

• <JSpaceElement> contains the Junos Space equivalent name for the element.

• <JSpaceElementXPath> contains the XPath for retrieving the value for the element from the response.

• <Action> specifies the class and the method name to be triggered when the specific action occurs.

For example, for getting the ManagedElement value in the GetPTP operation, the XML fragment shown below can be

used:

<Operation type=”INVENTORY” accept=”application/vnd.net.juniper.space.managed-domain.me-ptp+xml;version=1” requestURI=”/api/space/managed-domain/managed-elements/%KEY%/ptps/%KEY%” name=”GetPTPTerminationPoint” count=”count(/MTOSIAdapterDocument/ptp)”> <Element> <MTOSIElement>ManagedElement</MTOSIElement> <JSpaceElement>managed-elements</JSpaceElement> <Mode> <QueryMode> <JSpaceElementXPath>/MTOSIAdapterDocument/getTerminationPointRequest/tpRef/rdn[type=”ME”]/value/text()</JSpaceElementXPath> <ActionList> <Action name=”get”> <Class>GetTerminationPointRequestCtx</Class> <Method>getManagedElementValue</Method> </Action> <Action name=”set”> <Class>GetTerminationPointResponseCtx</Class> <Method>setMEID</Method>

Operation

1.00

ModeMTOSIMapping

Comment describingyour root element

Layer/Parameter

attributes

Element

MTOSIElement

QueryMode

JSpaceElementXPath

QueryModeTypeModeType

ElementType

OperationType (extension)

MTOSIMapping

Layerindex

URI

JSpaceElement

ConfigMode

ActionList

1.00

0.00



Layer Parameter: This contains the list of layer parameters, the layer type, and its related parameters.

Element details:

• <Index> is the unique value to identify the LayerParameter.

• <ParameterName> contains the name of the LayerParameter defined.

• <LayerRateList> contains the list of Layer Rates specific to the LayerParameter.

For example, the XML fragment is defined as follows for DuplexMode LayerParameter:

</Action> </ActionList> </QueryMode> </Mode> </Element></Operation>

<Layer> <Index>2</Index> <ParameterName>DuplexMode</ParameterName> <LayerRateList> <LayerRate>LR_DSR_10Gigabit_Ethernet</LayerRate> </LayerRateList> <LayerRateList> <LayerRate>LR_DSR_Fast_Ethernet</LayerRate> </LayerRateList> <LayerRateList> <LayerRate>LR_DSR_Gigabit_Ethernet</LayerRate> </LayerRateList></Layer>



MTOSI Adapter Customization Schema

Figure 4: MTOSI Customization Scheme

MTOSINamingMapping

1.00

MTOSIAdapterCustomization

Comment describing your root element

MTOSINaming

MTOSIElement

MTOSIAdapterImplementationIt..

MTOSIStanderName

LayerParameters

1.00

MTOSILayer

Name

InterfaceDetails

LayerRate

LegalValue

TPObject

AVC

DeviceConfigIndex

attributes

Index

LPIndex

HardDependency

Dependency

DeviceConfig

1.00

DeviceConfiguration

attributes

any

ConfigXML

DeviceVersion

DeviceType

XPath

MTOSIMappingTypeMTOSINamingType

LayerParameterTypeParameterListType (extension)

MTOSINamingMappingType

DeviceConfigType

xscamyType

DependencyType

LAType

Index

0.00

0.00

0.00

Name



MTOSI naming: This contains the mapping between the Adapter Implementation Name to the MTOSI Standard Name.

When a Standard Name undergoes any change, the Adapter code doesn’t need to be changed. The MTOSI Standard

Name must be updated properly by the data from the OSS.

Element details:

• <MTOSIAdapterImplementationName> contains the name used in the MTOSI Adapter.

• <MTOSIStandardName> contains the standard name specified by the OSS.

For example, the following XML fragment is defined for ManagedOS:

<MTOSINaming><MTOSINamingMapping> <MTOSIAdapterImplementationName>ManagedOS</MTOSIAdapterImplementationName> <MTOSIStandarName>OSS</MTOSIStandarName> </MTOSINamingMapping></MTOSINaming>

MTOSI Layer: The layer parameter configuration details are defined in this section.

Element details:

• <Name> contains the parameter name in MTOSI standards.

• <TPObject> contains the TransmissionParameter Object.

• <LegalValue> contains the valid values corresponding to the parameter.

• <InterfaceType> contains the type of the interface.

• <Speed> contains the speed for the specific type.

• <AVC> if given as yes means that any change in the layer parameter will trigger an aggregated virtual circuit (AVC)

notification.

• <Dependency> If the layer parameter has any dependencies on any other layer parameter, the reference to that layer

parameter index is mentioned in this section.

• <DeviceConfigIndex> If there is any configuration related to the layer parameter, the configuration is defined in the Device

Configuration section and a reference to it is mentioned here using the index.

For example, the following XML fragment is defined for MaximumFrameSize (MTU):

<LayerParameters Index=”1”> <Name>MaximumFrameSize</Name> <TPObject>PhysicalTerminationPoint</TPObject> <LegalValue>256 - 9192</LegalValue> <LayerRate> <Name>LR_DSR_Fast_Ethernet</Name> <InterfaceDetails> <InterfaceType>ge</InterfaceType> <Speed>1000</Speed> </InterfaceDetails> <InterfaceDetails> <InterfaceType>fe</InterfaceType> <Speed>10000</Speed> </InterfaceDetails> </LayerRate> <AVC>Yes</AVC> <Dependency> <LPIndex /> <HardDependency /> </Dependency> <DeviceConfigIndex>1</DeviceConfigIndex> </LayerParameters>



MTOSI element: Similar to LayerParameter, if any element contains/requires device configuration details, they can be

given using the guidelines in this section.

Element details:

• <OperationName> contains the operation name which contains the element to be configured.

• <ElementName> contains the name of the element.

• <DeviceConfigIndex> is the index of the referred Device Configuration Details.

• <AVC> If yes, any change in the element configuration will trigger an AVC notification; if no, there won’t be any

notifications triggered.

The sample format is shown below:

<MTOSIElementMapping> <OperationName /> <ElementName /> <DeviceConfigIndex /> <AVC>No</AVC> </MTOSIElementMapping>

Device Configuration: The device configuration commands/XML fragment are defined in this segment for each layer

parameter or element.

Element details:

• <Index> contains a unique index for identification.

• <DeviceType> contains the type of the device.

• <DeviceVersion> contains the version of the device.

• <ConfigXML> contains the complete XML structure used for configuring the layer parameter in the device.

• <XPath> contains the XPath required to retrieve the LayerParameter value while receiving information from the device.

As an example, the device configuration for LayerParameter MaximumFrameSize is shown below:

<DeviceConfig> <Index>1</Index> <DeviceType>MX480</DeviceType> <DeviceVersion>10.3R1.9</DeviceVersion> <ConfigXML><configuration><interfaces><interface><name>$PTP</name><mtu>$MaximumFrameSize</mtu></interface></interfaces></configuration></ConfigXML> <XPath>/configuration/interfaces/interface[name=’$TP’]/mtu/text()</ XPath></DeviceConfig>

Similar information for the same LayerParameter may need to be given for different types of devices. In that case, the

above XML fragment can be repeated with the same Index. The Index along with the DeviceType and Version will be

unique.



Input Details for Flow Domain-Related Operations

Table 17: Flow Domain Elements Supported

Attribute Notes

name FD/OSS defined name

userLabel OSS defined name

isForceUniqueness False

owner Juniper Inc.

aliasNameList Null

NetworkAccessDomain Null

mfdRefList Null

assignedCptpRefList Null

TerminationPointDataListType Null

Table 18: Matrix Flow Domain Elements Supported

Attribute Notes




owner Juniper Inc.

aliasNameList Null


unassignedCptpRefList

transmissionParameterList

Table 19: Flow Domain Fragment Elements Supported

Attribute Notes




owner Juniper Inc.

aliasNameList Null


direction Always CD_BI

administrativeState

transmissionParameters List of layer parameters applicable to FDFr

isFullRoute

FlowDomainFragmentType Always FDFRT_POINT_TO_POINT

connectivityRequirement

aEndREfList Interface Name

zEndRefList Interface Name

mfdfrList List of Matrix Flow Domain fragments attached to this flow domain fragment



Table 20: Matrix Flow Domain Fragment Elements Supported

Attribute Notes


direction Always CD_BI

transmissionParameters List of layer parameters applicable to FDFr

aEndREfList Interface name with complete hierarchy

zEndRefList Interface name with complete hierarchy

isFlexible

isActive

mfdfrList

Request SamplesThe sample request format for the operations supported by MTOSI Adapter is given below.

Operations System Retrieval Service• getAllOperationsSystems

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/osr/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetAllOperationsSystem</v1:activityName> <v1:msgName>GetAllOperationsSystemRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:9999/axis2/services/OperationsSystemRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:9999/axis2/services/OperationsSystemRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:9999/axis2/services/OperationsSystemRetrievalHttp </v1:replyToURI> <v1:originatorURI>http://localhost:9999/axis2/services/OperationsSystemRetrievalHttp </v1:originatorURI> <v1:failureReplytoURI>http://localhost:9999/axis2/services/OperationsSystemRetrievalHttp </v1:failureReplytoURI> <v1:correlationId>452435435</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:getAllOperationsSystemsRequest></v11:getAllOperationsSystemsRequest> </soapenv:Body></soapenv:Envelope>



• getOperationsSystem

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/osr/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetOperationsSystem</v1:activityName> <v1:msgName>GetOperationsSystemRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:9999/axis2/services/OperationsSystemRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:9999/axis2/services/OperationsSystemRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:9999/axis2/services/OperationsSystemRetrievalHttp </v1:replyToURI> <v1:originatorURI>http://localhost:9999/axis2/services/OperationsSystemRetrievalHttp </v1:originatorURI> <v1:failureReplytoURI>http://localhost:9999/axis2/services/OperationsSystemRetrievalHttp </v1:failureReplytoURI> <v1:correlationId>636654653</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:getOperationsSystemRequest></v11:getOperationsSystemRequest> </soapenv:Body></soapenv:Envelope>

Managed Domain Retrieval Service• getAllManagementDomains

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/mdr/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetAllManagementDomain</v1:activityName> <v1:msgName>GetAllManagementDomainRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/ManagementDomainRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/ManagementDomainRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/ManagementDomainRetrievalHttp </v1:replyToURI> <v1:correlationId>123345345</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body>



<v11:getAllManagementDomainsRequest> <v11:mdRef> </v11:mdRef> </v11:getAllManagementDomainsRequest> </soapenv:Body></soapenv:Envelope>

• getManagementDomain

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/mdr/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetManagementDomains</v1:activityName> <v1:msgName>GetManagementDomainsRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/ManagementDomainRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/ManagementDomainRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/ManagementDomainRetrievalHttp </v1:replyToURI> <v1:correlationId>1243245234</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:getManagementDomainRequest> <v11:mdRef> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net.123</v12:value> </v12:rdn> </v11:mdRef> </v11:getManagementDomainRequest> </soapenv:Body></soapenv:Envelope>



Managed Element Retrieval Service• getAllManagedElements

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/mer/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetAllManagedElements</v1:activityName> <v1:msgName>GetAllManagedElementsRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/ManagedElementRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/ManagedElementRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/ManagedElementRetrievalHttp </v1:replyToURI> <v1:correlationId>676676</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:getAllManagedElementsRequest> <v11:mdOrMlsnRef> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net</v12:value> </v12:rdn> </v11:mdOrMlsnRef> </v11:getAllManagedElementsRequest> </soapenv:Body></soapenv:Envelope>

• getManagedElement

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/mer/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetManagedElement</v1:activityName> <v1:msgName>GetManagedElementRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/ManagedElementRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/



ManagedElementRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/ManagedElementRetrievalHttp </v1:replyToURI> <v1:correlationId>7987887</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:getManagedElementRequest> <v11:meRef> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> <v12:rdn> <v12:type>ME</v12:type> <v12:value>192.168.1.1</v12:value> </v12:rdn> </v11:meRef> </v11:getManagedElementRequest> </soapenv:Body></soapenv:Envelope>

Equipment Inventory Retrieval Service• getAllEquipment (All EquipmentHolders List)

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/eir/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetAllEquipment</v1:activityName> <v1:msgName>GetAllEquipmentRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:replyToURI> <v1:correlationId>98677</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body>



<v11:getAllEquipmentRequest> <v11:meOrEhRef> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net</v12:value> </v12:rdn> <v12:rdn> <v12:type>ME</v12:type> <v12:value>192.168.1.1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EQH</v12:type> <v12:value></v12:value> </v12:rdn> </v11:meOrEhRef> </v11:getAllEquipmentRequest> </soapenv:Body></soapenv:Envelope>

• getAllEquipment (All Equipments List)

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/eir/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetAllEquipment</v1:activityName> <v1:msgName>GetAllEquipmentRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:replyToURI> <v1:correlationId>98677</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:getAllEquipmentRequest> <v11:meOrEhRef> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn>



<v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net</v12:value> </v12:rdn> <v12:rdn> <v12:type>ME</v12:type> <v12:value>192.168.1.1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EQH</v12:type> <v12:value>557062/Chassis/FPC 0</v12:value> </v12:rdn> <v12:rdn> <v12:type>CEQ</v12:type> <v12:value></v12:value> </v12:rdn> </v11:meOrEhRef> </v11:getAllEquipmentRequest> </soapenv:Body></soapenv:Envelope>

• getEquipment (Equipment Holder Details)

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/eir/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetEquipment</v1:activityName> <v1:msgName>GetEquipmentRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:replyToURI> <v1:correlationId>45657567</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:getEquipmentRequest> <v11:equipmentOrEhRef> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn>



<v12:rdn>

<v12:type>MD</v12:type>

<v12:value>juniper.net</v12:value>

</v12:rdn>

<v12:rdn>

<v12:type>ME</v12:type>

<v12:value>192.168.1.1</v12:value>

</v12:rdn>

<v12:rdn>

<v12:type>EQH</v12:type>

<v12:value>2883610/Chassis/FPC 1</v12:value>

</v12:rdn>

</v11:equipmentOrEhRef>

</v11:getEquipmentRequest>

</soapenv:Body>

</soapenv:Envelope>

• getEquipment (Equipment Details)

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/eir/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetEquipment</v1:activityName> <v1:msgName>GetEquipmentRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:replyToURI> <v1:correlationId>567567</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:getEquipmentRequest> <v11:equipmentOrEhRef> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type>



<v12:value>juniper.net</v12:value> </v12:rdn> <v12:rdn> <v12:type>ME</v12:type> <v12:value>192.168.1.1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EQH</v12:type> <v12:value>2883610/Chassis/FPC 0/PIC 2</v12:value> </v12:rdn> <v12:rdn> <v12:type>CEQ</v12:type> <v12:value>2883610/Chassis/FPC 0/PIC 2/Xcvr 4</v12:value> </v12:rdn> </v11:equipmentOrEhRef> </v11:getEquipmentRequest> </soapenv:Body></soapenv:Envelope>

• getContainedEquipment (Contained Equipment Holder)

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/eir/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetContainedEquipment</v1:activityName> <v1:msgName>GetContainedEquipmentRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:replyToURI> <v1:correlationId>3453453</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:getContainedEquipmentRequest> <v11:ehRef> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net</v12:value> </v12:rdn> <v12:rdn>



<v12:type>ME</v12:type> <v12:value>192.168.1.1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EQH</v12:type> <v12:value>557062/Chassis/FPC 0</v12:value> </v12:rdn> </v11:ehRef> </v11:getContainedEquipmentRequest> </soapenv:Body></soapenv:Envelope>

• getContainedEquipment (Contained Equipment)

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/eir/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetContainedEquipment</v1:activityName> <v1:msgName>GetContainedEquipmentRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/EquipmentInventoryRetrievalHttp </v1:replyToURI> <v1:correlationId>3453453</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:getContainedEquipmentRequest> <v11:ehRef> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net</v12:value> </v12:rdn> <v12:rdn> <v12:type>ME</v12:type> <v12:value>192.168.1.1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EQH</v12:type> <v12:value>557062/Chassis/FPC 1</v12:value> </v12:rdn>



<v12:rdn> <v12:type>CEQ</v12:type> <v12:value></v12:value> </v12:rdn>

</v11:ehRef> </v11:getContainedEquipmentRequest> </soapenv:Body></soapenv:Envelope>

Resource Inventory Retrieval Service• getInventory

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/rir/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetInventory</v1:activityName> <v1:msgName>GetInventoryRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI> http://localhost:8080/axis2/services/ResourceInventoryRetrievalHttp </v1:senderURI> <v1:destinationURI> http://localhost:8080/axis2/services/ResourceInventoryRetrievalHttp </v1:destinationURI> <v1:replyToURI> http://localhost:8080/axis2/services/ResourceInventoryRetrievalHttp </v1:replyToURI> <v1:originatorURI> http://localhost:8080/axis2/services/ResourceInventoryRetrievalHttp </v1:originatorURI> <v1:correlationId>56757657465</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:getInventoryRequest> <v11:filter> <v11:baseInstance> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> </v11:baseInstance> </v11:filter> <v11:diffDateAndTime/> </v11:getInventoryRequest> </soapenv:Body></soapenv:Envelope>



Common Resource Provisioning Service• setCommonAttributes

The request sample shown below is for updating a PTP:

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/rp/xsd/crp/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1” xmlns:v13=”http://www.tmforum.org/mtop/fmw/xsd/cosd/v1” xmlns:v14=”http://www.tmforum.org/mtop/fmw/xsd/gen/v1” xmlns:v15=”http://www.tmforum.org/mtop/nrb/xsd/crmd/v1”> <soapenv:Header> <v1:header> <v1:activityName>SetCommonAttributes</v1:activityName> <v1:msgName>SetCommonAttributesRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/CommonResourceProvisioningHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/CommonResourceProvisioningHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/CommonResourceProvisioningHttp </v1:replyToURI> <v1:originatorURI>http://localhost:8080/axis2/services/CommonResourceProvisioningHttp </v1:originatorURI> <v1:failureReplytoURI>http://localhost:8080/axis2/services/CommonResourceProvisioningHttp </v1:failureReplytoURI> <v1:correlationId>6767677</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:setCommonAttributesRequest> <v11:objectRef> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net</v12:value> </v12:rdn> <v12:rdn> <v12:type>ME</v12:type> <v12:value>192.168.1.1</v12:value> </v12:rdn> <v12:rdn> <v12:type>PTP</v12:type> <v12:value>ge-0/0/3</v12:value> </v12:rdn> </v11:objectRef> <v11:modifyData> <v13:userLabel>ge-0/0/3-usr</v13:userLabel> <v13:isForceUniqueness>false</v13:isForceUniqueness> <v13:owner>Junos</v13:owner>

<v13:aliasNameList> <v14:alias> <v14:aliasName>createPTP</v14:aliasName> <v14:aliasValue>ge-0/0/2</v14:aliasValue> </v14:alias> </v13:aliasNameList> <v13:vendorExtensions>  </v13:vendorExtensions> <v15:networkAccessDomain>Junos network</v15:networkAccessDomain> </v11:modifyData> </v11:setCommonAttributesRequest> </soapenv:Body></soapenv:Envelope>

Termination Point Control Service• setTerminationPointData

The request sample shown below is for creating a CTP using the SetTerminationPointData request format:

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/rp/xsd/tpc/v1” xmlns:v12=”http://www.tmforum.org/mtop/nrf/xsd/tpdata/v1” xmlns:v13=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1” xmlns:v14=”http://www.tmforum.org/mtop/nrb/xsd/lp/v1” xmlns:v15=”http://www.tmforum.org/mtop/fmw/xsd/gen/v1”> <soapenv:Header> <v1:header> <v1:activityName>SetTerminationPointData</v1:activityName> <v1:msgName>SetTerminationPointDataRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/TerminationPointControlHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/TerminationPointControlHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/TerminationPointControlHttp </v1:replyToURI> <v1:correlationId>6565655</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:setTerminationPointDataRequest> <v11:tpData> <v12:tpRef> <v13:rdn> <v13:type>EMS</v13:type> <v13:value>Junos Space EMS</v13:value> </v13:rdn> <v13:rdn> <v13:type>OSS</v13:type> <v13:value>OS1</v13:value> </v13:rdn> <v13:rdn> <v13:type>MD</v13:type> <v13:value>juniper.net</v13:value>

</v13:rdn> <v13:rdn> <v13:type>ME</v13:type> <v13:value>116.197.179.26</v13:value> </v13:rdn> <v13:rdn> <v13:type>PTP</v13:type> <v13:value>ge-1/3/0</v13:value> </v13:rdn> </v12:tpRef> <v12:tpMappingMode></v12:tpMappingMode> <v14:transmissionParametersList> <v14:transmissionParameters> <v14:layerRate extension=””>LR_DSR_Gigabit_Ethernet</v14:layerRate> <v14:parameterList> <v15:nvs> <v15:name>LogicalUnitNumber</v15:name> <v15:value>0</v15:value> </v15:nvs> <v15:nvs>

<v15:name>IPAddress</v15:name> <v15:value>4.4.4.6</v15:value> </v15:nvs> </v14:parameterList> <v14:vendorExtensions>  </v14:vendorExtensions> </v14:transmissionParameters> </v14:transmissionParametersList> <v12:ingressTmdRef> <v13:rdn> <v13:type></v13:type> <v13:value></v13:value> </v13:rdn> </v12:ingressTmdRef> <v12:egressTmdRef> <v13:rdn> <v13:type></v13:type> <v13:value></v13:value> </v13:rdn> </v12:egressTmdRef> </v11:tpData> </v11:setTerminationPointDataRequest> </soapenv:Body></soapenv:Envelope>



The request sample shown below is for modifying a PTP using the SetTerminationPointData request format:

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/rp/xsd/tpc/v1” xmlns:v12=”http://www.tmforum.org/mtop/nrf/xsd/tpdata/v1” xmlns:v13=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1” xmlns:v14=”http://www.tmforum.org/mtop/nrb/xsd/lp/v1” xmlns:v15=”http://www.tmforum.org/mtop/fmw/xsd/gen/v1”> <soapenv:Header> <v1:header> <v1:activityName>SetTerminationPointData</v1:activityName> <v1:msgName>SetTerminationPointDataRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/TerminationPointControlHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/TerminationPointControlHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/TerminationPointControlHttp </v1:replyToURI> <v1:correlationId>6565655</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:setTerminationPointDataRequest> <v11:tpData> <v12:tpRef> <v13:rdn> <v13:type>EMS</v13:type> <v13:value>Junos Space EMS</v13:value> </v13:rdn> <v13:rdn> <v13:type>OSS</v13:type> <v13:value>OS1</v13:value> </v13:rdn> <v13:rdn> <v13:type>MD</v13:type> <v13:value>juniper.net</v13:value> </v13:rdn> <v13:rdn> <v13:type>ME</v13:type> <v13:value>116.197.178.29</v13:value> </v13:rdn> <v13:rdn> <v13:type>PTP</v13:type> <v13:value>ge-3/3/2</v13:value> </v13:rdn> </v12:tpRef> <v12:tpMappingMode></v12:tpMappingMode> <v14:transmissionParametersList> <v14:transmissionParameters> <v14:layerRate extension=””>LR_DSR_Fast_Ethernet</v14:layerRate> <v14:parameterList> <v15:nvs> <v15:name>MaximumFrameSize</v15:name> <v15:value>256</v15:value>

</v15:nvs> </v14:parameterList> <v14:vendorExtensions>  </v14:vendorExtensions> </v14:transmissionParameters> </v14:transmissionParametersList> </v11:tpData> </v11:setTerminationPointDataRequest> </soapenv:Body></soapenv:Envelope>

Flow Domain Control Service• createFlowDomain

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/rp/xsd/fdc/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/cosd/v1” xmlns:v13=”http://www.tmforum.org/mtop/fmw/xsd/gen/v1” xmlns:v14=”http://www.tmforum.org/mtop/fmw/xsd/cocd/v1” xmlns:v15=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1” xmlns:v16=”http://www.tmforum.org/mtop/nrb/xsd/crcd/v1” xmlns:v17=”http://www.tmforum.org/mtop/nrb/xsd/lp/v1” xmlns:v18=”http://www.tmforum.org/mtop/nrf/xsd/tpdata/v1”> <soapenv:Header> <v1:header> <v1:activityName>CreateFlowDomain</v1:activityName> <v1:msgName>CreateFlowDomainRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/FlowDomainControlHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/FlowDomainControlHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/FlowDomainControlHttp </v1:replyToURI> <v1:correlationId>1234</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:createFlowDomainRequest> <v11:createData> <v12:userLabel></v12:userLabel> <v12:isForceUniqueness>false</v12:isForceUniqueness> <v12:owner>Juniper Inc</v12:owner> <v12:aliasNameList> <v13:alias> <v13:aliasName></v13:aliasName> <v13:aliasValue></v13:aliasValue> </v13:alias> </v12:aliasNameList> <v12:vendorExtensions>  </v12:vendorExtensions> <v14:name> <v15:rdn>



<v15:type>OSS</v15:type> <v15:value>OS1</v15:value> </v15:rdn> <v15:rdn> <v15:type>EMS</v15:type> <v15:value>Junos Space EMS</v15:value> </v15:rdn> <v15:rdn> <v15:type>MD</v15:type> <v15:value>juniper.net</v15:value> </v15:rdn> <v15:rdn> <v15:type>FlowDomain</v15:type> <v15:value>chennaiFlowDomain11</v15:value> </v15:rdn> </v14:name> </v11:createData> </v11:createFlowDomainRequest> </soapenv:Body></soapenv:Envelope>

• createMatrixFlowDomain

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/rp/xsd/fdc/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/cosd/v1” xmlns:v13=”http://www.tmforum.org/mtop/fmw/xsd/gen/v1” xmlns:v14=”http://www.tmforum.org/mtop/fmw/xsd/cocd/v1” xmlns:v15=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1” xmlns:v16=”http://www.tmforum.org/mtop/nrb/xsd/crcd/v1” xmlns:v17=”http://www.tmforum.org/mtop/nrb/xsd/lp/v1” xmlns:v18=”http://www.tmforum.org/mtop/nrf/xsd/tpdata/v1”> <soapenv:Header> <v1:header> <v1:activityName>CreateMatrixFlowDomain</v1:activityName> <v1:msgName>CreateMatrixFlowDomainRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/FlowDomainControlHttp</v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/FlowDomainControlHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/FlowDomainControlHttp </v1:replyToURI> <v1:correlationId>1245</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header> </soapenv:Header> <soapenv:Body> <v11:createMatrixFlowDomainRequest> <v11:createData> <v12:userLabel>MFD_ME_116.197.179.15</v12:userLabel> <v12:isForceUniqueness>false</v12:isForceUniqueness> <v12:owner>Junos Inc</v12:owner> <v12:aliasNameList> <v13:alias> <v13:aliasName></v13:aliasName> <v13:aliasValue></v13:aliasValue>



</v13:alias> </v12:aliasNameList> <v14:name> <v15:rdn> <v15:type>OSS</v15:type> <v15:value>OS1</v15:value> </v15:rdn> <v15:rdn> <v15:type>EMS</v15:type> <v15:value>Junos Space EMS</v15:value> </v15:rdn> <v15:rdn> <v15:type>MD</v15:type> <v15:value>juniper.net</v15:value> </v15:rdn> <v15:rdn> <v15:type>FlowDomain</v15:type> <v15:value>chennaiFlowDomain11</v15:value> </v15:rdn> <v15:rdn> <v15:type>MatrixFlowDomain</v15:type> <v15:value>116.197.179.26</v15:value> </v15:rdn> </v14:name> </v11:createData> </v11:createMatrixFlowDomainRequest> </soapenv:Body></soapenv:Envelope>

• createAndActivateFlowDomainFragment

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/rp/xsd/fdc/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/cosd/v1” xmlns:v13=”http://www.tmforum.org/mtop/fmw/xsd/gen/v1” xmlns:v14=”http://www.tmforum.org/mtop/fmw/xsd/cocd/v1” xmlns:v15=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1” xmlns:v16=”http://www.tmforum.org/mtop/nrb/xsd/crcd/v1” xmlns:v17=”http://www.tmforum.org/mtop/nrb/xsd/lp/v1” xmlns:v18=”http://www.tmforum.org/mtop/nrf/xsd/mfdfr/v1” xmlns:v19=”http://www.tmforum.org/mtop/nrf/xsd/tpdata/v1”> <soapenv:Header> <v1:header> <v1:activityName>CreateFlowDomainFragment</v1:activityName> <v1:msgName>CreateFlowDomainFragmentRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/FlowDomainControlHttp</v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/FlowDomainControlHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/FlowDomainControlHttp </v1:replyToURI> <v1:originatorURI>http://localhost:8080/axis2/services/FlowDomainControlHttp </v1:originatorURI> <v1:correlationId>2546</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> </v1:header>



</soapenv:Header> <soapenv:Body> <v11:createAndActivateFlowDomainFragmentRequest> <v11:createData> <v12:userLabel></v12:userLabel> <v12:isForceUniqueness>false</v12:isForceUniqueness> <v12:owner>Junos Inc</v12:owner> <v14:name> <v15:rdn> <v15:type>OSS</v15:type> <v15:value>OS1</v15:value> </v15:rdn> <v15:rdn> <v15:type>EMS</v15:type> <v15:value>Junos Space EMS</v15:value> </v15:rdn> <v15:rdn> <v15:type>MD</v15:type> <v15:value>juniper.net</v15:value> </v15:rdn> <v15:rdn> <v15:type>FlowDomain</v15:type> <v15:value>chennaiFlowDomain11</v15:value> </v15:rdn> <v15:rdn> <v15:type>FlowDomainFragment</v15:type> <v15:value>407</v15:value> </v15:rdn> </v14:name> <v11:direction>CD_BI</v11:direction> <v17:transmissionParameters> <v17:layerRate>LR_Ethernet</v17:layerRate> <v17:parameterList> <v13:nvs> <v13:name>MaximumFrameSize</v13:name> <v13:value>1522</v13:value> </v13:nvs> <v13:nvs> <v13:name>PhysicalEncapsulation</v13:name> <v13:value>flexible-ethernet-services</v13:value> </v13:nvs> <v13:nvs> <v13:name>LogicalEncapsulation</v13:name> <v13:value>vlan-ccc</v13:value> </v13:nvs> <v13:nvs> <v13:name>PortAcceptableFrameTypes</v13:name> <v13:value>vlanTaggedOnly</v13:value> </v13:nvs> <v13:nvs> <v13:name>AddSTag</v13:name> <v13:value>false</v13:value> </v13:nvs> <v13:nvs> <v13:name>IVID</v13:name> <v13:value>600</v13:value> </v13:nvs> </v17:parameterList>



</v17:transmissionParameters> </v11:createData> <v11:connectivityRequirement>CR_IGNORE</v11:connectivityRequirement> <v11:aEndRefList> <v15:name> <v15:rdn> <v15:type>MD</v15:type> <v15:value>juniper.net</v15:value> </v15:rdn> <v15:rdn> <v15:type>ME</v15:type> <v15:value>116.197.178.8</v15:value> </v15:rdn> <v15:rdn> <v15:type>PTP</v15:type> <v15:value>ge-1/0/3</v15:value> </v15:rdn> </v15:name> </v11:aEndRefList> <v11:zEndRefList> <v15:name> <v15:rdn> <v15:type>MD</v15:type> <v15:value>juniper.net</v15:value> </v15:rdn> <v15:rdn> <v15:type>ME</v15:type> <v15:value>116.197.178.7</v15:value> </v15:rdn> <v15:rdn> <v15:type>PTP</v15:type> <v15:value>ge-1/0/1</v15:value> </v15:rdn> </v15:name> </v11:zEndRefList> <v11:mfdfrList> <v18:mfdfr> <v18:direction></v18:direction> <v17:transmissionParameters> <v17:layerRate extension=”LR_Ethernet”></v17:layerRate> <v17:parameterList> <v13:nvs> <v13:name>IngressCIR</v13:name> <v13:value>10000000</v13:value> </v13:nvs> <v13:nvs> <v13:name>IngressCBS</v13:name> <v13:value>62500000</v13:value> </v13:nvs> </v17:parameterList> </v17:transmissionParameters> <v18:aEndTpRefList> <v15:name> <v15:rdn> <v15:type>MD</v15:type> <v15:value>juniper.net</v15:value> </v15:rdn> <v15:rdn>



<v15:type>ME</v15:type> <v15:value>116.197.178.8</v15:value> </v15:rdn> <v15:rdn> <v15:type>PTP</v15:type> <v15:value>ge-1/0/3</v15:value> </v15:rdn> <v15:rdn> <v15:type>CTP</v15:type> <v15:value>/unit=43/ethvid=221</v15:value> </v15:rdn> </v15:name> </v18:aEndTpRefList> <v18:zEndTpRefList> <v15:name> <v15:rdn> <v15:type>MD</v15:type> <v15:value>juniper.net</v15:value> </v15:rdn> <v15:rdn> <v15:type>ME</v15:type> <v15:value>116.197.178.7</v15:value> </v15:rdn> <v15:rdn> <v15:type>PTP</v15:type> <v15:value>ge-1/0/1</v15:value> </v15:rdn> <v15:rdn> <v15:type>CTP</v15:type> <v15:value>/unit=43/ethvid=221</v15:value> </v15:rdn> </v15:name> </v18:zEndTpRefList> <v18:isFlexible></v18:isFlexible> <v18:isActive></v18:isActive> <v18:mfdfrType></v18:mfdfrType> </v18:mfdfr> </v11:mfdfrList> </v11:createAndActivateFlowDomainFragmentRequest> </soapenv:Body></soapenv:Envelope>

• deleteFlowDomain

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/rp/xsd/fdc/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1” xmlns:v13=”http://www.tmforum.org/mtop/nrf/xsd/tpdata/v1” xmlns:v14=”http://www.tmforum.org/mtop/nrb/xsd/lp/v1” xmlns:v15=”http://www.tmforum.org/mtop/fmw/xsd/gen/v1”> <soapenv:Header> <v1:header> <v1:activityName>DeleteFlowDomain</v1:activityName> <v1:msgName>DeleteFlowDomainRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/FlowDomainControlHttp</v1:senderURI>



<v1:destinationURI>http://localhost:8080/axis2/services/FlowDomainControlHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/FlowDomainControlHttp </v1:replyToURI> <v1:correlationId>21456</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> <v1:timestamp>2011-01-14T12:57:55.166+05:30</v1:timestamp> </v1:header> </soapenv:Header> <soapenv:Body> <v11:deleteFlowDomainRequest> <v11:fdRef> <v12:name> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net</v12:value> </v12:rdn> <v12:rdn> <v12:type>FlowDomain</v12:type> <v12:value>chennaiFlowDomain22</v12:value> </v12:rdn> </v12:name> </v11:fdRef> </v11:deleteFlowDomainRequest> </soapenv:Body></soapenv:Envelope>

• deleteMatrixFlowDomain

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/rp/xsd/fdc/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1” xmlns:v13=”http://www.tmforum.org/mtop/nrf/xsd/tpdata/v1” xmlns:v14=”http://www.tmforum.org/mtop/nrb/xsd/lp/v1” xmlns:v15=”http://www.tmforum.org/mtop/fmw/xsd/gen/v1”> <soapenv:Header> <v1:header> <v1:activityName>DeleteMatrixFlowDomain</v1:activityName> <v1:msgName>deleteMatrixFlowDomainRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/FlowDomainControlHttp</v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/FlowDomainControlHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/FlowDomainControlHttp </v1:replyToURI> <v1:correlationId>?</v1:correlationId>



<v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> <v1:timestamp>2011-01-14T12:57:55.166+05:30</v1:timestamp> </v1:header> </soapenv:Header> <soapenv:Body> <v11:deleteMatrixFlowDomainRequest> <v11:mfdRef> <v12:name> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net</v12:value> </v12:rdn> <v12:rdn> <v12:type>FlowDomain</v12:type> <v12:value>chennaiFlowDomain11</v12:value> </v12:rdn> <v12:rdn> <v12:type>MatrixFlowDomain</v12:type> <v12:value>116.197.178.7</v12:value> </v12:rdn> </v12:name> </v11:mfdRef> </v11:deleteMatrixFlowDomainRequest> </soapenv:Body></soapenv:Envelope>

• deactivateAndDeleteFlowDomainFragment

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/rp/xsd/fdc/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1” xmlns:v13=”http://www.tmforum.org/mtop/nrf/xsd/tpdata/v1” xmlns:v14=”http://www.tmforum.org/mtop/nrb/xsd/lp/v1” xmlns:v15=”http://www.tmforum.org/mtop/fmw/xsd/gen/v1”> <soapenv:Header> <v1:header> <v1:activityName>DeleteFlowDomainFragment</v1:activityName> <v1:msgName>DeleteFlowDomainFragmentRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/FlowDomainControlHttp</v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/FlowDomainControlHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/FlowDomainControlHttp </v1:replyToURI> <v1:correlationId>14785</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern>



<v1:communicationStyle>MSG</v1:communicationStyle> <v1:timestamp>2011-01-14T12:57:55.166+05:30</v1:timestamp> </v1:header> </soapenv:Header> <soapenv:Body> <v11:deactivateAndDeleteFlowDomainFragmentRequest> <v11:fdfrRef> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net</v12:value> </v12:rdn> <v12:rdn> <v12:type>FlowDomain</v12:type> <v12:value>chennaiFlowDomain31</v12:value> </v12:rdn> <v12:rdn> <v12:type>FlowDomainFragment</v12:type> <v12:value>703</v12:value> </v12:rdn> </v11:fdfrRef> </v11:deactivateAndDeleteFlowDomainFragmentRequest> </soapenv:Body></soapenv:Envelope>

Flow Domain Retrieval Service• getFlowDomain

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/fdr/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetFlowDomain</v1:activityName> <v1:msgName>GetFlowDomainRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/FlowDomainRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/FlowDomainRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/FlowDomainRetrievalHttp </v1:replyToURI> <v1:correlationId>47757</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> <v1:timestamp>2011-01-14T12:57:55.166+05:30</v1:timestamp> </v1:header> </soapenv:Header>



<soapenv:Body> <v11:getFlowDomainRequest> <v11:fdRef> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net</v12:value> </v12:rdn> <v12:rdn> <v12:type>FlowDomain</v12:type> <v12:value>chennaiFlowDomain12</v12:value> </v12:rdn> </v11:fdRef> </v11:getFlowDomainRequest> </soapenv:Body></soapenv:Envelope>

• getMatrixFlowDomain

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/fdr/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetMatrixFlowDomain</v1:activityName> <v1:msgName>GetMatrixFlowDomainRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/FlowDomainRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/FlowDomainRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/FlowDomainRetrievalHttp </v1:replyToURI> <v1:correlationId>?</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> <v1:timestamp>2011-01-14T12:57:55.166+05:30</v1:timestamp> </v1:header> </soapenv:Header> <soapenv:Body> <v11:getMatrixFlowDomainRequest> <v11:mfdRef> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value>



</v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net</v12:value> </v12:rdn> <v12:rdn> <v12:type>FlowDomain</v12:type> <v12:value>chennaiFlowDomain12</v12:value> </v12:rdn> <v12:rdn> <v12:type>MatrixFlowDomain</v12:type> <v12:value>116.197.178.8</v12:value> </v12:rdn> </v11:mfdRef> </v11:getMatrixFlowDomainRequest> </soapenv:Body></soapenv:Envelope>

• getFlowDomainFragment

<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:v1=”http://www.tmforum.org/mtop/fmw/xsd/hdr/v1” xmlns:v11=”http://www.tmforum.org/mtop/mri/xsd/fdr/v1” xmlns:v12=”http://www.tmforum.org/mtop/fmw/xsd/nam/v1”> <soapenv:Header> <v1:header> <v1:activityName>GetFlowDomainFragment</v1:activityName> <v1:msgName>GetFlowDomainFragmentRequest</v1:msgName> <v1:msgType>REQUEST</v1:msgType> <v1:senderURI>http://localhost:8080/axis2/services/FlowDomainRetrievalHttp </v1:senderURI> <v1:destinationURI>http://localhost:8080/axis2/services/FlowDomainRetrievalHttp </v1:destinationURI> <v1:replyToURI>http://localhost:8080/axis2/services/FlowDomainRetrievalHttp </v1:replyToURI> <v1:correlationId>21312</v1:correlationId> <v1:communicationPattern>SimpleResponse</v1:communicationPattern> <v1:communicationStyle>MSG</v1:communicationStyle> <v1:timestamp>2011-01-14T12:57:55.166+05:30</v1:timestamp> </v1:header> </soapenv:Header> <soapenv:Body> <v11:getFlowDomainFragmentRequest> <v11:fdfrRef> <v12:rdn> <v12:type>OSS</v12:type> <v12:value>OS1</v12:value> </v12:rdn> <v12:rdn> <v12:type>EMS</v12:type> <v12:value>Junos Space EMS</v12:value> </v12:rdn> <v12:rdn> <v12:type>MD</v12:type> <v12:value>juniper.net</v12:value> </v12:rdn> <v12:rdn>



<v12:type>FlowDomain</v12:type> <v12:value>chennaiFlowDomain11</v12:value> </v12:rdn> <v12:rdn> <v12:type>FlowDomainFragment</v12:type> <v12:value>408</v12:value> </v12:rdn> </v11:fdfrRef> </v11:getFlowDomainFragmentRequest> </soapenv:Body></soapenv:Envelope>

MTOSI Solution Architecture Juniper’s MTOSI Adapter solution deploys the MTOSI Adapter over the Junos Space Network Management Platform.

Junos Space, the MTOSI Common Communication Vehicle (CCV), and the MTOSI Adapter are all running together

in the same JBoss environment. The Northbound Interface (NBI) of MTOSI Adapter is a Web service, and it can be

tested by using the OSS Client Stub. The OSS Client Stub sends the required HTTP messages to the MTOSI CCV.

Since the real OSS cannot be deployed due to various concerns, the OSS Client Stub is being developed for testing the

MTOSI Adapter. The SouthBound Interface SBI is a RESTful interface which interacts with the Junos Space Network

Management Platform. This SBI can be tested using the DMI simulator, which is available with Junos Space and can be

configured to act as different elements of the network for testing the MTOSI Adapter.

Junos Space MTOSI Adapter CCV

Junos Space Application

Junos JBossEnvironment

NBI

OSS Stub

DMI Simulator

Junos Space MTOSI Adapter

Junos Space Platform

SBI

Figure 5: MTOSI Simulation TestingJunos Space MTOSI Adapter fills the gap between the MTOSI OSS and Junos Space Network Management Platform

has a message-oriented middleware (MOM) system between the OSS and Junos Space. This system translates

the MTOSI messages into Junos Space-specific messages and vice versa. It provides a channel for exchanging the

respective translated messages between OSS and Junos Space. The MTOSI Adapter is deployed in the same JBoss

server where the Junos Space Network Management Platform is deployed.



Juniper Device Modeling Using MTOSIThis section explains how Juniper devices are modeled following the MTOSI model. Figure 6 shows the physical layout

of Juniper devices modeled for MTOSI.

Managed Element

Managed Domain

Network Element

Router / Switch

Managed Element

Network Element

Router / Switch

Managed Element

Network Element

Router / Switch

Figure 6: Juniper Device Modeling Using MTOSI

Tabel 21: MTOSI-Junos Space Element Mapping

MTOSI Element Reference MTOSI Element Junos Space Element

MD Managed Domain /managed-domain

ME Managed Element /managed-element/{id}

NE Network Element Device ID

PTP Physical Termination Point /ptp

CTP Connection Termination Point /ptp/{ptpid}/ctp

FTP Floating Termination Point Not supported

CPTP Connectionless Port Termination Point /ptp/{ptpid}/ctp

SNC Subnetwork Connection Not supported

FD Flow Domain Not supported

FP Flow Point Not supported

MFD Matrix Flow Domain Not supported

TL Topological Link Not supported

FPC FPC board Interface name interfacetype-fpc/slot/port:logical-channel

Slot Slot in the FPC board Interface name interfacetype-fpc/slot/port:logical-channel

Port Port in the slot Interface name interfacetype-fpc/slot/port:logical-channel

EH Equipment Holder

EQ Contained Equipment



Use CasesModifying the physical properties of the termination point from the OSS systems.Device/Router Command• set interface <interface name> link-mode full-duplex

• set interface <interface name> link-model half-duplex

The interface name could be ge-1/0/1.

MappingThe MTOSI operation “setTerminationPointData” is used to modify the termination point layer parameters. The

link-mode is one of the layer parameters defined under the different layer rates like LR_DSR_Fast_Ethernet, LR_DSR_

Gigabit_Ethernet, LR_DSR_10Gigabit_Ethernet, etc.

Table 22: MTOSI Services and Termination Points Mapping

MTOSI Services Termination Point

MTOSI operation setTerminationPointData

Network element (NE) key value Device ID

PTP identifier

FPC, slot, and port

Interface name

Layer rate

(The same will be used to identify the interface type like ge, so, fe, etc.)

LR_ETHERNET, LR_DSR_Fast_Ethernet, LR_DSR_Gigabit_Ethernet, LR_DSR_10Gigabit_Ethernet etc

Parameter name Link-mode

Accepted value Full/half

Junos Space device configuration command /api/space/configuration-management/change-requests

Junos Space configuration payload <change-request>

<deviceId>786433</deviceId>

<name>HCL</name>

<description/>

<xmlData><![CDATA Junos Space Device ConfigurationPayload]]></xmlData>

<syncAfterPush>true</syncAfterPush>

</change-request>

Junos Space device configuration payload <configuration>

<interfaces>

<name>ge-1/0/3</name>

<interface-range>

<ether-options>

<link-mode>full-duplex</link-mode>

</ether-options>

</interface-range>

</interfaces>

</configuration>



Figure 7: Shows the Inventory and Discovery OSS Screen Displaying the Discovered Network From Junos Space.

Figure 8: Shows the Inventory and Discovery OSS Screen Displaying the Physical Interfaces of the Network Element(s) Retrieved From Junos Space Using REST APIs.



Figure 9: Inventory and Discovery OSS Screen Showing Physical Interfaces of the Network Element(s) Retrieved From Junos Space Using REST APIs.

Figure 10: Shows the Inventory and Discovery OSS Screen Displaying the Hardware Inventory of the Network Elements Retrieved From Junos Space Using REST APIs.



Figure 11: Shows a View of Inventory Interface Properties on the Inventory and Discovery OSS.

Figure 12: Shows the Inventory and Discovery OSS Screen Where Device Notifications are Made Whaen Changes Occur in Junos Space for Cases Like Those Listed Below:

• Device discovery (new device added onto Junos Space)

• Device configuration change (configuration change on the device)

• Device deletion (any device deleted from Junos Space)



Configuring the L2VPN:To configure the L2VPN in Junos Space, we need to discover the devices for both of the remote end connections (AEnd

and ZEnd). To do this:

• Add 116.197.178.7 and 116.197.178.8 and verify that the corresponding entries for the devices (PTP, CTP) are present in the

MTOSI database

• Query the interfaces to be used for creating an L2VPN connection using a SOAP request

(TerminationPointRetrievalSoapHttpBinding – getAllPTP)

Then verify that the SOAP response is valid for these interfaces (for example, physical interface ge-1/0/1 for

116.197.178.7 and interface ge-1/0/3 for 116.197.178.8).

Now create a Flow Domain, two Matrix Flow Domains (representing the NEs/devices for the end connections), and

Flow Domain Fragment(s) for the actual L2 circuit connection.

Creating the Flow Domain:

• Set the service endpoint for the SOAP request FlowDomainControlSoapHttpBinding to:

http://localhost:9999/axis2/services/FlowDomainControlHttp

Create a Flow Domain using the request createFlowDomain

Figure 13: Creating a Flow Domain



Creating a Matrix Flow Domain:

• Set the service endpoint for the Soap request FlowDomainControlSoapHttpBinding to:

http://localhost:9999/axis2/services/FlowDomainControlHttp

• Create a Matrix Flow Domain using the request createMatrixFlowDomain

• Then create two Matrix Flow Domains—one for each of the devices (NEs) at each endpoint

Figure 14: Creating a Matrix Flow Domain



Creating a Flow Domain Fragment:

• Set the service endpoint for the SOAP request FlowDomainControlSoapHttpBinding to:

http://localhost:9999/axis2/services/FlowDomainControlHttp.

• Use the request createAndActivateFlowDomainFragment for creating a Flow Domain Fragment. The new Flow Domain

Fragment’s value in the request will have the Virtual-circuit-Id’s (VC Id) value.

• The SOAP request timeout needs to be adequately set for the configuration at the device endpoints for it to complete

and for the SOAP response to be returned back. The response timeout in the SOAP UI is set through the menu: File ->

Preferences -> SoapUIPreferences page -> Socket Timeout field. The value can be set between 6-10 minutes.

• The device configuration can be checked by using the CLI to verify the configuration on the respective devices.

Figure 15: Creating a Flow Domain Fragment (screen one)

Note: FlowDomainFragment’s value would correspond to its Virtual Circuit Id (VC Id)



Figure 16: Creating a Flow Domain Fragment

Figure 17: Creating a Flow Domain Fragment



CTP Request—Unit number/VLAN IDThe VLAN ID is specified with the MFDFr/CTP request embedded in the FDFr request. The Connection Termination

Point value given in the request (/unit=35/ethvid=35) specifies that the logical interface (unit) be created as 35 and

the VLAN ID be configured as 235. Once the createFlowDomainFragment request is executed from the SOAP Request,

you can verify the creation of new jobs being scheduled in the Job Management panel in the Junos Space Network

Management Platform UI, for the update of the network elements.

Figure 18: Manageing Jobs in Space Network Management Platform



Querying the Flow Domain:

• Set the service endpoint for the SOAP request FlowDomainRetrievalSoapHttpBinding to:

http://localhost:9999/axis2/services/FlowDomainRetrievalHttp

• Use the request getFlowDomain

Figure19: Querying the Flow Domain



Querying the Matrix Flow Domain:



• Use the request getMatrixFlowDomain

Figure 20: Querying the Matrix Flow Domain



Querying the Flow Domain Fragment:



• Use the request getFlowDomainFragment

Figure 21: Querying the Flow Domain Fragment

References To learn more about the MTOSI standard and see case studies, presentations, and webinar offerings, please visit: www.tmforum.org/MultiTechnologyOperations/2319/home.html.

To learn more about Junos Space Network Management Platform and the Junos Space SDK, please visit:

www.juniper.net.



8010093-001-EN Apr 2013

Copyright 2013 Juniper Networks, Inc. All rights reserved. Juniper Networks, the Juniper Networks logo, Junos, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.

APAC and EMEA Headquarters

Juniper Networks International B.V.

Boeing Avenue 240

1119 PZ Schiphol-Rijk

Amsterdam, The Netherlands

Phone: 31.0.207.125.700

Fax: 31.0.207.125.701

Corporate and Sales Headquarters

Juniper Networks, Inc.

1194 North Mathilda Avenue

Sunnyvale, CA 94089 USA

Phone: 888.JUNIPER (888.586.4737)

or 408.745.2000

Fax: 408.745.2100

www.juniper.net

To purchase Juniper Networks solutions,

please contact your Juniper Networks

representative at 1-866-298-6428 or

authorized reseller.

Printed on recycled paper

About Juniper NetworksJuniper Networks is in the business of network innovation. From devices to data centers, from consumers to cloud

providers, Juniper Networks delivers the software, silicon and systems that transform the experience and economics of

networking. The company serves customers and partners worldwide. Additional information can be found at

www.juniper.net.

mtosi adapter using junos space sdk - juniper networks · tabel 21: mtosi-junos space ... mtosi...

Documents