NSX Error Codes
Article ID: 314333
Updated On:
Products
VMware NSX
Issue/Introduction
This article provides information on helping customers identify errors and provide recommended actions to correct the errors.
Environment
VMware NSX
Resolution
Edge Routing :
Edge Datapath :
Edge Platform :
| Error Code | Meaning | Recommended Action | |
|---|---|---|---|
| 1 | EDG0200010 | Mempool creation failed in RCPM | Edge node has run out of memory. Contact VMware Technical Support. |
| 2 | EDG0200017 | An error occurred while cloning the message sent by NestDB (to be sent to RCPM) | Memory issue. First, try to put the Edge node into maintenance mode. If the issue persists, restart the Edge node to recover/fix. |
| 3 | EDG0200021 | Mismatch between the size of the Routing Protobuf message and the size of the file where the Routing Protobuf is written. | The filesystem does not have enough space to store the routing config file. Contact VMware Technical Support. |
| 4 | EDG0200024 | Failed to open file(s) for write. | It could also be a disk space issue, or the filesystem is write-protected. Contact VMware Technical Support. |
| 5 | EDG0200026 | Expected object not found in the RCPM DB | The routing DB is not in sync with NestDB. Contact VMware Technical Support. |
Edge Datapath :
| Error Code | Meaning | Recommended Action | |
|---|---|---|---|
| 1 | EDG0400009 | NSXA disconnected, Trace notification dropped | Reboot the Edge. |
| 2 | EDG0400013 | Duplicate IP detected ("UUID_FMT", "IP_FMT") from "ETH_ADDR_FMT | The user needs to find out the duplicated IP and change the configuration of the setup. |
| 3 | EDG0400022 | Too many connections | Reaching max ping/traceroute connections. The user needs to kill other ping/tracert processes or wait for any of them to complete. |
| 4 | EDG0400024 | Invalid VRF ID %d" | The user is not using a valid VRF ID to run ping/tracert commands. |
| 5 | EDG0400073 | lswitch already exists | The user is trying to create an existing logical switch. |
| 6 | EDG0400074 | lswitch for VNI already exists | The user is trying to create a logical switch with VNi used by another logical switch. |
| 7 | EDG0400075 | Maximum number of lswitches reached | 25000 is the maximum number of logical switches. |
| 8 | EDG0400320 | A valid lrouter with VRF ID already exists | The user is trying to create a logical router with a VRF ID that is used by another logical router. |
Edge Platform :
| Error Codes | Meaning | Recommended Action | |
|---|---|---|---|
| 1 | EDG0100010 | Fib update error. | Verify fib entry via CLI: "get forwarding" under respective vrf. |
| 2 | EDG0100032 | lrouter/lswitch port, bridge, l2forwarder, service port is not realised locally | This is a transient state. Wait for stabilized or check the edge configuration. CLI: "get edge-cluster status" |
| 3 | EDG0100127 | Tunnel vtep label not set | Check vtep label configuration from MP via CLI: "get vteps". Additional triage is required why label is not set. |
| 4 | EDG0100130 | VTEP/RTEP label is not set for a xtep | Check vtep label configuration from MP via CLI: "get vteps". Additional triage is required why label is not set. |
| 5 | EDG0100168 | Failed to restart HA FSM | Check edge-cluster and dataplane status via CLI: "get edge-cluster status", "get service dataplane". Check syslog to identify the configuration error and the failure reason around the message "Restart HA FSM". |
| 6 | EDG0100171 | Service router resource update error | Check syslog for any service router configuration errors. |
| 7 | EDG0100265 | NETCPA VXLAN app is not connected | Check ops-agent connection state via CLI: "get service nsx-opsagent". |
| 8 | EDG0100305 | Max span sessions have reached | max span size is reached. Please remove the existing one if a new entry is needed. |
| 9 | EDG0100306 | Max ports per session has reached | Max port limit is reached per session. Please remove the existing port if a new port is needed. |
| 10 | EDG0100372 | Receive configuration error acknowledged from Datapath | Check syslog in subcomp="datapathd" for configuration error. This could be transient. |
| 11 | EDG0100375 | Traceflow message dropped: netcpa not connected | Check ops-agent connection state. Check nsx-opagent service state via CLI:"get service nsx-opsagent". |
| 12 | EDG0100387 | Datapath is not connected | DP component is not connected. Check dataplane service state via CLI: "get service dataplane". |
| 13 | EDG0100391 | Datapath config update failed | DP component is not connected. Check dataplane service state via CLI: "get service dataplane". Check syslog for configuration. |
| 14 | EDG0100393 | Send delta datapath config failed | DP component is not connected. Check dataplane service state via CLI: "get service dataplane". Check syslog for configuration. |
| 15 | EDG0100394 | Datapath is not connected (FW sync) | DP component is not connected. Check dataplane service state via CLI: "get service dataplane". |
| 16 | EDG0100443 | HA session update message validation failed | Error on processing invalid HA update message. Look for any errors before logging "AppHA-rx". This could be transient. |
| 17 | EDG0100494 | Timeout to receive datapath ack for tunnel realisation |
Check any configuration error in subcomp="datapathd" log. Look for any errors before the log "Fail to receive datapath acknowledgement". This could be transient. |
| 18 | EDG0500001 | Client transaction error | RPC(Remote Procedure Call) error. Check syslog for JSON RPC client or JSON protocol validation errors. |
| 19 | EDG0500002 | Logical-Exporter query failed with this error | RPC(Remote Procedure Call) error. Check syslog for JSON RPC client or JSON protocol validation errors. |
| 20 | EDG0500003 | Logical-Exporter query did not return a result | No result in RPC(Remote Procedure Call response). Check syslog for JSON RPC client or JSON protocol validation errors. |
| 21 | EDG0000020 | NestDB is not initialised yet | No NestDB instance. Check for any error log for DB initialisation. |
| 22 | EDG0000057 | Nest DB is not connected while performing a write operation | Check the log to see the connection status to the nestdb server. |
MP to Policy Promotion :
| Error Codes | Meaning | Recommended Action | |
|---|---|---|---|
| 1 | 1400005 | {0} promotion error. Manager id: {1}, Error : {2}. Please contact support. | Check the error in /var/log/proton/nsxapi.log and look for the string 'Unable to migrate' in the log. Please contact support if needed. |
| 2 | 1400006 | {0} promotion error. Logical switch {1} not found in policy or not yet promoted. Please promote the logical switch {1} first. | Promotion failed for the given resource as the logical switch associated with it is not found on the policy/not yet been promoted. Please promote the associated logical switch first. |
| 3 | 1400007 | {0} promotion error. Logical router {1} not found in policy or not yet promoted. Please promote the logical router {1} first. | Promotion failed for the given resource as the logical router associated with it is not found on policy/not yet promoted. Please promote the associated logical router first. |
| 4 | 1400008 | {0} promotion error. Logical router port {1} not found in policy or not yet promoted. Please promote the logical router port {1} first. | Promotion failed for the given resource as the logical router port associated with it is not found on policy/not yet promoted. Please promote the associated logical router port first. |
| 5 | 1400009 | Tier0 Logical router port promotion error. Logical router port {0} not found in the manager. | Promotion failed for Tier0 as the logical router port associated with it was not found on the manager. |
| 6 | 1400010 | Tier0 promotion error. Exception occurred while migrating BGP Neighbour {0}, IP-prefix {1} not found on Policy. | Promotion failed for Tier0's BGP Neighbour as the IP prefix associated with it is not found in the policy. |
| 7 | 1400011 | Tier0 promotion error. Exception occurred while migrating BGP Neighbour {0}, Route-map {1} not found on Policy. | Promotion failed for Tier0's BGP Neighbour as the route-map associated with it is not found in policy. |
| 8 | 1400012 | Tier0 promotion error. Exception occurred while migrating Route map {0}, ip-prefix {1} not found on Policy. | Promotion failed for Tier0's Route map as the IP prefix associated with it is not found in the policy. |
| 9 | 1400013 | Tier0 promotion error. Exception occurred while migrating Route map {0}, community-list {1} not found on Policy. | Promotion failed for Tier0's Route map as the community list associated with it is not found in the policy. |
| 10 | 1400014 | Tier0 {0} promotion error. Error: {1}. | Promotion failed for the given Tier0. Please contact support. |
| 11 | 1400015 | Error while promoting the static route of Tier0. Logical router port not found in policy. manager id : {0}. | Promotion failed for Tier0's static route as the logical router port associated with it is not found in the policy. |
| 12 | 1400016 | Downlink logical router port promotion is not supported in Tier 0 logical router port promotion. RouterPort Id : {0}({1}). | Downlink logical router port promotion is not supported in Tier 0 logical router port promotion. Please refer to the documentation to check the valid configurations. |
| 13 | 1400021 | Static Routes configured with the downlink router port are not supported on policy. | Promotion failed as static routes configured with the downlink router port are not supported on policy. Please refer to the documentation to check the valid configurations. |
MP Edge fabric :
| Error Codes | Meaning | Recommended Action | |
|---|---|---|---|
| 1 | 15001 | The edge transport node is already consumed in another edge cluster |
Either remove the edge transport node from the current edge cluster or Create a new edge transport node and add it to the edge cluster. |
| 2 |
15002 |
The edge transport node identifier provided is not a valid edge transport node identifier. | Check if there is any mismatch between the intended identifier and the identifier used. Use the edge transport node identifier that is configured and in a successful state. |
| 3 | 15004 | The edge transport node provided is already participating in another edge cluster. | Choose a new edge transport node that is not part of any edge cluster. Else, remove this edge transport node from the current edge cluster. This may have traffic disruptions if a Logical router is realised on this edge transport node and serving the edge data path. |
| 4 | 15005 | Only one edge cluster high availability profile can be bound to an edge cluster. | The User should update the edge cluster high availability profile settings present in the edge cluster if the current configuration does not satisfy the requirement. |
| 5 | 15006 |
The deployment type of transport node is not supported in the edge cluster. |
The edge transport node deployment type must be either a virtual machine or a physical machine to participate in an edge cluster. |
| 6 | 15008 | The edge transport node getting added or replaced on the edge clusters does not belong to any transport zones of the current edge transport node. | The new edge transport node, which is replacing the existing edge transport node, should belong to all the transport zones of the current edge transport node. |
| 7 | 15010 | Edge cluster member index is system-allocated and should not be specified for a newly added transport node | Edge cluster member is not a user-provided input. It is system allocated. Remove the member index input provided for the edge transport node that is newly added. |
| 8 | 15011 | Edge cluster member index is system-allocated and cannot be changed. | Edge cluster member index is system-allocated and cannot be changed. Kindly reuse the already assigned member index to the edge cluster member in the edge cluster. |
| 9 | 15012 | Edge cluster member index does not exist. | The member index for which the user wanted to relocate all the logical entities and wants to remove it from the edge cluster is not present in the edge cluster. Kindly provide a valid member index of which user who wants to relocate and remove this member from the edge cluster. |
| 10 | 15015 | Edge cluster members should have homogeneous overlay transport zone endpoints. | Update the overlay transport zone of the edge transport node, which is newly getting added to the same as the existing members of the edge cluster. |
| 11 | 15017 | An invalid edge cluster is provided in the bridge endpoint profile while it is being configured. | The edge cluster ID provided in the bridge endpoint profile is not present in the NSX manager. Provide the correct edge cluster ID on which the bridge endpoint profile needs to be created. |
| 12 | 15019 | Edge transport node replacing an existing edge cluster member in the edge cluster has insufficient resources available on the new transport node for the service pool. | The user should create an edge with sufficient resources and use that edge to replace the current edge. |
| 13 | 15020 | The edge transport node should be in a successful state to add it to the edge cluster. | The user should check why the edge transport node is not in a successful state. Make sure the edge transport node is in a successful state while adding it to the edge cluster. |
| 14 | 15021 | To enable allocation based on failure domain, the edge cluster should have edge cluster members belonging to two different failure domains. | The user should add edge transport nodes that belong to two different failure domains to enable allocation based on failure domains. |
| 15 | 15022 | The edge transport node failure domain cannot be changed, as it hosts logical routers whose placement can be violated if the failure domain gets updated. | Ideally, this should never be the case to updating the failure domain of the edge transport node, as it will affect the allocation based on the failure domain in an edge cluster. If the user still wants to change the failure domain, the user has to move all the logical service contexts out of this edge transport node and try updating the failure domain on the edge transport node. |
| 16 | 15023 | The edge cluster member is not on the transport zone of the bridge endpoint profile. | The user should either update the edge transport node's transport zone or choose the right edge cluster member of the edge cluster that has the transport zone of the bridge endpoint profile to configure the bridge endpoint profile. |
| 17 | 15025 | Invalid edge cluster high availability profile got configured on the edge cluster. | The user should provide a valid edge cluster high availability profile on the edge cluster. |
| 18 | 15026 | The associated edge cluster HA profile BFD probe interval should be greater than 500 milliseconds. | The user should make sure the BFD interval specified in EdgeClusterHaProfile must be greater than 500 milliseconds. |
| 19 | 15031 | None of the other edge cluster members is healthy enough to relocate the logical routers and remove the requested edge cluster member. | The user should create new edge transport nodes and replace the unhealthy ones to perform relocation and remove a specific edge cluster member from the edge cluster. |
| 20 | 15032 | Cannot perform relocate and remove edge cluster member as the user has manually allocated logical service context (logical routers / logical services) are present on this edge cluster member. | Manually allocated logical routers are present. If you still need the relocate and remove API Action, the User should remove the manually allocated logical service contexts (logical routers / logical services) from the edge cluster |
| 21 | 15033 | The edge cluster has only two members. Cannot perform relocate and remove edge cluster member as it will impact the HA of the edge cluster. | User should add a new edge cluster member to the edge cluster and perform relocation, and remove of edge cluster member from the edge cluster. |
| 22 | 15034 |
There is only one healthy edge node other than the one getting removed present in the edge cluster; hence, relocate and removing the edge cluster member is not supported. |
User should add a new edge cluster member to the edge cluster and perform relocation, and remove of edge cluster member from the edge cluster. |
| 23 | 15036 | Relocating and removing the edge cluster member is not supported, as a bridge profile configuration is present in the edge cluster. | User should remove the bridge profile from edge clusters, relocate and remove the not allowed with the bridge profile for the given edge cluster. |
| 24 | 15504 | The edge transport node cannot be deleted as it is still used in the edge cluster. | User removes the edge transport node from the edge cluster and tries deleting the edge transport node. |
| 25 | 15505 | Multiple uplinks used in the active list are not supported for the edge node of type virtual machine. | Multiple uplinks used in the active list are supported on the bare metal edge if the uplink profile is of type load balance. |
| 26 | 15506 | There are no pnics specified in TransportNode backed by Edge | The user has to specify the pic of the edge transport node to be used in the host switches. |
| 27 | 15507 | There are no pnics specified in TransportNode backed by Edge | The user has to specify the pic of the edge transport node to be used in the host switches. |
| 28 | 15508 | Invalid PNIC device name specified | The device name given in the pnic must be a matching with the device name on the edge virtual machine pnics. |
| 29 | 15517 | Multiple overlay transport zones are not supported on the edge node | Keep only one overlay transport zone on an edge transport node. |
| 30 | 15518 | PNIC and device configurations do not match for the transport node. | The configured DPDK fastpath interfaces count should match the transport node pnics that are configured in the host switch. |
| 31 | 16025 | The IP specified in the management port subnets and as node ip_address must be the same. | User must make sure that the IP assigned to the management port subnets and node_ip_address must be the same. |
| 32 | 16037 | The password for the following user does not follow the complexity rules | Password must have at least 12 characters including 1 upper case character, 1 lower case character, 1 numeric digit, 1 special character and at least 5 different characters. Passwords based on dictionary words and palindromes are invalid |
| 33 | 16055 | NSX Manager connectivity with the NSX edge transport node is down | The user should check the connectivity between the NSX Edge and the NSX manager. |
| 34 | 16056 | Uplink is not mapped to a Physical network interface. | All active uplinks in the teaming policies of the HostSwitch Profile must be mapped in HostSwitch. |
| 35 | 16057 | Edge node registration timed out. | Use the join management plane CLI from the edge node to register the node. |
| 36 | 16062 | Replacing an auto-deployed VM with a manually deployed edge VM is not recommended. | Auto auto-deployed edge cluster member can be replaced with another auto-deployed edge transport node only. Create a new edge transport node from the NSX manager UI or over the REST api and use that to replace the edge transport node. |
| 37 | 16083 | Edge configuration request has duplicate entries for advanced configuration | Remove the duplicate keys of advanced configuration and retry the edge update api. |
| 38 | 16084 | Edge advanced configuration with keys <> is not allowed. | Provided the advanced configuration key is not supported. Remove the invalid key and retry the operation. |
| 39 | 16085 | Edge advanced configuration with keys is not allowed to be edited. Use edge redeploy to update the advanced configuration. | Edge advanced configuration cannot be edited using the update edge api. Use the edge redeploy api to update the advanced configuration. |
| 40 | 16086 | This error code is displayed in Edge TN state when Edge Node Settings on MP intent are different from those on CLI | This edge TN configuration state mismatch can be resolved from the UI. |
| 41 | 16087 | This error code is displayed in Edge TN state when Edge vSphere Settings on MP intent are different from those on VC | This edge TN configuration state mismatch can be resolved from the UI. |
| 42 | 16088 | This error code is displayed in Edge TN state when Edge Node Settings and vSphere Settings on MP intent are different from those on the CLI and on the VC | This edge TN configuration state mismatch can be resolved from the UI. |
| 43 | 16089 | This error code is displayed in Edge TN state when, Edge Node is vMotioned and the Edge node storage, compute IDs on VC are changed as compared to on MP intent | This edge TN configuration state mismatch can be resolved from the UI. |
| 44 | 16095 | Advanced configuration edit failed for Edge as key value pairs changed at both places, VsphereDeploymentConfig and EdgeNodeSettings. | Please modify values at one place only, preferably EdgeNodeSettings. |
| 45 | 16109 | Management port subnet IP and Default gateway addresses should have the same IP version | In the case of Edge TN Deployment, the Gateway and Management IP should belong to the same IP family, e.g. IPv4 or IPv6. |
| 46 | 16110 | An invalid IP address format is provided. | The provided IP address is not valid. Provide the correct format of the given IP. |
| 47 | 16111 | Management IP and default gateway are mandatory with a static IPv6 assignment type | In the case of IPv6 and dual-stack edge TN deployment, in API, if the ipv6_assignment_type param is provided and the management IP and default gateway fields are not present in the request, then hit this error. Please provide both management_port_subnets and default_gateway_addresses values in the request. |
| 48 | 16112 | Invalid coalescing scheme configured on edge. | Supported coalescing schemes are ["rbc", "adapt", "disabled", "static"]. The coalescing scheme must have one of these supported values. |
| 49 | 16113 | Invalid coalescing param configured on edge. | The Coalescing parameter can be either between 100-100000 for the coalescing scheme "rbc" and between 1-64 for the coalescing scheme "static". Adapt and disabled do not take any parameters. |
| 50 | 16114 | IPv6 assignment type value is missing in the request | In the case of IPv6 and dual-stack edge TN deployment, in API, if the IPv6_assignment_type param is not provided and the management IP and default gateway fields are present in the request, then hit this error. Please provide both IPv6_assignment_type values in the request. |
| 51 | 16115 | IP address update not allowed for the edge | In the case of IPv4, Address update is not allowed, so configuration of IPv4 is allowed during Edge TN Creation. For IPv6, only a single-time configuration is allowed. |
| 52 | 16116 | IP address is already configured on the edge | If the same IPv6 Address is provided in Edge TN, then it will hit this error. Provide a different IP address in the request. |
| 53 | 16117 | The coalescing parameter must be configured for the coalescing scheme on the edge. | The coalescing parameter must be configured for the coalescing scheme on the edge. For the ''rbc'' scheme, the supported value range is 100 - 100000. For the ''static'' scheme, the supported value range is 1 - 64. ''adapt'' and ''disabled'' do not accept the coalescing parameter. |
| 54 | 16020 | The deployment of the edge VM has failed | Check error details in Proton logs nsxapi.log and at the VC. Correct parameters if required and retry. |
| 55 | 16021 | The power on of the edge VM has failed | Check if sufficient resources are available at VC. |
| 56 | 16022 | The power off of the edge VM has failed | Check error details in Proton logs nsxapi.log and at the VC. |
| 57 | 16023 | The deletion of the edge VM has failed | Check error details in Proton logs nsxapi.log and at the VC. |
| 58 | 16035 | Transport node configuration needs to be updated for this Edge Node | Configure the Edge transport node. |
| 59 | 16040 | Edge VM rename failed | Check error details at VC. Check that the name is not already used by other VMs at the VC. |
| 60 | 16041 | Edge network reconfigure failed | Check error details at VC. |
| 61 | 16042 | Edge node configuration update failed. | Check edge VM - Manager connectivity. |
| 62 | 16054 | Edge resource reservation failed | Check if sufficient resources are available at VC. |
| 63 | 16067 | Delete VM failed during redeploy. | If the VM is accessible, delete the VM at vSphere and then retry redeploy. |
| 64 | 16082 | Edge advanced configuration edit failed. | Failed to set the Dataplane DynamicCore transport node. Check edge tech support logs for further details. |
| 65 | 16091 | An error occurred when refreshing the edge config. Referenced compute manager is not found. | Update placement references using API transport-nodes/<node-id>?action=addOrUpdatePlacementReferences. |
| 66 | 16107 | This error code is displayed in the Edge TN state api when Edge Node deletion fails due to the VM not being found in VC. | Follow the alarm's recommended action. |
| 67 | 16108 | This error code is displayed in the Edge TN state api when Edge Node deletion fails for Non Non-LCM edge. | Follow the alarm's recommended action. |
Multi-tenancy :
| Error Codes | Meaning | Recommended Action | |
|---|---|---|---|
| 1 | 524129 | The paths {0} cannot be accessed from {1} as the paths neither belong to its scope nor are shared with it. | Please provide paths in the same tenant's scope or please share them with tenant. |
| 2 | 524131 | Invalid member type {0} provided in a Project group {1}. | Make sure the member type provided is only VirtualMachine. |
| 3 | 524217 | Project segment {0} is not allowed to connect to Tier0 {1}. Please connect to Tier1. | Project segment is not allowed to be connected to Tier0. Please connect to Tier1. |
| 4 | 524223 | This API is not supported in the context of a Project. | This API is not supported in the context of a Project. |
| 5 | 524225 | short_id must contain only ASCII characters. | Please provide only ASCII characters in short_id. |
| 6 | 524227 | Following resources are not allowed for sharing [{0}] | Make sure valid resource type & path is shared. Please refer api documentation for valid shared resource types. |
| 7 | 524228 | Shared resource objects path=[{0}] cannot be unshared as it is being consumed by other objects path=[{1}] | Since some objects are consuming this shared object, it cannot be unshared. Please de-reference it from consuming objects to continue to remove share. |
| 8 | 524230 | Load Balancer pool_allocation is not supported for Multi Tenancy. | Load Balancer pool_allocation is not supported for Multi Tenancy. |
| 9 | 524233 | short_id {0} already exists for another {1}. | Please use different short_id because given short_id is already being used by another object. |
| 10 | 524234 | short_id once set cannot be modified. | short_id cannot be modified. |
| 11 | 524235 | short_id must contain less than or equal to {0} characters with no spaces. | Maximum allowed length for short_id is 8, please provide short_id without spaces and less than 8 in length. |
| 12 | 524255 | Invalid DNS server IPAddress [{0}]. | Please use ipv4 ip address for DNS server. |
| 13 | 524259 | Label {0} can have only 1 reference object of type {1}. | Label can have only one reference object of type mentioned in error message. |
| 14 | 524260 | The reference object in Label {0} should have resource of type {1}. | The reference object in Label should have resource of type mentioned in error message. |
| 15 | 524272 | Cannot disable N-S Service router as {0} user defined Nat Rule exists. Please remove the nat rules first then try disabling the N-S services. | Please remove the nat rules first then try disabling the N-S services. |
| 16 | 524279 | tier_0s paths {0} in dedicated_resources must be of resource type {1}. | Please make sure that the dedicated resource is of type Tier-0 or a Label. |
| 17 | 524280 | tier_0s paths {0} in dedicated_resources must also be present in tier_0s argument in project payload. | Please make sure that the tier-0 provided in the dedicated_resources is associated with the project. |
| 18 | 524281 | tier_0s paths {0} in dedicated_resources is already associated with another project. | Please make sure that the tier-0 provided in the dedicated_resources is not in the dedicated_resources of other projects. |
| 19 | 610744 | Allocated Tier-0 {0} cannot be consumed in gateway firewall under custom project {1} | Allocated Tier-0 to Project cannot be consumed in gateway firewall under custom project. |
| 20 | 610745 | Allocated Tier-0 {0} cannot be consumed in labels under custom project {1} | Allocated Tier-0 to Project cannot be consumed in labels under custom project. |
Inventory :
| Error Codes | Meaning | Recommended Action | |
|---|---|---|---|
| 1 | 7007 | VM object from host {0} does not have identifiers set. Incoming VM data: {1} | Check if host is in vSphere maintenance mode. |
| 2 | 7013 | Unable to find virtual machine with external identifier (instance UUID in VC) {0}. | Check if virtual machine with given external identifier (instance UUID in VC) exists. |
| 3 | 7026 | Sorting is not allowed on field {0} unless a filter is provided for field {1} | Provide host_id/source in request parameter to use sorting on field local_id_on_host/host local id. |
| 4 | 7027 | Node with this IP {0} was recently deleted and is being cleaned up. Please retry configuring after some time. | Please retry configuring host after some time. |
| 5 | 7030 | System tags cannot be added/modified/deleted, {0}. | System tags are not allowed for any user modification. Please refer to /api/v1/configs/reserved-tags to find system tag scopes. |
| 6 | 7031 | Discovered tags cannot be added/modified/deleted, {0}. | Discovered tags are not allowed for any user modification. Discovered tag scope starts with "dis:". |
| 7 | 7032 | Exceeded limit on number of user defined tags for VM, supports only {0} | Reduce the number of user defined tags for this VM below the supported limit. |
| 8 | 7034 | Unable to find valid node corresponding to node id {0}. | Transport nodes of type host or PCG are the only supported options. |
| 9 | 7036 | Unable to determine Client Type for host Id {0}. | Check if host is successfully configured with NSX or not. |
| 10 | 7038 | Could not clean up data for {0} with id {1}. | Operation will be retried again. |
| 11 | 7039 | VM object from host {0} does not have external id set. Incoming VM data: {1} | Check if host is in vSphere maintenance mode. |
| 12 | 7047 | Cannot register compute manager, user name is blank or empty | Provide user name for vCenter. |
| 13 | 7048 | Cannot register compute manager, password is blank or empty | Provide password for user of vCenter. |
| 14 | 7049 | Cannot register compute manager, server thumbprint is blank or empty. Found thumbprint {0} for server. If correct, please re-submit with this thumbprint |
Please verify if the thumbprint specified in the error message is correct and re-submit. |
| 15 | 7050 | Cannot register compute manager. Server {0} already registered with NSX | Check if compute manager is already registered with NSX. |
| 16 | 7051 | Could not clean up data for compute manager {0}, will be retried in next run | Data cleanup operation will be retried in the next run in 30 secs. |
| 17 | 7052 | Compute manager server {0} already exists. Existing compute manager with this server is {1} | Provide correct compute manager IP/FQDN. |
| 18 | 7054 | Compute manager {0} type input {1} is not valid. Supported compute manager server type {2} | Ensure the compute manager server is of type vCenter. |
Context Engine :
| Error Codes | Meaning | Recommended Action | |
|---|---|---|---|
| 1 | CTX3 |
Error in initializing context core |
Restart opsagent process |
| 2 | CTX4 | Error path in code was executed | Restart opsagent process |
| 3 | CTX31 |
Error in pthread mutex destroy |
Thread related errors come from the thread library and cannot be easily resolved. If they are persistent, restart opsagent |
| 4 | CTX32 |
Error in pthread lock destroy |
Thread related errors come from the thread library and cannot be easily resolved. If they are persistent, restart opsagent |
| 5 | CTX33 |
Error in pthread condition destroy |
Thread related errors come from the thread library and cannot be easily resolved. If they are persistent, restart opsagent |
| 6 | CTX34 |
Error in pthread condition wait |
Thread related errors come from the thread library and cannot be easily resolved. If they are persistent, restart opsagent |
| 7 | CTX35 |
Error in pthread condition timed wait |
Thread related errors come from the thread library and cannot be easily resolved. If they are persistent, restart opsagent |
| 8 | CTX36 |
Error in mutex unlock fail |
Thread related errors come from the thread library and cannot be easily resolved. If they are persistent, restart opsagent |
| 9 |
CTX283 |
VM VC UUID is empty |
Fill vm UUID |
| 10 |
CTX305 |
Error in parsing XML |
Check the Health message XML file. |
DHCP,DNS,NAT & MDProxy :
Proton :
Metadata Proxy :
| Error Codes | Meaning | Recommended Action | |
|---|---|---|---|
| 1 | [MetadataProxy] MP22501 | Secret of MetadataProxy is mandatory. | Provide the secret for the MetadatProxy |
| 2 | [MetadataProxy] MP22502 | EdgeCluster specified in MetadataProxy is not found. | Make sure the edge cluster existing |
| 3 | [MetadataProxy] MP22503 | EdgeCluster member index is NOT found in EdgeCluster specified in MetadataProxy. | Check the member index of the edge cluster to make sure member existing |
| 4 | [MetadataProxy] MP22504 | MetadataProxies exceeds maximum. | Delete the not used MetadataProxy |
| 5 | [MetadataProxy] MP22505 | Invalid server url with error. | Check the server url to make sure the url format is right |
| 6 | [MetadataProxy] MP22506 | CA with identifier is not found. | Check if the CA existing and change the CA id to the existed one |
| 7 | [MetadataProxy] MP22509 | Invalid schema in server url. Valid schemas are http and https. | Provide the valid schema in server url |
| 8 | [MetadataProxy] MP22510 | Invalid host name in server url. | Provide the valid host name in server url |
| 9 | [MetadataProxy] MP22511 | Invalid port in server url. Valid port range is 3000 ~ 9000. | Provide the valid port between 3000 ~ 9000 in server url |
| 10 | [MetadataProxy] MP22512 | Invalid IP in server url. 0.0.0.0, 255.255.255.255 and 127.0.0.0 ~ 127.255.255.255 can not be used as server ip. | Provide the valid IP in server url |
| 11 | [MetadataProxy] MP22513 | Invalid server url. Localhost can not be used as server name | Avoid localhost is used as server name |
| 12 | [MetadataProxy] MP22514 |
Invalid server url. Domain name length exceeds maximum. |
Provide short domain name |
Policy :
DHCP & DHCP relay :
| Error Codes | Meaning | Recommended Action | |
|---|---|---|---|
| 1 |
[DHCP] MP503017 |
Invalid DHCP range input specified. | Provide the vaild DHCP range |
| 2 | [DHCP] MP503027 | DHCP address pool dhcp ranges has overlapping IP addresses. | Reset IP of Dhcp ranges, it cannot overlap with other Dhcp ranges |
| 3 | [DHCP] MP503028 | DHCP address pool overlaps with gateway address. | Reset IP of Dhcp Pool, it cannot overlap with gateway address |
| 4 | [DHCP] MP503059 | Invalid DHCP server configuration. | Provide the valid DHCP server configuration |
| 5 | [DHCP] MP503063 | Invalid DHCP server IP address specified. | Provide the valid DHCP server IP address |
| 6 | [DHCP] MP503218 | DHCP static IP address overlaps with DHCP range. | Reset DHCP static IP address, it cannot overlap with DHCP range |
| 7 | [DHCP] MP503219 | DHCP server is not configured for segment path. | Provide the valid DHCP server for segment path |
| 8 | [DHCP] MP503221 | Failed to realize DHCP range on segment. | Retry to realized DHCP range |
| 9 | [DHCP] MP503222 | Only one server address per IPv4 and IPv6 address family allowed. | Ensure one server address per IPv4 and IPv6 address |
| 10 | [DHCP] MP503223 | Invalid generic DHCP option code specified | Provide the valid generic DHCP option code |
| 11 | [DHCP] MP503224 | Duplicate value specified in DHCP static binding | Ensure unique value in DHCP static binding |
| 12 | [DHCP] MP503226 | Failed to realize DHCP server on segment | Retry to realized DHCP server |
| 13 | [DHCP] MP503236 | Invalid number of values specified for option of allowed value count. | Reset number of values for DHCP option |
| 14 | [DHCP] MP503237 | Input exceeds max character count for option of max input size chars. | Reduce character count for option |
| 15 | [DHCP] MP503238 | Invalid value specified for DHCP option. | Provide the valid value for DHCP option |
| 16 | [DHCP] MP503240 | DHCP static config preferred time should be less than lease time. | Ensure preferred time is less than lease time in DHCP static configuration |
| 17 | [DHCP] MP503242 | DHCP static IP address cannot be same as server address. | Reset DHCP static IP address, it cannot be same as server address |
| 18 | [DHCP] MP503243 | DHCP address pool overlaps with server addres. | Reset DHCP address pool, it cannot overlap with server addres |
| 19 | [DHCP] MP503247 | Only local DHCP server configuration is supported for IPv6 DHCP. | Configure local DHCP server configuration for IPv6 DHCP |
| 20 | [DHCP] MP503262 | Modification of gateway connectivity impacts DHCP enabled workloads. If you would like to proceed, retry with '?force=true' parameter. | Avoid to modify gateway connectivity |
| 21 | [DHCP] MP503265 | Segment has static binding configuration. subnet DHCP configuration cannot be removed. | Aovid to remove subnet DHCP configuration while segment has static binding configuration |
| 22 | [DHCP] MP503267 | Duplicate value from segment path specified in DHCP static binding. | Ensure unique value from segment path in DHCP static binding. |
| 23 | [DHCP] MP503274 | DHCP configuration cannot be changed from relay to local DHCP server or gateway DHCP server. | Avoid to modify DHCP configuration from relay to local DHCP server or gateway |
| 24 | [DHCP] MP503290 | Connectivity path (segment, tier-0, or tier-1 path) is required to retrieve DHCP server runtime information. | Fetch DHCP server runtime information for Connectivity path |
| 25 | [DHCP] MP503291 | DHCP server config is not used. | Check if DHCP server config is not used |
| 26 | [DHCP] MP503292 | Edge cluster property cannot be removed while DHCP server config is in use at segment | Avoid to remove edge cluster property while DHCP server config is in use at segment |
| 27 | [DHCP] MP503293 | Gateway address in DHCP static binding does not belong to subnet. | Avoid to configure gateway address in DHCP static binding that it cannot belong to subnet. |
| 28 | [DHCP] MP503391 | Duplicate value specified for DHCP configuration property. | Ensure unique value for DHCP configuration property |
| 29 | [DHCP] MP503392 | Duplicate DHCP option code specified. | Ensure unique DHCP option code |
| 30 | [DhcpRelay] MP503060 | Invalid DHCP relay configuration. | Provide the valid DHCP relay configuration |
| 31 | [DhcpRelay] MP503251 | DHCP relay requires tier-0/tier-1 gateway connectivity. | Configure DHCP relay for tier-0/tier-1 |
| 32 | [DhcpRelay] MP503396 | Interface DHCP relay does not support DHCPv6 servers | Avoid to coinfigure DHCPv6 servers in interface DHCP relay |
DNS Forwarder :
| Error Codes | Meaning | Recommended Action | |
|---|---|---|---|
| 1 | [DnsForwarder] MP504001 | Upstream server cannot be null in a DNS Forwarder Zone. | Provide the valid upstream server in DNS Forwarder Zone |
| 2 | [DnsForwarder] MP504002 | Invalid domain name passed in DNS Forwarder Zone. | Provide the valid domain name in DNS Forwarder Zone |
| 3 | [DnsForwarder] MP504003 |
DNS Forwarder Zone cannot have more than {0} upstream servers. {0}: 3 |
Avoid configuring more than 3 upstream server. |
| 4 | [DnsForwarder] MP504004 |
DNS Forwarder Zone cannot have more than {0} domain names. {0}: 100 |
Avoid configuring more than 100 DNS Forwarder Zone. |
| 5 | [DnsForwarder] MP504005 | Listener IP for DNS forwarder is invalid. | Provide the valid listener IP in DNS forwarder |
| 6 | [DnsForwarder] MP504007 | Forwarder zone path provided in DNS Forwarder does not exist. | Provide the valid DNS Forwarder Zone path in DNS Forwarder |
| 7 | [DnsForwarder] MP504008 | Default forwarder zone cannot have DNS Domain Names populated. | Remove DNS Domain Names from Default forwarder zone |
| 8 | [DnsForwarder] MP504009 | Conditional forwarder zone should have DNS Domain names populated. | Provide the valid DNS Domain names in Conditional forwarder zone |
| 9 | [DnsForwarder] MP504011 | Invalid logical router instance for DNS forwarder path. | Provide the invalid logical router instance for DNS forwarder path |
| 10 | [DnsForwarder] MP504012 | Listener IP overlaps with the upstream server IP. Listener IP cannot overlap with upstream server IPs. | Use different lisener IP, and it cannot be the same with upstream server IPs |
| 11 | [DnsForwarder] MP504013 | DNS Domain Name from Conditional Forwarder Zone path is present in two or more Conditional Forwarder Zones for the DNS Forwarder path. | Use unique DNS Domain Name from Conditional Forwarder Zone in two or more Conditional Forwarder Zones for the DNS Forwarder path |
| 12 | [DnsForwarder] MP504015 | DNS Domain Name in a Conditional Forwarder Zone cannot be longer that characters. | Provide short DNS Domain Name in a Conditional Forwarder Zone |
| 13 | [DnsForwarder] MP504016 | Duplicate upstream servers not allowed in DNS Forwarder Zone. | Use unqiure upstream servers in DNS Forwarder Zone |
| 14 | [DnsForwarder] MP504017 | Unsupported HA mode of targeted logical router path. DNS forwarder can run only on ACTIVE_STANDBY logical router. | Put DNS forwarder on ACTIVE_STANDBY logical router |
| 15 | [DnsForwarder] MP504018 | Unable to clear cache for DNS forwarder-path on enforcement point-path with Error. | Please check DNS forwarder-path on enforcement point-path |
| 16 | [DnsForwarder] MP504019 | Invalid address, for DNS lookup. The address should be a fqdn less than 254 characters, or an ipv4 address except 0.0.0.0, 255.255.255.255. | Provide the valid IP address for DNS lookup |
| 17 | [DnsForwarder] MP504020 | Unable to fetch the nslookup result for DNS forwarder path, address, from enforcement point path with Error. | Please check DNS forwarder path, address, from enforcement point path |
| 18 | [DnsForwarder] MP504021 | Unable to get the status of DNS forwarder path from enforcement point path with Error. | Please check DNS forwarder path from enforcement point path |
| 19 | [DnsForwarder] MP504022 | Unable to get the statistics of DNS forwarder path from enforcement point path with Error. | Please check DNS forwarder path from enforcement point path |
| 20 | [DnsForwarder] MP504023 | DNS forwarder path is disabled. | Enable DNS forwarder |
| 21 | [DnsForwarder] MP504024 | Source IP for DNS forwarder zone is invalid. | Provide the valid Source IP for DNS forwarder zone |
| 22 | [DnsForwarder] MP504025 | Upstream server IP for DNS forwarder zone is invalid. | Provide the valid Upstream server IP for DNS forwarder zone |
| 23 | [DnsForwarder] MP504026 | Duplicate domain names not allowed in DNS forwarder zone. | Use unique for domain names in DNS forwarder zone |
| 24 | [DnsForwarder] MP504033 | DNS forwarder is not supported on VRF Tier0. | Avoid to configure DNS forwarder on VRF Tier0 |
Metadata Proxy :
| Error Codes | Meaning | Recommended Action | |
|---|---|---|---|
| 1 | [MetadataProxy] MP524201 | Invalid edge cluster in metadata proxy. | Provide the valid edge cluster in metadata proxy |
| 2 | [MetadataProxy] MP524202 | Invalid edge node in metadata proxy. | Provide the valid edge node in metadata proxy |
| 3 | [MetadataProxy] MP524203 | Edge node not a member of cluster. | Ensure the edge node is a member of the cluster |
| 4 | [MetadataProxy] MP524204 | Maximum limit for metadata proxies reached. | Reduce metadata proxies number |
| 5 | [MetadataProxy] MP524205 | Invalid certificate in metadata proxy. | Provide the valid certificate in metadata proxy |
| 6 | [MetadataProxy] MP524206 | Malformed server address in metadata proxy. | Provide the valid server address in metadata proxy |
| 7 | [MetadataProxy] MP524207 | Invalid port in server address in metadata proxy. | Provide the valid port in server address in metadata proxy |
| 8 | [MetadataProxy] MP524208 | Invalid schema in server url in metadata proxy. Valid schemas are http and https. | Provide the valid schema in server url in metadata proxy |
| 9 | [MetadataProxy] MP524209 | Invalid IP in server url. 0.0.0.0, 255.255.255.255 and 127.0.0.0 ~ 127.255.255.255 can not be used as server IP. | Provide the valid IP in server url |
| 10 | [MetadataProxy] MP524210 | Invalid server url. Domain name length exceeds maximum. | Reduce Domain name length |
| 11 | [MetadataProxy] MP524211 | Invalid server url. Localhost can not be used as server name. | Avoid to use localhost as server name. |
| 12 | [MetadataProxy] MP524212 | Invalid host name in server url. | Provide the valid host name in server url |
| 13 | [MetadataProxy] MP524213 | Edge cluster members must be empty to enable standby relocation in metadata proxy. | Ensure Edge cluster members are empty, the can enable standby relocation in metadata proxy |
NAT :
| Error Codes | Meaning | Recommended Action | |
|---|---|---|---|
| 1 | [NAT] MP508001 | NAT can have only one service entry. | Ensure one service entry for NAT |
| 2 | [NAT] (MP508002 - refactored to MP508024 NAT_INVALID_CIDR) | Invalid Source Network. | Provide the valid Source Network |
| 3 | [NAT] MP508003 - refactored to MP508024 NAT_INVALID_CIDR | Invalid Destination Network. | Provide the valid Destination Network |
| 4 | [NAT] MP508004 - refactored to MP508024 NAT_INVALID_CIDR | Invalid Translated Network. | Provide the valid Translated Network |
| 5 | [NAT] MP508005 | Invalid Translated Ports. | Provide the valid Translated Ports |
| 6 | [NAT] MP508006 | Invalid scope path, Scope path for NAT rule must be of type Tier1, Tier1Interface, Tier0, Tier0Interface, LocaleService or Label with references of said types. | Provide the valid scope path |
| 7 | [NAT] MP508007 | There should be exactly one service entry in service path. | Ensure one service entry in service path |
| 8 | [NAT] MP508008 | Invalid NAT Id. | Provide the valid NAT Id |
| 9 | [NAT] MP508009 | Invalid sequence number passed for NAT, valid values are for INTERNAL NAT section range is 0 - 1023, USER section 0 - 2147481599 and for DEFAULT section 0 - 1023. | Provide the valid sequence number passed for NAT |
| 10 | [NAT] MP508010 | NAT object with id is null or does not exist. | Check if NAT object is vaild |
| 11 | [NAT] MP508011 | Invalid destination port in service entry of service path. For NAT rule, destination port value should be a single port. | Provide a single port as destination port |
| 12 | [NAT] MP508012 | NAT action is not supported on the HaMode. | Current NAT rule is not supported on the HaMode, change NAT rule type |
| 13 | [NAT] MP508013 | Realized NAT rule for realized path does not exist. | Re-realize the NAT rule |
| 14 | [NAT] MP508014 | Realized NAT rule is already exists with realized path. Not creating new one. | Execute update instead of creation |
| 15 | [NAT] MP508015 | The tier-0 interface path must belong to the same tier-0 path for which the NAT Rule is created. | Ensure tier-0 interface path is belong to the same tier-0 path while the NAT Rule is created |
| 16 | [NAT] MP508016 | NAT rule does not support service entry type. | Avoid to configure service entry type for current rule |
| 17 | [NAT] MP508017 | Invalid Label path is specified in scope for NAT Rule. | Provide the valid Label path in scope for NAT Rule |
| 18 | [NAT] MP508018 | Realization path for scope with path not found. Failed to get uplink logical router port from MP. NAT rule realization failed. | Provide the valid label path in scope for NAT Rule |
| 19 | [NAT] MP508019 | By adding this NAT rule, the count of NAT rules on MP will exceed maximum rules allowed for a logical router. | Reduce the count of NAT rules for the logical router |
| 20 | [NAT] MP508020 | Unable to get NAT rule count for logical router from MP. | Check connectivity between Policy and MP |
| 21 | [NAT] MP508021 | Disallow different IP address count for NAT rule. | User same IP address count for NAT rule |
| 22 | [NAT] MP508022 | IP range is not supported for NAT rule. | Use single IP for NAT rule |
| 23 | [NAT] MP508023 | IP list is not supported for NAT rule. | Use single IP for NAT rule |
| 24 | [NAT] MP508024 | Invalid CIDR in rule. | Provide the valid CIDR in rule |
| 25 | [NAT] MP508025 | Invalid IP format. | Provide the valid IP address |
| 26 | [NAT] MP508026 | 1:M SNAT is not supported. | Configure other mapping type for SNAT |
| 27 | [NAT] MP508027 | The loopback address can not be used as translated IP(s). | Avoid loopback address as translated IP(s) |
| 28 | [NAT] MP508028 | Entity is mandatory for NAT. | Ensure mandatory entity for NAT |
| 29 |
[NAT] MP508029 |
Entity must be empty for NAT. | Ensure entity is empty for NAT |
| 30 | [NAT] MP508030 | Default scope path for NAT rule is empty | Ensure default scope path is not empty |
| 31 | [NAT] MP508033 | Invalid IP address. Quad-zero address 0.0.0.0 is disallowed in NAT. | Provide the valid IP address |
| 32 | [NAT] MP508034 | Invalid IP format. IP list must be of IPv4 addresses only. | Provide the valid IPv4 addresses only |
| 33 | [NAT] MP508035 | Invalid NAT rule action for HA mode. Only REFLEXIVE action is supported on ACTIVE-ACTIVE stateless router. | Use REFLEXIVE rule on ACTIVE-ACTIVE stateless router |
| 34 | [NAT] MP508036 | The Tier1 router path as scope must be the same Tier1 path under which the NAT Rule is created. | Ensure Tier1 router path as scope is belong to the same Tier1 path |
| 35 | [NAT] MP508037 | The valid values for scope under Tier1 NAT rule are Tier1 Interface or Label with references of said types. | Provide the valid scope under Tier1 |
| 36 | [NAT] MP508038 | The Tier0 path as scope must be the same tier0 router path under which the NAT Rule is created. | Ensure Tier0 path as scope is belong to the same tier0 router path |
| 37 | [NAT] MP508039 | Unable to get NAT rule stats for logical router from MP. | Please check logical router status |
| 38 | [NAT] MP508040 | Nat Rule with path is not yet realized. | Re-realize the Nat rule |
| 39 | [NAT] MP508042 | The tier-1 interface path must belong to the same tier-1 path for which the NAT Rule is created. | Ensure tier-1 interface path is belong to the same tier-1 path |
| 40 | [NAT] MP508043 | Only BYPASS is supported for firewall_match on a NO_SNAT/NO_DNAT rule. But entity is provided. | Ensure firewall_match with BYPASS |
| 41 | [NAT] MP508044 | Label updation is invalidating the object path. | Check Lablel of the object path |
| 42 | [NAT] MP508045 | The valid values for scope under Tier0 NAT rule are Tier0 Interface and label containing Tier0 interfaces. | Provide the valid scope with Tier0 Interface |
| 43 | [NAT] MP508048 | Invalid IPv6 address. Should be the list of IPv6 address. | Provide the valid IPv6 address |
| 44 | [NAT] MP508049 | Invalid NAT64 firewall_match type. Should be null or BYPASS. | Provide the valid NAT64 firewall_match type |
| 45 | [NAT] MP508050 | Invalid NAT64 action. Should be NAT64 only. | Use NAT64 rule |
| 46 | [NAT] MP508051 | Invalid NAT64 embedded IPv4 address from destination address. | Provide the valid NAT64 embedded IPv4 address from destination address |
| 47 | [NAT] MP508052 | Invalid NAT64 translated address. Should be single IP address, IP set or IP range and do not use multicast/broadcast/loopback/reserved/any address. | Provide the valid NAT64 translated address |
| 48 | [NAT] MP508053 | All zero IPv6 address is not allowed. | Avoid to use all zero IPv6 address |
| 49 | [NAT] MP508054 | Fail to create IP object. | Please check IP format |
| 50 | [NAT] MP508055 | Invalid NAT64 destination IPv6 address prefix. Should be 96 or 128. | Provide the valid NAT64 destination IPv6 address prefix with 96 or 128 |
| 51 | [NAT] MP508056 | Invalid NAT64 scope. Should be up-link or router-link. | Provide the valid NAT64 scope with up-link or router-link |
| 52 | [NAT] MP508057 | Invalid NAT64 destination IPv6 address. IPv6 multicast prefix is not allowed. | Provide the valid NAT64 destination IPv6 address, it cannot be IPv6 multicast prefix |
| 53 | [NAT] MP508058 | Invalid NAT64 service entry. Only TCP or UDP service entry is supported. | Provide the valid NAT64 service entry with TCP or UDP service entry |
| 54 | [NAT] MP508059 | Invalid NAT64 translated address. Composite addresses are not allowed. | Provide the valid NAT64 translated address, it cannot be composite addresses |
| 55 | [NAT] MP508060 | Invalid NAT64 translated address. CIDR is not allowed. | Provide the valid NAT64 translated address, it cannot be CIDR |
| 56 | [NAT] MP508061 | Provider interface IP address cannot be a loopback IP. | Avoid to use loopback IP as interface IP address |
| 57 | [NAT] MP508062 | The tier-0 interface type is not supported for the NAT scope path. | Avoid to use tier-0 interface type as NAT scope path |
Feedback
Yes
No
Powered by
