Cisco IP Solution Center System Error Messages, 4.0
System Error Messages
Downloads: This chapterpdf (PDF - 883.0KB) The complete bookPDF (PDF - 1.46MB) | Feedback

System Error Messages

Table Of Contents

System Error Messages

Messages Starting with +

Messages 0-99

Messages 100-199

Messages 200-299

Messages 300-399

Messages 400-499

Messages 500-599

Messages 600-699

Messages 700-799

Messages 800-899

Messages 900-999

Messages 1000-1099

Messages 1100-1199

Messages 1200-1299

Messages 1300-1399

Messages 1400-1499

Messages 1500-1599

Messages 2000-2099

Messages 2100-2199

Messages Without Numbers

Messages—L2TPv3

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

Messages—L2VPN and VPLS Only

Messages—L2VPN Only

Messages—MPLS Only

Messages—QoS 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 Technical Assistance" section on page -viii.

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 Starting with + (RBAC messages)

Messages 0-99 (Repository messages)

Messages 100-199 (Repository messages)

Messages 200-299 (Repository messages) - These messages are NOT SUPPORTED in this release. -

Messages 300-399 (Repository messages) - These messages are NOT SUPPORTED in this release. -

Messages 400-499 (Repository messages)

Messages 500-599 (Repository messages) - These messages are NOT SUPPORTED in this release. -

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 Without Numbers (L2TPv3, L2VPN, MPLS, QoS, and VPLS messages)

Messages—L2TPv3

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

Messages—L2VPN and VPLS Only

Messages—L2VPN Only

Messages—MPLS Only

Messages—QoS 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 Starting with +

Error Message

+ Change did not succeed, possible reason: old password is not correct.

Explanation Password change failed, due to incorrect old password.

Recommended Action Enter the correct old password.

Error Message

