Difference between revisions of "CCNP 3 Implementing Inter-VLAN Routing"
From Teknologisk videncenter
m (New page: =Describing Routing Between VLANs= ==Inter-VLAN Routing Using an External Router== {| |800px|left|thumb|Inter VLAN Routing |- |[[Image:ScreenShot381.jpg|800px|l...) |
m (→Configuring Inter-VLAN Routing Using an External Router) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
|[[Image:ScreenShot382.jpg|800px|left|thumb|802.1Q Trunk configuration]] | |[[Image:ScreenShot382.jpg|800px|left|thumb|802.1Q Trunk configuration]] | ||
|- | |- | ||
| − | |[[Image:ScreenShot383.jpg|800px|left|thumb| | + | |[[Image:ScreenShot383.jpg|800px|left|thumb|ISL Trunk configuration]] |
|} | |} | ||
| + | |||
==Explaining Multilayer Switching== | ==Explaining Multilayer Switching== | ||
{| | {| | ||
| Line 17: | Line 18: | ||
|- | |- | ||
|[[Image:ScreenShot385.jpg|800px|left|thumb|L3 Switching packet flow]] | |[[Image:ScreenShot385.jpg|800px|left|thumb|L3 Switching packet flow]] | ||
| + | |} | ||
| + | ==Frame Rewrite== | ||
| + | {| | ||
| + | |[[Image:ScreenShot386.jpg|800px|left|thumb|Packet rewrite]] | ||
| + | |- | ||
| + | |[[Image:ScreenShot387.jpg|800px|left|thumb|Content Addressable Memory]] | ||
| + | |- | ||
| + | |[[Image:ScreenShot388.jpg|800px|left|thumb|Ternary Content Addressable Memory]] | ||
| + | |} | ||
| + | =Enabling Routing Between VLANs= | ||
| + | ==Describing Configuration Commands for Inter-VLAN Communication on a Multilayer Switch== | ||
| + | {| | ||
| + | |[[Image:ScreenShot389.jpg|800px|left|thumb|Multilayer configuration]] | ||
| + | |} | ||
| + | |||
| + | ==Describing Routed Ports on a Multilayer Switch== | ||
| + | {| | ||
| + | |[[Image:ScreenShot390.jpg|800px|left|thumb|Routed switchport]] | ||
| + | |- | ||
| + | |[[Image:ScreenShot391.jpg|800px|left|thumb|Routed switchport configuration]] | ||
| + | |} | ||
| + | =Deploying CEF-Based Multilayer Switching= | ||
| + | ==Explaining Layer 3 Switch Processing== | ||
| + | {| | ||
| + | |[[Image:ScreenShot392.jpg|800px|left|thumb|Switch Processing]] | ||
| + | |} | ||
| + | There is a wide range of CEF-based Cisco multilayer switches: | ||
| + | |||
| + | *Catalyst 2970 | ||
| + | *Catalyst 3550 | ||
| + | *Catalyst 3560 | ||
| + | *Catalyst 3750 | ||
| + | *Catalyst 4500 | ||
| + | *Catalyst 4948 | ||
| + | *Catalyst 6500 | ||
| + | ==Identifying the Multilayer Switch Packet Forwarding Process== | ||
| + | {| | ||
| + | |[[Image:ScreenShot394.jpg|800px|left|thumb|MLS lookup]] | ||
| + | |- | ||
| + | |[[Image:ScreenShot395.jpg|800px|left|thumb|ARP Throttling]] | ||
| + | |- | ||
| + | |[[Image:ScreenShot396.jpg|800px|left|thumb|MPLS operation]] | ||
| + | |} | ||
| + | *'''Null adjacency:''' Packets destined for a null0 interface are dropped. This can be used as an effective form of access filtering. | ||
| + | *'''Glean adjacency:''' When a router is connected directly to several hosts, the FIB table on the router maintains a prefix for the subnet rather than for the individual host prefixes. The subnet prefix points to a glean adjacency. When packets need to be forwarded to a specific host, the adjacency database is gleaned for the specific prefix. | ||
| + | *'''Punt adjacency:''' Features that require special handling, or features that are not yet supported in conjunction with CEF switching paths, are forwarded to the next switching layer for handling. For example, the packet may require CPU processing. Features that are not supported are forwarded to the next-higher switching level. | ||
| + | *'''Discard adjacency:''' Packets are discarded. | ||
| + | *'''Drop adjacency:''' Packets are dropped, but the prefix is checked. | ||
| + | ==Describing CEF Configuration Commands== | ||
| + | {| | ||
| + | |[[Image:ScreenShot397.jpg|800px|left|thumb|Configure CEF]] | ||
| + | |- | ||
| + | |[[Image:ScreenShot398.jpg|800px|left|thumb|Switching Methods]] | ||
| + | |} | ||
| + | =Summary= | ||
| + | {| | ||
| + | |[[Image:ScreenShot400.jpg|800px|left|thumb|Chapter Summary]] | ||
|} | |} | ||
Latest revision as of 13:33, 8 September 2010
Contents
Describing Routing Between VLANs
Inter-VLAN Routing Using an External Router
Configuring Inter-VLAN Routing Using an External Router
Explaining Multilayer Switching
Frame Rewrite
Enabling Routing Between VLANs
Describing Configuration Commands for Inter-VLAN Communication on a Multilayer Switch
Describing Routed Ports on a Multilayer Switch
Deploying CEF-Based Multilayer Switching
Explaining Layer 3 Switch Processing
There is a wide range of CEF-based Cisco multilayer switches:
- Catalyst 2970
- Catalyst 3550
- Catalyst 3560
- Catalyst 3750
- Catalyst 4500
- Catalyst 4948
- Catalyst 6500
Identifying the Multilayer Switch Packet Forwarding Process
- Null adjacency: Packets destined for a null0 interface are dropped. This can be used as an effective form of access filtering.
- Glean adjacency: When a router is connected directly to several hosts, the FIB table on the router maintains a prefix for the subnet rather than for the individual host prefixes. The subnet prefix points to a glean adjacency. When packets need to be forwarded to a specific host, the adjacency database is gleaned for the specific prefix.
- Punt adjacency: Features that require special handling, or features that are not yet supported in conjunction with CEF switching paths, are forwarded to the next switching layer for handling. For example, the packet may require CPU processing. Features that are not supported are forwarded to the next-higher switching level.
- Discard adjacency: Packets are discarded.
- Drop adjacency: Packets are dropped, but the prefix is checked.
