Problem

There are connectivity Issues between Customer Premises Equipment and Versa Analytics Nodes.

Solution

Follow these steps to troubleshoot connectivity issues between Customer Premise Equipments (CPE) and Versa Analytics nodes:

1. Run the  show orgs org-services Costco lef collectors collector1 status CLI command to check the connectivity status between the CPE and Versa Analytics Node.
   Example:
   

   cli> show orgs org-services Costco lef collectors collector1 status
   
   VSN SOURCE          DESTINATION    DESTINATION   ROUTING      STATUS       PENDING 
   
   ID        IP                     IP                     PORT            INSTANCE                      MSGS     
   
   ------------------------------------------------------------------------------------------------------------------------
   
   2    20.10.31.1  1025    81.1.1.1                        1234               mgmt      Established          0  

2. Ping to the destination IP using source IP if the connectivity status is either Init or Reconnect.
   Example:
   

   CLI> ping 81.1.1.1 routing-instance mgmt source 20.10.31.1

   1. If the ping fails, run the  show route routing-instance <instance-name> CLI command to check if there is a route to destination on the routing instance.
      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    →

   2. If no route is found, add a static route to reach the destination.
   3. Check for a reverse route in the VAN for the source IP.
   4. Run a TCPDUMP command on the VAN interface to check the syn/syn-ack received status.
3. Run the show orgs org Provider sessions detail command to check CPE/Appliance is sending packets with no drops.
   Example:
   

   dropped-forward-pkt-count  0
   dropped-forward-byte-count 0
   dropped-reverse-pkt-count  0
   dropped-reverse-byte-count 0

4. Run the show system session | display set CLI command to check the status of the tcp adjust mss on the device.
   Example:
   

   cli(config)% show system session | display set
   set system session tcp-adjust-mss enable true

5. Run the show system session | display set CLI command to check the PE router configuration if there is a Versa PE router between the controller and Versa Analytics cluster, and if there is asymmetric traffic flowing.
   Example:
   

   PE-cli(config)% show system session | display set
   set system session check-tcp-syn false 

6. Run the show log-collector-exporter local collectors | display set CLI command to check for the  log collector configuration of the specified destination address and port.
   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

7. If LEF connection status is established, run the  show log-collector-exporter local collectors connection CLI command to check the status of the connections on the Van nodes.
   Example for tenant and appliance per client connection from release 16.1R :
   

   versa@PoP1-VA1> show log-collector-exporter local collectors connections
   COLLECTOR  CLIENT    CLIENT IP   CLIENT
   NAME           SOCKET   ADDRESS     PORT        TENANT       APPLIANCE 
   -----------------------------------------------------------------------------------------------------------------------
   lc1                 18          91.1.1.1         1073            Safeway           PoP1-Controller1
                         19         91.1.1.1          1055            OliveGarden     PoP1-Controller
                         20         91.1.1.1          1037            Costco              PoP1-Controller1
                         21         91.1.1.1          1046             Macys              PoP1-Controller1
                         22         91.1.1.1          1028             BestBuy           PoP1-Controller1
                         23         91.1.1.1          1063             Provider           PoP1-Controller1
                         26         91.1.1.1          52004           Costco              PoP1-Costco-Branch2
                         27         91.1.1.1          65041            Provider           PoP1-Costco-Branch2
                         28         91.1.1.1          31483            Provider           PoP1-Costco-Branch4
                         29         91.1.1.1          29150           Costco              PoP1-Costco-Branch4
                         30         91.1.1.1           9219             Costco             PoP1-Costco-Branch3
                         31         91.1.1.1           58761            Provider          PoP1-Costco-Branch3
                         38         20.10.31.1       1034              Provider          PoP1-Costco-Branch1
                         40         20.10.31.1        1025             Costco            PoP1-Costco-Branch1