Configuration Example, IDS / IPS
Upgrade CS MARS
A customer was running CS MARS with version 4.3.6. Lately the Cisco IPS sensor was upgraded to version 7.x. This version wasn’t supported anymore by CS MARS version 4.3.6. That is why the CS MARS needed to be upgraded to 6.x. I don’t have a lot of experience with CS MARS and I couldn’t find a way to upgrade from 4.3.6 to 6.x.
The only way to upgrade from 4.3.6 to 6.x is by re-imaging the server. At first I started with securing the current configuration. The current configuration can be saved to a NFS server. I secured the current configuration and event data with the following commands:
pnexp > export config 10.1.1.1:/home/NFS
pnexp > export data 10.1.1.1:/home/NFS
The next question I had was: which CS MARS version to download? Searching the documentation I only found a upgrade procedure for upgrade 4.3.6 to 6.0.1. The latest version is version 6.0.5, but I couldn’t find any documentation about upgrading directly from 4.3.6 to version 6.0.5. I decided to upgrade from 4.3.6 to 6.0.1 and then directly to 6.0.5.
Re-imaging the server took about an hour. The installation process didn’t take a lot of time, most of the time was spend on the process of creating an oracle database. After re-imaging I had to import the configuration from the NFS server.
Hmmm…. the server has a fresh installation, so no IP address or whatsoever. First I had to find the default username and password to login to CS MARS. The default username and password is pnadmin. I configured an IP address using the following command:
[pnadmin]$ ifconfig eth0 10.1.1.2 255.255.255.0
Next I was able to access CS MARS through SSH. I imported the configuration and the event data using the following commands:
pnimp > import config 10.1.1.1:/home/NFS
pnimp > import data 10.1.1.1:/home/NFS
The complete configuration, including hostname, dns servers and license, and the event data was nicely restored. Next I wanted to upgrade from version 6.0.1 to directly version 6.0.5. Stunned I was at that moment, I discovered that the different upgrades need to be installed sequentially. The different upgrades have multiple dependencies amongst each other. It is possible to install the upgrade packages through the web interface, but I got some dependency failures during this process.
The only way for me, and I think the best way, was installing the upgrades packages through a SSH session. I let the CS MARS download the required packages directly from the Cisco website by using valid CCO credentials. The first step involved checking which upgrade packages were available using the following command:
Package Name Type Version URL
csmars-220.127.116.1158.zip BD 18.104.22.16858.34 http://software-sj.cisco.com/cisco/crypto/3DES/ciscosecure/cs-mars/csmars-22.214.171.12458.zip
csmars-126.96.36.19929.zip BD 188.8.131.5229.33 http://software-sj.cisco.com/cisco/crypto/3DES/ciscosecure/cs-mars/csmars-184.108.40.20629.zip
csmars-220.127.116.1190-customer-patch.zip B 18.104.22.16890 http://software-sj.cisco.com/cisco/crypto/3DES/ciscosecure/cs-mars/csmars-22.214.171.12490-customer-patch.zip
csmars-126.96.36.19988.zip BD 188.8.131.5288.32 http://software-sj.cisco.com/cisco/crypto/3DES/ciscosecure/cs-mars/csmars-184.108.40.20688.zip
csmars-220.127.116.1102.zip BD 18.104.22.16802.31 http://software-sj.cisco.com/cisco/crypto/3DES/ciscosecure/cs-mars/csmars-22.214.171.12402.zip
The above upgrade packages are available. The packages need to be installed sequentially, so I started with version 126.96.36.19902.31 using the following command:
[pnadmin]$ pnupgrade -d -u <CCO username>:<CCO password> <upgrade package URL>
CS MARS starts downloading the specific upgrade package. The –d parameter tell CS MARS to ask first before installing the upgrade package, because a reboot is required after the installation. I repeated this step for all subsequent upgrade packages.
Now CS MARS is running version 6.0.5 (3358) 34 and the IPS can be added to CS MARS. It took some time, but I am still curious if I could re-image the server directly to version 6.0.5.
Latest posts by René Jorissen (see all)
- MacOS Big Sur and SSLKEYFILELOG - November 23, 2021
- ClearPass, Azure AD, SSO and Object ID - August 12, 2021
- ClearPass – custom MPSK - July 20, 2021
whoever posted this article – thank you. going thru the upgrade here now from 4.3.6 to 6.06 and (as usual) the MARS documentation is pretty much useless, and in this experience, incorrect. The 6.06 install guide says the “only” way to import an upgrade package direct from Cisco CCO is via the GUI. After a day of screwing around (and googling) it seems that the exact opposite was true (here anyway). The GUI option repeatedly fails, hangs – the CLI method (using the URL info in your post) succeeded first crack.
Managing MARS is a perpetual exercise in frustration. Your post was helpful – just wanted to say thanks….