10-27-2021 07:51 AM
Hola amigos una consulta. en la implementacion de APs y Controller 144 me pude dar cuenta de algo que pasaba. Cuando conectamos los AP (habilitado el telnet y SSH) a los sw y remotamente desde el sw puedo acceder a los APs ya sea por telnet o ssh y previamente direcionarlos con el comando:
set scg ip x.x.x.x
reboot
y puedo ingresar al AP de igualmente remotamente desde el Sw al AP cuando el AP esta en la controladora en la Zona por defecto (Default Zone).
Pero cuando muevo al AP a una zona creada ya no se puede ingresar remotamente desde el Sw al AP.
Porque pasaría esto.,? falta alguna configuración en la controladora.?
10-27-2021 08:34 AM
Hi Luis,
What do you mean exactly by "no longer possible to access remotely"?
Please note, moving the AP to different zone will apply the zone configuration to it.
Some major configuration related to device management are:
If you can confirm whether you are able to SSH but credentials are not working or SSH is not working at all?
10-27-2021 08:50 AM
@syamantak_omer Hi friend, SSH is working at all.
This is only when I move the AP to a zone other than Default Zone,
while the AP is in the Default Zone if I can remotely enter the ap
by ssh or telnet, the message it shows in the Sw is when the AP moved
to another zone different from the default one is connection
closed at the time of the ssh / telnet request.
10-27-2021 08:58 AM
Check if you can ping the AP IP.
Port 22 is must for AP to controller communication so if AP is managed by controller and online, there must be some network issue which is preventing you from accessing the AP over SSH.
10-27-2021 09:00 AM
Do I need some additional configuration to the new zones created to
allow SSH / Telnet access to the APs.