I don’t know if people from Argentina read my blog, but if they do I would like to thank them for their wireless coverage throughout the country. I am traveling for some time through Argentina and I slept in multiple hotels and hostels. Every single hotel and hostel offers some kind of internet connection. Mostly I have the option to use my iPhone and my iBook without extra fees to pay.
Many (public) places broadcast a wireless network, even in places you wouldn’t suspect a wireless network, like a baker or take the little town El Chaltén. El Chaltén doesn’t have an ATM machine. You cannot use your credit card, but there is a wireless internet connection via a satellite uplink. Some wireless networks are open and some have a captive portal configuration to log in. However most wireless networks are protected with a WPA(2) key. I only need to ask for the key and they directly write it down for me.
Security is something the Argentineans are less familiar with. I guess it’s a hobby, but every time I join a wireless network, I always try to access the router / default gateway. When trying to access the router, in most cases you get some kind of login page or basic authentication popup. These kind of pages mostly tell me what kind of router is used. A quick search on the internet for some default passwords already gave me access to three routers. Not so clever to use default password!!!
Internet speeds are also decent. You cannot compare it to the speed in the Netherlands, but I made some SIP phone calls without any problems. Internet access makes the holiday a lot easier, because I have to book multiple hostels and hotel along the ride and I can upload my picture from the camera to the iBook and from there to my NAS at home.
You Argentineans are doing a great job. I hope your friends in Chili are like you, because that is the next stop in a couple of days.
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-126.96.36.19958.zip BD 188.8.131.5258.34 http://software-sj.cisco.com/cisco/crypto/3DES/ciscosecure/cs-mars/csmars-184.108.40.20658.zip
csmars-220.127.116.1129.zip BD 18.104.22.16829.33 http://software-sj.cisco.com/cisco/crypto/3DES/ciscosecure/cs-mars/csmars-22.214.171.12429.zip
csmars-126.96.36.19990-customer-patch.zip B 188.8.131.5290 http://software-sj.cisco.com/cisco/crypto/3DES/ciscosecure/cs-mars/csmars-184.108.40.20690-customer-patch.zip
csmars-220.127.116.1188.zip BD 18.104.22.16888.32 http://software-sj.cisco.com/cisco/crypto/3DES/ciscosecure/cs-mars/csmars-22.214.171.12488.zip
csmars-126.96.36.19902.zip BD 188.8.131.5202.31 http://software-sj.cisco.com/cisco/crypto/3DES/ciscosecure/cs-mars/csmars-184.108.40.20602.zip
The above upgrade packages are available. The packages need to be installed sequentially, so I started with version 220.127.116.1102.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.