+ FATAL: AuthorizationManager.init() failed! Please check if your db server is up-running, or listening at the right port, by comparing your running dbsrv instance with `DataAccess.url.1' in etc/spe/cns.properties.

Explanation Possible problems could be: database server connection problem, JAVA classpath not set correctly, database missing entries, or wrong database.

Recommended Action Make sure vpnenv.sh or vpnenv.csh has been sourced; installation has been done properly; database 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 etc/spe/cns.properties. The two property values should be the same.

Error Message

+ FATAL: Cannot load ClassDescriptors. Please check JAVA CLASSPATH setting.

Explanation Running environment is 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. Please report this to the Repository team. Your repository may 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

+ FATAL: Failed to load service token. Please report this to the Repository team. Your repository may not have RBAC tables populated properly.

Explanation Possible problems could be: database server connection problem, JAVA classpath not set correctly, database missing entries, or wrong database.

Recommended Action Make sure vpnenv.sh or vpnenv.csh has been sourced; installation has been done properly; database 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 etc/spe/cns.properties. The two property values should 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 if the user specified 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.

Messages 0-99

Error Message

0: Attribute {2} does not exist

Explanation The value for the attribute is not specified.

Recommended Action Set the attribute value.

Error Message

0 (from RbacExceptionMsg_en.properties)

Explanation The user specified does not have Create, Modify, Delete, or View (denoted by "C", "M", "D", "V", respectively) permission to the object specified.

Recommended Action Check the roles assigned to the user. Add the missing permissions.

Error Message

1: Attribute not found for Column {2}

Explanation A dependent attribute for a column is not specified.

Recommended Action Set the attribute value.

Error Message

1 (from RbacExceptionMsg_en.properties)

Explanation Failed to login, due to invalid username or password provided.

Recommended Action Enter the correct username and password.

Error Message

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

Explanation Database Connection is not available.

Recommended Action Check whether the database is running. Also make sure it is running at the right port specified in the DB_PORT variable.

Error Message

2 (from RbacExceptionMsg_en.properties)

Explanation This indicates an ISC internal bug.

Recommended Action Report the problem with the complete stack shown.

Error Message

3: Cannot instantiate abstract class {2}

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

Recommended Action Abstract class can not be instantiated.

Error Message

3 (from RbacExceptionMsg_en.properties)

Explanation The user who created the object disallows 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 object's creator user'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

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

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

Recommended Action Internal error.

Error Message

5: Cant load {2} for {3}

Explanation An internal programmatic software error has occurred.

Error Message

6: Class Map not update because {2}

Explanation The error message explains the detail.

Recommended Action Internal Error.

Error Message

7: Class ==> {2} Not Found

Explanation The specified class is not found.

Recommended Action Make sure you have sourced vpnenv.(c)sh. It could be an internal error too.

Error Message

8: Column not found for Attribute {2}

Explanation The specified column is missing in the database.

Recommended Action Internal Error.

Error Message

9: Database driver not available

Explanation The JDBC driver for the database is not found.

Recommended Action Make sure your database driver is installed properly. If your database is Sybase from ISC, it could be an internal error.

Error Message

10: Database URL not available

Explanation Database URL is not specified.

Recommended Action Make sure your database URL is specified.

Error Message

11: Database Not Accessible ==> {2}

Explanation The database is not accessible by ISC.

Recommended Action Make sure your database is up and running.

Error Message

12: DCPL Property ==> {2} Not Found

Explanation The specified DCPL property is not set.

Recommended Action Specify the property value. It could be an internal error.

Error Message

13: Field type {2} not implemented

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

Recommended Action Internal Error.

Error Message

14: File {2} not found

Explanation The specified file is not found in the ISC path.

Recommended Action Make sure the file is under ISC path. If this is an ISC file, then it could be an internal error.

Error Message

15: Incorrect Class Name; Expected {2}, Got {3}

Explanation Wrong class name found for a class.

Recommended Action Internal Error.

Error Message

16: Incorrect Object type; Expected {2}, got {3}

Explanation Object type is incorrect.

Recommended Action Internal Error.

Error Message

17: IO Exception while accessing {2}

Explanation The exception message explains the error in detail.

Error Message

18: No attributes found for class {2}

Explanation Attributes are missing for a class.

Recommended Action Internal Error.

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 for a user is not available in the database.

Recommended Action Set the password.

Error Message

21: Could not update {2} 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 persons are trying to modify the same object.

Recommended Action Make sure not more than one person is working on the same connection object.

Error Message

22: SQL Exception {2}

Explanation The exception message explains the error in detail.

Error Message

23: SQL Type {2} not implemented

Explanation This SQL type is not implemented in ISC.

Recommended Action Internal Error.

Error Message

24: SQL Type Unknown for {2}

Explanation An unknown type was found for an object.

Recommended Action Internal Error.

Error Message

25: Table --> {2} Not Found

Explanation The specified table is missing in the database.

Recommended Action Internal Error.

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 ({2})should never have been called

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

Recommended Action Internal Error.

Error Message

28: Class {2} could not be instantiated

Explanation The specified class can not be instantiated.

Recommended Action Avoid instantiating the class. It could be an internal error.

Error Message

29: Cannot delete Object

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

Recommended Action First try deleting the dependencies.

Error Message

30: Could not rollback transaction

Explanation Rollback on this commit is failed.

Recommended Action Internal Error.

Error Message

31: General Exception

Explanation The given error message will have the details.

Error Message

32: Null Transaction

Explanation Invalid transaction.

Recommended Action Internal Error.

Error Message

33: Unable to load file "{2}"

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, {2} of {3} object

Explanation The given error message will have details

Recommended Action Internal error.

Error Message

35: Unable to Clone the object. {0}

Explanation The specified object can not be cloned.

Recommended Action Internal Error.

Error Message

36: Unable to set default value. {0}

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

Recommended Action Internal Error.

Error Message

37: Unable to set attribute value. {0}

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

Recommended Action Internal Error.

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 {1}.

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

Messages 100-199

Error Message

133: {0}::{1}: ResourcePool == Value {2} already exists.

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

Recommended Action Do not allocate the same resource multiple times.

Error Message

134: {0}::{1}: 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: {0}::{1}: 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: {0}::{1}: Cannot Allocate Resource, Pool is empty.

Explanation Cannot allocate resource because the pool is empty.

Recommended Action Create new resource pool.

Error Message

137: {0}::{1}: ResourcePool == Pool contains insufficient blocks.

Explanation Resource pool does not contain enough resource.

Recommended Action Check new resource pools.

Error Message

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

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: {0}::{1}: ResourcePool == Block starting with {2} of size {3} has already been allocated.

Explanation Resource pool overlaps with the allocated pool already existing.

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

Error Message

140: {0}::{1}: 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: {0}::{1}: PoolWithSeed == {2} is a malformed string, should be of the form 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: {0}::{1}: PoolWithSeed == {2} 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: {0}::{1}: PoolWithSeed == Release cannot be called for Pools with seed (Route Target and Route Distinguisher)

Explanation Pool with seed value once allocated cannot be released.

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

Error Message

144: {0}::{1}: Vlan == add cannot be called for Vlan. 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: {0}::{1}: ResourcePool == Associated Object of class {2} 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: {0}::{1}: IPAddressPool == IP Address {2} 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: {0}::{1}: IPAddressPool == Expected Mask to be <= 32, but got {2}

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: {0}::{1}: Vlan == Vlan Range {2}, {3} 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-4096).

Error Message

149: {0}::{1}: Vlan == Vlan Range {2}, {3} overlaps existing values

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

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

Error Message

150: {0}::{1}: Vlan == Vlan Range {2}, {3} has some values already allocated

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

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

Error Message

151: {0}::{1}: ResourcePool == {2}, {3} 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: {0}::{1}: ResourcePool == {2}, {3} 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: {0}::{1}: ResourcePool == Cannot Delete Allocated Pools

Explanation The allocated pools cannot be deleted.

Recommended Action Do not try to delete allocated pools.

Error Message

154: {0}::{1}: 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 the user 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: {0}::{1}: VCID == VCID Range {2}, {3} 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: {0}::{1}: VCID == VCID Range {2}, {3} has some values already allocated

Explanation The VCID pool with the starting value {2} and the ending value {3} 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 PersistentObject of type, {0} with ID = {1}

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

Recommended Action Check whether there are allocated resources associated with a PersistentObject 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} which 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 Make sure that the VCID pools being created are within the integer range.

Error Message

166: Out Of Bound Pool Size for Pool with seed with 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 PersistentObject associated with data blocks is not in the database.

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

Error Message

170: Overlaps Aged Data {1},{2}

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

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

Messages 200-299

- These messages are NOT SUPPORTED in this release. -

Error Message

200: {0}::{1}: FirewallRepository ==> CPE (id = {2}, {3}) must exists in repository before being added into Firewall Service Request. Try save CPE first, then adding it into SR.

Explanation To be added into a Firewall service request, the CPE must be saved in the repository.

Recommended Action Save the CPE first, and then add that CPE into the service request.

Error Message

201: {0}::{1}: FirewallRepository ==> CPE {2} is already associated with this Firewall SR.

Explanation A CPE can only be associated with a Firewall service request once. ISC issues this error message if a user tries to add a CPE to a service request that is already associated with that service request.

Recommended Action Abort this action, because a CPE has already been associated with this service request.

Error Message

202: {0}::{1}: FirewallRepository ==> CPE {2}, {3} is already added into other Firewall SR, id = {4}.

Explanation A CPE can only be associated with one Firewall service request. ISC issues this error message if a user tries to add a CPE that is already associated with another service request.

Recommended Action Find the service request that a CPE was originally associated with, remove the CPE from that service request, and add the CPE to a new service request again.

Error Message

203: {0}::{1}: FirewallRepository ==> Can not modify an existing SR in repository, id = {2}. Please create a new subsuming SR and modify that SR.

Explanation A service request that exists in a repository can no longer be modified. Only a new service request in memory can be modified.

Recommended Action Create a subsuming service request, and modify it instead.

Error Message

204: {0}::{1}: FirewallRepository ==> Create a MODIFY CPE for a root SR (id = {2})is not allowed, only ADD and DELETE is valid operation.

Explanation A modified CPE can only be added into a service request that is not at the bottom of a service request stack.

Recommended Action Add the modified CPE into the service request that is at the top of the stack.

Error Message

205: {0}::{1}: FirewallRepository ==> Create a MODIFY CPE in SR(id = {2}) for a DELETED CPE on is not allowed.

Explanation If a CPE is a Delete type in the service request, it can only be added in a subsuming service request. Modify is not allowed for a Delete type.

Recommended Action Create an Add type CPE to a service request.

Error Message

206: {0}::{1}: FirewallRepository ==> Set this policy {1} as parent policy for policy {2} will cause a loop.

Explanation This policy hierarchy has a loop, meaning that some policy is a parent of itself. This is invalid in ISC.

Recommended Action Abort this attempt. This is not a valid action.

Error Message

207: {0}::{1}: FirewallRepository ==> The CPE (id = {2}, {3}) is missing definitions needed by the firewall policy {4}:

Explanation The CPE is missing attributes that are required in the policy. ISC does not allow the CPE to be added into the service request that is using the policy.

Recommended Action Find out which attributes are missing. Add them into the CPE and retry this action.

Error Message

208: {0}::{1}: FirewallRepository ==> FirewallSR (id = {2}) must be in CLOSED state in order to be deleted.

Explanation Only a Closed service request can be safely deleted.

Recommended Action Decommission the service request into the Closed state or use the Force Purge option.

Error Message

209: {0}::{1}: FirewallRepository ==> Can not add a CPE into a DELETE SR. Please create an ADD SR instead.

Explanation A CPE cannot be added into a decommissioned service request.

Recommended Action Abort this action.

Error Message

210: {0}::{1}: FirewallRepository ==> CPE already deleted in parent SRs.

Explanation If a CPE is already deleted in a parent service request, it cannot be deleted again.

Recommended Action Abort this action, because the CPE is already the Delete type.

Error Message

211: Parent object {0} is missing or null

Explanation The required parent object is null.

Recommended Action Find out which object is missing and provide it.

Error Message

212: AAServer with ID {0} doesn't support TACACS+ or RADIUS protocol.

Explanation A Firewall policy requires an AA server with TACACS+ or RADIUS.

Recommended Action Create a new AA server object which TACACS+ or RADIUS protocol support, and use that new AA server in a policy.

Error Message

213: can not set the same parameter, {0}

Explanation The same parameter has been set.

Recommended Action Find out which parameter causes the problem and try to provide a different value.

Error Message

214: can not determine whether service is protocol or protocol bundle

Explanation From the service name, ISC can not decide whether the service is a protocol or a protocol bundle.

Recommended Action Go to the Access Rule that uses that service and reset the service.

Messages 300-399

- These messages are NOT SUPPORTED in this release. -

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

301: Cannot delete MASTER VPNSC Host.

Explanation An internal programmatic software error has occurred.

Error Message

302: Invalid interface encapsulation type.

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

310: CPE {0} must exists in repository before being added into NAT Service Request. Try save CPE first, then adding it into SR.

Explanation User tried to add a non-existing CPE into a NAT service request.

Recommended Action Save CPE and then create NAT service request.

Error Message

311: CPE {0} is already associated with this NAT SR.

Explanation This CPE is included in this service request.

Recommended Action Remove the CPE from the service request and save the service request again.

Error Message

312: CPE {0} is already in another NAT SR and it had been configured, Job id = {1}.

Explanation This CPE had been included with another NAT service request.

Recommended Action Remove the CPE from the service request and save the service request again.

Error Message

318: NAT SR (id = {0}) must be in CLOSED state in order to be deleted.

Explanation User tried to purge a service request that was not in Closed state.

Recommended Action Decommission the service request first, and then purge or delete the service request.

Error Message

321: This Nat SR id {0} is in processing state and cannot be modify.

Explanation User tried to modify a service request that is being deployed by ISC.

Recommended Action Wait until the deployment completes and then modify the service request.

Error Message

322: This Nat SR already been subsumed by {0}, fail to commit.

Explanation The NAT service request had been changed by another service request. Unable to commit.

Recommended Action Cancel the NAT service request save operation.

Messages 400-499

Error Message

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

Explanation An internal programmatic software error has occurred.

Messages 500-599

- These messages are NOT SUPPORTED in this release. -

Error Message

500: IPSecSR:=> Cannot create new IPSecSR. Attribute {0} not defined or missing

Explanation A new IPsec SR can not be created because the attribute given in the error message is not defined.

Error Message

501: IPSecSR:=> Query {0} with {1} found more than 1 matching row

Explanation A single row was expected, but the query returned many rows.

Recommended Action Internal error

Error Message

502: IPSecSR:=> Encountered error getting/processing {0}

Explanation Error while processing the IPsec SR.

Recommended Action The error message will have the details.

Error Message

503: IPSecSR:=> Cannot do query {0}. Reason : {1}

Explanation Query can not be done, details given in the error message

Error Message

504: IPSecSR:=> IPSEC SR Validation error. Validation Type : {1}. Reason : {2}

Explanation Validation error, reason given in the error message.

Error Message

505: IPSecSR:=> IPSEC SR Validation error. Logical device for : {0} is either not enbaled for IPSec or does not have a Secure interface

Explanation Validation error for the logical device given in the error message.

Recommended Action Make sure the particular logical device is IPsec enabled and has a secured interface.

Error Message

506: IPSecSR:=> The following Logical device pairs already have tunnels associated

between each other {0}

Explanation The pair of logical devices given already have tunnels created between them.

Error Message

507: IPSecSR:=> Invalid topology detected : {0}

Explanation Invalid topology found.

Error Message

508: IPSecSR:=> Topology has no hub specified

Explanation There is no hub specified for the topology.

Error Message

509: IPSecSR:=> Invalid or incomplete information in this CpeTopoRole instance. Logical Device represented : {0}, field : {1}, value : {2}

Explanation An internal programmatic software error has occurred.

Error Message

510: IPSecSR:=> Duplicate Logical Device {0} detected in SR {1}

Explanation The logical device is duplicated for the SR specified in the error message.

Recommended Action Make sure you are not adding the same device more than once to an SR.

Error Message

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

Explanation A policy cannot be deleted because it is associated with some SRs.

Recommended Action A policy can be deleted only if there are no SRs associated with it.

Error Message

512: {0}::{1}: IPSecProposal:=> IPSecProposal is not associated with a IPSec Policy

Explanation The IPsec proposal is not associated with any IPsec policy.

Recommended Action Associate the IPsec proposal with an IPsec policy object.

Error Message

513: {0}::{1}: IPSecProposal:=> Expected one IPSec Policy for policy ID {2}. Got {3}.

Explanation Expecting only one IPsec policy for an IPsec proposal, but more than one is returned.

Error Message

514: {0}::{1}: IPSecProposal:=> IPSecProposal with ID {2} has IPSecPolicies associated with the following SRs: {3}. It cannot be deleted

Explanation An IPsec proposal can not be deleted when its parent IPsec policy is associated with SRs.

Recommended Action To delete the IPsec proposal object, there should not be any IPsec SRs associated with the parent object IPsec policy.

Error Message

515: {0}::{1}: IKEProposal:=> IKEProposal is not associated with a IPSec Policy

Explanation The IKE proposal is not associated with any IPsec policy.

Recommended Action Associate the IKE proposal with an IPsec policy object.

Error Message

516: {0}::{1}: IKEProposal:=> Expected one IPSec Policy for policy ID {2}. Got {3}.

Explanation Expecting only one IPsec policy for an IKE proposal, but more than one is returned.

Error Message

517: {0}::{1}: IKEProposal:=> IKEProposal with ID {2} has IPSecPolicies associated with the following SRs: {3}. It cannot be deleted

Explanation IKE proposal can not be deleted when its parent IPsec policy is associated with SRs.

Recommended Action There should not be any IPsec SRs associated with the parent object IPsec policy to delete the IKE proposal object.

Error Message

518: User ==> User is not associated with a Group

Explanation User is not associated with a Group.

Recommended Action Associate the User with a Group.

Error Message

519: User ==> Expected one Group for group ID {2}. Got {3}.

Explanation Expected one Group for the user, but more than one is returned.

Error Message

520: User ==> User with ID {2} has Groups associated with the following SRs: {3}. It cannot be deleted.

Explanation User can not be deleted because its Group is associated with some SRs.

Recommended Action User can be deleted only if its Group is not associated with any SR.

Error Message

521: AAServer ==> AAServer is not associated with a customer

Explanation AAServer is not associated with a customer

Recommended Action AAServer must be associated with a customer.

Error Message

522: AAServer ==> Expected one customer for customer ID {2}. Got {3}

Explanation Expected one customer, but more than one is returned.

Error Message

523: AAServer ==> AAServer {2} is associated with the following SRs: {3}. It cannot be deleted

Explanation AAServer is associated with some SRs.

Recommended Action AAServer can not be deleted if it is associated with an SR.

Error Message

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

Explanation Address Pool is not associated with any Persistent Object.

Error Message

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

Explanation The error message will have the details.

Recommended Action Internal error

Error Message

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

Explanation The error message will have the details.

Recommended Action Internal error

Error Message

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

Explanation An internal programmatic software error has occurred.

Recommended Action Associate the Address Pool with the parent.

Error Message

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

Explanation This object can not be persisted in the database.

Error Message

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

Explanation The error message will have the details

Error Message

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

Explanation The error message will have all the details.

Error Message

531: 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: Remote Access ==> Expected one {2} for ID {3}. Got {4}.

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

Error Message

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

Explanation Query returns unexpected object type.

Recommended Action Internal error

Error Message

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

Explanation Expected one device-specific group object.

Error Message

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

Explanation Object returned is not of type Group.

Error Message

536: User ==> Parent Group has not been defined.

Explanation Parent Group has not been defined

Error Message

537: AAServer ==> Returned object ({2}) is not of type Customer.

Explanation Returned object ({2}) is not of type Customer.

Recommended Action Internal error

Error Message

538: IPSecPolicy ==> Parent Customer has not been defined

Explanation Parent Customer has not been defined.

Recommended Action Customer should be assigned to IPsec policy.

Error Message

539: IPSecProposal ==> Returned object ({2}) is not of type IPSecPolicy

Explanation Returned object ({2}) is not of type IPsec policy.

Error Message

540: IPSecProposal ==> Parent IPSecPolicy has not been defined.

Explanation Parent IPsec policy has not been defined.

Recommended Action IPsec policy should be assigned to IPsec proposal.

Error Message

541: IKEProposal ==> Returned object ({2}) is not of type IPSecPolicy

Explanation Returned object ({2}) is not of type IPsec policy.

Error Message

542: IKEProposal ==> Parent IPSecPolicy has not been defined

Explanation Parent IPsec policy has not been defined

Recommended Action IPsec policy should be assigned to IKE proposal.

Error Message

543: RepGroup3K ==> method call order error: addChildAttributesToTable must be called prior to setChildAttributes.

Explanation Method call order error.

Recommended Action addChildAttributesToTable must be called prior to setChildAttributes.

Error Message

544: RepGroup3K ==> the child attribute tables list is not associated with any Persistent Objects created via method RepGroup::createDeviceSpecificAttributes

Explanation The child attribute tables list is not associated with any Persistent Objects created by using method RepGroup::createDeviceSpecificAttributes.

Error Message

545: RemoteAccess ==> No {2} association exists for this object

Explanation No {2} association exists for this object.

Error Message

546: {0}::{1}: RemoteAccess :: Expected one {2} for ID "{3}". Got "{4}".

Explanation Expected one object, but query returns more than one.

Error Message

547: {0}::{1}: RemoteAccess :: Returned object ({2}) is not of type {3}.

Explanation Returned object ({2}) is not of type {3}.

Error Message

548: {0}::{1}: RemoteAccess :: Parent {2} is not defined.

Explanation A parent object is not defined for the given Remote Access object.

Recommended Action Associate this Remote Access object with the parent object.

Messages 600-699

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 Input string of length within the specified range.

Error Message

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

Explanation String has incorrect format.

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

Error Message

602: Invalid Integer: value {0} is not within valid range [{1}, {2}]

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

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

Error Message

603: Invalid Enumeration: value {0} is not valid for enum of type {1}

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.

Recommended Action Internal error.

Error Message

608: Invalid Object: The object {0} with id {1} is invalid since its attribute {2} has invalid value {3}

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

Recommended Action Internal error.

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 since 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/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 concerned object be deleted.

Error Message

611: The Object {0} with id {1} cannot be modified since Object {2} : {3} are associated with it

Explanation The Object {0: Class Name of Object} with ID {1} cannot be modified because object {2: ObjectType} : {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 modified

Explanation The specified object can not 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 since it is already modified

Explanation Another instance of the connection modified the object.

Error Message

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

Explanation The parent object is not committed. Thus, the specified object can not 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 since its parent Object {2} with id {3} is not in the database

Explanation The parent object is not committed. Thus, the specified object can not 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} since 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 since 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 can not be called with an invalid value set for an attribute.

Recommended Action Call this API with a valid attribute value.

Error Message

620: The {2} Service Request with Job id {3} and id {4} cannot be subsumed since its not on top of the stack

Explanation An SR on the bottom of the stack can not be subsumed.

Recommended Action Avoid subsuming an SR that is the bottom SR of the stack and there are one or more SRs on top of it.

Error Message

621: The {0} Service Request with Job id {1} and id {2} cannot be subsumed since it is decommissioned

Explanation A decommissioned SR can not be subsumed.

Recommended Action Avoid subsuming a decommissioned SR.

Error Message

622: The {0} Service Request with Job id {1} and id {2} cannot be purged since it is not in CLOSED state

Explanation The {Service Request type - MPLS, L2VPN, and so on} 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 SR 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 since its not on top of the stack

Explanation The {Service Request type - MPLS, L2VPN, and so on} 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 an SR that is not on the top of the stack. Purging the topmost SR 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} since 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 an SR 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.

Recommended Action Internal 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 since its not associated with Object {1}

Explanation The Object {Class Name of Object} cannot be persisted since its not associated with Object {1}

Recommended Action Read the error message details about why it can not 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 can not be removed.

Error Message

632: The {0} Service Request with Job id {1} and id {2} cannot be subsumed since its already subsumed

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

Recommended Action Subsume the SR which 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 at REQUESTED state. You need to decommission the SR then config audit succeeds before you can close it.

Explanation The {Service Request type - MPLS, L2VPN, and so on} Service Request concerned cannot be closed because one of the SRs in the subsumption stack is not at REQUESTED state.

Recommended Action You must decommission the SR 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 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 since it is not on top of the subsumption stack OR it is not in CLOSED state

Explanation This SR cannot be deleted because it is not on the top of the subsumption stack or it is not in CLOSED state.

Recommended Action Do not try to purge an SR that is not on top of the stack or is not in the closed state. Purging the topmost SR will purge the whole stack or first decommission the SR and then purge it or use Force Purge.

Error Message

636: VPN cannot be created as there is no sufficient license!

Explanation VPN cannot be created because there are not sufficient 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

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.

Messages 700-799

Error Message

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

Explanation Customer can not be deleted because it has been associated with an SR.

Recommended Action Do not delete this customer or purge those SRs 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 can not be deleted because it is associated with SRs.

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

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 can not be deleted because it has been associated with an SR.

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

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

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 An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

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

Explanation The users entered wrong data Mdt size. 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 since 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 accessdomain{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 IP address {0} with name {1} 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 can not 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.

Messages 800-899

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 Object can not 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 Object can not 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

812: Invalid QoSSR. It does not have a QoSPolicy, and one of the QoSLinks does not have a LinkProfile nor a EomplsLinkProfile.

Explanation Can not create a QoS service request. The reason is usually given in the error message itself.

Recommended Action Depending on the reason, specify a QoS Policy for the QoS SR and make sure the QoS Link has a Link Profile.

Error Message

814: {0} is null.

Explanation A QoS SR is requested to be created from a base SR, which could be an MPLS SR, an L2VPN SR, or a VPLS SR, but the base SR is not specified.

Recommended Action Specify or choose a base SR.

Error Message

815: {0}'s policy is null.

Explanation A QoS SR is requested to be created from a base SR, which could be an MPLS SR, an L2VPN SR, or a VPLS SR, but the base SR does not have a policy associated with it.

Recommended Action Specify a policy for a base SR.

Error Message

816: Can not get QoS links from {0} with id {1};

Explanation A QoS SR is requested to be created from a base SR, which could be an MPLS SR, an L2VPN SR, or a VPLS SR, but the base SR does not contain any MPLS links, L2VPN links, or VPLS links.

Recommended Action Make sure the base SR contains link(s).

Error Message

817: The logical links are null from {0};

Explanation A QoS SR is requested to be created from a base SR, which could be an MPLS SR, an L2VPN S, or a VPLS SR, but an MPLS or VPLS Link or an Attachment Circuit in an MPLS, VPLS, or L2VPN SR does not have any logical links.

Recommended Action Make sure the links in the base SR contain Logical Link(s).

Error Message

818: The first logical link is null from {0};

Explanation A QoS SR is requested to be created from a base SR, which could be an MPLS SR, an L2VPN SR, or a VPLS SR, but an MPLS or VPLS Link or an Attachment Circuit in an MPLS, VPLS, or L2VPN SR does not have any logical links, except for the first logical link.

Recommended Action Make sure the links in the base SR contain Logical Link(s).

Error Message

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

Explanation An internal programmatic software error has occurred.

Error Message

820: Can not add link. The link is already in SR ID {0}.

Explanation Can not add a link that is already part of another QoS SR into a new QoS SR.

Recommended Action Make sure not to add the same link twice into different QoS SRs.

Error Message

821: SR with OpType Delete can not remove link.

Explanation Can not save a QoS SR if the policy for that SR has not been committed.

Recommended Action Save the policy first.

Error Message

822: Cannot create QoSSR, policy is null;

Explanation There are different options when getting QoS Links from a QoS SR. This is an invalid or unknown option.

Recommended Action Pass a valid option type when getting links.

Error Message

823: Invalid accessType, supports PROVISIONING, CONFIG_AUDIT and FORCE_DEPLOY only

Explanation The access type passed into QoSSR.getLinks is incorrect.

Recommended Action Pass a valid access type defined in the class QoSSR.

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

Error Message

900: {0}::{1}: No Service Type Set For Policy "{2}".

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: {0}::{1}: VPLS Policy "{2}" 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 {2} is to be deleted.

Error Message

902: {0}::{1}: VPLS Policy "{2}" 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 {2} is to be modified.

Error Message

903: {0}::{1}: Service Request Being Subsumed Does Not Exist In The Database.

Explanation Service request being subsumed does not exist in the database.

Recommended Action Internal database error. The GUI should not display the service requests that do not exist in the database. Retry.

Error Message

904: {0}::{1}: 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 SR being subsumed before saving to the repository.

Error Message

905: {0}::{1}: VPLS Links Cannot be added to Delete Service Request.

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

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

Error Message

906: {0}::{1}: Service Data Missing "{2}" Attribute.

Explanation Mandatory data missing from VPLS links.

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

Error Message

907: {0}::{1}: VPLS Links Only Supports Ethernet Encapsulations

Explanation VPLS links support only Ethernet encapsulations.

Recommended Action Do not try saving links with other encapsulations.

Error Message

908: {0}::{1}: VPLS Link Not Present In the Database

Explanation Internal repository exception will be handled by the repository.

Recommended Action Will not be displayed on the GUI.

Error Message

909: {0}::{1}: Missing Loopback Address Error "{2}".

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

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

Error Message

910: {0}::{1}: VplsLink ID "{2}" 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: {0}::{1}: Invalid VPLSLink 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: {0}::{1}: Invalid Range for Service Attribute "{2}"

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

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

Error Message

913: {0}::{1}: SR With OPTYPE Delete Can Not Remove Link

Explanation Service request with Operation Type cannot remove link.

Recommended Action Do not try to remove link from service request with OPTYPE Delete.

Error Message

914: {0}::{1}: 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: {0}::{1}: 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: {0}::{1}: 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

917: {0}::{1}: VLAN POOL "{2}" Needs to be created for Vpls Enabled VPN's.

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: {0}::{1}: Unable to Generate XML.Trouble appending "{2}" Node.

Explanation Unable to generate XML for a particular service request.

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

Error Message

919: {0}::{1}: Exception in 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 Requested 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 Requests 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 VPN's.

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/Policy.

Explanation Parent attribute not set for VPLS link or 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 unknown option

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 unknown.

Recommended Action Have a valid value VPLS link Interface Encapsulation for VPLS link.

Error Message

931: PE's 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 belong to the same Access Domain.

Error Message

932: Some PE's 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 VPLS link have an associated Access Domain.

Messages 1000-1099

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 Request XML file for 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 Request XML file for proper parameter `name' XML elements.

