06-18-2021 12:25 PM - edited 07-02-2021 09:34 PM
I have 1800S Sensor Image Version 2.2.2.0 provisioned with wired backhaul to DNAC version 2.1.2.4
When sensor is connected on subnet with DHCP Option 43 for the DNAC, I'm able to login to console and SSH with the SSH password configured in DNAC.
When I move to a different subnet without Option 43 for the DNAC, 1800S LED has Red/Green lights and I cannot login to Console or SSH with the Username/Password configured in DNAC.
Also can't login with the default Cisco/Cisco username password.
How do I log in to sensor to verify it has the DNAC and NTP server information that should be provisioned from DNAC when claimed?
06-18-2021 01:19 PM
06-21-2021 05:43 AM
Thank you, this is helpful. The Sensor provisioning documentation needs to make that clear.
This is unfortunate because our DNAC covers a large amount of subnets. We will likely need to use the pnpserver DNS option instead.
I am able to console and SSH to the Sensor, but neither doucmented default user Cisco/Cisco nor the SSH username/password provisioned from DNAC is working in the state the sensor does not have the DHCP option. Is this intentional?
It would be nice to be able to save controller info with the DNAC reference, so we can send the sensor to multiple sites.
It would also be nice to be able to SSH to the sensor to use cli to provide the ntp server and DNAC reference.
06-21-2021 06:21 AM
06-21-2021 07:22 PM
Username is sensor. PW Is password
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