Table 8: Troubleshooting Named Receiver Connections show telemetry internal connection : This command takes an optional connection index value. When no index is specified, it displays the basic connection parameter information for all connections that are being used. When a connection index is specified in the command, it shows low-level details about the connection. The command output is transport-specific, and might not be available for all transports. The output from this command is subject to change. show telemetry internal diagnostics : This command attempts to dump all telemetry logs and operational state.
When reporting problems, it may be helpful to use this command as close to the problem time as possible and provide the output of the show running-config | section telemetry command as well. Model-Driven Telemetry Troubleshooting Named Receiver Connections Problem How to Check/Symptom What to Do Subscription is not valid. show telemetry ietf subscription id details Fix the subscription configuration. Subscription receiver is not valid. show telemetry ietf subscription id receiver Fix the named receiver configuration. Subscription receiver’s connection parameters cannot be resolved.
show telemetry ietf subscription id receiver Subscription receiver state appears to never leave the resolving state. Verify the receiver, the network configuration, or the interface state. Subscription receiver connection does not come up. show telemetry ietf subscription id receiver Subscription receiver state constantly changes from resolving to connecting. Verify that the resolved connection is valid, and the receiver or collector is reachable and able to accept inbound connections using the specified transport. Subscription receiver connections are rejected. show telemetry ietf subscription id receiver Subscription receiver state constantly changes through all states except disconnected.
Verify that the collector is of the correct type, and that the configured authentication and authorization is valid. Subscription receiver is connected, but no updates are received. show telemetry internal subscription id stats Message drop count is incrementing, but the records sent is not. Verify that the collector is able to keep up with the flow of update notifications. Subscription receiver is connected, but no updates are received. show telemetry internal subscription No change in the count. If the subscription is on-change, ensure that there really have been no events.
If the subscription is periodic, ensure that the update period is small, that the time is specified in hundredths of a second. Model-Driven Telemetry 28