Error Message

1005: The specified Class does not exist

Explanation The classname is not recognized.

Recommended Action Check Request XML file for proper `className' XML elements.

Error Message

1006: The requested object could not be found

Explanation The classname attribute is not recognized.

Recommended Action Check Request XML file for 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 Request XML file for valid method in `ns1' XML element of `Body' XML element.

Error Message

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

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

Recommended Action Check database for current condition of selected object.

Error Message

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

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

Recommended Action Check database for current condition of selected object.

Error Message

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

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

Recommended Action Check database for current condition of 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 database for current condition of selected object.

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 Request XML file for proper format of '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 Request XML file for proper format of 'item' XML elements.

Error Message

1014: The query language is not recognized or supported

Explanation The only supported type is SQL.

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

Error Message

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

Recommended Action Check Request XML file for proper format of 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 Request XML file for valid method in 'ns1' XML element of 'Body' XML element.

Error Message

1017: The request XML does not have a header

Explanation The header is the SOAP Header.

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

Error Message

1018: The request XML does not have a body

Explanation The body is the SOAP body.

Recommended Action Check Request XML file for proper format and existence of '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 Request XML file for 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 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 Request XML file for 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 Request XML file for 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 Request XML file for 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 Request XML file for 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 Request XML file for proper format of 'Template' XML element.

