Check DNS Propagation

Great online utility to check propagation of DNS changes.https://www.whatsmydns.net

Save Encrypted Passwords to Disk with PowerShell

Save Encrypted Passwords to Disk with PowerShell

Packet Capture

The challenge I often have for capturing packets is that I need 2 interfaces on the machine doing the capture. It has been problematic to use the wired NIC on the span port and using the wireless NIC for remote access to the laptop. I am tempted to do the following: - setup the span port on the interface where the only wired NIC of the laptop is attached. But don't enable it yet. - remote control and setup wireshark to capture from the wired NIC. Start the capture. - enable the span port on the switch. This will prevent remote access to the laptop during the capture. - when ready, disable the span config on the NIC. - remote control to the laptop and stop the capture. The advantage is I could use whatever machine is available instead of having to get a local person to setup a laptop and (try to) tell me what the wireless IP address is.

How to solve Windows 7 crashes in minutes | Network World

How to solve Windows 7 crashes in minutes | Network World: How to solve Windows 7 crashes in minutes

Jumbo Frames

Hurts my head to think about attempting jumbo frames.
http://www.bitplumber.net/2009/03/how-to-configure-jumbo-frames/

Cisco Nexus: EthAnalyzer

I've been fighting with getting EthAnalyzer trying to get it to do something useful.  But it always only showed me traffic to/from the switch itself, not packets that pass through it. 
Today I found the following information and EUREKA!
ethanalyzer data plane traffic analysis



ACLs and Ethanalyzer for Data Plane Sampling:

The Ethanalyzer captures only traffic on CPU, so seems as unsuitable solution for the data plane traffic analysis. However, this limitation can be avoided with a use of ACL logging to sample specific packets from data plane.

              .   .   .

When we use ACLs and the “log” keyword, access control entries (ACEs) with log keyword cause system to punt a copy of matching packets to supervisor CPU. Key point is that original traffic forwarded or dropped in hardware with no performance penalty. Note that punted copies subjected to hardware rate limiter, forwarding engine hardware enforces rate to avoid saturating inband interface/CPU.

So the following accomplished what I have been trying to do for a long time:

IP access list acl-cap

  10 permit ip 10.10.10.11/32 any log

  20 permit ip any any

Eth6/28

  ip port access-group acl-cap in

ethanalyzer local int inband limit-captured-frames 0 autostop duration 60 write bootflash:test-2.pcap