* A look at what topics need to be included in a WAN architecture
In the last newsletter, we began the discussion of what topics need to be included in a WAN architecture. We discussed the fact that Cisco’s Application eXtension Platform (AXP) allows IT organization to embed applications into their Integrated Services Router. This is an option that has not been available previously and IT organizations need to make a decision as to whether or not they want to make use of this new capability.
In the last newsletter, we began the discussion of what topics need to be included in a WAN architecture. We discussed the fact that Cisco’s Application eXtension Platform (AXP) allows IT organization to embed applications into their Integrated Services Router. This is an option that has not been available previously and IT organizations need to make a decision as to whether or not they want to make use of this new capability.
Cisco’s AXP is just one example of a new functionality that IT organizations can choose to implement in their routers. WAN optimization controllers (WOC) is another example. WOCs have been available in the marketplace for a number of years. Recently, a couple of vendors have started to integrate WOCs into routers. IT organizations need to decide if they want to deploy routers that integrate WOC functionality or if they prefer to implement WOCs as a stand-alone device.
Part of that decision process involves understanding what it means when a vendor says that they have integrated WOC functionality into a router. At one extreme, the WOC is a blade that gets power from the router and otherwise does not function any differently than if it was an external device. At the other extreme, the WOC interacts with other router functionality in ways that add real value. This is a critical distinction and IT organizations cannot make a good decision about whether or not an integrated WOC is a good idea without understanding the level of integration between the WOC and the router.
There is a lot of similarity between the question of whether or not to embed applications inside a router and the question of whether or not to integrate WOC functionality inside of a router. In essence, there are two very different architectural views presented by these questions. In one view, the router does traditional packet processing and other devices do Layer 4 through Layer 7 processing and application hosting. In the other view, the router is the device, at least in some offices, for any and all processing.
This is the last newsletter on the topic of WAN architecture for a while, although undoubtedly we will come back to this important topic again soon. In the meantime, we would like to hear from you. How does your organization view its WAN routers? Are they merely packet processors or do you see them as being the platform for a wide range of functionality?
