Posted by: Rob Chee
on Feb 9, 2010
The Cisco AnyConnect VPN client is Cisco’s SSL VPN client offering. Cisco currently supports this VPN client and the legacy IPSec VPN client, called the Cisco VPN Client. The Cisco VPN client will be phased out over time. This can be seen by the Cisco VPN Client FAQ explaining that 64 bit operating systems are not supported by the Cisco VPN client, but are supported by the Cisco AnyConnect VPN client.
Posted by: Terry Slattery
on Sep 1, 2009
Tagged in:
TTL exceeded ,
troubleshooting ,
TCP throughput ,
spanning tree ,
redundancy ,
redundancy ,
packet loss ,
OSI layer ,
NetMRI ,
Mathis equation ,
high availability ,
failure domains ,
debugging ,
configuration policy ,
bit error rate ,
BDP
Here is a recap of articles I posted in August to my blog at Netcordia:
Posted by: Carole Warner Reece
on Aug 10, 2009
Tagged in:
wireless ,
VPN ,
Unified Communications ,
troubleshooting ,
TCP ,
Security ,
REGEX ,
Layer 2 ,
Infrastructure ,
IGP ,
data center ,
BGP
As part of our booth display at CiscoLive /Networkers 2009, we put together a set of online questions that covered various networking topics from Layer 2 Switching to VoIP to the Data Center to Prefix-Lists. There is feedback for all the questions.
I think the questions range from CCNA to CCDE level questions. You can run a mini-quiz on any and all the topics you feel most comfortable with here:
Network Challenge Quizzes
Please feel free to submit your comments as suggestions for new questions!
Posted by: William Bell
on May 6, 2009
NetCraftsmen provides a UC Optimization service where we will perform, among other things, a general health check on an existing cluster. Some times this is done as part of a routine optimization task. As of late, we perform this task as part of upgrade preparations.
Anyone who has run CallManager (CM) on a Windows platform for any length of time knows that performing quick analysis of a problem is a daunting proposition. There are tools available that can help make analyzing logs easier.
Posted by: Terry Slattery
on Apr 28, 2009
Here is a recap of articles I posted in April to my blog at Netcordia:
-
"
Network SLA Methodologies" discusses the the types of data needed for SLA calculations. It also discusses useful calculation methodologies.
- "Network SLAs - Which One to Use?" discusses some ways to select your network SLAs.
- "The Network Microscope" describes my vision of the ultimate network microscope. This tool would tell me who is sending how much of what data on a link.
- "Mean Time to Convince" offers some ideas about little know components of MTTR. You probably have heard of MTTR - Mean Time to Repair. But you may want to learn about some underlying MTTR components - MTTC, MTTG, and MTTI.
Posted by: William Bell
on Dec 1, 2008
I offer you a handy dandy tool for testing, resetting, validating DSPs on a Cisco voice gateway (tested on ISR models):
Posted by: Carole Warner Reece
on Aug 14, 2008
Paris Traceroute is a new implementations of traceroute available that can infer multiple paths for Unix systems. More information is available at
http://www.paris-traceroute.net/
Posted by: Carole Warner Reece
on Jun 29, 2008
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' on a POS1/0/0 interface which is an STM-16 link. After changing the encapsulation from ppp to hdlc, the IOS automatically changes CDP to be on without even a system message. This could be an issue if you are trying to maintain a secure router.
This behavior has been documented in CSCso40579, but has been marked closed. CSCso59137 (sev=4) documents the behavior as working as designed. This bugid will print a CDP status change message when such an event occurs.
Moral of the story - if you want your router to stay secure, always double check your settings after making configuration updates since things might change without you knowing it.
Posted by: Carole Warner Reece
on Dec 1, 2007
One of our engineers wanted to get debug information about ISAKMP after a system reboot but found it was difficult to login quickly enough after the reboot. He found a way to get debug running without needing to login to the router and manually enter the debug commands.
For IOS devices which support the "do" command it is possible to put a "do debug ..." string b into a text copy of the config file and then TFTP this file to startup.
When the router reboots, the debugs run. It worked well for him, in terms of getting debug output when he wanted it.
Resources 
