Oracle© Communications IP Service Activator
Version 7.2
Solution Uptake Guide for MPLS VPN
with Ethernet Access
August 2012
Solution Uptake Guide
IP Service Activator 7.2 2
Oracle Communications IP Service Activator Solution Uptake Guide, Release...
Solution Uptake Guide
IP Service Activator 7.2 3
Contents
1. Introduction ...................................................
Solution Uptake Guide
IP Service Activator 7.2 4
6.2.7. Create L3 MPLS VPN Site with choice of routing protocol .............
Solution Uptake Guide
IP Service Activator 7.2 5
11. OSM Design – Modifying an L3 MPLS VPN Site .............................
Solution Uptake Guide
IP Service Activator 7.2 6
16.2.5. Other Tasks.........................................................
Solution Uptake Guide
IP Service Activator 7.2 7
1. Introduction
The implementation for MPLS VPN with Ethernet access is d...
Solution Uptake Guide
IP Service Activator 7.2 8
Resolving all IP Service Activator activation errors returned to OSM are ...
Solution Uptake Guide
IP Service Activator 7.2 9
Acronym Definition
ISC Internet Systems Consortium
NE Network Element
NID...
Solution Uptake Guide
IP Service Activator 7.2 10
2. Solution Architecture
This section defines the solution architecture....
Solution Uptake Guide
IP Service Activator 7.2 11
Oracle Product Description/Function
IP Service Activator Responsible for...
Solution Uptake Guide
IP Service Activator 7.2 12
Figure 3: Service Scenario Details
Refer to Summary of Activation of Tec...
Solution Uptake Guide
IP Service Activator 7.2 13
Management VPN connectivity is hub and spoke, the customer VPN connectiv...
Solution Uptake Guide
IP Service Activator 7.2 14
3. Installation
MPLS VPN with Metro Ethernet Implementation is not inten...
Solution Uptake Guide
IP Service Activator 7.2 15
either create their own licensed VM, or run the applications natively on...
Solution Uptake Guide
IP Service Activator 7.2 16
Order and Service
Management
Linux,
Oracle
Database
Server,
WebLogic,
JB...
Solution Uptake Guide
IP Service Activator 7.2 17
7.2.0.version.zip
MPLS VPN solution README README.txt
Note: The IP Servi...
Solution Uptake Guide
IP Service Activator 7.2 18
o Administration Server
 Set the WebLogic Administrator user and passwo...
