Blog Archives

RANCID and restricted user on ASA

You may not want to configure RANCID using yout your default privilege level 15 user when it performs backup of your Cisco ASA. Leveraging commmand authorization will enable granular control of which commands it runs. !– Allowed commands privilege cmd level 4 mode exec command more privilege cmd level 4 mode exec command dir privilege […]

Cisco Prime Infrastructure – SFTP Repository

A quick guide on how to backup your Prime Infrastructure Server to a remote SFTP repository. As of default, defaultRepo, the backup is placed locally on the appliance disk. For obvious reasons, this is not feasible in a production environment. The web interface, found under “Administration > Background Tasks > Other Background Tasks > Prime […]

Cisco Prime Infrastructure 2.0 virtual appliance boot loop

An issue I came across was a virtual appliance stuck in a boot loop after the VMware environment lost its power. The console output was giving off the following text prior to rebooting: Warning: pci_mmcfg_init marking 256MB space uncacheable sda: assuming drive cache: write through sda: assuming drive cache: write through Reading all physical volumes. […]

Converting stand-alone Cisco autonomous access point to lightweight access point

From time to time, IT personell find it feasible to purchase autonomous access points for later converting them to lightweight access points which connects to a central Wireless LAN Controller (WLC). Fortunately for us, the conversion from autonomous to lightweight is simple and straight forward. In this example I’ve converted a SAP1602i access point.

Cisco ASA NAT rule positioning

When you add a new NAT-rule via the CLI of a Cisco ASA, the newly added rule will be appended to the NAT rule list. Tradionally you will have a NAT-hide rule at the very end, in order to provide your clients with IP connectivity to the Internet. Fortunately there is a way to choose […]

Increase TCP timeouts on Cisco ASA – for example traffic destinated to your SQL-server.

Did you ever have a run-in with applications terribly sensitive in terms of losing their database-connection and you need to increase the time-out the TCP-connections to this server? This configuration basically matches all traffic to one specific IP-adress and uses a service-policy to give it a longer timeout value.