Error Message

1028: Error creating Template - Nbi

Explanation Error in ISC Template software.

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

Error Message

1029: Error creating Template Data - Nbi

Explanation Error in ISC Template software.

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

Error Message

1030: Error creating template Configlet

Explanation Error in ISC Template software.

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

Error Message

1031: Error finding Template - Nbi

Explanation Error in ISC Template software.

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

Error Message

1032: Error viewing Template - Nbi

Explanation Error in ISC Template software.

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

Error Message

1033: Error deleting Template - Nbi

Explanation Error in ISC Template software.

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

Error Message

1034: Error deleting Template data

Explanation Error in ISC Template software.

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

Error Message

1035: Error modifying Template Nbi

Explanation Error in ISC Template software.

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

Error Message

1036: Error occurred while processing (create) transaction.

Explanation Error occurred while processing (create) transaction.

Recommended Action Check Request XML file for 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 Request XML file for 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 Request XML file for 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 Request XML file for 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 an constructor arg for {1} should have value 1 in the composite meta

Explanation Internal error.

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 args 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 handeled 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 Request XML file for proper format and valid 'user' and 'password' values.

Error Message

1097: Invalid Session.

Explanation The session could have expired.

Recommended Action Check that 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

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 will be 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 in 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 SR and it expired. The NBI times out to free up the connection.

