Filter
Top Products
2-6
FAQ and Troubleshooting Guide for the CiscoWorks Wireless LAN Solution Engine
OL-8376-01
Chapter 2 Fault Descriptions
Access Point /Bridge Faults
HotStandBy is active The access point that is configured
for hot standby has become active.
The following conditions could cause
the hot standby access point to
become active: the primary access
point is down, the Ethernet port is
down, or the Radio port is down.
When this fault is cleared, the
following message displays:
HotStandBy is disabled.
Manage Fault
Settings > Access
Point/Bridge
Policies >
HotStandby Status
1. Check the primary access point,
the Ethernet port, or the Radio
port to see why the hot standby
access point has been activated.
2. Correct the condition. For
example, if the Radio Port on the
formerly active access point was in a
disabled state, then enable it using the
access point GUI.
3. Launch the GUI for access point
that is currently in Active
Takeover mode.
4. Select Hot Standby, click Disabled ,
then click Apply.
5. Click Enabled, then enter the
Radio MAC address of Monitored
Radio Port, leave the Polling
interval and Timeout for Each
Polling fields blank,.
6. Click Apply to reconfigure the
access point to Hot Standby
mode.
Inconsistent device
state found: MIB-name
table-name. OID-name
problem-details
One or more configuration values of
the AP/BR are either out-of-range or
are in conflict with another
configuration value. The fault
description and corresponding
swan.log entry provide details about
the suspect value, including the
official public MIB name of the
SNMP OID for which the error was
found.
When a radio is declared to have an
invalid configuration or has failed, it
cannot be manipulated by Radio
Management and is removed from
SWAN RM operations. For example,
if just the 802.11a radio on a WDS is
not configured correctly, only that
radio is excluded from RM
operations; the 802.11b/g radio and
the WDS remains fully
RM-operational. This behavior can
help you isolate the portions of your
network that are affected by
misconfigurations or failures.
Not applicable. To resolve an inconsistent
configuration, several possibilities
exist:
• It is possible that the most recent
Inventory failed for the device.
Re-running inventory might clear
the condition.
• If the configuration value being
contested is user-editable, you
can correct the problem using the
WLSE templates, the AP/BR
GUI, or the AP/BR CLI.
• If the configuration value being
contested is not user-editable, this
is probably an IOS error. You will
need to upgrade the affected
AP/BR to the most recent version
of IOS.
For information about the MIB
referenced in the fault description, see
http://www.cisco.com/public/sw-cent
er/netmgmt/cmtk/mibs.shtml.
Table 2-1 Access Point Faults (continued)
Fault Description Explanation Related Setting Recommended Action