02-01-2019 08:06 PM - edited 07-05-2021 09:47 AM
Tengo el siguiente problema con un punto de acceso Cisco 1562, el cual no me deja entrar en su configuración y me aparece el siguiente error, está leyendo y está apareciendo es un problema del poe, en la ficha técnica del diseño del modelo interior AIR-PWRINJ6 el cual tiene que ver para configurar y nada, alguien me puede apoyar para poder resolver el problema.
saludos
[* 12/02/2018 01: 38: 50.3875] DOT11_DRV [0]: set_channel Canal establecido en 6
[* 12/02/2018 01: 38: 50.5681] Radio iniciada 0
[* 12/02/2018 01: 38: 52.0447] Radio 1 detenida
[* 12/02/2018 01: 38: 52.0571] DOT11_DRV [1]: set_channel Canal establecido en 153
[* 12/02/2018 01: 38: 52.2780] Comenzó Radio 1
[* 12/02/2018 01: 38: 52.5761] Radio detenida 0
[* 12/02/2018 01: 38: 52.5885] DOT11_DRV [0]: set_channel Canal establecido en 7
[* 12/02/2018 01: 38: 52.7787] Radio iniciada 0
[* 12/02/2018 01: 38: 54.2894] Radio 1 detenida
[* 12/02/2018 01: 38: 54.3021] DOT11_DRV [1]: set_channel Canal establecido en 157
[* 12/02/2018 01: 38: 54.5293] Comenzó Radio 1
[* 12/02/2018 01: 38: 54.7867] Radio detenida 0
[* 12/02/2018 01: 38: 54.7990] DOT11_DRV [0]: set_channel Canal establecido en 8
[* 12/02/2018 01: 38: 54.9969] Radio iniciada 0
[* 12/02/2018 01: 38: 56.5376] Radio 1 detenida
[* 12/02/2018 01: 38: 56.5501] DOT11_DRV [1]: set_channel Canal establecido en 161
[* 12/02/2018 01: 38: 56.7760] Comenzó Radio 1
[* 12/02/2018 01: 38: 57.0049] Radio detenida 0
[* 12/02/2018 01: 38: 57.0170] DOT11_DRV [0]: set_channel Canal establecido en 9
[* 12/02/2018 01: 38: 57.2125] Radio iniciada 0
[* 12/02/2018 01: 38: 58.7844] Radio 1 detenida
[* 12/02/2018 01: 38: 58.7972] DOT11_DRV [1]: set_channel Canal establecido en 165
[* 12/02/2018 01: 38: 58.9967] Comenzó Radio 1
[* 12/02/2018 01: 38: 59.2205] Radio detenida 0
[* 12/02/2018 01: 38: 59.2331] DOT11_DRV [0]: set_channel Canal establecido en 10
[* 12/02/2018 01: 38: 59.4292] Radio iniciada 0
[* 12/02/2018 01: 39: 01.0081] Radio 1 detenida
[* 12/02/2018 01: 39: 01.0210] DOT11_DRV [1]: set_channel Canal establecido en 56
[* 12/02/2018 01: 39: 01.2298] Comenzó Radio 1
02-01-2019 08:49 PM
02-02-2019 12:10 PM
Thank you for your attention
according to your experience, what could be the cause of the problem? I assumed it was the power injector, which only gave 30 w and now I just bought a 60w and the following appears.
12/02/2018 01:41:21.9398] aptrace_register_sysproc_fn: duplicate registeration for 'wired'
[*12/02/2018 01:41:26.0455] Waiting for uplink IPv4 configuration
[*12/02/2018 01:41:31.0466] Waiting for uplink IPv4 configuration
Password: ng to your experience, what could be the cause of the problem? I ass
Error: Maximum input length exceeded
ing appears.
Password: [*12/02/2018 01:41:36.0477] Waiting for uplink IPv4 configuration
[*12/02/2018 01:41:37.0478] Resetting wired0 and[12/02/2018 01:41:37.0800] wired0: stopped
restart DHCP client
[12/02/2018 01:41:39.1600] wired0 emac 1: link up
[12/02/2018 01:41:39.2100] wired0: link up
[12/02/2018 01:41:39.2600] wired0: started
[*12/02/2018 01:41:39.3123] aptrace_register_sysproc_fn: duplicate registeration for 'wired'
[*12/02/2018 01:41:43.4179] Waiting for uplink IPv4 configuration
[*12/02/2018 01:41:48.4191] Waiting for uplink IPv4 configuration
[*12/02/2018 01:41:53.4202] Waiting for uplink IPv4 configuration
[*12/02/2018 01:41:54.4204] Resetting wired0 and[12/02/2018 01:41:54.4500] wired0: stopped
restart DHCP client
[12/02/2018 01:41:56.5400] wired0 emac 1: link up
[12/02/2018 01:41:56.5900] wired0: link up
[12/02/2018 01:41:56.6300] wired0: started
[*12/02/2018 01:41:56.6881] aptrace_register_sysproc_fn: duplicate registeration for 'wired'
[*12/02/2018 01:42:00.7939] Waiting for uplink IPv4 configuration
[*12/02/2018 01:42:05.7949] Waiting for uplink IPv4 configuration
[*12/02/2018 01:42:10.7959] Waiting for uplink IPv4 configuration
[*12/02/2018 01:42:11.7961] Resetting wired0 and[12/02/2018 01:42:11.8300] wired0: stopped
restart DHCP client
[12/02/2018 01:42:13.9100] wired0 emac 1: link up
[12/02/2018 01:42:13.9600] wired0: link up
[12/02/2018 01:42:14.0100] wired0: started
[*12/02/2018 01:42:14.0639] aptrace_register_sysproc_fn: duplicate registeration for 'wired'
[*12/02/2018 01:42:18.1698] Waiting for uplink IPv4 configuration
[*12/02/2018 01:42:23.1708] Waiting for uplink IPv4 configuration
02-02-2019 02:16 PM
@fsolis001 wrote:
Resetting wired0 and[12/02/2018 01:42:11.8300] wired0: stopped restart DHCP client
AP is not getting an IP address. AP is connected to an injector. So what is the injector connected to? Is DHCP Option 43 enabled?
02-04-2019 09:07 AM
The issue of the power injector has been solved, but I see that the ap is not autonomous and comes in mesh mode, can I do it autonomously to configure it in a normal way or forcefully require a controller?
02-04-2019 10:15 PM
@fsolis001 wrote:
the ap is not autonomous and comes in mesh mode
Console into the AP and enter the following command: capwap ap mode local
02-05-2019 12:51 AM
As the AP is in Mesh mode to convert to local mode you need to first authorized to register to the controller.
You need to add the AP Mac address in either the AP in Policies list or the MAC filtering on the controller.
Security > AAA > AP Policies
Click ADD and enter the Ethernet MAC Address of the AP, select MIC as the certificate type.
Reboot the AP and it will join the WLC (As long as normal discovery methods are configured like DHCP option 43)
Once the AP joins the controller, change the mode to local (will reboot again)
WIRELESS > Access Points > All APs then click an AP name to navigate to the AP Details page
Before switching an AP from Local to Bridge mode ensure that the AP has an image with a full radio support (…-k9w8-…) so that it can support Radios and that the AP MAC address has been added to the WLC.
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