Filter
Top Products
11-5
Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0
OL-21636-01
Chapter 11 Deploying, Monitoring, and Auditing Service Requests
Deploying Service Requests
Table 11-1 Summary of Cisco IP Solution Center Service Request States
Service Request Type Description
Broken
(valid only for MPLS
services)
The router is correctly configured but the service is unavailable (due to a
broken cable or Layer 2 problem, for example).
An MPLS service request moves to Broken if the auditor finds the routing
and forwarding tables for this service, but they do not match the service
intent.
Closed A service request moves to Closed if the service request should no longer be
used during the provisioning or auditing process. A service request moves to
the Closed state only upon successful audit of a decommission service
request. ISC does not remove a service request from the database to allow
for extended auditing. Only a specific administrator purge action results in
service requests being removed.
Deployed A service request moves to Deployed if the intention of the service request
is found in the router configuration file. Deployed indicates that the
configuration file has been downloaded to the router, and the intent of the
request has been verified at the configuration level. That is, ISC downloaded
the configlets to the routers and the service request passed the audit process.
Failed Audit This state indicates that ISC downloaded the configlet to the router
successfully, but the service request did not pass the audit. Therefore, the
service did not move to the Deployed state. The Failed Audit state is
initiated from the Pending state. After a service request is deployed
successfully, it cannot re-enter the Failed Audit state (except if the service
request is redeployed).
Failed Deploy The cause for a Failed Deploy status is that DCS reports that either the
upload of the initial configuration file from the routers failed or the
download of the configuration update to the routers failed (due to lost
connection, faulty password, and so on).
Functional
(valid only for MPLS
services)
An MPLS service request moves to Functional when the auditor finds the
VPN routing and forwarding tables (VRF) for this service and they match
with the service intent. This state requires that both the configuration file
audit and the routing audit are successful.
Invalid Invalid indicates that the service request information is incorrect in some
way. A service request moves to Invalid if the request was either internally
inconsistent or not consistent with the rest of the existing network/router
configurations (for example, no more interfaces were available on the
router). The Provisioning Driver cannot generate configuration updates to
service this request.
Lost A service request moves to Lost when the Auditor cannot find a
configuration-level verification of intent in the router configuration files.
The service request was in the Deployed state, but now some or all router
configuration information is missing. A service request can move to the Lost
state only when the service request had been Deployed.