Recommended Action Increase the wait time to allow the SR to complete.

Error Message

1109: Method arg for subsuming sr should be old sr, i.e., ({0}).

Explanation ISC uses subsuming to represent historical SRs.

Error Message

1110: nable to subsume the existing SR.

Explanation ISC uses subsuming to represent historical SRs.

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: MplsVpnLink id ({0}) to be removed does not belong to the SR to be modified.

Explanation Internal error.

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/className {0} is improperly nested.

Explanation The objectPath/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 Optype {0} not allowed on {1} when parent {2} optype 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 your XML input request cannot 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}, please 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}, please 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/value input.

Explanation Internal error.

Error Message

1136: Error downloading to the Download Console Util. 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 SR is found by its Locator ID, which is the same as the SR 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 for example. Some objects to 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 for example. 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 may 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 may not include keyProperties elements

Explanation Create requests might not include keyProperties elements.

Error Message

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

Explanation Create Instances might not 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 may not be more than one level deep.

Explanation Delete requests might not 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 may contain only delete, create, or modify sub-actions.

Explanation Modify requests might 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 SRs.

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. Please 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. Please 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 not corresponding database table for this object.

Explanation Object {0} not found in the meta or there is not 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 param {0} of object {1}.

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

Error Message

1179: Param {0} present in multiple objects, please 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/Alias {0} of param {1} not defined in object/alias list in from clause.

