I have a cluster of 4 WAP561, one week old. I upgraded firmware to 126.96.36.199 when I deployed them. They work perfectly for about a day or so, then become unresponsive.
They usually still respond to ping but not always. When they do, trying to access the management portal it redirects to ([ip]/admin.cgi?action=main), but the page isn't served (no data received). The SSID is still broadcast but clients are unable to connect.
Rebooting solves the problem temporarily, and when they're working they work perfectly. The issue doesn't occur on every wap at the same time - sometimes one or two will keep working for longer.
During the roll-out only 3 users have had access for testing so I can rule out any over subscription issues.
Hi every one!!!When you are configuring a remote VPN connection, there
are some steps that are lost on the path. Here you can see those steps.
A) In your Cisco device: 1. Ensure you don´t have any rule denying the
traffic between the device and the remote...
You have a Cisco Unified Communications Manager (CUCM) system and want
to configure a SPA112 analog telephone adaptor (ATA) to register to the
CUCM so that you can use up to two analog phones or similar FXS devices
with the CUCM.In this application note, ...
Introduction: This document describes how to connect SG300 with Catalyst
switch via STP. Spanning Tree Protocol (STP) is a Layer 2 protocol that
runs on mainly on switches. The specification for STP is IEEE 802.1D.
The main purpose of STP is to ensure tha...