Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[Contrail] contrail-vrouter-agent introspects

0

0

Article ID: KB31864 KB Last Updated: 22 Jun 2017Version: 1.0
Summary:

Every instance of a contrail compute node runs nova-compute and contrail-vrouter-agent processes. This article provides a list of all vrouter agent introspects which can be examined to monitor and troubleshoot vrouter agent processes.

Solution:

Contrail vRouter Agent Introspect can be accessed via HTTP port 8085 (http://<ip-address-of-compute-node>:8085/). Various links are accessible from here, and can be used to see the current operational data in the vrouter agent.
 
Complete list of available agent introspects:

<a href="agent.xml">agent.xml</a><br/>
<a href="agent_profile.xml">agent_profile.xml</a><br/>
<a href="agent_stats_interval.xml">agent_stats_interval.xml</a><br/>
<a href="cfg.xml">cfg.xml</a><br/>
<a href="controller.xml">controller.xml</a><br/>
<a href="cpuinfo.xml">cpuinfo.xml</a><br/>
<a href="diag.xml">diag.xml</a><br/>
<a href="discovery_client_stats.xml">discovery_client_stats.xml</a><br/>
<a href="flow_stats.xml">flow_stats.xml</a><br/>
<a href="ifmap_agent.xml">ifmap_agent.xml</a><br/>
<a href="kstate.xml">kstate.xml</a><br/>
<a href="multicast.xml">multicast.xml</a><br/>
<a href="pkt.xml">pkt.xml</a><br/>
<a href="port_ipc.xml">port_ipc.xml</a><br/>
<a href="sandesh_trace.xml">sandesh_trace.xml</a><br/>
<a href="sandesh_uve.xml">sandesh_uve.xml</a><br/>
<a href="services.xml">services.xml</a><br/>
<a href="stats.xml">stats.xml</a><br/>
<a href="stats_interval.xml">stats_interval.xml</a><br/>
<a href="task.xml">task.xml</a><br/>
<a href="xmpp_server.xml">xmpp_server.xml</a><br/>

http://<ip-address-of-compute-node>:8085/agent.xml shows agent operational data. Using this introspect, you can see the list of interfaces, VMs, VNs, VRFs, Next hops, MPLS labels, Security groups,ACLs and  Mirror configurations.

<?xml-stylesheet type="text/xsl" href="/universal_parse.xsl"?>
<agent type="rlist">
<PageReq type="sandesh">
<key type="string">0</key></PageReq>
<AgentInitStateReq type="sandesh">
</AgentInitStateReq>
<SgListReq type="sandesh">
<name type="string">0</name></SgListReq>
<VnListReq type="sandesh">
<name type="string">0</name><uuid type="string">0</uuid><vxlan_id type="string">0</vxlan_id><ipam_name type="string">0</ipam_name></VnListReq>
<VmListReq type="sandesh">
<uuid type="string">0</uuid></VmListReq>
<NhListReq type="sandesh">
<type type="string">0</type><nh_index type="string">0</nh_index><policy_enabled type="string">0</policy_enabled></NhListReq>
<VrfListReq type="sandesh">
<name type="string">0</name></VrfListReq>
<Inet4UcRouteReq type="sandesh">
...

VrfListReq introspect can be accessed via http://<ip-address-of–compute-node>:8085/Snh_VrfListReq. The URL is created by pre-pending 'Snh_' to the sandesh agent name 'VrfListReq' (marked bold in the output above :8085/agent.xml). Similar to this, Snh_VnListReq can be used to get VnListReq sandesh introspect, for example.

http://<ip-address-of-compute-node>:8085/controller.xml  shows agent <-> controller related statistics, such as current XMPP connections with the control node (XMPP server), the status and stats on these connections:

<?xml-stylesheet type="text/xsl" href="/universal_parse.xsl"?>
<controller type="rlist">
<AgentXmppConnectionStatusReq type="sandesh">
</AgentXmppConnectionStatusReq>
<AgentDnsXmppConnectionStatusReq type="sandesh">
</AgentDnsXmppConnectionStatusReq>
<AgentDiscoveryXmppConnectionsRequest type="sandesh">
</AgentDiscoveryXmppConnectionsRequest>
<AgentDiscoveryDnsXmppConnectionsRequest type="sandesh">
</AgentDiscoveryDnsXmppConnectionsRequest>
</controller>

AgentXmppConnectionStatusReq sandesh introspects can be observed on http://<ip-address-of-compute-node>:8085/Snh_AgentXmppConnectionStatusReq? Again, the URL is created by pre-pending 'Snh' to the sandesh agent name. 
 
The same method for creating URLs, and making HTTP requests can be used to gather statistics information for all other agent introspects.

List of most useful introspect pages:

  • 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 (kernel) module
  • pkt.xml - shows the current flow data in the agent
  • sandesh_trace.xml - gives the module traces
  • services.xml - provides stats and packet dumps for control packets like DHCP, DNS, ARP, ICMP.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search