Explanation Object/Alias {0} of parameter {1} not defined in object/alias list in 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 '{minRage,maxRange}' but found {1}, 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 param {0}.

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

Error Message

1189: Enum value string for param {0} should be enclosed in single quotes.

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

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 Ring not found in 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 has occurred while creating requested deployment tasks.

Error Message

1199: Must input at least one Protocol or one ProtocolBundle.

Explanation Must input at least one Protocol or one Protocol Bundle.

Messages 1200-1299

Error Message

1203: TeProvider "<name>" already exists.

Explanation TeProvider with the specified name has already been used.

Recommended Action Use a different name.

Error Message

1205: Tunnel Number "<#>" already exists.

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

Recommended Action Use a different number.

Error Message

1206: TeExplicitPath contains non-contiguous links.

Explanation The path in question is not contiguous.

Recommended Action Specify a contiguous path.

Error Message

1207: TeExplicitPath "<name>" already exists.

Explanation The pathname has been used by an existing path.

Recommended Action Use a different pathname.

Error Message

1208: TeProvider "<name>" is not deletable 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 SRs underneath it have been deleted.

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

Error Message

1209: SR(<id#>) can not be subsumed because it has been subsumed by SR(<id#>)

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

Recommended Action Exit the SR edit window and re-enter.

Error Message

1210: DeviceInterface can not be found with TeInterface id(<id#>)

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: TeInterface can not be found with interface name "<name>"

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: Te Tunnel Policy "<name>" is in use and cannot be deleted.

Explanation The tunnel policy is used by a 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

Error Message

1304: Invalid Api call : API {1} can not be called on object {2} because {3}

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

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

Error Message

1306: Internal Repository Error : {0}

Explanation Internal repository software error.

Recommended Action It should not happen. 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 Internal ISC software error. 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 SRs, it can not be modified or deleted.

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

Error Message

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

Explanation GUI passed the wrong data to the repository. Users will not see this error message. GUI will catch the exception and take the appropriate actions.

Error Message

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

Explanation User 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. Users will not see this error message. GUI will catch 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 landing on different source and destination endpoints.

Error Message

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

Explanation User 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} can not be Deleted because it is associated with {1} with IDs {2}

Explanation Object can not be deleted because it is already associated with other objects.

Recommended Action Do not delete this object.

Error Message

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

Explanation Object can not 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 SR because it did not have any policy associated with it.

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

Error Message

1361: Can not add a link into a DELETE SR. Please create an ADD SR instead.

Explanation The users tried to add link to a deleted SR, which is not allowed.

Recommended Action Create an ADD SR and add that link to that SR.

Error Message

1362: Can not remove a link from a DELETE SR. Please create an ADD SR instead.

Explanation The users tried to delete a link to a deleted SR, which is not allowed.

Recommended Action Create an ADD SR.

Error Message

1363: Link with ID {0} is already added to SR, it can not be added to SR again.

Explanation The link is already associated with an SR. It can not be added to another SR.

Recommended Action Create a new link and added it to an SR or abort this action.

Error Message

1364: VRF with ID {0} is with name {1}, which mismatched the name {2} input from the users

Explanation The users 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 The users tried to associate more than one CERC to the grey management VPN.

Recommended Action Grey management VPN is auto-created by the repository. The users 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 mplsVpnLink with ID {4} and SR ID {5}

Explanation The users 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. The users 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 SR creation.

Recommended Action Add the required data for SR creation.

Error Message

1370: Mpls Vpn Link with ID {0} join {1} MulticastVpns. Mpls Vpn Link can only join one Multicast VPN.

Explanation One MPLS VPN link can join only one multicast VPN. The users 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 invalid format

Explanation The users input RT is not in the correct format.

Recommended Action Enter the RT in the correct format.

Error Message

1372: IsFullMesh can not be changed on existing CERC with ID {0}

Explanation The users 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 The users assigned different VLAN IDs on link endpoints. Users will not see this error messages. GUI will 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 is with ID {0}, and UNI interface is landing on Device with ID {1}

Explanation The user-specified UNI interface did not land on the specified NPC.

Recommended Action Assign the UNI interface on the selected NPC.

Error Message

1375: Manually Assign resource {0} with value {1} has been used. Please assign a new value.

Explanation The users tried to use the resource that has been used.

Recommended Action Reassign a new value.

Error Message

1376: Only PE_POP is allowed to added to Access domain.

Explanation The users tried to add a non-PE_POP to the access domain. Only a PE with a PE_POP type can be associated with Access Domain.

Recommended Action Select the PE with the PE_POP 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-spoke topology.

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

Error Message

1378: Deleted type {0} can not add object {1}

Explanation Object with a deleted type can not 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 ACs are allowed within one EndToEndWire. There are {0} ACs in EndToEndWire.

Explanation The users tried to assign more than two ACs to one end-to-end wire.

Recommended Action Assign only two ACs 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. The user created a CERC without associating 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.

Messages 1400-1499

Error Message

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

Explanation The last physical link on and NPC did not terminate on a PE.

Recommended Action Reselect the last physical link that will terminate 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 will start 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 CE scenario.

Error Message

1404: NPC with ID {0} did not end on PE_POP device

Explanation The ending device of an NPC did not end on a PE with a PE_POP role.

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

Error Message

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

Explanation Entities for 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 (ring 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 and 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/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 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/Collection cannot be last object in ObjectList for NPC formation.

Explanation When creating an NPC, the ring should not be selected as the last element on the collection.

Recommended Action Do not add a ring as the last element.

Error Message

1413: Device with ID <id of device> can not be the source device for creating this NPC.

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 <id of device> is not a part of Ring which 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 is part of the Ring if the Ring is the first connectivity for an NPC.

Error Message

1415: Named Physical Circuit with Name : <name of the named physical circuit> is not a Valid NPC, Because it's Destination Device : <name of the device> is not of type PE-POP, Kindly 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 PE-POP and should be removed.

Recommended Action Delete the relevant NPC and try creating it again.

Error Message

1416: Device : <name of the device> is does not have a role of Type PE_POP. For NPC Creation destination device should be a POP.

Explanation The Named Physical Circuit's (NPC's) destination device must be of type PE-POP.

Recommended Action Select a device of type PE-POP as a destination device of the NPC.

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} Links, It should have a min 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 DB for given set of devices and interfaces

