I was able to put the finishing touches on the lab exercise I have been writing for That Study Place. I had a momentary scare, because my final topic was a particular construction that has the look, feel, and taste of a CCIE Lab topic, so I thought it important to cover it in my own work.
( Note that since no one has seen a CCIE Lab scenario containing the 3550's, I want to say everything I can prior to my going into the Lab. That way I protect myself against NDA violations by pointing out that I have actively studied and actively written about the switches prior to my ever seeing or hearing about actual scenarios that contain them. ) The construct in question is called a vlan map. Why I couldn't remember is beyond me. It has an easy pneumonic. Route-map VLAN map The two are very similar in construction. But in application they are a bit different, reflecting the nature of the task each is given to accomplish. first, the similarities. --------------------------- both use access-lists as the basis of their decision process both can be structured using a series of numbered groups, each of which refers to a different access-list, and each of which performs a different set of actions There can be multiple route-maps configured and in use on a router There can be multiple vlan filters configured and in use on a switch the differences -------------------- route-maps are IP only, and use IP access-lists as the basis for operation. route-maps may use ip prefix-lists as their basis for operation vlan maps are L2 and L3 both. vlan maps can refer to L2 access-lists and L3 access-lists in the same map, although not in the same group. for L3 filtering, vlan maps use ip access-lists only - they cannot use ip prefix lists route-maps have a wealth of actions that can be taken as a result of a match to an access-list vlan maps have only two actions - forward or drop route-maps can be applied in many ways for many purposes. they can apply to policy routing of inbound ip packets, redistribution of routing protocols into eachother, information forwarded to bgp neighbors, and more vlan maps apply globally to all traffic in and out of the switch route-maps apply locally - that is, only to the process for which they have been defined and associated. A route-map applied to policy routing has no effect on routing protocol redistribution, for example vlan maps apply globally. one must be careful how one constructs a vlan map. it can effect all traffic into and out of a switch. the application of route-maps involves some use of the term "route-map" e.g. redistribute rip route-map rip-route-filter ip policy route-map bad-boys vlan map application doesn't even involve the term "map" in fact, no where in the configuration is the term "map" used except "access-map" in the following configuration sequence: vlan access-map POLICY 20 action forward match mac address QWERTY a vlan map is applied by: vlan filter POLICY vlan-list 100,150 the biggest gotcha -------------------------- one must beware of configuring vlan filters that overlap vlans. InTheZone(config)#vlan filter AAAAA vlan-list 500-599 InTheZone(config)#vlan filter BBBBB vlan-list 595-605 excerpt from "show run" vlan filter AAAAA vlan-list 500-594 vlan filter BBBBB vlan-list 595-605 note that the most recent entry rewrites the earlier entry. The point of all of this? Beats me. It's been a long day! Still waters. Cool breezes. Another few steps along a long but golden road. Goodnight. everyone -- www.chuckslongroad.info still a work in progress, but on line for your enjoyment z Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=52191&t=52191 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
