I don't know, maybe the switch is just hangry and needs a snack. Have you tried turning it off and on again? (Just kidding, but seriously, this is a tough one!)
This is a classic Cisco networking question. I'm pretty sure the answer is D) feature http, since the playbook is trying to use the HTTP protocol to communicate with the switch.
Ah, I see. The playbook is trying to connect to the switch, but it's not working. I bet the answer is A) feature nxapi, which enables the NX-API feature on the switch and allows it to handle HTTP requests from Ansible.
Hmm, I'm not sure about this one. The error message mentions a connection refused, so it could be a network configuration issue. Maybe C) interface mgmt0; ip access-group allow_http_traffic in is the correct answer.
This is a tricky one. I think the answer is B) http-server enabled, since the error indicates a connection issue and the NX-OS needs to have the HTTP server feature enabled to handle the Ansible playbook's request.
Norah
10 days agoLindsay
13 days agoShalon
18 days agoMarnie
20 days agoErnest
21 days agoEttie
2 days agoSabina
22 days agoElise
22 days agoSanjuana
25 days agoHenriette
4 days ago