How SSR connects to the Mist portal

1) If an SSR has two Internet connections, will the SSR attempt to connect to Mist using both?

• SSR will use only one connection.

2) Assuming the answer is 'no' to the first question, will it attempt to connect from the Mgmt port over a configured WAN port?

• Yes, it will prefer Mgmt over WAN.

Here is a sample output from the lab. You could see that mgmt-0-0 has the lowest metric and WAN (kni254) has the next lowest. (kni254) will be used to route the traffic from Linux to SSR OS, from there it will take the available default route and egress through any available WAN.

default via 10.219.175.1 dev mgmt-0-0 proto dhcp metric 4 

default via 169.254.127.126 dev kni254 metric 20 

10.219.175.0/25 dev mgmt-0-0 proto kernel scope link src 10.219.175.17 metric 4 

169.254.0.0/16 dev xe-2-2 scope link metric 1033 linkdown 

169.254.0.0/16 dev xe-2-1 scope link metric 1034 linkdown 

169.254.0.0/16 dev ge-1-1 scope link metric 1038 linkdown 

169.254.0.0/16 dev team-ge-1-0 scope link metric 1049 

169.254.0.0/16 dev kni254 scope link metric 1082 

169.254.127.126/31 dev kni254 proto kernel scope link src 169.254.127.127 

169.254.253.0/30 dev team-ge-1-0 proto kernel scope link src 169.254.253.1 

[root@ar50230080 ~]# 

3) Which process is used to connect to mist?

• SSR uses the 128T-mist-agent service to connect to Mist.

[root@vmware-4229f17e8fa0fb79-559a84be21a0e07a t128]# systemctl status 128T-mist-agent

● 128T-mist-agent.service - 128T Mist System Agent

Loaded: loaded (/usr/lib/systemd/system/128T-mist-agent.service; enabled; vendor preset: disabled)

Active: active (running) since Thu 2025-04-24 01:51:55 UTC; 1 months 0 days ago

4) Which logs need to be checked for Mist connectivity issues?

• journalctl -u 128T-mist-agent
• journalctl -u 128T-mist-agent -f