Advertisement
Appendix B
Troubleshooting
Symptom
A change in the Global Controller, such as adding
a new global report or inspection rule, does not
appear on a managed Local Controller.
No incidents appear in the Global Controller
I deleted a Local Controller from the
Global Controller when there were
communication problems. How do I restore the
Local Controller?
A replacement Global Controller appliance has
been restored. How do I restore communications
with the Local Controllers?
OL-14672-01
Troubleshooting Global Controller-to-Local Controller Communications
Possible Resolution
Verify Activate was clicked.
You must click Activate for
Local Controller-based topological changes to be
pushed to the Global Controller
This issue can result from a time synchronization
mismatch. Make sure the Local Controller and
Global Controller have the system times set
properly as a time skew can cause incidents to not
appear in the Summary page.
If the Local Controller was deleted from a
Global Controller when communications were
failing, use the pnreset –s command to reset the
Local Controller to standalone mode. Then, you
can add it to the Global Controller again.
For more information, see
Use the pnreset –g command on each
Local Controller. This command removes the
Global Controller data from a Local Controller,
leaving Local Controller-specific data untouched.
This option keeps the Global Controller
connectivity information on the Local Controller
intact, enabling the Local Controller to reconnect
as soon as the Global Controller is restored (to
purge this information, use the -s option). For
more information, see
Use this option only when a
Note
Global Controller recovery is required.
Install and Setup Guide for Cisco Security MARS
pnreset, page
A-40.
pnreset, page
A-40.
B-9
Advertisement
Chapters
Troubleshooting
