At the moment we’re running Cisco Prime Infrastructure 2.1 on a Gen1 physical appliance. We’re looking to take the upgrade path from 2.1 all the way up to 3.1 (currently only 3.0.2 is supported on the Gen1 appliance).
First stop, 2.2.
The Gen1 appliance upgrade path isn’t a fun one. It requires that we back up our current application database, wipe our appliance, do a bare-metal install of 2.2, and then restore our application database. Cisco’s documentation for application backup and restore can be found here: http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-2/administrator/guide/PIAdminBook/backup_restore.html#72460
Back up the PI application database to an FTP repository (I recommend FileZilla Server for hosting a light-weight FTP server on your workstation).
- Create a ftp repository on your Prime Infrastructure server via CLI
- SSH to PI
user username password plain password
- Verify your repository configuration
- Backup your Prime Infrastructure application
backup backup-name repository repository-name application NCS
Install Prime Infrastructure 2.2
Reboot your appliance from the PI 2.2 installation media and follow the on-screen configuration prompts. For more information follow Cisco’s Installation Guide
Restore your application database
- SSH to the Prime Infrastructure server and setup your ftp repository again
user username password plain password
- Verify your repository configuration, and check that your backup is there
- Run the restore command, taking note of the scary warnings
restore BACKUP_NAME.tar.gpg repository REPOSITORY_NAME application NCS
After upgrading our Firepower Management Center to 6.0, we noticed that usernames were no longer populating in our dashboards. Instead of showing users, all we could see was “No Authentication Required.”
After opening a support case, TAC pointed me to the following bug: cscux39125 (cisco login required).
To resolve the issue we need to set the active directory domain to our domain’s NetBIOS short name in Firepower’s realm configuration.
To change your realm configuration go to System -> Integration -> Realms
Go to Realm Configuration and edit the AD Primary Domain field to your domain’s NetBIOS short name.
For more information see the following support forums post: https://supportforums.cisco.com/discussion/12879381/sourcefire-60-firesight-mc-60-users-not-populating
Just got in a new Cisco ISR 4431 and needed to upgrade IOS-XE out of the box. Cisco has been nice enough to include a 1Gb USB flash drive with their new ISRs, making the software upgrade process a cinch. Here are the steps involved to install a new version of IOS-XE via USB drive.
- Download your chosen version of IOS-XE from cisco.com. Keep in mind there are often may different trains and revisions of code available.
- To help you decide which version of code is right for you, there’s the cisco IOS feature navigator found here.
- To help differentiate the different designations of code, i.e., MD, ED, GD, take a look here.
- Typically I opt for a gold star release, which are cisco recommended releases “based on software quality, stability and longevity.”
- Copy the downloaded image to your USB drive and insert it into the ISR
- Copy the IOS-XE image from the usb to the ISR’s bootflash
- Enter global configuration mode and set the ISR to boot from the new image
boot system flash bootflash:isr4400-universalk9.03.13.05.S.154-3.S5-ext.SPA.bin
- Verify the correct boot system parameters
- Save your configuration
copy running-config startup-config
- Reload the ISR
- When the device finishes reloading, verify that the device is running the correct version of IOS-XE
This type of software installation is referred to as a consolidated package. Cisco also supports the installation of individual packages from an IOS-XE image. To see Cisco’s full documentation for software configuration on an ISR 4400 as well as instructions for consolidated and individual package installs please see here.
I don’t know about you, but self-signed certificates seem to trigger my IT OCD. When possible, I like to replace self-signed certs with one signed by our Active Directory CA. Here are the steps involved to replace the self-signed certificate on Cisco’s FirePOWER Management Center/SourceFire Defense Center with one signed by your internal Active Directory Certificate Authority.
- In Defense Center, go to System -> Configuration -> HTTPS Certificate
- Click “Generate New CSR”
- Fill out the Certificate Signing Request information, paying attention to the common name field. The common name should match the address you use to access defense center, e.g., defensecenter.domain.org
- Click generate, and copy/paste the certificate request output to notepad
- Next, navigate to your Certificate Services website and click “Request a Certificate”
- Click “Submit an advanced certificate request”
- Under “Saved Request,”paste your certificate request output from earlier and select the Web Server certificate template. Click Submit
- Download your newly generated certificate (Base64 encoded) and open it with your text editor of choice
- Copy the output of your cert and go back to Defense Center. Navigate to System -> Configuration -> HTTPS Certificate
- Click Import HTTPS Certificate and paste your certificate information into “Server Certificate”
- Click “Save” and you should now see your new certificate installed.
- Reload Defense Center and you should now trust the web server (assuming of course you trust the root CA)
On Windows I love the lightweight and open source TFTPD32, but there may come a time when you find youself needing to transfer some files and all you have is your trusty mac.
Luckily there’s a built in tftp daemon that you can use in a pinch.
By default tftpd uses the following folder:
which is hidden in finder, but can be accessed by using “go to folder” or hitting Command+Shift+G and entering /private/tftpboot
To launch the daemon run the following commands:
sudo launchctl load -F /System/Library/LaunchDaemons/tftp.plist
sudo launchctl start com.apple.tftpd
Be sure Read/Write/eXecute permissions are set on the tftpboot folder and any files you wish to transfer:
sudo chmod 777 /private/tftpboot
sudo chmod 777 /private/tftpboot/*
If you’ll be transferring a file TO your TFTP server, the file will technically need to exist on the server beforehand so create it with touch. For example:
sudo touch /private/tftpboot/running-config
sudo chmod 777 /private/tftpboot/running-config
If you’d like a graphical front end for launching tftp then check out the great TftpServer.
Now go ahead and get transferring.