Explanation Trying to commit a ring when a ring with an identical set of devices and connectivities 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

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: POLICY/AC_ATTRS 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/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 if the link attribute is not created properly.

Recommended Action An Internal Error.

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/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 Boolean type.

Error Message

1463: {0} : interfaceEncap is unknown.

Explanation The given interface encap is not a valid type.

Recommended Action Give a correct interface encap 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 L2VpnProtocol type value.

Error Message

1467: {0} : L2VpnSequenceType is unknown.

Explanation The given L2VpnSequence is not a valid type.

Recommended Action Give a valid L2VpnSequence type value.

Error Message

1468: {0} : L2VpnCoreType is unknown.

Explanation The given L2VpnCore is not a valid type.

Recommended Action Give a valid L2VpnCore type value.

Error Message

1469: {0} : L2VpnPayloadType is unknown.

Explanation The given L2VpnPayload is not a valid type.

Recommended Action Give a valid L2VpnPayload type value.

Error Message

1470: {0} Policy can not 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 can not be modified. {1}

Explanation The policy cannot be modified because of the reason given in the error message.

Recommended Action Most probably Service Requests are associated with the policy so it 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.

Messages 1500-1599

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 The user 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 can not 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} can not be freed since it is on the reserved vlan pool on Access Domain with name {1}

Explanation 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} can not be allocated as it is on the reserved vlan pool on Access Domain with ID {1}

Explanation 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 Resource pool is not yet created by the user.

Recommended Action Create the required resource pools for further operations.

Messages 2000-2099

Error Message

2000: The following device does not exist: {0}.

Explanation The following device does not exist: {0}.

Error Message

2001: Task create has failed. Unable to find a reference for {0}.

Explanation Task create 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

2004: FWSM download has failed with the following error: {0}.

Explanation FWSM download has failed with the following error: {0}.

Error Message

2005: Incomplete Attributes given. If {0} is given then {1} should also be given to for {2}.

Explanation Incomplete Attributes given. If {0} is given then {1} should also be given to for {2}.

Error Message

2006: No Vc available for {0} with value {1} and {2}.

Explanation No 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 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: ServiceRequest involving TemplateDownload are not schedulable

Explanation Service Requests involving TemplateDownload can not be scheduled.

Error Message

2014: Attempting to deploy improperly defined ServiceRequest.

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}Interval is missing for PeriodicType {0}.

Error Message

2016: Software error: The PeriodicType {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 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 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 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 since it is part of an SR.

Explanation The policy cannot be modified because it is part of an SR.

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 datatype 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} encountered.

Error Message

2029: Error processing request. Probable cause is inputed data.

Explanation Error processing request. Probable cause is entered data.

Error Message

2030: The Class {0} requires the keyProperty attribute {1}.

Explanation The Class {0} requires the key Property 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 lease one ServiceRequest LocatorId.

