Blog

One of the new technology rages in the market today is Cloud Computing (and Storage), of which S3, SQS, SimpleDB, EC2, and HaDoop) is one example.  As I was reading [...]

We were talking with Debra Curtis of Gartner yesterday about Network Configuration and Change Management (Network World blog by Jamey  Heary in which he describes new features of IOS 12.4(20)T.  [...]

Jamey Heary, CCIE No. 7680, who writes for Network World’s Cisco Subnet, recently wrote about a set of Applied Infrastructure blog under

I discovered a patent application (not yet granted) this week that gave me chills.  Part of its claims* are performing Layer 2 and Layer 3 network topology discovery and display, [...]

I’ve done a few seminars on troubleshooting VoIP at VoiceCon (Fall 07 and Spring 08).  Somewhere along the way, someone mentioned a relatively new web site to me: Network Symptoms [...]

In my last post, I described a common repository for EOL/EOS data for all vendors.  Continuing the wishful thinking, I propose that vendors publish the power consumption and heat generation [...]

You can save a lot of money by identifying obsolete products in your network that are costing more money to  keep on maintenance contracts than replacement products cost.  Vendors announce [...]

One of the NetCraftsmen engineers mentioned a condition where CDP can potentially leak information — this is based on a thread on the c-nsp mailer.   An organization had ‘cdp off’ [...]

Stuart Biggs, who was awarded CCIE number 1025, was able to track down the original CCIE lab’s number plaque and get a picture (see below).  I asked where it was [...]

Network World published an article yesterday, Netcordia down the path of creating a network analysis product.  By proactively finding an fixing common network problems, the networking team can make the [...]

Pv6 and the addresses are big and difficult to remember.  Upon initial configuration of network gear, it is tempting to use the EUI-64 encoding ( Applied Infrastructure blog under

It looks like Cisco has been fixing NAT issues with DMVPN. They fixed the NAT issue for spokes talking to the hub using NAT traversal. This is the same method that VPN clients use. It uses UDP port 4500 to send the IPSec traffic instead of IP protocol 50 (ESP) and IP protocol 51 (AH).