Advertisement
Appendix A
Command Reference
pnimp
Tip
To avoid IP address conflicts, reconfigure the MARS Appliance running 4.x before you import its
configuration data into a new appliance.
When you import configuration data, it overwrites the configuration running on the MARS Appliance
Note
and reboots the appliance. After rebooting, the MARS Appliance assumes the IP address, hostname, and
username/password of the appliance from which the configuration archive was exported.
The configuration import runs in the foreground displaying its status and errors immediately, where as
event data export runs in the background. Use the log {all | recent} command to view the running status
log for event data import.
Recent data is imported first. If an NFS-related problem results in a file not being imported properly, the
pnimp import program halts and logs an error to the
file.
/log/migrationrestore.log
The next time the import operation is started, you are prompted whether to retry the last failed file. If
no, the import operation continues with the next file. If another problem occurs, for example, a file
corruption, that prevents a file from being imported, pnimp import generates a log similar to "file
es_334_...gz is imported with error!" and continue with the next file.
When the import operation completes, the Local Controller begins to rebuild the RAW message indices.
You can use the web interface although keyword query will remain slow until the indices are rebuilt.
Examples
The following example specifies that the MARS Appliance should import the configuration data from
the NFS archive found at 192.168.3.138/storage/mars_migration/:
[pnadmin]$ pnimp
pnimp> import config 192.168.3.138:/storage/mars_migration/LC-220_2007-09-04-11-25-10
09/04/07
The most recent configuration archive from 4.3.1 release or later found on the NFS server
was created at 2007-09-04-11-25-10. Because events received after the config archive was
created may not be imported correctly later on when you try to import event data, so if
possible, you should always use 'pnexp' to export a fresh copy of configuration from the
Gen-1 MARS box before trying this command.
Do you wish to continue (yes/no) : yes
WARNING: this operation will overwrite current MARS box's configurations (both system and
DB) and reboot the machine. After reboot, current MARS box will take over the IP address,
hostname and MARS username/password of the MARS box from which the config archive was
exported, please make sure there will be no IP address conflict.
Do you wish to continue (yes/no): yes
!!! Stopping CS-MARS processes ...
Invoking binary config importing procedure ...
Recreating the database schema.
Importing data into database ...
Configuration data binary import done.
Configrestore succeeded!
!!! Updating system settings ...
Broadcast message from root (pts/5) (Wed Jun 13 15:23:46 2007):
The system is going down for reboot NOW!
[pnadmin]$
Install and Setup Guide for Cisco Security MARS
A-36
OL-14672-01
Advertisement
Chapters
Troubleshooting
