The first element to a QoS policy is to classify/identify the traffic that is to be treated differently. Following classification, certain “marking tools” can set an attribute of a frame or packet to a specific value. Such marking (or remarking) establishes a trust boundary that scheduling tools later depend on. Read more…
Stretch, from Packetlife.net recently produced an excellent article explaining IPv6 and EUI-64 addressing. The article is reproduced, verbatim, here: Read more…
Because it is part of Cisco IOS software, NetFlow enables networks to perform IP traffic flow analysis without deploying external probes, making traffic analysis economical even on large IP networks. Read more…
A base Access List for any internet facing router, re-produced from Mike Storm and Jeremy Cioara’s blogs:
Here is a basic overview of MPLS describing:
This article discusses configuration of the 6to4 tunnel on an IOS-based access router, however this concept applies to any router or end host which supports 6to4 tunneling and has a global IPv4 address. Read more…
Cisco switches perform most Quality of Service (QoS) operations in hardware, while routers perform QoS functions in software. It is best practice to use the switch to perform deep packet classification and marking functionality on the switches. The router will need to re-classify the packet, but the classification can be on the DSCP marking rather than a transport layer port number. Read more…
The 3550 is either a Layer 2 (L2) or Layer 3 (L3) switch, which depends on the software version and feature set that you install.
The naming conventions for 3550 images begin with either of these: Read more…
MPLS is deployed for managing traffic on IP networks, and in conjunction with other technologies like VPNs, will eventually replacing all other services, including dedicated T1s, Frame Relay, ATM and ISDN.
Read more…
