Cisco DSL Manager Error Code Reference

This appendix details the error messages that the Cisco Network Order Manager may receive from Cisco DSL Manager (CDM) if there are problems processing the work order. Error messages are returned as attribute values in the internal work order. The values of attributes in the internal work order are only returned if the attribute workOrder:DDM.finalWorkOrder is set in initiating external work order.

Either or both of the following attributes are set in the internal work order if an error condition occurs.

primitiveErrorMessage—Contains the error code generated by the first primitive to report an error
policyErrorMessage—Contains an error message that is set inside the policy

Table C-1 lists error messages for each element manager or network manager that CNOM communicates with during policy execution.

Table C-1: CDM Error Codes, Possible Causes, and Corrective Actions

Error Code	Possible Cause	Corrective Action
CDM_101 Unable to get ingress port from work order.	Invalid work order. The attribute `workOrder:DDMWorkOrder.ingressTP` is not present in the work order.	Make sure you are invoking a valid policy.
CDM_102 Missing DSL Service Characteristics in work order.	Invalid work order. The attribute `workOrder:DDMWorkOrder.serviceCharacteristics` is not present in the work order.	Verify that the attribute is passed to the CDM Network Order Adapter (NOA) with the profile name.
CDM_103 Missing Connection Identifier value in work order.	Invalid work order. The attribute `workOrder:DDMWorkOrder.connectionIdentifier` is not present in the work order.	Verify that the attribute is specified with a unique connection ID value.
CDM_104 `CDMDMM:GetTrunk` Unable to get ingress port from work order.	Invalid work order. The attribute `workOrder:DDMWorkOrder.ingressTP` is not present in the work order.	Make sure you are invoking a valid policy.
CDM_105 Unable to get containment path of the chassis object in Subtend view.	The CDM NOA module looks in the Subtend view for details on DSLAM connectivity. All chassis objects appear in the Subtend view as follows: Standalone chassis (which are not part of a subtend configuration) appear at the top level. Subtended chassis appear under the network port to which they are connected.	Make sure the chassis belonging to the line port is present in the Subtend view. To set up a subtend configuration, use the subtend command.
CDM_106 Unable to get the chassis ID of the top level chassis in the subtend path.	Internal Error.	None.
CDM_107 Unable to get trunk port for the top level chassis in the subtend path.	The CDM NOA module looks in the Subtend view for details on DSLAM connectivity. All chassis objects appear in the Subtend view as follows: Standalone chassis (which are not part of a subtend configuration) appear at the top level. Subtended chassis appear under the network port to which they are connected.	Make sure the trunk port of the chassis is configured correctly. To do this, specify the value 1 for the attribute `<`Trunk-Port-Name`> LocalDB:LCM-Subtend-MIB.isTrunk`. To set up the configuration, run the subtend command. To set up a subtend configuration, use the subtend command.
CDM_108 Unable to get connection object ID from work order.	Invalid policy.	Check the policy for aliasing.
CDM_109 Invalid connection object ID in work order.	Invalid policy.	Check the policy.
CDM_110 Unable to get ingress port object ID from work order.	Invalid policy.	Check the policy.
CDM_111 Invalid ingress port object ID in work order.	Invalid policy.	Check the policy.
CDM_112 Unable to get egress port object ID from work order.	Invalid policy.	Check the policy.
CDM_113 Invalid egress port object ID in work order.	Invalid policy.	Check the policy.
CDM_114 Unable to get ingress VPI value from work order.	The attribute `workOrder:DDMWOrkOrder.ingressVPI` is missing from the work order.	Make sure the attribute is present in the work order.
CDM_115 Unable to get ingress VCI value from work order.	The attribute `workOrder:DDMWOrkOrder.ingressVCI` is missing from the work order.	Make sure the attribute is present in the work order.
CDM_116 Unable to get egress VPI value from work order.	The attribute `workOrder:DDMWOrkOrder.egressVPI` is missing from the work order.	Make sure the attribute is present in the work order.
CDM_117 Unable to get egress VCI value from work order.	The attribute `workOrder:DDMWOrkOrder.egressVCI` is missing from the work order.	Make sure the attribute is present in the work order.
CDM_118 Unable to get ATM service characteristics from work order.	The attribute `workOrder:DDMWorkOrder.serviceCharacteristics` is missing from the work order.	Verify that the attribute is passed to the CDM NOA along with the profile name.
CDM_119 Unable to get trunk port of a chassis in subtend path.	The CDM NOA module looks in the Subtend view for details on DSLAM connectivity. All chassis objects appear in the Subtend view as follows: Standalone chassis (which are not part of a subtend configuration) appear at the top level. Subtended chassis appear under the network port to which they are connected.	Make sure the trunk port of the chassis is configured correctly. To do this, specify the value 1 for the attribute `<`Trunk-Port-Name`> LocalDB:LCM-Subtend-MIB.isTrunk`. To set up a subtend configuration, run the subtend command.
CDM_120 Unable to get containment path of the chassis object.	Internal Error.	None.
CDM_121 Unable to get object IDs of chassis in the subtend containment path.	Internal Error.	Make sure the containment path is valid.
CDM_122 Unknown chassis was recognized in subtend path.	The CDM NOA supports only NI-2 chassis in Subtend view.	Make sure there are no chassis which are not DSLAMs in the Subtend view.
CDM_124 Invalid VPI/VCI combination.	The VPI/VCI cannot be 0/0.	Make sure the VPI/VCI values for both ingress and egress attributes are valid. Check the log files for more details.
CDM_125 A connection was not set correctly.	The CDM NOA cannot successfully set up the connection across the subtend path.	Check the CDMDmmCtlr.log file for more details.
CDM_126 Unable to deploy `CDMDmmConnection` object.	The CDM NOA cannot create a `CDMDmmConnection` object under `connectionObjects:/<workOrder:DDMWorkOrder. connectionIdentifier>`.	Check the CDMDmmCtlr.log file for more details.
CDM_127 Unable to get connection object from work order.	Internal Error.	None.
CDM_200 Unable to get class inheritance for ingress port.	The CDM NOA cannot identify the ingress port's class model due to an invalid port object ID.	None.
CDM_201 Ingress port type is not supported in CDM DMM.	The CDM NOA supports only CAP, DMT, and SDSL for NI-2.	Make sure the line ID is set correctly for the port by checking `get_object_for_line <`line-id`>.` The object returned by the node must be of one of the above types.
CDM_202 Unable to get chassis object for ingress port.	The given ingress port object is not represented correctly in the ComponentManaged view. Either the ingress port is not a valid NI-2 port or the object no longer exists.	Make sure the line ID is set correctly for the port by checking `get_object_for_line <`line-id`>.` The object returned by the node must be of one of the above types.
CDM_203 Unable to get VCL attributes from the ingress and egress ports. Make sure the ports are valid DSL ports.	The CDM NOA cannot obtain virtual channel link (VCL) details from the ingress and egress ports to deploy a PVC object. The object may not be a valid type supported by CDM, or it may not exist in the CEMF database any more. The ingress port must be a valid CDM line port or subtend port and the egress port must be a valid trunk port for NI-2.	Make sure the objects are valid. Check the CDMDmmCtlr.log file for more details.
CDM_204 Unable to get VPI/VCI values from the PVC object. PVC connect did not succeed. Check log files for more details.	The CDM ATM Connection Manager cannot set up the connection. Possible reasons: VPI/VCI values are out of range. NI-2 modules support a VPI range of 0 to 255 and a VCI range of 32 to 65535 by default. VPI/VCI values have been allocated on the egress or ingress side. Connection parameters such as the ATM QoS parameters or network service access point (NSAP) address are not valid. Private Network-to-Network Interface (PNNI) is not configured for the node, and the CDM Domain Manager Module (DMM) cannot set up a soft PVC. Unable to communicate with the node due to invalid passwords. Loss of communication with the node.	Check the attribute `workOrder:DDMWorkOrder.primitiveErrorMessage` for more details. Check the CDMDmmCtlr.log and ATMCMController.log files for more details.
CDM_205 Unable to get PVC commission state from the PVC object. PVC connect did not succeed. Check log files for more details.	The CDM ATM Connection Manager cannot set up the connection. Possible reasons: VPI/VCI values are out of range. NI-2 modules support a VPI range of 0 to 255 and a VCI range of 32 to 65535 by default. VPI/VCI values have been allocated on the egress or ingress side. Connection parameters such as the ATM QoS parameters or NSAP address are not valid. Unable to communicate with the node due to invalid passwords. Loss of communication with the node.	Check the attribute `workOrder:DDMWorkOrder.primitiveErrorMessage` for more details. Check the CDMDmmCtlr.log and ATMCMController.log files for more details.
CDM_206 PVC object is not in normal state. PVC connect did not succeed. Element Manager reported the result: \n.	The CDM ATM ConnectionManager cannot set up the connection. Possible reasons: VPI/VCI values are out of range. NI-2 modules support a VPI range of 0 to 255 and a VCI range of 32 to 65535 by default. VPI/VCI values have been allocated on the egress or ingress side. Connection parameters such as the ATM QoS parameters or NSAP address are not valid. PNNI is not configured for the node, and the CDM DMM cannot set up a soft PVC. Unable to communicate with the node due to invalid passwords. Loss of communication with the node.	Check the attribute `workOrder:DDMWorkOrder.primitiveErrorMessage` for more details. Check the CDMDmmCtlr.log and ATMCMController.log files for more details.
CDM_207 Unable to get VPI/VCI values from PVC object.	The CDM ATM Connection Manager cannot set up the connection. Possible reasons: VPI/VCI values are out of range. NI-2 modules support a VPI range of 0 to 255 and a VCI range of 32 to 65535 by default. VPI/VCI values have been allocated on the egress or ingress side. Connection parameters such as the ATM QoS parameters or NSAP address are not valid. PNNI is not configured for the node, and the CDM DMM cannot set up a soft PVC. Unable to communicate with the node due to invalid passwords. Loss of communication with the node.	Check the attribute `workOrder:DDMWorkOrder.primitiveErrorMessage` for more details. Check the CDMDmmCtlr.log and ATMCMController.log files for more details.
CDM_208 Unable to get the NSAP address of the trunk port of the top level chassis. Make sure the value is set correctly.	The DMM module cannot retrieve the SNMP attribute with the NSAP address of the trunk port of the top node in a subtend environment. The CDM NOA uses this information to set up soft PVCs between the DSLAMs.	Make sure the node's ATM addresses are configured correctly.
CDM_209 Unable to complete deployment for PVC object.	The CDM NOA cannot deploy the PVC object for the ATM connection. Possible reasons: The object name is not unique, possibly because the VPI/VCI is already being used in the node. Connection parameters are not valid.	Check the CDMDmmCtlr.log and ATMCMController.log files for more details.
CDM_210 Deleting all PVCs failed.	The CDM NOA cannot delete all of the PVCs when attempting to remove the ATM connection.	Check the CDMDmmCtlr.log and ATMCMController.log files for more details.
CDM_211 Unable to apply ATM Profile for chassis. Element Manager returned the following report: \n.	The CDM NOA cannot apply the ATM profile.	Make sure the ATM profile is present and the connection parameters for the work order are valid.
CDM_212 Unable to connect PVC for work order. Element Manager reported the following result: /n	The CDM ATM Connection Manager cannot set up the connection. Possible reasons: VPI/VCI values are out of range. NI-2 modules support a VPI range of 0 to 255 and a VCI range of 32 to 65535 by default. VPI/VCI values have been allocated on the egress or ingress side. The connection parameters such as the ATM QoS parameters or NSAP address are not valid. PNNI is not configured for the node, and the CDM DMM cannot set up a soft PVC. Unable to communicate with the node due to invalid passwords. Loss of communication with the node.	Check the attribute `workOrder:DDMWorkOrder.primitiveErrorMessage` for more details. Check the CDMDmmCtlr.log and ATMCMController.log files for more details.
CDM_213 Unable to add PVC object to `CDMDMMconnection` object in connectionObjects view.	The CDM NOA cannot add a PVC object to the connectionObject view for display and disconnect.	Check the CDMDmmCtlr.log file for more details.
CDM_214 Unable to deploy PVC objects for work order.	The CDM NOA cannot add a PVC object to the connectionObject view for display or disconnect.	Check the CDMDmmCtlr.log file for more details.
CDM_215 Unable to check the SPVC Connection Status.	The CDM NOA cannot create an SPVC in the node. Possible reasons: VPI/VCI values are out of range. NI-2 modules support a VPI range of 0 to 255 and a VCI range of 32 to 65535 by default. VPI/VCI values have been allocated on the egress or ingress side. The connection parameters such as the ATM QoS parameters or NSAP address are not valid. PNNI is not configured for the node, and the CDM DMM cannot set up a soft PVC. Unable to communicate with the node due to invalid passwords. Loss of communication with the node.	Check the attribute `workOrder:DDMWorkOrder.primitiveErrorMessage` for more details. Check the CDMDmmCtlr.log and ATMCMController.log files for more details.
CDM_216 SPVC Connection did not succeed in the node.	The CDM NOA cannot create an SPVC in the node. Possible reasons: VPI/VCI values are out of range. NI-2 modules support a VPI range of 0 to 255 and a VCI range of 32 to 65535 by default. VPI/VCI values have been allocated on the egress or ingress side. The connection parameters such as the ATM QoS parameters or NSAP address are not valid. PNNI is not configured for the node, and the CDM DMM cannot set up a soft PVC. One or more interfaces in the subtend path are down. Unable to communicate with the node due to invalid passwords. Loss of communication with the node.	Check the attribute `workOrder:DDMWorkOrder.primitiveErrorMessage` for more details. Check the CDMDmmCtlr.log and ATMCMController.log files for more details.
CDM_301 Ingress Port is of unknown type.	The CDM NOA supports only Carrier Amplitude Phase (CAP), Discrete MultiTone (DMT), and single-line digital subscriber line (SDSL).	Make sure the line ID is set correctly for the port. Make sure the ingress port is valid. Check `get_object_for_line <`line-id`>`. The object returned by the node must be of one of the types listed at left.
CDM_308 Unable to get subscriber object for ingress port.	Internal Error.	None.
CDM_311 Unable to delete the subscriber object for ingress port. Element Manager reported the following: \n	The CDM NOA cannot delete the PVC.	Check the CDMDmmCtlr.log and C6100v30Ctrl.log files for more details.
CDM_354 Unable to get value for a profile attribute.	The given profile object is not assigned proper values for attributes.	Check the CDMDmmCtlr.log file for more details.
CDM_401 Chassis containment path is not provided in the work order.	The chassis containment path is expected in the work order attribute `workOrder:DDMWorkOrder.nodeContainmentPath`.	Make sure the attribute is set correctly.
CDM_402 Chassis containment path is not in proper format.	The chassis containment path is expected in the work order attribute `workOrder:DDMWorkOrder.nodeContainmentPath` as the value `<treeName>:/<objectName>/<objectName>`	Make sure the attribute is set correctly.
CDM_403 Subtend port containment path not in proper format.	The port containment path is expected in the work order attribute `workOrder:DDMWorkOrder.subtendPortContainmentPath` as the value `<treeName>:/<objectName>/<objectName>`	Make sure the attribute is set correctly.
CDM_404 Chassis or port containment path is invalid. Check the containment paths.	The chassis and port containment paths are expected in work order attributes `workOrder:DDMWorkOrder.chassisContainment Path` and `workOrder:DDMWorkOrder.subtendPort ContainmentPath` as the value `<treeName>:/<objectName>/<objectName>`	Make sure the attributes are set correctly.
CDM_405 Given containment path is not a valid chassis object.	The chassis containment path object in the attribute `workOrder:DDMWorkOrder.chassisContainmentPath` was not an NI-2 chassis object.	Make sure the attribute represents a chassis object.
CDM_407 Unable to get the NI-2 module for the chassis. Make sure the chassis has been commissioned.	The chassis did not contain an NI-2 module in the ComponentManaged view.	Make sure the chassis has been commissioned and the NI-2 module has been discovered correctly.
CDM_408 Too many NI-2 modules for the chassis.	The CDM NOA found more than one NI-2 module for the given chassis.	None.
CDM_409 Unable to get the NI-2 ports for the chassis. Make sure the chassis has been commissioned.	The chassis did not contain an NI-2 module in the ComponentManaged view.	Make sure the chassis has been commissioned and the NI-2 module has been discovered correctly.
CDM_412 Unable to identify trunk and subtend ports for NI-2 chassis. Check log files.	The CDM NOA uses the port number to identify the trunk port (with port number 1) and subtend port. The CDM NOA is not able to retrieve this information from CEMF database.	None.
CDM_414 Unable to mark the trunk and subtend port for the chassis.	The CDM NOA uses port numbers to identify the trunk and subtend ports and marks the port using the attribute `LocalDB:CDM-Subtend-MIB.isTrunk`.	None.
CDM_416 Unable to add the chassis and the ports to subtend tree. Make sure the subtending port if any is present in the view already.	The CDM NOA cannot add the chassis to the Subtend view, possibly because the parent subtending port is not present in the view.	Make sure the subtending port is present in the view.
Policy Error Messages
CDM_501 Unable to identify the DSL port from the line ID for work order.	The CDM NOA cannot identify the DSL port for a given line ID.	Use `get_object_for_line <`line-id`>` to make sure the line ID is correctly set up for the port. This should return success with valid line ID value.
CDM_502 Unable to get trunk port of the top level chassis in subtend path.	The CDM NOA cannot identify the egress end point for the DSLAM subdomain.	Check the primitive error message in `workOrder:DDMWorkOrder.primitiveError Message` for more details.
CDM_503 Unable to create connection object in connectionObjects view.	The CDM NOA cannot create the connection object with the name given in `workOrder:DDMWorkOrder.connectionIdentifier` in the connectionObjects view.	Make sure the connection identifier is unique and does not already exist in the connectionObjects view.
CDM_504 Unable to configure the DSL port with DSL service characteristics.	The CDM NOA cannot apply DSL service characteristics for the given port. Possible reasons: Profile does not exist for the given name. Given parameters are not valid for the port. Unable to communicate with the node.	Check the primitive error message in `workOrder:DDMWorkOrder.primitiveError Message` for more details.
CDM_505 Unable to set up PVCs in the subtend path.	The CDM NOA cannot set up a PVC in any of the nodes in the subtend path or could not set up a soft PVC in the leaf node.	Check the primitive error message in `workOrder:DDMWorkOrder.primitiveError Message` for more details.
CDM_506 Unable to identify the object underneath the connectionObjects view with the name provided in `workOrder:DDMWorkOrder.connectionIdentifier`.	The CDM NOA cannot get the connection objects to initiate disconnect for the given connection identifier.	Make sure the connection identifier is valid.
CDM_507 Unable to delete PVC objects in subtend path.	The CDM NOA cannot delete the PVC in the node and/or CEMF database. Possible reasons: PVC was already deleted from the node. Unable to communicate with the node.	Check the primitive error message in `workOrder:DDMWorkOrder.primitiveError Message` for more details.
CDM_508 Unable to delete the connection object. Check ddmGateway.log for more details.	The CDM NOA cannot delete the connection object from the view.	Check the ddmGateway.log file for more details.
CDM_524 Unable to modify the profile object. Check log for errors.	The CDM NOA cannot update the parameters in the profile object.	Check the CDMDmmCtlr.log file for more details.
CDM_525 Unable to create the profile parent `profileContainment: /Cisco` for adding profile objects.	The CDM NOA uses the technology name Cisco for NI-2 ATM QoS profiles. The CDM NOA could not add the technology object for adding the appropriate profile.	Check the log for errors.
CDM_526 Unable to create the profile object under parent `profileContainment: /Cisco`.	The CDM NOA cannot create the profiles for the CDM NI-2 module. A profile may already exist with this name.	Make sure a profile with this name does not already exist by using `get_ni2_profile ATMQoS <`profileName`>`.
CDM_527 Unable to create object for profile.	The CDM NOA cannot create the profile for the NI-2 module.	Check the CDMDmmCtlr.log file for more details.
CDM_528 Unable to find the profile object in profileContainment view under Cisco object.	The CDM NOA cannot find the profile in the profileContainment view.	Make sure the profile exists by using `get_ni2_profile ATMQoS <`profileName`>`.
CDM_529 Invalid profile.	Internal Error.	Internal Error. Profile must have an ATM `CiscoVirtualCircuit` object under the profile object.
CDM_530 Unable to modify the profile object with new values.	The CDM NOA cannot update the profile object.	Check the CDMDmmCtlr.log file for more details.
CDM_531 Unable to delete the object.	The CDM NOA cannot delete the NI-2 profile from the CEMF database.	Check the CDMDmmCtlr.log file for more details.
CDM_532 Unable to create the profile parent `profileContainment: /CAPTech` for adding profile objects.	The CDM NOA uses the technology name Cisco for NI-2 CAP profiles. The CDM NOA cannot add the technology object for adding the appropriate profile.	None.
CDM_533 Unable to create the profile object under parent `profileContainment: /CAPTech`. Make sure the profile name is unique.	The CDM NOA cannot create the profiles for the CDM NI-2 module. A profile may already exist with this name.	Make sure a profile with this name does not already exist by using `get_ni2_profile CAP <`profileName`>`.
CDM_534 Unable to find the profile object in profileContainment view under `CAPTech` object.	The CDM NOA cannot find the profile in the profileContainment view.	Make sure the profile exists by using `get_ni2_profile CAP <`profileName`>`.
CDM_535 Invalid profile.	Internal Error.	Internal Error. The profile must have an ATM `CiscoCAPFunctionality` object under the profile object.
CDM_536 Unable to create the profile parent `profileContainment: /SDSLTech` for adding profile objects.	The CDM NOA uses the technology name Cisco for NI-2 SDSL profiles. The CDM NOA cannot add the technology object for adding the appropriate profile.	Check the log for errors.
CDM_537 Unable to create the profile object under parent `profileContainment: /SDSLTech`.	The CDM NOA cannot create the profiles for the CDM NI-2 module. A profile may already exist with this name.	Use `get_ni2_profile SDSL <`profileName`>` to make sure a profile with this name does not already exist.
CDM_538 Unable to find the profile object in profileContainment view under `SDSLTech` object.	The CDM NOA cannot find the profile in the profileContainment view.	Make sure the profile exists using `get_ni2_profile SDSL <`profileName`>`.
CDM_539 Invalid profile.	Internal Error.	Internal Error. Profile must have a `CiscoSDSLFunctionality` object under the profile object.
CDM_540 Unable to create the profile parent `profileContainment: /ADSLIfManager` for adding profile objects.	The CDM NOA uses the technology name Cisco for NI-2 ADSL (subset of DMT) profiles. The CDM NOA cannot add the technology object for adding the appropriate profile.	Check the log for errors.
CDM_541 Unable to create the profile parent `profileContainment: /DMTTech` for adding profile objects.	The CDM NOA uses the technology name Cisco for NI-2 DMT profiles. The CDM NOA cannot add the technology object for adding the appropriate profile.	Check the log for errors.
CDM_542 Unable to create the profile object under parent `profileContainment: /ADSLIfManager`.	The CDM NOA cannot create the profiles for the CDM NI-2 module. A profile may already exist with this name.	Use `get_ni2_profile DMT <`profileName`>` to make sure a profile with this name does not already exist.
CDM_544 Unable to create the profile object under parent `profileContainment: /DMTTech`.	The CDM NOA cannot create the profiles for the CDM NI-2 module. A profile may already exist with this name.	Make sure the profile name is unique.
CDM_545 Unable to find the profile object in profileContainment view under `ADSLIfManager` object.	The CDM NOA cannot find the profile in the profileContainment view.	Make sure the profile exists by using `get_ni2_profile DMT <`profileName`>`.
CDM_546 Unable to find the profile object in profileContainment view under `DMTTech` object.	The CDM NOA cannot find the profile in the profileContainment view.	Make sure the profile exists by using `get_ni2_profile DMT <`profileName`>`.
CDM_547 Invalid profile. Profile must have a `CiscoADSLFunctionality` object underneath the profile object.	Internal Error.	None.
CDM_548 Invalid profile.	Internal Error.	Profile must have a `CiscoDMTFunctionality` object under the profile object.
CDM_550 Unable to modify the ADSL profile object with new values.	The CDM NOA cannot update the profile object.	Check the CDMDmmCtlr.log file for more details.
CDM_551 Unable to modify the DMT profile object with new values.	The CDM NOA cannot update the profile object.	Check the CDMDmmCtlr.log file for more details.
CDM_552 Unable to find the ADSL profile object in profileContainment view.	The CDM NOA cannot find the profile in the profileContainment view.	Make sure the profile exists by using `get_ni2_profile DMT <`profileName`>`.
CDM_553 Unable to find the DMT profile object in profileContainment view.	The CDM NOA cannot find the profile in the profileContainment view.	Make sure the profile exists by using `get_ni2_profile DMT <`profileName`>`.
CDM_554 Unable to delete the ADSL profile object.	The CDM NOA cannot delete the profile from the profileContainment view.	Check the CDMDmmCtlr.log file for more details.
CDM_555 Unable to delete the DMT profile object.	The CDM NOA cannot delete the profile from the profileContainment view.	Check the CDMDmmCtlr.log file for more details.
CDM_556 Unable to delete profile objects.	The CDM NOA cannot delete the profile from the profileContainment view.	Check the CDMDmmCtlr.log file for more details.
CDM_557 Unable to set up subtend.	The CDM NOA cannot set up subtending for the given node.	Check the attribute `workOrder:DDMWorkOrder.primitiveError Message` for more details.
CDM_568 Identified port object does not belong to DSLAM subdomain.	The CDM NOA expects the line ports for the given line ID to be assigned the subdomain value DSLAM.	Use `get_object_for_line <`line-id`>` to make sure the line ID is set to the subdomain value of DSLAM.
CDM_569 No valid `L` attribute in the work order.	Ingress input must be provided either as line ID in the attribute `workOrder:DDMWorkOrder.ingressIdentifier`or as port containment path in the attribute `workOrder:DDMWorkOrder.ingressContainment Path`.	Make sure that one of these attributes is present in the work order.
CDM_702 Error parsing string.	Corrupted attributes passed to the `restorePVC` primitive.	Check that the correct Data Recovery log information is supplied.
CDM_703 Unable to resolve TP paths.	Trying to restore a connection that refers to a nonexisting (removed) chassis.	Make sure the chassis exists.
CDM_704 Ingress/Egress paths cannot be the same.	Ingress and egress paths must be different. In the case of `restorePVC`, this error message may be the result of an internal error.	Check the log files.
CDM_705 Unable to tokenize.	Internal error.	Check the log files.
CDM_711 Unable to resolve attribute IDs for query.	Internal error.	None.
CDM_713 Query returned invalid object.	Internal error.	Check the log files.
CDM_714 Unable to get `ATMCMController:CEMCS-ATM-Conn_MIB.destNsap Addr` attribute. Check attribute lists.	No NSAP address attribute passed to the `restorePVC` primitive.	Check that the correct Data Recovery log information is supplied.
CDM_715 SNMP attribute missing. Check VCL attributes list.	Incorrect SNMP attributes were passed to the `restorePVC` primitive.	Check that the correct Data Recovery log information is supplied.
CDM_716 `DeployPVCobject` failed.	The PVC object cannot be deployed.	Check that the port object in ComponentManaged view includes a PVC object with the same name.
CDM_718 Unable to apply the QoS profile.	The ATM QOS profile cannot be applied. The profile may not exist.	Check that the profile exists.
CDM_721 Unable to add PVC object to connection object.	The PVC object cannot be added to the connectionObjects view.	Check that there are no objects with the same name.
CDM_751 Wrong PVC type.	An incorrect PVC type was supplied. There are two PVC types supported: PVC SPVC	Check that the correct Data Recovery log information was supplied.

bigmir)net

284

Table of Contents

Cisco DSL Manager Error Code Reference