Cisco Cisco Prime Central 1.5.1 开发者指南
3GPP OSS Integration
Cisco Prime OSS Integration Guide for MTOSI and 3GPP
63
Available
Exception
Exception
from the Web Service
call, stating that no
DMs are available.
call, stating that no
DMs are available.
PN is not proper. The
Integration layer was
not able to
communicate with the
domain manager ( DM
).
Integration layer was
not able to
communicate with the
domain manager ( DM
).
Networks application is
running.
running.
Network Connectivity to the
Prime Networks machine is
proper.
Prime Networks machine is
proper.
Exception
indicating No
Managed
Element in
Network
indicating No
Managed
Element in
Network
A call to
getAllInventory
returns a Web
Services exception
stating that there are
no Managed
Elements in the
network.
getAllInventory
returns a Web
Services exception
stating that there are
no Managed
Elements in the
network.
The PN system is not
configured to have any
managed elements
configured to have any
managed elements
Verify if the PN system
contains any managed
elements.
contains any managed
elements.
Add network elements that
can be managed by PN.
can be managed by PN.
Issue the Web Service request.
Verify if the Exception
message disappears and Web
Service response indicating
start of inventory collection
appears.
message disappears and Web
Service response indicating
start of inventory collection
appears.
Verify if Inventory files are
getting created
getting created
Inventory files
are not copied
to FTP servers
are not copied
to FTP servers
Inventory files are
not present on the
FTP server (primary
and secondary)
configured.
not present on the
FTP server (primary
and secondary)
configured.
The FTP server
configuration is not
proper.
configuration is not
proper.
Verify the FTP server
hostname is reachable.
hostname is reachable.
FTP / SFTP service is running
on the configured hosts.
on the configured hosts.
Login and password is
properly specified during the
FTP configuration setup.
properly specified during the
FTP configuration setup.
Note: The password will be encrypted
in the configuration file.
getManagedEle
ment returns a
SOAP Exception
ment returns a
SOAP Exception
A call to
getManagedElement
returns a Web
Services exception
stating that the
device is not in up-
state though it is
actually up.
getManagedElement
returns a Web
Services exception
stating that the
device is not in up-
state though it is
actually up.
The device name
specified in request is
incorrect
specified in request is
incorrect
Cross check the device name in
getAllManagedElementNames
response and verify if the device is
not in up state
getAllManagedElementNames
response and verify if the device is
not in up state
getManagedEle,
ent returns an
ME not in up
state message
ent returns an
ME not in up
state message
Call to
getManagedElement
returns with
exception indicating
the ME is not in up-
state
getManagedElement
returns with
exception indicating
the ME is not in up-
state
The Managed Element
is either not managed
by the EMS or is not a
valid name.
is either not managed
by the EMS or is not a
valid name.
This is a valid condition. The managed
element is expected to be managed by
the EMS.
element is expected to be managed by
the EMS.
Call to any
JMS did not get
There might be an
Please check the log file under the