Cisco Cisco Prime Central 1.5 Developer's Guide
MTOSI OSS Integration
Cisco Prime OSS Integration Guide for MTOSI and 3GPP
116
116
OL-31029-01
NOTE: Any failure in sending the Start Tracking request will not stop this API from listing
devices. However the status label will clearly capture the information that start tracking
failed.
devices. However the status label will clearly capture the information that start tracking
failed.
NOTE: The explicit request to start delta inventory tracking is not required from PN
version 4.1. The tracking is started internally when the Prime Network Integration Layer
starts.
version 4.1. The tracking is started internally when the Prime Network Integration Layer
starts.
Sl.No
Scenario
Result
1
Prime Network restarts
If a Prime Network restarts,then all the Managed
Elements will be shown as dirty i.e “UPDATE” in the
operation field in response.
Elements will be shown as dirty i.e “UPDATE” in the
operation field in response.
2
When there are no
changes after Start
Tracking was initiated
-or-
When Start Tracking
procedureitself has failed
changes after Start
Tracking was initiated
-or-
When Start Tracking
procedureitself has failed
The response will contain the message "No changes
detected or Start tracking not issued."
detected or Start tracking not issued."
8.12 MTOSI Standard Compliance
Cisco MTOSI Information Model is designed to conform to MTOSI 2.0 specifications.
Cisco reference implementation extensions are introduced to support proprietary APIs and
name space as per Cisco Prime Release requirements. Refer to the MTOSI standards in the
link:
Cisco reference implementation extensions are introduced to support proprietary APIs and
name space as per Cisco Prime Release requirements. Refer to the MTOSI standards in the
link:
8.13 Trouble Shooting - MTOSI
The below table includes the issues that might be encountered while setting up OSS
integration layer and steps to troubleshoot the problem.
integration layer and steps to troubleshoot the problem.
Table 8-4: OSS Integration Problems and Troubleshooting Procedure
Problem
Description
Description
Indication
Probable Cause
Troubleshooting Procedure
Web Services
Security
Exception
Security
Exception
Web Service call to
any of the Interfaces
will throw a WS
Security exception
with authentication
failure message
any of the Interfaces
will throw a WS
Security exception
with authentication
failure message
The user ID / password
provided for the web
service call might not
be correct.
provided for the web
service call might not
be correct.
Use a proper User ID / password for
the web services call.
the web services call.
No DMs
Available
Exception
Available
Exception
Exception message
from the Web Service
call, stating that no
from the Web Service
call, stating that no
The communication to
PN is not proper. The
Integration layer was
PN is not proper. The
Integration layer was
Verify that the Prime
Networks application is
running.
Networks application is
running.