troushooting SSR Node HA High availability

Owned by Jean-luc KRIKER
Last updated: Feb 02, 2023
6 min read





show system connectivity router SSR-top

show system connectivity internal router SSR-top

connectivity 
admin@node1.conductor# show system connectivity internal router SSR-top
Tue 2022-06-28 12:35:44 UTC
Retrieving internal system connectivity...

=============== ================= ========================= ================= =================================
 Local Node      Remote Node       Service                   Address           Message
=============== ================= ========================= ================= =================================
 node1.SSR-top   node1.SSR-top     epm                       127.0.0.2:14444   Connected
 node1.SSR-top   node1.SSR-top     routing-agent-listener    127.0.0.2:13333   Connected
 node1.SSR-top   node1.SSR-top     routing-engine-listener   127.0.0.2:2620    Connected
 node1.SSR-top   node1.SSR-top     runtime-data-store        127.0.0.1:4391    Connected
 node1.SSR-top   node1.SSR-top     runtime-data-store        127.0.0.2:6379    Connected
 node1.SSR-top   node1.SSR-top     ssc                       127.0.0.2:12222   Connected
 node1.SSR-top   node1.conductor   ssc                       127.0.1.2:12222   Connected
 node1.SSR-top   node1.conductor   step-repository           127.0.1.2:15555   Connected
 node1.SSR-top   node2.SSR-top     LeaderElect               127.0.0.1:2225    No route to server : 172.16.1.2
 node1.SSR-top   node2.SSR-top     Quorum                    127.0.0.1:2224    No route to server : 172.16.1.2
 node1.SSR-top   node2.SSR-top     ZED                       127.0.0.1:4392    No route to server : 172.16.1.2
 node1.SSR-top   node2.SSR-top     epm                       127.0.0.3:14444   No route to server : 172.16.1.2
 node1.SSR-top   node2.SSR-top     http-api                  127.0.0.1:4396    No route to server : 172.16.1.2
 node1.SSR-top   node2.SSR-top     influx-http               127.0.0.3:8086    No route to server : 172.16.1.2
 node1.SSR-top   node2.SSR-top     internal-ssh              127.0.0.1:932     No route to server : 172.16.1.2
 node1.SSR-top   node2.SSR-top     routing-agent-listener    127.0.0.3:13333   No route to server : 172.16.1.2
 node1.SSR-top   node2.SSR-top     routing-engine-listener   127.0.0.3:2620    No route to server : 172.16.1.2
 node1.SSR-top   node2.SSR-top     runtime-data-store        127.0.0.3:6379    No route to server : 172.16.1.2
 node1.SSR-top   node2.SSR-top     ssc                       127.0.0.3:12222   No route to server : 172.16.1.2
 node1.SSR-top   node2.SSR-top     tank                      127.0.0.3:11011   No route to server : 172.16.1.2
 node2.SSR-top   node1.SSR-top     LeaderElect               127.0.0.1:2223    No route to server : 172.16.1.1
 node2.SSR-top   node1.SSR-top     Quorum                    127.0.0.1:2222    No route to server : 172.16.1.1
 node2.SSR-top   node1.SSR-top     ZED                       127.0.0.1:4392    No route to server : 172.16.1.1
 node2.SSR-top   node1.SSR-top     epm                       127.0.0.2:14444   No route to server : 172.16.1.1
 node2.SSR-top   node1.SSR-top     http-api                  127.0.0.1:4396    No route to server : 172.16.1.1
 node2.SSR-top   node1.SSR-top     influx-http               127.0.0.2:8086    No route to server : 172.16.1.1
 node2.SSR-top   node1.SSR-top     internal-ssh              127.0.0.1:932     No route to server : 172.16.1.1
 node2.SSR-top   node1.SSR-top     routing-agent-listener    127.0.0.2:13333   No route to server : 172.16.1.1
 node2.SSR-top   node1.SSR-top     routing-engine-listener   127.0.0.2:2620    No route to server : 172.16.1.1
 node2.SSR-top   node1.SSR-top     runtime-data-store        127.0.0.2:6379    No route to server : 172.16.1.1
 node2.SSR-top   node1.SSR-top     ssc                       127.0.0.2:12222   No route to server : 172.16.1.1
 node2.SSR-top   node1.SSR-top     tank                      127.0.0.2:11011   No route to server : 172.16.1.1
 node2.SSR-top   node1.conductor   ssc                       127.0.1.2:12222   Connected
 node2.SSR-top   node1.conductor   step-repository           127.0.1.2:15555   Connected
 node2.SSR-top   node2.SSR-top     epm                       127.0.0.3:14444   Connected
 node2.SSR-top   node2.SSR-top     routing-agent-listener    127.0.0.3:13333   Connected
 node2.SSR-top   node2.SSR-top     routing-engine-listener   127.0.0.3:2620    Connected
 node2.SSR-top   node2.SSR-top     runtime-data-store        127.0.0.1:4391    Connected
 node2.SSR-top   node2.SSR-top     runtime-data-store        127.0.0.3:6379    Connected
 node2.SSR-top   node2.SSR-top     ssc                       127.0.0.3:12222   Connected

Completed in 0.13 seconds
admin@node1.conductor#


IssueTraffic did not use the fabric-interface

Investigation

show service-path service-name to-M-Hub-Lan1

>> service-path is down



show device-interface node all summary

show network-interface node all

ping egress-interface HA-Fabric-intf 172.16.13.2   >>>>>> isuse with the correct IP address 172.17.x.x or 172.16.x.x

show system connectivity internal router SSR-top
Solution

wrong IP address in the Fabric-interface