Cisco IP Solution Center System Error Messages, 5.0
System Error Messages
Downloads: This chapterpdf (PDF - 1.17MB) The complete bookPDF (PDF - 1.45MB) | Feedback

System Error Messages

Table Of Contents

System Error Messages

Messages 0-99 (Repository Messages)

Messages 100-199 (Repository Messages)

Messages 300-399 (Repository Messages)

Messages 400-499 (Repository Messages)

Messages 500-599 (Repository Messages)

Messages 600-699 (Repository Messages)

Messages 700-799 (Repository Messages)

Messages 800-899 (Repository Messages)

Messages 900-999 (Repository Messages)

Messages 1000-1099 (API Messages)

Messages 1100-1199 (API Messages)

Messages 1200-1299 (Traffic Engineering Management Messages)

Messages 1300-1399 (Repository Messages)

Messages 1400-1499 (Repository Messages)

Messages 1500-1599 (Repository Messages)

Messages 2000-2099 (API Messages)

Messages 2100-2199 (API Messages)

Messages 5000 - 6550 (Discovery Messages)

Messages Without Numbers (L2TPv3, L2VPN, MPLS, RBAC, and VPLS messages)

Messages—L2TPv3

Messages—L2VPN Only

Messages—L2VPN and VPLS Only

Messages—L2VPN, VPLS, and MPLS (multi-hop)

Messages—MPLS Only

Messages—RBAC Only


System Error Messages


This chapter gives some of the IP Solution Center (ISC) error messages with explanations and in some cases recommended actions. If there is no Recommended Action(s) or you still have questions, contact the Cisco Technical Assistance Center (TAC) or search the Cisco Technical Support Website, as explained in the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page -vii.

For ease of reaching a specific error message for which you want to find more information, the messages are broken into the following categories:

Messages 0-99 (Repository Messages)

Messages 100-199 (Repository Messages)

Messages 300-399 (Repository Messages)

Messages 400-499 (Repository Messages)

Messages 500-599 (Repository Messages)

Messages 600-699 (Repository Messages)

Messages 700-799 (Repository Messages)

Messages 800-899 (Repository Messages)

Messages 900-999 (Repository Messages)

Messages 1000-1099 (API Messages)

Messages 1100-1199 (API Messages)

Messages 1200-1299 (Traffic Engineering Management Messages)

Messages 1300-1399 (Repository Messages)

Messages 1400-1499 (Repository Messages)

Messages 1500-1599 (Repository Messages)

Messages 2000-2099 (API Messages)

Messages 2100-2199 (API Messages)

Messages 5000 - 6550 (Discovery Messages)

Messages Without Numbers (L2TPv3, L2VPN, MPLS, RBAC, and VPLS messages)

Messages—L2TPv3

Messages—L2VPN Only

Messages—L2VPN and VPLS Only

Messages—L2VPN, VPLS, and MPLS (multi-hop)

Messages—MPLS Only

Messages—RBAC Only


Note To find API messages, see "API Message Format." For all other messages, look in the log. If you find no message number, you can search this chapter on a message string.


Messages 0-99 (Repository Messages)

Error Message

0: Attribute {0} does not exist

Explanation The value for the attribute is not specified.

Recommended Action Set the attribute value.

Error Message

1: Attribute not found for Column {0}

Explanation A dependent attribute for a column is not specified.

Recommended Action Set the attribute value.

Error Message

2: Unable to get the Connection to the Database. {0}

Explanation Database connection is not available.

Recommended Action Database is running -> Listener and database instance are up. Location of DB_PORT variable can be specified.

Error Message

3: Cannot instantiate abstract class {0}

Explanation This error message appears while trying to instantiate an abstract class.

Recommended Action Abstract class cannot be instantiated.

Error Message

4: ClassDictionary for class ==> {0} Not Found

Explanation Class information is not found for a class in ISC. Internal error.

Error Message

5: Cannot load {0} for {1}.

Explanation Internal error.

Error Message

6: Class Map not updated because {0}.

Explanation The error message explains the detail. Internal error.

Error Message

7: Class ==> {0} not found.

Explanation The specified class is not found. It could be an internal error.

Recommended Action Make sure you have sourced vpnenv.(c)sh.

Error Message

8: Column not found for attribute {0}.

Explanation The specified column is missing in the database.

Recommended Action Set the attribute value.

Error Message

9: Database driver not available

Explanation The JDBC driver for the database is not found. If your database is Sybase from ISC, it could be an internal error.

Recommended Action Make sure your database driver is installed properly.

Error Message

10: Database URL not available

Explanation The database URL is not specified.

Recommended Action Make sure your database URL is specified.

Error Message

11: Database not accessible ==> {0}.

Explanation The database is not accessible by ISC.

Recommended Action Make sure your database is up and running.

Error Message

12: DCPL property ==> {0} not found.

Explanation The specified DCPL property is not set. It could be an internal error.

Recommended Action Specify the property value.

Error Message

13: Field type {0} not implemented.

Explanation The field type given in the error message is not implemented or supported. Internal error.

Error Message

14: File {0} not found

Explanation The specified file is not found in the ISC path. If this is an ISC file, then it could be an internal error.

Recommended Action Make sure the file is in the ISC path, meaning ISC_HOME, REPOSITORY_HOME, and VPNSC_TMP.

Error Message

15: Incorrect class name; expected {0}, got {1}.

Explanation Wrong class name found for a class.

Error Message

16: Incorrect object type; expected {0}, got {1}.

Explanation Object type is incorrect.

Error Message

17: IO Exception while accessing {0}

Explanation The exception message explains the error in detail.

Error Message

18: No attributes found for class {0}.

Explanation Attributes are missing for a class.

Error Message

19: Attribute {0} is null.

Explanation Attribute value is not specified. Null value found for the attribute.

Recommended Action Set a valid value to the specified attribute.

Error Message

20: Password not available

Explanation The password is not available in the database.

Recommended Action Set the password.

Error Message

21: Could not update {0} to database; the object could have been updated already by another user.

Explanation The object is already modified by another user. This could occur if multiple users are trying to modify the same object.

Recommended Action Make sure only one user is working on the connection object at a time.

Error Message

22: SQL Exception {0}

Explanation The exception message explains the error in detail.

Error Message

23: SQL Type {0} not implemented

Explanation This SQL type is not implemented in ISC.

Error Message

24: SQL Type Unknown for {0}

Explanation An unknown type was found for an object.

Error Message

25: Table --> {0} Not Found

Explanation The specified table is missing in the database.

Error Message

26: User Name not available

Explanation A specified username is not available in the database.

Recommended Action Make sure the username is stored in the database.

Error Message

27: This method ({0}) should never have been called.

Explanation The method given in the error message should not be invoked.

Error Message

28: Class {0} could not be instantiated.

Explanation The specified class cannot be instantiated. It could be an internal error.

Recommended Action Avoid instantiating the class.

Error Message

29: Cannot delete object.

Explanation This object cannot be deleted because some other objects might be dependent on it.

Recommended Action First try deleting the dependencies.

Error Message

30: Could not roll back transaction.

Explanation Rollback on this commit failed.

Error Message

31: General Exception

Explanation The given error message has the details.

Error Message

32: Null transaction.

Explanation Invalid transaction.

Error Message

33: Unable to load file "{0}".

Explanation The specified file is not loaded in the JVM.

Recommended Action The file might be missing or it might not be in the correct path.

Error Message

34: The size of data in the attribute, {0} of {1} object.

Explanation The given error message has the details.

Error Message

35: Unable to Clone the object. {0}

Explanation The specified object cannot be cloned.

Error Message

36: Unable to set default value. {0}

Explanation Error occurred while setting default value for the specified attribute.

Error Message

37: Unable to set attribute value. {0}

Explanation Error occurred while setting a value for the specified attribute.

Error Message

38: Invalid value, {0} detected for the argument.

Explanation Wrong value set for the argument.

Recommended Action Set valid value for the argument.

Error Message

39: {0} {1}. Increase the value for the DCPL property, repository.Concurrency.NO_OF_RETRIES.

Explanation Too many concurrent transactions; unable to get a unique ID for a table {0}.

Recommended Action Increase the value for the DCPL property: repository.Concurrency.NO_OF_RETRIES.

Messages 100-199 (Repository Messages)

Error Message

133: ResourcePool: Value {0} already exists.

Explanation Value specified by variable {0} already exists in the repository.

Recommended Action Do not allocate the same resource multiple times.

Error Message

134: ResourcePool: Block overflows into previous block.

Explanation Internal resource pool error when the resource pools overflow into the previous block.

Recommended Action Check the resource pools.

Error Message

135: ResourcePool: Block overflows into next block.

Explanation Internal resource pool error when the resource pool overflows into the next block.

Recommended Action Check the resource pools.

Error Message

136: Cannot allocate resource. Pool is empty.

Explanation Cannot allocate resource because the pool is empty.

Recommended Action Create a new resource pool.

Error Message

137: ResourcePool: Pool contains insufficient blocks.

Explanation Resource pool does not contain enough resources.

Recommended Action Check and create new resource pools with adequate range.

Error Message

138: ResourcePool: Pool already contains block starting with {0} of size {1} with name {2}.

Explanation Resource pool overlaps with the new resource pool being created.

Recommended Action Check the resource pool and create a new one. {2} Starting value of the block; {3} Size of the block; {4} Name given to the pool.

Error Message

139: ResourcePool: Block starting with {0} of size {1} has already been allocated.

Explanation Resource pool overlaps with the existing allocated pool.

Recommended Action Check the resource pool and create a new one that does not overlap with the allocated pool. {0} Starting value of the block; {1} Size of the block.

Error Message

140: ResourcePool: Could not recover from aged pool; IP addresses have not aged yet.

Explanation Could not recover addresses from the aged pool.

Recommended Action Adjust the aged timer if you want the IP addresses to be recovered in DCPL.

Error Message

141: PoolWithSeed: {0} is a malformed string. Should be in the form of sss:nnn.

Explanation The value being allocated is malformed.

Recommended Action Make sure the value to be manually allocated follows the valid format.

Error Message

142: PoolWithSeed: {0} has null value part.

Explanation Pool with seed to be allocated is not valid.

Recommended Action Either the seed value or the allocated value is null. Make sure that the value to be manually allocated follows the valid format.

Error Message

143: PoolWithSeed: Release cannot be called for pools with seed (Route Target and Route Distinguisher).

Explanation Pool with seed value cannot be released once allocated.

Recommended Action Route Target, Route Distinguisher, and SOO values cannot be released once allocated.

Error Message

144: VLAN: Add cannot be called for VLAN pool. The values are added automatically when an instance is created.

Explanation The Resource Pool API cannot be invoked with this function.

Recommended Action Avoid using the Resource Pool API that results in the exception.

Error Message

145: ResourcePool: Associated object of class {0} does not exist in the database.

Explanation The associated class to which the pool belongs does not exist in the database.

Recommended Action Check the reason for deletion of the associated object. This exception should not occur.

Error Message

146: IPAddressPool: IP address {0} has no mask specified.

Explanation The IP address being allocated does not have any mask specified.

Recommended Action Specify an IP address with a valid mask (8-29).

Error Message

147: IPAddressPool: Expected mask to be <= 32, but got {0}.

Explanation The IP address being allocated has an incorrect mask specified.

Recommended Action Specify an IP address with a valid mask (8-29).

Error Message

148: VLAN: VLAN range {0}, {1} out of range (must be between 1 and 4094 inclusive).

Explanation The VLAN pools being allocated are out of range. The valid ranges are between 1 and 4094.

Recommended Action Specify the valid VLAN range (1-4094).

Error Message

149: VLAN: VLAN range {0}, {1} overlaps existing values.

Explanation The VLAN pool being created overlaps with the existing pools.

Recommended Action Do not create the VLAN pool with a range overlapping with existing VLAN pools.

Error Message

150: VLAN: VLAN range {0}, {1} has some values already allocated.

Explanation The VLAN pool with the starting value {0} and the ending value {1} has some values already allocated.

Recommended Action Do not allocate values that have already been allocated.

Error Message

151: ResourcePool: {0}, {1} overlaps allocated data.

Explanation The resource pool being created overlaps the allocated data.

Recommended Action Do not allocate values that have already been allocated.

Error Message

152: ResourcePool: {0}, {1} not available for allocation.

Explanation The resource pool values are not available for allocation because they have already been allocated.

Recommended Action Do not allocate values that have already been allocated.

Error Message

153: ResourcePool: Cannot delete allocated pools.

Explanation The allocated pools cannot be deleted.

Recommended Action Do not try to delete allocated pools.

Error Message

154: VCID: Add cannot be called for VCID. The values are added automatically when an instance is created.

Explanation This is an internal exception that prevents you from calling an incorrect function for adding a VCID Pool.

Recommended Action Do not call the specific function for the VCID pool. This exception is not visible in the GUI.

Error Message

155: VCID: VCID range {0}, {1} overlaps existing values.

Explanation The VCID pool being created overlaps with the pools already existing.

Recommended Action Do not create the VCID pool with a range overlapping with existing VCID pools.

Error Message

156: VCID: VCID range {0}, {1} has some values already allocated.

Explanation The VCID pool with the starting value {0} and the ending value {1} already has some values allocated.

Recommended Action Do not allocate values that have already been allocated.

Error Message

157: Unable to delete the associated resource pools of the Persistent Object of type {0} with ID = {1}.

Explanation The resource pool associated with a particular Persistent Object cannot be deleted.

Recommended Action Check whether there are allocated resources associated with a Persistent Object with the class name specified with {0} and identifier specified by {1}.

Error Message

158: Unable to allocate IP address from the {0} IP address pool.

Explanation Unable to allocate a particular IP address from the pool.

Recommended Action Check whether an IP address being allocated {0} is already allocated.

Error Message

159: IP address {0} overlaps with the available /30 IP address pool for Provider {1} and Region {2}.

Explanation IP address being allocated from /30 pool for a particular region overlaps with the available pool for a different region belonging to the provider.

Recommended Action Do not allocate IP address {0} which belongs to Provider {1} and Region {2}.

Error Message

160: IP address {0} overlaps with the available /32 IP address pool for Provider {1} and Region {2}.

Explanation IP address being allocated from /32 pool for a particular region overlaps with the available pool for a different region belonging to the provider.

Recommended Action Do not allocate IP address {0} which belongs to Provider {1} and Region {2}.

Error Message

161: IP address {0} overlaps with the allocated /30 IP address pool for Provider {1} and Region {2}.

Explanation IP address being allocated from /30 pool for a particular region overlaps with the available pool for a different region belonging to the provider.

Recommended Action Do not allocate IP address {0} which belongs to Provider {1} and Region {2}.

Error Message

162: IP address {0} overlaps with the allocated /32 IP address pool for Provider {1} and Region {2}.

Explanation IP address being allocated from /32 pool for a particular region overlaps with the available pool for a different region belonging to the provider.

Recommended Action Do not allocate IP address {0} that belongs to Provider {1} and Region {2}.

Error Message

163: Trying to add out of bound IP address {0} for poolname {1}.

Explanation Trying to add an out of bound IP address for a particular pool.

Recommended Action Do not add an out of bound /30 or /32 pool.

Error Message

164: Invalid mask {0}. ISC supports mask between 8 and 29.

Explanation Invalid mask. Not in the range 8-29 supported by ISC.

Recommended Action Enter a valid mask in the range 8-29.

Error Message

165: Invalid range for VCID pools.

Explanation Invalid range for the VCID pools being created.

Recommended Action The VCID pool range should be 1-2147483646.

Error Message

166: Out of bound pool size for pool with seed for class {0}.

Explanation Invalid size of the new PoolWithSeed pool being created.

Recommended Action Check that the new PoolWithSeed resource pool being created associated with class {0} has a valid size.

Error Message

167: Incorrect size for poolname {0}.

Explanation Invalid size of the new resource pool being created.

Recommended Action Check that the new resource pool being created associated with name {0} has a valid size.

Error Message

168: Persistent Object with which the resource pool is to be associated does not exist in the database.

Explanation Internal resource pool error specifying the Persistent Object associated with data blocks is not in the database.

Recommended Action Check why the Persistent Object associated with the data blocks has been deleted.

Error Message

170: ResourcePool: {0}, {1} overlaps aged data.

Explanation The pool to be created with starting value {0} and size {1} overlaps aged data.

Recommended Action Make sure that the new pool does not overlap the aged data.

Error Message

171: VLAN Id is not allowed : {0}

Explanation The VLAN identifier provided is not valid for the operation.

Recommended Action Make sure the VLAN is valid and is not already in use.

Messages 300-399 (Repository Messages)

Error Message

300: Could not set isolation level back to {0}.

Explanation Internal error.

Error Message

301: Cannot delete MASTER VPNSC Host.

Explanation Internal error.

Error Message

302: Invalid interface encapsulation type.

Explanation Internal error.

Error Message

303: Unable to execute query using QueryManager. {0}

Explanation Internal error.

Error Message

304: Unable to delete persistent object, {0} - {1}

Explanation Internal error.

Error Message

305: Unable to instantiate object - {0} - {1}

Explanation Internal error.

Error Message

306: Object does not exist. - {0} - {1}

Explanation Internal error.

Error Message

307: This device is associated with a Service Request and cannot be deleted.

Explanation The device is being deleted, but there are active Service Requests.

Recommended Action Make sure the device being deleted does not have any Service Requests associated with it.

Messages 400-499 (Repository Messages)

Error Message

400: {0}::{1}: TIBCO ==> Could not register {2} with TIBCO.

Explanation Internal error.

Messages 500-599 (Repository Messages)

Error Message

524: {0}::{1}: AddressPool ==> AddressPool does not have a {2} association.

Explanation Address Pool is not associated with any Persistent Object.

Error Message

525: {0}::{1}: AddressPool ==> Expected one {2} for ID "{3}". Got "{4}".

Explanation The error message has the details.

Error Message

526: {0}::{1}: AddressPool ==> Returned object ({2}) is not of type {3}.

Explanation The error message has the details.

Error Message

527: {0}::{1}: AddressPool ==> Parent {2} has not been defined.

Explanation Internal error.

Recommended Action Associate the Address Pool with the parent.

Error Message

528: {0}::{1}: RepXXXMapping ==> Mapping object "{2}" is null. This object cannot be persisted in the database.

Explanation This object cannot be persisted in the database.

Error Message

529: {0}::{1}: RepGroup ==> List elements must each be of type {2}.

Explanation The error message has the details

Error Message

530: {0}::{1}: RepGroup ==> The device-specific group attributes object has not been associated with this group. Use the method createDeviceSpecificAttributes to create or getDeviceSpecificAttributes to retrieve and activate the device-specific group object.

Explanation The error message has all the details.

Error Message

531: {0}::{1}: RepGroup ==> Remote Access Group "{2}" is not defined

Explanation The object given in the error message is not defined for the Remote Access Group.

Error Message

532: {0}::{1}: Remote Access ==> Expected one {2} for ID {3}. Got {4}.

Explanation Expected one object of type {2} and many were returned.

Error Message

533: {0}::{1}: Remote Access ==> Unexpected object type ({2}). Expected {3}.

Explanation Query returns unexpected object type.

Error Message

534: {0}::{1}: Remote Access ==> Expected one device-specific group object. Got {2}.

Explanation Expected one device-specific group object.

Error Message

535: {0}::{1}: User ==> Returned object ({2}) is not of type Group

Explanation Object returned is not of type Group.

Error Message

536: {0}::{1}: User ==> Parent Group has not been defined.

Explanation Parent Group has not been defined.

Messages 600-699 (Repository Messages)

Error Message

600: Invalid String: String {0} has invalid size {1}. The valid range is [{2}, {3}].

Explanation The given string is invalid.

Recommended Action Enter a string that has a length within the specified range.

Error Message

601: Invalid String: String {0} has incorrect format.

Explanation String has incorrect format.

Recommended Action Specify the string given in the error message in the correct format.

Error Message

602: Invalid Integer:Value {0} is not within valid range {1}, {2} for {3}.

Explanation Invalid integer. The value is not within the specified valid range.

Recommended Action Give the integer specified in the error message a correct value.

Error Message

603: Invalid Enumeration: Value {0} is not valid for enum of type {1} for {2}.

Explanation Invalid enumeration. The value is not valid for the given enum type.

Recommended Action Give the correct enum type.

Error Message

604: Invalid IP address: {0} is in incorrect format.

Explanation The specified IP address is not in the correct format.

Recommended Action Enter a valid IP address.

Error Message

605: Invalid IP address: {0} has an invalid mask

Explanation The specified IP address does not have a valid mask.

Recommended Action Enter a valid IP address with a valid mask value.

Error Message

606: Invalid IP address: {0} is not a correct host address

Explanation The specified IP address is not a correct host address.

Recommended Action Enter the valid IP address of the host.

Error Message

607: Invalid Object: The object {0} with ID {1} is of invalid type {2}

Explanation The specified object is not of the correct or required type.

Error Message

608: Invalid Object: The object {0} with ID {1} is invalid because its attribute {2} has invalid value {3}.

Explanation An object is invalid because one of its attributes does not have a valid value.

Error Message

609: The Object {0} with ID {1} does not exist in the database.

Explanation The persistent object with the ID given in the error message is not persisted in the database.

Error Message

610: The Object {0} with ID {1} cannot be deleted because Object {2} with ID {3} is associated with it.

Explanation The object {0: Class Name of object} with ID {1} cannot be deleted because object {2} with ID {3: ID or IDS} is associated with it.

Recommended Action Find the objects of the given type and with the given IDs or ID and either delete or disassociate these from the concerned object. Only then can the specific object be deleted.

Error Message

611: The Object {0} with ID {1} cannot be modified because Object {2} : {3} is associated with it.

Explanation The object {0: Class Name of object} with ID {1} cannot be modified because objects {2: object type} : {3 :parameter} are associated with it.

