Identify if MVSO Failed or Crashed
Available Languages
Contents
Introducuction
This document helps to identify the current status of Cisco Prime Order Fullfilment - Multivendor Service Orchestration (MVSO) after it has run .
Contributed by Julio Molina Soler, Cisco TAC Engineer.
Prerequisites
Requirements
Cisco recommends that you have knowledge of these topics:
- MVSO
Components Used
This document is not restricted to specific software versions.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Background Information
It is crucial to identify the status of a Multivendor Service Orchestration (MVSO) and if there is a problem, determine what is the current output state:
- MVSO did the job but it return errors
- MVSO returned succeed or failed
- Tthe software itself crashed and it returned nothing.
When you receive the order logs, it is a zip file with the order number as name. When you extract it you see a list of 8 files with .log extension
Explanation of the files
| psa_request_##.log | This file will present the procedures executed in MVSO, after receiving the order from the Cramer, and the time it took. |
| message_payload_#id#.log | The order payload received in XML format |
| get_mvso_environment_values_#id#.log | Current installation of MVSO |
| timeout_values_#id#.log | Show some timeout values |
MVSO failed
In psa_request_##.log you see time for all of the procedures, but the Cramer receives the message of failure
old 4: where request_service_id = '&1'
new 4: where request_service_id = '120902'
REQUEST_SERVICE_ID O2S_ORDER_ID PSA_TRANSACTION_NAME TIME
-------------------- ------------ ------------------------------ ----------
120902 230402 MVSO RFS.VALIDATE 00:00:01
120902 230403 MVSO RFS.MANAGE RFS 00:00:02
120902 230404 MVSO RFS.MANAGE RESOURCE 00:00:01
120902 230405 MVSO RFS.CONFIGURE RFS 02:02:53
LAST_ORDER_ID=230405
SAFE_CALL_ID=71771
SAFE_CALL_ID_ROLLBACK=71795
MVSO crashed
In psa_request_##.log you see no time for one of the procedures and the Cramer receives nothing.
old 4: where request_service_id = '&1'
new 4: where request_service_id = '118152'
REQUEST_SERVICE_ID O2S_ORDER_ID PSA_TRANSACTION_NAME TIME
------------------ ------------ ------------------------------ ----------
118152 224571 MVSO RFS.VALIDATE 00:00:08
118152 224572 MVSO RFS.MANAGE RFS 00:00:02
118152 224573 MVSO RFS.MANAGE RESOURCE ::
LAST_ORDER_ID=224573
no safe called
Comparison between MVSO crash and order failures
| ARM_REQUEST_ID | REQUESTOROPERATIONID | REQUESTORSERVICEID | PARENT_REQUESTORSERVICEID | ARM_REQUEST_COMPONENT | REQUEST_TYPE | REQUEST_STATUS | REQUEST_INFO | REQUEST_DATE | REQUEST_ATTEMPTS | REQUEST_XML | MVSO_REQUEST_XML | MVSO_ACK_XML | MVSO_RESPONSE_XML | RESPONSE_STATUS_XML | RESPONSE_PAYLOAD | RESPONSE_STATUS | ARM_RESPONSE_STATUS | RESPONSE_INFO | RESPONSE_DATE | RESPONSE_ERRORCODE | RESPONSE_ERRORTEXT | RECOMMENDATION |
| 558891564 | 558891564 | DE21462 | NULL | DE | ACTIVATE | SUCCESS | Checking prerequisites::::Message sent to JMS Request Queue::::Message picked by MVSORequestMDB::::Web Service Invoked::::MVSO ACK Received | 09/22/2017 12:04:21 | 1 | ... | ... | ... | NULL | NULL | IN PROGRESS | NULL | ::::MVSO sent Transaction Response | 09/22/2017 12:04:22 | NULL | NULL | NULL | |
| 558891564 | 558891564 | DE21461 | NULL | DE | ACTIVATE | SUCCESS | Checking prerequisites::::Message sent to JMS Request Queue::::Message picked by MVSORequestMDB::::Web Service Invoked::::MVSO ACK Received | 09/22/2017 11:29:49 | 1 | ... | ... | SUCCESS | ... | <job id="558891564"><status>FAILURE</status></job> | ... | FAILURE | SUCCESS | ::::MVSO sent Transaction Response::::MVSO sent Transaction Complete::::MVSO Response placed on Response queue::::Message picked by MVSOResponseMDB::::Starting DE callout at 11:30:21::::Parent Procedure: MVSOResponseMDB.onMessage()::::<job id="558891564"><status>FAILURE</status></job>::::End DE callout at11:30:21::DE Error Code:0::DE Error Text:null | 09/22/2017 11:30:21 | 10100021 | RFS ID "ETHERNET_FLOW_POINT_RFSID_UPDATE" not found. | NULL |
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)