Posted by: Pete Welcher
on Oct 30, 2009
In October 2009, Dr. Pete Welcher presented
these slides at a Bluesnet Network Advisory Group meeting in Santa Barbara, CA. This presentation covers RF (radio frequency) essentials you need to make Wireless LAN (WLAN, WiFi, 802.11) work well. Click this link to review the
RF for 802.11 WLAN (784 KB) seminar PDF.
Posted by: Pete Welcher
on Oct 29, 2009
In October 2009, Dr. Pete Welcher presented
these slides at a Bluesnet Network Advisory Group meeting in Santa Barbara, CA. This presentation covers some of the acronyms and basics of Wireless LAN (WLAN, WiFi, 802.11). Click this link to review the
WLAN Basics (654 KB) seminar PDF.
Posted by: William Bell
on Oct 27, 2009
In September I discussed a feature called "Call Forward Unregistered" or CFUR. The point of this feature is to allow administrators to specify special call handling rules when an SRST enabled device was unregistered. I wanted to use CFUR as an example to illustrate how Local Route Groups and other CUCM7x dial plan features can be leveraged to simply admin tasks and improve an overall dial plan architecture.
Posted by: Carole Warner Reece
on Oct 21, 2009
Tagged in:
VRF-Lite ,
VRF ,
virtualization ,
static routes ,
shared services ,
redistribution ,
Multi-VRF ,
fusion router ,
EIGRP ,
design ,
data center
Part 2 of my experiments with VRF-Lite, which provides more thoughts on whether the customer edge (CE) device should run one or more VRFs. (Part 1 is available here CE Design Options When Using VRF-Lite End-to-End, and discusses using the CE as a "fusion" router to support dynamic routing the customer routing process(es) with the shared service VRFs by using multiple EIGRP processes on the CE without any VRFs.)
Posted by: Carole Warner Reece
on Oct 18, 2009
Tagged in:
VRF-Lite ,
VRF ,
virtualization ,
static routes ,
shared services ,
redistribution ,
Multi-VRF ,
fusion router ,
fusion ,
EIGRP ,
design ,
data center
I've been testing some end-to-end VRF-Lite configurations, and I've been thinking about whether the customer edge (CE) device should run one or more VRFs. Like many design choices in networking, the decision to run VRFs on your CE devices depends on your application and your network.
Posted by: William Bell
on Oct 17, 2009
A colleague of mine asked if I would do a blog on using the AXL/SOAP interface to execute custom queries for administrative purposes. I thought that this would be an interesting topic to cover. Though, it isn't something that can be fully addressed in one blog. So, I think this will need to be a series of blogs/articles. For Part 1 I think we will discuss the basic table structures and some key tables that are commonly queried by admins.
Posted by: Pete Welcher
on Oct 15, 2009
Tagged in:
xconnect ,
vlan-based EoMPLS ,
PWE ,
pseudowire ,
pseudo-wire ,
port-based EoMPLS ,
Layer 2 tunnel ,
Layer 2 over Layer 3 ,
L2 over L3 ,
jumbo ,
Ethernet over MPLS ,
EoMPLS ,
data center interconnect ,
Cisco 6500
That's "Ethernet over M
PLS" to you! My blog from a couple of days ago mentioned that the Catalyst 6500 with Sup720 has great forwarding performance with EoMPLS, without adding any specialized hardware such as the SIP or ES cards. See http://www.netcraftsmen.net/resources/blogs/extended-vlan-mitigation.html for the context.
In this blog, I intend to write (briefly, I think I can manage briefly...) about the basics, then show the lab tested configuration snippets.
Posted by: William Bell
on Oct 14, 2009
Recently I fielded a request from a customer to explain how they could restrict access to the Corporate Directory and Personal Directory from an IP phone. I checked into it and found that CUCM 7.x introduces a few changes that actually allows administrators to properly address requests like this one.
Posted by: Pete Welcher
on Oct 13, 2009
This blog is a quick summary of some port-related
tidbits I've run across recently.
Posted by: Pete Welcher
on Oct 11, 2009
This article is triggered by some recent work
I've been doing. We are migrating a customer with an old Nortel switching infrastructure to a high-speed Cisco 6509-based infrastructure with a lot of 10 Gbps links. Our design calls for Layer 3 (routing) to the closet or server zone. There are some nifty Spanning Tree mitigation techniques coming (or replacements that allow use of many paths in a L2 infrastructure). That technology is not quite here yet.