Recommended Action Find the objects of the given type and with the given parameter and either delete or disassociate these from the concerned object. Only then can the concerned object be modified.

Error Message

612: The Object {0} with ID {1} cannot be modifed

Explanation The specified object cannot be modified due to other dependent objects.

Recommended Action Find the objects of the given type and with the given IDs or ID and either delete or disassociate these from the concerned object. Only then can the concerned object be modified.

Error Message

613: The Object {0} with ID {1} cannot be modified because it is already modifed.

Explanation Another instance of the connection modified the object.

Error Message

614: The Object {0} cannot be persisted because its parent Object {1} is not in the database.

Explanation The parent object is not committed. Thus, the specified object cannot be committed.

Recommended Action Set the parent object before committing the specified object.

Error Message

615: The Object {0} with ID {1} cannot be persisted because its parent Object {2} with ID {3} is not in the database.

Explanation The parent object is not committed. Thus, the specified object cannot be committed.

Recommended Action Set the parent object before committing the specified object.

Error Message

616: The Object {0} with ID {1} cannot be associated with Object {2} with ID {3} because attribute {4} has value {5}.

Explanation An invalid association of objects occurred because their parent attribute has an invalid value.

Recommended Action Set the parent object with valid attribute values.

Error Message

617: The Object {0} with ID {1} is a duplicate because attribute {2} has value {3}.

Explanation A duplicate object is being committed, and thus an exception appears.

Recommended Action Make sure you do not commit duplicate objects, that is, objects having the same attribute values.

Error Message

618: null {0} Object has been obtained.

Explanation A query returned a null object.

Error Message

619: Invalid API Usage: The method {0} on Object {1} is not valid for attribute {2} with value {3}.

Explanation This API cannot be called with an invalid value set for an attribute.

Recommended Action Call this API with a valid attribute value.

Error Message

620: The {0} Service Request with Job ID {1} and ID {2} cannot be subsumed because it is not on top of the stack.

Explanation A Service Request on the bottom of the stack cannot be subsumed.

Recommended Action Avoid subsuming a Service Request that is the bottom Service Request of the stack and there are one or more Service Requests on top of it.

Error Message

621: The {0} Service Request with Job ID {1} and ID {2} cannot be subsumed because it is decommissioned.

Explanation A decommissioned Service Request cannot be subsumed.

Recommended Action Avoid subsuming a decommissioned Service Request.

Error Message

622: The {0} Service Request with Job ID {1} and ID {2} cannot be purged because it is not in Closed state.

Explanation The Service Request, MPLS, L2VPN, and so on type of Service Request, with the given Job ID and ID cannot be purged because it is not in the Closed state.

Recommended Action First decommission the Service Request and then purge it or use Force Purge.

Error Message

623: The {0} Service Request with Job ID {1} and ID {2} cannot be purged because it is not on top of the stack.

Explanation The Service Request, MPLS, L2VPN, and so on type of Service Request, with the given Job ID and ID cannot be purged because it is not on the top of the stack.

Recommended Action Do not try to purge a Service Request that is not on the top of the stack. Purging the topmost Service Request purges the entire stack.

Error Message

624: Cannot add Service Element {0} with ID {1} to Service Request with Job ID {2} and ID {3} because the Service Request is decommissioned.

Explanation Cannot add the Service Element with the ID mentioned in the error message to the Service Request with the given Job ID, because the Service Request is decommissioned.

Recommended Action Avoid adding any service elements to a Service Request that is already decommissioned.

Error Message

625: Data integrity error. Found {0} entries of object {1} while only {2} was expected.

Explanation Data integrity error.

Error Message

626: Interface {0} is not a loopback interface.

Explanation The interface is not a loopback interface when a loopback interface is expected.

Error Message

627: Object {0} with attribute {1} of value {2} could not be found on parent device with ID {0}.

Explanation Object {class name of object} with attribute {1} of value {2} could not be found on parent device with ID {0}.

Error Message

628: Attribute cache has not been enabled.

Explanation Attribute cache has not been enabled.

Error Message

629: The Object {0} with attribute {1} = {2} does not exist in the database.

Explanation The object {class name of object} with attribute {1} = {2} does not exist in the database.

Error Message

630: The Object {0} cannot be persisted because it is not associated with object {1}.

Explanation The object {class name of object} cannot be persisted because it is not associated with object {1}.

Recommended Action Read the error message details about why it cannot be persisted.

Error Message

631: The Object {0} cannot be removed from the object {1}.

Explanation The object {class name of object} cannot be removed from the object {1}.

Recommended Action Read the error message details about why it cannot be removed.

Error Message

632: The {0} Service Request with Job ID {1} and ID {2} cannot be subsumed because it is already subsumed.

Explanation The Service Request, MPLS, L2VPN, and so on type of Service Request, with Job ID {1} and ID {2} cannot be subsumed because it is already subsumed.

Recommended Action Subsume the Service Request that is on the top of the stack.

Error Message

633: The {0} Service Request with Job ID {1} and ID {2} cannot be closed because one of the SRs in the subsumption stack is not in the Requested state. You need to decommission the SR, before you close it, then the config audit succeeds.

Explanation The Service Request concerned, MPLS, L2VPN, and so on, cannot be closed because one of the Service Requests in the subsumption stack is not in Requested state.

Recommended Action You must decommission the Service Request and then config audit should succeed before you can close it.

Error Message

634: The state transition from {0} to {1} is not allowed for the Service Request with Job ID {2} and ID {3}.

Explanation The state transition from {initial State} to {intended state} is not allowed for Service Request with Job ID {2} and ID {3}.

Error Message

635: The Service Request with Job ID {0} and ID{1} cannot be deleted because it is not on top of the subsumption stack or it is not in Closed state.

Explanation This Service Request cannot be deleted because it is not on the top of the subsumption stack or it is not in the Closed state.

Recommended Action Do not try to purge a Service Request that is not on top of the stack or is not in the Closed state. Purging the topmost Service Request purges the whole stack. First decommission the Service Request and then purge it or use Force Purge.

Error Message

636: VPN cannot be created because there are no sufficient licenses.

Explanation VPN cannot be created because there are insufficient licenses.

Recommended Action Install proper or sufficient licenses.

Error Message

637: Cannot compare states {0} and {1}.

Explanation The states cannot be compared.

Error Message

638: XML parsing error.

Explanation Unable to parse XML document.

Recommended Action Contact ISC support with the context in which the exception is thrown.

Error Message

639: Invalid Integer : Value {0} for attribute {1} is not a valid integer.

Explanation The value provided for an attribute is not valid.

Recommended Action Provide valid integer value for the attribute.

Error Message

640: {0}:{1}: Migration: Target with ID {2} does not exist.

Explanation The target with a given ID (specified in the variable {2}) does not exist in the database.

Recommended Action The target ID referenced in this object did not get exported from the VPNSC 1.x/2.x repository for migration. Please verify the VPNSC 1.x/2.x repository and retry the export.

Error Message

641: {0}:{1}: Migration: String {2} is a malformed number.

Explanation The value exported from VPNSC 1.x/2.x is not in a valid number format.

Recommended Action Verify and fix the source data and retry the export.

Error Message

642: Invalid Multicast IP address {0}.

Explanation The address specified as the Multicast address is invalid.

Recommended Action Provide a valid multicast address.

Error Message

643: Unable to Force Purge the Service Request with Job ID {0} and ID {1}. You are not authorized for this action. Contact your ISC System Administrator.

Explanation Force Purge is not allowed for a Service Request because an operator does not have permission.

Recommended Action Only an administrator can delete a Service Request that is not in Closed state or provide operators with permission to Force Purge a Service Request by setting the DCPL option Services.Common.allowForcePurge to true.

Error Message

644: IP address: {0} :{1} has a mask, specify the address without a mask.

Explanation The IP address is specified with a mask but it should be specified without a mask.

Recommended Action Provide an IP address without a mask.

Error Message

645: PE Interface address : {0} and its Neighbor address {1} should not be same.

Explanation The PE interface address and the BGP neighbor address should not be the same.

Recommended Action Make sure the PE interface address and BGP neighbor address are not the same.

Messages 700-799 (Repository Messages)

Error Message

700: {0}::{1}: Customer ==> Customer with ID {2} is associated with the following SRs: {3}. It cannot be deleted.

Explanation Customer cannot be deleted because it has been associated with a Service Request.

Recommended Action Do not delete this customer or purge those Service Requests associated with it.

Error Message

710: {0}::{1}: Site ==> Site is not associated with a customer.

Explanation Site did not have any customer associated with it.

Recommended Action Reassign a customer to that site.

Error Message

711: {0}::{1}: Site ==> Expected one customer for customer ID {2}. Got {3}.

Explanation One site can only be associated with one customer. The current site is associated with more than one customer.

Recommended Action Make sure this site is associated with only one customer.

Error Message

712: {0}::{1}: Site ==> Site with ID {2} has CPEs associated with the following SRs: {3}. It cannot be deleted.

Explanation Site cannot be deleted because it is associated with Service Requests.

Recommended Action Do not delete this site or purge the associated Service Requests.

Error Message

713: {0}::{1}: VPN ==> VPN is not associated with a customer

Explanation VPN did not have any customer associated with it.

Recommended Action Reassign a customer to that VPN.

Error Message

714: {0}::{1}: VPN ==> Expected one customer for customer ID {2}. Got {3}.

Explanation One VPN can only be associated with one customer. The current VPN is associated with more than one customer.

Recommended Action Make sure that this VPN is associated with only one customer.

Error Message

715: {0}::{1}: VPN ==> VPN with ID {2} is associated with the following SRs: {3}. It cannot be deleted

Explanation VPN cannot be deleted because it has been associated with a Service Request.

Recommended Action Do not delete this VPN or purge those Service Requests associated with it.

Error Message

716: {0}::{1}: CustomerNetworkPrefix ==> CustomerNetworkPrefix is not associated with a CPE.

Explanation Internal error.

Error Message

717: {0}::{1}: CustomerNetworkPrefix ==> Expected one CPE for CPE ID {2}. Got {3}.

Explanation Internal error.

Error Message

718: {0}::{1}: CustomerNetworkPrefix ==> CustomerNetworkPrefix with ID {2} has CPE associated with the following SRs: {3}. It cannot be deleted

Explanation Internal error.

Error Message

725: {0}::{1}: RepManager ==> {2} "{3}" is not a Persistent Object.

Explanation Internal error.

Error Message

726: {0}::{1}: RepManager ==> Element "{2}" ({3}) is not of type DbAccess.

Explanation Internal error.

Error Message

727: {0}::{1}: RepManager ==> Could not find a public constructor for instantiation: "public {2}({3})".

Explanation Internal error.

Error Message

728: {0}::{1}: RepManager ==> A runtime exception occurred during the creation of an object of type {2}. Either the object's constructor failed or the Persistent Object constructor failed. This is likely due to the database being out of sync with the Repository object (the table attributes do not match the Repository object attributes).

Explanation Internal error.

Error Message

731: {0}::{1}: RepQueryManager ==> called getNextObjectsList before calling getObjectsList for query "{2}".

Explanation Internal error.

Error Message

732: {0}::{1}: RepQueryManager ==> The first filter expression should not define a connector ({2}).

Explanation Internal error.

Error Message

733: {0}::{1}: RepQueryManager ==> Filter consists of predefined operands only.

Explanation Internal error.

Error Message

734: {0}::{1}: RepQueryManager ==> No matching query found for query "{2}".

Explanation Internal error.

Error Message

735: {0}::{1}: RepQueryManager ==> Query "{2}" is missing select attributes.

Explanation Internal error.

Error Message

736: {0}::{1}: RepQueryManager ==> Alias "{2}" is not defined in the query "{3}".

Explanation Internal error.

Error Message

737: {0}::{1}: RepQueryManager ==> Operands array length ({2}) is less than the number of filter expressions requiring an operand.

Explanation Internal error.

Error Message

741: {0}::{1}: QueryBuilder ==> Alias "{2}" is not defined in the Query "{3}".

Explanation Internal error.

Error Message

742: {0}::{1}: QueryBuilder ==> Invalid operator "{2}".

Explanation Internal error.

Error Message

743: {0}::{1}: QueryBuilder ==> Invalid operator "{2}" in Sort "{3}".

Explanation Internal error.

Error Message

744: {0}::{1}: QueryBuilder ==> Invalid connector "{2}".

Explanation Internal error.

Error Message

745: {0}::{1}: RepVPN ==> Invalid Data Mdt Size "{2}".

Explanation Wrong data Mdt size was entered. The valid range should be 0 to 256.

Recommended Action Set the data Mdt size within the valid range.

Error Message

746: Logical Device {0} with ID {1} did not have corresponding directory device object.

Explanation Logical device did not have the corresponding directory device.

Recommended Action Reassociate this logical device to one directory device object.

Error Message

747: Multicast is enabled on Grey Mgmt VPN with name {0}, which is not allowed.

Explanation Multicast VPN is enabled on grey management VPN, which is not allowed.

Recommended Action Disable the multicast feature on a grey management VPN.

Error Message

748: Access Domain association of PE Device : {0} cannot be changed becasue it is already associated with AccessDomain : {1} and also has Service Requests.

Explanation The access domain of a PE device {0} cannot be changed to access domain{1}, because it has outstanding Service Requests associated with it.

Recommended Action Make sure that all the outstanding Service Requests are decommissioned before associating a PE with a different access domain.

Error Message

749: Invalid {0} IP address {1} with name {2} on PE. It did not exist in router.

Explanation The IP address {0} with loopback name {1} does not exist on the PE.

Recommended Action Make sure the loopback address provided for the PE is valid.

Error Message

750: Provider Name "{0}" is invalid. It cannot contain tab or spaces.

Explanation The Provider name {0} is invalid and cannot contain tabs or spaces.

Recommended Action Make sure the Provider name does not contain any tabs or spaces.

Error Message

751: Cannot set PimStaticRP List "{0}".

Explanation Cannot set PimStaticRP List. PIM Static RP should be enabled before setting the list.

Recommended Action Set the PimStaticRPEnabled attribute to true before setting the list.

Error Message

752: Invalid PimStaticRP Entry "{0}".

Explanation Invalid PimStaticRP Entry.

Recommended Action Provide a valid multicast IP address for the RP UnicastAddress in the PimStaticRP.

Error Message

753: SsmListname cannot be set because SSM mode is not equal to "RANGE".

Explanation SSM listname cannot be set because the SSM mode is not equal to "RANGE".

Recommended Action Set the SSM mode to RANGE before setting the SSM listname.

Error Message

754: DataMdtSubnet value cannot be set when DataMdtSize is 0.

Explanation DataMdtSubnet value cannot be set when DataMdtSize is 0.

Recommended Action Set DataMdtSize before setting DataMdtSubnetValue.

Error Message

755: Manually enterted DefaultMdtAddrress / DataMdtSubnet cannot be modified. Disable multicast, then re-enable it and enter new address.

Explanation The manually entered DefaultMdtAddress or DataMdtSubnet cannot be modified. Disable multicast, then re-enable it and enter a new address.

Recommended Action Disable multicast, then re-enable it and enter a new address.

Error Message

756: Cannot create duplicate site. A site with name {0} has already been associated with customer with name {1}.

Explanation Cannot create duplicate sites. A site with name {0} has already been associated with a customer with the name {1}.

Recommended Action Choose a different name for the site.

Error Message

757: Cannot create duplicate region. A region with name {0} has already been associated with provider with name {1}.

Explanation Cannot create duplicate regions. A region with the name {0} has already been associated with a provider with the name {1}.

Recommended Action Choose a different name for the region.

Messages 800-899 (Repository Messages)

Error Message

800: {0}::{1}: RBAC ==> SPE exception.

Explanation RBAC framework errors. Possible problems could be database server connection problem, JAVA class path not set correctly, database missing entries, or wrong database.

Recommended Action Make sure vpnenv.sh or vpnenv.csh has been sourced; make sure the installation has been done properly; make sure db server is up, running, and listening at the port expected by ISC, by checking the property repository.persistence.url in vpnsc.properties and the property DataAccess.url.1 in the etc/spe/cns.properties. The two properties' values should be the same.

Error Message

801: {0}::{1}: RBAC ==> Object not found. {2} {3} "{4}".

Explanation Object does not exist in the database.

Recommended Action Check whether the name is spelled correctly or create the object.

Error Message

802: {0}::{1}: RBAC ==> Object cannot be deleted. "{2}" {3}.

Explanation The object cannot be deleted. The specific reason is usually given in the error message itself. This could be a system object.

Recommended Action Do not delete a system object.

Error Message

803: {0}::{1}: RBAC ==> Object cannot be modified. "{2}" {3}.

Explanation The object cannot be modified. The specific reason is usually given in the error message itself; this could be a system object. Modification on a system object is not allowed.

Recommended Action Do not modify a system object.

Error Message

819: Cannot add non-Delete type link into a Delete type SR.

Explanation Internal error.

Error Message

824: Invalid value pair, value for attribute {0} must be {1} value for attribute {2}.

Explanation The combination of the values for the pair of attributes is incorrect.

Recommended Action Enter a valid pair of values suggested in the message.

Messages 900-999 (Repository Messages)

Error Message

900: No service type set for policy {0}.

Explanation Trying to save a VPLS policy with no service type.

Recommended Action Set the service type of the policy before saving.

Error Message

901: VPLS policy {0} associated with Service Request cannot be deleted.

Explanation Cannot delete a policy that has an associated Service Request.

Recommended Action Decommission and purge the associated Service Requests if the VPLS policy {0} is to be deleted.

Error Message

902: VPLS policy {0} associated with Service Request cannot be modified.

Explanation Cannot modify a policy that has an associated Service Request.

Recommended Action Decommission and purge the associated Service Requests if the VPLS policy {0} is to be modified.

Error Message

903: Service Request being subsumed does not exist in the database.

Explanation Service Request being subsumed does not exist in the database. Internal database error. The GUI should not display the Service Requests that do not exist in the database.

Recommended Action Retry.

Error Message

904: Service Request being subsumed does not have policy associated with it.

Explanation Service Request being subsumed does not have a policy associated with it.

Recommended Action Set the policy for the Service Request being subsumed before saving to the repository.

Error Message

905: VPLS links cannot be added to delete Service Request.

Explanation VPLS links cannot be added to a Service Request with operation type Delete.

Recommended Action Do not add VPLS link to delete Service Request.

Error Message

906: Service data missing {0} attribute.

Explanation Mandatory data missing from VPLS links.

Recommended Action Add the Service Data indicated by {0} to the attribute before saving.

Error Message

907: VPLS links only support ethernet encapsulations.

Explanation VPLS links support only Ethernet encapsulations.

Recommended Action Do not try saving links with other encapsulations.

Error Message

908: VPLS link not present in the database.

Explanation Internal repository exception handled by the repository.

Recommended Action Not displayed on the GUI.

Error Message

909: Missing loopback address error {0}.

Explanation VPLS links cannot be deployed if PEs do not have a loopback address.

Recommended Action The string {0} indicates all the PEs not having the loopback address. Give loopback addresses to these PEs before trying to redeploy.

Error Message

910: VPLS Link ID {0} is already stored in the database.

Explanation VPLS links that are going to be added already exist in the repository.

Recommended Action Do not save an already existing repository.

Error Message

911: Invalid VPLS link contains no service attributes.

Explanation Trying to save VPLS links without any attributes.

Recommended Action Add the attributes to the VPLS link before saving it to the repository.

Error Message

912: Invalid range for service attribute {0}.

Explanation Invalid range for a particular attribute of the VPLS link.

Recommended Action Correct the range of the attributes specified by {0}.

Error Message

913: Service Request with OPTYPE delete cannot remove link.

Explanation Service Request with operation type cannot remove link.

Recommended Action Do not try to remove a link from a Service Request with OPTYPE Delete.

Error Message

914: VLAN mismatch for VPLS service for ethernet core.

Explanation VLAN mismatch for VPLS link belonging to the same VPN over Ethernet core.

Recommended Action The VPLS links belonging to the same VPN over Ethernet core should have the same VLAN ID.

Error Message

915: No VLAN specified for VPLS link for manual allocation.

Explanation No VLAN specified for a VPLS link when the manual allocation flag is turned on.

Recommended Action VLAN must be specified when the manual allocation flag is turned on for VPLS link.

Error Message

916: VLAN {0} mismatch for VPLS service. All links belonging to the same VPN {1} under same Access Domain should have same VLAN.

Explanation VLAN mismatch for VPLS link belonging to the same VPN over Ethernet core.

Recommended Action The VPLS links belonging to the same VPN over Ethernet core should have the same VLAN ID.

Error Message

917: VLAN pool {0} needs to be created for VPLS enabled VPNs.

Explanation VLAN pool must be specified for auto allocation for VPLS enabled VPNs.

Recommended Action Create VLAN pools before saving the VPLS links.

Error Message

918: Unable to generate XML. Trouble appending {0} node.

Explanation Unable to generate XML for a particular Service Request.

Recommended Action Unable to generate XML. Some problems appending node specified by {0}.

Error Message

919: Exception when getting number of logical devices for deployable interface.

Explanation Repository exception while getting the number of logical devices over a deployable interface.

Recommended Action Check the repository exception.

Error Message

920: VPLS Service Request with ID {0} cannot be deleted.

Explanation VPLS Service Request cannot be deleted.

Recommended Action VPLS Service Request with ID {0} cannot be deleted. Check the state of the Service Request and decommission it before purging.

Error Message

921: VPN associated with VPLS Service Request is not present in the database.

Explanation VPN associated with a VPLS Service Request is not present in the database.

Recommended Action Check for the VPN associated with the VPLS Service Request in the VPN screen.

Error Message

922: VCID pool {0} needs to be created for VPLS enabled VPNs.

Explanation VCID pool must be specified for auto allocation for VPLS enabled VPNs.

