
Critical
Summit WM-Series WLAN Switch and Altitude Access Point Software Version 1.0 User Guide
199
VNMGR
VNMGR
Severity Critical
Log Message Critical internal error - memory protection flags have been corrupted. VN Manager will halt.
Description Indicates that internal memory protection flags have been corrupted.
Action If the process did not restart after emitting this error, or if client association, MAC-based
authentication, or mobility problems continue to exist, shell into the O/S and kill the process
to see if that clears the problem. If the problem does not clear, try downgrading to a
previous software release
VNMGR
Severity Critical
Log Message Internal system interrupt handlers failed to initialize. VN Manager will halt.
Description Indicates that internal system interrupt handlers have failed to initialize.
Action If the process did not restart after emitting this error, or if client association, MAC-based
authentication, or mobility problems continue to exist, shell into the O/S and kill the process
to see if that clears the problem. If the problem does not clear, try downgrading to a
previous software release
VNMGR
Severity Critical
Log Message Unable to initialize internal program thread. VN Manager will halt.
Description Indicates that the process cannot allocate or update process threads.
Action If the process did not restart after emitting this error, or if client association, MAC-based
authentication, or mobility problems continue to exist, shell into the O/S and kill the process
to see if that clears the problem. If the problem does not clear, try downgrading to a
previous software release
VNMGR
Severity Critical
Log Message Critical internal error - unable to allocate memory for VN Manager. VN Manager will halt.
Description Indicates a memory allocation failure.
Action If the process did not restart after emitting this error or if client association, MAC-based
authentication, or mobility problems continue to exist, shell into the O/S and kill the process
to see if that clears the problem. If the problem does not clear, try downgrading to a
previous software release, where the memory leak may not exist.
Comentarios a estos manuales