The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter documents service request transition states for MPLS.
Table A-1 and Table A-2 show the state transition paths for Prime Fulfillment service requests. The beginning state of a service request is listed in the first column; the states that service requests transition to are displayed in the heading row.
For example, to use Table A-1 to trace the state of a Pending service request to Functional, find Pending in the first column and move to your right until you find Functional in the heading. You can see that for a service request to move from Pending to Functional, a successful routing audit must take place.
Table A-1 shows the service request transitions from Requested to Lost.
Table A-2 shows the service request transitions from Broken to Closed.