Recommended Action Create VCID pools before saving the VPLS links.

Error Message

923: Unable to subsume; the Service Request is not on top of the stack.

Explanation Unable to subsume the Service Request that is not on the top of the stack.

Recommended Action Subsume the Service Request on the top of the stack.

Error Message

924: VPLS link does not have port security enabled.

Explanation VPLS link does not have Port Security enabled.

Recommended Action Enable the Port Security.

Error Message

925: Unknown value for attribute {0} of VPLS link.

Explanation Unknown value for attribute of the VPLS link.

Recommended Action Have a valid value for attribute {0} of the VPLS link.

Error Message

926: Parent attribute not set for interface {0} of VPLS link or policy.

Explanation Parent attribute not set for VPLS link policy.

Recommended Action Set the parent attribute before setting the child attributes.

Error Message

927: VPLS link does not have protocol tunneling enabled.

Explanation VPLS link does not have protocol tunneling enabled.

Recommended Action Enable the protocol tunneling.

Error Message

928: VPLS link interface type unknown.

Explanation VPLS link interface type unknown.

Recommended Action Have a valid value VPLS link interface type for VPLS link.

Error Message

929: VPLS link interface shutdown option unknown.

Explanation Unknown value for attribute of the VPLS link shutdown.

Recommended Action Have a valid value for the VPLS link shutdown.

Error Message

930: VPLS link encapsulation unknown.

Explanation VPLS link encapsulation type is unknown.

Recommended Action Have a valid value VPLS link interface encapsulation for VPLS link.

Error Message

931: PEs on ethernet core should belong to the same Access Domain.

Explanation PEs on Ethernet core belonging to the same VPN should belong to the same Access Domain.

Recommended Action Make sure all the PEs on the Ethernet core belonging to the same VPN also belong to the same Access Domain.

Error Message

932: Some PEs belonging to VPLS links do not have an associated Access Domain.

Explanation PEs belonging to the VPLS links do not have an associated Access Domain.

Recommended Action Make sure all the PEs for a VPLS link have an associated Access Domain.

Error Message

933: Cannot create VPLS SR because another VPLS SR already exists in the system with the UNI {0} for the VPN {1}.

Explanation ISC does not allow creation of a VPLS Service Request using a UNI and VPN that are already used in an existing active VPLS Service Request.

Recommended Action Change either the UNI selection or the VPN selection for this VPLS Service Request and save.

Messages 1000-1099 (API Messages)

Error Message

1000: Undefined Error error code

Explanation An unknown error was received and this error provides a generic wrapper for the error.

Recommended Action Examine error stack trace in log file: $VPNSC_HOME/tmp/nbi.0(.1) for more information about error.

Error Message

1001: A general error occurred that is not covered by a more specific error code

Explanation The API errors are sometimes from other components of the system and the exact cause of the error is not known to the API.

Recommended Action Examine error stack trace in log file: $VPNSC_HOME/tmp/nbi.0(.1) for more information about error.

Error Message

1002: Access to a ISC resource was not available to the client

Explanation The ISC application is not available.

Recommended Action Make sure the ISC WatchDog started all processes properly.

Error Message

1003: The target namespace does not exist

Explanation The target namespace does not exist.

Recommended Action Check the Request XML file for the proper namespace (ns0, ns1) variables.

Error Message

1004: One or more parameter values passed to the method were invalid

Explanation One or more parameter values passed to the method were invalid.

Recommended Action Check the Request XML file for the proper parameter "name" XML elements.

Error Message

1005: The specified Class does not exist

Explanation The classname is not recognized.

Recommended Action Check the Request XML file for the proper className XML elements.

Error Message

1006: The requested object could not be found

Explanation The classname attribute is not recognized.

Recommended Action Check the Request XML file for the proper className XML elements.

Error Message

1007: The requested operation is not supported

Explanation The method is not recognized. Normally it is the first line after the start of the SOAP body.

Recommended Action Check the Request XML file for the valid method in the "ns1" XML element of the "Body" XML element.

Error Message

1008: Operation cannot be carried out on this class because it has subclasses.

Explanation Operation cannot be carried out on this class because it has subclasses.

Recommended Action Check the database for the current condition of the selected object.

Error Message

1009: Operation cannot be carried out on this class because it has instances.

Explanation Operation cannot be carried out on this class because it has instances.

Recommended Action Check the database for the current condition of the selected object.

Error Message

1010: Operation cannot be carried out because the specified superclass does not exist.

Explanation Operation cannot be carried out because the specified superclass does not exist.

Recommended Action Check the database for the current condition of the selected object.

Error Message

1011: Operation cannot be carried out because an object already exists

Explanation Operation cannot be carried out because an object already exists.

Recommended Action Check if a duplicate object exists and if it does, create a new object with a different name or attributes.

Error Message

1012: The specified property does not exist.

Explanation The attributes in the API are called properties. There might be one that is spelled incorrectly.

Recommended Action Check the Request XML file for the proper format of the 'properties' XML elements.

Error Message

1013: The value supplied is incompatible with the type

Explanation The attributes in the API do type checking.

Recommended Action Check the Request XML file for the proper format of the 'item' XML elements.

Error Message

1014: The query language is not recognized or supported

Explanation The only supported type is SQL.

Recommended Action Check the Request XML file for the proper format of the execQuery XML elements.

Error Message

1015: The query is not valid for the specified query language

Recommended Action Check the Request XML file for the proper format of the execQuery XML elements.

Error Message

1016: The extrinsic method could not be executed.

Explanation The method is not recognized. Normally it is a createInstance, deleteInstance, or similar construct.

Recommended Action Check the Request XML file for the valid method in the ns1 XML element of the Body XML element.

Error Message

1017: The request XML does not have a header

Explanation The header is the SOAP Header.

Recommended Action Check the Request XML file for the proper format and existence of the Header XML element.

Error Message

1018: The request XML does not have a body

Explanation The body is the SOAP body.

Recommended Action Check the Request XML file for the proper format and existence of the Body XML element.

Error Message

1019: Multiple deletes not allowed

Explanation The API only supports deletes on one object at a time.

Recommended Action Check the Request XML file for the proper format of a single 'Delete' XML element.

Error Message

1020: Security has determined this transaction is invalid

Explanation The login did not work.

Recommended Action Check that the proper Session ID has been sent with the XML request.

Error Message

1021: RBAC Security Failure

Explanation The login did not work and might be in the RBAC area.

Recommended Action Make sure the ISC WatchDog started all processes, including RBAC, properly.

Error Message

1022: Error processing transaction for method: createInstance

Explanation Error processing transaction for method: createInstance.

Recommended Action Check the Request XML file for the proper format of the createInstance XML element and the current condition of the database.

Error Message

1023: Error processing transaction for method: deleteInstance

Explanation Error processing transaction for method: deleteInstance.

Recommended Action Check the Request XML file for the proper format of the deleteInstance XML element and the current condition of the database.

Error Message

1024: Error processing transaction for method: modifyInstance

Explanation Error processing transaction for method: modifyInstance.

Recommended Action Check the Request XML file for the proper format of the modifyInstance XML element and the current condition of the database.

Error Message

1025: Error processing transaction for method: enumerateInstances

Explanation Error processing transaction for method: enumerateInstances.

Recommended Action Check the Request XML file for the proper format of the 'enumerateInstance' XML element.

Error Message

1026: Error in NBI simple transaction; request is unsupported. View log for more details.

Explanation The simple transactions are for inventory objects normally. They usually only have one layer of hierarchy. They are processed in a separate module from the more complex composite objects.

Recommended Action Examine error stack trace in log file: $VPNSC_HOME/tmp/nbi.0(.1) for more information about error.

Error Message

1027: Error instantiating Template

Explanation Error in ISC template software.

Recommended Action Check the Request XML file for the proper format of the 'Template' XML element.

Error Message

1028: Error creating template - NBI.

Explanation Error in ISC template software.

Recommended Action Check the Request XML file for the proper format of the Template XML element.

Error Message

1029: Error creating template data - NBI.

Explanation Error in ISC template software.

Recommended Action Check the Request XML file for the proper format of the Template XML element.

Error Message

1030: Error creating template configlet.

Explanation Error in ISC template software.

Recommended Action Check the Request XML file for the proper format of the Template XML element.

Error Message

1031: Error finding template - NBI.

Explanation Error in ISC template software.

Recommended Action Check the Request XML file for the proper format of the Template XML element.

Error Message

1032: Error viewing template - NBI.

Explanation Error in ISC Template software.

Recommended Action Check the Request XML file for the proper format of the Template XML element.

Error Message

1033: Error deleting template - NBI.

Explanation Error in ISC Template software.

Recommended Action Check the Request XML file for the proper format of the Template XML element.

Error Message

1034: Error deleting template data.

Explanation Error in ISC template software.

Recommended Action Check the Request XML file for the proper format of the Template XML element.

Error Message

1035: Error modifying template - NBI.

Explanation Error in ISC template software.

Recommended Action Check the Request XML file for the proper format of the Template XML element.

Error Message

1036: Error occurred while processing (create) transaction.

Explanation Error occurred while processing (create) transaction.

Recommended Action Check the Request XML file for the proper format of the createInstance XML element and the current condition of the database.

Error Message

1037: Error occurred while processing (enumerate) transaction.

Explanation Error occurred while processing (enumerate) transaction.

Recommended Action Check the Request XML file for the proper format of the enumerateInstance XML element.

Error Message

1038: Error occurred while processing (modify) transaction.

Explanation Error occurred while processing (modify) transaction.

Recommended Action Check the Request XML file for the proper format of the modifyInstance XML element and the current condition of the database.

Error Message

1039: The following repository object could not be found: {0}, {1}

Explanation The database object could not be found.

Recommended Action Check the Request XML file for the proper contents of the XML elements and the current condition of the database.

Error Message

1040: NbiCompositeMgr:processCreateRequest:: Request node name {0} and rule node name {1} are different.

Explanation Internal error.

Error Message

1041: Argument {0} is required in the Constructor of {1}

Explanation Internal error.

Error Message

1042: NbiCompositeMgr:processCreateRequest:: Attribute occurs not defined in composite meta for node {0}

Explanation Internal error.

Error Message

1043: NbiCompositeMgr:processCreateRequest:: Attribute occurs of node {0} required as a constructor argument for {1} should have value 1 in the composite meta.

Explanation The occurs attribute defined in the composite meta XML for node {0} should have a value of 1.

Error Message

1044: Node {0} not defined under {1}

Explanation Internal error.

Error Message

1045: NbiCompositeMgr:processCreateRequest:: ID required for the attribute {0} parent of {1}

Explanation Internal error.

Error Message

1046: NbiCompositeMgr:processCreateRequest:: Parent of {0} is null for Id {1}

Explanation Internal error.

Error Message

1047: NbiCompositeMgr:processCreateRequest:: decisionAttr attribute should be defined for the node {0} in the composite meta

Explanation Internal error.

Error Message

1048: NbiCompositeMgr:processCreateRequest:: decisionObj attribute should be defined for the node {0} in the composite meta

Explanation Internal error.

Error Message

1049: NbiCompositeMgr:processCreateRequest:: Could not find {0} PersistentObject in created object list to invoke {1} method

Explanation Internal error.

Error Message

1050: NbiCompositeMgr:processCreateRequest:: Found more than one {0} PersistentObject in created object list. Not known on which {1} method should be invoked

Explanation Internal error.

Error Message

1051: NbiCompositeMgr:processCreateRequest:: Method {0} on {1} PersistentObject returned null. Cannot make decision on conditional element.

Explanation Internal error.

Error Message

1052: NbiCompositeMgr:processCreateRequest:: Could not find mapping for condition {0} in element {1} in the composite meta

Explanation Internal error.

Error Message

1053: NbiCompositeMgr:processCreateRequest:: Could not find node {0} in the composite meta under the node {1}

Explanation Internal error.

Error Message

1054: NbiCompositeMgr:processCreateRequest:: Could not get qualifierCtorArgName {0} for {1}

Explanation Internal error.

Error Message

1055: NbiCompositeMgr:processViewRequest:: Request node name {0} and rule node name {1} are different.

Explanation Internal error.

Error Message

1056: For view, refLookup should always be true.

Explanation Internal error.

Error Message

1057: searchAttrName attribute should be defined in composite for this persistent object

Explanation Internal error.

Error Message

1058: NbiCompositeMgr:processModifyRequest:: Request node name {0} and rule node name {1} are different.

Explanation Internal error.

Error Message

1059: Object {0} with ID {1} does not have association with its given parent.

Explanation Internal error.

Error Message

1060: Did not find persistent object {0} for id{1}

Explanation Internal error.

Error Message

1061: NbiCompositeMgr: PersistentObject getFromRepository ClassNotFoundException

Explanation Internal error.

Error Message

1062: NbiCompositeMgr: Collection getFromRepository ClassNotFoundException

Explanation Internal error.

Error Message

1063: Requires one or more of {0}

Explanation Internal error.

Error Message

1064: Requires {0} of {1} nodes and found {2}.

Explanation Internal error.

Error Message

1065: Requires at least one {0} node and found {1}.

Explanation Internal error.

Error Message

1066: Requires one or zero {0} node and found {1}.

Explanation Internal error.

Error Message

1067: More than one noOp node {0} found

Explanation Internal error.

Error Message

1068: The request has node {0} which is not present in Composite

Explanation Internal error.

Error Message

1069: Requires one or more nodes under {0}.

Explanation Internal error.

Error Message

1070: Requires {0} nodes under {1} and found {2}

Explanation Internal error.

Error Message

1071: Requires at least one node under {0} and found {1}

Explanation Internal error.

Error Message

1072: Requires one or zero nodes under {0} and found {1}

Explanation Internal error.

Error Message

1073: NbiCompositeMgr:getCtorArgs:: Found multiple {0} objects for constructor of {1}. Cannot determine which should be used.

Explanation Internal error.

Error Message

1074: NbiCompositeMgr:getCtorArgs:: Found only {0} constructor arguments for {1} out of {2}. Cannot proceed.

Explanation Internal error.

Error Message

1075: NbiCompositeMgr:getCtorArgs:: Found multiple {0} objects for constructor of qualifier. Cannot determine which should be used.

Explanation Internal error.

Error Message

1076: NbiCompositeMgr:processCreateRequest:: Multiple IDs found for the attribute {0}, parent of {1}

Explanation Internal error.

Error Message

1077: Expected one child under service definition or request: {0}

Explanation Internal error.

Error Message

1078: Query for modify must return one object. The query returned: {0} objects.

Explanation For modify or delete, only one object can be operated on at a time.

Error Message

1079: Improperly formatted request has caused internal errors. Resulted in error with class {0} using method {1} with value {2}.

Explanation Improperly formatted request has caused internal errors. Resulted in error with class {0} using method {1} with value {2}.

Error Message

1080: Simple object: {0} could not be instantiated

Explanation Simple object: {0} could not be instantiated.

Error Message

1081: The following repository object could not be found: {0}, {1}

Explanation A database object could not be found.

Error Message

1082: No method found for the class {0} and attribute {1}

Explanation No method found for the class {0} and attribute {1}.

Error Message

1083: Got a null for the desired due date

Explanation Problem with the due date. It must be in the specified format.

Error Message

1084: Unable to parse the DueDate {0}; format is invalid.

Explanation Problem with the due date. It must be in the specified format.

Error Message

1085: Failed to remove qualifier item

Explanation Internal error.

Error Message

1086: NbiCompositeMgr:processViewRequest:: decisionAttr attribute should be defined for the node {0} in the composite meta

Explanation Internal error.

Error Message

1087: NbiCompositeMgr:processViewRequest:: decisionObj attribute should be defined for the node {0} in the composite meta

Explanation Internal error.

Error Message

1088: NbiCompositeMgr:processViewRequest:: Could not find {0} PersistentObject in created object list to invoke {1} method

Explanation Internal error.

Error Message

1089: NbiCompositeMgr:processViewRequest:: Found more than one {0} PersistentObject in created object list. Cannot determine on which {1} method should be invoked.

Explanation Internal error.

Error Message

1090: NbiCompositeMgr:processModifyRequest:: Operation {0} cannot be handled by modify request for the first node {1}

Explanation Internal error.

Error Message

1091: NbiCompositeMgr:processModifyRequest:: Operation {0} not allowed on node {1}. Please see the composite for this request.

Explanation Internal error.

Error Message

1092: NbiCompositeMgr:processModifyRequest:: Found {0} {1} objects in the repository instead of 1. Modify cannot proceed.

Explanation Internal error.

Error Message

1093: NbiCompositeMgr:processModifyRequest:: FilterList cannot be empty for node {0}

Explanation Internal error.

Error Message

1094: NbiCompositeMgr:processModifyRequest:: Invalid opType {0} for node {1}

Explanation Internal error.

Error Message

1095: Parser failed, likely due to input XML formatting error near line {0} for element {1}.

Explanation This is like a compile type error. It attempts to highlight the line in error of the input XML.

Error Message

1096: Invalid Login.

Explanation The login is bad.

Recommended Action Check the Request XML file for the proper format and valid user and password values.

Error Message

1097: Invalid Session.

Explanation The session could have expired.

Recommended Action Check that the proper Session ID has been sent with the XML request.

Error Message

1098: Unable to construct the formatter or writer for NbiResponseMgr.

Explanation Internal error.

Error Message

1099: Error in constructing NbiWriter for NbiResponseMgr

Explanation Internal error.

Messages 1100-1199 (API Messages)

Error Message

1100: Error in constructing NbiFormatter for NbiResponseMgr

Explanation Internal error.

Error Message

1101: No installed licenses were found. You will be unable to use this NBI API for this application.

Explanation No installed licenses were found. You are unable to use this NBI API for this application.

Recommended Action The API must have a license.

Error Message

1102: RbacManager access failed.

Explanation RbacManager access failed.

Recommended Action Check the login username and password.

Error Message

1103: An error occurred when checking installed licenses for the NBI API. Make sure the proper NBI property is included in your copy of vpnsc.properties. You will be unable to login.

Explanation The API must have a license.

Recommended Action Check the login username and password.

Error Message

1104: Unable to find object ({0}) with value ({1}). Referenced object does not exist.

Explanation Internal error.

Error Message

1105: nbiSoapWriter.send():: Failed trying to Format XML to specified output.

Explanation Internal error.

Error Message

1106: nbiSoapWriter.send():: An error occur in encapsulation output XML into SOAP.

Explanation Internal error.

Error Message

1107: nbiSoapWriter.send():: Unable to set resCtx object

Explanation Internal error.

Error Message

1108: SR wait time {0} has expired. The SR is still being processed by the system.

Explanation The wait flag was set on the Service Request and it expired. The NBI times out to free up the connection.

Recommended Action Increase the wait time to allow the Service Request to complete.

Error Message

1109: Method argument for subsuming SR should be old SR, that is, {0}.

Explanation ISC uses subsuming to represent historical Service Requests.

Error Message

1110: Unable to subsume the existing SR.

Explanation ISC uses subsuming to represent historical Service Requests.

Error Message

1111: Failed to instantiate the Manager class ({0}).

Explanation Internal error.

Error Message

1112: Manager class should be defined for modify SR in composite for node {0}.

Explanation Internal error.

Error Message

1113: MPLS VPN Link ID {0} to be removed does not belong to the SR to be modified.

Explanation User can delete only those MPLS VPN links that belong to the Service Request being modified.

Recommended Action Remove the MPLS VPN link from the modify request.

Error Message

1114: Incoming XML had the following bad ClassName: {0}

Explanation The classname attribute is not recognized.

Error Message

1115: Incoming XML, in the node {0}, had the following bad Attribute name: {1}

Explanation One of the properties or attributes in the XML is not recognized.

Error Message

1116: Incoming XML could not be parsed or there is a system problem.

Explanation Incoming XML could not be parsed or there is a system problem.

Error Message

1117: General failure reading incoming message; suspect a system problem.

Explanation General failure reading incoming message; suspect a system problem.

Error Message

1118: Parser failed, likely due to input XML formatting error near line {0} for element {1}.

Explanation Parser failed, likely due to input XML formatting error near line {0} for element {1}.

Error Message

1119: XML input error. Input error occurred at line {0} column {1}

Explanation XML input error. Input error occurred at line {0} column {1}.

Error Message

1120: The objectPath or className {0} is improperly nested.

Explanation The objectPath or className {0} is improperly nested.

Error Message

1121: The item {0} with value {1} resolves to multiple records. You must use {0} ID to uniquely identify.

Explanation The item {0} with value {1} resolves to multiple records. You must use {0} ID to uniquely identify.

Error Message

1122: The item {0} with value {1} does not exist.

Explanation The item {0} with value {1} does not exist.

Error Message

1123: I{0} to be deleted/modified not associated with the {1}.

Explanation {0} to be deleted/modified not associated with the {1}.

Error Message

1124: Optype {0} not allowed on {1} when parent {2} optype is not {3}.

Explanation Operation type {0} not allowed on {1} when parent {2} operation type is not {3}.

Error Message

1125: The Class {0} requires the attribute {1}.

Explanation The Class {0} requires the attribute {1}.

Recommended Action A mandatory element was not supplied. Check the GUI or XML schema for all the mandatory elements.

Error Message

1126: Application was unable to determine which attributes are mandatory for Class {0}, therefore XML input request cannot be processed.

Explanation Internal error.

Recommended Action A mandatory element was not supplied. Check the GUI or XML schema for all the mandatory elements.

Error Message

1127: In the Class {0}, you cannot modify the attribute {1}. Remove this attribute from your Modify request.

Explanation Certain fields can only be viewed or set initially but not modified.

Error Message

1129: In the Class {0}, you cannot create the attribute {1}. Remove this attribute from your Create request.

Explanation Certain fields cannot be created but can be viewed. This usually means the system creates them internally.

Error Message

1131: Invalid enum: class {0}, attribute {1}, enum {2}.

