Troubleshoot using Introspect

Introspect

For vRouter-agent debugging, we use Introspect. You can access the Introspect data at http://<host server IP>:8085. Here is a sample of the Introspect data:

Table 1: Modules shown in contrail-vrouter-agent debug output
Link	and Description
agent.xml	Shows agent operational data. Using this introspect, you can see the list of interfaces, VMs, VNs, VRFs, security groups, ACLs and mirror configurations.
agent_ksync.xml	Shows agent ksync layer for data objects such as interfaces and bridge ports.
agent_profile.xml	shows agent operdb, tasks, flows, and statistics summary.
agent_stats_interval.xml	View and set collection period for statistics.
controller.xml	Shows the connection status of the jcnr-controller (cRPD)
cpuinfo.xml	Shows the CPU load and memory usage on the compute node.
ifmap_agent.xml	Shows the current configuration data received from ifmap.
kstate.xml	Shows data configured in the vRouter data path.
mac_learning.xml	Shows entries in vRouter-agent MAC learning table.
sandesh_trace.xml	Gives the different agent module traces such as oper, ksync, mac learning, and grpc.
sandesh_uve.xml	Lists all the user visible entitities (UVEs) in the vRouter-agent. The UVEs are used for analytics and telemetry.
stats.xml	Shows vRouter-agent slow path statistics such as error packets, trapped packets, and debug statistics.
task.xml	Shows vRouter-agent worker task details.

Note:

The table shows grouped output. The cloud-native router does not group or sort the output on live systems.

The http://host server IP address:8085 page displays only a list of HTML links.