Number
Mnemonic
184.
PROCID
185.
PROCSTART
186.
PROCRSTRT
187.
PROCMAXRSTRT
188.
PROCSYSRSTRT
189.
PROCSTOP
190.
STARTUPCOMPLETE
191.
ADOPTEXCEED
192.
PEERACTIVEUP
193.
PEERSTAUP
194.
PEERACTIVEDOWN
195.
PEERSTADOWN
196.
PEERACTIVEINVLCONF
Severity
Syslog Message
5
"Process ""[str]"" changed
its PID from [int] to [int]
6
"Starting process ""[str]
3
"Process ""[str]"" is not
responding. Restarting
process
1
"Process ""[str]"" reached its
maximum number of
allowed restarts
0
"Process ""[str]"" reached its
maximum number of
allowed restarts. Rebooting
the system !
5
"Process ""[str]"" has been
stopped
5
System startup complete
4
"Total APs adoption
exceeded redundancy group
authorization level in group
[uint], adoption count: [uint],
group authorization level:
[uint]
5
"Heartbeats getting
exchanged with peer [ip],
group ID [uint] in active
mode
5
"Heartbeats getting
exchanged with peer [ip],
group ID [uint] in standby
mode
4
"Peer [ip], with group ID
[uint] in active mode is down
4
"Peer [ip], with group ID
[uint] in standby mode is
down
1
"Peer [ip], with group ID
[uint] in active mode has
detected with invalid
configuration
Syslog Messages & MU Disassociation
Meaning / Cause
The process has changed its PID.
Informational only.
The process is started. Informational
only.
Unresponsive process detected.
Process will be restarted and a core
dump will be saved to the switch.
Too many restarts of the same
process. The maximum number of
process restarts has been reached
but the system-restart is disabled or
reached maximum the number of
system restarts Default number of
process restarts is 4.
The maximum number of process
restarts has been reached. The
switch is going to reboot.
The switch is killing the process from
the start-shell using a kill command.
The switch was started.
The adoption level on am AP has
exceeded the cluster adoption
license. Some APs will have to be
removed. Should not happen unless
there are unlicensed APs on the
network.
The primary peer is observable.
The standby peer is observable.
Error in the update message from the
peer. The connection will come down.
Re-establish the connection.
Error in the update message from the
peer. The connection will come down.
Re-establish the connection.
The redundancy configuration has to
be identical across the entire cluster.
Consequently, a misconfiguration has
been detected.