Explanation An enum is an allowed value for an attribute.

Recommended Action An enum is not supported. Check the GUI or XML schema for all the correct enums.

Error Message

1132: Delete query returned 0 objects.

Explanation The delete was not performed because the filter used did not return any objects.

Error Message

1133: Failed accessing RBAC security token

Explanation Internal error.

Error Message

1134: TestDeviceConsoleUtil: ERROR creating new DeviceConsoleUtil

Explanation Internal error.

Error Message

1135: Invalid element or value input.

Explanation Internal error.

Error Message

1136: Error downloading to the download console utility. ErrorMessage: {0}.

Explanation Internal error.

Error Message

1137: {0} type {1} is not defined. Please check valid set.

Explanation Internal error.

Error Message

1138: If {0} is/are given as constructor argument(s) then {1} should not be given for {2} object.

Explanation Internal error.

Error Message

1139: Required {0} as constructor argument(s) for {1} and found only {2}.

Explanation Internal error.

Error Message

1140: Unable to locate the Service Request with LocatorId {0}.

Explanation The Service Request is found by its Locator ID, which is the same as the Service Request Job ID in the GUI.

Error Message

1141: Provider must be defined if create default CERC for the VPN.

Explanation Provider must be defined if creating default CERC for the VPN.

Error Message

1142: The {0} {1} {2} is required for this operation.

Explanation The {0} {1} {2} is required for this operation.

Error Message

1143: subAction {0} not allowed on {1}.

Explanation A subaction is used in a modify to remove existing records. Some objects do not support subactions.

Error Message

1144: subAction {0} not allowed on {1} when parent {2} subAction is {3}.

Explanation A subaction is used in a modify to remove existing records. Some objects do not support subactions.

Error Message

1145: XML input error. Parsing error occurred for file {0}

Explanation XML input error. Parsing error occurred for file {0}.

Error Message

1150: Delete requests might not contain a properties section.

Explanation Delete requests might not contain a properties section.

Error Message

1151: Create requests must include a set of create attribute(s) and value(s).

Explanation Create requests must include a set of create attribute(s) and value(s).

Error Message

1152: Create requests might not include keyProperties elements.

Explanation Create requests might not include keyProperties elements.

Error Message

1153: Create Instances cannot include any other Instance(s) such as delete, modify, or view.

Explanation Create Instances cannot include any other Instance(s) such as delete, modify, or view.

Error Message

1154: Create requests must include a set of create attribute(s) and value(s).

Explanation Create requests must include a set of create attribute(s) and value(s).

Error Message

1155: Delete requests cannot be more than one level deep.

Explanation Delete requests cannot be more than one level deep.

Error Message

1156: Modify requests must include a set of modify attribute(s) and value(s).

Explanation Modify requests must include a set of modify attribute(s) and value(s).

Error Message

1157: Modify requests must include a keyProperties section for filtering purposes.

Explanation Modify requests must include a keyProperties section for filtering purposes.

Error Message

1158: Modify requests can contain only delete, create, or modify subactions.

Explanation Modify requests can contain only delete, create, or modify subactions.

Error Message

1159: Delete requests must include a keyProperties section for filtering purposes.

Explanation Delete requests must include a keyProperties section for filtering purposes.

Error Message

1160: Attribute {0} required for {1} operation of object {2}.

Explanation Attribute {0} required for {1} operation of object {2}.

Error Message

1161: Attribute {0} for Class {1} has an invalid enumeration value of {2}.

Explanation Attribute {0} for Class {1} has an invalid enumeration value of {2}.

Error Message

1162: Invalid Protocol: {0}.

Explanation Invalid Protocol: {0}.

Error Message

1163: Invalid Protocol Bundle: {0}.

Explanation Invalid Protocol Bundle: {0}.

Error Message

1164: Invalid Vendor Type: {0}.

Explanation Invalid Vendor Type: {0}.

Error Message

1165: The Request type ({0}) is not supported with Wait feature.

Explanation Waits are only supported on Service Requests.

Error Message

1166: Unable to start Service Request event collection

Explanation Unable to start Service Request event collection.

Error Message

1167: Select should be the first word in the query. Only select statements are supported.

Explanation A standard SQL requires select to be the first part of the statement.

Error Message

1168: Only one {0} allowed in the query. Correct the given SQL.

Explanation Only one {0} allowed in the query.

Recommended Action Correct the given SQL.

Error Message

1169: Word BY should follow {0}. Please correct the given SQL.

Explanation The word BY should follow {0}.

Recommended Action Correct the given SQL.

Error Message

1170: From clause (list of tables) is missing. Please correct the given SQL.

Explanation From clause (list of tables) is missing.

Recommended Action Correct the given SQL.

Error Message

1171: {0} clause should come before {1} clauses. Correct the given SQL.

Explanation {0} clause should come before {1} clauses.

Recommended Action Correct the given SQL.

Error Message

1172: Could not get database connection from the connection pool.

Explanation Could not get database connection from the connection pool.

Error Message

1173: Wrong column format for column {0}. Column name should have name and optional alias.

Explanation Wrong column format for column {0}. Column name should have name and optional alias.

Error Message

1174: Wrong table format for table {0}. Table name should have name and optional alias.

Explanation Wrong table format for table {0}. Table name should have name and optional alias.

Error Message

1175: Exception caught while processing ExecQuery request.

Explanation Exception caught while processing ExecQuery request.

Error Message

1176: Object {0} not found in the meta or there is no corresponding database table for this object.

Explanation Object {0} not found in the meta or there is no corresponding database table for this object.

Error Message

1177: Wrong column name format for column {0}. Column name format should be optional <table>.columnName

Explanation Wrong column name format for column {0}. Column name format should be optional <table>.columnName.

Error Message

1178: No corresponding database column for parameter {0} of object {1}.

Explanation No corresponding database column for parameter {0} of object {1}.

Error Message

1179: Param {0} present in multiple objects. Give fully qualified name <objectName/alias.paramName>.

Explanation Parameter {0} is present in multiple objects. Give fully qualified name <objectName/alias.paramName>.

Error Message

1180: Object or alias {0} of parameter {1} not defined in object or alias list in from clause.

Explanation Object or alias {0} of parameter {1} is not defined in an object or alias list in the from clause.

Error Message

1181: The attribute ({0}) is not editable.

Explanation The attribute ({0}) is not editable.

Error Message

1182: Required number of {0} node(s) between {1} and {2}, but found {3}.

Explanation Required number of {0} node(s) between {1} and {2}, but found {3}.

Error Message

1183: Wrong 'occurs' format for node {0}. The format should be '{range}'. Check the composite XML.

Explanation Internal error.

Error Message

1184: Wrong `occurs' format for node {0}. The format should be `{range}'. Check the composite XML.

Explanation Internal error.

Error Message

