Extreme Networks Summit WM Technical Reference Manual page 202

Logs and Events
Table 49: RU_SESMGR_ID (65) logs and events (Continued)
Log ID
36
37
38
Info
65
66
67
68
69
70
202
Log Message
Mobility tunnel establishment
failed with Peer%s. Please
verify peer's reachability.
Mobility manager startup.
RU Session Manager startup.
Access point registration and
authentication succeeded.
(%S.)
Access point registration and/
or authentication failed. (%S.)
Access point session poll
disconnect AP session timed
out. (%S.)
Access controller tunnel
registration failed (%s).
Access point software version
validation failed. (%s)
%s transmission failed.
Comment
Possible Feature Impact. Some
possible user impact as tunnel
change purges sessions
associated with peer. Users if
connected will need to re-
authenticate and renegotiate
topology profile.
Component state
Component state
Access Controller registration
state
Access Controller registration
failed. AP unsuccessful in
establishing credential
exchange with controller. AP
will retry.
AP disconnected from active
controller. May no longer be
available for RF coverage.
Possible Feature Impact. Some
possible user impact as tunnel
change purges sessions
associated with peer. Users if
connected will need to re-
authenticate and renegotiate
topology profile.
AP was determined to not be
running an adequate firmware
version for operation with
controller. May be result of
administration specification of
firmware upgrade request.
Interprocess communication
failure between AP and
controller.
Summit WM Technical Reference Guide, Software Version 5.1
Action
Determine if outage was
caused by configuration
change to Mobility feature
(add/Remove of controllers
from Mobility Domain).
Determine if outage was
caused by network path
interruption. If interruption was
caused by failure of Mobility
controller, please review log
file to determine appropriate
root cause and corresponding
action
None
None
None
If problem persists Contact
Technical Support for
investigation.
Determine if outage was
caused by configuration
change (Delete/Pending/
Release). Determine if outage
was caused by network path
interruption. If interruption was
caused by functional issue
with AP or controller please
contact Technical Support to
investigate.
Determine if outage was
caused by configuration
change to Mobility feature
(add/Remove of controllers
from Mobility Domain).
Determine if outage was
caused by network path
interruption. If interruption was
caused by failure of Mobility
controller, please review log
file to determine appropriate
root cause and corresponding
action.
Validate version incompatibility
of AP. Verify that correct
upgrade image is available.
Upgrade will take place
automatically.
If problem persists Contact
Technical Support for
investigation.