Solution Uptake Guide
IP Service Activator 7.2 19
11. Start the managed servers.
The managed servers must be restarted for...
Solution Uptake Guide
IP Service Activator 7.2 20
Refer to OSM post-installation tasks in the Oracle Communications Order ...
Solution Uptake Guide
IP Service Activator 7.2 21
Messaging Resource Adapter
To prepare the managed server for the Web ser...
Solution Uptake Guide
IP Service Activator 7.2 22
directory for OSM. user_projects/domains/
osmipsadomain
user_projects/do...
Solution Uptake Guide
IP Service Activator 7.2 23
Before you run the Installer, all managed servers (that is, for IP Servi...
Solution Uptake Guide
IP Service Activator 7.2 24
run the Installer, the following warning message appears when undeployin...
Solution Uptake Guide
IP Service Activator 7.2 25
SDK Tools and Samples
Administrator Client
Note: On a Windows platform, ...
Solution Uptake Guide
IP Service Activator 7.2 26
1. Verify that you can log in to the OSM Administrator using the admin u...
Solution Uptake Guide
IP Service Activator 7.2 27
value as needed (for example, for a 4 GB system a value of 3048m may be ...
Solution Uptake Guide
IP Service Activator 7.2 28
WebLogic Home: OracleMiddlewareHomewlserver_10.3
Java JDK Home: JavaHome...
Solution Uptake Guide
IP Service Activator 7.2 29
OSM_homeSDKXMLImportExportcredStoreAdmin eclipse workspace
folderOracleC...
Solution Uptake Guide
IP Service Activator 7.2 30
2. Deploy a single cartridge using the sceadmin user, namely:
OracleComm...
Solution Uptake Guide
IP Service Activator 7.2 31
Solution Uptake Guide
IP Service Activator 7.2 32
4. Use Case Overview
Each use case scenario corresponds to a provisionin...
Solution Uptake Guide
IP Service Activator 7.2 33
Change routing protocol Illustrate a Change that affects both a customer...
Solution Uptake Guide
IP Service Activator 7.2 34
Cancel order before completion Illustrate the use of the Activation Task...
Solution Uptake Guide
IP Service Activator 7.2 35
Equipment CTM Template for base
config managed CE
CTM Template for
Routi...
Solution Uptake Guide
IP Service Activator 7.2 36
4.1.2. Design Approach
This section describes the design approach.
4.1.3...
Solution Uptake Guide
IP Service Activator 7.2 37
5. Provisioning Orders
This section discusses provisioning orders.
5.1 C...
Solution Uptake Guide
IP Service Activator 7.2 38
Table 10: Parent/Child Relationships
Parent Child Remarks
L3 MPLS
VPN
L3...
Solution Uptake Guide
IP Service Activator 7.2 39
ImportExport
RTNumber2
Address Family
Ipv4, Ipv6,
Ipv4_Ipv6
Address fami...
Solution Uptake Guide
IP Service Activator 7.2 40
Interface Private
IPv4 Mask
text PE interface private IPv4 mask
Interfac...
Solution Uptake Guide
IP Service Activator 7.2 41
6. L3 MPLS VPN Detailed Use Cases - Order Scenarios
This section describ...
Solution Uptake Guide
IP Service Activator 7.2 42
o This is applicable to orders which include order line(s) to ADD Metro ...
Solution Uptake Guide
IP Service Activator 7.2 43
o SNMP ifType: 6 (6 is ethernet such as FastEthernet or GigabitEthernet)...
Solution Uptake Guide
IP Service Activator 7.2 44
6.2 Basic Orchestration, variations on sites & L3 MPLS VPNs
Summary
This...
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Solution Uptake Guide for MPLS VPN with Ethernet Access
Upcoming SlideShare
Loading in...5
×

Solution Uptake Guide for MPLS VPN with Ethernet Access

377

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
377
On Slideshare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Solution Uptake Guide for MPLS VPN with Ethernet Access

  1. 1. Oracle© Communications IP Service Activator Version 7.2 Solution Uptake Guide for MPLS VPN with Ethernet Access August 2012
  2. 2. Solution Uptake Guide IP Service Activator 7.2 2 Oracle Communications IP Service Activator Solution Uptake Guide, Release 7.2 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to thirdparty content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of thirdparty content, products, or services.
  3. 3. Solution Uptake Guide IP Service Activator 7.2 3 Contents 1. Introduction ............................................................................................................. 7 1.1 Overview and Purpose ............................................................................................... 7 1.2 Project Goals.............................................................................................................. 7 1.3 Assumptions and Restrictions..................................................................................... 7 1.4 Glossary of Acronyms ................................................................................................ 8 2. Solution Architecture............................................................................................ 10 2.1 Solution Overview......................................................................................................10 2.2 Service Scenario Details............................................................................................11 2.3 Service Scenario Topology........................................................................................12 2.4 Solution Components Overview.................................................................................13 2.4.1. Inventory...........................................................................................................................13 2.4.2. IP Service Activation ........................................................................................................13 2.4.3. Integration and Interfaces ................................................................................................13 2.5 Architecture Principles...............................................................................................13 3. Installation ............................................................................................................. 14 3.1 Virtual Machine Distributions .....................................................................................14 3.1.1. Virtual Machine Distribution Restrictions..........................................................................14 3.2 Installation and Configuration ....................................................................................15 3.2.1. MPLS VPN with Ethernet Access Solution Media Pack ..................................................16 3.2.2. Core Configuration ...........................................................................................................17 3.2.3. Windows Configuration ....................................................................................................24 3.2.4. Seed Data for L3 MPLS VPN Implementation .................................................................30 3.2.5. Patching the IP Service Activator Design Studio Cartridge .............................................30 4. Use Case Overview ............................................................................................... 32 4.1 General Use Case Information ..................................................................................34 4.1.1. Overall Business Context.................................................................................................34 4.1.2. Design Approach..............................................................................................................36 4.1.3. Actors ...............................................................................................................................36 4.1.4. Error Handling ..................................................................................................................36 5. Provisioning Orders.............................................................................................. 37 5.1 Considerations ..........................................................................................................37 5.2 Provisioning Order Structure .....................................................................................37 5.2.1. Service Definitions............................................................................................................37 5.2.2. Parent/Child relationships in Provisioning Order .............................................................37 5.2.3. Service Actions, and Provisioning Order Attributes .........................................................38 6. L3 MPLS VPN Detailed Use Cases - Order Scenarios........................................ 41 6.1 Seed Data: ................................................................................................................41 6.2 Basic Orchestration, variations on sites & L3 MPLS VPNs ........................................44 6.2.1. Create and link new L3 MPLS VPN (mesh) for a new customer .....................................45 6.2.2. Create and link new L3 MPLS VPN (mesh) for existing customer ..................................47 6.2.3. Create and link new single EBGP L3 MPLS VPN Site to existing customer’s L3 MPLS VPN .......................................................................................................................48 6.2.4. Create and link multiple new L3 MPLS VPN Sites to existing customer’s L3 MPLS VPN ..................................................................................................................................50 6.2.5. Delete single L3 MPLS VPN Site .....................................................................................52 6.2.6. Delete entire L3 MPLS VPN.............................................................................................54
  4. 4. Solution Uptake Guide IP Service Activator 7.2 4 6.2.7. Create L3 MPLS VPN Site with choice of routing protocol ..............................................56 6.2.8. Order that mixes operations (e.g., some adds and some deletes of L3 MPLS VPN Sites) ................................................................................................................................58 6.3 Order Enrichment (Manual Addition of Data) .............................................................61 6.3.1. View Framework selection of PE interfaces...........................................................................62 6.4 Modifies of a L3 MPLS VPN Site ...............................................................................65 6.4.1. Modify routing protocol.....................................................................................................66 6.5 Managed Sites ..........................................................................................................68 6.5.1. Create and link new L3 MPLS VPN Site which includes a managed CE to existing customer’s L3 MPLS VPN, and to existing management VPN........................................69 6.6 L3 Site Quality of Service ..........................................................................................73 6.6.1. Add QoS to all sites in a VPN (all sites are unmanaged).................................................75 6.7 Failure Isolation and Recovery Options .....................................................................78 6.7.1. Failure Resolution for Activation Order Failure ................................................................78 6.8 Metro Ethernet Support .............................................................................................80 6.8.1. Create a new VLAN subinterface when creating and linking new L3 MPLS VPN Site to customer’s L3 MPLS VPN............................................................................................80 6.8.2. Add a managed L3 MPLS VPN Site with an access network..........................................84 6.9 Compensation ...........................................................................................................89 6.9.1. Cancel order before completion .......................................................................................89 7. L3 MPLS VPN Implementation OSM Cartridges ................................................. 92 8. OSM Technical Design/Notes – Basic Orchestration......................................... 93 8.1 Design – AddVpn, AddSite, DeleteVpn, DeleteSite....................................................93 8.1.1. Solution configuration data...............................................................................................93 8.1.2. Order Item Associations...................................................................................................93 8.1.3. IP Service Activator Queries ............................................................................................93 8.1.4. Orchestration Plans..........................................................................................................94 9. OSM Technical Design – Basic Orchestration.................................................... 97 9.1 Design – Automated Query .......................................................................................97 9.1.1. Generic Query Task .........................................................................................................97 9.1.2. Specific Query Tasks .......................................................................................................97 9.1.3. Embedding activation task within sub-processes ............................................................97 9.1.4. New Fulfillment Function..................................................................................................98 9.2 Cartridge Enhancements - Query ..............................................................................98 9.2.1. Data Schema....................................................................................................................98 9.2.2. Activation Task.................................................................................................................98 9.2.3. Sub-processes .................................................................................................................99 9.2.4. Sample Orders .................................................................................................................99 9.3 Implementation – Fully Qualified Orders....................................................................99 9.3.1. XQueries ........................................................................................................................100 9.3.2. Manual Tasks.................................................................................................................100 9.3.3. Service Action ................................................................................................................100 10. OSM Technical Design – L3 Site Quality of Service......................................... 101 10.1 Design – Apply pre-defined QoS policies to unmanaged sites.................................101 10.1.1. Use MQC-PHB Group....................................................................................................101 10.1.2. Data Schema..................................................................................................................101 10.1.3. Order Item Associations.................................................................................................102 10.1.4. Orchestration Plan..........................................................................................................102 10.1.5. Activation Task...............................................................................................................103 10.1.6. Provide IDs to Activation Task for Pre-defined IP Service Activator Objects ................104
  5. 5. Solution Uptake Guide IP Service Activator 7.2 5 11. OSM Design – Modifying an L3 MPLS VPN Site ............................................... 107 11.1 Design.....................................................................................................................107 11.1.1. IP Service Activator Queries ..........................................................................................107 11.1.2. Orchestration Plan..........................................................................................................107 11.2 Implementation........................................................................................................107 11.2.1. Order Enrichment Function ............................................................................................107 11.2.2. ActivateL3Site Function – ActivateSiteConfiguration Task............................................108 11.2.3. Sample Orders ...............................................................................................................109 12. OSM Design – Managed Sites ............................................................................ 110 12.1 Design – Create and Link Site (including managed CE) to L3 MPLS Vpn and Management Vpn ....................................................................................................110 12.1.1. Data Schema..................................................................................................................110 12.1.2. IP Service Activator Queries ..........................................................................................110 12.1.3. Orchestration Plan..........................................................................................................111 12.1.4. Order Item Associations.................................................................................................112 12.1.5. Order Enrichment Function ............................................................................................112 12.1.6. Query Function...............................................................................................................112 12.1.7. ActivateL3SiteFunction...................................................................................................112 12.1.8. DiscoverFunction............................................................................................................112 12.1.9. ActivateCPEFunction .....................................................................................................112 12.1.10. Solution Configuration Data ...........................................................................................114 12.1.11. Sample Orders ...............................................................................................................114 13. OSM Design – Order Enrichment Select Interface ........................................... 115 13.1 Design – View Framework selection of PE Device/Interface....................................115 13.1.1. Solution Configuration....................................................................................................115 13.1.2. Data Provider parameters ..............................................................................................116 13.1.3. FindRequest – Query Device.........................................................................................116 13.1.4. FindRequest – Query Interface ......................................................................................117 13.1.5. FindRequest – Query Linked Interface ..........................................................................117 13.1.6. Model Variable ...............................................................................................................117 13.1.7. Credentials .....................................................................................................................117 13.1.8. Sample Orders ...............................................................................................................118 14. OSM Technical Design – Route Targets............................................................ 119 14.1.1. Data Schema..................................................................................................................119 14.1.2. Order Enrichment...........................................................................................................119 14.1.3. CreateL3VpnFunction ....................................................................................................119 14.1.4. Sample Orders ...............................................................................................................120 15. OSM Design – Order Failure............................................................................... 121 15.1 Default Handling......................................................................................................121 15.1.1. HandleFailureTask .........................................................................................................121 15.2 Failure Handling Options .........................................................................................121 15.2.1. HandleSiteFailureTask...................................................................................................121 15.3 Activation Result Data .............................................................................................122 15.4 Sample Orders to Exercise Failure Options.............................................................123 16. OSM Technical Design – Cancel Activation of a Site....................................... 124 16.1 Triggering Order Cancellation in OSM.....................................................................124 16.2 OSM Entities ...........................................................................................................124 16.2.1. Fulfillment Mode .............................................................................................................124 16.2.2. Amendment Processing .................................................................................................124 16.2.3. Lifecycle Policy...............................................................................................................125 16.2.4. Point of No Return..........................................................................................................125
  6. 6. Solution Uptake Guide IP Service Activator 7.2 6 16.2.5. Other Tasks....................................................................................................................125 16.3 Undo Execution Mode .............................................................................................125 16.3.1. ActivateL3Site Activation Task.......................................................................................125 16.4 Cancellation Failure.................................................................................................126 16.5 Sample Orders ........................................................................................................126 17. OSM Technical Design – Metro Ethernet Use Case ......................................... 127 17.1 SubInterface creation ..............................................................................................127 17.1.1. Data Schema..................................................................................................................127 17.1.2. Order Enrichment...........................................................................................................128 17.2 ActivationSiteConfiguration Task.............................................................................128 17.2.1. New Service Actions ......................................................................................................128 17.2.2. Updated Service Actions................................................................................................128 17.2.3. Service Action ordering ..................................................................................................129 17.2.4. Solution Configuration Data ...........................................................................................129 17.2.5. Sample Orders ...............................................................................................................130 17.3 Metro Ethernet Access Service................................................................................130 17.3.1. Orchestration Plan..........................................................................................................130 17.3.2. Data Schema..................................................................................................................131 17.3.3. Activate MetroE Task .....................................................................................................132 17.3.4. Solution Configuration Data ...........................................................................................133 17.3.5. Sample Orders ...............................................................................................................134
  7. 7. Solution Uptake Guide IP Service Activator 7.2 7 1. Introduction The implementation for MPLS VPN with Ethernet access is designed to consume structured provisioning orders and drive activation operations into the network using Oracle Communications IP Service Activator as the downstream fulfillment system for Oracle Communications Order and Service Management (OSM). This implementation provides a fully functional example of OSM cartridges, which model OSM order fulfillment. The tested and documented solution illustrates the application of best practices for OSM to IP Service Activator integration using broadly deployed services, L3 MPLS VPN with Metro Ethernet access. This document contains solution designs that explain the rationale of the implementation, and relate the design to best practices. For information about best practices, see Guidelines and Best Practices Integration of Oracle Communications IP Service Activator with Oracle Communications Order and Service Management. 1.1 Overview and Purpose The purpose of this document is as follows: Define the business process requirements and use cases Define the solution architecture that supports the proposed solution Specify the project deliverables Provide recommendations for future processes to accommodate the automated activation using OSM and IP Service Activator Use cases are defined for each business process flow. Details about actors, assumptions, functional flows, service actions, parameters, activation interface, exception handling scenarios, and post-conditions are included. These use cases, in conjunction with the process flows, define the behavior of the overall integrated solution. The Architecture sections in this document cover architecture design, functional architecture, technical architecture, and interface implementation. 1.2 Project Goals The MPLS VPN implementation is intended to reduce the risk of issues in customer deployments by providing working patterns to follow, and an implementation that can be extended to meet specific needs. 1.3 Assumptions and Restrictions This document makes the following assumptions. If a use case has any additional assumptions, it is noted in the individual use case: For the current release of the implementation, only IP Service Activator support for service activations is provided. The provisioning orders are created and submitted using Oracle Communications Design Studio. Inventory is provided using manual tasks for feature walk-through, or using fully qualified orders for verification runs, or by querying IP Service Activator. Integration with external inventory management systems is not demonstrated. Given that the MPLS VPN implementation focuses on illustrating integration patterns with OSM, as opposed to illustrating comprehensive functionality available in IP Service Activator, the order data and use cases have been streamlined to provide the maximum number of patterns and examples with minimal duplication the same techniques.
  8. 8. Solution Uptake Guide IP Service Activator 7.2 8 Resolving all IP Service Activator activation errors returned to OSM are first attempted manually, and then with the use of the option to resubmit to IP Service Activator. Interactions with billing, trouble ticketing, alarming, and dispatch systems are not supported by the implementation. As shown in Figure 1, the implementation is not limited to, but is demonstrated with, devices already discovered and in an offline maintenance mode (when using IP Service Activator as pre-configured in the virtual machine): PE: Cisco 7206VXR series routers running IOS CE: Cisco 3640 series routers running IOS U-PE L2 Switch: Cisco 6509 switches Figure 1: Devices in Metro Ethernet Access L3 MPLS VPN The implementation is not designed for, nor intended to be, a production environment. 1.4 Glossary of Acronyms Table 1 defines the acronyms used in this document. Table 1: Document Acronyms Acronym Definition ASAP Automated Service Activation Program (Oracle product) ASR Access Service Request CE Customer Edge CPE Customer Premise Equipment CRM Customer Relationship Management CSD Communications Solutions Designer CSDL Common Service Description Language CTAG Customer Tag (Customer VLAN ID) DHCP Dynamic Host Configuration Protocol DIA Direct Internet Access ELAN Ethernet Local Area Network EPL Ethernet Private Line EVC Ethernet Virtual Circuit EVPL Ethernet Virtual Private Line
  9. 9. Solution Uptake Guide IP Service Activator 7.2 9 Acronym Definition ISC Internet Systems Consortium NE Network Element NID Network Interface Device NNI Network to Network Interface (This may refer to an interface between the Metro and National networks or an interface to a third-party network.) NP Network Processor NPE Network Provider Edge OSM Order and Service Management (Oracle product) OVC Operator Virtual Circuit PE Provider Edge PSR Provisioning Service Request QoS Quality of Service SSL Secure Sockets Layer STAG Service Tag (Service VLAN ID) UNI User Network Interface UPE User Provider Edge VCID Virtual Connection ID VLAN Virtual Local Area Network VM Virtual Machine
  10. 10. Solution Uptake Guide IP Service Activator 7.2 10 2. Solution Architecture This section defines the solution architecture. 2.1 Solution Overview Oracle proposes an Order-to-Activate Solution to support the service fulfillment lifecycle of Business to Business (B2B) data services across a broad range of Network Equipment Vendors. The solution comprises the following functions: IP Service Provisioning IP Service Activation Figure 2 provides an end-to-end functional architecture view for this implementation, including components that are outside the scope of the current document. MPLS VPN with Ethernet Access Functional Architecture Figure 2: Functional Deployment Context The Oracle products within the solution are described in Table 2. Table 2: Oracle Products within the Solution Oracle Product Description/Function Order and Service Management (OSM) Responsible for provisioning order decomposition and orchestration; also responsible for interfacing with activation
  11. 11. Solution Uptake Guide IP Service Activator 7.2 11 Oracle Product Description/Function IP Service Activator Responsible for service activation on the network and for the management of network elements In this reference implementation, OSM provides Service Order Management. Incoming orders are in a Provisioning Order Enterprise Business Message (EBM) format Only relevant, commercially significant provisioning information is contained in the provisioning order o Therefore the OSM order must be augmented with additional information before activation can be initiated. o Some exceptions can be made. For example, we can assume that the PE is specified directly in the order rather than forcing a manual task to select the PE. The customer order is populated with all the details captured from the commercial design that was done at Lead-to-Quote time. OSM to IP Service Activator is not attempting to contribute to that process. 2.2 Service Scenario Details Table 3 defines the commercial services available for flow-through activation of MPLS VPN with Ethernet Access on the network. Table 3: Service Definitions Service Name Description L3 MPLS VPN MPLS VPN for a specified customer. A VPN not containing any sites yet does not activate any configuration on the network. L3 MPLS VPN Site VPN site using EBGP, and/or RIP routing protocol. L3 Site Quality of Service Layer 3 Quality of Service selection for vpn site. Metro Ethernet Access Service Configure VLAN on Metro Ethernet Network to provide transport from the Metro Ethernet Network to the IP/MPLS core Customer Premise Equipment CPE is a customer edge device discovered into IP Service Activator to participate in a site of management vpn to enable access to the CE device. Figure 3 shows the service scenario details.
  12. 12. Solution Uptake Guide IP Service Activator 7.2 12 Figure 3: Service Scenario Details Refer to Summary of Activation of Technical Services in this document for an overview of activation applied at the provider edge (PE) device, customer edge (CE) device, and U-PE (Layer 2 switches) for each orderable service. Overview of IP Service Activator Readiness Assumptions: All customer VPNs are full mesh Management VPN is configured (Managed) CEs are shipped, preconfigured, and are IP reachable from IP Service Activator Core network and PEs are preconfigured for MPLS A set of standard QoS definitions are preconfigured in IP Service Activator for PE ingress and egress – Specific QoS policies must be defined for managed CEs as part of workflows Single vendor model used for all PEs Single vendor model used for all CEs Single vendor model used for all U-PE (L2 Switches) 2.3 Service Scenario Topology Figure 4 shows the L3 MPLS VPN with Metro Ethernet Access network configuration proposed for the reference implementation. Figure 4: Service Scenario Topology
  13. 13. Solution Uptake Guide IP Service Activator 7.2 13 Management VPN connectivity is hub and spoke, the customer VPN connectivity is a mesh. CEs may be connected to PEs over a Metro-E access network. 2.4 Solution Components Overview The implementation includes: IP Service Activation. 2.4.1. Inventory Inventory management functionality is not supported by this version of the reference implementation. Any required information is provided using either manual tasks or a fully qualified order input into Order and Service Management. 2.4.2. IP Service Activation The Order to Activate IP Service Provisioning solution uses IP Service Activator to deliver real-time, dynamic, mass customized network services on commonly deployed network hardware using common network standards. IP Service Activator is supported by a number of base cartridges and service cartridges to interact with network devices (CPE devices and routers). 2.4.3. Integration and Interfaces For integration between applications, Oracle proposes the following: The integration layer: o Creates a new service order request to OSM for fulfillment of service actions. o Updates the service order requests to update an in progress or in-flight order. o Cancels an in progress (in-flight) service request. OSM to IP Service Activator: IP Service Activator provides a Design Studio cartridge that contains service actions available for use in an activation task at OSM cartridge design time. At run time, the activation task, configured with a sequence of service actions and parameter bindings to order data, communicates with the IP Service Activator Web service. The Web service then communicates with the IP Service Activator Integration Manager using the IP Service Activator OJDL interface to fulfill activation, query, and discovery requests. IP Service Activator to OSM: The IP Service Activator Web service monitors completion of requests, which require an IP Service Activator transaction, using IP Service Activator status transaction monitoring functionality, and returns activation and query results to OSM. 2.5 Architecture Principles To ensure a consistent architectural approach that provides the benefits of reduced Total Cost of Ownership (TCO) and alignment to current best practices, the following are defined: Standardization: The solution is built on Oracle CGBU packaged software applications. Process Consistency: The process scope determines the solution implementation, but the focus is on using as much out-of-the-box capability as possible. Reuse: The core solution is developed by configuration of standard software components. Custom development is treated as an exception, limited where possible, and clearly identified. Data and Consistency: Data mapping and transformation across systems is controlled by the integration layer.
  14. 14. Solution Uptake Guide IP Service Activator 7.2 14 3. Installation MPLS VPN with Metro Ethernet Implementation is not intended to be co-resident with any other sample reference implementation, such as the GSM Mobile provisioning solution. 3.1 Virtual Machine Distributions A separate deployment configuration, as shown in Figure 5, is available to simplify the distribution and consumption of the implementation. The distribution consists of two virtual machines (VMs), organized as follows: The core reference implementation VM, based on Linux, is responsible for running the Oracle Database, the WebLogic server, and IP Service Activator. IP Service Activator may be run using pre-populated network devices in an offline mode, or against a real network. The Windows VM is responsible for hosting Design Studio and the IP Service Activator client components. The virtual machines may be run on any computer system capable of running Oracle VM VirtualBox. Oracle strongly recommends a minimum of 8G of RAM and 60G of hard disk space. Figure 5: MPLS VPN with Metro Ethernet Implementation Deployment Configuration 3.1.1. Virtual Machine Distribution Restrictions Distribution of the virtual machines is subject to the following restrictions: The core reference implementation VM has no restrictions and may be distributed internally and to interested third parties. The Windows 7 VM is available only to internal Oracle Corporation parties because of restrictions with Microsoft Windows licensing. For parties outside Oracle Corporation, a complete set of installation and configuration instructions will be provided so that they can
  15. 15. Solution Uptake Guide IP Service Activator 7.2 15 either create their own licensed VM, or run the applications natively on a computer running Windows 7. 3.2 Installation and Configuration Table 4 lists recommended platforms. Table 4: Recommended Platforms Operating System Version Comment Linux 6u1 Oracle Linux recommended for core product installations 64-bit version recommended Windows 7 Windows required for Design Studio and IP Service Activator graphical user interface 64-bit version recommended Oracle Solaris 10 64-bit version Table 5 lists product versions required. Table 5: Required Product Versions Component Depends On Version Comment Oracle VM VirtualBox Linux, Windows 4.1 Oracle Database Server Linux 11gR2 (11.2.0.3) OSM and IP Service Activator server components require Oracle Database Server to be installed and configured before you begin installation. 32-bit version recommended in order to minimize memory consumption. Oracle Database Client Windows 11gR2 (11.2.0.3) The OSM Administrator tool and OSM SDK scripts require the Oracle Database Client to connect directly to an Oracle RDBMS. Java JDK Linux, Windows, Solaris 1.6.0_31 32-bit version recommended in order to minimize memory consumption. WebLogic Oracle Database Server 10.3.5
  16. 16. Solution Uptake Guide IP Service Activator 7.2 16 Order and Service Management Linux, Oracle Database Server, WebLogic, JBoss Cache, Saxon-B 7.2.0 Order and Service Management SDK Windows 7.2.0 Order and Service Management Administrator Client Windows, Oracle Database Client 7.2.0 JBoss Cache 1.4.1.SP12 Third-party requirement of OSM installer Saxon-B 9.1.0.7j Third-party requirement of OSM 7.2 installer IP Service Activator Linux, Oracle Database Server, WebLogic 7.2.0 IP Service Activator Client Components Windows 7.2.0 Oracle Enterprise Pack for Eclipse Windows 12.1.1.0.1 Oracle Enterprise Pack for Eclipse (OEPE) is based on Eclipse 3.7 (Indigo) Design Studio Windows, Eclipse, OSM SDK, Java JDK, WebLogic 7.2.1 3.2.1. MPLS VPN with Ethernet Access Solution Media Pack The MPLS VPN with Ethernet Access Provisioning Solution Media Pack is distributed as a ZIP file named MPLSVPNProvisioning.zip. It contains the components listed in Table 6. Table 6: Components of Media Pack Component Names MPLS VPN Solution Installer SolutionInstaller/osmipsa_setup.properties SolutionInstaller/osmipsa_setup.py SolutionInstaller/run.sh MPLS VPN cartridges for OSM OracleCommsOSM_IPSA_L3MPLSVPN-
  17. 17. Solution Uptake Guide IP Service Activator 7.2 17 7.2.0.version.zip MPLS VPN solution README README.txt Note: The IP Service Activator Design Studio cartridge (ipsaStudioCartridge-7.2.0version.zip) is not included in this media pack. 3.2.2. Core Configuration Install and configure all of the following on a Linux or Oracle Solaris platform. Refer to details in each section below. 1. WebLogic 10.3.5 and ADF, and WebLogic Domain Creation 2. Oracle Database Server 11gR2 (11.2.0.3) 3. Order and Service Management 7.2.0 4. IP Service Activator 5. IP Service Activator Web Service 6. Messaging Resource Adapter 7. MPLS VPN Solution Installer WebLogic 10.3.5 and ADF, and WebLogic Domain Creation See OSM System Requirements in Oracle Communications OSM Installation Guide for the application server requirements for the version of WebLogic required for your environment. For development, demonstration, and test environments, you can install Oracle JDeveloper, which contains both the WebLogic Server software and ADF. For production environments, Oracle recommends that you install the WebLogic Server software and ADF software individually. You can have a single WebLogic domain. Within the WebLogic domain, OSM resides within a managed server or cluster, and IP Service Activator resides in a managed server. For production environments, a managed server cluster for OSM and a managed server for IP Service Activator Web service deployed in a single WebLogic domain is recommended for multi-product deployments. When configuring a WebLogic domain within a managed server or cluster, ensure that you follow detailed instructions in Oracle Communications OSM Installation Guide. This section outlines choices for a quick installation for development, demonstration, and test environments. Set up a WebLogic domain for a multi-product deployment of OSM and IP Service Activator Web service. To set up a WebLogic domain: 1. Create a single WebLogic domain with a managed server for OSM, such as osm_ms, and a managed server for IP Service Activator Web service, such as ipsa_ms. 2. On the Select Domain Source page, make sure that Oracle JRF is selected: "Oracle JRF - 11.1.1.0 [oracle_common]" 3. On the Configure Server Start Mode and JDK page, select Other JDK, and browse to set the location to the directory where JDK1.6.0_31 is installed. Do not use any Java version that might be included with the Application Server. 4. On the Select Optional Configuration page, select all of the following:
  18. 18. Solution Uptake Guide IP Service Activator 7.2 18 o Administration Server  Set the WebLogic Administrator user and password.  If required, change the administration server settings to select a listen address, and port other than the default listen address (localhost), and default port (7001). Note that localhost may map to both an IPv4 address and an IPv6 address. If this applies to your environment, you can specify 127.0.0.1 to specify the the IPv4 localhost address. o Managed Servers, Clusters, and Machines  Create a managed server for OSM, such as osm_ms, and a managed server for IP Service Activator Web service, such as ipsa_ms. o Deployments and Services  Select all deployments, for each managed server on the Target Deployments to Clusters or Servers page.  Select all services, for each managed server on the Target Services to Clusters or Servers page. 5. On the Creating Domain page of Fusion Middleware Configuration Wizard, select Start Admin Server, and then click Done. 6. Login to the WebLogic administration console at: http://host:port/console such as http://localhost:7001/console 7. Click the name of WebLogic server domain, which you will find under "Domain Structure" On the Security tab, select the Anonymous Admin Lookup Enabled check box, and click Save. On JTA tab, modify the value of the Timeout Seconds parameter to an appropriate value in seconds, such as 3000, and click Save. 8. Under "Domain Structure", expand your domain > Environment > Servers. For each server, select the Logging tab. Increase the log rotation file size to an appropriate value, such as 10000 Select Advanced. Increase the minimum severity of log messages going to the server log file to Info. Increase the minimum severity of log messages going to standard out to Error. Click Save. The default Trace level logging for the server log file, and the default Notice level logging for standard out is too extensive. 9. Increase the maximum heap size to an appropriate value in your WebLogic domain. The memory arguments variables are found in YourOracleMiddlewareInstallDiruser_projectsdomainsyourdomainnamebinsetDom ainEnv.cmd The recommended maximum heap size for OSM is between 2000 Mb and 3000 Mb for production environments (e.g. -Xmx2000m). Development environments can be allocated less memory (between 1000 Mb and 2000 Mb). o Example: # IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values USER_MEM_ARGS="-Xms512m -Xmx3000m -XX:PermSize=512m - XX:MaxPermSize=760m -Xrs" 10. Restart the WebLogic domain using the command startWebLogic.sh
  19. 19. Solution Uptake Guide IP Service Activator 7.2 19 11. Start the managed servers. The managed servers must be restarted for deployment of OSM and IP Service Activator Web service. The managed server for IP Service Activator Web service can be started with the standard startManagedWebLogic script. If OSM is clustered, an OSM managed server must be started with an OSM-specific startup script that identifies the appropriate coherence parameters file; otherwise, the standard startManagedWebLogic script can be used to start the OSM managed server. Oracle Database Server 11gR2 (11.2.0.3) See Oracle Database documentation for information about how to install Oracle Database. Refer to the product installation documentation for the application (Order and Service Management, IP Service Activator) that requires Oracle Database for recommended patch sets, configuration guidelines, and recommendations for performance tuning. Order and Service Management 7.2.0 This section outlines choices that you can make for a quick installation for development, demonstration, and test environments. See Oracle Communications OSM Installation Guide for pre-installation tasks, installation instructions, and post-installation tasks. To run a quick installation: 1. In OSM installer, select the View third party readme now check box. Click Next. OSM has third-party requirements that you need to download before continuing with the OSM installation 2. Download and install JBoss Cache 1.4.1.SP12 and Saxon-B 9.1.0.7 from sourceforge as instructed http://sourceforge.net/projects/jboss/files/JBossCache/JBossCache%201.4.1.SP12/ http://sourceforge.net/projects/saxon/files/Saxon-B/9.1.0.7 3. Select a Custom install, and select all components Tip: On the Database Administrator Credential Information window, if you get a Database Schema Privilege check error, you can either follow the instructions in the error window or try appending as sysdba to the user name you specified for Database Admin Username such as system as sysdba for username system. On the Database Schema Partition Information page, you can de-select Use Oracle Partitioning features unless you require partitioning. On the Provisioning Server Session Information page, you can select Don’t use ssl during http login unless you require SSL. When OSM installation is complete, the OSM installer instructs you to restart the WebLogic server. Restart twice. Note: The first time you restart the WebLogic server after installation, an exception indicating Cannot create file system at Attachments, or T3 file attachment not found is expected.
  20. 20. Solution Uptake Guide IP Service Activator 7.2 20 Refer to OSM post-installation tasks in the Oracle Communications Order and Service Management installation guide. After installation, verify that the application installed properly. To verify if the application installed properly: 1. Log in to the Oracle WebLogic server Console. 2. In the left pane of the console, expand the Environments node and select Servers. 3. In the right pane of the console, click the OSM managed server link, such as osm_ms. 4. In the tabs, select Deployments and expand oms to verify that all EJBs and modules have been deployed. 5. Verify that both oms and cartridge_management_ws applications are active. 6. Perform these post-install tasks while you are still logged in to the console: a. Create a persistent store for OSM, which will be required by the solution installer. i) In the left pane of the console, expand the Services node and select Persistent Stores. ii) Select New > Create FileStore. Enter a name, Target osm_ms. Click OK. b. Navigate to the security realm in the WebLogic console to add users to additional groups: i) If you want to use the log4J console, add users such as admin user to OMS_log_manager group ii) If you plan to perform order enrichment in the OrderManagement Web client (which uses data providers to access information from IP Service Activator Web services), add users such as admin user to Cartridge_Management_WebService group IP Service Activator Install all components of IP Service Activator on an Oracle Solaris or Linux server. The Solaris and Linux installation do not include the IP Service Activator client, which must be installed on a Windows platform. IP Service Activator Web Service IP Service Activator Web service is installed through the Oracle Universal Installer. After installation, the Web service needs to be configured and deployed to a WebLogic application server. Configuration and deployment is done through the IP Service Activator configuration GUI. For more information, see IP Service Activator documentation. Note: The IP Service Activator Web service user name and password, which you enter in the configuration GUI, must match the username such as ‘ipsa_ws_user’ and password, which you enter when using the OSM SDK script credStoreAdmin to setup a credential store for OSM access to IP Service Activator Web service credentials.
  21. 21. Solution Uptake Guide IP Service Activator 7.2 21 Messaging Resource Adapter To prepare the managed server for the Web service to support a messaging bridge, the jms-notran- adp.rar resource adapter must be deployed. The resource adapter is located in WL_HOME/server/lib/jms-notran-adp.rar. To prepare the managed server for the Web service to support a messaging bridge: 1. Install jms-notran-adp.rar as an application and target the managed server for the Web service. a. In the WebLogic administrator console, click Lock & Edit. b. Go to Deployments, and click Install. c. Go to the FMW_HOME/wlserver_10.3/server/lib directory, select the jms-notran- adp.rar resource adapter, and click Next. d. Select the Install this deployment as an application option, and click Next. e. Target the managed server for IP Service Activator Web service, and click Next. Keep the “Use the defaults defined by the deployment's targets” setting. The name may be edited or left unchanged. f. Go to Finish. g. Click Activate Changes. The jms-notran-adp deployment should be in a prepared state. 2. Start the jms-notran-adp application. This enables the JNDI name eis.jms.WLSConnectionFactoryJNDInoTX on the managed server for the Web Service. MPLS VPN Solution Installer Configure the Installer for the server environment. Using a text editor, edit the file osmipsa_setup.properties. The table below shows examples of properties for a single WebLogic domain that is hosting IP Service Activator Web Services and OSM. From the server where the WebLogic domain directories are accessible, the Installer runs once to set up the application server resources in the server environment. When prompted, enter the WebLogic administrator passwords. Property Description Sample for single WebLogic domain hosting managed servers for Web services and OSM Sample for single WebLogic domain hosting managed server for Web services and clustered OSM solution_deployme nt_model SINGLE_DOMAIN=1 MULTIPLE_DOMAIN=2 1 1 osm_admin_url T3 URL to the admin server for administering OSM. In a single domain deployment model all applications will use the same admin server. t3://localhost:7001 t3://mclaren.us.oracle.c om:9101 osm_domain_dir The full path to the WebLogic domain /opt/oracle/Middleware/ /opt/oracle/Middleware/
  22. 22. Solution Uptake Guide IP Service Activator 7.2 22 directory for OSM. user_projects/domains/ osmipsadomain user_projects/domains/ osmipsadomain osm_login The WebLogic administrator on the admin server for OSM. You will be prompted for the WebLogic administrator password. WebLogic WebLogic osm_cluster The name of the OSM cluster (empty if non- clustered). osm_cluster osm_servers The list of managed servers for OSM. osm_ms osm_ms1,osm_ms2 osm_server_urls The T3 URL to the OSM managed server or cluster. t3://localhost:7003 t3://osm_ms1:8404,osm _ms2:8405 osm_app_url HTTP URL to the OSM application. http://localhost:7003/Or derManagement http://osm_proxy:8403/ OrderManagement ipsa_admin_url T3 URL to the admin server for administering IP Service Activator WebService . In a single domain deployment model all applications will use the same admin server. t3://localhost:7001 t3://mclaren.us.oracle.c om:9101 ipsa_domain_dir The full path to the WebLogic domain directory for IP Service Activator WebService. /opt/oracle/Middleware/ user_projects/domains/ osmipsadomain /opt/oracle/Middleware/ user_projects/domains/ osmipsadomain ipsa_login The WebLogic administrator on the admin server for IP Service Activator WebService. You will be prompted for the WebLogic administrator password. WebLogic WebLogic ipsa_server The managed server for IP Service Activator WebService. ipsa_ms ipsa_ms ipsa_server_url T3 URL to the managed server for IP Service Activator WebService. t3://localhost:7004 t3://ipsa_ms:8406 ipsa_env The IP Service Activator WebService environment id. A single deployment may be deployed; the deployment is identified by its environment id. IPSA IPSA The following steps have been provided in the run.sh script for convenience: If osm_cluster is not empty (meaning OSM is deployed as a cluster), the osm_server_urls must specify a T3 URL with a cluster address in the format t3://osm_ms1:8404,osm_ms2:8405, where osm_ms1 and osm_ms2 are the managed server host addresses and 8404 and 8405 are the port numbers on the respective managed servers. After the osmipsa_setup.properties file is edited, and the JAVA_HOME and WL_HOME environment variables are set, you can run the Installer from a server with access to the WebLogic domain directories. For a multi-domain deployment, all three domain directories must be accessible. It must have access to the domain directories to be able to encrypt passwords appropriate to the security realm for each domain. Before you run the Installer, ensure that a file store or JDBC store is configured for OSM. By default, the OSM Installer configures its JMS servers to use the default persistent store, which is not a migratable service. This is not sufficient for a highly available deployment. An explicit persistent store for OSM is a pre-requisite.
  23. 23. Solution Uptake Guide IP Service Activator 7.2 23 Before you run the Installer, all managed servers (that is, for IP Service Activator Web service, and OSM) must be shut down. This leaves only the admin server running for each domain, as well as any proxy servers (inconsequential). If any managed servers are running while the Installer runs, it will fail; to recover, shut down all managed servers and re-run the Installer. To run the Installer: JAVA_HOME= /tools/packages/jdk/jdk1.6.0_31 WL_HOME=/opt/oracle/Middleware/wlserver_10.3 $JAVA_HOME/bin/java -cp $WL_HOME/server/lib/weblogic.jar weblogic.WLST osmipsa_setup.py The solution installer performs the following steps: 1. Configures OSM with JMS reply-to destinations and an event topic for integrating with the Web service. JMS Server(s): osm_ipsa_oss_jms_server_osm_server (where osm_server is the OSM managed server name) JMS Module: osm_ipsa_oss_jms_module 2. Configures OSM with a store-and-forward agent for sending requests to the Web service. Store- and-forward agents: osm_ipsa_oss_saf_agent (for non-clustered OSM) osm_ipsa_oss_saf_agent_osm_server (for clustered OSM, where osm_server is the OSM managed server name) 3. Configures the Web service with a store-and-forward agent for sending replies and events to OSM. JMS Module: IPSA.ipsa_oss_jms_module Store-and-Forward Agents: ipsa_oss_saf_agent 4. Configures the Web service with a messaging bridge for copying events to a SAF queue that forwards to OSM. Bridges: ipsa_osm_even_bridge After you run the Installer, restart the managed servers. You can use the standard startManagedWebLogic script to start the managed server for the Web service. If OSM is clustered, an OSM managed server must be started with an OSM-specific script that identifies the coherence parameters file; otherwise, you can use the standard startManagedWebLogic script to start the OSM managed server. Note: The Installer creates WebLogic resources that reference WebLogic resources that are created during deployment of the IP Service Activator Web Services, namely ipsa_jms_module. Although you can undeploy and redeploy IP Service Activator Web Services (using the Configuration GUI), after you
  24. 24. Solution Uptake Guide IP Service Activator 7.2 24 run the Installer, the following warning message appears when undeploying IP Service Activator Web Services: Warning: Undeployment completed with warnings. Failed to delete JMS server and queues. 3.2.3. Windows Configuration Install and configure all of the following on a Windows 7 platform. Refer to details in each section below. 1. Oracle Database 11g Release 2 Client 2. Order and Service Management 7.2.0 SDK, Administrator Client 3. WebLogic 10.3.5 and ADF (no domain creation) 4. Java JDK 1.6.0_31 5. Eclipse Indigo 6. Design Studio plugins version 7.2.1 7. IP Service Activator 7.2.0 Client Components Oracle Database 11g Release 2 Client OSM Administrator client requires the Oracle Database Client to connect directly to an Oracle RDBMS. Any machine on which the OSM Administrator tool is installed requires the Oracle Database Client. OSM Administrator client requires the following 32-bit Oracle libraries: Oracle Objects for OLE Oracle Provider for OLE DB Oracle SQL*Plus (This is optional, and suggested to select as well.) These 32-bit Oracle client libraries need to be installed separately. The best way to install them is to download Oracle Data Access Components (ODAC) with Oracle Developer Tools for Visual Studio (http://www.oracle.com/technetwork/topics/dotnet/utilsoft-086879.html). During installation, along with any other mandatory components, ensure that the mandatory 32-bit Oracle libraries components are also selected. After installation, you can use SQL*Plus to verify that the application installed properly. To verify if the application installed properly: 1) Verify that you can log in to sqlplus using the database credentials which you supplied in the OSM installer for the primary schema Order and Service Management SDK, Administrator Client To install OSM SDK Administrator client: 1. In OSM installer, select the View third party readme now check box. Click Next. OSM 7.2.0 has third-party requirements that need to be downloaded before continuing with OSM7.2.0 install 2. Download and install JBoss Cache 1.4.1.SP12 and Saxon-B 9.1.0.7 from sourceforge as instructed http://sourceforge.net/projects/jboss/files/JBossCache/JBossCache%201.4.1.SP12/ http://sourceforge.net/projects/saxon/files/Saxon-B/9.1.0.7 3. Select a Custom install, and the following components:
  25. 25. Solution Uptake Guide IP Service Activator 7.2 25 SDK Tools and Samples Administrator Client Note: On a Windows platform, the Typical installation type installs everything except the SDK Tools and Samples. Order and Service Management SDK scripts are documented in Oracle Communications Order and Service Management System Administrator's Guide. Instructions are given below as specific to the MPLS VPN implementation: In order to be able to use OSM SDK scripts, such as for purging cartridges, you need to update database connection information in config.xml with the database server connection parameters, and database credentials for the primary schema which you specified in the OSM installer which you ran on the Linux platform. In the OSM installation, the default name for the primary schema is ordermgmt. In order to be able to secure credentials required to access IP Service Activator web services, you will need to update j2eeAdminConnection in config.xml with the connection information to the WebLogic instance hosting IP Service Activator web services. To update config.xml, and config.bat in preparation for use of SDK scripts such as purge, credStoreAdmin, and EncyptPasswords: 1. Copy OSMHOMESDKXMLImportExportconfigconfigSample.xml to OSMHOMESDKXMLImportExportconfigconfig.xml 2. Update database connection in config.xml such as: <databaseConnection> <user>ordermgmt</user> <password>password</password> <dataSource>jdbc:oracle:thin:@(description=(address=(host=yourDat abaseServerIpOrName)(protocol=tcp)(port=1521)) (connect_data=(SID=yourOracleSID)))</dataSource> </databaseConnection> 3. Update j2eeAdminConnection in config.xml with the connection information to the WebLogic admin server in the domain hosting OSM such as: <j2eeAdminConnection> <j2eeServiceName>weblogic</j2eeServiceName> <user>system</user> <password>password</password> <hostname>localhost</hostname> <port>7001</port> </j2eeAdminConnection> 4. Update JAVA_HOME, APP_ROOT, AND MIDDLEWARE_HOME variables found in OSMHOMESDKXMLImportExportconfig.bat to point to the jdk in your Fusion Middleware folder (such as C:Program FilesJavajdk1.6.0_31), the XMLImportExport folder in the OSM SDK installation (such as C:OSMSDKXMLImportExport), and the Fusion Middleware installation folder (such as C:OracleMiddleware) respectively. To verify if the OSM Administrator installed properly:
  26. 26. Solution Uptake Guide IP Service Activator 7.2 26 1. Verify that you can log in to the OSM Administrator using the admin user, and connection information for the OSM managed server. Note: When you attempt to login to the OSM Administrator client, if you get an error Provider not found, then check that you have the mandatory Oracle Provider for OLE DB component installed. WebLogic and ADF (no domain creation) WebLogic 10.3.5 and ADF are required on the Windows host to be able to set the path for the WebLogic home directory in Design Studio, and for use by OSM SDK scripts. To set Order and Service Management Design Studio properties in Design Studio: 1. From the menu bar, select Window > Preferences and select Oracle Design Studio > Order and Service Management Preferences 2. Set path for WebLogic Home as: WebLogic Home: OracleMiddlewareHomewlserver_10.3 Refer to OSM System Requirements in the Oracle Communications Order and Service Management installation guide for the Application Server requirements to obtain the appropriate version of WebLogic for your environment. Note: The JDeveloper option is for development, demonstration, and test environments. WebLogic 10.3.5 comes bundled along with JDeveloper Studio installer 11.1.1.5.0 Design Studio for OSM For information about installing Design Studio, see Oracle Communications Design Studio Installation and System Administration Guide. Instructions are given below as specific to the MPLS VPN implementation: Design Studio 7.2.1 requires JDK 1.6.0_31 and Eclipse Indigo. To download required components for Design Studio: 1. Download and install the JDK. (32-bit or 64-bit depending on your Windows platform) jdk-6u31-windows-i586.exe (32-bit) jdk-6u31-windows-x64.exe (64-bit) 2. Download and extract the Oracle Enterprise Pack for Eclipse archive 12.1.1.0.1. (32-bit or 64-bit depending on your Windows platform) oepe-indigo-all-in-one-12.1.1.0.1.201203120349-win32.zip (32-bit) oepe-indigo-all-in-one-12.1.1.0.1.201203120349-win32-x86_64.zip (64-bit) The default Eclipse settings may be suitable for small cartridges, but for larger cartridges and to improve performance the default VM arguments should be updated. The VM arguments need to be set in the eclipse.ini file located in the Oracle Enterprise Pack for Eclipse folder. The maximum memory usage setting (Xmx) should be adjusted based on your system. For systems with 2 GB of memory a setting of -Xmx1024m is recommended (as shown in the example below). On 32-bit systems, the maximum is limited and values above 1024 MB may result in out of memory errors on startup. If you are on a 64-bit system using the 64-bit JDK and OEPE packages, you may increase this
  27. 27. Solution Uptake Guide IP Service Activator 7.2 27 value as needed (for example, for a 4 GB system a value of 3048m may be used). It is recommended that at least 1024m be left for use by other applications. Example eclipse.ini settings: -vmargs -XX:NewRatio=5 -XX:+UseAdaptiveSizePolicy -XX:+UseParallelGC -Xms128m -Xmx1024m -XX:MaxPermSize=512m -Dsun.lang.ClassLoader.allowArraySyntax=true Note: Installing new Design Studio plug-in versions does not automatically remove older versions. If required, uninstall existing Design Studio features. To install Design Studio features in Eclipse Indigo: 1. Download the Oracle Communications Design Studio Media Pack. See Oracle Communications Design Studio Installation and System Administration Guide for information about creating a local or shared update site that you can use to install Design Studio features in Eclipse. 2. In Design Studio, from the menu, select Help, Install New Software. 3. Click Add. 4. Enter the local or remote site for Design Studio. 5. Select the update site from the Work with drop down list. 6. Make sure that hide items that are already installed is selected. 7. Install all Design Studio 7.2.1 plugins: Oracle Communications Design Studio Domain Modeling Oracle Communications Design Studio for Activation SRT Oracle Communications Design Studio for Activation UI Oracle Communications Design Studio for Inventory Oracle Communications Design Studio for Order and Service Management Oracle Communications Design Studio for Order and Service Management Orchestration Oracle Communications Design Studio for Order and Service Management Orchestration Application Integration Architecture (AIA) Oracle Communications Design Studio Integration Oracle Communications Design Studio Platform To set OSM Design Studio properties in Design Studio: 1. In the menu, select Window, Preferences, and then select Oracle Design Studio, Order and Service Management Preferences. 2. Set paths for WebLogic Home, Java SDK Home, and OSM SDK Home as:
  28. 28. Solution Uptake Guide IP Service Activator 7.2 28 WebLogic Home: OracleMiddlewareHomewlserver_10.3 Java JDK Home: JavaHomejdk1.6.0_31 OSM SDK Home: OSMHomeSDK Note: WebLogic is required on the Windows host to be able to set the path for WebLogic Home in Design Studio, so that Design Studio can use WebLogic libraries. Domain creation is not required. This is not to be confused with WebLogic installation and domain creation required in the core configuration for hosting OSM and IP Service Activator Web service. To import the IP Service Activator Studio project and MPLS VPN provisioning cartridges into the Eclipse workspace: 1. Download the IP Service Activator Design Studio cartridge, named ipsaStudioCartridge- 7.2.0.xxx.zip Note: You do not need to unzip this file. 2. Extract MPLS VPN cartridges for OSM (OracleCommsOSM_IPSA_L3MPLSVPN- 7.2.0.xxx.zip) from MPLSVPNProvisioning.zip. Note: You do not need to unzip the OracleCommsOSM_IPSA_L3MPLSVPN-7.2.0.xxx.zip file. 3. For each zip file, from the main menu bar, select File > Import.... The Import wizard opens. 4. Select General > Existing Project into Workspace 5. Select the radio button named Select archive file. Browse to locate the directory or file containing the archive zip file. Select Finish. Note: After you import the ipsaStudioCartridge-7.2.0.xxx.zip file into your workspace, you should not unseal the OSMIPSA_7 cartridge. 6. Close and re-open eclipse after importing all cartridges into your workspace. The activation tasks in the MPLS VPN provisioning cartridges are configured to use the keyname and mapname in ipsa-cred.xml for access to IP Service Activator Web service credentials. After you import the MPLS VPN provisioning cartridges, you can find ipsa-cred.xml in your eclipse workspace at OracleCommsOSM_IPSA_L3MPLSVPN-Resourcesresourcescredentialsipsa-cred.xml You must run the EncryptPasswords, and credStoreAdmin scripts provided in the OSM SDK to create a credential store in WebLogic. Successful execution of these scripts, which can be executed in your Windows environment, depends on having already installed JDK1.6.0_31, WebLogic 10.3.5, and ADF as discussed in WebLogic and ADF (no domain creation), and correct configuration of the OSM SDK as described in Order and Service Management SDK, Administrator Client. Use the xml data file ipsa- cred.xml as the xml data file for the credStoreAdmin script such as: OSM_homeSDKXMLImportExportEncryptPasswords .configconfig.xml –dbUser user -wlsUser user
  29. 29. Solution Uptake Guide IP Service Activator 7.2 29 OSM_homeSDKXMLImportExportcredStoreAdmin eclipse workspace folderOracleCommsOSM_IPSA_L3MPLSVPN-Resourcesresourcescredentialsipsa-cred.xml .configconfig.xml Note: As a result of the IP Service Activator Web services installation and setup, a WebLogic user matching the user name given in ipsa-cred.xml, such as ipsa_ws_user, is created. Note: For more information about credStoreAdmin and EncyptPasswords, see Oracle Communications OSM System Administrator’s Guide. To configuration for View Framework selection: 1. In the Design Studio perspective, use the Design Studio cartridge view. 2. Open the Composite cartridge entity. 3. Go to the Model Variables tab and update the value for the following three variables: o CREDENTIAL_MAP – the mapname for the Credential you created. ipsa should be the default o CREDENTIAL_KEY – the keyname for the Credential you created. ipsa should be the default o IPSA_WS_URL – the hostname and port of the managed server hosting IP Service Activator Web services for your configuration. The default is localhost:7004. Note: the hostname should be the physical machine where the IP SERVICE ACTIVATOR managed server is installed, which is not necessarily the same machine where the AdminServer resides. Note: These changes must be made before the cartridges are built and deployed. To create a new Environment project: 1. In the new Environment project, create a new Studio Environment. Update the connection parameters to specify the connection parameter necessary to connect to the OSM run-time environment by following the steps in the procedure below. To update the connection parameters for cartridge deployment and for test order submission: 1. In the Studio Environment project, from the main menu, select Studio > Show Design perspective 2. Double-click on the Studio Environment to open it. 3. On the Connection Information tab of the Studio Environment, update the Connection address, Oracle Submission URL, and Web UI URL to replace localhost:7001 with the WebLogic IP address (or the fully qualified domain name if DNS is enabled) and port necessary to connect to the OSM run-time environment. Specify the port number of the OSM managed server such as localhost:7003 for the sample osm_ms managed server in this document. To build and deploy cartridges, and assign users to roles: 1. Build all cartridges.
  30. 30. Solution Uptake Guide IP Service Activator 7.2 30 2. Deploy a single cartridge using the sceadmin user, namely: OracleCommsOSM_IPSA_L3MPLSVPN-Composite 3. After the cartridges are deployed, login to the OSM Administrator to assign users to the roles IPProvisioningRole, and the IPProvisioning_CancelSiteRole. Login using the admin user, and connection information for the OSM managed server such as localhost:7003. IP Service Activator Client Components Install all client components of IP Service Activator on a Windows host. This includes the main IP Service Activator User Interface, the GUI extensions, and the configuration GUI. Download and install the Win64 client-only installer if the client must connect to a 64-bit IP Service Activator policy server. 3.2.4. Seed Data for L3 MPLS VPN Implementation Refer to Seed Data under L3 MPLS VPN Detailed Use Cases - Order Scenarios for data required in IP Service Activator, and OSM solution configuration data to execute the test orders. 3.2.5. Patching the IP Service Activator Design Studio Cartridge Upgrading from one version to a newer version of the IP Service Activator Web service also requires you to upgrade to a corresponding version of the IP Service Activator Design Studio cartridge named ipsaStudioCartridge-7.2.x.xxx.zip. To patch the IP Service Activator Design Studio Cartridge: 1. Extract MPLS VPN provisioning cartridges for OSM (OracleCommsOSM_IPSA_L3MPLSVPN-7.2.0.xxx.zip) from the newer version of MPLSVPNProvisioning.zip Note: You do not need to unzip the file OracleCommsOSM_IPSA_L3MPLSVPN- 7.2.0.xxx.zip 2. In your eclipse workspace, open the Studio Design perspective. 3. Delete the OSMIPSA_7. You are prompted with: The following cartridges ‘OSMIPSA_7’ have dependants. Do you want to delete? 4. Click ok. You will be prompted Are you sure you want to delete project ‘OSMIPSA_7? 5. Select the option Also delete contents under eclipse workspace folderOSMIPSA_7 To import the newer version of the IP Service Activator Studio project into your eclipse workspace: 1. From the main menu bar, select File > Import.... The Import wizard opens. 2. Select General > Existing Project into Workspace 3. Select the radio button named Select archive file. Browse to locate the directory or file containing the archive zip file. Select Finish. You will need to re-build, and re-deploy your cartridges to prepare the runtime environment for compatibility with the corresponding version of the IP Service Activator web service. Note: Any new features such as new service actions, or new service action parameters for pre-existing service actions, or additions to configuration policies schemas will be available for use in Design Studio.
  31. 31. Solution Uptake Guide IP Service Activator 7.2 31
  32. 32. Solution Uptake Guide IP Service Activator 7.2 32 4. Use Case Overview Each use case scenario corresponds to a provisioning order consumed by OSM service order management to transform/enrich order, decompose order, and provision services. A provisioning order may be a new order with only ADD actions, or a follow-on change order with a combination of changes such as ADD, UPDATE, DELETE, or a cancellation request. A use case represents a functional variation which exercises one or more of the available fulfillment system functions and implements dependencies between them as required. Table 7 gives a summary of the use cases. Table 7: Summary of Use Cases Use Case Business Value (What concept, best practice, or technology is illustrated by this use case) Basic Orchestration, variations on sites & L3 MPLS VPNs Create and link new L3 MPLS VPN (mesh) for a new customer Provide simple streamlined example of order processing Create and link new L3 MPLS VPN (mesh) for existing customer Illustrate the use of conditional code within the Activation task to control the execution of certain Services Actions (such as "Create Customer") to enable greater re-use of the Activation Task. Create and link new single EBGP L3 MPLS VPN Site to existing customer’s L3 MPLS VPN Illustrate how to add another site to an appropriate VPN. Create and link multiple new L3 MPLS VPN Sites to existing customer’s L3 MPLS VPN Illustrate the flexibility of dynamic orchestration to manage orders with an arbitrary number of line items. Delete single L3 MPLS VPN Site Illustrate delete, and possible best practices for "Pending" delete pattern to provide additional failure handling options in case of delete failures. Delete entire L3 MPLS VPN Illustrate how a complex delete operation can be trigger by deleting network and orchestration required to make this happen correctly. Create L3 MPLS VPN Site with choice of routing protocol Illustrate selection of different "Assign and Design" operations dependent on order data. Order that mixes operations (e.g., some adds and some deletes of L3 MPLS VPN Sites) Illustrate complex orchestration Order Enrichment (manual addition of data) View Framework selection of PE interfaces Illustrate a design and assign operation involving retrieval of data from IP Service Activator using the HTTPS web service. Modifies of a L3 MPLS VPN Site
  33. 33. Solution Uptake Guide IP Service Activator 7.2 33 Change routing protocol Illustrate a Change that affects both a customer visible order attribute, but also detailed parameters achieved during Assign and Design (enrichment) Managed Sites Create and link new L3 MPLS VPN Site which includes a managed CE to existing customer’s L3 MPLS VPN, and to existing management VPN. Illustrate the implementation of a more complex order involving an additional line item for CPE equipment. Illustrate subprocesses that coordinate discovery actions. Illustrate the additional (non-customer visible) configuration implied by this line item in which association of the Site to the management VPN is managed. L3 Site Quality of Service Add QoS to all sites in a VPN (all sites are unmanaged) Illustrate best practices for managing QoS definitions, and roles. Illustrate that incremental services can be added to existing deployments with minimal disruption to baseline implementation. Apply QoS to Managed Sites Note: How to use service actions in an activation task to construct an MQC- PHB definition is documented in the Best Practices Guidelines and not currently illustrated in the MPLS VPN implementation. Illustrate an Activation Task for creating a "custom" MQC-PHB definition. (“Managed Site” means the site is included in the management vpn) Configuration Templates Apply CTM Templates to CE Note: How to create a service action for CTM template use in an activation task is documented in Design Studio online help and not currently illustrated in the MPLS VPN implementation. Illustrate the use of CTM templates within the Activation Task. Metro Ethernet Support Create a sub interface when create a new site (versus selecting existing i/f) Illustrate how subinterface creation is done using an Activation Task. Adding a managed site with an access network Illustrate incremental implementation for a complex order for sites that have managed CEs as well as an access network. Ideally, this configuration is well decoupled from other order processing and illustrates the power of orchestration and modular design. Illustrate the use of the specialized Service Actions for managing VLANS. Compensation
  34. 34. Solution Uptake Guide IP Service Activator 7.2 34 Cancel order before completion Illustrate the use of the Activation Task Undo compensation strategy to trigger the rollback of the corresponding IP Service Activator transaction. Failure Isolation and Recovery Options Failure resolution for activation order failure Illustrate best practices for diagnosing failure causes based on error reporting. Illustrate possible recovery actions within Order Processing environment. 4.1 General Use Case Information The information in this section applies to all the use cases. 4.1.1. Overall Business Context Oracle recommends that commercial products are always based on a single commercial service. A commercial service represents the commercial view of a sellable technical service. A commercial service captures all customer-facing data to fulfill the service. A commercial service exposes the commercial interface of a technical service, which requires data enrichment, and the usage of resources to provision the services. The customer facing data, and the enrichment of data captured in OSM service order management are described per service in the use cases below. Table 8 summarizes services available for flow-through activation of MPLS VPN with Ethernet Access. Table 8: Summary of Activation of Technical Services Service Name Activation applied to PE (at interface) Activation applied to CE Activation applied to Switch L3 MPLS VPN L3 MPLS VPN Site VRF, EBGP and/or RIP routing, IP address, VLAN subinterface creation L3 Site Quality of Service Attach QoS: Ingress (Policing) for managed sites Attach QoS: Ingress (Classification and Policing) for unmanaged Attach QoS: Egress (Shaping and Queuing) Metro Ethernet Access Service Device – Enable VLAN on device Switch Access - Enable VLAN Switch Trunk - Enable VLAN Customer Premise Not currently implemented:
  35. 35. Solution Uptake Guide IP Service Activator 7.2 35 Equipment CTM Template for base config managed CE CTM Template for Routing MQC-PHB for Traffic Classification Network Topology Figure 6 shows a diagram of the network topology. Figure 6 Network Topology Figure 7 shows a depiction of technical services available for automated activation on the network. Figure 7: Services
  36. 36. Solution Uptake Guide IP Service Activator 7.2 36 4.1.2. Design Approach This section describes the design approach. 4.1.3. Actors The following list of the actors applies to all the use cases in this document. Design Studio Communications Solutions Designer (CSD) - the individual responsible for implementing a new set of customized OSM workflows that can reliably configure service instances in the network OSM - OSM automation user configured with permissions to execute automated tasks OSM Provisioner (this would include different user groups with specific permissions in OSM, typically for handling failure isolation or Manual tasks). IP Service Activator (IP Service Activator automation user configured with permissions to execute activation commands automatically on the network elements that IP Service Activator manages) IP Service Activator Provisioner (IP Service Activator manual user with permissions to apply activation commands manually on the network elements that IP Service Activator manages) Administrator (the individual responsible for overall maintenance of the solution) 4.1.4. Error Handling The following error handling processes apply to the use cases in this document. If Design Studio is unable to submit a provisioning order to OSM, the error is manually investigated and the Design Studio Engineer would resubmit the provisioning order to OSM. If the OSM order validation fails, the OSM Provisioner fails the provisioning order and sets the reason for the failure. If there is a failure returned from IP Service Activator, the error is manually fixed in OSM and the OSM Provisioner would resubmit the request for activation.. If there is a failure in IP Service Activator, then the IP Service Activator Provisioner may proceed with manual activation and complete the activation order request in IP Service Activator.
  37. 37. Solution Uptake Guide IP Service Activator 7.2 37 5. Provisioning Orders This section discusses provisioning orders. 5.1 Considerations In this reference implementation, OSM will be acting in the role of the Service Order Management system. Incoming orders are in a Provisioning Order Enterprise Business Message (EBM) format Only relevant commercially significant provisioning information is contained in the provisioning order, therefore the OSM order must be augmented with additional information before activation can be initiated. Illustrates handling a Customer Service order component provided by OSM acting as Central Order Management Some exceptions may be made. For example, we may assume that the PE is specified directly in the order rather than forcing a manual task to select the PE. The customer order is populated with all the details captured from the commercial design that was done at Lead-to-Quote time. OSM-IP Service Activator is not attempting to contribute to that process. 5.2 Provisioning Order Structure This section outlines the provisioning order structure. 5.2.1. Service Definitions Table 9 lists the commercial services available for flow-through activation of MPLS VPN with Ethernet Access on the network. Table 9: Commercial Servers Available for Flow-through Activation Service Name Description L3 MPLS VPN Layer 3 MPLS VPN for a specified customer. A VPN not containing any sites yet does not activate any configuration on the network. L3 MPLS VPN Site Layer 3 MPLS VPN site using EBGP, and/or RIP routing protocol. L3 Site Quality of Service Layer 3 Quality of Service selection for vpn site. Metro Ethernet Access Service Configure VLAN on Metro Ethernet Network to provide transport from the Metro Ethernet Network to the IP/MPLS core Customer Premise Equipment CPE is a customer edge device discovered into IP Service Activator to participate in a site of management vpn to enable access to the CE device. 5.2.2. Parent/Child relationships in Provisioning Order Table 10 describes the parent/child relationships between order lines in the provisioning order.
  38. 38. Solution Uptake Guide IP Service Activator 7.2 38 Table 10: Parent/Child Relationships Parent Child Remarks L3 MPLS VPN L3 MPLS VPN Site OSM will determine the customer vpn to which a site belongs to by its parent VPN order line. L3 MPLS VPN Site L3 Site Quality of Service OSM will determine whether QoS is being applied to a managed site or unmanaged site by the value of the ‘Managed’ user-defined attribute in the parent VPN site order line. L3 MPLS VPN Site Customer Premise Equipment OSM will determine incremental template that configures specific routing configuration for the CE device based on the value of the ‘Routing Protocol’ user-defined attribute in the parent VPN site order line. 5.2.3. Service Actions, and Provisioning Order Attributes Table 11 describes the customer-facing service actions and provisioning order attributes. Table 11: Customer-Facing Service Actions and Provisioning Order Attributes Service Name Service Actions User Defined Attributes Values Remarks L3 MPLS VPN ADD, NONE Customer Name text If customer name does not match customer object in IP Service Activator, a new customer object will be created in IP Service Activator. Vpn Name text Name of VPN in IP Service Activator Vpn Description text RTNumber1 High Order text High order number for custom route target1. RTNumber1 Low Order text Low order number for custom route target1. RTNumber1 Mesh Behaviour Import, Export, ImportExport Mesh behaviour for custom route target1. RTNumber1 Address Family Ipv4, Ipv6, Ipv4_Ipv6 Address family for custom route target1. RTNumber2 High Order text High order number for custom route target2. RTNumber2 Low Order text Low order number for custom route target2. RTNumber2 Mesh Behaviour Import, Export, Mesh behavior for custom route target2.
  39. 39. Solution Uptake Guide IP Service Activator 7.2 39 ImportExport RTNumber2 Address Family Ipv4, Ipv6, Ipv4_Ipv6 Address family for custom route target2. L3 MPLS VPN Site ADD, UPDATE, DELETE, NONE Site Name text Name of VPN site in IP Service Activator Managed YES, NO Managed=Yes means VPN site participates in not only customer’s vpn, but also ‘Management’ VPN. Management VPN is a VPN, which is pre- configured in IP Service Activator to enable access to the managed CE device. Routing Protocol EBGP, EBGP_RIP, RIP Selections are EBGP only, EBGP and RIP, or RIP only. VPN site order data is enriched in OSM through capture of routing protocol specific attribute values. Connectivity IP, Ethernet VLAN VPN Site order data is enriched in OSM with selection of a PE interface queried from IP Service Activator. If connectivity=IP, the selected PE interface is linked to the site. If connectivity=Ethernet VLAN, a VLAN sub- interface is created on a PE device and linked to the site. VLAN ID number VLANID is populated when Connectivity=Ethernet VLAN The VLAN sub-interface, which is created on the PE interface, when connectivity=Ethernet VLAN, is configured with the VLANID. VLAN Encapsulation dot1Q, ISL VLAN encapsulation BGP ASN number Site BGP ASN. Remote ASN - ASN of the BGP instance on the CE PE Device Name text Name of provider edge device. PE Interface Name text Name of access interface on provider edge device. Interface Private IPv4 Addr text PE interface private IPv4 address
  40. 40. Solution Uptake Guide IP Service Activator 7.2 40 Interface Private IPv4 Mask text PE interface private IPv4 mask Interface Private IPv6 Addr text PE interface private IPv6 address Interface EBGP Neighbour IP Address text EBGP neighbour IP address. Applies to EBGP routing protocol only. Interface RIP Passive Interface TRUE, FALSE RIP passive interface. Applies to RIP routing protocol only. L3 Site Quality of Service ADD, NONE Qos Profile VoIP Profile, Retail Profile, Data Profile There will be a mapping file of customer visible QoS selections to pre-configured MQC-PHB and custom role objects in IP Service Activator for QoS applied to the PE interface linked to the site (PE Ingress and PE Egress). Metro Ethernet Access Service ADD, NONE VLAN ID number VLANID of virtual LAN that the access port on the layer 2 switch will use. VLAN Encapsulation dot1q,isl VLAN encapsulation Switch text Name of layer 2 switch Port text Name of access interface on layer 2 switch Access Network Name text Name of access network in IP Service Activator. The VLANID will be enabled on switches pre- configured in the access network in IP Service Activator. Customer Premise Equipment ADD, NONE CE Management IP text Discover CE device into IP Service Activator using CE Management IP address
  41. 41. Solution Uptake Guide IP Service Activator 7.2 41 6. L3 MPLS VPN Detailed Use Cases - Order Scenarios This section describes the order submission use cases for the orders included with the reference implementation, and presumes the OSM cartridges have been deployed to OSM. The orders illustrate uses of the MPLS VPN implementation and how it affects whether incoming data is already fully qualified or needs to be enriched in OSM. Unless otherwise stated the scenarios describe fully qualified orders. For non-fully qualified orders, you can enter enriched order data in the OSM web client. Uses of MPLS VPN implementation: Option 1: Incoming data from an upstream system is not fully qualified. Manual tasks in OSM enrich order data with technical service parameters. Option 2: Inventory integration. Manual tasks are “stubs” for assign/design done externally. Option 3: MSS integration. Fully qualified order (includes technical service parameters) is input into OSM. 6.1 Seed Data: Unless otherwise stated, the following pre-conditions apply to all of the order scenarios: IP Service Activator Pre-conditions: Domain is already created. MPLS VPN implementation supports a single domain. Domain has an Internal BGP ASN assigned Any needed policy files are already loaded into domain. The MPLS VPN implementation requires the following policy files to be loaded into the domain: o InterfaceManagementPolicyTypes.policy o VLANPolicyTypes.policy IP Service Activator user used for the session has the required permissions to perform requested operations o a user with "Read Write" access without restrictions for the requested operations o "Super User" Provider network is already pre-configured in IP Service Activator o This is applicable to orders which include order line(s) to ADD L3 MPLS VPN Sites o Any PE device to be used for assignment of a PE access interface to the site, is already discovered into a network object under the domain such as “provider network”, capabilities fetched, and is managed by a Network Processor cartridge supporting L3 MPLS VPN such as the Cisco cartridge o PE device is already managed o PE device already has a role of Gateway o PE access interface has a role of Access Management VPN is already pre-configured in IP Service Activator o This is applicable to orders which include order line(s) to ADD Customer Premise Equipment o A customer object such as “Management”, and vpn such as “ManagementVpn” with connectivity type set to “Management” is already created o Note: You can refer to the IP Service Activator VPN User’s Guide for additional information on setting up management and customer VPNs. Access network is already pre-configured in IP Service Activator
  42. 42. Solution Uptake Guide IP Service Activator 7.2 42 o This is applicable to orders which include order line(s) to ADD Metro Ethernet Access Service o Switches to be used for VLAN enablement in the access network, are already discovered into a network object under the domain such as “access network”, capabilities fetched, and is managed by a Network Processor cartridge supporting the VLANDefinitions, and VLANInterface configuration policies such as the Cisco cartridge o Switches are already managed o A custom device role named ‘Switch’ is created, and the switches in the access network are assigned a role of Switch o Two custom interface roles are created, namely ‘MetroESwitch’, and ‘Trunk’. Assign the interface role ‘MetroESwitch’ to a single interface on each switch. (The roles Switch/MetroESwitch will be used for the VLANDefinitions configuration policy, when created, although the interface selection is not significant as the VLAn will be enabled on the switch not at an interface.) Interfaces, which will carry multiple VLANs are assigned the role ‘Trunk’. Access interfaces are assigned the role ‘Access’ role. A standard set of QoS policies and custom interface roles used to apply them for PE Ingress and Egress are pre-configured in IP Service Activator o This is applicable to orders which include order line(s) to ADD L3 Site Quality of Service for managed or unmanaged sites. o Pre-configure custom interface role, and an MQC-PHB Group object with classification and policing behavior for each of the three sample QoS Profiles: VoIP Profile, Retail Profile, and Data Profile to apply at the PE access interface Ingress for unmanaged sites. o Pre-configure custom interface role, and an MQC-PHB Group object with policing behavior only for each of the three sample QoS Profiles: VoIP Profile, Retail Profile, and Data Profile to apply at the PE access interface Ingress for managed sites. o Pre-configure custom interface role, and an MQC-PHB Group object with shaping and queuing behavior for each of the three sample QoS Profiles: VoIP Profile, Retail Profile, and Data Profile to apply at the PE access interface Egress for managed and unmanaged sites. o Note: You can refer to the IP Service Activator QoS User’s Guide for additional information on defining MQC-PHB Groups. Interface policy registration object is pre-configured for VLAN subinterface creation. This requires InterfaceManagementPolicyTypes.policy to be loaded into the domain. Sample configuration for Interface Policy Registration: o Name: VLAN subinterface creation o Action: Create o Menu Text: Create VLAN subinterface o Policy Type: Subinterface CreationVLAN Subinterface o Applied Context: Interface o Vendor Name: Cisco(9)
  43. 43. Solution Uptake Guide IP Service Activator 7.2 43 o SNMP ifType: 6 (6 is ethernet such as FastEthernet or GigabitEthernet) OSM Cartridge Pre-conditions: Each cartridge, which includes an activation task with IP Service Activator service actions, has model variable ACTIVATION_ENVIRONMENT_ID set to value: IPSA OracleCommsOSM_IPSA_L3MPLSVPN-Resources cartridge contains a file named SolutionConfiguration.xml in the resources folder. SolutionConfiguration.xml has values set to match pre-configured objects in IP Service Activator as displayed in Table 12. Table 12: Pre-configured Object Values Name Value ipsaDomain Value for ipsaDomain matches domain name in IP Service Activator such as: IPSA_DOMAIN ipsaProviderNetwork Value for ipsaProviderNetwork matches provider network name in IP Service Activator such as: provider network ipsaManagementCustomer Value for ipsaManagementVpnCustomer matches customer name in IP Service Activator such as: Management ipsaManagementVpn Value for management vpn created in IP Service Activator such as: ManagementVpn qosProfileMap This structure contains IDs of standard QoS policies and custom interface roles pre-configured in IP Service Activator for each of the three sample QoS Profiles: VoIP Profile, Retail Profile, and Data Profile deviceRoleMap This mapping contains IDs of pre-configured device roles in IP Service Activator, which can be provided to OSM activation tasks as configuration interfaceRoleMap This mapping contains IDs of pre-configured interface roles in IP Service Activator, which can be provided to OSM activation tasks as configuration interfacePolicyRegistrationMap This mapping contains IDs of pre-configured interface policy registration objects in IP Service Activator, which can be provided to OSM activation tasks as configuration
  44. 44. Solution Uptake Guide IP Service Activator 7.2 44 6.2 Basic Orchestration, variations on sites & L3 MPLS VPNs Summary This scenario specifies the proposed flow of activities required to provision a new multi-site L3 MPLS VPN for a customer where the request is initiated from a provisioning order. The reference implementation provides a simple, streamlined example of order processing to create a new customer’s L3 MPLS VPN, and builds on it with add, update, and delete operations on L3 MPLS VPN Sites. This has the dual purpose to illustrate greater use of the OSM activation task with conditional execution service actions and conditional inclusion of attributes, and more complex OSM orchestration, as well as best practices in IP Service Activator such as a pending delete pattern to provide additional failure handling options in case of delete failures. This scenario illustrates the flexibility of OSM orchestration to manage an arbitrary number of order lines. Using orchestration you can design an OSM sub-process to manage the activation of one instance of the service, and then model an orchestration stage to establish the granularity of activation such as activating all new L3 MPLS VPN Sites in the incoming order at once. Objective Provision a new L3 MPLS VPN for a new or existing customer, with all the services and service options that realize the products included in the sales order. This service fulfillment process includes all the sub-processes and activities required to: Enrich order data to assign the required technical service parameters, physical and logical resources Configure the VPN and its sites in IP Service Activator with all the related service components Activate the network elements in order to realize the services and service options requested Context Order Capture (CRM process). Select products, product actions, and options. Product View - Customer-facing product data (in CRM) L3 MPLS VPN L3 MPLS VPN Site A provisioning order is fulfilled by OSM Service Order Management. See tables below for test orders to be submitted for each detailed use case. Main/Alternate Flows Sales order submitted for immediate processing. A provisioning order is subsequently generated and handled by OSM Service Order Management. Primary and alternate flows are described per detailed use case in the tables below. Exceptions Manual failure recovery for the following cases: activation order failures

×