1185: Wrong `occurs' format for node {0}. The format should be {minRage,maxRange} and minRange should be a number. Given occurs is {1}. Check the composite XML.

Explanation Internal error.

Error Message

1186: Wrong occurs format for node {0}. The format should be {minRage,maxRange} and minRange should be less than maxRange. Given occurs is {1}. Check the composite XML.

Explanation Internal error.

Error Message

1187: Wrong occurs format for node {0}. The format should be {minRage,maxRange} and maxRange should be a number or "*". Given occurs is {1}. Check the composite XML.

Explanation Internal error.

Error Message

1188: Only '=' and '!=' operations are supported for enum parameter {0}.

Explanation Only the '=' and '!=' operations are supported for the enum parameter {0}.

Error Message

1189: Enum value string for parameter {0} should be enclosed in single quotation marks.

Explanation Enum value string for parameter {0} should be enclosed in single quotation marks.

Error Message

1190: The attribute {0} has an invalid value {1}. Please check valid values in {2}.

Explanation The attribute {0} has an invalid value {1}. Check valid values in {2}.

Error Message

1191: {0} is not a valid Transaction Attribute. Cannot {1} this attribute value.

Explanation {0} is not a valid Transaction Attribute. Cannot {1} this attribute value.

Error Message

1192: The value for the Transaction Attribute {0} is NULL; the transaction cannot be completed.

Explanation The value for the Transaction Attribute {0} is NULL; the transaction cannot be completed.

Error Message

1193: A minimum of {0} physical links are required to form a ring.

Explanation A minimum of {0} physical links are required to form a ring.

Error Message

1194: Named Physical Circuit Ring modification failed.

Explanation Named Physical Circuit Ring modification failed.

Error Message

1195: Sequential Physical Links must have a common device. Destination device #{0} of Ring Link {1} does not match the next source {2} of Ring Link {3}.

Explanation Sequential physical links must have a common device. Destination device #{0} of ring link {1} does not match the next source {2} of ring link {3}.

Error Message

1196: Device to be used in Ring not found in database

Explanation Device to be used in a ring is not found in the database.

Error Message

1197: A Ring MUST have a common first and last device! The first source device #{0} of the Ring does not match the final destination device #{1}

Explanation A ring must have a common first and last device. The first source device #{0} of the ring does not match the final destination device #{1}.

Error Message

1198: An error has occurred while creating requested deployment tasks.

Explanation An error occurred while creating requested deployment tasks.

Messages 1200-1299 (Traffic Engineering Management Messages)

Error Message

1203: {0}::{1}: TeProvider "{2}" already exists.

Explanation TeProvider with the specified name has already been used.

Recommended Action Use a different name.

Error Message

1205: {0}::{1}: Tunnel Number "{2}" already exists.

Explanation The tunnel number has been used for an existing tunnel.

Recommended Action Use a different number.

Error Message

1206: {0}::{1}: Failed to commit TeExplicitPath "{2}", because it contains non-contiguous links.

Explanation The path in question is not contiguous.

Recommended Action Specify a contiguous path.

Error Message

1207: {0}::{1}: TeExplicitPath "{2}" already exists.

Explanation The pathname has been used by an existing path.

Recommended Action Use a different pathname.

Error Message

1208: {0}::{1}: TeProvider "{2}" cannot be deleted while SRLGs, Explicit Paths, or SRs are still associated with it.

Explanation TeProvider cannot be deleted unless the Share Risk Link Groups (SRLGs), Explicit Paths, and Service Requests underneath it have been deleted.

Recommended Action Delete the SRLG, Explicit Path, or Service Request objects underneath the provider before deleting the provider.

Error Message

1209: {0}::{1}: SR({2}) cannot be subsumed because it has been subsumed by SR({3}).

Explanation The Service Request in question has been edited, possibly from another session or user.

Recommended Action Exit the Service Request edit window and re-enter.

Error Message

1210: {0}::{1}: DeviceInterface cannot be found with TeInterface ID({2}).

Explanation The DeviceInterface might have been removed while others were still referencing it.

Recommended Action Remove the backup tunnel that is protecting the TeInterface.

Error Message

1211: {0}::{1}: TeInterface cannot be found with interface name "{2}".

Explanation The TeInterface might have been removed while others were still referencing it.

Recommended Action Remove the backup tunnel that is protecting the TeInterface.

Error Message

1212: {0}::{1}: TE Tunnel Policy "{2}" is in use and cannot be deleted.

Explanation The tunnel policy is used by a Traffic Engineering (TE) primary tunnel and therefore it cannot be deleted.

Recommended Action Delete the tunnel that is using the policy before deleting the policy.

Messages 1300-1399 (Repository Messages)

Error Message

1304: Invalid API call: API {0} cannot be called on object {1} because {2}.

Explanation Internal ISC software error. The application layer did not invoke the correct API.

Recommended Action If this happens, please submit a bug with detailed steps to reproduce it.

Error Message

1306: Internal Repository Error : {0}

Explanation Internal error.

Recommended Action If this happens, please submit a bug with detailed steps to reproduce it.

Error Message

1318: Object {0} is null for {1} with {2} : {3}

Explanation NULL object.

Recommended Action GUI or NBI should pass a valid object to the repository.

Error Message

1319: Invalid Class : Class {0} should be a subclass of {1}

Explanation Object with wrong class.

Error Message

1320: Invalid Policy Node: Attribute {0} is not defined.

Explanation Assigned wrong policy attribute to the policy.

Recommended Action Re-create the policy again.

Error Message

1321: Invalid Attribute Value: Attribute {0} should have {1} value.

Explanation Assigned wrong value or out of range value to the attribute.

Recommended Action Reassign the expected value specified on {1} to that attribute.

Error Message

1322: Policy with ID {0} is associated with SRs, hence {1}.

Explanation Policy is already associated with Service Requests. It cannot be modified or deleted.

Recommended Action Do not update or delete this policy if it is already associated with Service Requests.

Error Message

1323: Argument {0} is invalid because {1} is {2}

Explanation GUI passed the wrong data to the repository.

Error Message

1324: Duplicate Policy: Policy with name {0} already exists under {1} with ID {2}.

Explanation You tried to create a duplicate policy.

Recommended Action Assign a different name to this policy.

Error Message

1325: Parent object {0} is null.

Explanation ISC internal error. This object did not have a parent object. GUI catches the exception and take the appropriate actions.

Error Message

1326: More than one physical link object exists between source interface with ID {0} and destination interface with ID {1}

Explanation Duplicate links between two end points.

Recommended Action Re-create the physical link using different source and destination endpoints.

Error Message

1327: Invalid value passed for attribute {0} : value {1} is invalid, it should be {2}

Explanation You assigned a wrong value to the object.

Recommended Action Reassign the correct value as specified on {2}.

Error Message

1328: Policy attribute {0} is not set for attribute {1}

Explanation Policy attribute specified on {0} is required to be set for attribute specified on {1}. Attribute specified on {1} is dependent on attribute {0}.

Recommended Action Set the required attribute {0}.

Error Message

1329: Invalid Policy Node: Attribute {0} is not set.

Explanation Required policy attribute is not set.

Recommended Action Set this attribute.

Error Message

1330: Invalid {0} value {1} is set for attribute {2}. Valid range is {3}.

Explanation Invalid value is assigned to attribute.

Recommended Action Set the valid attribute value within the range.

Error Message

1356: Object {0} cannot be deleted because it is associated with {1} with IDs {2}.

Explanation This object cannot be deleted because it is already associated with other objects.

Recommended Action Do not delete this object.

Error Message

1357: Object {0} cannot be modified because it is associated with {1} with IDs {2}.

Explanation This object cannot be modified because it is already associated with other objects.

Recommended Action Do not modify this object.

Error Message

1360: Object {0} with ID {1} did not have policy associated with it.

Explanation Invalid Service Request because it did not have any policy associated with it.

Recommended Action Re-create the Service Request and assign a policy to this Service Request.

Error Message

1361: Cannot add a link into a DELETE SR. Create an ADD SR instead.

Explanation You tried to add a link to a deleted Service Request, which is not allowed.

Recommended Action Create an add Service Request and add that link to that Service Request.

Error Message

1362: Cannot remove a link from a DELETE SR. Create an ADD SR instead.

Explanation You tried to delete a link to a deleted Service Request, which is not allowed.

Recommended Action Create an add Service Request.

Error Message

1363: Link with ID {0} is already added to the SR; it cannot be added to the SR again.

Explanation The link is already associated with a Service Request. It cannot be added to another Service Request.

Recommended Action Create a new link and add it to a Service Request or abort this action.

Error Message

1364: VRF with ID {0} is with name {1}, which mismatches with the name {2}provided by the user.

Explanation You assigned a VRF name which is different than the name in the database.

Recommended Action Assign the correct VRF name.

Error Message

1366: Only one CERC is allowed to be associated with grey mgmt VPN. There are {0} CERCs associated with grey mgmt VPN with name {1}

Explanation You tried to associate more than one CERC to the grey management VPN.

Recommended Action Grey management VPN is auto-created by the repository. You should not change the definition of grey management VPN by assigning more than one CERCs to that VPN.

Error Message

1367: Same connectivity between {0}:{1} and {2}:{3} has existed on MPLS VPN Link with ID {4} and SR ID {5}.

Explanation You tried to create duplicate links with the same connectivity.

Recommended Action Change the endpoints of the link to avoid the duplicate connectivity.

Error Message

1368: {0} IP address {1} and {2} IP address {3} are not in the same subnet.

Explanation Manually assigned IP addresses should be in the same subnet. You tried to assign IP addresses of a link on a different subnet.

Recommended Action Assign the IP addressed within one subnet.

Error Message

1369: SR creation failed due to missing information on {0}

Explanation Missing some required information during the Service Request creation.

Recommended Action Add the required data for Service Request creation.

Error Message

1370: MPLS VPN Link with ID {0} joins {1} Multicast VPNs. MPLS VPN Link can only join one Multicast VPN.

Explanation One MPLS VPN link can join only one multicast VPN. You tried to assign more than one multicast VPN to that VPN link.

Recommended Action Assign only one multicast VPN to that link.

Error Message

1371: RT with value {0} is in invalid format.

Explanation Your input RT is not in the correct format.

Recommended Action Enter the RT in the correct format.

Error Message

1372: IsFullMesh cannot be changed on the existing CERC with ID {0}.

Explanation You tried to change the topology definition on an existing CERC, which is not allowed.

Recommended Action Do not change the topology definition on an existing CERC.

Error Message

1373: VLAN ID on link endpoints with value {0} and {1} are different.

Explanation You assigned different VLAN IDs on link endpoints. The GUI should catch the exception and take the appropriate actions.

Recommended Action Assign the same VLAN ID on link endpoints.

Error Message

1374: UNI and NPC are not in the same device. NPC CE-facing device has the ID {0}; however the UNI interface is landing on the device with ID {1}.

Explanation The user-specified UNI interface did not land on the specified Named Physical Circuit. (NPC).

Recommended Action Assign the UNI interface on the selected NPC.

Error Message

1375: Manually assigned resource {0} with value {1} that has already been used. Assign a new value.

Explanation You tried to use a resource that has been used.

Recommended Action Reassign a new value.

Error Message

1376: Only N-PE can be added to an Access Domain.

Explanation You tried to add a non-N-PE to the access domain. Only a PE with an N-PE type can be associated with an Access Domain.

Recommended Action Select the PE with the N-PE role to associate with the Access Domain.

Error Message

1377: Full Mesh CERC with ID {0} is not allowed to join as spoke.

Explanation CERC with full-mesh topology definition is not allowed to be changed to hub-and-spoke topology.

Recommended Action Do not change the topology definition on an existing CERC.

Error Message

1378: Deleted type {0} cannot add object {1}.

Explanation An object with a deleted type cannot add any object.

Recommended Action Create a new object with add type, then add the required objects to that object.

Error Message

1379: Only 2 Attachment Circuits are allowed within one EndToEndWire. There are {0} Attachment Circuits in EndToEndWire.

Explanation You tried to assign more than two Attachment Circuits to one end-to-end wire.

Recommended Action Assign only two Attachment Circuits to that end-to-end wire.

Error Message

1380: CERC with ID {0} is not tied to VPN.

Explanation CERC should be associated to a VPN. You created a CERC without associating it to any VPN.

Recommended Action Associate the CERC to a VPN.

Error Message

1381: Feature {0} is not supported yet.

Explanation The specified feature is not yet supported.

Recommended Action Do not access this feature.

Error Message

1382: VRF with name {0} with RD {1} already exists on PE with ID {2}. The VRF name that you input with RD value {3} will create conflicts on the router. Assign another new VRF name. The Associated SRs are: {4}.

Explanation ISC enforces that the route distinguisher (RD) be unique across VRFs across PEs. That is, two VRFs with different VRF names on two different PEs cannot have the same RD. IOS enforces this restriction for a given device.

Recommended Action Specify an RD that does not conflict with an existing VRF in ISC.

Error Message

1383: VRF with ID {0}, with name {1}, and with RD {2} is associated with Closed SR {3}. You cannot modify the VRF name to {4}. Purge these Closed SRs first.

Explanation ISC enforces that the route distinguisher (RD) be unique across VRFs across all PEs. If Closed Service Requests have VRFs with different names using the same RD, this exception occurs to indicate which Service Requests must be purged so you are permitted to create a new Service Request with a different VRF and the same RD.

Recommended Action Purge the Service Requests indicated in the exception.

Error Message

1384: VRF with ID {0}, with name {1}, and with RD {2} is associated with SR {3}. You cannot modify the VRF name to {4}.

Explanation ISC enforces that the route distinguisher (RD) be unique across VRFs across all PEs. This exception is thrown to inform you of the list of Service Requests that use the same RD with different VRF names and non-closed states.

Recommended Action Specify a different RD for this Service Request. If the same RD needs to be used, decommission and purge all the Service Requests specified in the exception.

Error Message

1385: RD value {0} is invalid. It has to be "#:#" where # is an integer value.

Explanation The provided RD value is in an invalid format. It must be "#:#" where # is an integer value.

Recommended Action Provide a valid RD value.

Error Message

1386: Cannot enable multicast for MPLS VPN Link with ID {0} because no Multicast VPN is associated with it.

Explanation Cannot enable multicast for MPLS VPN Link with ID {0}, because there is no multicast VPN associated with it.

Recommended Action Enable multicast at the VPN level before enabling it for the link.

Error Message

1387: Cannot set PIM Mode for MPLS VPN Link with ID {0} because no Multicast VPN is associated with it.

Explanation You cannot set PIM mode for MPLS VPN Link with ID {0}, because there is no multicast VPN associated with it.

Recommended Action Enable multicast at the VPN level and at the link level before setting the PIM mode for the link.

Error Message

1388: Cannot set PIM Mode for MPLS VPN Link with ID {0} because multicast is not enabled for the link.

Explanation You cannot set the PIM mode for the MPLS VPN Link with ID {0}, because multicast is not enabled for the link.

Recommended Action Enable multicast for the link before setting the PIM mode.

Error Message

1389: Mismatched shared attribute values. The shared attribute {0} in database has value {1}, but the user has entered the shared attribute with value {2}.

Explanation The value entered for a shared attribute is different from the value shared across all links sharing these attributes.

Recommended Action Use the shared attribute value for the attribute.

Error Message

1390: Residential MPLS VPN Link with VLAN ID {0} cannot be created as a MPLS VPN Link with ID {1} and SR job ID {2} already exists with this VLAN ID terminating on N-PE {3} in the access domain {4}.

Explanation Two U-PEs cannot use the same VLAN in the same access domain for creating ETTH and residential services.

Recommended Action Use a different shared VLAN value for the link being created.

Error Message

1391: PE cannot be associated with Region {0} because Device {1} is already associated with Region {2}.

Explanation PEs created out of the same device cannot be associated with two different regions.

Recommended Action Do not create PEs on the same device associated with two different regions.

Messages 1400-1499 (Repository Messages)

Error Message

1401: Last physical link with ID {0} on NPC did not land on PE.

Explanation The last physical link on a Named Physical Circuit (NPC) did not terminate on a PE.

Recommended Action Reselect the last physical link that terminates on a PE.

Error Message

1402: First physical link with ID {0} on NPC did not land on CE for CE scenario.

Explanation The first physical link on an NPC did not terminate on a CE.

Recommended Action Reselect the first physical link that starts on a CE.

Error Message

1403: NPC with ID {0} did not start on CE device for CE scenario

Explanation The starting device of an NPC did not start on a CE for a CE scenario.

Recommended Action Re-create the NPC with the starting device set on a CE for a CE scenario.

Error Message

1404: NPC with ID {0} did not end on an N-PE device.

Explanation The ending device of a Named Physical Circuit (NPC) did not end on a PE with an N-PE role.

Recommended Action Re-create the NPC with the ending device set on a PE with role N-PE.

Error Message

1405: {0} creation error: {1} with {2}: {3} cannot be followed by {4} with {5}: {6} because they have no common devices between them. Connectivity is not established.

Explanation Entities for Named Physical Circuit (NPC) creation are not connected. Two consecutive physical links should have a device that is common. A consecutive pair of ring and physical links should have at least one device in common.

Recommended Action Ensure proper connectivity between consecutive entities, rings, or physical links.

Error Message

1406: NPC creation error: Ring with name {0} does not have device in common with Ring {1}

Explanation Entities for NPC Creation are not connected. Two consecutive rings should have at least one device that is common.

Recommended Action Ensure concerned rings are connected.

Error Message

1407: NPC creation error: The logical device with name {0} is not part of the ring with name {1}

Explanation A consecutive physical link and ring for NPC creation are not connected. The physical link's destination should be one of the devices in the ring if the physical link is before the ring. The physical link's source should be in one of the devices in the ring if the physical link is after the ring in NPC creation order.

Recommended Action Ensure the concerned ring and physical link are connected.

Error Message

1408: NPC creation error: The set of physical links in ring {0} and ring {1} are identical.

Explanation The same ring was consecutively added for the NPC creation.

Recommended Action Do not select the same ring twice while creating an NPC.

Error Message

1409: {0} creation error: Physical link with ID {1} cannot be followed by physical link with ID {2} because interface with name {3} is selected as both source and destination for the common device {4}.

Explanation The same interface has been selected both as the destination and source on the given device while creating an NPC.

Recommended Action Select different interfaces as source and as destination on the given device.

Error Message

1410: {0} creation error: Device with name: {1}, and ID: {2} is source or destination for more than two links.

Explanation The error message says whether the error occurred while creating a ring or an NPC. While creating a ring or an NPC, the same device is selected more than twice.

Recommended Action For the proper connectivity of devices, the same device cannot be part of more than two links.

Error Message

1411: NPC creation error: {0} with ID: {1} is already added to the NPC.

Explanation The same ring or physical link is being added to the Named Physical Circuit (NPC) twice.

Recommended Action Do not try to add the same link, a pair of source and destination interfaces, twice. This error might also appear when adding a ring to an NPC and the ring contains the link already added to the NPC or when adding a link that is contained in the ring already added to the NPC.

Error Message

1412: Ring or Collection cannot be the last object in the object list for NPC formation.

Explanation When creating a Named Physical Circuit (NPC), the ring should not be selected as the last element in the collection.

Recommended Action Do not add a ring as the last element.

Error Message

1413: Device with ID {0} cannot be the source device for creating this Named Physical Circuit.

Explanation The selected device cannot be a source device of a Named Physical Circuit (NPC).

Recommended Action Select a device that it is part of the ring if the ring is the first connectivity for an NPC.

Error Message

1414: Device with ID {0} is not a part of ring that is the last element on the collection for creating NPCs.

Explanation The device selected as the destination cannot be the destination device of a Named Physical Circuit (NPC).

Recommended Action Select a destination device so that it is part of the ring if the ring is the last connectivity for an NPC.

Error Message

1415: Named Physical Circuit with Name: {0} is not a valid NPC, because its Destination Device: {1} is not of type N-PE. Delete this Named Physical Circuit and try creating the NPC again.

Explanation The Named Physical Circuit (NPC) given by the name is already created erroneously, because its destination device is not of type N-PE and should be removed.

Recommended Action Delete the relevant NPC and try creating it again.

Error Message

1416: Device: {0} does not have a role of type N-PE. For an NPC creation destination device, you should be an N-PE.

Explanation The NPC's destination device must be of type N-PE.

Recommended Action Select a device with a role of N-PE as a destination device for NPC.

Error Message

1417: Devices : {0} cannot be deleted from the ring, because these devices are being provisioned by SRs with job IDs: {1}. Decommission or purge these SRs before deleting the devices from the ring.

Explanation Because a device has Service Requests provisioned, you cannot delete nodes from the ring.

Recommended Action Decommission or purge these Service Requests before deleting the devices from the ring.

Error Message

1418: Device: {0} cannot be added to the ring, because this device belongs to Named Physical Circuits: {1}. These Named Physical Circuits also contain the ring. Delete these Named Physical Circuits if you want to add this node to the ring.

Explanation Because the device has already been modeled in another NPC with ring, it cannot be part of the current ring.

Recommended Action Delete the old NPCs if you want to add the device to the current ring.

Error Message

1419: Device: {0} would get added twice for the Named Physical Circuit creation. This could happen either because a Named Physical Circuit was automatically extended because the terminating device chosen was a U-PE and the ISC database Named Physical Circuit to which this was being added already contained this device, this device was added twice, or this device is also a part of the ring that is added for the Named Physical Circuit creation.

Explanation This could happen either because a Named Physical Circuit (NPC) was automatically extended because the terminating device chosen was a U-PE and the ISC database NPC to which this was being added already contained this device, this device was added twice, or this device is also a part of the ring that is added for the NPC creation.

Recommended Action Do not use the same device twice in a particular NPC.

Error Message

1421: UNI Port {0} with ID {1} on device {2} with ID {3} is used by customer with name {4} on {5} with ID:{6}, SR_ID:{7}, SR_JOB_ID:{8}. It cannot be used by the current customer with the name {9}.

Explanation Because a particular UNI has been used by a different customer, you cannot reuse this UNI for the current customer.

Recommended Action Select a different UNI.

Error Message

1422: EIGRP PE/CE AS ID cannot be modified on a Deployed link.

Explanation PE/CE AS ID in EIGRP routing protocol cannot be modified after a link is deployed.

Recommended Action Decommission the link and redeploy a new link with new attributes.

Error Message

1423: BGP neighbor IP address cannot be same as PE IP address.

Explanation BGP neighbor IP address cannot be the same as the PE IP address.

Recommended Action Enter a different IP address for the BGP neighbor.

Error Message

1424: VRF is already deployed and RD override value cannot be modified.

Explanation Cannot modify RD override value for a VRF that is already deployed.

Recommended Action If RD override value needs to be modified, first decommission all the Service Requests associated with this VRF.

Error Message

1425: Cannot form a Ring with {0} devices and {1} links.

Explanation The given set of devices and the connectivity specified do not form a ring. That is, the circular connectivity among the devices is not properly established.

Recommended Action Ensure that the given devices and their connectivities form a circular ring.

Error Message

1426: Ring: {0} has only {1} link. It should have a minimum of {2} links to form a Ring.

Explanation A specified minimum number of links are required to form a ring.

Recommended Action Specify at least the minimum number of links, as recommended in the error message to form a ring.

Error Message

1427: Ring with {0}: {1} exists in database for a given set of devices and interfaces.

Explanation Trying to commit a ring when a ring with an identical set of devices and connections already exists in the database. A case of a duplicate ring.

Recommended Action Do not try to create a ring that is identical to one already in the database.

Error Message

1429: Cannot remove CERC from VPN when there are policy or service requests associated with it.

Explanation CERC cannot be removed when there are policy or service requests associated with it.

Recommended Action Decommission and purge all the associated Service Requests and delete all the associated policies before removing a CERC.

Error Message

1430: Interface: {0} on Device: {1} is already used for this ring. Select another interface for the cross link.

Explanation The interface has already been used in the ring.

Recommended Action Select a different interface for a cross connection.

Error Message

1431: Device: {0} is selected as both source and destination of the cross link.Select another device.

Explanation Same device has been selected as both the source and the destination for the cross link.

Recommended Action Select a different device as a source or destination for the cross link.

Error Message

1432: Device: {0}, selected for cross link, is not used for this ring. Select a device which is part of the ring.

Explanation The device selected for the cross link is not used in the ring.

Recommended Action Make sure that the selected device in the cross link is also part of the ring.

Error Message

1433: Interface: {0} on Device: {1} is used for {2}. Use another interface or delete the concerned {3}.

Explanation The specified interface on the device is already being used in another Named Physical Circuit (NPC).

Recommended Action Either use a different interface or delete the NPC using the interface.

Error Message

1451: {0} not a valid MAC address.

Explanation The given MAC address is not valid.

Recommended Action Give a valid MAC address.

Error Message

1452: MAC address cannot be null.

Explanation The given MAC address is null.

Recommended Action Give a valid MAC address.

Error Message

1453: Attributes for Policy or Attachment Circuit not set.

Explanation Trying to persist or create a Service Request or link that does not have a valid policy or link attributes set respectively.

Recommended Action Associate the respective Service Request or link with a proper policy or link attribute.

Error Message

1454: Protocol Tunneling is not enabled or not set.

Explanation Protocol tunneling is not enabled.

Recommended Action This attribute should be enabled before setting any tunneling related fields.

Error Message

1455: ATTRIBUTE_ID not set.

Explanation A generic error occurs if the link attribute is not created properly.

Error Message

1456: {0} : permissionType is unknown.

Explanation The given permission type is not a valid permission type.

Recommended Action Give a valid permission type.

Error Message

1457: {0} : speedType is unknown.

Explanation The given speed type is not valid.

Recommended Action Give a valid speed type.

Error Message

1458: {0} : duplexType is unknown.

Explanation The given duplex type is not valid.

Recommended Action Give a valid duplex type.

Error Message

1459: Port Security is not enabled or not set.

Explanation Trying to set the UNI secure Mac address without setting the port security flag.

Recommended Action Enable the port security flag.

Error Message

1460: {0} : violationActionType is unknown.

Explanation The given violation action type is not a valid type.

Recommended Action Give a valid violation action type.

Error Message

1461: {0} : interfaceType is unknown.

Explanation The given interface type is not a valid type.

Recommended Action Give the correct interface type.

Error Message

1462: interfaceShutdown value should be Boolean: {0}.

Explanation An improper string value exists for interfaceShutdown.

Recommended Action Give a correct string value for the Boolean type.

Error Message

1463: {0} : interfaceEncap is unknown.

Explanation The given interface encapsulation is not a valid type.

Recommended Action Give a correct interface encapsulation type.

Error Message

1464: {0} policy not set.

Explanation Trying to create a Service Request that does not have a valid policy set.

Recommended Action Associate the concerned Service Request with a proper policy.

Error Message

1465: {0} : Boolean value given is invalid.

Explanation An improper string value was given for the Boolean type.

Recommended Action Give a correct string value for the Boolean type.

Error Message

1466: {0} : L2VpnIpProtocolType is unknown.

Explanation The given L2VpnIpProtocol is not a valid type.

Recommended Action Give a valid L2VpnIpProtocol type value.

Error Message

1467: {0} : L2VpnSequenceType is unknown.

Explanation The given L2VpnSequenceType is not a valid type.

Recommended Action Give a valid L2VpnSequenceType value.

Error Message

1468: {0} : L2VpnCoreType is unknown.

Explanation The given L2VpnCoreType is not a valid type.

Recommended Action Give a valid L2VpnCoreType value.

Error Message

1469: {0} : L2VpnPayloadType is unknown.

Explanation The given L2VpnPayloadType is not a valid type.

Recommended Action Give a valid L2VpnPayloadType value.

Error Message

1470: {0} Policy cannot be deleted. {1}.

Explanation The policy cannot be deleted because of the reason given in the error message.

Recommended Action Most probably Service Requests are associated with the policy so it cannot be deleted. Purge the Service Request if you really want the policy to be deleted.

Error Message

1471: {0} Policy cannot be modified. {1}.

Explanation The policy cannot be modified because of the reason given in the error message.

Recommended Action Policy is associated with a Service Request and cannot be modified. Purge the Service Request if you really want the policy to be modified or create a new policy.

Error Message

1472: L2VPN service type not set.

Explanation A valid service type must be set on the L2VPN policy.

Recommended Action Set a valid service type on the policy.

Error Message

1473: {0}::{1}: Invalid range for service attribute {2}.

Explanation An invalid range is given for the attribute given in the error message.

Recommended Action Give a correct range for the attribute given in the error message.

Error Message

1474: {0}: AtmVcEnabelOamType is unknown.

Explanation L2TPv3 OAM type for Asynchronous Transfer Mode (ATM) Virtual Circuit (VC) mode is invalid.

Recommended Action Choose a valid OAM type.

Error Message

1475: {0}: SessionSetupMode is unknown.

Explanation L2TPv3 Session Setup Mode is invalid.

Recommended Action Choose a valid setup mode.

Error Message

1476: {0}: DfbitSetType is unknown.

Explanation L2TPv3 Don't Fragment Bit value is invalid.

Recommended Action Choose a valid Don't Fragment Bit value.

Error Message

1477: {0}: DLCI values mismatch between AttachmentCircuit1 (CE_DLCI={1}; PE_DLCI={2}) and AttachmentCircuit2 (CE_DLCI={3}; PE_DLCI={4}) with Transport mode FrameRelay port trunking.

Explanation L2TPv3 FrameRelay data-link connection identifier (DLCI) mismatch between the CE and the PE.

Recommended Action Choose the same DLCI for the CE and the PE.

Error Message

1478: {0}: VPI values mismatch between AttachmentCircuit1(CE_VPI={1}; PE_VPI={2}) and AttachmentCircuit2 (CE_VPI={3}; PE_VPI={4}) with transport mode ATM VP.

Explanation L2TPv3 Asynchronous Transfer Mode (ATM) virtual path identifier (VPI) mismatch between the CE and the PE.

Recommended Action Choose the same VPI for the CE and the PE.

Error Message

1479: {0}: PE's and CE's VPI/VCI values mismatch for AttachmentCircuit1 (CE_VPI={1}; CE_VCI={2}; PE_VPI={3}; PE_VCI={4}) or AttachmentCircuit2 (CE_VPI={5}; CE_VCI={6}; PE_VPI={7}; PE_VCI={8}) with transport mode ATM VCI.

Explanation L2TPv3 Asynchronous Transfer Mode (ATM) virtual path identifier (VPI) or virtual channel identifier (VCI) mismatch between the CE and the PE.

Recommended Action Choose the same VPI or VCI for the CE and the PE.

Error Message

1480: {0}: FrameRelay port trunking and DLCI are mutually exclusive. L2VPN SRs (JobIDs={1}) with Transport mode {2} already exist on major interface {3} on PE {4}.

Explanation L2TPv3 FrameRelay port_trunking cannot share the data-link connection identifier (DLCI) with the other link.

Recommended Action Choose another DLCI for the intended link.

Error Message

1481: Interfaces PE: {0} CE: {1} are of type Multi-link FrameRelay so transport mode cannot be PORT_TRUNKING. Use DLCI as transport mode.

Explanation L2TPv3 FrameRelay multi-link FrameRelay (MFR) does not support the port_trunking mode.

Recommended Action Choose another type of interface for the port_trunking mode.

Error Message

1482: {0}: ATM VP and VC are mutually exclusive with VPI value. L2VPN SRs (JobIDs={1}) with Transport mode {2} already exist on ATM port {3} on PE {4}.

Explanation L2TPv3 Asynchronous Transfer Mode (ATM) virtual path identifier (VPI) cannot be shared by another link of the same port.

Recommended Action Choose another VPI for this link.

Error Message

1483: {0} : Same SR cannot have mix of local and non-local switch links. Two UNIs for each link (wire) should be from the same PE or two UNIs for each link(wire) should be from different PEs. Cannot have links with mixture of both in the same SR.

Explanation A Service Request cannot have a mix of local and non-local switch links. Two UNIs for each link (wire) should be from the same PE or two UNIs for each link (wire) should be from different PEs. A mixture of links cannot occur in the same Service Request.

Recommended Action Change the PEs or create the link under a new Service Request.

Error Message

1484: {0} : DLCI values should not be same on AttachmentCircuit1 (PE_DLCI={1}) and AttachmentCircuit2 (PE_DLCI={2}) for UNI local switch link on same PE physical interface.

Explanation Identical data-link connection identifiers (DLCIs) exist for this locally switched FrameRelay L2VPN on the same port.

Recommended Action Use a different DLCI for each endpoint.

Error Message

1485: {0}: VPI and VCI values should not be same on AttachmentCircuit1 (PE_VPI={1}; PE_VCI={2}) and AttachmentCircuit2 (PE_VPI={3}; PE_VCI={4}) for UNI local switch link on same PE major interface.

Explanation Identical virtual path identifier (VPI) and virtual channel identifier (VCI) for this locally switched Asynchronous Transfer Mode (ATM) L2VPN on the same port.

Recommended Action Use a different VPI and VCI for each endpoint.

Error Message

1486: {0}: Interface encapsulation should be the same on AttachmentCircuit1(ceIntfEncap={1}) and AttachmentCircuit2(ceIntfEncap={2}) for ATM VP service.

Explanation Different interface encapsulation types exist for this point-to-point L2VPN.

Recommended Action Select the same encapsulation type.

Error Message

1487: L2VPN Policy: Unknown PE port type: {0}

Explanation The port type should be set by the GUI and should be either data terminal equipment (DTE) or data communication equipment (DCE).

Error Message

1488: Devices in the Attachment Circuit do not support 1:1 VLAN translation.

Explanation You have chosen one-to-one translation to be applied to an Attachment Circuit. However, none of the devices in the Attachment Circuit support one-to-one translation.

Recommended Action Make sure there are 3750 or 7600 devices supporting one-to-one translation in the Attachment Circuit.

Error Message

1489: Devices in the Attachment Circuit do not support 2:1 VLAN translation to be applied at the translation point: {0}.

Explanation You have chosen two-to-one translation to be applied to an Attachment Circuit. However, none of the devices in the Attachment Circuit support two-to-one translation.

Recommended Action Make sure there are 3750 or 7600 devices supporting two-to-one translation in the Attachment Circuit.

Error Message

1490: Devices in two directions of ring do not support VLAN translation.

Explanation Devices in one or two paths of a ring from source to destination do not support VLAN translation.

Recommended Action Make sure there are 3750 or 7600 devices supporting translation in both directions of a ring.

Error Message

1491: Internal API returning incorrect topology information for Attachment Circuit.

Explanation Internal API in ISC returns incorrect topology information for a particular Attachment Circuit.

Recommended Action Contact ISC support.

Error Message

1492: AC with service type: ERS, VLAN translation: {0} and {1} cannot be created because AC with following details: SR Job ID: {2} , AC_ID: {3} , Service Type: {4}, VLAN translation: {5} and {6} is already configured over the UNI: {7}.

Explanation VLAN translation cannot be created over a UNI if another Service Request already exists with translation over the same UNI.

Recommended Action Do not provision translation over a UNI that has already been involved in translation.

Error Message

1493: A {0} with Job_Id : {1} already exists over the UNI : {2} and hence the given {3} cannot be configured.

Explanation Conflicting L2VPN services cannot be configured over the same UNI.

Recommended Action Do not provision conflicting L2VPN services over the same UNI.

Error Message

1494: The parent Attachment Circuit has the translation type : {1} and it cannot be changed to {0}

Explanation Cannot change the VLAN translation type from one-to-one to two-to-one or from two-to-one to one-to-one.

Recommended Action Do not change the VLAN translation type on a deployed service. Decommission and create a new service with a different translation type.

Error Message

1495: Disallowed use of multiple Customers using duplicate VLAN ID for 3750.

Explanation Different customers with the duplicate VLAN ID should not undergo translation on the same 3750.

Recommended Action Make sure the Service Requests belonging to different customers and the same VLAN IDs are not created on the same 3750.

Error Message

1496: Two UNIs are on the same Device: {0} therefore VLAN 2:1 translation cannot be performed.

Explanation Different customers with the duplicate VLAN ID should not undergo translation on the same 3750.

Recommended Action Make sure the Service Requests belonging to different customers and the same VLAN IDs are not created on the same 3750.

Error Message

1497: Two UNIs are on the same Device: {0} therefore VLAN 2:1 translation cannot be performed.

Explanation Different customers with the duplicate VLAN ID should not undergo translation on the same 3750.

Recommended Action Make sure the Service Requests belonging to different customers and the same VLAN IDs are not created on the same 3750.

Error Message

1497: {0}: ATM Transport Mode should be the same on AttachmentCircuit1(TransportMode={1}) and AttachmentCircuit2(Transport Mode={2} for ATM service.

Explanation Asynchronous Transport Mode (ATM) is not symmetrical across attachment circuit for ATM service.

Recommended Action Transport mode on attachment circuit should be symmetrical for ATM virtual paths (VPs) for ATM virtual circuits (VCs).

Messages 1500-1599 (Repository Messages)

Error Message

1500: Find Exception while getting {0} for {1}

Explanation Cannot find the specified object.

Error Message

1501: Policy Element {0} is not defined in the {1} policy.

Explanation Invalid policy attribute for the policy with the type specified on {1}.

Recommended Action Assign the correct policy attribute to the policy.

Error Message

1502: Policy Element {0} should be type of {1}

Explanation Invalid policy attribute type.

Recommended Action Assign correct data type to that policy element.

Error Message

1521: Vlan Id Pool with range {0}:{1} overlaps with the existing reserved pool with value {2}:{3} on Access Domain with name {4}

Explanation You tried to add a VLAN ID pool that overlaps with the existing reserved VLAN ID pool.

Recommended Action Re-create the VLAN ID pool without overlapping the VLAN ID on the reserved VLAN ID pool.

Error Message

1522: Reserved Vlan Id Pool with range {0}:{1} cannot be reserved on Access Domain with name {2} as Vlan with value {3} is already allocated.

Explanation Reserved VLAN ID with the specified range cannot be added because some of the VLAN IDs have been used.

Recommended Action Redefine the reserved VLAN ID pool range.

Error Message

1523: Vlan ID with value {0} cannot be freed since it is on the reserved vlan pool on Access Domain with name {1}

Explanation A reserved VLAN ID is freed, which is not allowed.

Recommended Action Do not free this VLAN ID or remove this VLAN ID from the reserved VLAN ID pool.

Error Message

1524: Vlan ID with value {0} cannot be allocated as it is on the reserved vlan pool on Access Domain with ID {1}

Explanation A reserved VLAN ID is used, which is not allowed.

Recommended Action Remove this VLAN ID from a reserved VLAN ID pool.

Error Message

1530: Resource pool {0} on {1} object with ID {2} did not exist

Explanation You have not yet created a resource pool.

Recommended Action Create the required resource pools for further operations.

Messages 2000-2099 (API Messages)

Error Message

2000: The following device does not exist: {0}.

Explanation Device {0} does not exist.

Error Message

2001: Task create has failed. Unable to find a reference for {0}.

Explanation Task creation has failed. Unable to find a reference for {0}.

Error Message

2002: Error processing transaction for method: execMethod

Explanation Error processing transaction for method: execMethod.

Error Message

2003: Error occurred configuring Task

Explanation Error occurred configuring task.

Error Message

2005: Incomplete Attributes given. If {0} is given then {1} should also be given for {2}.

Explanation Incomplete Attributes given. If {0} is given then {1} should also be given for {2}.

Error Message

2006: No VC available for {0} with values {1} and {2}.

Explanation No virtual circuit (VC) available for {0} with value {1} and {2}.

Error Message

2007: {0} with value {1} for {2} does not exist.

Explanation {0} with value {1} for {2} does not exist.

Error Message

2008: No VC available of type {0} for {1} {2}.

Explanation No virtual circuit (VC) available of type {0} for {1} {2}.

Error Message

2009: Exec method requires a helper for the following class: {0}.

Explanation Internal error.

Error Message

2010: Exec Method - the target object for the exec method was not found. Expected one object to be returned from the query but got {0} objects back.

Explanation Exec Method - the target object for the exec method was not found. Expected one object to be returned from the query but got {0} objects back.

Error Message

2011: Template Error- A Template Definition Path is required

Explanation Template Error- A Template Definition Path is required.

Error Message

2012: Template Error- A Template Data File is required

Explanation Template Error- A Template Data File is required.

Error Message

2013: Service Requests involving templatedownload are not schedulable.

Explanation Service Requests involving template download cannot be scheduled.

Error Message

2014: Attempting to deploy improperly defined Service Request.

Explanation Attempting to deploy improperly defined Service Request.

Error Message

2015: The interval value {0} interval is missing for PeriodicType {0}.

Explanation The interval value {0} is missing for the periodic type {0}.

Error Message

2016: The periodic type {0} is not properly defined.

Explanation Internal error.

Error Message

2017: The device {0} with interface {1} is not unique or does not exist.

Explanation The device {0} with the interface {1} is not unique or does not exist.

Error Message

2018: The device: {0} with interface: {1} is not unique.

Explanation The device {0} with the interface {1} is not unique.

Error Message

2019: The specified probe does not exist.

Explanation The specified probe does not exist.

Error Message

2020: Criteria does not specify a unique probe.

Explanation The criteria does not specify a unique probe.

Error Message

2021: Attribute {0} for class {1} does not exist.

Explanation Attribute {0} for class {1} does not exist.

Error Message

2022: This request has failed due to an error in the Repository Layer.

Explanation This request has failed due to an error in the Repository Layer.

Error Message

2023: The policy cannot be modified because it is part of an SR.

Explanation The policy cannot be modified because it is part of a Service Request.

Error Message

2024: The template specified by the path: {0} does not exist

Explanation The template specified by the path: {0} does not exist.

Error Message

2025: The variable {0} is required by the Template Definition.

Explanation The variable {0} is required by the template definition.

Error Message

2026: The variable {0} is a duplicate.

Explanation The variable {0} is a duplicate.

Error Message

2027: The data type for variable {0} must be {1}.

Explanation The data type for variable {0} must be {1}.

Error Message

2028: Unsupported Task type {0} encountered.

Explanation Unsupported task type {0} was encountered.

Error Message

2029: Error processing request. Probable cause is entered data.

Explanation Error occurred when processing a request. The probable cause is entered data.

Error Message

2030: The class {0} requires the keyProperty attribute {1}.

Explanation The class {0} requires the keyProperty attribute {1}.

Error Message

2031: This request has failed due to an error in the Repository Layer.

Explanation This request has failed due to an error in the Repository Layer.

Error Message

2032: The input value for variable {0} is less than the specified minimum value: {1}.

Explanation The input value for variable {0} is less than the specified minimum value {1}.

Error Message

2033: The input value for variable {0} is greater than the specified maximum value: {1}.

Explanation The input value for variable {0} is greater than the specified maximum value {1}.

Error Message

2034: The input value String for variable {0} is too short.

Explanation The input value string for variable {0} is too short.

Error Message

2035: The input value String for variable {0} is too long.

Explanation The input value string for variable {0} is too long.

Error Message

2036: The input value for variable {0} does not match the specified pattern.

Explanation The input value for variable {0} does not match the specified pattern.

Error Message

2037: {0} is not a valid IP address.

Explanation {0} is not a valid IP address.

Error Message

2038: {0} is not contained in the list of Available Values: {1}.

Explanation {0} is not contained in the list of available values {1}.

Error Message

2039: {0} is not a valid URL.

Explanation {0} is not a valid URL.

Error Message

2040: No transactions exist upon which to perform a request.

Explanation No transactions exist upon which to perform a request.

Error Message

2041: IP address does not fall under class {0}.

Explanation IP address does not fall under class {0}.

Error Message

2042: API meta data is not available. It is missing or corrupted.

Explanation API meta data is not available. It is missing or corrupted.

Error Message

2043: This task requires at least one Service Request locator ID.

Explanation This task requires at least one Service Request locator ID.

Error Message

2044: Problem encountered creating template variable {0}.

Explanation Problem encountered creating template variable {0}.

Error Message

2045: Template variable name {0} already exists.

Explanation Template variable name {0} already exists.

Recommended Action Check the Request XML file for the proper format of the Template XML element.

Error Message

2047: Template type is unsupported: {0}.

Explanation Template type {0} is unsupported.

Recommended Action Check the Request XML file for the proper format of the Template XML element.

Error Message

2048: Attribute subAction missing for object {0}. This attribute is required for modify request.

Explanation Attribute subAction is missing for object {0}. This attribute is required for the modify request

Recommended Action Check the Request XML file for the proper format of the modifyInstance XML element and the current condition of the database.

Error Message

2049: Template type is unsupported: {0}.

Explanation Template type {0} is unsupported.

Recommended Action Check the Request XML file for the proper format of the Template XML element.

Error Message

2050: Incoming body text is not valid.

Explanation Incoming body text is not valid.

Recommended Action Check the Request XML file for the proper format and existence of the Body XML element.

Error Message

2051: Incoming variable {0} is not part of body text.

Explanation Incoming variable {0} is not part of body text.

Recommended Action Check the Request XML file for the proper format and existence of the Body XML element.

Error Message

2052: Incoming variable {0} is not part of Template Definition.

Explanation Incoming variable {0} is not part of the template definition.

Recommended Action Check the Request XML file for the proper format of the Template XML element.

Error Message

2053: Problem in template data validation.

Explanation Problem in template data validation.

Recommended Action Check the Request XML file for the proper format of the Template XML element.

Error Message

2054: {0} with ID {1} to be deleted or modified does not belong to the SR to be modified.

Explanation The link between network devices designated in the request is not part of the Service Request designated in the request.

Recommended Action Recheck the designated link against those included in the designated Service Request. Then modify the designated link.

Error Message

2056: Attribute {0} for Class {1} has an out of range value of {2}. Allowed range: min {3} - max {4}.

Explanation The value for the given attribute is not within the allowed range of values.

Recommended Action Change the attribute value to be within the allowed range.

Error Message

2057: Expected ServiceRequestDetails object does not exist.

Explanation The Details section of the designated Service Request does not exist.

Recommended Action Recheck that the proper Service Request is designated.

Error Message

2058: Incoming XML does not contain any objects to modify.

Explanation Your modify request contains no objects that can be modified.

Recommended Action Recheck the request for validity.

Error Message

2059: Incoming XML does not identify an existing VRF.

Explanation The incoming request contains a reference to a VRF not found in the database.

Recommended Action Recheck the value for the designated VRF in the request.

Error Message

2060: L2TP_AUTH_PAP or L2TP_AUTH_CHAP cannot be set when L2TP_ENCRYPTION_REQUIRED is set

Explanation An invalid request was made with regards to variable L2TP_ENCRYPTION_REQUIRED.

Recommended Action Either modify the value of L2TP_ENCRYPTION_REQUIRED to set L2TP_AUTH_PAP or L2TP_AUTH_CHAP or avoid attempting to set these values.

Error Message

2061: The name {0} with the value {1} is in an invalid time format. It should be 00:00:00 - 23:59:59.

Explanation The incoming request has a time format that cannot be read by the application.

Recommended Action Change the desired time designation to the required format of HH:MM:SS where: HH is hours (00 - 23), MM is minutes (00 - 59), and SS is seconds (00 - 59).

Error Message

2062: The following column name(s) are not part of this table {0}.

Explanation An error occurred when the request was sent to the database.

Recommended Action Ensure that the designated column name(s) are part of the desired data table in the database.

Error Message

2063: The row number {0} does not exist in this table.

Explanation An error occurred when the request was sent to the database.

Recommended Action Ensure that the designated row number in the request exists in the database.

Error Message

2064: The mandatory filter {0} for report {1} is not defined in requested XML.

Explanation A required filter in the incoming report request is missing.

Recommended Action Include the required filter in the incoming report request.

Error Message

2065: The number of columns {0} returned from the database does not match {1} which is defined in report meta {2}.

Explanation An error exists in the meta file that defines report formats.

Recommended Action Recheck the database and report meta file for compatibility.

Error Message

2066: The substitute set {0} is not found in meta SQL for report {1}.

Explanation A designated name in the incoming report request cannot be properly substituted in the report meta file to produce the proper report.

Recommended Action Recheck the names designated in the incoming report request.

Error Message

2067: The label for parameter {0} is not found in report {1}.

Explanation A designated parameter in an incoming report request cannot be found for the report.

Recommended Action Recheck the values of the parameters in the report request for validity.

Error Message

2068: The sort item {0} is not found in the display parameter list.

Explanation The sort item for the incoming report request is not one of the items that can be displayed in the report output.

Recommended Action Recheck the items in the sort list for validity with respect to the items that can be displayed in a report output.

Error Message

2069: Either simpleHelper or SQL needs to be defined in report meta for report {0}.

Explanation The meta file defining the given report is missing required definitions.

Recommended Action Modify or request a modification to the report meta file to include the required information.

Error Message

2070: The parameter {0} for report {1} cannot only have objectRefParamName. objectRefName is also expected.

Explanation The meta files defining the designated report are missing a required attribute in the XML element for the given parameter.

Recommended Action Modify or request a modification to the report meta file to include the required information.

Error Message

2071: The filter set item {0} for report {1} needs to have paramDef defined.

Explanation One of the items in the filter set of the meta file defining the given report is not properly defined. A paramDef XML element is needed for this item.

Recommended Action Modify or request a modification to the report meta file to include the required information.

Error Message

2072: The SQL in report {0} should not have "order by" clause in it.

Explanation The SQL section of the meta file for the given report contains an "order by" clause that cannot be processed.

Recommended Action Modify or request a modification to the report meta file to make the required change.

Error Message

2073: The SQL in report {0} should not have embedded filter blocks in it.

Explanation The SQL section of the meta file for the given report contains embedded filter blocks that cannot be processed.

Recommended Action Modify or request a modification to the report meta file to make the required change.

Error Message

2074: The SQL in report {0} has multiple filter sets within a set of markers. This is not supported.

Explanation The SQL section of the meta file for the given report contains multiple filter sets that cannot currently be processed.

Recommended Action Verify that the UNI interface is present and re-run the request.

Error Message

2075: UNI Interface {0} not present for provided device ID {1}.

Explanation The UNI interface must exist for this provisioning operation to occur.

Recommended Action Verify that the UNI interface is present and re-run the request.

Error Message

2076: ID should be given for NPC {0}.

Explanation The NPC identification is not correct or recognized by the system.

Recommended Action Verify the NPC and re-run the request.

Error Message

2077: NPC (ID) should be given to derive UNIDeviceInterface ID from NPC source device and given UNIDeviceInterface name {0}.

Explanation In ISC, the UNI device or Named Physical Circuit (NPC) is required to specify the provisioning path. The NPC can be located by the API from the UNIDeviceInterface if it is given.

Recommended Action Verify that the UNIDeviceInterface or NPC is correct and re-run the request.

Error Message

2078: Error retrieving Worker instance.

Explanation Internal error.

Error Message

2079: Please specify a WaitTimeout value or change wait value to false.

Explanation The wait timeout flag is set in the header but no wait time is specified.

Recommended Action Specify a WaitTimeout value or change the wait value to false.

Error Message

2080: The WaitTimeout value of {0} is invalid.

Explanation The wait time out flag is set in the header but no wait time is specified.

Recommended Action Specify a WaitTimeout value or change the wait value to false.

Error Message

2081: Wait time {0} has expired. The job is still being processed by the system. Use status request for job status.

Explanation The wait time out value and flag were set but the request is taking too long to return and hence the timeout has expired.

Recommended Action Increase the WaitTimeout value.

Error Message

2082: Failed locking the device.

Explanation The API has certain operations that use the software lock feature of ISC. The lock could not be acquired.

Recommended Action Retry the request.

Error Message

2083: Failed while waiting for Lock event {0}.

Explanation The API has certain operations that use the software lock feature of ISC. The lock could not be acquired.

Recommended Action Retry the request.

Error Message

2084: There is no job associated with Job ID {0}.

Explanation Internal error.

Error Message

2085: Set items for filter set {1} in report {0} are not all defined in whole filter set.

Explanation The Reports meta data requires a proper filter.

Recommended Action Check the filters in the reports meta for accuracy.

Error Message

2086: Key property {1} is not defined in any filter set for report {0}.

Explanation The reports meta data requires a proper filter using key properties.

Recommended Action Check the filters in the reports meta for accuracy

Error Message

2087: {0} cannot be created or deleted if {1} is disabled. Please remove {0} objects from the request or enable {1}.

Explanation L2 or VPLS repository error due to PORT SECURITY attribute.

Recommended Action Check that the PORT_SECURITY attributes are used correctly.

Error Message

2088: Error creating the Named Physical Circuit

Explanation A general error has occurred when creating the NPC.

Recommended Action Check that the NPC is specified correctly in the input XML.

Error Message

2089: Error creating Named Physical Circuit with ring, check NPC ring used in request for validity

Explanation A general error has occurred when creating the NPC ring.

Recommended Action Check that the NPC ring is specified correctly in the input XML.

Error Message

2091: Object {0} not allowed in {1} L2VpnPolicy Type.

Explanation A general error has occurred when creating the NPC ring.

Recommended Action Check that the NPC is specified correctly in the input XML.

Error Message

2094: Data MDT Size, Data MDT Threshold, and either a CERC or a default CERC must be provided if multicast is enabled.

Explanation The multicast feature requires certain attributes to be set.

Recommended Action Insure that all multicast attributes are set.

Error Message

2096: One or more property list item values passed were invalid: {0} , {1}

Explanation This error message appears when there is an invalid parameter defined for a given report and prints the report name and the invalid parameter.

Recommended Action Enter valid input filter values and regenerate the report.

Error Message

2097: Duplicate LinkTemplate with DatafilePath {0} not allowed for logical device {1}.

Explanation A unique template name or path must be specified.

Recommended Action Correct the template name or path.

Error Message

2098: VPN_POLICY_MISMATCH

Explanation Using {0} type VPN with {1} type VPLS Policy for Service Request creation is not allowed.

Recommended Action Correct the input.

Error Message

2099: CUSTOMER_PROVIDER_EXCLUSIVE

Explanation A variable can belong to either the Organization or the Provider, but both were found in the request.

Recommended Action Remove either the Organization or the Provider, because both cannot exist in the request.

Messages 2100-2199 (API Messages)

Error Message

2100: Given UNIDeviceInterface {0} not present in the PE device {1}.

Explanation In ISC, the PE UNI interface is required to specify the provisioning path.

Recommended Action Verify that the PE UNI interface is correct and re-run the request.

Error Message

2101: NPC (ID) or PE should be given to derive UNIDeviceInterface ID from given UNIDeviceInterface name {0}.

Explanation The NPC identification is not correct or recognized by the system.

Recommended Action Verify the NPC and re-run the request.

Messages 5000 - 6550 (Discovery Messages)

Error Message

5001: Invalid parameter: {0}

Explanation An invalid argument was passed to a method. This is a runtime error.

Recommended Action Contact ISC support.

Error Message

5002: {0}

Explanation Generic error message.

Recommended Action The actual error sent by the module that had the exception is also shown. Perform the recommended action for that error.

Error Message

5003: IO error: {0}

Explanation An I/O error occurred. This message contains the actual message sent by the JVM.

Recommended Action The actual error sent by the module that had the exception is also shown. Perform the recommended action for that error.

Error Message

5004: File IO error: {0}

Explanation Indicates a file I/O error sent by the JVM. Possible causes could be that the file was not found or did not have sufficient permissions to either read or write. The message contains the actual error message thrown by the JVM.

Recommended Action The actual error sent by the module that had the exception is also shown. Perform the recommended action for that error.

Error Message

5005: An unrecoverable error occurred while performing an operation. Cannot continue. You must fix the error before continuing with discovery. Cause: {0}

Explanation An unrecoverable error has occurred. You cannot continue with the discovery operation until the error is fixed. Causes might vary. The actual error message is shown.

Recommended Action The actual error sent by the module that had the exception is also shown. Perform the recommended action for that error.

Error Message

5006: Cannot find class {0}.

Explanation A required class is not found in the classpath. This is a runtime error.

Recommended Action Contact ISC support.

Error Message

5007: Unable to instantiate the class {0} due to insufficient access to the constructor of the class. Check the log files for more detail.

Explanation This is a runtime error. The constructor of the class being instantiated does not have the required access permission.

Recommended Action Contact ISC support.

Error Message

5008: Unable to instantiate the class {0}. Check to make sure that the class is not an abstract class, not an interface, and has a default constructor. Check the log files for more detail.

Explanation This is a runtime error. Unable to create a class.

Recommended Action Contact ISC support.

Error Message

5009: Null {0} argument passed to {1}.

Explanation This is a runtime error. A null argument was passed to a method where a non-null argument was expected.

Recommended Action Contact ISC support.

Error Message

5010: File not found. {0}.

Explanation The file does not exist.

Recommended Action Make sure the file exists and has proper permissions. If the file does not exist, create it.

Error Message

5011: Cannot read file {0}. Permission denied.

Explanation The file does not have read permissions.

Recommended Action Change the permissions on the file.

Error Message

5101: Database query failed. Cause: {0}

Explanation A database query failed. The actual error message is appended to this message.

Recommended Action The actual error sent by the module that had the exception is also shown. Perform the recommended action for that error.

Error Message

5102: The object {0} cannot be persisted because its parent object {1} is not in the database.

Explanation This is a programming error. The parent object of the object being saved to the repository does not exist in the repository.

Recommended Action Contact ISC support.

Error Message

5201: A discovery request exists in the database. Only one discovery request can exist in the database.

Explanation Only one discovery request can be created. The GUI should make sure that you cannot create more than one discovery request in an ISC repository.

Recommended Action Contact ISC support.

Error Message

5202: The workflow cannot be committed. It needs a discovery request parent. Please associate the workflow with a discovery request and then process with the commit.

Explanation The discovery workflow object cannot be saved to the repository before saving the discovery request to the repository. The GUI makes sure that the discovery request is saved before saving the workflow.

Recommended Action Contact ISC support.

Error Message

5203: The workflow cannot be deleted. It is associated with a discovery request. To delete the workflow, the associated discovery request must be deleted.

Explanation The discovery workflow cannot be deleted because the parent discovery request exists. This is an API level error. Currently there is no support for deleting a discovery workflow.

Recommended Action Contact ISC support.

Error Message

5204: Unable to load the workflow steps for the workflow {0} due to an error condition while executing the database query. Check the logs for more details.

Explanation A low level database query failed. The log does not show the actual error message sent by the database API.

Recommended Action The actual error sent by the module that had the exception is also shown. Perform the recommended action for that error.

Error Message

5205: Unable to fetch the workflow step with ID {0} from database either due to a database problem or invalid query. Check the logs for more details.

Explanation A low level database query failed. The log shows the actual error message sent by the database API.

Recommended Action The actual error sent by the module that had the exception is also shown. Perform the recommended action for that error.

Error Message

5206: The step already exists in the workflow.

Explanation The workflow step being created already exists in the repository. The GUI should handle the error.

Recommended Action Contact ISC support.

Error Message

5207: The workflow step cannot be committed. It needs a workflow parent. Please associate the workflow step with a workflow and then process with the commit.

Explanation This is a programming error. The GUI handles the error.

Recommended Action Contact ISC support.

Error Message

5208: The workflow step cannot be deleted. It is associated with a workflow.

Explanation An attempt to delete the step failed because the parent object exists in the repository. Currently there is no support for deleting workflow steps from the GUI.

Recommended Action Contact ISC support.

Error Message

5209: Unable to fetch the input parameters for workflow step input {0} from the database, either due to a database problem or invalid query. Check the logs for more details.

Explanation Unable to fetch records from the database.

Recommended Action Check whether the database server is running or if the record exists in the database. The log contains the actual error message returned by the database server.

Error Message

5210: Unable to fetch the input parameter values for workflow step input {0} from the database, either due to a database problem or invalid query. Check the logs for more details.

Explanation Unable to fetch records from the database.

Recommended Action Check if the database server is running or if the record exists in the database. The log contains the actual error message returned by the database server.

Error Message

5451: Cannot find the data.

Explanation The data returned from the database query is empty.

Recommended Action No data is present in the database for this query.

Error Message

5452: The data is not unique

Explanation The data returned from the query is not unique.

Recommended Action Check if the data is supposed to be unique or if the database has duplicate data, which is not supposed to occur.

Error Message

5453: A FindException is thrown.

Explanation A find exception occurred when the database was queried.

Recommended Action Check if the database server is running or if the record exists in the database. The log contains the actual error message returned by the database server.

Error Message

5454: Cannot update record.

Explanation The specific record cannot be updated.

Recommended Action Check if the database server is running or if the record exists in the database. The log contains the actual error message returned by the database server.

Error Message

5455: Cannot group a partial mesh VPN.

Explanation You cannot group a set of VPNs that contains partial mesh VPN(s).

Recommended Action Remove the partial mesh VPN(s) from the list to be grouped.

Error Message

5456: An error occurs while reading or writing to repository.

Explanation An error occurred when reading or writing to the repository.

Recommended Action Check if the database server is running or if the record exists in the database. The log contains the actual error message returned by the database server.

Error Message

5457: A full mesh or hub-and-spoke VPN cannot be split.

Explanation You cannot split a full mesh or hub-and-spoke VPN.

Recommended Action Correct the error and redo the split.

Error Message

5458: IP address is missing from the interface.

Explanation The interface must have a valid IP address.

Recommended Action Assign an IP address to this interface.

Error Message

5459: Invalid IP address.

Explanation The format of the IP address is not correct.

Recommended Action Correct the error by giving a valid IP address.

Error Message

5651: Cannot continue to run the workflow. The current step is a failed state.

Explanation Cannot proceed with discovery. One of the discovery steps has failed.

Recommended Action Fix the error and restart discovery.

Error Message

5652: Cannot continue to run the workflow. No more steps to execute.

Explanation Cannot proceed with discovery because all the steps are complete. The GUI should handle the error.

Recommended Action Contact ISC support.

Error Message

5653: A runner class name not found for the step {0}.

Explanation Required information to create the step was not provided. The GUI should handle the error.

Recommended Action Contact ISC support.

Error Message

5654: The runner class {0} for the step {1} not found.

Explanation Could not load the required class. This is an installation error.

Recommended Action Contact ISC Support.

Error Message

5655: The runner class {0} for the step {1} does not implement the IWorkflowStepRunner interface.

Explanation This is a programming error and should not occur.

Recommended Action Contact ISC support.

Error Message

5656: Unable to run the workflow with ID {0}. Cause: {1}

Explanation An unknown error occurred during discovery. The log files might contain additional information regarding the actual cause of the problem.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5657: Could not find a workflow with ID {0} in the repository.

Explanation The required record was not found in the repository or could not be read.

Recommended Action Make sure the database server is running. Contact ISC support.

Error Message

5658: Invalid or no action found for state {0} of step {1}.

Explanation This is a programming error and should not occur.

Recommended Action Contact ISC support.

Error Message

5659: An error occurred while updating the workflow {0} due to a database related problem. This might have caused the workflow to be in an inconsistent state. Please fix the problem before continuing with the workflow execution. Check the error log for more details.

Explanation An error occurred during the discovery process and the rest of discovery cannot proceed. The log files contain the actual error.

Recommended Action Fix the error and restart discovery.

Error Message

5660: An error occurred while refreshing the updated workflow {0} during execution. The current handle to the workflow object might be stale. Client code should refresh the workflow instance from the repository before continuing to run the workflow. Check the error log for more details.

Explanation An error occurred while updating the workflow record. The log files contain the actual error.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5661: An error occurred while committing the state transition of the workflow step {0} due to a database related problem. This might have caused the workflow to be in an inconsistent state. Please fix the problem before continuing with the workflow execution. Check the error log for more details.

Explanation An error occurred while updating the state transitions of a discovery step. The log files contain the actual error.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5662: An error occurred while updating the state of the workflow {0} due to a database related problem. This might have caused the workflow to be in an inconsistent state. Please fix the problem before continuing with the workflow execution. Check the error log for more details.

Explanation An error occurred while updating the workflow record. The log files contain the actual error.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5663: An error occurred while refreshing the updated workflow step {0} during execution. The current handle to the workflow step object might be stale. Client code should refresh the workflow instance from the repository before continuing to run the workflow. Check the error log for more details.

Explanation An error occurred while updating the workflow step record. The log files contain the actual error.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5664: A repository error occurred while trying to get the workflow from the database.

Explanation An error occurred while reading the workflow record. The log files contain the actual error.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5665: Unknown action - {0}.

Explanation This is a programming error. An unknown action was sent to the workflow state machine.

Recommended Action Contact ISC support.

Error Message

5666: Invalid response received from the runner for the action request. Expected Response: {0} Received Response: {1}

Explanation This is a programming error. An invalid response was generated by the workflow step runner.

Recommended Action Contact ISC support.

Error Message

5667: The step input parameter {0} is missing.

Explanation This is a programming error. The required input parameter is missing. The GUI should handle the error.

Recommended Action Contact ISC support.

Error Message

5668: Invalid value {0} for step input parameter {1}.

Explanation The value of the input parameter is invalid. The GUI handles the error.

Recommended Action Contact ISC support.

Error Message

5669: There are unhandled errors that occurred during the previous run of the workflow {0}. Please fix those errors before continuing.

Explanation This is a generic error message when an unknown error occurred during discovery. The actual error message sent by the underlying discovery component is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5751: Config file location {0} exists and is not a directory.

Explanation The location where the configuration files are to be stored already exists and is not a directory.

Recommended Action Make sure that the location is a directory or change the configuration file location in DCPL.

Error Message

5752: Could not create the config directory {0}. Check if the parent directory has write permissions.

Explanation Unable to create the directory where the configuration files are to be stored.

Recommended Action Make sure there are sufficient write permissions to create the directory.

Error Message

5753: Unsupported device type - {0}.

Explanation The device is not supported.

Recommended Action Contact ISC support.

Error Message

5754: The device helper factory class {0} name not found for the device type {1}.

Explanation The required factory class is not found in the path.

Recommended Action This is an installation problem. Contact ISC support.

Error Message

5755: An error occurred while setting up DCS helpers for the device {0}.

Explanation Errors occurred while setting up the device configuration services module. The actual error message returned by DCS is logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5756: An error occurred while trying to uploading the running configuration of the device {0}. Cause: {1}

Explanation Errors occurred while uploading the device configuration.

Recommended Action Check whether the device is accessible. The actual error message returned by DCS appears.

Error Message

5757: An error occurred while trying to save the running configuration of the device {0}.

Explanation An error occurred while saving the running configuration to a file.

Recommended Action Check whether there are sufficient write permissions to create the file.

Error Message

5758: IE2100 associated with device {0} not defined.

Explanation IE2100 definitions were not provided.

Recommended Action Using the device editor, provide the required information.

Error Message

5759: Error while initializing the NOM network factory.

Explanation An error occurred while initializing the NOM module.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5760: Invalid configuration handler class specified - {0}.

Explanation An invalid configuration handler module was specified. This is a programming error.

Recommended Action Contact ISC support.

Error Message

5761: Log file location {0} exists and is not a directory.

Explanation The given location where the log files are to be stored already exists and is not a directory.

Recommended Action Make sure the location is a directory or change the log file location in the Dynamic Components Property Library (DCPL).

Error Message

5762: Could not create the log directory {0}. Check if the parent directory has write permissions.

Explanation Unable to create the directory where the log files are to be stored.

Recommended Action Make sure that there are sufficient write permissions to create the directory.

Error Message

5851: An error occurred while creating the device/service model objects in the ISC repository.

Explanation An error occurred while creating service model objects in the repository. The actual error returned by the repository is displayed in the log.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5852: Unable to create provider from the XML definitions. Missing required attributes "Name" and "AS Number".

Explanation The required provider-name and as-number tags were not specified in the inventory XML definition file.

Recommended Action Edit the inventory XML definitions and specify the required definitions.

Error Message

5853: Unable to create provider from the XML definitions. Missing required attribute "Name".

Explanation Unable to create the provider. The required provider name parameter is missing. The XML definitions should have been validated earlier, and if the provider name was missing, error message 5852 is returned.

Recommended Action Edit the inventory XML definition and specify the provider name.

Error Message

5854: Unable to create provider from the XML definitions. Missing required attribute "As Number".

Explanation Unable to create the provider. The required provider AS number parameter is missing. The XML definitions should have been validated earlier, and if the provider AS number was missing, error message 5852 is returned.

Recommended Action Edit the inventory XML definition and specify the provider AS number.

Error Message

5855: Unable to create provider from the XML definitions. Invalid "AS Number" - {0}. Please give a valid AS number in the range 1 - 65535.

Explanation Unable to create a provider because the given AS number is not in the valid range.

Recommended Action Edit the inventory XML definitions and provide an AS number in the range 1-65535.

Error Message

5856: An error occurred while creating provider from XML definitions. {0}.

Explanation This is a generic error message written to the log file if any repository related errors occurred while creating the provider. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5857: Unable to create region from the XML definitions. Missing required attribute "Name".

Explanation Unable to create the object. The required tags were not specified in the inventory XML definition file.

Recommended Action Edit the inventory XML definitions and specify the required attributes.

Error Message

5859: An error occurred while creating region from XML definitions. {0}.

Explanation This is a generic error message written to the log file if any repository-related errors occurred while creating the region. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5860: Unable to create customer from the XML definitions. Missing required attribute "Name".

Explanation Unable to create the customer. The required customer-name tag was not specified in the inventory XML definition file.

Recommended Action Edit the inventory XML definitions and specify the required definitions.

Error Message

5862: An error occurred while creating customer from XML definitions. {0}.

Explanation This is a generic error message written to the log file if any repository-related errors occurred while creating the customer. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5863: Unable to create site from the XML definitions. Missing required attribute "Name".

Explanation Unable to create the site. The required site-name tag was not specified in the inventory XML definition file.

Recommended Action Edit the inventory XML definitions and specify the required definitions.

Error Message

5865: An error occurred while creating site from XML definitions. {0}.

Explanation This is a generic error message written to the log file if any repository-related errors occurred while creating the site. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5866: Error in creating prover {0}.

Explanation An error occurred while creating the provider. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5867: Error in creating providers.

Explanation An error occurred while creating providers. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5868: Error in adding region {0} to provider {1}.

Explanation An error occurred while adding the region to the provider. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5869: Error in adding regions to provider {0}.

Explanation An error occurred while adding regions to the provider. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5870: Error in adding PE {0} to region {1}.

Explanation An error occurred while adding the PE to the region. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5871: Error in adding PEs to region {0}.

Explanation An error occurred while adding PEs to the region. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5872: Error in creating customer {0}.

Explanation An error occurred while creating the customer. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5873: Error in creating customers.

Explanation An error occurred while creating customers. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5874: Error in adding site {0} to customer {1}.

Explanation An error occurred while adding the site to the customer. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5875: Error in adding sites to customer {0}.

Explanation An error occurred while adding sites to the customer. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5876: Error in adding CPE {0} to site {1}.

Explanation An error occurred while adding the CPE to the customer site. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5877: Error in adding CPEs to site {0}.

Explanation An error occurred while adding CPEs to the customer site. The actual error message returned by the repository API is also logged.

Recommended Action The actual error sent by the module with the exception also appears. Perform the recommended action for that error.

Error Message

5878: The class with name {0} given in the "classname" attribute of the "match" condition tag not found.

Explanation This is a runtime error. The given class is not found in the classpath.

Recommended Action Contact ISC support.

Error Message

5879: The class {0} does not implement the required IMatch interface.

Explanation This is a runtime error. The class does not implement the required IMatch interface.

Recommended Action Contact ISC support.

Error Message

5880: The required attribute "key" for the match condition is missing in the XML rule definition.

Explanation The required attribute with the name "key" is missing.

Recommended Action Edit the rules XML and provide the required attribute.

Error Message

5881: The required attribute "value" for the match condition is missing in the XML rule definition.

Explanation The required attribute "value" is missing.

Recommended Action Edit the rules XML and provide the required attribute.

Error Message

5882: Error in XML rule definition. Invalid attribute "matchType" for the match condition - {0}.

Explanation The "matchType" attribute for the action is invalid.

Recommended Action Edit the rules XML and provide a valid match type for the action.

Error Message

5883: Error in XML rule definition. Missing children for a condition tag. A condition tag should have a MATCH, OR, NOT or OR child.

Explanation The required child tag for the condition is missing in the rules XML.

Recommended Action Edit the rules XML and provide the required tag definitions.

Error Message

5884: Error in XML rule definition. Missing children for an AND condition tag. An AND condition tag should have at least one MATCH, OR, NOT, or OR condition child.

Explanation The required child tag for the condition is missing in the rules XML.

Recommended Action Edit the rules XML and provide the required tag definitions.

Error Message

5885: Error in XML rule definition. Missing children for an OR condition tag. An OR condition tag should have at least one MATCH, OR, NOT, or OR condition child.

Explanation The required child tag for the condition is missing in the rules XML.

Recommended Action Edit the rules XML and provide the required tag definitions.

Error Message

5886: Error in XML rule definition. Missing children for a NOT condition tag. A NOT condition tag should have a MATCH, OR, or OR child.

Explanation The required child tag for the condition is missing in the rules XML.

Recommended Action Edit the rules XML and provide the required tag definitions.

Error Message

5887: Error in XML rule definition. Missing child node for an action tag. An action tag should have a create-pe or create-cpe child.

Explanation The required child tag for the action is missing in the rules XML.

Recommended Action Edit the rules XML and provide the required tag definitions.

Error Message

5888: The required attribute "customerName" for the create-cpe action is missing in the XML rule definition.

Explanation The required attribute customerName is missing.

Recommended Action Edit the rules XML and provide the required attribute.

Error Message

5889: The required attribute "siteName" for the create-cpe action is missing in the XML rule definition.

Explanation The required attribute siteName is missing.

Recommended Action Edit the rules XML and provide the required attribute.

Error Message

5890: The required attribute "managementType" for the create-cpe action is missing in the XML rule definition.

Explanation The required attribute managementType is missing.

Recommended Action Edit the rules XML and provide the required attribute.

Error Message

5891: Error in XML rule definition. Invalid attribute "managementType" for the create-cpe action - {0}.

Explanation The managementType attribute for the CPE is invalid.

Recommended Action Edit the rules XML and provide a valid management type for the CPE.

Error Message

5892: The required attribute "providerName" for the create-pe action is missing in the XML rule definition.

Explanation The required attribute providerName is missing.

Recommended Action Edit the rules XML and provide the required attribute.

Error Message

5893: The required attribute "regionName" for the create-pe action is missing in the XML rule definition.

Explanation The required attribute regionName is missing.

Recommended Action Edit the rules XML and provide the required attribute.

Error Message

5894: The required attribute "role" for the create-pe action is missing in the XML rule definition.

Explanation The required attribute "role" is missing.

Recommended Action Edit the rules XML and provide the required attribute.

Error Message

5895: Error in XML rule definition. Invalid attribute "role" for the create-pe action - {0}.

Explanation The role attribute for the PE is invalid.

Recommended Action Edit the rules XML and provide a valid role for the PE.

Error Message

5896: Error in XML rule definition. Missing child node for a "rule" tag. A "rule" tag should have a "action" child.

Explanation The required "action" tag for the rule is missing in the rules XML.

Recommended Action Edit the rules XML and provide the required tag definitions.

Error Message

5897: Inventory XML file not found - {0}. Please make sure that the file exists and has sufficient read permissions.

Explanation The inventory XML file specified in the discovery input page does not exist.

Recommended Action Make sure the file exists and has the right read permissions. If the file does not exist, create it.

Error Message

5898: Rules XML file not found - {0}. Please make sure that the file exists and has sufficient read permissions.

Explanation The rules XML file specified in the discovery input page does not exist.

Recommended Action Make sure the file exists and has the correct read permissions. If the file does not exist, create it.

Error Message

6053: The device discovery engine class {0} was not found.

Explanation The required discovery engine class was not found.

Recommended Action Contact ISC support.

Error Message

6054: The discovery engine class {0} does not implement the IDeviceDiscoveryEngine interface.

Explanation The discovery engine class does not implement the required interfaces.

Recommended Action Contact ISC support.

Error Message

6055: An I/O error occurred when reading file {0} or the file is not present.

Explanation The given file does not exist or could not be read.

Recommended Action Make sure the given file name and path are correct and that the file has sufficient read permission.

Error Message

6056: Unable to create DocumentBuilder.

Explanation Not able to create DocumentBuilder for reading XML files.

Recommended Action Contact ISC support.

Error Message

6057: Failed to parse file {0}.

Explanation Unable to parse the XML file.

Recommended Action Make sure the file has proper XML format.

Error Message

6058: Unable to load a class.

Explanation The required class could not be loaded by the class loader.

Recommended Action Contact ISC support.

Error Message

6059: Method {1} not found in class {0}.

Explanation The required method was not found in the class.

Recommended Action Contact ISC support.

Error Message

6060: Device Type {0} for Device {1} is not supported.

Explanation The given device type is not supported by this discovery.

Recommended Action Remove the device for the device XML file.

Error Message

6061: Device XML file not found - {0}. Please make sure that the file exists and has sufficient read permissions.

Explanation The device XML file specified in the discovery input page does not exist.

Recommended Action Make sure that the files exists and has the correct read permissions. If the file does not exist, create it.

Error Message

6062: Topology XML file not found - {0}. Please make sure that the file exists and has sufficient read permissions.

Explanation The topology XML file specified in the discovery input page does not exist.

Recommended Action Make sure that the files exists and has the correct read permissions. If the file does not exist, create it.

Error Message

6063: AD_HOME environment variable is not set yet. Please restart the server and try again. If the problem still exists, contact the Cisco ISC team.

Explanation The required environment is not set.

Recommended Action Make sure that the AD_HOME property is set in the vpnenv.(c)sh file. Stop the server. Run vpnenv.(c)sh and start the server. If the problem still exists, contact the Cisco ISC team.

Error Message

6064: LD_LIBRARY_PATH is not set yet. Please restart the server and try again. If the problem still exists, contact the Cisco ISC team.

Explanation The required environment is not set.

Recommended Action Make sure that the LD_LIBRARY_PATH property is set in the vpnenv.(c)sh file. Stop the server. Run vpnenv.(c)sh and start the server. If the problem still exists, contact the Cisco ISC team.

Error Message

6065: Discovery process failed to start. Another instance is already running. Please change the TIBCO port in vpnsc.properties and restart the server.

Explanation Another process might have taken the TIBCO port, so discovery server cannot be started.

Recommended Action Change the TIBCO port number by using the idle port. Stop the server and then start the server. If the problem still exists, contact Cisco ISC team.

Error Message

6151: Unable to find management CE in repository

Explanation Cannot proceed with management VPN discovery. No management CPE defined in ISC repository.

Recommended Action Fix the error and restart VPN discovery.

Error Message

6152: Error from repository - {0}

Explanation Cannot proceed with VPN discovery. ISC repository has an exception.

Recommended Action Fix the error stated in the exception and restart VPN discovery.

Error Message

6153: Error from find query - {0}

Explanation Cannot proceed with VPN discovery. ISC repository unable to find object in the query.

Recommended Action Fix the error and restart VPN discovery.

Error Message

6154: Error in management VPN discovery - {0}

Explanation Cannot proceed with management VPN discovery.

Recommended Action Fix the error and restart VPN discovery.

Error Message

6155: Device discovery failed to populate [{0}] IP address.

Explanation Cannot proceed with VPN discovery. The device discovery did not populate the required IP address.

Recommended Action Fix the error and restart VPN discovery.

Messages Without Numbers (L2TPv3, L2VPN, MPLS, RBAC, and VPLS messages)

The messages in this section are listed alphabetically within the subsections. These messages can appear in two places, the Service Request details screen and the task log screen.

In a Service Request details screen, a device name is associated with the error message. For example: [mlsw1] Provisioning Failures, [cannot config trunk port on an access port without native VLAN defined]

In the task log screen, other information is provided. For example:

Date                          Level       Component                                   Message

2004-01-27 12:52:24 SEVERE Provisioning Engine Engine Error: cannot config trunk port on an access port without native VLAN defined functionElement: AttachmentCircuit provisioning deviceElement: Device configElement: Ether_Layers context: E2E, ID: 7

The messages are listed in the following subsections:

Messages—L2TPv3

Messages—L2VPN Only

Messages—L2VPN and VPLS Only

Messages—L2VPN, VPLS, and MPLS (multi-hop)

Messages—MPLS Only

Messages—RBAC Only

Messages—L2TPv3

Error Message

AC is starting with U-PE for ATM/FR no CE case.

Subject: L2TPv3 Service Editor

Explanation Trying to start a connection with a device with a U-PE type.

Recommended Action Use a device with the type of either CE or N-PE.

Error Message

CE DLCI must be from 16 to 1007

Subject: L2TPv3 Service Editor

Explanation The value of the DLCI field for CE is not in the required range.

Recommended Action Enter a numeric value in the range 16 to 1007 for CE DLCI.

Error Message

CE VCD must be from 1 to 4294967295

Subject: L2TPv3 Service Editor

Explanation The value of the virtual circuity descriptor (VCD) field for CE is not in the required range.

Recommended Action Enter a numeric value in the range 1 to 4294967295 for CE VCD.

Error Message

CE VCI must be from 33 to 65525

Subject: L2TPv3 Service Editor

Explanation The value of the virtual channel identifier (VCI) field for CE is not in the required range

Recommended Action Enter a numeric value in the range 33 to 65525 for CE VCI.

Error Message

CE VPI must be from 0 to 255

Subject: L2TPv3 Service Editor

Explanation The value of the virtual path identifier (VPI) field for CE is not in the required range.

Recommended Action Enter a numeric value in the range 0 to 255 for CE VPI.

Error Message

Device is not selected in AC

Subject: L2TPv3 Service Editor

Explanation An attempt was made to save the attachment circuit without selecting a device.

Recommended Action Select a device and then save.

Error Message

Device selected is a U-PE and no NPC is found.

Subject: L2TPv3 Service Editor

Explanation Trying to start a connection with a device with a U-PE type.

Recommended Action Use a device with the type of either CE or N-PE.

Error Message

Did you forget to select a VPN?

Subject: L2TPv3 Service Editor

Explanation A valid VPN was not selected.

Recommended Action Select a valid VPN before saving the Service Request.

Error Message

Interface is not selected in AC

Subject: L2TPv3 Service Editor

Explanation A UNI interface was not selected when creating an AC.

Recommended Action Select a UNI interface when creating an AC.

Error Message

Invalid value for "Max Path MTU for Session". Please enter a numeric value in the range 68 to 65535.

Subject: L2TPv3 Policy Editor

Explanation The value for the Max Path MTU field is not in the required range.

Recommended Action Enter a numeric value in the range 68 to 65535.

Error Message

Invalid value for "Sequencing". Please select a valid value for "Sequencing" IP parameter from the list.

Subject: L2TPv3 Policy Editor

Explanation A valid value for the Sequencing field is not selected.

Recommended Action Select a valid value for the Sequencing IP parameter from the list.

Error Message

Invalid value for Set Don't Fragment Bit. Please select a valid value from the list.

Subject: L2TPv3 Policy Editor

Explanation A valid value for the Set Don't Fragment Bit field is not selected.

Recommended Action Select a valid value from the list.

Error Message

Invalid value for "Time To Live". Please enter a numeric value in the range 1 to 255.

Subject: L2TPv3 Policy Editor

Explanation The value for the Time to Live field is not in the required range.

Recommended Action Enter a numeric value in the range 1 to 255.

Error Message

Invalid value for "Type of Service". Please enter a numeric value in the range 0 to 255.

Subject: L2TPv3 Policy Editor

Explanation The value for the Type of Service field is not in the required range.

Recommended Action Enter a numeric value in the range 0 to 255.

Error Message

Local Cookie High Value must be from 0 to 4294967295

Subject: L2TPv3 Service Editor

Explanation The value of the Local Cookie High Value field is not in the required range.

Recommended Action Enter a numeric value in the range 0 to 4294967295 for the Local Cookie High Value.

Error Message

Local Cookie Low Value must be from 0 to 4294967295

Subject: L2TPv3 Service Editor

Explanation The value of the Local Cookie Low Value field is not in the required range.

Recommended Action Enter a numeric value in the range 0 to 4294967295 for the Local Cookie Low Value.

Error Message

Local Session ID must be from 0 to 65535

Subject: L2TPv3 Service Editor

Explanation The value of the Local Session ID field is not in the required range.

Recommended Action Enter a numeric value in the range 0 to 65535 for the Local Session ID.

Error Message

Max Path MTU must be from 68 to 65535

Subject: L2TPv3 Service Editor

Explanation The value of the Max Path MTU field is not in the required range.

Recommended Action Enter a numeric value in the range 68 to 65535 for Max Path MTU.

Error Message

No NPC found for AC starting with CPE

Subject: L2TPv3 Service Editor

Explanation No NPC is pre-defined for this CE.

Recommended Action Create the NPC first.

Error Message

PE DLCI must be from 16 to 1007

Subject: L2TPv3 Service Editor

Explanation The value of the DLCI field for PE is not in the required range.

Recommended Action Enter a numeric value in the range 16 to 1007 for PE DLCI.

Error Message

PE VCD must be from 1 to 4294967295

Subject: L2TPv3 Service Editor

Explanation The value of the virtual circuity descriptor (VCD) field for PE is not in the required range.

Recommended Action Enter a numeric value in the range 1 to 4294967295 for PE VCD.

Error Message

PE VCI must be from 33 to 65525

Subject: L2TPv3 Service Editor

Explanation The value of the virtual channel identifier (VCI) field for PE is not in the required range.

Recommended Action Enter a numeric value in the range 33 to 65525 for PE VCI.

Error Message

PE VPI must be from 0 to 255

Subject: L2TPv3 Service Editor

Explanation The value of the virtual path identifier (VPI) field for PE is not in the required range.

Recommended Action Enter a numeric value in the range 0 to 255 for PE VPI.

Error Message

Please enter a valid VLAN ID.

Subject: L2TPv3 Service Editor

Explanation A value for VLAN ID was not entered.

Recommended Action Enter a valid VLAN ID.

Error Message

Please enter a value for Local Session ID

Subject: L2TPv3 Service Editor

Explanation A value was not entered for Local Session ID.

Recommended Action Enter a numeric value in the range 0-65535 for the Local Session ID.

Error Message

Please select a policy to proceed.

Subject: L2TPv3 Service Editor

Explanation A valid policy was not selected.

Recommended Action Select a valid policy from the list.

Error Message

Please select at least one EndToEndWire

Subject: L2TPv3 Service Editor

Explanation No End to End wire was selected.

Recommended Action Add at least one End to End wire.

Error Message

Please select at least two tunnels.

Subject: L2TPv3 Service Editor

Explanation When creating a Service Request, you need to create at least two sessions before trying to save the Service Request.

Recommended Action Add at least two tunnels (sessions).

Error Message

Please select one AC as a Hub AC

Subject: L2TPv3 Service Editor

Explanation In a Hub/Spoke topology, no AC was selected as a hub.

Recommended Action Select one AC as a hub.

Error Message

Policy name not specified. Please enter a name for the L2VPN policy.

Subject: L2TPv3 Policy Editor

Explanation A valid value for a Policy Name is not entered in the GUI.

Recommended Action Enter a valid name for the policy being created.

Error Message

Policy owner not specified. Please select an owner for this policy

Subject: L2TPv3 Policy Editor

Explanation A Policy Owner Type is either a Customer or a Provider and a valid owner is not selected.

Recommended Action Either change the Policy Owner Type to Global Policy or select an owner for this policy.

Error Message

The value of "Max Path MTU for Session" is not specified. Please select a numeric value in the range 68 to 65535.

Subject: L2TPv3 Policy Editor

Explanation The Max Path MTU field is empty.

Recommended Action Enter a numeric value in the range 68 to 65535.

Error Message

The value of "Sequencing" is not specified. Please select a value for "Sequencing" IP parameter from the list.

Subject: L2TPv3 Policy Editor

Explanation The Sequencing field is empty.

Recommended Action Select a value for the Sequencing IP parameter from the list.

Error Message

The value of "Set Don't Fragment Bit" is not specified. Please select a value from the list.

Subject: L2TPv3 Policy Editor

Explanation The Set Don't Fragment Bit field is empty.

Recommended Action Select a value from the list.

Error Message

The value of Time To Live is not specified. Please select a numeric value in the range 1 to 255.

Subject: L2TPv3 Policy Editor

Explanation The Time To Live field is empty.

Recommended Action Enter a numeric value in the range 1 to 255.

Error Message

The value of Type Of Service is not specified. Please select a numeric value in the range 0 to 255.

Subject: L2TPv3 Policy Editor

Explanation The Type of Service field is empty. Note that 0 means reflection, getting the TOS value from the tunnelled IP product.

Recommended Action Enter a numeric value in the range 0 to 255.

Error Message

Time to Live must be from 1 to 255

Subject: L2TPv3 Service Editor

Explanation The value of the Time to Live field is not in the required range.

Recommended Action Enter a numeric value in the range 1 to 255 for Time to Live.

Error Message

Type of Service must be from 0 to 255

Subject: L2TPv3 Service Editor

Explanation The value of the Type of Service field is not in the required range.

Recommended Action Enter a numeric value in the range 0 to 255 for Type of Service.

Messages—L2VPN Only

Error Message

ATM AAL0 is for PE encap only

Subject: AnyTransportOverMPLS (ATOM)

Explanation For L2VPN ATMoMPLS, AAL0 encapsulation is only for a PE.

Recommended Action Change to AAL5 for CEs.

Error Message

ATM CE encap mismatch (both CE have to be the same AAL5 subtype)

Subject: AnyTransportOverMPLS (ATOM)

Explanation For L2VPN ATMoMPLS, encapsulation on both CEs must match.

Recommended Action Modify encapsulation of CEs.

Error Message

ATM VCD cannot be zero

Subject: AnyTransportOverMPLS (ATOM)

Explanation For L2VPN ATMoMPLS, virtual circuity descriptor (VCD) cannot have a zero value.

Recommended Action Modify VCD.

Error Message

ATM VPI and VCI cannot both be zero

Subject: AnyTransportOverMPLS (ATOM)

Explanation For L2VPN ATMoMPLS, Virtual Path Identifier (VPI) and virtual channel identifier (VCI) cannot both be zero.

Recommended Action Modify VPI or VCI.

Error Message

peerRouterId (PE loopback) is missing

Subject: AnyTransportOverMPLS (ATOM)

Explanation For L2VPN service, the loopback address for both local N-PE and remote N-PE must be pre-configured.

Recommended Action Set the value manually in PE devices > loopback IP address.

Messages—L2VPN and VPLS Only

Error Message

cannot config qinq port on a trunk port

Subject: Layer 2 access domain

Explanation For safety reasons, the system does not configure a Layer 2 qinq port if this port has been provisioned as a trunk port.

Recommended Action Make sure you want to overwrite the port mode. If yes, manually delete the port mode command before redeploying the Service Request.

Error Message

cannot config qinq port on an access port

Subject: Layer 2 access domain

Explanation For safety reasons, the system does not configure a Layer 2 qinq port if this port has been provisioned as an access port.

Recommended Action Make sure you want to overwrite the port mode. If yes, manually delete the port mode command before redeploying the Service Request.

Error Message

EWS is not supported on this device

Subject: Layer 2 access domain

Explanation The target device does not support EWS (qinq) service.

Recommended Action Use another type of device or change the type of service to ERS.

Error Message

qinq port already has a different access VLAN defined.

Subject: Layer 2 access domain

Explanation For safety reasons, the system does not configure a Layer 2 qinq port if this port has been provisioned as a qinq port with a different VLAN.

Recommended Action Make sure you want to overwrite the VLAN. If yes, manually delete the "switchport access vlan xxx" before redeploying the Service Request.

Messages—L2VPN, VPLS, and MPLS (multi-hop)

Error Message

cannot config a CAT Queue in Queue (qinq) port on a trunk port

Subject: Layer 2 access domain

Explanation For safety reasons, the system does not configure a Layer 2 qinq port on a CAT device if this port has been provisioned as a trunk port.

Recommended Action Make sure you want to overwrite the port mode. If yes, manually delete the port mode command before redeploying the Service Request.

Error Message

cannot config a CAT trunk port on a qinq port

Subject: Layer 2 access domain

Explanation For safety reasons, the system does not configure a Layer 2 trunk port on a CAT device if this port has been provisioned as a qinq port.

Recommended Action Make sure you want to overwrite the port mode. If yes, manually delete the port mode command before redeploying the Service Request.

Error Message

cannot config access port on a qinq port

Subject: Layer 2 access domain

Explanation For safety reasons, the system does not configure a Layer 2 access port if this port has been provisioned as a qinq port.

Recommended Action Make sure you want to overwrite the port mode. If yes, manually delete the port mode command before redeploying the Service Request.

Error Message

Cannot config access port on a trunkport that has no native VLAN already defined or has another VLAN defined.

Subject: Layer 2 access domain

Explanation For safety reasons, the system does not configure a Layer 2 access port if this port has been provisioned as a trunk port unless a native VLAN on this port matches the VLAN to be deployed.

Recommended Action Make sure you want to overwrite the port mode and the VLAN. If yes, manually delete the port mode command or the access VLAN command before redeploying the Service Request.

Error Message

cannot config trunk port on a qinq port

Subject: Layer 2 access domain

Explanation For safety reasons, the system does not configure a Layer 2 trunk port if this port has been provisioned as a qinq port.

Recommended Action Make sure you want to overwrite the port mode. If yes, manually delete the port mode command before redeploying the Service Request.

Error Message

cannot config trunk port on an access port without a native VLAN defined.

Subject: Layer 2 access domain

Explanation For safety reasons, the system does not configure a Layer 2 trunk port if this port has been provisioned as an access port unless a native VLAN is specified.

Recommended Action Make sure you want to overwrite the port mode. If yes, manually delete the port mode command before redeploying the Service Request.

Error Message

platform information missing

Subject: Layer 2 access domain

Explanation The platform information such as C3550 must be provided for any switches or multi-layer routers.

Recommended Action Do a "collect config" on this device or set the value manually in Devices > Edit > Additional Properties > Platform.

Error Message

switch must be in VTP transparent mode.

Subject: Layer 2 access domain

Explanation To provision L2VPN, VPLS, or MPLS multi-hop, the switches in the access domain must be configured as VTP transparent (not master or client mode).

Recommended Action Configure the following on the switches: VTP mode transparent.

Error Message

"trunk vlan allowed list" is absent on the ERS UNI port.

Subject: Layer 2 access domain

Explanation This message appears only if the DCPL value Provisioning > Service > shared > actionTakenOnUNIVlanList is set to abort and there is no "vlan allowed" command on a trunk port.

Recommended Action Make sure the DCPL value is set correctly (default DCPL value is: prune).

Messages—MPLS Only

Error Message

Cannot provision export map because the route map for this name is not found.

Explanation Missing corresponding route-map command. The route map name should be provisioned prior to adding the export map.

Recommended Action Verify that the route map name exists and use only the same name.

Error Message

Cannot provision import map because the route map for this name is not found.

Explanation Missing corresponding route map command. The route map name should be provisioned prior to adding the import map.

Recommended Action Verify that the route map name exists and use only the same name.

Error Message

Cannot find the major interface for subinterface {0} on device {1}.

Explanation The major interface was not found in the router configuration when provisioning a subinterface.

Recommended Action Verify the router configuration to ensure the existence of the major interface.

Error Message

Cannot provision maximum routes. This command already exists with a different value.

Explanation Command exists with another value.

Recommended Action Verify that the maximum routes value exists for this VRF.

Error Message

Cannot provision router BGP. This command already exists with a different autonomous system #.

Explanation BGP exists with different autonomous system number.

Recommended Action Verify the autonomous system number from BGP. There can be only one BGP process running per router.

Error Message

Invalid interface name {0} on device {1}.

Explanation When provisioning an interface {0} on a device {1}, ISC found this interface has a wrong name format.

Recommended Action Verify the syntax for the interface name.

Error Message

Invalid non-Frame Relay encap type {0} for subinterface {1} on device {2}.

Explanation A serial type of subinterface (such as Serial, POS, or HSSI) can only be configured with FrameRelay encapsulation.

Recommended Action Make sure the FrameRelay encapsulation was assigned for such a subinterface.

Error Message

IP address {0} already assigned to {1} on device {2}.

Explanation The specified IP address {0} has already been assigned to interface {1} on device {2}.

Recommended Action Either select another IP address or un-assign the IP address from interface Y.

Error Message

IP address {0} already assigned to {1} with VRF {2} on device {3}.

Explanation The specified IP address {0} has already been assigned to interface {1} with VRF name {2} on device {3}.

Recommended Action Either select another IP address or un-assign the IP address from interface Y.

Error Message

IP addresses or subnetworks violation between CE and connecting device.

Explanation The IP addresses of an MPLS link between a CE and another device (PE or MVRF-CE, dependent on the configuration) do not belong to the same subnetwork.

Recommended Action Verify the IP addresses and make sure they are under the same subnetwork.

Error Message

IP addresses or subnetworks violation between PE and MVRF-CE.

Explanation The IP addresses of an MPLS link between PE and MVRF-CE do not belong to the same subnetwork.

Recommended Action Verify the IP addresses and make sure they are under the same subnetwork.

Error Message

IP unnumbered is not supported for the interface type.

Explanation ISC only points the IP unnumbered to a loopback interface. The only valid interface types to have IP unnumbered are point-to-point types such as Serial, POS, ISDN, ATM, and Switch. ISC does not allow a shared media type of interface, such as FDDI, Ethernet, or Port-Channel to be configured as IP unnumbered.

Recommended Action Verify that the interface type qualifies for IP unnumbered.

Error Message

ISL encap not supported on C2950.

Explanation ISL encapsulation type is not supported on the Cisco 2950 device.

Recommended Action Verify the encapsulation type and select the correct one.

Error Message

Residential Services only support on switch platform as L3 device.

Explanation Only 76xx platforms (as N-PE) can support the Residential Services feature.

Recommended Action Verify that the N-PE is a 76xx platform that supports the Residential Service feature.

Error Message

Secured interface setup mismatched at devices.

Explanation The interfaces of an MPLS link between two devices was configured differently. One is set to be secured while the other one is not.

Recommended Action Verify the set up and correct it.

Error Message

Secured interface setup mismatched between CE and other device.

Explanation The interfaces of an MPLS link between a CE and another device, PE or MVRF-CE, dependent on the configuration, was configured differently. One is set to be secured while the other one is not.

Recommended Action Verify the set up and correct it.

Error Message

The major interface for {0} on device {1} does not have Frame Relay encapsulation.

Explanation When provisioning a subinterface with FrameRelay encapsulation, its major interface was set to another encapsulation type.

Recommended Action Verify the encapsulation type of its major interface.

Error Message

Unable to update interface {0} encapsulation from {1} to {2} on device {3}. Check any other active subinterfaces.

Explanation Cannot update a major interface encapsulation type from 1 to 2. It might have other active subinterfaces configured to encapsulation type 1.

Recommended Action Verify the condition from the router's configuration.

Error Message

VLAN ID is required for L2 device.

Explanation Missing VLAN ID when configuring an Ethernet-type Interface of an L2 device for an L3 service.

Recommended Action Verify that the VLAN ID exists for such a configuration.

Messages—RBAC Only

Error Message

{0}::{1}: RBAC ==> Insufficient privilege. Resource type "{2}" cannot be found. Report the bug to the Repository team.

Explanation This indicates an ISC internal bug which results in insufficient privileges for the specified resource type.

Recommended Action Report the problem to the Repository team.

Error Message

{0}::{1}: RBAC ==> Insufficient privilege. The object creator "{2}" disallows the operation: Permission "{3}".

Explanation The user who created the object does not permit other users to perform the operation on the object shown, even if the current user does possess the permissions on the object type.

Recommended Action Check the creator's Permissions For Others field in the user editor. Check the box needed to allow others to perform the operation. Creator's permission checking is the last line of defense.

Error Message

{0}::{1}: RBAC ==> Insufficient privilege. User "{2}" Permission "{3}".

Explanation The user specified does not have the permission specified to create, modify, delete, or view (denoted by "C", "M", "D", or "V", respectively) to the object and associated ID specified.

Recommended Action Check the roles assigned to the user. Add the missing permissions.

Error Message

{0}::{1}: RBAC ==> Invalid credential. User name "{2}" Password "{3}".

Explanation Failed to log in due to invalid username or password.

Recommended Action Enter the correct username and password.

Error Message

{0}::{1}: RBAC ==> Token context is not set. The thread stack is: {2}

Explanation This indicates an ISC internal bug which results in the context not being set.

Recommended Action Report the problem with the complete stack trace shown.

Error Message

FATAL: Cannot load ClassDescriptors. Check JAVA CLASSPATH setting.

Explanation Running environment is not set properly.

Recommended Action Make sure to run vpnenv.sh or vpnenv.csh.

Error Message

FATAL: Failed to get key for user, group, or role container. Report this to the Repository team. Your repository might not have RBAC tables populated properly.

Explanation Wrong database, missing RBAC database tables, or database connection problem.

Recommended Action Have the database administrator examine the database. Make sure the database server is up, running, and listening at the port expected by ISC, by checking the property: repository.persistence.url in the vpnsc.properties file and the property: DataAccess.url.1 in the etc/spe/cns.properties file. The two property values must be the same.

Error Message

RbacManager.setTokenContext: Cannot find user for the token.

Explanation User might have been deleted.

Recommended Action Log in as a user with SysAdminRole to check whether the specified user exists.

Error Message

setSecurityContext: Failed to load service token.

Explanation Missing entries in database, incorrect database, or database is corrupted.

Recommended Action Report the problem or have the database administrator diagnose the database.