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 18.104.22.168, which seems a little short sighted to me!!!
Any help is appreciated!
Solved! Go to Solution.
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…