Putty – Auto Save Sessions

Problem

Remembering what happened in your last putty session!

Solution

Within Session > Logging > {all session output } insert the following

C:\Users\<user>\Documents\Projects\PUTTY SESSIONS\&H-&Y&M&D&T.log

It will save all session output into the folder specified with the filename of Host-Year-Month-Day-Time.log

Save this in the default profile to enable it for future use.

I am using putty Release 0.67

 

F5 – TCPDump Basics

Problem

Needing to monitoring the traffic on an F5.

Solution

Running a packet capture over SSH and then grabbing the file using sftp or winscp.

tcpdump -s0 -nni 0.0 host <Client_IP> and port <number> and host <VS_IP> -w /var/tmp/Monitor_Resets.pcap

 where:
-s0 gives the complete packet.
-nni disable service port lookups, dns lookups and specifies internal interface

 

All the rest of the options can be found at F5 here.

 

Cisco Firepower 6.1.0 Upgrade Fail

 

Problem

I hit this Firepower bug while upgrading two 5525x firepower modules to 6.1.0.  Everything appeared normal until i got to one of the 6.1.0 firepower images.

The error appeared in the sfr console logs as:

Cisco-Firewall# show module sfr log console

DB error - will retry: Cannot connect to DB at /usr/local/sf/lib/perl/5.10.1/SF/SFDBI.pm line 588.
DB error - will retry: Cannot connect to DB at /usr/local/sf/lib/perl/5.10.1/SF/SFDBI.pm line 588.
DB error - will retry: Cannot connect to DB at /usr/local/sf/lib/perl/5.10.1/SF/SFDBI.pm line 588.

Solution

This ties in with following bug at Cisco.com.

Re-imaging SFR module to 6.1 fails on ASA version 9.5(2) : CSCvb53856

An upgrade to the ASA software to 9.6 resolved the issue!