Problem

When you place an order and the order goes into provisioning but fails during provisioning. Cisco MSX service interface indicates that the order provisioning has failed.

Solution

1. Review the tenant event logs web interface to confirm the error occurred during provisioning and not initial validation.

2. The tenant user needs to escalate this issue to the service provider operator.

   Note	The system will not self-recover even if the unplugged devices are plugged back in.

3. The service provider operator has to login to NSO directly and fix the problem.

   • Ensure that the malfunctioning devices are taken offline.

   • Retry the provisioning operation.

When the NSO provisioning operation completes successfully, it sends the correct notification to the northbound interface, and resets the Cisco MSX service interface to the provisioned state.

Problem

When you place an order and get an order failed message right away (due to first-level call to NSO failing), it means that the order has failed.

Solution

1. Review the tenant Event logs and confirm the error is caused due to first-level call to NSO failing.

2. Deletes the order from the Cisco MSX service interface.

3. Place a new order.

Problem

When you try to order a service, the service ordering fails.

Solution

• Verify if all microservices are running

• Verify orchestration microservice is sending the appropriate provider name to NSO. Confirm that the "Provider Name" is populated correctly by navigating to Settings as an Admin.

• Check NSO netconf-north.log. If not, check connectivity between the Cisco MSX Portal and the NSO.

Problem

The device does not get registered with the PnP server and does not return any error if the tenant user enters an incorrect serial number during registration.

NSO PnP server zero touch provisioning works as:

• Tenant users register a device serial number against a device, which associates a device with a tenant, a site and a device, so Cisco MSX knows what type of configurations to push to this device.

• The connected devices call home to the PnP server, register themselves, and wait for the PnP server to push the configuration.

These events happen in any order and if the tenant user registers a device with a serial number that has not called home to the PnP server, the server waits for the device to call the PnP server. If this device never calls (because the serial number is invalid), the PnP server continues to wait.

Solution

Tenant user needs to register the device with the correct serial number. For more information, see the service pack guides on cisco.com.

Solution

1. Log in to the device and verify to which PNP server the device is connected to.

2. Run command show run | s pnp to list the current PnP server that this device is talking to, and examine the output:

   Router#show run | s pnp pnp
   Router#profile zero-touch transport https ipv4 <IP address> port 443 remotecert ncs 

3. To change the IP address of the PNP server, switch to the configuration mode.

   Router#config terminal 
   Router(config)#

4. Enter text that you received as output in Step 2, replacing the IP address with the new one.

   Router(config)#pnp profile zero-touchtransport https ipv4 <IP address> port 443 remotecert ncs

5. Exit out of Router(config-pnp-init) mode and then out of Router(config) mode.

6. Copy the configuration into flash configuration, by running the following command:

   Router#copy running-config flash:day--1-config
   Destination filename [day--1-config]?
   %Warning:There is a file already existing with this name
   Do you want to over write? [confirm]
   4609 bytes copied in 0.876 secs (5261 bytes/sec)

Blocking of data due to low disk space

The table below lists the issues encountered in Read-Only indices.

PUT .kibana/_settings
{
"index": {
"blocks": {
"read_only_allow_delete": "false"
}
}
}

Device Health Status is Down

The table below lists the issues due to which the device health status is down.

No Device Health Status is Available

The table below lists the issues due to which the device health status may not be available.

Device Metrics are not Available

The table below lists the issues due to which the device metrics may not be available.