10-10-2018 07:57 AM - edited 03-01-2019 05:40 AM
Hi,
I had our ACI environment registered to a Smart Software Manager Satellite 5.something which worked very well. Now I wanted to switch over to the SSMS 6.0 Enhanced Edition which doesn't seem to work at all.
The SSMS is configured and synchronized to SSM. I have IP reachability between APIC and SSMS but no matter what I put into the URL-Field of the registration dialog of the APIC I always receive a "registration failed" fault (F3058) saying the APIC failed to send out Call Home HTTP message.
I tried:
http://<IP address>:8080/Transportgateway/services/DeviceRequestHandler
https://<IP address>:8080/Transportgateway/services/DeviceRequestHandler
http://<IP address>/Transportgateway/services/DeviceRequestHandler
https://<IP address>/Transportgateway/services/DeviceRequestHandler
With
http://<IP address>:443/Transportgateway/services/DeviceRequestHandler
interestingly the fault description changes to "Fail to parse response data from SCH server" but this doesn't put me in a better position...
Does anyone have this setup working and can tell me which URL to put there? Or should anyone of the above work and I have to find the issue elsewhere?
Kind regards,
Nik
Solved! Go to Solution.
11-14-2018 10:17 PM
For those who might face the same issue:
I finally opened a TAC case. Apparently 6.0 doesn't handle manual synchronization in conjunction with ACI very well. There is a bug I couldn't find but which is obviously known to the inner circle.
An update to 6.0.1 is needed, then it works as a charm.
The correct satellite URL with 6.0.1 is https://<IP address>/Transportgateway/services/DeviceRequestHandler so no special ports, just the default 443. IP address and hostname both work (as expected).
Kind regards
Nik
10-16-2018 05:29 PM
Nik,
Can you resolve DNS for "software.cisco.com"?
10-18-2018 12:10 PM
10-22-2018 07:33 AM
Nik,
Here is a link to a short blurb that may help out with some possible troubleshooting steps:
Scroll down to "Smart Licensing APIC Registration Failed"
Essentially, we may have issues with SSL certs or using the correct port numbers.
11-14-2018 10:17 PM
For those who might face the same issue:
I finally opened a TAC case. Apparently 6.0 doesn't handle manual synchronization in conjunction with ACI very well. There is a bug I couldn't find but which is obviously known to the inner circle.
An update to 6.0.1 is needed, then it works as a charm.
The correct satellite URL with 6.0.1 is https://<IP address>/Transportgateway/services/DeviceRequestHandler so no special ports, just the default 443. IP address and hostname both work (as expected).
Kind regards
Nik
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide