cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
655
Views
0
Helpful
1
Replies

SSM On-Prem issue with IP

billmoise
Level 1
Level 1

Hello,

>> tcpdump -r pcaps:ssmonprem.pcap
executing the logic for read!
reading from file /var/files/pcaps/ssmonprem.pcap, link-type LINUX_SLL (Linux cooked)
tcpdump: 18:33:08.689393 IP 172.18.0.5.60480 > webproxv.nexweb.us.tproxy: Flags [S], seq 3739517236, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0

tcpdump: 18:33:08.689393 IP 172.18.0.5.60480 > webproxv.nexweb.us.tproxy: Flags [S], seq 3739517236, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0

tcpdump: 18:33:08.689410 IP ssm-on-prem.nexad.nexweb.us.60480 > webproxv.nexweb.us.tproxy: Flags [S], seq 3739517236, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0

I did a capture trying to find out why i get a “SSO service: unable to reach Cisco.” 
Turns out that the SSM On-Prem is using its docker atlantis0 interface to talk to the proxy instead of its configured IP. 
Is there a way to fix this?

1 Reply 1

fratpoly
Level 1
Level 1

I encountered a similar issue on our website and successfully resolved it. To address the problem with the SSM On-Prem docker atlantis0 interface not communicating as expected, I suggest exploring our article on 'Enhancing Customer Service' . It contains valuable insights that may assist you in troubleshooting the 'SSO service: unable to reach Cisco' issue.

Rhhman
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: