Troubleshoot Connectivity Issues
For supported software information, click here.
To troubleshoot connectivity issues between customer premise equipment (CPE) devices and Versa Analytics nodes:
- On the CPE, issue the show orgs org-services lef collectors status CLI command to check the connectivity status between the CPE and Versa Analytics node. For example:
cli> show orgs org-services Costco lef collectors collector1 status VSN SOURCE SOURCE DESTINATION DESTINATION ROUTING STATUS PENDING ID IP PORT IP PORT INSTANCE MSGS ------------------------------------------------------------------------------------------------------------------------ 2 20.10.31.1 1025 81.1.1.1 1234 mgmt Established 0
- Ping to the destination IP using source IP if the connectivity status is either Init or Reconnect. For example:
cli> ping 81.1.1.1 routing-instance mgmt source 20.10.31.1
- If the ping fails, issue the show route routing-instance instance-name command to check whether there is a route to destination on the routing instance. For example:
cli> show route routing-instance mgmt Routes for Routing instance : mgmt AFI: ipv4 Codes: E1 - OSPF external type 1, E2 - OSPF external type 2 IA - inter area, iA - intra area, L1 - IS-IS level-1, L2 - IS-IS level-2 N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 RTI - Learnt from another routing-instance + - Active Route Prot Type Dest Address/Mask Next-hop Age Interface name ---- ---- --------------- ----------- --------- -------------------- static N/A +0.0.0.0/0 20.10.31.1 1d13h06m tvi-0/2.0 conn N/A +10.10.31.0/24 0.0.0.0 1d13h06m tvi-0/1.0 local N/A +10.10.31.1/32 0.0.0.0 1d13h06m directly connected static N/A +81.1.1.1/32 20.52.1.1 1d13h06m ptvi1 -→ static N/A 81.1.1.1/32 20.52.1.2 1d13h06m ptvi2 →
- If no route is found, add a static route to reach the destination.
- Check for a reverse route in the Versa Analytics node for the source IP.
- Issue a tcpdump command on the Versa Analytics node interface to check the syn/syn-ack received status.
- Issue the show orgs org provider sessions detail command to check that the CPE device is sending packets with no drops. For example:
cli> show orgs org Organization1 sessions detail dropped-forward-pkt-count 0 dropped-forward-byte-count 0 dropped-reverse-pkt-count 0 dropped-reverse-byte-count 0
- Issue the show system session | display set command to check the status of the tcp adjust mss on the device. For example:
cli(config)% show system session | display set set system session tcp-adjust-mss enable true
- Issue the show system session | display set command to check the PE router configuration if there is a Versa PE router between the Controller node and Versa Analytics cluster, and if there is asymmetric traffic flowing. For example:
PE-cli(config)% show system session | display set set system session check-tcp-syn false
- On the Analytics node, issue the show log-collector-exporter local collectors | display set command to check for the log collector configuration of the specified destination address and port. For example:
PoP1-VA1% show log-collector-exporter local collectors | display set set log-collector-exporter local collectors lc1 address 81.1.1.1 set log-collector-exporter local collectors lc1 port 1234 set log-collector-exporter local collectors lc1 storage Directory /var/tmp/lo set log-collector-exporter local collectors lc1 storage format syslog set log-collector-exporter local collectors lc1 storage file-generation-interval 10
- If LEF connection status is established, issue the show log-collector-exporter local collectors connection command to check the status of the connections on the Analytics nodes. For example, for a tenant and appliance per-client connection:
versa@PoP1-VA1> show log-collector-exporter local collectors connections COLLECTOR CLIENT CLIENT IP CLIENT NAME SOCKET ADDRESS PORT TENANT APPLIANCE ---------------------------------------------------------------------------------- lc1 18 10.1.1.1 1073 Grocery1 PoP1-Controller1 19 10.1.1.1 1055 Restaurant1 PoP1-Controller 20 10.1.1.1 1037 BigBox1 PoP1-Controller1 21 10.1.1.1 1046 Clothing1 PoP1-Controller1 22 10.1.1.1 1028 Electronics1 PoP1-Controller1 23 10.1.1.1 1063 Provider PoP1-Controller1 26 10.1.1.1 52004 BigBox2 PoP1-BigBox-Branch2 27 10.1.1.1 65041 Provider PoP1-BigBox-Branch2 28 10.1.1.1 31483 Provider PoP1-BigBox-Branch4 29 10.1.1.1 29150 BigBox3 PoP1-BigBox-Branch4 30 10.1.1.1 9219 BigBox4 PoP1-BigBox-Branch3 31 10.1.1.1 58761 Provider PoP1-BigBox-Branch3 38 10.10.31.1 1034 Provider PoP1-BigBox-Branch1 40 10.10.31.1 1025 BigBox5 PoP1-BigBox-Branch1
Supported Software Information
Releases 20.2 and later support all content described in this article.