Smart Software Manager Satellite route issues

[dongill]

Hi all,

I’ve deployed a SSM Satellite VM (v6.0) from the ISO as per the installation guide, however, I have noticed that there are a handful of static routes to IP prefixes in the appliances OS routing table that point to a “docker” network interface (these appeared out of the box).

Unfortunatey, these routes are preventing connectivity to devices I have in this range of prefixes - is there any way to change this range to something else?

I have put static routes in place on the box to get connectivity for a subnet within the range, but have no doubt this is/will break the application?

*the range is 172.0.0.0, which seems a little short sighted to me!!!

Any help is appreciated!

[csmula]

Same for us....
172.17.xx.xx is the DMZ were our proxy is located :-(
no internet access for our satellite

[HOLGER ALIX]

similar behavior in 6.1
Docker Interface in IP Subnet 172.17.0.0/16
same as our WAN Router / Proxies

useless....

[dongill]

Agreed – I have a support call in progress with TAC around this and am feeding back through our Cisco AM, but I did find a way around it.
I thought I’d see what happened it I used an IP in that range for the VM itself [as you do!].
If you re-image the appliance and give it an IP in the 172.16.0.0/16 range during the setup, the docker interface changes to 172.18.0.0 /16 and Atlas interface to 172.16.2.0 which was sufficient for me to start using it, but obviously not a good state to be in long term.

I could then change the IP back to what I needed it to be via the application network menu once it had been installed.

[bit of a hack as I had to use another box on the same L2 segment with a secondary IP address in the 172.16.0.0/16 subnet to gain access to the Satellite GUI ;-)]

Definitely has the whiff of a product that isn’t quiet finished…

[dongill · Accepted solution]

Quick update on this...

I was running v6.0.1 and hit this "catastrophic" bug - not great and caused me a lot of pain..
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvk50537

I have had to rebuild the entire box with v7 on the advice from TAC and re-register all devices, but when doing so I came across this little gem that explains how to easily change the docker at atlantis interface IP's:
https://community.cisco.com/t5/smart-licensing-enterprise/how-to-change-internal-ip-addresses-used-by-satellite-smart/ta-p/3792288
@rokazemi - great posting and thanks!

Works a treat... hopefully this will help any one else who has had this prob.

Thanks