Explanation This task requires at least one Service Request LocatorId.

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 Request XML file for proper format of `Template' XML element.

Error Message

2046: Multiple Cpes were found at the site {0}. This is not allowed in an IPSec SR.

Explanation Multiple CPEs were found at the site {0}. This is not allowed in an IPsec SR.

Error Message

2047: Template type is unsupported: {0}.

Explanation Template type is unsupported: {0}.

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

Error Message

2048: Attribute subAction missing for object {0}. This attribute is required for modify request.

Explanation Attribute subAction missing for object {0}. This attribute is required for modify request.

Recommended Action Check Request XML file for 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 is unsupported: {0}.

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

Error Message

2050: Incoming Body Text is not valid.

Explanation Incoming Body Text is not valid.

Recommended Action Check Request XML file for proper format and existence of `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 Request XML file for proper format and existence of `Body' XML element.

Error Message

2052: Incoming variable {0} is not part of Template Definition.

Explanation Incoming variable {0} is not part of Template Definition.

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

Error Message

2053: Problem in template data validation.

Explanation Problem in template data validation.

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

Error Message

2054: {0} with id ({1}) to be deleted/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 which link is designated.

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 The Modify Request from the user 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 the request 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 param {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 param 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 need 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 param {0} for report {1} can't only have objectRefParamName, objectRefName is 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} need 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} have Multiple filter sets within a set of markers, this is not supported currently.

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 Inteterface 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 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 API error message.

Error Message

2079: Please specify a WaitTimeout value or change wait value to false.

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

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 JobId {0}.

Explanation Internal API 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 correctness.

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 KeyProperties.

Recommended Action Check the filters in the reports meta for correctness.

Error Message

2087: {0} cannot be created/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

2097: Duplicate LinkTemplate with DatafilePath {0} not allowd for Logical Device {1}.

Explanation A unique template name/path must be specified.

Recommended Action Correct the template name/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 {0} can belong to either the Organization or the Provider, but both were found in the request

Recommended Action Remove either the Organization or Provider, because both cannot exist in the request.

Messages 2100-2199

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.

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 Without Numbers

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, VPLS, and MPLS (multi-hop)

Messages—L2VPN and VPLS Only

Messages—L2VPN Only

Messages—MPLS Only

Messages—QoS Only

Messages—L2TPv3

Error Message

AC is starting with PE-CLE for ATM/FR no CE case.

Subject: L2TPv3 Service Editor

Explanation Trying to start a connection with a device with a PE-CLE type.

Recommended Action Use a device with the type of either CE or PE-POP.

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-1007 for CE DLCI.

Error Message

CE VCD must be from 1 to 4294967295

Subject: L2TPv3 Service Editor

Explanation The value of the VCD field for CE is not in the required range.

Recommended Action Enter a numeric value in the range 1-4294967295 for CE VCD.

Error Message

CE VCI must be from 33 to 65525

Subject: L2TPv3 Service Editor

Explanation The value of the VCI field for CE is not in the required range

Recommended Action Enter a numeric value in the range 33-65525 for CE VCI.

Error Message

CE VPI must be from 0 to 255

Subject: L2TPv3 Service Editor

Explanation The value of the VCI field for CE is not in the required rang.

Recommended Action Enter a numeric value in the range 0-255 for CE VCI.

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 PE-CLE and no NPC found.

Subject: L2TPv3 Service Editor

Explanation Trying to start a connection with a device with a PE-CLE type.

Recommended Action Use a device with the type of either CE or PE-POP.

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 - 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-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- 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-255.

Error Message

Invalid value for "Type of Service". Please enter a numeric value in the range 0 - 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-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-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-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-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-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-1007 for PE DLCI.

Error Message

PE VCD must be from 1 to 4294967295

Subject: L2TPv3 Service Editor

Explanation The value of the VCD field for PE is not in the required range.

Recommended Action Enter a numeric value in the range 1-4294967295 for PE VCD.

Error Message

PE VCI must be from 33 to 65525

Subject: L2TPv3 Service Editor

Explanation The value of the VCI field for PE is not in the required range.

Recommended Action Enter a numeric value in the range 33-65525 for PE VCI.

Error Message

PE VPI must be from 0 to 255

Subject: L2TPv3 Service Editor

Explanation The value of the VCI field for PE is not in the required range.

Recommended Action Enter a numeric value in the range 0-255 for PE VCI.

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 Customer or 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" not specified. Please select a numeric value in the range 68 - 65535.

Subject: L2TPv3 Policy Editor

Explanation The Max Path MTU field is empty.

Recommended Action Enter a numeric value in the range 68-65535.

Error Message

The value of "Sequencing" 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" 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 not specified. Please select a numeric value in the range 1 - 255.

Subject: L2TPv3 Policy Editor

Explanation The Time To Live field is empty.

Recommended Action Enter a numeric value in the range 1-255.

Error Message

The value of "Type Of Service" not specified. Please select a numeric value in the range 0 - 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-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-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-255 for Type of Service.

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 will 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 will 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 will 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 which has no native vlan already defined or has other vlan defined

Subject: Layer 2 access domain

Explanation For safety reasons, the system will 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 will 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 native vlan defined

Subject: Layer 2 access domain

Explanation For safety reasons, the system will 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 has to 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 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—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 will 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 will 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 support 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 will 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 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 PE-POP and remote PE-POP must be pre-configured.

Recommended Action Set the value manually in PE Devices > Loopback IP Address.

Messages—MPLS Only

Error Message

Can not provision export map since the route map for this name is not found

Explanation Missing corresponding route-map command. 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

Can not provision import map since the route map for this name is not found

Explanation Missing corresponding route-map command. 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 sub-interface {X} on device {Y}.

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 had 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 existed 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 {X} on device {Y}

Explanation When provisioning an interface {X} on a device {Y}, ISC found this interface has a wrong name format.

Recommended Action Verify the syntax for the interface name.

Error Message

Invalid non-FrameRelay encap type {X} for sub-interface {Y} on device {Z}.

Explanation A serial type of subinterface (such as Serial, POS, or HSSI) can only be configured with frame-relay encapsulation.

Recommended Action Make sure the frame-relay encapsulation was assigned for such a subinterface.

Error Message

IP address {X} already assigned to {Y} on device {Z}.

Explanation The specified IP address X has already been assigned to interface Y on device Z.

Recommended Action Either select another IP address or un-assign the IP address from interface Y.

Error Message

IP address {X} already assigned to {Y} with VRF {V} on device {Z}.

Explanation The specified IP address X has already been assigned to interface Y with VRF name V on device Z.

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 MVRFCE.

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 a 2950 device.

Recommended Action Verify the encapsulation type and select the correct one.

Error Message

Secured interface setup mismached 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 {X} on device {Y} does not have frame-relay encapsulation.

Explanation When provisioning a subinterface with frame-relay 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 {W} encapsulation from {X} to {Y} on device {Z}. Check any other active subinterfaces.

Explanation Cannot update a major interface encapsulation type from X to Y. It might have other active subinterfaces configured to encapsulation type X.

Recommended Action Verify the condition from the router's configuration.

Error Message

VLAN ID is required on C3550 MVRF.

Explanation Missing VLAN ID when configuring an Ethernet interface of a 3550 router as MVRF-CE.

Recommended Action Verify that the VLAN ID exists for such a configuration.

Messages—QoS Only

Error Message

Download failure: downloadConfigAndEnableCommands: error pushing config cmd=[bandwidth percent 10], resp=[bandwidth percent 10 All classes with bandwidth should have consistent units enqosce42(config-pmap-c)#].

SR State FAILED-DEPLOY.

Explanation When you configure bandwidth for the classes of service within a QoS policy, all classes must use the same units, that is, all in percentage or all in absolute bandwidth. ISC does not enforce such checking although IOS does, thus the possible error in downloading.

Recommended Action Modify the QoS policy to use either all percentage bandwidth or all absolute bandwidth for all its classes of service and redeploy the QoS Service Request.

Error Message

Download failure: downloadConfigAndEnableCommands: error pushing config cmd=[service-policy output p2], resp=[service-policy output p2 Policy map p1 is already attached enqosce42(config-if)#].

SR State FAILED-DEPLOY.

Explanation There can be only one input policy and one output policy attached to an interface or subinterface. Otherwise, errors result.

Recommended Action 1. If the existing QoS policy was deployed from ISC, modify that QoS Service Request with the new policy and deploy the modified Service Request. 2. Or manually remove the old policy on the router and redeploy the QoS Service Request.

Error Message

"ip cef" not turned on. QoS policy can NOT be provisioned.

SR State INVALID.

Explanation Cisco expedited forwarding (CEF) is required for QoS to be configured on a router. CEF is configured with the ip cef IOS command.

Recommended Action On the router, turn CEF on, and then redeploy the QoS Service Request.

Error Message

Value xxx out of range.

SR State INVALID.

Explanation QoS Parameter value out of range for the Platform in question, for example, Shape rate, Police rate, and so on.

Recommended Action Review the values on the QoS policy and adjust and redeploy the QoS Service Request.

Error Message

<xxx> Command missing.

SR State FAILED-AUDIT.

Explanation IOS might silently ignore without errors or warnings an invalid command upon download. This can be the case if: 1. it is an unsupported platform or IOS version and ISC uses the default support matrix to provision QoS; 2. nested QoS policy is not supported on an Asynchronous Transfer Mode (ATM) permanent virtual circuit (PVC).

Recommended Action 1. Double-check whether this platform and IOS version is supported. 2. Do not configure a nested QoS policy on ATM PVCs.

Error Message

<xxx> Command missing.

SR State FAILED-DEPLOY.

Explanation cRTP (Link Efficiency) command fails if the interface does not have IP unnumbered or IP address on it.

Recommended Action Configure IP unnumbered or IP address on the target interface and redeploy the QoS Service Request.

Error Message

<xxx> Command missing.

SR State LOST.

Explanation After an audit task, a QoS Service Request in DEPLOYED state can go to the LOST state, if some QoS commands provisioned by ISC have been modified on the router.

Recommended Action Redeploy the QoS Service Request again.